This document covers the following topics:

• Listing all Network Definitions

• Selecting a Range of Networks to be Listed

• Commands: Network Maintenance Screen

• Displaying and Modifying a Network Definition

• Adding a Network Definition

• Fields and Commands: Network Definition

• Operating System and Environment Defaults

• Specifying Recipients for Network Messages

• Granting Definition: Authorizing Other Users or Owners to Access a Network

• Documenting Your Networks

• Deleting a Job Network

---

Listing all Network Definitions

To list all networks defined for an owner

• Select the Network and Job Maintenance option on the Main Menu.

  Or:
  Use the direct command LIST NETWORKS as described in the Direct Commands documentation.

  A Network Maintenance screen similar to the example below appears:

  12.03.18 ***** Entire Operations ***** 13:35:38 Owner EXAMPLE Network Maintenance Selection OR________ ------------------------------------------------------------------------------- Cmd Runs Owner Network Node Description *--------- *--------- *---- _ EXAMPLE ADMIN N0146 Administrator workshop _ EXAMPLE ADMIN2 N0146 Administrator workshop _ P * EXAMPLE B60-FLOW N0031 Job Flow, BS2000 _ P EXAMPLE B60-FLOWFX N0031 Job Flow, BS2000 _ P EXAMPLE B60-FLOW38 N0038 Job Flow, BS2000 _ P EXAMPLE B60-FX N0031 Job Flow, BS2000 _ P EXAMPLE B60FLOW194 N0194 Job Flow, BS2000 _ P EXAMPLE B60FLOW211 N0031 Job Flow, BS2000 _ EXAMPLE DEMO-NET N0146 BRY-DEMO-NET _ EXAMPLE EXA-NET1 N0146 Example Network _ P EXAMPLE E01-CO-FX N0146 Completion-Codes, Job Duration *********************************** m o r e ********************************** A Active C Copy D Delete F Flow G Grant H Check L List Jobs M Modify N Deact P Descr R Activate S Schedule T Acct U Vers.Usage W Disp.Sched. X History Command => ____________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add End Save Up Down NxtSt Menu

  When one or more job networks are defined for the owner, they appear in the main information section of this screen.

Columns: Network Maintenance

The Network Maintenance screen contains the following columns:

Column	Description
Cmd	One-character line command input field. Possible values are listed in the command section of the screen (see also the section Line Commands: Network Maintenance).
	Note: The letter L (loop) appears between the Cmd and Runs columns if a loop was found during a loop test for the corresponding network. For further information, see the description of the field Loop.
Runs	Asterisk (*) in this column indicates that one or more active job runs exist for the network.
Owner	Owner name of the network. For possible selection criteria, see Specifying Filter Criteria.
Network	User-defined network name. For possible selection criteria, see Specifying Filter Criteria.
Node	Default execution node for the jobs in the network. For possible range specifications, see Specifying Filter Criteria.
Description	Short description of the network.

Selecting a Range of Networks to be Listed

You can specify the range of networks to be listed by entering one or more of the following values in the Selection field on the Network Maintenance screen and pressing ENTER:

Value	Description
A	Only networks with at least one active run are listed.
G	Granted networks are listed for the current user and the owner selected on the Network Maintenance screen (excluding the current owner).
O	Networks of the current owner are listed. Owner selected on Network Maintenance screen has no effect.
R	Indicate active job runs with an asterisk (*) in the Runs column.
U	Networks granted for the user.

Specify at least O, G or U or combine these values in any order, for example, GUO.

If you enter a question mark (?) in the first position of the Selection field and press ENTER, a Network Selection window opens where you can enter the required value(s).

Commands: Network Maintenance Screen

This section describes the commands available on the Network Maintenance screen:

• Line Commands: Network Maintenance

• Special PF Keys: Network Maintenance

Line Commands: Network Maintenance

You can perform the following functions on any network listed on the Network Maintenance screen:

In the Cmd column of the Network Maintenance screen, you can enter the following line commands to perform the described functions on any network displayed on the screen:

Line Command	Description
A	List all active jobs for the network: proceed as described in To list all jobs defined for a network (section Maintaining Active Jobs and Networks). Use this command to maintain active jobs.
C	Copy all definitions of the selected network for a new network, or clone a network version.
D	Delete the selected network, including all jobs and all other definitions for this network.
F	Display overview of job flow within network.
G	Grant other users or owners access to this network.
H	Check for loops in the network.
L	List all jobs defined for this network: proceed as described in To list all jobs defined for a network (section Job Maintenance). Use this command for job maintenance.
M	Modify the selected network definition.
N	Deactivate active jobs, selectable by dates.
P	Description. Invoke the Entire Operations editor to write an online text description for the selected network.
R	Activate the selected network manually.
S	Network schedule definition.
T	View job/network accounting information. See also the example of report type Accounting Information in the section Reporting.
U	Maintain the usage of network versions.
W	View a network schedule definition as a calendar.
X	Display the execution history (previous network runs).

Special PF Keys: Network Maintenance

You can perform the following functions from the Network Maintenance screen using these PF keys:

PF Key	Name	Function
PF2	Add	Add a network definition.
PF11	NxtSt	Display a system-wide list of all planned job and network activations.

Displaying and Modifying a Network Definition

To view or modify a network definition

1. Type M in the line command field of the selected network on the Network Maintenance screen and press ENTER.

   A Network Modification window opens similar to the example below opens:

   +------------------------------------------------------------------------+ | | | Network Modification | | Owner EXAMPLE Network EXA-NET1__ Version __________ | | Description Example Network_________________________________________ | | Retention Period for Network: ____ Days Loop N | | Deactivation Mode for active Conditions: _ | | | | Default Values for the Jobs | | Execution Node N0146 MVS/ESA Symbol Table __________ | | JCL Node N0146 MVS/ESA Symbol Table Version __________ | | JCL Location ___ Symbol Table Activation Mode X | | Escape Act @ Sub $ | | End-of-Job Action Errors set 'not ok' Conditions ==> N | | File ______________________________________________________ | | VolSer ______ Password | | defined no | | --PF1-----PF3-----PF5---PF6---PF7---PF8---PF9---PF10---PF11--------- | | Help End Save Spec Symb SP-UR DfJb Copy MsgRe | +------------------------------------------------------------------------+

   The window shows the current values defined for the network.

   The fields and commands available are explained in Fields and Commands: Network Definition.

2. Choose PF5 (Save) to save any changes.

3. Choose PF3 (End) to close the window.

Adding a Network Definition

To add a new network definition

1. Choose PF2 (Add) on the Network Maintenance screen.

2. A Network Addition window opens.

   Define the network by entering the required values in the input fields.

   The fields and commands available correspond to the fields and commands available in the Network Modification window. They are described in Fields and Commands: Network Definition.

3. Choose PF5 (Save) to save your new network definition.

4. Choose PF3 (Exit) to return to the Network Maintenance screen.

   The new network is now listed on the screen.

Fields and Commands: Network Definition

The fields in the Network Addition/Modification window are described in the following table:

Field	Description
Owner	Owner of the network.
Network	Network name. Together with owner name, uniquely identifies the network in the master database.
Version	Network version. You can add a new network with a blank (unnamed) version or an alphanumeric version name: see Version Names and Reserved Version Names for Networks. You can use the Network Addition window for all additional versions you want to add to an existing network. New network versions can also be created by copying networks as described in Copying Job Network Definitions. For further information, see Maintaining Job Network Versions.
Description	Short description of the network. This text appears in the list of networks on the Network Maintenance screen. A longer description of the network can be added using the editor (see Documenting Your Networks).
Retention Period for Network	See Retention Period for Network in Retention of Active Network Data.
Loop	Y Loop exists: a loop has been found in the network while linking network jobs via their input and output conditions or while defining input and output conditions of a job. N Loop does not exist: no loop has been found in the network, or no loop test has yet been performed, for example, with the line command H.
Deactivation Mode for active Conditions	See Deactivation Mode for active Conditions in Retention of Active Network Data.
Default Values for the Jobs	The input fields under this heading are used to specify default values for subsequent new job definitions in the network. Each default value specified here can be overridden at the job level.
Execution Node	Default node ID on which jobs within this network are submitted. This value can be modified here or overridden at the job level (see the field Execution Node in Job Maintenance). To list all available nodes, type an asterisk (*) here and press ENTER. The operating system type appears after a valid node number. To display the field help, type a question mark (?) here and press ENTER. You can define the execution node as a symbol. For details, see Symbols in Node Definitions in the section Symbol Table and Symbol Maintenance.
JCL Node	Node on which JCL can be accessed. The default is the same as for the Execution Node. The operating system type appears after a valid node number. You can define the JCL node as a symbol. For details, see Symbols in Node Definitions in the section Symbol Table and Symbol Maintenance.
JCL Location	Type of storage for the JCL: see List of JCL Locations. The default is used in new job definitions and can be overridden there.
Symbol Table	Default symbol table for those jobs in the network that use the dynamic JCL generation facility. Can be overridden at the job level and is therefore optional here. Enter an asterisk (*) and press ENTER to display a selection list of available symbol tables. The selected symbol table can be edited using PF7 (Symb).
Symbol Table Version (symbol table)	You can maintain several versions of a symbol table. Enter an asterisk (*) and press ENTER to display a selection list of available symbol tables. Reserved names: blank Unknown (implicit) version. (current) Is replaced by the current version for the activation date or determination date. (nv) Is replaced by the version of the network used. For further information, see Versioning of Symbol Tables in the section Symbol Table and Symbol Maintenance.
Symbol Table Activation Mode	A During the network activation. No symbol prompting is possible. X After schedule extraction. Symbol prompting can be used for scheduled networks. This is the default.
Esc Act	Activation Escape Character = Network default value This escape character is the prefix for Natural code lines and symbols to be replaced at activation time. Caution: Existing Dynamic JCL might become invalid after changing this escape character and applying defaults to jobs.
Esc Sub	Submission Escape Character = Network default value This escape character is the prefix for Natural code lines and symbols to be replaced at submission time. Caution: Existing Dynamic JCL might become invalid after changing this escape character and applying defaults to jobs.
End-of-Job Action Errors set 'not ok' Conditions	If Y is specified here, for all output condition(s) defined for job events at the step level, the default checks All Checks ok or Any Check not ok are performed after all End-of-Job actions are performed. This includes End-of-Job action (EJA) exits. Any error that occurs in the End-of-Job action processing then causes the setting of the conditions for job not ok. If the job was already set to not ok, it will remain not ok, regardless of the definition here. Notes: Setting this option may cause a longer elapsed time of a network, because the condition setting waits for the termination of the other End-of-Job actions. The network level setting will be overridden by job settings. This option does not change the settings of any conditions defined for any individual events. If N is specified, errors during End-of-Job action processing will have no impact on the job result. Job level: If the field is empty, the network level definition will be inherited at activation time. This is the default. See also the field End-of-Job Action Errors set 'not ok' Conditions in the job master definition.
File	Name of the file or Natural library according to the value of the JCL Location field. For BS2000: The default pubset will be stripped from the file name prior to storing it. This allows easier migration to another default pubset.
VolSer	Volume serial number of data set (if data set is not cataloged).
Password defined	Password if the file or library specified in the File field is password protected: no No password is defined. yes Password is defined.

Retention of Active Network Data

You can specify how long data from an active network run is stored in the active database by using the Retention Period for Network and Deactivation Mode for active Conditions options provided in the Network Addition/Modification window.

The settings specified here override the retention periods for active networks and active conditions, respectively, set in the Entire Operations defaults (see Default Setting (1) in the Administration documentation).

Retention Period for Network

This option is used to keep active network data in the active database for the minimum number of days specified in the Days field.

The following rules apply:

• Valid input values for Days are 1 to 9999.

  If no value is entered in this field (default), the default retention period set for active networks in the Entire Operations defaults is used.

• If the network is not completed within the given period, a warning message is sent to the mailbox(es) associated with the network.

• For unfinished active jobs, the retention periods set in the Entire Operations defaults and the retention period set for the single network calculate the actual retention period as follows:

  (active jobs default - active networks default) + single network period = actual retention period

  Example: (12 days - 10 days) + 5 days = 7 days

Deactivation Mode for Active Conditions

This option is used to remove active job conditions from the active database after a network run.

Possible values are:

0 or blank	Remove active conditions after the period (1 or more days) specified as retention period for active conditions in the Entire Operations defaults under Default Setting (1). This is the default setting.
1	Remove active job conditions set by a network run immediately after the network is deactivated either manually or by an API (application programming interface).
2	Remove active conditions set by a network run immediately after the network is deactivated either manually or automatically.

Special PF Keys: Network Addition/Modification

You can perform the following functions using these PF keys in the Network Addition/Modification window:

PF Key	Name	Function
PF6	Spec	Special definitions for different operating systems and environments.
PF7	Symb	Open the Usable Symbol Tables window, and select a symbol table for browsing or modification. See also Listing Usable Symbol Tables in the section Symbol Table and Symbol Maintenance.
PF8	SP-UR	Define a symbol prompt user exit. See also Specifying User Exits for Symbol Modification in the section Symbol Table and Symbol Maintenance.
PF9	DfJb	Apply network defaults to jobs.
PF10	Copy	Copy a network definition.
PF11	MsgRe	Specify message recipients for the network.

Operating System and Environment Defaults

To specify operating system specific defaults

1. Choose PF6 (Spec) in the Network Modification window.

   An additional window similar to the following opens:

   +----------------------------------------+ | | | Please select the Operating System | | | | _ BS2000 | | _ z/OS | | _ z/VSE | | _ UNIX, Windows | | | | or Environment | | | | _ SAP | | | +----------------------------------------+

2. Choose an entry and press ENTER.

   Depending on the operating system selected, a Network Defaults window similar to the examples below opens:

   For BS2000:

   +-----------------------------------------------------------------+ | | | Network Defaults (BS2000) | | | | Network B60-FLOW Version Owner EXAMPLE | | Description Job Flow, BS2000 | | JCL Node N0194 Execution Node N0082 | | | | Default Values for the Jobs | | Esc Activation _ Submit User ID ________ | | Esc Submit _ SYSOUT User ID ________ | | Default User ID NOP_____ SYSOUT Cat ID ____ | | JCL User ID ________ Job Priority ___ | | Job Class ________ Run Priority ___ | | Account Number ________ | | | | --PF1-----PF3--------PF5-------------------------------------- | | Help End Save | +-----------------------------------------------------------------+

   For z/OS:

   +-----------------------------------------------------------------+ | | | Network Defaults (z/OS) | | | | Network B60-FLOW Version Owner EXAMPLE | | Description Job Flow, BS2000 | | JCL Node N0194 Execution Node N0082 | | | | Default Values for the Jobs | | Esc Activation _ JCL User ID ________ | | Esc Submit _ Submit User ID ________ | | | | | | --PF1-----PF3--------PF5-------------------------------------- | | Help End Save | +-----------------------------------------------------------------+

   For z/VSE:

   +-----------------------------------------------------------------+ | | | Network Defaults (z/VSE) | | | | Network B60-FLOW Version Owner EXAMPLE | | Description Job Flow, BS2000 | | JCL Node N0194 Execution Node N0082 | | | | Default Values for the Jobs | | Esc Activation _ | | Esc Submit _ | | | | --PF1-----PF3--------PF5-------------------------------------- | | Help End Save | | | +-----------------------------------------------------------------+

   For UNIX and Windows:

   +-------------------------------------------------------------------+ | | | Network Defaults (UNIX, Windows) | | | | Network B60-FLOW Version Owner EXAMPLE | | Description Job Flow, BS2000 | | JCL Node N0194 Execution Node N0082 | | | | Default Values for the Jobs | | Esc Activation _ | | Esc Submit _ | | JCL User ID ____________________ | | JCL Group ____________________ | | | | Submit User ID ____________________ | | Submit Group ____________________ | | | | --PF1-----PF3--------PF5--------------------------------------- | | Help End Save | +-------------------------------------------------------------------+

   For SAP:

   +-------------------------------------------------------------------+ | | | Network Defaults (SAP) | | | | Network B60-FLOW Version Owner EXAMPLE | | Description Job Flow, BS2000 | | | | Default Values for the Jobs | | System ID ___ System Number __ | | Client ___ | | | | --PF1-----PF3--------PF5--------------------------------------- | | Help End Save | +-------------------------------------------------------------------+

3. Enter the required values.

   For more information about the specific operating system settings, see the Input Fields: Network Defaults.

4. Choose PF5 (Save) to save your changes and then PF3 (End) to close the window.

This section covers the following topic:

Input Fields: Network Defaults

The input fields available in the Network Defaults window depend on the operating system selected as indicated in the following table:

Field	Description
Esc Activation	Activation Escape Character = Network default value specific for operating system This escape character is the prefix for Natural code lines and symbols to be replaced at activation time. Caution: Existing Dynamic JCL might become invalid after changing this escape character and applying defaults to jobs.
Esc Submit	Submission Escape Character = Network default value specific for operating system This escape character is the prefix for Natural code lines and symbols to be replaced at submission time. Caution: Existing Dynamic JCL might become invalid after changing this escape character and applying defaults to jobs.
JCL User ID	(Not applicable to z/VSE) The user ID to be used for JCL loading
	BS2000: If this field is not empty, the JCL is loaded with the rights of this BS2000 user ID. It can be overwritten with specific definitions. TSOS may only be defined if the user himself has logged on under TSOS. Default: The user ID from the fully qualified file name. If this field is left empty in a job definition, then the Default User ID will be inserted during the activation of the job.
	z/OS: JCL in z/OS will be loaded under this user ID by the Entire Operations Monitor. You can define this field only if you are logged on to the JCL node with the same user ID. Default: If this field is left blank, the user ID of the last modification will be used as JCL user ID.
	UNIX and Windows: With the authorization of this user ID, the Entire Operations Monitor loads the JCL of type TXT.
	See also the default setting User ID Definition (Default Setting (1), Administration documentation), Operating System User IDs and Default User ID Determination.
Submit User ID	(Not applicable to z/VSE) The user ID to be used at job start
	BS2000: The Entire Operations Monitor starts jobs in BS2000 under this user ID. In the network definition, this is a default value for the jobs. If this field is left empty in a job definition, then the Default User ID is inserted during the activation of the job.
	z/OS: The Entire Operations Monitor starts jobs in z/OS under this user ID. You can only define this user ID if you have logged on to the executing node with the same user ID. Default: If this field is empty, the user ID of the last modification is taken as submit user ID.
	UNIX and Windows: With the authorization of this user ID, the Entire Operations Monitor starts the script or the executable program.
	See also the default setting User ID Definition (Default Setting (1), Administration documentation), Operating System User IDs and Default User ID Determination.
Applies to BS2000 only:
Default User ID	This user ID is a default for all objects of this job network or job which are linked to a user ID.
Job Class	This job class is a default for all jobs in the network. It can be overridden by specific definitions.
Account Number	This account number is a default for the Submit User ID defined for the job network. It can be overridden by specific definitions.
Job Priority	If not empty, this job priority will be used during submission and will override a possible setting in the LOGON statement. The default value on network level will be used for new job definitions.
Run Priority	If not empty, this run priority will be used during submission and will override a possible setting in the LOGON statement. The default value on network level will be used for new job definitions.
SYSOUT User ID	This is the user ID under which internal SYSOUT files are created by Entire Operations. If you do not enter an ID here, the Submit User ID is used. See also the default setting User ID Definition (Default Setting (1), Administration documentation), Operating System User IDs and Default User ID Determination.
SYSOUT Cat ID	This is the catalog ID under which internal SYSOUT files are created by Entire Operations. This field is meaningful only if a SYSOUT user ID different from the submit user ID is used.
Applies to UNIX and Windows only:
JCL Group	Applies to UNIX only (optional) If this field is left blank, the standard group of the UNIX user ID is used as defined under /etc/passwd. Otherwise, this field must contain one of the groups issued by the UNIX command groups.
Submit Group	Applies to UNIX only (optional) If this field is left blank, the standard group of the UNIX user ID is used as defined under /etc/passwd. Otherwise, this field must contain one of the groups issued by the UNIX command groups.
Applies to SAP only:
System ID	SAP System ID (SID), as required by jexa4S.
System Number	SAP System Number, as required by jexa4S.
Client	SAP Client Symbol replacement is possible (except at logon).

Specifying Recipients for Network Messages

You can define one or more users (recipients) to receive network-related standard messages that are sent when a specified event occurs. This is especially useful for sending information about the abnormal end of a job.

Among the events, which can cause a message to be sent, are:

• a calendar not defined for next year;

• a network not correctly terminated;

• symbol prompting requests.

The specific message text is generated automatically by the Entire Operations Monitor.

To define or remove recipients for network-related messages

1. In the Network Modification window, choose PF11 (MsgRe).

   A Message and Message Recipients window similar to the example below opens:

   +------------------------------------------------------------+ | | | Owner EXAMPLE Network EXA-NET1 Version | | Job | | | | Message and Message Recipients | | | | Text ==> (Network-related Messages)___________________ | | | | to ==> Destination Type Node | | __________ ________ _____ | | __________ ________ _____ | | __________ ________ _____ | | __________ ________ _____ | | __________ ________ _____ | | __________ ________ _____ | | __________ ________ _____ | | __________ ________ _____ | | | | Execute if temp. Dummy (EOJ only) ===> _ | | Enter-PF1---PF3---------PF5--------PF9---------------- | | Help End Save Delete | +------------------------------------------------------------+

2. Change, add or delete a message recipient as described in Defining Notification Messages and the following sections:

   • Fields and Columns: Message and Message Recipients and

   • Special PF Keys: Message and Message Recipients.

3. Choose PF5 when you are finished.

Granting Definition: Authorizing Other Users or Owners to Access a Network

Entire Operations allows you to authorize other users and owners to access a network that belongs to you.

Users grouped under the owner SYSDBA have unlimited access to all networks in the system. They do not need the authorization described in this section.

Users and linked owners (lower than administrator) have limited access rights to granted networks in accordance with the rights specified in their user profiles and the restrictions specified in their individual network granting definition.

To add or modify a granting definition

1. Type G in the line command field of the selected network on the Network Maintenance screen.

2. Press ENTER.

3. A Granting Definition window similar to the example below opens:

   18-03-12 ***** En +------------------------------------------+ Owner SAGTEST Ne ! ! Selection OR________ ! Owner SAGTEST Network B60-FLOW ! --------------------------------- ! Version (unnamed) ! Cmd Runs Owner Network N ! Granting Definition ! *--------- *--------- ! ------------------------------ ! G P SAGTEST B60-FLOW ! Cmd Type Name Option ! _ SAGTEST SAG-PROMPT ! _ Owner SAGTEST___ O_____ ! _ SAGTEST SAGNET ! _ User_ DEMO______ R_____ ! _ SAGTEST SAGNET-HEB ! _ Owner EXAMPLE___ D_____ ! _ SAGTEST SAGNET-P 5 ! _ _____ __________ ______ ! _ SAGTEST SAGNETHEB ! _ _____ __________ ______ ! _ SAGTEST SAGNETSUB1 ! _ _____ __________ ______ ! _ SAGTEST SAGNETSUB2 ! _ _____ __________ ______ ! _ SAGTEST SAGNET2 ! _ _____ __________ ______ ! ! _ _____ __________ ______ ! ! _ _____ __________ ______ ! ******************************* ! ------------------------------ ! A Active C Copy D Delete F Flow ! D Delete ! P Descr R Activate S Schedule T ! ! Command => _____________________ ! Enter-PF1---PF3-----PF5-----PF7---PF8--- ! ! Help End Save Up Down ! +------------------------------------------+ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add End Save Up Down NxtSt Menu

4. Type in the user ID or owner you want to authorize network access and the access level to be granted.

   The columns and options available are described in Fields: Granting Definition.

5. Choose PF5 (Save) to save the definition.

6. You can enter up to 30 different names and options. If current window is full, choose PF8 (Down) to scroll forward to next window. Choose PF7 (Up) to scroll back to previous window.

7. Choose PF3 (Exit) to return to the Network Maintenance screen.

8. The network appears on the Network Maintenance screen when the authorized user logs on to Entire Operations. You can also use this function to delete existing authorizations.

To delete a granting definition

• In the Granting Definition window, type D (Delete) next to the user or owner whose definition you want to remove and press ENTER.

The users and owners you can remove depend on your user authorization. For the delete restrictions that apply, see Adding and Removing an Owner.

Fields: Granting Definition

The columns and input options in the Granting Definition window are described in the following table:

Column/Field	Description
Cmd	Line command input field. You can enter D to delete a specified user or owner.
Type	Specifies the users to be authorized for network access. Possible options:
	Owner	All users linked to the owner specified in the Name field.
	User	A defined user.
	You can enter O for Owner or U for User.
Name	User or owner to be granted network access. If the access rights are given to an owner, all linked users can obtain these access rights. Use an asterisk (*) for selection.
Option	Authorization level for network access. You can specify one or more (for example RA for read and activate authorization) of the following authorization levels:
	R	Read authorization (maintenance not allowed).
	W	Read and write authorization (maintenance allowed except delete network).
	D	Read, write and delete authorization for the user or owner entered in the Name field.
	O	Read, write and delete authorization. Authorization is also granted to all users and owners possibly authorized by the specified owner.
	A	Activate network authorization.

Documenting Your Networks

You can add a brief description of a job network when defining a network in the Network Addition/Modification window. This short description appears in the list of networks on the Network Maintenance screen.

If you wish to add more online documentation for a network, you can invoke the Entire Operations editor.

To create or modify a detailed description for a job network

1. Type P in the line command field of the selected network.

2. Press ENTER.

3. The Entire Operations editor screen appears:

   Edit Description Nw: E01-CO-148------------------------ ==> Description saved ====> Scroll===> CSR ***** ****************************** top of data ***************************** 00001 Network 'E01-CONTI' 00002 ------------------- 00003 This network consists of 6 independent jobs. Each of them forces 00004 a defined event at end-of-job time. Each job executes the 00005 program 'NOPCONTI' which resides on the installation library 00006 'NOPnnn.LOAD'. The necessary JCL which is named as 'NOPE*' is stored on 00007 the installation library 'NOPnnn.SRCE'. 00008 00009 This is a short description to enable the user to define his 00010 own test examples. 00011 00012 Log Jobname Event at End-of-job 00013 ----------- ------------------- 00014 00015 +---------+ 00016 ! E01-J01 ! Job ended ok. 00017 +---------+ 00018 ! Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help End Rfind Rchan Up Down Impo Left Right Curso

You can enter and edit text using editor commands. For a detailed description of the Entire Operations editor, see the Software AG Editor documentation.

Once a text is written, it can be read by any user who is authorized to access the network. The line command P entered for the network in the list of networks displays the current text.

You can also display or print online documentation in the Entire Operations Reporting Facility (Reports option on the Main Menu - see the section Reporting).

You can also create online documentation at the job level (see the section Job Maintenance).

Deleting a Job Network

Only authorized users can delete a network. Only networks without active runs and version usage can be deleted.

Deleting a network also deletes all definitions made for the network on lower levels using network and job maintenance functions.

Entire Operations saves the last run number of a deleted network. The first run of a new network under the same name receives the last run number incremented by 1.

To delete a network

1. Type D in the line command field of the selected network on the Network Maintenance screen.

2. Press ENTER.

3. If several network versions exist, a Network Version Selection window opens. Select the version you want to delete.

4. A window opens in which you can confirm the deletion by entering the network name.

5. Type in the network name and press ENTER to delete the network.