Using mainframe

To use the mainframe support, you must:

  1. Copy the template file z/OS_Template.xml from JS_TOP/10.2/examples to JS_TOP/work/templates.

  2. Define your template job in Flow Editor.

Define your job

Use the template job feature to define your mainframe job.

  1. Make sure you have copied the zOS_Template.xml file from JS_TOP/10.2/examples to JS_TOP/work/templates.

  2. Select the Insert Application button from the design palette.

    The Insert Application window displays.

  3. Select zOS Job from the list and click OK.

  4. Click anywhere on your flow page.

    A zOS job is added to your flow.

  5. Right-click your zOS job and select Open Definition.

    The Application Definition window displays:

On the General tab

Field

Description

z/OS® host name

The full host name where the mainframe job is submitted to.

Login User ID

The mainframe log in ID.

Password

The mainframe log in password.

Is JCL file located on z/OS host?

Location of the JCL file (either on the z/OS host or LSF® execution host).

JCL File

Full path to the JCL file to submit with the job.

Output file

Full path to the file to receive the mainframe job output. Note: Any existing output file will be overwritten without a warning.

Estimated run time (in minutes)

(Optional) The estimated run time of the job. This value informs the system when to begin checking the job status. Specifying this value reduces system overhead for long jobs.

Check interval (in minutes)

(Optional) How often the status of the job is checked by the system.

Time out (in minutes)

(Optional) The number of minutes before the job times out. If the job times out, the job exits with exit status 237. A time out period of 0 means no time out (the job runs until it finishes).

On the Execution Environment tab

Field

Description

Submit to queue/partition

(Required for Windows only) Specify a queue created by the Administrator to be able to kill the job if necessary. Contact your Administrator for the mainframe queue name.

Run on host

(Optional) Specify the LSF host name where the proxy job will run.

Run as user

(Optional) Specify an LSF user name.

File Transfer

(Optional) Specify file transfers between theProcess Manager Server and LSF execution hosts.

Format:

"local_file operator [remote_file]"

where:

  • local_file is the path and file name on the Process Manager server
  • operator : The operator(<, >, <>, ><, <<) specifies whether the file is copied to the remote host, or whether the file is copied back from the remote host. The operator must be surrounded by white space. The following are valid operators:
    • < Copies the remote file to the local file after the job completes. Overwrites the local file if it exists.
    • > Copies the local file to the remote file before the job starts. Overwrites the remote file if it exists.
    • <> Copies the local file to the remote file before the job starts. Overwrites the remote file if it exists. Then copies the remote file to the local file after the job completes. Overwrites the local file.
    • >< Copies the local file to the remote file before the job starts. Overwrites the remote file if it exists. Then copies the remote file to the local file after the job completes. Overwrites the local file.
    • << Appends the remote file to the local file after the job completes. The local file must exist.

    Example: copy the local file on the Process Manager server c.s to the LSF execution host and name the file a.s:

    /share/usr1/c.s > /home/usr1/a.s
  • remote_file is the path and file name on the LSF execution host

Log File

(Optional) Full path to the log file that contains the stdout of the LSF job. Includes FTP messages. Use for troubleshooting.

Status of jobs

The status of your mainframe jobs is displayed in Flow Manager just like any other job.

Killing a job (Windows)

To kill a job in a Windows environment, the Administrator must create a queue specifically for mainframe jobs. For jobs to be eligible to be killed, you must submit the mainframe job to that special queue. Contact your Administrator for more information.

Killing a job (UNIX)

You can kill a mainframe job regularly if you are on a UNIX platform.