ESPCOM Command: Control Communications

Commands › ESPCOM Command: Control Communications

ESPCOM Command: Control Communications

To display and control communications activity between z/OS Agent and the scheduling manager, use the ESPCOM command.

Type: General command

Authority: To issue the ESPCOM command, you require OPER authority.

This command has the following format:

ESPCOM
|[[LIST|QUIESCE|RESTART|FLUSH] DEST(dest_name)]

ESPCOM: Lists the attributes of the COMMQ checkpoint data set in use when issued by itself.
LIST: Lists the attributes of the COMMQ checkpoint data set in use. LIST is the default. When the DEST keyword is included, the state of the specified scheduling managers is displayed.
QUIESCE: Quiesces the communication to the scheduling manager that the DEST keyword specifies. The scheduling manager continues processing.
RESTART: Restarts the communication with the scheduling manager that the DEST keyword specifies.
FLUSH: Purges all pending messages for the scheduling manager that the DEST keyword specifies.
DEST(dest_name): Specifies the scheduling manager names that you want to view or manipulate. Wildcards can be used when specifying dest_name.

Example: List COMMQ Attributes

This example shows how to list the COMMQ data set attributes.

OPER ESPCOM
CommQ data set name: CYBER.ZAG.ESPCOMQ
               size: 1474560 bytes
               used: 320 bytes
1 senders are defined, 0 of them quiesced

Example: List COMMQ Attributes Using Wildcard

This example shows how to list the COMMQ data set attributes of all the scheduling managers whose names begin with AIX.

ESPCOM DEST(AIX-)

Here is a sample response:

CommQ data set name: CAB2.TST.VXXX.ZAG.ESPCOMQ
               size: 1474560 bytes
               used: 42952 bytes
Destination name|status|     last operation     | sent |queued|address
AIXTCNP         |active|Conn err 16.24.27 03 APR|     0|     0|111.111.30.144:81
AIXV3NP         |active|Conn err 16.24.27 03 APR|     0|     0|111.111.25.12:806
47 senders are defined, 0 of them quiesced

Example: Quiesce Multiple Scheduling Managers

This example shows how to quiesce all scheduling managers whose names begin with AIX.

ESPCOM QUIESCE DEST(AIX-)

Here is a sample response:

ESP1519I Quiesce requested for two destinations

You can verify that the scheduling managers have been quiesced by issuing this command:

OPER ESPCOM DEST(AIX-)

Here is a sample response:

CommQ data set name: CAB2.TST.VXXX.ZAG.ESPCOMQ
               size: 1474560 bytes
               used: 42952 bytes
Destination name|status|     last operation     | sent |queued|address
AIXTCNP         |quiet |Conn err 16.24.27 03 APR|     0|     0|111.111.30.144:81
AIXV3NP         |quiet |Conn err 16.24.27 03 APR|     0|     0|111.111.25.12:806
47 senders are defined, 2 of them quiesced

Example: Restart Multiple Scheduling Managers

This example shows how to quiesce all scheduling managers whose names begin with AIX.

ESPCOM DEST(AIX-) RESTART

Here is a sample response:

ESP1520I Restart requested for two destinations

You can verify that the scheduling managers have been restarted by issuing the following command:

ESPCOM DEST(AIX-)

Here is a sample response:

CommQ data set name: CAB2.TST.VXXX.ZAG.ESPCOMQ
               size: 1474560 bytes
               used: 51528 bytes
Destination name|status|     last operation     | sent |queued|address
AIXTCNP         |active|Conn err 16.24.27 03 APR|     0|     0|111.111.30.144:81
AIXV3NP         |active|Conn err 16.24.27 03 APR|     0|     0|111.111.25.12:806
47 senders are defined, 0 of them quiesced

Example: Flush Scheduling Manager Messages

This example shows how to flush the message queues of all scheduling managers whose names begin with AIX.

ESPCOM FLUSH DEST(AIX)

Here is a sample response:

ESP1521I Queue, flush requested for 2 destinations.