OSI/TS Management Programming Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

191

192

193

194

195

196

197

198

199

200

LISTOBJECTS SERVICE Command

Commands and Responses

5–122 056786 Tandem Computers Incorporated

ZCOM-TKN-CMD-TIMEOUT

is described in the Communications Management Programming Manual. This token is

optional; duplicate occurrences are not allowed.

ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKN-

COMMENT

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

These tokens are optional and, with the exception of ZSPI-TKN-COMMENT,

duplicate occurrences are not allowed.

ZSPI-TKN-CONTEXT

is used to get the next response message if multiple response messages are

returned, as described in the Distributed Systems Management (DSM) Programming

Manual.

Tokens in Response Buffer

ZSPI-TKN-DATALIST and the final ZSPI-TKN-ENDLIST

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

Programming Manual. 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, all object names are enclosed in a single data list, provided

they can fit into one response message. (The maximum number of data lists that

can be returned is two: one for the L3 service and one for the L4 service for the

process specified in either ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR.

Therefore, the object names will always fit into one response message, and no

more than one data list or response message will ever be returned.)

ZCOM-TKN-OBJTYPE

specifies the type of object named in all ZCOM-TKN-OBJNAME tokens that

follow it in the list. The token value is ZCOM-OBJ-SERVICE.

ZCOM-TKN-OBJNAME

is the name of a SERVICE object. One ZCOM-TKN-OBJNAME token is included

in the response for each SERVICE object that matches the ZCOM-TKN-OBJNAME

token given in the command. If none are defined, this token is absent from the

data list.

ZSPI-TKN-RETCODE

indicates whether or not the command was successful. If the command failed, this

token supplies the reason for the failure. Its use is described further in the

Distributed Systems Management (DSM) Programming Manual.