DSM Template Services Manual

Display-Text Procedures
DSM Template Services Manual—427187-004
2-14
SPI_BUFFER_FORMATNEXT_
Representation Determined by DISPLAY Clause
Table 2-3 shows the DISPLAY codes that are suitable to represent certain token data
types. Token data types that are not in the table have no suitable DISPLAY codes.
(Tokens with these types are representable. But they are represented through the
conversion associated with the token data type. For details, see Table 2-2.)
For the meaning of these DISPLAY codes, see Table 2-1 on page 2-11.
Representation of Field Values
The methods you use to represent fields and tokens in display text are essentially the
same. In addition, DDL DISPLAY clauses are honored with fields and mean the same
as they do with tokens.
Whereas token data types play a large role in determining the representation of simple
tokens, these DDL clauses play that role for fields:
•
DDL TYPE and PIC clauses. Basic field types—for example, integers, character
strings, and Boolean variables—are available in DDL through TYPE and PIC
clauses.
•
DDL TACL clauses. The more complex types—TSTAMP, SSID, and FNAME32, for
example—are available in DDL through TACL clauses.
Representation Determined by DDL Types
Table 2-4 and Table 2-5 show the conversion methods that are indicated for fields with
TYPE and TACL clauses, respectively. The ellipsis (...) indicates missing parts of the
declaration, not repetition.
Table 2-3. Suitable DISPLAY Codes by Token Data Type
Token Data Type
(ZSPI-TDT-) DISPLAY Codes Used With This Type
BYTE I, B, O, Z
CHAR A, I, B, O, Z
ENUM I, B, O, Z
INT I, B, O, Z
INT2 I, B, O, Z
INT4 I, B, O, Z
TOKENCODE I, B, O, Z
UINT I, B, O, Z
Note. If both TACL and TYPE clauses are present for the same field, the TACL clause
determines the representation.