Inspect Manual

High-Level Inspect Commands

Inspect Manual—429164-006

6-54

Examples that Display SPI Buffers

The symbolic names in the following examples are in DDL format, which uses hyphens

as separators. If your application is written in TAL, Inspect displays symbolic names

using the circumflex symbol (^) rather than the hyphens.

1. The following command displays an SPI response buffer named SPI-BUFFER.

Inspect uses the SSGET procedure to extract the information from the buffer. The

FNAME [\system.]

FNAME32 \system.$volume.subvolume.filename

INT, INT2, INT4 Signed integer

LIST The word LIST for a generic list, the words ERROR LIST for an error list,

or the words DATA LIST for a data list

MAP Enclosed in quotation marks if displayable; otherwise, as an unsigned

numeric byte value preceded by a question mark

MARK The word MARK or the words SUBJECT MARK for the ZEMS-

SUBJECT-MARK token

SSCTL The words END LIST

SSID owner.ssname.version-text if the SSNAME record for the subsystem ID

is available, or owner.ssnumber.version-number converted using the

SSIDTOTEXT procedure

SSTBL The word TABLE

STRUCT Enclosed in quotation marks if displayable; otherwise, as an unsigned

numeric byte value preceded by a question mark

SUBVOL [system.]$volume.subvolume.

TIMESTAMP YYYY-MM-DD HH:MM:SS.mmm.nnn timestamp converted from GMT to

local civil time (LCT), or, if the timestamp is less than year one before the

conversion to LCT, as the elapsed time in microseconds

TOKENCODE 32-bit signed number for the token code, followed by the token data type,

token length, and token number in parentheses

TRANSID TMF transaction ID converted using the TRANSIDTOTEXT procedure

USERNAME group.user group-id, user-id

Table 6-2. SPI Token Formatting by the DISPLAY Command (page2of2)

Token Type Formatting Description