cassub

Runs a JCL batch job.

Syntax:

cassub {[/rserver-name]|[/saddress]|[/lserver-name]}
       {[/jjobfile-name-by-content]|[/jrestart]|[/xjobfile-name-by-reference]}
       [/uuser-ID]
       [/ppassword]
       [/cgroup]
       [/z[userid]]
       [/v{1|2|3}]
       [/i{correlator}]

Parameters:

Options /r, /s, /l are alternative ways of identifying the enterprise server that you want to connect to.

/rserver-name

Name of the enterprise server region to run the job. Defaults to ESDEMO.

Note: When calling this utility from JCL or from a Web service, that is, when you are running the utility within a SEP, you cannot use the /r option to connect to the server. Where this is the case, you must use the /s or /l options to connect to the server.

The JCL command cassub is now designated as a system program and as such will not be cancelled by runtime container de-initialization.

/saddress

Submits the job to a remote server. The address is the address of the listener associated with the server's MF JES service. The format is protocol:ip-address:port.

Where:

protocol is tcp or tcpssl if you are using an SSL-enabled listener.
ip-address is either the host name or IP address of the enterprise server listener.
port is the port number value.

/lserver-name

This is an alternative to using the /r and /s options. This is the name of the enterprise server region to run the job. You must specify a name - there is no default. This option searches all the repositories specified in mf-client.dat, or whichever configuration file you have identified with the MFC_CONFIG environment variable, for an enterprise server region with the specified name. Repositories are specified in the [directories] section, in the format:

mrpi://host[:port]

or:

file:///path-to-repository

/jjobfile-name-by-content

Path and filename of the file containing the JCL to run. See Comments below for more infromation.

/jrestart

Used to restart jobs using the advanced restart functionality. See Advanced Restart Functionality for more infromation.

/xjobfile-name-by-reference

Path and filename of the file containing the JCL to run. See Comments below for more information.

/u user-id

Authorization user ID. See Security below for more infromation.

/p password

Authorization password. See Security below for more infromation.

/cgroup

Authorization group (optional). See Security below for more infromation.

/z[userid]

The parameter enables you to pass user credentials through an interactive prompt or as a redirection from the console, the userid is optional. This can be used to pass credentials stored in the Vault Facility.

Note: Micro Focus recommends that you use this option in preference to /u and /p.

/v{1|2|3}

The version of the job control system software to use:

1: VSE/Power
2: JES2
3: JES3

The default value is 2 (JES2).

/i{correlator}

This parameter enables you to supply a correlator, up to 32-bytes long, comprised of ASCII printable characters. The JCL engine will ensure this correlator has not previously been supplied for a JCL JOB, if a duplicate correlator is detected then the job submission will be rejected and the previous JOB ID will be returned.

Dependencies

To use this command:

If you specify the /r parameter, you must have started the enterprise server region named with the /r parameter first, or the ESDEMO on the local machine if you do not specify either /r or /s, using the casstart command. If you specify the /s parameter, you must have started the enterprise server region identified by the /s parameter, using ES Admin.
You must be running under the same user ID as the enterprise server region named with the /r parameter. If the Directory Server was started as a system service, and the enterprise server region was started using the Administration interface, then the enterprise server region is probably running under the LOCAL_SYSTEM user ID, and this command will not work. For more information see the section Starting and Stopping the Directory Server in the chapter Introduction to Enterprise Server Administration in your Enterprise Server Configuration and Administration Guide.
In order to successfully run the cassub command, you must have execute permissions on the cassub resource within the OPERCMDS resource class

Comments

You can use a dash (-) before a parameter as an alternative to a forward slash (/).

You must specify either the /j parameter or the /x parameter.

/r and /s are mutually exclusive. If you do not supply either, it is assumed that you are submitting to the server ESDEMO on the local machine.

For /x (by reference) the submitted file must be on the same platform as the enterprise server. This technique is more efficient, since only the name of the file is passed by the communications link. This is used internally (internal reader). You would use this technique where you run a job scheduling system on the same platform as the target enterprise server.

For /j (by content) the submitted file must be on the client's platform (which could be the same platform as the target enterprise server). The submitted JCL is physically passed over the communications link. This would be appropriate for an interactive user that has created the job stream on their machine and wants to submit it to an enterprise server running on another platform.

You can specify the /j or /x parameter more than once, in order to submit several JCL files in the same command.

The job is run by the most recently started available initiator that can handle the class specified on the JOB card.

Many of the command-line utilities, including casstart, casstop, casfile, casout, and cassub, can be invoked by program using the call interface and passing the command line parameters to the call. For an example, please see casstart.

Security

If you are running this command against a secure region, then you will need to specify the /u and /p parameters, and optionally the /c parameter. If you omit these parameters, your job may fail with an authentication error.