cassi

Starts a service execution process. You should use this command only when you want to debug a service, using the /a option.

Syntax

cassi [/res-name]
      [/a]

      [/atterminal-id]     (CICS specific)
      [/axtransaction-id]  (CICS specific)

      [/bjob-class-list]   (JCL specific)
      [/poutput-class-list](JCL specific)
      [/qprinter-name]     (JCL specific)
      [/zprinter-exit]     (JCL specific)

      [/v]                 (IMS specific)
                      [/wmpr-name]         (IMS specific)

Parameters

General

/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

CICS specific

/at`terminal-id`	Debug any application that runs in response to a request from the terminal identified by `terminal-id`
/ax`transaction-id`	Debug any application that runs in response to a non-facility transaction identified by `transaction-id`

JCL specific

/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`

IMS specific

[/v]	Specify IMS transaction classes when debugging (using the `/a` parameter) In order to debug an IMS transaction running in a specific IMS region, from a telnet shell, after you have unset DISPLAY and used the appropriate umask, start the command: cassi –a –v <trans-classes> -r REGION where `<trans-classes>` contains the IMS classes that you want to debug for.
[/w`mpr-name`]	Name of the IMS MPR to be used.

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:

If the execution of this command takes the number of service execution processes over the configured number, Enterprise Server will terminate one of the service execution processes.

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