Defining Job Types and Job Execution Features

#### Search Results

Search

# Defining Job Types and Job Execution Features

You define a job according to the job type you require and the operating system on which your Entire Operations environment runs.

The functions and specification options available to define a job depend on the following entries in the Job Definition (Master) window:

- The job type entered in the Job Type field,

- The job type entered in the Special Type field, and

- The operating system of the node entered in the Execution Node field.

Depending on the job type, the special type and the operating system of the execution node entered in the Job Definition (Master) window, a special window is provided to define individual execution criteria for the job.

This section describes the types of jobs you can define in Entire Operations and the type specific features provided to execute a job.

- Available Job Types

- Defining Job Type Specific Execution Features

- Defining Operating System Specific Execution Features

## Available Job Types

Note
Only the job types `JOB`, `SRV` and `STC` result in operating system jobs when submitted.

You can define the following job types to Entire Operations:

Job Type | Description
--- | ---
`DAT` Text File | A UNIX, Windows or `DAT` 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.
`DUM` Dummy Job | A dummy job has no JCL and is not submitted to the operating system. 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.
`FTP` File Transfer Job | This job type can be used for file transfers in batch mode using the File Transfer Protocol (FTP). The JCL for the file transfer job is generated by Entire Operations, depending on the FTP parameters in the JCL definition.
`JOB` Standard Job | This includes all standard operating system jobs with their own JCL. Jobs of the type `JOB` (Standard Job) are submitted as batch jobs. The JCL of `JOB`-type jobs can contain symbols as placeholders for variables defined in the symbol table specified for the job. These symbols are replaced by their current value at job activation or at job submission time. See also Symbol Replacement in JCL. 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.
`NAT` Natural Program | This is a Natural subprogram. 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.
`NET` Subnetwork | This job type enables you to execute a complete network within a main network. For detailed information on defining subnetworks, see the section Defining a Subnetwork.
`SRV` Windows Service | With this job type, you can define a service under Windows. A service must first be defined in Windows before it can be started. 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 `SRV` job, and define the special type `P` described in Fields: Job Definition.
`STC` Started Task | A started task is a special type of batch job on z/OS. Started tasks have static JCL which can reside in any PROCLIB. 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 `STC` job, and define the special type `P` described in Fields: Job Definition.
`WPS` Windows PowerShell Script | Applies to Windows only. 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.

## Defining Job Type Specific Execution Features

To define job type specific execution features

1. In the Job Type and Special Type fields of the Job Definition (Master) window, enter the required types. Press ENTER.

2. Choose PF6 (Spec).

   A Specials for Job Type window like the example of the job type `DAT` below opens:

       +------------------------------------------------------------------------+
       |                                                                        |
       |                          Job Master Definition                         |
       |                        Specials for Job Type DAT                       |
       |                                                                        |
       |             Owner ==> EXAMPLE             Job Type ==> DAT             |
       |           Network ==> B60-FLOW           Exec Node ==> N0146 MVS/ESA   |
       |               Job ==> JOB-06                                           |
       |                                                                        |
       |    Submit User ID ==> NOP_____                                         |
       |   Target Location ==> PDS         Target overwrite ==> N               |
       |       Target File ==>                                                  |
       |        ______________________________________________________          |
       |            Member ==> ________                                         |
       |       Member Type ==> ________                                         |
       |                                                                        |
       |                                                                        |
       | Enter-PF1---------PF3---------PF5---------PF6-------------------PF12-- |
       |       Help        End         Save        Spec                  Menu   |
       +------------------------------------------------------------------------+

   Or:
   For the job type `NET`, choose PF8 (Net).

   A Job: Subnetwork Definition window opens.

   All type specific fields are described in Fields: Job Type Specific Execution Features.

   If there are no type specific fields available, an appropriate message occurs indicating that this function is not available.

This section covers the following topics:

- Fields: Job Type Specific Execution Features

### Fields: Job Type Specific Execution Features

Job Type | Field | Description
--- | --- | ---
`NET` Subnetwork | JCL Node | Node where the JCL of the job (if defined) is located.
Subnetwork Owner | Owner of the subnetwork. Use a wildcard to select an owner.
Subnetwork Name | Name of the subnetwork. Use a wildcard to select a network.
Subnetwork Version | Version of the subnetwork if defined.
Subnetwork Run | Run number of the subnetwork (read-only field).
Subnet Activation Mode | Activation time: see Time of Activation of a Subnetwork in the System Overview. Possible values:
`A` (or blank) | At the moment of the activation of the calling job.
`S` | At the moment of the start of the calling job.
`D` | Use global default values as set in the Entire Operations Default Setting (2) (see the Administration documentation).
Append Mult. Suffix | Enter `Y` to append the suffix of the calling multiple job to the name of the subnetwork. 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.
Use Subnetwork Time Frames | Possible values:
`N` | Use the time frame from the calling job of the type `NET` (default).
`Y` | Use the time frame defined for the subnetwork itself.
Subnetwork Input Condition | Default input condition automatically set for a job of the type `NET`. See also Link to the Main Network.
Subnetwork Output Condition | Default output condition automatically set for a job of the type `NET`. See also Link to the Main Network.
`DAT` Text File | Submit User ID | The user ID to be used to write a `DAT` text output file.
Target Location | `AJC` | Generate active JCL only.
`BS2` | BS2000 text file.
`LMS` | BS2000 LMS file.
`NAT` | Natural source object.
`PDS` | z/OS partitioned data set.
`TXT` | UNIX or Windows text file.
Target overwrite | This option is available only for some target locations. Possible values:
`N` | Append the output to target file.
`Y` | Overwrite target file with the output.
Target File | Text file to which the `DAT` output is to be written. 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.
Member | The target locations `LMS`, `NAT` and `PDS` also require the definition of a target file member. 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.
Member Type | BS2000, LMS: The LMS member type. For possible input values, see the description of the Type field in Fields: Operating System Specials for JCL.
`SRV` Windows Service | Service Name | The internal name of a Windows service. Note You can obtain the internal name of a Windows service by using the following Windows command line command: `sc getkeyname <external-name>`.

## Defining Operating System Specific Execution Features

To define operating system specific execution features

1. In the Job Type field of the Job Definition (Master) window, enter the required job type and press `ENTER`.

2. Choose PF6 (Spec).

   If no job type specific features are available, the Specials, Execution window like the example below opens:

       +------------------------------------------------------------------------+
       |                                                                        |
       |                          Job Master Definition                         |
       |                        BS2000 Specials, Execution                      |
       |                                                                        |
       |             Owner ==> EXAMPLE           Job Type ==> JOB               |
       |           Network ==> B60-FLOW         Exec Node ==> N0121 BS2000      |
       |               Job ==> JOB-012                                          |
       |                                                                        |
       |   Default User ID ==> NOP_____   Submit Password ==>                   |
       |    Submit User ID ==> NOP_____           defined ==> no                |
       |    Account Number ==> ________    SYSOUT User ID ==> ________          |
       |  BS2000 Job Class ==> ________    SYSOUT Cat  ID ==> ____              |
       |      Job Priority ==> ___         Collect SYSLST ==> _                 |
       |      Run Priority ==> ___           Share SYSOUT ==> _                 |
       |                                                                        |
       |      MonJV ==> ______________________________________________________  |
       |   Password ==>                           defined ==> no                |
       |                                                                        |
       | Enter-PF1---------PF3---------PF5-------------------------------PF12-- |
       |       Help        End         Save                              Menu   |
       +------------------------------------------------------------------------+

   If job type specific features are available, the Specials for Job Type window opens first when you choose PF6 (Spec) from this window.

   The input fields provided depend on the operating system (here: `BS2000`) of the execution node specified for the job.

   All operating system specific fields are described in Fields: Operating System Specific Execution Features.

   In general, these fields correspond to the operating system specific fields provided for network maintenance.

   If no execution features can be specified for the operating system of the specified execution node, the following message occurs:

       Function not available for ...

   For the job type `DAT`, execution features are only available for the target location LMS on BS2000 only.

This section covers the following topics:

- Fields: Operating System Specific Execution Features

### Fields: Operating System Specific Execution Features

The operating system specific input fields provided for job execution are described in the following table.

Operating System | Field | Description
--- | --- | ---
BS2000 | Default User ID | Valid logon user ID defined for BS2000. 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. Note The user ID TSOS can be defined only if the user defining the ID is working under TSOS.
Submit User ID | Jobs in BS2000 are submitted under this user ID by the Entire Operations Monitor. This ID has no meaning for other operating systems. Note The user ID TSOS can be defined only if the user defining the ID is working under TSOS. 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. Symbol replacement is performed in this field if the activation escape character or the submission escape character is used. See also the default setting User ID Definition (Default Setting (1), Administration documentation), and the sections Operating System User IDs and Default User ID Determination.
Account Number | Account number to be used for the BS2000 Submit User ID. Symbol replacement is performed in this field if the activation escape character or the submission escape character is used. 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).
BS2000 Job Class | Valid job class for job submission defined for BS2000. Symbol replacement is performed in this field if the activation escape character is used.
Job Priority | If not empty, this job priority is used during submission and overrides a possible setting in the `LOGON` statement. The default value on the network level is used for new job definitions.
Run Priority | If not empty, this run priority is used during submission and overrides a possible setting in the `LOGON` statement. The default value on the network level is used for new job definitions.
Share SYSOUT | Make BS2000 SYSOUT file shareable. If you enter `Y` here, the internal temporary SYSOUT file can be accessed from other BS2000 user IDs.
Submit Password | Password for job submission. (Required only for BS2000 password encryption where submit node Entire System Server version is less than Version 3.4.1).
SYSOUT User ID | User ID under which internal SYSOUT files are created by Entire Operations. If you leave this field blank, the Submit User ID is used. Symbol replacement is performed in this field if the activation escape character or the submission escape character is used. See also the default setting User ID Definition described in Default Setting (1) in the Administration documentation.
SYSOUT Cat ID | Enter the SYSOUT catalog ID. 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.
Collect SYSLST | If you enter `Y` here, and if the job contains a SYSLST assignment (like `/SYSFILE SYSLST=...` or `/ASSIGN-SYSLIST TO-FILE=...`), the SYSLST output is appended to the SYSOUT collection by Entire Operations. The SYSLST output is then also available in the SYSOUT online display.
MonJV | Name of the BS2000 Monitor Job Variable to be used at job submission. If you leave this field blank, Entire Operations generates an internal unique name.
Password | Password for the defined BS2000 Monitor Job Variable. Only alphanumeric passwords are supported.
z/OS | Submit User ID | 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. Symbol replacement is performed in this field if the activation escape character or the submission escape character is used. 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 (Default Setting (1), Administration documentation), and the sections Operating System User IDs and Default User ID Determination.
UNIX and Windows | Submit User ID | The Entire Operations Monitor sets the user ID of the shell script to this value. The user ID is converted to lower case automatically. Symbol replacement is performed in this field if the activation escape character or the submission escape character is used. 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 (Default Setting (1), Administration documentation), and the sections Operating System User IDs and Default User ID Determination.
Submit Group | UNIX: If this field is empty, the user's default UNIX group (from `/etc/passwd`) is used. Otherwise, this field must contain one of the UNIX groups, which is visible in the output of the UNIX groups command. Windows: You can specify the user’s domain in this field. Symbol replacement is performed in this field if the activation escape character or the submission escape character is used.
SYSOUT Node | Only if SYSOUT is to be copied to BS2000: 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. For details, see Symbols in Node Definitions in the section Symbol Table and Symbol Maintenance. See also Defining the Handover of SYSOUT Files from UNIX/Windows to BS2000.
SYSOUT Cat ID | Only if SYSOUT is to be copied to BS2000: Catalog ID under which internal SYSOUT files are copied by Entire Operations. See also Defining the Handover of SYSOUT Files from UNIX/Windows to BS2000.
SYSOUT User ID | Only if the SYSOUT is to be copied to BS2000: User ID under which internal SYSOUT files are copied by Entire Operations. See also the default setting User ID Definition (Default Setting (1), Administration documentation), and the sections Operating System User IDs and Default User ID Determination.
Command Line obligatory | Possible values:
`Y` | The existence of the symbol `CMDLINE-job` is obligatory. If it is missing or empty, the job is not submitted. See Reserved Symbols for Command Line Parameters in the section Symbol Table and Symbol Maintenance.
`N` | A command line is not obligatory for the job (default).

> BS2000: User ID Propagated to Variables and Files

>   The BS2000 user ID specified in the Default User ID field of a job master or job active definition is propagated to all job variables and file names linked to an EOJ checking and/or input condition defined for the respective job.

>   Examples:

>   Old Default User ID | New Default User ID | New User ID in Job Variable/File Name
>   --- | --- | ---
>   No user ID (blank field) | `ID-A` | `ID-A` (provided the old user ID is also blank)
>   `ID-A` | `ID-B` | `ID-B` (provided the old user ID is also `ID-A`)
>   `ID-B` | No user ID (blank field) | No value changes, the old user ID is retained.

>   Restriction:

>   The ID is not propagated if the job variable or file name contains the job activation escape character.

### On this page

- Available Job Types
- Defining Job Type Specific Execution Features
- Defining Operating System Specific Execution Features