LINC Programming Reference Manual - Public Support Login - Unisys

LINC 

Programming 

Reference Manual 

May 1998 

v

!()+ 

LINC 

Programming 

Reference Manual 

Copyright ( 1998 Unisys Corporation. 

All rights reserved. 

Unisys is a registered trademark of Unisys Corporation. 

LINC is a registered trademark of Unisys Corporation. 

Level 16.3/16R3 May 1998 

v

The names, places, and/or events used in this publication are not intended to correspond to any 

individual, group, or association existing, living or otherwise. Any similarity or likeness of the names, 

places and/or events with the names of any individual living or otherwise is purely coincidental and 

unintentional. 

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product and related 

material disclosed herein are only furnished pursuant and subject to the terms and conditions of a duly 

executed Program Product License or Agreement to Purchase or Lease Equipment. The only warranties 

made by Unisys, if any, with respect to the products described in this document are set forth in such 

License or Agreement. Unisys cannot accept any financial or other responsibilities that may be the 

result of your use of this information or software material, including direct, indirect, special or 

consequential damages. 

You should be very careful to ensure that the use of this software material and/or information complies 

with the laws, rules, and regulations of the jurisdictions with respect to which it is used. 

The information contained herein is subject to change without notice. Revisions may be issued to advise 

of such changes and/or additions. 

RESTRICTED. Use, reproduction, or disclosure is subject to the restrictions set forth in DFARS 

252.227-7013 and FAR 52.227-14 for commercial computer software. 

Correspondence regarding this publication should be forwarded using the Business Reply Mail form at 

the back of this document to:Australian Centre for Unisys Software, 115 Wicks Road, North Ryde NSW 

2113, AUSTRALIA. Alternatively you can send an E-Mail message to: linc.pi@unisys.com 

MAPPER is a registered trademark of Unisys Corporation. 

UNIX is a registered trademark of X/Open Company Ltd. 

Sequent is a registered trademark of Sequent Computer Systems Inc. 

PTX is a registered trademark of Sequent Computer Systems Inc. 

Sun is a registered trademark of Sun Microsystems, Inc. 

RS/6000 is a registered trademark of International Business Machines Inc.

Contents 

About This Document :::::::::::::::::::::::::::::::::::::::::: xix 

Section 1. LINC Logic Commands 

Overview ::::::::::::::::::::::::::::::::::::::::::: 1-1 

Conventions for Syntax Diagrams ::::::::::::::::::::: 1-3 

ABORT ::::::::::::::::::::::::::::::::::::::::::::: 1-6 

Using the ABORT; Command in Ispecs :::::::::::: 1-6 

Using the ABORT; Command in Reports :::::::::: 1-7 

Syntax :::::::::::::::::::::::::::::::::::: 1-7 

Examples :::::::::::::::::::::::::::::::::: 1-7 

References ::::::::::::::::::::::::::::::::: 1-8 

ACCEPT (AX) ::::::::::::::::::::::::::::::::::::::: 1-9 

Syntax :::::::::::::::::::::::::::::::::::: 1-9 

Examples :::::::::::::::::::::::::::::::::: 1-10 


ACCESS.EXT (AEXT) ::::::::::::::::::::::::::::::::: 1-11 

Syntax :::::::::::::::::::::::::::::::::::: 1-11 

Examples :::::::::::::::::::::::::::::::::: 1-13 

Reference :::::::::::::::::::::::::::::::::: 1-14 

ADD (AD) ::::::::::::::::::::::::::::::::::::::::::: 1-15 

Syntax :::::::::::::::::::::::::::::::::::: 1-15 

Examples :::::::::::::::::::::::::::::::::: 1-15 


ADHOC.MODE (ADHOC) :::::::::::::::::::::::::::::: 1-16 

Syntax :::::::::::::::::::::::::::::::::::: 1-16 


ADVANCE (AV) :::::::::::::::::::::::::::::::::::::: 1-17 

ADVANCE; CHANNEL Variant ::::::::::::::::::: 1-17 

Syntax :::::::::::::::::::::::::::::::::::: 1-17 

Examples :::::::::::::::::::::::::::::::::: 1-18 


ASCENDING :::::::::::::::::::::::::::::::::::::::: 1-18 

ATTACH (ATT) and ATTACH&SPACE (ATS) :::::::::::::: 1-19 

Truncation of Data ::::::::::::::::::::::::::: 1-19 

v iii

Contents 

Syntax :::::::::::::::::::::::::::::::::::: 1-20 

Examples :::::::::::::::::::::::::::::::::: 1-20 

ATTRIBUTE (ATTR) ::::::::::::::::::::::::::::::::::: 1-21 

Purpose of ATTRIBUTE; command ::::::::::::::: 1-21 

Errors ::::::::::::::::::::::::::::::::::::: 1-21 

Syntax :::::::::::::::::::::::::::::::::::: 1-22 

Examples :::::::::::::::::::::::::::::::::: 1-22 

AUTO (AU) and AUTO.ARRAY (AUA) :::::::::::::::::::: 1-23 

Transferring Values Using AUTO; and AUTO.ARRAY; 

Commands :::::::::::::::::::::::::::::: 1-23 

Syntax :::::::::::::::::::::::::::::::::::: 1-24 

Example ::::::::::::::::::::::::::::::::::: 1-25 


AUTO; CONTRA ::::::::::::::::::::::::::::::::::::: 1-27 

Syntax :::::::::::::::::::::::::::::::::::: 1-27 

Examples :::::::::::::::::::::::::::::::::: 1-27 


AUTO.CLEAR (AC) ::::::::::::::::::::::::::::::::::: 1-28 

Syntax :::::::::::::::::::::::::::::::::::: 1-28 

Example ::::::::::::::::::::::::::::::::::: 1-28 


AUTO.ENTRY (AE) ::::::::::::::::::::::::::::::::::: 1-29 

Syntax :::::::::::::::::::::::::::::::::::: 1-30 

Examples :::::::::::::::::::::::::::::::::: 1-30 


AUTO.FORMAT (AF) :::::::::::::::::::::::::::::::::: 1-32 

Syntax :::::::::::::::::::::::::::::::::::: 1-32 


AUTO; WRITE and AUTO; WRITE&CLEAR :::::::::::::::: 1-33 

Internal Automatic Entries ::::::::::::::::::::: 1-33 

External Automatic Entries ::::::::::::::::::::: 1-34 

OLTP Automatic Entry :::::::::::::::::::::::: 1-34 

Syntax :::::::::::::::::::::::::::::::::::: 1-36 

Examples :::::::::::::::::::::::::::::::::: 1-36 

Settings of GLB.STATUS and GLB.HUBSTATUS ::::: 1-37 


BEGIN.CASE (BC) :::::::::::::::::::::::::::::::::::: 1-43 

BEGIN.EDIT and END.EDIT :::::::::::::::::::::::::::: 1-44 

Syntax :::::::::::::::::::::::::::::::::::: 1-44 

Examples :::::::::::::::::::::::::::::::::: 1-44 

BEGIN.LOOP (BG) ::::::::::::::::::::::::::::::::::: 1-46 

Syntax :::::::::::::::::::::::::::::::::::: 1-46 

Examples :::::::::::::::::::::::::::::::::: 1-46 


iv v

Contents 

BEGIN.PAGE (BP) :::::::::::::::::::::::::::::::::::: 1-48 

Reports Using LINC Report Output Control (ROC) ::: 1-48 

Reports Not Using ROC ::::::::::::::::::::::: 1-48 

Syntax :::::::::::::::::::::::::::::::::::: 1-49 

Examples :::::::::::::::::::::::::::::::::: 1-49 


BREAK (BK) :::::::::::::::::::::::::::::::::::::::: 1-50 

Syntax :::::::::::::::::::::::::::::::::::: 1-50 

Examples :::::::::::::::::::::::::::::::::: 1-50 

CALL :::::::::::::::::::::::::::::::::::::::::::::: 1-51 

Syntax :::::::::::::::::::::::::::::::::::: 1-52 

Using the CALL; Command in LDA ::::::::::::::: 1-55 

Using BYFUNCTION; with the CALL; Command ::::: 1-56 

Using Coroutines with the CALL; Command :::::::: 1-58 

Examples :::::::::::::::::::::::::::::::::: 1-59 


CASE (CS) :::::::::::::::::::::::::::::::::::::::::: 1-61 

Syntax :::::::::::::::::::::::::::::::::::: 1-61 

Examples :::::::::::::::::::::::::::::::::: 1-63 


CLEAR.ARRAY; (CLA) :::::::::::::::::::::::::::::::: 1-64 

COMPUTE (COMP) and COMPUTE.FROM (CMP, CF) :::::: 1-65 

Syntax :::::::::::::::::::::::::::::::::::: 1-65 

Examples :::::::::::::::::::::::::::::::::: 1-66 


CONTRA (CN) ::::::::::::::::::::::::::::::::::::::: 1-68 

Syntax :::::::::::::::::::::::::::::::::::: 1-68 

Example ::::::::::::::::::::::::::::::::::: 1-68 


CRITICAL.POINT (CP) :::::::::::::::::::::::::::::::: 1-69 

Critical Points in Reports Using ROC ::::::::::::: 1-70 

Storage of Recovery Data ::::::::::::::::::::: 1-71 

Syntax :::::::::::::::::::::::::::::::::::: 1-71 

Example ::::::::::::::::::::::::::::::::::: 1-72 


CURSOR (CU) ::::::::::::::::::::::::::::::::::::::: 1-74 

Syntax :::::::::::::::::::::::::::::::::::: 1-74 

Examples :::::::::::::::::::::::::::::::::: 1-74 

DATE.CONVERT (DC) :::::::::::::::::::::::::::::::: 1-75 

Complex Form :::::::::::::::::::::::::::::: 1-75 

Data Item Formats ::::::::::::::::::::::::::: 1-79 

Examples :::::::::::::::::::::::::::::::::: 1-80 

Simple Form :::::::::::::::::::::::::::::::: 1-81 

DESCENDING (DSC) ::::::::::::::::::::::::::::::::: 1-82 

v v

Contents 

DETACH (DET, DTH) ::::::::::::::::::::::::::::::::: 1-83 

Position and Delimiter ::::::::::::::::::::::::: 1-83 

Truncation of Data ::::::::::::::::::::::::::: 1-83 

Syntax :::::::::::::::::::::::::::::::::::: 1-84 

Examples :::::::::::::::::::::::::::::::::: 1-84 


DETERMINE; (DT) Commands ::::::::::::::::::::::::: 1-86 

Variants of the DETERMINE; Command ::::::::::: 1-86 

Setting of GLB.STATUS ::::::::::::::::::::::: 1-87 

Logically Deleted Records ::::::::::::::::::::: 1-87 

Handling of Duplicate Keys in MCP based LINC 

Systems :::::::::::::::::::::::::::::::: 1-88 

DETERMINE; Commands in ORACLE LINC Systems :: 1-88 

DETERMINE; Commands Over Multiple Logic Lines :: 1-88 

DETERMINE; ACTUAL :::::::::::::::::::::::::::::::: 1-90 

Extract File Processing :::::::::::::::::::::::: 1-90 

Syntax :::::::::::::::::::::::::::::::::::: 1-92 

Example ::::::::::::::::::::::::::::::::::: 1-93 


DETERMINE; BACK :::::::::::::::::::::::::::::::::: 1-95 

Syntax :::::::::::::::::::::::::::::::::::: 1-95 


DETERMINE; EVERY ::::::::::::::::::::::::::::::::: 1-96 

Syntax :::::::::::::::::::::::::::::::::::: 1-96 

Example ::::::::::::::::::::::::::::::::::: 1-96 


DETERMINE; FROM :::::::::::::::::::::::::::::::::: 1-98 

Syntax :::::::::::::::::::::::::::::::::::: 1-98 

Example ::::::::::::::::::::::::::::::::::: 1-98 


DETERMINE; GROUP ::::::::::::::::::::::::::::::::: 1-100 

Syntax :::::::::::::::::::::::::::::::::::: 1-100 

Examples :::::::::::::::::::::::::::::::::: 1-101 


DETERMINE; LAST ::::::::::::::::::::::::::::::::::: 1-103 

Syntax :::::::::::::::::::::::::::::::::::: 1-103 

Examples :::::::::::::::::::::::::::::::::: 1-103 


DETERMINE; TOTAL ::::::::::::::::::::::::::::::::: 1-105 

Syntax :::::::::::::::::::::::::::::::::::: 1-105 

Examples :::::::::::::::::::::::::::::::::: 1-105 


DISCOUNT.CASH (DCF) :::::::::::::::::::::::::::::: 1-107 

Syntax :::::::::::::::::::::::::::::::::::: 1-107 

vi v

Contents 


DIVIDE (DV) ::::::::::::::::::::::::::::::::::::::::: 1-109 

Syntax :::::::::::::::::::::::::::::::::::: 1-109 

Examples :::::::::::::::::::::::::::::::::: 1-110 


DO.WHEN (DW) ::::::::::::::::::::::::::::::::::::: 1-111 

Syntax :::::::::::::::::::::::::::::::::::: 1-111 


Examples :::::::::::::::::::::::::::::::::: 1-113 


ELSE :::::::::::::::::::::::::::::::::::::::::::::: 1-114 

Syntax :::::::::::::::::::::::::::::::::::: 1-114 


END ::::::::::::::::::::::::::::::::::::::::::::::: 1-116 

Syntax :::::::::::::::::::::::::::::::::::: 1-116 

Example ::::::::::::::::::::::::::::::::::: 1-116 


END.EDIT :::::::::::::::::::::::::::::::::::::::::: 1-116 

END.CASE (EC) ::::::::::::::::::::::::::::::::::::: 1-116 

END.EXIT (EE) :::::::::::::::::::::::::::::::::::::: 1-117 

Syntax :::::::::::::::::::::::::::::::::::: 1-117 

Examples :::::::::::::::::::::::::::::::::: 1-117 


END.NO.PRINT (ENP) :::::::::::::::::::::::::::::::: 1-118 

Syntax :::::::::::::::::::::::::::::::::::: 1-118 

Examples :::::::::::::::::::::::::::::::::: 1-118 


END.USE (EU) ::::::::::::::::::::::::::::::::::::::: 1-119 

Syntax :::::::::::::::::::::::::::::::::::: 1-119 


EXCLUSIVE.USE (EXU) ::::::::::::::::::::::::::::::: 1-120 

Syntax :::::::::::::::::::::::::::::::::::: 1-120 


EXTRACT (EX) :::::::::::::::::::::::::::::::::::::: 1-121 

Types of Extract File Format ::::::::::::::::::: 1-122 

Multiple Extracts to the Same File ::::::::::::::: 1-123 

Compatibility of Extract Files ::::::::::::::::::: 1-124 

Categories of Extract file :::::::::::::::::::::: 1-124 


Syntax :::::::::::::::::::::::::::::::::::: 1-126 

Examples :::::::::::::::::::::::::::::::::: 1-127 


FLAG (FL, FG) ::::::::::::::::::::::::::::::::::::::: 1-130 

Syntax :::::::::::::::::::::::::::::::::::: 1-131 

v vii

Contents 

Examples :::::::::::::::::::::::::::::::::: 1-132 


FLAG.ARRAY (FLA) :::::::::::::::::::::::::::::::::: 1-133 

Syntax :::::::::::::::::::::::::::::::::::: 1-133 

Examples :::::::::::::::::::::::::::::::::: 1-133 


GET.LENGTH; (GL) ::::::::::::::::::::::::::::::::::: 1-135 

Syntax :::::::::::::::::::::::::::::::::::: 1-135 

Examples :::::::::::::::::::::::::::::::::: 1-135 

GLB.STATUS (GS) ::::::::::::::::::::::::::::::::::: 1-137 

Syntax :::::::::::::::::::::::::::::::::::: 1-137 

Example ::::::::::::::::::::::::::::::::::: 1-138 


INITIALIZE (INIT) ::::::::::::::::::::::::::::::::::::: 1-139 

Syntax :::::::::::::::::::::::::::::::::::: 1-139 

Example ::::::::::::::::::::::::::::::::::: 1-140 


INSERT (INS) ::::::::::::::::::::::::::::::::::::::: 1-141 

Syntax :::::::::::::::::::::::::::::::::::: 1-141 

Example ::::::::::::::::::::::::::::::::::: 1-141 


JUMP.TO (JTO) :::::::::::::::::::::::::::::::::::::: 1-142 

Syntax :::::::::::::::::::::::::::::::::::: 1-142 

Examples :::::::::::::::::::::::::::::::::: 1-142 


KEYONLY :::::::::::::::::::::::::::::::::::::::::: 1-144 

Restrictions and Limitations :::::::::::::::::::: 1-144 

Syntax :::::::::::::::::::::::::::::::::::: 1-145 

Example ::::::::::::::::::::::::::::::::::: 1-145 


LABEL (LAB) :::::::::::::::::::::::::::::::::::::::: 1-146 

Syntax :::::::::::::::::::::::::::::::::::: 1-146 

Example ::::::::::::::::::::::::::::::::::: 1-146 


LEFT.ALIGN (LA) :::::::::::::::::::::::::::::::::::: 1-147 

Syntax :::::::::::::::::::::::::::::::::::: 1-147 

Examples :::::::::::::::::::::::::::::::::: 1-148 

LOAD :::::::::::::::::::::::::::::::::::::::::::::: 1-151 

Considerations for Using the LOAD; Command ::::: 1-151 

Syntax :::::::::::::::::::::::::::::::::::: 1-152 

Example ::::::::::::::::::::::::::::::::::: 1-152 


LOOK.UP; (LU;) Commands ::::::::::::::::::::::::::: 1-153 

Variants of the LOOK.UP; Command ::::::::::::: 1-153 

viii v

Contents 


Logically Deleted Records ::::::::::::::::::::: 1-154 

LOOK.UP; Commands for UNIX ORACLE LINC 

Systems :::::::::::::::::::::::::::::::: 1-155 


LOOK.UP; (LU) :::::::::::::::::::::::::::::::::::::: 1-156 

Syntax :::::::::::::::::::::::::::::::::::: 1-156 

Examples :::::::::::::::::::::::::::::::::: 1-156 


LOOK.UP; EVERY :::::::::::::::::::::::::::::::::::: 1-158 

Syntax :::::::::::::::::::::::::::::::::::: 1-158 

Examples :::::::::::::::::::::::::::::::::: 1-158 


LOOK.UP; FROM :::::::::::::::::::::::::::::::::::: 1-160 

Syntax :::::::::::::::::::::::::::::::::::: 1-160 

Examples :::::::::::::::::::::::::::::::::: 1-160 


LOOK.UP; GROUP ::::::::::::::::::::::::::::::::::: 1-161 

Syntax :::::::::::::::::::::::::::::::::::: 1-161 

Example ::::::::::::::::::::::::::::::::::: 1-162 


LOWER.CASE (LC) ::::::::::::::::::::::::::::::::::: 1-163 

Syntax :::::::::::::::::::::::::::::::::::: 1-163 


MATCH :::::::::::::::::::::::::::::::::::::::::::: 1-164 

Syntax :::::::::::::::::::::::::::::::::::: 1-165 

KEY; Command Option :::::::::::::::::::::::: 1-166 

Example 1 ::::::::::::::::::::::::::::::::: 1-166 

Example 2 ::::::::::::::::::::::::::::::::: 1-167 


MESSAGE (ME) :::::::::::::::::::::::::::::::::::::: 1-168 

Using MESSAGE; in OS 2200 based LINC Systems : 1-170 

Syntax :::::::::::::::::::::::::::::::::::: 1-170 

Examples :::::::::::::::::::::::::::::::::: 1-171 


MOVE (MV) ::::::::::::::::::::::::::::::::::::::::: 1-172 

Simple Form of the MOVE; Command :::::::::::: 1-172 

Complex Form of the MOVE; Command ::::::::::: 1-173 


MOVE.ARRAY (MVA) ::::::::::::::::::::::::::::::::: 1-177 

Syntax :::::::::::::::::::::::::::::::::::: 1-177 

Examples :::::::::::::::::::::::::::::::::: 1-178 

MOVE.AUTO (MA) and MOVE.AUTO.ARRAY (MAA) :::::::: 1-179 

Syntax :::::::::::::::::::::::::::::::::::: 1-180 

v ix

Contents 

Examples :::::::::::::::::::::::::::::::::: 1-180 


MOVE.DATE (MD) :::::::::::::::::::::::::::::::::::: 1-183 

Syntax :::::::::::::::::::::::::::::::::::: 1-183 


MOVE.TIME (MT) :::::::::::::::::::::::::::::::::::: 1-184 

Syntax :::::::::::::::::::::::::::::::::::: 1-184 


MULTI ::::::::::::::::::::::::::::::::::::::::::::: 1-185 

Syntax :::::::::::::::::::::::::::::::::::: 1-185 


MULTIPLY (MU) ::::::::::::::::::::::::::::::::::::: 1-186 

Syntax :::::::::::::::::::::::::::::::::::: 1-186 

Examples :::::::::::::::::::::::::::::::::: 1-186 


ON.CHANGE (OCH) :::::::::::::::::::::::::::::::::: 1-187 

Values of Data items ::::::::::::::::::::::::: 1-187 

Grouping ON.CHANGE; Commands :::::::::::::: 1-187 

ON.CHANGE; Statistical Routines :::::::::::::::: 1-189 


OTHERWISE (OW) ::::::::::::::::::::::::::::::::::: 1-192 

PAGE (PG) :::::::::::::::::::::::::::::::::::::::::: 1-193 

Syntax :::::::::::::::::::::::::::::::::::: 1-193 

Example ::::::::::::::::::::::::::::::::::: 1-193 


PERFORM.FRAME.LOGIC (PFL) :::::::::::::::::::::::: 1-195 

Syntax :::::::::::::::::::::::::::::::::::: 1-195 


PRINT.FRAME (PF) ::::::::::::::::::::::::::::::::::: 1-196 

Syntax :::::::::::::::::::::::::::::::::::: 1-197 

Examples :::::::::::::::::::::::::::::::::: 1-197 


PURGE (PU) :::::::::::::::::::::::::::::::::::::::: 1-198 

Syntax :::::::::::::::::::::::::::::::::::: 1-198 

Example ::::::::::::::::::::::::::::::::::: 1-198 


RECALL (RC) ::::::::::::::::::::::::::::::::::::::: 1-199 

Syntax :::::::::::::::::::::::::::::::::::: 1-200 

Examples :::::::::::::::::::::::::::::::::: 1-200 


RELEASE (REL) :::::::::::::::::::::::::::::::::::::: 1-202 

Reports Using Report Output Control (ROC) :::::::: 1-202 

Reports Not Using ROC (MCP environment only) :::: 1-202 

Syntax :::::::::::::::::::::::::::::::::::: 1-202 

x v

Contents 

Examples :::::::::::::::::::::::::::::::::: 1-202 

RESTART (RT) ::::::::::::::::::::::::::::::::::::::: 1-203 

Syntax :::::::::::::::::::::::::::::::::::: 1-203 

Examples :::::::::::::::::::::::::::::::::: 1-203 


ROC.MODE (ROC) ::::::::::::::::::::::::::::::::::: 1-205 

Syntax :::::::::::::::::::::::::::::::::::: 1-205 


RUN ::::::::::::::::::::::::::::::::::::::::::::::: 1-206 

For an MCP based LINC System :::::::::::::::: 1-206 

For an OS 2200 based LINC System ::::::::::::: 1-206 

For a UNIX LINC System ::::::::::::::::::::::: 1-207 

In LDA Run Time ::::::::::::::::::::::::::::: 1-207 

All Hosts ::::::::::::::::::::::::::::::::::: 1-207 

SECURE :::::::::::::::::::::::::::::::::::::::::::: 1-211 




Syntax :::::::::::::::::::::::::::::::::::: 1-212 

Examples :::::::::::::::::::::::::::::::::: 1-212 


SEND.MESSAGE (SEND.STATUS; SM; SMSG; SS) :::::::: 1-213 

Syntax :::::::::::::::::::::::::::::::::::: 1-214 

Examples :::::::::::::::::::::::::::::::::: 1-214 


SEND.PRINT (SEND, SP) :::::::::::::::::::::::::::::: 1-215 

Syntax :::::::::::::::::::::::::::::::::::: 1-215 


SENDLIST.DYNAMIC (SLDYN) ::::::::::::::::::::::::: 1-217 

AboutListBoxes :::::::::::::::::::::::::::: 1-217 

For OS 2200 Based LINC Systems :::::::::::::: 1-218 

Format of the Data ::::::::::::::::::::::::::: 1-218 

Syntax :::::::::::::::::::::::::::::::::::: 1-219 

Example ::::::::::::::::::::::::::::::::::: 1-220 


SENDLIST.STATIC (SLSTA) :::::::::::::::::::::::::::: 1-221 

AboutListBoxes :::::::::::::::::::::::::::: 1-221 

Availability of the Command :::::::::::::::::::: 1-221 

Format of the Data ::::::::::::::::::::::::::: 1-222 

Syntax :::::::::::::::::::::::::::::::::::: 1-222 

Examples :::::::::::::::::::::::::::::::::: 1-223 


SERIAL ::::::::::::::::::::::::::::::::::::::::::::: 1-224 

Syntax :::::::::::::::::::::::::::::::::::: 1-224 

v xi

Contents 

Example ::::::::::::::::::::::::::::::::::: 1-225 


SET.DB :::::::::::::::::::::::::::::::::::::::::::: 1-226 

Syntax :::::::::::::::::::::::::::::::::::: 1-226 

Examples :::::::::::::::::::::::::::::::::: 1-227 


SET.TITLE (SETT) :::::::::::::::::::::::::::::::::::: 1-230 


Syntax :::::::::::::::::::::::::::::::::::: 1-231 

Examples :::::::::::::::::::::::::::::::::: 1-233 


SLEEP (SLP) :::::::::::::::::::::::::::::::::::::::: 1-234 

Report Output Control (ROC) Standard Reports ::::: 1-235 

Syntax :::::::::::::::::::::::::::::::::::: 1-235 

Examples :::::::::::::::::::::::::::::::::: 1-235 


SORT (SO) :::::::::::::::::::::::::::::::::::::::::: 1-237 


Syntax :::::::::::::::::::::::::::::::::::: 1-238 

Examples :::::::::::::::::::::::::::::::::: 1-239 


START (ST) ::::::::::::::::::::::::::::::::::::::::: 1-241 

Syntax :::::::::::::::::::::::::::::::::::: 1-243 

Examples :::::::::::::::::::::::::::::::::: 1-244 


STN.INFO (SI) ::::::::::::::::::::::::::::::::::::::: 1-245 




Syntax :::::::::::::::::::::::::::::::::::: 1-246 

SUBTRACT (SB) ::::::::::::::::::::::::::::::::::::: 1-247 

Syntax :::::::::::::::::::::::::::::::::::: 1-247 

Example ::::::::::::::::::::::::::::::::::: 1-247 


SWITCH.TO (SWT) ::::::::::::::::::::::::::::::::::: 1-248 

Runtime Requirements :::::::::::::::::::::::: 1-249 

Runtime Transaction Flow ::::::::::::::::::::: 1-249 

Syntax :::::::::::::::::::::::::::::::::::: 1-250 

Examples :::::::::::::::::::::::::::::::::: 1-253 


TRACE (TR) ::::::::::::::::::::::::::::::::::::::::: 1-255 

Syntax :::::::::::::::::::::::::::::::::::: 1-255 

Example ::::::::::::::::::::::::::::::::::: 1-255 


xii v

Contents 

UPPER.CASE (UC) ::::::::::::::::::::::::::::::::::: 1-256 

Syntax :::::::::::::::::::::::::::::::::::: 1-256 


WAKE.UP (WU) :::::::::::::::::::::::::::::::::::::: 1-257 

Syntax :::::::::::::::::::::::::::::::::::: 1-258 

Example ::::::::::::::::::::::::::::::::::: 1-258 


Section 2. System Data Items 

Overview ::::::::::::::::::::::::::::::::::::::::::: 2-1 

Screen Heading Information :::::::::::::::::::::::::: 2-2 

Recovery of System Data Items ::::::::::::::::::::::: 2-3 

System Data Item Descriptions :::::::::::::::::::::::: 2-9 

ACTMTH ::::::::::::::::::::::::::::::::::: 2-9 

GLB.ACTIONKEY ::::::::::::::::::::::::::::: 2-9 

GLB.ADD :::::::::::::::::::::::::::::::::: 2-10 

GLB.ALTUSER :::::::::::::::::::::::::::::: 2-10 

GLB.APPNAME :::::::::::::::::::::::::::::: 2-11 

GLB.APPNO :::::::::::::::::::::::::::::::: 2-11 

GLB.ASCPRT ::::::::::::::::::::::::::::::: 2-11 

GLB.ASCPRTHOST ::::::::::::::::::::::::::: 2-12 

GLB.BACKUP ::::::::::::::::::::::::::::::: 2-12 

GLB.BALANCE :::::::::::::::::::::::::::::: 2-13 

GLB.BASE :::::::::::::::::::::::::::::::::: 2-14 

GLB.CCS :::::::::::::::::::::::::::::::::: 2-14 

GLB.CENTURY :::::::::::::::::::::::::::::: 2-14 

GLB.CENTURY-START ::::::::::::::::::::::::: 2-15 

GLB.CHANGE ::::::::::::::::::::::::::::::: 2-15 

GLB.CHARGECODE ::::::::::::::::::::::::::: 2-15 

GLB.CHG :::::::::::::::::::::::::::::::::: 2-16 

GLB.CLOSE :::::::::::::::::::::::::::::::: 2-16 

GLB.COPY ::::::::::::::::::::::::::::::::: 2-16 

GLB.CORSTATUS :::::::::::::::::::::::::::: 2-17 

GLB.DATE :::::::::::::::::::::::::::::::::: 2-17 

GLB.DBG- System Data Items :::::::::::::::::: 2-17 

GLB.DBTYPE ::::::::::::::::::::::::::::::: 2-18 

GLB.DC- System Data Items :::::::::::::::::::: 2-18 

GLB.DC-CC ::::::::::::::::::::::::::::::::: 2-20 

GLB.DEL ::::::::::::::::::::::::::::::::::: 2-20 

GLB.DESTENV :::::::::::::::::::::::::::::: 2-20 

GLB.DESTHOST ::::::::::::::::::::::::::::: 2-20 

GLB.DESTINATION ::::::::::::::::::::::::::: 2-21 

v xiii

Contents 

GLB.DESTNOFORM :::::::::::::::::::::::::: 2-21 

GLB.DEVICE :::::::::::::::::::::::::::::::: 2-22 

GLB.DLRECOVER :::::::::::::::::::::::::::: 2-23 

GLB.EOP ::::::::::::::::::::::::::::::::::: 2-24 

GLB.ERROR :::::::::::::::::::::::::::::::: 2-24 

GLB.EXAMKEY :::::::::::::::::::::::::::::: 2-25 

GLB.EXNAME ::::::::::::::::::::::::::::::: 2-25 

GLB.EXTDB ::::::::::::::::::::::::::::::::: 2-25 

GLB.EXTDBSTATUS :::::::::::::::::::::::::: 2-26 

GLB.EXTEXT :::::::::::::::::::::::::::::::: 2-27 

GLB.FILEINFO ::::::::::::::::::::::::::::::: 2-27 

GLB.FILLER ::::::::::::::::::::::::::::::::: 2-27 

GLB.FORMDEPTH :::::::::::::::::::::::::::: 2-28 

GLB.FORMID :::::::::::::::::::::::::::::::: 2-29 

GLB.FULLLENGTH ::::::::::::::::::::::::::: 2-30 

GLB.FULLSTN ::::::::::::::::::::::::::::::: 2-30 

GLB.GUI ::::::::::::::::::::::::::::::::::: 2-30 

GLB.HIGH :::::::::::::::::::::::::::::::::: 2-31 

GLB.HTIMEOUT :::::::::::::::::::::::::::::: 2-31 

GLB.HUBSTATUS :::::::::::::::::::::::::::: 2-31 

GLB.HUBTIMEOUT ::::::::::::::::::::::::::: 2-31 

GLB.INITFULLSTN :::::::::::::::::::::::::::: 2-32 

GLB.INITSTN :::::::::::::::::::::::::::::::: 2-32 

GLB.INPUTDATA ::::::::::::::::::::::::::::: 2-33 

GLB.INQ ::::::::::::::::::::::::::::::::::: 2-33 

GLB.LANGUAGE ::::::::::::::::::::::::::::: 2-33 

GLB.LENGTH ::::::::::::::::::::::::::::::: 2-34 

GLB.LINECOUNT :::::::::::::::::::::::::::: 2-34 

GLB.LINEUP :::::::::::::::::::::::::::::::: 2-35 

GLB.LINEUPNAME ::::::::::::::::::::::::::: 2-36 

GLB.LOW :::::::::::::::::::::::::::::::::: 2-36 

GLB.MACHINE :::::::::::::::::::::::::::::: 2-36 

GLB.MATCH :::::::::::::::::::::::::::::::: 2-37 

GLB.MAXCOPY :::::::::::::::::::::::::::::: 2-37 

GLB.MIXNO ::::::::::::::::::::::::::::::::: 2-37 

GLB.NUMCOPIES :::::::::::::::::::::::::::: 2-37 

GLB.OLTPSERVICE ::::::::::::::::::::::::::: 2-38 

GLB.OLTPSUBTYPE :::::::::::::::::::::::::: 2-38 

GLB.OLTPTYPE :::::::::::::::::::::::::::::: 2-38 

GLB.OLTPVALUE :::::::::::::::::::::::::::: 2-39 

GLB.ORIGIN :::::::::::::::::::::::::::::::: 2-39 

GLB.ORIGINENV ::::::::::::::::::::::::::::: 2-39 

GLB.ORIGINHOST :::::::::::::::::::::::::::: 2-40 

GLB.ORIGINISPEC :::::::::::::::::::::::::::: 2-40 

xiv v

Contents 

GLB.ORIGINPTN ::::::::::::::::::::::::::::: 2-41 

GLB.ORIGINXNID ::::::::::::::::::::::::::::: 2-41 

GLB.PAGECOUNT :::::::::::::::::::::::::::: 2-41 

GLB.PARAM :::::::::::::::::::::::::::::::: 2-42 

GLB.PARAMFLAG :::::::::::::::::::::::::::: 2-42 

GLB.PITCH ::::::::::::::::::::::::::::::::: 2-43 

GLB.PREVISPEC ::::::::::::::::::::::::::::: 2-43 

GLB.PRINTAT ::::::::::::::::::::::::::::::: 2-43 

GLB.PRINTBANNER :::::::::::::::::::::::::: 2-44 

GLB.PRINTHOST ::::::::::::::::::::::::::::: 2-44 

GLB.PRIORITY ::::::::::::::::::::::::::::::: 2-45 

GLB.PRIV :::::::::::::::::::::::::::::::::: 2-46 

GLB.PRODUCT :::::::::::::::::::::::::::::: 2-47 

GLB.PRTPARAM ::::::::::::::::::::::::::::: 2-48 

GLB.PUR ::::::::::::::::::::::::::::::::::: 2-48 

GLB.RECORDx :::::::::::::::::::::::::::::: 2-48 

GLB.RECOVER :::::::::::::::::::::::::::::: 2-49 

GLB.REPGENDATE ::::::::::::::::::::::::::: 2-49 

GLB.REPGENTIME ::::::::::::::::::::::::::: 2-49 

GLB.REPLANG :::::::::::::::::::::::::::::: 2-49 

GLB.REPNAME :::::::::::::::::::::::::::::: 2-50 

GLB.REPORT ::::::::::::::::::::::::::::::: 2-50 

GLB.REPUNIQUE ::::::::::::::::::::::::::::: 2-50 

GLB.REPVERSION :::::::::::::::::::::::::::: 2-51 

GLB.REQUEST :::::::::::::::::::::::::::::: 2-51 

GLB.ROCFLAG :::::::::::::::::::::::::::::: 2-51 

GLB.SAVEDAYS ::::::::::::::::::::::::::::: 2-51 

GLB.SECONDARY :::::::::::::::::::::::::::: 2-52 

GLB.SELF :::::::::::::::::::::::::::::::::: 2-52 

GLB.SELFDB :::::::::::::::::::::::::::::::: 2-53 

GLB.SELFENV ::::::::::::::::::::::::::::::: 2-53 

GLB.SELFHOST ::::::::::::::::::::::::::::: 2-53 

GLB.SELFXNID :::::::::::::::::::::::::::::: 2-54 

GLB.SHADOW ::::::::::::::::::::::::::::::: 2-54 

GLB.SOURCE ::::::::::::::::::::::::::::::: 2-54 

GLB.SPACES ::::::::::::::::::::::::::::::: 2-54 

GLB.STALANG :::::::::::::::::::::::::::::: 2-55 

GLB.STATION ::::::::::::::::::::::::::::::: 2-55 

GLB.STATUS ::::::::::::::::::::::::::::::: 2-55 

GLB.STN ::::::::::::::::::::::::::::::::::: 2-57 

GLB.STNHOST :::::::::::::::::::::::::::::: 2-59 

GLB.STYLE ::::::::::::::::::::::::::::::::: 2-59 

GLB.SUBSYS ::::::::::::::::::::::::::::::: 2-60 

GLB.SYSGENDATE ::::::::::::::::::::::::::: 2-61 

v xv

Contents 

GLB.SYSGENTIME ::::::::::::::::::::::::::: 2-61 

GLB.SYSVERSION :::::::::::::::::::::::::::: 2-62 

GLB.TASK :::::::::::::::::::::::::::::::::: 2-62 

GLB.TIME :::::::::::::::::::::::::::::::::: 2-64 

GLB.TITLE :::::::::::::::::::::::::::::::::: 2-64 

GLB.TODAY :::::::::::::::::::::::::::::::: 2-66 

GLB.TODAYS-DATE-NUM :::::::::::::::::::::: 2-66 

GLB.TODAYS-DAY :::::::::::::::::::::::::::: 2-66 

GLB.TODAYS-MONTH ::::::::::::::::::::::::: 2-67 

GLB.TODAYS-MONTH-NUM ::::::::::::::::::::: 2-67 

GLB.TODAYS-YEAR ::::::::::::::::::::::::::: 2-67 

GLB.TOTAL ::::::::::::::::::::::::::::::::: 2-67 

GLB.TPGROUP :::::::::::::::::::::::::::::: 2-67 

GLB.TRANSTATE :::::::::::::::::::::::::::: 2-68 

GLB.UNIQUE :::::::::::::::::::::::::::::::: 2-68 

GLB.USER :::::::::::::::::::::::::::::::::: 2-68 

GLB.USERCODE ::::::::::::::::::::::::::::: 2-69 

GLB.VERSIONID ::::::::::::::::::::::::::::: 2-69 

GLB.WORK ::::::::::::::::::::::::::::::::: 2-70 

GLB.YYMMDD ::::::::::::::::::::::::::::::: 2-70 

GLB.ZEROS :::::::::::::::::::::::::::::::: 2-70 

GLB.2PC ::::::::::::::::::::::::::::::::::: 2-71 

INPUT-DATE :::::::::::::::::::::::::::::::: 2-71 

ISPEC ::::::::::::::::::::::::::::::::::::: 2-72 

LAST-LINE :::::::::::::::::::::::::::::::::: 2-72 

MAINT ::::::::::::::::::::::::::::::::::::: 2-72 

TODAY :::::::::::::::::::::::::::::::::::: 2-76 

TODAYS-DATE-NUM :::::::::::::::::::::::::: 2-76 

TODAYS-DAY ::::::::::::::::::::::::::::::: 2-77 

TODAYS-MONTH ::::::::::::::::::::::::::::: 2-77 

TODAYS-MONTH-NUM ::::::::::::::::::::::::: 2-77 

TODAYS-YEAR ::::::::::::::::::::::::::::::: 2-78 

TRANNO ::::::::::::::::::::::::::::::::::: 2-78 

Appendix A. Formulas for the DISCOUNT.CASH; Command 

Overview ::::::::::::::::::::::::::::::::::::::::::: A-1 

Calculations :::::::::::::::::::::::::::::::::::::::: A-2 

xvi v

Appendix B. Railroad Diagram Syntax 

Glossary 

Index 

Contents 

Overview ::::::::::::::::::::::::::::::::::::::::::: B-1 

Required Items ::::::::::::::::::::::::::::::::::::: B-2 

Optional Items :::::::::::::::::::::::::::::::::::::: B-2 

Loops :::::::::::::::::::::::::::::::::::::::::::::: B-2 

Bridges :::::::::::::::::::::::::::::::::::::::::::: B-3 

v xvii

About This Document 

Purpose 

Scope 

Audience 

The purpose of this document is to provide reference material for the definition of a LINC 

Specification. 

This document gives details of LINC commands and LINC System Data items. 

The primary audience for this document consists of developers responsible for the 

specification of LINC Systems. 

A secondary audience consists of LINC System designers who need to understand the 

capabilities of LINC Generate. 

Prerequisites 

The audience should have been trained on the LINC product. 

How to Use This Document 

This document should be used in conjunction with the LINC Generate Operations Guide. 

A list of LINC reserved words is provided in the LINC Release 16.3/16R3 Migration and 

Conversion Guide. 

Conventions used in each section are explained in the introduction to each section. 

This document refers to UNIX function keys (for example, the XMIT key). The key 

sequences equivalent to each function key are contained in your UNIX LINC 

Administration and Operations Guide. 

The term OS 2200 refers to Unisys computers using the OS 2200 operating system. 

Any reference to LINC means the LINC product. 

v xix


Organization 

This document is organized into two sections and two appendixes. 

Section 1. LINC Logic Commands 

This section describes LINC Logic commands, which are entered using LINC Editor. 

Section 2. System Data Items 

This section describes the predefined LINC System Data items. 

Appendix A. Formulas for the DISCOUNT.CASH; Command 

This appendix contains details of the formulas used by the DISCOUNT.CASH; command. 

Appendix B. Railroad Diagram Syntax 

This appendix shows how to interpret the syntax diagrams used in Section 1 of this 

document. 

Related Product Information 

The following documents contain information relevant to the definition and operation of a 

LINC System. These publications are intended as reference sources for users who have 

completed LINC training courses, and do not replace these courses. See your local Unisys 

representative for information on available LINC training courses. 

All of these documents are published by Unisys Corporation, and can be ordered through 

Plymouth Operations Software Manufacturing (POSM), or your local Unisys subsidiary. 

LINC Generate Operations Guide 

This document describes the use of LINC Generate to create and maintain user 

information systems. 

LINC Executive Overview - The Business Case (7833 2145) 

This document is an introduction to LINC for executive and general readers. 

LINC Technical Overview - The Business Case (7833 2152) 

This document is an overview of LINC features and facilities for more technically oriented 

readers. 

LINC Programming Reference Handbook (7844 8057) 

This document contains the syntax of LINC Logic commands and System Data items and 

other commands used in LINC Generate. 

xx v

LINC Generate Reference Manual: Painter and Editor 


This document contains reference material for LINC Generate, including LINC Editor and 

LINC Painter commands, Data commands and Data Attributes, and screens and commands 

for defining Profiles. 

A Series/V Series LINC II NETCON Operations Guide (7833 1980) 

This document describes how to define and generate an MCP based network. 

MCP Based LINC Administration and Operations Guide 

This document describes the generation and operation of LINC Systems and Reports, and 

the general administration of LINC Systems for MCP based hosts. 

MCP Based LINC Installation and Configuration Guide 

This document contains procedures for installing and configuring released LINC Software 

on MCP based hosts. 

OS 2200 Based LINC Administration and Operations Guide 


the general administration of LINC Systems for OS 2200 based hosts. 

OS 2200 Based LINC Installation and Configuration Guide 

This document describes the procedures for installing and configuring released LINC 

Software on OS 2200 based hosts. 

UNIX LINC Administration and Operations Guide 


the general administration of LINC Systems for UNIX based hosts. 

UNIX LINC on Unixware Installation and Configuration Guide 


Software on UnixWare hosts. 

UNIX LINC on Sun Installation and Configuration Guide 


Software on Sun hosts. 

UNIX LINC on RS/6000 Installation and Configuration Guide 


Software on RS/6000 hosts. 

v xxi


UNIX LINC on Sequent PTX Installation and Configuration Guide 


Software on Sequent PTX hosts. 

LINC Ad Hoc Inquiry Operations Guide 

This document describes the operation of LINC Ad Hoc Inquiry, which enables users to 

make inquiries against a LINC System, either interactively, or by using structured (SQL) 

statements. 

LINC Developers Guide: LCOPY 

This document provides reference material for using the LINC LCOPY Utility, which is 

used to transfer LINC Specifications between versions of LINC Generate. 

A Series DMS II Interpretive Interface Programming Reference Manual 

(8600-0155) 

This document gives details of MCP based DMS II Interpreter commands, some of which 

may be accessed in LINC logic. 

Micro Focus COBOL/2 U5000/6000 Operating Guide (UP 14120) 

This document contains reference material for UNIX LINC Systems, such as details of the 

use of the UNIX variable COBLPFORM with the ADVANCE; CHANNEL command. 

xxii v

Section 1 

LINC Logic Commands 

Overview 

This section covers LINC Logic commands, which define and implement the business rules 

of a LINC System in high level logic. Logic commands are entered by using the LINC Editor 

for Ispecs, Reports, and Global Logics. 

The following general statements apply throughout this section: 

$ Commands are listed alphabetically. 

$ Commands can be assumed as valid for Ispecs and Reports, and for Global Logic used 

in Ispecs or Reports, unless explicitly stated otherwise. Commands available in 

Insertable Global Logics depend on where the Global Logics are inserted (Ispecs or 

Reports). 

Note: Report-only commands will appear as errors in your Insertable 

Global Logic but may generate correctly in a Report. 

$ Commands can be assumed as valid for all types of target host (UNIX, MCP and 

OS 2200 environments), unless explicitly stated otherwise. 

$ Further restrictions may be contained in the command descriptions. 

$ The syntax of each command is given. 

To explain complex syntax, railroad diagrams are used. See Appendix B for guidance 

on interpreting these. 

Where explanations of command parameters are not included with the syntax 

diagram, see ‘‘Conventions for Syntax Diagrams’’, later in this section. 

$ The GLB.STATUS; command can be used with many commands to direct the error 

status to a specified data item instead of the System Data item GLB.STATUS. 

References to the System Data item GLB.STATUS may be taken to mean that specified 

data item where appropriate. 

Note: The GLB.STATUS; command is not included in the syntax diagrams 

of individual commands. 

$ In Reports, you can define data items with the same name in several Frames. Use OF; 

frame to identify which of these data items is being referenced. If not used, the current 

Frame is assumed. 

OF; is not a logic command or a command option. It is a data item qualification used to 

qualify a Frame data item in a Report logic command. For more details, see your LINC 

Generate Operations Guide. 

v 1-1

Overview 

$ For commands used in the definition of Keywords, see your LINC Generate Reference 

Manual: Painter and Editor. 

$ For commands used in defining Profiles, see your LINC Generate Reference Manual: 

Painter and Editor. 

$ Global Setup Data items and Dictionary items may also be further defined using the 

LINC Editor. See your LINC Generate Reference Manual: Painter and Editor for 

details. 

1-2 v

Conventions for Syntax Diagrams 

AS; shadow report 


The selection of a Shadow Report, identified by the one-character Shadow Report 

designator (A to Z). 

component 

The name of a Component. 

constant 

A numeric constant. A sign and decimal point may be included inside the parentheses. 

data item 

A data item (Data item, Ordinate, Setup Data item, or Global Setup Data item). When 

indicated by the syntax diagram, literals or System Data items may be used instead. In 

some instances GLB.ZEROS, GLB.SPACES, GLB.LOW, and GLB.HIGH are treated as 

special cases. 

Each Frame of a Report is logically distinct. If the same name is used for data items in 

several Frames, use the OF; data item qualification to specify which Frame applies for the 

particular item. The OF; is not required within Frame logic if you are referring to the data 

item in that Frame and it has already been painted. Otherwise, it refers to the first 

occurrence of this Frame item in the Report (and continues to do so after an item of the 

same name is painted in the same Frame, unless you re-edit your logic). For further 

information, see your LINC Generate Operations Guide. 

device 

The output device for a Report, as shown in the following table, by target host type. 

Value Report output device Valid for: 

LP Line Printer All hosts 

TP Terminal Printer All hosts 

VD Video All hosts 

RP Remote Printer MCP environment only 

DI ROC Direct output All ROC 

EX Extract file All ROC (OS 2200 environment 

via GLB.DEVICE in logic) 

FL Fast Load Report OS 2200 environment only 

Spaces ROC Standard output All ROC 

v 1-3


EVENT 

The Event Dataset. 

extract file 

The one-character Extract file designator (A through Z). 

frame 

A Frame number of the current Report (01 through 99, where99 represents main logic). 

GLB.STATUS; data item 

Directs that the error status of the command be stored in the specified data item instead of 

the System Data item GLB.STATUS. 

insertable global logic 

A predefined Global Logic to be inserted. 

performable global logic 

A predefined Global Logic to be performed. 

ispec 

The name of a Component or Event. 

label 

A previously defined label (see the LABEL; command). 

literal 

An alphanumeric value or a constant. The literal must be placed within parentheses. 

logic sequence 

One or more LINC logic commands. 

memo component 

The name of a Memo Component. 

multiple ordinate profile 

The Profile defining the multiple Ordinates of a Memo Component. 

numeric data 

A previously defined numeric data item, appropriate System Data item, or literal value. 

profile 

The name of a Profile. 

1-4 v

profile keys 


Data items whose values are to match those of Ordinates named in the Profile declaration, 

or the System Data items GLB.SPACES or GLB.ZEROS. 

There must be the same number of data items as Ordinates declared for the Profile. As the 

keys determine which records are retrieved from the LINC Database, they must be 

specified in the same order as declared in the Profile specification. The same name need 

not be used in both places, but a numeric data item may not be used as a key for an 

alphanumeric Profile Ordinate, or vice versa. 

A data item brought into memory may not be specified as a key over its own structure. For 

example, if the Profile is over a Component CUST, you may not specify CUST.data name 

as a key. If you need to do this, move the value to a Setup Data item, and specify that Setup 

Data item as the key. 

shadow report 

A Shadow Report, identified by the one-character Shadow Report designator (A to Z). 

v 1-5

ABORT 

ABORT 

The ABORT; command terminates the current transactions, and restores the LINC 

database. The command only allows the following actions after the termination: 

$ Display a message. The Ispec screen layout that was used to initiate the transaction or 

the screen used to initiate the Report is displayed. 

If no message is included, the message ABORTED: System commanded ABORT of 

this transaction is displayed. This message may be translated. 

$ Recall an Ispec (Ispec logic only). The message is displayed on the status line and the 

Ispec recalled. 

The ABORT; command causes any incomplete transactions to be rolled back. On OS 2200 

based LINC Systems, the Ispec screen layout that initiated the transaction, or the page 

used to start the Report (using the :RUN LINC System Command), will be displayed on 

your terminal if no Ispec Recall option is specified. For UNIX and MCP based LINC 

Systems, and for LDA Run Time, the screen remains unaltered, and the message will be 

displayed on the Status line. 

For details on the extent of a LINC transaction as affected by the ABORT; command, see 

your LINC Generate Operations Guide. 

OLTP 

Use of this command with OLTP is described in "Online Transaction Processing (OLTP)" in 


LDA 

For LDA, check the Preserve Session Data field in the Business Segment Options dialog 

box to enable the ABORT; command to roll back GLB.WORK. 

Using the ABORT; Command in Ispecs 

Note the following points when using the ABORT; command in Ispecs: 

$ The Ispec is rolled back to the start. This means that any AUTO; or FLAG; commands 

performed by the Ispec will also be rolled back, with the exception of External 

Automatic Entries that do not use a two-phase commit. 

$ If you use the Ispec Recall option on a Copy.From Ispec that is processing the last 

Copy.From line (when the value of GLB.COPY equals the value of GLB.MAXCOPY), 

the Ispec is not recalled and the abort message is displayed on the Copy.From screen. 

In all other cases, the Ispec is recalled, and the ABORT message is displayed on that 

screen. 

$ Any changes you have made to GLB.WORK before the ABORT; will not be saved. The 

contents of GLB.WORK will be rolled back to the value it had at the start of the 

transaction. 

1-6 v

ABORT 

$ If a specified Ispec is recalled, its updates are performed, even though the calling Ispec 

was rolled back. 

$ When a value is moved to GLB.PARAM before an ABORT; command is issued, the 

value is passed to the Ispec. 

Using the ABORT; Command in Reports 

Syntax 

Note the following points when using the ABORT; command in Reports. 

$ Reports are rolled back to the last commit point; for example, a Critical Point or 

SLEEP; command. Updates up to the last commit point will remain, regardless of the 

method of Report initiation. 

$ After the Report is aborted and rolled back, it is your responsibility to restart it. 

$ If extended Report recovery is in operation, the recovery records will be retained in 

the database. 

DDD DDBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDD4 

3 3 

@D DBDDDDDDDDDDDDDBY 

3 3 

@DDD DDDY 

message 

A data item or literal containing a message of up to 50 characters. 

ispec 

Examples 

A data item or literal containing the name of an Ispec to be recalled. This feature is only 

available in Ispec logic. 

 

 

 

 

 

 

In this example, when ERROR1 has the value YES, the transaction is aborted and the 

message Error 1 encountered is displayed. 

v 1-7

ABORT 

References 

When ERROR2 has the value YES, the transaction is aborted and the Ispec ERRS is 

recalled. The default message is displayed. 

Note: In the second example indicating the default message, the first set of 

parentheses is required, with at least one space inside. 

Use of this command with OLTP is described in your LINC Generate Operations Guide. 

1-8 v

ACCEPT (AX) 

Syntax 

ACCEPT (AX) 

The ACCEPT; command enables you to pass information to a running Report from the 

terminal that initiated the Report. ACCEPT; commands are usually preceded by an 

associated MESSAGE; command that prompts for input. 

When an ACCEPT; command is encountered, the Report suspends execution until it 

receives a reply input from the terminal. 

Kanji characters must be entered in Kanji (EDIT; K) fields. If you enter an invalid Kanji 

character, GLB.STATUS is set to five asterisks (*****). If you move a mixed alphanumeric 

and Hankaku-Katakana value into an EDIT; W data item, the value is moved character by 

character, and is truncated to the length of the data item. However, if you move a mixed 

alphanumeric and Hankaku-Katakana value into an EDIT; A data item, the value is moved 

byte by byte and is truncated to the length of the data item. If the truncation occurs after 

the first byte of a double-byte Hankaku-Katakana character, this will result in an invalid 

character. 

Note: EDIT; W data items are not implemented in LDA. 

For full details of LINC Report operations, see your LINC Administration and Operations 

Guide for your target host type. 

DDDD DDD DDDDDDDDDDDDDDDDDDDDDDDDDD4 

DDDD DDD DDD DD DDDDDDDD 

DDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDD4 

3 3 

@DD DDY 

Note: For LDA only the first form is valid. A syntax error occurs if you use the 

second form of the ACCEPT; command in LDA. 

data item 1 

An existing Setup Data item, Global Setup Data item, or Report Data item that will receive 

the input. 

data item 2 

A Setup Data item created by the ACCEPT; command to receive the input. 

edit characteristics 

Edit attributes and settings for data item 2. 

Edit characteristics are not permitted for a previously defined data item. 

v 1-9

ACCEPT (AX) 

Examples 


The following logic will accept and validate a date. If a valid date is entered, the loop is 

ended by the BREAK; command, and the remaining logic is performed. If the date is not 

valid, another entry is requested. 

 

 

 

 

 

 

 

 

The following logic illustrates the use of the ACCEPT; command for a numeric value with 

decimals. 

 

 

An input of 12345 means that RUNQTY would have the value 123.45. If a value of 7.63 was 

required, 00763 would need to be entered. 

The following logic could be used as an alternative. 

 

 

 

The logic ACCEPT; CUST.NO would not be valid (since Ispec data items may not be used). 

"LENGTH (LE)" in your LINC Generate Reference Manual: Painter and Editor. 

‘‘MESSAGE (ME)’’. 

"Types of Data Item" in your LINC Generate Operations Guide. 

1-10 v

ACCESS.EXT (AEXT) 

Syntax 

Note: This command is valid for MCP based LINC Systems only. 


The ACCESS.EXT; command enables an MCP based LINC System user to inquire on a 

different DMS II database. One or two databases may be named on the Environmental 

Options screen for each generate set. The labels DB1 and DB2 are used to access these 

databases through the ACCESS.EXT; command. 

Two options are available: Find and Get. The Find option is used to access a data set, 

locate and read a particular record. The Get option moves a value from a record accessed 

by the Find option into a data item. This value can then be manipulated by LINC logic. 

The System Data item GLB.STATUS is set to ***** if an exception occurs. The System Data 

items GLB.EXNAME and GLB.EXTEXT provide information about the reason for the 

exception. See your A Series DMS II Interpretive Interfaces for a description of the 

exception messages that may be used. 

The DMS II Interpreter program DMINTERPRETER/database must have been generated 

for the required database. It is your responsibility to ensure that this program matches the 

current version of your LINC Specification. It is also your responsibility to ensure 

compatibility between the parameters of the ACCESS.EXT; command and the structure of 

the database. 

Notes: 

$ The access provided by the ACCESS.EXT; command requires more system resources 

than a normal LINC database access. 

$ The data names used must be the names as declared in the DASDL source. 

$ You can use the ACCESS.EXT; command to access another LINC database (since 

LINC generates DMS II databases), but using external Automatic Entries (AUTO; 

commands) is the recommended method. 

DD DBDD DDBDDDBDD DDBD4 

3 3 3 3 

@DD DDY @DD DDDY 

find statement 

The command required to locate and read a record from the database. The data in the 

record is not directly available to LINC commands. This command has the following 

syntax. 

DD DDDDDDDDDDD DDDDDDDDDDDDDDDDDDD4 

v 1-11


The find literal parameter is a data item or a literal not exceeding 150 characters (anything 

longer than 150 characters, inclusive of both parameter string and text, will be truncated) 

that contains a valid DMINTERPRETER DBVERB Search command and has the following 

syntax. 

DDBDDDDDDDDDBDBDDDD DDDBDBDDDDDDDDDDDDDDBDDD4 

3 33 33 3 

CD D4 CDDDD DDD4CD D4 

3 33 33 3 

CD DD4 @DDDD DDDDDDY@DDDD DDDDY 

3 3 

CD DD4 

3 3 

@D DY 

The semantics of the Find literal command are described in the A Series DMS II 

Interpretive Interfaces. 

get statement 

The command required to access a data item in a database record previously read using a 

find statement, and to move its value into a LINC data item. This command has the 

following syntax. 

DD DDDDDD DDDDDD DDDDDD4 

The get literal parameter is a data item or literal, not exceeding 150 characters, that 

contains a value describing the database item to be accessed, and has the following syntax. 

DB BDBD DDBDBDDDDDDDDDDDDDBD4 

3 33 33 3 

@ Y3 3@ Y 

CD DDDDDDD4 

3 3 

CD DDDDDD4 

3 3 

CD DDDDDDDD4 

3 3 

CD DDDDDDD4 

3 3 

CD DDDDDDD4 

3 3 

@D DY 

The items are DMS II data items. Currently, a DMS II BOOLEAN data item may not be 

accessed. Note that alphabetic item, group item, number item, real item, field item, 

count item, andrecord type item are all data names that must be defined within the target 

database. 

The DASDL data items required for ACCESS.EXT; command access to a LINC Database 

are not necessarily the same as the item names painted on the screen; they may be prefixed 

by the Ispec name. See the appropriate system DASDL for the correct name. 

For access to a LINC database Ispec containing Memo Data, use the form: 

 

1-12 v

Examples 

For example, for an Ispec called ISP1 containing Memo Data, use: 

 

data item 


A LINC data item that is to receive the specified database item value. The edit type of this 

item must be the same type as the source item in the DMS II database (alphanumeric or 

numeric). 

subscript 

Where a data item is defined as part of a table in a DMS II structure, the subscript value 

must be specified. Note that the subscript must be enclosed within square brackets, as 

shown in the following example. 

 

Example 1 

The branch name for a customer is recorded in an existing DMS II database, and is 

required for validation in the LINC System. 

The database DB1 is expected to contain a dataset CUST, which contains at least 

CUSNAME and BRCHNAME data items. The CUST record for the required CUSTOMER is 

located and read. The GET command moves the BRCHNAME value to the LINC data item 

SDBRANCH, where it can be used by other commands. 

 

 

 

 

 

 

 

 

Note: In the database, a Component data item has the name ispec-line name, andan 

Event has the name line name. 

v 1-13


Reference 

Example 2 

The DB2 database is expected to contain a dataset GOODPRINTERS, containing at least 

the DASDL data item PRINTER-NAME. The first record in GOODPRINTERS is located and 

read. The GET command moves the value of the first record in the DASDL data item 

PRINTER-NAME to SD-PRINTER for later processing. 

 

 

 

 

 

‘‘GLB.EXNAME’’ and ‘‘GLB.EXTEXT’’. 

1-14 v

ADD (AD) 

Syntax 

Examples 


ADD (AD) 

The ADD; command adds the value of a numeric data item or constant to that of a second 

numeric data item and stores the result; either in the second data item, or (optionally) in a 

third specified data item. 

The GIVING; and ROUNDED; command options can be applied in conjunction with the 

ADD; command. The System Data item GLB.STATUS is not accessed by the ADD; 

command. Use the GLB.STATUS; command to test for arithmetic overflow. 

DDD DBD DBD DDDD 

3 3 

@DDDD DDDDY 

DDBDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDDBDDDDDDDDDDDDBDD4 

3 3 3 3 

@D DD DY @D DY 

GIVING; numeric data 3 

The GIVING; command option directs the result to the specified data item. The GIVING; 

command option must be on the same line as the ADD; command. GIV is a valid 

abbreviation for GIVING. 

ROUNDED; 

The ROUNDED; command option rounds the result when truncation occurs. ROU is a 

valid abbreviation for ROUNDED. 

 

 

 

 

‘‘GLB.STATUS’’ for directing the value of GLB.STATUS to a data item. 

v 1-15

ADHOC.MODE (ADHOC) 

ADHOC.MODE (ADHOC) 

Syntax 

The ADHOC.MODE; command enables the LINC Ad Hoc Inquiry Utility to be accessed 

from Ispec logic. All following logic in the Ispec is ignored and will not be executed. 

If an Ispec name is included with the ADHOC.MODE; command, Pre-Screen logic for that 

Ispec is invoked when LINC Ad Hoc Inquiry is terminated. If no Ispec is included, 

Pre-Screen logic for the calling Ispec is invoked. 

Note: OS 2200 based LINC Systems do not support LINC Ad Hoc Inquiry. When this 

command is executed on OS 2200 based LINC Systems, Pre-Screen logic is 

invoked for the specified Ispec (which defaults to the calling Ispec). 

A command may also be included if an Ispec name is specified. This command is actioned 

by LINC Ad Hoc Inquiry as an Action field command. For more details, see your LINC Ad 

Hoc Inquiry Operations Guide. 

This command is not available with OLTP. 

In LDA Run Time, this command recalls either the named or current Ispec. 

DDD DDBDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDD4 

3 3 

@D DDBDDDDDDDDDDDDD4 

3 3 

@DD DDY 

Here: 


$ ispec is a data item or literal containing the name of an Ispec. 

$ command is a data item or literal containing a command to be interpreted by LINC Ad 

Hoc Inquiry. 

For more details, see your LINC Ad Hoc Inquiry Operations Guide. 

1-16 v

ADVANCE (AV) 

ADVANCE (AV) 

The ADVANCE; command is used in Reports or Shadow Reports to advance a specified 

number of lines between Frames, or to advance to a new page. If a Shadow Report is 

specified, only that Shadow Report is affected by the ADVANCE; command. 

Which using Report Output Control (ROC) Reports, or non-ROC MCP based TP Reports, 

an ADVANCE; NEW.PAGE command is ignored if no Report output has been produced, 

since all Reports start at top-of-page. Page headings resulting from an ADVANCE; 

command are not produced until further output is produced. This has two implications: 

headings can be changed after an ADVANCE; command (but before output) and Reports 

will not produce a final page containing only headings. 

For MCP based non-ROC Reports that output to LP or RP, the ADVANCE; NEW.PAGE 

command produces footers, a new page, and headings whenever it is executed. 

ADVANCE; CHANNEL Variant 

Syntax 

Note: This variant is not valid on OS 2200 based LINC Systems, and is ignored in 

LDA Run Time. 

For UNIX and MCP based LINC Systems, the ADVANCE; CHANNEL command variant can 

be used for Reports directed to an LP device. It is intended for printing on special 

stationery. 

For Reports directed to TP devices, (or RP devices in MCP based LINC Systems), 

ADVANCE; CHANNEL 1 causes an advance to end-of-page, and any other channel causes 

an advance of one line. If end-of-page is passed, the System Data item GLB.PAGECOUNT 

is not incremented and no headings are printed. The System Data item GLB.LINECOUNT is 

incremented by one. 

For a UNIX LINC System, the shell variable COBLPFORM must be set for the ADVANCE; 

CHANNEL command to have the desired effect. For Standard ROC Reports, the 

COBLPFORM variable must be set when you initiate the ROC Output Report, not when the 

Report is run. For Direct Reports, the COBLPFORM variable must be set when the Report 

is run. For more details, see the Micro Focus COBOL for UNIX COBOL System Reference. 

DD DDDBDDDDDDDD DDDDDDDBDDDDDDDDDD 

3 3 

CDDDDDD DDDDDD4 

3 3 

@DDD DD DDY 

DDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDD4 

3 3 

@DD DD DDY 

v 1-17

ADVANCE (AV) 

Examples 


numeric data 

The number of lines to advance: this can be specified as a numeric data item or an integer 

value (with or without enclosing parentheses). 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

‘‘GLB.LINECOUNT’’, ‘‘GLB.FORMDEPTH’’, and ‘‘GLB.PAGECOUNT’’. 

ASCENDING 

For information on the ASCENDING; command option, see either the MATCH; or SORT; 

command later in this section, as relevant. 

1-18 v

ATTACH (ATT) and ATTACH&SPACE (ATS) 


The ATTACH; command appends the first data item to the second data item after the last 

non-space character, and then stores the result in the second data item. Embedded blanks 

in either data item are retained. 

When the ATTACH&SPACE; command is used, a space is inserted between the two data 

values when they are joined. However, if the second item has the same value as 

GLB.SPACES, the result is the first data item (with no leading spaces, unless the first data 

item contained leading spaces). 

Truncation of Data 

With the ATTACH; and ATTACH&SPACE; commands, the System Data item GLB.LENGTH 

is set to the untruncated length of the result, ignoring trailing spaces. 

The second data item must have a length that is large enough to contain the resulting data, 

otherwise truncation will occur. If truncation occurs, the truncated data is returned in the 

destination data item, GLB.LENGTH is set to the untruncated length, and no error message 

is given. 

For UNIX and MCP based LINC Systems, the maximum length of an item created with the 

ATTACH; and ATTACH&SPACE; commands is 2000 characters. (This is equivalent to 1000 

Kanji (EDIT; K) characters.) 

On OS 2200 based LINC Systems, the maximum length of the item you are joining (the first 

data item) is 2000 characters. If you attempt to join a longer item, its value is truncated to 

2000 characters before being joined. The second data item and the result may be any length. 

If you move a mixed alphanumeric and Hankaku-Katakana value into an EDIT; W data 

item, the value is moved character by character, and is truncated to the length of the 

data item. However, if you move a mixed alphanumeric and Hankaku-Katakana value into 

an EDIT; A data item, the value is moved byte by byte and is truncated to the length of the 

data item. If the truncation occurs after the first byte of a double-byte Hankaku-Katakana 

character, this will result in an invalid character. 

Notes: 

$ EDIT; W data items are not implemented in LDA. 

$ For an MCP based LINC System, when numeric data items containing separators 

are used with ATTACH; or ATTACH&SPACE; commands, the effective length of the 

data item will include separators. For example, a numeric data item with attributes 

LE; 5 SP; (,) will have an effective length of 6, with an included leading zero. 

For LDA there is no upper limit on the size of the item created. 

v 1-19


Syntax 

Examples 

DBDDD DDDDDBDD DDD DD4 

3 3 

@D DY 

data name 1 

If this data item is numeric, it may not have decimals declared. Sign and separators are 

ignored when the value is attached. A literal or constant value may be used instead of a 

data item. 

data name 2 

An alphanumeric data item. 

 

 

 

 

 

 

The following table shows the results of the above use of the ATTACH; and 

ATTACH&SPACE; commands, and the resultant GLB.LENGTH values. 

Data Item Data item Value GLB.LENGTH 

FIRSTNAME HENRYWILLIAMS 13 

SECONDNAME SUSAN ANNE DE LEON 18 

SURNAME WILLIAMSHE 13 

Notice that the value of GLB.LENGTH is 13 for SURNAME, even though the actual length 

is 10. This indicates that truncation has occurred. 

1-20 v

ATTRIBUTE (ATTR) 


Use this command for MCP based LINC Systems to define the printer backup file names 

for your Report output. The command is available for ROC Direct Reports and non-ROC 

Reports directed to LP or RP devices. 

Note: The printer backup file name is set when the file is opened. The ATTRIBUTE; 

command must therefore be executed before a print file is opened. 

Purpose of ATTRIBUTE; command 

Errors 

About printer backup files 

Printer backup files created by LINC Reports are named: 

 

In this name: 

$ usercode is the usercode of the file 

$ bdname is a prefix for the file name 

$ mix is the seven-digit mix number of the Report 

$ counttitle consists of count, a three-digit number, and title, the title of the file 

Using the ATTRIBUTE; command 

The ATTRIBUTE; command enables you to define the BDNAME attribute - the 

(usercode)bdname portion of this name - in similar fashion to the LINC System command 

:BDD. 

By default, the BDNAME attribute is LINCBD, although this may have been changed by 

using the LINC System command :BDD. For standalone Reports, the default value is a 

period (.), which means the system default *BD is used. 

If the command cannot set the BDNAME attribute (for example, the syntax is not correct), 

the attribute is unchanged. The System Data item GLB.STATUS is not set by this 

command. You can include the GLB.STATUS; command if you wish to test the success of 

the command. 

There is no recovery of the BDNAME attribute. It is your responsibility to ensure that your 

change is saved and recovered. 

If your Report is not running under a privileged usercode, exceeding the limit (180 

characters) or creating an invalid file name (for example, of more than 14 levels) will result 

in your Report terminating with a fatal error. 

v 1-21


Syntax 

Examples 

DD DD DD DDBDDDDDDDDDDDDBDD4 

3 3 

@D DY 

bdname 

Data item, Setup Data item, Global Setup Data item, or literal that holds the BDNAME 

attribute. Non-literal values must be terminated with a period (.). This is illustrated in the 

examples of this command. 

The maximum length of the BDNAME is 180 characters. For a literal , the maximum length 

is 58 characters (56 characters if a usercode is supplied). 

usercode 

Literal that contains a usercode. If omitted, the file is produced with the same usercode 

with which the Report is running. The Report program must be privileged, or running 

under a privileged usercode, in order to produce a file under a different usercode 

(otherwise, the Report will terminate). 

The usercode parameter can only be included if bdname is entered as a literal. If you 

include bdname as a data item, you must include the usercode (complete with 

parentheses) in the value of bdname, if required. 

The following command sets BDNAME to *BD. This is equivalent to the LINC System 

command :BDD. (See your MCP Based LINC Administration and Operations Guide for 

details). 

 

The following command sets BDNAME to PRINT/FILE/FOR/BILLING. 

 

The following command sets BDNAME to (USER1)LOCALPRINT. 

 

The following command sets BDNAME to REPORT/PRINTOUT. 

 

 

1-22 v

AUTO (AU) and AUTO.ARRAY (AUA) 


The AUTO; command transfers the value of a data item to a data item in the Auto Entry 

buffer. Data items in the Auto Entry buffer must be contained in the Ispec specified by the 

associated AUTO.ENTRY; command. 

The AUTO.ARRAY; command transfers a Setup Data array or Global Setup Data array to 

the Auto Entry buffer. Otherwise, it functions as the AUTO; command does for a data item. 

The receiving item must be of sufficient size to store the array, and it must be 

alphanumeric. 

Rejection of data transfer 

A transfer using the AUTO; or AUTO.ARRAY; commands to an Event or a Memo 

Component is always valid, although the transfer may be rejected if it involves Profiles that 

do not allow duplicates. A transfer to a Standard, Table,orMultiple Ordinate Memo 

Component is rejected in the following cases: 

$ Where the value of MAINT is GLB.ADD and the record already exists 

$ Where the value of MAINT is GLB.CHG or GLB.DEL, and the record does not exist 

If an AUTO; command fails during Ispec logic execution, GLB.STATUS is set to *****. 

Transferring Values Using AUTO; and AUTO.ARRAY; Commands 

When transferring values using AUTO; and AUTO.ARRAY; commands: 

$ Do not transfer an alphanumeric value to an unsigned numeric data item with decimals 

(or vice versa). 

$ Do not transfer an alphanumeric value to a signed numeric data item (or vice versa). 

$ Do not transfer signed numerics if you are performing a transfer between different 

host types. The recommended method for transferring a signed field between systems 

on different host types is to have a separate field for the sign, and simply transfer the 

positive numeric. 

$ Perform the transfer of data explicitly for each data item required, including a value for 

the MAINT System Data item where appropriate. Use GLB.ADD, GLB.CHG, and 

GLB.DEL for the MAINT System Data item. FIR, LAS, BAC and NEX are also valid for 

external Automatic Entries. 

$ For new records, any data items not included in AUTO; commands are sent a zero or 

space value as appropriate. 

$ For records being changed, any items not included in AUTO; commands retain their 

existing values, unless CLW; (0) or CLW; ( ) are defined for those items. 

$ Use the AUTO.CLEAR; command to clear the value of a data item. However, if the 

CLEAR.WHEN; character is a space (or zero for a numeric item), the value will be set 

to spaces (or zero). 

v 1-23


Syntax 

$ Numeric Setup Data arrays and signed numeric data items will be corrupted if they are 

passed in an external Automatic Entry to a host with a different character set; that is, 

between EBCDIC (MCP environment) and ASCII (UNIX or OS 2200 environments). 

$ For an external Automatic Entry to an OLTP View Ispec using OLTP, an AUTO.ARRAY 

of a numeric Setup Data array moves the individual numeric array elements to the 

corresponding element in the OLTP View Ispec buffer. 

$ You cannot use Usage Inquiry data items in conjunction with the AUTO; command for 

OLTP. 

$ External Automatic Entries are not supported in LDA Run Time. 

Hankaku-Katakana values 








Numeric Setup Data arrays 

Numeric Setup Data arrays are stored in COMP (BCD, for MCP based LINC Systems) data 

format. This is different from the way in which alphanumeric Setup Data arrays are stored 

(alphanumeric values). 

Calculate the required size for the receiving item to store an incoming numeric array as 

follows: 

1. Allow one byte for every two numeric digits. 

2. Plus one half byte for each array element, rounded up to the nearest byte. 

For example: An array with ten elements, each three digits in length, would be calculated 

as follows: ((10 * 3) / 2 + (0.5 * 10)) = 20. 

Notes: 

$ Numeric Setup Data arrays will be corrupted if passed in an external Automatic 

Entry to a host with a different character set, that is, between EBCDIC (MCP based 

LINC Systems) and ASCII (UNIX or OS 2200 based LINC Systems). 

$ Signed numeric items will be corrupted if passed in an external Automatic Entry to 

a host with a different character set, that is, between EBCDIC (MCP based LINC 

Systems) and ASCII (UNIX or OS 2200 based LINC Systems). 

1-24 v

Example 

DD DDDDDD DDDDDD DDDDD4 

DD DDDD DDDD DDD4 

data item 1 

This item may be a literal or a data item. 

data item 2 

Thisitemmayonlybeadataitem(notaliteral). 

data item 3 

A Setup or Global Setup Data array. 

data item 4 

An alphanumeric data item in the receiving Ispec. 


The following example shows Report logic that reads a customer’s bank balance and 

creates an automatic interest entry. It also makes an Automatic Entry in an external 

database, under a given condition. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

v 1-25



In the following example, a Setup Data array is transferred to a data item in the FIRUP 

Ispec. 

 

 

 

 

 

 

‘‘AUTO.CLEAR (AC)’’ for clearing the value of a data item. 

‘‘AUTO.ENTRY (AE)’’ for defining the Ispec. 

‘‘AUTO; WRITE and AUTO; WRITE&CLEAR’’ for transferring the data and for a description 

of the setting of GLB.STATUS. 

‘‘MOVE.AUTO (MA) and MOVE.AUTO.ARRAY (MAA)’’ for retrieving data from the auto 

entry buffer. 

‘‘CONTRA (CN)’’ for changing the sign of a data item in the Auto Entry buffer. 

"AUTO" in your LINC Generate Reference Manual: Painter and Editor, which allows fast 

entry of logic for the AUTO; command. 

The System Data Items ‘‘GLB.SELF’’, ‘‘GLB.DESTINATION’’, ‘‘GLB.DESTENV’’, 

‘‘GLB.DESTHOST’’, ‘‘GLB.HUBSTATUS’’, ‘‘GLB.HUBTIMEOUT’’, ‘‘GLB.OLTPTYPE’’, 

‘‘GLB.OLTPSUBTYPE’’, ‘‘GLB.OLTPSERVICE’’, and ‘‘GLB.OLTPVALUE’’. 

"External Automatic Entries" in your LINC Generate Operations Guide. 

The "Interfaces" section, in your LINC Administration and Operations Guide for your 

host type. 

1-26 v

AUTO; CONTRA 

Syntax 

Examples 


AUTO; CONTRA 

The AUTO; CONTRA command changes the sign of a signed numeric data item that has 

been moved into the Auto Entry buffer. 

DDDD DDD DDDDD DDDDDDDDDD4 

 

 

 

 

 

‘‘AUTO; CONTRA’’ and ‘‘AUTO; WRITE and AUTO; WRITE&CLEAR’’. In particular, see 

‘‘Examples’’. 

v 1-27

AUTO.CLEAR (AC) 

AUTO.CLEAR (AC) 

Syntax 

Example 


The AUTO.CLEAR; command clears the value of the data item in the Auto Entry buffer. 

Numeric data items are set to zero, alphanumeric items to spaces. 

Using this command means you do not need to allow for data items that have the 

CLEAR.WHEN; Data Attribute. 

DDDD DDDDDD DDDDDDDDDDDDDDDDD4 

In the following example, the customer balance is being cleared from the CUST 

Component. 

 

 

 

 

 

 

In the following example, data is being sent from an Event named RECPT to an Event 

named AJNL in the same LINC System. In this example, the data item AMOUNT is set to 

zero. 

 

 

 

 

‘‘AUTO; CONTRA’’. 

"CLEAR.WHEN (CLW)" in your LINC Generate Reference Manual: Painter and Editor. 

1-28 v

AUTO.ENTRY (AE) 


The AUTO.ENTRY; command identifies the name of the Component or Event to which 

data is to be sent by an Automatic Entry. This in turn determines the format of the Auto 

Entry buffer to which data is to be sent by the AUTO; and AUTO.ARRAY; logic commands. 

Data items not given a value explicitly (with an AUTO; command) are sent a value of 

spaces (or zero for a numeric item). When changing an existing record, this is usually 

interpreted as indicating no change to the existing record. However, if the CLEAR.WHEN; 

character is a space (or zero for a numeric item), the value will be set to space (or zero). 

Restrictions on the Ispec 

The AUTO.ENTRY; command can only be used if the receiving Ispec is defined as one of 

the following: 

$ An Automatic Entry Ispec (by setting the Automatic Entry field on its Component or 

Event Options screen to Y). 

$ An External-only Ispec (by setting the External Only Ispec field on its Component or 

Event Options screen to Y). 

$ An OLTP View Ispec (by using the OVI choice from the LINC Definition Menu screen). 

External Automatic Entries 

For an external Automatic Entry (from one LINC System to another), the Ispec must be 

identical to an Ispec in the receiving LINC System. 

You can also use external Automatic Entries to interface to a non-LINC system, using the 

NOF or LINC USER interface methods. For more details, see your LINC Generate 

Operations Guide. 

Multiple AUTO.ENTRY; Commands 

The Ispec used in an AUTO; WRITE command is the Ispec specified in the most recent 

AUTO.ENTRY; command in the logic prior to the AUTO; WRITE; command, regardless of 

any conditional commands such as the DO.WHEN; or BEGIN.CASE; command. 

Ispec Locking on OS 2200 based LINC Systems 

On OS 2200 based LINC Systems, AUTO.ENTRY; applies an implicit RDMS lock. 

Attempting to explicitly lock the same Ispec later in the same transaction (for example, 

with a LOOK.UP; command with a SECURE; command option) can result in an RDMS 

error. 

OLTP 

In an OLTP environment, the AUTO.ENTRY; command sets GLB.OLTPTYPE, and also sets 

GLB.OLTPSUBTYPE if the specified Ispec is an OLTP View Ispec. 

v 1-29


Syntax 

Examples 

DDD DDDD DDDBDDDDDDDDDDDDDBDDD4 

3 3 

@D DY 

EXTERNAL; 

If this command option is included, the System Data items GLB.DESTINATION, 

GLB.DESTENV and GLB.DESTHOST are checked at runtime to see if an external 

Automatic Entry is to be initiated. If not, GLB.STATUS is set to NOEXT when the AUTO; 

WRITE command is executed. See the AUTO; WRITE command for further details. (Note 

that GLB.HUBSTATUS does not have a value set to it in this situation.) 

An external Automatic Entry is initiated when one or more of the following conditions is 

false: 

$ GLB.DESTINATION is equal to GLB.SELF 

$ GLB.DESTHOST is equal to GLB.SELFHOST 

$ GLB.DESTENV is equal to GLB.SELFENV 

If the Automatic Entry is to an Ispec defined as an External-only Ispec on its Ispec Options 

screen, the EXTERNAL; command option is mandatory. If EXTERNAL; is not specified, no 

error will be generated if the user attempts an Automatic Entry to another LINC System. 

Note: The EXTERNAL; command option is ignored in LDA Run Time. 

On OS 2200 based LINC Systems, automatic date/time validation is not 

performed by Reports for External-only Ispecs. 

In the following example, data is being sent from an Event named RECPT to an Event 

named AJNL in the same LINC System. 

 

 

 

 

In the following example, data is being sent from LINC System A to LINC System B. 

 

 

 

 

 

 

 

 

1-30 v


 

 

 

‘‘AUTO; CONTRA’’, ‘‘AUTO.FORMAT (AF)’’, and ‘‘AUTO; WRITE and AUTO; 

WRITE&CLEAR’’. 


‘‘GLB.DESTINATION’’, ‘‘GLB.DESTENV’’, ‘‘GLB.DESTHOST’’, ‘‘GLB.HUBSTATUS’’, 

‘‘GLB.HUBTIMEOUT’’, ‘‘GLB.OLTPTYPE’’, ‘‘GLB.OLTPSUBTYPE’’, ‘‘GLB.OLTPSERVICE’’, 

and ‘‘GLB.OLTPVALUE’’ 


"Using LINC Logic for OLTP" in your LINC Generate Operations Guide. 

The Interfaces section in your LINC Administration and Operations Guide. 

v 1-31

AUTO.FORMAT (AF) 

AUTO.FORMAT (AF) 

Syntax 


The AUTO.FORMAT; command is specific to OLTP. 

Use this command to nominate an Ispec whose data items match the data layout of the 

OLTP response in the Auto Entry buffer. This enables the reply buffer to have a format 

different from the AUTO; request. 

After you have defined the format of the Auto Entry buffer, you can extract data from it by 

using MOVE.AUTO; or MOVE.AUTO.ARRAY; commands that must immediately follow the 

relevant AUTO.FORMAT; command. 

The AUTO.FORMAT; command does not clear the Auto Entry buffer. 

DD DDD DDDDDDDDDDDDDDDDDDDDDDDDDDD4 

"Using LINC Logic for OLTP" in your LINC Generate Operations Guide. 

‘‘MOVE.AUTO (MA) and MOVE.AUTO.ARRAY (MAA)’’ later in this section. 

1-32 v

AUTO; WRITE and AUTO; WRITE&CLEAR 


The AUTO; WRITE command transfers information from the Auto Entry buffer to the 

destination (receiving) Ispec or buffer, depending on whether it is an internal or external 

Automatic Entry. Internal Automatic Entries transfer data within the same LINC Database. 

External Automatic Entries transfer data to an external LINC System (which can be on a 

different host). 

The AUTO; WRITE (and AUTO.WRITE&CLEAR) command can be used more than once in 

the same Ispec or Report logic. A record is transferred each time a command is executed. 

GLB.ERROR and GLB.STATUS 

Updating is not completed if GLB.ERROR has a value other than GLB.SPACES. Changes to 

GLB.ERROR after the AUTO; WRITE is executed have no effect on the current Automatic 

Entry. 

For Automatic Entries, GLB.STATUS is set at the time the AUTO.WRITE; command is 

executed. The setting of GLB.STATUS is discussed under ‘‘Settings of GLB.STATUS and 

GLB.HUBSTATUS’’, later in this command subsection. 

Event Data Items 

In an Automatic Entry to an Event, the System Data items ACTMTH, INPUT-DATE, and 

ISPEC are handled automatically. 

Differences between AUTO; WRITE and AUTO; WRITE&CLEAR 

There are some differences with the way the AUTO; WRITE and AUTO; WRITE&CLEAR 

commands work, depending on whether you are transferring data internally, to an external 

LINC System, or to another system through OLTP. These differences are described in the 

following subsections. 

Internal Automatic Entries 

For internal Automatic Entries, the AUTO; WRITE command transfers information from 

the Auto Entry buffer to the database structure of the destination (receiving) Ispec. A 

record is sent to the LINC database each time an AUTO; WRITE command is executed. 

Any record currently in memory for the destination Ispec is overwritten by the Auto Entry 

buffer record prior to its storage in the LINC database. On completion of a successful 

Automatic Entry, the current database record will be the one just created. 

Requirements 

The destination Ispec must have the Automatic Entry field set to Y on the Ispec Options 

screen for the LINC Specification of the LINC System that is performing the AUTO; WRITE 

command. This field enables the Ispec to receive Automatic Entries. 

v 1-33


Rejecting an Automatic Entry 

A transfer to a Standard or Table Component will be rejected in the following cases: 

$ Where the value of MAINT is the same as GLB.ADD, and the record already exists 

$ Where the value of MAINT is the same as GLB.CHG or GLB.DEL, and the record does 

not exist 

AUTO; WRITE&CLEAR 

The AUTO; WRITE&CLEAR command performs the additional function of clearing the 

Automatic Entry buffer. 

Caution (MCP based LINC Systems only) 

If an AUTO; WRITE or AUTO; WRITE&CLEAR command creates a duplicate record 

on a Profile defined with Duplicates Allowed set to N, the write will fail and the 

transaction will be aborted. 


For External Automatic Entries the AUTO; WRITE command transfers information from 

the Auto Entry buffer of the sending Ispec, to the input buffer of the destination Ispec in 

the external LINC System. 

Requirements 

The destination Ispec must have the Automatic Entry field set to Y on the Ispec Options 

screen for the LINC Specification of the LINC System that is performing the AUTO; WRITE 

command. This enables the information for the destination Ispec to be assembled 

correctly. 

The LINC Specification of the sending and destination Ispecs must be identical. 

AUTO; WRITE&CLEAR 

The AUTO; WRITE&CLEAR command will only clear the Auto Entry buffer if no data is 

returned to the buffer, in which case it will clear the buffer regardless of the setting of 

GLB.ERROR. If data is returned, the action is identical to an AUTO; WRITE command. 

External Automatic Entries are not supported in LDA Run Time. 

OLTP Automatic Entry 

As for any external Automatic Entry, use the AUTO; WRITE and AUTO; WRITE&CLEAR 

commands to send an OLTP transaction containing data you have set up in the Auto Entry 

buffer. 

1-34 v

Procedure 

To send an OLTP transaction: 


1. Nominate an External Auto Ispec or an OLTP View Ispec with the AUTO.ENTRY; 

command (GLB.OLTPTYPE and GLB.OLTPSUBTYPE are set automatically for OLTP 

View Ispecs). 

2. Set GLB.DESTHOST to GLB.OLTP. 

3. Set GLB.DESTINATION to the OLTP Service you require. 

4. Set GLB.OLTPSUBTYPE (if it is not an OLTP View Ispec) to the value required by the 

OLTP Service specified. For a LINC Service, this will be as follows. 

$ For UNIX and OS 2200 based LINC Systems: 

 

$ For MCP based LINC Systems: 

 

The values entered in ispec, system, andwindow refer to the destination LINC 

System. 

5. Use AUTO; logic commands to prepare the data items in the message. 

6. Use the AUTO; WRITE logic command to send the message. 

Results 

If GLB.DESTHOST does not specify an OLTP transaction but your AUTO.ENTRY 

command specified an OLTP View Ispec, a runtime error occurs, GLB.STATUS is set to 

five asterisks (*****), and GLB.HUBSTATUS is set to an appropriate error message. 

If the OLTP transaction is processed successfully, GLB.STATUS contains spaces or DATA. 

A DATA value indicates that there is a response message in the Auto Entry buffer . 

If the processing on the OLTP Server is aborted and the transaction is using Two-Phase 

commit, the client transaction will be immediately aborted (for more details, see the 

ABORT; command). 

If any other processing or OLTP exception is encountered, your LINC logic execution will 

continue after the AUTO; WRITE command. Note the following points regarding these 

exceptions: 

$ GLB.STATUS will be set to five asterisks (*****), and GLB.HUBSTATUS will contain 

the error code. GLB.STATUS and GLB.HUBSTATUS settings are described later in this 

subsection. 

$ The buffer is not changed by the AUTO; WRITE command. The buffer is cleared to 

spaces by the AUTO; WRITE&CLEAR command. 

v 1-35


Syntax 

Examples 

DDDDD DDDDDDBDDDDD DDDDDBDDDDDDDDDDDDDDDDDDDD4 

3 3 

@DD DDY 

The following example adds a record for the component CUST to the database. 

 

 

 

 

 

 

 

In the following example, a Component PROD, designated AUTO.ENTRY, has an Ordinate 

PRODUCT (with a length of 10), and a numeric data item SELLPRICE (with Data 

Attributes LENGTH; 8 and DECIMALS; 2). PROD resides in the LINC System DBASE1 and 

has the following logic. 

 

 

 

 

PROD is defined identically in the LINC System DBASE2. 

In the following example, DBASE2 has an Ispec which is used for product maintenance 

and inquiry against DBASE1. It has a data item IN-MAINT (with a length of 3), a data item 

FINDPROD (length 10), and a data item SELLPRICE (as defined in DBASE1). 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1-36 v

Settings of GLB.STATUS and GLB.HUBSTATUS 


The AUTO; WRITE command sets the System Data item GLB.STATUS. If GLB.ERROR is 

spaces, GLB.STATUS is cleared (set to spaces) before the command is executed. 

For an internal Automatic Entry, GLB.STATUS is set to five asterisks (*****) if an attempt 

is made to add a record with an existing Ordinate to a Component, or to change or delete a 

nonexistent record. Also, attempting to set the MAINT System Data item to FIR, LAS, 

NEX, or BAC sets GLB.STATUS to five asterisks. 

For an External Automatic Entry, GLB.STATUS can be set to one of a number of values, as 

shown in the following table. (These values are described in further detail in the following 

subsections. In some cases, you can use the System Data item GLB.HUBSTATUS to get 

more status information.) 

Value Description 

Spaces Automatic Entry successful 

BLOCK Transaction sent, no reply received 

BUSY Insufficient resources 

DATA Successful: data returned 

NODB Could not find external LINC System 

NOEXT Internal Automatic Entry attempted 

TOUT No response received within the time limit 

***** Error in external LINC System 

For an OLTP Automatic Entry, GLB.STATUS can be set to one of a number of values, as 

shown in the following table. (These values are described in further detail in the following 

subsections. In some cases, you can use the System Data item GLB.HUBSTATUS to get 

more status information.) 

v 1-37



Spaces Depends on value in GLB.HUBSTATUS 

DATA Successful: data returned to OLTP buffer 

NODB Value in GLB.DESTINATION not recognized as an 

OLTP service 

***** Error: see GLB.HUBSTATUS 

The values of GLB.STATUS are described in further detail in the following subsections. In 

some cases, you can use the System Data item GLB.HUBSTATUS to get more status 

information, as indicated. 

GLB.STATUS is spaces 

For non-OLTP Automatic Entries, this indicates a successful Automatic Entry. 

GLB.HUBSTATUS has the value OK. 

For OLTP, the following table shows the values of GLB.HUBSTATUS when GLB.STATUS 

is spaces. 

GLB.HUBSTATUS Meaning 

OK Transaction was successfully processed, and did not perform a 

RECALL; 

NO RESPONSE Transaction performed a RECALL; of an Ispec with no 

Pre-Screen logic 

GLB.STATUS is BLOCK 

An external Automatic Entry was sent to its destination, but the connection was lost 

before a response was received. This value can only occur with inter-host (non-OLTP) 

Automatic Entries. (This status will not be sent to OS 2200 based hosts.) 

The following values of GLB.HUBSTATUS can occur when GLB.STATUS is set to BLOCK: 

$ GLB.HUBSTATUS is LOST.CONNECTION 

Insufficient resources were available to process or deliver the external Automatic 

Entry. 

$ GLB.HUBSTATUS is USER.DISABLED 

The destination LINC System has been locally disabled while your external Automatic 

Entry was in progress. The transaction has been cleared. 

If Immediate Commit applies, the status of the transaction on the destination System is 

undefined. 

1-38 v

GLB.STATUS is BUSY 


For more details, see the :HUB- LINC System command in the LINC Administration 

and Operations Guide for the relevant host type. 

Insufficient resources were available to process or deliver the External Automatic Entry. 

GLB.HUBSTATUS has the value INSUFF.RESOURCE. This GLB.STATUS value cannot 

occur with OLTP Automatic Entries. 

GLB.STATUS is DATA 

For all types of Automatic Entry, this indicates that the Automatic Entry was successful, 

and data has been returned. GLB.HUBSTATUS has the value OK. Use the MOVE.AUTO; or 

MOVE.AUTO.ARRAY; commands to obtain the returned data. 

GLB.STATUS is NODB 

For non-OLTP Automatic Entries, the following list shows the values of GLB.HUBSTATUS 

when GLB.STATUS is NODB. GLB.HUBSTATUS is: 

$ CONNECT.FAILED 

Connection to GLB.DESTHOST could not be established. 

$ HUB.DISABLED 

The mechanism for passing external Automatic Entries (HUB) is disabled on either the 

sending or destination host, or the destination LINC System is not known. 

$ INVALID.HOST 

The target host name (in GLB.DESTHOST) is not defined in the network. 

$ LINCSYS.DOWN 

The Server LINC System is not active. 

$ USER.DISABLED 

The destination LINC System is locally disabled for new external Automatic Entries. 

For more details, see the :HUB- LINC System command in the LINC Administration 


For OLTP Automatic Entries, the following table shows the values of GLB.HUBSTATUS 

when GLB.STATUS is NODB. 

v 1-39



SERVICE UNKNOWN Client attempted to send an OLTP transaction with a value in 

GLB.DESTINATION that is not recognized as an OLTP service 

NOT OLTP CLIENT A non OLTP-capable client attempted to call an OLTP service 

GLB.STATUS is NOEXT 

An internal Automatic Entry was attempted when the EXTERNAL; command option was 

specified in the AUTO.ENTRY; command. GLB.HUBSTATUS has no value. This 

GLB.STATUS value cannot occur with OLTP Automatic Entries. 

GLB.STATUS is TOUT 

GLB.HUBSTATUS has the value: 

$ TIMEOUT 

An external Automatic Entry was sent, but no response has been received within the 

time specified in the System Data item GLB.HUBTIMEOUT. This can only occur if 

GLB.HUBTIMEOUT is not zero. 

$ DM.DEADLOCK (MCP environment only) 

The External Automatic Entry was sent, but a timeout has occurred at a server system 

while it is attempting to enter a transaction state. The timeout (60 seconds) will 

normally only occur at a database syncpoint. This status is most likely to occur with 

non-two-phase commit transactions. 

Possible solutions are as follows: 

v Set Two-Phase Commit. 

v Use smaller transactions (for example, use more frequent SLEEP commands in 

Reports). 

GLB.STATUS is ***** 

non-OLTP Automatic Entries 

v Set the DMS II SYNCWAIT parameter to a value less than 60 seconds, by using the 

LINC DASDL options. 

For non-OLTP Automatic Entries, the following table shows the values of 

GLB.HUBSTATUS when GLB.STATUS is five asterisks (*****). 

1-40 v



SECURITY.ERROR Username/usercode of sending LINC System does not have 

sufficient security to perform the Automatic Entry on the 

destination LINC System. Security is defined by using the LINC 

Security Module (LSM). 

FATAL.ERROR An unrecoverable error occurred at the destination LINC 

System. 

CYCLE.ERROR See text following the table 

INVALID ISPEC Ispec in the destination LINC System does not exist or is Usage 

Output. 

DEST.AMBIGUOUS (UNIX only) GLB.DESTINATION is not unique on the sending 

host. Specify a value in GLB.DESTENV to give uniqueness. 

TRAN.ERROR Processing of the External Automatic Entry in the destination 

LINC Server has set GLB.ERROR to *****. For example, 

attempts to insert using an existing key value, or to update 

using a non-existent key value will cause this error. 

DATABASE.ERROR An unrecoverable database error occurred in the receiving LINC 

System. 

2PC.NOT.AVAIL An external Automatic Entry using two phase commit has been 

attempted to a destination system that does not support 

two-phase commit. 

DM.DEADLOCK (MCP environment only) An error occurred when a server 

transaction encountered a DMS deadlock error while 

attempting to lock a record. Entire server subtransaction is 

rolled back. To resolve error, set Two-Phase Commit; use 

smaller transactions (for example: more frequent sleeps from 

Reports); or set the DMSII DMSYNCWAIT parameter to a value 

less than 60 seconds, by using the LINC DASDL options. 

INVALID.RECALL An Ispec in the destination LINC System executed a RECALL; 

command. 

INVALID An entirely invalid action has been attempted. 

CYCLE.ERROR 

When GLB.HUBSTATUS is CYCLE.ERROR, external Automatic Entries have attempted to 

create a closed cycle. In a cycle, a LINC System sends an external Automatic Entry to a 

destination LINC System, and waits for acknowledgment from that System. The 

destination LINC System may itself send external Automatic Entries to other LINC 

Systems before it sends this acknowledgment, and so on, creating a chain of Automatic 

entries for one transaction. 

v 1-41


A closed cycle is formed if this chain tries to include the same System more than once; that 

is, a sending System (waiting for acknowledgment) is itself sent an Automatic Entry as part 

of the same transaction. That System would never be able to handle the incoming 

transaction, as it will never receive the acknowledgment it is waiting for. 

For example, suppose your System A sends an external Automatic Entry to System B, 

which needs to send an external Automatic Entry to System C before the transaction is 

complete. If System C then tries to send an external Automatic Entry to System A as part 

of this transaction, you have attempted to create a closed cycle, and the attempted 

external Automatic Entry from System C will receive this error notification. 

For OLTP Automatic Entries 

For OLTP Automatic Entries, the following table shows the values of GLB.HUBSTATUS 

when GLB.STATUS is five asterisks (*****). 


BAD USE OF OVI Client attempted to perform an external Automatic Entry using 

an OLTP View Ispec 

COMS SYSTEM ERR System interface error when receiving control information from 

the CRM (MCP based LINC Systems only) 

INTERSUBSYS RC; Transaction attempted to recall (using the RECALL; command) 

an Ispec in a different Subsystem (MCP based LINC Systems 

only) 

INVALID ISPEC Ispec was unknown at the server 

NO CONV. MODE Client attempted to use Conversational Mode 

NON-OLTP ISPEC The addressed Service Ispec is not OLTP-capable 

NON-2PC SERVER The addressed Service Ispec is not Two-Phase commit-capable 

when Two-Phase commit was requested 

OLTP SVC ERR A zero-length reply was unexpectedly received 

OLTP TP An error prevented the OLTP transaction from being processed 

OLTP TX Unable to communicate with OLTP TM while initiating an OLTP 

transaction 

TIMEOUT OLTP timed out waiting for a response from the server 

TRAN.ERROR GLB.ERROR was set, and no data returned 

RC; UNKNOWN Transaction attempted to RECALL; an unknown Ispec, or BYE or 

EXIT 

SWITCH CMD. Transaction attempted to perform a SWITCH; command 

1-42 v



The following table lists possible values of GLB.HUBSTATUS when an OLTP transaction is 

aborted. These fatal result messages are not visible to user logic in LINC, but they are 

available to a user with non-LINC clients. 


DATABASE.ERROR Transaction received a fatal database error and aborted. 

DM.DEADLOCK Transaction received a database deadlock error and aborted. 

The initiator of the global transaction is responsible for 

performing any transaction retries. 

REPLY INV ISPEC Service attempted to reply from an Ispec which is not 

OLTP-capable. The transaction was aborted. 

TRANS.ABORTED Transaction performed an ABORT; command and then aborted. 

‘‘AUTO (AU) and AUTO.ARRAY (AUA)’’ and ‘‘AUTO.FORMAT (AF)’’. 

The Interfaces section in the LINC Operations Guide for the relevant host type. 

‘‘GLB.ERROR’’ and ‘‘GLB.HUBSTATUS’’. 


"Online Transaction Processing (OLTP)" in your LINC Generate Operations Guide. 

BEGIN.CASE (BC) 

For details of this command, see ‘‘CASE (CS)’’. 

v 1-43

BEGIN.EDIT and END.EDIT 


Syntax 

Examples 

The BEGIN.EDIT; and END.EDIT; commands delimit sequences of main logic that perform 

editing and validation of input data in a Copy.From Ispec. Although there may be multiple 

pairs, the logic contained in the various pairs is treated as a single unit called the 

Copy.From Edit Logic, which is executed in the validation phase of the Copy.From cycle. 

Any logic that may cause rejection of data must be coded as Copy.From Edit logic. AUTO; 

FLAG; or RECALL; commands cannot be included. 

In Copy.From Ispecs, MESSAGE; commands can be coded only within Pre-LINC and Edit 

logic. The MESSAGE; command sets GLB.ERROR to ***** (and so inhibits updating the 

database) only in the validation phase of the Copy.From cycle. MESSAGE; commands are 

not actioned in the update phase of the Copy.From cycle. 

The BEGIN.EDIT; and END.EDIT; commands are not implemented in LDA Run Time. Use 

Copy.From Edit logic instead. 

For details about Copy.From Ispecs in the LINC Cycle, see your LINC Generate 


DDDD DDDD DDDD DDD4 

An Event named SALE is specified with MAX.COPIES of 5, starting from line 5. The Data 

items on line 5 are PRODUCT, QUANTITY, and AMOUNT. A CUSTOMER Data item is on 

line 3. 

 

 

 

 

 

 

 

 

 

 

 

 

 

This Copy.From edit loop will be cycled through 5 times. Any executed MESSAGE; or 

RECALL; command means that the edit loop fails, and the LINC database will not be 

updated. If the edit loop is successful, Pre-LINC and Main Logic (including the Copy.From 

edit loop) are processed MAX.COPIES times, and the database is updated (provided 

PRODUCT has a value). 

1-44 v


"Using the Copy.From Facility" in your LINC Generate Operations Guide. 


v 1-45

BEGIN.LOOP (BG) 


Syntax 

Examples 


The BEGIN.LOOP; command allows a series of logic commands to be executed repeatedly. 

Loops can be nested within loops. 

A condition should be included to specify when the loop is to be broken. 

If the loop is closed with an END.EXIT; command, and that command is actioned (that is, 

the loop is not broken earlier by some other means), then the loop is not repeated, and the 

current Ispec or Report is exited as normal for an END.EXIT; command. 

DDD DDD DDBDDDDD DDDDDDBD4 

3 3 

CDDD DDD4 

3 3 

@D DY 

In the following example, if SORTQUES is an alphanumeric data item containing 

ZYXWVUTSRQPOMNLKJIHGFEDCBA, the result in SORTANS (which has LENGTH at 

least 26) is ABCDEFGHIJKLMNOPQRSTUVWXYZ. 

 

 

 

 

 

 

 

 

Or, in a Report, the following logic could be used to print Frame 6 when a valid product 

name is input. The loop is used to repeat the prompt and input if an invalid product name is 

supplied. 

 

 

 

 

 

 

 

 

 

 

‘‘BREAK (BK)’’ and ‘‘JUMP.TO (JTO)’’, associated with a ‘‘DO.WHEN (DW)’’ to terminate 

the loop. 

1-46 v


‘‘END’’, ‘‘END.EXIT (EE)’’, and ‘‘END.NO.PRINT (ENP)’’, for terminating Ispec and Report 

logic. 

v 1-47

BEGIN.PAGE (BP) 


The BEGIN.PAGE; command designates a Frame that is to appear as a heading at the top 

of each new page of a Report. The BEGIN.PAGE; command does not generate a new page 

when it occurs. 

If several Frames are required as headings, use multiple BEGIN.PAGE; commands to 

specify the required Frames. The Frames are printed at the top of all subsequent pages in 

numerical frame order, not the order in which they are specified. 

The logic of the heading Frame is executed after the logic of the Frame currently being 

printed, during the printing of the Frame. 

The BEGIN.PAGE; CLEAR command cancels the definition of all headings. It causes an 

advance to a new page when the next frame is printed. 

Note: When the BEGIN.PAGE; CLEAR command is executed, GLB.LINECOUNT is set 

to 9999 to force the new page. Since the logic of the print frame is executed 

before the advance to new page occurs, the value of GLB.LINECOUNT is 9999, 

not 0. 

Reports Using LINC Report Output Control (ROC) 

An ADVANCE; NEW.PAGE command specified within a heading causes the heading to 

continue on the next page without restarting the heading. Use the END.NO.PRINT; 

command to suppress output. 

There is no limit on the length of the heading. 

Notes: 

$ If GLB.FORMDEPTH is set to zero, headings are not printed. In this case, use the 

PRINT.FRAME; command to print the headings you require. 

$ ROC is not available with LDA. 

Reports Not Using ROC 

During the definition of headings, the following situations may result in the creation of an 

infinite loop: 

$ An ADVANCE; NEW.PAGE command included within a heading 

$ An END.NO.PRINT; command in a heading 

$ The length of a heading equals or exceeds GLB.FORMDEPTH 

These situations should be avoided. 

1-48 v

Syntax 

Examples 


DD DBD DBDBDDDDDDDDDDDDDDDDDDDDDDDBD4 

3 33 3 

@D DY @D D DY 

Frame 1 has the display item LISTING OF DEPOSITS. 

Frame 2 has the display item LISTING OF WITHDRAWALS. 

Frame 3 has the headings CUSTOMER and AMOUNT. 

Frame 4 has the data items CUSTOMER and AMOUNT. 

A Report has the following logic. 

 

 

 

 

 

 

 

 

 

 

 


The first two BEGIN.PAGE; commands print LISTING OF DEPOSITS (Frame 1) then 

CUSTOMER and AMOUNTS (Frame 3). 

The DETERMINE; ACTUAL command creates a loop and retrieves information from the 

LINC database for printing (Frame 4). 

A new heading is created by first removing the old one (BEGIN.PAGE; CLEAR), and 

specifying the LISTING OF WITHDRAWALS heading (Frame 2), and Frame 3. Information 

is again retrieved through a DETERMINE; ACTUAL loop and printed (Frame 4). 

‘‘ADVANCE (AV)’’ 

ROC and non-ROC Reports, in your LINC Administration and Operations Guide. 

v 1-49

BREAK (BK) 

BREAK (BK) 

Syntax 

Examples 

The BREAK; command is used to terminate a loop in the logic. The loop is interrupted at 

the point at which the BREAK; command is invoked, and processing continues after the 

end of the loop. 

The BREAK; ALL variant of the command terminates all current loops. In Insertable Global 

Logic, this includes loops in the logic into which the Global Logic is inserted. In 

Performable Global Logic, this does not include loops in the logic from which the Global 

Logic is performed. 

A BREAK; command executed in Frame logic will not terminate a loop from which the 

Frame was invoked. Logic must be provided to cater for such a requirement. 

DDDDD DDBDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDDDDDDDDD4 

3 3 

@DD DDY 

Obtain a total for a customer’s invoice amounts: 

 

 

 

 

 

 

 

Check a customer’s credit level: 

 

 

 

 

 

 

 

1-50 v

CALL 

CALL 

The CALL; command enables access to external routines or programs. For each target host 

type, you can use a CALL; command to access: 

$ MCP based Library procedures, by title or by System Library (SL) function name 

For MCP based LINC Systems, the CALL; BYFUNCTION variant gives you access to 

common user libraries that have been installed using the SL system command. For 

more details, see the following subsection ‘‘Using BYFUNCTION; with the CALL; 

Command’’. 

$ MCP based LINC Reports as Coroutines. 

$ OS 2200 based COBOL or Assembler programs or procedures, and LINC Subroutine 

Reports (in conjunction with the LINCSUB SGS) 

$ UNIX programs or routines, or the shell 

For UNIX LINC Systems, external COBOL programs exist as programs separate from 

the LINC System. Their location is contained in the environment variable COBPATH. 

$ Dynamic Linc Libraries (DLL) 

In LDA, the entry points used with the CALL: command to access DLLs are case 

sensitive. 

$ LDA Reports that have been specified as Able to be run as a Sub/Coroutine 

Parameter Passing 

Parameters can be passed by using the System Data item GLB.PARAM, whose value you 

must define before executing the CALL; command. Data returned from the routine also 

uses GLB.PARAM. 

Note: The internal common field used to pass this information is GLBPARAM (not 

GLB-PARAM), which enables access by programs written in a variety of 

languages. 

For information on passing parameters when using internal or external routines with the 

CALL; command, see your UNIX LINC Administration and Operations Guide. 

Checking of Operands 

No syntax checking is performed on the literal operands of the CALL; command. It is your 

responsibility to ensure that the literal operand conforms to the syntax requirements of the 

compiler you are using to generate the runtime system. If not, your generate will fail. It is 

also your responsibility to ensure the library procedure, routine, or program being called 

actually exists, and is able to be called at runtime. If not, the calling LINC System or Report 

will abort. 

For More Information 

For more details, see: 

$ 

"Syntax" for each host type, later in this subsection 

v 1-51

CALL 

Syntax 

$ ‘‘Using BYFUNCTION; with the CALL; Command’’ (for MCP based LINC Systems), 

later in this subsection 

$ ‘‘Using Coroutines with the CALL; Command’’ (for MCP based LINC Systems), later in 

this subsection 

$ Your OS 2200 Based LINC Administration and Operations Guide (for OS 2200 based 

LINC Systems) 

$ The Interfaces section of your LINC Administration and Operations Guide for the 

relevant host type 

$ " CALL" in the LDA online help 

Note: The syntax of the CALL; command is different for UNIX, MCP and OS 2200 

based LINC Systems. The syntax for each host type is given separately in the 

following subsections. 

MCP Based Syntax 

D B D BDBDDDDDDDDDDDDDDBDDBD4 

3 33 3 3 

CDDDDDD DD DDDDDY@ Y 3 

3 3 

@DDDDDDDDDD DDD DDDDDDDDDDY 

literal 1 

A literal value containing the Procedure name. For COBOL routines, this value is always 

PROCEDUREDIVISION. The entry point identified by literal 1 is interpreted as being a 

function provided by the System Library. The CALL; command passes the contents of 

GLB.PARAM to that function, and causes the function to be performed. 

literal 2 

A literal value containing the name of the Library. Total length of literal 1 and 2 is not 

greater than 50 characters 

literal 3 

The literal value is the name of the Library (up to 50 characters), and must be the same as 

literal 2 in any CALL; commands that invoke functions in the Library. 

In the MCP SL command, you must specify the actual file title associated with this value. 

This parameter is ignored on other target host types. 

For more information, see ‘‘Using BYFUNCTION; with the CALL; Command’’, later in this 

section. 

1-52 v

eport 

CALL 

Indicates that a Report generated as a Coroutine is to be called by the CALL; command. 

You supply the name of the Report in report (a literal value of up to 56 characters), which 

must be in the form: 

 

The pack value defaults to the object pack for your LINC System. 

For more information, see ‘‘Using Coroutines with the CALL; Command’’, later in this 

section. 

usercode 

A literal containing the usercode of the Report or library, enabling you to include CALL; 

commands across usercodes (if this is permitted by your system security). 

OS 2200 Based Syntax 

DDDD DDD DDD DDDDDD4 

literal 1 

A literal value of up to 12 characters containing the Procedure name. 

literal 2 

UNIX Syntax 

Include either the literal (CANCEL) or a dummy literal. 

If you include (CANCEL), the dbank requirements for the subroutine will be discarded 

after it has been run. You are required to include a literal to satisfy the syntax of the 

command. If you do not include (CANCEL), the literal is ignored by the CALL; command. 

DDDDD DBD DD DBDDDDDDD4 

3 3 

CD DD D4 

3 3 

@DDDD DDDDDD DY 

data name 1 (INTERNAL;) 

A data item that contains the name (up to 14 characters) of a routine or process (program). 

The name is case sensitive. The value of the data item is interpreted as the name of a 

routine. Aroutine used in this way is a set of logic that is always called from some other 

logic; that is, it cannot be executed on its own. 

v 1-53

CALL 

A COBOL routine may be: 

$ A object code format (.o) routine bound into the lrts 

$ A native code file (.gnt), whose name must be in uppercase 

$ An interpretive code file (.int), whose name must be in uppercase 

The routines are searched for in order of precedence (bound routines are highest, 

interpretive are lowest). 

At runtime, if the called routine is not found, the LINC System will abort with a COBOL 

error. 

To bind object code format routines into the lrts, define the environment variable 

LINCII_DOT_O. This should be set to the name of the file that lists the object code files to 

be bound in to the lrts. This must be done before the system is generated. 

For information on passing parameters when using internal or external routines with the 

CALL; command, see your UNIX LINC Administration and Operations Guide. 

data name 2 (EXTERNAL;) 

A data item that contains the name (up to 14 characters) of a routine or process (program). 

The name is case sensitive. The value of the data item is interpreted as the name of a 

process (or program), which is a compiled program that may be executed in its own right. 

Caution 

If the EXTERNAL; command option is used, the called routine must not attempt to 

read from or write to the terminal. 

The value of the System Data item GLB.PARAM is used as an argument to this process. 

GLB.PARAM is also used to return data: 

$ The value NOTOK means that an error was detected in the execution of the command. 

$ Multiple lines of output are separated by newline characters. 

$ A null value is returned after the last byte of output. Use the System Data item 

GLB.LOW to test for null values. 

(:;) EXTERNAL; 

A two-character literal consisting of a colon followed by a semi-colon (:;) followed by 

EXTERNAL; . This names the Bourne shell as the process. 

1-54 v

LDA Syntax 

Caution 

If the EXTERNAL; command option is used, the called routine must not attempt to 

read from or write to the terminal. 

CALL 

The value of the System Data item GLB.PARAM is used as an argument to this process. 

GLB.PARAM is also used to return data, as described previously for the data name 2 value. 

DDDD DDD DDD DDDDDD4 

literal 1 

The name of your function (routine), up to 18 characters long. 

literal 2 

An alphanumeric Literal value of up to 18 characters containing the DOS pathname of your 

DLL. In cases where the DLL pathname is longer than 18 characters, open a DOS session 

and execute the following DOS command to associate the long path with a drive letter, 

before executing this LINC command. For example: 

 

If literal 2 does not include a period (.) then LDA will automatically append the suffix 

‘‘.DLL’’. Because the period character causes an error in an MCP based COBOL compile, 

you should leave the addition of the ‘‘.DLL’’ suffix to LDA. For example: 

 

willbeconvertedinLDARunTimeto: 

 

Note: The GLB.PARAM parameter is a character buffer. Numeric fields (like alpha 

fields) can be passed by using the ATTACH; Logic command or the DETACH; 

Logic command to add or remove them from GLB.PARAM, respectively. 

Using the CALL; Command in LDA 

The CALL; command provides an interface to non-LINC routines that are held in a Dynamic 

Link Library (DLL). It is your responsibility to ensure that the DLL being called exists. 

Each CALL to the same DLL will cause the DLL to be loaded; therefore, do not assume that 

values set within the DLL in a previous CALL; of the Library will be retained for the current 

CALL;. 

v 1-55

CALL 

The dllmgr.dll library supplied with LDA contains the LoadAndStick() and 

UnstickAndFree() functions to preload and retain a specific DLL. If you need to access 

those values in a subsequent CALL; command, call LoadAndStick() in dllmgr.dll to retain 

that DLL in memory and leave the values. When you no longer need those values, call 

UnstickAndFree(). The memory management of these values is your responsibility. 

Note: The entry points used with the CALL; command to access DLLs are case 

sensitive. For example, the entry point names to access the dllmgr.dll must be 

in the format LoadAndStick() and UnstickAndFree(). 

The source, definitions, and make files for dllmgr.dll are also supplied with LDA. These are 

the dllmgr.c, dllmgr.def, and dllmgr.mak files. 

It is your responsibility to call UnstickAndFree() during the shutdown of LDA Run Time 

for each DLL preloaded using LoadAndStick(). 

LDA supports the use of the CALL; command to run Reports as Coroutines or subroutines 

for: 

$ MCP based LINC Systems 

$ OS 2200 based LINC Systems 

Note: Use of Coroutines or subroutines to initiate Reports is not supported in UNIX. 

The implementation of the CALL; command varies depending on the target host. 

LDA and MCP based LINC Systems 

See ‘‘MCP Based Syntax’’ for a description of the syntax for calling a Coroutine from an 

MCP based LINC system. 

See ‘‘Using Coroutines with the CALL; Command’’ for a description of the implications of 

using a Coroutine to initiate a Report, instead of the standard LINC Report initiation 

process. 

LDA and OS 2200 based LINC Systems 

See ‘‘OS 2200 Based Syntax’’ for a description of the syntax for calling a Report from an 

OS 2200 target host. 

See your OS 2200 Based LINC Administration and Operations Guide for a description of 

using a subroutine to initiate a Report, instead of the standard LINC Report initiation 

process. 

Using BYFUNCTION; with the CALL; Command 

1-56 v

Introduction 

CALL 

For MCP based target hosts, using the BYFUNCTION; option with the CALL; command 

gives you access to common user libraries that have been installed using the SL system 

command. You do not have to embed the title of the library in the CALL; command that you 

use to access the libraries. Instead, your user-defined System Library names (as used in SL 

commands) can be used in the CALL; command, to identify the required library. 

For each of the library programs you want to access in this way, you must code an 

additional CALL; command that serves only to identify the library as called by function. 

This command is required once within each LINC Subsystem in which there is a CALL; 

command to a particular library, and once within each Report that calls that library. 

The initialization code associated with the command is unconditionally executed. 

Therefore, the Ispec or Global Logic containing the code does not need to be invoked to 

begin execution. The Ispec or Global Logic does, however, need to be included as part of 

your LINC System (or in a module of your LINC System). 

Reasons for Using BYFUNCTION; Command Option 

Reasons to use the BYFUNCTION; command option with the CALL; command are: 

$ You do not need to embed the Library title, including pack name, in your logic. 

$ You are not required to specify a usercode with the library name. 

Using the BYFUNCTION; Command Option 

In Reports, the BYFUNCTION; command option with the CALL; command is only valid in 

Main Logic (Frame 00). The actual CALL; commands can be anywhere in Report logic. 

If the command is included within your LINC Logic more than once (for example, because 

of Inserted Global Logics), then the initialization will be generated for each occurrence. 

Also, whenever a BYFUNCTION; command option is inserted, edited, or deleted, 

(including LCOPY operations), all Subsystems of the LINC Specification are regenerated 

when the LINC Specification is next generated. 

This creates overhead; thus it is recommended that you place this command in a standard 

location in your LINC Specification - for example, CLOSEDOWN Global Logic, where 

accidental maintenance can be avoided or minimized. 

Note: You must ensure that the libraries you call by function are first declared as 

System Libraries by using the SL command. If this is not done on site, the 

LINC program will be suspended, waiting for the library. 

When you wish to make changes to the functions of an SL library, you should consult with 

other users of the System Library, to prevent conflicting requirements. 

v 1-57

CALL 

Using Coroutines with the CALL; Command 

For an MCP based LINC System, you can generate LINC Reports as COBOL Coroutines 

that can then be called by using the CALL; command. 

Generating a Report as a Coroutine 

To specify that a Report is to be generated as a Coroutine, enter Y in the Generate as a 

Coroutine field on the MCP based Report Environmental Options screen. 

Reports generated as Coroutines cannot be run as normal LINC Reports. 

Coroutines can also be called from non-LINC programs. See the description of the CALL; 

command in your MCP Based LINC Administration and Operations Guide. 

Passing Parameters to Coroutines 

Use the System Data item GLB.PARAM to pass parameters to and from a Coroutine. It is 

good practise to include a GLB.FILLER item that makes the total parameter area length 

equal to the length defined in your LINC System. 

Execution of a Coroutine sets the System Data item GLB.CORSTATUS. 

Executing a Coroutine 

When executing a Coroutine: 

$ The System Data item GLB.INITSTN contains BATCH while the Coroutine is running. 

$ MESSAGE; and ACCEPT; commands function in the same way as they do for 

standalone Reports. 

$ CRITICAL.POINT; commands perform an end transaction and wait for any specified 

sleep time. 

$ SLEEP;UNTIL.WOKEN commands perform only an end transaction. WAKE.UP; 

commands are ignored by Coroutines. 

$ External Automatic Entries set GLB.STATUS to NODB. 

$ The value of the System Data item GLB.CORSTATUS is defined. See "Handling Errors 

from Coroutines", later in this section. 

$ If the Coroutine enters transaction state, it will exit from transaction state before it 

returns to the calling program. 

$ Extract files and print files are closed, before returning to the calling program. 

$ There is no Report recovery. 

$ The Coroutine remains linked to the calling program until EOJ . 

Handling Errors from Coroutines 

Executing Coroutines with the CALL; command sets the System Data item 

GLB.CORSTATUS. Values of GLB.CORSTATUS are contained in the following table. 

1-58 v

Examples 

Value Execution 

spaces Successful 

MWAIT Failed: resource deadlock exceeded the system MAXWAIT timeout 

DMERR Failed: fatal DMS error 

INVKY Failed: invalid key in LINCNET file 

PRINT Failed: Coroutine restarted after approaching limit of 1000 file opens 

permitted in a BD file 

***** Failed: unspecified error 

MCP environment 

The following logic calls the procedure CALCULATOR in the library MY/LIBRARY: 

 

CALL 

For an MCP based LINC System, this logic results in the following generated COBOL code: 

 

The following logic runs the LCORTEST Coroutine report from the LINC Specification 

named TEST, under the usercode (TESTUSER). 

 

The following logic calls the CALCULATION procedure in your System Library 

(SITEFUNCTIONS). This library must have been installed by using the following ODT 

command (SL SITEFUNCTIONS = library). 

 

 

OS 2200 environment 

The following logic calls the procedure MYROUTINE: 

 

UNIX environment 

The following logic commands list the files in the current directory: 

 

 

The following command calls the bound routine CALCULATOR: 

 

v 1-59

CALL 


‘‘GLB.PARAM’’. 

1-60 v

CASE (CS) 

Syntax 

CASE (CS) 

The CASE; command is the central part of a case statement, which enables multiple 

actions selected by the case variable to be specified. This is an efficient alternative to using 

multiple DO.WHEN; commands. 

The commands used to define a case statement are summarized in the following table. 

Command Abbreviation Function 

BEGIN.CASE; BC; Start of the case statement 

CASE; CS; Case condition 

OTHERWISE; OW; Default case condition 

END.CASE; EC; End of the case statement 

Each command (and all enclosed logic commands) must start on a new line. 

A BEGIN.CASE; (BC;) command specifies a data item against which values defined by 

CASE; commands are compared. 

If any of the values specified matches that of the data item, the following logic (up to the 

next case condition) is performed and execution continues from the END.CASE; (EC;) 

command associated with the case statement. 

The OTHERWISE; (OW;) command can be used to specify logic to be performed when no 

other case conditions with the CASE; statement apply. 

Case statements may be nested to nine levels deep, including the use of case statements 

within the logic associated with the OTHERWISE; command. 

DDDD DD DDDDDDDDDDDDDDDDDDDDDDDD 

ZDDDDDDDDDDDDDD? 

3 3 

DDDD DAD DADDDDDDDDDDDDDDDDDDDDDDDDDD 

DDDDDBDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDDDDBDDD 

3 3 3 

@DD DDY CDDD 

3 

@DDD 

DDDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD 

DDDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD 

DDDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD4 

v 1-61

CASE (CS) 

data item 1 

A valid data item name. The System Data items GLB.SPACES and GLB.ZEROS are not 

valid. 

data item 2 

A data item or literal (up to 18 characters long), giving a value that defines the specific 

case, where data item 1 has that same value. More than one data item or literal value can 

define any one case. 

The following table shows the types of data item 1 that can be compared to each type of 

data item 2. For example, if data item 2 is a pure Kanji data item, it can only be compared 

with another Kanji data item in data item 1. 

If data item 2 is... Then data item 1 can be... 

Alpha A 

Alpha Literal A 

Numeric ANSCD 

Numeric Literal ANSCD 

Signed ANSCD 

Signed Decimal Literal ANSCD 

Decimals ANSCD 

Date ANSCD 

Kanji K 

GLB.ZEROS ANSCDK 

GLB.SPACES, GLB.HIGH, 

GLB.LOW 

Legend 

A Alpha 

N Numeric 

S Signed 

C Decimals 

D Date 

K Kanji 

1-62 v 

AK

Examples 


CASE (CS) 

In the following example of Report main logic, all EMPLY Ispecs are accessed to obtain 

employee details. Depending on the department each employee works in, their details are 

either extracted to one of four predefined Extract Files (A, J, M, or C), or ignored (for 

departments S and T, and invalid departments). Employees with invalid department codes 

are listed (by printing Frame 90). 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

‘‘DO.WHEN (DW)’’ 

‘‘JUMP.TO (JTO)’’ for restrictions on branching and case statements. 

v 1-63

CLEAR.ARRAY; (CLA) 

CLEAR.ARRAY; (CLA) 

The CLEAR.ARRAY; command clears the entire contents of a Setup Data array or Global 

Setup Data array in a single operation. If the array is alphanumeric, each element is set to 

spaces. If the array is numeric, each element is set to zero. 

The data item used to index the array is not reset by this command. 

Syntax 

DDD DDDDDDDDD DDDDDDDDDDDDDDD4 

Here data name is a Setup Data array or Global Setup Data array. 

1-64 v

COMPUTE (COMP) and COMPUTE.FROM (CMP, CF) 


Syntax 

The COMPUTE; and COMPUTE.FROM; commands enable the entry of free-form 

expressions involving arithmetic operations and data items. 

The result of the calculation is stored in a numeric data item. 

$ For the COMPUTE; command, the data item is named as part of the command. 

$ For the COMPUTE.FROM; command, the data item must be a Setup Data item, defined 

immediately before the COMPUTE.FROM; command. 

Note: The COMPUTE.FROM; command is not implemented in LDA Run 

Time. 

Calculations are performed in the standard mathematical order of precedence for 

arithmetic operators, and from left to right. 

When using the COMPUTE; and COMPUTE.FROM; commands: 

$ The System Data item GLB.STATUS is not affected by either of these commands. Use 

the GLB.STATUS; command (in LDA, the GS; command) to test for a divisor of zero or 

arithmetic overflow. If either occurs, the result is set to zero. (You could include logic 

to test for a divisor of zero before the COMPUTE; or COMPUTE.FROM; commands are 

executed.) 

$ A maximum of fifteen operands may be used in a COMPUTE; command. 

In LDA, the maximum is 98 operators and 99 operands. 

$ Data items and operators in the COMPUTE; or COMPUTE.FROM; command must be 

separated by at least one space. 

$ If the receiving data item in a COMPUTE; or COMPUTE.FROM; command does not 

allow sufficient decimal places for precision, the result will be truncated (rather than 

rounded). 

$ In host LINC, if you do not use the GLB.STATUS; command in your arithmetic logic 

and you divide by zero, your program will abort. 

DDDDD DDDDDDDDDDBD DDDD 

3 

DDDDD DD DDY 

ZDDDD? 

ZDDDDDDDDDDDY @DDDDDDDDDDDDD? 

3 3 

DDDDDDDADDD DD DDAD DDDDDDD4 

data item 

A previously defined data item into which the result is to be placed. 

v 1-65


Examples 

operator 

An arithmetic operator symbol value from the following table. 

Delimit all operators with spaces. 

COMPUTE; Example 

Symbol Arithmetic Operator 

+ Addition 

- Subtraction 

* Multiplication 

/ Division 

** Exponentiation 

In the following result, the total price and tax price are calculated. 

 

 

 

 

 

 

 

 

COMPUTE.FROM; Example 

Three signed numeric data items AMOUNT, AMOUNT1, and TOTAL are declared in an 

Event. A Setup Data item named SDTWO has a value of 2. 

 

 

 

 

 

 

 

1-66 v



 

 

 

 

 

 

 

 

‘‘Setting of GLB.STATUS’’ 

v 1-67

CONTRA (CN) 

CONTRA (CN) 

Syntax 

Example 


The CONTRA; command changes the sign of a data item. This is equivalent to changing a 

debit to a credit, or a credit to a debit. 

The data item must be numeric and signed (ED; C, ED; S, ED; -, or ED; +). See the EDIT; 

Data Attribute for further details. 

DDDDD DDDDDD DDDDDDDDDDDDDDDDDDD4 

 

"EDIT (ED)" in your LINC Generate Reference Manual: Painter and Editor. 

1-68 v

CRITICAL.POINT (CP) 


The CRITICAL.POINT; command is used in Reports to enable easy and rapid recovery 

following a system failure. 

Restrictions on CRITICAL.POINT; commands 

For an MCP based LINC System, CRITICAL.POINT; commands are not allowed with 

Reports being output to Video. 

There is a maximum limit of 99 Critical Points in one Report. 

The CRITICAL.POINT; command can be inserted anywhere in main Report logic, except 

within DETERMINE or LOOK.UP loops. It may be necessary to include logic to exit such 

loops before performing a Critical Point. 

What Happens at a Critical Point 

During normal operation, the following processes occur at a Critical Point: 

$ Recovery data is moved from memory to the LINC database. 

$ In Direct Reports printed under the LINC Report Output Control System (ROC), all 

print files are released, and completed parts of Direct Reports are printed. For a UNIX 

LINC System, if output is being directed to a file, this means that a new output file is 

created for each release. For LDA, all print files are released and all disk files (such as 

extract files) are closed. The release of print files can be inhibited by including the 

NO.RELEASE; command option. 

$ Profile information is reset. This means that after the Critical.Point, data must be 

retrieved from the LINC Database before FLAG; commands can be used successfully. 

Automatic Entries will function correctly without additional retrieval. 

Ensure that reference data items are brought into memory by DETERMINE; or 

LOOK.UP; commands before executing the CRITICAL.POINT; command. 

$ For UNIX and MCP based LINC Systems, an end-of-transaction is forced. (For an MCP 

based LINC System, in a LINC Report (including a LINC Report generated as a 

Coroutine), the CRITICAL.POINT; command performs an end transaction and then 

waits for any specified sleep time. See the CALL; command for details of Coroutines.) 

$ On OS 2200 based LINC Systems, a COMMIT of database updates occurs. 

$ For performance reasons, ensure that the number of Critical Points used is not 

excessive. 

$ Extract files that were open for output are CLOSED. 

On Recovery 

When recovery takes place after a system failure, the Critical Point performs an automatic 

read of recovery data back into memory and resumes processing at the instruction 

immediately following the most recently processed CRITICAL.POINT; command. 

v 1-69


For files being written at the last Critical Point, Report Recovery will automatically restart 

writing the Report from the record written at the last Critical Point. For files being read at 

the last Critical Point, Report Recovery will restart reading at the beginning of the file. If 

you find that this is not what you require, you must save the current record number, 

GLB.RECORDx, in the Critical Point data block and restore the value of GLB.RECORDx if 

the Report is restarted. 

Where to include Critical Points 

The CRITICAL.POINT; command should be used at important points in the processing 

cycle of the Report, such as after a record is read, but before it is written. This means that 

data stored for recovery is the data about to be processed. 

For an MCP based LINC System, regular Critical Points should be included to avoid delays 

at sync points and control points, when other programs using the database may be 

suspended waiting for this Report. 

For a UNIX based LINC System, regular Critical Points should be included to avoid delays 

in committing the locked records, when other programs using this database may be 

suspended waiting for this Report. 

OLTP 


Critical Points in Reports Using ROC 

Standard ROC Reports write output to the ROC tables in the LINC Database. For MCP and 

OS 2200 based LINC Systems, if the database is not in transaction state when data has to 

be written to a ROC data structure, a transaction state will be started for the database 

update, and then immediately end. For a UNIX LINC System, the database will stay in 

transaction state until a Critical Point. 

ROC database activity does not affect user database activity, and so CRITICAL.POINT; 

commands (or SLEEP; commands) are not required to avoid long database transactions 

due to ROC database activity. 

At a Critical Point, all output for a Report is written to the database so that it may be 

recovered. On resumption of the Report, output continues to the same database files. The 

current files are not released. 

On recovery, the System Data items GLB.FORMDEPTH, GLB.PITCH, GLB.LINECOUNT, 

GLB.PAGECOUNT, and GLB.STN are returned to their current values as at the last 

CRITICAL.POINT. All other System Data items are set to the values held at the time of first 

output to the current print file. 

Note: ROC is not available with LDA. 

1-70 v

Storage of Recovery Data 

Syntax 


The CRITICAL.POINT; command uses a special Critical Point Group Setup Data item or 

Global Setup Data item (CP-GROUP-SD) to store the required recovery data. 

The CP-GROUP-SD item is named on the Report Options screen in the Critical Point SD 

field, and its characteristics are declared in the logic of the Report. CP-GROUP-SD may 

have a maximum size of 2,000 characters. 

The required recovery data must be stored in the CP-GROUP-SD item prior to each 

CRITICAL.POINT; command. Typically, such data consists of running totals being 

accumulated in memory, and details that will enable LINC to identify the record to be 

processed. 

The Extract file activities related to the CRITICAL.POINT; command are shown in the 

following table. 

File Status Temporary Extract 

File 

Not open for 

output 

Permanent Extract 

File 

No action No action No action 

Existing Extract File 

Open for output Closed/Reopened Closed/Reopened Closed/Reopened 

D DBDDDDDDDDDDDDDDDDDDBDBDDDDDDDDDDDDDBD4 

3 33 3 

@ D Y@ Y 

SLEEP; seconds 

The SLEEP; command option causes the Report to be suspended for the number of 

seconds (0 to 9999) specified by either the constant or the numeric data item seconds. 

Note: Do not confuse this command option with the SLEEP; command, whichisnot 

valid in Reports that contain CRITICAL.POINT; commands. 

Suspension occurs immediately the CRITICAL.POINT; command is executed, and this 

frees access to the LINC database. The Report is activated after the specified time lapse, 

and then performs any activity that may have accumulated for it. The Report is also 

activated by an explicit WAKE.UP; command. 

If the SLEEP; command option is not specified or has a zero time value, the Report will 

continue immediately after the end-of-transaction processing is complete. 

v 1-71


Example 

NO.RELEASE; 

The default is for printed output for ROC Direct Reports and non-ROC Reports to be 

released when a CRITICAL.POINT; command is executed. The NO.RELEASE; command 

option prevents this release. It has no effect in ROC Standard Reports. All output is written 

for all print files when the CRITICAL.POINT is executed. 

NO.RELEASE can be abbreviated as NR. 

The following example shows the use of the CRITICAL.POINT; command. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1-72 v


 

 

 

 

 


In this example, the CRITICAL.POINT; command is executed after every 500 records. 

Suppose a failure occurs after record 4,438 has completed. The system will then be restored 

to the condition it was in at record 4,000, and processing will restart from record 4,001. 

‘‘GLB.RECOVER’’, in Section 2. (This can be accessed through logic to identify the status of 

a recovery following a system failure.) 

‘‘GLB.TRANSTATE’’, in Section 2. 

‘‘WAKE.UP (WU)’’. 

‘‘SLEEP (SLP)’’. 

v 1-73

CURSOR (CU) 

CURSOR (CU) 

Syntax 

The CURSOR; command positions the cursor on an Ispec screen Data item or Ordinate 

when the screen is displayed. It overrides the Cursor field field on the Ispec Options 

screen. 

If multiple CURSOR; commands are specified, the last one determines the position of the 

cursor. 

For MCP and OS 2200 based LINC Systems only, the cursor can be positioned at the end of 

the page, by including the GLB.EOP command option. For UNIX LINC Systems, the use of 

GLB.EOP is ignored unless full page transmission has been disabled. 

Note: Cursor positioning has no effect when multiple error messages are displayed 

(on Page 2). 

OLTP 

Examples 

This command is not available with OLTP, and is ignored in LDA Run Time. 

DDD DDBDD DDBDDDDDDDDDDDDDDDDDDDD4 

3 3 

@DDD DDDY 

In this example, the cursor is positioned on the Data item PRICE, which has invoked an 

error condition: 

 

 

 

 

To position the cursor at end-of-page: 

 

1-74 v

DATE.CONVERT (DC) 

The DATE.CONVERT; command converts dates between date formats. 

There are two forms of the DATE.CONVERT; command: 


$ The complex form performs the conversion and updates either a series of System Data 

items, enabling the date to be accessed in various formats, or a single user data item in 

a specified format. It can also be used just to perform date editing. 

$ The simple form uses the System Data item GLB.TOTAL as either the source or 

destination of a relative day number, and offers simple conversion to or from a date. 

Note: The recommended form for the DATE.CONVERT; command is the complex 

form. 

Further details of each form are given in the following subsections. 

Complex Form 

Description of Use 

The complex form of the DATE.CONVERT; command has the following features: 

$ Convert the value of a data item in a format you specify, storing the result in a series of 

System Data items that have the prefix GLB.DC-. 

These System Data items are cleared before the DATE.CONVERT; command is 

executed. For a list of the GLB.DC- data items available to you after successful 

execution of the complex DATE.CONVERT; command, see Section 2. 

$ Modify the result of date conversion, by adding or subtracting a number of days from 

the input date value. 

$ Convert the value of a data item, into a format you specify, into another data item with 

a date format that you specify. (The remaining GLB.DC- items are undefined.) 

$ Validate the value of a data item (with EDIT.ONLY; command option). (The GLB.DCitems 

are undefined, and GLB.CENTURY is not set.) 

$ May set GLB.CENTURY. 

Complex DATE.CONVERT; commands set GLB.CENTURY if you entered Y in the DC; 

sets GLB.CENTURY field on the Primary Specification Options screen. If you entered 

N, GLB.CENTURY is not changed automatically. In LDA, both forms of the 

DATE.CONVERT; command set GLB.DC-CC. 

Note: If you use historic dates, dates are not adjusted for past changes in the 

calendar. 

v 1-75


Restrictions 

The following restrictions apply to the DATE.CONVERT; command: 

$ The handling of signed numerics in Group items by the DATE.CONVERT; command 

varies, depending on the compiler implementation. If you use numeric items within a 

Group for handling dates, they should be unsigned. 

$ There is a limit of 999999 days conversion on relative day number, starting from 1 

January of your base year. 

$ Numeric inputs to the DATE.CONVERT; cannot be more than 23 characters in length. 

Use of GLB.BASE and GLB.CENTURY 

The conversion is based upon a base date defined by the System Data items GLB.BASE, 

GLB.CENTURY, and GLB.CENTURY-START. 

How GLB.BASE is used 

GLB.BASE is used in the following ways: 

$ GLB.BASE is set on your Primary Specification Options screen, when defining your 

LINC Specification. The base year defaults to 1957. The valid range is 1 through 9999. 

$ The relative day number of January 1 of the base year is 0. The relative day number 

field is a six-digit numeric field. 

$ Dates prior to the base year are invalid. However, as described in "Deducing the 

Century for Six Digit Dates", the value of GLB.CENTURY may be adjusted 

automatically (if the value of GLB.CENTURY is zero or is the same century as 

GLB.BASE) to ensure that dates are valid. See also ‘‘Invalid Input Dates’’, later in this 

section. 

$ You can define the working range of dates (of 100 years) for your LINC System by 

using the System Data item, GLB.CENTURY-START, and by using the Supervisor 

command SCENTURY. The working range is used to interpret six digits dates, as 

described in "Deducing the Century for Six Digit Dates". 

Deducing the Century for Six Digit Dates 

The value of GLB.CENTURY can be set before the DATE.CONVERT; command, if your 

input date does not contain the century (it is a six digit date). This is required if the century 

of the input date is different from the LINC default century. 

When GLB.CENTURY is zero or is the same century as GLB.CENTURY-START, date 

conversion sets GLB.CENTURY, as follows: 

$ If the year is equal to or greater than GLB.CENTURY-START year, then 

GLB.CENTURY is not set. 

1-76 v


$ If the year is less than the GLB.CENTURY-START year, GLB.CENTURY is the 

following century. 

Once GLB.CENTURY has been set to a value other than 0 or the century of the base year, it 

remains set until explicitly changed or an invalid date is entered. 

Examples 

For example, GLB.CENTURY-START is 1957 (the same as GLB.BASE) and GLB.CENTURY 

is 0 (or 19). 

$ The years 57 through 99 represent 1957 through 1999. 

$ The years 00 through 56 represent 2000 through 2056. 

If you perform a date conversion with a year 50 followed by years of 60 and 70, andthe 

DC; sets GLB.CENTURY field on the Primary Options screen is set to Y, the date 

conversion will set GLB.CENTURY to 20 (as 1950 is prior to the value of 

GLB.CENTURY-START), and the years are interpreted as 2050, 2060, and2070. 

Special Date Conversions 

Date conversion of the values of the following six-digit dates will not use GLB.CENTURY. 

The current century will be used. 

$ GLB.TODAY (TODAY) 

$ GLB.TODAYS-DATE-NUM (TODAYS-DATE-NUM) 

$ GLB.YYMMDD 

$ INPUT-DATE 

Invalid Input Dates 

If the date involved is invalid, GLB.STATUS is set to *****. Alternatively, the GLB.STATUS; 

command may be used to direct the result to a data item. It is important to test for an error 

whenever the DATE.CONVERT; command is used. 

GLB.STATUS is set to five asterisks (*****) under any one of the following circumstances: 

$ Invalid input date is supplied, for example 31 February 1998. 

$ Input date is prior to the start of the GLB.BASE year. 

Note: GLB.CENTURY may be adjusted automatically to ensure that the 

date is valid. For details, see ‘‘Use of GLB.BASE and 

GLB.CENTURY’’, earlier in this section. 

If GLB.STATUS is set to five asterisks, date conversion is still performed, but using the 

current date. If the current date is invalid (for example, it is prior to the start of the base 

year), then 1 January of the base year is used as input. 

v 1-77


Syntax 

DD DD DBDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDD 

3 3 

@D DY 

DD DD DBDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBD4 

3 3 

CD DD DD D4 

3 3 

@DDDDDDDDDDDDD DDDDDDDDDDDDDY 

data item 1 

An alphanumeric or numeric data item. If data item 1 is numeric, then format 1 is 

restricted to the numeric formats listed in the table of data item formats in the following 

subsection. 

increment 

Use a plus (+) or minus (-) sign followed by either a numeric literal,ornumeric data item 

if you require your resulting date to be offset from the input date by the specified number 

of days. 

FORMAT; format 1 

This specifies the format of data item 1. Theformat 1 value must be one of the formats 

specified in the table of data item formats, in the following subsection. FT is a valid 

abbreviation for FORMAT. 

data item 2 

Alpha or numeric receiving field. If it is numeric, then format 2 is restricted to the numeric 

formats listed in the table of data item formats, in the following subsection. 

FORMAT; format 2 

This specifies the format of data item 2. Theformat 2 value must be one of the formats 

specified in the table of data item formats, in the following subsection. FT is a valid 

abbreviation for FORMAT. 

After DATE.CONVERT; executes with this command option, the values contained in the 

GLB.DC- items will be undefined. 

EDIT.ONLY; 

Validate the date value of data item 1. 

After DATE.CONVERT; executes with this command option, the values contained in the 

GLB.DC- items will be undefined. 

1-78 v

Data Item Formats 


The following table lists the formats you can specify in the complex DATE.CONVERT; 

command. (The Example column values are set based on a GLB.BASE of 1957.) 

Date Items Length, Edit Format Example 

DAYNUM 6N nnnnnn 13960 

UK-ALPHA 25 A DDbMMMMMMbCCYY 23 MARCH 1998 

US-ALPHA 25 A MMMMMMbDDbCCYY MARCH 23 1998 

IN-ALPHA 25 A CCYYbMMMMMMbDD 1998 MARCH 23 

DD-MM-YY 8A DD/MM/YY 23/03/98 

DD-MM-CCYY 10 A DD/MM/CCYY 23/03/1998 

DD-MMM-YY 9A DDbMMMbYY 23 MAR 98 

DD-MMM-CCYY 11 A DDbMMMbCCYY 23 MAR 1998 

DDMMMYY 7A DDMMMYY 23MAR98 

DDMMMCCYY 9A DDMMMCCYY 23MAR1998 

DDMMYY 6N DDMMYY 230398 

DDMMCCYY 8N DDMMCCYY 23031998 

MM-DD-YY 8A MM/DD/YY 03/23/98 

MM-DD-CCYY 10 A MM/DD/CCYY 03/23/1998 

MMDDYY 6N MMDDYY 032398 

MMDDCCYY 8N MMDDCCYY 03231998 

MMM-DD-YY 9A MMMbDDbYY MAR 23 98 

MMM-DD-CCYY 11 A MMMbDDbCCYY MAR 23 1998 

MMMDDYY 7A MMMDDYY MAR2398 

MMMDDCCYY 9A MMMDDCCYY MAR231998 

YY-MM-DD 8A YY/MM/DD 98/03/23 

CCYY-MM-DD 10 A CCYY/MM/DD 1998/03/23 

YY-MMM-DD 9A YYbMMMbDD 98 MAR 23 

CCYY-MMM-DD 11 A CCYYbMMMbDD 1998 MAR 23 

YYDDD 5N YYDDD 98082 

CCYYDDD 7N CCYYDDD 1998082 

continued 

v 1-79


Examples 

continued 

Date Items Length, Edit Format Example 

YYMMDD 6N YYMMDD 980323 

CCYYMMDD 8N CCYYMMDD 19980323 

YYMMMD 6A YYMMMDD 98MAR23 

CCYYMMMDD 9A CCYYMMMDD 1998MAR23 

TODAY 15 A MONDAY 

WEEKNO 2N 13 

In the following example, the value of the specified data item as a relative day number, is 

converted, and the results stored in the GLB.DC System Data items. The command status 

is stored in GLB.STATUS. 

 

In the next example, the value of the TRAN-DATE input date, in the format YYMMDD, is 

converted to the form CCYY-MMM-DD, and stored in DB-DATE. 

 

In the next example, the century is non-current, so it is stored in GLB.CENTURY prior to 

converting TRAN-DATE, in format YYMMDD. The results are stored in the GLB.DC System 

Data items. 

 

 

In the next example, the date, 45 days after ORDERDAY (IN DAYNUM format), is 

converted, and is stored in the GLB.DC System Data items. 

 

In the next example, the date, NUM-DAYS before GLB.TODAY (IN YYMMMD format), is 

converted, and is stored in the GLB.DC System Data items. Note that if NUM-DAYS is 

signed, its sign will be ignored. 

 

In the next example, the date held in the data item BIRTH-DATE is converted to a relative 

day number, and stored in the GLB.TOTAL System Data item. The value of GLB.STATUS is 

directed to SDERROR. 

 

1-80 v

Simple Form 


In the next example, TRAN-DATE with the format YYMMDD is validated. GLB.STATUS 

will contain five asterisks (*****) if the date is invalid. There is no output conversion. 

 

The simple form of the DATE.CONVERT; command uses the System Data item 

GLB.TOTAL, and is based upon the fixed base date of January 1, 1957. The relative day 

number for the base date is zero. 

DATE.CONVERT; TO.DATE takes the relative day number from GLB.TOTAL, converts it to 

a date, and moves the result into the specified data item. DATE.CONVERT; TO.ALPHA 

works in the same way. With both variants, the form of the data item determines the form 

of the result date (alphanumeric or numeric form). For more details on valid edit types, see 

‘‘Data Item Formats’’, earlier in this section. 

DATE.CONVERT; TO.DAYNUMBER takes the date contained in the data item, converts it 

to a relative day number, and moves the result into GLB.TOTAL. 

If the date involved is invalid, GLB.STATUS is set to *****. Alternatively, the GLB.STATUS; 

command may be used to direct the result to a data item. It is important to test for an error 

whenever the DATE.CONVERT; command is used. 

Syntax of the Simple Form 

Restrictions 

DDD DDBDD DDBDD DD4 

3 3 

CDDDD DDDDD4 

3 3 

@DDDD DDDDY 

You cannot use the simple form of the DATE.CONVERT; command with: 

$ 8-digit dates 

$ Hankaku-Katakana characters 

The handling of signed numerics in Group items by the DATE.CONVERT; command varies, 

depending on the compiler implementation. If you use numeric items within a Group for 

handling dates, they should be unsigned. 

v 1-81

DESCENDING 

DESCENDING (DSC) 

For information on the DESCENDING; command option, see either the MATCH; or SORT; 

command later in this section, as relevant. 

1-82 v

DETACH (DET, DTH) 


The DETACH; command moves text from an alphanumeric (EDIT; A, EDIT; K or EDIT; W) 

data item into a second data item of the same edit type. 

Following execution of the DETACH; command, the System Data item GLB.LENGTH 

contains the length of the text selected from the first data item. 

Position and Delimiter 

The text to be moved is defined by a starting position, and by the occurrence of a delimiter. 

Starting Position 

If the starting position is invalid, no move will take place and the second data item will 

contain spaces. The default starting position is the first character. 

If a data item is used to specify a starting position, it will be updated to the position of the 

first non-delimiter character (following the delimiter) in the first data item value. 

Delimiter 

The default delimiter is a space. Multiple consecutive occurrences of the delimiter are 

treated as a single occurrence. The delimiter is not included in the move. 

If the specified delimiter is not found, the contents of the first data item starting from the 

specified starting position are moved to the second data item The contents are truncated if 

the second data item is too small. 


The maximum length moved by a DETACH; command is 2000 characters. This is 

equivalent to 1000 Kanji (EDIT; K) characters. 

The text selected by the DETACH; command may be truncated if the second data item is 

too small. 








v 1-83


Syntax 

Examples 

DDD DDDDD DDDDD DDDDDDDDDDDD 

DBDDDDDDDDDDDDDDDDDDDDDDDDDDBDBDDDDDDDDDDDDDDDDDDDDDDDDDDBD4 

3 33 3 

@ D Y@ D Y 

Note: The three alphanumeric items must have the same edit type. 

data name 1 

An alphanumeric data item (not a literal) 

data name 2 

An alphanumeric data item (not a literal) 

POSITION; numeric data 

The numeric data value can be a numeric data item or literal. It must be unsigned, and it 

must not have decimals. 

POSITION may be abbreviated to POS or PO. START is also a valid. 

DELIMITER; data name 3 

DELIMITER may be abbreviated to DELIM. 

The data item (or literal) must be alphanumeric. 

In the following example, SD-DATA1 initially contains THE QUICK BROWN FOX. The 

DETACH; command moves QUICK BROWN FOX and stores it in SD-DATA2. The fifth 

character is the starting point for the DETACH command, signified by POS; (05). 

GLB.LENGTH will be set to 15 following execution of the DETACH; command. 

 

 

 

1-84 v



In the next example, words in a sentence are displayed one by one (with their lengths) on 

Page 2. 

 

 

 

 

 

 

 

 

 

 

 

 

Since SD-PTR is updated to the next word as each word is detached, the loop will cause 

the following to be displayed. 

 

 

 

 

‘‘GLB.LENGTH’’ in Section 2. 

v 1-85

DETERMINE; (DT) Commands 


The DETERMINE; command variants are used to read data into memory from the LINC 

database through a Profile or, using DETERMINE; ACTUAL, an Extract file or dataset. 

The particular variant controls the manner in which records are read into memory, and 

how many. Once a record is in memory, it can be manipulated by the associated logic. 

The definition of the Profile, in particular its Ordinates and ASCENDING; or 

DESCENDING; Profile Attributes, determine which records are retrieved, and the order in 

which the records are retrieved. 

Caution 

There are differences in the way in which database accesses are handled on the 

various host types. 

For MCP based LINC Systems and UNIX Griffin LINC Systems, accesses by 

DETERMINE; commands are dependent on the positioning of the Profile by nested 

DETERMINE; commands. To avoid unexpected side-effects do not access the 

sameProfilewithnestedDETERMINE;commandsasaccessesbynested 

DETERMINE; commands can alter the positioning on the Profiles required by outer 

DETERMINE; commands, and unexpected records can be read. 

For OS 2200 based LINC Systems and UNIX ORACLE LINC Systems, each 

DETERMINE; command is independent of previous positioning. 

For LDA, the behaviour matches that of the target host defined by the TargetHost 

parameter in your LINC.INI file. 

Variants of the DETERMINE; Command 

The particular variant controls the number and manner in which records are read into 

memory. Once in memory, a record may be manipulated by logic. 

The DETERMINE; command variants are summarized in the following table, and are then 

described in detail in the following subsections. 

Variant Summary of Function 

DETERMINE; ACTUAL Creates a loop in which all records are read in order from a Profile, 

Extract file, or Component 

DETERMINE; BACK Creates a loop in which all the records are read in reverse Profile 

order, starting from specified values 

continued 

1-86 v

continued 

Variant Summary of Function 


DETERMINE; EVERY Creates a loop in which all records that match specified values are 

read in order from a Profile 

DETERMINE; FROM Creates a loop in which all records are read that are greater than or 

equal to specified values 

DETERMINE; GROUP Creates a loop in which all data are read, between specified start and 

end values, from a Profile. The order is specified as part of the 

command 

DETERMINE; LAST Reads a single record equal to or lower than the values specified 

DETERMINE; TOTAL Reads through a Profile in order and, where the Profile Ordinates 

match the specified values, accumulates a nominated data item 

An END; command must terminate the loop created by all variants except DETERMINE; 

LAST and DETERMINE; TOTAL. The logic contained in the loop is executed for each 

record read. 

Setting of GLB.STATUS 

If a DETERMINE; command fails to retrieve any record (that is, no record satisfies the 

specified criteria), GLB.STATUS is set to *****. If any record is retrieved, GLB.STATUS 

will not be set by the DETERMINE; command. GLB.STATUS is not set when end-of-file is 

detected. 

The contents of GLB.STATUS should always be checked after a DETERMINE; command 

or, if a loop is created, after the END; or END.EXIT; command for that loop. GLB.STATUS 

is cleared (set to spaces) before the command is executed. 

You can direct the new value of GLB.STATUS resulting from the DETERMINE; command 

to another data item, by including the GLB.STATUS; command. This is especially useful 

where many commands may set GLB.STATUS (for example, where there are nested 

DETERMINE; commands). 

Logically Deleted Records 

Logically deleted records are brought into memory by DETERMINE; commands (unless 

they are specifically excluded by the Profile conditions). If you wish to ignore them you 

have to code your logic to bypass them. 

v 1-87


Handling of Duplicate Keys in MCP based LINC Systems 

For an MCP based LINC System, the order in which records with duplicate key values are 

retrieved depends upon the setting of the Duplicates First/Last Profile DASDL option, as 

shown in the following table. 

Duplicates DT Command Order of Duplicates 

FIRST FROM Reverse order to that of entry 

FIRST BACK Order of entry 

LAST FROM Order of entry 

LAST BACK Reverse order to that of entry 

blank FROM/BACK Physical order of records in database (note that 

this may change during a reorganization) 

A database reorganize or garbage collect may alter the order of Duplicates First/Last 

entries. For further details, see your Data and Structure Definition Language (DASDL) 

Programming Reference Manual. 

DETERMINE; Commands in ORACLE LINC Systems 

The following issues can arise with UNIX ORACLE LINC Systems: 

$ DETERMINE; BACK and DETERMINE; LAST command performance 

ORACLE has no direct means of reading a Profile in reverse order. When executing 

these commands, ORACLE may read and sort the entire Profile (table) to obtain the 

required records. 

$ Inappropriate ORACLE Index Selection 

On occasion, ORACLE may select the wrong index (Profile) where the Indexes have 

identical keys but in a different order. This can have performance implications for your 

LINC System. 

These issues and suggested solutions are described in your UNIX LINC Administration 

and Operations Guide. 

DETERMINE; Commands Over Multiple Logic Lines 

DETERMINE; commands can be written over multiple lines, provided that line breaks 

occur within the parentheses, and a line does not commence with a right parenthesis. 

In DETERMINE; GROUP commands, the first line may break before any data item within 

any of the parentheses sets. 

1-88 v


Under certain circumstances, lines can be marked with errors even if these conditions 

have been met. If this occurs, you can force the full command to be reedited by changing it 

to a comment, transmitting, and then changing it back to a command. 

For more details, see your LINC Generate Reference Manual: Painter and Editor. 

v 1-89

DETERMINE; ACTUAL 


The DETERMINE; ACTUAL command is used to read Component and Event records into 

memory from the LINC database, using a Profile. It also enables access to Standard, Direct, 

or Table Components, without having to specify Ordinate values. 

When a DETERMINE; ACTUAL command specifies a multiple ordinate memo value, the 

Automaint Profile of the named Memo Component is used. 

In Reports, a DETERMINE; ACTUAL command can also be used to read records from an 

Extract file. The syntax of the DETERMINE; ACTUAL command for reading Extract files 

has a special form. You can control the first record from which the read of an Extract file is 

to begin, by moving a value to the System Data item GLB.RECORDx before the 

DETERMINE; ACTUAL command is executed. 

References to data items read from an Extract file must be prefixed by the one-character 

Extract file designator (A through Z) and an asterisk (*), as shown in the example. See also 

to notes on the qualification of data items in your LINC Generate Operations Guide. 

Extract File Processing 

There are three categories of Extract file. 

$ EXISTING files, which exist before the Report begins and are retained after the Report 

ends. 

$ PERMANENT files, which do not exist before the Report begins, but are retained after 

the Report ends. 

$ TEMPORARY files, which do not exist before the Report begins, and are deleted after 


For more details, see ‘‘Categories of Extract file’’ under the EXTRACT; command, later in 

this section. 

The way a DETERMINE; ACTUAL command handles an Extract file at runtime is 

influenced by: 

$ Category of Extract file (TEMPORARY, PERMANENT, or EXISTING) 

$ Whether it is the first or a subsequent access of the Extract file 

A first access is defined as the first execution of any DETERMINE; ACTUAL, SORT , 

EXTRACT, or MATCH; commands for a specific Extract file, either in the logic of the 

Report, or following a SET.TITLE; or RESTART; command. 

The action performed on the specified Extract file when a DETERMINE; ACTUAL (or 

MATCH;) command is executed depends on whether or not the EXTRACTED.AS; 

command option is included, as shown in the following subsections. 

1-90 v

With EXTRACTED.AS; 


The DETERMINE; ACTUAL or MATCH; command attempts to read a record from the 

specified Extract file. The EXTRACTED.AS; command option implies that the file was not 

created by this Report (that is, the Report does not include an EXTRACT; command which 

writes the file and defines the layout). 

$ If this is not the first access of the file, the record is read. 

$ If this is the first access of the file: 

v If it is a Temporary file, the file will be created as an empty file if it does not 

already exist, or it will be cleared if it does exist. The read of the empty file will 

then immediately set GLB.STATUS to *****. 

v If it is a not a TEMPORARY file, the record will be read if the file exists, or the 

Report will abort (on UNIX or OS 2200 based LINC Systems) or become a waiting 

entry (on MCP based LINC Systems) if the file does not exist. 

v The following table summarizes the actions performed when this is the first access 

of the file. 

File Status Extract 

FileTemporary 

Extract File 


File 

File exists Read Read Read 

File does not exist Created Abort/Wait Abort/Wait 

Without EXTRACTED.AS; 


The DETERMINE; ACTUAL or MATCH; command attempts to read a record from the 

specified Extract File. Not including an EXTRACTED.AS; command option implies that the 

file was created by this Report (that is, the Report includes an EXTRACT; command which 

writes the file and defines the layout). 

$ If this is not the first access of the file, the record is read. 


v If it is not an EXISTING file, the file will be created as an empty file if it does not 

already exist, or it will be cleared if it does exist. The read of the empty file will 

then immediately set GLB.STATUS to *****. 

v If it is an EXISTING file, the record will be read if the file exists, or the Report will 

abort (on UNIX or OS 2200 based LINC Systems) or become a waiting entry (on 

MCP based LINC Systems) if the file does not exist. 

v The following table summarizes the actions performed when this is the first access 

of the file. 

v 1-91


Syntax 


File 


File 

File exists Cleared Cleared Read 

File does not exist Created Created Abort/Wait 

For Components and Profiles : 

DD DBDDDDDDDDDD DDDDDDDDDDBDD 

3 3 

CDDDDDDD DDDDDDD4 

3 3 

@D DY 

DDBDDDDDDDDDBDBDDDDDDDDDDBDBDDDDDDDDDDDDDDDDDDDDDDDBDD4 

3 33 33 3 

@ YC 4@ D Y 

3 3 

@ Y 

For Extract Files (valid only in Reports) 

DDDD DDDDDDD DDDDDBDDDDDD4 

3 

@DDDDD 

DDDDD DDDBDDD DDDDBDDDDDDDDDD 

3 3 

CDDDDD DDDDDD4 

3 3 

@DDDDD DDDDDDY 

DDDDDDDDBDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDD4 

3 3 

@DD DDD DDY 

KEYONLY; 


Note: This command option is ignored for UNIX and OS 2200 based LINC Systems, 

andinLDARunTime. 

See ‘‘KEYONLY’’, later in this section, for a description of this command option. 

extract file 

The one-character Extract file designator for an Extract file previously saved by using an 

EXTRACT; command. 

EXTRACTED.AS; 

Access records from the specified Extract file as a specified Component, the Event 

dataset, or a specified Report Frame. 

1-92 v

Example 

EAS is a valid abbreviation for EXTRACTED.AS. 

RETAINED.AS; ( file name ) 


Specifies the file name under which the Extract file was previously saved with an 

EXTRACT; command. 

RAS is a valid abbreviation for RETAINED.AS. 

Note: If you use RETAINED.AS; and SET.TITLE; for the same Extract file in a 

Report, the Extract file will be purged when the SET.TITLE; is performed. It is 

recommended that you do not use RETAINED.AS; and SET.TITLE; on the same 

file. 

In the following example, an Extract file is created through a read over the Profile 

INVOICE. A check is then made to ensure that at least one record was found. If no record is 

found, a Frame containing the message NO RECORDS WERE FOUND is printed (Frame 9). 

 

 

 

 

 

 

In the next example, an Extract file is created containing all customers with balances over 

$1000. This file is then sorted, and may be used by other Reports. 

If no customers exist with a balance over $1000, then the CUSTS/FILE file will be created 

as an empty file. This ensures that the customer records are not processed from a previous 

run. 

Note: CUSTS/FILE is an MCP based filename. UNIX and OS 2200 based filenames 

have a different form. 

 

 

 

 

 

 

 

 

 

 

v 1-93



Fast access to the Component CUST can be achieved without using the default Profile of 

the Component, as in the following example. Access is in order of storage of the records. 

 

 

 

 

 

 

 

‘‘EXTRACT (EX)’’. 

‘‘GLB.STATUS (GS)’’. 

‘‘SERIAL’’ and ‘‘SECURE’’. 

‘‘MULTI’’ (2200 Series target hosts only). 

‘‘SET.TITLE (SETT)’’ for defining your Extract files. 

‘‘GLB.RECORDx’’. 

‘‘RESTART (RT)’’ for resetting to start of file. 

The sections on Extract Files and MAPPER Extract Files in the Interfaces section in the 

LINC Administration and Operations Guide for the relevant host type. 

"Profile Options Screen" in your LINC Generate Operations Guide. 

1-94 v

DETERMINE; BACK 

Syntax 


DETERMINE; BACK 

The DETERMINE; BACK command is used to read Component and Event records into 

memory from the LINC database, in reverse order of the Profile, starting from specified 

values. 

For an MCP based LINC System, the order in which records with duplicate Profile 

Ordinate values are retrieved depends upon the setting of the Duplicates First/Last field 

on the relevant Profile DASDL Options screen. 

For details about the duplicate keys, see ‘‘Handling of Duplicate Keys in MCP based LINC 

Systems’’, earlier in this section. 

For a UNIX LINC System, the order of records with identical values cannot be guaranteed. 

Apart from the sequence of records, operation is similar to the DETERMINE; FROM 

command variant. 

If the name of a Multiple Ordinate Memo Component is used in place of the Profile with the 

DETERMINE; BACK command, the Automaint Profile for the Memo Component is used. 

DD DDBDDDDDDDD DDDDDDDDDBDDDDDDDDD 

3 3 

@D DY 

DD DDBDDDDDDDDDDDDDBDDDBDDDDDDDDDDDDBDD 

3 3 3 3 

@D DY CD D4 

3 3 

@D DY 

DDDBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDDDDDDD4 

3 3 

@D DD DY 




‘‘KEYONLY’’. 

"The Profile Options" in your LINC Generate Operations Guide. 

v 1-95

DETERMINE; EVERY 


Syntax 

Example 

The DETERMINE; EVERY command is used to read Component and Event records into 

memory from the LINC database, for those records that match the Profile Ordinate values 

specified. 


DETERMINE; EVERY command, the Automaint Profile for the Memo Component is used. 

Caution 

It is not good practice to change your Profile keys during the operation of a 

DETERMINE; EVERY loop. If you do, the results cannot be guaranteed. 

DD DDBDDDDDDDDD DDDDDDDDBDDDDD 

3 3 

@D DY 

DD DDBDDDDDDDDDDDBDDDBDDDDDDDDDDDBDD 

3 3 3 3 

@D DY CD D4 

3 3 

@D Y 

DDDBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDDDD4 

3 3 

@D DD DY 

A Profile INVOICE, with Ordinates CUSTOMER and INVOICE-NO, spans an Event SALE. 

 

 

 

 

 

 

 

If CUSTOMER and INVOICE-NO have been entered through the screen with values SMITH 

and 1234, respectively. The DETERMINE; EVERY command searches the Profile INVOICE 

to find an Event named SALE with a CUSTOMER value of SMITH and an INVOICE-NO 

value of 1234. 

When a SALE Event is found, it is read into memory, and the value of the AMOUNT data 

item is accumulated into INV-TOTAL, completing the logic for this read. 

1-96 v



This process is repeated until all matching records have been read. The logic then 

proceeds from the END; command. If no SALE Events for SMITH and 1234 are found, 

GLB.STATUS is set to *****, and the error message is returned. 





v 1-97

DETERMINE; FROM 


Syntax 

Example 

The DETERMINE; FROM command is used to read Component and Event records into 

memory from the LINC database in the order of the Profile, starting from specified values. 


DETERMINE; FROM command, the Automaint Profile for Memo Component is used. 

DD DDBDDDDDDDDD DDDDDDDDDDDBDDDD 

3 3 

@D DDDDY 

DD DDBDDDDDDDDDDDBDDBDDDDDDDDDDDBDDDD 

3 3 3 3 

@D DY CD D4 

3 3 

@D Y 

DDDDDBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDDD4 

3 3 

@D DD DY 

The DETERMINE; FROM command can be used to get the total sales value for a 

CUSTOMER when the individual invoice number is not known. The Profile INVOICE spans 

the Event dataset. 

 

 

 

 

 

 

 

 

 

 

 

In this example, suppose the value of CUSTOMER is entered from the screen as SMITH. 

As the initial value for INVOICE-NO is GLB.ZEROS, the DETERMINE; FROM command 

will bring into memory all SALE Events for SMITH in ascending order of INVOICE-NO, 

adding AMOUNT into CUST-TOTAL. 

When EVENT.CUSTOMER is not SMITH (that is, a new name is read), the loop is 

terminated with the BREAK; command. If no SALE Events were read (that is, no SALES for 

SMITH, and there are no more customers alphabetically after SMITH), GLB.STATUS is set 

to *****. 

1-98 v






v 1-99

DETERMINE; GROUP 


Syntax 

The DETERMINE; GROUP command reads Component or Event records into memory 

from a Profile. You can specify the following details: 

$ The order in which records are retrieved 

$ The initial record to be retrieved 

$ The final record to be retrieved 

The order in which records are read is defined by the FROM; and BACK; command 

options. The FROM; command option means the Profile is read in Profile order, while the 

BACK; command option means the Profile is read in reverse order. 

The initial record is defined by the high-order values (values for some of the Profile 

Ordinates) and the start values (specified by the FROM; or BACK; command option). 

The final record is defined by the high-order values and the end values (specified by the 

UNTIL; command option). If the UNTIL; command option is not included, the loop is 

terminated when the last record with the specified high-order values is retrieved (or the 

last record in the file, if high-order values are not specified). 

Note: End values, Start values, or high-order values should not be changed within the 

DETERMINE; GROUP loop. 

The record left in memory is not defined when the loop of a DETERMINE; GROUP 

command terminates automatically, because of differences between the types of host on 

which LINC Systems may run. However, the current record will remain in memory 

following a BREAK; or JUMP.TO; command. 


DETERMINE; GROUP command, the Automaint Profile for Memo Component is used. 

DD DBDDDDDDD DDDDDDDDBDDDDDDDD 

3 3 

@ Y 

DD DDDBD DBDDDDDDDDDDDDDDDD 

3 3 

@D DY 

DD DBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDD 

3 3 

@D DD DY 

DDBDDDDDDDDDBDBDDDDDDDDDDBDBDDDDDDDDDDDDDDDDDDDDDDDBDD4 

3 33 33 3 

@ YC D4 @ D Y 

3 3 

@ Y 

1-100 v

Examples 


high-order values, start values, andend valuesmust be specified by data items. 

The number of high-order values plus the number of start values must equal the number of 

Profile Ordinates. The number of end values must equal the number of start values. 

Either the high-order values or the start values (and end values) may be omitted. The 

parentheses must still be supplied in each case. However, parentheses are not required for 

omitted end values. 

In these examples, a Profile INVOICE over the Event SALE has Profile Ordinates 

CUSTOMER, ACTMTH, TRANDATE, and TRANTIME. 

 

The previous logic reads all records for the Profile Ordinate specified by the item 

CUSTOMER. 

In the next example, since no high-order values are included, records on the Profile are 

read, starting from first the record with the first Profile Ordinate greater than or equal to 

the value specified by the data item CUSTOMER. (This is equivalent to DETERMINE; 

FROM.) 

 

In the next example, the DETERMINE; GROUP command is used to get the total sales 

value for a customer. 

 

 

 

 

 

 

 

 

 

In this example, suppose the value SMITH is entered from the screen for CUSTOMER. 

STARTMTH and ENDMTH have values of 9801 and 9812, respectively. 

The DETERMINE; GROUP command reads the Profile INVOICE, starting with the first 

record with EVENT.CUSTOMER equal to SMITH, and EVENT.ACTMTH equal to or 

greater than 9801. EVENT.AMOUNT is accumulated in SD-TOTAL. When 

EVENT.CUSTOMER is not equal to SMITH, or when EVENT.ACTMTH is greater than 

9812, the loop is terminated. 

If there are no records for SMITH with EVENT.ACTMTH between 9801 and 9812, 

GLB.STATUS will be set to *****. 

v 1-101






1-102 v

DETERMINE; LAST 

Syntax 

Examples 


The DETERMINE; LAST command brings a single record into memory. It searches the 

Profile for a record that matches the specified values and retrieves that record, or the 

record that would precede it on the Profile (if there is no match). 

When using DETERMINE; LAST in a running balance or equivalent situation, it is 

recommended that you set Integrity or use the SECURE; command option. This will ensure 

that the record retrieved is always the last record. For more details, see your LINC 

Generate Operations Guide or your LINC Development / LDA III Installation and 

Administration Guide. 


DETERMINE; LAST command, the Automaint Profile for Memo Component is used. 

DD DDBDDDDDDDDDD DDDDDDDDDDDDBD 

3 3 

@DD DDDDDY 

DDD DDDDDDBDDDDDDDDDDDDDDDBDDDDDDDDDD4 

3 3 

@DDD DDDY 

The following example displays the last invoice number used for the specified customer. 

 

 

 

 

 

In the next example, a DETERMINE; LAST command in Report logic specifies a Profile 

CUSTSALE, which spans the Event SALES, and has Ordinate data items CUSTOMER, 

SALEDATE, and SALETIME. The following example logic verifies that the DETERMINE; 

LAST command has found a record, and that it is the correct one. 

 

 

 

 

 

 

v 1-103



‘‘SECURE’’ and ‘‘GLB.STATUS (GS)’’ 

1-104 v

DETERMINE; TOTAL 

Syntax 

Examples 


The DETERMINE; TOTAL command creates a balance by adding together the numeric 

values of the specified data items of the selected records. The DETERMINE; TOTAL 

command is like a combination of the DETERMINE; EVERY and ADD; commands, except 

that a loop is implicit within the command. 

The DETERMINE; TOTAL command brings into memory all records on the Profile that 

match the specified values. Values of the specified data item are totalled, and the result is 

stored in the System Data item GLB.TOTAL. 


DETERMINE; TOTAL command, the Automaint Profile for Memo Component is used. 

DD DBDDD DDDBD 

3 3 

@DDDDDDDDDD DDDDDDDDDDDY 

DDDDD DD DDDDDDDDDDDDD 

DDDBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDDD4 

3 3 

@D DD DY 

In the following example, a Profile INVOICE, with Ordinates CUSTOMER and 

INVOICE-NO, spans an Event SALE. The AMOUNT values in SALE are totalled for the 

current CUSTOMER and INVOICE-NO values. 

 

 

 

 

The next example shows a Report that adds up the quantity of each product. For any 

product that has a total quantity less than 10, it prints the message STOCK-IN-HAND is 

CRITICALLY LOW (contained in Frame 09). The Profile STOCK, with Ordinate 

PRODUCT, spans Events that affect quantities (that is, stock movements). The 

stock-in-hand value is totalled for the current PRODUCT value as follows. 

 

 

 

 

 

 

 

v 1-105



In this example, Frame 10 contains "NO TRANSACTIONS FOR THIS ITEM". 

‘‘GLB.TOTAL’’. 



1-106 v

DISCOUNT.CASH (DCF) 

Syntax 


The DISCOUNT.CASH; command provides functions commonly used in financial analysis. 

These functions are listed in the following table. 

Action Synonym Brief Description 

PV.FLOW P.A* Present value yielding rate of flow 

FLOW.PV A*.P Rate of flow to amortize present value 

FV.FLOW SN.A* Future sum resulting from rate of flow 

FLOW.FV A*.SN Rate of flow yielding future value 

COMPOUND SN.P,C Future value resulting from present lump sum 

DISCOUNT P.SN,D Present lump sum yielding future value 

MORTGAGE A.P,M Annuity to repay present value 

PV.ANNUITY P.A Present value yielding annuity 

FV.ANNUITY SN.A Future value resulting from annuity 

SINK A.SN Annuity yielding future value 

The DISCOUNT.CASH; command may return an unpredictable result if an error is 

returned. The value of the System Data item GLB.STATUS (or a data item specified by the 

GLB.STATUS; command) should be checked before the result is used. 

When using signed numeric data items with edit types of $, *, or -, truncation of significant 

digits will occur without warning, if the lengths are too short. 

DD DD DD DD 

DDDDDD DDD DDD DDDDDDDDDDDDDD4 

initial value 

A numeric data item holding the initial value. This data item is treated as a LE; 12, ED; N, 

DE; 3 data item, and thus if you specify a data item that does not have these attribute 

values, you must ensure that significant truncations will not occur. 

interest rate 

A numeric data item holding the percentage interest rate to be applied per time unit. This 

value must be positive and is interpreted as a percentage. It is treated as a LE; 10, ED; N, 

DE; 8 data item. 

v 1-107


time unit 

A numeric data item holding the number of time units. It is treated as a LE; 12, ED; N, DE; 6 

data item. 

action 

The required actions and synonyms are listed in the preceding table. The System Data item 

GLB.STATUS is set to ***** if the specified action is invalid. 

result 


The numeric data item into which the result is stored. The LENGTH and DECIMAL 

characteristics may vary. As a guideline, the internal intermediate work files are stored as 

follows, and rounded on output: 

$ PIC 9(11)V 9(12) for MCP based LINC Systems 

$ USAGE COMP-2 for UNIX and OS 2200 based LINC Systems 

Full details of the calculations are contained in ‘‘Calculations’’ in Appendix A. 


1-108 v

DIVIDE (DV) 

Syntax 

DIVIDE (DV) 

The DIVIDE; command divides the value of a numeric data item into the value of second 

numeric data item, and stores the result in the second data item (or in a third data item, if 

explicitly given). 

The GIVING; and ROUNDED; command options can be applied in conjunction with the 

DIVIDE; command. If the ROUNDED; command option is used with the REMAINDER; and 

GIVING; command option the result is rounded, but the value of the remainder is still valid. 

If the divisor is zero or an arithmetic overflow occurs, the result is zero. 

The System Data item GLB.STATUS is not updated by the DIVIDE; command. Use the 

GLB.STATUS; command (in LDA, the GS; command) to test for division by zero or 

arithmetic overflow. 

D DBD DBD DDDDDD 

3 3 

@DD DDY 

DDBDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDD 

3 3 

@DD DD DDY 

DDBDDDDDDDDDDDDBDDBDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBD4 

3 3 3 3 

@D DY @D DD DY 

numeric data 1 

A data item containing the value to divide by (the divisor). A numeric literal is valid. 


A data item containing the value to be divided (the dividend). A literal is not valid. This 

data item contains the result if GIVING; is not specified. 



command option must be on the same line as the DIVIDE; command. GIV is a valid 

abbreviation for GIVING. Thenumeric data 3 parameter cannot be a literal. 

REMAINDER; numeric data 4 

Directs the true remainder of the division to a numeric data item. 

ROUNDED; 

Rounds the result when truncation occurs. 

v 1-109

DIVIDE (DV) 

Examples 


In the following example, three Setup Data items, AMOUNT1, AMOUNT2, and AMOUNT3 

(all LE; 5, ED; +) have already been defined. 

 

 

 

 

 

‘‘GLB.STATUS (GS)’’ for directing the value of GLB.STATUS to a data item. 

1-110 v

DO.WHEN (DW) 

Syntax 

DO.WHEN (DW) 

The DO.WHEN; command creates a condition that controls the execution of logic. This 

logic is delimited by an END; END.EXIT; or END.NO.PRINT; command which must follow 

the DO.WHEN; condition. 

To create a compound condition involving several DO.WHEN; statements, you can use the 

AND and OR logical connectors. In compound conditions, the OR connectors are 

evaluated first. Compound conditions require only one END; END.NO.PRINT; or 

END.EXIT; command, as they create a single logical condition. 

You can use the ELSE; command to handle reverse conditions. 

Caution 

On OS 2200 based LINC Systems, DO.WHEN; commands with more than 50 

conditions will cause COBOL compilation errors when compiling your system. 

DDDBDD DD DBDDDDDDDBDBD D 

3 3 33 

DY @D DY@D DD 

DDDDDDD DDDDDDBDDDDDDDBDDDDDDDDDDDDDDDDDDD4 

3 3 

DDDDDDDDDDDDDDDDDDDDDDDDDDY CD DBDDDDDDDDDD 

3 3 

@D DDY 

The relation value represents a relational operator, which must be delimited with spaces. 

Valid relational operators for the DO.WHEN; command are shown in the following table. 

Relation Description 

= Equal 

> Greater than 

< Less than 

NOT = Not equal to 

NOT > Less than or equal to 

NOT < Greaterthanorequalto 

v 1-111

DO.WHEN (DW) 






Alpha ANDZG 


Numeric ANSCDZ 


Signed NSCDZ 

Signed Decimal Literal ANSCD 

Decimals NSCDZ 

Date ANSCDZ 

Kanji KZG 



GLB.LOW 

AK 

Legend 

A Alpha 

N Numeric 

S Signed 

C Decimals 

D Date 

K Kanji 

Z GLB.ZEROS 

G GLB.SPACES, GLB.HIGH, GLB.LOW 

Most processes that set GLB.STATUS on an error condition also set GLB.STATUS to 

spaces if no errors are detected. 

As various conditions can affect GLB.STATUS, you must exercise care when coding 

complex decision logic that involves more than one DO.WHEN; command. Consider the 

following code: 

 

 

1-112 v

Examples 


DO.WHEN (DW) 

In this example, it is intended that the first DO.WHEN; command checks the result of a 

previous action. However, the action of the array item sets the value of GLB.STATUS 

before the first DO.WHEN; condition is evaluated. This is because the array evaluation that 

changes GLB.STATUS takes place before the start of the DO.WHEN; command, and not at 

the point of reference. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

‘‘CASE (CS)’’ for multiple conditions. 

‘‘ELSE’’ for reverse conditions. 

‘‘END’’, ‘‘END.EXIT (EE)’’, and ‘‘END.NO.PRINT (ENP)’’ for terminating the DO.WHEN; 

loop. 

v 1-113

ELSE 

ELSE 

Syntax 

Use the ELSE; command to provide code to handle the reverse condition to that specified 

in an associated DO.WHEN; command. 

For example, in the following logic, the ADD; command is actioned if A equals B, but the 

SUBTRACT; command is actioned if A is not equal to B. 

 

 

 

 

 

One END; command terminates the DO.WHEN; command and its enclosed ELSE; 

command block. 

ELSE; Commands with nested DO.WHEN; commands 

The ELSE; command is valid with nested DO.WHEN; commands. When used with nested 

DO.WHEN; commands, each ELSE; command provides the reverse path for its current 

level of DO.WHEN; command. There can be only one ELSE; command within the 

DO.WHEN; command. 

In the following example, the second ELSE; command provides the reverse flow for the 

first DO.WHEN; command; that is, when A is not equal to B. In this case, where A is not 

equal to B, the nested DO.WHEN; command and its ELSE; command is completely 

bypassed. 

 

 

 

 

 

 

 

 

 

DDD DDD DDBDDDDD DDDDDDBDD4 

3 3 

CDDD DDD4 

3 3 

@D DY 

Note: An END.EXIT; after an ELSE; command applies only to the ELSE; command, 

and not to the associated DO.WHEN; command. 

1-114 v


‘‘DO.WHEN (DW)’’. 

ELSE 

v 1-115

END, END.EDIT, END.CASE 

END 

Syntax 

Example 


The END; command defines the end of a block of logic introduced by a loop or a condition. 

DDDDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD4 

 

 

 

END.EDIT 

 

‘‘END.EXIT (EE)’’ and ‘‘END.NO.PRINT (ENP)’’. 

For details of this command, see the ‘‘BEGIN.EDIT and END.EDIT’’. 

END.CASE (EC) 

For details of this command, see the ‘‘CASE (CS)’’. 

1-116 v

END.EXIT (EE) 

Syntax 

Examples 


END.EXIT (EE) 

The END.EXIT; command is similar to the END; command in that it defines the end of a 

block of logic introduced by a loop or a condition. When an END.EXIT; command 

terminates a loop, only one pass is made through the loop. 

The END.EXIT; command has the additional function that, when executed, it causes the 

remaining logic to be skipped, effectively terminating Pre-Screen, Pre-LINC, or Main logic 

in Ispecs, or Main logic in Reports. In Report Frame logic, the END.EXIT; command 

terminates the logic of the Frame, the Frame is printed, and execution continues after the 

PRINT.FRAME; command that invoked the Frame. 

When Pre-LINC logic is terminated by an END.EXIT; command execution continues with 

Main logic unless GLB.ERROR is equal to *****. 

Including an END.EXIT; command in an Insertable Global Logic has the same result as if 

the END.EXIT; command were included directly in the logic. 

Note: The END.EXIT; command does not set GLB.ERROR and does not inhibit 

updating of the LINC database. An END.EXIT; after an ELSE; command 

applies only to the ELSE; command and not to the associated DO.WHEN; 

command. 

DDDDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD4 

 

 

 

 

‘‘END’’ and ‘‘END.NO.PRINT (ENP)’’. 

v 1-117

END.NO.PRINT (ENP) 

END.NO.PRINT (ENP) 

Syntax 

Examples 


The END.NO.PRINT; command is similar to the END; command in that it defines the end 

of a block of Report logic introduced by a loop or a condition. It causes the Report Frame 

to terminate (without printing), and execution continues from after the PRINT.FRAME; 

command which invoked the Frame. It is valid in Reports only. 

In the Main logic of a Report, it terminates the Report. 

In Report Frame logic, it causes the Frame to terminate without printing, and execution 

continues after the PRINT.FRAME; command that invoked the Frame. 

When an END.NO.PRINT; command is executed in a Report Frame, Usage Output data 

items are not reset to spaces or zeros. You must include logic to initialize these data items 

as required. 

Note: An END.NO.PRINT; command after an ELSE; command applies only to the 

ELSE; command, and not to the associated DO.WHEN; command. 

DDDDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD4 

A Frame has a data item BALANCE. 

 

 

 

‘‘END’’ and ‘‘END.EXIT (EE)’’. 

‘‘PRINT.FRAME (PF)’’. 

‘‘BEGIN.PAGE (BP)’’. 

1-118 v

END.USE (EU) 

Syntax 


END.USE 

The END.USE; command is used in conjunction with the EXCLUSIVE.USE; command. It is 

used to unlock restricted access to the database records of an Ispec. 

This command is ignored: 

$ In LDA Run Time 

$ For MCP based LINC Systems, if the command has not been executed outside the DMS 

transaction state 

DDD DD DDDDDDDDDDDDDDDDDDDDD4 

‘‘EXCLUSIVE.USE (EXU)’’. 

v 1-119

EXCLUSIVE.USE (EXU) 

EXCLUSIVE.USE (EXU) 

Syntax 


The EXCLUSIVE.USE; command is a means of restricting access to the database records 

of an Ispec. The Ispec must be read in the logic in which the lock is applied. The command 

locks all of the records of a Component, or all records of all Events. 

This command is ignored in LDA Run Time. 

Restrictions on record access are: 

$ For UNIX and MCP based LINC Systems, records may be read by other users, but 

cannot be updated until either the end of the current transaction, or an END.USE; 

command (in a Report). 

$ For OS 2200 based LINC Systems, records remain inaccessible to other users until 

either the end of the current transaction, or an END.USE; command (in a Report). 

The EXCLUSIVE.USE; command is ignored if a SECURE; command option has been 

applied to the same Ispec in the same logic. (The effect of the EXCLUSIVE.USE; command 

can also be achieved by locking a control-type record.) 

EXCLUSIVE.USE; enables faster access at execution time, as no locks have to be applied, 

but has the potential disadvantage of locking out all other users of the Ispec until the lock 

is released. 

Caution 

Excessive use of the EXCLUSIVE.USE command may result in: 

$ Long waits for other users 

$ Deadlocks 

$ An abort at runtime 

DDDD DDBDD DDBDDDDDDDDDDDDDDDDDDD4 

3 3 

@DD DDY 

"Integrity" in your LINC Generate Operations Guide. 

1-120 v

EXTRACT (EX) 

EXTRACT (EX) 

The EXTRACT; command puts the current values of data items from selected Component, 

Event, or Report Frame records into an Extract file. 

An Extract file can be read by: 

$ The same Report that created it 

$ Another Report within your LINC system 

$ Another LINC System (on the same host or on a different host) 

$ A standalone program (which may read the data into a non-LINC system) 

$ MAPPER (by specifying the MAPPER; command option with an EXTRACT; command) 

When using Extract files, consider the following points: 

$ Up to 26 simultaneous Extract files can be created in a Report. 

$ Multiple extracts involving the same Extract file append to the file. For more details, 

see ‘‘Multiple Extracts to the Same File’’, later in this section. 

$ On OS 2200 based LINC Systems, the Extract file is opened when the first EXTRACT; 

command is executed, and is closed when the Report terminates. Therefore the data 

items defined in the Extract file will not be available until the EXTRACT; command is 

actually executed. Using data items defined in the Extract file when the file has not 

been opened will cause a runtime error (in UCS). Therefore, if the EXTRACT; 

command is executed conditionally, use of the data items should also be conditional. 

$ In LDA Run Time, the PACKED BINARY and TAPE options are not implemented. The 

location of the extract files is determined by the Extract path field in the Report 

Options dialog box. 

$ To close the current Extract file and open another one, use the SET.TITLE; command. 

$ When switching from reading an Extract file to appending data to it, the first 

EXTRACT; command should be immediately followed by a CRITICAL.POINT; 

command. Failure to do this could result in duplicate records on the Extract file if the 

Report was aborted and automatically recovered at this point. 

Caution (OS 2200 based LINC Systems) 

On OS 2200 based runtime hosts, a maximum of 60,000 tracks will be allocated 

to your Extract file, as the default. If you envisage your file being larger than this, 

catalog the file prior to running the Report. You can increase this maximum by 

using the file size option within @CAT. If you pre-catalog an Extract file, it must be a 

permanent file. 

v 1-121

EXTRACT (EX) 

Types of Extract File Format 

You can define an Extract file in one of two formats: 

$ Ispec format 

$ Report Frame format 

With either choice, the layout of the Extract file is determined when the LINC Report 

is generated (not dynamically at runtime), and it applies throughout the Report. 

Defining an Extract File in Ispec Format 

This form is useful when you want to perform operations internal to your LINC System 

(such as sorting data without using Profiles). To write Ispec data to an Extract file (in 

internal Ispec format), use the EXTRACT; logic command, specifying an Ispec name. 

Any one Extract file can contain either of the following (but not both). 

$ All the data items from one Component (the record size is the Component record size) 

$ All the data items from one or more Events (the record size is the Event set record size) 

See ‘‘Numeric Data Items in Extract Files’’, later in this section for further details. 

Important Considerations 

$ You will receive a generate error if you attempt to extract an Ispec that has the same 

name as a Profile over that Ispec. 

$ When you generate a Report, the definition of the Ispec is taken from the current LINC 

Specification. This may cause problems if your Ispec definition has been changed but 

your LINC System has not been generated, as the definition will not match the 

database. 

Defining an Extract File in Report Frame Format 

This form is useful when you want to transfer of data in and out of a LINC System. This type 

of Extract file can be used by both LINC and non-LINC programs, for example, MAPPER. 

To write the contents of a Frame to an Extract file (in a format defined by the Frame 

layout), use the EXTRACT; command, specifying the Frame. You can set up a Frame 

particularly for this purpose, if required. 

For Extract files in Report Frame format: 

$ You can include Display Items, but only after you have defined all your data items. 

$ The record size of the file is defined by the largest extracted Report Frame. 

1-122 v

EXTRACT (EX) 

$ As logic associated with a Frame is performed when the Frame is extracted, a Frame 

cannot be extracted from within its own logic. If a Frame is extracted for use in 

another Report, the Frames should be defined identically in both Reports. 

$ See ‘‘Numeric Data Items in Extract Files’’, later in this section for further details. 

To create an Extract file for MAPPER you must create an Extract file in Report Frame 

format. In MAPPER Extract files, the columns of data values are separated by tabs. 

Numeric Data Items in Extract Files 

For numeric data items in Extract files: 

$ Numeric data items extracted as part of a Frame may have a different format from 

those extracted as part of an Ispec record (depending on the host type). The default 

for Frame numeric data items is COBOL type DISPLAY. This can be changed to COMP 

by adding the BCD Data Attribute to the data item. Ispec numerics are always COMP. 

$ Numeric data items extracted as part of an Ispec record are extracted as COMP for 

MCP based LINC Systems, COMP-3 for UNIX, and DISPLAY for OS 2200 based LINC 

Systems. See the COBOL Manual for implications of signed points. 

$ Numeric data items extracted as part of a Frame have the sign folded into the least 

significant digit. See your COBOL manual for a description of the PICTURE clause for 

details on folding the sign in. 

$ For MAPPER Extract files, numeric data items must have leading signs. To achieve 

this, define the relevant numeric data items with the FLOATING.SIGN Data Attribute. 

Multiple Extracts to the Same File 

If an Extract file has already been accessed by another command, such as a DETERMINE; 

ACTUAL or SORT; command, the EXTRACT; command will append data to the existing 

file, unless the RESTART; command is used. 

If you Extract multiple Frames that include the same data item (from the same Ispec) to an 

Extract file, and then read this item back in, you will receive a COBOL error or warning, 

and your Reports may not function as intended. 

LINC does not distinguish the same data item extracted to the same file from different 

Frames when that file is read back in. 

For example, you may have an Ispec data item CUST.NAME painted in both Frames 10 and 

11, and you extract both these Frames to file A. A later DETERMINE; ACTUAL A 

EXTRACTED.AS; 10 and a reference to A*CUST.NAME will refer to Extract file records 

extracted from both Frame 10 and 11. 

v 1-123

EXTRACT (EX) 

For an MCP based LINC System, COBOL gives an error, but on OS 2200 based LINC 

Systems using the ACOB compiler, only a warning is generated, and COBOL resolves the 

problem itself (not necessarily correctly), by using the first definition of the duplicates it 

finds. 

Compatibility of Extract Files 

When extracting Ispecs, Extract files are not compatible between different host types. If 

you extract a file on one host type and want to load it into a system that is running on a 

different host type, you may need to write additional code to convert some fields into the 

correct format. For example, when extracting a Component or Event on UNIX or OS 2200 

based LINC Systems, the GLB-DTIME field (used internally by LINC) can cause problems 

when loading the file into LDA. 

On UNIX and OS 2200 based LINC Systems, extracting a Memo Component will give you 

all the user fields and GLB-DTIME. A Standard Component gives you user fields plus 

GLB-DTIME and a one-character MAINT field. Events give you user fields and 

GLB-DTIME, ACTMTH, GLB.REPORT, INPUT-DATE, ISPEC name, TRANNO, and 

LAST-LINE. 

Categories of Extract file 


$ EXISTING files 

These files exist before the Report begins and are retained after the Report ends. To 

specify an EXISTING file, use one of the following logic command constructs: 

v SET.TITLE; with the EXIST; command option 

v DETERMINE; ACTUAL with the EXTRACTED.AS; command option, at the point 

from which it was executed (only applies while the command is being executed) 

v MATCH; (only applies while the command is being executed) 

$ PERMANENT files 

These files do not exist before the Report begins, but are retained after the Report 

ends. To specify a PERMANENT file, use one of the following logic command 

constructs: 

v SET.TITLE; (without the EXIST; command option) 

v EXTRACT; with the RETAIN.AS; command option 

v DETERMINE; ACTUAL with the RETAINED.AS; command option 

$ TEMPORARY files 

1-124 v

EXTRACT (EX) 

These files do not exist before the Report begins, and are deleted after the Report 

ends. To specify a TEMPORARY file, use one of the following logic command 

constructs (and do not include a SET.TITLE; command): 

v EXTRACT; (without the RETAIN.AS; command option) 

v DETERMINE; ACTUAL (without the RETAINED.AS; command option) 


The way an EXTRACT; command handles an Extract file at runtime is influenced by: 

$ The category of the Extract file (TEMPORARY, PERMANENT, or EXISTING) 





The EXTRACT; command attempts to write a record to the specified Extract File. 

$ If this is not the first access of the Extract file, the extracted data will be appended to 

the existing file. 

$ If this is the first access of the Extract file, the action performed on the file when the 

EXTRACT; command is executed depends on the category of the file, as shown in the 



File 


File 

File exists Cleared Cleared Cleared 

File does not exist Created Created Created 


At the end of Report execution, the action performed on the file when an EXTRACT; 

command has specified that file depends on the category of the file and whether it was 

actually accessed, as shown in the following table. 


File 


File 

Not accessed Deleted Cleared No action 

Accessed Deleted Closed Closed 


v 1-125

EXTRACT (EX) 

Syntax 

Creation of Persistent Dummy Extract Files in LDA 

When the logic below is executed, if the file MISSING.FIL does not exist, a message box 

gives the choice of ‘‘Abort, Retry, or Ignore’’. If you choose ‘‘Ignore’’, a dummy file of zero 

length is created. If the file title has the EXIST; attribute, the file will persist after the 

Report is completed. 

 

 

 

 

 

Subsequent attempts to read a file created as a result of an ‘‘Ignore’’ response will not cause 

the missing file message box to be displayed. However, GLB.STATUS will be set on the 

first read of each attempt. 

DD DDBDD DDBDDDDDDDDDDDDDDDDDDDDBD 

3 3 3 

CDDDD DDDDY 3 

3 3 

@DDDD DDBDDDDDDDDDDDDDDDDDDDDDD4 

3 3 

@D DBDDDDDDDDDD4 

3 3 

@D DY 

DD DD DDBDDDDDDDDDDDDDDDDDDDDDDBDD4 

3 3 

@D DD DY 

header 

Report Frame used to provide header records for an Extract file in MAPPER form. The 

header included in an extracted Report Frame is that specified in the first EXTRACT; 

command for that Frame. 

Note: MAPPER header frames specified in the EXTRACT; command are ignored in 

LDA Run Time. Records in the Extract file are produced in MAPPER format. 

You can add appropriate MAPPER header information to the Extract file after 

it has been created. 

The MAP command in the LINC Painter can be used to create a default heading Frame. 

The MAPPER; command can abbreviated as MP. 

RETAIN.AS; file 

This command option enables you to save the Extract file (for example, for use in other 

Reports) in the file specified by the value of file, an alphanumeric literal. 

1-126 v

Examples 

There are restrictions on the name of the file: 

EXTRACT (EX) 

$ For an MCP based LINC System, the file name can contain any number of levels, but 

cannot exceed 18 characters (including slashes). System usercodes cannot be 

included. 

$ On OS 2200 based LINC Systems, the file name may not contain more than one asterisk 

(*) character, and cannot be longer than 18 characters. If no asterisk character is used, 

the maximum is 12 characters. 

Note: At runtime, if you want to write the extracted data to a different file 

from that named by the RETAIN.AS; command option, you can add 

the appropriate @USE statement into the ECL generated with each 

Report, prior to the @XQT of the Report. 

$ For a UNIX LINC System, the name may be any valid pathname, with a maximum 

length of 18 characters, but any portion of the pathname between successive slash (/) 

characters cannot exceed 14 characters. 

On all host types, assignment of the file name is not dynamic, but is always assigned to the 

last RETAIN.AS; command option in the current logic, whether that command is executed 

or not. For more details, see "Example 3" in the following subsection. 

RETAIN.AS may be abbreviated as RAS or RTN. 

Example 1 

In the following example: 

1. Selected INVOICE records on a Profile are read. 

2. Each selected record is stored in turn in an Extract file. 

3. This file is then sorted on the data items SALE and STATS. 

4. Selected records are then printed. 

 

 

 

 

 

 

 

 

 

 

 

 

v 1-127

EXTRACT (EX) 

Example 2 

In the following example of an extracted Frame: 

$ Frame 21 has three Data items: CUST.CUSTOMER, AMOUNT, and PBALANCE1 (LE; 6 

ED; +). 

$ Frame 22 has three corresponding items: A*CUST.CUSTOMER, A*AMOUNT and 

PBALANCE2 (LE; 6 ED; +). 

$ The following logic is included in the Main Logic of the Report. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Example 3 

The next example illustrates that assignment of the name of the Extract file by the 

RETAIN.AS; command option is not dynamic, but is always that of the last RETAIN.AS; 

command option specified in the Report. 

 

 

 

 

 

 

 

 

 

1-128 v


EXTRACT (EX) 

The file will be retained under the name BB, even when FIELD1 contains the values A or C. 

To prevent this, use the SET.TITLE; command, as follows: 

 

 

 

 

 

 

 

"MAP" in your LINC Generate Reference Manual: Painter and Editor for creating Extract 

file headers in MAPPER format. 

‘‘DETERMINE; ACTUAL’’ for details of reading an extracted file. 

‘‘SORT (SO)’’. 

‘‘SET.TITLE (SETT)’’. 

"BCD" in your LINC Generate Reference Manual: Painter and Editor. 

"BINARY (BIN)" in your LINC Generate Reference Manual: Painter and Editor. 

The "Extract Files" and MAPPER Extract Files" subsections in the "Interfacing to Other 

Systems" sectioninyourLINC Administration and Operations Guide for the relevant 

host type. 

v 1-129

FLAG (FL, FG) 

FLAG (FL, FG) 

The FLAG; command is used to directly modify data in the LINC database. 

Note: A FLAG command causes a database update, regardless of the setting of 

GLB.ERROR (unlike an AUTO.WRITE; command, or Ispec automatic update at 

the end of Main logic). 

For flagging a Setup Data item array to an alphanumeric data item, use the FLAG.ARRAY; 

command. 

What You Cannot Use a FLAG; Command For 

You cannot use the FLAG; command to: 

$ Change the value of the Ordinate of a Component. 

$ Store an alphanumeric value in a numeric data item. 

$ Move the value of a Data item to another Data item in the same Ispec. If this is 

required, use a Setup Data item as intermediate storage. (See "Before Executing a 

FLAG; Command".) 

Before Executing a FLAG; Command 

Before executing a FLAG; command, the record to be changed should be retrieved. When 

the FLAG; command is executed, the record is again retrieved from the LINC database, to 

reduce the chance of data corruption. Since the record in memory is overwritten, it is 

advisable to hold required values in Setup Data items until after the execution of any 

FLAG; commands. (This is why you cannot use the FLAG; command to move the value of a 

Data item to another Data item in the same Ispec. Use a Setup Data item as intermediate 

storage.) 

Grouping FLAG; Commands 

Consecutive FLAG; commands are grouped together, with the combined database record 

changes being written to the database in one operation. When the FLAG; commands are 

separated by other commands, multiple database update operations will occur, possibly 

causing unexpected performance degradation. 

Record Locking 

The first FLAG; command locks the record being flagged, prior to storing it. The record is 

not freed until End of Transaction. 

1-130 v

Syntax 


FLAG (FL, FG) 








DDDD DDBDD DDBDD DDDDD4 

3 3 

@DD DDY 





Alpha A 


Numeric ANSCD 


Signed NSCD 

Signed Decimal Literal NSCD 

Decimals NSCD 

Date ANSCD 

Kanji K 


Legend continued 

A Alpha 

N Numeric 

S Signed 

C Decimals 

D Date 

K Kanji 

v 1-131

FLAG (FL, FG) 

Examples 


continued 



GLB.LOW 

Legend 

A Alpha 

N Numeric 

S Signed 

C Decimals 

D Date 

K Kanji 

In a Report, a flag is set (the data item PRINTED in the EVENT data set) when an Invoice is 

printed. 

AK 

 

 

 

 

 

‘‘FLAG.ARRAY (FLA)’’. 

1-132 v

FLAG.ARRAY (FLA) 

Syntax 


The FLAG.ARRAY; command writes the contents of a Setup Data array or Global Setup 

Data array to the LINC database. It performs the same function for arrays as the FLAG; 

command does for data item values. 

Note: Numeric Setup Data array items are implemented as COBOL 

COMPUTATIONAL fields. A move from a numeric array to anything other 

than an identically defined numeric array may result in data that is invalid 

for use in either computation or display. 


When moving an array into a data item: 

$ You must ensure that the receiving alphanumeric data item is of sufficient size to store 

the array. 

$ If you move a mixed alphanumeric and Hankaku-Katakana value into an EDIT; W data 


data item. However, if you move a mixed alphanumeric and Hankaku-Katakana value 

into an EDIT; A data item, the value is moved byte by byte and is truncated to the 

length of the data item. If the truncation occurs after the first byte of a double-byte 

Hankaku-Katakana character, this will result in an invalid character. 


DD DDDD DDDDD DDDDDDDDDDDDDD4 

array 

Examples 


data item 


In the following example, a Setup Data array is stored in the LINC database. 

 

 

 

v 1-133



‘‘FLAG (FL, FG)’’. 

1-134 v

GET.LENGTH; (GL) 

Syntax 

Examples 


The GET.LENGTH; commands returns the length of the data in alphanumeric (EDIT; A), 

Kanji (EDIT; K), and Hankaku-Katakana (EDIT; W) data items. The length includes leading 

and embedded spaces, but not trailing spaces. The results are stored in the System Data 

items GLB.LENGTH and GLB.FULLLENGTH. If the data item is spaces, both System Data 

items are set to zero. 

GLB.LENGTH is the length of the data item in characters. GLB.FULLLENGTH is the length 

in bytes. GLB.FULLLENGTH will equal GLB.LENGTH except for data items that contain 

Hankaku-Katakana characters in UNIX LINC Systems. See the description of 

Hankaku-Katakana characters in your LINC Generate Reference Manual: Painter and 

Editor, for further details. 

Note: GLB.FULLLENGTH is not implemented in LDA, so GET.LENGTH returns only 

the length in characters and stores the result in GLB.LENGTH. 

The maximum length that can be determined by the GET.LENGTH; command is 2000 

characters. If the truncated data exceeds this length, GLB.LENGTH is set to 2000. 

Note: A two-byte KANJI character is counted as one character in GLB.LENGTH. 

DDDD DDDD DDDDDDDDDDDDDDDDDDDD4 

data name 

Thedataitemdata name must be EDIT; A, EDIT; K, or EDIT; W. 

 

 

 

 

 

 

 

 

 

 

v 1-135


In this example, when the ATTACH&SPACE; command is executed, the value of 

GLB.LENGTH is set to 9, the length of ABCDE FGH. This value is truncated to ABCDE and 

stored in SD-DATA1. The difference in values between SD-LENGTH and GLB.LENGTH 

indicates that truncation has occurred. 

1-136 v

GLB.STATUS (GS) 

Syntax 


The GLB.STATUS; command directs the system error status of a command result to a 

specified data item, instead of using the System Data item GLB.STATUS. 

The GLB.STATUS; command is used as follows: 

$ The GLB.STATUS; command is associated with another command, and it must appear 

on the same logic line as that command (or as part of the last line if the command 

spans several lines). 

$ Before the associated command is executed, the data item specified by the 

GLB.STATUS; command is cleared (set to the value of the System Data item 

GLB.SPACES). 

$ The result is moved to the data item after the execution of the associated command or 

completion of the loop created by the associated command. 

$ Valid associated commands are: 

v ADD; 

v ATTRIBUTE; 

v COMPUTE; and COMPUTE.FROM; 

v DATE.CONVERT; 

v DETERMINE; commands 

v DIVIDE; 

v LOOK.UP; commands 

v MATCH; 

v MOVE; 

v MULTIPLY; 

v SUBTRACT; 

v WAKE.UP; 

$ For LDA, you must use GS; (and not GLB.STATUS;). GLB.STATUS is always 

interpreted as the System Data item, and may cause a syntax error. 

Note: The GLB.STATUS; command has an additional effect when included as part of 

the MOVE; command. See the MOVE; command for further details. 

DDDD DDD DDDDDDDDDDDDDDDDDDDDDDDD4 

data item 

The data item must be alphanumeric and have a minimum length of five. 

v 1-137


Example 


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

‘‘GLB.STATUS’’. 

‘‘MOVE (MV)’’ (‘‘Setting GLB.STATUS’’). 

1-138 v

INITIALIZE (INIT) 

Syntax 


The initialization of Group Setup Data items and Group Global Setup Data items is subject 

to different behavior on the different host types. For example, for MCP based LINC 

Systems and LDA, you can move spaces to a Group Setup Data item that contains numeric 

Setup Data items. These numeric data items are interpreted as containing zero. For OS 

2200 and UNIX LINC Systems, this is not the case. Moving alphanumeric values to Group 

Setup Data items that contain numeric Setup Data items can cause unpredictable results 

on a host that uses a different character set (EBCDIC or ASCII). 

The INITIALIZE; command ensures that initialization is the same across all host types. In 

addition, the command offers a wide range of choices of initial value. 

Note: Although this command will initialize the values of Setup Data items (and 

Global Setup Data items) with initial values, it strongly recommended that the 

values of these items are not changed in your logic. See your LINC Generate 


Data Types 

For the INITIALIZE; command: 

$ The term alphanumeric includes KANJI (EDIT; K) and Hankaku-Katakana (EDIT; W) 

characters. 

$ Date values (EDIT; D) are treated as numeric values. 

DD DD DBDDDDDDDDDDDBDDD4 

3 3 

@D DY 

item 

This is a Global Setup Data item or Setup Data item. Must not be a Setup Data array or 

Global Setup Data array. 

setting 

Specifies the type of initialization. Values of setting are contained in the following table. 

v 1-139


Example 


Setting Description 

(none) Sets all alphanumeric items to spaces and all numerics to 

zeros. 

GLB.ZEROS Sets all items to zeros. 

GLB.HIGH Sets alphanumeric values to highest alphanumeric value, and 

numerics to all 9s. 

GLB.MAX Same as GLB.HIGH. 

GLB.LOW Sets all alphanumeric items to lowest alphanumeric value, all 

numericstozero. 

GLB.MIN Sets all alphanumeric items to lowest alphanumeric value, all 

unsigned numerics to zero, and all signed numerics to minus all 

9s. 

In the following logic, the Group Setup Data item SD-MYGROUP is defined, and then the 

INITIALIZE; command is used to set the numeric Setup Data items to zero and the 

alphanumeric Setup Data item to spaces. 

 

 

 

 

 

 

"Types of Data Item" in your LINC Generate Operations Guide. 

1-140 v

INSERT (INS) 

Syntax 

Example 

INSERT (INS) 

The INSERT; command inserts a Global Logic into an Ispec or Report. The INSERT; 

command can also be used to insert a Report into another Report. The inserted Report 

must not contain logic. 

Note: An INSERT; of a Performable Global Logic will not be marked as in error even 

if the Performable Global Logic contains errors. Error checking of Performable 

Global Logics is only performed when the logic is entered. 

Caution 

When inserting one Report into another, duplicate Frame numbers may result in 

severe truncation and overwriting in those Frames. 

In LDA Run Time, Macro Global Logics may not be used with this command. 

Removing the insertion of a Report 

When you remove the INSERT; command that inserts a Report, the inserted Frames still 

appear on the Frame Descriptions screen for the Report, and are listed by the WHFRAMES 

Inquiry mode command. 

DD DDDBDDD DDDDBDDDDDD4 

3 3 

CDDD DDD4 

3 3 

@DDDDDDDDDDDD DDDDDDDDDDDDY 

report 


An existing Report to be inserted into the current Report. If the inserted Report contains 

logic, the logic is not inserted. All Report Frame data and displays are validated, and all of 

the painted Frames are inserted into the current Report. 

 

"Using Global Logics" in your LINC Generate Operations Guide. 

v 1-141

JUMP.TO (JTO) 

JUMP.TO (JTO) 

Syntax 

Examples 

The JUMP.TO; command causes a branch to a point in the logic specified by a LABEL; 

command. Any number of JUMP.TO; commands may refer to one label. 

A loop or a nested loop is terminated by branching out of the loop. 

The following restrictions also apply: 

$ A branch into a loop statement is not permitted. 

$ Branching between different types of logic (Pre-Screen, Pre-LINC or Main logic), is not 

permitted. 

$ A JUMP.TO; command in a Report Frame must have an associated LABEL; command 

in that Frame. Branching between Report Frames is not permitted. 

$ The destination of the JUMP.TO; command cannot be earlier in the logic; that is, you 

can only jump forwards. 

DDDDD DDD DDDDDDDDDDDDDDDDDDDDDDDDDDDD4 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1-142 v


 

 

 

 

 

 

 

 

 

 

 

 

‘‘LABEL (LAB)’’. 

JUMP.TO (JTO) 

v 1-143

KEYONLY 

KEYONLY 

Note: This command option is relevant only to MCP based LINC Systems. It is 

ignored in LDA Run Time and on all other host types. 

The KEYONLY; command option increases the efficiency of LOOK.UP; and DETERMINE; 

commands by limiting data retrieval to data items and Ordinates declared in the Profile 

description only. This eliminates unnecessary I/O operations when other data items are not 

required. 

Key data is stored on a Profile, and includes: 

$ Profile ORDINATE data items 

$ The MAINT System data item in Automaint Profiles and automatic Profiles over 

Standard and Table Components 

$ Profile Data items 

Restrictions and Limitations 

LOOK.UP; retrievals may use the KEYONLY; command option only on Standard and Table 

Components. 

If you reference a non-key data item it will contain the GLB.HIGH value. This is because 

LINC fills the record buffer with GLB.HIGH before the database access is performed. 

Therefore, access to non-key data items, while syntactically valid, may produce unwanted 

results. 

KEYONLY; is ignored for Integrity systems, and is not allowed with: 

$ The SECURE; command option in the same data retrieval command 

$ EXTRACT files 

$ DETERMINE; commands on Ispecs not using Profiles 

$ DETERMINE; TOTAL commands 

$ LOOK.UP; of a direct component 

$ LOOK.UP; EVERY EVENT or memo component 

When CCSVERSION is set, full database record retrieval is always performed, and 

KEYONLY will have no effect. 

The KEYONLY; command option must be included on the same line as the DETERMINE; 

or LOOK.UP; command. 

1-144 v

Syntax 

Example 


Caution 

KEYONLY 

Do not code FLAG; commands to an Ispec (or EVENT) which has been read with 

KEYONLY, as the KEYONLY read does not bring the record into memory. The 

nominal record in memory is the record from the previous non-KEYONLY read. The 

FLAG; command would result in an unexpected record being updated. 

DDDDDDDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD4 

In the following example, you want to validate a supplier name using the Component 

SUPP, with minimal database access. The Ordinate for the Component SUPP contains the 

Supplier name. Your current supplier name is stored in the data item SUPPNAME, which 

has compatible edit characteristics. 

 

 

 


‘‘SECURE’’. 

‘‘SERIAL’’. 

"Understanding the LINC Cycle" in your LINC Generate Operations Guide. 

v 1-145

LABEL (LAB) 

LABEL (LAB) 

Syntax 

Example 


The LABEL; command defines the destination for preceding JUMP.TO; commands. The 

same label name can be used by more than one JUMP.TO; command, but a label must 

follow all JUMP.TO; commands referring to it in the logic. 

The label name is a literal of up to 18 characters. Label names must be unique within the 

frame (for LINC Reports) or within structures (for Ispecs or global logics). 

DDDDD DDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDD4 

 

 

 

 

‘‘JUMP.TO (JTO)’’. 

1-146 v

LEFT.ALIGN (LA) 

Syntax 


The LEFT.ALIGN; command removes leading zeros from a numeric data item and moves 

the result, left-aligned, and without separators, into an alphanumeric data item. Trailing 

decimal zeros are not removed. 

Moving Non-Zero Values 

If the numeric data item is not zero: 

$ The RETAIN.ZERO; command option has no effect. 

$ If the numeric data item is signed and it has a negative value, a leading minus sign is 

output. 

$ The number of decimal digits output is determined by the DECIMALS Data Attribute of 

the numeric data item. Trailing zeros are not removed. 

$ A decimal point character is output before any decimal digits. If a decimal character is 

specified in the LEFT.ALIGN; command, the default decimal character, and any 

DECIMAL.CHAR Data Attribute, are overridden. 

Moving a Zero Value 

If the numeric data item is zero: 

$ Spaces are output if the RETAIN.ZERO; command option is not specified (whether a 

decimal character is also specified or not). 

$ A single zero is output in the leftmost character position if the RETAIN.ZERO; 

command option is specified, provided a decimal character is not also specified. 

$ The specified decimal character is output followed by the number of zeros specified by 

the DECIMALS Data Attribute, if both the RETAIN.ZERO; command option and a 

decimal character are specified in the command. 

Truncation 

If the alphanumeric item does not have sufficient length, truncation is at the right. 

DDD DDDDD DDDDD DDDDDD 

DDDDDDBDDDDDDDDDDDDDDDDBDDDDDDBDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDD4 

3 3 3 3 

@D DY @D DY 

numeric data 

A numeric data item containing the data to be left-aligned. 

v 1-147


Examples 

Example 1 

alphanumeric item 

The receiving alphanumeric data item. If the data item is negative, a leading minus sign will 

be moved to the data item. 

RETAIN.ZERO; 

If specified: 

$ A zero value is output as a single left-aligned zero, provided a decimal character value 

is not specified. 

$ A zero value is output as the decimal character followed by the number of zeros 

specified by the DECIMALS Data Attribute when a decimal character is also specified. 

$ It has no effect with non-zero values. 

If not specified, zero values are output as spaces (whether a decimal character value is 

specified or not). 

A valid abbreviation for RETAIN.ZERO is RZ. 

decimal character 

Only a period or comma is valid. Enclosing parentheses are mandatory. 

This one-character value specifies the decimal point character to be output for numeric 

items with the DECIMALS Data Attribute. This value overrides the DECIMAL.CHAR Data 

Attribute (if any) and the default decimal character entered on the Report or Ispec Options 

screen. 

The following command is included in logic: 

 

Results for various values and attributes of NUMIN are given in the following table. (The 

ALPHOUT value is shown with each blank represented with a small b character.) 

NUMIN Value NUMIN DECIMALS; ALPHOUT (LENGTH; 9) 

724 None 724bbbbbb 

0 None bbbbbbbbb 

0 1ormore bbbbbbbbb 

123.45 2 123.45bbb 

continued 

1-148 v

Example 2 

continued 



123.45 4 123.4500b 

-724 None -724bbbbb 

-123.45 3 -123.450b 

-123.45 6 -123.4500 

-12345.6789 4 -12345.67 


 

Results for non-zero values are as for Example 1. Results for zero values are shown in the 



0 None 0bbbbbbbb 

0 1+ .0bbbbbbb 

Example 3 (With Decimal Character) 


 

Results for whole number values are as for example 1. Results for other values are shown 

in the following table. 


0 None bbbbbbbbb 

0 4 ,0000bbbb 

123.45 2 123,45bbb 

-123.45 3 -123,450b 

0.12 2 ,12bbbbbb 

continued 

v 1-149


continued 


-0.12 3 -,120bbbb 

Example 4 (RZ and a Decimal Character) 


 

Results for whole number values are as for Example 1. Results for other non-zero values 

are as for Example 3. Results for zero values are shown in the following table. 


0 None 0bbbbbbbb 

0 2 ,00bbbbbb 

0 4 ,0000bbbb 

0 8+ ,00000000 

1-150 v

LOAD 

LOAD 

The LOAD; command applies to the Fast Database Load feature on OS 2200 based hosts 

only. 

When you create a Report to run a Fast Load, use the LOAD; command to define how the 

format of your external input file relates to the Ispec into which you are loading your data. 

The Ispec item name is validated to ensure that it is an I/O or Output item. There is no 

validation on the edit type of the input. Loading will occur unless it is rejected by the 

RDMUTL utility. 

Considerations for Using the LOAD; Command 

The following restrictions should be noted in regard to your LOAD; data items: 

$ You must include a LOAD; command for each field of your input file, and associate it 

with the appropriate data item in your target Ispec. For fields that are not to be loaded, 

code the LOAD; command with the length but no data item, which specifies that the 

field is a filler. 

$ LOAD; commands must be in the sequence of the fields on your input file. Each data 

item in your Ispec can be loaded only from a single field defined with the LOAD; 

command. Checks are performed to ensure that no duplicates exist. 

$ The data item can be a System Data item such as GLB-DTIME, MAINT, or ACTMTH. 

GLB-DTIME should be unique across all records in your Ispec. 

$ The current or a future load may fail, or a future reorganization may fail if you load a 

field into records that may not be unique. If the definition does not include a field to be 

loaded into GLB-DTIME, then the load process will append a unique GLB-DTIME field 

to each record of the input file. This will involve preprocessing the file, and appending 

values to the end of each record from where GLB-DTIME will be loaded. 

$ Not every data item in your Ispec needs to be related to the input file. If your input 

contains fields that are not be loaded, you should write a space/zero as the first two 

bytes of the record when creating the input file. When you define the Fast Load options 

for your Report, set the Space/Zero leads each Record field to Y. If you want to 

assign a constant value to a field, you must do this at the time of creating the input file. 

This load process cannot assign constant values other than spaces or zeros to fields. 

$ The loading of numerics is right-aligned. Consult your Relational Data Management 

System (RDMS 2200) Administration Guide for a description of how to prepare a file 

for loading, and the particular requirements of the file, especially where numeric fields 

are to be loaded. 

$ When an alphanumeric item is longer than the data item into which it is being loaded, 

the value of the item will be truncated from the right. 

$ When a numeric item is longer than the data item into which it is being loaded, no 

truncation occurs. This is because RDMSLOAD accepts a wide variety of lengths for 

numeric fields. You must ensure that your numerics fit the size specified in the 

definition of the Ispec being loaded. 

v 1-151

LOAD 

Syntax 

Example 


$ You may not use exponential notation for numeric data. 

DDD DDDD DD DDDBDDDDDDDDDDDDDDDDBDDD4 

3 3 

@DD DDDY 

In this example, you input file is as follows: 

 

 

 

 

To relate to the input file in this example, your LOAD; commands could be as follows. In 

this example, CUST-INITS is not required to be loaded: 

 

 

 

 

"Fast LINC Database Load" in your OS 2200 Based LINC Administration and Operations 

Guide. 

1-152 v

LOOK.UP; (LU;) Commands 


The LOOK.UP; command variants are used to read data into memory from the LINC 

database, without the use of a Profile. 

The particular variant controls the number and manner in which records are read into 

memory. Once a record is in memory, it may be manipulated by your associated logic. All 

Data items of the record are available to the logic (unless, on MCP based LINC Systems, 

the KEYONLY; command option is specified). 

Variants of the LOOK.UP; Command 

The variants of the LOOK.UP; command are summarized in the following table. More 

detailed explanations are given under separate command descriptions for each variant, 

following this general command description. 

Variant Summary of Operation 

LOOK.UP; Reads the single Component record for the specified Ordinate value. 

LOOK.UP; EVERY Creates a loop that reads each record from a Component, Memo 

Component, or the Event dataset. 

LOOK.UP; FROM Creates a loop that reads each record from a Component, starting 

from the specified Ordinate value. 

LOOK.UP; GROUP Creates a loop that reads each record from a Component, between 

specified Ordinate values. The order is specified as part of the 

command. 

Where a loop is created by a variant of the LOOK.UP; command, any logic contained in this 

loop is executed for each record read. An END; or END.EXIT; command must terminate 

the loop. 


In Host LINC 

If a command fails to retrieve any record (that is, no record satisfies the specified criteria), 

all variants of the LOOK.UP; command with one exception, set GLB.STATUS to *****. The 

exception is a single LOOK.UP; command in Ispec logic, which does not set GLB.STATUS. 

If you use the GLB.STATUS; command with a single LOOK.UP; command in Ispec logic, 

then the named data item is set. 

If any record is retrieved, GLB.STATUS is not set by a LOOK.UP; command. GLB.STATUS 

is not set when end-of-file is detected. 

v 1-153


Single record LOOK.UP; commands in Performable Global Logics behave differently 

depending on whether they are inserted in a Report or inserted in an Ispec., where that 

Global Logic attempts to look up a non-existent key. The command sets GLB.STATUS to 

*****, and processing continues from after the LOOK.UP; command. 

The contents of GLB.STATUS should always be checked after a LOOK.UP; command in a 

Report or, if a loop is created, after the END; or END.EXIT; command of that loop. 

The value of GLB.STATUS resulting from the LOOK.UP; command can be directed to 

another data item by using the GLB.STATUS; command. This is especially useful where 

many commands can update GLB.STATUS, or if you want to test the success of a single 

LOOK.UP; command. 

In LDA 

In Ispecs, if a single LOOK.UP; command fails to find a record and the GS; command is not 

included, an error message appears. If the GS; command is included, the error is 

suppressed and the data item referenced by the GS; command is set to *****. 

For other LOOK.UP; command variants, if no record is found, GLB.STATUS is set to *****. 

If the first attempt is successful, GLB.STATUS will not be set in the event of a subsequent 

failure to retrieve a record. It is not set at End-Of-File, for example. 

Always check the contents of GLB.STATUS after a LOOK.UP; command or, if a loop is 

created, after the END; or END.EXIT; command of that loop. 

The new value of GLB.STATUS, resulting from the LOOK.UP; command, can be directed to 

another data item by the GS; command. This is especially useful where many commands 

may set GLB.STATUS. 

In Reports, GLB.STATUS is set to ***** for all variants of the LOOK.UP; command, 

including the single version. 

Logically Deleted Records 

In Ispec logic, logically deleted records are read into memory by a LOOK.UP; command, 

but they are effectively ignored; that is, they are not returned for use by your LINC logic. If, 

however, the last record read by a LOOK.UP; command is logically deleted, it will remain in 

memory after the command . You should test for this situation. See the following example. 

The setting of GLB.STATUS also depends on whether records, although physically present, 

are marked as logically deleted. If every record retrieved by a LOOK.UP; FROM or 

LOOK.UP; EVERY is a logically deleted record, then GLB.STATUS will be set to *****. 

In Report logic, logically deleted records are brought into memory by LOOK.UP; 

commands. You must include specific logic if you want to exclude logically deleted 

records. 

1-154 v

LOOK.UP; Commands for UNIX ORACLE LINC Systems 



For UNIX LINC Systems, on occasion ORACLE may select the wrong index (Profile), 

where the Indexes have identical keys but in a different order. This can have performance 

implications for your UNIX LINC System. This issue and suggested solutions are described 

in your UNIX LINC Administration and Operations Guide. 


‘‘SERIAL’’. 




‘‘DETERMINE; (DT) Commands’’. 

v 1-155

LOOK.UP; (LU) 

LOOK.UP; (LU) 

Syntax 

Examples 


The single LOOK.UP; command variant is used to read a single Standard or Table 

Component record whose Ordinate value matches that contained in a data item. This data 

item must have compatible edit characteristics with the Ordinate. 

The single LOOK.UP command variant does one single read, and does not have an 

associated END; command, END.NO.PRINT command, or END.EXIT; command. 

In Ispec logic, if a LOOK.UP; command fails to find a record and the GLB.STATUS 

command is not included, an automatic error message is returned to the operator and no 

further logic is processed. The System Data item GLB.STATUS is not affected by the single 

LOOK.UP; command variant in Ispec logic. However, if you include the GLB.STATUS; 

command with the LOOK.UP; command, the data item is set to ***** and processing 

continues. 

In Report logic, GLB.STATUS is set to ***** if a record is not found, and execution 

continues. 

DD DD DD DDDDDDDDDDDDD 

DDDDDDBDDDDDDDDDDDBDDDDDDDDBDDDDDDDDDDDDBDDDDDDDDDDDDD4 

3 3 3 3 

@D DY CD D4 

3 3 

@D DY 

A product can have two suppliers. The Component PROD has the following data items: 

 

 

 

The Component SUPP has an Ordinate SUPPLIER. While an entry in PROD of a value for 

SUPPLIER will automatically be validated, SUPPLIER2 must be explicitly validated by 

logic, as follows: 

 

 

 

If no such supplier is found, a system error message is automatically sent to the operator. 


1-156 v



LOOK.UP; (LU) 

v 1-157

LOOK.UP; EVERY 


Syntax 

Examples 

The LOOK.UP; EVERY command is used to read Component, Memo Component, or Event 

records into memory. It sequentially reads every record in the requested Ispec. Each new 

record overwrites the old one. 

For Standard and Table Components, the order in which records are read into memory is 

determined by the value of the Ordinate. For Memo Components and Events, records are 

read in the order of physical storage. This can change with additions and deletions, or 

reorganization. 

LOOK.UP; EVERY EVENT is valid in Report logic only. 

The LOOK.UP; EVERY command creates a loop, and this loop must be terminated by an 

END; or END.EXIT; command, as shown under ‘‘Syntax’’ and ‘‘Examples’’. 

DD DDDDBDDDDD DDDDDDBDD 

3 3 

CDDD DDD4 

3 3 

@DDDDDDDDD DDDDDDDDDDY 

DDDDDDDBDDDDDDDDDDDDDDDBDDDDDBDDDDDDDDDDDDDDDDBDDDD 

3 3 3 3 

@DDD DDDY CDDD DDDD4 

3 3 

@DDD DDDY 

DDDBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDD4 

3 3 

@D DD DY 

The following example finds the tax rate for a taxable amount entered by the user. The 

Component TAX has the Ordinate TAXRANGE and a Data item RATE with the following 

values in four different records. 

TAXRANGE 1 10000 30000 50000 

RATE 0 .15 .25 .35 

The tax rates are to be applied as shown in the following table. 

1-158 v



RANGE 1-9999 10000-29999 30000-49999 50000+ 

RATE 0 .15 .25 .35 

The Event PAY includes the following data items and logic: 

 

 

 

 

 

 

 

 

 

 





v 1-159

LOOK.UP; FROM 

LOOK.UP; FROM 

Syntax 

Examples 


The LOOK.UP; FROM command is used to read records from a Standard, Direct, or Table 

Component into memory, starting from a specified Ordinate value. 

DD DDD DDD DDDD 

DDDDDDBDDDDDDDDDDDDDDDBDDDDDBDDDDDDDDDDDDDDDDBDDDDDD 

3 3 3 3 

@DDD DDDY CDDD DDDD4 

3 3 

@DDD DDDY 

DDDBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDDD4 

3 3 

@D DD DY 

The following is an example of LOOK.UP; FROM in a report. 

 

 

 

 

 

 

 





1-160 v

LOOK.UP; GROUP 

Syntax 


The LOOK.UP; GROUP command is used to read Standard, Direct, or Table Component 

records into memory. It enables the following details to be specified: 

$ The order in which records are retrieved. Use FROM; to read the Component 

Ordinates are read in ascending order, or BACK; to read in reverse order. 

$ The initial record to be retrieved. This is defined by the start value that follows the 

FROM; or BACK; command option. 

$ The final record to be retrieved. This is defined by the end value that follows the 

UNTIL; command option. If the UNTIL; command option is not included, the loop is 

terminated when there are no more records. 

Note: The start and end values should not be altered within a LOOK.UP; 

GROUP loop. 

Caution 

The LOOK.UP; GROUP BACK; command will read at least one record (and lock it, if 

the SECURE; command option is used) to find out if there are any records in the 

specified range. This record will be locked until the end of the transaction. On an 

OS 2200 based LINC System, the lock is applied by page and, in the case of a 

structure containing 10 records only, for example, they will all be locked until the 

end of the transaction. 

The record left in memory is not defined when the loop of a LOOK.UP; GROUP command 

terminates automatically. The record will differ depending upon the type of host on which 

the LINC System is running. The current record will remain in memory following a BREAK; 

or JUMP.TO; command. 

DD DD DBD DBD DDD 

3 3 

@D DY 

DDDDBDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDBDDDDDDDDDDDDBDDDDDDDDDD 

3 3 3 3 

@D DD DDY @DD DY 

DDDDBDDDDDDDDDDDDDBDDDDBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDD4 

3 3 3 3 

CDD DD4 @D DD DY 

3 3 

@DD DY 

start value 

A data item containing the starting value. 

v 1-161


Example 

end value 


A data item containing the ending value. 

The following example shows a LOOK.UP; GROUP command in a Report. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

In this example, the LOOK.UP; GROUP will read CUST Component records in ascending 

order. The first record read will be the first record with an Ordinate equal to or greater 

than the value of STARTCUST. The loop will terminate after an Ordinate with a value equal 

to or greater than ENDCUST is read, or if there are no records within the specified values. 

If no record in the specified range is found, the Setup Data item SD-STATUS is set to *****. 





1-162 v

LOWER.CASE (LC) 

Syntax 



The LOWER.CASE; command enables you to convert the value of an alphanumeric data 

item to lowercase. The characters A through Z are converted to a through z respectively. 

Embedded digits or non-alphabet characters are unchanged. 

Data items used in LOWER.CASE; commands cannot exceed 2000 characters. 

This command will use the appropriate CCS Version routines if they are available. 

Note: OS 2200 based LINC Systems support only the US English ASCII character set. 

UNIX and MCP based character conversions use standard system utilities. 

DDD DDD DDDDDDDDDDDDDDDDDDDD4 

data item 

An alphanumeric data item, Setup Data item, or Global Setup Data item (including Group 

Setup Data items and Group Global Setup Data items). It is not valid for literals. 

‘‘UPPER.CASE (UC)’’. 

v 1-163

MATCH 

MATCH 

The MATCH; command is used in Report logic to compare two Extract files. The Extract 

files are read in a similar manner to that for a DETERMINE; ACTUAL command, but using 

two files instead of one. These files may either be read simultaneously, or one file may be 

read repeatedly until the user-defined keys in that file match up with the keys in the other 

file. 

The end of a MATCH; command loop is defined by an END; command, END.EXIT; 

command, or END.NO.PRINT; command. 

If the KEY; command option is not used, a record from each file is read until GLB.MATCH 

does not equal spaces. GLB.MATCH can be set in one of two ways: 

$ End-Of-File is reached on one of the files. 

Note: In an OS 2200 based LINC System at runtime, when the MATCH; 

command encounters the End-of-file, the last record read for that file 

is not available in the buffer. References to that record and its data 

item will return a value of spaces. This is different from UNIX and 

MCP environments, where the last record is available. 

$ You explicitly set GLB.MATCH within your LINC logic. 

The MATCH; command updates the System Data item GLB.STATUS. 

When MATCH; commands are executed at runtime, Extract file handling is similar to that 

for DETERMINE; ACTUAL commands. For more details, see ‘‘Extract File Processing’’ 

earlier in this section. 

Recovery of a Report containing MATCH; command logic can be coded similarly to 

recovery when using DETERMINE; ACTUAL commands. 

Restrictions on the MATCH; Command 

$ You must ensure that the Extract files are fully defined within an EXTRACT; 

DETERMINE; ACTUAL or SET.TITLE; command, as required. 

$ Within a MATCH; loop, the results of using a DETERMINE; ACTUAL or EXTRACT; 

command on the same files as those being matched are unpredictable, and therefore 

the use of both commands on the same files is not recommended. 

$ The CRITICAL.POINT; and RESTART; commands are invalid within the MATCH; loop. 

$ Nesting of MATCH; commands is invalid. 

$ You cannot MATCH; an Extract file with itself. 

$ There are differences between host types in the way database numeric items are 

defined in COBOL. If you use the KEY; command option to match a database numeric 

data item with a Frame numeric data item, the COBOL definitions of the numeric items 

may not be compatible if the Extract files you are comparing were not created using 

LINC or if the files being compared were created on different host types. 

1-164 v

Syntax 

MATCH; Command 

DD DD DBDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBD 

3 3 

@D DD DY 

DDDDDDDDDD DBDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDD4 

3 3 

@D DD DY 

extract file 1 

An Extract file name (A to Z) that you wish to match to a second Extract file. 

data name 1 

An optional data item or literal giving an Ispec name or Frame number that the first 

Extract file is extracted as. 

extract file 2 

A second Extract file name (A to Z) that you wish to match with the first Extract file. 

data name 2 

MATCH 

An optional data item or literal giving an Ispec name or Frame number that the second 

Extract file is extracted as. 

KEY; Command Option 

DDD DD DD DBDDDDDDDDDDDDDDBDDDD4 

3 3 

CD D4 

3 3 

@D Y 

data name 3 

The key in the first Extract file. This data item must be the same edit type as data name 4. 

data name 4 

The key in the second Extract file. This data item must be the same edit type as 

data name 3. 

Note: If you specify the KEY; command option, it must follow the MATCH; command 

with no logic (other than comments or blank lines) between the MATCH; 

command and its KEY; option. 

v 1-165

MATCH 

KEY; Command Option 

Example 1 

Use the KEY; command option to specify the keys to be used in the MATCH; command to 

compare two Extract files, and to control the sequence that sorted files are read in. If the 

KEY; command option is used, GLB.MATCH can be set in one of three ways: 

$ End-Of-File is reached in one of the files. 

$ The key values mismatch. 

$ You explicitly set GLB.MATCH within your logic. 

If the keys are not equal, GLB.MATCH is set to the name of the file that is to be read on the 

next iteration. This depends on the use of the ASCENDING; and DESCENDING; command 

options. 

The default for the KEY; command option is ascending. If the KEY; command order is 

ascending and the KEY; values are not the same, GLB.MATCH will be set to the file name 

of the lower KEY; value. Descending is the converse of ascending. 

If you specify the KEY; command option, it must follow the MATCH; command with no 

logic (other than comments or blank lines) between the MATCH; command and its KEY; 

command option. 

In this example, consider the following two Extract files: 

 

 

 

 

 

 

 

If KEY; is not specified, as in the logic: 

 

 

 

 

 

Then the following occurs: 

 

 

 

 

1-166 v

Example 2 


MATCH 

In this example, the same two Extract files as in Example 1 (A and B) are matched. The 

key for the comparison is the Customer name. 

If A*NAME and B*NAME are set as keys: 

 

 

 

 

 

 

Then the following occurs: 

 

 

 

 

 

 

‘‘GLB.MATCH’’. 

‘‘DETERMINE; ACTUAL’’, ‘‘EXTRACT (EX)’’, and ‘‘SET.TITLE (SETT)’’. 

The subsections on Extract Files and MAPPER Extract Files in "Interfacing to Other 

Systems" in your LINC Administration and Operations Guide for the relevant host type. 

v 1-167

MESSAGE (ME) 

MESSAGE (ME) 

The MESSAGE; command sends a message from Ispec or Report logic to the screen (or to 

a PRINT$ file if from an OS 2200 based Report). 

The MESSAGE; command sets GLB.ERROR to ***** in Ispec logic, but not in Report logic. 

Parts of a Message 

A message consists of two parts: 

$ A value. This can be a data item or the words ERROR or ATTENTION. It is displayed 

in reverse video, and will be truncated to a length of 16 characters. 

Signed numeric data values are displayed left-aligned with leading zeros suppressed. 

Decimals are displayed, and negative values are followed by a minus sign. 

$ Associated text. This text can be a literal or data item containing a value of up to 50 

characters. Due to a COBOL restriction, the double-quote character requires two 

character positions. Global Setup Data items can be used to hold messages, which can 

be stored in multiple languages. A numeric value in the text area will be syntaxed as an 

error. 

Note: When the MESSAGE; command is used in Reports, no truncation of the value is 

done, but the combined message is truncated to 80 characters. 

How Messages are Displayed 

If only one message is to be displayed, it appears on the status line at the bottom of Page 1. 

(On OS 2200 based LINC Systems, the first character of the message must not be a slash (/) 

character.) If two or more messages are invoked, they will appear on Page 2 (or Page 3 for 

UNIX and OS 2200 based LINC Systems) of the terminal. 

For LDA, if only one message is to be displayed, it appears on the status line. If two or 

more messages are invoked, they appear in a dialog box and a message is displayed on the 

status line indicating there are multiple messages. 

Multiple messages are displayed on MCP based LINC Systems and in LDA in reverse order 

to which they are coded, but on OS 2200 based and UNIX LINC they are displayed in the 

order specified on the System Environment Options screen. 

For UNIX and OS 2200 based LINC Systems, there is a limit of how many messages are 

displayed (22 messages for UNIX and 19 messages for OS 2200 based). When this limit is 

exceeded, an error message is produced. 

Messages sent from an unattached Report are not returned to the screen. 

Note: Messages queued from the MESSAGE; command take priority over any Teach 

screen currently displayed on Page 2. 

1-168 v

OLTP 

MESSAGE (ME) 



v 1-169

MESSAGE (ME) 

Using MESSAGE; in OS 2200 based LINC Systems 

Syntax 

Message Locations 

For OS 2200 based LINC Systems, the possible locations for a message destination are: 

$ The TIP terminal that initiated the transaction (Ispec). 

$ The TIP terminal attached to a Report (see the RUN; command for details about the 

significance of attached Reports). 

$ The PRINT$ file associated with the DEMAND terminal from which an unattached 

Report was submitted through @XQT. 

$ The PRINT$ file associated with the BATCH run from which an unattached Report 

was submitted through @XQT. 

$ An operator’s console, for a Report submitted from DEMAND or BATCH using 

@XQT,C. 

For more details of OS 2200 based LINC Report operations, see your OS 2200 Based LINC 

Administration and Operations Guide and OS 2200 Based LINC Installation and 

Configuration Guide. 

Avoiding the Loss of Messages 

On OS 2200 based LINC Systems, if a Report is coded with a large group of MESSAGE; 

commands one after the other, the network CMS queues them up. When the limit is 

reached, the messages are discarded and not sent to the user terminal. To avoid this 

problem, code a SLEEP; command between each MESSAGE; command. 

DDD DDBDD DDBDD DDDDDDDDDDD4 

3 3 

CDDDDD DDDDD4 

3 3 

@DDD DDDY 

data item 1 

A data item whose contents are displayed in reverse video before the message text, as an 

alternative to either ERROR or ATTENTION. 

data item 2 

An alphanumeric data item (or literal) containing the text of the message. 

1-170 v

Examples 


MESSAGE (ME) 

In the following example, three message lines are displayed if the tested condition is TRUE. 

 

 

 

 

 

The following example shows that a literal message does not have to be supplied with the 

MESSAGE; command. 

 

 

 

‘‘SEND.MESSAGE (SEND.STATUS; SM; SMSG; SS)’’, and ‘‘GLB.ERROR’’. 

‘‘BEGIN.EDIT and END.EDIT’’ for details of the function of the MESSAGE; command in a 

Copy.From Ispec. 



v 1-171

MOVE (MV) 

MOVE (MV) 

MOVE; commands are used for data manipulation. 

There are two forms of the MOVE; command: 

$ The simple form copies the value of a data item directly to that of another. 

$ The complex form enables the values of two data items to be manipulated, to give a 

new result. For an MCP based LINC System, LINC replaces leading zeros in numeric 

data items with decimals with a space, so that larger values cannot be moved back into 

the field. 

Note: In LINC Logic it is possible to code MOVE; commands that will produce 

inconsistent or unexpected results. These commands are known as overlapping 

moves. You can check for overlapping moves by using the LINC Checker Utility 

(CHK) in LINC Generate. See your LINC Generate Operations Guide for details. 

These commands and variants are described in more detail in the following subsections. 

Simple Form of the MOVE; Command 

The simple form copies the value of a data item directly to that of another. Alphanumeric 

values may not be moved into numeric data items that have decimals declared, or vice 

versa. Due to a COBOL compiler restriction, an alphanumeric data item greater than length 

23 cannot be moved to a numeric or signed data item. 

For alphanumeric data, the move is left-aligned. The result is blank filled from the right or 

truncated, if necessary. 

For numeric data, the move is right-aligned, according to the position of the decimal point. 

Extra decimals are truncated, not rounded. The result is zero-filled from the left or 

truncated from the leftmost significant digit as necessary, without warning. 

When moving a Group data item to or from another Group data item, the field will be 

left-aligned. 

A signed numeric data value will lose its sign if it is moved into an EDIT; N data item. 








1-172 v

Syntax 

Examples 

DDDD DDDDD DDDDD DDDDDD4 

data name 2 

The receiving data item (you cannot specify a literal). 

The following example shows a simple MOVE command. 

 

 

 

 

 

The following example shows a MOVE; of a GROUP data item. 

 

 

 

 

 

 

 

 

 

 

This logic sets TIMEW to 200402 and RECEPTW to 20040200. 

Complex Form of the MOVE; Command 

MOVE (MV) 

The complex form of the MOVE; command enables the values of two data items to be 

manipulated to give a new result. It has no effect on the contents of the first data item. 

Values of different edit characteristics can be missed, although the sign of the first data 

item is not moved. Due to a COBOL compiler restriction, an alphanumeric data item 

greater than length 23 cannot be moved to a numeric or signed data item. 








There are two variants of the complex MOVE; command: direct and sorted. 

v 1-173

MOVE (MV) 

Direct 

In this variant, characters are taken from the first data item, starting at a specified position 

and continuing for a specified length. The characters are moved into the second data item, 

starting at a specified position, overwriting the current characters. Characters not 

overwritten are retained. 

Sorted 

This variant is indicated by specifying either the SORTA; (ascending) or SORTD; 

(descending) command option. 

A group of characters is taken from the first data item, starting at a specified position and 

continuing for a specified length. This group of characters is inserted into the second data 

item. The position of the insertion is determined by grouping characters in the second data 

item into groups (the same size as the group from the first data item), and then comparing 

the group to be inserted with each group in the second data item. 

The size of the value of the second data item increases with each MOVE; command. 

Truncation may occur if the value exceeds the length of the second data item. If the last 

right-hand significant group of figures do not have their position changed, truncation will 

not take place. 

Spaces are not sorted. 

Setting GLB.STATUS 

The MOVE; command is validated if any of the following situations apply: 

$ The Def bounds checking field on the Primary Specification Options screen is set to 

Y. 

When this field is set to N, error checking code is not generated, so a check for errors 

will not occur. This means that if a complex move is performed that is out of bounds of 

the receiving data item, that data item may contain unpredictable results. 

$ The GLB.STATUS; command is included in the MOVE; command. 

$ The sorted variant of the MOVE; command is used. 

If validation is in effect, it proceeds as follows. 

$ If an invalid MOVE; command is attempted, ***** is moved to the System Data item 

GLB.STATUS, and the move is not performed. 

$ If truncation occurs, GLB.STATUS is not usually set to *****. However, if a group of 

characters in a sorted complex MOVE; command is appended to the second data item 

and would be truncated, GLB.STATUS is set to ***** and the move is not performed. 

1-174 v

Syntax 

DBD DBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDD 

3 3 3 

3 @D DD DY 

3 

@DDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD 

DDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDD 

3 3 

@D DD DY 

DD DBDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDD4 

3 3 

CDD DD DD4 

3 3 

CDD DDDDDDDDDDDDDDDDDD4 

3 3 

@DD DDDDDDDDDDDDDDDDDDY 

data item 1 

You can use GLB.SPACES or GLB.ZEROS as the source field in a complex MOVE; 

command of the form: 

 

This results in one space character being placed in position n of data item 2. 

You can also specify GLB.LOW, GLB.HIGH, or GLB.SPACES. 

MOVE (MV) 

Note: The length of GLB.LOW, GLB.HIGH, GLB.SPACES, and GLB.ZEROS defaults to 

1 in complex MOVE; commands. 

POS; numeric data 1 

The numeric data item (or literal) must not include decimals. A literal value must be 

enclosed in parentheses. The default position is 1. 

Do not specify any of the System Data items GLB.SPACES, GLB.ZEROS, GLB.HIGH, or 

GLB.LOW as the numeric data 1 value. 

POSITION and PO are valid synonyms for POS. 

POS; numeric data 3 

The numeric data item (or literal) must not include decimals. A literal value must be 

enclosed in parentheses. The default position is 1. 

POSITION and PO are valid synonyms for POS. 

LENGTH; numeric data 2 

The numeric data item (or literal) numeric data 2 must not include decimals. A literal 

value must be enclosed in parentheses. 

v 1-175

MOVE (MV) 

Examples 


The default length is the length of data item 1. 

LE is a valid synonym for LENGTH. 

At the end of the following example of the complex MOVE; command, if ACTMTH has a 

value of 9803, then the Setup Data items MY-MONTH and MY-DATE will have values of 03 

and 000300, respectively. 

 

 

 

 

The following example of the complex MOVE; command uses the SORTA; command 

option. 

 

 

 

 

 

 

 

 

 

 

 

Two characters are moved each time the MOVE; command in the loop is executed. First, 

QW is moved, followed by ER. ER is before QW when sorted in ascending order, so the 

result is ERQW. TY is moved next, giving ERQWTY. The final result is 

ASDFERGHJKLZNMOPQWTYUIVBXC. 

The following lines of logic have invalid syntax. 

 

 

In the first line, the LE; command option is not allowed with a literal. In the second, the 

POS; command option is not allowed with GLB.SPACES. 

‘‘GLB.STATUS (GS)’’ 

LINC Programming Reference Manual for the lengths of System Data items. 

1-176 v

MOVE.ARRAY (MVA) 

Syntax 


The MOVE.ARRAY; command moves a Setup Data array or Global Setup Data array in a 

single operation. You can use this command to save the contents of an entire array (in an 

alphanumeric data item), and restore it later. This would enable you to store the contents 

of an array in Global Work and restore it, across transactions. 

The following moves are possible: 

$ Array to an array. 

On OS 2200 based LINC Systems, this is the only valid move if the values are EDIT; K 

(the values are moved as if they are a standard alphanumeric data items). 

$ Array to a data item. 

$ Non-array data item (or literal) to an array. 

If the data item is a database data item, it must be alphanumeric. 

Restrictions 

$ The definition of sending and receiving arrays must be similar if the values are to be 

preserved. 

In numeric arrays, individual items are defined as COBOL COMPUTATIONAL fields. If 

you move a numeric data item or numeric literal to an array, or move a numeric array 

to anything other than an identically defined numeric array, the result may be invalid 

for use in either computation or display. In LDA, this restriction does not apply if the 

literal being moved matches the defined numeric array. LDA users should avoid 

writing logic that relies on this capability to maintain compatibility. 

$ You cannot use this command to move entire Data arrays, although you may move an 

array to an EDIT; A data item in a Data array. 

$ If you move a mixed alphanumeric and Hankaku-Katakana value into an EDIT; W data 


data item. However, if you move a mixed alphanumeric and Hankaku-Katakana value 

into an EDIT; A data item, the value is moved byte by byte and is truncated to the 

length of the data item. If the truncation occurs after the first byte of a double-byte 

Hankaku-Katakana character, this will result in an invalid character. 


DD DDBDD DDDBDDD DDDBDDDDDDD4 

3 3 3 

3 @D D4 

3 3 

@DD DDD DDDY 

array 1 

A Setup Data array or Global Setup Data array. 

v 1-177


Examples 

array 2 

A receiving Setup Data array or Global Setup Data array. 

array 3 

A receiving Setup Data array or Global Setup Data array. 

data item 1 

A receiving alphanumeric data item. A literal is not valid. 

 

 

 

 

Values of SD-ARRAY after the last MOVE.ARRAY; command in this example are shown in 

the following table. 

SD-IND1 SD-IND2 Value 

1 1 A 

1 2 B 

2 1 C 

2 2 D 

1-178 v

MOVE.AUTO (MA), MOVE.AUTO.ARRAY (MAA) 

MOVE.AUTO (MA) and MOVE.AUTO.ARRAY (MAA) 

The MOVE.AUTO; command moves data from the Auto Entry buffer to a data item in the 

originating LINC System. 

The MOVE.AUTO; command is the converse of the AUTO; command. It is used with 

external Automatic Entries to retrieve data from the Auto Entry buffer. 

Following an external AUTO.ENTRY, if the Ispec in the receiving LINC System has a 

RECALL; command that is invoked by the receipt of data, the recall information is 

returned to the Auto Entry buffer of the sending LINC System. If the AUTO; WRITE 

command is successful, GLB.STATUS in the originating LINC System contains the value 

DATA. The data returned to the Auto Entry buffer can be retrieved by using the 

MOVE.AUTO; and MOVE.AUTO.ARRAY; commands. 

In LDA Run Time, external Automatic Entries are not supported. The MOVE.AUTO; and 

MOVE.AUTO.ARRAY; commands are ignored. 

An AUTO; WRITE&CLEAR command will not clear the buffer when data is being returned. 

Restrictions 

The same restrictions apply to MOVE.AUTO; command as to the AUTO; command. You 

cannot send an alphanumeric item to a numeric item with decimals or to a signed numeric 

item or vice versa. 






character, this will result in an invalid character. However truncation does not occur if you 

move such a value into an EDIT; W Setup Data array (or Global Setup Data array). 


Numeric Setup Data array items are implemented as COBOL COMPUTATIONAL fields. A 

move from a numeric array to anything other than an identically defined numeric array 

may result in data that is invalid for use in either computation or display. 

MOVE.AUTO.ARRAY; 

The MOVE.AUTO.ARRAY; command moves the value of a data item from the Auto Entry 

buffer to a Setup or Global Setup Data array. Otherwise, its function is the same as the 

MOVE.AUTO; command. 

OLTP 

For OLTP, the response in the AUTO buffer may use a different buffer description than the 

one in your original request. There is no validation that the data present matches the data 

format expected by your logic. To specify the correct format, use the AUTO.FORMAT; 

LINC logic command immediately before the relevant MOVE.AUTO commands. 

v 1-179


Syntax 

For more details of interdatabase communication, see the LINC Operations Guide for the 

relevant host type. For more details of OLTP, see your LINC Generate Operations Guide. 

DDD DDD DDD DDDDD4 

DDD DD DD DDDDDDDDD4 

data item 1 

A data item that is not Usage Input or Usage Inquiry. 

data item 2 

The receiving data item. 

data item 


array 

Examples 


MOVE.AUTO; Command Example 

As well as giving an example of this command, this example shows how to use an 

Automatic Entry Memo Component to access another database. 

A LINC System called PRODUCTS has an Auto Entry Component PROD that has the 

following data items and logic: 

 

 

 

 

 

 

A second LINC System called SELLING also has a Component PROD defined in the same 

way as in the PRODUCTS System. The actual data for PROD is stored in the PRODUCTS 

System. 

1-180 v


The SELLING System also includes an Auto Entry Memo Component PRODM which is 

used for product inquiries and maintenance on the PRODUCTS System. PRODM has the 

following Data items and logic, which enables the relevant detail for PROD to be accessed 

from the PRODUCTS system database and displayed. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

MOVE.AUTO.ARRAY; Command Example 

The Ispec FIRUP receives data, using an Automatic Entry from an Ispec in another LINC 

System. The data is placed in the Auto Entry buffer for FIRUP. FIRUP includes the 

following lines of logic: 

 

 

When using the MOVE.AUTO.ARRAY; command to move a numeric array from an OLTP 

View Ispec buffer to a numeric Setup Data array, the individual numeric array elements are 

moved to the corresponding element in the OLTP View buffer. 

v 1-181



‘‘AUTO; CONTRA’’, ‘‘AUTO.FORMAT (AF)’’, and ‘‘AUTO; WRITE and AUTO; 

WRITE&CLEAR’’. 

The System Data items ‘‘GLB.DESTINATION’’, ‘‘GLB.DESTENV’’, ‘‘GLB.DESTHOST’’, 

‘‘GLB.HUBSTATUS’’, ‘‘GLB.HUBTIMEOUT’’, ‘‘GLB.OLTPTYPE’’, ‘‘GLB.OLTPSUBTYPE’’, 

‘‘GLB.OLTPSERVICE’’, and ‘‘GLB.OLTPVALUE’’. 


The Interfaces section in your LINC Administration and Operations Guide for the 

relevant host type. 

1-182 v

MOVE.DATE (MD) 

Syntax 


MOVE.DATE (MD) 

The MOVE.DATE; command obtains the current date (or the debug date if debug date and 

time is activated), and returns the result as a numeric value, in a format you can specify. By 

default the form is YYMMDD (where YY is the year, MM is the month, and DD the day). 

The date at which the Ispec or Report was initiated (or the last SLEEP; or 

CRITICAL.POINT; command was executed) is available in the System Data item 

GLB.DATE. 

DD D DBDDDDDDDDDDDDDDDDDDDBDD4 

3 3 

@D DY 

numeric data 

A numeric data item, of length 6 or 8, without decimals. 

FORMAT; format 

Specifies the format of the value. The value of format is one of: 

$ CCYYMMDD 

$ YYMMDD (default) 

$ DDMMCCYY 

$ DDMMYY 

$ MMDDCCYY 

$ MMDDYY 

Note: GLB.DC- System Data items are not affected by this command. 

‘‘GLB.DATE’’. 

"Debug Date and Time Commands" in your MCP Based LINC Administration and 


v 1-183

MOVE.TIME (MT) 

MOVE.TIME (MT) 

Syntax 


The MOVE.TIME; command obtains the current time, or the debug time if debug date and 

time is activated. (The time (or the last SLEEP; or CRITICAL.POINT; command) at which 

the Ispec or Report was initiated is available in the System Data item GLB.TIME.) 

The result is returned, in twenty-four hour format, in the form HHMMSShh (where HH is 

hours, MM is minutes, SS is seconds, and hh is hundredths of seconds). 

DD DDDDDDDD DDDDDDDDDDDDDD4 


A numeric data item, of length 8, without decimals. 

‘‘GLB.TIME’’. 

"Debug Date and Time Commands" in your MCP Based LINC Administration and 


1-184 v

MULTI 

Syntax 


MULTI 

Note: This command option is relevant only to 2200 Series target hosts. It is ignored 

on other host types. 

MULTI; is not a full logic command. It is a command option that can be specified with a 

DETERMINE; or LOOK.UP; command only, to enable the reading of ranges of records. 

This command option may be used with all variants except: 

$ DETERMINE; LAST command 

$ DETERMINE; ACTUAL command with the EXTRACTED.AS; option 

$ Single LOOK.UP; command 

This command option is placed after all the other options, and before the GLB.STATUS; 

command. 

DDDD DDDDDD DDDDDDDDDDD4 

numeric data 

A numeric data item or numeric literal which is the number of records to be retrieved by 

RDMS into its multiple record buffer. 

This value should not be greater than the maximum set in your Environmental or Bulk 

Options screens, although the values is not checked until execution time. If the value is 

greater than the maximum, the specified maximum value is used. 

‘‘LOOK.UP; (LU;) Commands’’ and ‘‘DETERMINE; (DT) Commands’’. 

v 1-185

MULTIPLY (MU) 

MULTIPLY (MU) 

Syntax 

Examples 


The MULTIPLY; command multiplies the value of a numeric data item by that of a second 

numeric data item, and stores the result in the second data item; or in a third data item, if 

one is explicitly given. 

The GIVING; and ROUNDED; command options may be applied in conjunction with the 

MULTIPLY; command. 

The System Data item GLB.STATUS is not updated to ***** by the MULTIPLY; command. 

Use the GLB.STATUS; command (in LDA, the GS; command) to test for arithmetic 

overflow. 

DD DDD DDD DDDDDDDD 

DDBDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDBDDDDDDDDDDDDDDBDDD4 

3 3 3 3 

@DD DD DDY @DD DDY 


A data item or literal to be multiplied. 


A data item or literal to be multiplied. This data item will contain the result if GIVING; is 

not specified. A literal is therefore valid only if the GIVING; command option is used. 



command option must be on the same line as the MULTIPLY; command. GIV is a valid 

abbreviation for GIVING. Thenumeric data 3 item cannot be a literal. 

ROUNDED; 

Rounds the result when truncation occurs. 

 

 

 


1-186 v

ON.CHANGE (OCH) 


The ON.CHANGE; command is used to specify control breaks in Reports. A footer and 

(optionally) a heading are invoked whenever the value of the controlling data item 

changes. This data item can be any Report data item, including an item in the database, or 

a Setup Data item. 

Footers and headings are Report Frames. Typically, a footer prints a summary, such as 

subtotals. A heading usually prints a title corresponding to the new value of the data item, 

and it can be used to initialize Setup Data items associated with the Report. 

The ON.CHANGE; command can be used only within a loop in the Main logic of a Report 

and is not supported with sleeping reports. 

The heading is invoked before the first record, and the footer is invoked after the last 

record. The final footer is printed immediately after the end of all the current loops, and 

before any following logic. 

The System Data item GLB.CHANGE holds the name of the data item whose value has 

changed. GLB.CHANGE contains spaces until a change in value occurs. 

The ON.CHANGE; command can be used in association with standard statistical routines. 

For more details, see ‘‘ON.CHANGE; Statistical Routines’’, later in this section. 

Values of Data items 

After a change of value, data items in the footer are from the old LINC database record 

(the record with the old value of the control data item). However, logic references to LINC 

database items (for example, CUST.NAME) access the new record (the record with the 

new value of the control data item). Also, this means that any Frames called from the 

footer use the new value. 

To get the new value into the footer, move the value into the specified data item after the 

relevant database access command (for example, LOOK.UP; or DETERMINE;). 

All database items used within the heading are taken from the new database record. 

Grouping ON.CHANGE; Commands 

Multiple ON.CHANGE; commands may be grouped to form a hierarchy of control breaks 

(for example, customer within branch). If multiple ON.CHANGE; commands are used, they 

must be grouped together. Such a hierarchy may be up to nine levels deep. Only one such 

group may occur within a Report. 

When multiple levels of control breaks are specified, the hierarchy of levels is given by the 

order in which the commands are coded. The first is the highest level (associated with the 

first heading and the last footer). 

v 1-187


Syntax 

Example 

DDD DDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDD 

DDD DDD DDDBDDDDDDDDDDDDDDDDDBDDDBDDDD4 

3 3 3 

@D DD DY @DDD 

DDD DDD DDDBDDDDDDDDDDDDDDDDDBDDDDDDDD4 

3 3 

@D DD DY 

FOOTING; foot frame 

Specifies the Report Frame to be the footer. FTG is a valid abbreviation for FOOTING. 

HEADING; head frame 

Specifies the Report heading Frame. HDG is a valid abbreviation for HEADING. 

line 1 

The line number where you require the Report heading to start. 

line 2 

The line number where you require the Report footing to start. 

 

 

 

 

 

This will result in the Frames being invoked in the following sequence: 

Frame Comment GLB.CHANGE is 

1 Branch heading 

2 Customer heading 

3 Multiple customer account records until 

CUST.CUSTNO or CUSTBRANCH changes 

4 Customer Summary CUST.CUSTNO 

2 Customer Heading 

3 Multiple customer account records until 

CUST.BRANCH changes 

continued 

1-188 v


continued 


Frame Comment GLB.CHANGE is 

4 Customer summary CUST.CUSTNO 

5 Branch summary CUST.BRANCH 

1 Branch heading CUST.BRANCH 

2 Customer heading CUST.CUSTNO 

3 Multiple customer account records ... 

... and so on ... 

‘‘ON.CHANGE; Statistical Routines’’. 

‘‘GLB.CHANGE’’. 

ON.CHANGE; Statistical Routines 

Standard statistical routines are available in association with the ON.CHANGE; command 

in Report main logic. 

Calculations are based on the values of a source data item at each iteration of the loop 

containing the ON.CHANGE; command, and on the number of iterations. 

The result of the statistical routine is stored in a numeric data item, and can be accessed in 

the footer. This data item will usually be included in the Frame, although this is not 

compulsory. If the item is not part of the Frame, set its value to zero or spaces in the logic 

of the Frame. 

Statistical Routines must immediately follow the related ON.CHANGE; command they 

qualify. 

The following table summarizes the statistical routines and their abbreviations. 

Routine Name Abbreviation Description 

COUNT; CNT; Number of values (iterations) 

SUM; Sum of the values 

AVERAGE; AVG; MEAN; Average of the values 

MAXIMUM; MAX; Largest value 

continued 

v 1-189


continued 

Routine Name Abbreviation Description 

MINIMUM; MIN; Smallest value 

SUM.SQUARES; SSQ; Sum of the squares of the values 

MEAN.SQUARES; MSQ; Average of the squares of the values 

VARIANCE; VAR; Variance of the values 

STD.DEVIATION; STD; Standard deviation of the values 

When using the ON.CHANGE; statistical routines, internal working storage variables are 

generated in the Report where necessary, to store the intermediate values for some of the 

calculations. 

These variables are of a fixed size. If the magnitude of the data used when running the 

Report exceeds this size, runtime calculation errors can occur. The internal variable 

number and usage are shown in the following table. 

Routine Name Routine Number Used to Store the ... 

MAXIMUM; 1 Maximum value found 

MINIMUM 2 Minimum value found 

VARIANCE; 3 Sum of the squares of the data 

4 Sum of the data 

5 Count of the data items 

STD.DEVIATION; 6 Sum of the squares of the data 

7 Sum of the data 

8 Count of the data items 

AVERAGE; 9 Count of the data items 

MEAN.SQUARES; 10 Count of the data items 

These internal variable routine numbers listed in the above table and the variable size for 

each host are shown in the following table. 

1-190 v

Syntax 

Number MCP based COBOL 

Definition 

OS 2200 based 

COBOL Definition 


UNIX COBOL Definition 

1 PIC 9(12)V9(6) PIC 9(12)V9(6) PIC 9(12)V9(6) 

2 PIC 9(12)V9(6) PIC 9(12)V9(6) PIC 9(12)V9(6) 

3 PIC 9(14)V9(9) USAGE COMP-2 PIC 9(12)V9(6) 

4 PIC 9(12)V9(6) PIC 9(12)V9(6) PIC 9(12)V9(6) 

5 PIC 9(10) PIC 9(10) PIC 9(10) 

6 PIC 9(14)V9(9) USAGE COMP-2 PIC 9(12)V9(6) 

7 PIC 9(12)V9(6) PIC 9(12)V9(6) PIC 9(12)V9(6) 

8 PIC 9(10) PIC 9(10) PIC 9(10) 

9 PIC 9(10) PIC 9(10) PIC 9(10) 

10 PIC 9(10) PIC 9(10) PIC 9(10) 

In all other routines, the resultant item declared in the command is also used as an 

intermediate variable. 

DDD DDDD DDDD DD DDD4 

routine 

The name of the On Change Statistical routine you choose to use, or its abbreviation, as 

shown in the first table in the previous subsection. 

source 

The data item used by the Statistical routine as the basis of its computation. 

GIVING; numeric item 

The GIVING; command option directs the result to the specified data item. GIV is a valid 

abbreviation for GIVING. 

v 1-191

OTHERWISE (OW) 

Examples 


An Employee listing by Job type within Department, giving the numbers of persons, 

average salary, and standard deviation of salary, could be expressed as follows: 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

‘‘ON.CHANGE (OCH)’’. 

OTHERWISE (OW) 

For details of this command, see ‘‘CASE (CS)’’. 

1-192 v

PAGE (PG) 

Syntax 

Example 

PAGE (PG) 

The PAGE; command is available only for MCP based LINC Systems. It is valid, but ignored 

on all other host types and in LDA Run Time. 

The PAGE; command enables you to send a string of information to a specific screen page 

of the current station (terminal). This leaves you out of forms mode. 

The PAGE; command can be used only in Ispecs. 

The PAGE; command output is sent immediately (casual output), and does not wait for the 

end of the current transaction. Multiple PAGE; commands to the same page within the 

same transaction overwrite each other. 


DDD DDDDDDD DDDDDD DDDDDD4 

page number 

This value specifies the destination page of the text. This number cannot be in parentheses, 

and if it is any value other than 0, or 2 through 5, is syntax checked by the editor. 

If the page number value is in the range 2 through 5, then the text field name value is 

appended to page switching code, to automatically send the text string to the specified 

page, followed by home and top of page. 

If the page number value is 0, then the text field name value is sent, without any 

modification to the terminal. This means that if you enter a page number value of 0, you 

must embed the page control sequence into the actual text field name text string. 

text field name 

The text field name value is the name of a Global Setup Data item, Setup Data item, or 

screen data item that contains the string of information to be sent to the specified page. 

Any text longer than 1920 characters is truncated. 

In a distribution company system, whenever the Sales Representative screen is accessed, 

you might want to display the valid commission codes and their meanings. If you did not 

want this to be displayed on Page one due to space limitations, you could use the PAGE; 

command to display this information on Page three every time the Sales Representative 

screen was displayed. If the person using the screen wanted to have more information on 

the commission codes, they could simply go to Page three, and then return to Page one and 

complete the function they required. 

v 1-193

PAGE (PG) 


In the Pre-Screen logic of the Sales Representative screen, you would have logic similar to 

the following: 

 

 

 

 

 

 

 

 

In this example, SD-CCODES contains the text to be displayed on Page 3. The hexadecimal 

code @0D@ will cause any following text to go onto a new line. 

Note: The functionality shown in this example could also be achieved using Teach 

screens, although Teach screens can only be displayed on Page 2. 

The Teach (TE) choice in your LINC Generate Operations Guide. 


1-194 v

PERFORM.FRAME.LOGIC (PFL) 

Syntax 

PERFORM.FRAME.LOGIC (PFL) 

The PERFORM.FRAME.LOGIC; command is used in Report logic to execute the logic of a 

Report Frame without printing the Frame. Any painted Frame data items are ignored. 

This command is not valid in Performable Global Logics. 

DDD DDD DDDDDDDDDDDDDDDDD4 

frame 


A valid Frame number in the range 1 through 98 of an existing Frame that is not the current 

Frame. 

‘‘PRINT.FRAME (PF)’’. 

v 1-195

PRINT.FRAME (PF) 


The PRINT.FRAME; command executes the logic of the specified Report Frame (including 

any PRINT.FRAME; commands), and then the Frame is output for printing. 

The AS; command option indicates that you are printing this Report as a Shadow Report 

with a different title. 

The AT; command option directs that printing is to start at the line specified (counting from 

the top of the page). If headings have printed beyond this line, printing will commence 

from the next available line. If the specified line is less than the current line, the Frame is 

printed on the next page. If the line specified by the AT; command option is greater than 

GLB.FORMDEPTH, the Frame will be printed on a new page on a line calculated by 

subtracting the value of GLB.FORMDEPTH until an acceptable value is found. 

For example, suppose a Report requesting printing to start at line 53 is directed to Video. 

Since GLB.FORMDEPTH is 48, one page is skipped (48 lines) and output starts at line 5. 

At the time of the first PRINT.FRAME; to the print file (or a shadow print file) in ROC and 

non-ROC Reports, the current value of GLB.STN is captured. On subsequent 

PRINT.FRAME; commands to the same print file, the associated captured GLB.STN value 

is compared with the then current GLB.STN. If they are different, a RELEASE; command is 

invoked before performing the requested print. Similar logic applies for GLB.DEVICE and 

GLB.PRINTHOST in ROC Reports. 

Multiple blank pages are not printed if the LINC System is using the Report Output Control 

System (ROC) for video output (device type of VD). 

Notes: 

$ In an MCP based LINC System that does not use ROC, a Frame that contains only 

logic may print a blank line when accessed by the PRINT.FRAME; command. 

Use an END.NO.PRINT; command to prevent a blank line from being printed. 

In ROC Reports, a blank line is not printed in this case. 

$ ROC files are created with the usercode of the parent LINC System when the value of 

GLB.USER is spaces. ROC text files for UNIX LINC Systems are created with the 

usercode of the initiator of the Report when GLB.USER is spaces, with read/write 

access for all. 

$ System Data items associated with Report or Shadow Report output should not be 

used if there is no associated PRINT.FRAME; command, as COBOL syntax errors 

would result. 

$ The values of GLB.STN, GLB.DEVICE, and GLB.PRINTHOST are only relevant at the 

time of the actual printing of the Frame. Their values may change any number of 

times between PRINT.FRAME; commands, without affecting the printing of the 

Report. 

1-196 v

Syntax 

Examples 


DDD DD DDBDDDDDDDDDDDDDDDDDDDDDDDDBD 

3 3 

@D DD DY 

DDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDDDDDDDDDDDBDDD4 

3 3 

@D DBD DBDY 

3 3 

@D DDY 

 

 

 

 

‘‘GLB.FORMDEPTH’’. 


v 1-197

PURGE (PU) 

PURGE (PU) 

Syntax 

Example 


The PURGE; command physically deletes the most recently accessed Component or Event 

record from the LINC database. 

This physical record deletion is performed immediately, (but not committed until the end 

of the transaction). Logically, for the user performing the PURGE, the PURGE takes effect 

immediately. If a LOOK.UP; follows a PURGE within the same transaction, the record will 

not be found. For other users, the record will be locked. 

Caution 

The PURGE; command causes all access paths to the Ispec record to be physically 

removed from the LINC database. This is the same as when the System Data item 

MAINT is given the value PUR. 

This is not a logical delete, as when the System Data item MAINT is given the value 

DEL. 

PURGE permanently breaks all physical and logical relationships with the records on 

which it operates. The disk space that was occupied is immediately available for use by 

other records of the Ispec, when the transaction is completed. 

To release the disk space for other uses, run the LINC Database Management Utility (DMU, 

or GMU for Griffin databases on UNIX LINC Systems). 

DDDDD DDDDBDDDD DDDDDBDDDDDDDDDDDDDDDDD4 

3 3 

@DDDDDD DDDDDDDY 

 

 

 

 

 

‘‘MAINT’’. 

The Database Management Utility (DMU and GMU) in your LINC Administration and 

Operations Guide for the relevant host type. 

1-198 v

RECALL (RC) 

The RECALL; command can be used to: 

RECALL (RC) 

$ Display a specified Ispec (or, if none is specified, the current Ispec). If more than one 

RECALL; or SWITCH.TO; commands are in the logic, then only the last command is 

actioned. 

Note: If a RECALL; command is used in an OLTP Service, then the last 

Ispec to be recalled must be OLTP-reply capable. 

$ Display Teach information associated with an Ispec. When the TEACH; command 

option is included, the Ispec is displayed on Page 1, and the Teach information on 

page 4 for UNIX and OS 2200 based LINC Systems, and Page 2 for MCP based LINC 

Systems. 

If the Ispec recalled is the current one, the contents of Page 1 remain undisturbed; 

there is no loss of data. 

The TEACH; command option must be on the same logic line as the RECALL; 

command. 

Note: Messages that are queued from the MESSAGE; command take 

priority over recalled Teach screens. 

$ RECALL; (BYE) Sign off the LINC System without retaining the current Ispec and user 

information 

You can perform a RECALL; (BYE) command to log off from your LINC System even if 

you have a Report running. If the Report attempts to display or access information 

from the terminal from which you logged off: 

v For MCP based LINC System, if the Report produces messages they are discarded 

and any ACCEPT; commands will hang the system (same as 2200?). 

v For MCP based and OS 2200 based LINC Systems, ACCEPT; commands cause the 

Report to hang waiting for a response. To provide the response, log back onto that 

terminal and provide the input to the ACCEPT; command in the usual way (> 

character followed by a text response). 

v For UNIX LINC Systems, the Report will terminate abnormally. 

$ RECALL; (EXIT) Sign off, for MCP and OS 2200 based LINC Systems, while retaining 

the current Ispec and user information. This enables later reentry. 

On OS 2200 based LINC Systems, if you use RECALL; (EXIT) to exit from a system 

that does not have security set, and then you turn security on before you re-enter the 

system, the LSM Security screen will be displayed when you re-enter the system. After 

satisfying the security requirements, the Fireup Ispec will be displayed. 

The new screen format is not displayed until the current logic has been completed. 

v 1-199

RECALL (RC) 

Syntax 

Examples 

If you recall the current Ispec, the Pre-Screen logic for the Ispec is ignored. If Pre-Screen 

logic is required, you can use one of the following methods: 

$ Set the Refresh Screen field on the Component or Event Options screen to Y. 

$ Recall an intermediate (dummy) Ispec that recalls the current Ispec. 

The RECALL; command sets GLB.ERROR to *****. 


DD DDDBDDDDDDDDDDDDDDDDDBDDDDDBDDDD 

3 3 3 

CDD DD4 @DDDDD4 

3 3 

CDD DDY 

3 

CDDDD DDDDBDDDDDDDDDDD4 

3 3 

CDDD DDDD4 

3 3 

@DD DDY 

DD DDBD DBDDDDDDDDDD4 

3 3 

@DD DDDY 

data item 1 is an alphanumeric item containing a valid Ispec name. 

data item 2 is an alphanumeric item containing the value BYE or EXIT. 

data item 3 is an alphanumeric item containing a valid Teach name for the Ispec. 

The following logic is in the Component CUST, which has an Ordinate CUSTOMER: 

 

 

 

 

 

The Event SALE has the following data items and Pre-Screen logic: 

 

 

 

 

1-200 v


‘‘GLB.ERROR’’. 

RECALL (RC) 


v 1-201

RELEASE (REL) 

RELEASE (REL) 

The RELEASE; command sends to the printer all PRINT.FRAME; commands that have 

been previously executed in a Report or Shadow Report. 

A change in the value of the System Data item GLB.STN will invoke an automatic release. 

For ROC Systems, a change in the value of the System Data items GLB.DEVICE or 

GLB.PRINTHOST will also invoke an automatic release. 

Reports Using Report Output Control (ROC) 

When a RELEASE; command is executed, the current Report file is closed, and any 

subsequent output will begin with a new page. The System Data item GLB.PAGECOUNT is 

set to zero after a release. 

Depending on whether or not the Report is performing other updates, the Report output 

may not be available to ROC until a CRITICAL.POINT; command, a SLEEP; command, or 

end of Report occurs. 

When the RELEASE command is used with the ON.CHANGE; command, the footing frame 

is not sent to the printer in the current ROC file. 

Reports Not Using ROC (MCP environment only) 

Syntax 

Examples 

GLB.PAGECOUNT is NOT set to zero after a release. 

An automatic page throw occurs at the start of Report output to a TP or LP device, 

following a RELEASE; command. 

The RELEASE; command cannot be used in Video reports. 

DDD DDDDBDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDD4 

3 3 

@DD DD DDY 

 

 

 

 

 

 

 

1-202 v

RESTART (RT) 

Syntax 

Examples 

There are two forms of the RESTART; command: Restart of a Profile, and Restart 

specifying an Extract file. 

Restart of a Profile 

RESTART (RT) 

$ The RESTART; command must appear within the loop of a DETERMINE; ACTUAL 

command. 

$ The RESTART; command causes the DETERMINE; ACTUAL command with which it 

is associated to restart the current Profile from the beginning. The remainder of the 

logic in the current loop is executed before the restart. 

$ Records deleted or flagged from the Profile by the logic will not be brought into 

memory after the RESTART; command. 

Restart with an Extract File 

$ The RESTART; command must be coded outside of a DETERMINE; ACTUAL loop. 

$ The RESTART; command purges the Extract file. 

$ If an open Extract file is currently being read, it is closed and purged, so that the name 

can be reused. 

$ This feature is for Reports that repeatedly loop to extract data, sort, output, and then 

clear the file for the next iteration. 

$ It is recommended that if you are using CRITICAL.POINT; in your Extract file print 

logic, you should code the RESTART; command immediately before the 

CRITICAL.POINT; command. This will effectively eliminate the chances of a Report 

recovery situation encountering a NO-FILE condition on the Extract file. 

$ The RESTART; command deletes all types of Extract file, whether they are temporary, 

permanent, or existing. For more details, see ‘‘EXTRACT (EX)’’, earlier in this section. 

DDDDD DDDDDDDBDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDD4 

3 3 

@DDD DDDY 

In the following example, a Profile named RUNREQUEST is defined as follows: 

 

 

 

 

v 1-203

RESTART (RT) 

The main logic of Report THISREPT contains the following logic: 

 

 

 

 

 

 

 

 

 

 

 

In the next example, Report THATREPT needs to process each customer’s orders in order 

of product: 

 

 

 

 

 


 

 

 

 

 

‘‘DETERMINE; ACTUAL’’. 

1-204 v

ROC.MODE (ROC) 

Syntax 

ROC.MODE (ROC) 

The ROC.MODE; command enables the Report Output Control System (ROC) to be 

accessed from Ispec logic. All following logic in the Ispec is ignored and will not be 

executed. 

If an Ispec name is included with the ROC.MODE; command, Pre-Screen logic for that 

Ispec is invoked when ROC is terminated. If no Ispec is included, Pre-Screen logic for the 

calling Ispec is invoked. 

If an Ispec name is specified, a command to be passed to ROC can also be included. The 

passed command is actioned by ROC. For more details of ROC, see the LINC Operations 

Guide for the relevant host type. 

ROC is not available with LDA. In LDA Run Time, the ROC.MODE; command behaves like 

the RECALL; command. 

DDD DDBDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDDD4 

3 3 

@DD DDDBDDDDDDDDDDDDDDD4 

3 3 

@DDD DDDDY 

ispec 

A data item or literal containing the name of an Ispec. 

action 


A data item or literal containing a command of up to 50 characters to be interpreted by 

ROC. 

A value of CLEAR instructs ROC to clear the usercode and history station information for 

the current station, and then return immediately to the specified Ispec. The CLEAR value 

is typically used where station assignment is dynamic and the user was logging on or off. 

‘‘RECALL (RC)’’. 


v 1-205

RUN 

RUN 

The RUN; command is used to initiate a Report from Ispec logic. 


For an MCP based LINC System 

After the Report is initiated, it is not dependent on the completion of the logic of the Ispec. 

The destination of the Report output is determined by the setting of the output device type 

and by the value of the System Data item GLB.STN. 

If the output device type is VD, and input is from a terminal, the Report is attached to that 

terminal. If input is from External Automatic Entries (HUB), GLI, or OFFLINE, the Report 

will not be initiated. If the device type is RP, TP, orLP, and input is from a terminal, GLI, 

HUB, or OFFLINE, the report will be unattached. 

The ROC system will recognize EX as a valid device type and write the output to a 

standard system data file. The name of this file will be derived from the Destination Station 

value held in GLB.STN. You can specify a longer name if required. 

When running an unattached Report, any messages will be ignored, and requests for 

ACCEPT; command input from that Report will cause it to go to end-of-job. Instead of 

using MESSAGE; and ACCEPT; commands in Reports, you can pass parameters, as 

described under ‘‘Passing Parameters to Your Report’’, later in this section. 

The chargecode that applies to your Report run is dependent on the values of the :COD 

LINC System command and the GLB.CHARGECODE System Data item. 

For further details, see your MCP Based LINC Administration and Operations Guide and 

‘‘GLB.CHARGECODE’’ in this manual. 

For an OS 2200 based LINC System 

The RUN; command is interpreted as if a :RUN LINC System (colon) command had been 

entered. It is not available for Fast Load Reports. 

A Report can be run as attached or unattached. If the Report is run as attached by using the 

AT device type, messages are returned to the screen from which the Ispec issuing the RUN 

command was initiated. The current screen display is overwritten, and replies can only be 

entered from the same terminal. Each terminal can only have one active attached Report at 

a time. Reports can only be run as attached if the default device is VD. 

1-206 v

RUN 

If the AT device type is not used, the device must be LP, and the Report will run 

unattached. Messages from unattached Reports are directed to the System Log file, and 

accepts are taken from any data images following the @XQT command in the runstream. If 

there is not enough data to match all the ACCEPT; LINC logic commands, the Report 

aborts. To enter data images into the runstream, edit the element with the same name as 

the Report in the following file: 

 

See the MESSAGE; command and ACCEPT; command for methods of accepting runtime 

information into a running Report. You can also pass parameter information to your 

report, by including the PA; command option in the RUN; command. For more details, see 

‘‘Passing Parameters to Your Report’’, later in this section. 

For a UNIX LINC System 

The RUN; command is interpreted as if a :RUN LINC System (colon) command had been 

entered. 

For a UNIX LINC System, if the input is from a terminal id the type is VD, the Report is 

attached to the terminal. In all other cases with UNIX, the Report is run in background, and 

any requests for ACCEPT; command input will cause the Report to terminate. 

After it is initiated, the Report is not dependent on the completion of the logic of the Ispec. 

Note: Do not initiate multiple copies of the same Report, as this may result in 

ORACLE errors. 

The destination of the Report output is determined by the setting of the output device type, 

and by the value of the System Data item GLB.STN. 

Any messages appear on the status line of the terminal issuing the RUN; command. 

You can pass parameter information to your report, by including the PA; command option 

in the RUN; command. For more details, see ‘‘Passing Parameters to Your Report’’, later in 

this section. This method could be used to eliminate MESSAGE; and ACCEPT; commands 

from Report logic. 

In LDA Run Time 

All Hosts 

Only hard copy output is produced. 

Values of GLB.STATUS 

When the RUN; command is executed, the System Data item GLB.STATUS will contain one 

of the values shown in the following table. 

v 1-207

RUN 


ACTIV The terminal already has a Report attached. 

BUSY The maximum number of Reports are already running, or the Report has 

already been initiated by the same user. 

INVAL The Report name is invalid or unlocatable. 

spaces The value is spaces when the report is first initiated. 

Note: There are some conditions under which a Report may seem to have started 

satisfactorily with no error status being returned, but may not run due to a 

system limitation. That is, you may have exceeded the maximum number of 

processes that your operating system can handle. 

Passing Parameters to Your Report 

You can use LINC logic to pass parameter information to your Report in the following ways: 

$ Use MESSAGE; and ACCEPT; logic commands so that your Report can collect runtime 

information from user input. 

$ In your Ispec logic, you can store information in the Database for your Report to read. 

You must use this method if your parameter information is greater than 254 characters. 

$ Specify the PA; command option with your RUN; command. Before you generate the 

Report you want to run, you must have specified a data item on the Report Options 

screen that will contain your parameter data. For more details, see your LINC 

Generate Operations Guide. This is the simplest method of passing parameter data to 

a Report using LINC logic, but it is limited to a maximum of 254 characters. 

Restrictions on parameter passing are: 

$ The PA; command option is ignored in LDA Run Time. 

$ GLB.PARAM may be used to pass parameters in LDA Run Time. 

$ Binary data is not allowed in the parameter for a UNIX LINC System, . 

$ The contents of the Report parameter are undefined if a Report parameter is defined in 

the Report, but the RUN; command does not pass the parameter. 

$ The parameter will be ignored with no error, if the RUN; command passes a parameter, 

but the Report does not specify a parameter. 

$ The initial value of your Report parameter will be recovered regardless of any changes 

you have made to the contents of Setup Data or Global Setup Data in your Report 

logic, if the Report goes into recovery. 

$ Up to 254 bytes of information can be sent to the Report from a WAKE.UP; command 

in your Report or Ispec logic. 

1-208 v

Syntax 

DD DDD DDD DDDBDDDDDDDDDDBDD 

3 3 

@D DY 

DBDDDDDDDDDDDDDDDDDDDBDBDDDDDDDDDDDDDDDDDDDDBD4 

3 33 3 

@D DD DY @D DD DY 

report 

A data item or literal giving the name of the Report. 

device 

The type of output device: one of the valid values for the relevant target host type, as 


Device Output to MCP 

environment 

OS 2200 

environment 

LP System or user-defined Line Printer Yes Yes Yes 

AT Video (Attached Report) No Yes No 

EX Extract file (standard system data 

file) 

Yes No Yes 

RP Remote Printer, via Prints/Reprints Yes No No 

TP User-defined Terminal Printer (UNIX 

alias) 

VD The attached user terminal (UNIX 

temporary file) 

Yes No Yes 

Yes No Yes 

On OS 2200 based LINC Systems, LP specifies the Report is to be run unattached. 

UNIX 

RUN 

ForaUNIXLINCSystem,LP specifies that output is piped to a command defined by the 

LP alias; TP specifies that output is piped to a ROC alias; VD specifies output to the ROC 

database or to a temporary file for Direct Reports. VD Reports are attached to the initiating 

terminal for input. 

TRACE; 

Activates the Trace function for a Report that has been generated with the capability to 

produce trace output. 

TRACE can be abbreviated as TR. 

LA; language 

Use this command option to supply the initial language for the Report. The language value 

can be a data item or literal. 

v 1-209

RUN 

Examples 


The language is validated when the Report is initiated. If not valid, the current station 

language is used. If you did not enter a language, the Report defaults to the current station 

language. 

This option is ignored for a single language Report. That is, you did not enter Y in the 

Generate to all Languages field on the Report Options screen for this Report. 

PA; parameter 

Note: This option is ignored in LDA Run Time. 

Use this command option to pass parameter data to the Report you want to run. The 

parameter value can be an alphanumeric data item or a literal, with a maximum of 254 

characters. 

 

 

 

‘‘ACCEPT (AX)’’, ‘‘MESSAGE (ME)’’, and ‘‘START (ST)’’. 

See your LINC Generate Operations Guide for further details of the Trace facility. 

Runtime operation of the Trace facility is described in your in your LINC Administration 


The LINC System Command :RUN has a similar function to the RUN; command. Details of 

the :RUN command, and additional information on the execution of Reports, are described 

in the LINC Operations Guide for the relevant target host type. 

"Report Options Screen" in your LINC Generate Operations Guide, for details of 

specifying a data item for passing a parameter. 


1-210 v

SECURE 

SECURE 

SECURE; is not a full logic command. It is a command option that can be specified with a 

DETERMINE; or LOOK.UP; command only, to facilitate record locking of the LINC 

database in a non-Integrity LINC System. 

The SECURE; command option is applicable to No.Integrity Ispecs and Reports; that is, 

those that do not have the Integrity field set (to Y) on either their Ispec or Report Options 

screen and on the Primary Specification Options screen. Where the Integrity field is set, 

those Ispecs and Reports will automatically secure all required resources. 

The type of locking on each host type at runtime is described in the following subsections. 


The SECURE; command option facilitates record-level locking of the LINC database in a 

non-Integrity MCP based LINC System. The SECURE; command option locks the record 

that is read into memory by the associated LOOK.UP; or DETERMINE; command. The 

record remains locked until one of the following situations occur: 

$ The Ispec or Report logic is complete. 

$ A SLEEP; or CRITICAL.POINT; command is executed in Report logic. 


The SECURE; command allows page-level locking of a non-Integrity OS 2200 based LINC 

database. The SECURE; command option locks the page containing the record read into 

memory by the associated LOOK.UP; or DETERMINE; command. The page remains locked 

until: 

$ The Ispec or Report logic is complete. 

$ A SLEEP; command or CRITICAL.POINT; command is executed in Report logic. 

Note: If you use the SECURE; command option when reading a database record that 

has already been updated by logic earlier in your Ispec, then an RDMS error 

6002 (semantic error) and an RDMS ERROR 23030 (Table nnnn cannot be 

explicitly locked because it is currently locked explicitly or implicitly for 

update) will occur. 

Always append your SECURE; command option to a LOOK.UP; or 

DETERMINE; of the database record before the logic that updates the record. If 

an exclusive lock has already been placed on the table using the 

EXCLUSIVE.USE; command, the SECURE; command option will have no affect. 

v 1-211

SECURE 


Syntax 

Examples 


The SECURE; command option facilitates row-level locking of the LINC database in a 

non-Integrity UNIX LINC System. The SECURE; command option locks the row read into 

memory by the associated LOOK.UP; or DETERMINE; command. The row remains locked 

until the transaction (the Ispec or Report logic) is complete. 

A lock applied to a row prevents other users from updating that row. It does not prevent 

other users from reading the row. Another user wanting to update that row (whether they 

have SECURE set or not) will be forced to wait until the transaction is complete before 

their update is processed. 

DDDDDDDDDDD DDDDDDDDDDDDDDDDDDDDDDDDD4 

A Report is to be initiated by a RUN; command in Ispec logic. The Ispec stores parameters 

in the Memo Component RPRAM, by using AUTO; commands. This Memo Component is 

accessed by the Report through a Profile PRINPARAM, which has the following condition: 

 

Since several copies of the Report INVOICE may be running at the same time, it is essential 

that each set of parameters is processed only once. 

 

 

 

 

 

 

 

 

Different Reports could use the same runtime parameter file, by using a Report identifier 

as one of the Profile Ordinates. 


1-212 v

SEND.MESSAGE (SEND.STATUS; SM; SMSG; SS) 


This command enables you to send messages of up to 50 characters directly to the status 

line of specified user terminals signed on to your runtime LINC System. The message is 

sent immediately, and does not wait for the end of the current transaction. 

SEND.STATUS, SM, SMSG,andSS are valid synonyms for SEND.MESSAGE. 

The message can be sent to: 

$ The initiating terminal 

$ Another nominated terminal 

$ All terminals currently signed on to your LINC System (broadcast message) 

Note: Considerable processor overhead can be incurred by this broadcast 

variant of the command, (SEND.MESSAGE; ALL). 

$ An MCP based Operator Display Terminal (ODT) 

Messages directed to the ODT are always delivered. They appear as displays, and 

indicate the sending Ispec or Report. The mix number of the relevant LINC Update 

program is also displayed. Messages sent from Reports do not indicate the copy of the 

Report from which they originate. The mix number of system/LSS is displayed. 

If an invalid terminal name is specified, or the designated terminal is not logged on, no 

message is delivered, and no error is returned. 

To send a message to the current terminal from an Ispec, send it to GLB.STN. To send a 

message to the initiating station from a Report, send it to GLB.INITSTN. 


Specific details for each runtime host type are given in the following subsections. 


Reports initiated in batch mode under LINC/RIP have the value of their initiating station 

(GLB.INITSTN) set to BATCH, so that attempts to send messages to GLB.INITSTN will 

have no effect. No messages are delivered, and no errors are returned. 


The PID of the receiving terminal and the message can be given in data items or as literals. 


The message may be sent to a username, all users, or the initiating station. If an invalid 

userid is specified (or the designated user is not signed on to the LINC System), no 

message is delivered and no error is returned. 

v 1-213


Syntax 

Examples 


In LDA Run Time 

The destination station is ignored, and the message is displayed immediately on the Status 

Line (or in the message window for Reports). 

DD DDBDD DDBDD DDDDDD4 

3 3 

CDDDD DDDD4 

3 3 

CDDDDDD DDDDDD4 

3 3 

@DDDDDD DDDDDDY 

data item 1 

A data item or literal giving the destination of the message. 

The ODT value is valid for MCP based LINC Systems only. 

On OS 2200 based LINC Systems, if the message is to be sent to an individual terminal, its 

PID must be specified as a data item (not in GLB.STN). 

data item 2 

An alphanumeric data item or literal giving the text of the message. The text must not be 

numeric. 

 

Ispec Initiated 

 

Report Initiated 

 


1-214 v

SEND.PRINT (SEND, SP) 

Syntax 


The SEND.PRINT; command enables a Report to be output to multiple destinations. It is 

applicable only to Standard Reports printed under the Report Output Control System 

(ROC). It is ignored for ROC Direct Reports (and, on MCP based LINC Systems, all Reports 

that do not use ROC). A SEND.PRINT; command must come after the first PRINT.FRAME; 

command for a Report. 

Output to the specified device or devices does not commence until a RELEASE; command 

(or end-of-job) is encountered. If directed to a video device, output must be explicitly 

requested by the receiving terminal through the ROC menu. 

The System Data item GLB.STATUS is set to ***** if invalid device types or destinations 

are specified, or if no output has been produced by the Report. Otherwise, GLB.STATUS is 

set to spaces upon completion of the SEND.PRINT; command. 


DD DBDDDDDDDDDDDDDDDDDDDDDDDDBD DD 

3 3 

@D DD DY 

DDDBDDDDDDDDDDDDDDDDDBDDDBDDDDDDDDDDDDDDDDDDDDDBDDDD4 

3 3 3 3 

@DD DDY @DD DD DDY 

device 

A two-character value (without enclosing parentheses) or a data item containing a 

two-character value giving the output device type. Valid values for each runtime host type 

are shown in the following tables. 

Device Host Types Output is sent to 

LP MCP 

environment 

Line Printer 

OS 2200 

environment 

User-defined Line Printer 

UNIX Piped to a command defined by the LP alias 

continued 

v 1-215



continued 

Device Host Types Output is sent to 

TP MCP 

environment 

User-defined Terminal Printer 

OS 2200 

environment 

User-defined Terminal Printer 

UNIX Piped to a ROC alias 

RP MCP 

environment 

Remote Printer, via Prints/Reprints 

MCP 

environment 

Extract file (standard system data file) 

EX UNIX Extract file (standard system data file) 

VD MCP 

environment 

The attached user terminal 

OS 2200 

environment 

The attached user terminal 

UNIX Output to a temporary file for Direct Reports. For ROC Reports, 

an output request is created, and you must view this through 

the ROC system. 

destination 

A data item or literal specifying the name of the destination output device. This is required 

if device is a data item, or two-character value other than LP. Adestination value is 

optional only if device is LP, (not a data item containing LP). 

AT; hostname 

This command option applies only to ROC Reports directed to LP, RP, and TP devices on 

MCP based LINC Systems. The hostname value is a data item or literal specifying the host. 

‘‘RELEASE (REL)’’, ‘‘SLEEP (SLP)’’, and ‘‘CRITICAL.POINT (CP)’’. 

Report Output Control System information in your LINC Administration and Operations 

Guide for the relevant target host type. 

1-216 v

SENDLIST.DYNAMIC (SLDYN) 


This command enables PowerClient users to use specific Ispec data item list boxes whose 

values are created by a host LINC System. 

The SENDLIST.DYNAMIC; command creates a list box specific to a particular transaction. 

To create a list box with several values, execute the SENDLIST.DYNAMIC; command 

several times. 

The SENDLIST.DYNAMIC; command has an effect only in an Ispec initiated by a 

PowerClient station (or NOF program or terminal), or in a Report initiated from a 

PowerClient station (or NOF terminal or NOF program). This command is not available 

with OLTP. 

You can modify the format, size and location of the list box when you are using 

PowerClient during the screen design process. 

You are responsible for supplying end of Kanji (SOE) and start of Kanji (SOK) characters 

to the description field of the listbox data. 

Note: The SENDLIST.DYNAMIC; command is designed to be used with PowerClient 

(Designer Workbench). The use of this command with NOF is also supported. 

About List Boxes 

In your LINC logic, you can define the contents of list boxes, and download the data to 

PowerClient. You can design two types of list box: 

$ Dynamic 

A dynamic list box is used when data needs to be tailored for each transaction; for 

example, a customer is to see only those choices that apply directly to them. Dynamic 

list box items can be individually and selectively changed in Ispec logic. 

The SENDLIST.DYNAMIC; command causes a data item with a LISTBOX; Data 

Attribute to display as a dynamic list box when the Ispec screen containing that data 

item is downloaded to PowerClient. 

$ Static 

A static list box is intended for information that is the same for each transaction and 

that changes infrequently; for example, branch names of a company. 

Static list box data is obtained from a standard sequential file that you can create by 

using a LINC Report or an editor. 

The SENDLIST.STATIC; command causes a data item with a LISTBOX; Data Attribute 

to display as a static list box when the Ispec screen containing that data item is 

downloaded to PowerClient. See ‘‘SENDLIST.STATIC (SLSTA)’’ later in this section. 

Note: You can use PowerClient to maintain the data for dynamic and static list 

boxes. 

v 1-217


When data is downloaded 

When a SENDLIST.DYNAMIC; command is executed at runtime, your dynamic list box 

data is prepared for downloading to PowerClient. This data: 

$ Applies to data items with the LISTBOX; or LISTBOX*; Data Attribute 

$ Is stored in the PowerClient repository, for use whenever the named list box is 

required for a screen format 

$ Is downloaded to PowerClient or NOF: 

v At end of transaction 

v When a SLEEP; or CRITICAL.POINT; command is executed in a Report initiated 

from a PowerClient or NOF terminal 

v On MCP based target hosts, when an Ispec in another Subsystem is recalled 

For OS 2200 Based LINC Systems 

For an OS 2200 based LINC System, move the transaction ID for WDP into GLB.STN before 

executing the SENDLIST.DYNAMIC; command. In addition, you should note the following 

consideration when using large dynamic listboxes. 

Large dynamic listboxes 

Large dynamic listboxes (greater than 2000 entries of 30 characters) on 2200 Series hosts 

can cause severe network congestion. This may result in the PCE station not receiving all 

the listbox information. If the information cannot be delivered, it is discarded by the 

standard (non-LINC) host communications software. 

To avoid network congestion, perform one of the following: 

$ Make the listbox static (using the SENDLIST.STATIC; command) 

$ Adjust the CMS1100 configuration parameter MAX-QUEUE-ENTRIES (default is 10). 

This defines the maximum depth of messages that can be queued to a terminal before 

the MCB discards the information. For the impact of changing this parameter, see your 

Communications Management System (CMS 1100) Configuration Reference 

Manual. 

Format of the Data 

The SENDLIST.DYNAMIC; command downloads a single alphanumeric value. This value 

consists of a number of parts - referred to as columns - separated by delimiters. 

How the various columns are used is determined by your PowerClient application. See 

your PowerClient documentation for further details. 

1-218 v

Syntax 

Columns 

Commonly the downloaded value consists of two columns, in the form: 

 


The delimiter can be any printable character, including all alphanumeric and special 

characters. Notice that the first character of the value is the delimiter. 

You are not limited to two columns: you can have one or more. You must ensure that the 

length of each particular column is the same in each value, if not, the 

SENDLIST.DYNAMIC; command will fail. 

Example 

In this example, a slash (/) is used as the delimiter and the listbox contains a code to be 

handled by your LINC System, and a description to be displayed in a list box in 

PowerClient. 

 

 

DDD DDD DDD DDDDDDDDDDD4 

listbox 

A data item or literal containing the name of the listbox to be downloaded. Names longer 

than 23 characters are not permitted. The listbox name has one of the following forms 

(where item is the name of the data item the list box applies to): 

$ ispec.item 

This form indicates that the list box applies only to users of the specified Ispec. 

$ *.item 

This form indicates that the list box applies to users of all Ispecs. 

data name 

A Setup Data item or Global Setup Data item that contains a value and description to be 

downloaded. The item must be alphanumeric. It may be a Group Setup Data item or Group 

Global Setup Data item. 

The maximum combined length of the name and the description is 80 characters. Text in 

excess of 80 characters will be truncated. 

v 1-219


Example 


 

 

 

 

 

 

 

 

 

 

 

"LISTBOX (LBX)" in your LINC Generate Reference Manual: Painter and Editor. 

‘‘SENDLIST.STATIC (SLSTA)’’. 

The PowerClient Forms Designer Planning and Operations Guide. 

1-220 v

SENDLIST.STATIC (SLSTA) 


The SENDLIST.STATIC; command enables PowerClient users to use specific Ispec data 

item list boxes whose values are created by a host LINC System. This command is 

designed to be used with PowerClient (Designer Workbench). The use of this command 

with NOF is also supported. 

In a Report, you can create a file of list box items by using the EXTRACT; command and 

then name the file by using the SENDLIST.STATIC; command. When an Ispec screen is 

displayed in PowerClient, a data item that has the LISTBOX; Data Attribute is displayed as 

a static list box containing the data downloaded by the SENDLIST.STATIC; command. 

The first time each user accesses the file, it is downloaded. 

About List Boxes 

For a description of the types of list boxes, see ‘‘About List Boxes’’ under 

‘‘SENDLIST.DYNAMIC (SLDYN)’’, earlier in this section. 

You can modify the format, size and location of the list box when you are using 

PowerClient during the screen design process. 

Availability of the Command 

The SENDLIST.STATIC; command is not available with OLTP. 

For MCP Based LINC Systems 

For Reports run from a NOF terminal or program for an MCP based LINC System, the 

SENDLIST.STATIC; command sends data to the NOF terminal or program. Otherwise, the 

data is submitted to the Workstation Driver Program (WDP). 

For Ispecs in an MCP based LINC System, executing the SENDLIST.STATIC; command 

from a T27 style, IBM 3270 or OLTP terminal is ignored unless contained in the System 

Global Logic STARTUP (in which case the data is submitted to WDP). NOF input results in 

the data being sent to the NOF terminal or program. 

For OS 2200 Based LINC Systems 

For OS 2200 based LINC Systems, the SENDLIST.STATIC; command has an effect only in 

Ispecs or Reports initiated by a PowerClient station, or in standalone Reports. 

For UNIX LINC Systems 

For UNIX LINC Systems, the SENDLIST.STATIC; command has an effect only in Ispecs or 

Reports initiated by a PowerClient station, or in standalone Reports. 

v 1-221


Format of the Data 

Syntax 

The file downloaded to PowerClient must consist of a series of lines (each line creates an 

entry in the static listbox). Each line contains a number of parts - referred to as columns - 

separated by delimiters. 

How the various columns are used is determined by your PowerClient application. See 

your PowerClient documentation for further details. 

Columns 

Commonly the downloaded value consists of two columns, in the form: 

 

The delimiter can be any printable character, including all alphanumeric and special 

characters. Notice that the first character of the value is the delimiter. 

You are not limited to two columns: you can have one or more. You must ensure that the 

length of each particular column is the same in each value, if not, the SENDLIST.STATIC; 

command will fail. 

For OS 2200 based LINC Systems, to store trailing spaces in the D_SDF table, insert a third 

delimiter in your data. 

Example 

In this example, a slash (/) is used as the delimiter and the listbox contains a code to be 

handled by your LINC System, and a description to be displayed in a list box in 

PowerClient. 

 

 

DD DD DBD DBDDDDDDDDDDDDDBD4 

3 3 3 

3 @ DD 4 

3 3 

@D DD DDDY 

listbox 

A data item or literal containing the name of the list box to be downloaded. Names longer 

than 23 characters are not permitted. The list box name has one of the following forms 

(where item is the name of the data item the list box applies to): 

$ ispec.item 

This form indicates that the list box applies only to the users of the specified Ispec, 

ispec. 

$ *.item 

1-222 v

This form indicates that the list box applies to users of all Ispecs. 

data name 


A data item or literal containing the name of the list box file to be downloaded. 

pack 

Examples 


For MCP based LINC Systems, a data item or literal containing the pack on which the file is 

stored. The default is the Dictionary pack for the LINC System. 

extract file 

A literal value (A through Z), indicating an Extract file whose existing definition is to be 

used. The Extract file must have been defined by a DETERMINE; ACTUAL or EXTRACT; 

command with a RETAIN.AS; command option, or referenced by a SET.TITLE; command 

in the Report. 

In the following example, an Extract file is created and downloaded. 

 

 

 

 

In the next example, an Ispec CUST has the following data items: 

 

 

In logic, a static listbox for BRANCH is to be downloaded to PowerClient from the file 

BRANCHLBX, and a list box for CUSTYP is to be downloaded from the file CUSTYPLBX. 

The BRANCH list box is used by other Ispecs, but the CUSTYP list box is specific to CUST. 

 

 

"LISTBOX (LBX)" in your LINC Generate Reference Manual: Painter and Editor. 

‘‘SENDLIST.DYNAMIC (SLDYN)’’. 

The Designer Workbench Operations Guide. 

v 1-223

SERIAL 

SERIAL 

Syntax 

SERIAL; is not a full logic command. It is an command option that can be specified with a 

DETERMINE; or LOOK.UP; command only, to increase the efficiency of Profile accesses in 

Copy.From Ispecs. The SERIAL; command option retains the pointers to the Profile when 

it is first accessed and, on subsequent accesses, simply retrieves the next record without 

reading through the Profile again. 

The SERIAL; command option is valid only in Copy.From Ispecs. When GLB.COPY is equal 

to 1, the DETERMINE; command will start retrieving records at the point specified in the 

DETERMINE; command, until End-of-file is detected or until a BREAK; is executed. When 

GLB.COPY is greater than 1, the DETERMINE; command will continue retrieving records 

from the last record previously retrieved, and not from the point specified in the 

DETERMINE; command. 

Caution 

Using the SERIAL; command option at other parts of the Copy.From cycle, having 

not used it on the first copy, will produce unpredictable results. The results will 

differ from host type to host type, and could cause problems when porting LINC 

Systems between different hosts. 

When a DETERMINE; command with the SERIAL; command option reaches end-of-file, 

the buffer containing the dataset records continues to contain the data values of the last 

record read. Any subsequent reads using the DETERMINE; command with the SERIAL; 

command option will not alter those values. 

Since the success of the use of the SERIAL; command option depends upon the setting of 

the pointer, the same Profile should not be accessed elsewhere in the same logic, or 

unpredictable results can occur. Also, the SERIAL; command option must be executed in 

the first cycle of the logic (when the System Data item GLB.COPY has a value of 1). See the 

‘‘Example’’. 

The SERIAL; command option is associated with a loop-forming variant of the 

DETERMINE; or LOOK.UP; command, and should only be used in Copy.From Ispecs. It 

must appear on the same logic line as the associated DETERMINE; or LOOK.UP; command. 

The SERIAL; command option is ignored in an Ispec that is not a Copy.From Ispec. 

DDDDDDDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD4 

1-224 v

Example 


SERIAL 

An Event DRINQ has a Copy.From line number of 4 and a MAX.COPIES value of 5. The 

data item STARTCUST is used to enter the starting customer. The Data items CUSTOMER 

(which has LINK; IF.PRESENT applied to it) and BALANCE are part of the Copy.From 

area of the screen. Part of the logic for DRINQ is as follows: 

 

 

 

 

 

 

 

 

Suppose CUST has records with CUSTOMER values: ARNOLD, BRUCE, COLLEEN, 

DIANE, EDWARD,andFRED. If STARTCUST has the value BARRY when the loop is 

entered the first time, the LOOK.UP; FROM command finds BRUCE. The second time 

(when GLB.COPY is 2), the LOOK.UP; FROM command will find COLLEEN, and not 

reread BRUCE. The third time (when GLB.COPY is 3) the LOOK.UP; FROM will find 

DIANE, and not reread BRUCE and COLLEEN. 


v 1-225

SET.DB 

SET.DB 

Syntax 

Note: This command is valid for OS 2200 based LINC Systems only. It is ignored on 

UNIX and MCP based LINC Systems and in LDA Run Time. 

Use the SET.DB; command to specify a target database for Ispecs in your system. You can 

associate a target database with all interdatabase Ispecs, and you can also specify a target 

database for individual Ispecs. Only Ispecs defined as interdatabase Ispecs can be used 

with this command. 

Note: A SET.DB command cannot be executed with recall values entered in the 

MAINT field (FIR, NEX, LAS, REC, andBAC), as these do not process user 

logic. You can define logic that uses the INQ value in the MAINT field. 

The following conditions apply when using the SET.DB; command: 

$ The target database is set to the local database for all Ispecs at the start of Pre-Screen 

and Pre-LINC logic. 

$ Previous target database definitions are overridden by subsequent SET.DB; commands 

(including those with the ALL; command option). 

$ Note the following points when making target database assignments before and during 

DETERMINE; or LOOK.UP; loops. 

v The target database assignment used to run the DETERMINE; or LOOK.UP; loop is 

not affected by any SET.DB; assignment within the loop. 

v SET.DB; assignments within the loop will however affect subsequent database 

commands. 

The following System Data items can be used in conjunction with interdatabase access: 

$ GLB.APPNAME 

$ GLB.APPNO 

$ GLB.EXTDB 

$ GLB.EXTDBSTATUS 

Note: The SET.DB; command is used to facilitate interdatabase access. There are a 

number of important considerations when using this facility, and therefore 

you should thoroughly read the subsection on External Automatic Entries in 

your LINC Generate Operations Guide before using the SET.DB; command. 

DD DDD DDBDDDD DDDDBDDDDDDDDDDDD4 

3 3 

@D DY 

1-226 v

database 

SET.DB 

An alphanumeric data item or literal (in parentheses) that specifies a database (database 

name must be upper case). 

ispec 

Name of an interdatabase Ispec. The name must be in upper case, and in parentheses. 

ALL 

Examples 

Specifies that all interdatabase Ispecs are to have the same target database. 

In the following example, the database named in the ADB data item is the target database 

for all interdatabase Ispecs. The PROD Ispec is given a target database of BOB,andCUST 

is given a target database of FRED. The target database for the SALE Ispec is reset to the 

local database. 

 

 

 

 

In the next example, the database SALEDB is used by the LOOK.UP; EVERY command 

(even though there is a SET.DB; command in the loop). In the loop, however, the 

LOOK.UP; command uses the database named CUSTDB. 

 

 

 

 

 

 

To recall data from a record in the BOBDB database: 

 

 

 

 

 

 

 

 

 

 

v 1-227

SET.DB 

To read from one database and AUTO; to the other: 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Flag to an existing record in the database of another LINC System: 

 

 

 

 

Read one database, and flag to another database: 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Using System Data Items to determine the name of a target database: 

 

 

 

 

 

 

1-228 v


‘‘GLB.APPNAME’’, ‘‘GLB.APPNO’’, ‘‘GLB.EXTDB’’, and ‘‘GLB.EXTDBSTATUS’’. 

SET.DB 

"Interdatabase Access" in your OS 2200 Based LINC Administration and Operations 

Guide. 

v 1-229

SET.TITLE (SETT) 


The SET.TITLE; command enables the name of a Report Extract file to be dynamically 

changed during the running of the Report. 

The SET.TITLE; command explicitly closes the specified Extract file, and defines a 

filename to be used by subsequent DETERMINE; ACTUAL, EXTRACT; or SORT; 

commands. If no pack is specified, the default Extract pack is used. 

For an MCP based LINC System, since SET.TITLE; is a runtime command, it will overwrite 

any TITLE system attribute set (for example, for a Report initiated from RIP). 

Caution 

If you use RETAIN.AS; and SET.TITLE; for the same Extract file in a Report, then 

when the SET.TITLE; command is executed, the Extract file will be purged. You 

should not use both the RETAIN.AS; and SET.TITLE; commands on the same file. 




ends. Use the EXIST; command option with the SET.TITLE; command to specify an 

EXISTING file. 

$ PERMANENT files, which do not exist before the Report begins, but are created by the 

Report and retained after the Report ends. To specify a PERMANENT file, do not use 

the EXIST; command option. 


the Report ends. Including a SET.TITLE; command changes a TEMPORARY file to 

PERMANENT. 

For more details, see ‘‘Categories of Extract file’’ under the ‘‘EXTRACT (EX)’’ command, 

earlier in this section. 

The way a SET.TITLE; command handles an Extract file at runtime is influenced by: 


$ Whether the Extract file has been accessed or not 

The SET.TITLE; command explicitly closes the specified Extract file and changes the 

name of the file. The file category is changed to PERMANENT if the EXIST; command 

option is not included, or to EXISTING if the EXIST; command option is included. The new 

file is not opened until it is accessed by a DETERMINE; ACTUAL, MATCH; EXTRACT; or 

SORT; command. 

1-230 v

Syntax 

On entry to the SET.TITLE; command: 


$ If the file previously was a TEMPORARY file, the file is deleted (if it had been created). 

$ If the file previously was a PERMANENT file, the file is created as an empty file (if it 

does not exist), cleared (if it exists, but has not been accessed), or closed (if it has 

been accessed). 

$ If the file previously was an EXISTING file, the file is closed (if it has been accessed), 

otherwise no action is taken. 

$ The following table shows the actions performed on the Extract file on entry to the 

SET.TITLE; command. 

Current State of file TEMPORARY PERMANENT EXISTING 

File exists Deleted Closed/Cleared No action 

File does not exist No action Created Closed 


File 


File 

File exists Deleted Closed/Cleared No action 

File does not exist No action Created Closed 

DD DDD DDD DDDDD 

DDDBDDDDDDDDDDDDDDDDDDDDDDBDDDDBDDDDDDDDDDBDDDDDDDD4 

3 3 3 3 

@D DD DY @D DY 

extract file 

The one-character Extract file designator, A through Z. 

data name 1 

A data item or literal giving the file name of the Extract file. 


$ For MCP based runtime hosts, the name (in data name 1) may contain any number of 

levels, but cannot exceed 18 characters (including slash characters). System usercodes 

must not be included. If a pack name is specified (in data name 2), the filename length 

can be up to 39 characters less the length of the name of the Extract pack or the length 

of the data name 2 value. 

v 1-231


$ For OS 2200 based LINC Systems, the file name cannot contain more than one asterisk 

character, and cannot be longer than 25 characters. Each portion of the file name, 

before and after the asterisk, cannot be longer than 12 characters. If no asterisk 

character is used, the maximum is 12 characters. 

$ For UNIX LINC Systems, the name may be any valid pathname up to 100 characters in 

length. Within that, the filename may be up to 14 characters in length. If you do not 

specify an absolute path name for the file, the file name is relative to the LINC System 

directory. 

If the Extract file is to go to TAPE, the value of this parameter depends on the host type, as 


ON; data name 2 

Host type Parameter value 

MCP 

environment 

OS 2200 

environment 

Tape name 

Tape serial number 

UNIX Pathname to the tape drive 

Note: This command option is valid only for MCP based LINC Systems. 

This command option gives the disk pack name if the Extract file is to go to disk (that is, 

DISK was selected on the Extract File Options screen). 

EXIST; 

If you include this command option, the file will be treated as an existing file, and it will 

not be cleared unless the first access is by way of an EXTRACT; command. 

If you do not include this command option, the standard SET.TITLE; command will 

operate in the same manner as the RETAINED.AS; command option, namely: 

$ If the first command after the SET.TITLE; is a SORT; or DETERMINE; ACTUAL, 

(without the EXTRACTED.AS; command option), the file will be initialized (created 

with no records). 

$ If the first command after the SET.TITLE; is a DETERMINE; ACTUAL with the 

EXTRACTED.AS; command option, the file will be treated as existing, and it will not 

be cleared or initialized. 

$ If the file is not used after the SET.TITLE; command, then when the Report completes, 

the file will be empty. 

1-232 v

Examples 



The following example will create a physical file that will be given the name entered by the 

user. The file is then loaded by extracting SREP records into it. Assuming this is all the 

code in the Report, at the end of the Report the file will be kept, and it will contain the 

details extracted from SREP. 

 

 

 

 

 

 

 

 

The next example will open the existing physical file that it is identified by the name 

entered by the user. The file is then sorted into name order. Assuming this is all the code in 

the Report, at the end of the Report the file will be kept, with records sorted in ascending 

order of salesrep name. In the code, a dummy DETERMINE; command is used to associate 

the file layout B with the SREP Component. In a normal situation, you would probably use 

such a DETERMINE; command loop to perform a required function; for example, printing 

the sorted file. 

 

 

 

 

 

 

 

 

 

 

 

‘‘EXTRACT (EX)’’ 

‘‘DETERMINE; ACTUAL’’ 

‘‘SORT (SO)’’ 

The subsections on Extract Files and MAPPER Extract Files in the "Interfacing to Other 

Systems" sectionintheLINC Administration and Operations Guide for the relevant host 

type. 

v 1-233

SLEEP (SLP) 

SLEEP (SLP) 

The SLEEP; command suspends execution of a Report. When reactivated, execution 

resumes from the next command in the Report logic. 

The SLEEP; command has the following variants: 

$ SLEEP n 

Any current database transaction is committed, and the Report is suspended for a 

number of seconds (in the range 0 through 9999). The Report is reactivated after this 

time, or if a WAKE.UP; command is received. 

For OS 2200 base LINC Systems, a SLEEP; 0 forces a database commit. A SLEEP; n 

(where n is greater than zero) initiates an end thread, followed by a wait of n seconds, 

followed by a begin thread. 

$ SLEEP; UNTIL WAKE.UP 

Any current database transaction is committed, and the Report is suspended until it is 

explicitly reactivated by a WAKE.UP; command, or termination of the Report. 

$ SLEEP; UNTIL WAKE.UP END.AFTER; n 

Any current database transaction is committed, and the Report is suspended until it is 

explicitly reactivated by a WAKE.UP; command, Report termination, or until after the 

specified number of seconds. In the latter case, GLB.CLOSE is set to CLOSE. 

Note: In a LINC Report generated as a Coroutine, the SLEEP; UNTIL WOKEN 

command performs an end transaction only. See the CALL; command for 

details of Coroutines. 

About the SLEEP; Command 

If GLB.CLOSE equals CLOSE when a SLEEP; command is executed, the Report goes to 

end-of-job. 

Following the SLEEP; command, a new database transaction (thread) will be started. On 

MCP based LINC Systems, this will occur on the first database update following the 

SLEEP; command. 

On OS 2200 based LINC Systems, if your Report is executed with the no restart option on 

the @XQT (@XQT,X), then the SLEEP; will not be actioned. 

On UNIX ORACLE Systems, updates are not available to other processes until a database 

commit occurs, normally at the end of Pre-Screen logic. If a WAKE.UP; command occurs in 

Main logic, and the update has not been committed in the Ispec, it is possible that the 

sleeping Report might not find any outstanding request in the parameter file when it is 

reactivated. This could result in some outstanding requests remaining in the parameter file. 

In LDA Run Time, if a SLEEP; command is executed within a block of logic introduced by a 

loop or a condition, it does not perform a database commit or close command, and 

therefore does not release any database locks that have been set. 

1-234 v

SLEEP (SLP) 


Report Output Control (ROC) Standard Reports 

Syntax 

Examples 

It is recommended that the CRITICAL.POINT; command be used instead of the SLEEP; 

command in Standard ROC Reports, because although a SLEEP; command causes a 

database commit, all ROC Standard Report output may not have been written to the 

appropriate LINC structures (as it is with a CRITICAL.POINT; command). Recovery of the 

output cannot therefore be fully guaranteed. In addition, the values of System Data items 

are not recovered. 

DD DBDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDD4 

3 3 

CDD DBDDBDDDDDDDDDDDDDDDDDDDDDDDDD4 

3 3 3 3 

@DD DDDY @D DD DY 

sleep time 

A numeric data item or constant giving the number of seconds (in the range 0 through 

9999) for which the Report is to be suspended. The Report is reactivated after this time, or 

if a WAKE.UP; command is received. 

timeout 

A numeric data item giving the number of seconds (in the range 0 through 9999) for which 

the Report is to be suspended. The Report is reactivated after this time (and the System 

Data item GLB.CLOSE is set to CLOSE), or if a WAKE.UP; command is received 

In the following example, the Report is suspended for 30 seconds every time Frame 03 is 

printed. 

 

 

 

 

 

 

 

 

 

 

 

 

v 1-235

SLEEP (SLP) 


In the following example, the Report is suspended until the Ispec sends a WAKE.UP; 

command. 

 

 

 

 

 

 

 

‘‘GLB.CLOSE’’. 

 


1-236 v

SORT (SO) 

SORT (SO) 

The SORT; command orders records in an Extract file into ascending or descending order, 

based on the values of data items specified with one or more ASCENDING; and 

DESCENDING; command options. The order of the sort is based on the first data name 

first, then the second, and so on. 

Note: MAPPER Extract files cannot be sorted by using this command. 

The SORT; fields are not qualified. The following rules must be adhered to: 

$ Each sort data item must be in all records of the Extract file. 

$ Each sort data item must be unique within all Frames that are defined for that Extract 

file. 

$ Each sort data item must have the same edit characteristics in all Frames. 

For MCP based and OS 2200 based LINC Systems, you can set the sort memory size on the 

Environmental Options screen. For UNIX LINC Systems, you can set the sort memory size 

using the COBSW switch before running the Report (see your COBOL documentation for 

more information). 

The sorting order is based on the standard character sequence, as for Profiles. For more 

details, see "ASCENDING (ASC)" in your LINC Generate Reference Manual: Painter and 

Editor. 


The Extract file should be opened before the SORT; command is executed. 



ends. Use the EXIST; command option of the SET.TITLE; command to specify an 

EXISTING file. 

$ PERMANENT files, which do not exist before the Report begins, but are created by the 

Report and retained after the Report ends. To specify a PERMANENT file, do not use 

the EXIST; command option. 

v 1-237

SORT (SO) 

Syntax 



These files do not exist before the Report begins, and are deleted after the Report 

ends. To specify a TEMPORARY file, use one of the following logic command 

constructs (and do not include a SET.TITLE; command): 

v EXTRACT; (without the RETAIN.AS; command option) 

v DETERMINE; ACTUAL (without the RETAINED.AS; command option) 

For more details, see ‘‘Categories of Extract file’’ under ‘‘EXTRACT (EX)’’ command, earlier 

in this section. 

The way a SORT; command handles an Extract file at runtime is influenced by: 






The SORT; command attempts to sort the specified Extract file. 

$ If this is not the first access of the file, the file is sorted. 


v If it is not an EXISTING file, the file will be created as an empty file if it does not 

already exist, or it will be cleared if it does exist. 

v If it is an EXISTING file, the file will be sorted if it already exists. If it does not 

exist, the Report will abort (on UNIX and OS 2200 based LINC Systems) or 

become a waiting entry (on MCP based LINC Systems). 

v The following table shows the actions performed on the Extract file if the SORT; 

command is the first access to it. 


File 


File 

File exists Cleared Cleared Sorted 

File does not exist Created Created Wait 

ZDDDDDDDDDDDDDDDDDDDDDDDDDDDDD? 

3 3 

DD DD DABDD DBD DADD4 

3 3 

@D DY 


1-238 v

Examples 

SORT (SO) 

The first ASCENDING; or DESCENDING; command option must be specified on the same 

logic line as the SORT; command. Subsequent ordering command options must be on 

separate lines. 

ASCENDING; 

The ASCENDING; command option is used to sort an Extract file into ascending order, 

based on the value of the specified data item. Several data items may be used to sort the 

file, but each data item requires its own separate ASCENDING; (or DESCENDING;) 


ASCENDING can be abbreviated as ASC. 

DESCENDING; 

The DESCENDING; command option is used to sort an Extract file into descending order, 

based on the value of the specified data item. Several data items can be used to sort the 

file, but each data item requires its own separate DESCENDING; (or ASCENDING;) 


DESCENDING can be abbreviated as DSC. 

data item 

A data item present in all records in the Extract file. Qualification of these items is 

discussed in your LINC Generate Operations Guide. 

Note: The data item must be unique in the Extract file. 

In the following example, Extract file A is sorted into ASCENDING order of INPUT-DATE 

within ASCENDING order of PRODUCT. 

 

 

 

 

 

 

 

 

In the next example, Extract file A is sorted into ASCENDING order of ADDRESS, within 

DESCENDING order of BRANCH, within DESCENDING order of COMPANY. 

 

 

 

 

v 1-239

SORT (SO) 


"Profiles" in your LINC Generate Reference Manual: Painter and Editor 

‘‘SET.TITLE (SETT)’’ 

"Report Environmental Options Screen" in your LINC Generate Operations Guide. 

The subsections on Extract Files and MAPPER Extract Files in the "Interfacing to Other 

Systems" sectionintheLINC Administration and Operations Guide for the relevant host 

type. 

1-240 v

START (ST) 

START (ST) 

Depending on the target host type, this command enables an Ispec or Report to start: 

$ An MCP based WFL Job 

$ An OS 2200 based ECL runstream 

$ A UNIX executable shell script in the background. 

$ A .EXE, .COM or .BAT file in Windows NT or Windows 95. 


Specific details for each target host type are given in the following subsections. 


The START; command enables an Ispec or Report to execute a WFL Job with parameters. 

If the parameter item is a Setup.Data item or a screen item, it must include quotation 

marks, or the WFL will fail. The WFL Job File should be located on the Object pack family, 

or on the alternative (OTHERWISE) pack for the system usercode. It is your responsibility 

to provide a valid parameter as required by the Job. 

Files started in this way will not be attached to (or controlled by) the LINC System. 

The START; command has the following parameters: 

$ A literal or data item giving the 32-character Work Flow Job file. This parameter is 

compulsory. 

$ A literal or data item value (not exceeding 200 characters), being a file equate or a WFL 

string parameter value. This parameter is optional. 

If the length of the first parameter and the length of the second parameter both exceed 18, 

data items must be used (not literals). 

If the file equates, Accept command, or string parameter is invalid, MCP will reject the 

START; command, the program or job will not be started, and the LINC logic will not 

receive notification of the error. 

GLB.STATUS is set to indicate the result of the START; command, as shown in the 


Value Result Indicated 

INVAL The program or job name is invalid or cannot be located. 

Space The MCP has been instructed to start the program or job. 

v 1-241

START (ST) 

To avoid duplication, LINC will only restart jobs in Ispec or Report recovery, where those 

START; commands were apparently not successfully executed for those jobs prior to the 

failure. START; commands that were successfully executed prior to the failure will be 

ignored. 

If the failure is due to a system halt/load, the MCP will automatically restart all jobs that 

were active at the time of the interruption. 

The chargecode that applies to your WFL start is dependent on the values of the :COD LINC 

System command and the GLB.CHARGECODE System Data item. For further details, see 

$ ‘‘GLB.CHARGECODE’’, in this manual 

$ 

$ 

"Setting Chargecodes for LINC Systems and Reports" in your MCP Based LINC 

Administration and Operations Guide 

"Report and WFL Job Chargecodes" in your MCP Based LINC Administration and 

Operations Guide 


The START; command executes an OS 2200 based ECL runstream. The request is passed to 

the LINC Background Run which performs an @START of the runstream. Consequently, 

the run is executed under the same account/userid as the LINC Background Run. 

No status is returned on the success or otherwise of the runstream. 

There is only one parameter for the START; command. This is the element name of the 

runstreams. No parameters can be passed to the runstream. 

All runstreams to be accessed by the START; command must be copied into the following 

file: 

 




INVAL The runstream cannot be located. 

Space The LINC Background Run has been instructed to start the runstream. If for some 

reason it cannot be started, EXEC will reject the START command from the LINC 

Background Run, the runstream will not be started, and LINC logic will not receive 

error notification. 

1-242 v

Syntax 

Caution 

On OS 2200 based LINC Systems, the job will not be restarted during LINC 

Background Run recovery. 


START (ST) 

The START; command enables an Ispec or Report to start an executable shell script. The 

shell script is started in the background, at the end of the current transaction. 




INVAL The script is invalid (permissions) or it cannot be found. 

Space The script has been found and initiated. 

Note: If the Ispec or Report is restarted by LINC Recovery, the START; command is 

executed again, even if the program or job is still active or has successfully 

terminated. 

DD DDDDD DDDBDDDDDDDDDDDDDDDDDBDD4 

3 3 

@DD DDY 

parameter 1 

For an MCP based LINC System, a data item or literal giving the Work Flow Job file name. 

For an OS 2200 based LINC System, a data item or literal giving an element name within 

the START$ file, that contains the runstream to be started. 

For a UNIX LINC System, a data item or literal giving the full pathname of a shell script to 

be executed. May be up to 32 characters. Do not use environmental variables in the 

pathname. 

For LDA, the program or .BAT file to be executed. 

parameter 2 

For an MCP based LINC System, an optional data item or literal giving a WFL string 

parameter value for the job. 

v 1-243

START (ST) 

Examples 

For an OS 2200 based LINC System, this parameter is not required. 

For a UNIX LINC System, an optional data item or literal giving the argument to be passed 

to the shell script. 

For LDA, a set of command line arguments. 


 

The following example shows the use of Setup Data items in a START; command. 

 

 

 

 

 

 

 

 

 


 

UNIX 


 

‘‘RUN’’. 


1-244 v

STN.INFO (SI) 

STN.INFO (SI) 

This command is ignored in LDA Run Time, and its function differs depending on the type 

of host, as described in the following subsections. 


The STN.INFO; command is used to validate a station or printer name. It accesses the 

network file, and stores station or printer information in a specified user data item. 

GLB.STATUS is set to indicate the validity of the supplied station or printer name. It is set 

to five asterisks (*****) if the station or printer name is not valid. 

Station information recalled includes the values shown in the following table (in the listed 

sequence). 

Description Value Field 

Length 

Terminal type TP or VD 2 

Model As declared in network file 10 

Associated Printer or Printer 

Host is recalled 

VD (Associated printer) or TP (Printer Host) 17 

Not used 50 


STN.INFO is valid syntax, but has no effect. It will always return a GLB.STATUS value of 

*****, and clears data item 2 to spaces . 


The STN.INFO; command is used to obtain information about a username in the 

LINCIINET file or an Alias in the LINC Report Output Control System (ROC), as follows: 

$ If the value is found in the LINCIINET file (indicating a username), information is 

returned in the specified data item, as shown in the following table (in the listed 

sequence). 

v 1-245

STN.INFO (SI) 

Syntax 

Description Value Length 

Type VD 2 

Not used 10 

Printer Associated printer 17 

Privilege GLB.PRIV value 4 

$ If the value is not found in the LINCIINET file, the ROC Aliases are then examined. 

$ If the value is a valid ROC Alias is found, information is returned as shown in the 

following table (in the listed sequence). 

Description Value Length 

Type TP 2 

Not used 27 

Alias Full ROC Alias 50 

$ If the name is not found, GLB.STATUS is set to *****. 

DD DDD DDD DDDDDDDD4 

data item 1 

A data item or literal (depending on host type) specifying: 

$ The MCP based station or printer name to be validated 

$ A UNIX username or ROC Alias 

data item 2 

An alphanumeric data item that is to receive the requested information. The minimum 

length for this data item is 79. 

1-246 v

SUBTRACT (SB) 

Syntax 

Example 


SUBTRACT (SB) 

The SUBTRACT; command subtracts the first value from the value in the second data item 

and stores the result in the second data item, or in a third data item if one is explicitly 

specified by the GIVING; command option. 

The GIVING; and ROUNDED; command options can be included with the SUBTRACT; 

command. 

The System Data item GLB.STATUS is not updated by the SUBTRACT; command. Use the 

GLB.STATUS; command to test for arithmetic overflow. 

DD DDD DDD DDDDDD 

DDBDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDDBDDDDDDDDDDDDDDBDDD4 

3 3 3 3 

@DD DD DDY @DD DDY 


A numeric data item or literal giving the value to be subtracted. 


A numeric data item containing the value to be subtracted from. If the GIVING; command 

option is not specified, the result is stored in this data item. (If it is specified, this data item 

is unchanged.) This can be a literal only if the GIVING; command option is used. 



command option must be on the same line as the SUBTRACT; command. GIV is a valid 

abbreviation for GIVING. If it is not included, the result is stored in numeric data 2. 

ROUNDED; 

This command option specifies that the result is to be rounded (rather than truncated). 

 

 


v 1-247

SWITCH.TO (SWT) 


The SWITCH.TO; command enables you to transfer directly to another system by using 

LINC logic. The other system can be: 

$ Another LINC System 

$ Another LINC System running PowerClient 

$ A non-LINC System in an MCP or OS 2200 environment. For example, an MCP based 

CANDE session, or an OS 2200 based 3GL System 

$ A default UNIX or MCP based screen; for example, a Logon or Logoff screen 

Use this command if you want to perform a certain function outside your current LINC 

System without having to go through the procedure of exiting from the LINC System and 

signing on to another LINC System or non-LINC System. 

Once you have completed your task in the other system, you can then switch back to 

where you were, or to a default screen. 

The SWITCH.TO; command can be used in MCP and OS 2200 based LINC Systems, and in 

UNIX LINC Systems that are using LINC Server mode. See your UNIX LINC 

Administration and Operations Guide for details of LINC Server mode for UNIX LINC 

Systems. 

On OS 2200 based LINC Systems, you can use the INHERIT; command option to pass the 

terminal type, language, usercode, and partition (if executed from PowerClient) to the 

destination system, if that destination system is a LINC System. On UNIX and MCP based 

LINC Systems, you cannot pass these values. 

The SWITCH.TO; command is not available in Reports. It sets GLB.ERROR to five asterisks 

(*****). The command is ignored in LDA Run Time. 


LDA Restrictions and Limitiations 

The functionality of the SWITCH.TO; command in LDA differs from host LINC, and has the 

following restrictions and limitations: 

$ The new Business Segment must reside in the same Repository as the calling Business 

Segment. 

$ When the SWITCH.TO; command is executed in LDA Run Time, the current LDA 

session is closed and a new session is opened for the called Business Segment. This 

may take a few seconds, because the .FRM file must be recreated for the called Ispec. 

$ STARTUP and CLOSEDOWN Global Logics cannot be invoked automatically in LDA. 

1-248 v


Host LINC implementation of SWITCH.TO; assumes the disengagement of one LINC 

System and the engagement of another, and does not involve the shutdown of either 

system. The LDA implementation cannot avoid closing down one system before 

engaging the other. Therefore, it cannot be assumed that STARTUP logic has been 

executed in LDA. 

Runtime Requirements 


To use this command on MCP based target hosts, you must install a COMS processing 

item, such as TPTOMARC, for the MARCINPUT agenda. For more details, see your MCP 

Based LINC Installation and Configuration Guide. 

If you switch to an invalid system name, your originating screen is displayed. A message 

informs you that the system you were attempting to switch to is not available. 


You can use this command to switch to another LINC System. If you are switching from a 

System running with PowerClient, and the other LINC System is not generated for use with 

PowerClient, the SWITCH.TO; command will fail and you will be signed off. 


Define the environment variables database_DIR and database_ENV. These variables can 

be defined for each user, for all users of a LINC System, or for all users. See your UNIX 

LINC Administration and Operations Guide for details of environment variables. 

If you attempt to switch to an invalid system name, you will be returned to your originating 

screen if you switch without a BYE command, or logged off if you switch with a BYE 

command. A message is displayed informing you of the unavailability of the system you 

were attempting to switch to. 

Runtime Transaction Flow 

The effects of using the SWITCH.TO; command on transaction flow are as follows. 

$ The SWITCH.TO; command takes effect at the end of the Ispec Logic. This is similar to 

the RECALL; command. 

$ On execution of the command, GLB.ERROR is set to five asterisks (*****). 

$ All logic following the SWITCH.TO; command is processed. 

$ If multiple SWITCH.TO; and RECALL; commands are executed in the same Ispec, only 

the last SWITCH.TO; or RECALL; command executed is actioned. 

$ GLI, OFFLINE, external Automatic Entry (HUB), and OLTP transactions ignore this 

command. 

v 1-249


Syntax 

$ On UNIX and MCP based LINC Systems, you cannot switch to the LINC Report Output 

Control System (ROC) or LINC Ad Hoc Inquiry Utility. Use the ROC.MODE; or 

ADHOC.MODE; commands instead. 

$ On OS 2200 based LINC Systems you can switch to the LINC Report Output Control 

System (ROC). 

$ For an MCP based LINC System you cannot use the DATA; command option when 

switching to a LINC Release 15 System. 

The SWITCH.TO; command has the following syntax: 

DD DD DBDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDD 

3 3 

@D DD DY 

DBDDDDDDDDDDDDDDDDDDDDDDDDBDBDDDDDDBDBDDDDDDDDBDBDDDDDDDDDDBDD4 

3 33 33 33 3 

@ D Y@ Y@ Y@ Y 

system 

An alphanumeric data item or literal specifying the destination system, as follows: 

$ For an MCP based LINC System, a valid window name, or an asterisk (*) for the 

default window name. 

$ For an OS 2200 based LINC System, a valid transaction id. 

$ For a UNIX LINC System, the name of the LINC Database for the target LINC System. 

If you enter an invalid system name, the current screen of your sending LINC System is 

displayed with a message informing you of the unavailability of the target system. 

DATA; data name 

Specifies an alphanumeric data item or literal whose value is to be passed to the target 

LINC System. Up to 1850 characters (1884 on UNIX LINC Systems) may be passed. DATA 

may be abbreviated as DA. 

$ If the first 5 characters of the data make up the name of a valid Ispec, and are followed 

by data in NOF format, normal Pre-LINC and Main Logic of that Ispec is performed. 

NOF format in MCP and OS 2200 environments is defined by the LINCOFF file, while 

on UNIX LINC Systems it is defined by the LINCNOF file. See your UNIX LINC 

Administration and Operations Guide for details of creating the LINCNOF file. 

$ If the first 5 characters of the data make up the name of a valid Ispec, and the sixth 

character is not a T, normal Pre-Screen logic of that Ispec is performed. 

1-250 v


$ For an MCP based LINC System, if the first 5 characters of the data do not contain a 

valid Ispec name: 

v The data will be processed as for a normal station, that has received invalid data or 

LINC System command. 

v If no data is sent, and if the ?OPEN notification is set, and you are going on to the 

window for the first time, the Fireup Ispec is displayed. If no data is sent, and the 

?ON notification is set, and you have been on the same window previously, the 

previous Ispec is displayed. (You must also have either Output protection or 

Logging set.) 

v Otherwise, the Ispec Selection screen (Page 2) is displayed (you are in fact signed 

on to the destination system). 

$ For an OS 2200 based LINC System, if the first 5 characters of the data do not contain a 

valid Ispec name: 

v If no data is sent and if the destination system is not being re-entered, then the 

Fireup Ispec of the destination system is displayed. If the destination system is 

being re-entered (that is, you previously exited or switched out of the system 

without using a BYE command), then the Pre-Screen Logic of the Ispec that was 

current at the time of the exit will be performed. 

v Otherwise the Ispec Selection screen (Page 2) is displayed. 

$ For a UNIX LINC System, if the first 5 characters of the data do not contain a valid 

Ispec name: 

v If the data is a valid LINC System command, the command is processed. 

v If no data is sent, the Fireup Ispec is displayed. 

v Otherwise, the Ispec Selection screen (Page 2) is displayed. 

If your data requires a transaction number, set the value of TRANNO in your data 

to zero. This will avoid the possibility of your transaction being rejected with a 

duplicate transaction number. 

PARTITION; partition 

Specifies an alphanumeric data item or literal whose value is a partition name for 

PowerClient. The value may be up to 19 characters long. PARTITION may be abbreviated 

as PA. 

When using PowerClient (PCE) with the SWITCH.TO; command: 

$ Do not use the prefix LINC for a partition name. 

$ The value of the system is used if no value is supplied. 

$ In PowerClient on UNIX LINC Systems, the Ispec in the current LINC System is 

displayed if you switchback from your destination LINC System. . 

$ For an MCP based LINC System, the Fireup Ispec is displayed when you switch back, 

unless an Ispec is explicitly specified using the DATA; command option with the 

SWITCH.TO; command. 

v 1-251


$ On OS 2200 based LINC Systems, if the INHERIT; command option had been used 

when the SWITCH.TO; was executed, you can use the System Data items 

GLB.ORIGINPTN, GLB.ORIGINISPEC, and GLB.ORIGINXNID to switch back to the 

originating LINC System. 

In the destination LINC System, the values of these System Data items are defined if 

the SWITCH.TO; command was executed with the INHERIT; command option. The 

values of these System Data items are initialized to spaces if you access another Ispec 

in the destination system. 

Note: You must target another PCE application when you use the 

SWITCH.TO command from a PCE station. Switching to a LINC 

window with data, if that window is not another PCE application, 

will result in the receiving non-PCE window receiving error 

messages about non-PCE format input. Further input from the PCE 

station receives the message; "Transmission inhibited as a 

transaction is in progress". 

If the PARTITION; command option is executed on a terminal that is not using 

PowerClient, the command option is ignored. 

BYE; 

Including the BYE; command option signs you off from the originating system. 

You can perform a RECALL; (BYE) command to log off from your LINC System even if you 

have a Report running. If the Report attempts to access the terminal from which you 

logged off, it will terminate abnormally. 

For an MCP based LINC System: 

$ If you sign back onto the original system, an ?OPEN notification is sent, and the Fireup 

Ispec is displayed. 

$ If you switch back to the system with data, the data you send with the SWITCH.TO; 

command overrides the ?OPEN notification. 

For an OS 2200 based LINC System, if the BYE; command option is not specified, the 

current Ispec is retained in the STN (station id) file. If you sign back on to, or switch to the 

original system by using the SWITCH.TO; command, the original Ispec is displayed. 

ForaUNIXLINCSystem: 

$ If BYE; is not included, you remain signed on to original system as well as the target 

system. 

$ If you are running a Report (initiated by using the LINC System command :RUN or the 

LINC logic command RUN;) with device type of VD, a SWITCH.TO; command with the 

BYE; command option causes an error. You must first terminate the Report. 

1-252 v

Examples 

CLEAR; 


This command option applies to OS 2200 based LINC Systems only. Specifying the CLEAR; 

command option: 

$ Resets the page control for the terminal. 

$ Clears the screen before switching to the destination. 

$ Resets the page control for the terminal before switching. 

This sets the page control variables to those defined in the CTLPAGE SGS statement. 

CLEAR may be abbreviated as CL. 

INHERIT; 

This command option applies to OS 2200 based LINC Systems only. Specifying the 

INHERIT; command option passes the terminal type, language, usercode, and partition (if 

executed from PowerClient) to the destination system, if that destination system is a LINC 

System. 

In the destination LINC System, the values of the System Data items GLB.ORIGINPTN, 

GLB.ORIGINISPEC, and GLB.ORIGINXNID are set, so that you can switch back to that 

system if required. See Section 2 for details of these System Data items. 

INHERIT may be abbreviated as IN. 

In the following example, SWITCH.TO; commands are used to in a variety of ways on an 

MCP based LINC System. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

v 1-253



The following line of logic switches the user to the LINC System MENUSYSTEM, and 

executes Pre-Screen logic for the Ispec SALES. 

 

The following logic is used with a LINC System being run using PowerClient. The Ispec 

TWOIS is accessed in the LINC System DWTWO in PowerClient partition DWLINCTWO. 

 

‘‘GLB.ERROR’’, ‘‘GLB.ORIGINISPEC’’, ‘‘GLB.ORIGINPTN’’, and ‘‘GLB.ORIGINXNID’’. 

The Interfaces section in the LINC Administration and Operations Guide for the relevant 

host type, for details of LINCOFF date format. 


1-254 v

TRACE (TR) 

Syntax 

Example 

TRACE (TR) 

The TRACE; command forces trace output to be written (if TRACE; has been enabled for 

the Ispec or Report in which it appears). 


DDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD4 

 

 

 

 


The Trace function is described in more detail in your LINC Generate Operations Guide, 

andinyourLINC Administration and Operations Guide for the relevant host type. 

v 1-255

UPPER.CASE (UC) 

UPPER.CASE (UC) 

Syntax 


The UPPER.CASE; command enables you to convert the value of an alphanumeric data 

item to uppercase. The characters a through z are converted to A through Z respectively. 

Embedded digits or non-alphabetic characters are unchanged. 

Data items used in UPPER.CASE; commands cannot exceed 2000 characters. 

This command will use the appropriate CCS Version routines if they are available. 

Note: OS 2200 Series based LINC Systems support only the US English ASCII 

character set. UNIX and MCP based character conversions use standard system 

utilities. 

DDDD DDD DDDDDDDDDDDDDDDDDDDD4 

data item 

An alphanumeric data item, Setup Data item, or Global Setup Data item (including Group 

Setup Data items and Group Global Setup Data items). It is not valid for literals. 

‘‘LOWER.CASE (LC)’’. 

1-256 v

WAKE.UP (WU) 

WAKE.UP (WU) 

The WAKE.UP; command is used to reactivate a Report suspended by a SLEEP; or 

CRITICAL.POINT; command. When a WAKE.UP; command is executed, a message is sent 

to the specified Report (if it is not running, the message is discarded). If multiple copies of 

the Report are running, each copy is sent a message. The WAKE.UP; command can be 

executed from a Report. 

Reports check for wake up messages when the following commands are executed: 

$ SLEEP; 

$ CRITICAL.POINT; 

When WAKE.UP; Commands Are Not Sent 

WAKE.UP; commands are not sent in the following circumstances: 

$ If the nominated Report is not running, the message is discarded. 

$ For an MCP based LINC System, the WAKE.UP; command is ignored in standalone 

Reports and in LINC Reports generated as Coroutines. See the CALL; command for 

details of Coroutines. . 

$ For an MCP based LINC System, if the Report currently has 63 outstanding input 

messages a WAKE.UP; command is not sent. 

$ For a UNIX LINC System, each message is sent if there are sufficient message queue 

resources to permit immediate queuing. Queues depend on user customization of the 

host and the current resource utilization. 

$ On all hosts, queued wake ups will not be recovered. 

Passing Parameters 

You can optionally specify a parameter of up to 254 characters, to be passed to the 

specified Report with the WAKE.UP message. The parameter can be specified using a data 

item name or literal. (In order to process the parameter data, the Report you are waking up 

must have been generated with a dataname on the Report Options screen, to contain the 

parameter data. For more details, see your LINC Generate Operations Guide.) 

If a parameter is passed, the System Data item GLB.PARAMFLAG is automatically set to Y, 

in the Report, to signal that there is parameter data included with the WAKE.UP; 

command. GLB.PARAMFLAG is reset to the appropriate value (which depends on whether 

data has been sent) at the next SLEEP; command or CRITICAL.POINT; command with 

SLEEP; command option. 

With the parameter you can also specify a data item to store the contents of GLB.STATUS. 

GLB.STATUS is set to (*****) if data is being passed but there is no eligible target Report. 

v 1-257

WAKE.UP (WU) 

Syntax 

Example 

Parameter data is not saved for recovery. 

Note: For UNIX and MCP based LINC Systems, if the WAKE.UP; command includes 

parameter data it is queued for all copies of the Report. On OS 2200 based 

LINC Systems the data is only queued for sleeping Reports. 

LDA 

Like host LINC, LDA gives the Ispec no indication of the success of a WAKE.UP; command. 

The WAKE.UP; command will wake any sleeping Reports on your workstation that have 

the same Repository path, Business Segment name, or Report name. 

The WAKE.UP; command will only reactivate a Report on the workstation through which 

the command is given. 

SLEEP; UNTIL WAKE.UP; is a valid alternative to the SLEEP; UNTIL.WOKEN command. 

DD DD DDBDDDDDDDDDDDDDDDDDDDDDDBDDDD4 

3 3 

@DD DD DDY 

report name 

A data item or literal giving the Report name. 

parameter 


A data item or literal giving an optional parameter value to be passed to the Report. 

 

 

 

‘‘SLEEP (SLP)’’. 

‘‘CRITICAL.POINT (CP)’’. 

‘‘GLB.PARAMFLAG’’. 

1-258 v

Section 2 

System Data Items 

Overview 

System Data items can be considered as system-defined Global Setup Data items. They can 

be referenced in the logic of Ispecs and Reports (and Global Logic for Ispecs or Reports). 

The values of some System Data items can be changed, although many are read-only and 

can be used only for reference. 

COBOL Syntax Errors 

The following list shows some circumstances when you may receive COBOL Syntax Errors: 

$ For an MCP based LINC System, some System Data items can only be used in Reports 

and Shadow Reports generated for use with the LINC Report Output Control System 

(ROC). Including such items in non-ROC Reports will cause COBOL syntax errors 

when the Report is compiled. 

$ For an OS 2200 based LINC System, if you code certain System Data items for a 

Shadow Report, to avoid COBOL syntax errors you must also code a PRINT.FRAME; 

command for that Shadow Report (the PRINT.FRAME; command may never be 

executed). 

Conventions for this Section 

The following general statements apply throughout this section: 

$ System Data items can be assumed as valid for use in Ispec and Report logic, and for 

Global Logic used in Ispecs or Reports, unless explicitly stated otherwise. System Data 

items available in Global Logics depend on where the Global Logics apply (Ispecs or 

Reports). 

$ System Data items can be assumed as valid for all types of host (MCP based, OS 2200 

based, and UNIX), unless explicitly stated otherwise. 

$ Further restrictions may be contained in the individual System Data item descriptions. 

v 2-1

Screen Heading Information 

Screen Heading Information 

System information is contained in the first 32 characters of the first line of every Ispec 

screen, and is also included in the Auto Entry buffer. 

This information is contained in a number of System Data items and can be accessed 

through these items, which are listed in the following table. 

Description Name Length Edit type 

Ispec name ISPEC 5 A 

Message Type GLB.SOURCE 1 A 

Transaction reference number TRANNO 6 N 

System input date INPUT-DATE 7 A 

Accounting period ACTMTH 4 N 

Maintenance type MAINT 3 A 

In Events, the System Data items TRANNO, INPUT-DATE, and ACTMTH are included in 

the LINC database record. 

The System Data item MAINT appears only for Standard, Table, Direct, or Multiple 

Ordinate Memo Components. When moving values to MAINT you should use GLB.ADD, 

GLB.CHG, and so on (instead of literals ADD, CHG, and so on). The full list of these 

System Data items is described in the subsection on the MAINT System Data item later in 

this section. 

2-2 v

Recovery of System Data Items 


For Ispecs, recovery is back to the start of the transaction, which means that System Data 

items will return to the initialized state (spaces, zeros, or the relevant system settings that 

apply to some items). 

For Reports, see the following table. 

Three columns in the table require further explanation. 

Report Type 

The values for this column indicate the types of Report for which a given System Data item 

is applicable, as shown in the following table. 

Report Type Description 

D ROC Direct Report 

S ROC Standard Report 

N Non-ROC Report (MCP based LINC Systems only) 

x All Shadow Reports (Non-ROC MCP based LINC System Reports only) 

Value On Recovery 

The values under their subheadings indicate the value that the System Data item will be set 

to on recovery for ROC and MCP based non-ROC Reports respectively, as shown in the 


Entry System Data item value on Recovery 

ST Initial value or default value as at start of Report 

FO Value it contained when the print file was opened 

CP Value it contained at the last CRITICAL.POINT command 

RS Value when Report restarted 

Host Types 

The values in this column indicate the valid host types, with a one-character designation 

for each, as shown in the following table. 

v 2-3


Notes: 

Value Host Type 

A MCP based 

U UNIX 

2 OS 2200 based 

$ System Data items that have different values for Shadow Reports are shown with an 

x suffix; for example, GLB.FORMDEPTHx, where x represents the one-character 

Shadow Report designator (A through Z). Thus GLB.FORMDEPTHA refers to the 

value for Shadow Report A, and so on. 

$ Not all System Data items listed apply to all host types. 

System Data 

Item 

Applies to 

Report 

Type 

Value 

On Recovery: 

ROC 

Value 

On Recovery: 

Non-ROC 

Hosts Possible values 

ACTMTH DSNx RS RS AU2 Account Month 

(YYMM) 

GLB.APPNAME DSNx ST ST 2 Application group 

name 

GLB.APPNO DSNx ST ST 2 Application number 

GLB.ASCPRT DSNx ST ST AU Terminal printer name 

GLB.ASCPRTHOST DS ST A Host Name for 

terminal Printer 

GLB.BACKUPx DNx ST ST A Y, R, or space 

GLB.BASE DSNx ST ST AU2 Base year 

GLB.CCS DSNx ST ST 2 Coded char.set ID 

(LT300 terminals) 

GLB.CENTURY DSNx RS RS AU2 Century number 

GLB.CENTURY-START 

DSNx RS RS AU2 Century number 

GLB.CHANGE DSNx ST ST AU2 ON.CHANGE Data 

item name 

GLB.CHARGECODE 

DSNx ST ST A Chargecode 

GLB.CLOSE DSNx ST ST AU2 Spaces or CLOSE 

continued 

2-4 v

continued 

System Data 

Item 

Applies to 

Report 

Type 

Value 

On Recovery: 

ROC 

Value 

On Recovery: 

Non-ROC 



GLB.DATE DSNx RS RS AU2 Current date 

GLB.DBG- items DS ST ST 2 Debug trace level 

GLB.DC- items DSNx RS RS AU2 Formatted date 

GLB.DESTENV DSNx ST ST U2 Destination:- Oracle 

SID (U)- Environment 

(2)- Spaces (A) 

GLB.DESTHOST DSNx ST ST AU2 Destination hostname 

GLB.DESTINATION DSNx ST ST AU2 Dest db name 

(A,U)TIP tran no. (2) 

GLB.DESTNOFORM 

DSNx ST ST AU2 NOF program (A,2) 

Initiator process (U) 

GLB.DEVICEx DSNx FO ST AU2 DI,LP,RP,TP,VD, 

EX(U), spaces 

GLB.ERROR DSNx ST ST AU2 Spaces or ***** 

GLB.EXNAME DSNx ST ST A AEXT exception 

dataname 

GLB.EXTDB DSNx ST ST 2 Interdatabase access 

db name 

GLB.EXTDBSTATUS 

DSNx ST ST 2 Interdatabase access 

status 

GLB.EXTEXT DSNx ST ST A AEXT exception text 

GLB.FILEINFO DNx ST ST A YorN 

GLB.FILLER DSNx ST ST AU2 Data value 

GLB.FORMDEPTHx DSNx CP ST AU2 Lines per page 

GLB.FORMIDx DS FO AU2 Form name 

GLB.GUI DSNx ST ST AU2 Source terminal type 

GLB.HUBSTATUS DSNx ST ST AU2 Auto Entry (Hub) 

Status 

GLB.HUBTIMEOUT DSNx ST ST AU2 Hub timeout value, as 

GLB.HTIMEOUT 

v 2-5


continued 

System Data 

Item 

Applies to 

Report 

Type 

Value 

On Recovery: 

ROC 

Value 

On Recovery: 

Non-ROC 


GLB.INITSTN DSNx ST ST AU2 Station name 

GLB.LENGTH DSNx ST ST AU2 Data item length 

GLB.LINECOUNTx DSN CP ST AU2 Report line number 

GLB.LINEUPx DSNx FO ST A Y = Special stationery 

GLB.LINEUPNAMEx 

DSNx FO ST A Page lineup file name 

GLB.MACHINE DSNx ST ST AU2 Host type A, U or 2 

GLB.MATCH DSNx ST ST AU2 Extract file to be read 

GLB.NUMCOPIESx DSNx FO ST AU2 Number of Report 

copies 

GLB.ORIGIN DSNx ST ST AU2 AUTO origin db 

GLB.ORIGINENV DSNx ST ST U2 Origin Oracle SID (U) 

Environment (2) 

Spaces (A) 

GLB.ORIGINHOST DSNx ST ST AU2 Origin Host name 

GLB.PAGECOUNTx DSNx CP ST AU2 Current page number 

GLB.PARAM DSNx ST ST AU2 Parameter area 

GLB.PARAMFLAG DSNx ST ST AU2 Parameter indicator 

for WAKE.UP 

GLB.PITCHx SNx CP ST A2 Print pitch 

GLB.PRINTATx D ST A END or RELEASE 

GLB.PRINTBANNERx 

DSNx FO ST A YorN 

GLB.PRINTHOSTx DSNx FO ST A Printer host name 

GLB.PRIV DSNx FO ST AU2 Privilege 0 to 15 

GLB.PRODUCT DSNx ST ST AU2 LINC, LITE, or LDAIII 

GLB.PRTPARAM DSNx FO ST 2 Data for USERPRT 

handler 

GLB.RECORDy DSNx ST ST AU2 Extract file record 

number 

2-6 v

continued 

System Data 

Item 

Applies to 

Report 

Type 

Value 

On Recovery: 

ROC 

Value 

On Recovery: 

Non-ROC 



GLB.RECOVER DS ST AU2 Recovery startup 

indicator 

GLB.REPGENDATE DSNx ST ST AU2 Generate date 

GLB.REPGENTIME DSNx ST ST AU2 Generate time 

GLB.REPLANG DSNx ST ST AU2 Language name for 

Report 

GLB.REPNAME DSNx ST ST AU2 Name for Report 

GLB.REPORT DSNx ST ST AU2 Event record status 

GLB.REPUNIQUE DSNx ST ST A Report unique number 

GLB.REPVERSION DSNx ST ST AU2 Report version 

number 

GLB.ROCFLAG DS ST AU2 Rorspace 

GLB.SAVEDAYSx S FO AU2 Days to keep output 

GLB.SECONDARY DSNx ST ST A Secondary db run: Y 

or N 

GLB.SELF DSNx ST ST AU2 Current db name (AU) 

or Tranid (2) 

GLB.SELFDB DSNx ST ST 2 Current database 

name 

GLB.SELFENV DSNx ST ST U2 Own Oracle SID (U) 

Environment (2) 

spaces (A) 

GLB.SELFHOST DSNx ST ST AU2 Own host name 

GLB.SHADOW DS FO AU2 Shadow Report name 

GLB.STATIONx DSNx ST ST A2 as GLB.STN 

GLB.STATUS DSN ST ST AU2 Result status 

GLB.STNx DSNx CP ST AU2 Destination of Report 

GLB.STNHOST DSNx ST ST A Hostname 

GLB.STYLE DSNx ST ST AU2 Source terminal type 

v 2-7


continued 

System Data 

Item 

Applies to 

Report 

Type 

Value 

On Recovery: 

ROC 

Value 

On Recovery: 

Non-ROC 


GLB.SYSGENDATE DSNx ST ST AU2 System Generate date 

GLB.SYSGENTIME DSNx ST ST AU2 System Generate time 

GLB.SYSVERSION DSNx ST ST AU2 System version 

number 

GLB.TASK DSNx ST AU Report run result 

GLB.TIME DSNx RS RS AU2 Time (HHMMSSTT) 

GLB.TITLEx DSNx FO ST AU2 Print file id 

GLB.TOTAL DSNx ST ST AU2 Numeric value 

GLB.TRANSTATE DSNx ST ST A Transaction state 

GLB.USERx SNx FO ST AU2 User id for output 

GLB.VERSIONID DSNx ST ST AU2 Version description 

GLB.YYMMDD DSNx RS RS AU2 Current date 

GLB.2PC DSNx ST ST AU2 2-phase commit: Y or 

N 

ISPEC DSNx ST ST AU2 Ispec name 

LAST-LINE DSNx ST ST AU2 Repeat.From line 

number 

MAINT DSNx ST ST AU2 Component action: 

ADD, CHG, DEL, INQ 

TODAY DSNx RS RS AU2 Initiation date 

TODAYS-DATE-NUM 

DSNx RS RS AU2 Initiation date, 

MMDDYY 

TRANNO DSNx ST ST AU2 Transaction number 

2-8 v

System Data Item Descriptions 

ACTMTH 


The System Data items are described in the sections below, and listed in alphabetical order. 

In an Ispec, ACTMTH contains the current accounting month in the form YYMM. If debug 

date and time is activated, it contains the month of the current debug date. In a Report, it 

contains the ACTMTH value from the last Event record read. It appears on all Ispec screen 

formats, and is available to all logic. It is included in Event database records. 

ACTMTH may be assigned the NOT.ENTERED attribute for a particular Ispec, by selecting 

an option on the Ispec Option screen. 

LENGTH = 4 EDIT = N 

Using ACTMTH After the Year 2000 

The length of the System Data item ACTMTH is 4. If you use ACTMTH as a Profile 

Ordinate, you should consider replacing it with a data item of length 6 in order the include 

the century. 

GLB.ACTIONKEY 

Note: This System Data item is valid in Ispecs for an OS 2200 based LINC System 

only. It is available in LDA and may be tested using LDA Run Time. 

GLB.ACTIONKEY is a read-only System Data item containing the value of the Function 

Key pressed (if you are using the FKHANDLE SGS statement). If you are trapping EXIT or 

BYE, this data item will contain EX or BY if an EXIT or BYE request is made, respectively. 

The value in GLB.ACTIONKEY is retained across recalls to other Ispecs. You may need to 

check the value of GLB.PREVISPEC against the value of ISPEC to make sure it contains 

the value of the current Ispec. For an example of the code required to test the value of 

GLB.PREVISPEC, see your OS 2200 Based LINC Administration and Operations Guide. 

LENGTH = 2 EDIT = A 

LDA 

The GLB.ACTIONKEY stores the value of the function key selected from the LDA Run 

Time Action Key dialog box. The function keys available are listed in the following table. 

v 2-9


GLB.ADD 

GLB.ALTUSER 

Function 

Key 

Description 

F2 Display Page 2 format 

line 

F3 Display multiple error 

messages 

F4 Display available 

Teach screen 

F6 Refresh current 

screen 

F13 Transmit the screen 

to LINC system 

F21 Exit from LINC 

system, retaining the 

current ISPEC name 

and user code 

F22 SignofffromLINC 

system 

GLB.ADD is a read-only System Data item. It can be used in place of the literal ADD,to 

allow for translation of MAINT values in multiple-language systems. 

For more details, see the MAINT System Data item, later in this section. 

Note: This System Data item is valid for MCP based LINC Systems using non ROC 

TP Reports. 

GLB.ALTUSER associates an alternative MCP based user name with output from Terminal 

Printer Spooler (TPS) Reports, for security purposes. You may sign on to TPS with the user 

name that is stored in GLB.USER or GLB.ALTUSER. 

GLB.ALTUSER may be used for Shadow Reports, in the form GLB.ALTUSERx, where x is 

the one-character Shadow Report designator (A through Z). 

Once output from a Report has been produced, the value of GLB.ALTUSER remains until 

the next RELEASE; command or end-of-job, when the most recent change to its value is 

effected. 

GLB.ALTUSER has a default value of spaces. 

2-10 v

GLB.ALT.USER is a synonym for GLB.ALTUSER. 


GLB.APPNAME 

GLB.APPNO 

GLB.ASCPRT 


Note: This System Data item is valid for an OS 2200 LINC System only. 

Use this read-only System Data item in conjunction with Interdatabase access and with 

Global Logics. It contains the name of the application group in which your LINC System is 

running. 


Note: This System Data item is valid for OS 2200 environments only. 

Use this read-only System Data item in conjunction with Interdatabase access and with 

Global Logics. It contains the number of the application in which your LINC System is 

running. This value is passed to HUB when an incorrect Environment is registered. 


Note: This System Data item is valid only for MCP based and UNIX hosts. 


GLB.ASCPRT contains the name of the printer associated with a terminal that is specified 

in the LINC Network Configuration System with the ASSOC.PRINTER option, and stored 

in the LINC/NET file. Its value may be read but not updated in logic. If output is sent to a 

device type of TP and GLB.STN is not specified, then GLB.ASCPRT (if specified) will be 

used as the output printer. 

The default value is NILNILNILNILNILNI. 


UNIX 

GLB.ASCPRT contains the name of the alias associated with a usercode that is specified in 

the LINCIINET file. This name is moved to the print destination GLB.STN when the output 

report type is TP. 

v 2-11


For related information, see the System Data item GLB.STN. For more details of the 

LINCIINET file, see your UNIX LINC Administration and Operations Guide. 


GLB.ASCPRTHOST 

GLB.BACKUP 

Note: This System Data item is valid only for MCP based Report logic. 

GLB.ASCPRTHOST contains the name of the host computer controlling the GLB.ASCPRT 

printer, as specified in the LINC Network Configuration System, and stored in the 

LINC/NET file. 

This item is available only for MCP based LINC System Reports that use the Report Output 

Control System (ROC). For related information, see also the GLB.STN and GLB.ASCPRT 

System Data items in this section. 



For non-ROC Reports, move Y to GLB.BACKUP to retain Report output directed to TP 

devices only (the Report output is retained regardless of the setting of the REMOVE 

command). If GLB.BACKUP contains any value other than Y, the Report output is deleted 

after printing. 

For ROC Direct Reports, move Y to GLB.BACKUP to retain the printer backup file for your 

main Report, or move Y to GLB.BACKUPx to retain the printer backup file for a Shadow 

Report (where x is the Shadow Report designator). If the System Data item contains any 

value other than Y, the printer output backup file is removed after printing. 

GLB.BACKUP cannot be used for ROC Standard Reports. 

Once output from a Report has been produced, the value of GLB.BACKUP remains until 

the next RELEASE; command (or end-of-job), when the most recent change to 

GLB.BACKUP is effected. 


2-12 v

GLB.BALANCE 


Note: GLB.BALANCE is valid in Ispecs only. It is not implemented in LDA Run Time. 

GLB.BALANCE is used in conjunction with Repeat.From Ispecs. The value of 

GLB.BALANCE (if it is used in the logic of the Ispec) is displayed in the status line of the 

screen, after each Repeat.From line has been transmitted. 

Only ten characters (including the decimal point, two decimal digits, and sign) are 

displayed in the status line. Truncation of the whole number part to six digits can thus 

occur. 

Maintenance of the value of GLB.BALANCE is your responsibility. Any combination of 

data items whose sum over the transaction should balance to zero can be specified. 

If GLB.BALANCE is not zero after the last Repeat.From line (that is, the balance is 

non-zero after 999 is entered in LAST-LINE to end the transaction), an error message is 

displayed. This system-generated error message does not inhibit the 999 line updating the 

database, and thus your logic should include setting GLB.ERROR to five asterisks (*****) if 

you do not want the 999 line to update the database. 

You cannot start a new transaction until the value of GLB.BALANCE equals zero. (Note 

that in Pre-Screen logic for Repeat.From Ispecs, LAST-LINE is always equal to 1, even 

though Pre-screen logic is performed for each line. 

In the following example, a Repeat.From Event includes one BATCHTOT item, and an 

AMOUNT item for each Repeat.From line. If the sum of the AMOUNT values is not equal to 

BATCHTOT, an error message is displayed and the database is not updated. 

The associated logic is: 

 

 

 

 

 

 

 

 

 

 

GLB.BALANCE is recovered automatically after an abnormal system shutdown. 

See your LINC Generate Operations Guide which includes notes on the use of 

GLB.BALANCE. 

LENGTH = 16 EDIT = + DECIMALS = 4 

v 2-13


GLB.BASE 

GLB.CCS 

GLB.BASE is a read-only System data item which holds the value of the year upon which 

relative day numbers are based. Its value is used by the complex form of the 

DATE.CONVERT; command. 

The value of GLB.BASE is set on the Specification Options screen, using the Base year 

field. You can set this field to any year in the range 0001 through 9999. The default value is 

1957. 


Note: This System Data item is valid for an OS 2200 based LINC System only. 

GLB.CCS is a read-only System Data item that stores the Coded Character Set (CCS) 

identifier (CCS ID) for input messages from LT300 terminals. It can be accessed in Ispecs 

and Reports. 

For example, when using the GLB.CCS in your LINC logic: 

$ You can define a data item in your LINC database to contain the CCS of the data. Then, 

on input, move GLB.CCS to your data item to indicate the CCS of the data input from 

the LT300 terminal. 

$ When processing a record in your database, you can use the CCS when making data 

comparisons to distinguish names in different character sets. You could use the CCS as 

an Ordinate of a Profile, so that you can access names in name order within a 

character set. 

$ When outputting to the screen, you can compare the CCS stored in the database with 

GLB.CCS. If the values do not match, a message can be output to advise that the data is 

in a character set that cannot be displayed on the screen. 

For details about the available character sets and their CCS IDs, see the OS 1100 EXEC 

System Software Executive Requests Programming Reference Manual and the Message 

Control Bank (MCB) Programming Reference Manual. For guidelines on 

internationalizing applications for an OS 2200 environment, see the Internationalization 

(I18N) Planning and Implementation Overview. 

GLB.CENTURY 


Use GLB.CENTURY in conjunction with the DATE.CONVERT; command. If your input to 

the DATE.CONVERT; command does not contain the century, you should move the 

century into GLB.CENTURY. 

2-14 v


Date conversion from a relative day number to a date format (using the FORMAT; option 

of the DATE.CONVERT; command) updates GLB.CENTURY. 

The value of GLB.CENTURY is changed to the current century by complex 

DATE.CONVERT; commands if you entered Y in the DC; sets GLB.CENTURY field on 

the Primary Specification Options screen. If you entered N, GLB.CENTURY is not changed 

by the DATE.CONVERT; command. 

See also GLB.DC-CC and GLB.CENTURY-START. 


GLB.CENTURY-START 

GLB.CHANGE 

Use GLB.CENTURY-START in conjunction with the DATE.CONVERT; command to define 

how six digit dates (those without an explicit century) are to be interpreted. 

GLB.CENTURY-START defines the first year of a 100 year period, and all six digit dates are 

interpreted as being in that period. 

By default, GLB.CENTURY-START is set by the SCENTURYnnnn Supervisor command. If 

it is not set, GLB.CENTURY-START is the same value as GLB.BASE. 

GLB.CENTURY-START is restored to its default value at the start of PreScreen logic. 

See also GLB.CENTURY, GLB.BASE, GLB.DC-CC, and the DATE.CONVERT; command. 


GLB.CHANGE is a read-only System data item you use in conjunction with the 

ON.CHANGE; command in Reports. It contains the name of the data item whose change in 

value invoked the printing of a current heading or footing. See ‘‘ON.CHANGE (OCH)’’ in 

this manual for further details. 


GLB.CHARGECODE 

Note: This System Data item is valid for an MCP based LINC System only. 

GLB.CHARGECODE defines the chargecode to be used with the RUN; and START; logic 

commands on an MCP based LINC System. It can be used in Reports to access the 

chargecode used to run the Report. 

GLB.CHARGECODE is ignored if the :COD LINC System command is set to 0. 

v 2-15


GLB.CHG 

GLB.CLOSE 

GLB.COPY 

The chargecode that applies to your Report run or WFL job initiation is the chargecode 

contained in GLB.CHARGECODE when the RUN; or START; logic command is executed. 

RIP reports that are run from WFL have the chargecode set to the name (usercode)station. 

RIP reports that are not attached to a terminal have the chargecode set to LINCRIP. 

Move the chargecode value into GLB.CHARGECODE before the appropriate RUN; or 

START; Logic command. Do not include the period on the end of your chargecode, as this 

is automatically appended. 

For further details, see your MCP Based LINC Administration and Operations Guide. 


GLB.CHG is a read-only System Data item. It should be used in place of the literal CHG,to 



GLB.CLOSE is a read-only data item used in conjunction with the SLEEP; command in 

Reports. 

If a manual stop (for example, from the :STO LINC System command) or a programmatic 

stop (invoked by the END.AFTER; option of the SLEEP; command) is received by the 

Report, GLB.CLOSE is set to CLOSE, and the Report is reactivated. This enables 

termination logic, such as printing a summary, to be performed. 

If a SLEEP; command is executed when GLB.CLOSE has the value CLOSE, the Report 

goes to end-of-job. 

GLB.CLOSE is set to GLB.SPACES when a Report is initiated. 


GLB.COPY is a read-only System data item that contains the number of the current copy in 

a Copy.From Ispec. GLB.COPY can be compared to the System Data item GLB.MAXCOPY 

to determine whether the logic is being performed for the final time. 

In non-Copy.From Ispecs, GLB.COPY is always zero. 


2-16 v

GLB.CORSTATUS 

GLB.DATE 


Note: This System Data item is valid on MCP based hosts and is also supported in 

LDA. 

GLB.CORSTATUS is a read-only System Data item that is set when a Coroutine is executed 

by using the CALL; command. Valid values of GLB.CORSTATUS are listed in the following 

table. 

Value Execution 

spaces Successful 

MWAIT Failed: resource deadlock exceeded the system MAXWAIT timeout 

DMERR Failed: fatal DMS error 

INVKY Failed: invalid key in LINCNET file 

PRINT Failed: Coroutine restarted after approaching limit of 1000 file opens 

permitted in a BD file 

***** Failed: unspecified error 

LENGTH = A EDIT = 5 

GLB.DATE is a read-only System data item that contains the current date, or the debug 

date if debug date and time is activated. Its format is the same as the System Data item 

TODAY (or GLB.TODAY). For example, if the Date format IN UK or US field (on the 

Primary Specification Options screen) is set to UK, GLB.DATE will be in the form 

DDMMMYY (for example: 04JUL98). 


GLB.DBG- System Data Items 

Note: This series of System Data items applies to OS 2200 based LINC Systems only. 

This series of System Data items is used when the debug trace facility has been initiated 

with the LINC Colon command :DGB. These items contain the current level of debug trace. 

The System Data items in this series are: 

$ GLB.DBG-DB 

$ GLB.DBG-LG 

v 2-17


GLB.DBTYPE 

$ GLB.DBG-OLTP 

For the valid levels for each type of debug trace, see your OS 2200 Based LINC 


Note: This System Data item is valid only for UNIX hosts. 

Use this read-only System Data item to display the database bound to your UNIX LINC 

System. A UNIX LINC System can use either an Oracle or Griffin database. As a LINC 

developer, it may be useful to know which database your UNIX system is using when 

writing ispecs and reports, or when converting to another platform so that you can take 

advantage of any features or limitations unique to that database. 

GLB.DBTYPE displays the value O if your UNIX LINC System is bound to an Oracle 

database, or G if bound to a Griffin database. For further information about the features 

and differences of Oracle and Griffin databases, see your LINC Release 16.3/16R3 

Migration and Conversion Guide 


GLB.DC- System Data Items 

Note: This series of System Data items is not implemented in LDA Run Time. 

This series of read-only System Data items is used with the DATE.CONVERT; command. 

These items receive new values whenever a DATE.CONVERT; command (with the 

FORMAT; option) is used. They are cleared before the command is executed. 

If you use the DATE.CONVERT; command with the output FORMAT; option, only the 

System Data item corresponding to that FORMAT will receive a new value. 

These System Data items are listed in the following table with their LENGTH; and EDIT; 

attributes and example values for one particular date. 

Name Length Edit Example 

GLB.DC-TODAY 15 A MONDAY 

GLB.DC-WEEKNO 2 N 13 

GLB.DC-DAYNUM 6 N 13960 

GLB.DC-UK-ALPHA 25 A 23 MARCH 1998 

GLB.DC-US-ALPHA 25 A MARCH 23 1998 

continued 

2-18 v

continued 


Name Length Edit Example 

GLB.DC-IN-ALPHA 25 A 1998 MARCH 23 

GLB.DC-DD-MM-YY 8 A 23/03/98 

GLB.DC-DD-MM-CCYY 10 A 23/03/1998 

GLB.DC-DD-MMM-YY 9 A 23 MAR 98 

GLB.DC-DD-MMM-CCYY 11 A 23 MAR 1998 

GLB.DC-DDMMMYY 7 A 23MAR98 

GLB.DC-DDMMMCCYY 9 A 23MAR1998 

GLB.DC-DDMMYY 6 N 230398 

GLB.DC-DDMMCCYY 8 N 23031998 

GLB.DC-MM-DD-YY 8 A 03/23/98 

GLB.DC-MM-DD-CCYY 10 A 03/23/1998 

GLB.DC-MMDDYY 6 N 032398 

GLB.DC-MMDDCCYY 8 N 03231998 

GLB.DC-MMM-DD-YY 9 A MAR 23 98 

GLB.DC-MMM-DD-CCYY 11 A MAR 23 1998 

GLB.DC-MMMDDYY 7 A MAR2398 

GLB.DC-MMMDDCCYY 9 A MAR231998 

GLB.DC-YY-MM-DD 8 A 98/03/23 

GLB.DC-CCYY-MM-DD 10 A 1998/03/23 

GLB.DC-YY-MMM-DD 9 A 98 MAR 23 

GLB.DC-CCYY-MMM-DD 11 A 1998 MAR 23 

GLB.DC-YYDDD 5 N 98082 

GLB.DC-CCYYDDD 7 N 1998082 

GLB.DC-YYMMDD 6 N 980323 

GLB.DC-CCYYMMDD 8 N 19980323 

GLB.DC-YYMMMDD 7 A 98MAR23 

GLB.DC-CCYYMMMDD 9 A 1998MAR23 

GLB.BASE and GLB.CENTURY are also used in this process. 

v 2-19


GLB.DC-CC 

GLB.DEL 

For the calculation of GLB.DC-WEEKNO, weeks start on Sundays, and end on Saturdays. 

The value of the GLB.DC-WEEKNO for January 1 of any year is 1. 

This value of this read-only System Data item is set by complex DATE.CONVERT; 

commands to the century involved in the date conversion. See also GLB.CENTURY. 


GLB.DEL is a read-only System Data item. It can be used in place of the literal DEL, to 


GLB.DESTENV 

See the MAINT System Data item later in this section for details on GLB.DEL. 

GLB.DESTENV is used only with intersystem External Automatic Entries for an OS 2200 

based LINC System or UNIX LINC System. 

GLB.DESTENV is not implemented in LDA Run Time. If set for an Automatic Entry, 

GLB.STATUS will be set to NODB. 

For an Automatic Entry to an OS 2200 based host, its value specifies the destination LINC 

Environment. 

For an Automatic Entry to a UNIX host, its value specifies the ORACLE SID (or Griffin 

Universe) of the database for the destination LINC System. 

The value of GLB.DESTENV is set to the value of GLB.SELFENV at the start of the Ispec or 

Report on an OS 2200 based or UNIX host. For an MCP based LINC System, 

GLB.DESTENV will contain spaces. 

For more details, see the section on "Interfacing to Other Systems" in the LINC 

Administration and Operations Guide for the relevant host type. 


GLB.DESTHOST 

GLB.DESTHOST is used to specify the name of the host where the GLB.DESTINATION 

LINC System is located. Its value is set to that of GLB.SELFHOST at the start of each Ispec 

or Report. 

2-20 v


To send an External Auto Entry to a different host name, the host name value must be 

moved to GLB.DESTHOST as follows: 

$ For an MCP based LINC System, move the host name attribute established in the BNA 

definition. 

$ For an OS 2200 based LINC System, move the host name as defined in the COMUS 

General Configuration parameter. 

$ For a UNIX LINC System, move the node name (the name of the host in the 

communications network). 

GLB.DESTHOST is not implemented in LDA Run Time. If set for an Automatic Entry, 


For information on OLTP, see your LINC Generate Operations Guide. 


GLB.DESTINATION 

GLB.DESTINATION contains the name of the database (or for an OS 2200 environment, 

the TIP Transaction number of the LINC System) to which an external Automatic Entry is 

being sent. For an internal Automatic Entry, its value is GLB.SELF or GLB.SPACES. 

If data is to be sent to a non-LINC System (or to the LINC/USER interface program), move 

the value NON.LINC into GLB.DESTINATION. If data is to be sent to a NOF program, 

move the value NON.FORMAT to GLB.DESTINATION, and move the particular NOF 

program name to GLB.DESTNOFORM. 

If GLB.DESTINATION holds an invalid name, and an Automatic Entry is performed, 


GLB.DESTINATION is automatically reset at the start of an Ispec or in a Report, but you 

will have to reset it manually after performing an AUTO.ENTRY; command. 

GLB.DESTINATION is not implemented in LDA Run Time. If set for an Automatic Entry, 



GLB.DESTNOFORM 

Note: GLB.DESTNOFORM is not implemented in LDA Run Time. 

The GLB.DESTNOFORM System Data item enables two-way communication between a 

LINC System and a NOF program using External Automatic Entries. It is used to specify 

the particular NOF program to be targeted (when GLB.DESTINATION must contain 

NON.FORMAT). 

v 2-21


GLB.DEVICE 

The value that you specify in GLB.DESTNOFORM depends on the runtime host type: 

$ For an MCP based LINC System, specify the COMS program name for the NOF 

program. If this is not set, the value will default to windowNOF, where window is the 

COMS window name defined for the generated LINC System. 

$ For an OS 2200 based LINC System, specify the name of the NOF program. 

$ For a UNIX LINC System, specify the shell script that initiates the NOF program. 

$ For a UNIX LINC System, if GLB.DESTNOFORM is spaces, the Automatic Entry will 

fail, unless the transaction was initiated by a NOF program (when the Automatic Entry 

is sent back to that NOF program). 

For more details, see "Interfacing to Other Systems" in the LINC Administration and 

Operations Guide for the relevant host type. 


Note: LDA only supports the use of GLB.DEVICE for Shadow Reports in the form 

GLB.DEVICEx. 

This System data item contains the type of output device to which Report output is 

directed. 

Valid values for GLB.DEVICE are shown in the following table for each type of Report 

(ROC Standard, ROC Direct and MCP based non-ROC Reports), and each host type. 

An X indicates a valid value. The values in the Hosts column indicate valid host types (A 

MCP based, U for UNIX, 2 for OS 2200 based). 

Value Description Standard 

Report 

Direct 

Report 

Non-ROC 

Report 

DI Direct output X AU2 

LP Line printer (See 

Note 1) 

X X X AU2 

RP Remote Printer X X X A 

TP Terminal printer 

(See Note 2) 

X U X AU2 

VD Video output X U X AU2 

Spaces To be assigned 

within ROC 

X AU2 

Hosts 

continued 

2-22 v

continued 

Value Description Standard 

Report 

EX Output to Extract 

file 

Note: For a UNIX LINC System: 


Direct 

Report 

Non-ROC 

Report 

X U AU2 

Hosts 

1. LP means output is piped to a command defined by the LP alias. 

2. TP means output is piped to a command or alias. 

3. An entry of U in the ROC Direct column indicates the item is valid only 

for ROC Direct Reports on UNIX hosts. 

For ROC Reports, a value may be moved into GLB.DEVICE. If the device type changes, this 

causes an automatic release of the Report when the next output is produced (see the 

RELEASE; command). If an invalid value is moved into GLB.DEVICE, the default value for 

the Report is moved into GLB.DEVICE. 

Note: Such a release is prompted when a difference is detected by a comparison done 

before a PRINT.FRAME; command is executed, not by a MOVE; into 

GLB.DEVICE Data item. 

GLB.DEVICE can be used for Shadow Reports, in the form GLB.DEVICEx, where x is the 

one-character Shadow Report designator (A through Z). 

If GLB.DEVICE is changed in the logic of a Report, associated System Data items should 

also be changed (particularly GLB.STN). 

For MCP based LINC System Reports that do not use ROC, GLB.DEVICE is a read-only 

item. 


GLB.DLRECOVER 

Note: This System Data item is valid only in OS 2200 based Report logic. 

This is a read-write System Data item. The value of GLB.DLRECOVER indicates whether 

Report logic has detected a deadlock error when running your Report. 

v 2-23


GLB.EOP 

GLB.ERROR 

If GLB.DLRECOVER contains a numeric value other than zero, a deadlock error has been 

detected and the Report has been restarted by LINC Recovery. 

This System Data item will not be set unless the H execute option has been added to the 

execute statement for detecting deadlock errors. 

See GLB.RECOVER, later in this section. 

LENGTH=1, EDIT=N 

(This is not a System Data item. It is an option that can be included with the CURSOR; logic 

command in Ispec logic, to position the screen cursor at the end-of-page position when an 

Ispec screen is displayed. For more details, see the CURSOR; command, in this manual.) 

The setting of GLB.ERROR determines whether: 

$ The automatic store of input data for a USAGE; INPUT-OUTPUT Ispec is to be 

performed. 

$ An Internal Automatic Entry is to be performed. 

The setting of GLB.ERROR will affect the path through the LINC Cycle. For information on 

the LINC Cycle, see your LINC Generate Operations Guide. 


$ An AUTO; WRITE (or AUTO; WRITE&CLEAR) command causes an update to the 

database if GLB.ERROR is equal to GLB.SPACES at the time the command is 

executed, unless it fails a system check (for example, the same value has been used 

twice as a Component Ordinate value). 

The database update takes place immediately. Any later setting of GLB.ERROR has no 

effect. 

$ If GLB.ERROR is not equal to GLB.SPACES at the time the command is executed, the 

new record is not stored, and no Auto Entries are performed. 

$ This has no effect on any AUTO.WRITE (or AUTO; WRITE&CLEAR) commands 

executed earlier in the Ispec logic. 

Ispec Automatic Updates 

The automatic update performed at the end of Main logic for a USAGE; INPUT-OUTPUT 

Ispec (or at the end of Main logic for each cycle of a Copy.From Ispec cycle) is executed 

only if GLB.ERROR is equal to GLB.SPACES at that time. 

FLAG Commands 

A FLAG command causes a database update regardless of the setting of GLB.ERROR. 

2-24 v

MESSAGE; or RECALL; Commands 


The LINC System sets GLB.ERROR to ***** when MESSAGE; or RECALL; commands are 

executed in Ispec logic. 


GLB.EXAMKEY 

GLB.EXNAME 

GLB.EXTDB 

Note: This System Data item is valid only in MCP based Ispec logic. 

Use GLB.EXAMKEY if you want to enter up to 30 characters of diagnostic comment to be 

included in the Examiner trace record for an Ispec transaction. Move the alphanumeric 

value you require into GLB.EXAMKEY in your Ispec logic. 

For more information, see your MCP Based LINC Administration and Operations Guide. 


Note: This System Data item is valid for MCP based LINC Systems only. 

GLB.EXNAME is a read-only System Data item that holds the name of an item associated 

with an exception encountered with the use of the ACCESS.EXT; command. 


Note: This System Data item is valid for OS 2200 based LINC Systems only. 

Use this read-only System Data item in conjunction with Interdatabase access. It contains 

the name of the database that was being referenced during the last database access 

command for an Interdatabase Ispec. 


v 2-25


GLB.EXTDBSTATUS 

Note: This System Data item is valid for OS 2200 based LINC Systems only. 

Use this read-only System Data item in conjunction with Interdatabase access. It contains 

values that indicate the status of a database access. It should be used in conjunction with 

the GLB.STATUS System Data item. Valid values are shown in the following table. 

GLB.STATUS GLB.EXTDBSTATUS Meaning 

Spaces Spaces Access completed. 

Spaces Non-spaces Access failed. This may be the case where no 

GLB.STATUS is normally returned, such as the 

FLAG; command. 

***** Spaces Record not found. 

***** DB.DIFFERENT Ispecs do not match (data definitions, Profiles, 

and so on). 

***** DB.DISABLED Target database disabled in the HUB Common 

Bank. 

***** HUB.DOWN HUB background run is not running. 

***** INVAL.ISPEC The target Ispec specified by the SET.DB; 

command may be non-existent in the target 

system, or you have not set "Allow External 

Access" on your Ispec Environmental Options 

screen. 

***** INVAL.TARGET Access not allowed to target system. 

***** NO.DATABASE External database not found in the HUB 

Common Bank. 

***** NO.ENV Internal HUB error occurred when attempting to 

locate the environment details for the target 

system. 

***** NO.TABLE Database found, but the table name is unknown. 

***** NOT.LOCAL Table for this Ispec not defined in the local LINC 

System database, and an external database 

has not been designated by the use of a 

SET.DB; command. 

For more details, see your OS 2200 Based LINC Administration and Operations Guide 


2-26 v

GLB.EXTEXT 

GLB.FILEINFO 

GLB.FILLER 



This read-only System Data item holds the descriptive text of an exception encountered 

when using the ACCESS.EXT; command. See A Series DMS II Interpretive Interfaces for 

more details of these exception messages. 



GLB.FILEINFO is a System Data item you can use as a flag in Reports that use the Report 

Output Control System (ROC). It applies to Direct Reports only. 

The setting of GLB.FILEINFO explicitly controls print file attributes only (not Extract file 

attributes). This is to control the overwriting of the print file attributes by System Data 

items such as GLB.TITLE and GLB.SAVEDAYS. 

$ If GLB.FILEINFO is set to Y, the values are entered using file equation, and values of 

System Data items (which would otherwise be used to control the output files) are 

ignored. This is the default value for Reports initiated through the LINC Report 

Initiation Program (LINC/RIP). 

$ If GLB.FILEINFO is set to N, the values of System Data items are used, and any print 

file file-equate information is ignored. This is the default value for Reports initiated by 

the RUN; command or :RUN colon command. 


Use GLB.FILLER as a dummy data item to reserve space in Report Frames for Extract files 

and in Group Global System Data items and Group Setup Data items. 

You define GLB.FILLER as usual for a data item, although you can only apply the EDIT, 

LENGTH, DECIMAL, BINARY, and BCD (Binary Coded Decimal) Data Attributes. 

You must define a length for GLB.FILLER. If you do not define an edit type, GLB.FILLER is 

treated as alphanumeric. You may use the SAME.AS Data Command to specify the 

attributes for GLB.FILLER. 

v 2-27


Examples 

Records in a file consist of a code, surname, and firstname separated by spaces. You define 

a Group Global Setup Data item to obtain these values as follows. You use GLB.FILLER in 

place of the spaces. 

 

 

 

 

 

 

 

 

 

If you wish to create a Report Frame to define the format of an Extract file in the same 

format as the above file, you can also use GLB.FILLER. After creating the item for the code, 

you can paint the spaces between the code and surname by using the following command. 

 

Restrictions 

The following restrictions apply to GLB.FILLER: 

$ Do not use the SAME.AS; Data Command to see the attributes of GLB.FILLER. (You 

may use SAME.AS; to copy the attributes of a data item to GLB.FILLER.) 

$ You cannot define GLB.FILLER in your Dictionary. 

$ You cannot include GLB.FILLER in your logic (apart from in the definitions of Group 

Global Setup Data items or Group Setup Data items). 

$ You cannot include GLB.FILLER in the list of data items to be traced. 

$ When you create a Report Frame that defines the format of an Extract file you can 

include multiple GLB.FILLER data items. 

$ If you print a Report Frame that includes GLB.FILLER data items, these items will 

print as spaces regardless of their edit type (extra spaces are included where required 

for edit types such as EDIT; $). 

Edit Characteristics 

LENGTH = (user-defined) EDIT= (user-defined) 

GLB.FORMDEPTH 

GLB.FORMDEPTH contains the number of printable lines of Report output on a page. 

GLB.FORMDEPTH is valid in Reports only. It can be used for Shadow Reports, in the form 

GLB.FORMDEPTHx, where x is the one-character Shadow Report designator (A through 

Z). 

2-28 v

GLB.FORMID 


The value of GLB.FORMDEPTH is used to determine when to advance to top-of-form (and 

print footings and headings). For Reports that use the Report Output Control System 

(ROC), when GLB.FORMDEPTH is zero, no automatic advance to top-of-form occurs, and 

no headings are printed. 

Once output from a Report has been produced, the value of GLB.FORMDEPTH remains 

until the next RELEASE; command (or end-of-job), when the most recent change to its 

value is effected. 

The default values are set when the Report is initiated. If GLB.DEVICE is changed, 

GLB.FORMDEPTH may also need to be changed. Default values are listed in the following 

table, for each device and target host type. An entry of Page Config means the configured 

page length for that device (OS 2200 based LINC Systems only), while a blank entry 

indicates an invalid device/host type combination. 

Device Type Default Form 

Depth: MCP 

based 

Default Form 

Depth: OS 

2200 based 

Default Form 

Depth: UNIX 

LP 60 lines Page Config 60 lines 

RP 60 lines - - 

TP 66 lines 66 lines 66 lines 

VD (not IBM 3270) 48 lines 48 lines 48 lines 

VD (IBM 3270) 22 lines - - 

Spaces 60 lines Page Config 60 lines 

Note: For LDA Run Time, GLB.FORMDEPTH defaults to 66 lines. 


GLB.FORMID holds the name of the stationery to be used for printing of Report output by 

the LINC Report Output Control System (ROC). 

GLB.FORMID is valid in Reports only. It can be used for Shadow Reports, in the form 

GLB.FORMIDx, where x is the one-character Shadow Report designator (A through Z). 

The default value for GLB.FORMID is spaces. The value of GLB.FORMID is ignored when 

the Report is directed to a video device. Trailing spaces in the value are also ignored. 

Once output from a Report has been produced, the value of GLB.FORMID remains until 

the next RELEASE; command (or end-of-job), when the most recent change to its value is 

effected. 

v 2-29


GLB.FORMID is not implemented in LDA Run Time. 

For more details, see the ROC information in the LINC Administration and Operations 

Guide for the relevant host type. 

For a UNIX LINC System, the value of GLB.FORMID must have been created as an Alias in 

ROC, using the following command: 

 

In addition, the required forms must have been set up using lpforms and lpadmin. 

For MCP based LINC Systems, if GLB.FORMID is used in Reports that do not use ROC, 

COBOL74 syntax errors will occur. 


GLB.FULLLENGTH 

GLB.FULLSTN 

GLB.GUI 

GLB.FULLLENGTH is a read-only System Data item that contains the length (in bytes) of 

the data of a data item. The value of GLB.FULLLENGTH is defined when GET.LENGTH; 

and ATTACH; LINC logic command is executed. 

GLB.LENGTH is the length of the data of a data item (in characters). GLB.FULLLENGTH 

will equal GLB.LENGTH except for data items that contain Hankaku-Katakana characters 

in UNIX LINC Systems. See the description of Hankaku-Katakana characters in your LINC 

Generate Reference Manual: Painter and Editor and the ‘‘GET.LENGTH; (GL)’’ in this 

manual, for further details. 


GLB.FULLSTN is a read-only System Data item that applies to Ispecs for MCP based LINC 

Systems. For UNIX and OS 2200 based LINC Systems, GLB.FULLSTN contains the same 

station name as GLB.STN. 

For MCP based Ispecs, the value of GLB.FULLSTN is the full station name of the originator 

of the current transaction. See your MCP Based LINC Administration and Operations 

Guide for details of full station names and reference station names. 


GLB.GUI is a read-only System Data item that is available in Ispecs only. The value of 

GLB.GUI indicates the type of terminal from which a transaction originated: if Y the 

transaction is from a PowerClient terminal; if N it is from another terminal type. 

2-30 v

GLB.HIGH 


GLB.GUI can be used with GLB.STYLE to determine where a particular transaction 

originated. If GLB.STYLE is set to NOFORM and GLB.GUI is Y, the transaction has come 

from DW/PCE. Any other combination means that the transaction has come from the NOF 

program. 

In LDA, GLB.GUI can be initialized to a LINC.INI parameter. However, if input is received 

from a NOF program, GLB.GUI cannot be changed. 


GLB.HIGH is a read-only System Data item whose value is the maximum alphanumeric 

value that can be represented in the host type on which the LINC System is running. It is 

intended as for use as a starting point for DETERMINE; BACK or DETERMINE; LAST 

commands. 

GLB.HIGH is similar in usage to GLB.LOW, GLB.ZEROS, and GLB.SPACES. 

Note: The length of GLB.HIGH defaults to 1 in complex MOVE; commands. 

LENGTH = Indefinite EDIT = A 

GLB.HTIMEOUT 

This is a synonym for GLB.HUBTIMEOUT. 


GLB.HUBSTATUS 

GLB.HUBSTATUS is a read-only System Data item that contains information about the 

result of an external Automatic Entry. It is not implemented in LDA Run Time. 

The values returned by GLB.HUBSTATUS are messages indicating whether the Automatic 

Entry was successful, or a reason for its failure. For more details of these values, see 

‘‘AUTO; WRITE and AUTO; WRITE&CLEAR’’ in this manual. 


GLB.HUBTIMEOUT 

GLB.HUBTIMEOUT is used with External Automatic Entries, to define the length of time 

(in seconds) the sending LINC System should wait for a reply. 

v 2-31


A value of zero means that the LINC System will continue to wait until a reply is received. 

(For MCP based LINC Systems, a value of zero defaults to 120 seconds.) 

GLB.HUBTIMEOUT is set to 300 seconds after each Automatic Entry. 

Note: GLB.HUBTIMEOUT is not used with External Automatic Entries to NOF or the 

LINC USER interface program. It is not implemented in LDA Run Time. 

For more information about what happens when the time set in GLB.HUBTIMEOUT is 

exceeded, see ‘‘AUTO; WRITE and AUTO; WRITE&CLEAR’’ in this manual. 


GLB.INITFULLSTN 

GLB.INITSTN 

GLB.INITFULLSTN is a read-only System data item that applies to MCP based LINC 

System Reports. For UNIX and OS 2200 based LINC Systems, the value of 

GLB.INITFULLSTN is the same as GLB.INITSTN. 

For an MCP based LINC System, the value of GLB.INITFULLSTN is the full station name of 

the station from which the Report was initiated. 

See your MCP Based LINC Administration and Operations Guide for details of full 

station names and reference station names. 


GLB.INITSTN is a read-only System data item that can be accessed in Report logic to 

identify the terminal or username from which the Report was initiated. 

The value of GLB.INITSTN is BATCH if the Report was initiated: 

$ Through LINC/RIP for an MCP based LINC System 

$ In standalone mode for an MCP based LINC System 

$ From Startup logic for an MCP based LINC System 

$ Through a batch runstream for an OS 2200 based LINC System 

$ Through the shell for a UNIX LINC System 

$ Through LINCRPT with the command line option of -c for LDA 

$ As a Coroutine 

See the CALL; command in this manual for details of Coroutines. 

2-32 v


For an MCP based LINC System, the value of GLB.INITSTN is a reference station name. 

The full station name corresponding to the reference station held in GLB.INITSTN is 

contained in the System Data item GLB.INITFULLSTN. See your MCP Based LINC 

Administration and Operations Guide for further details. 

In LDA, GLB.INITSTN is initialized with the user or computer name before a session is 

opened. It can then be set to BATCH using the -c parameter with LINCRPT. 


GLB.INPUTDATA 

GLB.INQ 

Note: This System Data item is valid only in Ispec logic for MCP based target hosts. 

GLB.INPUTDATA is a read-only System Data item which contains the data received for 

processing the current transaction (that is, all screen data items excluding Usage Input 

data items). 

In a Copy.From Ispec, GLB.INPUTDATA should only be accessed on the first copy (when 

GLB.COPY is equal to 1). 


GLB.INQ is a read-only System Data item. It should be used in place of the literal INQ, to 



GLB.LANGUAGE 

The System Data item GLB.LANGUAGE can be used to change the working language of a 

station in a multiple language environment. Its value can be changed in Ispec and Report 

logic. 

In Ispecs, if you attempt to set GLB.LANGUAGE to a language name that is not defined for 

the LINC System, then GLB.LANGUAGE will contain ***** until the next transaction. You 

should test the result of GLB.LANGUAGE immediately after any move to it in your Ispec 

logic. 

For Ispecs, the language currently in use on the station is held in the System Data item 

GLB.STALANG. 

GLB.LANGUAGE is not implemented in LDA Run Time. 

v 2-33


GLB.LENGTH 

For Reports generated in a single language, if you attempt to change GLB.LANGUAGE, the 

current setting is retained. 

For Reports generated in multiple languages, if you attempt to set GLB.LANGUAGE to a 

language in which the Report was not last generated, the current setting of 

GLB.LANGUAGE is retained. 

For Reports, the current value of GLB.LANGUAGE is always held in the GLB.REPLANG 

System Data item. 

LENGTH = 10 ED = A 

The System Data item GLB.LENGTH contains the length of the data in a data item, 

including any initial and embedded spaces. GLB.LENGTH is valid in Ispecs, Reports, and 

Global Logics. It is set when any of the commands shown in the following table are 

executed. See also GLB.FULLLENGTH. 


GLB.LINECOUNT 

Command Value of GLB.LENGTH 

DETACH; Length of detached value 

ATTACH; Untruncated length of resulting value 

ATTACH&SPACE; Untruncated length of resulting value 

GET.LENGTH; Length of value 

GLB.LINECOUNT contains the number of lines of Report output printed on the current 

page. 

GLB.LINECOUNT is valid in Reports only. It can be used for Shadow Reports, in the form 

GLB.LINECOUNTx, where x is the one-character Shadow Report designator (A through Z). 

2-34 v

GLB.LINEUP 


When the value of GLB.LINECOUNT exceeds the value of GLB.FORMDEPTH (except 

when GLB.FORMDEPTH is zero), any footings are output, an advance to top-of-page 

occurs, and any headings are output. 

Note: When the BEGIN.PAGE; CLEAR command is executed, GLB.LINECOUNT is set 

to 9999 to force the new page. Since the logic of the print frame is executed 

before the advance to new page occurs, the value of GLB.LINECOUNT is 9999, 

not 0. 


Note: This System Data item is valid only for MCP based Report logic . 

GLB.LINEUP determines whether Report output requires stationery to be aligned before 

printing commences. (The System Data item GLB.LINEUPNAME specifies a file to be used 

in conjunction with this, for aligning your ROC Report output.) 

GLB.LINEUP can be used for Shadow Reports, in the form GLB.LINEUPx, where x is the 


Once output from a Report has been produced, the value of GLB.LINEUP remains until the 

next RELEASE; command (or end-of-job), when the most recent change to its value is then 

effective. 

For Reports using the Report Output Control System (ROC), GLB.LINEUP is only valid for 

non-video output. 

For non-ROC Reports: 

$ GLB.LINEUP is not valid for Shadow Reports. 

$ GLB.LINEUP is valid for output directed to TP devices when Terminal Printer Spooler 

(TPS) is used. For further details of TPS, see your MCP Based LINC Administration 


$ If Y is moved to GLB.LINEUP before output is produced, the Report is sent to backup, 

and the TPS AUTO setting is ignored. 

The Report is not printed until it is explicitly sent to the printer by using the TPS 

POSITION command, and it must be deleted manually from the printer directory using 

the TPS PURGE command. 

$ A value other than Y means that no alignment is required. 

$ If output is sent to a Terminal Printer with the TPS POSITION command, the printer is 

automatically set to AUTO-. This enables any special stationery to be changed before 

the file is printed, or removed before anything else is printed. 


v 2-35


GLB.LINEUPNAME 

GLB.LOW 

Note: This System Data item is valid only for MCP based Report logic . 

GLB.LINEUPNAME may be used for Shadow Reports, in the form GLB.LINEUPNAMEx, 

where x is the one-character Shadow Report designator (A through Z). 

GLB.LINEUPNAME contains the name of a file that is to be used to perform initial 

alignment of stationery. It is valid only for Reports directed to non-video output using the 

Report Output Control System (ROC). 

This item is used in association with the System Data item GLB.LINEUP. 

The value of GLB.LINEUPNAME may include usercode and pack definition as well as a file 

name. If GLB.LINEUPNAME contains spaces (the default value), the first page of the 

Report output is used for initial stationery alignment. 

Once output from a Report has been produced, the value of GLB.LINEUPNAME remains 

until the next RELEASE; command (or end-of-job), when it is overridden by the previous 

value. 


GLB.LOW is a read-only System Data item whose value is the minimum alphanumeric 

value that can be represented in the host type on which the LINC System is running. It is 

intended as a starting point for DETERMINE; FROM commands. 

GLB.MACHINE 

GLB.LOW is similar in usage to GLB.HIGH, GLB.ZEROS, and GLB.SPACES. 

Note: The length of GLB.LOW defaults to 1 in complex MOVE; commands. 


GLB.MACHINE is a read-only System Data item that describes the type of host machine on 

which the LINC System is running. 

In LDA, The value of GLB.MACHINE can be derived from the value of the TargetHost 

parameter in LINC.INI. If the targethost parameter is not present, GLB.MACHINE defaults 

to A. 

Possible values of GLB.MACHINE are shown in the following table. 

2-36 v

GLB.MATCH 


Value Running On... 

A MCP environment 

U UNIX 

1 OS 2200 environment 

P LDA Run Time 


GLB.MATCH is a System Data item that can be used in Report logic in conjunction with the 

MATCH; logic command, which compares key values in two Extract files. It holds a single 

alphabetic character that identifies the Extract file which is to be read next. A space value 

denotes that both files are to be read (because the current key values match). 

Note: GLB.MATCH always has a space value outside of the MATCH; loop. Testing 

GLB.MATCH outside the MATCH; loop is meaningless. 

For more details, see the MATCH; logic command in this manual. 


GLB.MAXCOPY 

GLB.MIXNO 

GLB.MAXCOPY is a read-only System Data item that contains the value of the 

MAX.COPIES option set for a Copy.From Ispec. It can only be accessed from Ispec logic. 


GLB.MIXNO is a read-only System Data item valid in Reports only. It contains the mix 

number (MCP based or OS 2200 based) or PID number (UNIX) of the Report at run time. 


GLB.NUMCOPIES 

GLB.NUMCOPIES contains the number of copies of a Report that are to be printed. It is 

valid only for Reports (standard Reports for UNIX) directed to non-video devices using the 

Report Output Control System (ROC). A value of zero (the default value) is interpreted as 

meaning one copy. 

v 2-37


GLB.NUMCOPIES can be used for Shadow Reports, in the form GLB.NUMCOPIESx, 

where x is the Shadow Report name. 

Note: GLB.NUMCOPIESx is not implemented in LDA Run Time. 

Changes can be made to GLB.NUMCOPIES until the first output from a Report has been 

produced. After that, any attempted changes to GLB.NUMCOPIES will have no effect. 

Once output from a Report has been produced, the value of GLB.NUMCOPIES remains 


value then applies. 

GLB.NUMCOPIES is not implemented in LDA Run Time. 


GLB.OLTPSERVICE 

This read-only System Data item contains the OLTP Service name invoked for the OLTP 

transaction received for processing. It is set prior to start of user logic in an OLTP Server. 


GLB.OLTPSUBTYPE 

This System Data item contains the most-recent OLTP Buffer Subtype name: 

$ Associated with an OLTP transaction received for processing (set automatically prior 

to start of user logic in the OLTP Server) 

$ Required for an AUTO; WRITE command (set automatically by an AUTO.ENTRY; 

command in the OLTP Client if the Ispec is an OLTP View Ispec) 

$ From the response to an AUTO; WRITE command (set automatically by an AUTO; 

WRITE command in the OLTP Client) 


GLB.OLTPTYPE 

This read-only System Data item contains the most-recent OLTP Buffer Type name: 

$ Associated with an OLTP transaction received for processing (set prior to the start of 

user logic in the OLTP Server) 

$ Required for an AUTO; WRITE command (set by an AUTO.ENTRY; command in the 

OLTP Client) 

2-38 v


$ Associated with the response to an AUTO; WRITE command (set by an AUTO; WRITE 

command in the OLTP Client) 


GLB.OLTPVALUE 

GLB.ORIGIN 

This read/write System Data item contains the OLTP application-defined return code: 

$ Given in the server, to be returned to the client 

$ Received by the client 

This value is attached to the response when a server replies to an OLTP-initiated message, 

and is made available in GLB.OLTPVALUE following the AUTO; WRITE command in the 

OLTP client transaction. 

GLB.OLTPVALUE is initialized to zero at the beginning of a transaction in both client and 

server, and is set by an AUTO; WRITE command for an OLTP client transaction. 

(GLB.OLTPVALUE is not set by a non-OLTP AUTO; WRITE command.) 

LENGTH = 9 EDIT = S 

GLB.ORIGIN is a read-only System Data item that contains the name of the LINC database 

from which an Automatic Entry originated. You can compare it to the System Data item 

GLB.SELF in your logic, to detect if an Ispec is receiving an Auto Entry from another LINC 

System or not. 

GLB.ORIGIN is not implemented in LDA Run Time. 

See also the GLB.ORIGINENV and GLB.ORIGINHOST System Data items. 


GLB.ORIGINENV 

This read-only System Data item is used only with external Automatic Entries from LINC 

Systems in OS 2200 or UNIX environments. 

The value of an Automatic Entry from an OS 2200 environment specifies the originating 

LINC Environment. 

The value of an Automatic Entry from a UNIX environment specifies the ORACLE SID (or 

Griffin Universe) of the database for the originating LINC System. 

The value of an Automatic Entry from an MCP based LINC System is spaces. 

v 2-39


GLB.ORIGINENV is not implemented in LDA Run Time. 

For more details, see the section on "Interfacing to Other Systems" in the LINC 

Administration and Operations Guide for the relevant host type. 


GLB.ORIGINHOST 

GLB.ORIGINHOST is a read-only data item that contains the name of the host from which 

an External Automatic Entry originated. Its value is set to the value of the System Data 

item GLB.SELFHOST at the start of an Ispec or Report. 

GLB.ORIGINHOST is not implemented in LDA Run Time. 


GLB.ORIGINISPEC 

Note: This System Data item is valid only for OS 2200 based Ispec logic. 

GLB.ORIGINISPEC is a read-only System Data item that is defined in the following 

situations: 

$ GLB.ORIGINISPEC contains the name of the Ispec that originated a PASSOFF when a 

specified Function Key was pressed. This value is used to determine the originating 

Ispec in the source system, when that system is being run with the FKSWITCH SGS 

statement and the INHERIT option. 

For more details, see your OS 2200 Based LINC Administration and Operations 

Guide. 

$ GLB.ORIGINISPEC contains the Ispec in the LINC System that used the SWITCH.TO; 

logic command with the INHERIT; option to access the current LINC System. It is 

provided for you to switch back to the Ispec in the previous LINC System. 

See also GLB.ORIGINXNID and GLB.ORIGINPTN. 

GLB.ORIGINISPEC is initialized to spaces when another Ispec is accessed (that is, when 

you recall another Ispec). 


2-40 v

GLB.ORIGINPTN 


Note: This System Data item is valid only in OS 2200 based Ispec logic. 

GLB.ORIGINPTN is a read-only System Data item that contains the partition for the LINC 

System that used the SWITCH.TO; logic command with the INHERIT; option to access the 

current LINC System. It is provided for you to switch back to the previous LINC System, 

but only if the SWITCH.TO; was performed from a PowerClient station. 

If the current LINC System has not been accessed by a SWITCH.TO; command, the value of 

GLB.ORIGINPTN is spaces. GLB.ORIGINPTN is initialized to spaces when another Ispec is 

accessed (that is, when you recall another Ispec). See also GLB.ORIGINXNID and 

GLB.ORIGINISPEC. 


GLB.ORIGINXNID 

Note: This System Data item is valid only in OS 2200 based Ispec logic. 

GLB.ORIGINXNID is a read-only System Data item that contains: 

$ Transaction id of the transaction that was running when an FKSWITCH command with 

INHERIT option was executed. For more details, see your OS 2200 Based LINC 

Installation and Configuration Guide. 

$ Transaction id of the LINC System that used the SWITCH.TO; logic command with the 

INHERIT; option to access the current LINC System. It is provided to enable you to 

switch back to the previous LINC System. 

See also GLB.ORIGINISPEC and GLB.ORIGINPTN. 

GLB.ORIGINXNID is initialized to spaces when another Ispec is accessed (that is, when 

you recall another Ispec). 


GLB.PAGECOUNT 

GLB.PAGECOUNT is incremented with each report page to contain the current Report 

output page number. It is set to zero when the Report is initiated and after a RELEASE; 

command. 

GLB.PAGECOUNT can be used for Shadow Reports, in the form GLB.PAGECOUNTx, 

where x is the one-character Shadow Report designator (A through Z). 

v 2-41


GLB.PARAM 

GLB.PAGECOUNT is incremented by one when the first line on a new page is output, after 

the Frame logic has been executed. While the Frame logic is being executed, 

GLB.PAGECOUNT still contains the page number of the preceding page of the Report. 

For details of the effect of a release on GLB.PAGECOUNT, see ‘‘RELEASE (REL)’’. 


GLB.PARAM holds the parameters for the CALL; command. 

Depending on the host type, when the CALL; command is executed, the contents of 

GLB.PARAM are passed to: 

$ An MCP based LINC System external library or program 

$ An MCP based LINC Report generated as a Coroutine 

$ An OS 2200 based LINC System external procedure 

$ A UNIX routine or process, or to the Bourne shell 

$ A LDA Run Time Report. 

Data is returned through this item to the calling Ispec or Report. See ‘‘CALL’’ for further 

details. 

The maximum length of GLB.PARAM is defined in the GLB.PARAM size field on the 

Primary Specification Options screen. 

For LDA Run Time, the length is assumed to be greater than 24. 

LENGTH = user defined EDIT = A 

GLB.PARAMFLAG 

GLB.PARAMFLAG is set to Y to indicate that parameter data is attached to the WAKE.UP; 

command that is calling your Report. 

It is reset at the next SLEEP; command, or CRITICAL.POINT; command with a SLEEP; 

option. GLB.PARAMFLAG is not set when a parameter is passed to the Report by a RUN; 

command. 


2-42 v

GLB.PITCH 


Note: GLB.PITCH is not valid for a UNIX environment, and is not implemented in 

LDA Run Time. 

GLB.PITCH contains the default print pitch when output is first produced by the Report, as 

specified on the Report Options screen. The default pitch may be modified in a line 

containing data or display items by Report logic. Each line printed by the Report will 

default to this pitch unless an explicit pitch is specified in a data item or display in that line. 

GLB.PITCH can be used for ROC Shadow Reports, in the form GLB.PITCHx, where x is the 


Note: GLB.PITCHx is not implemented in LDA Run Time. 

GLB.PITCH applies to ROC Standard Reports outputting to Terminal Printer devices (and 

Remote Printer devices in an MCP environment). Also, for MCP based LINC Systems only, 

GLB.PITCH is available in read-only mode for non-ROC Reports output to Terminal 

Printers. 

Note: The Report Options screen Default Device field must be set to TP for non-ROC 

reports, otherwise the spacing on the printed output will be incorrect. 


GLB.PREVISPEC 

GLB.PRINTAT 

Note: This System Data item is valid for OS 2200 based Ispec logic and is also 

supported in LDA when the target host is OS 2200. 

GLB.PREVISPEC is a read-only System Data item that contains the name of the Ispec that 

was currently on display when a Function key was pressed. 

For more details, see your OS 2200 Based LINC Installation and Configuration Guide. 

See also, GLB.ACTIONKEY. 



GLB.PRINTAT is used by Direct Reports that use the LINC Report Output Control System 

(ROC). It indicates when output is to be queued for printing. 

v 2-43


GLB.PRINTAT can be used for Shadow Reports, in the form GLB.PRINTATx, where x is 

the one-character Shadow Report designator (A through Z). 

GLB.PRINTAT can have one of two values, as shown in the following table. 

Value Operation 

END Accumulate all output and print when the Report terminates. 

RELEASE Print each print file as it is released. 


GLB.PRINTBANNER 


The value of GLB.PRINTBANNER determines whether banner pages are printed with 

Report output. If its value is Y, banners are printed. It is used for Reports produced using 

the Report Output Control System (ROC). 

GLB.PRINTBANNER can be used for Shadow Reports, in the form GLB.PRINTATx, where 

x is the one-character Shadow Report designator (A through Z). 

GLB.PRINTBANNER applies to ROC Reports directed to Line Printer (LP), Remote Printer 

(RP), and Terminal Printer (TP) devices. Its default value is Y for LP and RP devices, and N 

for TP devices and VD Reports. 

Once output from a Report has been produced, the value of GLB.PRINTBANNER remains 

until the next RELEASE; command or end-of-job, when the most recent change to its value 

then applies. 


GLB.PRINTHOST 


GLB.PRINTHOST contains the name of the host computer to which the required 

destination output device is connected. 

GLB.PRINTHOST can be used for Shadow Reports, in the form GLB.PRINTHOSTx, where 

x is the Shadow Report name. 

2-44 v


The value of GLB.PRINTHOST is stored when a Frame is printed. This value is later 

compared to current values when a PRINT.FRAME; command is next used, to determine if 

a release is required. 

The release is not done when the GLB.PRINTHOST value changes. Such a release is 

prompted when a difference is detected by a comparison done before a PRINT.FRAME; 

command is executed, not by a MOVE; into GLB.PRINTHOST. 

When output from a Report has been produced, the value of GLB.PRINTHOST remains 


value is then effected. 

GLB.PRINTHOST applies to Reports that use the Report Output Control System, with 

output directed to Line Printer, Remote Printer, and Terminal Printer devices. Its default 

value is the value of GLB.SELFHOST. 

GLB.PRIORITY 


Note: This System Data item is valid only in Ispec logic. 

GLB.PRIORITY enables you to set the run priority of a Report initiated from Ispec logic by 

the RUN; logic command, at run time. This allows Report output to be scheduled more 

effectively, resulting in improved use of resources. 

GLB.PRIORITY sets the priority at which the Report runs. It can have a value in the range 

01 through 99. For MCP based LINC Systems and OS 2200 based LINC Systems, the value 

equates directly to the level of priority; that is 99 is the highest priority. For a UNIX LINC 

System, the value relates inversely to the level of priority; that is 01 is the highest priority. 

An entry of zero will cause the Report to be run at the default priority. GLB.PRIORITY is 

invalid in the Report logic itself. 



A nonzero value of GLB.PRIORITY overrides the default Report priority of the :RPR LINC 

System command. The default value of GLB.PRIORITY is zero. 

If a Report is run through LINC/RIP, then it will be run at the priority of the RIP program. If 

the priority is higher than the maximum priority set by the :RPR system command, then it 

will be changed to the maximum priority. 

If the priority is higher than the maximum priority set by :RPR, then it will be changed to 

the maximum priority. (This applies to RIP and GLB.PRIORITY.) 

v 2-45


GLB.PRIV 


If it is lower than the user’s account priority, then it will automatically downgrade the 

Report priority in GLB.PRIORITY. If the Report is run in standalone mode, then the priority 

is under the control of the initiating user. The default value of GLB.PRIORITY is zero. 

UNIX 

The value corresponds to nice values in the range 1 (high) through 40 (low). The default 

value is 20. 

LDA Run Time 

GLB.PRIORITY is not implemented in LDA Run Time. 

LENGTH = 2 EDIT = N (All host types) 

In Ispec logic, GLB.PRIV contains the privilege level of the Ispec transaction originator. In 

Report logic, it contains the privilege level of the Report output printer device. Its value 

can range from 0 to 15 (1 to 15 for an MCP based LINC System). 



The privilege level of terminals is contained in COMS. The privilege level of printers is 

contained in the LINC/NET file, and can be specified by using the MCP based LINC 

Network Configuration System (NETCON). 

In a Report directed to a Terminal Printer, if a value in the range 1 through 15 is moved to 

GLB.PRIV before the first PRINT.FRAME; command, then the file can only be printed on a 

printer of an equal or higher privilege. 

If the printer privilege is zero, a user privilege value of 15 will be assumed, and any Report 

output will be able to be sent to that printer. 

For Reports that use the LINC Report Output Control System (ROC), GLB.PRIV can be 

used when output is directed to all MCP based output devices, except EX (extract files). 

For Reports that do not use ROC, GLB.PRIV can only be used when output is directed to 

Terminal Printers. If GLB.PRIV has a nonzero value, the file is forced to a printer backup 

file, regardless of other settings for Terminal Printer Spooler (TPS). For further details, see 

the information on Terminal Printer Spooler in your MCP Based LINC Administration 


The external interface programs GLI, Offline, and NOF have a privilege level of 15. For 

more details of these programs, see your MCP Based LINC Administration and 


2-46 v



Reports have unrestricted access to the LINC database. The value of GLB.PRIV determines 

the access privilege of output stored in the LINC Report Output Control System (ROC) 

Database. 

In a Report directed to a Terminal Printer, if a value in the range 0 to 15 is moved to 

GLB.PRIV before the first PRINT.FRAME; command, then the file can only be printed on a 

printer of an equal or higher privilege. 

The external interface programs GLI, Offline, and NOF have a privilege level of 15. For 

more details of these programs, see your OS 2200 Based LINC Administration and 


UNIX 

The privilege level of usernames is contained in the LINCIINET file. 

Reports have unrestricted access to the LINC database. The value of GLB.PRIV determines 

the access privilege of output stored in the LINC Report Output Control System (ROC) 

Database. You may only view Report output if you have a privilege level of an equal or 

higher value. 

LDA Run Time 

GLB.PRIV is not implemented in LDA Run Time. 

The external interface programs GLI, Offline, and NOF use the privilege of the initiating 

username. For more details of these programs, see your MCP Based LINC Administration 


GLB.PRODUCT 

LENGTH = 2 EDIT = N (All host types) 

GLB.PRODUCT is a read-only System Data item containing the LINC Generate 

(Deployment) software product under which your LINC System is running. Valid values 

are: 

 

 

 

GLB.PRODUCT enables you to take alternate logic paths within your code, based on the 

product under which the system is running. For example, you may wish to bypass 

execution of some code when your generated LINC System is running under LITE. 

To include some code to be executed when testing in LDA Run Time, but not in your 

generated LINC System, you could include the condition: 

 

v 2-47



GLB.PRTPARAM 

GLB.PUR 

Note: This System Data item is valid only for OS 2200 based Report logic. 

This System Data item enables you to pass data from a Shadow Report to a user-written 

USERPRT print handler program. It is valid only in Direct Reports that produce output for 

a Shadow Report. 

When GLB.PARAM applies to a Shadow Report, use the form GLB.PRTPARAMx, where x 

is the one-character Shadow Report designator (A through Z). 

For more details, see your OS 2200 Based LINC Administration and Operations Guide. 

LENGTH = user-defined (maximum 9999) EDIT = A 

This is a read-only System Data item. It can be used in place of the literal PUR to allow for 

translation of MAINT values in multiple-language systems. 

GLB.RECORDx 


This System Data item is used in conjunction with a DETERMINE; ACTUAL command 

when reading an Extract file in Report logic. 

When a value is moved into GLB.RECORDx, the Extract file is read from the record after 

that specified number. If no number (or GLB.ZEROS) is moved into GLB.RECORDx, the 

read starts from the first record. 

If a value equal to, or greater than, the last record number in the file is moved to 

GLB.RECORDx, GLB.STATUS will be set to (*****) after the DETERMINE; ACTUAL 

command is executed. 

This System Data item can only be used in the form GLB.RECORDx, where x is the 

one-character Extract file designator (A through Z). 

GLB.RECORDx is not automatically updated as records are accessed. 

See also ‘‘DETERMINE; ACTUAL’’ in this manual. 


2-48 v

GLB.RECOVER 


In Report logic, the value of GLB.RECOVER indicates whether that Report has been 

restarted by LINC Recovery. It can also be used to inhibit LINC Recovery on MCP based 

runtime hosts. 

If GLB.RECOVER has a value of 1, the Report has been restarted. If the Report includes 

CRITICAL.POINT; commands, it will have been recovered to the last executed Critical 

Point, and the Critical Point data will have been retrieved. The Report logic should perform 

any reinitialization and reset GLB.RECOVER to zero (its default value). 

For an MCP based LINC System, to disable the LINC recovery and permit your Report logic 

to handle the recovery, set GLB.RECOVER to 9. 


GLB.REPGENDATE 

GLB.REPGENDATE is a read-only System Data item that can be accessed in Report logic 

to obtain the generation date of the Report, in the date format CCYYMMDD. Together with 

GLB.REPGENTIME, it gives a generation timestamp for the current (running) version of a 

LINC Report. 

GLB.REPGENDATE is not implemented in LDA Run Time. 


GLB.REPGENTIME 

GLB.REPGENTIME is a read-only System Data item that can be accessed in Report logic to 

obtain the generation time of the Report. 

The four-digit time value has the format HHMM, where HH represents hours (in 24-hour 

format), and MM represents minutes. For example, 2158 is 9:58 pm, and 0001 is one 

minute past midnight. Together with GLB.REPGENDATE, it gives a generation timestamp 

for the current (running) version of a LINC Report. 

GLB.REPLANG 

GLB.REPGENTIME is not implemented in LDA Run Time. 


In Report logic, the value of this read-only System Data item gives the language name for 

which the Report was generated. 

GLB.REPLANG is not implemented in LDA Run Time. 

v 2-49



GLB.REPNAME 

GLB.REPORT 

In Report logic, the value of this read-only System Data item gives the name of the Report. 


GLB.REPORT is a System Data item that is included in all Event records, for use as a status 

flag in Reports. Its value can be changed by using the FLAG; command. 

This item is provided for general-purpose developer use. It is not used or affected by any 

automatic LINC processes. 


GLB.REPUNIQUE 


GLB.REPUNIQUE is a read-only System Data item automatically set by the LINC System to 

provide a unique number for each Report at run time. Use of this System Data item is not 

recommended and the preferred method is to use the RUN; command with the PA; 

parameter. 

If the Report is initiated from the Report Initiation Program (RIP) you must supply the 

unique number that has to be passed to the Report in GLB.REPUNIQUE. By matching this 

number against the first 15 characters of the GLBPAK filename, the LINC System identifies 

the GLBPAK filename to RIP. The first 15 characters of GLBPAK filename must be numeric. 

Enter the Report name and the unique number for GLB.REPUNIQUE as follows: 

 

 

Here report is the name of the Report, and number is the unique 15-digit number. GLBPAK 

must have a filename that contains only numbers for the first 15 characters. 


2-50 v

GLB.REPVERSION 


GLB.REPVERSION is a read-only System Data item that can be accessed in Report logic to 

obtain the current version number of a Report. This number is incremented every time you 

generate the Report. To cause this number to be reset to one when you generate your LINC 

system with a new version id, enter Y in the Reset Report counts on system generate 

field on the Change Control Options screen. You can also change it directly by using the 

Supervisor RESET VER command. 

GLB.REQUEST 

GLB.REPVERSION is not implemented in LDA Run Time. 


GLB.REQUEST is a read-only System Data item for use in Pre-Screen Ispec logic and 

applies to Ispecs and Global Logics. It contains the value Y if the Ispec format was 

requested from page 2 of the terminal, or a space if the Ispec format was requested from 

logic. 

GLB.ROCFLAG 


GLB.ROCFLAG is a read-only System Data item used in Ispec and Report logic. It shows 

whether or not LINC Report Output Control System (ROC) is set. It contains the value R if 

ROC is set, or a space if ROC is not set. 


GLB.SAVEDAYS 

GLB.SAVEDAYS holds the number of days that Report output is to be retained by the LINC 

Report Output Control System (ROC). The output will be deleted when this time has 

elapsed, and when there are no outstanding requests for it to be printed. A value of 99 

means the output is retained indefinitely. 

GLB.SAVEDAYS has no effect for Direct Reports (and MCP based non-ROC Reports), and 

is invalid in Ispec logic. It is not implemented in LDA Run Time. 

v 2-51


GLB.SAVEDAYS can be used in the form GLB.SAVEDAYSx, where x is the one-character 

Shadow Report designator (A through Z). 

Note: GLB.SAVEDAYSx is not implemented in LDA Run Time. 

Once output from a Report has been produced, the value of GLB.SAVEDAYS remains until 

the next RELEASE; command (or end-of-job), when the most recent change to its value 

then applies. 

GLB.SAVEDAYS has a default of zero. If sufficient information is provided to print the data 

(that is, if the System Data items GLB.DEVICE and GLB.STN both have non-space values, 

or GLB.DEVICE has the value LP), the Report output will be removed after printing. If 

there is insufficient information to automatically print the data, Report output will be 

retained until the end of the current day. Reports are deleted after midnight. 

LENGTH = 2 ED = N 

GLB.SECONDARY 

GLB.SELF 


GLB.SECONDARY is a read-only System Data item that is used with the Remote Database 

facility (RDB) to detect when the Report is running against the Secondary database. It can 

have the following values: 

$ N indicates the Primary database: read or update access is permitted. 

$ Y indicates the Secondary database: read-only access is permitted. 


For an OS 2200 based LINC System, GLB.SELF is a read-only System Data item containing 

the transaction id of the current LINC System. 

For an MCP based or UNIX LINC System, GLB.SELF is a read-only System Data item 

containing the database name of the system currently executing. 

After using the System Data item GLB.DESTINATION to target an intersystem External 

Automatic Entry, you can use GLB.SELF to restore GLB.DESTINATION. 


2-52 v

GLB.SELFDB 

GLB.SELFENV 


Note: This differs from the GLB.SELF System Data item only for an OS 2200 based 


GLB.SELFDB is a read-only System Data item containing the database name of the current 


After using the SET.DB; command to set the target database for interdatabase access 

(OS 2200 based LINC Systems only), GLB.SELFDB can be used to reset back to the current 

database, again using the SET.DB; command. 


GLB.SELFENV is a read-only System Data item for use with intersystem External 

Automatic Entries sent from a LINC System in an OS 2200 based or UNIX environment. 

$ For an OS 2200 based LINC System, it contains the name of the LINC environment. 

$ For a UNIX LINC System, it contains the ORACLE SID (or Griffin Universe) of the 

LINC database for the current LINC System. 

$ For MCP based LINC Systems, it is set to spaces. 

$ Not implemented in LDA Run Time. 

For more details, see your OS 2200 Based LINC Administration and Operations Guide. 


GLB.SELFHOST 

GLB.SELFHOST is a read-only System Data item that contains the name of the host on 

which the current LINC System is running (that is, the name used to identify that host 

computer in a communications network). 

GLB.SELFHOST is not implemented in LDA Run Time. 


v 2-53


GLB.SELFXNID 

GLB.SHADOW 

GLB.SOURCE 

GLB.SPACES 

Note: This System Data item is valid only for OS 2200 based Ispec logic. 

GLB.SELFXNID is a read-only System Data item that contains the tranid of the LINC 

System. 


GLB.SHADOW is a read-only System Data item that can be accessed in Report Frame logic 

to indicate the Shadow Report currently being output. It contains the one-character 

Shadow Report designator (A through Z). If no Shadow Report is being output, 

GLB.SHADOW contains a space. 


GLB.SOURCE is a read-only System Data item that can be accessed in Ispec logic to 

indicate the message type. This is a value derived from the source of input of a record to 

the database. 

Valid values are shown in the following table. 

Value Source of Record 

G Generalized LINC Interface (GLI) 

O Offline Input 

N(orspace) Page 2 format request 

T Standard terminal transaction (Also, for MCP based 

External Autos or OLTP Autos) 

For LDA Run Time, GLB.SOURCE defaults to T, and its value is ignored. 


GLB.SPACES is a System Data item that can be used in place of a literal value of spaces 

(for comparing, ordering and sorting purposes). 

2-54 v


GLB.SPACES can be used to set any alphanumeric data item, regardless of length, to 

spaces. It can also be used in conditions. 

GLB.STALANG 

GLB.STATION 

GLB.STATUS 

Note: The length defaults to 1 in complex MOVE; commands. 


Caution 

For an OS 2200 based LINC System, moving GLB.SPACES to a Group Setup Data 

item or a Group Global Setup Data item that contains numeric data items may give 

erroneous results if the numeric data items are subsequently used in computation. 

GLB.STALANG is a read-only System Data item that can be accessed in Ispec logic to 

indicate the language currently in use by the initiator of the current transaction. The 

language can be changed by altering the value of the System Data item GLB.LANGUAGE in 

Ispec logic, or by using the :SLA LINC System (colon) command at run time. 

GLB.STALANG is not implemented in LDA Run Time. 


This is a synonym for GLB.STN. See GLB.STN for more details. 

GLB.STATUS is used to indicate the result status of some logic commands. It can contain 

one of a range of values, depending upon the circumstances in which it is set. The most 

common values are spaces (when there is no error), and five asterisks (*****) when there 

is an error. 

When GLB.STATUS is set 

GLB.STATUS can be set (to a non-space value) in the following situations: 

$ LOOK.UP; and DETERMINE; command variants find no records. 

$ A DATE.CONVERT; command fails. 

$ Arithmetic overflow occurs. 

$ An invalid subscript is used when accessing an array. 

v 2-55


$ An invalid complex MOVE; command is attempted. 

$ An Automatic Entry within Ispec logic fails. 

$ An External Automatic Entry (between LINC Systems) fails. 

$ An External Automatic Entry is rejected by the destination LINC System. 

$ An ACCESS.EXTERNAL; command fails (MCP based LINC Systems only). 

$ A START; command fails, and the Report is unable to be started. 

$ A RUN; command fails, and the Report is unable to be started. 

$ A MATCH; command finds both Extract files empty. 

$ A WAKE.UP; command with the PARAMETER option cannot pass the parameter to 

the Report. 

Note: Some LINC commands do not automatically set GLB.STATUS but you are able 

to obtain a result in GLB.STATUS by using the GLB.STATUS; command in 

conjunction with those commands. The arithmetic commands, ADD; 

SUBTRACT; MULTIPLY; and DIVIDE; are of this type. See ‘‘GLB.STATUS (GS)’’ 

in this manual. 

When using arrays, do not use GLB.STATUS for anything other than index 

checks. Instead, use the GLB.STATUS extension to the DC; command. 

See the relevant commands for more details of the values to which GLB.STATUS may be 

set. 

When GLB.STATUS is Initialized 

GLB.STATUS is set to the value of the System Data item GLB.SPACES before the following 

commands are executed: 

$ ACCESS.EXTERNAL (MCP based LINC Systems only) 

$ AUTO; WRITE, and AUTO; WRITE&CLEAR commands 

$ DETERMINE; commands 

$ LOOK.UP; commands (except for the LOOK.UP; command variant in Ispec logic) 

$ RUN; command 

$ START; command 

$ MATCH; command 

$ WAKE.UP; command 

Using the GLB.STATUS; Command 

Instead of using the GLB.STATUS System Data item, you can explicitly direct the 

command status result to a specific data item, by appending the GLB.STATUS; command 

to a logic command, where valid. For more details, see ‘‘GLB.STATUS (GS)’’ in this manual. 

2-56 v

GLB.STN 

In Ispecs 

Overwriting GLB.STATUS Values 


The value of GLB.STATUS can be changed in a DO.WHEN; command. You should exercise 

caution when coding complex decision logic that involves more than one DO.WHEN; 

command. 

Consider the following logic: 

 

 

You may be checking the result of a previous action in the first DO.WHEN; command, but 

the test on an array item in the second DO.WHEN; command also affects GLB.STATUS, 

and will overwrite the GLB.STATUS value that you intended to check. 


GLB.STN (or GLB.STATION, which is a synonym) applies to all hosts, Ispecs and Reports. 


For details of reference station names, see your MCP Based LINC Administration and 


In Ispecs, the originator of the current transaction is identified by GLB.STN as follows. 

Transaction From ... GLB.STN Value 

Standard user terminal $ MCP based LINC System reference station 

name 

$ OS 2200 based LINC System user station 

PID 

$ UNIX user id 

External Automatic Entry Identifier for terminal originating external 

Automatic Entry: 

$ MCP based LINC System reference station 

name 

$ OS 2200 based LINC System user station 

PID 

$ UNIX user id 

continued 

v 2-57


In Reports 

continued 

Transaction From ... GLB.STN Value 

OLTP GLB.OLTP 

An offline source OFF 

Generalized LINC Interface program GLI 

LDA Run Time User id 

In Reports, GLB.STN contains the Report destination. 

GLB.STN can be used for ROC Shadow Reports, in the form GLB.STNx (not applicable for 

non ROC Reports), where x is the one-character Shadow Report designator (A through Z). 

Changing the value of GLB.STN causes a release of the current print file. The value of 

GLB.STN is stored when a Frame is printed. This value is later compared to the current 

value at the next PRINT.FRAME; command, to determine if a release is required. The 

release is prompted by that comparison, not by a MOVE; into the GLB.STN data item. 

Default GLB.STN values for each device type (GLB.DEVICE value) and runtime host type 

are shown in the following table. 

GLB.DEVICE Default for GLB.STN Runtime Host Types 

DI GLB.SPACES All 

EX GLB.SPACES All (ROC only) 

LP GLB.SPACES All 

RP GLB.ASCPRT MCP based LINC Systems only 

TP GLB.ASCPRT All 

VD GLB.INITSTN All 

Spaces GLB.SPACES All (ROC only) 

Further specific details for each host type are given in the following subsections. 


GLB.STN is optional for ROC line printer (LP) Reports. If it is used, it enables a Report to 

specify a particular line printer; for example, LP10 or LP11. 

2-58 v


If the Report is run unattached, and GLB.ASCPRT or GLB.STN is not defined in the 

LINC/NET file, the Report will go to end-of-job. 

For ROC Reports where GLB.DEVICE contains EX, an asterisk (*) in GLB.STN indicates 

that the Extract file name is specified in GLB.TITLE. 

For specific information on MCP based stations for PowerClient, see your MCP Based 

LINC Administration and Operations Guide. 

OS 2200 

For Reports directed to Line Printers, the name of the symbiont queue can be specified by 

moving it to GLB.STN. If GLB.STN contains spaces, the output is directed to the default 

symbiont queue. 

If GLB.DEVICE contains TP, then the destination of the Report must be a station (PID). 

UNIX 

For Reports directed to LP or TP, GLB.STN contains the piped alias, and for Reports 

directed to EX it contains the file name. GLB.STN is not used for device types VD or DI. 

LDA Run Time 

GLB.STNHOST 

GLB.STYLE 

GLB.STN must be set by the Report to indicate the output device. 


GLB.STNHOST is used in BNA V1 networks. When a terminal is connected to a LINC 

System running on another host processor, the terminal name is prefixed by the name of 

the host. GLB.STNHOST holds the name of this host, and the terminal name is held in 

GLB.STN for Ispec logic, and in GLB.INITSTN for Report logic. 


GLB.STYLE is a read-only System Data item that contains the type of terminal or program 

from which a transaction originated. Valid values for each runtime host type are shown in 

the following table. 

v 2-59


GLB.SUBSYS 

GLB.STYLE (Terminal Type) Host Types 

ET1100 MCP based 

MT983 MCP based 

LT300 OS 2200 based 

UTS20L, UTS20R OS 2200 based 

UTS20, UTS30, UTS40, UTS60, UTS60I OS 2200 based 

DS7 OS 2200 based 

SVT1120 OS 2200 based 

IBM3270, IBM3178, IBM3278, IBM3279 OS 2200 based 

SNA3270 OS 2200 based and UNIX 

IBM3270 All 

NOFORM (NOF interface program or WDP) All 

OLTP All 

GLB.STYLE can be used with GLB.GUI to determine where a particular transaction 

originated. If GLB.STYLE is set to NOFORM and GLB.GUI is Y, the transaction has come 

from DW/PCE. Any other combination means that the transaction has come from the NOF 

program. 

In LDA, GLB.STYLE can be initialized to a LINC.INI parameter. However, if input is 

received from a NOF program, GLB.STYLE cannot be changed. 


Note: This System Data item is valid only for MCP based Ispec logic. 

This read-only System Data item contains the number of the particular LINC Update 

program you are in. It is accessible from Ispec logic only, and corresponds to the LINC 

Subsystem for the current Ispec. 

For OS 2200 based and UNIX runtime hosts, the value defaults to zero. 


2-60 v

GLB.SYSGENDATE 


GLB.SYSGENDATE is a read-only System Data item that relates to version control. It gives 

the LINC System generation date, in the format CCYYMMDD. Together with 

GLB.SYSGENTIME, it provides the date and time the current version of your LINC System 

was generated. It is not updated for a syntax-only generate. 

Note: For MCP based LINC Systems only, if your latest generate has only compiled 

Subsystems in which there have been some Ispec changes, current version 

information will only be applied to those Subsystems that have been compiled. 

Before generating, mark all Subsystems for generate in order to propagate the 

latest version information across your whole system. 

GLB.SYSGENDATE is not implemented in LDA Run Time. 


GLB.SYSGENTIME 

GLB.SYSGENTIME is a read-only System Data item that relates to version control. It gives 

the LINC System generation time, in the 24-hour format HHMM. For example, 21:30 is 

9:30 pm, and 00:01 is one minute past midnight. Together with GLB.SYSGENDATE, it 

provides the date and time of the current version of your system was generated. It is not 

updated for a syntax-only generate. 

Note: For an MCP based LINC System only, if your latest generate has only compiled 





GLB.SYSGENTIME is not implemented in LDA Run Time. 


v 2-61


GLB.SYSVERSION 

GLB.TASK 

GLB.SYSVERSION is a read-only System Data item that gives the version number of the 

current LINC System. This number is incremented by one every time you generate your 

Specification (except for syntax-only generates). You may cause this number to be reset 

when you generate your Specification with a new version id, by entering Y in the Reset all 

version counts on id change field on the Change Control Options screen, or you can 

change it directly by using the Supervisor RESET VER command. 






GLB.SYSVERSION is not implemented in LDA Run Time. 


GLB.TASK can be used to provide a result for the running of a Report. 


GLB.TASK is accessible from a WFL job, and its value can be used to control subsequent 

WFL execution. 

If the Report is run through the batch Report Initiation Program (RIP), and a value is 

moved into GLB.TASK, the value returned to RIP at end-of-task is TASKVALUE. 

A MOVE; of a value to GLB.TASK causes the TASKVALUE attribute to be set immediately. 

This occurs for a MOVE; logic command only; any other command that has GLB.TASK as a 

receiving field results in GLB.TASK being set only at the end of the Report. 

GLB.TASK is zero unless it is explicitly given a value. 

Caution 

GLB.TASK should not be set to 1, as this value is used specifically to indicate a 

Report runtime error, for example, divide by zero or DMSII errors. 


2-62 v

For 2200 Series 


The value of GLB.TASK is stored in T3 of the Run Condition Word and can be tested later 

in the same runstream by a succeeding task. 

Note: LINC Reports generated as LINC Subroutines cannot use this System Data 

item. 

If you use a MOVE; command to move a value to GLB.TASK, T3 of the Run Condition Word 

is set immediately. If you use any other command that has GLB.TASK as a receiving field, 

GLB.TASK is set only at the end of the Report. 

If the LINC Report terminates normally, the error status of the current task is cleared and 

the value in GLB.TASK is stored in T3 of the Run Condition Word. If the LINC Report 

terminates abnormally, the error status of the current task remains as it was set in T3 of 

the Run Condition Word. 

GLB.TASK is zero unless it is explicitly given a value. 

For more information on Run Condition Words, see your OS 2200 Based LINC 



For UNIX 

For Reports initiated using the runrep shell script, you can determine the value of 

GLB.TASK from the return code of a LINC Report, and use that information to control 

dependent actions. The Report will return a value of zero through 99 to indicate the Report 

has successfully completed, or 100 through 199 to indicate that it has failed. 

You should set the value of GLB.TASK to a number in the range 60 through 99. This is 

because UNIX returns values in the ranges 1 through 31 and 129 through 159 if a Report is 

terminated by using a UNIX kill or a :TER LINC System command. 

For a description of the use of GLB.TASK for UNIX LINC System Reports, see your UNIX 

LINC Administration and Operations Guide. 

GLB.TASK defaults to zero. 


For LDA 

Moving a value to GLB.TASK causes the task value to be set. This value can then be tested 

by the program initiator. This value is written to ERRLOG.TXT at the completion of a 

report or at the end of an online session. This value is also written to the log file if logging 

is enabled. 

The initial value of GLB.TASK is zero. 

v 2-63


GLB.TIME 

GLB.TITLE 


GLB.TIME is a read-only System Data item that gives the system time in the form 

HHMMSSTT (hours, minutes, seconds, and hundredths of seconds). If debug date and time 

is activated, it contains the debug time. Its value is set at the beginning of an Ispec or 

Report. It is not changed during each Ispec transaction, and in a Report, it is only updated 

when SLEEP; or CRITICAL.POINT; commands are executed. 


GLB.TITLE contains a name used for Report output. A value in GLB.TITLE overrides the 

default name for a Report. 

GLB.TITLE is valid only in Report logic. It can be used for Shadow Reports in the form 

GLB.TITLEx, where x is the one-character Shadow Report designator (A through Z). 

Once output from a Report has been produced, the value of GLB.TITLE remains until the 

next RELEASE; command or end-of-job, when the most recent change to its value then 

applies. 

For related information, see also ‘‘GLB.FORMID’’. 

Further specific details for each host type are given in the following subsections. 


The default for the primary Report is PRINT. The default for Shadow Reports is PRINTx, 

where x is the Shadow Report designator (A through Z). 

MCP based Non-ROC and ROC Direct Reports 

The :BDD LINC System (colon) command can also be used to affect names used for Report 

output directed to Line Printers, or Remote Printers. (Also applies to ATTRIBUTE; 

BDNAME.) 

If a :BDD command is used with a GLB.TITLE value, the name of the backup disk file will 

be: 

 

2-64 v


Here bdd is the name set by the :BDD LINC System command, mix is the mix number, and 

title is the value of GLB.TITLE. The slash (/) character is a node delimiter, and cannot be 

used as a file name character when using GLB.TITLE. 

Notes: 

$ If the Report is a ROC Direct Report and the value of GLB.FILEINFO is Y, then the 

value of GLB.TITLE will be ignored. 

$ Using GLB.TITLE with the USERBACKUPNAME attribute in conjunction with 

CRITICAL.POINT or RELEASE; commands can give unpredictable results. For 

further details, see your MCP Based LINC Administration and Operations Guide. 

In Direct ROC Reports, GLB.TITLE is also used (as title) in the NOTE attribute of created 

printer backup files, in the form: 

 

MCP based ROC Standard Reports 

In standard ROC LINC Systems, GLB.TITLE is used as follows: 

$ In ROC Report and Output Request menus of files available 

$ In the NOTE attribute of created printer backup files, in the form (where title is the 

value of GLB.TITLE): 

 

$ In the REQUESTNAME attribute of the PRINTS/REPRINTS menus of print files, in the 

form (where title is the value of GLB.TITLE): 

 

$ In the printer backup file title, in the following form, where word is the first word of 

GLB.TITLE, and value is a three digit number: 

 

If GLB.DEVICE has a value of EX and the value of GLB.STN is an asterisk (*), the name to 

be used for the extracted file is the value of GLB.TITLE. This can be overridden on the 

ROC Write screen, by entering a value in the Filename field. 

Note: ROC uses the first word in GLB.TITLE as part of the print file name. Ensure 

that this word is in uppercase and that it only contains valid file name 

characters. 

v 2-65


OS 2200 

GLB.TITLE contains the name of the print file for Direct Reports. The default for the 

primary Report is $n, and for Shadow Reports it is $xn, wherex is the Shadow Report 

designator and n is a generated random number. You can move an alternative print file 

name to GLB.TITLE if required. 

If you are using the USERPRT facility, GLB.TITLE returns different values. When you have 

received the expected status from USERPRT, (spaces in CALL-FLAG) GLB.TITLE will 

contain PRINT for a primary Report, and PRINTx for Shadow reports (where PRINTx is 

the one-character Shadow Report designator). 

UNIX 

GLB.TODAY 

GLB.TITLE contains the name of the print file for Direct Reports. The default value for 

GLB.TITLEx is: 

 

Here x is the Shadow Report name, pid is the process id of the Report, and release is the 

number incremented for each release. The default value for GLB.TITLE is Ppid.1. The 

default location is $TMPDIR. 

If the full pathname is not specified, the file will be created in the system directory. 

LENGTH = 60 EDIT = A (All host types) 

A synonym for TODAY. For more details, see ‘‘TODAY’’ and ‘‘TODAYS-DATE-NUM’’, later 

in this section. 


GLB.TODAYS-DATE-NUM 

A synonym for TODAYS-DATE-NUM. For more details, see ‘‘TODAY’’ and 

‘‘TODAYS-DATE-NUM’’, later in this section. 


GLB.TODAYS-DAY 

A synonym for TODAYS-DAY. For more details, see ‘‘TODAY’’ and ‘‘TODAYS-DATE-NUM’’, 

later in this section. 


2-66 v

GLB.TODAYS-MONTH 

A synonym for TODAYS-MONTH. For more details, see ‘‘TODAY’’ and 



GLB.TODAYS-MONTH-NUM 


A synonym for TODAYS-MONTH-NUM. For more details, see ‘‘TODAY’’ and 



GLB.TODAYS-YEAR 

GLB.TOTAL 

A synonym for TODAYS-YEAR. For more details, see ‘‘TODAY’’ and 



GLB.TOTAL is a System Data item that is used in conjunction with the DATE.CONVERT; 

and DETERMINE; TOTAL logic commands. For more details, see the descriptions of these 

commands in this manual. 

GLB.TPGROUP 

LENGTH = 12 EDIT = + DECIMALS = 2 

Note: This System Data item is valid only for MCP based non-ROC Reports. It is not 

applicable for devices of type RP. 

This System Data item enables you to direct Report output to a predefined terminal printer 

group. The valid values of GLB.TPGROUP are contained in the following table. 

Value Output 

Valid group name Sent to the terminal printer group 

Not spaces Sent to TPS backup file 

spaces Determined by other settings 

v 2-67


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 



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. 


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 



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


For a UNIX LINC System , user names must be in your password file. The superuser 

usercode has a user name of spaces. 

GLB.USER is not implemented in LDA Run Time. 

GLB.USER can be used for Shadow Reports, in the form GLB.USERx, where x is the 


Once output from a Report has been produced, the value of GLB.USER remains as it is 

until the next RELEASE; command or end-of-job. At that point, the most recent change to 

GLB.USER then applies. 

GLB.USER has a default value of spaces. 


(When identifying MCP based Terminal Printer Spooler users, only the first 10 characters 

of GLB.USER are used.) 

GLB.USERCODE 

GLB.USERCODE is a read-only System Data item that can be accessed in Ispec logic to 

identify the current user sign-on identifier, as follows: 

$ MCP based usercode 

$ OS 2200 based userid 

$ UNIX user name 

$ Network user id (in LDA Run Time) 


GLB.VERSIONID 

GLB.VERSIONID is a read-only System Data item related to version control. It contains a 

short description of the current version of the LINC System, as entered on the Change 

Control Options screen for the LINC Specification. 






GLB.VERSIONID is not implemented in LDA Run Time. 


v 2-69


GLB.WORK 

GLB.WORK can be used in Ispec logic for transferring information between Ispecs. It is 

associated with each terminal user, and is unaffected by the activity of other terminals in 

the network. 

GLB.WORK is accessible from all Ispecs in the LINC System. Values are usually stored and 

retrieved from GLB.WORK by using either complex MOVE; commands or Group Setup 

Data items, or automatically by specifying a Global Setup Data item (GSD) or Group GSD 

name in the Global Work GSD field on the Primary Specification Options screen. For 

more details, see your LINC Generate Operations Guide. 

If the specified Global Work GSD contains initial values, these will be overwritten by the 

contents of GLB.WORK. Thus initial values used in this context have no effect. The 

contents of the Global Work GSD are not cleared by automatic logic, but are overwritten 

by the contents of GLB.WORK. 

You can preserve the contents of GLB.WORK between sessions by selecting the option 

Preserve Session Data on the Primary Specification Options screen. For more details, 

see your LINC Generate Operations Guide. 

You can also specify the length of GLB.WORK on the Primary Specification Options 

screen. The default minimum length is 128 characters. The maximum is 2000 characters. 

For LDA Run Time, the length is assumed to be greater than 24. 

GLB.WORK is recovered with the LINC System. It is maintained when GLB.ERROR is set 

to (*****), but not when Teach screens are displayed. GLB.WORK can be used by GLI 

input, although it is not available for Offline input or External Automatic Entries. 

GLB.YYMMDD 

GLB.ZEROS 

LENGTH = 128 to 2000 EDIT = A 

This read-only System Data item contains the current date (or the debug date, if debug date 

and time is activated) in YYMMDD format; for example, 980323, (for March 23, 1998). 

GLB.YYMMDD is accessible in Ispec logic only. 


GLB.ZEROS is a read-only System Data item that can be used in place of a literal value of 

zero (for comparing, ordering, and sorting purposes) on any host type. 

2-70 v

GLB.2PC 

INPUT-DATE 


GLB.ZEROS can be used to compare or set any numeric data item, regardless of its length, 

to zero. 

Note: The length defaults to 1 in complex MOVE; commands. 

LENGTH = Indefinite EDIT = N 

GLB.2PC can be used to change the default transaction commit level for an External 

Automatic Entry. Its default value is set by the value in the Two phase commit field on 

the Primary Specification Options screen. 

$ To change to two-phase commit, set GLB.2PC to Y. 

$ To change to immediate commit, set GLB.2PC to N. 

GLB.2PC must be set before the first external Automatic Entry in a transaction. 

For OLTP external Automatic Entries, the setting of GLB.2PC remains in effect only for the 

current transaction. 

For Hub external Automatic Entries, a change to GLB.2PC from Y to N will be ignored, and 

GLB.2PC will be treated as Y for all subsequent external Automatic Entries in that 

transaction. A change from N to Y after the first external Automatic Entry will be 

recognized. This permits the user to perform an initial non-2PC external Automatic Entry 

inquiry and then to do a 2PC global transaction for the updates. 

In Reports, the transaction commit level can be changed after each CRITICAL.POINT; or 

SLEEP; command. 

In a chain of external Automatic Entries, the commit level will be that imposed by the 

ultimate originator. 

Note: For an MCP based LINC System, moving Y to this System Data item will have 

no effect if the REAPPLYCOMPLETED/INDEPENDENTTRANS option is set to 

N on your Global Database DASDL Options screen. 

For further details, see the description of external Automatic Entries in "Interfacing to 

Other Systems",intheLINC Administration and Operations Guide for the relevant host 

type. 


INPUT-DATE contains the date on which a transaction is initiated. Its value is derived from 

that displayed in the Ispec screen header, (not from the date of transmission). Therefore, if 

debug date and time is activated, it contains the debug date. 

v 2-71


ISPEC 

LAST-LINE 

MAINT 

INPUT-DATE is accessible in all Ispec logic (but not in Reports). It is included in Event 

records (but not Components). 

INPUT-DATE takes the form from specified in the Date format IN UK or US field on the 

Primary Specification Options screen. 


ISPEC contains the name of the current Ispec, as displayed in the screen header line. 

ISPEC is included automatically with Event database records. 


LAST-LINE contains the number of the current line in a Repeat.From Ispec. It is 

automatically included with the record in the LINC database. If the value 999 is entered 

from the screen, the transaction is ended. 

Notes: 

$ In Pre-Screen logic for Repeat. From Ispecs, LAST-LINE is always equal to 1. 

$ When LAST-LINE appears in a Painter SHOW command, it may be shown as 

USAGE; OUTPUT. This is not relevant, since LAST-LINE is a System Data item. 


MAINT is used for maintaining Standard, Table, Direct, and Multiple Ordinate Memo 

Components. It has two functions: 

$ To enter an action for the Component, from the screen. 

$ To hold the status of the Component in the LINC database the first character of the 

relevant value of MAINT is stored in the database records (A, C,orD only.) 

Values (in English) that are valid in the MAINT field in the header line on a Component 

screen are listed in the following table. Further details of each action are given after the 

table. 

2-72 v

Action Purpose 

ADD Adds a record to the database. 

CHG Alters an existing record. 


DEL Logically deletes an existing record. (Not implemented in LDA Run Time) 

PUR Physically deletes an existing record. 

REC Recalls a record to the screen. 

FIR Recalls the first record in Ordinate order. 

LAS Recalls the last record in Ordinate order. 

NEX Recalls the next record. If no value is entered for the Ordinate, the first record in 

Ordinate order is retrieved. 

BAC Recalls the previous record. 

INQ Brings a record into memory (you must code logic to recall it to the screen). 

Note: The English values ADD, CHG, DEL, PUR and INQ are contained in the items 

GLB.ADD, GLB.CHG, GLB.DEL, GLB.PUR and GLB.INQ, respectively. These 

items may be translated. See the LLANGUAGE file details in the 

multiple-language section of your LINC Administration and Operations Guide 

for the relevant host type. 

Five values of MAINT (FIR, LAS, NEX, BAC, REC) provide recall functions, and have the 

following restrictions: 

$ They are only available if the AUTO.RECALL option has been set on the Component 

Options screen. 

$ They are not available if the Component has a Usage Output Ordinate. 

$ They do not change any values stored in the LINC database (including the value of 

MAINT). 

All of the values in the table are described in more detail in the following subsections. 

LENGTH = 3 (1 in the LINC database) EDIT = A 

ADD Value for MAINT 

A MAINT value of ADD (or its translated equivalent in GLB.ADD) is used to add new 

records. 

On the Ispec screen, this is the default value for the MAINT field. 

In the database, the record will have the value A. 

v 2-73


CHG Value for MAINT 

A MAINT value of CHG (or its translated equivalent in GLB.CHG) is used to modify an 

existing record that may have been recalled to the screen using one of the recall values 

above. When the transaction is submitted, fields that are blank on the screen are not 

changed in the LINC database (see the CLEAR.WHEN attribute). 

In the database, the record will have the value C. 

Note: When MAINT is set to CHG, Usage OUTPUT items that have the CLEAR.WHEN 

attribute set to zero are initialized to zero. 

DEL Value for MAINT 

A MAINT value of DEL (or its translated equivalent in GLB.DEL) is used to logically delete 

a record on the database. If a record is recalled to the screen by entering one of the recall 

values (REC, FIR, and so on), and the transaction is then resubmitted with DEL in the 

MAINT field, any non-blank fields will be stored on the LINC database. 

In the database, the record will have the value D. Such records are recalled using any of the 

recall options, and may have their deleted status removed by subsequently entering CHG 

(or its translated equivalent in GLB.CHG) in the MAINT field. 

(Records can be physically deleted by using the PURGE; command, or by entering PUR in 

the MAINT field.) 

This value is not implemented in LDA Run Time. 

PUR Value for MAINT 

A MAINT value of PUR (or its translated equivalent in GLB.PUR) is used to physically 

delete a record from the database. (In the database, the record no longer exists.) PUR is 

only valid if the Allow Purge Ispec option field is set to Y. 

If a record is recalled to the screen by using one of the recall values, and the transaction is 

resubmitted with PUR in the MAINT field, the record will be physically deleted. 

It is recommended (but not essential) that you first recall a record before it is purged in 

this way, to allow for visual checking. 

In an Automatic Entry, it is not valid to move a value of PUR into MAINT. This will set 

GLB.STATUS, and the Auto Entry will fail. 

REC Value for MAINT 

A MAINT value of REC brings a database Component record into memory, and displays 

the Usage Input-Output data items from that record. 

2-74 v

The following requirements and restrictions apply: 


$ REC is only available if the AUTO.RECALL option has been set on the Component 

Options screen. 

$ An Ordinate value must be specified. 

$ Numeric validation is performed, and so decimal points or separator characters must 

be included for numeric Ordinates. 

$ Trailing zeros must be included if the Ordinate contains decimals. 

$ Where the Ordinate is also a Keyword, leading zeros must be entered for numeric 

items. 

$ Pre-Screen, Pre-LINC, and Main logic are not performed. 

$ Logic dependent on a condition testing for a value of REC is never executed. For 

example: 

 

The recall function does not change any database values (including the value of MAINT) in 

the database records. 

FIR Value for MAINT 

A MAINT value of FIR retrieves the first Component record (the record with the lowest 

Ordinate value). 

This recall function does not change any database values, including the value of MAINT in 


For details of the requirements for the Ordinate value, see ‘‘REC Value for MAINT’’. 

LAS Value for MAINT 

A MAINT value of LAS retrieves the last Component record (the record with the highest 

Ordinate value). 

This recall function does not change any database values (including the value of MAINT) in 



NEX Value for MAINT 

A MAINT value of NEX retrieves the next Component record (the record with the 

next-highest Ordinate value to that specified). If no Ordinate value is entered, the first 

record is retrieved (the record with the lowest Ordinate value). 

v 2-75





BAC Value for MAINT 

A MAINT value of BAC retrieves the previous Component record (the record with the 

next-lowest Ordinate value to that specified). 




INQ Value for MAINT 

TODAY 

A MAINT value of INQ (or its translated equivalent in GLB.PUR) validates the Ordinate and 

brings a record into memory. Control is then passed to your LINC logic. Your LINC logic 

should then set up the screen appropriately, and perform the RECALL;. 

TODAY is a read-only System Data item that holds the date that an Ispec transaction was 

initiated, or the date a Report was started (or restarted after a SLEEP; command). If debug 

date and time is activated, it contains the debug date. 

TODAY is in the form of an alphabetic date. The format depends on that set on the Primary 

Specification Options screen (UK, US, or IN). The day number of the month can be 

accessed as TODAYS-DAY, the month as TODAYS-MONTH, and the year as 

TODAYS-YEAR. 

GLB.TODAY is a synonym for TODAY. 


TODAYS-DATE-NUM 

TODAYS-DATE-NUM is a read-only System Data item that holds the date that an Ispec 

transaction was initiated, or the date a Report was started (or restarted after a SLEEP; 

command). If debug date and time is activated, it holds the debug date. 

This data item has a fixed format of MMDDYY (for example, 022598 for February 25, 1998). 

The month can be accessed as TODAYS-MONTH-NUM, the day as TODAYS-DAY, and the 

year as TODAYS-YEAR. 

2-76 v

TODAYS-DAY 

GLB.TODAYS-DATE-NUM is a synonym for TODAYS-DATE-NUM. 


Note: TODAYS-DATE-NUM causes a syntax error in LDA Run Time. Use 

GLB.TODAYS-DATE-NUM instead. 

For more details, see ‘‘TODAY’’, earlier in this section. 


TODAYS-DAY is a read-only System Data item that holds the day part of the date that an 

Ispec transaction was initiated, or the date a Report was started (or restarted after a 

SLEEP; command). If debug date and time is activated, it holds the day part of the debug 

date. 

GLB.TODAYS-DAY is a synonym for TODAYS-DAY. 

Note: TODAYS-DAY causes a syntax error in LDA Run Time. Use GLB.TODAYS-DAY 

instead. 



TODAYS-MONTH 

TODAYS-MONTH is a read-only System Data item that holds the three-character 

alphabetic month part of the date that an Ispec transaction was initiated, or the date a 

Report was started (or restarted after a SLEEP; command). If debug date and time is 

activated, it holds the month part of the debug date. 

GLB.TODAYS-MONTH is a synonym for TODAYS-MONTH. 

Note: TODAYS-MONTH causes a syntax error in LDA Run Time. Use 

GLB.TODAYS-MONTH instead. 



TODAYS-MONTH-NUM 

TODAYS-MONTH-NUM is a read-only System Data item that holds the numeric month part 

of the date that an Ispec transaction was initiated, or the date a Report was started (or 

restarted after a SLEEP; command). If debug date and time is activated, it holds the 

numeric month part of the debug date. 

v 2-77


TODAYS-YEAR 

TRANNO 

GLB.TODAYS-MONTH-NUM is a synonym for TODAYS-MONTH-NUM. 

Note: TODAYS-MONTH-NUM causes a syntax error in LDA. Use 

GLB.TODAYS-MONTH-NUM instead. 



TODAYS-YEAR is a read-only System Data item that holds the two-digit year part (within 

the century) of the date that an Ispec transaction was initiated, or the date a Report was 

started (or restarted after a SLEEP; command). If debug date and time is activated, it holds 

the year part of the debug date. 

GLB.TODAYS-YEAR is a synonym for TODAYS-YEAR. 

Note: TODAYS-YEAR causes a syntax error in LDA Run Time. Use 

GLB.TODAYS-YEAR instead. 



TRANNO contains a number (in the range 000001 through 999999), that is incremented by 

one for each transaction, according to the rules shown in the following table. 

Host TRANNO is incremented for...... 

MCP based Transactions that update the database or change the contents of 

GLB.WORK. It is not incremented for inquiry transactions that do not modify 

GLB.WORK. 

OS 2200 based All transactions that do not set GLB.ERROR to *****, and are not in 

recovery 

UNIX All transactions that do not set GLB.ERROR to *****, and are not in 

recovery 

It is used for both Component and Event transactions, but is included only in the Event 

record on the LINC database. 

TRANNO values are unique for each transaction sent from a station (username). 

2-78 v

Caution 


Exercise care when using TRANNO as a unique key in Event records. It is possible 

for records from different stations to have the same TRANNO value. 


v 2-79

Appendix A 

Formulas for the DISCOUNT.CASH; 

Command 

Overview 

This appendix contains formulas for the calculations used by the DISCOUNT.CASH; 

command. 

Conventions used in the various formulas are listed in the following table. 

Symbol Meaning 

. Multiplication operator 

ln Natural logarithm 

i Interest rate (0.0 through 1.0) 

n Number of time units in the calculation 

P Present value of the financial amount 

SN Financial amount after time period n (the sum after n periods) 

A Annuity payment occurring at the end of each time period 

A* Annual rate of flow (the rate of steady flow throughout the term, as opposed to 

discrete annuity payments) 

A and A* are related by the following formula. 

 

v A-1

Formulas for the DISCOUNT.CASH; Command 

Calculations 

PV.FLOW (P.A*) Present Value 

This action calculates the present value required to produce an annual rate of flow for n 

periods, leaving a future value of zero. 

P = A* . ((1 + i) - 1) / ((1 + i) .ln(1+i)) 

FLOW.PV (A*.P) Annual Rate of Flow 

This action calculates the annual rate of flow required to reduce the present value to zero 

in n periods. 

A*=P.((1+i) . ln(1 + i)) / ((1 + i) -1) 

FV.FLOW (SN.A*) Future Value 

This action calculates the future value that will accumulate in n periods from an annual 

rate of flow. 

SN=A*.((1+i) -1)/ln(1+i) 

FLOW.FV (A*.SN) Rate of Flow yielding Future Value 

This action calculates the Annual Rate of Flow required to produce a nominated future 

value. 

A*=SN.ln(1+i)/((1+i) -1) 

COMPOUND (C, SN.P) Future Value from Present Value 

This action calculates the future value accumulated in n periods from the present value. 

SN = P . (1 + i) 

DISCOUNT (D, P.SN) Present Value yielding Future Value 

This action calculates the present value required to accumulate into a nominated future 

value. 

P=SN/(1+i) 

MORTGAGE (M, A.P) Annuity to repay Present Value 

This action calculates the annuity (regular payment) required to amortize the present value 

in n periods. 

A=P.i.(1+i) / ((1 + i) -1) 

PV.ANNUITY (P.A) Present Value yielding Annuity 

This action calculates the present value required to produce an annuity for n periods, with 

a zero final balance. 

A-2 v

P = A . ((1 + i) -1)/(i.(1+i) ) 

Formulas for the DISCOUNT.CASH; Command 

FV.ANNUITY (SN.A) Future Value resulting from Annuity 

This action calculates the future value accumulated in n periods from an annuity (regular 

savings). 

SN = A . ((1 + i) -1)/i 

SINK (A.SN) Annuity yielding Future Value 

This action calculates the annuity (regular savings) required to accumulate into a 

nominated future value. 

A = SN . i / ((1 + i) -1) 

v A-3

Appendix B 

Railroad Diagram Syntax 

Overview 

In Section 1, the syntax of LINC logic commands is illustrated with railroad diagrams. 

Railroad diagrams are read left-to-right, or in the direction indicated by an arrowhead. The 

end of the diagram is indicated by a vertical bar. Continuation from one line to another is 

indicated by a number at the end of a line and a corresponding number at the beginning of 

another line. 

Information contained in italics is variable information to be supplied. Further 

information about these values (called metatokens) will follow the syntax diagram, or can 

be found in ‘‘Conventions for Syntax Diagrams’’ , in this manual. 

Otherwise, enter everything else exactly as it appears. 

Sample 

A sample railroad diagram and an explanation of its parts follows. 

DD DDDDDD DDDDD 

DDBDDDDDDDDDDDDDDDDDDDDDDDDDDDBDDDDBDDDDDDDDDDDDDDDDDDBDDDD 

3 3 3 3 

@D DDDDD DDY @D DDDDD DDY 

DDDD DDDDDDDDDDDDDDDDDD4 

The following are statements that may be constructed from this diagram. 

 

 

 

 

 

v B-1


Required Items 

An item is required if there is no alternative path through the diagram. 

DDDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD4 

Optional Items 

Loops 

Items listed vertically below the main line of the diagram indicate optional items. 

DDDD DDDDDBDDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDD4 

3 3 

CDDD DDD4 

3 3 

@DDD DDDY 

The following statements are valid constructions from the previous diagram. 

 

 

 

A loop indicates repeated access to part of a railroad diagram. 

Note: There may be limits (such as the number of items allowed) associated with 

loops. Limits are included with the description of the command. 

ZDDD? 

ZDDDDDDDDDY @DDDDDDDDDDDDDD? 

ZDDDDDDDDDDDDDDDDDDDDDDDDDDDD? 

3 3 

DDDDDDDDDDDDDDDDDDDDDADDDBDD DDBDDDADDDDD4 

3 3 

@DD DDY 

The following statements may be constructed from this diagram. 

 

 

 

A loop must be used in the direction indicated by the arrow. If there is no arrow, read 

left-to-right. 

B-2 v

Bridges 

A bridge indicates the maximum number of times a loop may be traveled. 

ZDDD? 

ZDDDDDDDDDY @DDDDDDDDDDDDDD? 

3 3 

DDDDDDDDDDDDDDDDDDDDDADDDBDD DDBDDDADDDDD4 

3 3 

@DD DDY 

The following statements may be constructed from this diagram. 

 

 

 

 

 

 


v B-3

Glossary 

A 

access class 

For LINC Ad Hoc Inquiry, a particular type of user access to queries, defined by a letter (A 

through Z) or an asterisk (*, for unrestricted access). Also called query class. 

Action line 

A field that appears on most screens in LINC Generate, enabling fast-track navigation to 

required functions. Also referred to as the Action field. 

Ad Hoc Inquiry 

See LINC Ad Hoc Inquiry. 

Automaint Profile 

The Profile of a Multiple Ordinate Memo Component that provides automatic access to the 

records of that Component. See Multiple Ordinate Memo Component, Profile. 

Automatic Entry 

(1) A facility that enables an Ispec to create a record in another Ispec. (2) A facility that 

enables an Ispec to modify an existing record in a Standard Component, Table Component, 

or Multiple Ordinate Memo Component. (3) Not applicable to Copy.From Ispecs. (4) See 

also Automatic Entry buffer, external Automatic Entry, internal Automatic Entry, HUB. 

Automatic Entry buffer 

An area in memory used by the Automatic Entry facility. See Automatic Entry. 

Automatic Lookup 

A process where a Component record is automatically read into memory from the 

database. 

v Glossary-1

Glossary 

B 

banner 

A system-generated page that prints at the start of a Report and provides control 

information about that Report. 

base year 

The year upon which the DATE.CONVERT; command bases relative day numbers. The 

year is defined using the Primary Database Options screen and may be accessed through 

the System Data item GLB.BASE. See relative day number. 

Buildable LINCIIDIR 

The LINC installation directory is defined by the environment variable LINCIIDIR. A 

LINCIIDIR that contains the LINC object packages necessary to build LINC executables 

using object packaging is a buildable LINCIIDIR. A buildable LINCIIDIR is necessary to use 

object packaging to maintain your LINC environment 

Bulk Option screens 

A group of screens in LINC Generate that enable options for several Ispecs, Reports, 

Profiles, or Global Logics to be entered together. 

C 

CER 

A Customer Engineering Request (CER) is a customer specific EIF resulting from a 

customer request. CERs are handled in the same way as EIFs. See EIF. 

Change Control 

A method for tracking changes to LINC Specifications in LINC Generate. 

Change identifier 

A alphanumeric value used to identify a single user or user terminal for change control 

purposes. Applies when the Change Identification option is selected for that LINC 

Specification. Contrast with Patch identifier. 

class 

See access class, security class. 

Column name 

For LINC Ad Hoc Inquiry, an SQL term equivalent to data item. 

Glossary-2 v

Glossary 

Component 

(1) A business resource such as a customer, product or vendor. (2) A store of static data 

about a business resource. (3) Consists of a screen layout and associated logic (Pre-Screen 

logic, Pre-LINC logic, and Main logic). (4) Together with Events, Components form the 

fundamental building blocks of a LINC System. (5) See also Ispec, Standard Component, 

Table Component, Memo Component, Multiple Ordinate Memo Component. 

Component Profile 

For LINC Ad Hoc Inquiry, a Profile over one Component. (2) Contrast with Event Profile. 

Component record 

For LINC Ad Hoc Inquiry, an individual database record for a Component. Equivalent in 

SQL terminology to a row. 

COMUS 

For os 2200 based LINC Systems, a product used to build LINC Deployment before 

installation (see SOLAR). 

Copy.From Ispec 

An Ispec with a screen that has a number of identical recurring lines. Transmission of the 

whole screen produces a separate record in the database for each completed line. See also 

Ispec. 

Critical Point 

(1) A procedure used within a LINC Report to aid in recovery following a system failure. 

(2) Created by using the CRITICAL.POINT; LINC Logic command. 

Customizer 

See LINC Customizer. 

D 

DAD 

See Data Display. 

Data Attribute 

An attribute of a data item. For example, LENGTH, EDIT, BRIGHT. 

Data Command 

A command that identifies or creates a data item used in a screen layout, LINC Report, or 

logic. 

Data Display (DAD) 

(1) Optional descriptive text for a data item. Used in status messages in place of the name 

of the data item. (2) Defined using the DATA.DISPLAY Data Attribute. 

v Glossary-3

Glossary 

Data item 

Part of a LINC Specification defined by using the DATA; command in LINC Painter. Used 

to enter, store and display data. 

data item 

The collective term for the variables used to enter, manipulate, store, and display data 

(Data items, Ordinates, Setup Data items, and so on). 

database 

See LINC Database. 

Database Management Utility (DMU) 

(1) A LINC Utility that enables you to maintain your LINC Database. (2) Use to perform 

such tasks as changing the amount of disk space allocated to database structures, initiate a 

full or partial database reorganizations (for MCP based LINC Systems), and creating 

ORACLE SIDs and Griffin Universes (for UNIX LINC Systems). (3) See also Griffin 

Database Management Utility (GMU). 

Development System 

See LINC Development and LINC Generate. 

Direct Component 

A Component type that uses a key for direct access to the dataset, saving on the number of 

Input/Output operations. It has a single numeric Ordinate with a maximum of 8 digits. See 

Component. 

Direct Report 

(1) A specific type of Report that uses the LINC Report Output Control System (ROC), and 

which sends output directly to an output device and not to the ROC database. (2) See also 

LINC Report Output Control System. (3) Contrast with Standard Report. 

Display item 

A string of descriptive information displayed on an Ispec screen layout or Report Frame, 

primarily used to inform the user which data items are which. 

DMU 

E 

Editor 

EIF 

See Database Management Utility. 

See LINC Editor. 

Engineering Interim Fixes (EIFs) are used to distribute new features, fixes, customer 

requests and newly validated versions of support software. 

Glossary-4 v

Glossary 

Environmental Options screens 

Screens in LINC Generate that enable you to define options for your LINC Specification 

that apply to the generation on a particular host type. 

Event 

(1) An activity performed by an organization, for example a sale, purchase, or payment. (2) 

A store of data about an activity performed. (3) Consists of a screen layout and associated 

logic (Pre-Screen logic, Pre-LINC logic, and Main logic). (4) Together with Components, 

Events form the fundamental building blocks of a LINC System. (5) See also Ispec. 

Event file 

For LINC Ad Hoc Inquiry, the file containing the Event records. 

Event Profile 

For LINC Ad Hoc Inquiry, a Profile over one or more Events. Contrast with Component 

Profile. 

Event record 

For LINC Ad Hoc Inquiry, an individual database record for an Event. Equivalent in SQL 

terminology to a row. 

Executables 

Executables are one of two methods of distributing LINC to customers. They are the 

compiled set of LINC files which are ready to install and run. Contrast this with Objects. 

external Automatic Entry 

An Automatic Entry to or from an external source, such as another LINC System. See 

Automatic Entry, HUB. Contrast with internal Automatic Entry. 

Extract file 

A non-database (text) file created or read by a LINC Report. 

F 

Fireup Ispec 

A particular Ispec that is displayed on your terminal when you sign on to a LINC System. 

G 

Generalized LINC Interface (GLI) 

A facility that enables a non-LINC program to initiate transactions into a LINC Information 

System. 

Generate Group 

A specified group of Reports that can be generated together. 

v Glossary-5

Glossary 

Generate Set 

A named set of values for generating a particular LINC System from a LINC Specification; 

for example, for a particular host type. 

GLI 

See Generalized LINC Interface. 

Global Data Dictionary 

(1) A data dictionary that controls the use of data items over all LINC Specifications within 

the same LINC Generate. (2) Part of GLOBAL Specification. (3) See also LINC Data 

Dictionary, Local Data Dictionary. 

Global Logic 

(1) Part of a LINC Specification that can be reused in other parts of your LINC 

Specification. (2) Inserted into Ispecs, Reports, or Global Logics by using the INSERT; 

logic command. (3) See Insertable Global Logic, Performable Global Logic. 

Global Setup Data item 

A Setup Data item that can be used by any Ispec or Report logic within a LINC 

Specification. See Setup Data item, Group Global Setup Data item. 

GMU 

See Griffin Database Management Utility. 

Griffin Database Management Utility (GMU) 

The equivalent of the Database Management Utility (DMU) for Griffin (UNIX) LINC 

Systems. 

Griffin 

Database Management System used as the underlying database software for Griffin (UNIX) 

LINC Systems and LINC Generate. Griffin is produced by Unisys Corporation. See also 

ORACLE. 

Griffin Universe 

A Griffin term for a logical storage area that may contain one or more UNIX LINC 

Databases. Equivalent of ORACLE SID. See also Tablespace. 

Group Global Setup Data item 

A Global Setup Data item that is a concatenation of a number of other Global Setup Data 

items. See Global Setup Data item. 

group query 

For LINC Ad Hoc Inquiry, an SQL format query whose output lines are for groups of 

related records (rather than individual records). The group is defined by including a 

GROUP BY clause, or by including group functions (such as MAX, MIN, SUM, and AVG) in 

the select list. 

Glossary-6 v

Glossary 

Group Setup Data item 

A Setup Data item that is a concatenation of a number of other Setup Data items. See Setup 

Data Item. 

H 

highlighting attribute 

An attribute of a data item or Display item that affects its appearance when displayed on a 

screen or printed in a LINC Report. For example, BRIGHT or REVERSE. 

Home position 

Top left corner of the screen. Often used as the position from which commands are 

entered. 

Home screen 

For LINC Ad Hoc Inquiry, the base screen from which the main functions are chosen. 

host list 

(1) The list of valid host types for which LINC Generate can perform reserved word 

checking and generation of LINC Systems. (2) The initial list is specified on installation. (3) 

Can be changed in the GLOBAL Specification, by using the Supervisor screen. (For LINC 

Customizer, the list cannot be changed.) 

HUB Background Run 

For OS 2200 LINC Systems, a background run that processes external Automatic Entries. 

There is one LINC Background Run for each LINC Deployment. See also HUB. 

HUB 

I 

ICP 

The facility that controls external Automatic Entries between LINC Systems. See 

Automatic Entry, external Automatic Entry. 

See Initial Control Program (for OS 2200 based LINC Systems) and Ispec Control Program 

(forUNIXLINCSystems). 

Initial Control Program (ICP) 

The program that controls the generated Ispec subprograms in OS 2200 based LINC 

Systems. Contrast with Update Program (for MCP based LINC Systems) and Ispec Control 

Program (for UNIX LINC Systems). 

Insertable Global Logic 

A sequence of business rules (logic) and a screen layout that can be copied into any 

number of Ispecs and LINC Reports. Contrast with Performable Global Logic. 

v Glossary-7

Glossary 

interdatabase access 

The accessing of the database of an OS 2200 based LINC System by another OS 2200 based 


internal Automatic Entry 

An Automatic Entry from within the same LINC System. See Automatic Entry. Contrast 

with external Automatic Entry. 

interrogation point 

For LINC Ad Hoc Inquiry, a regular interval during query execution when the status of that 

query is written to the database. 

Ispec 

(1) A collective term for Components and Events. (2) A contraction of the term Interface 

Specification. (3)See also Component, Event. 

Ispec Control Program (ICP) 

The program that controls the generated Ispec subprograms in UNIX LINC Systems. 

Contrast with Update Program (for MCP based LINC Systems) and Initial Control 

Program (for OS 2200 based LINC Systems). 

K 

Keyword 

A data item that has multiple data entry fields and display items. See also Keyword Term 

Item, Keyword Term Display. 

Keyword Term Display 

The Display item associated with a Keyword. See Keyword. 

Keyword Term Item 

The data item associated with a Keyword. See Keyword. 

L 

LDA 

See LINC Development. 

LDL Listing Utility 

A facility in LINC Generate used for printing a LINC Specification. 

LCOPY Utility 

(1) A utility that provides a means of backing up, maintaining and controlling LINC 

Specifications, on the same or different machines (and host types). (2) Formerly known as 

LINC Copy. 

Glossary-8 v

LINC Ad Hoc Inquiry 

A facility used for making inquiries on a LINC Database. 

Glossary 

LINC Administration Guide 

The LINC manual that contains instructions for administering and operating LINC Systems 

on a particular host type. See the front matter for details. 

LINC Background Run 

For OS 2200 LINC Systems, a background run that controls certain functions; for example 

recovery, report handling, and setting up of Common Banks. There is one LINC 

Background Run for each LINC Deployment. 

LINC Customizer 

A collective term for the automated facilities and utilities used during the customizing and 

generation of a LINC Specification. 

LINC Data Dictionary 

A collective name for the Local and Global data dictionaries. See Local Data Dictionary, 

Global Data Dictionary. 

LINC Database 

The database created in the generation of a LINC System. Used for storing data. 

LINC Deployment 

(1) A collective term for the software programs required to operate, control and audit a 

LINC System and its LINC Database. (2) Contrast with LINC Generate. (3) Formerly LINC 

Run Time. 

LINC Development 

(1) PC based development tool for creating and maintaining LINC Business Models (LINC 

Specifications). (2) LINC Business Models are transferred to host based LINC Generate for 

generation and deployment in LINC Deployment. (3) Formerly known as LDA III. 

LINC Development Environment 

A collective term for the tools used to design, develop and generate LINC Systems. 

Includes LINC Development, LINC Generate, and LINC utilities. 

LINC Development System 

See LINC Generate. 

LINC Development Test 

Part of LINC Development that enables testing of your LINC Business Model. 

LINC Editor 

A facility for specifying business rules (logic), expressed using LINC Logic commands and 

text. 

v Glossary-9

Glossary 

LINC Generate 

(1) The LINC Software used to generate LINC Specifications as LINC Systems for use in 

LINC Deployment. (2) Formerly known as LINC Development System. 

LINCIIDIR 

LINCIIDIR is an environment variable specifying the LINC installation directory. 

LINC Installation Guide 

The LINC manual that contains instructions for installing and configuring LINC Systems on 

a particular host type. See the front matter for details. 

LINC Interactive Test Environment (LITE) 

(1) Software that enables testing and debugging of LINC Systems. (2) Interacts with LINC 

Generate and LINC Deployment. 

LINC Painter 

A facility of LINC Generate used to define an Ispec screen layout or Report Frame layout. 

LINC Report 

(1) Part of a LINC Specification, generated and used to produce output or to carry out 

specialized batch processing of a LINC Database. (2) Consists of Report Frames and 

Report Main logic, and a number of options that define the operation and output of the 

Report. (3) Many programs in LINC Generate and LINC Utilities are LINC Reports. 

LINC Report Output Control System (ROC) 

A utility that provides control over the output of a LINC Report. 

LINC Run Time 

See LINC Deployment. 

LINC Security Level 

A value from 0 through 9 that is assigned to a specific user or terminal to restrict access to 

various functions. 

LINC Security Module (LSM) 

A utility which provides security facilities for both LINC Generate and LINC Systems. 

LINC Specification 

(1) The source definition of a LINC System. LINC Specifications are stored within LINC 

Generate. (2) The result of specifying a LINC Business Model using LINC Development. (3) 

The source from which a LINC System is generated. 

LINC System 

The set of programs (and database) generated from a LINC Specification. 

Glossary-10 v

Glossary 

LINC System command 

A command to assist in the operation of a LINC System or LINC Report. Formerly known 

as a colon command. 

LITE 

See LINC Interactive Test Environment. 

local Data Dictionary 

A data dictionary that controls the use of data items within a single LINC Specification. See 

also LINC Data Dictionary, Global Data Dictionary. 

locked query 

For LINC Ad Hoc Inquiry, a query that is not available for editing or running because it is 

currently queued for execution, or its execution has terminated abnormally, or it is being 

edited. 

logically deleted 

A term used to describe the status of an Ispec record that has been deleted from a database 

as far as all processes are concerned, but is physically still present. 

LSM 

See LINC Security Module. 

LSM security 

For LINC Ad Hoc Inquiry, the security imposed by the LINC Security Module (LSM). If in 

effect, user access to queries and the limits associated with queries may be restricted. 

M 

Main Logic 

A section of user-specified Ispec logic that is executed after any Pre-LINC logic and LINC 

automatic editing and validating sequences have been executed. 

MAINT 

(1) A System Data item, stored with each record of every Standard, Table, and Multiple 

Ordinate Memo Component, that indicates whether that record is added, changed or 

deleted. (2) A screen field for every Standard, Table, and Multiple Ordinate Memo 

Component used to indicate the database maintenance action request. 

Maintenance Mode 

A Painter facility that enables an existing Ispec screen layout or Report Frame to be 

modified. 

Memo Component 

A Component type that has no Ordinate, and which is used to store data of a memorandum 

nature. See Component, Multiple Ordinate Memo Component. 

v Glossary-11

Glossary 

Memo Data 

Memo-type, optional Ispec data that is stored separately to the primary Ispec records to 

assist with the optimization of disk usage. Valid for MCP based LINC Systems only. See 

Ispec. 

Menu Assistance 

A LINC Painter facility that provides assistance when painting an Ispec screen layout or 

LINC Report Frame. 

menu format query 

A query created using the various selection screens of LINC Ad Hoc Inquiry. Contrast with 

SQL format query. 

MLA 

Module 

See Multiple Language Mode. 

LINC Specification that is a subset of a Module Master. When generated a Module 

produces a complete LINC System. See also Module Master. 

Module Master 

A complete LINC Specification that contains defined parts (Modules) that can be 

generated as separate LINC Systems. See also Module. 

multiple language facilities 

A collective term for the LINC facilities that enable a LINC System to be translated and 

used in up to fifteen different languages, from a single LINC Specification. 

Multiple Language Mode (MLA) 

An facility in a menu of LINC Generate that enables a language name or number to be 

defined. (2) See multiple language facilities. 

Multiple Ordinate Memo Component 

(1) A Memo Component with one or more Ordinates defined by a specified Profile (that is 

sometimes referred to as its Automaint Profile). (2) Similar to a Standard Component, but 

with multiple Ordinates. (3) See also Component, Standard Component and Automaint 

Profile. 

N 

NOF 

NOFORM 

See NOF. 

(1) A facility for interfacing to and from a LINC System, usually to an non-LINC System and 

terminals. (2) The interface to PowerClient uses NOF. 

Glossary-12 v

Non-Formatted Input/Output (NOF) 

See NOF. 

O 

Glossary 

Object Packaging 

Object packaging allows the creation of LINC executables from supplied LINC object files, 

the installation of LINC, the installation of LINC EIFs, and the maintenance of your LINC 

environment. It also allows the creation of new LINC object and executable packages 

which can include supplied EIFs. Packages can be created for distribution and as backups. 

. 

Objects 

Objects are one of two methods of distributing LINC to customers. They are the set of 

LINC object files which must be built into executables on your site before LINC can be run. 

Objects files are built using Object Packaging. Contrast this with Executables 

Offline interface 

A facility for passing batches of high-volume, non-LINC transactions for a LINC System. 

OLTP 

See Online Transaction Processing. 

On Change Statistical Routine 

A statistical routine (for example, AVERAGE;) that can be performed on a data item as 

part of an ON.CHANGE; LINC Logic command. 

Online Transaction Processing (OLTP) 

A generic method for transferring transactions to other systems. 

ORACLE 

Relational Database Management System used as the underlying database software for 

ORACLE (UNIX) LINC Systems. ORACLE is produced by Oracle Corporation. See also 

Griffin. 

ORACLE SID 

An ORACLE term for a logical storage area that may contain one or more UNIX LINC 

Databases. Equivalent of Griffin Universe. See also Tablespace. 

Ordinate 

The data item of a Component that acts as the unique identifier of one record from 

another. The access path to individual Component records. 

v Glossary-13

Glossary 

P 

pack 

Painter 

patch 

The location in which part of a LINC System or LINC Database is stored. For a UNIX LINC 

System, a pack is either a Tablespace or a UNIX pathname. 

See LINC Painter. 

A set of changes to a LINC Specification made over a period of time by users signing on to 

LINC Generate under a specific patch identifier value. 

Patch identifier 

A number used to identify and group changes to a LINC Specification by one or more 

users. Applies when the patch identification option is selected for that LINC Specification. 

Contrast with Change identifier. 

Performable Global Logic 

A sequence of business rules (logic) that can be executed by any number of Ispecs and 

LINC Reports. Contrast with Insertable Global Logic. 

Pre-LINC Logic 

A section of user-specified Ispec logic that is executed before the Ispec Main logic is 

executed. 

Pre-Screen Logic 

A section of user-specified Ispec logic that is executed before the screen layout is 

displayed on the terminal. 

Primary Database Options screen 

The screen in LINC Generate for setting basic options and parameters for a LINC System. 

The screen displayed whenever a new LINC Specification is being created. 

Product Menu Utility 

Product Menu is a menu driven utility to access object packaging features. See Object 

Packaging for details of the functions that can be performed with Product Menu. 

Profile 

(1) An index to a specified selection of records. (2) A method of providing access to just 

those records that are required to perform a specific function. (3) A functional view of the 

database. 

Profile Data 

A data item that is physically stored in a Profile as well as in its associated Ispec. See also 

Profile. 

Glossary-14 v

Glossary 

Profile Ordinate 

The data item by which a Profile accesses individual records. A Profile can have several 

Profile Ordinates. See also Profile. 

Q 

query class 

See access class. 

Query Compiler 

For LINC Ad Hoc Inquiry, the part of LINC Ad Hoc Inquiry that validates an entered query 

and transforms it to a standard internal code and format. See also Query transformation. 

Query Front End 

For LINC Ad Hoc Inquiry, the part of LINC Ad Hoc Inquiry that allows a query to be entered. 

Query Optimizer 

The part of LINC Ad Hoc Inquiry that selects the most efficient way to access the LINC 

Database for a query. 

Query Output Handler 

The part of LINC Ad Hoc Inquiry that provides facilities to manipulate query output. 

Query Processor 

The part of LINC Ad Hoc Inquiry that interprets the query code and runs the query against 

the LINC Database. 

Query Processor report 

For LINC Ad Hoc Inquiry, the program that performs the functions of the Query Processor. 

This program is a LINC Report. 

query transformation 

For LINC Ad Hoc Inquiry, the process performed by the Query Compiler to convert a 

validated query into a standard internal form. 

queued query 

For LINC Ad Hoc Inquiry, a query waiting (for resources) to begin execution. 

v Glossary-15

Glossary 

R 

relation name 

For LINC Ad Hoc Inquiry, an SQL term equivalent to a Component, the Event file, or an 

Event Profile. Also called a table . 

relative day number 

A date expressed as the number of days since January 1 of the base year (which is 

accessible through the System Data item GLB.BASE). The relative day number of January 

1 of the base year is zero. See also base year. 

Report 

See LINC Report. 

Report Frame 

(1) Layout that contains display text and data items, and some associated logic that is part 

of a LINC Report. (2) The logic is executed (often to define the data items in the layout) 

and then the layout is included in the Report output. (3) Report Frames are accessed as 

single units from the logic of Report Frame or from Main logic of the Report. 

Report Initiation Program (RIP) 

An MCP based LINC utility that enables you to execute a line printer Report or terminal 

printer Report in batch mode. 

Report Output Control System (ROC) 

See LINC Report Output Control System. 

resource locking 

A facility of LINC Generate that prevents access to parts of a LINC Specification by more 

than one user at a time. 

ROC 

See LINC Report Output Control System. 

ROC Background Run 

For OS 2200 LINC Systems, a background run that identifies Report output requests and 

spools the output to the required print queue. There is one ROC Background Run for each 

LINC Deployment. 

row 

For LINC Ad Hoc Inquiry, an SQL term equivalent to a Component record or an Event 

record. 

Run Time Environment 

See LINC Deployment. 

Glossary-16 v

S 

Screen Build mode 

A Painter facility that is used to specify a new Ispec screen layout. 

Glossary 

search expression 

For LINC Ad Hoc Inquiry, a logical expression used in a search list to define records to be 

included in query output. 

search list 

For LINC Ad Hoc Inquiry, the part of a query that determines whether records will be 

included in the output. 

security access 

For LINC Ad Hoc Inquiry, full access to all queries. 

security class 

For LINC Ad Hoc Inquiry, a type of user access to queries. See access class. 

select list 

For LINC Ad Hoc Inquiry, the part of a query that defines the data items to be included in 

the output. 

Setup Data item 

A data item used in memory only for data manipulation by an Ispec or LINC Report. See 

also Global Setup Data item, Group Setup Data item. 

Shadow Report 

Part of a LINC Report used to produce additional output separate from that produced by 

the primary functions of the Report. 

Sleeping Report 

A Report that, by the use of the SLEEP; LINC Logic command, stops executing for a 

predetermined number of seconds or until reactivated by your LINC System. 

SOLAR 

For OS 2200 LINC Systems, a product used to install LINC Software. 

sort expression 

For LINC Ad Hoc Inquiry, a logical expression used in a sort list to define output sort order. 

sort list 

spooler 

For LINC Ad Hoc Inquiry, the part of a query that defines the order of the output. 

See Terminal Printer Spooler. 

v Glossary-17

Glossary 

SQL format query 

AnSQLqueryenteredinfreeformatinLINCAdHocInquiry.Contrast with menu format 

query. 

Standard Component 

A Component type that requires a single Ordinate. See also Component. 

Standard Report 

A specific type of Report that uses the LINC Report Output Control System, and whose 

output is written to the database. Subsequent use of the output is determined by the user. 

See Report Output Control System. Contrast with Direct Report. 

station 

structure 

(1) General term in LINC for method used to identify users. (2) For UNIX LINC Systems, 

station equates to user name, while for OS 2200 based LINC Systems, station equates to 

userid. 

(1) In LINC Generate, part of a LINC Specification that can be selected (for example, for 

printing, copying, or extraction). (2) For LINC Ad Hoc Inquiry, part of a LINC Database 

that can be the subject of a query. 

structure list 

For LINC Ad Hoc Inquiry, the part of a query that defines the structures to be included. 

One of the following: 

$ Component 

$ Event Profile 

$ All Events 

Supervisor 

A facility of LINC Generate enabling administration-level functions. 

System Data item 

(1) Data item that is automatically part of your LINC Specification. (2) Used for accessing 

or setting parameter or control-type data in LINC logic. (3) Some System Data Items are 

stored automatically in your LINC Database (for example, MAINT). 

Glossary-18 v

T 

table 

Glossary 

For LINC Ad Hoc Inquiry, an SQL term equivalent to a Component, the Event file, or an 

Event Profile. Also called relation name. 

Table Component 

A Component type that is used to store low-volume, frequently accessed data, such as code 

tables. See also Component. 

Tablespace 

Discrete part of an ORACLE SID or Griffin Universe. Tablespaces in the same ORACLE 

SID or Griffin Universe can be stored on different physical devices. 

Teach Screen 

A user-written screen display of information about an Ispec being used within a LINC 

System, intended to provide online help for users at run time. 

Terminal Printer Spooler (TPS) 

An MCP based LINC Utility that enables users to manipulate the output of a LINC Report 

to terminal printers. 

TPS 

Trace 

See Terminal Printer Spooler. 

(1) A facility to monitor the logic of an Ispec or Report in your LINC System. (2) Enabled in 

LINC Generate. (3) Contrast with LINC Interactive Test Environment. 

Translation Screen 

A copy of an Ispec screen that is modified to create a secondary language version. 

U 

Update program 

A generated program that contains the necessary logic for performing Ispec operations in a 

MCP based LINC System. 

Usage Input 

An Ispec attribute that enables a data item to be entered or displayed on the screen, 

accessed by logic, but not stored in the database. 

Usage Input Ispec 

An Event or Memo Component that is not output to the database, and where Data items 

default to Usage Input. (Individual data items can be set to Usage Inquiry.) 

v Glossary-19

Glossary 

Usage Input-Output 

An Ispec attribute that enables a data item to be entered or displayed on the screen, 

accessed by logic, and stored in the database. 

Usage Input-Output Ispec 

Ispec that is both Usage Input and Usage Output. 

Usage Inquiry 

An Ispec attribute that enables a data item displayed on the screen, but not to be entered 

on the screen, nor written to the database. 

Usage Output 

An Ispec attribute that enables a data item to be written to the database and accessed by 

logic, but not entered or displayed on the screen. 

Usage Output Ispec 

An Ispec that is written to the database, but does not have a screen display. 

V 

Validation EIF 

Validation EIFs are a special type of EIF which provide support for newly validated 

versions of LINC support software such as ORACLE, Griffin, COBOL, and Tuxedo. 

value expression 

For LINC Ad Hoc Inquiry, a logical expression used in an SQL format query to define a 

value, and made up of data items, literals, operators, and functions. 

value logic 

Logic associated with a Dictionary item that determines acceptable values for that item. 

version control 

A method for identifying different versions of a LINC System by version number, 

description, and generation date. 

Glossary-20 v

Index 

A 

ABORT; logic command, 1-6 

ACCEPT; logic command, 1-9, 1-206, 1-207, 

1-208 

ACCESS.EXT; logic command, 1-11, 2-25, 2-27 

accounting month, 2-9 

ACTMTH System Data item, 1-33, 2-9 

ADD; logic command, 1-15 

ADHOC.MODE; logic command, 1-16 

Ad Hoc Inquiry 

accessing from logic, 1-16 

ADVANCE; logic command, 1-17 

AE; logic command, 1-29 

AEXT; logic command, 1-11 

ALL; command option 

SEND.MESSAGE; command, 1-213 

SET.DB; command, 1-226, 1-227 

application group 

OS 2200 based, 2-11 

application number 

OS 2200 based, 2-11 

arithmetic operations 

addition, 1-15 

COMPUTE; or COMPUTE.FROM; 

command, 1-66 

division, 1-109 

logic commands for, 1-65 

multiplication, 1-186 

subtraction, 1-247 

arithmetic overflow 

DIVIDE; command, 1-109 

GLB.STATUS set by, 2-55 

MULTIPLY; command, 1-186 

testing for, 1-65 

arrays 

Automatic Entries including, 1-23 

clearing, 1-64 

invalid subscripts in, 2-55 

moving, 1-177, 1-179 

writing to database, 1-133 

AS; command option 

PRINT.FRAME; command, 1-196 

ASCENDING; command option 

MATCH; logic command, 1-165 

SORT; command, 1-239 

Assembler programs or procedures 

calling OS 2200, 1-51 

AT; command option 

PRINT.FRAME; command, 1-196 

SEND.PRINT; command, 1-216 

ATS; logic command, 1-19 

ATTACH; logic command, 1-19 

AUTO.ARRAY; logic command, 1-23 

AUTO.ENTRY; logic command, 1-29 

AUTO.FORMAT; logic command, 1-32 

AUTO; CLEAR logic command, 1-28 

AUTO; CONTRA logic command, 1-27 

AUTO; logic command, 1-23 

AUTO; WRITE logic command, 1-33 

Automaint Profiles, 1-90, 1-96, 1-98, 1-100, 

1-103, 1-105 

Automatic Entries 

buffer format for, 1-29 

clearing buffer for, 1-28, 1-34 

data in buffer for, 1-23, 1-179 

GLB.ERROR setting by, 2-24 

identifying origin of, 2-39 

naming Ispec receiving, 1-29 

OLTP response to, 1-32 

B 

BACK; command option 

LOOK.UP; GROUP command, 1-161 

banner pages 

Report output including, 2-44 

base year, 2-14 

BEGIN.CASE; logic command, 1-61 

BEGIN.EDIT; logic command, 1-44 

BEGIN.LOOP; logic command, 1-46 

BEGIN.PAGE; logic command, 1-48 

BG; logic command, 1-46 

BK; logic command, 1-50 

BP; logic command, 1-48 

v Index-1

Index 

branching 

logic commands for, 1-142, 1-146 

BREAK; logic command, 1-50, 1-224 

broadcast messages 

sending screen Status line, 1-213 

BYE; command option 

RECALL; (BYE)., 1-199 

SWITCH.TO; command, 1-252 

BYFUNCTION option 

CALL; command, 1-57 

MCP based CALL; command, 1-57 

BYFUNCTION variant 

MCP based CALL; command, 1-51, 1-52 

C 

CALL; logic command, 1-51, 2-42 

in LDA, 1-56 

CASE; logic command, 1-61 

case statements, 1-61, 1-63 

CCS ID 

OS 2200 based, 2-14 

CF; logic command, 1-65 

Change Control Options screen, 2-51 

channels 

Report output stationery, 1-17 

character sets 

OS 2200 coded, 2-14 

chargecodes 

RUN; and START; command, 2-15 

CLA; logic command, 1-64 

CLEAR.ARRAY; logic command, 1-64 

CLEAR.WHEN; Data Attribute, 1-23, 1-29 

CLEAR; command option 


closed cycle 

External Automatic Entries forming, 1-42 

CN; logic command, 1-68 

COBOL programs or procedures 

calling, 1-51 

Coded Character Set (CCS) identifier 

OS 2200, 2-14 

common user libraries 

accessing MCP based LINC Systems, 1-57 

COMP; logic command, 1-65 

complex MOVE; command, 1-173 

Components 

MAINT value for, 2-72 

recalling, 2-74 

specifying Automatic Entry, 1-29 

transaction numbers for, 2-78 

COMPOUND (C, SN.P) action 

DISCOUNT.CASH; command, A-2 

COMPUTE.FROM; logic command, 1-65 

COMPUTE; logic command, 1-65 

conditions 

compound, 1-111 

DO.WHEN; command, 1-111 

CONTRA; logic command, 1-68 

control breaks 

Report output, 1-187 

Copy.From Ispecs 

accessing Profiles in, 1-224 

editing and validation of, 1-44 

example of, 1-44 

GLB.INPUTDATA value in, 2-33 

MAX.COPIES option for, 2-37 

value of GLB.COPY in, 2-16 

Coroutines 

with CALL; command, 1-58 

generating, 1-58 

restrictions on, 1-58 

with SLEEP; UNTIL WOKEN command, 

1-234 

CP; logic command, 1-69 

CRITICAL.POINT; logic command, 1-69, 1-202, 

1-203, 1-211, 1-218, 1-235, 1-257 

CU; logic command, 1-74 

current date 

accessing, 2-17 

cursor 

positioning Ispec screen, 1-74 

CURSOR; logic command, 1-74 

D 

DATA; command option 


database 

adding records to, 2-73 

changing records in, 2-74 

DETERMINE; command accessing, 1-86 

logically deleting records in, 2-74 

modifying data in, 1-130 

name of current, 2-52, 2-53 

OS 2200 based Fast load into, 1-151 

purging records from, 2-74 

reading records from, 1-153 

recalling records from, 2-74 

retrieving records from, 2-75, 2-76 

Index-2 v

setting OS 2200 environment target, 1-226 

type, 2-18 

database records 

deadlocks when accessing, 1-120 

restricting access to, 1-120 

source of input for, 2-54 

OF data item qualification 

Report Frame data, 1-3 

data items 

changing sign of numeric, 1-68 

in commands, 1-3 

data manipulation 

MOVE; command for, 1-172, 1-173 

date 

converting formats of, 1-75, 2-14, 2-15 

DATE.CONVERT; formats for, 1-79 

GLB.DC- System Data items giving, 2-18 

Ispec transaction initiation, 2-76 

Report start/restart, 2-76 

retrieving current, 1-183 

transaction initiation, 2-71 

DATE.CONVERT; logic command, 1-75, 2-14, 

2-15, 2-18 

DC; logic command, 1-75 

DCF; logic command, 1-107 

deadlocks 

database record, 1-120 

DELIMITER; command option 

DETACH; command, 1-84 

DESCENDING; command option 


SORT; command, 1-239 

destination database 

External Automatic Entry, 2-21 

destination host 


destination LINC Environment 

OS 2200 based External Automatic Entry, 

2-20 

destination TIP Tran no 

OS 2200 External Automatic Entry, 2-21 

DETACH; logic command, 1-83 

detecting deadlock errors, 2-23 

DETERMINE; ACTUAL logic command, 1-90, 

1-203, 1-232 

DETERMINE; BACK logic command, 1-95 

DETERMINE; commands 

duplicate records, 1-88, 1-95 

END command with, 1-87 

KEYONLY; command option in, 1-144 

line breaks in, 1-88 

Index 

logically deleted records, 1-87 

MULTI; command option in, 1-185 

MULTI command option in, 1-185 

nested, 1-87 

overview of, 1-86 

SECURE; command option in, 1-211 

SERIAL; command option in, 1-224 

SET.DB; commands in loop of, 1-226 

variants of, 1-86 

DETERMINE; EVERY logic command, 1-96 

DETERMINE; FROM logic command, 1-98 

DETERMINE; GROUP logic command, 1-100 

DETERMINE; LAST logic command, 1-103 

DETERMINE; TOTAL logic command, 1-105 

AT device type 

RUN; command, 1-206 

device types 


RUN; command specifying output, 1-206, 

1-209 

SEND.PRINT; command specifying, 1-215 

DISCOUNT (D, P.SN) action 


DISCOUNT.CASH; logic command, 1-107, A-1 

DIVIDE; logic command, 1-109 

dllmgr.dll library 

LDA CALL; command, 1-55 

DMS II database 

inquiring in an MCP environment, 1-11 

DO.WHEN; logic command, 1-111, 2-57 

DTH; logic command, 1-83 

duplicate records 

DETERMINE; commands accessing, 1-88, 

1-95 

DV; logic command, 1-109 

DW; logic command, 1-111 

dynamic list boxes, 1-217 

E 

EAS; command option 

DETERMINE; ACTUAL command, 1-92 


ECL runstream 

START; command initiating OS 2200 

environment, 1-241, 1-242 

EDIT.ONLY; command option 

DATE.CONVERT; command, 1-78 

editing and validation logic 

Copy.From Ispec, 1-44 

v Index-3

Index 

EE; logic command, 1-117 

ELSE; logic command, 1-114 

END.AFTER; option 

SLEEP; command, 1-234, 2-16 

END.CASE; logic command, 1-61 

END.EDIT; logic command, 1-44 

END.EXIT; logic command, 1-117 

END.NO.PRINT; logic command, 1-118, 1-196 

END.USE; logic command, 1-119 

END; logic command, 1-87, 1-116 

end values 

DETERMINE; GROUP command, 1-100 


ENP; logic command, 1-118 

errors 

internal Automatic Entry, 2-24 

Ispec update prevented by, 2-24 

EU; logic command, 1-119 

Events 


transaction numbers for, 2-78 

EX; logic command, 1-121 

EXCLUSIVE.USE; logic command, 1-120, 1-211 

EXIST; command option 

SET.TITLE; command, 1-230, 1-232, 1-237 

EXIT command option 

RECALL; command, 1-199 

External-only Ispecs, 1-29 


AUTO; WRITE commands effecting, 1-34 

closed cycles of, 1-42 

destination for, 2-20, 2-21 

GLB.HUBSTATUS values for, 1-37 

GLB.STATUS values for, 1-37 

Griffin Universe for UNIX, 2-53 

identifier for terminal originating, 2-57 

identifying origin of, 2-39, 2-40 

initiating, 1-33 

interfacing to non-LINC systems with, 1-29 

LINC environment for OS 2200, 2-53 

NOF, 2-21 

ORACLE SID for UNIX, 2-53 

RECALL; command invoked by, 1-179 

restrictions on, 1-23 

results of, 2-31 

retrieving data from, 1-179 

setting timeout for, 2-31 

EXTERNAL command option 

AUTO.ENTRY logic command, 1-30 

external database 


accessing MCP environments, 1-11 

EXTERNAL option 

UNIX CALL; command, 1-54 

external routines or programs 

calling, 1-51 

EXTRACT; logic command, 1-121 

EXTRACTED.AS; command option 

DETERMINE; ACTUAL command, 1-92, 

1-232 

MATCH; command, 1-165 

Extract files 

categories of, 1-90, 1-124, 1-230, 1-237 

closing and purging, 1-203 

designator for, 1-4, 1-90, 1-92, 1-231 

DETERMINE commands accessing, 1-90, 

1-92 

dynamically renaming, 1-230 

end-of-job handling, 1-125 

existing, 1-124 

host type differences in, 1-124 

MAPPER, 1-121, 1-123, 1-237 

multiple EXTRACT; commands to same, 

1-123 

notes for using, 1-121 

permanent, 1-124 

restarting, 1-203 

runtime processing of, 1-90, 1-125, 1-230, 

1-237 

setting start record for, 2-48 

sorting, 1-237 

tape, 1-232 

temporary, 1-125 

using MATCH; to compare, 1-164, 2-37 

writing records to, 1-121 

EXU; logic command, 1-120 

F 

Fast load 

OS 2200 based database, 1-151 

FG; logic command, 1-130 

financial analysis 

formulas for, A-1 

logic commands for, 1-107 

FIND statement 

ACCESS.EXT; command, 1-11 

Fireup Ispec 

displaying, 1-199 

FL; logic command, 1-130 

FLA; logic command, 1-133 

Index-4 v

FLAG.ARRAY; logic command, 1-133 

FLAG; logic command, 1-130, 2-24 

FLOW.FV (A*.SN) action 


FLOW.PV (A*.P) action 


FOOTING; command option 

ON.CHANGE; command, 1-188 

FORMAT option 

DATE.CONVERT; command, 1-78, 2-15, 2-18 

formulas 


Frames 

executing logic for, 1-196 

extracting Report, 1-122 

printing, 1-196 

Report output footer, 1-187 

Report output heading, 1-48, 1-187 

terminating Report, 1-118 

FROM; command option 


FT command option 


function keys 

current Ispec when pressing, 2-43 

OS 2200, 2-40 

value of OS 2200, 2-9 

FV.ANNUITY (SN.A) action 


FV.FLOW (SN.A*) action 


G 

GET.LENGTH; logic command, 1-135, 2-30 

GET statement 

ACCESS.EXT; command, 1-12 

GIVING; command option 



SUBTRACT; command, 1-247 

GLB.2PC, 2-71 

GLB.ACTIONKEY, 2-9 

GLB.ADD, 2-10, 2-73 

GLB.ALTUSER, 2-10 

GLB.APPNAME, 1-226, 2-11 

GLB.APPNO, 1-226, 2-11 

GLB.ASCPRT, 2-11 

GLB.ASCPRTHOST, 2-12 

GLB.BACKUP, 2-12 

Index 

GLB.BALANCE, 2-13 

GLB.BASE, 1-76, 2-14 

GLB.CCS, 2-14 

GLB.CENTURY, 1-76, 2-14 

GLB.CENTURY-START, 1-76, 2-15 

GLB.CHANGE, 1-187, 2-15 

GLB.CHARGECODE, 1-206, 1-242, 2-15 

GLB.CHG, 2-16, 2-74 

GLB.CLOSE, 1-234, 2-16 

GLB.COPY, 1-224, 2-16 

GLB.DATE, 2-17 

GLB.DBTYPE, 2-18 

GLB.DC- System Data items, 1-75, 2-18 

GLB.DEL, 2-20, 2-74 

GLB.DESTENV, 1-30, 2-20 

GLB.DESTHOST, 1-30, 1-35, 1-39, 2-20 

GLB.DESTINATION, 1-35, 1-39, 2-21 

GLB.DESTNOFORM, 2-21 

GLB.DEVICE, 1-196, 1-202, 2-22, 2-29 

GLB.DLRECOVER, 2-23 

GLB.EOP option 

CURSOR; command, 2-24 

GLB.ERROR 

AUTO; WRITE command affected by, 1-33, 

1-34 

details of, 2-24 

MESSAGE; command setting, 1-168 

RECALL; command setting, 1-200 

Repeat.From Ispecs and, 2-13 

SWITCH.TO; command setting, 1-248 

GLB.EXAMKEY, 2-25 

GLB.EXNAME, 2-25 

GLB.EXTDB, 1-226, 2-25 

GLB.EXTDBSTATUS, 1-226, 2-26 

GLB.EXTEXT, 2-27 

GLB.FILEINFO, 2-27 

GLB.FILLER 

reserving space in report frames, 2-27 

specifying attributes with SAME.AS, 2-27 

GLB.FORMDEPTH, 1-48, 1-196, 2-28 

GLB.FORMID, 2-29 

GLB.FULLLENGTH, 1-135, 2-30 

GLB.FULLSTN, 2-30 

GLB.GUI 

terminal types, 2-30 

GLB.HIGH, 1-3, 1-175, 2-31 

GLB.HTIMEOUT, 2-31 

GLB.HUBSTATUS, 1-35, 1-37, 2-31 

GLB.HUBTIMEOUT, 1-40, 2-31 

GLB.INITFULLSTN, 2-32 

GLB.INITSTN, 1-213, 2-32 

v Index-5

Index 

GLB.INPUTDATA, 2-33 

GLB.INQ, 2-33, 2-76 

GLB.LANGUAGE, 2-33 

GLB.LENGTH, 1-83, 1-135, 2-30, 2-34 

GLB.LINECOUNT, 2-34 

GLB.LINEUP, 2-35 

GLB.LINEUPNAME, 2-36 

GLB.LOW, 1-3, 1-54, 1-175, 2-36 

GLB.MATCH, 1-164, 1-166, 2-37 

GLB.MAXCOPY, 2-37 

GLB.MIXNO, 2-37 

GLB.NUMCOPIES, 2-37 

GLB.OLTPSERVICE, 2-38 

GLB.OLTPSUBTYPE, 1-29, 1-35, 2-38 

GLB.OLTPTYPE, 1-29, 1-35, 2-38 

GLB.OLTPVALUE, 2-39 

GLB.ORIGIN, 2-39 

GLB.ORIGINENV, 2-39 

GLB.ORIGINHOST, 2-40 

GLB.ORIGINISPEC, 1-251, 1-253, 2-40 

GLB.ORIGINPTN, 1-251, 1-253, 2-41 

GLB.ORIGINXNID, 1-251, 1-253, 2-41 

GLB.PAGECOUNT, 1-202, 2-41 

GLB.PARAM, 1-51, 1-54, 1-55, 2-42 

GLB.PARAMFLAG, 1-257, 2-42 

GLB.PITCH, 2-43 

GLB.PREVISPEC, 2-43 

GLB.PRINTAT, 2-43 

GLB.PRINTBANNER, 2-44 

GLB.PRINTHOST, 1-196, 1-202, 2-44 

GLB.PRIORITY, 2-45 

GLB.PRIV, 2-46 

GLB.PRODUCT, 2-47 

GLB.PRTPARAM, 2-48 

GLB.PUR, 2-48, 2-74 

GLB.RECORDx, 2-48 

GLB.RECOVER, 2-49 

GLB.REPGENDATE, 2-49 

GLB.REPGENTIME, 2-49 

GLB.REPLANG, 2-49 

GLB.REPNAME, 2-50 

GLB.REPORT, 2-50 

GLB.REPUNIQUE, 2-50 

GLB.REPVERSION, 2-51 

GLB.REQUEST, 2-51 

GLB.ROCFLAG, 2-51 

GLB.SAVEDAYS, 2-27, 2-51 

GLB.SECONDARY, 2-52 

GLB.SELF, 1-30, 2-52 

GLB.SELFDB, 2-53 

GLB.SELFENV, 1-30, 2-53 

GLB.SELFHOST, 1-30, 2-53 

GLB.SELFXNID, 2-54 

GLB.SHADOW, 2-54 

GLB.SOURCE, 2-54 

GLB.SPACES, 1-3, 1-175, 2-54 

GLB.STALANG, 2-55 

GLB.STATION, 2-57 

GLB.STATUS; command option 


COMPUTE; commands, 1-65 

DATE.CONVERT; command, 1-77, 1-81 

definition of, 1-137 

DETERMINE; commands with, 1-87 

DISCOUNT.CASH; command, 1-107 


instead of GLB.STATUS System Data item, 

1-1, 1-4, 2-56 

logic commands with, 1-137 

LOOK.UP; command, 1-154 



GLB.STATUS System Data item 

AUTO; WRITE setting, 1-37 

complex MOVE; setting, 1-174 

DATE.CONVERT; setting, 1-77 


DETERMINE; setting, 1-87 

DISCOUNT.CASH; setting, 1-107 

MATCH; setting, 1-164 

nested DO.WHENs overwriting, 1-112, 2-57 

RUN; setting, 1-207 

SEND.PRINT; command setting, 1-215 

situations initializing, 2-56 

situations setting, 2-55 

START; setting, 1-241, 1-242, 1-243 

STN.INFO; setting, 1-245, 1-246 

using GLB.STATUS; command instead of, 

1-1, 1-4, 1-137 

WAKE.UP; setting, 1-257 

GLB.STN, 1-196, 1-202, 1-206, 1-207, 1-213, 

1-218, 2-57 

GLB.STNHOST, 2-59 

GLB.STYLE, 2-59 

GLB.SUBSYS, 2-60 

GLB.SYSGENDATE, 2-61 

GLB.SYSGENTIME, 2-61 

GLB.SYSVERSION, 2-62 

GLB.TASK, 2-62 

GLB.TIME, 2-64 

GLB.TITLE, 2-27, 2-64 

GLB.TODAY, 2-76 

Index-6 v

GLB.TODAYS-DATE-NUM, 2-76 

GLB.TODAYS-DAY, 2-77 

GLB.TODAYS-MONTH, 2-77 

GLB.TODAYS-MONTH-NUM, 2-77 

GLB.TODAYS-YEAR, 2-78 

GLB.TOTAL, 1-75, 1-105, 2-67 

GLB.TRANSTATE, 2-68 

GLB.UNIQUE, 2-68 

GLB.USER, 1-196, 2-68 

GLB.USERCODE, 2-69 

GLB.VERSIONID, 2-69 

GLB.WORK 


effects of ABORT; command on, 1-6 

GLB.YYMMDD, 2-70 

GLB.ZEROS, 1-3, 1-175, 2-70 

Global Logics 

insertable, 1-141 

Global Setup Data arrays 


moving, 1-177, 1-179 


Global Setup Data items 


Global Work area, 1-6, 2-70 

Griffin Universe 

UNIX External Automatic Entry, 2-20, 2-53 

Group Setup Data 

moving, 1-172 

GS; command (see GLB.STATUS; command), 

1-137 

GS; command option 


H 

HEADING; command option 

ON.CHANGE; command, 1-188 

heading Frames 


high-order values 


host name 

current, 2-53 

External Automatic Entry destination, 2-21 

I 

Index 

Immediate Commit 

Automatic Entry, 1-38 

INHERIT; option 

SWITCH.TO; command, 1-248, 1-253, 2-40, 

2-41 

INIT; logic command, 1-139 

INITIALIZE; logic command, 1-139 

INPUT-DATE System Data item, 1-33, 2-71 

INS; logic command, 1-141 

INSERT; logic command, 1-141 

interdatabase access 


OS 2200 based, 1-226, 2-11, 2-25, 2-26 

internal Automatic Entries 



initiating, 1-33 

INTERNAL option 

UNIX CALL; command, 1-53 

Ispecs 

aborting runtime logic in, 1-6 

accessing ROC from, 1-205 

automatic updating, 2-24 

Copy.From, 1-44, 1-224, 2-16, 2-37 

External-only, 1-29 

Extract file data from, 1-122 

GLB.ERROR effects on, 2-24 

initiating Reports from, 1-206 

No.Integrity, 1-211 

NOF-initiated, 1-217 

OLTP View, 1-29, 1-35 

originator of current transaction for, 2-30, 

2-57 

OS 2200 based interdatabase, 1-226, 2-25 

page 2 format request, 2-51 

PowerClient-initiated, 1-217 

privilege of, 2-46 

RECALL; command displaying, 1-199 

recalling, 2-74 

Repeat.From, 2-13, 2-72 

screen header line for, 2-2, 2-72 


transaction numbers for, 2-68, 2-78 

transferring information between, 2-70 

ISPEC System Data item, 1-33, 2-72 

v Index-7

Index 

J 

JTO; logic command, 1-142, 1-146 

JUMP.TO; logic command, 1-142, 1-146 

K 

KEY; command 

MATCH; logic command, 1-164, 1-166 

key data 

MCP environment Profile, 1-144 

KEYONLY; command option 

DETERMINE; command, 1-144 


L 

LA; logic command, 1-147 

LAB; logic command, 1-146 

LABEL; logic command, 1-142, 1-146 

language 

current LINC System, 2-55 

LAST-LINE System Data item, 2-13, 2-72 

LDA 

GLB.MACHINE, 2-36 

LDA CALL; command 

dllmgr.dll library, 1-55 

LEFT.ALIGN; logic command, 1-147 

LENGTH; command option 


library procedures 

calling MCP based LINC Systems, 1-51 

LINC/NET file 

MCP based, 2-11, 2-12, 2-46 

LINCIINET file 

UNIX, 1-245, 2-11, 2-47 

LINCNOF file 

UNIX, 1-250 

LISTBOX* Data Attribute, 1-218 

LISTBOX Data Attribute, 1-218 

list boxes 

dynamic, 1-217 

sending PowerClient, 1-217, 1-221 

LOAD; logic command, 1-151 

LoadAndStick() function 


locking 

database record, 1-120, 1-211 

logic 

aborting Ispec, 1-6 

aborting Report, 1-7 

AND logical connector 

DO.WHEN; commands, 1-111 

logical connectors 

AND and OR, 1-111 

logically deleted records, 1-87, 1-154, 2-74 

logic commands 

overview of LINC, 1-1 

logic loops 

breaking out of , 1-142, 1-146 

terminating, 1-142, 1-146 

LOOK.UP; commands 

EVERY logic command, 1-158 

GLB.STATUS; command option with, 1-154 

GLB.STATUS setting by, 1-153, 1-154 

GROUP logic command, 1-161 

GS; command option with, 1-154 

KEYONLY; command option in, 1-144 

in LDA, 1-154 

logically deleted records and, 1-154 

FROM logic command, 1-160 

LOOK.UP; logic command, 1-156 

loops created by, 1-153 

MULTI; command option in, 1-185 

SECURE; command option in, 1-211 

SERIAL; command option in, 1-224 

SET.DB; commands within loop for, 1-226 

variants of, 1-153 

loops 

breaking out of logic, 1-142, 1-146 

creating logic, 1-46 

DO.WHEN; conditions creating, 1-111 

ending logic, 1-50, 1-116, 1-117, 1-118 

Global Logic including, 1-50 

MATCH; command, 1-164 

railroad diagram syntax, B-2 

terminating logic, 1-142, 1-146 

LOWER.CASE logic command, 1-163 

LSM Security screen, 1-199 

LU; logic command, 1-153 

M 

MA; logic command, 1-179 

MAA; logic command, 1-179 

MAINT System Data item, 1-23, 1-34, 1-198, 

2-72 

MAPPER 

Extract files for, 1-121, 1-123, 1-237 

Index-8 v

MAPPER; command option 

EXTRACT command, 1-126 

MATCH; logic command, 1-164, 2-37 

MD; logic command, 1-183 

ME; logic command, 1-168 

Memo Components 

Multiple Ordinate, 1-96, 1-98, 1-100, 1-103, 

1-105 

MESSAGE; logic command, 1-168, 1-199, 1-206, 

1-207, 1-208, 2-25 

messages 

sending screen Status line, 1-213 

mix number 

runtime Report, 2-37 

MORTGAGE (M, A.P) action 


MOVE.ARRAY; logic command, 1-177 

MOVE.AUTO.ARRAY; logic command, 1-179 

MOVE.AUTO; logic command, 1-179 

MOVE.DATE; logic command, 1-183 

MOVE.TIME; logic command, 1-184 

MOVE; logic command, 1-172 

MP; command option 


MT; logic command, 1-184 

MU; logic command, 1-186 

MULTI; command option 


DETERMINE; commands, 1-185 


multilanguage Systems, 2-33 

multiple record buffer 

RDMS, 1-185 

MULTIPLY; logic command, 1-186 

MV; logic command, 1-172 

MVA; logic command, 1-177 

N 

nesting DO.WHEN; commands, 1-111, 1-114 

NO.RELEASE option 

CRITICAL.POINT; logic command, 1-72 

node name 

UNIX External Automatic Entry 

destination, 2-21 

NOF program 

COMS program name for an MCP based 

LINC System, 2-22 

External Automatic Entries to, 2-21 

name for OS 2200, 2-22 

Index 

sending list boxes to, 1-217 

shell script initiating UNIX, 2-22 

NOF terminal 

sending list boxes to, 1-217 

Non-Formatted output interface (see NOF), 

2-21 

non-Integrity Systems 

record locking in, 1-211 

non-LINC systems 


interfacing to, 1-29 

switching to, 1-248 

non-ROC Reports 

GLB.TITLE in, 2-64 

output from MCP based LINC Systems, 

1-196 

RELEASE; command effects, 1-202 

System Data items invalid in, 2-1 

NOT.ENTERED Data attribute, 2-9 

NOT relational operator 


NR command option 

CRITICAL.POINT; logic command, 1-72 

numeric data items 

changing sign of, 1-27, 1-68 

left-aligned, 1-147 

O 

OCH; logic command, 1-187 

ODT 

sending messages to MCP based LINC 

System, 1-213 

OF data item qualification 

Report Frame data, 1-1 

OLTP 

aborted transactions, 1-43 

AUTO.FORMAT; command for, 1-179 

AUTO; command for, 1-24 

GLB.HUBSTATUS values for, 1-37 


MOVE.AUTO command for, 1-179 

runtime exceptions, 1-35 

sending transactions, 1-34 

specifying Automatic Entries for, 1-32 

specifying Service required for, 1-35 

System Data Items for, 2-38 

transaction errors, 1-42 

View Ispecs for, 1-29 

v Index-9

Index 

ON.CHANGE; logic command, 1-187, 1-202, 

2-15 

ON; command option 

SET.TITLE; command, 1-232 

Operator Display Terminal 

sending messages to MCP based LINC 

System, 1-213 

ORACLE SID 

UNIX External Automatic Entry 


UNIX External Automatic Entry origin, 2-39, 

2-53 

Ordinates 

changing values of, 1-130 

OR logical connector 

DO.WHEN; commands, 1-111 

OTHERWISE; logic command, 1-61 

output devices 

defining Report, 1-3 

host-attached, 2-44 

overflow (see arithmetic overflow), 1-65 

P 

PA; command option 



page-level locking 

SECURE; command option causing OS 2200 

environment, 1-211 

page 2 

format request from, 2-51 

PAGE; logic command, 1-193 

page number 


PA option 

RUN; command, 1-208, 1-210 

WAKE.UP; command, 1-258 

parameters 

CALL; command, 1-51, 2-42 

passing Report, 1-208, 1-210 

WAKE.UP; command passing, 2-42 

PARTITION; command option 


PERFORM.FRAME.LOGIC logic command, 

1-195 

PF; logic command, 1-196 

PG; logic command, 1-193 

physically deleted records, 1-198, 2-74 

PID number 

runtime Report, 2-37 

pitch settings 

Terminal Printer, 2-43 

POS; command option 



POSITION; command option 



PowerClient 

sending list boxes to, 1-217, 1-221 

switching to a system running, 1-248, 1-251, 

2-41 

Pre-Screen logic 

RECALL; command ignoring, 1-200 

PRINT$ file 

sending messages to OS 2200 environment, 

1-168 

PRINT.FRAME; logic command, 1-196, 1-202, 

2-45, 2-46, 2-58 

printer 

associated, 2-11 

host controlling, 2-12 

STN.INFO; validating name of, 1-245 

print file attributes 

controlling MCP based LINC Systems, 2-27 

priority 

Ispec-initiated Report, 2-45 

privilege 

Ispec, 2-46 

Report output printer, 2-46 

product 

currently running LINC Generate 

(Deployment) software, 2-47 

Profiles 

Copy.From Ispecs accessing, 1-224 

data in MCP based LINC System, 1-144 

DETERMINE; commands using, 1-86, 1-96, 

1-98, 1-100 

duplicate records in, 1-34 

Ordinate values for, 1-5 

restarting, 1-203 

programs 

calling external, 1-51 

PU; logic command, 1-198 

PURGE; logic command, 1-198 

PV.ANNUITY (P.A) action 


PV.FLOW (P.A*) action 


Index-10 v

Q 

queuing 


R 

railroad diagram syntax, B-1 

RAS; command option 



RC; logic command, 1-199 

RDB 

Reports against Secondary database, 2-52 

RDMS 

AUTO.ENTRY applying lock, 1-29 

multiple record buffer, 1-185 

possible errors with SECURE; command 

option, 1-211 

RDMUTL utility 

OS 2200 based Fast load, 1-151 

reading ranges of 

database record, 1-185 

RECALL; logic command, 1-199, 2-25 

record-level locking 

SECURE; command option causing MCP 


recovery 

Report, 1-71, 2-49 

System Data item value, 2-3 

REL; logic command, 1-202 

relational operators 


RELEASE; logic command, 1-202, 1-215, 2-10, 

2-29, 2-38 

REMAINDER; command option 


Remote Database facility (RDB) 

MCP environment, 2-52 

Repeat.From Ispecs 

using GLB.BALANCE in, 2-13 

using LAST-LINE in, 2-72 

Report Output Control System (see ROC), 

1-196 

Reports 

aborting runtime logic in, 1-7 

activating Trace for, 1-209 

critical points in, 1-69 

heading Frames for, 1-48 

identifying initiators of, 2-32 

Index 

initiating multiple UNIX, 1-207 

inserting logic for whole, 1-141 

Ispec logic initiating, 1-206 

lines per page from, 2-28 

multilanguage, 2-49 

multiple output destinations for, 1-215 

name of, 2-50 

No.Integrity, 1-211 

number of copies of, 2-37 

output destination for, 2-58 

output devices for, 1-3 

output line count for, 2-34 

passing parameters to, 1-208, 1-210 

passing runtime information to, 1-9 

printer privilege in, 2-46 

printing output from, 2-43 

priority of, 2-45 

recovery of, 2-49 

releasing, 1-202, 2-58 

RUN; command initiating, 1-206 

running as Coroutines or subroutines in 

LDA, 1-56 

running attached OS 2200 environment, 

1-206 

running unattached MCP based LINC 

Systems, 1-206 

running unattached OS 2200 environment, 

1-206 

special stationery, 2-29, 2-35, 2-36 

suspending execution of, 1-234 

System Data items in, 2-3 

terminating, 1-118 

unique number identifying, 2-50 

reserving space in report frames 

using GLB.FILLER, 2-27 

RESTART; logic command, 1-203 

RETAIN.AS; command option 


SET.TITLE; commands clashing with, 1-230 

RETAIN.ZERO; command option 

LEFT.ALIGN; command, 1-148 

RETAINED.AS; command option 


ROC 

accessing, 1-205, 1-250 

ROC.MODE; logic command, 1-205 

ROC; logic command, 1-205 

ROC Alias 

UNIX Report, 1-245, 2-30, 2-59 

ROC Reports 

CRITICAL.POINT; versus SLEEP; in, 1-235 

v Index-11

Index 

GLB.TITLE in, 2-64, 2-65 

PRINT.FRAME; command with, 1-196 

RELEASE; command effects, 1-202 

retaining output for, 2-51 

ROC set or not, 2-51 

special stationery, 2-29 

user names for, 2-68 

video output, 1-196 

ROUNDED; command option 

ADD; command, 1-15 




routines 

calling, 1-51 

row-level locking 

SECURE; command option causing UNIX, 

1-212 

RT; logic command, 1-203 

RUN; logic command, 1-206, 2-15, 2-45 

run condition words 

setting of, 2-63 

RZ; command option 

LEFT.ALIGN; command, 1-148 

S 

SB; logic command, 1-247 

screen pages 

sending data to MCP based LINC System, 

1-193 

screens 

header line on Ispec, 2-2, 2-72 

positioning cursor on Ispec, 1-74 


refreshing display of, 1-200 

sending messages to, 1-168, 1-213 

secondary database 

MCP based Reports running against, 2-52 

SECURE; command option 




SEND.MESSAGE; logic command, 1-213 

SEND.PRINT; logic command, 1-215 

SEND.STATUS; logic command, 1-213 

SEND; logic command, 1-215 

SENDLIST.DYNAMIC; logic command, 1-217 

SENDLIST.STATIC; logic command, 1-221 

SERIAL; command option 


SERIAL option 


Service 

specifying OLTP, 1-35 

SET.DB; logic command, 1-226, 2-53 

SET.TITLE; logic command, 1-230 

SETT; logic command, 1-230 

Setup Data arrays 


moving, 1-177, 1-179 


Setup Data items 


Shadow Reports 

designator for, 1-3, 1-5 

identifying running, 2-54 

passing data from OS 2200, 2-48 

PRINT.FRAME; command specifying, 1-196 

shell 

calling UNIX, 1-51 

shell script 

START; command initiating UNIX, 1-241, 

1-243 

SI; logic command, 1-245 

SINK (A.SN) action 


SLDYN; logic command, 1-217 

SLEEP; logic command, 1-202, 1-211, 1-218, 

1-234, 1-257, 2-16 

SLEEP command option 

CRITICAL.POINT logic command, 1-71 

SLP; logic command, 1-234 

SLSTA; logic command, 1-221 

SM; logic command, 1-213 

SMSG; logic command, 1-213 

SO; logic command, 1-237 

software product 

currently running LINC, 2-47 

SORT; logic command, 1-232, 1-237 

sorting 


SP; logic command, 1-215 

SS; logic command, 1-213 

ST; logic command, 1-241 

START; logic command, 1-241, 2-15 

start values 



station 

MCP based, 2-57 

Index-12 v

eference station, 2-57 

stationery 

special Report, 2-29, 2-35, 2-36 

station name 

STN.INFO; command validating, 1-245 

statistical routines, 1-189 

Status line messages 

sending screen, 1-213 

STN.INFO; logic command, 1-245 

subroutines 

calling, 1-51 

subscripts 

array, 2-55 

Subsystems 

current MCP based, 2-60 

SUBTRACT; logic command, 1-247 

SWITCH.TO; logic command, 1-199, 1-248, 

2-40, 2-41 

SWT; logic command, 1-248 

symbiont queue 

OS 2200 based line printer Report, 2-59 

SYNCWAIT option 

MCP based DMS II, 1-40 

syntax diagrams 

conventions for, B-1 

System Data items 


invalid non-ROC Report, 2-1 

Ispec screen header, 2-2 

OLTP, 2-38 

overview of, 2-1 

recovery of, 2-3 

System libraries 


declaring MCP based LINC Systems, 1-57 

system time 

GLB.TIME giving, 2-64 

T 

TASKVALUE attribute 

setting MCP environment, 2-62 

TEACH; command option 

RECALL; command, 1-199 

Teach screens 


terminal printers 

saving output to an MCP based LINC 

System, 2-12 

Terminal Printer Spooler (TPS), 2-10 

Index 

terminal type 

finding the originating, 2-59 

time 

retrieving current, 1-184 

TIP Tran no 

OS 2200 External Automatic Entry 


TO.ALPHA command option 


TO.DATE command option 


TO.DAYNUMBER command option 


TODAYS-DATE-NUM System Data item, 2-76 

TODAYS-DAY System Data item, 2-77 

TODAYS-MONTH-NUM System Data item, 2-77 

TODAYS-MONTH System Data item, 2-77 

TODAYS-YEAR System Data item, 2-78 

TODAY System Data item, 2-76 

TPS 

MCP based Reports using, 2-10 

TR; logic command, 1-255 

TRACE; logic command, 1-255 

Trace function 

Reports, 1-209 

TRACE option 


tran id 

OS 2200 based LINC System, 2-41, 2-52, 2-54 

TRANNO System Data item, 2-78 

transaction numbers, 2-78 

transaction state 

MCP based runtime Report, 2-68 

translation 

MAINT System Data item, 2-73 

TR option 


truncation 


Two-Phase commit 

default setting for, 2-71 

External Automatic Entries, 1-40 

OLTP transactions with, 1-35 

U 

unique number 

Ispec transaction, 2-68 

running Report, 2-50 

UNIX 

v Index-13

Index 

database type, 2-18 

UNIX shell 

calling, 1-51 

UnstickAndFree() function 


UNTIL; command option 


SLEEP; command, 1-234 

Update program 

current MCP based, 2-60 

UPPER.CASE logic command, 1-256 

usercode 

current MCP environment sign-on, 2-69 

user id 

current OS 2200 sign-on, 2-69 

UNIX, 2-57 

USER interface program 


user libraries 


usernames 

current UNIX sign-on, 2-69 

MCP based TPS Report, 2-10 

obtaining information about UNIX, 1-245 

ROC Report, 2-68 

USERPRT print handler program 

OS 2200, 2-48 

user station PID 

OS 2200, 2-57 

V 

validation 

Copy.From Ispec, 1-44 

version identification 

description, 2-69 

generate date, 2-49, 2-61 

generate number, 2-62 

generate time, 2-49, 2-61 

Report number, 2-51 

video Reports 

initiation of, 1-206 

non-ROC MCP environment, 1-202 

W 

WAKE.UP; logic command, 1-208, 1-257 

WFL job 

accessing GLB.TASK in an MCP 


chargecodes for an MCP based LINC 

System, 2-16 

START; command initiating MCP 


WU; logic command, 1-257 

Z 

zero suppression, 1-147 

:BDD LINC System command, 2-64 

:COD LINC System command, 1-206, 2-15 

:RUN LINC System command, 1-206 

:SLA LINC System command, 2-55 

:STO LINC System command, 2-16 

Index-14 v

Tape 

Fold Here 

Airmail 

Unisys Australia Pty Ltd 

115-117 Wicks Rd 

North Ryde, NSW 2113 

Australia 

Cut along dashed line 

Do Not Staple 

Please Fold and Fasten 

Attention: ACUS Product Information 

Correct Airmail 

Postage Required 

Tape

Addition Deletion 

Revision Error 

Publication title 

Document number 

Comments: 

Name 

Title 

Address 

City 

Help Us To Help You 

Unisys Corporation is interested in your comments and suggestions regarding this manual. We will 

use them to improve the quality of your Product Information. Please check type of suggestion: 

Company 

Date 

Telephone number 

( ) 

State ZIP code

*-*

LINC Programming Reference Manual - Public Support Login - Unisys

Create successful ePaper yourself

Delete template?

Save as template?