The Entire Operations Monitor will activate job networks automatically according to their defined schedules. However, it is also possible to activate a network manually from the Network Maintenance screen.
When a network is activated, all jobs within the network, except recovery jobs, are activated.
Note:
Only authorized users can activate job networks manually.
There are several situations in which you may wish to activate a job network manually (press ENTER to activate the network):
When no schedule has been defined for the network;
To start the same network several times (with different run numbers);
When the network is not scheduled for the current date;
To reactivate a network.
To activate a network manually
Type R
(Activate) in the line command
field of the selected network, and press ENTER.
A Network Activation window like the example below opens:
+--------------------------------------------------------+ | | | Network Activation | | | | Owner ==> EXAMPLE | | Network ==> B60-FLOW | | Version ==> __________ | | No current Network Version | | | | Last Schedule Extraction ==> 18.01.20 | | at ==> 00:00:11 | | Last Execution ==> 18.01.20 | | Last Run Number ==> 3233 | | | | Preferred Run Number ==> _____ | | Use Time from Schedule ==> N (Y/N) | | or activate on ==> 18.01.20__ | | at ==> 10:55:25 | | JCL Check only ==> N (Y/N) | | Enter----PF1---PF3------------------------------- | | Activate Help End | +--------------------------------------------------------+ |
Change the input fields as required. The fields are explained in Fields: Network Activation.
Press ENTER when you are finished.
If symbol prompting has been defined for the network, a Symbol Prompting for Table screen appears with a table of symbols used during dynamic JCL generation.
If required, change the symbols and symbol values. For further explanations, see Symbol Prompting during Network or Job Activation in the section Symbol Table and Symbol Maintenance.
Choose PF5 (Accpt) when you are finished.
If the activation is successful, the activated network gets a new run number as returned in a message.
This document covers the following topics:
The fields in the Network Activation window are described in the following table:
Field | Description | |
---|---|---|
Owner | Owner of the network to be activated. | |
Network | Network to be activated. | |
Version | Version of the network to
be activated.
If a current version exists for the current date, it will be preset as the default value. It is possible to activate any other existing version of the network. When using a wildcard, a Network Version Selection window will open. Below the version field, an explanative text for the version will be shown (if applicable). Example: 01-01-19 - >>>>>>>> - current on 19-06-08 |
|
Last Schedule Extraction | Date and time of the last
automatic schedule extraction for this network by the Entire Operations
Monitor.
See also Date and Time Formats. |
|
Last Execution | Date of the last
activation.
See also Date and Time Formats. |
|
Last Run Number | Run number of the last activation. | |
Preferred Run Number | If input is allowed for
this field, you can enter the run number you want to be used for the activated
network. Run numbers for further network activations increment from this
number.
If the requested run number is in use, Entire Operations assigns the next free number to the run. If this field contains a zero ( Field input is allowed or not allowed (default) in the network default settings: see the option Activation: Allow run number setting in the section Default Setting (4) in the Administration documentation. |
|
Use Time from Schedule | Enter Y (yes) here to activate the network within the
defined time frames
(Earliest Start, Latest Start,
Deadline), even if the current date is not a scheduled
date for this network. With this option, you can force the same time
dependencies as if the network were scheduled and activated
automatically.
|
|
or activate on/at | Shows the current date and
time. You can modify the date and time to force activation at any time on any
date. There is no limitation for future date and time settings.
See also Date and Time Formats. |
|
JCL Check only | If set
to Y (yes):
Only a JCL check is performed for all jobs of the job network. See JCL Check only for further reference. |
|
If set
to N (no):
Normal job submission is initiated. This is the default. |
For a JCL check, the required commands are automatically inserted:
OS | Command |
---|---|
z/OS, JES2 | TYPRUN=SCAN |
z/OS, JES3 | EXEC PGM=JCLTEST |
BS2000: | /MODIFY-SDF-OPTIONS MODE=TEST |
UNIX | Script execution with set -vn |
The following applies:
Windows: Jobs are executed as Dummy due to JCL
Check
.
Jobs of type NAT (Natural) are executed as Dummy due to
JCL Check
.
End-of-Job action user exits (exit type EJA
) will
be skipped.
Notes: