SPI Tokens
Data Definition Language (DDL) Reference Manual — 426798-002
7 -7
TOKEN-TYPE Statement
DDL generates the token-type value by left-shifting the token length in the second
(low-order) byte and combining it with the token data type in the first (high-
order) byte.
•
TAL source code:
Literal ZSPI^TYP^INT = 2 '<<' 8 + 2;
Literal ASSN^TYP^STATUS = 2 '<<' 8 + 2;
Literal ASSN^TYP^VARIABLE^TOKEN = 3 '<<' 8 + 255;
The generated values are identical to the values generated for COBOL or TACL
source-code output from the same TOKEN-TYPE statements.
•
TACL source code:
?Section ZSPI^TYP^INT Struct
BEGIN
UINT TOKEN^TYPE VALUE 514;
END;
?Section ASSN^TYP^STATUS Struct
BEGIN
UINT TOKEN^TYPE VALUE 514;
END;
?Section ASSN^TYP^VARIABLE^TOKEN Struct
BEGIN
UINT TOKEN^TYPE VALUE 1023;
END;
The generated values are identical to the values generated for pTAL, TAL, or
COBOL source-code output from the same TOKEN-TYPE statements.
•
C source code:
#pragma section zspi_typ_int
#define ZSPI_TYP_INT 514U
#pragma section assn_typ_status
#define ASSN_TYP_STATUS 514U
#pragma section assn_typ_variable_token
#define ASSN_TYP_VARIABLE_TOKEN 1023U
The generated values are identical to the values generated for COBOL, TAL, or
TACL source-code output from the same TOKEN-TYPE statements.
•
Pascal source code:
?Section ZSPI_TYP_INT
CONST ZSPI_TYP_INT = 514;
?Section ASSN_TYP_STATUS
CONST ASSN_TYP_STATUS = 514;