z/OS Job
z/OS jobs are used to execute a task on a z/OS system.
To create a z/OS job, see Creating a Job.
The following table describes the attributes for a z/OS job type.
Attribute |
Description |
---|---|
Job Type |
Defines the type of job that determines which fields are exposed in a job definition. The value of the job type is based on the platform for the job execution. Jobs defined as Dummy provide instructions for Control-M such as post-processing actions. Value: z/OS |
Job Name |
Defines the name of the job processing definition. Rules:
|
Description |
Defines a description of the job in free text. Rules:
|
Run as Dummy |
Enables you to execute jobs using a dummy job, and not as a Dummy job type. |
What |
Defines one or more attributes which determines what the job executes, as follows:
If you have Control-M JCL Verify version 9.0.22 or later installed and enabled in the mainframe, you can verify the JCL code when the Workspace is checked in. See Verifying JCL Code in a z/OS Job. |
Member Library |
Defines the location of the Member that contains the JCL, started task procedure, or warning message. Rules:
|
Member |
Defines the name of a member that contains one of the following in relation to the job to be executed:
You can browse and select the required member on the Agent defined in the Host/Host Group attribute. You must define the Member Library and Run as User attributes. Rules:
|
Embedded JCL |
Defines a script exactly as it would be specified in a terminal for the specific computer and is part of the job definition. Rule: 64000 B |
Control-M/Server |
Defines the name of the Control-M for z/OS that processes the job. |
Run as |
Defines the user name with the authorization to execute the job. This attribute is used by the Control-M security mechanism. Rules: 1–8 characters. |
Override Path |
Defines a temporarily-modified job script file without changing the original script file in the File Path/Member library and without changing the scheduling order of a folder. Rules:
|
Pre-Execution Sleep |
Determines the number of minutes or seconds to wait before a job executes. The job must meet all the prerequisite criteria and be eligible for execution before the wait time starts. Rules: 0–9999 Default: 0 If you export the Workspace, the attribute functions as the variable %%CTM_PRE_SUB_WAIT, with a value of up to four digits, followed by M (minutes) or S (seconds). If you define this attribute with a value of 655 seconds, the XML output appears as follows: %%CTM_PRE_SUB_WAIT=655S This attribute is supported in Control-M/Server version 9.0.21 or higher. |
Run as started task |
Specifies that the job is invoked with the operator START command. |
Application |
Defines a logical name for sorting groups of jobs. This attribute is used to supply a common descriptive name to a set of related job groups. The jobs do not necessarily have to execute at the same time. Rules:
|
Sub Application |
Defines the name of the Sub Application where the job belongs logically. It is a sub-category of the Application attributes, such as, Application = Finances, and Sub Application = Payroll. Rules:
|
Scheduling Environment |
Defines the JES2 workload management scheduling environment that is to be associated with the job. Rules:
|
System Affinity |
Defines the identity of the system in which the job must be initiated and executed (in JES2). Rules:
|
Request NJE Node |
Defines the node in the JES network where the job executes. Rules:
|
Prevent NCT2 |
Performs data set cleanup before the original job execution. |
Control-D Category |
Defines the name of the Control-D Report Decollating Mission Category. If specified, the report decollating mission is scheduled whenever the job is scheduled under Control-M. Rules:
|
Variables |
All variables are identified by the %% prefix. If %% is included in the value for a job processing attribute, Control-M assumes that it is referring to a variable or function. Rules:
|
Documentation |
Defines a description related to the job, and is saved in a defined location. The location where the document is saved depends on whether the type is File or URL. For a file, the description is located in a file located in a file path. For a URL, the Documentation is located in a URL address. z/OS: Documentation is saved in a Doc Member located in a Doc Library. |
Doc Library |
Defines the name of the library where the Documentation (description) is saved. Rules:
|
Doc Member |
Defines the name of the member where the job documentation (description) is saved. You can browse and select the required member on the Agent defined in the Host/Host Group attribute. You must first define the Doc Library and Run as User attributes. Rules:
IBM i (AS/400): Indicates the name of the member in the Doc Library or Doc Path file. This attribute is optional even if a value is supplied for Doc Library. If you specify a library and file name but no value for Doc Member, the *FILE default member name is used. |
Priority |
Determines the order of job processing. Use an * (asterisk) to mark the job as Critical. |
Emergency Job |
Determines whether the z/OS job is an Emergency Job. |
Verifying JCL Code in a z/OS Job
This procedure describes how to verify JCL code in a z/OS job definition, with the option of setting custom parameter values and filters for the JCL verification. This enables you to view and correct JCL code, such as missing field values or other errors, before running the job.
Before you begin
-
Ensure that you have created a Workspace to contain your z/OS job and that you have checked in this Workspace. To verify the JCL code, the Workspace must be checked in.
-
Ensure that you have Control-M JCL Verify version 9.0.22 or later installed and enabled in the mainframe. For more information, see the Control-M JCL Verify Documentation. To enable Control-M JCL Verify, contact your Control-M Administrator.
Begin
-
Select a z/OS job within a checked-in Workspace.
-
In the job definitions pane, click the General tab.
-
Do one of the following:
-
In the Type field, click
(Verify JCL).
-
In the JCL field of an embedded JCL, click
to display the full JCL code, and then click Verify JCL.
-
-
In the Verify JCL dialog box, set custom parameter values and filters for JCL verification. For descriptions of the available parameters, see Verify JCL Parameters.
Changes are saved for future JCL verifications by the same user.
-
Click Verify.
The Verify JCL Report appears in the bottom pane.
Verify JCL Parameters
The following tables describes the Verify JCL parameters. For more information about these parameters, see Control-M JCL Verify Defaults panel (JD screen) in the INCONTROL Documentation.
Parameter |
Description |
---|---|
Run Date |
Determines the Control-M order date of jobs to verify. Default: Current date |
Environment Name |
Determines the name of the Control-M JCL Verify environment to limit rule processing. |
Check Dataset |
Determines whether to verify dataset existence and creation options. Valid Values:
Default: Default |
Check Dataset Authorization |
Determines whether to verify dataset access privileges. Valid Values:
Default: Default |
Check Program Existence |
Determines whether to verify that the load modules exist. Valid Values:
Default: Default |
Check Site Standards Rules |
Determines whether to verify site standards. Valid Values:
Default: Default |
Check JES Syntax |
Determines whether to verify that JES2 or JES3 statements are correct. Valid Values:
Default: Default |
Resolve Control-M Auto-Edit Variable |
Determines whether to resolve Control-M AutoEdit variables in the job. Valid Values:
Default: Default |
Check Utility Validation |
Determines whether to verify the syntax of IBM utilities. Valid Values:
Default: Default |
PROCDD |
Defines the name of a predefined DD card for procedure resolution. |
LINKDD |
Defines the name of a predefined DD card for load modules search. |
User |
The ID of the user associated with security verification. |
Triggered Rule Information ID |
Determines whether to display the triggered rule information ID. Valid Values:
Default: Default |
Check CNDALC |
Determines whether to consider datasets that are created or deleted by conditional steps as conditional references. Valid Values:
Default: Default |
Message Summary Section Format |
Determines the display format for the message summary section. Valid Values:
Default: Default |
Messages Level |
Determines the minimum severity level of messages to issue. Valid Values:
Default: Default |
Messages ID |
Determines whether to include message IDs in messages and in the message summary. Valid Values:
Default: Default |
Node |
Defines the LPAR where verification is performed. |
System |
Defines the target SYSTEM name in the target SYSPLEX where verification is performed. |
IOA Environment |
Defines the QNAME of the IOA environment in the target SYSPLEX where verification is performed. |
Auto Routing |
Determines whether to enable automatic routing of the JCL Verification request to the most appropriate JCL Verify monitor based on the JCL's execution destination attributes. Valid Values:
Default: Default |