OSI/AS Management Programming Manual

LISTOPENS SU Command

Commands and Responses

5–184 056785 Tandem Computers Incorporated

Tokens in Response Buffer (continued)

ZSPI-TKN-RETCODE token-type ZSPI-TYP-ENUM.

ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST.

. . .

ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.

ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING.

Tokens in Command Buffer

ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR

is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system

(ZCOM-TKN-XMGR) process name of the TAPS process to which SCP is to send

this command. This token is optional and must occur only once in the command.

ZCOM-TKN-OBJNAME

is the name of the TAPS subdevice whose opens are to be listed. This token is

required, can occur multiple times, and can be an object-name template (wild card

name).

ZCOM-TKN-CMD-TIMEOUT

is described in the Communications Management Programming Manual.

ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT,

and ZSPI-TKN-CONTEXT

are described in the Distributed Systems Management (DSM) Programming Manual.

Tokens in Response Buffer

ZSPI-TKN-DATALIST

introduces a data list, as described in the Distributed Systems Management (DSM)

Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list. These

tokens enclose the other response tokens only if the value of the header token

ZSPI-TKN-MAXRESP is nonzero. If ZSPI-TKN-MAXRESP is nonzero, the

information about all opens of a subdevice is enclosed in a single data list,

provided it can fit into one response message. Multiple data lists can appear in the

response, each containing information about a different subdevice. In addition,

multiple response messages can be returned.

ZCOM-TKN-OBJTYPE and ZCOM-TKN-OBJNAME

are described in the Communications Management Programming Manual. These

tokens identify the particular subdevice whose opens are described in this data

list.