cassub

Runs a JCL batch job.

Syntax:

cassub [/res-name] or [/saddress] or [/les-name]
       [/jjobfile-name-by-content]
       [/xjobfile-name-by-reference]
       [/u]
       [/p]
       [/vversion]

Parameters:

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

/res-name

Name of the enterprise server 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.

/saddress

Submit the job to a remote server. 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
ip-address is either the text host name or IP address of the server listener
port is the port value

/les-name

Alternative to using the /r and /s options. Name of the enterprise server 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 a server with the given 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.

/xjobfile-name-by-reference

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

/u and /p

Reserved for future use.

/vversion

The version of the job control system software to use:

VSE/Power
JES2 (default)
JES3

Dependencies

To use this command:

If you specify the /r parameter, you must have started the enterprise server 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 identified by the /s parameter, using ES Admin.
You must be running under the same user ID as the enterprise server named with the /r parameter.
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.