DSM Template Services Manual

Display-Text Procedures
DSM Template Services Manual—427187-004
2-11
SPI_BUFFER_FORMATNEXT_
In this example, all tokens are simple rather than structured. The value of
Generation Timestamp is split between two lines, so the logical-line length is not
exceeded.
Representation of Tokens and Fields
Representing token values in display text is nearly the same as representing field
values. Differences are pointed out where applicable throughout this section.
DISPLAY Clauses and Conversion Methods
Through a DDL DISPLAY clause, you can choose which conversion method
represents a simple token or a field of a structured token in display text. To do so,
include the DISPLAY clause in the DDL definition file in which the token or field is
defined. Table 2-1 shows the applicable methods and DISPLAY clauses.
Example 2-1. Appearance of EMS Event Message 520 (ZEMS-EVT-FILE-ROTATE-
PURGE
Header Type: 1
Checksum: F
Last Error: 0
Last Error Tkncode: (0,0,0)
Max Field Version: 0
SSID: TANDEM.EMS.C20
Used Byte Length: 118
Buffer Byte Length: 1000
Console Print: F
CPU: 2
Crtpid: \NCN.02,094
Emphasis: F
Event Number: 520
Generation Timestamp: 1986-05-13 14:25:00.00
0.000
Logged Timestamp: 00:00:00.000.000
PIN: 94
Suppress Display: F
System Number: 221
Userid: 165 82
Subject Mark:*
Collector: 0
Purged Logfile:- $VOLUME.SUBVOL.FNAME
Table 2-1. DISPLAY-Clause Conversion Methods (page 1 of 2)
DISPLAY Code Conversion Method Fill Character
“Iw“ Integer to decimal Leading spaces
“Iw.m“ Integer to decimal Leading zeros
“Bw“ Integer to binary Leading spaces
“Bw.m“ Integer to binary Leading zeros
“Ow“ Integer to octal Leading spaces
“Ow.m“ Integer to octal Leading zeros