Mainframe Modernization Connection Profiles
The following topics describe connection profiles for mainframe modernization platforms and services:
ConnectionProfile:AWS Mainframe Modernization
AWS Mainframe Modernization enables you to migrate, manage, and run mainframe applications in the AWS cloud.
For more information about this plug-in, see Control-M for AWS Mainframe Modernization.
The following examples show how to define an AWS Mainframe Modernization.
-
This JSON authenticates with an AWS access key and secret:
Copy"AWS_MAINFRAME":
{
"Type": "ConnectionProfile: AWS Mainframe Modernization",
"Mainframe Modernization URL": "https://m2.us-east-1.amazonaws.com",
"AWS Logs URL": "https://logs.us-east-1.amazonaws.com",
"AWS Region": "us-east-1",
"Authentication": "Secret",
"AWS Secret": "*****",
"AWS Access key": "BDIARY7B2LKRUXPTXDO6",
"HTTP Codes": "429",
"Attempt Reruns": "3",
"Rerun Interval": "10",
"Connection Timeout": "30",
"Description": "",
"Centralized": true
} -
This JSON authenticates with an AWS IAM role from inside an EC2 instance:
Copy"AWS_MAINFRAME_IAM":
{
"Type": "ConnectionProfile:AWS Mainframe Modernization",
"Mainframe Modernization URL": "https://m2.us-east-1.amazonaws.com",
"AWS Logs URL": "https://logs.us-east-1.amazonaws.com",
"AWS Region": "us-east-1",
"Authentication": "NoSecret",
"IAM Role": "myMainframeRole",
"HTTP Codes": "429 404",
"Attempt Reruns": "3",
"Rerun Interval": "10",
"Connection Timeout": "30",
"Description": "",
"Centralized": true
}
The following table describes the AWS Mainframe Modernization connection profile parameters.
Parameter |
Description |
---|---|
Mainframe Modernization URL |
Defines the AWS Mainframe Modernization API authentication endpoint, based on the following format: https://m2.<AWSRegion>.amazonaws.com For more information about regional endpoints available for the AWS Mainframe Modernization service, refer to the AWS documentation. |
AWS Logs URL |
Defines the AWS Logs URL: https://logs.{{AWSRegion}}.amazonaws.com |
AWS Region |
Determines the AWS region where the job is located. us-east-2 |
Authentication |
Determines one of the following authentication methods:
|
AWS Access Key |
Defines the access key assigned to the account with the relevant permissions to the AWS service. |
AWS Secret |
Defines the secret access key assigned to the account with the relevant permissions to the AWS service. You can use Secrets in Code to hide this value in the code. |
IAM Role |
Defines the Identity and Access Management (IAM) role name for the AWS service connection. |
HTTP Codes |
Defines the HTTP code that appears in the response if you want to rerun a job execution step (authentication, trigger or completion). Multiple HTTP codes must be separated with a space. You cannot rerun a step with HTTP codes when you perform manual execution, such as rerun from point of failure. Default: 429 |
Rerun Interval |
Defines the number of seconds to wait to rerun a job step. Default: 10 |
Attempt Reruns |
Defines the number of attempts to rerun a job step. Default: 3 |
Connection Timeout |
Determines the number of seconds to wait after Control-M initiates a connection request before a timeout occurs. Default: 30 |
Centralized |
Determines whether to create a centralized connection profile, which is stored in the Control-M/EM database and is available to all Agents. You must set this parameter to true. Valid Values:
Default: false |
ConnectionProfile:Micro Focus
Micro Focus enables you to run Job Control Language (JCL) files on mainframe environments, as follows.
For more information about this plug-in, see Control-M for Micro Focus.
The following examples show how to define a connection profile for a Micro Focus job, for mainframe modernization.
-
This JSON defines a Micro Focus connection profile on Windows:
Copy"MICROFWINDOWS":
{
"Type": "ConnectionProfile:Micro Focus Windows",
"MFBSI Directory Path": "C:\\MicroFocus\\ES\\mfbsi\\ESBMC",
"MFBSI Config Path": "C:\\Workspace\\system\\config\\MFBSI.cfg",
"Runtime Environment": "\"C:\\Program Files (x86)\\Micro Focus\\Enterprise Developer\\createenv.bat\"",
"Additional Micro Focus Settings Script": "C:\\MicroFocus\\ES\mfbsi\\ESBMC\\settings\\options.bat",
"Run As": "microuser",
"Password": "*****",
"Description": "Centralized Connection Profile for Micro Focus Windows",
"Centralized": true
} -
This JSON defines a Micro Focus connection profile on UNIX:
Copy"MICROFLINUX":
{
"Type": "ConnectionProfile:Micro Focus Linux",
"MFBSI Directory Path": "/home/esuser/ES/mfbsi/ESBMC1",
"MFBSI Config Path": "/home/user/config/mfbsi.cfg",
"Runtime Environment": ". /opt/microfocus/EnterpriseDeveloper/bin/cobsetenv",
"Additional Micro Focus Settings Script": "/home/esuser/bmc/configuration/mfexports.sh",
"Run As": "microuser",
"Password": "*****",
"Description": "Centralised Connection Profile for Micro Focus Linux",
"Centralized": true
}
The following table describes the Micro Focus connection profile parameters.
Parameter |
Description |
---|---|
MFBSI Directory Path |
Defines the directory path of the Micro Focus Batch Scheduler Integration (MFBSI) configuration file. The temporary files JOBnnnnn.Sem and JobId.Log are stored here. This folder must be accessible for the Micro Focus Batch Scheduler Integration JCL (MFBSIJCL) file to run. |
MFBSI Config Path |
Defines the file path of the MFBSI configuration file. |
Runtime Environment |
Defines the path of the runtime environment, as follows:
|
Additional Micro Focus Settings Script |
(Optional) Defines the path to a script file that contains additional variables for the job. Defines the variables in the script file in the following format:
|
Run As |
(Optional) Defines the user that runs the job. |
Password |
(Optional) Defines the password of the user that runs the job. You can use Secrets in Code to hide this value in the code. |
Centralized |
Determines whether to create a centralized connection profile, which is stored in the Control-M/EM database and is available to all Agents. You must set this parameter to true. Valid Values:
Default: false |