Mainframe Modernization Jobs
The following topics describe job attributes that work with mainframe modernization platforms and services:
AWS Mainframe Modernization JobLink copied to clipboard
AWS Mainframe Modernization enables you to migrate, manage, and run mainframe applications in the AWS cloud.
To create an AWS Mainframe Modernization job, see Creating a Job. For more information about this plug-in, see Control-M for AWS Mainframe Modernization.
The following table describes the AWS Mainframe Modernization job type attributes.
Attribute |
Action |
Description |
---|---|---|
Connection Profile |
All Actions |
Determines the authorization credentials that are used to connect Control-M to AWS Mainframe Modernization, as described in AWS Mainframe Modernization Connection Profile Parameters. Rules:
|
Application Name |
All Actions |
Defines the name of the predefined application, on the AWS Mainframe Modernization service, that executes. |
Action |
All Actions |
Determines one of the following actions to perform:
|
JCL Name |
Start Batch Job |
Defines the JCL job stream filename to execute. A job stream is a sequence of JCL statements and data that form a single unit of work for an operating system. |
Secret ARN |
|
Defines the Amazon Resource Name that is a unique identifier for a secret stored in the AWS Secrets Manager. |
Retrieve CloudWatch Logs |
|
Determines whether to append the CloudWatch JCL job stream log to the output Only the Micro Focus engine is supported. |
Rerun Execution ID |
Restart Batch Job |
Defines a unique identifier to re-run a specific job or batch process within the AWS environment. |
From Step |
Restart Batch Job |
Defines the step in a job workflow where execution resumes or restarts. This is particularly useful in environments, such as mainframe job processing (for example, JCL or AWS Mainframe Modernization), where batch jobs consist of multiple sequential steps. |
From Proc Step |
Restart Batch Job |
Defines the step within a procedure (PROC) where the job execution restarts. This is particularly relevant in environments, such as IBM mainframes, that use JCL (Job Control Language), where a PROC is a reusable set of JCL statements defining part of a job. |
To Step |
Restart Batch Job |
Defines the step in a job sequence where the execution stops. This is particularly useful to control partial job execution or debug workflows in environments, such as mainframes or batch processing systems. |
To Proc Step |
Restart Batch Job |
Defines the step within a procedure (PROC) where the job execution stops. This is typically used in mainframe environments (for example, with JCL) to control the scope of execution for a subset of steps defined in a PROC. |
Delay Logs Retrieval |
Restart Batch Job |
Determines the number of seconds for the delay function to fully retrieve logs generated in CloudWatch. Default: 60 seconds |
Application Action |
Application Management |
Determines one of the following actions to perform on the defined application:
|
Latest Application Version |
Update |
Defines the current application version on the AWS Mainframe Modernization service. |
Definition S3 Location |
Update |
Defines the pathname of the Amazon S3 bucket that holds the application definition. s3://Mainframe/definition.json |
Client Token |
Deploy |
Defines a unique ID (idempotency token) that guarantees that the job runs only once. Tokens expire one hour after the job runs. Default: Token_Mainframe_%%ORDERID |
Application Version |
Deploy |
Determines which application version to use for succeeding jobs. |
Environment ID |
Deploy |
Defines the environment ID where the application is executed. |
Status Polling Frequency |
All Actions |
Determines the number of seconds to wait before checking the job status. Default: 60 |
Failure Tolerance |
All Actions |
Determines the number of times to check the job status before the job ends Not OK. Default: 3 |
Micro Focus JobLink copied to clipboard
Micro Focus enables you to run Job Control Language (JCL) files on mainframe environments on UNIX or Windows.
To create a Micro Focus job, see Creating a Job. For more information about this plug-in, see Control-M for Micro Focus.
The following table describes the Micro Focus job type attributes.
Attribute |
Description |
---|---|
Connection Profile |
Determines the authorization credentials that are used to connect Control-M to Micro Focus on UNIX or on Windows, as described in Micro Focus Connection Profile Parameters. Rules:
|
JCL Filename |
Defines the JCL job stream filename to execute. A job stream is a sequence of JCL statements and data that form a single unit of work for an operating system. |
PDS |
Defines the Partitioned Data Set (PDS) and its members for Mainframe Subsystem Support (MSS). A PDS is a computer file that contains multiple data sets, which are called members. MSS is a program that enables JCL applications to be migrated from a mainframe and maintained, developed, and run on Windows or UNIX platforms. |
Enable JCL Variables |
Determines whether to enable JCL variables. This option must be checked if the JCL job stream needs JCL variables, or if it needs additional variables that are defined by Additional Variables. |
Additional Variables |
Defines the environment variables that the Micro Focus Batch Scheduler Integration JCL (MFBSIJCL) needs to submit the JCL job stream. To submit the Control-M variable ODATE to the JCL job stream, you define the variable in the following format: export PDS=XXX&&export MYVAR=YYY |
Restart on Rerun |
Determines whether to re-execute a JCL job stream from (and to) a specific step that you define in the following attributes. A JCL job stream contains one or more programs. Each program execution is called a job step, or step. You can initiate a rerun from the Monitoring domain as long as a job stream has not been hard-killed. |
From Step/Proc |
Determines which step the JCL job stream re-execution starts from, which enables you to define the range of steps in the JCL job stream that is re-executed. To re-execute the JCL job stream from STEP2:PSTEP(1), write the following script: |
To Step/Proc |
Defines which step the JCL job stream re-execution ends on, which enables you to define the range of steps in the JCL job stream that is re-executed. To restart to STEP4(1):PSTEP(2), write the following script: #tSTEP4(1):PSTEP(2) |
Recapture ABEND Codes |
Determines how to handle abnormal end (ABEND) codes, which call attention to a software or hardware error, from a previous JCL job stream run, as follows:
|
Recapture COND Codes |
Determines how to handle condition (COND) codes from a previous JCL job stream run, as follows.
|
Auto Adjust Restart |
Determines whether to automatically adjust the specified From Step/Proc step if an earlier step is bypassed and must be run to successfully re-execute a later step in the JCL job streams, as follows:
|
Step-Specific Condition Codes |
Defines changes to step condition codes and their values in the JCL job stream re-execution. #cSTEP20(3):PSTEP10(2):1 |
Set MF_UCC11 |
Determines how to enable the UCC11 environment variable, which affects JCL job stream restart functionality, as follows:
|
Advanced Restart Parameters |
Defines the advanced restart parameters to add to the re-executed JCL job stream. To add a restart parameter that resets any step that ended abnormally in a previous run to RC=0, and that maintains the same condition code from the previous run, write the following script: |
Rerun Job ID |
Defines the Job ID for the JCL job stream to re-execute. You can find the Job ID in the Submit Job step where the JCL job stream was first executed in one of the following Micro Focus platforms:
|
Restart with Modified JCL |
Determines whether to re-execute the JCL job stream with the modified JCL job stream file, as follows:
|
Modified JCL Path and Filename |
Defines the full path and filename of the modified JCL job stream file. |