Previous Topic: Problems with WTO and WTOR Messages in Subsystem InterfaceNext Topic: Problems Related to DOM Events in Subsystem


Problems Related to Commands in Subsystem

Symptom:

I am finding problems related to commands in the subsystem interface.

Solution:

When you find problems related to commands in the subsystem interface, CA Customer Support may ask you to invoke a special REXX function called OPS0ATRC. This function returns a string containing a z/OS control block useful for debugging purposes.

Important! Use this function only when CA Customer Support asks you to do so, because it is not intended as a programming interface and we may change it at any time.

One way to use the OPS0ATRC function is to trap a particular command through a rule and copy the returned control block strings into global variables. You can then use the X line command (for hexadecimal browse) of OPSVIEW option 4.8 to examine the returned data.

A sample rule, called DEBUGCMD, demonstrates how to use the OPS0ATRC function. The DEBUGCMD rule is in the OPS.CCLXRULS data set.

Use the following format to call the OPS0ATRC function:

CB = OPS0ATRC("functioncode")

The functioncode argument can be any of the following values:

SSOB

Returns the SSOB related to the current subsystem interface call. Mapped by macro IEFJSSOB.

SSCM

Returns the command SSOB extension related to the current subsystem interface call. Mapped by macro IEFSSCM.

MGCR

Returns the first part of the MGCR parameter list (control portion and command buffer) related to the current subsystem interface call. Mapped by macro IEZMGCR.