cassi (JCL version)

Starts a batch initiator or batch printer service execution process. Use this version of the command if you have MSS JCL Support installed. You should use this command to debug a JCL job.

Syntax:

cassi [/res-name]
      [/a]
      [/bjob-class-list]
      [/poutput-class-list]
      [/qprinter-name]
      [/zprinter-exit]

Parameters:

/r`es-name`	Name of the enterprise server for which to start a service execution process. Defaults to ESDEMO
/a	Debug any application that runs in this service execution process
/b`job-class-list`	Start a batch inititiator SEP to handle the job classes named in `job-class-list`
[/p`output-class-list`]	Start a batch printer SEP to handle the output classes named in `output-class-list`
[/q`printer-name`]	Send output to `printer-name`, which must be the name of a printer defined on your machine.
[/z`printer-exit`]	Direct output through the program `printer-exit`

Dependencies:

To use this command:

You must have started the enterprise server named with the /r flag first.
You must be running under the same user ID as the enterprise server named with the /r flag. If the Directory Server was started as a system service, and the enterprise server was started using the Administration interface, then the enterprise server 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.

Comments:

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

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.