This document covers the following topics:

• Listing Jobs

• Displaying and Modifying a Job Definition

• Creating a Job Definition

• Writing and Viewing Online Documentation for a Job

• Deleting a Job Definition

• Displaying Job Dependencies and Connecting or Disconnecting Jobs

• Defining Job-Specific Log Information

---

Listing Jobs

This section describes how to list all job masters defined for a network.

Related Topics:

• Listing Active Jobs in the section Active Job Networks

• Listing Jobs of a Subnetwork

To list all jobs defined for a network

1. On the Network Maintenance screen, type L in the line command field of the network for which you wish to list all jobs, and press ENTER.

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

   If several network versions exist, a Network Version Selection window similar to the example below opens first:

   18-03-12 ***** Entire Operations ***** 18:38:08 Owner SA +-------------------------------------------------------------------+ Selectio ! ! --------- ! Network Version Selection ! Cmd Runs ! Owner SAGTEST Network SAGNET ! ! Version Usage ! _ P ! _ (unnamed) unnamed version ! _ P ! _ V1 ! _ P ! _ V2 ! _ ! ! L ! ! _ ! ! _ ! ! _ ! ! _ ! ! _ ! ! _ ! ! ******** ! ! A Activ ! ** Bottom ** ! P Descr ! ----------PF3-----------PF7---PF8----------------------------- ! Command ! End Up Down ! +-------------------------------------------------------------------+ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add End Save Up Down NxtSt Menu

   The window shows a list of the versions defined for a network.
   If a current version exists for the current date, it is presented in the first line.
   The other versions appear in alphabetical order after the current version.
   If necessary, use PF7 to scroll up or PF8 to scroll down.

2. Select the required network version by marking it with any character and press ENTER.

   A Job Maintenance screen similar to the example below appears:

   18-03-06 ***** Entire Operations ***** 10:21:46 Job Maintenance Owner SAGTEST Network B60-FLOW Version ------------------------------------------------------------------------------ Cmd C R PU Job Type Loc Description File or Library Member *--------- --- _ C2R2 JOB-01 DUM Where it all starts _ C1R2P JOB-012 JOB NAT Depending on Job-01 SYSEORU B60-P01 _ C1R2 JOB-013 JOB NAT Depending on JOB-012 B60-M01 _ R2 JOB-015 DUM NAT Depending on JOB-014 _ C1 JOB-019 JOB NAT Depending on JOB-01 B60-M01 _ C1R1 JOB-02 JOB NAT Mail Test BIZDEMO JOB-02 _ C1 JOB-03 NAT NAT Depending on JOB-02 B60-P01 _ C1R1 JOB-04 JOB NAT Depending on JOB-03 B60-M01 _ C1 JOB-05 STC NAT Depending on JOB-04 _ C1R1 JOB-06 JOB NAT Where it all ends B60-M02 _ C3 J2-SUB NAT NAT Subnetwork Job for Su SYSEORU ABX--001 _ C2R1 SUBNETJOB1 NET Subnetwork job for su SAGTEST/SAGNETSUB (D) *********************************** m o r e ********************************** A Dep. B Browse C Copy D Del. E Edit G Pregen. I Input Cond. J JCL L Resources M Mod. O EOJ Chk + Act P Prose R Activate S Sched.Parms U Ext.Log Z Subnet Command => ____________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add End Save Up Down Menu

   This screen displays all jobs defined for the selected network.

   The screen columns are described in Columns: Job Maintenance.

This section covers the following topics:

• Columns: Job Maintenance List

• Line Commands: Job Maintenance

• Special PF Keys: Job Maintenance

Columns: Job Maintenance List

The following table explains the columns of the Job Maintenance screen.

Column	Description
Cmd	One-character line command input field. Possible commands are described in Line Commands: Job Maintenance.
	Special job type. The unnamed column between Cmd and C indicates special job types. Possible indicators are:
	C	Cyclic execution.
	D	Execute as a dummy job but keep definitions
	G	Pre-generated JCL is available. See also Pregenerating Active JCL. This indicator is only displayed if no other indicator is already used for the job.
	P	For job type SRV: Stop a Windows service. For job type STC: Stop a started task.
	R	Recovery job, usually not activated. See also Defining Recovery Actions.
C	If input conditions have been defined for the job listed, C appears here followed by the number of conditions defined. For example: C4 indicates that four input conditions exist. For more than nine conditions, a plus sign (+) appears: C+.
R	If resources have been defined for the job listed, R appears here followed by the number of resources defined for the job. For example: R4 indicates that four resources are defined for the job. For more than nine resources, a plus sign (+) appears: R+.
P	If a description is available for the job listed, P appears here.
U	If extended logging has been defined for the job listed, U appears here.
Job	User-defined job name. In the input field of the Job column, you can make a preselection using a wildcard. The preselection is kept until you switch to another network.
Type	Job type. They are described in the section Job Types. See also the field Job Type described in Fields: Job Definition (Master). In the input field of the Type column, you can enter a job type (for example, DUM) to list jobs of this type only.
Loc	JCL location. (Empty if no JCL is defined, or if no JCL is required for the job type.) For possible JCL locations, see List of JCL Locations.
Description	Short description of the job. Note: The description is truncated if it exceeds 21 characters.
File or Library	Physical storage of JCL according to the JCL location. For a job of the type NET (subnetwork), this column contains the name of the owner and the name of the subnetwork defined for the job (see the jobs J2-SUB and SUBNETJOB1 in the example of a Job Maintenance screen).
Member	The member which contains the JCL. This refers to the JCL location. For possible members, see List of JCL Locations. For a job of the type NET (subnetwork), this column contains a letter (for example, (D)) denoting the subnetwork activation mode.

Line Commands: Job Maintenance

You can perform several functions on any job listed on the Job Maintenance screen using line commands. The following line commands are available:

Line Command	Description
A	Display job dependencies (previous and following jobs). Includes connection and disconnection of jobs. See Displaying Job Dependencies and Connecting or Disconnecting Jobs.
B	Display JCL or a Natural source in read-only mode.
C	Copy a job definition to a new job, including all associated definitions.
D	Delete a job definition, including its input conditions and End-of-Job checking and actions.
E	Edit JCL or a Natural source.
G	Opens an Active JCL Pregeneration window where you can choose a PF key to perform one of the following operations: Edit pregenerated JCL; Pregenerate active JCL; Remove pregenerated active JCL; Browse pregenerated JCL. See also Pregenerating Active JCL in the section Active Job Networks.
I	List input conditions for the job.
J	Define the JCL for the job.
L	Handle prerequisite resources for the job.
M	Modify a job definition: see Displaying and Modifying a Job Definition.
O	Define End-of-Job checking and actions.
P	Invoke the editor to write a long description for the job. See Writing and Viewing Online Documentation for a Job.
R	Activate a single job.
S	Define scheduling parameters for the job. See also Maintaining Schedule Dependencies for a Job.
U	Define extended logging. See Defining Job-Specific Log Information.
Z	List jobs in subnetwork (for jobs of type NET only). See Listing Jobs of a Subnetwork.

Special PF Keys: Job Maintenance

The PF keys of the Job Maintenance screen have the standard behavior, except the following:

PF Key	Description
PF3	Leave the job maintenance screen. If the job maintenance screen has been invoked by the line command Z (Subnet) for a subnetwork job, you will return to the job maintenance screen of the calling network.

The following sections give detailed descriptions of the functions you can perform on each job using line commands.

Displaying and Modifying a Job Definition

To view and modify a job definition

1. On the Job Maintenance screen, type M in the line command input field next to the job you want to view or modify.

2. Press ENTER.

3. A Job Definition (Master) window opens containing the current values for the job:

   12.11.15 ***** Entire Operations ***** 18:01:52 Job Maintenance Owner EXAMPLE Network B60-FLOW Version ------------------------------------------------------------------------------ +------------------------------------------------------------------------+ | | | Job Definition (Master) | | | | Job Name ==> JOB-01____ Mod ==> SAG 24.02.15 12:16 | | Description ==> Where it all starts_______________________________ | 2 | Job Type ==> JOB | 1 | Execution Node ==> N0082 MVS/ESA | 1 | | 1 | Special Type ==> ________ Symbol Table ==> EXAM-ST1__ | | Restartable ==> _ Symbol Table Version ==> __________ | 1 | Suffix Symbol ==> ________________________________________ | 2 | Escape Characters: Activation ==> @ | 1 | Submit ==> $ | 1 | End-of-Job Action Errors set 'not ok' Conditions ==> _ | ** | | | Enter-PF1---PF2--PF3--PF4---PF5---PF6---PF7---PF8---PF9---------PF12- | | Help Add End Edit Save Spec Symb Net JCL Menu | +------------------------------------------------------------------------+ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add End Save Up Down Menu

   You can change the values in the fields described in the section Fields: Job Definition (Master).

   Note:
   Depending on your job type or operating system, you may have to define additional parameters. Choose PF6 (Specials) to open a window with the additional parameters. For further information, see Displaying Job Dependencies and Connecting or Disconnecting Jobs.

4. Choose PF5 (Save) to save all changes.

5. Choose PF3 (End) to return to the Job Maintenance screen.

This section covers the following topics:

• Fields: Job Definition (Master)

• Special PF Keys: Job Definition (Master)

Fields: Job Definition (Master)

The fields in the Job Definition (Master) window are described in the following table.

Field	Description
Job Name	Job name. Entire Operations recognizes a job by this name. It can, but need not be the same name as the JCL source used by the job (the operating system recognizes a job by its JCL name). Note: Job names should start with a character. Job names starting with a digit are tolerated, but are not recommended.
Description	Short description of the job. The maximum input is 50 characters. This text appears in the list of jobs on the Job Maintenance screen. Note: The description is truncated on this list after 21 characters. You can add a long description for the job: see Writing and Viewing Online Documentation for a Job.
Job Type	Job type as defined to Entire Operations. For further information, see the section Job Types.
Special Type	Leave this field empty if this is a normal job or enter one of the following values: (empty field) Normal job without special condition. C - Cyclic execution (This is a replacement and extension of the former CYC (cyclic) job type.) Execution at certain intervals. If this type is specified, a cyclic interval must be defined in the job schedule parameters. This is checked during job activation and before job start. Each job type can be provided with this attribute. Note: You can use the reserved condition P-STOPCYC-jobname to interrupt a cyclic job execution loop. See also reserved condition names in Restrictions for Condition Names. D - Execute as dummy Execution as a dummy job. This allows you to prevent the job from being executed without having to delete the definition. You can also set this type in an active job before a repetition. If this value is deleted in an active job, then the active JCL is generated, provided that it is already present. However, this does not have a resubmission of the job as a consequence. To resubmit the job, use the line command R in the list of active jobs in this case as well. See Resubmitting an Active Job in the section Maintaining Active Jobs and Networks. P - Stop Job Job type STC: Stops a started task. Job type SRV: Stops a Windows service. R - Recovery Job For a recovery job. You must also use this special type for jobs that are later activated with the job import API NOPUJIxN (see the section API Routines). Note: Recovery jobs are not activated during a normal job network activation. They are activated only if they are defined for another job and if a certain event makes a recovery necessary.
Execution Node	Node on which to submit the job. The default is the value specified in the job network definition (see the field Execution Node in the section Network Maintenance). You can enter a different node for the job here. The name of the operating system appears after the node number. You can define the execution node as a symbol. For details, see Symbols in Node Definitions in the section Symbol Table and Symbol Maintenance.
Symbol Table	Name of the symbol table to be referenced for substitution of variables in dynamic JCL. Enter an asterisk (*) and press ENTER to list available symbol tables for network owner. Select a name from the list. Alternatively, you can enter a new name and choose PF7 (Symb) to define a new symbol table. See Modifying a Symbol Table Master in the section Symbol Table and Symbol Maintenance for more information. Note: If no symbol table is defined on the job level, the symbol table on the network level (if defined) is activated during network activation or job activation (if defined).
Symbol Table Version	Version of the symbol table to be used. Reserved names (are replaced).
	current	Current version for the activation date or determination date.
	nv	Version of the using network.
	svn	Symbol table version of the using network.
Suffix Symbol	(Optional field) If several instances of the job are to be activated in parallel, this field must contain a symbol name which is in the defined symbol table. The symbol itself must contain the suffixes to be appended to active job names and output conditions. The sum of the lengths (prefix+suffix) must not exceed the maximum field lengths for job names or conditions. For example, if the job master name is PARA, and the symbol contains 001, 003, 012, then the active jobs PARA001, PARA003 and PARA012 are created. If the suffix symbol value is not defined in a network and the network has a calling network (if it is a subnetwork), then the search for the suffix symbol is performed upward up to the highest level. If Suffix Symbol does not contain any values, the job is activated as a temporary dummy job. For information about the definition of multiple symbol values, see Defining Multiple Symbol Values in the section Symbol Table and Symbol Maintenance. For information about the assignment of multiple symbol values to Suffix Symbol, see Symbol Replacement with Multiple Symbol Values.
Restartable	Only applies to BS2000. Job can be restarted automatically. Possible values: Y - Restart The job is to be restarted without any recovery after a system crash. N - No restart No automatic restart after a system crash. R - BS2000/RESTART The job is to be restarted when repeated. SYSOUT files are not renamed. Automatic SYSOUT rerouting can be delayed with the following line right after the /LOGON instruction: /REMARK EOR-SYSOUT-DIRECT=LATER Later, the following line must appear: /REMARK EOR-SYSOUT-DIRECT=NOW This allows user-defined actions before using a SYSOUT file. Additional Restart Criteria: Job submission time must be before the last IPL time and the job must not be terminated. The field MonJV must contain $R. The system session number at the job check time must be different from the session number at submission time.
Mod	User ID, date and time of the last modification of the job definition.
End-of-Job Action Errors set 'not ok' Conditions	Job output conditions. Possible values: N - No impact on the job result Errors during End-of-Job action processing have no impact on the job result. Y - Errors impact the job result Errors during End-of-Job action processing have an impact on the job result. For all output condition(s) defined for events at the job step level, the default checks All Checks ok and 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 defined for job not ok. If the job was already set to not ok, it remains not ok, regardless of the definition here. Notes: Setting this option can 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 settings are overridden by job settings. This option does not change the settings of any conditions defined for any individual events. empty field - Impact as defined for the network If the field is empty, the job uses the End-of-Job definition from its network. See also the field End-of-Job Action Errors set 'not ok' Conditions in the network master definition.
Milestones	Milestone job types. You can set single or multiple milestone attributes (types) for a job that performs an important task within a job network, such as tracking significant events or controlling the successful completion of other jobs. Possible values for user-defined milestones: B - Network Begin Milestone job performs as the first network job. E - Network End Milestone job performs as the last network job. I - Other Milestone job performs in no particular job order. Possible values for system milestones dynamically set by Entire Operations during job submission (applies to active jobs only): 1 - Network Begin Milestone job performs as the first network job. 2 - Network End Milestone job performs as the last network job. You can use the application programming interface NOPUMI1N (see the section API Routines) to define your own milestones. For further information on milestone jobs, see the section Event Store Milestones in the System Automation Tools documentation.
Escape Characters: Activation	This is the activation escape character. It is a prefix for Natural code lines and symbols to be replaced at activation time. If you change this character, dynamic JCL can become invalid. See also Symbol Escape Characters (Symbol Maintenance) and Notes about Escape Characters.
Escape Characters: Submit	This is the submission escape character. It is a prefix for symbols to be replaced at submission time. If you change this character, dynamic JCL can become invalid. Default is the dollar sign ($). See also Symbol Escape Characters (Symbol Maintenance) and Notes about Escape Characters.

Note about Escape Characters

The job escape character is always used for symbol replacements and macro JCL.

When a job is created or when an escape character is reset, the default value is taken in the following order from:

1. Network defaults (operating system specific) if defined for the current operating system;

2. Network definition if non-blank;

3. Global operating system specific defaults for z/OS and z/VSE, BS2000, UNIX and Windows (Administration documentation).

See also Symbol Escape Characters in the section Symbol Maintenance.

Special PF Keys: Job Definition (Master)

You can perform the following functions using these PF keys in the Job Definition (Master) window:

PF Key	Name	Function
PF4	Edit	Edit the JCL. You can edit the job's JCL directly from here. Make sure that you have defined JCL in advance. The JCL definition can be invoked with PF9 from this screen.
PF6	Spec	Define job execution features. Depending on whether you choose PF6 in the Specials for Job Type window or in the Specials, Execution window, you can define job execution features specific to the job type or operating system. The input fields available are described in Fields: Job Type Specific Execution Features and Fields: Operating System Specific Execution Features.
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	Net	Job type NET: See Defining a Subnetwork.
PF9	JCL	Define the JCL for a job.

Creating a Job Definition

When defining a new job, you can either enter all required attributes individually, or copy all attributes from an existing job master including all input conditions and End-of-Job activities defined for the job.

This section covers the following topics:

• Adding a Job Definition

• Copying Job Definitions

Adding a Job Definition

To add a job definition

1. On the Network Maintenance screen, type L in the line command field of the network for which you wish to add a job and press ENTER.

   Or:
   Use the direct command ADD JOB as described in Direct Commands documentation.

   The Job Maintenance screen appears.

2. Choose PF2 (Add).

   A Job Definition (Master) window similar to the example below opens:

   24.11.16 ***** Entire Operations ***** 11:38:03 Job Maintenance Owner EXAMPLE Network B60-FLOW Version ------------------------------------------------------------------------------ +------------------------------------------------------------------------+ | EOR1080 - Job Network Defaults inserted | | Job Definition (Master) | | | | Job Name ==> __________ Mod ==> SAG 24.11.16 11:38 | | Description ==> __________________________________________________ | 2 | Job Type ==> ___ | 1 | Execution Node ==> N0082 MVS/ESA | 1 | | 1 | Special Type ==> ________ Symbol Table ==> EXAM-ST1__ | | Milestones ==> ________ Symbol Table Version ==> __________ | 1 | Restartable ==> N | 2 | Suffix Symbol ==> ________________________________________ | 1 | Escape Characters: Activation ==> @ | 1 | Submit ==> $ | ** | End-of-Job Action Errors set 'not ok' Conditions ==> N | | | | Enter-PF1---PF2--PF3--PF4---PF5---PF6---PF7---PF8---PF9---------PF12- | | Help Add End Edit Save Spec Symb Net JCL Menu | +------------------------------------------------------------------------+ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add End Save Up Down Menu

3. Enter values for the fields described in Fields: Job Definition (Master).

   Note:
   Depending on your operating system, you may have to define additional parameters. Choose PF6 (Spec) to open a window with the additional parameters. For further information, see Displaying Job Dependencies and Connecting or Disconnecting Jobs.

Copying Job Definitions

You can copy a job within the current network or between networks.

Prerequisites for copying are:

• You must be allowed to perform the copy function; see the settings of the write permissions in the Network Maintenance Functions of your user profile (Administration documentation).

• You must be granted access to the networks of a specified target owner.

• The target network must exist; you cannot create a new network with the copy function.

To copy a job definition

1. On the Job Maintenance screen, type C in the line command field next to the job whose definition you want to copy and press ENTER.

   A Job Master Definition Copy window similar to the example below opens:

   +-------------------------------------------------------------+ | | | Job Master Definition Copy | | | | From To | | Owner ==> EXAMPLE Owner ==> EXAMPLE___ | | Network ==> B60-FLOW Network ==> B60-FLOW__ | | Version ==> Version ==> __________ | | Job ==> JOB-01 Job ==> __________ | | | | | | PF1 Help PF3 End | +-------------------------------------------------------------+

   The From section contains read-only fields with the name of the job selected for copying and the owner and network to which the job belongs.

   The To section contains modifiable target fields which are preset to the name of the owner, network and version (if applicable) of the selected job.

2. In the To section, enter the names required to specify the new job and its target environment. You can use an asterisk (*) as a wildcard to open a window and select a name from a list.

3. When you are finished, press ENTER to save the new job and close the window.

   The new job appears in the list of jobs on the Job Maintenance screen for the owner specified for the new job.

Writing and Viewing Online Documentation for a Job

You can add a short description of a job when defining a job in the Job Definition (Master) window. This short description appears in the list of jobs on the Job Maintenance screen.

If you wish to add more online documentation for a job, proceed as described in the following instruction.

To create, view or modify a long job description

1. On the Job Maintenance screen, type P in the line command input field next to the required job.

2. Press ENTER.

   The description is displayed on an editor screen similar to the example below:

   Edit Description Jb: ABC3A Nw: EORACCT------------------------------ Columns 001 072 ====> SCROLL===> CSR ***** ****************************** top of data ***************************** 00001 Job 'ABC3A' 00002 ----------- 00003 This job forces a defined event at end-of-job time and executes the 00004 program 'EORCONTI' which resides on the installation library 00005 'EORnnn.LOAD'. The necessary JCL which is named 'EORE*' is stored in 00006 the installation library 'EORnnn.SRCE'. ***** **************************** bottom of data ****************************

   The example above shows the screen with 6 lines of text.

   (If no documentation exists for the selected job, the editor screen appears without text.)

   Write new or replace existing text using editor commands which are briefly described in the online help. For detailed descriptions of all editor functions, see Software AG Editor in the Natural documentation.

3. Choose PF3 when you are finished.

   The text is saved and the editor window closes.

   On the Job Maintenance screen, the letter P in the P column next to the modified job indicates that a long description exists for this job.

Once online documentation is written, it can be read by any user who is authorized to access the network to which the job belongs. Use the line command P to display the current text.

You can also display or print online documentation by using the Reports facility described in the section Reporting. If long job descriptions exist, they are included in the Network Description (detailed) report as shown under item 5 of the Example of Network Description (detailed).

Deleting a Job Definition

To delete a job definition

1. On the Job Maintenance screen, type D in the line command input field next to the job you want to delete.

2. Press ENTER.

   A window prompts you to confirm the deletion by entering the job name.

3. Press ENTER to delete the job definition.

Displaying Job Dependencies and Connecting or Disconnecting Jobs

The Job Maintenance facility allows you to see which jobs must run before a specific job can start, and which jobs run after it.

You can trace job dependencies through whole networks and display cross-network job links.

You can connect or disconnect jobs from the same or different networks.

This section covers the following topics:

Displaying Job Dependencies for a Specific Job

To display job dependencies for a specific job

1. On the Job Maintenance screen, type A in the line command input field next to the required job.

2. Press ENTER. A Job Dependencies window opens:

   19-02-07 ***** Entire Operations ***** 11:38:10 Job Maintenance Owner NATSAG Network A-OGCDEMO Version +--------------------------------------------------------------------------+ | | | Predecessors Job Dependencies Successors | | --------------------------+ +--------------------------- | | M Network Job I I Output Condition | | Input Condition I I Network Job M | | _ A-OGCDEMO J-OGCDEMO I I=> OGC-DEMO1-OK | | OGC-DEMO-OK =>I I A-OGCDEMO J-OGCDEMO2 _ | | _ +---------------+=> OGC-DEMO-NOK | | => Ow NATSAG A-OGCDEMO J-OGCDEMO7 _ | | _ Nw A-OGCDEMO => | | => Job J-OGCDEMO1 _ | | _ +---------------+=> | | =>I I _ | | _ I I=> | | =>I I _ | | --------------------------+ +--------------------------- | | X Chain D Disconnect X Chain D Disconnect | | Enter----PF1---PF2------PF3-------PF5---------PF7---PF8--------------- | | Help Connect End Save Up Down | +--------------------------------------------------------------------------+ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add End Save Up Down Menu

   The selected job name and network name appear in the middle of the window with its dependencies displayed in the two smaller windows on either side of the selected job name:

   • The Predecessors window on the left of the selected job contains the job and network names of the jobs that must run before the selected job can run. Directly beneath these are the linking conditions.

   • The Successors window on the right of the selected job contains the job and network names of the jobs for which the selected job is a prerequisite. Directly above these are the linking conditions.

   You can scroll both lists by using PF7 (Up) and PF8 (Down).

Line Commands: Job Dependencies

In the M column of the Job Dependencies window, you can enter the following line commands to perform the described functions on any job displayed in the window:

Line Command	Description
D	Disconnect the job from a predecessor or successor job. See also Disconnecting Jobs.
X	Chain. Move the selected job into the center of the window and display its dependencies.

Special PF Keys: Job Dependencies

You can perform the following function from the Job Dependencies window using this PF key:

PF Key	Name	Function
PF2	Connect	Connect the job to a predecessor job. For the standard case, event Job OK. See Connecting Jobs from the Same or Different Networks.

Connecting Jobs from the Same or Different Networks

You can connect two jobs within the same or different networks without defining logical conditions for them by using the Entire Operations default condition.

This function is also useful to link jobs across networks. In this case, you should check the input condition reference of the successor job. Use a reference different from RUN.

To connect two jobs

• Choose PF2 (Connect) in the Job Dependencies window of the job you wish to connect.

  A Job Connection window opens in which you can define a job which must precede the selected job:

  10.02.10 ***** Entire Operations ***** 16:31:28 Owner SN Job Maintenance Network A-1 +--------------------------------------------------------------------------+ ! EOR1141 - No Dependencies found ! ! Predecessors Job Dependencies Successors ! ! --------------------------+ +--------------------------- ! ! M Network Job I I Output Condition ! ! Input Condition I I Network Job M ! ! _ I I=> ! ! =>I I _ ! ! _ +-------------------------------------------------------+ ! ! ! ! _ ! ! _ ! Job Connection ! ! ! ! ! _ ! ! _ ! from Owner: SN________ to Owner: SN ! ! ! ! Network: A-1_______ Network: A-1 ! _ ! ! _ ! Job: __________ Job: D1 ! ! ! ! Event: OK ! _ ! ! ---- ! ! ------- ! ! X Ch ! PF3 End ! ct ! ! Ente +-------------------------------------------------------+ ------- ! E ! Help Connect End Save Up Down ! +--------------------------------------------------------------------------+

  The identifiers of the selected job appear in the protected fields on the right in the window.

This section covers the following topics:

• Fields: Job Connection

Fields: Job Connection

The input fields in the Job Connection window have the following meaning:

Field	Description
from/ Owner	Enter owner of job to run as predecessor.
from/ Network	Enter network name of job to run as predecessor.
from/ Job	Enter name of job to run as predecessor.
Event	OK	Job ended ok The condition predecessor-job-OK is added as an input condition to the successor job for the event job ok.
	NO	Job ended not ok The condition predecessor-job-NOT-OK is added as an input condition to the successor job for the event job not ok. If an output condition already exists for a mentioned event, it is used for the linkage (instead of creating a new condition).

Disconnecting Jobs

To disconnect two jobs linked by conditions

1. In the Job Dependencies window, type D in the line command input field of the second job in the sequence.

2. Press ENTER.

   A confirmation window opens:

   23.10.08 ***** Entire Operations ***** 15:35:41 Owner SN Job Maintenance Network BIG-1 +--------------------------------------------------------------------------+- ! NOP1457 - Several Predecessor Jobs ! ! Predecessors Job Dependencies Successors ! ! --------------------------+ +--------------------------- ! ! M Network Job Output Condition ! ! Input Condition Network Job M ! ! _ BIG-1 JOB-012 => E60-J013-O ! ! E60-J0 +----------------------------------------------+JOB-014 d ! ! _ BIG-1 ! ! ! ! E60-JO ! Please confirm ! _ ! ! _ ! the Disconnection from JOB-014 ! ! ! ! by entering 'Y' ===> _ ! _ ! ! _ ! ! ! ! ! PF3 End ! _ ! ! _ +----------------------------------------------+ ! ! => _ !* ! --------------------------+ +--------------------------- ! ! X Chain D Disconnect X Chain D Disconnect ! ! Enter----PF1---PF2------PF3-------PF5---------PF7---PF8--------------- ! E ! Help Connect End Save Up Down !- +--------------------------------------------------------------------------+

3. Enter Y.

4. Press ENTER to perform the disconnection and close the window. You can disconnect any two jobs linked by conditions using this function. There is no need to delete any defined conditions.

   Note:
   No disconnection is performed if the use of the conditions is not unique, for example:

   

   Note:
   Remove the condition definitions manually if the link is not unique.

Disconnection from a Predecessor Job

When disconnecting from a predecessor job, the linking input condition definition of the job displayed in the center (of the Job Dependencies window) is deleted.

Disconnection from a Successor Job

When disconnecting from a successor job, the linking output condition definition of an event definition of the job displayed in the center (of the Job Dependencies window) is deleted.

Note:
The input condition definitions of the successor job remain unchanged. After the output condition definition is deleted, the successor job can wait for a condition which is never satisfied.

Restrictions:

• A linking condition is deleted, only if it links no more than two jobs.

• If the X line command (Chain) was invoked for jobs in different networks, a disconnection of this type is not possible.

Defining Job-Specific Log Information

Entire Operations allows you to define which information is to be logged in addition to the Entire Operations default system log.

This information is defined at the job level and can be job SYSOUT, JCL or selected operating system messages from the SYSOUT.

This section covers the following topics:

• Specifying Extended Log Information

• Fields: Extended Log

Specifying Extended Log Information

To specify extended log information

1. Type U in the line command input field of the selected job on the Job Maintenance screen and press ENTER.

   An Extended Log screen opens in which you can specify the information to be logged:

   16.01.14 ***** Entire Operations ***** 15:00:28 Extended Log Owner SN Network A-1 Version V00003 Job IEFBR14 ------------------------------------------------------------------------------ Log SYSOUT ==> Y (Y/N) Files ==> ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ Log JCL ==> Y (Y/N) Log System Messages M Code M Code M Code M Code _ IEF403I _______ _______ _______ _ IEF404I _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ S Message Contents Selection Command=> ____________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help End Save Menu

2. Specify the information to be logged.

   The input fields and options are explained in Extended Log.

3. Choose PF5 (Save) to save your entries.

4. Choose PF3 (End) to return to the Job Maintenance screen.

The logged information can be viewed after job termination using the Log Information facility described in the section Log Information.

Fields: Extended Log

The input fields of the Extended Log screen are described in the following table:

Field/Column	Description
Log SYSOUT	Specifies logging of job SYSOUT files after job termination. Possible values:
	Y	Logs SYSOUT.
	N	No SYSOUT files are logged.
	SYSOUT logging can also be defined as SYSOUT action. If the SYSOUT file or spool data set exceeds a given line limit, the log display is truncated: see SYSOUT Line Limit in Default Setting (4) in the Administration documentation.
Files	(z/OS only) Input valid only if Log SYSOUT is specified. Enter number(s) of SYSOUT file(s) to be logged. If left blank and Log SYSOUT is specified, all files are logged.
Log JCL	Specifies logging of JCL after job termination. This is useful for dynamically generated JCL or if JCL is frequently modified for different job runs. Possible values:
	Y	Logs JCL.
	N	No JCL is logged.
	See also JCL Log.
Log System Messages	Specifies operating system messages to be logged. Enter a message code in a field under the Code column. If you enter S (Message Contents Selection) in the field headed M preceding a specified code and press ENTER, the Message Contents Selection window (see below) opens in which you can define additional selection strings. The message is logged if no additional string is specified, or if at least one specified string is found in the message.

Message Contents Selection

+----------------------------------------------------------+ ! ! ! Message Contents Selection ! ! ! ! Network A-1 Version V00003 Job IEFBR14 ! ! ! ! Log Message IEF403I , if it contains one of the ! ! following strings: ! ! ________________________________________ ! ! ________________________________________ ! ! ________________________________________ ! ! ________________________________________ ! ! ________________________________________ ! ! ! ! PF1 Help PF3 End ! +----------------------------------------------------------+

System messages are logged if they are selected by their message code, and one of the following conditions is true:

• No message contents selection is specified. (No selection strings defined.)

• A message contents selection is specified, and at least one of the strings is found within the pre-selected message.

JCL Log

The JCL log is generated from the following sources:

BS2000	From the ENTER file. (The ENTER file is deleted after copying into the Entire Operations Log.)
z/OS	If Entire Operations runs on a mainframe: from the SYSOUT. If Entire Operations does not run on a mainframe: from the active JCL.
z/VSE	From the active JCL.
UNIX	From the effectively submitted shell script.
Windows	From the effectively submitted BAT file.