LINC Programming Reference Manual - Public Support Login - Unisys

System Data Item Descriptions
To force the Report output to a terminal printer group (regardless of other settings), prior
to the first PRINT.FRAME; command, move the name of a group (defined in the
LINC16TP/GROUPS file) to GLB.TPGROUP.
For details of using GLB.TPGROUP, see your MCP Based LINC Administration and
Operations Guide.
LENGTH = 10 EDIT = A
GLB.TRANSTATE
GLB.UNIQUE
GLB.USER
Note: This System Data item is valid for MCP based Report logic only.
GLB.TRANSTATE is a read-only System Data item which is automatically set by the LINC
System to indicate when a Report is in transaction state at run time.
If your Report is in transaction state, GLB.TRANSTATE is set to 1, otherwise it is set to
zero.
LENGTH = 1 EDIT = N
GLB.UNIQUE is a read-only System Data item that is automatically incremented by the
LINC System for every transaction except Automatic Entries. It is accessible in Ispec logic
only, and provides a unique number for each transaction.
For OS 2200 based and UNIX environments, GLB.UNIQUE is stored in the database.
For an MCP based LINC System, GLB.UNIQUE is stored in a file on your Dictionary pack,
with a duplicate on your Audit pack as a backup. For further details on GLB.UNIQUE and
changing the current value in an MCP environment, see your MCP Based LINC
Administration and Operations Guide.
LENGTH = 12 EDIT = N
GLB.USER associates a user name with output from ROC Standard Reports, for security
purposes. If the value is not set to spaces, Report output is visible only to users signed on
with the user name contained in GLB.USER for the particular Report, or with a user name
of spaces. GLB.USER is ignored for Direct Reports, and can only be used in Report logic.
For an MCP based LINC System, user names are validated against usercodes.
2-68 v