Defining Job Types and Job Execution Features

Text File

Jobs of type DAT (data file generation) can be used to create text files in the same way as active JCL is generated.

Instead of a submission, the created text is just being written to a text (data) file.

Symbol replacement, symbol functions, text block inclusions can be used like in other JCL.

If the DAT output file is to be created on a mainframe node, no trigraph encoding is performed during JCL loading.

If the DAT output file is to be created on a UNIX or Windows node, trigraph encoding is performed during JCL loading, and trigraph decoding is performed during DAT file writing.

For more information, see Trigraph Encoding for JCL Submission on UNIX and Windows.

Dummy Job

You can use dummy jobs to set input conditions with a time range, to provide a time window for other jobs or as placeholders for future or seldom used jobs, etc.

You can define an estimated running time for a dummy job (see the field Estimated Elapsed Time). The dummy job is then executed for exactly this amount of time without burdening the system.

Execution node:

Even if a dummy job itself does not need it, it may be necessary to define an execution node with a Submit User ID. This is the case if any prerequisite check, End-of-Job check or End-of-Job action uses an Entire System Server node. The Monitor determines whether a node access is required, and performs Entire Systems Management logons only if they are necessary for any action.

See also Using a Dummy Job.

File Transfer Job

Standard Job

If the job is executed on a UNIX or Windows node, command line parameters can be passed by the symbol CMDLINE-job. See Reserved Symbols for Command Line Parameters in the section Symbol Table and Symbol Maintenance.

Natural Program

It has no JCL and is executed directly by the Entire Operations Monitor.

A subprogram, for example, is used to code user exit routines (see the relevant section) used by a job.

See also Editing Master JCL and Natural Sources.

Subnetwork

The concept of subnetworks is described in detail in the section Defining a Subnetwork.

Job within SAP System

See the SAP-specific network defaults described in Input Fields: Network Defaults (Operating System and Environment Defaults) and Job Execution Specials for Job Type SAP.

Windows Service

For further information, see:

• Job Execution Specials for Job Type SRV

• Passing Command Line Parameters

Stopping a Windows service: Create a copy of the main Windows Service job, and define the special type Stop Job described in Fields: Job Master Definition.

Started Task

For z/OS: only PDS is a valid JCL location for this job type.

Entire Operations can activate and process started tasks like any other job type. See also Passing Command Line Parameters.

Stopping a started task: Create a copy of the main Started Task job, and define the special type Stop Job described in Fields: Job Master Definition.

Windows PowerShell Script

This job type is for Windows PowerShell Scripts (with extension .ps1).

The Windows PowerShell (powershell.exe) is used as the command interpreter instead of the old Windows command interpreter. The script must conform to the PowerShell syntax.

Command line parameters can be passed by the symbol CMDLINE-job. See Reserved Symbols for Command Line Parameters in the section Symbol Table and Symbol Maintenance.

Possible selection options:

The resulting name must not have more than 10 characters. Otherwise, the name of the active job network is the same as the name of the job master network. Uniqueness is ensured by different run numbers.

Possible check box settings:

Symbol replacement is possible.

Additionally to symbols with activation escape characters, also symbols with submission escape characters are resolved. Both resolutions are performed at submission time.

Symbol replacement is possible.

Additionally to symbols with activation escape characters, also symbols with submission escape characters are resolved. Both resolutions are performed at submission time.

BS2000, LMS: The LMS member type. For possible selection options, see the description of the Type field in Fields: Operating System Specials for JCL.

z/VSE: Member type of the z/VSE library.

This is a read-only field and applies to active (submitted) jobs only.

The ciphering is to be performed with the jexa4S utility encryptpw.

Default: Submit User ID of the Entire Operations job.

Unqualified file and job variable names in this job definition are prefixed with this BS2000 user ID. File and job variable names are not prefixed with the user ID if the name contains the activation escape character in input conditions and End-of-Job actions.

See also BS2000: User ID Propagated to Variables and Files.

This ID has no meaning for other operating systems.

In the Monitor standard values/submit user type in the access control system, certain checks of the Submit User ID can be defined. See also the field Submit Security User Type in the section Monitor Defaults in the Administration documentation.

If this field is left blank, then the default user ID is inserted at job activation.

See also the default setting User ID Definition (Defaults for Other Settings, Administration documentation), and the sections Operating System User IDs and Default User ID Determination.

If you leave this field blank, the account number is taken automatically from the BS2000 JOIN entry (only if the Entire Operations Monitor is under TSOS or under the same user ID as the job).

Symbol replacement is performed in this field if the activation escape character is used.

Symbol replacement is performed in this field if the activation escape character is used.

The default value on the network level is used for new job definitions.

The default value on the network level is used for new job definitions.

If you select this check box, the internal temporary SYSOUT file can be accessed from other BS2000 user IDs.

See also the default setting User ID Definition described in Defaults for Other Settings in the Administration documentation.

This is the catalog ID under which internal SYSOUT files are created by Entire Operations. This field is meaningful only if you specify a SYSOUT User ID different from the Submit User ID.

If you leave this field blank, Entire Operations generates an internal unique name.

Only alphanumeric passwords are supported.

In z/OS, the Entire Operations Monitor starts jobs under this user ID. You can only define this user ID if you are logged on to the executing node with the same user ID.

Default: If this field is empty, the user ID from the last Submit User ID change is taken.

In the Monitor standard values/job start user type in the access control system, certain checks of the job start user ID can be defined. See also the field Submit Security User Type in the section Monitor Defaults in the Administration documentation.

See also the default setting User ID Definition (Defaults for Other Settings, Administration documentation), and the sections Operating System User IDs and Default User ID Determination.

The Entire Operations Monitor sets the user ID of the shell script to this value. The user ID is converted to lower case automatically.

In the Monitor standard values/job start user type in the access control system, certain checks of the job start user ID can be defined. See also the field Submit Security User Type in the section Monitor Defaults in the Administration documentation.

See also the default setting User ID Definition (Defaults for Other Settings, Administration documentation), and the sections Operating System User IDs and Default User ID Determination.

Windows: You can specify the user’s domain in this field.

Node to which internal SYSOUT files are to be copied by Entire Operations. The SYSOUT node must be different from the execution node, and it must be a BS2000 node.

You can define the SYSOUT node as a symbol if the Use Symbol as SYSOUT Node option is selected. For details, see Symbols in Node Definitions in the section Symbol Table and Symbol Maintenance.

Catalog ID under which internal SYSOUT files are copied by Entire Operations.

User ID under which internal SYSOUT files are copied by Entire Operations.

See also the default setting User ID Definition (Defaults for Other Settings, Administration documentation), and the sections Operating System User IDs and Default User ID Determination.