UNISYS MAPPER® System

Run Design
Operations
Reference Manual
Volume 2:
Run Statements

May 1990

Printed in U S America
Priced Item 7831 9274-000
UNISYS MAPPER® System
Run Design
Operations
Reference Manual
Volume 2:
Run Statements

Copyright © 1990 Unisys Corporation

All Rights Reserved
Unisys and MAPPER are registered trademarks of Unisys Corporation

May 1990

Printed in U S America
Priced Item 7831 9274-000
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, or that of any group or association is purely coincidental and unintentional.

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THE 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 responsibility that may be the result of your use of the
information in this document or software material, including direct, indirect, special, or consequential damages.

You should be very careful to ensure that the use of this information and/or software material 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.

Correspondence regarding this publication should be forwarded using the Business Reply Mail form in this document, or remarks
may be addressed directly to Unisys Corporation, MAPPER Product Information, P.O. Box 64942 MS: 4792, St. Paul, Minnesota,
55164-0942, U.S.A.
Page Status

Page Issue

Volume 1

iii through xvi Original

Contents tab Original
xvii through xxxi Original
xxxiii through xxxiv Original
Section 1 tab Original
1-1 through 1-6 Original
Section 2 tab Original
2-1 through 2-16 Original
Section 3 tab Original
3-1 through 3-8 Original
Section 4 tab Original
4-1 through 4-44 Original
Section 5 tab Original
5-1 through 5-20 Original
Section 6 tab Original
6-1 through 6-18 Original
Appendixes tab Original
A-1 through A-21 Original
B-1 through B-8 Original
C-1 through C-4 Original
D-1 through D-15 Original
E-1 through E-9 Original
F-1 through F-3 Original
G-1 through G-2 Original

Volume 2

iii through iv Original

Contents tab Original
v through xxii Original
Section 7 tab Original

7831 9274-000 iii

 Page Issue

7-1 through 7-21 Original

A-E tab Original
7-23 through 7-119 Original
F-P tab Original
7-121 through 7-233 Original
R-Z tab Original
7-235 through 7-364 Original
Glossary tab Original
Glossary-1 through Glossary-44 Original
Index tab Original
Index-1 through Index-25 Original

iv 7831 9274-000
Contents

Volume 1: Usage

About This Manual v

Section 1. Overview of MAPPER Run Design

What Is a Run? 1-2
Why Use Runs? 1-2
Run Statements 1-3
Run Control Reports 1-3
Creating and Executing Runs 1-4
Creating a New Run 1-4
Executing a Run 1-4
Starting a Run 1-5
Stopping a Run 1-5
Handling Errors 1-5

Section 2. Formulating Run Statements

Run Statement Format 2-2
Using Multiple Statements 2-3
Example of a Run Statement 2-4
Guidelines for Formulating Run Statements 2-5
Entering Statements 2-5
Terminating Lines 2-6
Using Reserved Words in Run Statements 2-6
Examples Using Reserved Words 2-7
Using the Output Area 2-8
Using Labels in Runs 2-9
Relative Line Numbers in the Lab (Label)
Subfield 2-10
Using a Label Table 2-10
Specifying Reports to Process 2-12

7831 9274-000 v
Contents

Specifying Columns to Process 2-13

Maximum Number of Report Fields 2-13
Using Special Characters 2-14
Specifying Multiple Parameters in
Run Statements 2-14
Separating Multiple Expressions and Decisions 2-15
Using Multiple Lines for One Run Statement 2-15
Denoting Literal Data in Run Statements 2-16

Section 3. Using Data Naming

Naming Cabinets, Drawers, and Reports 3-2
Names in Variables 3-3
Naming Results 3-3
Naming Fields 3-4
Report Headings and the Heading Divider Line 3-4
Field Names 3-5
Field Order 3-6
Field Names in Variables 3-6
Naming Partial Fields 3-6
Field Size Variable Definition 3-7
Converting to Field Names 3-8
Selecting Fields to Display 3-8
Efficiency Considerations 3-8

Section 4. Variables, Reserved Words, and Constants

Some Terms You Should Know 4-2
What Is a Variable? 4-2
What Is an Array? 4-2
What Is a Reserved Word? 4-2
What Is a Constant? 4-3
Selecting a Variable Name 4-4
Named Variables 4-4
Numbered Variables 4-4
Named Vs Numbered Variables 4-5
Using Named and Numbered Variables on
OS 1100 MAPPER Systems 4-5

vi 7831 9274-000
 Contents

Assigning Names to Numbered Variables 4-5

Converting Named Variables to Numbered
Variables 4-5
Understanding Variable Types and Sizes 4-6
Default Justification of Variables 4-8
No Type Verification 4-8
Selecting a Variable Type and Size 4-9
Determine the Size 4-9
Defining and Initializing Variables 4-10
Methods for Defining a Variable 4-10
Using the LDV Statement 4-11
Using the CHG Statement 4-11
Using Other Run Statements 4-11
Redefining Variables 4-11
Using Variables in Run Statements 4-12
Referring to Substrings 4-12
Trailing Characters 4-12
Unknown Number of Trailing Characters 4-13
Using Contents to Act as Name or Number 4-13
Using Scientific Notation 4-14
Changing the Contents of Variables 4-15
Using the LDV Statement 4-15
Using the INC and DEC Statements 4-15
Using the ART Statement 4-15
Using the CHG Statement 4-16
Testing the Contents of Variables 4-17
Using the DEF Statement 4-17
Using the IF Statement 4-17
Using the LCV Statement 4-17
Using the VARIABLE Run to Check Contents 4-18
Using a Variable Table 4-19
Using the BVT Run to Build Variable Tables 4-19
Working with Variable Limits 4-22
Maximum Number of Variables Allowed 4-22
Run Registration 4-22
Maximum Number of Characters 4-23
String Space Limits 4-23

7831 9274-000 vii

Contents

Techniques for Handling Variable Limits 4-23

Writing Modular Subroutines 4-23
Passing Variable Arrays 4-24
Clearing Numbered Variables 4-24
Using the Variable Stack 4-24
Capturing Input 4-26
Screen Input 4-26
Initial Input Parameters 4-26
Prompting the User for Input 4-26
Using the Output Area 4-27
Accepting User Input 4-27
Using INPUT$ 4-28
Using INSTR$ 4-29
Using INVAR$ 4-30
Using INVR1$ 4-31
Using INMSV$ with the OUM Statement 4-31
Using ICVAR$ with the CHD Statement 4-32
Using FKEY$ with the KEY and
CHD Statements 4-32
Capturing Initial Input Parameters 4-33
Passing Input to the Run 4-33
Examples Using Variables 4-35
Using Reserved Words 4-38
Reserved Words in the Output Area 4-38
Using Predefined Constants 4-39
Defining Constants 4-39
Including Defined Constants 4-43

Section 5. Getting Online Assistance

Displaying Information about MAPPER
Functions (HELP) 5-2
Creating, Modifying, and Removing APT
Tables (BAT) 5-6
Creating Input Screens and Menus (SCGEN) 5-8
Displaying Horizontal Column Positions (CC) 5-10
Displaying Field Column-Characters (FCC) 5-11
Displaying Run Statement Formats (FORM) 5-12
Using a Function Mask to Get Format (FORMC) 5-13
Creating Run Statements (MARS) 5-14

viii 7831 9274-000

 Contents

Generating Runs (RUN) 5-15

RUN Run Function Key Bar 5-16
Displaying Reports and Results in Your Generated
Run 5-16
Registering Run Statements as a Run 5-17
RUN Run Limitations 5-17
Analyzing Your Run (RUNA) 5-19

Section 6. Designing and Debugging Runs

Planning and Registering Your Run 6-2
Handling Reports and Results 6-5
The Output Area 6-6
Results 6-7
The Relationship Between Output Area and Results 6-7
Debugging Your Run 6-8
Interactive Debugging 6-8
Online Help System 6-8
Checkpoint Displays 6-9
Run Debug (RDB) Statement 6-9
Register Error Routine (RER) Statement 6-9
Using Conditional Statements 6-10
Branching 6-10
Conditional Branching 6-10
Looping 6-11
Using Subroutines 6-12
Writing Efficient Runs 6-13
Run Control Reports 6-13
Analysis and Registration 6-14
Loading Variables 6-15
Statements and Functions 6-15
Updating Reports 6-16
Logic 6-17
Batch Processing 6-18

Appendix A. Summary of Statements and Options

Run Statements A-2
Reminders for Run Statement Syntax A-2
Run Statement Formats A-3

7831 9274-000 ix
Contents

Field and Subfield Abbreviations A-10

Options for 10 Common Run Statements A-17

Appendix B. Reserved Words

Reserved Words in the Output Area B-2
Commonly Used Variable Types and Sizes of
Reserved Words B-2

Appendix C . Control Commands for Transferring Data

Data Control Commands C-2

Appendix D . Character Sets and Sorting Orders

ASCII Character Set D-2
Fieldata (Limited Character Set) D-5
Using the C(S) Option D-7
Character Set Processing on the OS 1100 MAPPER
System D-9
LCS, FCS, and FCSU D-9
Character Hierarchy D-9
Using the C(x) Option D-10
Using the C(L) and C(F) Options D-10

Appendix E. Using Your Keyboard and Mouse

Function Keys E-2
Online Help for Keys E-7
Use of the MAPPER Mouse E-8
Installing the Mouse on Your PC E-8
Guidelines E-9

Appendix F. Developing Source-Protected Applications

Developing an Application F-1
How to Design a Run-Timed Application F-1

Appendix G. Setting up Local Code in Your MAPPER System

Writing Your Functions G-1
Accessing Your Functions G-2

x 7831 9274-000
 Contents

Volume 2: Run Statements

Section 7. Run Statements
Run Statements by Name 7-2
Run Statements by Topic 7-8
Locating, Changing, Comparing, Sorting, and
Reformatting Data 7-8
Manipulating Reports and Results 7-9
Manipulating Screen Displays 7-10
Obtaining Information about the Database, Display,
and Runs 7-11
Calculating 7-12
Printing Results or Reports 7-13
Manipulating Variables 7-13
Controlling Runs 7-14
Manipulating and Updating Report Lines 7-16
Sending and Receiving Messages, and Handling
Devices 7-17
Interfacing the Operating System, Other
Applications, and Other MAPPER Systems 7-18
ADD (Append Report) Online
ADR (Add Report) Online
ART (Arithmetic) 7-23
Operators 7-24
Formulating Arithmetic Expressions 7-24
Multiple Expressions 7-25
Internal Computation 7-25
Negative Numbers 7-26
Changing the Hierarchy of Expressions 7-26
Arithmetic and Trigonometric Functions 7-27
V ASR (A Series Run) 7-28
AUX (Auxiliary) 7-31
BFN (Binary Find) 7-33
Using the IBFN Run to Create a BFN Statement 7-39
BLT (Build Label Table) Online
BR (Background Run) 7-40
V' BR (Background Run): OS 1100 7-42
BRG (Break Graphics) Online

7831 9274-000 xi
Contents

BRK (Break) 7-44

CAB (Cabinet Switch) Online
CAH (Cache Report) Online
CAL (Calculate) 7-46
Priority of Operations 7-50
True/False Conditions 7-52
Date and Time Processing 7-54
Character String Processing 7-54
Using the ICAL Run to Create a CAL Statement 7-54
CAL Statement Examples 7-55
CALL (Call Subroutine) 7-58
CAR (Clear Abort Routine) Online
CAU (Calculate Update) Online
CER (Clear Error Routine) Online
CHD (Command Handler) 7-65
CHG (Change Variable) 7-68
Using Expressions 7-69
Guidelines for Addition and Subtraction 7-69
Processing Octal Variables 7-70
CLK (Clear Link) Online
CLT (Clear Label Table) Online
CLV (Clear Variables) Online
CMP (Compare Report) 7-72
CMU (Commit Updates) Online
V CNT (Count) 7-78
Using the ICNT Run to Create a CNT Statement 7-84
CNT Statement Example 7-85
CPY (Copy) Online
CSR (Clear Subroutine) Online
DAT (Date) 7-86
Using the IDAT Run to Create a DAT Statement 7-90
DC (Date Calculator) 7-91
Date and Time Formats 7-92
V LJUP'T tuur L.017) Online
DCR (Decode Report) 7-95
DCRE (DPD rr-ite) Online
DCU (Decommit Updates) Online
DDI (Data Definition Information) Online

xii 7831 9274-000

 Contents

DEC (Decrement Variable) Online

DEF (Define) 7-97
DEL (Delete) Online
DEV (Device) Online
DFU (Defer Updates) Online
DIR (Directory) 7-100
V DIS (Diskette) Online
V DLL (Downline Load) Online
DLR (Delete Report) Online
DPUR (DDP Purge) Online
DRW (Drawer) 7-102
DSF (Display Form) 7-320
DSG (Display Graphics) Online
DSM (Display Message) 7-104
DSP (Display Report) 7-107
DSX (Display Report and Exit) Online
DUP (Duplicate Report) Online
DVS (Define Variable Size) 7-110
ECR (Encode Report) 7-112
V EL- (Element Delete) 7-115
V ELT (Element) 7-117
ESR (Exit Subroutine) Online
EXT (Extract) Online
FCH (Relational Aggregate Fetch) Online
FDR (Find and Read Line) 7-121
FIL (Create File) 7-125
FKY (Function Key) 7-129
FMT (Format) 7-131
FND (Find) 7-133
Using the IFND Run to Create an FND
Statement 7-137
GOC (Generate Organization Chart) Online
GS (Graphics Scaler) Online
GTO (Go To) 7-138
HOF (Host Sign-off) Online
HRD (Host Read) Online
HRN (Host Run) Online
HSH (Hash) 7-140

7831 9274-000
Contents

HST (Host Sign-on) Online

HWR (Host Write) Online
IDU (Index User) 7-141
IF (If Conditional) 7-143
INC (Increment Variable) Online
IND (Index) 7-148
INS (Insert Variable) Online
ITV (Input Variable) 7-149
JUV (Justify Variable) 7-151
KEY (Function Key Input) 7-154
LCH (Locate and Change) 7-155
LCV (Locate and Change Variable) 7-158
LDA (Load Variable Array) 7-166
LDV (Load Variable) 7-169
Loading Multiple Variables 7-171
Packing Variables 7-172
Loading Variables Based on Content 7-172
LDV Examples with Various Options 7-173
LFC (Load Format Characters) 7-175
LFN (Load Field Name) 7-176
LGF (Logoff Relational System) Online
LGN (Logon Relational System) Online
LLN (Last Line Number) Online
LMG (List Merge) Online
LN+ (Add Line) Online
LN- (Delete Line) Online
LNA (Append Line) Online
LNG (Language) Online
LNI (Insert Line) Online
LNK (Link to Another Run) 7-178
LNM (Move Line) Online
LNP (Put Line) Online
LNX (Duplicate Line) Online
LNY (Yank Line) Online
LOC (Locate) 7-180
LOG (Log for Analysis) Online
LOK (Update Lock) Online
LSM (Load System Message) 7-183

xiv 7831 9274-000

 Contents

LZR (Line Zero) 7-184

MAU (Match Update) Online
MCH (Match) 7-187
MSG (Message to Control) 7-192
NET (Network Sign On) 7-194
NOF (Network Off) 7-196
NRD (Network Read) 7-197
NRM (Network Remote) 7-198
NRN (Network Run) 7-200
NRT (Network Return) 7-202
NWR (Network Write) 7-203
Receiving Report Entries 7-203
OK (Acknowledge Message) 7-205
V 0S2 (Operating System Interface) 7-207
OUM (Output Mask) 7-209
OUT (Output) 7-214
Displaying Information At Another Terminal 7-220
If the User Is At the Terminal 7-221
If the User Is Not at the Terminal 7-221
Four- and Five-to-One Output 7-221
Color Characters 7-226
Emphasis Characters 7-227
Four-to-One Screens 7-228
OUV (Out Variable) 7-231
PEK (Peek Variables) Online
PNT (Refresh Screen) Online
POK (Poke Variables) Online
POP (Pop Variables) Online
PRT (Print) 7-232
PSH (Push Variables) Online
V QCTL (Queue Control) Online
V QREL (Release Message) Online
V QRSP (Send Response Message) Online
V QSND (Send Message, No Response) Online
V QSNR (Send Message, Expect Response) Online
RAM (Relational Aggregate Modify) Online
RAR (Register Abort Routine) 7-235
RDB (Run Debug) 7-238
RDB Commands and Function Keys 7-239

7831 9274-000 xv
Contents

V RDB (Run Debug): OS 1100 7-244

RDII Commands and Function Keys: OS 1100 7-245
RDC (Read Continuous) 7-250
RDL (Read Line) 7-254
V REH (Retrieve from History) 7-257
REL (Release Display) Online
REP (Replace Report) Online
RER (Register Error Routine) 7-258
RET (Retrieve File) 7-261
V RET (Retrieve File): OS 1100 7-263
RETURN (Return Call Routine) Online
RFM (Reformat Report) 7-265
RLN (Read Line Next) 7-267
RMV (Remove Variables) Online
RNM (Rename) Online
RPW (Read Password) 7-270
RRN (Remote Run) Online
V RS (Run Status) -272
V RSI (Remote Symbiont Interface) 7-273
RSL (Create Result Copy) Online
RSR (Run Subroutine) 7-275
RTN (Return Remote) Online
RUN (Run Start) 7-278
SC (Screen Control) 7-280
Reserved Words 7-284
Error Status Reserved Words 7-285
Screen Commands 7-285
Cursor Control Commands 7-288
Screen Editing Commands 7-289
Field and Attribute Commands 7-290
Text Handling Commands 7-307
Screen Printing Commands 7-312
Setup Commands 7-312
Special FKEY Actions 7-316
Displaying a Form and Returning Control to
the Run 7-320
SCH (Schedule) 7-324
SEN (Send Report) 7-325

xvi 7831 9274-000

 Contents

SFC (Set Format Characters) 7-327

SNU (Send Report to User) 7-328
SOR (Sort) 7-330
Using the ISOR Run to Create an SOR
Statement 7-332
SQL (Submit SQL Statement) Online
SRH (Search) 7-333
Using the ISRH Run to Create an SRH
Statement 7-337
SRR (Sort and Replace Report) Online
SRU (Search Update) Online
STN (Station Information) 7-338
STR (Start) 7-340
IBM Start Requirements 7-342
SUB (Subtotal) 7-343
V TCS (Tape Cassette) Online
TOT (Totalize) 7-347
Using the ITOT Run to Create a TOT
Statement 7-351
TRC (Trace) Online
ULK (Unlock) Online
UNX (UNIX Interface) 7-352
UPD (Update) Online
USE (Use Variable Name) 7-355
WAT (Wait) 7-356
WDC (Word Change) Online
WDL (Word Locate) Online
WPR (Word Process) Online
WRL (Write Line) 7-358
XCH (Exchange Variables) Online
XIT (Sign off MAPPER Software) Online
XQT (Execute) 7-360
XUN (Exit MAPPER System) 7-363
*cmd (Local Code) 7-364

Glossary

Index

7831 9274-000 xvii

Figures

4-1. Fields in Variable Tables 4-20

6-1. Sample Flow Chart 6-2
6-2. Processing a Report or Result 6-5
6-3. One Run Using Several Reports and Results 6-6
6-4. Relationship between Output Area and Results 6-7

7831 9274-000 xix

Tables

4-1. Variable Types and Sizes 4-7

4-2. Default Justification 4-8

A-4. Options for 10 Common Run Statements A-18

B-1. Reserved Words B-3

C-1. Data Control Commands C-2

D-1. ASCII Character Set D-2

D-2. Limited Character Set D-5
D-3. Sorting with the C(S) Option D-8
D-4. Sorting without the C(S) Option D-8
D-5. LCS Order Using the C(x) Option D-11
D-6. FCS Order Using the C(x) Option D-13

E-1. Function Key Descriptions E-2

E-2. Screen Location of Keys on the Function Key Bar E-6

7-1. Run Statements by Name 7-2

7-2. ART: Arithmetic Operators 7-24
7-3. ART: Priority of Arithmetic Operations 7-25
7-4. ART: Arithmetic and Trigonometric Functions 7-27
7-5. CAL: Priority of Arithmetic Operations 7-50
7-6. CAL: Priority of Relational Operations 7-51
7-7. CAL: AND and OR True/False Conditions 7-52
7-8. Characteristics for the Expanded M 7-223
7-9. Characteristics for the Expanded N 7-225
7-10. Five-to-One Color Codes 7-227
7-11. Emphasis Characters 7-228

7831 9274-000 xxi

Tables

7-12. RDB Commands and Function Keys 7-239

7-13. RDB Commands and Function Keys: OS 1100 7-245
7-14. Cursor Control Commands 7-288
7-15. Screen Editing Commands 7-289
7-16. Special Commands 7-307

xxii 7831 9274-000

Section 7
Run Statements

V You may find additional information specific to your MAPPER system by

pressing ReadMe from the sign-on screen.

This section presents the MAPPER run statements by run function call in
alphabetical order. Complete reference information is included about most
statements; those that are documented only in the online help system are
flagged with an asterisk in Table 7-1.
If you need tutorial information, refer to the Run Design Training Guide.
This section contains:
• A list of run statements by name
• A list of run statements by topic
• Reference information for run statements, presented alphabetically

7831 9274-000 7-1

Run Statements by Name

Run Statements by Name

In Table 7-1, the descriptive run statement names and their corresponding
run function calls are listed for cross-reference purposes. Some MAPPER
statements are documented in the online help system only. These are
flagged with an asterisk (*) in Table 7-1.
Note: Since this list encompasses several different kinds of MAPPER
systems, some run statements may not be available on your system.

Table 7-1. Run Statements by Name

Name Call

A Series Run ASR

Acknowledge Message OK
Add Line LN+ *
Add Report ADR *
Append Line LNA *
Append Report ADD *
Arithmetic ART
Auxiliary AUX

Background Run BR
Binary Find BFN
Break BRK
Break Graphics BRG *
Build Label Table BLT *

Cabinet Switch CAB *

Cache Report CAH *
Calculate CAL
Calculate Update CAU *
Call Subroutine CALL
Change Variable CHG
Clear Abort Routine CAR *
Clear Error Routine CER *
Clear Label Table CLT *
Clear Link CLK *
Clear Subroutine CSR *
Clear Variables CLV * /-"\
Command Handler CHD

continued

* Documented in online help system only (enter help,@call).

7-2 7831 9274-000

 Run Statements by Name

Table 7.1. Run Statements by Name (cont.)

Name Call

Commit Updates CMU *

Compare Report CMP
Copy CPY *
Count CNT
Create Result Copy RSL *
Create File FIL

Data Definition Information DDI .r

Date DAT
Date Calculator DC
DDP Copy DCPY *
DDP Create DCRE *
DDP Purge DPUR *
Decode Report DCR
Decommit Updates DCU *
Decrement Variable DEC *
Defer Updates DFU *
Define DEF
Define Variable Size DVS
Delete DEL *
Delete Line LN- *
Delete Report DLR *
Device DEV *
Directory DIR
Diskette DIS *
Display Form DSF
Display Graphics DSG *
Display Message DSM
Display Report DSP
Display Report/Exit DSX *
Downline Load DLL *
Drawer DRW
Duplicate Line LNX *
Duplicate Report DUP *

Element ELT
Element Delete EL-
Encode Report ECR
Exchange Variables XCH *
Execute MT

.* Documented in online help system only (enter help,@call).

T Documented in MRI Run Statements Reference.

7831 9274-000 7-3

Run Statements by Name

Table 7-1. Run Statements by Name (cont.)

Name Call

Exit MAPPER System XUN

Exit Subroutine ESR *
Extract EXT *

Find FND
Find and Read Line FDR
Format FMT
Function Key FKY
Function Key Input KEY

Generate Organization Chart GOC *

Go To GTO
Graphics Scaler GS *

Hash HSH
Host Read HRD *
Host Run HRN *
Host Sign-off HOF *
Host Sign-on HST *
Host Write HWR *

f Conditional F
ncrement Variable NC *
ndex ND
ndex User DU
nput Variable TV
nsert Line LNI *
nsert Variable NS *

Justify Variable JUV

Language LNG *
Last Line Number LLN *
Line Zero LZR
Link to Another Run LNK
List Merge LMG *
Load Field Name LFN
Load Format Characters LFC
Load System Message LSM
Load Variable LDV
Load Variable Array LDA

Documented in online help system only (enter help,@call).

7-4 7831 9274-000

 Run Statements by Name

Table 7-1. Run Statements by Name (cont.)

Name Call

Local Run Call *cmd

Locate LOC
Locate and Change LCH
Locate and Change Variable LCV
Log for Analysis LOG
Logoff Relational System LGF I
Logon Relational System LGN I.

Match MCH
Match Update MAU *
Message to Console MSG
Move Line LNM *

Network Off NOF

Network Read NRD
Network Remote NRM
Network Return NRT
Network Run NRN
Network Sign-On NET
Network Write NWR

Operating System Interface 0S2

Out Variable OUV
Output OUT
Output Mask OUM

Peek Variables PEK *

Poke Variables POK *
Pop Variables POP *
Print PRT
Push Variables PSH *
Put Line LNP *

Queue Control QCTL *

Read Continuous RDC

Read Line RDL
Read Line Next RLN
Read Password RPW
Reformat Report RFM

* Documented in online help system only (enter help,@call).

Documented in MRI Run Statements Reference.

7831 9274-000 7-5

Run Statements by Name

Table 7-1. Run Statements by Name (cont.)

Name Call

Refresh Screen PNT *

Register Abort Routine RAR
Register Error Routine RER
Relational Aggregate Fetch FCH
Relational Aggregate Modify RAM t
Release REL *
Release Message QREL *
Remote Run RRN *
Remote Symbiont Interface RSI
Remove Variables RMV *
Rename RNM *
Replace Report REP *
Retrieve File RET
Retrieve from History REH
Return Call Routine RETURN *
Return Remote RTN *
Run Debug RDB
Run Start RUN
Run Status RS
Run Subroutine RSR

Schedule SCH
Screen Control SC
Search SRH
Search Update SRU *
Send Message, No Response QSND *
Send Message, Expect Response QSNR *
Send Report SEN
Send Report to User SNU
Send Response Message QRSP *
Set Format Characters SFC
Sign off XIT *
Sort SOR
Sort and Replace Report SRR *
Start STR
Station Information STN
Submit SQL Statement SQL t
Subtotal SUB

Tape Cassette TCS *

* Documented in online help system only (enter help,@call).

t Documented in MRI Run Statements Reference.

7-6 7831 9274-000

 Run Statements by Name

Table 7-1. Run Statements by Name (cont.)

Name Call

Totalize TOT
Trace TRC 1.

UNIX Interface UNX

Unlock ULK*
Update UPD *
Update Lock LOK *
Use Variable Name USE

Wait WAT
Word Change WDC *
Word Locate WDL *
Word Process WPR *
Write Line WRL

Yank Line LNY *

.* Documented in online help system only (enter help,@call ).

T Documented in MRI Run Statements Reference.

7831 9274-000 7-7

Run Statements by Topic

Run Statements by Topic

This section categorizes MAPPER run statements and describes them
briefly.
Note: Since this list encompasses several different kinds of MAPPER
systems, some run statements may not be available on your system.

Locating, Changing, Comparing, Sorting, and Reformatting Data

The following statements locate, change, compare, sort, or reformat data.
See also "Manipulating and Updating Report Lines" in this subsection.
• Binary Find (BFN) - Finds data items in a sorted report by sampling the
report from the midpoint.
• Compare Report (CMP) - Compares the contents of a report or result
with another report.
• Find (FND) - Finds data in a report or result.
• Find and Read Line (FDR) - Finds data in a report or result.
• Generate Organization Chart (GOC) - Generates organization charts
using the GOC command language.
• Locate (LOC) - Locates a character string within a report or result.
• Locate and Change (LCH) - Searches for a specific target string and
replaces it with another specified string in a report or result.
• Match (MCH) - Matches fields in two reports, and optionally moves data
from an issuing report to a receiving report, creating a result.
• Match Update (MAU) - Performs the same operation as MCH, but you
can blend the changed lines back into the original report (cannot be a
result). The receiving report is locked so that it cannot be updated while
the match is being performed.
• Read Continuous (RDC) - Reads report lines and segments into the
output area.
• Reformat Report (RFM) - Moves data between reports or across drawers
and creates a result.

7-8 7831 9274-000

 Run Statements by Topic

• Search (SRH) - Searches vertically through reports or results and puts

located items in a result.
• Search Update (SRU) - Does the same thing as SRH, but you can also
blend the changed lines back into the original report (cannot be used on
a result).
• Sort (SOR) - Sorts report data.
• Sort and Replace Report (SRR) - Sorts report data and replaces the
sorted data into the original report (cannot be used on results).

Manipulating Reports and Results

The following statements manipulate reports and results:
• Add Report (ADR) - Adds a new report to a drawer.
• Append Report (ADD) - Appends a report or result to the end of another
report or result.
• Break (BRK) - Turns the output area of a run into the current -0 result
and creates a new output area (containing only a date line).
• Break Graphics (BRG) - Packs data, such as graphics primitive code, in
the output area and places it into a result.
• Cache Report (CAH) - Loads (caches) all of the specified report into
memory for fast processing.
• Create Result Copy (RSL) - Creates a copy of a report as a result.
• Decode Report (DCR) - Transforms an encoded report into a readable
report by specifying the key.
• Delete Report (DLR) - Deletes a MAPPER report.
• Duplicate Report (DUP) - Copies an existing report or result, creating a
new report.
• Encode Report (ECR) - Encodes a report, changing the data from
readable text into code that can be read only if a key is specified.
• Generate Organization Chart (GOC) - Generates organization charts
using the GOC command language.

7831 9274-000 7-9

Run Statements by Topic

• Rename (RNM) - Creates a new reference for a report or result, -1

through -8, in any order.
• Replace Report (REP) - Replaces the contents of a report with the
contents of another report or result.

Manipulating Screen Displays

The following statements manipulate screen displays:
• Change Variable (CHG INPUT$) - Loads variables with input from a
screen display.
• Command Handler (CHD) - Registers a routine to be executed whenever
the user of the run enters information in the control line after a DSP,
OUT, or SC statement.
• Display Form (DSF) - Displays a report containing screen control
commands (form) from within a run.
• Display Graphics (DSG) - Translates the graphics primitive code in a
report and displays it on your terminal.
• Display Message (DSM) - Allows you to display your own one-line
message at the top of the screen.
• Display Report (DSP) - Displays a report or result on your terminal.
• Display Report and Exit (DSX) - Displays a report or result on your
terminal and exits the run.
• Format (FMT) - Creates a display format by selecting which fields of a
report or result to display on a following DSP, OUM, or OUT statement.
• Function Key (FKY) - Stores function key information for a function key
bar and loads it into the reserved word FKEY$.
• Graphics Scaler (GS) - Increases or decreases the size of your charts and
creates custom graphics using the expanded syntax.
• Input Variable (ITV) - Accepts input into variables from a screen
displayed with an Out Variable (OUV) statement.
• Language (LNG) - Lets you switch to another language for system
messages.

7-10 7831 9274-000

 Run Statements by Topic

• Load Format Characters (LFC) - Captures the display format of a

report.
• Out Variable (OUV) - Displays the contents of variables, reserved words,
constants, or literal data on the screen.
• Output (OUT) - Displays portions of a report or result or the output area
of a run.
• Output Mask (OUM) - Displays a blank function mask from report
headings.
• Refresh Screen (PNT) - Refreshes the screen display.
• Release Display (REL) - Terminates the run and displays the active
screen.
• Screen Control (SC) - Allows you to create menus and other input
screens or to edit text already on the screen. You can also use it to
overlay existing OUT or DSP screens.
• Set Format Characters (SFC) - Defines a format for the display of a
report or result with a DSP, DSX, OUM, or OUT statement.
• Sign off MAPPER Software (XIT) - Terminates a MAPPER session and
signs off the user (sign-on screen).
• Wait (WAT) - Suspends a screen display.

Obtaining Information about the Database, Display, and Runs

The following statements provide information about the database, the
display terminal, and runs currently being executed:
• Directory (DIR) - Loads variables with information about a data name
from the system directory.
• Drawer (DRW) - Loads a variable with the number of characters per line
in a drawer.
• Index (IND) - Indexes a specific drawer in a cabinet and creates a result.
• Index User (IDU) - Indexes a specific drawer in a cabinet and creates a
result by user, date, or report range.

7831 9274-000 7-11

Run Statements by Topic

• Last Line Number (LLN) - Loads a variable with the last line number of
a specified report.
• Line Zero (LZR) - Initializes or loads variables with data from line 0 of a
report or result.
• Load Field Name (LFN) - Loads variables with the names of report
fields that correspond to the column-character positions supplied.
• Load Format Characters (LFC) - Captures the display format of a
report.
• Log for Analysis (LOG) - Logs statements executed in a run.
• Retrieve from History (REH) - Retrieves the version of a MAPPER
report prior to the last system purge or merge process.
• Run Status (RS) - Creates a result showing the status of runs being
executed with your user-id.

Calculating
The following statements perform calculations on literal data, report data,
or dates and times:
• Arithmetic (ART) - Performs arithmetic on variables or constants.
• Calculate (CAL) - Performs arithmetic calculations on a report or result.
• Calculate Update (CAU) - Performs the same operation as CAL, but you
can also blend the changed lines back into the original report.
• Count (CNT) - Computes subtotals, percentages, standard deviations,
averages, entry counts, and other calculations on reports or results,
creating a result.
• Date (DAT) - Computes dates in a report or result.
• Date Calculator (DC) - Computes and calculates dates and times in
variables.
• Subtotal (SUB) - Subtotals report or result data.
• Totalize (TOT) - Performs arithmetic and move operations on report or
result fields.

7-12 7831 9274-000

 Run Statements by Topic

Printing Results or Reports

The following statements print reports and results on auxiliary or system
printers:
• Auxiliary (AUX) - Sends a report or result to auxiliary printers.
• Print (PRT) - Prints reports or results on the system printer.

Manipulating Variables
The following statements manipulate variables in several ways:
• Change Variable (CHG) - Changes or initializes the contents of a
variable.
• Clear Variables (CLV) - Clears the definition and contents of a set of
variables.
• Decrement Variable (DEC) - Decrements the numeric value of a
variable.
• Define (DEF) - Tests the contents and type of a variable or array.
• Define Variable Size (DVS) - Creates variables equal to the size of report
fields.
• Exchange Variables (XCH) - Exchanges a set of variables in your run
with a set stored in a level of the variable stack.
• Increment Variable (INC) - Increases the numeric value of a variable.
• Input Variable (ITV) - Accepts all input from OUV or interim OUT
output and initializes variables.
• Insert Variable (INS) - Inserts variable or constant data into a variable.
• Justify Variable (JUV) - Reformats the contents of numeric variables.
• Load Variable (LDV) - Loads or initializes variables with specified
contents.
• Load Variable Array (LDA) - Defines a variable array and puts data into
the array.
• Locate and Change Variable (LCV) - Locates a string in a variable and
optionally changes the string.

7831 9274-000 7-13

Run Statements by Topic

• Out Variable (OUV) - Displays the contents of a variable, constant,

reserved word, or literal data.
• Peek Variables (PEK) - Retrieves variables saved with a previous Push
(PSH) statement.
• Poke Variables (POK) - Replaces the contents and definition of variables
saved with a previous Push (PSH) statement.
• Pop Variables (POP) - Retrieves variables saved with a previous Push
(PSH) statement and removes their level from the stack.
• Push Variables (PSH) - Saves both the contents and definition of
variables so that you can restore them later in the run with a POP or a
PEK statement.
• Remove Variables (RMV) - Removes a level from the variable stack.
• Use Variable Name (USE) - Allows you to assign a variable name to a
specific variable number.

Controlling Runs
The following statements encompass several areas of run design, including
logic, subroutines, and utilities:
• Background Run (BR) - Begins a run in the background so that you can
still perform operations from the terminal.
• Break (BRK) - Puts the output area of a run into a result (-0).
• Build Label Table (BLT) - Builds label table definition lines for a run
control report.
• Cabinet Switch (CAB) - Switches the current cabinet to a different
cabinet.
• Call Subroutine (CALL) - Saves the contents and definitions of all
variables currently defined in the run and transfers control to a
subroutine; you can also pass the value of up to 40 variables to the called
subroutine.
• Clear Abort Routine (CAR) - Cancels an abort routine set by a Register
Abort Routine (RAR) statement.

7-14 7831 9274-000

 Run Statements by Topic

• Clear Error Routine (CER) - Cancels an error routine set by a Register

Error Routine (RER) statement.
• Clear Link (CLK) - Clears the link to the original run from the run that
was started by a LNK statement.
• Clear Label Table (CLT) - Deletes label table definition lines from a run
control report.
• Clear Subroutine (CSR) - Clears the return path to the calling run
control report in an external subroutine called by the Run Subroutine
(RSR) statement.
• Command Handler (CHD) - Registers a routine to be executed whenever
the user of the run enters information in the control line after a DSP,
OUT, or SC statement.
• Execute (XQT) - Executes a run statement.
• Exit Subroutine (ESR) - Exits a subroutine and returns you to the line
following the RSR statement in the run control report.
• Function Key Input (KEY) - Provides you with a number indicating the
function key the run user pressed after a noninterim display.
• Go To (GTO) - Allows you to branch within a run (GTO label or LIN n),
execute run statements in another run control report (GTO RPX), or
terminate a run and display the output area (GTO END).
• If Conditional (IF) - Compares values and performs an action depending
on whether the condition is true or false.
• Link to Another Run (LNK) - Executes another run in the MAPPER
system.
• Load System Message (LSM) - Loads a variable with the contents of a
system message.
• Read Password (RPW) - Allows a run to access reports containing one of
two read passwords.
• Register Abort Routine (RAR) - Registers or names a routine specified
by a label to be executed if the user aborts a run.
• Register Error Routine (RER) - Registers or names a routine specified by
a label to be executed if the run encounters an error.

7831 9274-000 7-15

Run Statements by Topic

• Return Call Routine (RETURN) - Exits the called subroutine and

returns to the calling run.
• Run Debug (RDB) - Allows you to step through a run, one statement at a
time, to debug it.
• Run Start (RUN) - Terminates the current run and executes another run
at the same station.
• Run Subroutine (RSR) - Transfers control to a specified label to execute
a set of run statements.
• Schedule (SCH) - Allows you to schedule any queuing function that
follows the SCH statement on the same logic line.
• Wait (WAT) - Temporarily suspends the execution of a run.

Manipulating and Updating Report Lines

The following statements allow you to manipulate or update reports and
results:
• Add Line (LN+) - Adds lines to a report or result.
• Append Line (LNA) - Adds lines to an existing temporary buffer.
• Commit Updates (CMU) - Commits updates to reports that were
deferred.
• Decommit Updates (DCU) - Decommits updates to reports which were
deferred.
• Defer Updates (DFU) - Defers all updates to specified reports until
updates are committed or decommitted.
• Delete (DEL) - Deletes lines in an update result (SRU, MAU, CAU) from
the original report.
• Delete Line (LN-) - Deletes lines from a report or result.
• Duplicate Line (LNX) - Duplicates lines within a report or result.

7-16 7831 9274-000

 Run Statements by Topic

• Extract (EXT) - Extracts lines in an update result from a report, deletes

them from the original report, and moves the extracted lines into the
current result.
• Insert Line (LNI) - Inserts a line or lines into a report or result.
• Move Line (LNM) - Moves lines within a report or result.
• Put Line (LNP) - Copies lines from a temporary buffer into a report or
result.
• Read Continuous (RDC) - Reads report lines and segments into the
output area.
• Read Line (RDL) - Reads a report line or line segment.
• Read Line Next (RLN) - Continues reading from the report or current
result after an RDL or FDR.
• Unlock (ULK) - Releases an update lock on a report.
• Update (UPD) - Blends updated lines in the result of an update result
(SRU, MAU, CAU) back into the report.
• Update Lock (LOK) - Assumes update control of a report, preventing
other users from updating it until it is released.
• Write Line (WRL) - Updates up to 23 lines of a report or result.
• Yank Line (LNY) - Copies lines from a report or result into a temporary
buffer area.

Sending and Receiving Messages, and Handling Devices

The following statements allow you to send and receive messages and
handle devices:
• Acknowledge Message (OK) - Acknowledges an incoming message.
• Device (DEV) - Lists auxiliary devices if any are connected to a terminal.
• Diskette (DIS) - Writes data to and reads data from a 5-1/4-inch diskette
drive connected to a Unisys UTS 30 display terminal.

7831 9274-000 7-17

Run Statements by Topic

• Downline Load (DLL) - Loads a precompiled program stored in a

MAPPER report into a Unisys UTS 400 master or UTS 40 display
terminal.
• Message to Console (MSG) - Sends a message to the system console.
• Send Report (SEN) - Sends a report or result as a message to a station
as a result.
• Send Report to User (SNU) - Sends an entire report or result to another
user.
• Station Information (STN) - Provides you with information about a
specific station number.
• Tape Cassette (TCS) - Transfers data to and from a tape
cassette/diskette unit connected as an auxiliary device of a display
terminal.

Interfacing the Operating System, Other Applications, and Other

MAPPER Systems
The following statements allow you to work with the operating system,
applications outside of MAPPER software, and with other MAPPER
systems.
Note: See the online help system (HELP,DOC) for a list of related product
information. Some of the run statements listed in this category are
described in other manuals.
• A Series Run (ASR) - Enables you to execute A series programs.
• Copy (CPY) - Copies an OS 1100 program file or element, or a data file,
from one site to another through the remote run link.
• Create File (FIL) - Creates a native data file from a MAPPER report or
result.
• Data Definition Information (DDI) - Retrieves a table description from a
relational database.
• DDP Copy (DCPY) - Copies an OS 1100 program file or element, or data
file, from one host to another using DDP 1100.

7-18 7831 9274-000

 Run Statements by Topic

• DDP Create (DCRE) - Creates a file on a DDP 1100 host.

• DDP Purge (DPUR) - Deletes a file on a DDP 1100 host.
• Element (ELT) - Copies a MAPPER report or result to a standard
OS 1100 program file or symbolic element, or to a data file.
• Element Delete (EL-) - Deletes a standard OS 1100 program file or
symbolic element, or a data file.
• Exit MAPPER System (XUN) - Terminates a MAPPER session, exits
MAPPER software, and returns you to your previous environment.
• Host Read (HRD) - Lets you transfer data from the OS 1100 MAPPER
System.
• Host Run (HRN) - Lets you transfer run statements to the OS 1100
MAPPER System to be executed.
• Host Sign-off (HOF) - Signs you off the OS 1100 MAPPER System.
• Host Sign-on (HST) - Signs you on to the OS 1100 MAPPER System.
• Host Write (HWR) - Lets you write a report or result to the OS 1100
MAPPER System.
• Logoff Relational System (LGF) -Terminates communication with a
relational database manager.
• Logon Relational System (LGN) - Establishes communication between a
MAPPER system and a relational database management system.
• Network Off (NOF) - Signs the local MAPPER system caller off the
remote MAPPER system.
• Network Read (NRD) - Enables the user to read and pass data from a
remote MAPPER system to the local MAPPER system.
• Network Remote (NRM) - Executes a run that resides on a remote
MAPPER system.
• Network Run (NRN) - Allows a local MAPPER system user to pass run
statements to a remote MAPPER system to be executed.
• Network Return (NRT) - Returns control from a run executed with NRM
to the run executing on the local system.

7831 9274-000 7-19

Run Statements by Topic

• Network Sign On (NET) - Signs on to the remote MAPPER system from

the calling (local) MAPPER system.
• Network Write (NWR) - Allows a user to send a report or result from a
local MAPPER system to a remote MAPPER system.
• Operating System Interface (0S2) - Interfaces with the operating
system and allows the execution of native PC operating system
commands.
• Queue Control (QCTL) - Obtains various information about the Data
Transfer Module (DTM) interface.
• Relational Aggregate Fetch (FCH) - Retrieves data from one or more
relational tables and places the data in a MAPPER result.
• Relational Aggregate Modify (RAM) - Creates or deletes relational
tables, updates a table, or issues a COMMIT command.
• Release Message (QREL) - Indicates that Data Transfer Module (DTM)
processing is complete.
• Remote Run (RRN) - Starts a run in background at another MAPPER
site.
• Remote Symbiont Interface (RSI) - Initiates an interactive demand
program through a MAPPER run.
• Retrieve File (RET) - Retrieves a native data file as a MAPPER result.
• Return Remote (RTN) - Returns a report or result from a remote
MAPPER site to the local site as a current result.
• Send Message, No Response (QSND) - Through Data Transfer Module
(DTM), sends a message to a named queue, expecting no response.
• Send Message, Response Expected (QSNR) - Through Data Transfer
Module (DTM), sends a message on a named queue, expecting a
response.

7-20 7831 9274-000

 Run Statements by Topic

• Send Response Message (QRSP) - Through Data Transfer Module

(DTM), sends a response when a MAPPER run is initiated by a QSNR
statement (from another MAPPER run) or a CALL 'QSNR' (from a batch
COBOL program or COBOL TIP transaction).
• Start (STR) - Starts a batch job.
• Submit SQL Statement (SQL) - Submits SQL syntax to a relational
database manager.
• Trace (TRC) - Saves the SQL syntax generated by MAPPER Relational
Interface (MRI) run statements in a specified report.
• UNIX Interface (UNX) - Accesses the UNIX operating system.

7831 9274-000 7-21

 ART (Arithmetic)

ART (Arithmetic)
The Arithmetic (ART) statement performs arithmetic operations on
variables or constants. Variables capture the resulting numbers. Use the
ART statement for complex operations; use a Change Variable (CHG)
statement for simple computations.
In ART statements, you can use A, F, and I type variables containing
numeric characters.
Format
@ART exp vrslts .

Following is a description of the fields:

Field Description

exp Arithmetic expression or expressions.

visits Variables to capture the results of the expressions. Initialize the variables for the
number of results you want to capture.

7831 9274-000 7-23

ART (Arithmetic)

Operators
Table 7-2 lists arithmetic operators that you can combine to form an
expression.

Table 7-2. ART: Arithmetic Operators

Operator Operation Expression Description

+ Addition a+b Value a plus value b

- Subtraction a-b Value a minus value b

/ Division a/b Value a divided by value b

// Integer Division a//b Value a integer divided by value b

* Multiplication a*b Value a times value b

** Exponentiation a**b Value of a raised to the power of value b

- Unary Minus -a Negative the value of a

Note: Values a and b are real integers and numbers and can include decimal
fractions or expressions composed of such numbers.

Formulating Arithmetic Expressions

When formulating expressions, consider the following:
• Specify arithmetic operators for every operation; for example, enter the
operation a times b as a*b. Forms such as (a)(b) or ab are not valid.
• Do not precede or follow operators with spaces.
Table 7-3 shows the priority by which the calculator of the MAPPER system
performs arithmetic operations. For operators of equivalent priority, the
operators are processed from left to right unless you change the priority
with parentheses (see "Changing the Hierarchy of Expressions" in this
subsection).

7-24 7831 9274-000

 ART (Arithmetic)

Table 7-3. ART: Priority of Arithmetic Operations

Priority Operator Operation

First - Unary minus

Second ** Exponentiation

Third *,/,// Multiplication, division,integer division

Fourth +,- Addition, Subtraction

Example
Raise 3 to the 4th power, divide the result into 2, and place the answer in vl:
@a r t 3**4/2 v116.2 .

Multiple Expressions
Evaluating multiple expressions in a single statement is more efficient than
using a separate ART statement for each expression.
Add v33 to v34 and put the answer in v36i3; subtract v34 from v33 and put
the answer in v37i3 (note that a semicolon [ ; ] separates the expressions):
@art v33+v34;v33-v34 v36i3,v37i3 .

Internal Computation
You can refer to variables that are created internally by an ART statement
(a, b, and so on), then use these variables for computing expressions within
the same ART statement, as in this example:
@art v1+v2;a*v3;b+5 ,v4i3,v5i3 .

7831 9274-000 7-25

ART (Arithmetic)

In this example, the addition of vl to v2 produces answer a, which is used in

the second expression. The second expression, a*v3, produces answer b,
which is used in the third expression. The first subfield in the variables
field is skipped and a comma is used in its place, so the answer from the
first expression (a) is not captured in a variable. V4 contains the answer to
the second expression, and v5 contains the answer to the third expression.

Negative Numbers
If it is possible that a variable used in an arithmetic expression has a
negative number, place the variable in parentheses; otherwise, the
calculator reads it as part of an expression and the run errs. Place all
negative numbers in arithmetic expressions in parentheses. For example, in
this statement, v5 contains a negative number:
@art 3+(v5) v6i3 .

Changing the Hierarchy of Expressions

Use parentheses to change the hierarchy of expressions. In this example, 2
is divided by 3, the product is raised to the power of 4, and the answer is
placed in vl:
@art (2/3)**4 vlf6.2 .

7-26 7831 9274-000

 ART (Arithmetic)

Arithmetic and Trigonometric Functions

You can perform the arithmetic and trigonometric functions shown in
Table 7-4 using an ART statement. Note that x is a numeric value (whole or
fraction) or an arithmetic expression.
Table 7-4. ART: Arithmetic and Trigonometric Functions

Function Description

ABS(x) Absolute value or magnitude of x

ACOS(x) Arc cosine: angle in radians that has a cosine of x
ASIN(x) Arc sine: angle in radians that has a sine of x
ATAN(x) Arc tangent: angle in radians that has a tangent of x
CBRT(x) Cube root of x
COS(x) Cosine of x radians
CTN(x) Cotangent of x radians
DEG(x) x radians expressed in degrees
EXP(x) Exponent: natural number e raised to power x
FRAC(x) Fractional portion of x
HCOS(x) Hyperbolic cosine of x
HSIN(x) Hyperbolic sine of x
HTAN(x) Hyperbolic tangent of x
INT(x) Integer portion of x
LOG(x) Logarithm of x in base "e"
LOG10(x) Logarithm of x in base 10
Pi Pi CO
RAD(x) x degrees in radians
SIN(x) Sine of x radians
SORT(x) Square root of x
TAN(x) Tangent of x radians

7831 9274-000 7-27

ASR (A Series Run)

ASR (A Series Run)

V' This section applies only to the A Series MAPPER System.
The A Series Run (ASR) statement enables you to execute A Series
programs.
Format
WSR[,rmt?,xmt?,c1,(11,r1,h17,in,co,do,ho?,out,lab] In [ergs]

Following is a description of the fields and subfields.

Field Description

rmt? Program uses a remote file, Y or N. Default = N (remote file is not allowed).

xmt? After program executes, require user to press Transmit before returning to
MAPPER software, Y or N. Default = N (user automatically returns to MAPPER
software).

ci,di,ri Report to send to the program as input (must be specified if in is specified).

hi? Append headings to the input file, Y or N. Default = N.

in INTNAME of the input file of the program run. If specified, the following filecard is
added to the program:

FILE in-int (KIND=DISK,TITLE=fn-inputrpt,DEPENDENTSPECS=TRUE);

in-int is the INTNAME specified in the in subfield.

fn-inputrpt is the file name (supplied by MAPPER software) containing the

input report specified in the ci,di,ri subfields.

co,do Cabinet and drawer in which to place the result (must be specified if out is
specified).

ho? Append headings to the output file when it returns to the MAPPER system, Y or N.
Default = Y.

continued

7-28 7831 9274-000

 ASR (A Series Run)

continued

Field Description

out INTNAME of the output file returned to the MAPPER system. If specified, the
following filecard is added to the program:

FILE out-int (KIND=DISK,TITLE=fn-outputrpt,MAXRECSIZE=line);

out-int is the INTNAME specified in the out subfield.

fn-outputrpt is a file to return to the MAPPER system.

line is the line size of the drawer specified in the co,do subfields.

lab Label to go to if an error occurs.

fn Name of the object code file to execute.

args Arguments passed to the program, if the program takes arguments (maximum of
255 characters). Do not specify args if the program does not take arguments.

Comments
• If the file name contains spaces or if you specify arguments, enclose the
entire file name and the arguments within apostrophes ( '); however, do
not enclose variables, such as vl or v2, within apostrophes if they are
used as arguments. For example, ' *OBJECT/ABC ON PACK' or
'*OBJECT/ABC 1,CDE,'1/2.

• The input report, if specified, is file-equated to the INTNAME specified

in the i n subfield. For output, the file whose INTNAME is specified in
the out subfield is file-equated to a temporary file of the appropriate
size for the drawer.
• The i n, out, f n, and a rgs fields are case sensitive. The file name ABC
cannot be accessed as abc.

7831 9274-000 7-29

ASR (A Series Run)

Examples

Run the program (NEWUSER)OBJECT/GEN/SALES/REPORT ON PACK

using a remote file, create a temporary file, which is file-equated to a file
with an INTNAME of OUTPUT, and return it as a result in cabinet 0,
drawer B:
@as r, y 0b 1
OUTPUT ' (NEWIJSER )0BJECT /GEN/SALES/REPORT ON PACK' .

Run the program *OBJECT/PROD_STATUS using a remote file and the

arguments ADD and v3:
@as r , y , n ' *OBJECT /PROD_STATUS ADD , ' v3 .

7-30 7831 9274-000

 AUX (Auxiliary)

AUX (Auxiliary)
'This section does not apply to the BTOS II MAPPER System.
The Auxiliary (AUX) statement sends a report or result to an auxiliary
printer connected to a display terminal.
V 1100: On OS 1100 MAPPER Systems, you can also send reports or results to
other kinds of auxiliary devices, such as diskette devices.
Format
@AUX,c,d,r,sn,[dev,dinos?,1 ,tabs1,dhdgs1,d1char?,Isp,transp?,
unit ,s1,spcc] .

Following is a description of the subfields:

Field Description

c,d,r Report to print.

sn Station number where the auxiliary printer is connected.

dev Auxiliary printer device name. Default = COP. To specify a device other than
the default, see the coordinator.
1100: On OS 1100 MAPPER Systems, you can specify devices other than
printers. Also, this subfield is not optional; there is no default.

dins? Delete the line numbers, Y or N. Default = N. Use Y if the report is 132
characters and you are printing in basic format.

f Report format to be printed. Default = basic format.

V 1100: On OS 1100 MAPPER Systems, default = basic format or, if a report
was on display, the fields currently displayed by means of the VIEW function
or those selected by an FMT or SFC run statement.

1100: tabs? Include tab characters in the output, Y or N. Default = N, change them to
spaces.

dhdgs? Delete the report headings and end report line in the output, Y or N.
Default = N.

dichar? Delete the first character of each line in the output, Y or N. Default = N.

Isp Line spacing (1, 2, or 3). Default = 1.

continued

7831 9274-000 7-31

AUX (Auxiliary)

continued

Field Description

V 1100: transp? Print reports exceeding 132 characters, write lines exceeding 80 characters
(for cassettes and diskettes), Y or N. Default = N.

V 1100: unit Unit on which to locate data in subsequent search operations. (This subfield
is applicable only for cassettes and diskettes.)

sl Site letter of the station to which the printer is attached. Default = local site.
1100: This subfield is not available on OS 1100 MAPPER Systems.

spcc Special print control character used to specify printer device controls.
Default = blank, printer ignores control characters in text and prints them
literally.

The usual printer device control code is a tilde (-). To change the control
character, see the Manual Functions Reference.

Comments
• An AUX statement does not create a result.
• You can direct output from an AUX statement to configured stations
only.
Note: For printing to start, the sign-on screen must be displayed on the
terminal connected to the specified printer.
• For more information on printing, such as suspending or stopping
printing or emphasizing text, see the Manual Functions Reference.
Example
Print report 2B0, at station 9 on device name COP with deleted line
sequence numbers, deleted headings, and double spacing:
@aux,0,b,2,9,cop,y„,y„2 .

7-32 7831 9274-000

 BFN (Binary Find)

BFN (Binary Find)

The Binary Find (BFN) statement finds items very quickly in sorted reports
by sampling the data at midpoint in the report or series of reports to
determine whether the data to be found precedes or follows this point
(therefore the term binary). With the N or 0 option, it creates a result.
Format
@OFN,c,d[,r,l,lab] o cc Ityp,p [vrpt,y1no] .

Following is a description of the fields and subfields:

Field Description

c,d,r Report to scan.

I Line number where the binary find starts its first sample.

Designating a line number slightly before the general location of the data speeds
up the binary find process. If the data is actually located before the line number
specified, the BFN statement searches the entire report to find the data. Use a
Find (FND) statement if you want to locate data after a specific line.

lab Label to go to if no finds are made or in case of an error.

o Options field (see Options).

cc Column-character positions or names of the fields to scan.

Ityp Line type to scan (if you specify the A option, you can leave this subfield blank, but
enter the comma).

p The item to find. Addition& find parameters:

K Designates fields to compare (use with N, K, B, or @ option)

= Designates result field (use with B or N option)
=N Designates integer subtotal field (use with N option)

vrpt Variable to capture the report number where the find was made.

continued

7831 9274-000 7-33

BFN (Binary Find)

continued

Field Description

vino Variable to capture the line number where the find was made.

If no finds are made, the first variable contains the report number where a find
should have been made; the second variable gives the line number preceding the
line where a find should have been made.

With the 0 option, four variables are produced:

1st Number of finds

2nd Number of lines in the result
3rd Report number of the first find
4th Line number of the first find

Options
A Processes all line types.
B Builds an index containing the first data line of each report. Use
an index to speed up the find operations across multiple reports.
Enter a K in the p (parameter) field for the target field or fields.
Be sure the targets do not cross reports.
V 1100: On OS 1100 MAPPER Systems, targets may cross reports.
With the B option, the BFN statement creates a result that you
must replace into the report immediately preceding the first
report of the specified range.
If you would like the report numbers where the target items
reside placed in a field, enter an equal sign in the corresponding
parameter field.

7-34 7831 9274-000

 BFN (Binary Find)

If any reports in the range of reports are empty (headings only),

you must add one blank line into the empty report before
building the index. After the index is built, delete the blank line.
V 1100: On OS 1100 MAPPER Systems, empty reports may exist
within the range of reports being processed.
C(S) Distinguishes between uppercase and lowercase letters.
V 1100: C(x) Alters the find process based on the character set order.
Ordinarily the system processes the report based on the
character set of the drawer. The C option allows you to choose
the character set type on which to base the find. Use one of the
following:
C(F) Full character set (FCS)
C(L) Limited character set (LCS)
C(S) Strict comparison; distinguishes between uppercase
and lowercase letters.
E Displays last item only if the target item appears more than
once. Do not use this option with the 0 option.
Fn,n,... Specifies the order of sorted fields when searching multiple
fields. For n, type the corresponding sort parameter you used for
the fields from left to right.
I[n] Uses the index in drawer at report n. Enter only I for the
default report (report 2); the BFN statement scans report 2 or
report n to determine where to find items, assuming that the
reports having data to scan follow the index report.
K Verifies that reports are sorted in ascending order. Enter a K in
the corresponding parameter field. Note that when you specify
the K option, the BFN statement tests each line of every report
specified, so use it with discretion on large databases.
N Creates a result containing the last occurrence of each different
character string found in the specified field and the number of
occurrences of each string. Do not use this option with the 0
option. See the Manual Functions Reference for details.

7831 9274-000 7-35

BFN (Binary Find)

O Creates a result containing the items found. (Also, you can

capture the information in four variables instead of just two, as
previously described.) Do not use this option with the E or N
options.
P Includes trailer lines (all line types other than the target line
type) from the last valid find in the result (valid only with the N
option).
Q Quickly finds an item that appears only once in the report. Use
the Q option if you know that the item appears only once in the
report. When used with the 0 option, no trailer lines are
included.
Rx[-y] Scans a range of reports from report number x to report y.
Normally, when you process all reports in a drawer, report
numbers 1 and 2 are skipped. You can use the R option to
specify a range of reports, including reports 1 and 2. Note that
you must specify a range; it cannot be a series of selected reports
such as R3,5-10. All reports in the range must exist.
S Scans each report separately (data does not have to be sorted
across all reports).
U Sets an update lock on the report in which the find is made (or
would have been made).
Finds the first blank line or fields within a report (use to find a
place to enter data). Use this option in runs that write blank
lines at the end of the report. When a blank field is found, it is
the first blank field after the last line with data in it. If lines
with blank fields are interspersed with lines containing data, the
blank fields are not found.
When using the @ option, enter a K in the corresponding
parameter field.
Finds a slant as data.

7-36 7831 9274-000

 BFN (Binary Find)

Reserved Word
STAT1$ contains one of the following codes in case of an error:
1 Data not found
2 All lines with space fields filled (@ option)
3 Data not sorted
Comments

• If you do not specify an N or 0 option, you must examine the variables

to determine where the find was made.
• Before executing the BFN statement, be sure the data is sorted (across
reports, if processing a range of reports) on the fields or partial fields to
search.
• If the BFN statement detects a sort order discrepancy, does not find
data, or does not find blanks when looking for them, it gives control to
the label specified in the statement.
• If a find is made, the report in which the find is made becomes the
current -0. Any previous -0 result is released.
• If you specify a range of reports, make sure there are no empty reports
(containing no valid data or headings only) within the range. If the BFN
statement encounters an empty report, then finds the data that matches
the search criteria in a subsequent report, it ignores any reports
preceding the empty report. In this case, no system message is supplied
because a valid find is made.
V 1100: On OS 1100 MAPPER Systems, empty reports may exist within
the range of reports being processed.

7831 9274-000 7-37

BFN (Binary Find)

Example 1: Finding All Occurrences of an Item

Find all occurrences of blackbox4 in report 1CO:
o 'producttype' ❑ ,blackbox4 .
where:
0,c,1 Searches report 1C0
o Creates a result (0 option)
'producttype' Searches the Product Type field
❑ Processes tab lines only
b I ackbox4 Finds blackbox4s
Example 2: Finding the Only Occurrence of an Item
Use the Q option to quickly find the only blackbox4, and capture the line
number where the find is made in <line>:
@bin,O,c,1„099 q 2-9 ❑ ,blackbox4 ,<Iine>i3
where:
0, c,1 Searches report 'CO
099 Goes to label 99 in case of no finds or an error
q Quickly finds the item (Q option)
2-9 Looks in the Product Type field (column 2 for 9
characters)
❑ Processes tab lines only
blackbox4 Finds the only blackbox4
< I i ne> Captures the line number where the find is made in
variable <line>

7-38 7831 9274-000

 BFN (Binary Find)

Using the IBFN Run to Create a BFN Statement

'This section on using the IBFN run applies only to the OS 1100 MAPPER
System.
You can use the Iterative Binary Find (IBFN) run to create a BFN
statement. For information on how to use the iterative runs, see the Manual
Functions Reference.

7831 9274-000 7-39

BR (Background Run)

BR (Background Run)
This section does not apply to the OS 1100 MAPPER System. See "BR
(Background Run): OS 1100" in this section for a description of the BR
statement as it applies to the OS 1100 MAPPER System.
The Background Run (BR) statement starts a MAPPER run at your site and
executes it in background, allowing you to continue executing other
functions and runs at your terminal.
The system removes the current (-0) result from the run, if one exists, passes
it to the background run, and starts the run in background. The run
containing the BR statement then continues at the next statement.
Format
@BR[,c,d,r] run[,vld] .

Following is a description of the subfields:

Field Description

c,d,r Report to pass as a -0 result to the background run. Default = current -0 (the
system removes the current result from your run, if one exists, and passes it to the
background run).

run Name of the run.

vld Variables, literals, reserved words, constants, or any combination of these, to be

picked up by the background run via 1NPUT$. You can pass up to 40 variables;
however, the maximum total number of characters for the run and vld fields
together is only 200 characters.

Reserved Word
ORSTAN$ contains the station number that started the background run
(contains zero if the run is not being executed in background).

7-40 7831 9274-000

 BR (Background Run)

Comments
• You cannot use the following statements in a background run: DSG,
DSM, DSP, DSX, GOC (when display requested), GS (when display
requested), HST, ITV, OTV, OUM, OUT, OUV, RDB, REL, SC, XIT, or
XUN statements in a background run.
Note: Since this list encompasses several different kinds of MAPPER
systems, some run statements may not be available on your
system.
• A Return Remote (RTN) statement in a background run sends the
specified report to the calling terminal.
• If the background run fails, the run user receives a message indicating
there was an error.
• To check the status of the run, use the System function.
• To terminate an active background run, use the Kill function. To
terminate a queued background run, contact the MAPPER system
coordinator.
Example
Start the test run, pass the letters abed as input to the run, and pass
report 2B0 for processing in the run:
@br,O,b,2 test ,abcd .
The run containing the BR statement continues at the next statement after
the background run starts.

7831 9274-000 7-41

BR (Background Run): OS 1100

BR (Background Run): OS 1100

This section applies only to the OS 1100 MAPPER System. See
"BR (Background Run)" in this section for a description of the BR statement
as it applies to other MAPPER systems.
The Background Run (BR) statement starts a MAPPER run and executes it
in background, allowing you to continue executing other functions and runs
at your terminal.
The system removes the current (-0) result from the run, if one exists, passes
it to the background run, and starts the run in background. The run
containing the BR statement then continues at the next statement.
Format
OR[,sn,lab] run[,vid] .

Following is a description of the subfields:

Field Description

sn Station number to be notified when the background run completes. Default = no

station notified.

lab Label to go to if the number of active background runs has already reached the
maximum allowed at your site. Default = run containing the BR statement stalls
until the background run is able to start.

run Name of the run.

vld Variables, literals, reserved words, constants, or any combination of these, to be

picked up by the background run via 1NPUT$. You can pass up to 40 variables;
however, the maximum total number of characters for the run and vld fields
together is only 640 characters.

Reserved Word
ORSTAN$ contains the station number from the s n subfield of the BR
statement that started the run, or the originating station number if not
supplied in the BR statement (contains zero if the run is not being executed
in background).

7-42 7831 9274-000

 BR (Background Run): OS 1100

Comments
• Have the coordinator register the run in one of the following ways:
As a normal run eligible for background execution (you can execute
the run either normally or in background)
As a background run only
• You cannot use the following statements in a background run: DSG,
DSM, DSP, DSX, GOC (when display requested), GS (when display
requested), ITV, OUM, OUT, OUV, REL, RSI, SC, XIT
• You can use the DSG, OUT, and SC statements if you send the output to
another terminal.
• In addition to the statements listed above, the background run must not
contain a BR statement. In other words, a background run may not
start another background run.
• If the background run fails, the run user receives a message indicating
there was an error.
• To check the status of the run, use the Run Status (RS) function.
• To terminate an active background run, use the Stop function.
Example
Start a background run and transfer data to it:
@br ,123,099 test ,abcd
where:
123 Notify station 123 when the background run completes.
099 Go to label 99 if the number of active background runs has
already reached the maximum at this site.
test Start the run named test.
abcd Pass the literal value abcd as input to the run.
The run containing the BR statement continues at the next statement after
the background run has started.

7831 9274-000 7-43

BRK (Break)

BRK (Break)
The Break (BRK) statement turns the output area of a run into the current
-0 result and creates a new output area (containing only a date line).
Format
CiERK[,c,d,qj .

Following is a description of the subfields:

Field Description

c,d Cabinet and drawer letter of the new output area. The drawer letter is required if a
cabinet is specified. Default = cabinet and drawer of the run control report or
cabinet and drawer specified on a previous BRK statement.

1100: q Estimated number of output lines. For output exceeding 500 lines, estimating
improves efficiency by reducing I/Os.

Comment
• When a run encounters a BRK statement, all data currently in the
output area becomes the current result, -0 and a new, empty output area
(containing only a date line) is created. If you specify a cabinet and
drawer, the location of the current result is not affected. However, the
new output area is placed into the specified cabinet and drawer.

7-44 7831 9274-000

 BRK (Break)

Examples
This example uses multiple BRK statements:
1. @b rk .
Datal
2. @brk,O,b .
Da ta2
3. @brk .
Da ta3
4. @brk .
Statement 1. The current output area resides in the same cabinet and
drawer as the run control report.
Statement 2. Following this statement, Da t a1 is the current -0 which is
in the same cabinet and drawer as the run control report.
The new output area however, resides in cabinet 0, drawer
B.
Statement 3. Following this statement, Da t a2 is in the -0 result in
cabinet 0, drawer B.
Statement 4. Following this statement, Da t a3 is in the -0 result in
cabinet 0, drawer B.
V 1100: This example applies only to OS 1100 MAPPER Systems.
This example places the output area into a result and estimates that the
following output area will be 2,500 lines:
@br k „ ,2500 .

7831 9274-000 7-45

CAL (Calculate)

CAL (Calculate)
The Calculate (CAL) statement performs arithmetic calculations and
conditional evaluations on reports or results, creating a result (except with
the 0 option). See the Manual Functions Reference for details on the CAL
function.
To create an update result that allows you to blend the changed lines back
into the original report or delete lines from the original report, use the
Calculate Update (CAU) statement. The CAU statement uses the same
fields and subfields as the CAL statement. See the online help system
(HELP,@CAU) for more information.
Format
WAL,c,d,r[,l,q,leb] o cc Ityp,p eq [vrelts]

Following is a description of the fields and subfields:

Field Description

c,d,r Report to process.

Line number at which to start processing.

q Number of lines to process.

lab Label to go to if no data exists. (Be sure to use this field if there is any possibility
that the report does not contain data; otherwise, no result is created.)

o Options field (see Options).

cc Column-character positions or names of the fields to process.

ltyp Line type to process. If you specify the A option, you can leave this subfield
blank, but enter the comma.

p Parameters:

Alphabetic field labels

Vertical operators (+,/,<, and >)

continued

7-46 7831 9274-000

 CAL (Calculate)

continued

Field Description

eq Equations in the format:

receiving-label[,options]=expression[;...]

receiving-label can have alphabetic field labels, or one- to six-alphabetic character

value labels including the characters $, %, !, and ?. (It can also have constant
label LT.)

Note that receiving-label can be a partial label in the format:

receiving-label(x-y)

x is the starting column and y is the number of characters.

options are equation options E, I, J(x), Kn, Nn, Rn, V, X, and *. Use them to
specify options on individual equations. To remove a function option from an
equation, enter a minus sign (-) after the equation option. For example, J-, K-, V-,
and so on.

expression is a combination of one or more operands and zero or more operators

regarded as a single numeric value.

Separate multiple equations with a semicolon ( ; ).

vrsits Variables to capture the results of vertical operations and the contents of value
labels in the order initialized. Variables that capture vertical operations are loaded
in the order their fields exist in the report.

Options
A Processes all line types.
C Conditionally displays specific result lines. After all equations
are processed, include only those lines that meet a true condition
based on the last If Conditional (IF) statement in the result. For
example, if the last IF statement is IF:A=0, include only lines
where field A is equal to zero in the result.
E Erases fields (fill them with spaces) if the answer equals zero.
I Produces integer results, truncating any fractional part
(numbers to the right of a decimal point) in the result.

7831 9274-000 7-47

CAL (Calculate)

J(x) Justifies the numeric result value, where x is one of the following
justification options:
C Inserts commas in the integer portion every three digits,
eliminating nonsignificant zeros. Places the resulting
value in the leftmost portion of the field.
L Left-justifies and eliminates nonsignificant zeros. Places
the resulting value in the leftmost portion of the field.
R Right-justifies and eliminates nonsignificant zeros.
Places the resulting value in the rightmost portion of the
field.
X Eliminates leading nonsignificant zeros. Places the
resulting value in the leftmost column and fill the
remaining columns with zeros.
Z Eliminates nonsignificant zeros, right-justify, and fills
the preceding columns with zeros.
Kn Initializes a value label to n. Default value = 0.
L Lists all value label names and their final values at the end of
the result.
Nn Substitutes the numeric value of n for nonnumeric fields. The
default value of nonnumeric fields is zero. A nonnumeric field
has either no data (all space or tab characters) or data that has a
nonnumeric character in its leftmost significant position.
0 Omits result. Only receiving variables are loaded.
Rn Rounds results to the nearest n: R.0000000000000001 through
R100000 (nearest 100,000 units).
Note: To control rounding by equation, use R as an equation
option.

7-48 7831 9274-000

 CAL (Calculate)

S(s) Distinguishes between uppercase and lowercase characters

when processing character strings.
V 1100: S(x) Defines character set interpretation as x (F, L, or S). Note that
the system compares limited character set (LCS) strings to LCS
internal codes, full character set (FCS) strings to FCS internal
codes, and interprets uppercase and lowercase characters the
same.
F Use FCS internal codes. Use only when processing LCS
reports.
L Use LCS internal codes. Use only when processing FCS
or full character set upper (FCSU) reports.
S Use strict character set internal codes to differentiate
between uppercase and lowercase characters. Only with
FCS reports.
T Includes both processed and unprocessed lines in the result. Do
not use if you want to include only the line type being processed.
V Processes only those equations whose result values are
calculated from valid data. Equations containing invalid data
are not included in the result, and the receiving label is not
altered. See the note following this options list.
X Excludes invalid values in minimum, maximum, sum, and
average computations (MIN, MAX, SUM, AVG, VMIN, VMAX,
VSUM, VAVG), as well as in functions specified by vertical
operators. See the note following this options list.
* Flags all invalid results with an asterisk following the value.
See the note following this options list.
Note: Invalid data includes field labels representing nonnumeric data and
value labels whose value was calculated from nonnumeric data or an
invalid date. Nonnumeric fields are fields containing either
nonnumeric data in the leftmost column of the field or no data.

7831 9274-000 7-49

CAL (Calculate)

Reserved Words
STAT1$ contains the number of lines processed (of the line type specified).
STAT2$ contains the total number of lines in the report (excluding
headings).

Priority of Operations
Table 7-5 shows the priority by which the calculator performs arithmetic
operations.

Table 7-5. CAL: Priority of Arithmetic Operations

Priority Operator Operation

First - Unary Minus

Second ** Exponentiation

Third *,/,// Multiplication, Division, Integer Division

Fourth +,- Addition, Subtraction

7-50 7831 9274-000

 CAL (Calculate)

Table 7-6 shows the priority by which the MAPPER system evaluates
relational operations.

Table 7-6. CAL: Priority of Relational Operations

Priority Operator Relational Operation

First = Compare equal to

<> or >< Compare not equal to

> Compare greater than

<= or =< Compare not greater than (less than or equal to)

< Compare less than

>= or => Compare not less than (greater than or equal to)

Second & AND (Boolean)

Third OR (Boolean)

Note: The operators ampersand and comma (& and ,) do not perform a
numeric comparison but are based on a true 1 false concept. See the
Manual Functions Reference for details on using relational and
logical operators.

7831 9274-000 7-51

CAL (Calculate)

True/False Conditions

Table 7-7 shows the result of all possible true/false conditions. valuel and
value2 are usually relational expressions (such as a>1000).

Table 7-7. CAL: AND and OR True/False Conditions

AND Operation OR Operation

valuel & value2 Result valuel value2 Result

False False False False False False

True False False True False True

False True False False True True

True True True True True True

Comments

• You can use the following internal arithmetic and trigonometric

functions in the equations:

ABS(x) LOG(x)
ACOS(x) LOG10(x)
ASIN(x) MAX(xl,...,xn)
ATAN(x) MIN(xl,...,xn)
AVG(xl,...,xn) MOD(x,y)
CBRT(x) RAD(x)
COS(x) RAN(x,y)
CTN(x) SIN(x)
DEG(x) SQRT(x)
EXP(x) SUM(xl,...,xn)
FRAC(x) TAN(x)
HCOS(x) VAVG(xl,...,xn)
HSIN(x) VMAX(xl,...,xn)
HTAN(x) VMIN(xl,...,xn)
INT(x) VSUM(xl,...,xn)
See Arithmetic (ART) for an explanation of these functions.

7-52 7831 9274-000

 CAL (Calculate)

• You can use variables in any field of the CAL statement, including
equations. Variables can contain entire equations or parts of equations.
Since the system interprets variables enclosed in apostrophes as literal
data (for example, the statement uses literal vl rather than the contents
of the variable v1), do not enclose variables in apostrophes.
• Use a DEF statement to produce a numeric value that defines the
contents of a report field. Use the following format:
DEF(tield•label)

Following are the report field values and what they represent:

Value Contents of Report Field

0 All tab characters or spaces or both

1 All numeric characters
2 All alphabetic characters
3 Alphabetic and numeric characters
4 All special characters
5 Special and numeric characters
6 Special and alphabetic characters
7 Special, numeric, and alphabetic characters

• You can include both characters and spaces in the contents of a report
field.
• Use the any of the following conditional statements in the equations:
IF:expression];

THEN:equation];

ELSE:equation];

FIRST:equation]; . . ]
SKIP:expression]; . . . ]
EXIT:expression]; . . . ]
For details on conditional statements, see the Manual Functions
Reference.

7831 9274-000 7-53

CAL (Calculate)

Date and Time Processing

You can use the CAL statement to perform computations on dates and
times. The CAL statement converts the date and time data to numeric
values and processes them with equations. See the Manual Functions
Reference for details on using the CAL function to process dates and times.

Character String Processing

You can use the CAL statement to manipulate character strings in reports.
Enclose all literal values in quotation marks ( " ).
V 1100: On OS 1100 MAPPER Systems, to use literal data that contains
spaces, enclose the data in apostrophes or quotation marks.
Since quotation marks are not allowed in the limited character set (LCS),
you must use the reserved word TIC$ or a variable containing an apostrophe
before and after literal data in runs residing in LCS reports.
See the Manual Functions Reference for details on processing character
strings.

Using the ICAL Run to Create a CAL Statement

You can use the Iterative Calculate (ICAL) run to create a CAL statement.
For information on how to use the ICAL run, see the online help system
(HELP,ICAL).

7-54 7831 9274-000

 CAL (Calculate)

CAL Statement Examples

Note: All CAL examples except the last one process tab lines in report 1CO.
Example 1: Multiplying Two Fields
Multiply the Space Req field by the Demo Quantity field:
@cal ,0,c, 1 " 'spacereq' , ' demoquan'
'demoresu I ts' ❑ ,a,b,c c=a*b .
where:
, Uses no options
'spacereq' Labels the Space Req field:
a Field a
'demoquan' Labels the Demo Quantity field:
b Field b
'demor esu I ts' Labels the Demo Results field:
c Field c
c=a*b Multiplies the Space Req field (a) by the Demo
Quantity field (b) and places the product in the
Demo Results field (c)
Example 2: Moving Values into Fields Based on Values
Move all values that exceed 24,000 from one field into another field:
@ca1,0,c,1 " 'retail $$$$','demoresults'
❑,a,b if:a>24000;then:b=a .
where:
Uses no options
'retai I $$$$' Labels the Retail $$$$ field:
a Field a
'demoresu Its' Labels the Demo Results field:
b Field b
i f : a>24000; Puts all Retail $$$$ field (a) values that
then:b=a exceed 24,000 into the Demo Results field (b)

7831 9274-000 7-55

CAL (Calculate)

Example 3: Averaging Items in a Field

Calculate the vertical average of the Sales Commis field:
@cal,0,c,1 r.01 42-7,65-15 ❑ ,a,b b=vavg(a) .
where:
r.01 Uses the R option, rounds result to nearest one
hundredth
42-7 Labels the Sales Commis field (column 42 for seven
characters):
a Field a
65-15 Labels the Demo Results field (column 65 for 15
characters):
b Field b
b=vav g (a) Puts the cumulative vertical average of the Sales
Commis field (a) into the Demo Results field (b)
Example 4: Testing Literal Data
The following example uses quotation marks when testing a literal value:
@ca1,0,c,1„,099 c 2-8 ❑ ,a if:a="blackbox" .
where:
099 Goes to label 99 if no data exists
c Uses the C option to include in the result
only those lines that meet a true condition
based on the last IF statement
2-8 Labels the first eight characters of the
Product Type field (column 2 for 8
characters):
a Field a
if:a="blackbox" Includes all lines with the word blackbox
in the first eight characters of the Product
Type field

7-56 7831 9274-000

 CAL (Calculate)

Example 5: Calculating Vertical Totals and Maximum Values

Calculate the vertical totals of the Retail $$$$ field and the Demo Results
field, and capture the highest value found in the Retail $$$$ field and the
Whole Sale$ field:
@c a ,O, c , 1, „ 099 I 25-7,33-8,65-15 0 , a , b+, c+
maxa=vmax(a) onaxb=vmax(b);c=b-a v1 i 9 , v2 i 9,1
v3 i 9 , v4 i 9 .

where:
099 Goes to label 99 if no data exists
Uses the L option to list all value label names
and their final values at the end of the result
25-7,33-8,65-15 Labels the Whole Sale$ field (column 25 for 7
characters), the Retail $$$$ field (column 33 for
8 characters), and the Demo Results field
(column 65 for 15 characters):
a , b+, c+ Fields a, b, and c, with the vertical operator + on
fields b and c
maxa=vmax(a); Puts the highest value found in the Whole Sale$
field (a) in the value label maxa
maxb=vmax(b); Puts the highest value found in the Retail $$$$
field (b) in the value label maxb
c=b-a Subtracts field a from field b and puts the
difference in field c
v1i9,v2i9, Captures the vertical total of Retail $$$$
v3i9,v4i9 (field b) in vl, the vertical total of Demo Results
(field c) in v2, the contents of the MAXA value
label in v3, and the contents of the MAXB value
label in v4

7831 9274-000 7-57

CALL (Call Subroutine)

CALL (Call Subroutine)

The Call Subroutine (CALL) statement saves the contents of all variables
currently defined in the run and transfers control to an internal or external
subroutine.
You can pass up to 40 variables to the subroutine. You can manipulate
these variables within the subroutine and pass them back to the calling run
without affecting any of the other currently defined variables.
V 1100: On OS 1100 MAPPER Systems, you can also pass parameters that the
system does not change upon return to the calling run.
Format
WALL[,c,d,r] lab ([v,v,...]) .
V 1100,
WAL14,c,d,r] lab ([p o p,...]) .
Following is a description of the fields and subfields:

Field Description

c,d,r Report containing an external subroutine.

lab Label where subroutine begins.

At the subroutine label, you must include the parentheses and a

corresponding variable for each variable passed on the CALL statement. Use
the following format for the label:

@lab:(v,v,...)

continued

7-58 7831 9274-000

 CALL (Call Subroutine)

continued

Field Description

(v,v...) Variables to pass to the subroutine (maximum of 40). Parentheses are

required (even if you do not pass any variables).

'' 1100: (p,p...) Parameters to pass to the subroutine (maximum of 40). Parentheses are
required (even if you do not pass any parameters). Enter one of the following
kinds of parameters:

v Variable (system returns the new value from the subroutine).

*v Variable (system retains the original value from the calling run).

'string' Literal character string, up to 256 characters. Enclose each

string in apostrophes ( ' ). To pass an apostrophe, use two
apostrophes ( " ).

At the label, enter variables for the strings. The system

initializes these variables as S type variables of the same size
as the strings.

Comments
• The statement returns only the -0 result created in the subroutine and
the variables that you passed with the CALL statement. Renamed
results (-1 to -8) remain unchanged.
• Use the RETURN statement to exit the subroutine and return to the
line following the CALL statement.
• To pass all the variables in an array, specify only the name of the array;
to pass a specific array member, specify the array name and member
number ([n]). An entire variable array counts as one variable of the 40
allowed. See LDA in this section.

7831 9274-000 7-59

CALL (Call Subroutine)

• Variables you pass with the CALL statement have a one-to-one

relationship with the variables specified at the label. MAPPER software
equates these variables by their position in the statement, not by their
name. That is, the first variable in parentheses is equated with the first
variable of the CALL statement, and so on.
If the subroutine modifies the value of a variable in parentheses, the
system passes the new value to the equivalent variable in the CALL
statement.
• Any changes you make to variables you passed to the subroutine using
the CALL statement still exist when control returns. Variables you did
not pass to the subroutine remain unchanged when control returns to
the calling run.
• Within the subroutine, you can use up to 199 variables (or the number
configured for your site, up to 399), less the number of variables
previously defined. Since you can pass up to 40 variables with the
CALL statement, you can initialize and use up to 159 (or up to 359)
additional variables within that subroutine, less the number previously
defined.
V 1100: On OS 1100 MAPPER Systems, you can use the system limit of
variables both in the calling run and in the subroutine.
When control returns to the calling run, the system returns only the
variables specified on the CALL statement. The system releases all
variables initialized within the subroutine.
• You can nest up to ten CALL subroutine levels (internal or external).
The system keeps track of up to ten sets (levels) of variables. Each time
you issue a CALL or Link to Another Run (LNK) statement, the system
saves a level.
V 1100: On OS 1100 Systems, the syse,cal aavca a each time y ou issue
a CALL statement, not a LNK statement.
• If you pass a string variable in a CALL statement, you cannot modify its
size.
V 1100: On OS 1100 Systems, you cau modify the size of string variables.

7-60 7831 9274-000

 CALL (Call Subroutine)

• The total number of variables used in all CALL statements cannot

exceed 199 (or the number configured for the run).
V 1100: On OS 1100 Systems, you can use the system limit of variables in
each of the CALL statements.
• Error routines registered in called routines override previously
registered error routines; however, when control returns to the calling
run, the system automatically reregisters the original error routine.
V 1100: On OS 1100 Systems, error routines registered in called routines
do not override previously registered error routines.
• If you do not register an error routine in the called routine, in case of an
error, control goes to the error routine in the calling run.
V 1100: On OS 1100 Systems, if the run fails, the system cancels all active
subroutines.
• Do not place other run statements on the same line after the CALL
statement. Other run statements following it on the same line are
ignored. Put the next run statement on a new line.

7831 9274-000 7-61

CALL (Call Subroutine)

Example 1

This statement transfers control to label 054 and passes only v102 and v103
to the subroutine. The subroutine uses the values of v102 and v103 for
<drw> and <line>, respectively.
@I dv v101 i 4=1234,v102h1=b, v103 i4=5
@ca l 054 (v102, v103) .

. (other processing)

@054:(<drw>,<Iine>) .
@fnd,0,<drw>„<line> a 'cunt' kamco <rpt>i4,<Iine> .
@return .
In the example, when control returns, the variables used in the main routine
and subroutine have been affected as follows:
• V101 still contains 1234 because it was not passed to the subroutine.
• V102 (<drw> in the subroutine) still contains the letter b because the
subroutine did not change it.
• V103 (<line> in the subroutine) contains a new value because the Find
(FND) statement in the subroutine changed it.
• <rpt> is not defined any longer because it was used only in the
subroutine.

7-62 7831 9274-000

 CALL (Call Subroutine)

Example 2

This statement transfers control to label 99 and passes v102, v103, and
v104. The subroutine uses the values of v102, v103, and v104 for <scan>,
<item>, and <qty>, respectively.
@ca I I 099 (v102,v103,v104) .

. (other processing)

t2099:(<scan>,<item>,<qty>) .

.(other processing using <scan1>, <item>, and <qty>)

@srh,0,b dha 'product type' I,<item> <qty>,<scan>

.(other processing)

@return .

The system returns v102, v103, v104, and the -0 result created in the
subroutine. All other variables remain unchanged since you did not pass
them to the subroutine.

7831 9274-000 7-63

CALL (Call Subroutine)

Example 3

1100: This example applies only to OS 1100 MAPPER Systems.

This statement transfers control to label 100 and passes v101 and v102.
The asterisk (*) before v102 specifies that its value be retained upon return
to the calling run, even if it is changed in the subroutine. The subroutine
changes both variables.
@ca I I 100 (v101,*v102) .

. (other processing)

@100:(<datal>,<data2>) .
@I dv <da ta1>=5000,<da ta2>=2500 .
@return .

The system returns 5000 in v101, but does not change v102 because it was
preceded with an asterisk when passed with the CALL statement.
Example 4
V 1100: This example applies only to OS 1100 MAPPER Systems.
This statement transfers control to label 100 and passes v101 and strings
hokey and pokey. The subroutine automatically initializes <data2> and
<data3> as S type variables of the same size as the strings.
@call 100 (v101,'hokey', 1 pokey') .

. (other processing)

@100:(<datal>,<data2>,<data3>) .
The system returns the current value of v101, but does not return any
variable comparable to <data2> or <data3>.

7-64 7831 9274-000

 CHD (Command Handler)

CHD (Command Handler)

The Command Handler (CHD) statement registers a routine to be executed
when the user of the run enters information in the control line after a
Display Message (DSM), Display Report (DSP), Output (OUT), or Screen
Control (SC) statement.
Note: Do not use the CHD statement unless you are an advanced run writer.
It is intended primarily for intercepting and interpreting commands
that normally go to MAPPER software.
Format
@CHD[,c,d,r,rel?] lab .

Following is a description of the field and subfields:

Field Description

c,d,r Report that contains a command handler routine. (Specify only if the routine is in
another run control report.)
V 1100: The report containing the command handler routine must be in ll-^ —
character set type as the calling run control report.

rel? Transfer release control (") to the run, Y or N. Default = N. If you specify Y, the
run user cannot execute the Release Display (") function because the caret (-) is
intercepted by the run.

lab Label where the command handler routine starts. Use 0 to cancel the currently
registered command handler routine. To begin the routine at the first line of the
external run control report, use LIN1 in this field.

Reserved Words
ICVAR$ captures user input from the control line whenever the user
transmits from the control line. Follow these guidelines when using
ICVAR$:
• Use only with a CHD statement.
• Place ICVARS before the variable in the CHG statement, and put the
CHG statement before the DSM, DSP, OUT, or SC statement.

7831 9274-000 7-65

CHG (Change Variable)

CHG (Change Variable)

The Change Variable (CHG) statement initializes or redefines the contents
of variables. See Section 4 for more information on initializing and
redefining variables.
Format
(CHG v (explvld} .

or
CHG rw v[,v...,v]

Following is a description of the fields and subfields:

Field Description

v Variable you are changing. To define or redefine the variable, include the variable
type and size.

exp Expression by which you want to set the value of the variable.

vid Value to place into the variable. You can specify the value using a variable, literal,
constant, or reserved word.

rw Reserved word that determines the kind of input data you want to capture in the
variable.

Reserved Words
You can use only the following reserved words to capture user input with the
CHG statement:
ICVAR$ (see CHD)
INMSV$ (see OUM)
INPUT$ (see OUT)
INSTR$ (see OUT)
INVAR$ (see OUT)
INVR1$ (see OUT)
Put reserved words that capture user input before the variable.

7-68 7831 9274-000

 CHG (Change Variable)

Examples

Set the value of <commission> with the solution of a simple expression:

@chg <commission> <sales> * <percent> .

Capture the current input in <name>, <address>, and <phone>:

@chg input$ <name>,<address>,<phone> .

Capture the next input entered on the control line in <controlln>:

@chg icvar$ <control In> .

Using Expressions
You can use variables, constants, reserved words, and the following
operators in a CHG statement expression:
addition (+)
subtraction (-)
multiplication (*)
division (/)
integer division (If)
Precede each operator with a space. If you include a variable in the
expression, the variable must have been defined prior to the CHG
statement.
The system evaluates the expression from left to right, following no
precedence rules. Therefore, use only simple expressions with the CHG
statement.

Guidelines for Addition and Subtraction

Follow these guidelines when adding or subtracting with variables:

• A type variables:
Produce numeric results whenever the variable contains numbers.
Type A variables containing letters or special characters produce a
result based on the order of the character set of the run control report
(for example, A + 1 = B).

7831 9274-000 7-69

CHG (Change Variable)

• H type variables:
Produce a result based on the order of the character set, even for
numbers (for example, 9 + 1 = : , not 10 [this assumes that the number 9
was right-justified in the variable]).
V 1100: On OS 1100 Systems, the example also assumes the run control
report is in a full character set drawer.
• S type variables:
Produce a result based on the order of the character set, even for
numbers.
• 1100: 0 type variables:
Produce octal answers.
• To simply increase or decrease the numeric value of a variable, use the
Increment Variable (INC) or Decrement Variable (DEC) statement.

Processing Octal Variables

This section on processing octal variables applies only to the OS 1100
MAPPER System.
You can use the following operators with octal (type 0) variables:
A Logical AND
O Logical OR
X Exclusive OR
L Left shift (also -)
R Right shift (also +)
C Circular shift
A shift of a type 0 variable is actually a bit-count shift. If the data being
loaded is a literal value, MAPPER software assumes an octal value. If the
data resides in another variable, MAPPER software assumes a decimal
value and converts it to octal before processing.

7-70 7831 9274-000

 CHG (Change Variable)

Examples
Initialize <testoctal> as a four-character octal variable with an initial value
of 2:
@chg <testoctal>o4 2 .

Perform a logical AND of the contents of <testoctal> with the number 7:

@chg <testoctal> <testoctal> a 7 .

Perform a shift on the contents of <testoctal> to the left one bit:

@chg <testoctal> <testoctal> L 1 .

7831 9274-000 7-71

CMP (Compare Report)

CMP (Compare Report)

The Compare Report (CMP) statement compares the contents of a report or
result with another report. The CMP statement performs a character-
to-character comparison between the two reports. If any character
differences are detected, the variables are loaded with their line numbers
and column character positions and the run continues at the label (if
specified).
Format
CICMP,c1,d1,r1,[11n1],c2,d2,r21,11n2,q,lan o ccl Itypl,pl cc2
Altyp2,p2 [vInol,vcoll,v1no2,vco12] .

Following is a description of the fields and subfields:

Field Description

cl,dl,rl Report to compare.

linl Line number in the first report at which to begin the comparison.
Default = line 2.

c2,d2,r2 Report to compare with the first report.

lint Line number in the second report at which to begin the comparison.
Default = line 2.

q Number of lines to compare. Default = all.

lab Label to go to if the statement detects a difference.

0 Options field (see Options).

ccl Column-character positions or names of the fields to compare in the first

report.

4131 Line type to compare in the first report. If you specify the A option, leave this
subfield blank but enter the comma.

Al Parameters for the first report.

continued

7-72 7831 9274-000

 CMP (Compare Report)

continued

Field Description

cc2 Column-character positions or names of the fields to compare in the second

report.

Ityp2 Line type to compare in the second report. If you specify the A option, leave
this subfield blank but enter the comma.

p2 Parameters for the second report.

vinol Variable to capture the line number in the first report where the fields are not
identical.

vcoll Variable to capture the column in the first report where the fields are not
identical.

Owl Variable to capture the line number in the second report where the fields are
not identical.

vcoll Variable to capture the column in the second report where the fields are not
identical.

Options
A Processes all line types. Each line is compared regardless of line
type.
C(S) Distinguishes between uppercase and lowercase letters.
V 1100: On OS 1100 MAPPER Systems, this option applies only to
full character set (FCS) reports.

7831 9274-000 7-73

CMP (Compare Report)

Examples
Compare reports 2D0 and 3D0:
@cmp,0,d,2,6,0,d,3,6,20,099 " 12-9,61-17 *,1,2 \
12-9,61-17 *,1,2 v1i4,v2i3,v3i4,v4i3 .
where:
0,d,2,6 Compares twenty lines, beginning at line 6, in
0,d,3,6,20 reports 2D0 and 3D0
099 Goes to label 99 if the report fields are not the same
Uses no option
12-9,61-17 Compares column 12 for 9 characters and
1,2 column 61 for 17 characters in the issuing report
12-9,61-17 with column 12 for 9 characters and column
1,2 61 for 17 characters in the receiving report
Compares asterisk lines only
v1i4,v2i3, If the report fields are not the same, captures
v3 i 4, v4 i 3 issuing and receiving report line numbers and
columns where the reports are not identical in v1, v2,
v3, and v4
The run continues at the next run statement if the report fields are the
same.

7-74 7831 9274-000

 CMP (Compare Report)

Compare reports 1C0 and 2C0:

@tmp,0,c,2,15,0,c,1,22,5,001 a 2-79 ❑ ,1 2-79 ❑ ,1 1
v1i4,v2i3,v3i4,v4i3 .
where:
0,c , 2,15 Compares five lines, beginning at line 15 in report
0, c, 1,22,5 2CO3 and five lines, beginning at line 22 in report
1 CO.
001 Goes to label 1 if the reports are not the same.
a Compares all line types (line 15 compared to line 22
regardless of line type).
2-79 Compares column 2 for 79 characters in the issuing
report.
2-79 with column 2 for 79 characters in the receiving
report.
❑ Processes tab lines (but A option overrides this
subfield and compares all line types).
v1i4, v2 i 3, If the report fields are not the same, captures
v3 i 4, v4 i 3 issuing and receiving report line numbers and
columns where the reports are not identical in vl, v2,
v3, and v4.
The run continues at the next run statement if the report fields are the
same.

7831 9274-000 7-75

CMP (Compare Report)

Compare reports 2B0 and 1CO:

Cbcmp,O,b,2„0,c,1„15 c(s) 15-9 ❑ ,1 2-9 ❑ ,1 1
v1 i4,v2i3,v3i4,v4i3

where:
0, b , 2 Compares fifteen lines, beginning at line 2
0,c,,1, ,15 (default) in reports 2B0 and 1CO.
c(s) Detects uppercase and lowercase differences.
15-9 Compares column 15 for 9 characters in the
2-9 issuing report with column 2 for 9 characters in the
receiving report.
❑ Compares tab lines only.
v1i4,v2i3, If the report fields are not the same, captures
v3 i 4, v4 i 3 issuing and receiving report line numbers and
columns where the reports are not identical in vl, v2,
v3, and v4, then continues at the next statement.

7-76 7831 9274-000

 CMP (Compare Report)

Compare renamed results -1 and -2:

@cmp,-1„-2„,003 " 25-6,39-5 ❑ ,1,2 5-6,110-5 1
❑,1,2 v1i4,v2i3,v3i4,v4i3 .
where:
-1 Compares all lines (default), beginning at line 2
-2 (default), in renamed results -1 and -2.
003 Goes to label 3 if the reports are not the same.
Uses no option.
25-6,39-5 Compares column 25 for 6 characters and column
1,2 39 for 5 characters in the issuing report.
5-6,110-5 with column 5 for 6 characters and column 110
1,2 for 5 characters in the receiving report.
0 Compares tab lines only.
v1i4,v2i3, If the report fields are not the same, captures
v3i4,v4i3 issuing and receiving report line numbers and
columns where the reports are not identical in vl, v2,
v3, and v4.

7831 9274-000 7-77

CNT (Count)

CNT (Count)
This section applies only to the OS 1100 MAPPER System.
The Count (CNT) statement computes subtotals, percentages, standard
deviations, averages, entry counts, and other calculations on reports or
results creating a result. See the Manual Functions Reference for more
information.
Format
tICNT,c,d[, r] o cc Ityp,p [vrolts] .

Following is a description of the fields and subfields:

Field Description

c,d,r Report or drawer to process.

0 Options field (see Options).

CC Column-character positions or names of the fields to process.

!typ Line type to process. If you specify the A option, you can leave this subfield
blank, but enter the comma.

p Parameters:

1-9 to specify key fields (at least 1 is required)

N to specify numeric key fields (1 N)

Df to specify date key fields

f = 0-8 to specify date format (See the Sn option for date format codes.)
Example: 1DO, specifies key field 1 in date format 0

Tf to specify time key fields

f = 0-3 to specify time format (See the Sn option for time format codes.)
Example: 2T3, specifies key field 2 in time format 3

R to set up report key fields

Example: 1R, loads the field with the report number when processing a
drawer or range of reports

L to specify line key fields

Example: 1L, loads the field with the input report line number

visits Variable to capture the number of lines for the corresponding output result. Up to
eight variables may be returned by the statement.

7-78 7831 9274-000

 CNT (Count)

Options
A Processes all line types.
B Extends the boundaries for scaling intervals to the minimum
and maximum values defined in the scaling option. Every
interval between those boundaries is displayed, even those with
no entries.
C Distinguishes between uppercase and lowercase letters.
Default = the system processes and displays the keys as
uppercase.
D[n] Processes only those keys that occur n or more times, where n is
an integer greater than 1. Default = 2.
E Extracts result fields from the last occurrence of each unique
key. Default = first occurrence.
F Extracts result fields from the first occurrence of each unique
key. When using a minimum (<) or maximum (>) operator,
default = minimum or maximum field.
H Displays only the first set of headings in the result when you
process more than one set of parameters in a single statement.
I Includes out-of-range keys. Substitutes the minimum or
maximum boundary value, when applicable, for an out-of-range
key. The key field is then considered valid, and all its values are
counted. Default = the line is discarded for values outside the
boundaries.
Nn Substitutes invalid numeric data with the value n. Default = 0.
0 Omits data lines from the result. Only heading lines, grand total
summary, and warning messages are included in the output
result. The T and W options are automatically implied when the
0 option is specified.

7831 9274-000 7-79

CNT (Count)

Removes all non-referenced fields from the result and reorders

the fields, from left to right, according to this hierarchy:
1. Key fields in numeric order
2. Extraction fields in alphabetical order
3. Computational fields (subtotals, averages, and so on)
4. Minimum fields
5. Maximum fields
6. Entry counts
7. Percentages
Rx-y Processes a range of reports from x through y.
Rx,y Processes reports x and y. The reports are processed in the order
you specify.
Rx-y,z Processes reports x through y and also z. The reports are
processed in the order you specify.
Sn Creates intervals or scales in key fields. Following are the
formats for this option.
Sn(intalminlmax]) Scales numeric values.
SnDftintv[IminlmaxIstrt]) Scales dates.
SnTitintv[IminlmaxIstrth Scales times.

n Number of the key field to scale (1 through 9).

f Date or time format number.

Date format numb ers.

0 YMMDD 5 DDMMYY
1 YYMMDD 6 MM/DD/YY
2 DD MMM YY 7 MONTH DD,YYYY
3 YDDD 8 MMDDYY
4 YYDDD

Time format numbers.

0 HH:MM:SS 2 HHMMSS
1 HH:MM 3 HHMM

7-80 7831 9274-000

 CNT (Count)

into Interval size.

Date intervals:
nD n = number of days (default)
nW n = number of weeks
nM n = number of months
nY n = number of years

Time intervals:
nS n = number of seconds
nM n = number of months
nH n = number of hours

min Minimum value at which to begin scaling.

max Maximum value at which to end scaling.

strt Starting value.

If into is: Then strt is:

nD or nW 3-character day name, example: SUN

nM 3-character month name, example: MAY
nY 2- or 4-digit year, example 90 or 1990

nS same time format as data in the key field

nM same time format as data in the key field
nH same time format as data in the key field
T Displays total, overall summary values for each computed field at
the end of each result. For example, subtotaling shows a grand
total; averaging shows a grand average; entry counting shows total
entries; minimum and maximum operators show the smallest or
largest values in the field. You can also calculate the overall
standard deviation of values in a field.
U Displays the upper limit of the interval for scaled results rather than
the lower limit.

7831 9274-000 7-81

CNT (Count)

v Does not count lines with invalid numeric, date, or time fields.
Default = 0 for numeric operations; January 1,1944, for date
calculations; or 00:00:00 for time operations.
W Adds messages at the end of the result showing the number of lines
skipped due to invalid key or data fields.
Z Displays all intervals in the result, even those with no entries. This
option allows you to create a scale with no gaps. Use this option only
with the S option.
* Flags invalid subtotals, averages, standard deviations, maximums,
and minimums if invalid data were used in the calculations.

Reserved Words
STAT2$ contains the number of lines ignored in all results for invalid or
out-of-range key conditions.
STAT3$ contains the number of lines ignored in all results for invalid
numeric, date, or time values. The value is meaningful only if you specified
the V option.

Numeric Operators
Entry Count (=) Counts the number of entries for each unique key.
Subtotal (+) Subtotals values for each unique key in the key
field.
Percentage (%) Provides the entry counts for unique keys
expressed as a percentage of the total entries in
the field.
Subtotal Percent (+%) Expresses the subtotal for each unique key as a
percentage of the grand total of the key field.
Average (/) Computes the average by subtotaling values and
dividing by the number of entries.

7-82 7831 9274-000

 CNT (Count)

Minimum (<) or Computes minimum value for each unique key.

(<Dn) or (<Tn) For date or time entries use <Dn or <Tn; n is the
date or time format. For example, <D1 indicates
to find the earliest date for each key (in format
number 1, YYMMDD).
Maximum (>) or Computes maximum value for each unique key.
(>Dn) or (>Tn) For date or time entries use >Dn or >Tn; n is the
date or time format. For example, >TO indicates
to find the latest time for each unique key (in
format 0, HH:MM:SS).
Standard Deviation Computes standard deviation for a numeric field.
(!-) or (!+) Following are the operators and formulas used in
calculating standard deviation. (n = entry count,
and x = numeric field)
To Calculate Standard Deviation for a Sample:
Operator: !-
Formula: SORT((SUM(x**2)/(n-1))-(SUM(x)*SUM(x)/(n*(n-1))))

To Calculate Standard Deviation for a Population:

Operator: !+
Formula: SORTUSUM(x**2)/(n))-(AVG(x)*AVG(x)))

Variance (!!-) or (!!+) Computes the variance for a numeric field.

Following are the operators and formulas used in
calculating variance. (n = entry count, and x =
numeric field)
To Calculate Variance for a Sample:
Operator: !!-
Formula: ((SUM(x**2)/(n-1))-(SUM(x)*SUM(x)/(n*(n-1)))

To Calculate Variance for a Population:

Operator: !!+
Formula: ((SUM (x**2)/(n))-(AVG(x)*AVG(x))

7831 9274-000 7-83

CNT (Count)

Constant Label Operators

Constant labels (:R, :L, and :M) load fields with constants whose values are
based on conditions that exist while the statement is executing.
Report Number (:R) Places the input report number into the field.
Line Number (:L) Loads the field with the input report line number.
Multiple Analysis Loads the field with the corresponding analysis
Number (:M) number. If you use more than one set of
parameters (perform more than one analysis) in a
statement, the statement creates a single result
containing output from all of the analyses. This
operator (:M) loads the specified field with the
number of the analysis that is the source of the
output line. For example, output lines created by
the first set of parameters are loaded with a value
of one.

Using the ICNT Run to Create a CNT Statement

You can use the Iterative Count (ICNT) run to create a CNT statement. For
information on how to use the iterative runs, see the Manual Functions
Reference.

7-84 7831 9274-000

 CNT (Count)

CNT Statement Example

This statement finds the average of the Down field for each unique value in
the Location field:
@CNT,O,a,42 " 'Location','Down' 1,1,1' .
0,a,42 Searches report 42A0.
Of
Uses no options.
' Loca t i on ' Identifies the fields to process.
'Down'
I Processes tab lines only.
1, Identifies the Location field as the key field.
'/' Identifies the Down field as the field to find the average
for.

7831 9274-000 7-85

DAT (Date)

DAT (Date)
The Date (DAT) statement performs computations on dates (from 1944 to
2043) within a report or result and creates a result.
V 1100: On OS 1100 MAPPER Systems, y betwweni964
and 2063.
Format
tiOAT,c,d,r o cc Ityp,p .

Following is a description of the fields and subfields:

Field Description

c,d,r Report in which the computations are to be performed.

0 Options field (see Options).

CC Column-character positions or names of the fields to perform computations on.

!typ Line type to process. If you specify the A option, you can leave this subfield blank
but enter the comma.

p Parameters:

Date Format Arithmetic

A YMMDD + field to perform operations on

B YYMMDD - field to subtract
C DD MMM YY = field in which to place result
D YDDD K constant field to add to or subtract from a
E YYDDD field
F DDMMYY .• field in which to place day of week
G MM/DD/YY +n or -n constant number to add to or subtract
I MMDDYY from a field

continued

7-86 7831 9274-000

 DAT (Date)

continued

Field Description

The parameters subfield identifies which operations are performed in a DAT

statement, how many date fields are used, their format, and which arithmetic
functions are performed on each one. Always specify a result date field, such as
B= or ..

If you do not specify a format in either a + or - field, format B is assumed in both

fields.

If you specify a format for either a + or - field (but not both), that format is assumed
for both fields.

If you do not specify a format for the = field, the format specified for the + field (if
one exists) is assumed; otherwise, the format specified for the - field is assumed.

Options
A Processes all line types.
T Converts a time field to decimal hours. The time field must be in the
format HH:MM:SS or HHMM. Use the + parameter to specify the
field to convert and an = parameter in the field in which to place the
converted time. If you do not specify a result field, the converted
time is placed into the original time field.
W Converts a date field into days of the week.
n Specifies the number of work days in a week for computations,
where n is the number of work days.

',....-%

7831 9274-000 7-87

DAT (Date)

Example 1: Subtracting Dates

Subtract the dates in the Produc Actual field from the dates in the Produc
Plan field:
@dat,0,b,2 " 'producactual','producplan',X
'shipdate' ❑ ,-,+,= .
or
@dat,0,b,2 " 57-6,50-6,64-6 El ,-,+,= .
where:
9 9
Uses no options
'producactual' Subtracts the date in the Produc Actual
57-6 field (column 57 for 6 characters)
'producplan' from the Produc Plan field (column 50 for 6
50-6 characters)
+
'shipdate' and puts the difference in the Ship Date
64-6 field (column 64 for 6 characters)
=
❑ Processes tab lines only
Example 2: Converting Dates to a Different Format
Convert format B dates to format F dates:
@dat,0,b,2 " 50-6,32-6 0 ,b, f= .
where:
9 9
Uses no options
50-6 Converts the format b date in the Produc Plan field
b (column 50 for 6 characters)
32-6 to a format f date, and places it in the Produc Cost
i= field (column 32 for 6 characters)
❑ Processes tab lines only

7-88 7831 9274-000

 DAT (Date)

Example 3: Subtracting Dates in Different Date Formats

Subtract format F dates in the Produc Cost field from the format B dates in
the Produc Actual field:
tbda t, -0 " 32-6,57-6,77-3 0 , f -,b+,= .
where:
Uses no options
32-6 Subtracts the format f date (from the previous example) in
f- the Produc Cost field (column 32 for 6 characters)
57-6 from the format b date in the Produc Actual field
b+ (column 57 for 6 characters)
77-3 and places the result in the Spc Cod field (column 77
= for 3 characters)
Example 4: Adding a Constant Number of Days
Add three days to the dates in the Produc Actual field:
@dat,O,b,2 " 57-6,64-6 0 ,b+3,= .
or
@dat,O,b,2 " 'producactual ' ,eshipdate' 0 ,b+3,= .
where:
Uses no options
'producactual ' Adds three days to the format b date in the
57-6 Produc Actual field (column 57 for 6
b+3 characters)
'shipdate' and places the resulting date in the
64-6 Ship Date field (column 64 for 6 characters)
=

❑ Processes tab lines only

b+3,= Adds three days to the first field (column 57 for
6) and places the resulting date in the second
field (column 64 for 6)

7831 9274-000 7-89

DAT (Date)

Example 5: Adding a Constant Number Contained in a Field

Add the constant in the Spc Cod field to the dates in the Ship Date field:
@dat ,O,b,2 " 77-3,64-6, ' statusdate' 1:1,k,+,= .
where:
P II
Uses no options
77-3 Adds the constant in the Spc Cod field
k (column 77 for 3 characters)
64-6 to the date in the Ship Date field (column
+ 64 for 6 characters)
'statusdate' and places the resulting date in the
= Status Date field (column 5 for 6 characters)
El Processes tab lines only

Using the IDAT Run to Create a DAT Statement

v This section on using the IDAT run applies only to the OS 1100 MAPPER
System.
You can use the Iterative Date (IDAT) run to create a DAT statement. For
information on how to use the iterative runs, see the Manual Functions
Reference.

7-90 7831 9274-000

 DC (Date Calculator)

DC (Date Calculator)
The Date Calculator (DC) statement performs arithmetic calculations on
dates (from 1944 to 2043) or times that reside in variables, or on literal
dates or times.
Format

(SDC eq vrslts

Following is a description of the fields:

Field Description

eq Equations (separate with semicolons).

vrsits Variables to capture the results of the equations in the order presented.

Comments

• Each equation in a DC statement creates a label (A through Z,

consecutively) that you can use in subsequent equations in the same
statement. You do not need to specify the format of a date represented
by a label — it stays the same as the answer it represents and is
remembered by the system.
• You cannot name your own labels, as you can with an Arithmetic (ART)
statement. However, two constant labels are available for calculations
based on the current date and time (TODAY and TIME).
• Your answer appears in the same format as the date you use in the
equation unless you specify a format change.
• If the resulting value is not a valid date or time, the DC statement fills
the variable with asterisks (*). It then treats the asterisks as zeroes in
subsequent calculations.

7831 9274-000 7-91

DC (Date Calculator)

Date and Time Formats

For each date and time you use in the equation, specify the format it is in
first.
Format for Specifying Date and Time Formats
{DIT}n(x)
Following is a description of the subfields:

Field Description

D Denotes this is a date format.

T Denotes this is a time format.

n Number identifying the date format (0 through 8) or time format (0 through 3).

x Variable containing the date or time, or the actual date or time.

Note: If you add 1 to the time, it adds one to the hours.

Use these date and time formats:
DO(x) DATEO$ YMMDD
D1(x) DATE1$ YYMMDD
D2(x) DATE2$ DD MMM yr
D3(x) DATE3$ YDDD
D4(x) DATE4$ YYDDD
D5(x) DATE5$ DDMMYY
D6(x) DATE6$ MM/DD/YY
D7(x) DATE7$ MONTH DD, YYYY* (constant label TODAY format)
D8(x) DATE8$ MMDDYY
TO(x) TIMEO$ HH:MM:SS (constant label TIME format)
T1(x) TIME1$ HH:MM
T2(x) TIME2$ HHMMSS
T3(x) TIME3$ HHMM
* Since these formats contain spaces, enclose actual dates in apostrophes; however, do not
enclose variables containing these formats in apostrophes.

7-92 7831 9274-000

 DC (Date Calculator)

Format for Changing Date and Time Formats

(DITHnlw}=expression

Following is a description of the subfields:

Field Description

D Denotes this is a date format.

T Denotes this is a time format.

n Number identifying the date or time format of the answer to expression.

w Specifies the answer of expression should be expressed as the day-of-

the-week name.

expression Calculations using literal data or variables (using the date and time
formats listed earlier), constant labels, labels created previously in the
same DC statement, or any combination of these.

Examples
V1 equals today's date plus 90 days in DATE7$ format:
@dc today+90 v1h18 .
V1 equals today's date in DATE1$ format; v2 equals current time in
TIMEO$ format:
@dc dl=today;time v1i6,v2h8 .
V1 equals the day of the week on which June 4, 1990 fell; v2 equals 900626
plus five days, changed to DATE7$ format; v3 equals the number of days
difference between the date in v2 (label B) and today's date:
@dc dw=d7( ' j one 4, 1990' ) ; d7=d1(900626)+5;
b-today v1h10,v2h18,v3 i 4 .

7831 9274-000 7-93

DC (Date Calculator)

V1 equals 900604 (v5) plus 60 days in DATE1$ format; v2 equals the day of
the week that is the date in vl (a); v3 equals the date in vi (a) in DATE7$
format; v4 equals the date in v3 (c) minus two days in DATE7$ format:
@I d v v5 i 6=900604 .
@dc d1(v5)+60;dw=a;d7=a;c-2 v1i6,v2h10,v3h18,X
v4h18 .

7-94 7831 9274-000

 DCR (Decode Report)

DCR (Decode Report)

vy This section applies only to the OS 1100 MAPPER System, the U Series
MAPPER System, and UNIX MAPPER Systems.
The Decode Report (DCR) statement returns an encoded report to a
readable format. The decoded report becomes the current (-0) result.
Condition
You must use the same encryption key and encryption level used when the
report was encoded.
V 1100: Encryption levels are not available on OS 1100 MAPPER Systems.
Format
OCR,c,d,r,key[-level„dspscram?'

1100:
fDCR,c,d,r,key .

Following is a description of the subfields:

Field Description

c,d,r Report to decode.

key The one- to eight-character key that was used to encode the report.

-level Encryption level. If the report was coded with a level, you must specify the
same level here.
V 1100: This subfield is not available on OS 1100 MAPPER Systems.

Subfield not used at this time.

dspscram? Is the scrambled data displayable? Y or N. Default = N. If you specified Y in

this field when you encoded the report, you must specify Y here.
V 1100: This subfield is unnecessary on OS 1100 MAPPER Systems.

7831 9274-000 7-95

DCR (Decode Report)

Comments
• Use caution when encoding and decoding reports. Do not forget your
key. A report cannot be decoded if you lose or forget the key because no
record of it is kept by the MAPPER system. Your coordinator cannot tell
you what it is.
• Because of high processing overhead, excessive use of this statement
may affect system performance.
• System messages are produced in these cases:
- You specified the incorrect key or encryption level.
- The encoded report is corrupted.
- The report is not encoded.
V 1100: On OS 1100 MAPPER Systems, the decoding process produces
invalid characters under those circumstances.
Whenever the system produces these invalid characters, it displays a
system message indicating an error and flags each invalid character in
the result with an SOE character.
If the encoded report is corrupted, characters in the result shown as
SOEs cannot be recovered.
V • 1100: If you are using a normal ASCII terminal, you may not be able to
decode a report that was encoded from a National Character Set (NCS)
terminal.
Examples
Decode report 10B0, which was encoded using the key jak:
@dcr,0,b,10,jak .

V 1100: The following example does not apply to OS 1100 MAPPER Systems.
Decode report 2CO3 which was encoded using the key ins with level 6:
@dcr,0,c,2, ins-6 .

7-96 7831 9274-000

 DEF (Define)

DEF (Define)
The Define (DEF) statement tests a variable, substring, or reserved word for
its current contents or characteristics, or sets another variable to a value
based on the option used.
Format
4DEN,0,1abl setv,testv .

Following is a description of the subfields:

Field Description

0 Option that specifies the information you want to determine about the variable.
You can specify only one option. If you do not specify an option, the DEF
statement returns a code that describes the contents of testy.

lab Label to go to if testy is not defined. (To simplify your run logic, if you want the run
to continue on the next line, use LIN1 in this subfield instead of a label number.)

sets Variable in which the MAPPER system returns a value describing the variable or
reserved words tested.

testy Variable or reserved word to test. To test a member of an array, use testv[n],
where n is the member (brackets are required).

Options
A Determines the alphabetic drawer. The variable to be tested must
contain a valid numeric drawer (a positive octal number that
identifies the drawer and cabinet within the system). The variable
being set must be type A or H.
C Determines the number of significant characters (any characters
other than spaces). Tab characters are significant characters.

7831 9274-000 7-97

DEF (Define)

I Determines the variable type. The system returns one of the

following values to indicate the variable type:

Test Type Setting

A 1
F 2
S 3
I 4
H 5
V 1100: 0

K Determines whether the variable contains Kanji characters (set v

contains 8 if so; otherwise, it contains 0 through 7 as described in the
table at the end of this option list.
M Determines the cabinet. The variable to be tested must contain a
valid numeric drawer.
N Determines the numeric drawer. The variable to be tested must
contain a valid cabinet and drawer designation, for example OB.
P Determines the packed size, that is, the size of the variable if it were
loaded with a LDV,P statement.
S Determines the size.
T Determines the number of tab characters.
✓ Determines the name of the variable. For testy, enter an integer
to represent the order in which the run created the variable. For
example, the following statement loads <set> with the name of the
variable that was fifth to be created in the run:
@def <set>s 10,5
V 1100: On OS 1100 Systems, determines the name of the variable. If
testy does not have a variable name assigned, the system returns
spaces in setv . See Section 4 for a description of named variables.

7-98 7831 9274-000

 DEF (Define)

If you do not use an option, the DEF statement sets the setv variable to a
value from 0 to 7, depending on the contents of the testy variable:

setv testy

0 All tab characters or spaces or both

1 All numeric characters
2 All alphabetic characters
3 Alphabetic and numeric characters
4 All special characters
5 Special and numeric characters
6 Special and alphabetic characters
7 Special, numeric, and alphabetic characters

Note that the contents of testy can include either just the characters
indicated or both the characters and spaces.
Examples
Determine the kinds of characters in <chars> and return the code in <code>:
@def <code>il <chars> .

Determine the number of significant characters in <input> and return the

value in <characters>:
@def,c <characters>,<input>

Determine the size of <name> and return the value in <size>:

@Wef,s <size>i2 <name> .

7831 9274-000 7-99

DIR (Directory)

DIR (Directory)
The Directory (DIR) statement loads variables with information about a
data name from the system directory. With the DIR statement, you can
determine whether a data name is valid and the kind of data the name
represents (cabinet, drawer, or report).
Format
OIR[,lab] name [vcablnet,vdrawer,vrpt,vhirptr] .

Following is a description of the field and subfields:

Field Description

lab Label to go to if the name is invalid.

name Data name to define.

vcabinet* Variable to capture the cabinet number.

vdrawer* Variable to capture the drawer letter.

vrpt* Variable to capture the report number.

vhirptr* Variable to capture the higher report number if the data name defines a range
of reports.

* A data name can represent a cabinet, a drawer, a report, or a range of reports.

Variables that do not apply for a particular data name are loaded with spaces unless they
are defined as I type variables.

77 1100: Variables that do not apply for a particular data name are loaded with spaces.

7-100 7831 9274-000

 DIR (Directory)

Reserved Word
STAT1$ contains one of the following error codes if the data name supplied
is invalid and the run continues at the label (the run errs if you do not use
the label):
1 Data name was not found in the system directory.
2 Data name does not begin with an alphabetic character (A to Z).
3 Data name contains invalid characters (A, ;, /, comma, space, tab).
V 1100: Data name contains no alphanumeric characters (A to Z or
Oto 9).
4 Data name contains more than 16 characters.
Example
Load variables with information about data name order-status:
@Wir,099 order-status <cabinet>a4,<drawer>h1,1
<report>a4,<hireport>a4 .

where:
099 Goes to label 99 if data name order-status does not
exist
order - status Specifies the data name to obtain information about
<cab i net>a4 Loads <cabinet> with the cabinet number of
order-status
<drawer>hl Loads <drawer> with the drawer letter
<r epor t>a4 Loads <report> with the report number
<h i r epor t>a4 Loads <hireport> with the higher range report
number

7831 9274-000 7-101

DRW (Drawer)

DRW (Drawer)
The Drawer (DRW) statement loads variables with the following
information: number of characters per line, next report to add, highest
report number, and the report and line limits in a drawer.
Format
@ORW,c,d[,1ab vcpl ,vcs,vmtno,vintn,vnxrd,vh1 rptd,vInd,
vrptsd,vrImt,v1 Imt] .

Following is a description of the subfields:

Field Description

c,d Cabinet and drawer to process.

lab Label to go to if the drawer does not exist.

vcpl Variable to capture the number of characters per line.

V 1100: vcs Variable to capture the character set type:

0 LCS
1 FCS
2 FCSU

V 1100: vmfno Variable to capture the MAPER file number (for example, 1,2, or 3) where the
drawer resides. (MAPER files are OS 1100 program files where the MAPPER
database resides.)

V 1100: vmfn Variable to capture the internal MAPER file name (for example, M00001,
M00002, or M00003) where the drawer resides.

vnxrd Variable to capture the next report number available in the drawer if a new
report were added.

vhirptd Variable to capture the highest report number used in the drawer.

vind Variable to capture the total number of lines in the drawer.

vrptsd Variable to capture the total number of reports in the drawer.

vrlmt Variable to capture the report limit for the drawer.

Om t Variable to capture the line limit for the drawer.

7-102 7831 9274-000

 DRW (Drawer)

Reserved Word
If a drawer exists, STAT1$ contains the number of the highest report
created. If the drawer does not exist, STAT1$ contains 0, and the run goes
to the specified label. If you did not use a label, the run continues at the
next statement.
Example
Load vl with the number of characters per line in cabinet 0, drawer B, and if
that drawer does not exist, continue the run at label 5:
@Wrw,0,b,005 v1i3 .

7831 9274-000 7-103

DSM (Display Message)

DSM (Display Message)

The Display Message (DSM) statement displays a one-line message at the
top of the screen. You can use the DSM statement in one of two ways:
• Display a message at the top of an existing screen.
• Display a report or result, placing a message at the top of the screen.
You can display the report or result beginning at line one or at a
specified line number.
Format
tiOSIA,c,d,r,imsg1,tabp,erese1,interim1,pdq,dc,dd,dr,dspi ,dspf]

Following is a description of the subfields:

Field Description

c,d,r Report containing the message.

lmsg Line number of the message in the report.

tabp Tab character after which to place the cursor. Use a negative number to
indicate the number of tab positions to move backwards. Maximum = 100.
Default = the Roll field in the control line (position 0).

erase? Erase the rest of the screen, Y or N. Default = N.

interim? Continue the run without the user pressing Resume, Y or N. Default = N.

Oct Number of lines to push down on the screen. Default = 0.

dc Cabinet number of the report to display.

dd Drawer of the report to display.

dr Report number of the report to display.

dspl Line number of the specified report at which to start the display. Default =1.

dspf Format of the report to display. (Omit this field if you are displaying a format
defined with a FMT or SFC statement.)

Format = 0 - 25. Default = 0, basic format.

V 1100: Format = 0 - 6. Default = 0, basic format.

7-104 7831 9274-000

 DSM (Display Message)

Comments

• The message to display resides in a report or result. You display it by

specifying its line number.
• The DSM statement stalls the run until the run user presses Resume,
unless you specify the interim display, in which case the run continues
automatically. Note that the DSM statement clears the output area.
• The text displayed by the DSM statement appears as it does for
MAPPER system messages.
• The screen display contains a function key bar. You can customize the
function key bar so that you can include operations not available with
the standard function key bar. See FKY in this section.
1100: On OS 1100 MAPPER Systems, the screen display may not
contain a function key bar, depending on how your system or sign-on is
set up.
• Less than (<) and greater than (>) signs are translated into blink
characters.
• If you have a 132-character terminal, the messages are automatically
centered.
• You can customize the report format by preceding the DSM statement
with a Format (FMT) or Set Format Characters (SFC) statement. See
FMT and SFC in this section.
• Do not place other run statements on the same line after the DSM
statement. Other run statements following it on the same line are
ignored. Put the next run statement on a new line.
• Capture input with INV , INVR1$, INPUT$, or INSTR$.

7831 9274-000 7-105

DSM (Display Message)

Examples

Display a message (located on line 4 of the current result) at the top of the
current screen:
@dsm, -0,4 .
Display report 2D0, place a message (located on line 4 of report 12A0) on the
top of the screen, and position the cursor at the tenth tab position:
@dsm,O,a,12,4,1O,,,,O,d,2 .

7-106 7831 9274-000

 DSP (Display Report)

DSP (Display Report)

The Display Report (DSP) statement displays a report or result on the
screen and clears the output area. If the display includes the standard
function key bar, you can customize it to include operations not available on
the standard function key bar. For information, refer to the Function Key
(FKY) and Screen Control (SC) run statements.
If you want the run to finish automatically after displaying the report or
result, use the Display Report and Exit (DSX) statement. With a DSX
statement, the user exits the run when the display appears on the screen.
The DSX statement uses the same fields and subfields as the DSP
statement, except for the Interim? subfield, which does not apply to the
DSX statement. See the online help system (HELP,@DSX) for more
information.
Format
OSP,c,d,r1,1,tabp,I,Interim?,hold,msg] .

Following is a description of the subfields:

Field Description

c,d,r Report to display.

I Line number in the report at which to start the display.

tabp Tab character after which to place the cursor. Use a negative number to
indicate the number of tab positions to move backwards. Maximum = 100.
Default = the Roll field in the control line (position 0).

f Report format. (Omit this field if you are displaying a format defined with a
FMT or SFC statement.)

Format = 0 - 25. Default = 0, basic format.

V 1100: Format = 0 - 6. Default = 0, basic format.

interim? Continue the run, Y or N (Y causes the run to display the report and continue
and N stalls the run until it is resumed). Default = N.

continued

7831 9274-000 7-107

DSP (Display Report)

continued

Field Description

hold Number of lines already on the display screen that you want to hold. Report
is displayed beginning with the first nonheld screen line.
V 1100: On OS 1100 MAPPER Systems, you can also enter the letter H to
display the report headings.

msg Message of up to 80 characters to display in the control line. Enclose the

message in apostrophes. Default tab position = home position.
V 1100: On OS 1100 MAPPER Systems, you can enter up to 79 characters to
display on the control line.

Comments

• In debugging runs, the DSP statement displays the results of

statements as they are processed to see if they produce the desired
results. When they do, remove the DSP statements used for this
purpose.
• In manually updating reports, the DSP statement displays reports to
update during a run. If manual updating is to be an integral part of the
run, leave in the DSP statements used for this purpose.
o The screen display contains a function key bar. You can customize the
function key bar so that you can include operations not available with
the standard function key bar. See FKY in this section.
1100: On OS 1100 MAPPER Systems, the Screen display may not
contain a function key bar, depending on how your system or sign-on is
set up.
• You can customize the report format by preceding the DSP statement
with a Format (FMT) or Set Format Characters (SFC) statement. See
FMT and SFC in this section.
• Do not place other run statements on the same line after a DSP
statement. Other run statements following it on the same line are
ignored. Put the next run statement on a new line.
e The DSP statement clears the output area after executing.
• To continue the run after the display, press Resume.

7-108 7831 9274-000

 DSP (Display Report)

• To continue the run after the display, press Resume.

• The 110 and LLP counts are reset following a noninterim DSP
statement.
Examples
The first DSP statement displays the current result, the second displays
renamed result -3, and the third displays report 2B0.
tbdsp,-0 .
@dsp,-3 .
@dsp,O,b,2 .

Display report 1CO, starting at line 8 and continuing the run after the
display:
@dsp,O,c, 1 , 8 ,,,y .
Display format 5 of report 1DO, starting at line 3:
@dsp,O,d,1,3„5„,' This line displayed on control line.

7831 9274-000 7-109

DVS (Define Variable Size)

DVS (Define Variable Size)

The Define Variable Size (DVS) statement creates variables equal to the
size of report fields. For example, use the DVS statement to capture input
parameters to be processed against report fields, or to build screens whose
input fields must be the same size as report fields.
V 1100: The DVS statement creates a -0 result and releases any previous -0
result.
Format
0VS[,c,d,r,lab] v[,v,...,v]

Following is a description of the subfields:

Field Description

c,d,r Report where the fields reside. Default = -0.

lab Label at which to continue execution if the specified fields are not found.

field Fields whose size you want to define (can be field names or column-character
positions). Separate fields with commas.

Variables to define. Specify the variable name or number and type, for example,
vi h, v2s, and so on. Separate variables with commas.

Comments

• Generally, you use a DVS statement with named fields, because a name
does not directly specify the field size. The run defines the size of the
variable when it executes. Any input parameter or screen using the
affected variable adjusts to changes in field sizes.
• In a DVS statement, you specify the variable and its type; you do not
specify the variable size. The run assigns a size to the variable equal to
its corresponding report field.

7-110 7831 9274-000

 DVS (Define Variable Size)

Examples

Initialize a variable to the size of the Cust Code field in report 2B0, for use
as an input parameter:
@dvs,0,b,2 'custcode' vlh .
@chg input$ v1 .

Initialize variables to the size of the Order Number and Ord Qty fields from
the current -0, and create a screen using their sizes:
@dvs 'ordernumber', 'ordqty' <num>h,<qty>i .
@brk
Enter Order Number: 0<nump,
Enter Quantity: 0<qty>,
@brk out,-0,2,23,1,1,y,„p .
@chg input$ <nunP,<qty> .

7831 9274-000 7-111

ECR (Encode Report)

ECR (Encode Report)

Q This section applies only to the OS 1100 MAPPER System, the U Series
MAPPER System, and UNIX MAPPER Systems.
The Encode Report (ECR) statement transforms report data into unreadable
code. The report data cannot be displayed until the correct key is specified
with the Decode Report (DECODE) function or the DCR run statement.
(See DCR in this section.)
•;7 1100: On OS 1100 MAPPER Systems, the encoded report becomes the
current (-0) result. You can display the encoded report, but it is not
readable.
The ECR statement is particularly useful for highly sensitive reports and
messages. It is more secure than read/write passwords because no one,
including the coordinator, can decode the report without knowing the key.
Notes: 1. Ask the coordinator whether the ENCODE feature is installed
on your system.
2. Because of high processing overhead, excessive use of the ECR
statement may affect system performance.
Format
@ECR,c,d,r,key[ - level,hdgs?„dspscramn
V' 1100:
@ECR,c,d,r,key[,hdgs1] .

7-112 7831 9274-000

 ECR (Encode Report)

Following is a description of the subfields:

Field Description

c,d,r Report to encode.

key The one- to eight-character key used to encode the report. Valid characters
are A-Z and 0-9.
V 1100: On OS 1100 MAPPER systems, since tne -level subfield is not
available to scramble the data more, use more characters for the key to make
it more difficult for an unauthorized user to guess the key.

-level Level at which to encode the report. Valid levels are 1-8. The higher the level,
the more the data is scrambled. Default =1.
V 1100: This subfield is not available on OS 1100 MAPPER Systems.

hdgs? Encode report headings? Y or N. Default = N.

Subfield not used at this time.

dspscram? Allow the scrambled data to be displayed? Y or N. Default = N.

V 1100: This subfield does not apply to OS 1100 MAPPER Systems.

Comments
• Use an encryption level to specify the amount of scrambling. The higher
the level of encryption, the more the data is scrambled. Note that the
higher levels of encryption consume more system resources to process
the report.
V 1100: Encryption levels are not available on OS 1100 MAPPER
Systems.
• Specify the dspscram? subfield to allow encoded reports to be
transferred to the OS 1100 MAPPER System. If you enter a Y in this
subfield, the system uses the encryption process used on the OS 1100
MAPPER System, allowing the report to be decoded using the OS 1100
MAPPER System.
V 1100: When encoding reports on OS 1100 MAPPER Systems, the
dspscram? subfield does not apply; the subfield is for encoding reports
on other systems so that they can be decoded on OS 1100 MAPPER
Systems.

7831 9274-000 7-113

ECR (Encode Report)

• Use caution when encoding reports. Do not forget your key. A report
cannot be decoded if you forget the key because no record of it is kept by
the MAPPER system. Your coordinator cannot tell you what it is.
• You cannot move encoded data between drawers with different report
widths because you will not be able to decode it. If a drawer width is
changed, all encoded reports in that drawer will be corrupted and they
will not be able to be decoded.
V • 1100: Do not update an encoded report. Any change to the encoded
report corrupts the report and you will not be able to decode it. Protect
your report from updates by using an update password (see the
Password [PSW] function in the online help system [HELP,PSW]).
• You may not be able to decode data with a normal ASCII terminal if the
data was encoded with a National Character Set (NCS) terminal. Also,
a report containing special NCS characters cannot be encoded with a
normal ASCII terminal.
Encoding a report approximately doubles its size.
Examples

This example encodes report 10B0, using the characters jak as the
encryption key. The report headings are also encoded:
tbecr ,O,b, 10, jak ,y .

V 1100: The following example does not apply to OS 1100 MAPPER Systems.
This example encodes report 2CO3 using the characters salplan as the
encryption key at encryption level 3. If you display the result, the encoded
data appears as scrambled data:
@ecr,0,c,2,salplan-3„,y .

7-114 7831 9274-000

 EL- (Element Delete)

EL- (Element Delete)

This section applies only to the OS 1100 MAPPER System.
The Element Delete (-EL) statement to delete a standard OS 1100 program
file or symbolic element, or a data file.
Condition
The file must be a sector-formatted file with no read or write keys.
Format
-
@EL [,lab] qual,In[,cyc,elt,ver]

Following is a description of the fields and subfields:

Field Description

lab Label to go to if the run encounters an error. See the STAT1$ reserved word
status codes following this table.

qual Qualifier.

fn Name of the file to delete, or the file name containing the element to delete.

cyc File cycle.

elt Element name.

ver Version.

7831 9274-000 7-115

EL- (Element Delete)

Reserved Words
STAT1$ contains the following status codes if the statement is not able to
delete the file:
0 Requested element not found in specified file.
1 File does not exist.
2 File already assigned to MAPPER system.
3 File already assigned exclusively to MAPPER system.
4 File already assigned to another user.
5 File already assigned exclusively to another user.
6 File rolled out.
7 Facilities currently unavailable.
8 Private file, under different project-id.
9 Read or write restrictions on the file.
10 File is not sector-formatted mass storage file.
11 File is not program file (if element is specified).
12 File is a MAPPER file.
13 System I/O error.
14 Facility warning or reject.
15 Insufficient or improperly formatted statement.
STAT2$ contains the system message number. User this number in the
Load System Message (LSM) statement to retrieve the text of the message.
Example

Delete the file myqual*myfile:

@eI- myqua I ,myf i le .

7-116 7831 9274-000

 ELT (Element)

ELT (Element)
'This section applies only to the OS 1100 MAPPER System.
The Element (ELT) statement copies a MAPPER report or result to a
standard OS 1100 program file or symbolic element, or to a data file.
If the file you are copying is not a currently assigned file, the ELT statement
assigns it with a maximum granularity of 262,143 tracks.
Condition
The file must be a sector-formatted file with no read or write keys.
Format
@ELT,c,d,r[,lab] qual,inkcyc,elt,ver,mapperf?,hdgs?,
cs,newcycn .

Following is a description of the fields and subfields:

Field Description

c,d,r Report to copy.

lab Label to go to if the run encounters an error.

qua/ Qualifier.

fn File name to transfer the report to.

cyc File cycle.

elt Element name.

ver Version.

mapperf? MAPPER format, Y or N. Default = N.

hdgs? Include headings, Y or N. Default = N.

continued

7831 9274-000 7-117

ELT (Element)

continued

Field Description

cs Character set of the new report:

L Fieldata
F ASCII (default)
U ASCII, uppercase

newcyc? Create a new cycle, Y or N. Y creates a new cycle (+1) for the file and ignores
the entry in the cyc subfield. Note that the run errs if you try to create a new
cycle of a nonexistent file.

Reserved Words
STAT1$ contains error codes:
1 File (relative cycle requested) does not exist.
2 File is already assigned to the MAPPER system.
3 File is already assigned exclusively to the MAPPER system.
4 File is already assigned to another user.
5 File is already assigned exclusively to another user.
6 File is rolled out.
7 Facilities currently unavailable.
8 Private file, under different project-id.
9 Read or write restrictions are on the file.
10 File is not sector-formatted mass storage file.
11 File is not program file (if the element is specified).
12 File is a MAPPER file.
13 System I/O error.
14 Facility warning or reject.
15 Insufficient or improperly formatted statement.
16 File is not a data file (if the element is not specified).
17 Cycle attempted on nonexistent file.
18 Attempted to write past end of file.
STAT2$ contains a line number identifying the system message. Use a
Load System Message (LSM) run statement to read the message. Place the
number in STAT2$ in the ms g n o subfield in the LSM statement.

7-118 7831 9274-000

 ELT (Element)

Example
This example creates myqual*myfile (qualifier*file) and copies the data
from report 2B0 to the file. If there is an error and the system cannot copy
the data, the run goes to label 99.
@elt,O,b,2,99 myqual,myfile .

7831 9274-000 7-119

 FDR (Find and Read Line)

FDR (Find and Read Line)

The Find and Read Line (FDR) statement finds a line containing data you
specify. Follow the FDR statement with one or more Read Line Next (RLN)
statements or a Read Line (RDL) statement, to read the line or lines.
Format
@FDR,c,d[,r,l,q,lab] o cc Ityp,p [vrpt,vino]

Following is a description of the fields and subfields:

Field Description

c,d,r Report in which to find (and later read) a line.

Line number at which to start the scan.

q Number of lines to scan. Default = all lines.

lab Label to go to if no lines or data are found.

0 Options field (see Options).

CC Column-character positions or names of the fields to scan.

Ityp Line type to scan. If you specify the A option, you can leave this subfield blank,
but enter the comma.

p Find parameters.

vrpt Variable to capture the report number where the first find was made.

vino Variable to capture the line number where the first find was made.

7831 9274-000 7-121

FDR (Find and Read Line)

Options
A Processes all line types.
C(S) Distinguishes between uppercase and lowercase letters.
V7 1100: C(x) Alters the find process based on the character set order.
Ordinarily the system processes the report based on the
character set of the drawer. The C option allows you to
choose the character set type on which to base the find. Use
one of the following:
C(F) Full character set (FCS)
C(L) Limited character set (LCS)
C(S) Strict comparison; distinguishes between
uppercase and lowercase letters.
Rx(-y I ','y) Scans a range of reports from report x through report y; scan
reports x,y,...y. (Note that the format Rx,y requires
apostrophes around the comma.)
'' 1100: On OS 1100 MAPPER Systems, you do not need to
enclose the comma in apostrophes.
Examples:
r2','5 Scan reports 2 and 5
r2-10 Scan reports 2 through 10
r2-10','14 Scan reports 2 through 10 and 14
Searches for spaces.
Searches for the slant character.
Comments
• The FDR statement is different from a Find (FND) statement in that
the FDR statement may be followed by an RLN statement instead of an
RDL statement. It is generally more efficient to use an FDR/RLN
combination instead of an FND/RLN combination.
• If a find is made, the report in which the find is made becomes the
current -0. Any previous -0 result is released.
• See also RDC, RDL, and RLN in this section.

7-122 7831 9274-000

 FDR (Find and Read Line)

Example 1: Finding a Specific Line in a Drawer

Look for characters ip and read the order number on the found line:
@fdr,O,b " 'stcd' D, ip <report>i6,<Iine>i6
@rin,<Iine>,099 'order' <ord>i .

where:
5 5
Uses no options
'stcd' Looks in the St Cd field (column 2 for two
characters)
0 Processes tab lines only
ip Looks for the characters ip
<r epo r t> i 6 Captures the report number where the find was
made in <report>
<line>i6 Captures the line number where the find was
made in <line>
r I n ,‹I ine>,099 Captures the order number on the found line (in
'order' <ord>i <line>) in <ord>

7831 9274-000 7-123

FDR (Find and Read Line)

Example 2: Finding a Line in a Report

Look for the word green and read the order number on the found line:
@qdr,O,b,2,6,100,099 " 15-5 0,green ,v1i6
&In,v1,099 39-5 v2i5
where:

6 Starts the scan at line 6

100 Scans 100 lines
099 Goes to label 99 if no finds are made
Uses no options
15-5 Scans column 15 for five characters
Processes tab lines only
green Looks for the characters green
v1i6 Captures in vl the line number where the find was
made
r I n , v1,099 Captures in v2 the order number on the found line in
39-5 v2 i 5 vl

7-124 7831 9274-000

 FIL (Create File)

FIL (Create File)

The Create File (FIL) statement creates a file in either MAPPER format or
native data file format using the data from a MAPPER report or result.
Format
WIL,c,d,r1,mapperf?,hdgs?,labj fn .

Following is a description of the field and subfields:

Field Description

c,d,r Report to copy.

mapped? Create the report in MAPPER format, Y or N. Default = N, creates the report
in standard data file format. To create a file in binary format (from a binary
report), enter a B.
' 1100: Binary files are not available on OS 1100 MAPPER Systems.

hdgs? Place report headings into the file, Y or N. Default = N.

lab Label to go to if the report or drawer does not exist.

fn Name of the file to create.

V 1100: Include the full file name. The qualifier and file name must conform to
OS 1100 file naming standards. Only alphabetic, numeric, and the special
characters dollar sign ($) and minus (-) can be included. Refer to the
ECL Operations and Programming Reference for complete information on files,
elements, and cataloging. Default character set of the file to create = F (full
character set; creates an ASCII file).

' U Series and UNIX: Include the full path name. The directory in which the
file is to be created must exist. The maximum length of the file name is 14
characters; the maximum length of the path name and file name is 70
characters. File names can be uppercase or lowercase letters but are
created (or must already exist) exactly as typed. For example, Abc must be
accessed with an uppercase A and lowercase b and c.

' A Series: Include a usercode and pack family (optional). File names must
be uppercase letters. If a usercode is not specified, the file is created under
the user's usercode. If a pack family is not specified, the file is created on the
pack family equated to DISK in the family statement. The file is created with
security set to PUBLIC (I/O).

continued

7831 9274-000 7-125

FIL (Create File)

continued

Field Description
fn V BTOS: Use the full path name: [volume]<directory>fi/ename. The volume and
(cont.) directory in which the file is to be created must exist. BTOS does not default
to the current directory when creating the file. File names are not case
sensitive.

V PC MAPPER: Include the complete path name. The directory you specify
for the file must exist.

A file name cannot exceed eight characters in length; an extension cannot

exceed three characters. Follow the DOS file naming conventions.

If you use a reverse slant ( \ ) to define a directory path in an FIL statement, it

must be enclosed in apostrophes. This prevents the directory path from
being misinterpreted as a MAPPER run statement that continues on the next
line.

Comments
• If you create a file using the name of an existing file, the existing file is
overwritten.
• If the file being loaded does not exist, the FIL statement creates the file.
• To keep information such as report number and date the report was last
updated with the file, create the file with headings. This writes the date
line into the file, so when you retrieve the file, the date line of the
original report is part of the result.
• If the MAPPER report contains tab characters and you do not create the
file in MAPPER format, the tab characters are translated to spaces. See
Appendix C for information on translating tab characters to tab or other
characters using the $TABA$ command.
• To control the format of the data in the files you create, use the data
control commands described in Appendix C.
• U Series and UNIX: You can create the file in MAPPER format (which
is unreadable by UNIX) or in standard UNIX file format (which can be
processed by UNIX utilities).

7-126 7831 9274-000

 FIL (Create File)

• A Series: You can create the file in MAPPER format (which is

unreadable by CANDE and MARC and contains special control
characters) or in standard data file format (which can be processed by
CANDE, MARC, and other A Series edit utilities).
• See the A Series I/O Subsystem Programming Reference for a description
of valid file names.
V • BTOS: If you use a variable for a BTOS file name, pack the variable to
eliminate trailing spaces. A file name with trailing spaces can cause an
error when the FIL statement is used. For information about packing a
variable, refer to the Load Variable (LDV) statement and its P option.
Example 1: Translating Characters Using the $TRNA$ Command
Translate ampersands (&) to spaces (ASCII octal code 040) and dollar signs
($) to question marks (?):
$t rna$ &,040 $,'?'
' Example 2: 1100: Creating a Standard OS 1100 File
Create a standard OS 1100 data file called myqual*myfile using the data in
report 2B0, including report headings:
@f i I ,O,b,2,n,y myqua l*my f i le .
V Example 2: U Series and UNIX: Creating a Standard UNIX File
Create a standard UNIX file called production in the test directory using the
data in report 2B0, including the report headings:
@fil,0,b,2,n,y /test/production .

' Example 2: A Series: Creating a Standard Data File

Create a standard data file called PRODUCTION on the TEST pack family,
using the data in report 2B0, including the report headings:
@fil,0,b,2,n,y '(TEST)PRODUCTION ON TEST' .

7831 9274-000 7-127

FIL (Create File)

V Example 2: PC MAPPER: Creating a Standard Data File

This example creates a file called prodstat.new in the \ test directory using
the data in report 2B0, including the report headings:
CH i 1,0,b,2,n,y '%tesnprodstat.new' .

7-128 7831 9274-000

 FKY (Function Key)

FKY (Function Key)

The Function Key (FKY) statement customizes the function key bar that is
displayed at the bottom of the screen during a display by the Display (DSP),
Display Message (DSM), or Output Mask (OUM) statements. You can also
use the FKY statement to customize the control line.
1100: On OS 1100 MAPPER Systems you cannot use the FKY statement to
customize the control line.
Condition
Use Screen Control commands, such as FKEY, in a separate report or in the
output area of your run to define the function keys, and with the exception
of the OS 1100 MAPPER System, the control line. See SC in this section.
Format
@FKY[,c, d , r
Following is a description of the subfields:

Field Description

c,d,r Report containing the Screen Control commands that create a custom
function key bar, control line, or both, for the following DSP, DSM, or OUM
statement to display.
vu; kin OS 1100 MAF I-Ln oysteni, yuu jai root Ube a IC [-INT statenient to
customize the control line.

7831 9274-000 7-129

FKY (Function Key)

Comments
• The DSP, DSM, and OUM statements continue to use the report you
specified until one of the following conditions occur:
The run terminates.
The run links to another run via the Link to Another Run (LNK)
statement.
You designate another Screen Control report with the FKY
statement.
You use another FKY statement with no report specified.
• To return control to your run, use the KEY screen control command.
Example
This example sets up Screen Control commands in the output area,
performs a Break (BRK) statement to make them accessible as -0, then uses
FKY and DSP statements to display reports with and without a customized
function key bar:
@brk .
fkey,l,'Resume',rsin
fkey,2,'Paint',pnt
fkey,4,'Return',KEY
fkey,10,'Quit',"
@brk fky,-0 .
@d sp , 0 , c ,1 . (Report 1C0 appears with a custom function key bar.)
@i f fkey$ = 4 gto 010 ; .

. (other processing)

@fky .
@d s p , 0, b ,2 . (Report 2B0 appears with the default function key bar.)

7-130 7831 9274-000

 FMT (Format)

FMT (Format)
The Format (FMT) statement creates a display format for a following output
display, such as that created by a Display Report (DSP) or Output Mask
(OUM) run statement. You can select which fields to display by specifying
either field names or column characters.
✓ 1100: On OS 1100 MAPPER Systems, you can also select columns to print
the next time you call the Auxiliary (AUX) or Print (PRT) run statements.
Format
@FMT[,c,d,r] field[,fleld,...,fleld] .

Following is a description of the subfields:

Field Description

c,d,r Report from which to display fields. Default = -0.

field Fields to display (can be field names or column-character positions).

Comments
• You can use field names or standard column-character syntax to define
report fields:
- If you name the fields, the display includes the columns of each field
as well as the character immediately following the field.
If you use the column-character positions, the run displays only the
columns specified.
• The system always includes column 1, which contains the line type
designator, in the format.
• You can list fields in any order; however, fields are always displayed in
the same order they appear in the report.

7831 9274-000 7-131

 FMT (Format)

FMT (Format)
The Format (FMT) statement creates a display format for a following output
display, such as that created by a Display Report (DSP) or Output Mask
(OUM) run statement. You can select which fields to display by specifying
either field names or column characters.
V 1100: On OS 1100 MAPPER Systems, you can also select columns to print
the next time you call the Auxiliary (AUX) or Print (PRT) run statements.
Format
@FMT[,c,d,r] .

Following is a description of the subfields:

Field Description

c,d,r Report from which to display fields. Default =

field Fields to display (can be field names or column-character positions).

Comments
• You can use field names or standard column-character syntax to define
report fields:
- If you name the fields, the display includes the columns of each field
as well as the character immediately following the field.
- If you use the column-character positions, the run displays only the
columns specified.
• The system always includes column 1, which contains the line type
designator, in the format.
• You can list fields in any order; however, fields are always displayed in
the same order they appear in the report.

7831 9274-000 7-131

FMT (Format)

Examples
Display the St Cd, Ship Date, and Cust Code fields of the current -0:
@fmt 'stcd','shipdate','custcode' .
@dsp , -0 .
Display column 2 for 3 characters, column 45 for 5 characters and column 64
for 7 characters from report 2B0:
@fmt ,O,b,2 2-3,45-5,64-7 .
@dsp,O,b,2 .

7-132 7831 9274-000

 FND (Find)

FND (Find)
The Find (FND) statement scans vertically through one or more reports or a
result for one or more items.
Format
o cc Ityp,p [vrpt,vino]

Following is a description of the fields and subfields:

Field Description

c,d,r Report in which to find the data.

I Line number at which to start the scan.

lab Label to go to if no lines or data are found.

0 Options field (see Options).

CC Column-character positions or names of the fields to scan.

Ityp Line type to scan. If you specify the A option, you can leave this subfield
blank, but enter the comma.

p Find parameters.

vrpt Variable to capture the report number where the first find is made.

vino Variable to capture the line number where the first find is made.

7831 9274-000 7-133

FND (Find)

Options
A Processes all line types.
C(S) Distinguishes between uppercase and lowercase letters.
V 1100: C(x) Alters the find process based on the character set order.
Ordinarily the system processes the report based on the
character set of the drawer. The C option allows you to
choose the character set type on which to base the find. Use
one of the following:
C(F) Full character set (FCS)
C(L) Limited character set (LCS)
C(S) Strict comparison; distinguishes between
uppercase and lowercase letters
Rx(-y I '31 Scans range of reports from report x through report y; scan
reports x,y,...y. (Note that the format Rx,y requires
apostrophes around the comma.)
V 1100: On OS 1100 MAPPER Systems, you do not need to
enclose the comma in apostrophes.
Examples:
r2','5 Scan reports 2 and 5
r2-10 Scan reports 2 through 10
r2-10','14 Scan reports 2 through 10 and 14
Searches for spaces.
Searches for the slant character.

7-134 7831 9274-000

 FND (Find)

Comments
• A find is different from a search. A search creates a result, but a FND
statement loads a variable with the line number where the find is made.
• If the specified data is found, the statement:
Renames the report where the find is made to -0. Note that any
previous -0 result is released.
Loads variables with information.
• To update a single line, use a FND statement followed by a Write Line
(WRL) statement (see WRL in this section).
Example 1: Searching a Drawer for an Item
Search for the letters ip in the St Cd field and capture the report and line
numbers where the find is made:
@frid,O,b " 'stcd' ❑ ,ip vli6,v2i6 .
where:
Uses no options
'stcd' Looks in the St Cd field (column 2 for two characters)
❑ Processes tab lines only
ip Looks for the characters ip
v1i6 Captures the report number where the find is made in vl
v2 i 6 Captures the line number where the find is made in v2

7831 9274-000 7-135

FND (Find)

Example 2: Searching a Report for an Item

Search for the word green in column 15 for 5 characters and capture the line
number where the find is made:
@fnd,O,b,2,6,099 " 15-5 0 ,green ,<I ine>i 6
where:
6 Starts the scan at line 6
099 Goes to label 99 if no finds are made
,, Uses no options
15-5 Scans column 15 for five characters
❑ Processes tab lines only
green Looks for the characters green
<I i ne>16 Captures the line number where the find is made in
<line>
Example 3: Searching for Spaces
Search a field for spaces and capture the line number where the find is
made:
@fnd,O,b,2„099 @ 25-6 ❑ ,Cry ,v1i 6 .
where:
099 Goes to label 99 if no finds are made
@ Uses the @ option to find spaces
25-6 Finds spaces in the Serial Number field (column 25 for
six characters)
❑ Processes tab lines only
Cly Looks for spaces
,v1i 6 Captures the line number where the find is made in vl

7-136 7831 9274-000

 FND (Find)

Using the IFND Run to Create an FND Statement

V This section on using the IFND run applies only to the OS 1100 MAPPER
System.
You can use the Iterative Find (IFND) run to create a FND statement. For
information on how to use the iterative runs, see the Manual Functions
Reference.

7831 9274-000 7-137

GTO (Go To)

GTO (Go To)

The Go To (GTO) statement allows you to transfer control (branch) to
another point in the run.
Format
@GTO flablENDI,n,n,n1ILIN NnILIN -nIRPX
Following is a description of the fields and subfields:

Field Description

lab Line label number (may be a variable).

END[,n,n,n] Call to go to the end of the run (terminates the run and displays the output
area).

For runs started with a Link to Another Run (LNK) statement, n,n,n are up to
three integer status codes that the linked run can pass back to the original
run. The original run can access the codes using the reserved words
STAT1$, STAT2$, and STAT3$. The codes are ignored if the run was not
started via LNK (see LNK in this section).

LIN Current line.

[+]n Integer representing the number of lines following the current line. When the
system encounters continued lines (reverse slant N at the end of a line), it
considers the current line as the last line of the continuation sequence.

-n Integer representing the number of lines preceding the current line. When the
system encounters continued lines (reverse slant [\] at the end of a line), it
considers the current line as the last line of the continuation sequence.

R PX Call to go to another run control report in the same cabinet and drawer and
execute the run statements.

r Report number of a run control report in the same cabinet and drawer (cannot
be a result).

Note: +n, • n,and r can be variables. Do not, however, type a minus sign in
front of the variable. The plus sign is optional with the line number, so
if v1 contained 5, you could use @gto lin v1. Here is another example:
@gto lin v2, where v2 contains the value -5, is the same as saying
@gto lin -5.

7-138 7831 9274-000

 GTO (Go To)

Comments
• The GTO RPX statement executes the run statements in the specified
run control report with these considerations:
The run control report being entered must be in the same cabinet
and drawer as the run that has the GTO RPX statement.
All security checks for the first run must be met by the run control
report being entered.
All variables established in the run having the GTO RPX statement
are valid in the run being entered. Label names used in the calling
run can be used in the RPX run.
The run being entered by a GTO RPX statement need not be
registered. However, since the RPX run control report resides in a
drawer especially for MAPPER runs, inform your coordinator that
you intend to use RPX in the run as part of the run plan.
• For information on computed IF/GTO statements, see IF in this section.
Examples
Go to a line with a label equaling the contents of v6:
@gto v6 .

Terminate the run and display the contents of the output area:
@gto end .
Execute the run statements in report 2 of the same cabinet and drawer
beginning at line 3:
@gto rpx 2 .

Continue executing two lines beyond the current statement line:

@gto lin +2 .

7831 9274-000 7-139

HSH (Hash)

HSH (Hash)
The Hash (HSH) statement assigns a hash number within a specified range
to a given piece of input. As long as the specified range remains the same,
the statement always produces the same numeric value for a given piece of
input.
Format
@FISH v=v1d,min-max

Following is a description of the subfields:

Field Description

Variable to receive the hash value.

vid Data to which the system assigns a hash number. Specify the data using a
variable, constant, reserved word, literal, or any combination.

min-max Range within which the system assigns a hash number, where min is the
lowest number in the range and max is the highest number in the range.

Comments
• The HSH statement performs a routine to assign a numeric value to the
input. As long as the range remains the same, the routine produces the
same numeric value for a given piece of input.
• A hash value can serve as a numeric identifier to index information.
Using a hash value rather than an alphabetic or numeric scheme to
index data ensures a more even distribution of data.
Examples
Index employee information among reports:
@hsh <empinfo>=user$,1-100 .
Assign a hash number within a range of 1 to 100 to the combined input of
the user-id and local site identifier:
@hsh <hash>=user$Ilrsd$,1-100 .

7-140 7831 9274-000

 IDU (Index User)

IDU (Index User)

The Index User (IDU) statement creates a result containing an index of a
specified number of lines from selected reports in a drawer. You can choose
one of these or all three: reports created or updated by a specific user,
reports with specific last update start and end dates, and reports in a range.
Format
@IDU,c,d[,q,user,sdate,endate,srpt,endrpt vrpts,vllnes,
vrptsd,vhirptd] .

Following is a description of the subfields:

Field Description

c,d Cabinet and drawer to index.

q Number of lines to display from each report. Default = all heading lines up to
eight lines.

user User-id to index or "all" to index all users. Default = current user.

sdate First update date to be included in the date range (format DDMMMYY).
Default = all. This is the date of the most recent update to the report, or the
creation date if there are no updates.

endate Last update date to be included in the date range (format DDMMMYY).
Default = current date. This is the date of the most recent update to the
report, or the creation date if there are no updates.

srpt Start report number for report range. Default =1.

endrpt End report number for report range. Default = highest report number.

vrpts Variable to capture the number of reports found.

vlines Variable to capture total number of lines in the reports found.

vrptsd Variable to capture the total number of reports in the drawer.

vhirptd Variable to capture the highest report number in the drawer.

7831 9274-000 7-141

IDU (Index User)

Examples
Index cabinet 0, drawer A, and create a result containing the first three lines
from each report updated by the user newuser:
tDi du ,0,a,3,newuser .
Index a range of reports under the user-id of newuser:
ti)i du ,O,b ,7,newuser ,01 jan90,30no' v '90,5,10 v1i3,v2i9, \
v3i4,v4i4 .
where:
0, b Indexes cabinet 0, drawer B reports
7 Displays seven lines of data from each report indexed
newuser Indexes user-id newuser
01 jan90 Indexes reports starting on January 1, 1990
30no' v ' 90 Indexes reports ending on November 30, 1990
5 Starts index at report 5
10 Stops index at report 10
vii3 Captures number of reports found in v1
v2 i9 Captures number of lines found in v2
v3i4 Captures number of reports in drawer indexed in v3
v4 i4 Captures highest report number created in v4

7-142 7831 9274-000

 IF (If Conditional)

IF (If Conditional)
The If Conditional (IF) statement tests the relationship between two or
more values and specifies the statements to execute when the test condition
is true or false.
Formats
Basic Format
@IF' ,C] vail op val2 stmtl . ; stmt2 .
Logical OR
@IF[ ,C] veil op val2,val3[,va14,...,valn] stmtl . ; stmt2 .
Logical AND
ILDIF[ ,C] vall op va12 & op va13 (45 op va14 ...
... & op vain] stmtl ; stmt2 .

Computational IF/GTO
@IF' ,CI vall op val2,(lab)1,val3,(18b),...,valn,
(lab)] . ; stmtl .

Following is a description of the fields and subfields:

Field Description

C C option to distinguish between uppercase and lowercase characters.

vail Data to compare to another value. You can specify the data as a variable,
constant, literal, or reserved word.

op One of the following relational operators:

= or EQ Equal
GE Greater than or equal
> or GT Greater than
LE Less than or equal
< or LT Less than
NE Not equal
NOT = or NOT EQ Not equal
NOT < or NOT LT Not less than
NOT > or NOT GT Not greater than

continued

7831 9274-000 7-143

IF (If Conditional)

continued

Field Description

val2 Value to compare to vall.

stmtl . Run statement or statements to execute when the condition is true. Include
the space-period-space after the statement. To omit the statement, include
only the space-period-space.

Starts the "else' clause of the condition.

stmt2 . Run statement or statements to execute when the condition is false. Include
the space-period-space after the statement. To omit the statement and
terminate the IF statement, include only the space-period-space.

,val3,valn A comma (logical OR) and a third value, fourth value, and so on.

& op val3 & An ampersand (logical AND), another relational operator, and a third value,
op vain fourth value, and so on.

,(lab) A comma and label number or location in the run to go to if the IF statement
condition is met (TRUE).

Valid entries for lab (computed GTO), in addition to a label number, include
the following:

END End of run

LIN +n Current line plus n lines

LIN -n Current line minus n lines

RPX r Report number r (another run control report), where r is a report

number in the same cabinet and drawer

stmt2 Statement indicating the action to take if the IF statement condition is not met
(FALSE).

Comments
• Use the IF statement for conditional branching or the execution of
another statement.
• If the condition is true, the statements are executed until a branch is
encountered or the equation is terminated with a period. If the
condition is false, the statements following the semicolon are executed.

7-144 7831 9274-000

 IF (If Conditional)

• Always include the space-period-space-semicolon-space-period-space to

terminate the IF statement, even when you omit s tmt 1 or s tmt 2 . For
example, the following IF statement specifies the statement to execute
when the condition is true; when the condition is false, the system
continues execution with the next line in the run:
@if <number> 0 Idv,p <packed>=<number> . ; .

• The IF statement treats spaces and the following characters as zeros in

type A variables:. + -
• In type H variables, characters must be identical to satisfy a true
condition.
V • 1100: The IF statement considers the contents of a type 0 variable as a
decimal value, not octal.
• When you compare substrings of up to 18 characters, the IF statement
considers the characters in the substring as type A variables.
Examples
If USER$ equals newuser, go to label 2; or else go to label 1:
@i f user$ = newuser gto 002 ; gto 001 .

If vl equals v2, load vl with 1 and continue on the next line; or else release
the screen:
@i f v1 = v2 Idv v1=1 . ; rel .

If <vall> and <val2> are not equal, go to label 3; or else release the screen:
@i f <val1> ne <val2> gto 003 ; rel .

If v21 is greater than v20, go to label 3; or else execute the IF statement:

@i f v21 > v20 gto 003 ; if v21 < v15 inc v21 . ;

If <num> equals 2 OR 4, go to label 1; or else continue:

@i f <num> eq 2,4 gto 001 ; .

If vl is greater than 0 AND less than 100, go to label 3; or else continue:

@if v1 > 0 & < 100 gto 003 ; .

7831 9274-000 7-145

IF (If Conditional)

If v22 is greater than 10 AND less than 50, go to label in v99; or else
continue:
@i f v22 > 10 & < 50 gto v99 ;

This example uses two IF statements. If vl equals A and if v2 is less than

B, go to label 1; or else continue:
@i f v1 = a if v2 It b gto 001 ; .

The following examples use a computed IF/GTO sequence.

If <total> equals 30, go to label 1; if <total> equals 40, go to label 2; if
<total> equals 50 OR 60, go to label 3; or else continue:
@i f <total> = 30,(001),40,(002),50,60,(003) ; .

If v2 equals 4, go to the second line following current line, OR if v2 equals 5,

go to the end of the run; or else continue:
@i f v2 = 4, ( I i n +2),5,(end) ; .

If vl equals 2, execute the Load Variable (LDV) statement (load v3 with the
value 4), go to label 1 and continue; if vl does not equal 2, go to label 2:
@i f v1 = 2 Idv v3=4 gto 001 ; gto 002 .

Execute the LDV statement (load v3 with the value 4) only if vl equals 2; in
either case (TRUE or FALSE), go to label 2 and continue:
@i f v1 = 2 Idv v3=4 ; gto 002 .

Note that in the previous example, the run goes to label 2 even if the
condition of the IF statement is not met, because the GTO statement is the
next logical statement to execute.
This example uses an unknown trailing substring. (The 0-3 specifies the
last three characters; the starting column position is unknown.) If the last
three characters of vl contain the letters mon, go to label 25:
@if v1(0-3) = mon,(025) ; .

7-146 7831 9274-000

 IF (If Conditional)

This example uses a known trailing substring. (The 3-0 specifies the known
starting position of 3 for the remainder of the field.) If the characters
beginning with character 3 through the end of the field contain the letters
fri, go to label 26:
@i f v1(3-0) = fr i,(026) ; .
If the value of <testl> is equal to <count>, the value of <testi.> is increased
by 1; otherwise, <testi.> is increased by 2:
@if <testi> = <count> inc <testi> . ; inc,2 <testi> .

7831 9274-000 7-147

IND (Index)

IND (Index)
The Index (IND) statement creates a result containing a listing of a specified
number of lines from all reports in a drawer.
Format
@IND,c,d[,q, lab] .

Following is a description of the subfields:

Field Description

c,d Cabinet and drawer to index.

q Number of lines to display from each report. Default = heading lines (up to eight).

lab Label to go to if the drawer does not exist.

Reserved Words
STAT1$ contains the number of reports in the drawer.
STAT2$ contains the total number of lines in the drawer.
Comments
• The result contains a date line and lists the number of reports in the
drawer, the total number of lines in the drawer, the number of lines
contained in each report, and a specified number of lines from each
report.
• If you are indexing reports that are fewer than 80 characters wide, the
information containing the number of lines from each report is added as
trailer lines.
Example
Index cabinet 0, drawer A, and create a result containing the first four lines
from each report in the drawer (if no report exists, go to label 2):
@ind,O,a,4,002 .

7-148 7831 9274-000

 ITV (Input Variable)

ITV (Input Variable)

The Input Variable (ITV) statement accepts all input from an Out Variable
(OUV) or interim Output (OUT) display by loading variables with the
output.
Format
@ITVI,lab] v[,v...,v] .
Following is a description of the subfields:

Field Description

lab Label to go to if the user presses a function key.

v Variables in which to capture input (up to 40 variables).

Comments
• The OUV/ITV combination does not alter or affect the current -0.
• The ITV statement following an OUV or interim OUT stalls the run
until the user presses a function key or Transmit. While the run is
stalled, the ITV statement controls the terminal and all input.
• Normally, if output is on display and you enter data on the control line
and press Transmit, MAPPER software interprets the input. With the
ITV statement, any data entered on the control line is ignored by
MAPPER software and interpreted by the ITV statement. You can
capture data entered on the control line if you place a tab character at
home position.
• Data starts from a tab character; data following the first tab character is
captured in the first variable, data following the second tab character is
captured in the second variable, and so on.

7831 9274-000 7-149

ITV (Input Variable)

• The ITV statement resets the I/O and LLP count.

• The length of an individual input field varies depending on the variable
length or by what follows the tab character. The length of each data
input is determined by the tab delimiter, the length of the variable, or
the width of the run user's terminal.
• If the run user presses a function key while the ITV statement is active
and the statement contains a label, the run continues at the label.
FKEY$ contains a number indicating the function key pressed (contains
0 if the run user pressed Transmit with the cursor positioned below the
control line).
Examples
This example captures input from an OUT statement:
• brk .
Product:1
Description:I
• brk out,-0,2,3,1,1,y,y .
• itv,010 <product>s10,<desc>s10 .

. (other processing)

@010: . respond to function key

@ if fkey$ = 1,(020),2(030) .
This example captures input from an OUV display:
• ouv,1,15 'what is the password?'I
• itv <password>s6 .

7-150 7831 9274-000

 JUV (Justify Variable)

JUV (Justify Variable)

The Justify Variable (JUV) statement reformats the contents of numeric
variables. Normally, you reformat the contents of a variable before
displaying the value on the screen or writing it to a report.
V 1100: On OS 1100 Systems, you can reformat the contents of numeric
variables up to 18 characters in length.
Once justified, a variable retains that justification until its contents are
altered.
Format
@JUV,o v[,v,...v]
Following is a description of the subfields:

Field Description

o Options field (see Options). Use only one option.

v Variable to reformat. If the variable you specify does not contain numeric data, the
system does not change the variable.

7831 9274-000 7-151

JUV (Justify Variable)

Options
C Inserts commas in the integer portion of the variable every third
digit, eliminates leading zeros, right-justifies the contents, and blank
fills all remaining characters to the left of the number.
Notes: 1. You must remove commas inserted by the C option
before executing a Change Variable (CHG) or If
Conditional (IF) statement against the variable. Use
any other option to remove commas.
V 1100: On OS 1100 Systems, you do not need to remove
commas before using CHG or IF statements.
2. If inserting commas would expand the variable beyond
the defined size of the variable, the variable remains
unchanged.
D Deletes all commas and leading zeros, and right-justifies the
contents within the variable.
L Eliminates leading and trailing zeros, left-justifies the contents, and
blank fills all remaining characters to the right of the number.
R Eliminates leading and insignificant trailing zeros, right-justifies the
contents, and blank fills all remaining characters to the left of the
number.
X Eliminates leading zeros, left-justifies the contents, and zero fills all
remaining characters to the right of the number.
Z Eliminates insignificant trailing zeros, right-justifies the contents,
and zero fills all remaining characters to the left of the number.

7-152 7831 9274-000

 JUV (Justify Variable)

Examples
In the following examples, A stands for a blank character position.
Initialize <string> to a type A, 12-character variable with a value of
6543.210:
@Idv <str ing>a12=6543.210 . <string> = 6543.210AA00

Insert commas in <string>:

@jay ,c <string> . <string> = AAA6,543.210

Delete commas from <string>:

@juv,d <string> . <string> = 0A006543.210

Left-justify the contents of <string>:

@juv, I <string> . <string> = 6543 2100A00
Right-justify the contents of <string>:
@juv,r <string> . <string> = 0006.06543.21

Expand the contents of <string>:

@juv,x <string> . <string> = 6543.2100000

Right-justify the contents of <string> and add leading zeros:

@juv,z <string> . <string> = 000006543.21

7831 9274-000 7-153

KEY (Function Key Input)

KEY (Function Key Input)

The Function Key Input (KEY) statement lets you obtain a number via the
FKEY$ reserved word that indicates the function key the run user pressed
to move on from a noninterim Display Message (DSM), Display Report
(DSP), Output (OUT), or Screen Control (SC) display. Use a KEY statement
before DSM, DSP, OUT, or SC statements.
Note: A noninterim display is a screen displayed by a run that remains on
display until the run user transmits or resumes.
Use the KEY statement only with output displays that do not use a function
key bar (for example, the DSP statement displays the default MAPPER
function key bar) since the functions on the function key bar override the
effect of the KEY statement. See SC and FKY in this section for information
about using a function key bar.
Format
@EY .
Reserved Word
FKEY$ contains a number indicating the function key pressed (contains 0 if
the run user pressed Transmit with the cursor positioned below the control
line).
Example
Request function key input with the KEY statement and display report 2B0
using the OUT statement:
@key .
@out ,-0,4,1 .
Following these statements, the run can test FKEY$ for its contents and
proceed accordingly.

7-154 7831 9274-000

 LCH (Locate and Change)

LCH (Locate and Change)

The Locate and Change (LCH) statement scans specific column-character
positions of a report for a specified target string and changes it to a specified
replacement string, creating a result.
Format
@LCH,c,d,r[,1,1ab] o cc tgtstr/replstr [orlines,vrpt]

Following is a description of the fields and subfields:

Field Description

c,d,r Report in which to locate and change data.

I Line number at which to start the scan. (The LCH statement processes data
lines only; if you specify a heading line, the scan begins with the first data
line.)

lab Label to go to if no target string is located.

o Options field. The A, F, and M options are always assumed (see Options).

cc Column-character positions or names of the fields to be scanned.

tgtstr Characters to locate.

replstr Characters with which to replace the target string.

, A skipped subfield. (This subfield is not used in LCH statements. Type the
comma before entering the other variables.)

vlines Variable to capture the number of lines located that contain the target string.

vrpt Variable to capture the report number where the target string is located.

7831 9274-000 7-155

LCH (Locate and Change)

Options
A Processes all line types. If used alone, this option instructs the
system to ignore the first character of the target string, and to
change the line type of all lines having finds to the first character of
the replacement string. The A, F, and M options are always
assumed.
C Distinguishes between uppercase and lowercase characters.
Without this option, case is ignored.
V 1100: On OS 1100 MAPPER Systems, tnis option applies only to full
character set (FCS) reports.
F Processes all line types and uses the first character of the tgtstr
and repistr subfields as part of the target and replacement
strings. The A, F, and M options are always assumed.
V 1100: On OS 1100 MAPPER Systems, the F option processes all line
types and locates and changes the entire string. It does not locate
strings that start in column one. The A, F, and M options are always
assumed.
M Treats the first character of the target string as the line type
designator. This option takes the place of a line type subfield
(normally shown as i t yp). You must use the M option to locate a
string beginning in column 1. The A, F, and M options are always
assumed.
O Creates a result containing the items found.
OU Creates an update result, after which you can do one of the
following:
• Delete the found lines from the report with a Delete (DEL)
statement.
• Delete the found lines from the report and place them in a result
(-0) with an Extract (EXT) statement.
• Make changes to the update result and blend the updated lines
from the result back into the report with an Update (UPD)
statement.

7-156 7831 9274-000

 LCH (Locate and Change)

Sx Starts the scan at line x, where x is a positive number.

Sx-y Starts the scan at line x and stop at line y.
Sx','n Starts the scan at line x and scan for n lines. Be sure to enclose the
comma within apostrophes ( ' ).
'' 1100: On OS 1100 MAPPER Systems, you ao not neea Lo enclose the
comma in apostrophes.
Tx Sets x to a transparent character to match any character in that
position. Do not, however, use the transparent character in the first
character position of the target string. The default transparent
character is a space.
V 1100: On OS 1100 MAPPER Systems, if the replacement string is
shorter than the target string, the rightmost characters are filled
with the specified transparent character.
Example
Change the word execution to processing:
tPlch,0,a,1,40,099 atm 2-79 execution/processing ,X
<Iines>i4 .

where:
40,099 Starts scan at line 40 and goes to label 99 if no target
string is located
afm Uses A, F, and M options
2-79 Starts scan in column 2 for 79 characters
execut i on/ Specifies target and replacement strings: each
processing time the word execution is encountered, replace it
with the word processing
<lines>i4 Captures the number of lines located that contain
the target string in <lines>

7831 9274-000 7-157

LCV (Locate and Change Variable)

LCV (Locate and Change Variable)

The Locate and Change Variable (LCV) statement finds and optionally
replaces data within a variable.
With the LCV statement, you can locate a string, change a string, count the
number of occurrences, or compare two variables literally.
An LCV statement is to variables what a Locate (LOC) or Locate and
Change (LCH) statement is to data in reports.
Format
QLCV[dab] o v tgtstr[/repIstr vpos,voces]
Following is a description of the fields and subfields:

Field Description

lab Label at which to continue execution when no finds are made or when n
occurrences are not found (see the Bn option). To continue execution at the
label when a find is made, use the N option. (To simplify your run logic, if you
want the run to continue on the next line, use LIN1 in this subfield instead of a
label number.)

o Option that determines how to search the variable for data (see Options).

v Variable to be scanned. You can specify any type of variable, and you can
specify a substring or an array member.

tgtstr The data you want to locate within the variable (called the target string). You
can specify the data using a variable, literal, constant, or reserved word.

Within the target string, the transparent character is a wildcard character; that
is, the transparent character matches any character in that position.

The default transparent character is the space. Therefore, any spaces in the
data are treated as wildcard characters. You can use the Tx option to
change the default transparent character when you need to locate spaces.

continued

7-158 7831 9274-000

 LCV (Locate and Change Variable)

continued

Field Description

replstr The data (from 0 to 256 characters) to replace the target string. If you do not
use the Bn option, the statement replaces all occurrences of the target string
with the replacement string.

To completely remove the target string, enter nothing for the replacement
string (for example, target/ ).

vpos Variable to capture the character position within the variable of the first
occurrence of the target string.

With the Bn option, vpos captures the character position of the nth
occurrence of the target string within the variable.

voccs Variable to capture the number of occurrences of the target string within the
variable. This is useful when doing a change or locate with the B option.

Options
B(n I n-x) Bail out option—with the Bn and Bn-x option, indicates which
occurrences of the target string are to be processed.
Bn Locates only the nth occurrence of the target string
(variable vpos captures the character position within
the variable of the nth occurrence), or locates and
changes n occurrences (vpos contains the character
position of the first changed occurrence).
Bn-x Locates and changes from n through x occurrences of the
target string, where n is the first occurrence to process
and x is the number of subsequent occurrences from n to
process. Variable vpos captures the character position
of the first changed occurrence.
C Distinguishes between uppercase and lowercase characters.
Lr Locates a specific line type where x is the line type. The first
\......" character in the variable must match the line type designator
the statement stops processing variable.

7831 9274-000 7-159

LCV (Locate and Change Variable)

M Uses the transparent character (see the Tx option) as a mask to

inhibit replacements. Characters in the variable that correspond
to the positions of the transparent characters in the target string
are not replaced with those in the replacement string.
N Goes to the specified label when a find is made rather than when
no finds are made.
Tx Specifies the character to use as the transparent character. The
transparent character is a wildcard character used to match any
character in the corresponding position. You can also use the
transparent character as a mask to inhibit replacements (see the
M option). Default = space character.
Example 1: Locating Second Occurrence of an Item
Contents of vl for this example:
v1=doghorsecowpigbirdcatcatcatcatmouse

column 15 column 34
locate columns

Locate the second occurrence of the word cat in vl starting at column 15 for
20 characters:
@lcv,001 b2 v1(15-20) cat v2i6 .
where:
001 Goes to label 1 if fewer than two occurrences of the word
cat are found
b2 Bails out on the second occurrence of the word cat
v1(15-20) Scans vl starting in column 15 for 20 characters
ca t Locates target string cat
v2 i 6 Captures the character position where the second
occurrence of the word cat begins
After the statement executes, v2 contains 22 (the column in vl where the
second occurrence of the word cat was found).

7-160 7831 9274-000

 LCV (Locate and Change Variable)

Example 2: Counting Occurrences of an Item

Contents of vl for this example:
CAT d o gCATDOGCATDo gCATDOGCAT d o g
Count the number of times the word dog occurs in vl:
@lcv b99 vi dog ,v3i6 .
where:
b99 Bails out on the 99th occurrence of the word dog
v1 Scans vl (the entire variable)
dog Locates target string dog
v3 i 6 Captures the number of occurrences of the word dog in v3
In this example, the bail-out count was set to a value higher than the
number of occurrences of the word dog because we did not want to bail out.
V3 continues to count each occurrence of the word dog. After the statement
executes, v3 contains 5.

7831 9274-000 7-161

LCV (Locate and Change Variable)

Example 3: Changing Character Strings

Contents of vl for this example:
*CATDOGCATDOGCATDOGCATDOGCATDOG

Change the second, third, and fourth occurrences of the word DOG to cat in
v1:
iP1 cv l*b2-3 v1 DOG/cat v2i6 .

where:
l* Makes the change only if the first character of vl is an
asterisk (the line type indicator)
b2-3 Changes target string starting at the second occurrence for
three occurrences
v1 Scans vl
DOG Locates target string DOG
cat Changes target string DOG to cat
v2 i 6 Captures character position of first occurrence of target
string changed
Since the first character of v1 matches the character specified in the L
option, the change is made. V2 equals 11 and v1 contains:
*CATDOGCAT c a t CAT c a t CAT c a t CATDOG
1 2 3 4 5
v2=11

7-162 7831 9274-000

 LCV (Locate and Change Variable)

Example 4: Comparing Strings

Contents of <stringl> for this example:
abc 123
Contents of <string2>:
abc+++

Compare <stringl> to <string2>:

@lcv,001 " <stri ngl> <s t r i ng2>
where:
001 Goes to label 1 if <stringl> is not equal to <string2>
Uses no options
<s t r i ng1> Compares <stringl> with <string2>
<s t r i ng2>
Since <stringl> is not equal to <string2>, the run goes to label 1.
Remember, if you use the N option, the run does not go to the label unless
the two variables are equal.

7831 9274-000 7-163

LCV (Locate and Change Variable)

Example 5: Masking Transparent Characters in the Replacement

String
Contents of vl for this example:
blackboxl*blackcanl*blackbagl*blackcupl

Use the M option to locate each occurrence of the string black followed by
any three characters, followed by the number 1. Each time the locate string
is found, the characters black are changed to green, the next three
characters remain unchanged, and the last character, 1, is changed to 2.
@Icv m vl 'black/1M1'/'green 2' v2i6,v3i6 .

where:
m Specifies the mask option — transparent characters
in the replacement string are not inserted into the
variable being changed
vl Scans vl
'blacktAi\l'/ Specifies the target string and change string
delimiter ( / )
'green 2' Specifies the replacement string (characters with
which to replace each occurrence of the target string)
v2i6 Captures the column of the first occurrence changed
in v2i6
v3 i 6 Captures the number of occurrences changed in v3i6
V1 now contains:
greenbox2*greencan2*greenbag2*greencup2

7-164 7831 9274-000

 LCV (Locate and Change Variable)

Example 6: Using an Unknown Trailing Substring

Contents of vl for this example:
feature010101
Use an unknown trailing substring and bail out after the second find:
@lcv,001 b2 v1(0-6) 01 v2i3
where:
001 Goes to label 1 if no finds are made
b2 Bails out after the second occurrence
v1(0-6) Scans the last six characters of vl (the 0-6 specifies the
last six characters — the starting character position is
unknown)
01 Locates the target string 01
v2 i 3 Captures the character position where the second
occurrence of 01 begins in the specified substring (in this
example, v2 contains 10 because the second 01 begins in
the tenth column of v1)
Example 7: Using a Known Trailing Substring
Contents of <money> for this example:
=dollars
Use a known trailing substring to scan column 4 through the end of the field
and changes the word dollars to the word yen in all occurrences:
@lcv,001 " <money>(4-0) dollars/yen .
where:
001 Goes to label 1 if no finds are made
V P
Uses no options
<money>(4-0) Scans <money> beginning with column 4 through
the remaining characters (the 4-0 specifies the
known starting position of 4 through the end of the
field)
do I Iars/yen Changes the target string dollars to yen
7831 9274-000 7-165
LDA (Load Variable Array)

LDA (Load Variable Array)

The Load Variable Array (LDA) statement defines a variable array and puts
data into the array. Each variable in an array is referred to as a member of
the array.
V 1100: The run control report must be in full character set (FCS or FCSU).
Format
QUA[,o] nametypesize[n]=vid[,vId...,vtd] .
Following is a description of the subfields:

Field Description

o Option that determines how data is put into the variables in the array (see
Options).

nametypesize Name of the variable array to initialize immediately followed by the variable
type and number of characters allowed in each member of the array.

[n] Number of members in the array. Brackets are required.

vid Information to load in each member of the array (variables, literal data,
constant, or reserved word).

Options
C Centers data within the variable.
L Left-justifies the data within each variable.
P Packs data into each variable so that the variable contains only
significant characters.
If you pack data that does not contain any significant characters,
the variable into which you packed the data becomes a variable
of 0 length. And, if you try to use a variable of 0 length in a run
statement, the results are unpredictable.
To avoid creating a variable of 0 length, use the Define (DEF)
run statement to determine the packed size of a variable before
you pack it. See DEF in this section.

7-166 7831 9274-000

 LDA (Load Variable Array)

R Right-justifies the data within each variable.

U Converts all lowercase alphabetic characters to uppercase
characters.
V 1100: W Loads variables with the values of reserved words. (The
reserved word values are left-justified. Make sure the variables
are large enough to hold the values of the reserved words.)
Z Zero fills each variable after the data is loaded. Right-justified
variables are zero-filled to the left; left-justified variables are
zero-filled to the right.
Comments
• Each variable in the array is counted as one variable of the total number
of variables allowed on the system.
V • 1100: Array members consume string variable space, regardless of the
variable type.
• When you pass a variable array to a Call Subroutine (CALL) statement
without specifying the array size ( [ n ]), you can access all members of
the array, but they count as only one of the 40 allowed to be passed.
• Use variable arrays to stack variables for the CALL statement.
• You cannot redefine the variable array, the size, or the type of any
member of the array.
• Use brackets and numbers following the variable array name to access a
member of the array. See the following example.

7831 9274-000 7-167

LDA (Load Variable Array)

Example
Initialize an array of variables called <qty> as an integer array containing
five array members, and load information into each member of the array:
@Ida <ci ty>i 61 51=1, 12, 123, 1234, 12345 .
The members <qty>[1] through <qty>[5] contain the following information:
<qty>[ 1] = 1
<qty>121 = 12
<qty>13] = 123
<qty>14] = 1234
<qty>151 = 12345

7-168 7831 9274-000

 LDV (Load Variable)

LDV (Load Variable)

The Load Variable (LDV) statement initializes and loads variables. See also
"Loading Variables Based on Content" in this subsection.
Format
@EDV[,o] v=vid[,v=vid,...v=v1d] .
or
@i0V,0 .

Following is a description of the subfields:

Field Description

o Option that determines how data is put into the variable or variables (see Options).

v Variable into which you want to put data. To define or redefine the variable,
include the variable type and size.

vld Data you want to put into the variable. You can specify the data using a literal,
constant, variable, reserved word, or any combination of these.

Options
C Centers data within the variable.
V 1100: H Tests the remote run link. Use the format LDV,H v=rms, where
v is the variable to capture the result (0 = offline; 1 = online)
and rms is the remote site number.
L Left-justifies the data within the variable.

7831 9274-000 7-169

LDV (Load Variable)

Packing Variables
With the P option, you can delete leading or trailing spaces from a variable.
This is called packing a variable. Do not, however, pack a variable to
contain no characters at all. If you do, other functions trying to use the
variable may err.
Once you pack a variable to contain fewer than its original number of
characters, you must reinitialize the variable to make it larger. If you try to
place more than the original number of characters in a variable, you lose the
extra characters.

Loading Variables Based on Content

The Q option allows you to load variables based on tab characters (or a
specified delimiter) contained in the variable. The receiving variable is
loaded with the data from the specified tab character (or delimiter) to the
next tab set in the variable. Use the Q option when processing variables
initialized using INVR1$ or INSTR$.
Format
@LDV,Q rv=iv,n1(delim),rv=iv,n(delim)...,rv=iv,n(delim)] .
Following is a description of the subfields:

Field Description

/V Receiving variable.

iv Issuing variable.

n Number of delimiters in iv to skip before loading data. Default = 1. This

subfield must be a literal value.

(delim) Character to use as a delimiter. Default = tab character. The parentheses are
required.

7-172 7831 9274-000

 LDV (Load Variable)

LDV (Load Variable)

The Load Variable (LDV) statement initializes and loads variables. See also
"Loading Variables Based on Content" in this subsection.
Format
@EDV1,01 v=v1ri[,v=v1d,...v=v1d] .
or
@t011,0
Following is a description of the subfields:

Field Description

0 Option that determines how data is put into the variable or variables (see Options).

Variable into which you want to put data. To define or redefine the variable,
include the variable type and size.

vld Data you want to put into the variable. You can specify the data using a literal,
constant, variable, reserved word, or any combination of these.

Options
C Centers data within the variable.
V 1100: H Tests the .emote run link. Use the format LDV,H v=rms, where
v is the variable to capture the result (0 = offline; 1 = online)
and rms is the remote site number.
L Left-justifies the data within the variable.

7831 9274-000 7-169

LDV (Load Variable)

P Packs the data in a variable so that the variable contains only

significant characters. Use this option to remove unnecessary
leading and trailing spaces.
If you pack a variable that does not contain any significant
characters, the variable will contain no characters at all and
other functions may not be able to use it. To avoid this
condition, use the DEF run statement before packing a variable
to determine its packed size. See "Packing Variables" in this
section.
Q Loads delimited data from a variable or reserved word into
another variable. See "Loading Variables Based on Content" in
this section.
R Right-justifies the data within the variable.
S Case sensitivity; differentiates between uppercase and lowercase
character input when using the N option. Use the S option only
with the N option; specify NS and not SN for this option.
U Converts all lowercase alphabetic characters to uppercase
characters.
V 1100: W Loads the variable with the value of the reserved word. (The
reserved word value is left-justified. Make sure the variable is
large enough to hold the value of the reserved word.)
Z Zero fills the variable after the data is loaded. Right justified
variables are zero-filled to the left; left-justified variables
zero-filled to the right.
Comments
• Use an LDV statement to perform these tasks:
Initialize variables.
Load variables from other variables.
Load variables with literal data.
Load variables already initialized.
Load a substring of a variable already initialized. Use the substring
format (posit lon•characters) to load a substring.

7-170 7831 9274-000

 LDV (Load Variable)

Load variables with the contents of reserved words.

Load a variable with its own contents.
When you load a variable with its own contents, you need only
specify the receiving variable. This is particularly useful for packing
variables. You can use, for example, @I dv,,p <var1>,<var2> rather
than @I dv ,p <va r 1>=<va r 1> ,<va r 2>=<va r 2> . Loading variables
in this manner is also useful when centering, left justifying, right
justifying variables, and initializing space filled variables without
setting the characters equal to spaces.
• Whenever an LDV statement encounters a space or comma, it stops
loading the variable with data. To place a space or comma in a variable
without placing either character in a variable beforehand, enclose spaces
and commas in apostrophes.
• You cannot do arithmetic computations with an LDV statement as you
can with a Change Variable (CHG) statement (see CHG in this section).
However, an LDV statement is faster and more efficient than a CHG
statement for loading literal data and reserved words.

Loading Multiple Variables

In the following example, the first LDV statement loads vl through v4; the
second LDV statement then loads these four variables into v5:
@I dv <st r1>a5=Th i s ,<s t r2>a3=i s,<st r3>a3=an,<st r4>a8=examp le .
@I dv <st r ng>s40=<st r1><str2><st r3><st r4> .

<string> now contains the words "This is an example".

7831 9274-000 7-171

LDV (Load Variable)

Packing Variables
With the P option, you can delete leading or trailing spaces from a variable.
This is called packing a variable. Do not, however, pack a variable to
contain no characters at all. If you do, other functions trying to use the
variable may err.
Once you pack a variable to contain fewer than its original number of
characters, you must reinitialize the variable to make it larger. If you try to
place more than the original number of characters in a variable, you lose the
extra characters.

Loading Variables Based on Content

The Q option allows you to load variables based on tab characters (or a
specified delimiter) contained in the variable. The receiving variable is
loaded with the data from the specified tab character (or delimiter) to the
next tab set in the variable. Use the Q option when processing variables
initialized using INVR1$ or INSTR$.
Format
@LDV,0 rv=iv,n1(delim),rv=iv,n(delim)...,rv=iv,n(delim)] .
Following is a description of the subfields:

Field Description

ry Receiving variable.

iv Issuing variable.

n Number of delimiters in iv to skip before loading data. Default =1. This

subfield must be a literal value.

(delim) Character to use as a delimiter. Default = tab character. The parentheses are
required.

7-172 7831 9274-000

 LDV (Load Variable)

LDV Examples with Various Options

The following statements are shown as if in sequential order in a run. The
A stands for a blank character position.
Initialize vl to 1:
@I dv v1i2=1 .
Initialize vl to the letter a and v2 to 10:
thldv v1a1=a,v2i2=10 .
Load vl with This is dataAAAAAAAA•
@I dv v1s20='Th is is data' .
Load vl with AdaLLALL62LVIMALMAL.
@I dv ,c v1=2 .
Load vl with 2:
@I dv ,p v1=2 .
Load vl with ALLAALSAMALMALMALl.
@I dv , r v1s20=1 .
Load vl with 00000000000000000001:
@Idv,rz v1=1 .
Load vl with Ada.6.6.6.6.6.6AaLdaZZA6,-1-
@1dv,r v1=-1 .
Load vl with -0000000000000000001:
@I dv , r z v1=-1 .
Load vl with /1M20000000000000001:
@I dv , r v1(1-4)=2 .
Load vl with 00020000000000000001:
@I dv , r z v1(1-4)=2 .

7831 9274-000 7-173

LDV (Load Variable)

Load vl with ABCdOileS.M.O.O.O.MLAM.6.6.

@Idv,u v1=abc .

Load <cab> with the cabinet number, <drawer> with the numeric drawer
number, and <report> with the report number of the last report or result
processed or on display:
@Idv,w <cab>i4=cab$,<drawer>i6=drw$,<report>i4=rpt$ .

If NEWUSER is on station 12, v4 contains abcjdol2xyz:

@Idv,pw v4s20='abc'user$(1-3)stnum$xyz .

Use an unknown trailing substring to load v2 with the minutes and seconds
(MM:SS) substring from vl (the 0-5 specifies the last five characters, but the
starting character position is unknown):
@Idv,w v1a8=time$ . v1 now contains hh:nrEss
@Idv v2i5=v1(0-5) . v2 now contains mm:ss

Use a known trailing substring to load v2 with the seconds (SS) substring
from vl (from the previous example — the 7-0 specifies the substring
beginning with the seventh character through the end of v1):
@Idv v2i2=v1(7-0) . v2 now contains ss

7-174 7831 9274-000

 LFC (Load Format Characters)

LFC (Load Format Characters)

The Load Format Characters (LFC) statement captures the format of the
current report or result (-0). Use it, for example, when the run user might
start your run with a displayed report that has been shifted or reformatted
using the Create Temporary Format (VIEW) function (see the online help
system [HELP,VIEW]).
Format
@LFC v .
Following is a description of the field:

Field Description

v Variable to capture the format of the report or result currently on display.

Comments
• The variable receives a string of Xs and blank characters. The Xs stand
for character positions displayed, similar to report 0.
• An LFC statement works only in runs registered as format sensitive.
• Use an Set Format Characters (SFC) statement after an LFC statement
to set format characters.
Example
Capture the format of the current result in variable vl:
tbl tc vls80
The variable receives a string of Xs and blank characters. The Xs stand for
character positions displayed, similar to the format lines in report 0.

7831 9274-000 7-175

LFN (Load Field Name)

LFN (Load Field Name)

The Load Field Name (LFN) statement loads variables with the names of
report fields that correspond to the column-character positions supplied.
Format
@LFN[,c,d,r,tics?,lab] cc v[,v,...,v]

Following is a description of the field and subfields:

Field Description

c,d,r Report from which to load field names. Default = -0.

tics? Enclose the field name in apostrophes, Y or N. Default = N.

lab Label to go to if the field name cannot be loaded.

cc Column-character positions of the fields.

v Variables to load with field names.

Reserved Word
STAT1$ contains one of the following codes in case of an error:
1 Report heading is improperly formatted for field names.
2 Columns supplied do not fall within field boundaries.
3 Field name in the report heading has no significant characters.
4 Field name is not unique in the report heading.
5 Field name was truncated because of the variable size, and the name
is not unique in the report heading.
STAT2$ contains the number of the field in error.

7-176 7831 9274-000

 LFN (Load Field Name)

Comments
• See Section 3 for a general description of named fields.
• The LFN statement is especially useful for converting an existing run to
one that uses named fields. It is also useful for translating column
position data, such as that obtained from the Output Mask (OUM)
statement (see OUM in this section), into field names.
• You can have field names enclosed in apostrophes; this makes it easier
for you to create run statements.
• If a specified variable is not large enough to contain an entire field
name, any trailing characters in the name are truncated.
• If the specified columns do not represent an entire field, the statement
loads the name followed by a partial field description.
• If the run cannot load a field name, it continues at the label.
• If the statement has no label and a field name cannot be loaded, the run
continues at the next statement, loading the variable with the actual
column-characters (for example, 2-2).
Example
Load field names from report 2B0:
@I fn,0,b,2,y 2-2,45-3 v1h18,v2h18 .

where:
0, b , 2 Loads field names from report 2B0
y Encloses field names in apostrophes
2-2,45-3 Gets names from column 2 for two characters and
column 45 for three characters
v1h18 Loads vl with the name from positions 2-2 (v1 = 'StCd')
v2h 18 Loads v2 with the name from positions 45-3
(v2 = 'CustCode(1-3)')

7831 9274-000 7-177

LNK (Link to Another Run)

LNK (Link to Another Run)

The Link to Another Run (LNK) statement executes another run in the
MAPPER system.
Format
@LNK run[,vid] .
Following is a description of the subfields:

Field Description

run Name of the other run to start.

vld Up to 40 input parameters consisting of variables, literals, reserved words,

constants, or any combination of these. When the run starts, it uses their
values to initialize variables via 1NPUT$. Pack or right-justify all variables.

Reserved Word
LINK$ contains 0 if the run is not started by a LNK statement or nonzero if
the run is started by a LNK statement.
Comments
• A LNK statement differs from a Run Start (RUN) statement, in that
when it starts a run that executes a GTO END statement, it returns
control to the calling run. See RUN and GTO in this section.
• The system can transfer up to 40 input parameters, as well as the
current result (-0), to the called run for processing.
• You cannot link to a run that is registered for a greater number of
variables, labels, or variable characters.
V 1100: On OS 1100 MAPPER Systems, registering runs for different
numbers of variables, labels, or variable characters is not available.
• The called run can return up to three numeric status codes via the
GTO END statement, which you can use to signify whatever you like.
The current -0 result is also available to the calling run. To capture the
numeric status codes once control returns to the calling run, examine
the reserved words STAT1$, STAT2$, and STAT3$.

7-178 7831 9274-000

 LNK (Link to Another Run)

• If the called run terminates with a Release Display (REL) statement,

because of an error, or if the run user executes a Display Graphics
(DSG), Display Report (DSP), Output Mask (OUM), Output (OUT), or
Screen Control (SC) statement, the calling run does not resume.
• A run started by a LNK statement cannot itself contain another LNK
statement unless you use a Clear Link (CLK) statement first to clear the
original link.
• You can link to several utility runs, including chart runs and the
Application Power Tools (APT) INFO run. See the online help system
(HELP,@LNK) for details.
• Do not place other run statements on the same line after the LNK
statement. Other run statements following it on the same line are
ignored. Put the next run statement on a new line.
Example
Execute a run named test and pass the variables <first> and <second> to
the linked run; when the linked run completes execution and passes control
back to the original run, test the contents of STAT1$:
@Ink test,<first>,<second> .
@if statl$ = 5 gto 100 .
The run named test returns control to the original run and passes three
status codes to the run:
@gto end,5,10,20 .

7831 9274-000 7-179

LOC (Locate)

LOC (Locate)
The Locate (LOC) statement locates a character string within a report or
result and, with the 0 or OU option, creates a result.
Format
@LOC,c,d,r[,1,101:0] o cc tgtstr [vcol,vIno,vrpt] .

Following is a description of the fields and subfields:

Field Description

c,d,r Report in which to locate a string of characters.

I Line number at which to begin the scan. (The LOC statement processes data
lines only; if you specify a heading line, the scan begins with the first data line.)

lab Label to go to if no target string is located.

o Options field. The A, F, and M options are always assumed (see Options).

cc Column-character positions or names of the fields to be scanned.

tgtstr String of characters to be located.

vcol Variable to capture the number of the column preceding the column where the find
starts.

vino Variable to capture the line number where the target string is located.

vrpt Variable to capture the report number where the target string is located.

Options
A Processes all line types. If used alone, the first character of the
target string is ignored. For example, if the target string is I abc
( I represents a tab character), the A option looks for the string abc
on all line types. The A, F, and M options are always assumed.
C Distinguishes between uppercase and lowercase characters.
V 1100: On OS 1100 MAPPER Systems, this option applies only to full
character set (FCS) reports.

7-180 7831 9274-000

 LOC (Locate)

F Processes all line types and includes in the target the first character
of the t g t s t r subfield. The A, F, and M options are always
assumed.
M Uses the first character of the target string as a line type designator.
This option takes the place of a line type subfield (normally shown
as i t yp). For example, if the target string is I abc ( I represents a
tab character), the M option looks for the string abc on tab lines.
Use with the F option to find the string on all line types, even when
the string starts in column 1. The A, F, and M options are always
assumed.
0 Creates a result containing items that are found.
Note: With the 0 option, the variable v CO contains 0, the variable
vino contains the total number of lines that contain the target
string (not the line number where the target string was
located), and the variable vrpt contains the report number
where the target string was located.
OU Creates an update result; then you can perform one of the following
operations:
• Delete the found lines from the report with a Delete (DEL)
statement.
• Delete the found lines from the report and place them in a result
(-0) with an Extract (EXT) statement.
• Make changes to the update result and blend the updated lines
from the result back into the report with an Update (UPD)
statement.
You cannot execute the LOC statement with the OU option against a
result.
Sx Starts scan at line x, where x is a positive number.
Sx-y Starts scan at line x and stop at line y.

7831 9274-000 7-181

LOC (Locate)

Sx','n Starts scan at line x and scan n lines. The comma must be enclosed
in apostrophes ( ').
1100: On OS 1100 MAPPER Systems, you do not need enclose the
comma in apostrophes.
Tx Sets x to a transparent character to match any character in that
position. Do not use it in the first character position of the target
string. If you do not specify the T option, all blank characters are
transparent. For example, the character string "A D" with the T
option locates all A-space-space-D strings; without the T option,
"A D" locates all four-character strings with A in the first character
position and D in the fourth character position, such as ABCD,
A 2D, and A%CD.
Example
Locate the characters fed:
@loc,0,b,2„099 afm 2-79 fed <col>i3,<I ine>i 5 .

where:
099 Goes to label 99 if no target string is located
afm Uses the A, F, and M options
2-79 Starts scan in column 2 for 79 characters
fed Locates the target string fed
<col> Captures a number one less than the column number
where the target string was located in <col>
<I i ne> Captures the line number where the target string was
located in <line>

7-182 7831 9274-000

 LSM (Load System Message)

LSM (Load System Message)

The Load System Message (LSM) statement loads a variable with the
contents of a system message.
Format
@LSM,msgno[ ,I rib) vmsg .

Following is a description of the field and subfields:

Field Description

msgno Message number. If you are using this statement in an error subroutine, capture
the message number with the reserved word XERR$ (see RER in this section).

lab Label to go to if the message number does not exist.

vmsg Variable in which to place the message. Specify 80 characters for the variable size
so that the entire text of the system message fits in the variable.

Example
Load v2 with the message in message number vl:
tbldv,w v1i4=xerr$ Ism,v1 v2s80 .
or
@Ism,xerr$ <error>s80 .

7831 9274-000 7-183

LZR (Line Zero)

LZR (Line Zero)

The Line Zero (LZR) statement creates or loads variables with information
from line 0 of the designated report or result. The LZR statement does not
create a result. The previously existing -0 result remains after the LZR
statement executes.
Format
@LZR,c,d,rklab vllnes,vcpl,vhdgs,vcs,vupds,vdepf,vuser,vrpw,
vwpw,v1gn] .

Following is a description of the subfields:

Field Description

c,d,r Report from which to obtain information.

lab Label to go to if the report number or drawer does not exist. Use this subfield
alone to find out whether the report or drawer exists. (To simplify your run
logic, if you want the run to continue on the next line, use LIN1 in this subfield
instead of a label number.)

vlines Variable to capture the number of lines.

vcpl Variable to capture the number of characters per line.

vhdgs Variable to capture the number of heading lines. For a result, this always
equals 1.

V 1100: vcs Variable to capture the number of the set typ.... 0 = LCS, I = FCS,
and 2 = FCSU.

V 1100: vupds Variable to capture th= n.,,,d-snr of updates to the report it wa-

vdept Variable to capture the department number if the report has a department-
private read password.

vuser Variable to capture the user-id if the report has a user-private read password.

continued

7-184 7831 9274-000

 LZR (Line Zero)

continued

Field Description

vrpw Variable to capture the read password, or the word LOCKED if the report has
a read password.

vwpw Variable to capture the write password, or the word LOCKED if the report has
a write password.

vIgn Variable to capture the number of the language with which this drawer was
created.
V 1100: On OS 1100 MAPPER Systems, the vIgn subfield does not apply.

Reserved Words
STAT1$, STAT2$, and STAT3$ contain the following information under
these circumstances:
If the report exists:
STAT1$ Date of the last update in DATE1$ format YYMMDD
STAT2$ Creation date of the report in DATE1$ format YYMMDD
STAT3$ Save flag date, if one exists. If the save flag contains an
invalid date, STAT3$ = 0.
If the report has never been updated:
STAT1$ 0
If the report does not exist:
STAT1$ Highest report number in the drawer
STAT2$ (Disregard)
If the drawer does not exist:
STAT1$ 0
STAT2$ (Disregard)

7831 9274-000 7-185

LZR (Line Zero)

Comments
• The v r pw and vwpw variables contain the word LOCKED if the report
has a read or write password. The word LOCKED is also indicated if
the user is not signed on in department 2 (the MAPPER system
coordination department).
V 1100: On OS 1100 MAPPER Systems, the word LOCKED is also
indicated if the user is not signed on with the key user sign-on accessible
to coordinators, which is not necessarily in department 2.
• If the report or drawer does not exist, the run continues at the label or, if
you did not specify a label, the run continues at the next statement.
• If you specify a renamed result that is not previously renamed with a
Rename (RNM) statement, the run errs; it does not go to the specified
label.
V 1100: Under the same circumstances on the OS 1100 MAPPER System,
the run continues at the specified label.
Example
Capture the number of lines in report 2B0, in <lines> (if that report or
drawer does not exist, the run goes to label 99):
@lzr,0,b,2,099 <I ines>i5 .

7-186 7831 9274-000

 MCH (Match)

MCH (Match)
The Match (MCH) statement matches fields in two reports, then moves data
from the issuing report to the receiving report, creating a result.
To create an update result that allows you to blend the changed lines back
into the original report or delete lines from the original report, use the
Match Update (MAU) statement. The MAU statement uses the same fields
and subfields as the MCH statement. See the online help system
(HELP,@MAU) for more information.
Format
@MCH,lc,iddr,rc,rd,rr[dab] o !cc iltypdp rcc rltyp,rp

Following is a description of the fields and subfields:

Field Description

ic,id,ir Issuing report.

rc,rd,rr Receiving report.

lab Label to go to if the issuing or receiving report is not sorted (valid only with
the P option).

o Options field (see Options).

icc Column-character positions or names of the fields in the issuing report.

iltyp Line type in the issuing report to match against. (If you specify the A option,
you can leave this subfield blank, but enter the comma.)

ip Parameters in the issuing report.

ICC Column-character positions or names of the fields in the receiving report.

rltyp Line type in the receiving report to match against. (If you specify the A
option, you can leave this subfield blank, but enter the comma.)

rp Parameters in the receiving report.

7831 9274-000 7-187

MCH (Match)

Options
A Matches all line types.
B Blends issuing and receiving report lines in a result. Data must be
presorted. Do not use this option with the M or N options. This
option does not apply to the MAU statement.
C(S) Distinguishes between uppercase and lowercase letters.
V 1100: On OS 1100 MAPPER Systems, this option applies only to full
character set (FCS) reports.
D Deletes match information lines from the result. The D option is
always assumed.
E Does not move blank fields from the issuing report. For matched
items appearing in multiple lines of the issuing report, if the last
item of the group is blank, the function does not move the data.
F Does not fill move fields in a no-match condition. This option does
not apply to the MAU statement.
M Includes in the result only lines containing fields that match
between the compared reports. Do not use this option with the B
option. The M option is always assumed with the MAU statement.
N Includes in the result only lines containing fields that do not match
between the compared reports. Do not use this option with the
B option.
P Specifies that issuing and receiving reports are presorted by fields to
be matched. Do not use this option with the Q option.
V 1100: See also Appendix D for information about which character set
to specify when presorting.

7-188 7831 9274-000

 MCH (Match)

Q Specifies quick execution of match data by assuming the data is

presorted. When you specify the Q option, you guarantee that the
reports are sorted, so the system does not check for unsorted fields.
Do not use this option with the P option.
1100: See also Appendix D for information about which character set
to specify when presorting.
S Includes in the result only lines containing fields that match,
appearing in the same order as the issuing report.
Reserved Words
STAT1$ contains the number of lines in the receiving report that are
matched or not matched, depending on options selected.
STAT2$ contains the total number of lines in the receiving report against
which a match was attempted.
Comments
• If the match fields are not presorted, the system performs an internal
sort on both reports. After processing, the receiving report is restored to
its original order. (The maximum number of characters sorted
internally is 64.) Use the P or Q option whenever possible.
• The MAPPER system places an update lock on the reports so that other
users cannot update the reports while your run is matching data in
them.

7831 9274-000 7-189

MCH (Match)

Example 1: Finding Lines That Do Not Match

Compare the same field name in reports 2B0 and 2CO3 and find lines that
exist in the receiving report but not in the issuing report:
ttrnch,O,b,2,0,c,2 n 'product' ❑ ,1 'product' ❑ ,1

Or

thch,O,b,2,0,c,2 n 15-9 ❑ ,1 2-9 ❑ ,1 .

where:
0,b,2 Compares lines in reports 2B0 and 2C0
0,c,2

n Uses the N option to include only lines that do not match

'product' Matches the Product Type field (column 15 for nine
15-9 characters) in report 2B0
1
'product' to the Product Type field (column 2 for nine
2-9 characters) in report 2C0
1
❑ Processes tab lines in both reports

7-190 7831 9274-000

 MCH (Match)

Example 2: Moving Columns in Lines That Match

Compare fields in reports 1C0 and 2B0, and move columns in lines that
match:
tihich,O,c,1,0,b,2 m 2-9, 'spacereq(0-3)' 0 ,1,a 1
15-9,77-3 0 , 1,a .
where:
0, c , 1 Compares lines in reports 1C0 and 2B0
0 ,b ,2
m Uses the M option to include only matched lines
in the result
2-9 Matches column 2 for nine characters in the
1 issuing report
15-9 to column 15 for nine characters in the
1 receiving report.
' spacer eq (0-3) ' Moves the last three columns of the
a Space Req field from report 1C0
77-3 to the Spc Cod field (column 77 for three
a characters) in report 2B0
0 Processes tab lines in both reports

7831 9274-000 7-191

MSG (Message to Control)

MSG (Message to Control)

V This section does not apply to the Personal Computer MAPPER System.
The Message to Console (MSG) statement sends a message to the system
console.
Format
@MSG vid [vrsp] .
Following is a description of the field:

Field Description

vld Variables, literal data, reserved words, or any combination of these (up to 48
characters), to make up the message. If you use spaces, enclose the
message in apostrophes.

V 1100: vrsp Variable to capture the operator response (up to 60 characters). If you use
this field, the run waits for a response before continuing.

The system console displays the message preceded by the following signal:
MAPPER*nnn*

where nnn is the run user's station number.

' 1100: On OS 1100 MAPPER Systems, the system console displays the
message preceded by the following identifier:
MAPPER*4101: MESSAGE FROM user-id AT MAPPER STATION nnn:
where user-id and nnn are the run user's user-id and station number,
respectively.
The message itself appears on the next line of the console preceded by the
characters MAPPER*4101+ .

7-192 7831 9274-000

 MSG (Message to Control)

Examples

The following statement is an example of a message:

@nsg 'Please reload rpt 2B0 from 891103 tape.' .
V 1100: The following example applies only to OS 1100 MAPPER Systems:
This statement asks the operator whether to continue, and loads <response>
with the response:
@msg 'Should my run cont i nue?' <response>h3 .
@i f <response> = no g 1 o end ; .

7831 9274-000 7-193

NET (Network Sign On)

NET (Network Sign On)

vz This section does not apply to the BTOS II MAPPER System.
The Network Sign On (NET) statement signs on to the remote MAPPER
system, from the calling (local) MAPPER system.
Use the Network Remote (NRM) statement following the NET statement to
use distributed MAPPER applications.
With the NRM statement, since the terminal remains under local control,
the screen and keyboard retain the look and feel of the local site regardless
of the kind of system to which the user is connected. This allows you to
design distributed applications that let users process data on different
systems transparently.
Format
@NET,net - Irl[,site-id,rmu,rmd,rmpw,trnrpt,mtr,lab]

Following is a description of the subfields:

Field Description

net-id Network identifier of the host system.

site-id Site identifier of the remote MAPPER system. Default = first site configured
for the specified network identifier.

rmu User-id registered on the remote MAPPER system. Default = user-id of the
user executing the run.

rmd User department number for the remote MAPPER sign-on. Default =
department number of the user executing the run.

rmpw User-id password for the remote MAPPER sign-on. Default = password of
the user executing the run.

trnrpt Report that contains a translation table used to translate characters between
the local and remote MAPPER sites. The translation reports must be in
drawer F of the user's language cabinet. Default = no translation used.

mtr Monitor transferred data, Y or N. Default = N.

lab Label to go to if the connection fails.

7-194 7831 9274-000

 NET (Network Sign On)

Comments
V • U Series, UNIX, and PC MAPPER: The user must be registered to
execute the INTER_RUN run on the remote MAPPER system. Contact
the coordinator to verify access to the INTER_RUN run.
V • 1100: The user must be registered to execute the INTER-RUN run on
OS 1100 MAPPER Systems.
V • A Series: The user must have a usercode on the remote system and
must be registered to execute the INTER_RUN run on the remote
MAPPER system. Contact the coordinator to verify usercodes and
access to the INTER_RUN run.
• You must specify either the network identifier or the site identifier. If
you do not specify the site identifier, MAPPER software defaults to the
first site configured for the specified network identifier.
If you specify only the site identifier, MAPPER software reads the
network configuration report for the correct network identifier. Contact
your MAPPER system coordinator for the network and site identifiers
configured on your system.
Example
Sign on to remote host SYS15, site identity z, with sign-on
newuser,7,newuser and monitor the sign-on to the remote site:
@net,SYS15,z,newuser,7,newuser „y .

7831 9274-000 7-195

NOF (Network Off)

NOF (Network Off)

`Q This section does not apply to the BTOS II MAPPER System.
The Network Off (NOF) statement signs the local MAPPER system caller off
the remote MAPPER system after executing other network statements, such
as Network Read (NRD) and Network Write (NWR). The NOF statement
closes the communications connection with the remote system.
Format
eiNOF .

7-196 7831 9274-000

 NRD (Network Read)

NRD (Network Read)

v This section does not apply to the BTOS II MAPPER System.
The Network Read (NRD) statement enables the user to read and return
data from a remote MAPPER system to the local MAPPER system. Before
using the NRD statement, you must first sign on to the remote system by
using the Network Sign On (NET) statement.
Format
vmsg] .

Following is a description of the field and subfields:

Field Description

ic,id,ir Issuing report on the remote MAPPER system (if you specify a result, you
must also specify the cabinet and drawer, for example, 0,b,-2).

rc,rd,rr Receiving report on the local MAPPER system. If you leave the rr subfield
blank or enter 0, the issuing report is returned as a result (-0).

lab Label to go to if an error occurs on the remote system.

vmsg Variable to contain an 80-character system message if control goes to the

label.

Example
Read report 2B0, on the remote MAPPER system and place the data into
report 5B0, on the local MAPPER system (go to label 99 in case of an error):
• nrd,O,b,2,0,b,5,099 <error>s80 .
• dsp,-0 .

. Other processing

@1099:ouv,1,1 <error> wat 50000 .

7831 9274-000 7-197

NRM (Network Remote)

NRM (Network Remote)

p This section doe. apply to LI LG dTOS II MAPPER System.
The Network Remote (NRM) statement executes runs and manual functions
that reside on a remote MAPPER system. Before using the NRM statement,
you must first sign on to the remote system by using the Network Sign On
(NET) statement.
Format
(NRM "cmd" .
Following is a description of the field:

Field Description

"cmd" Run name or manual function call to execute at the remote site, including
input parameters to be sent to the run or manual function. Enclose the
request in quotation marks ( " ).

Comments
• With the NRM statement, since the terminal remains under local
control, the screen and keyboard retain the look and feel of the local site
regardless of the kind of system to which the user is connected. This
allows you to design distributed applications that let users process data
on different systems transparently.
• To return to the local site, the run user can type two release characters
(^^) and press Transmit.
If the NRM statement started a run, you can have the remote run
execute a Network Return (NRT) statement to return to the local site.

7-198 7831 9274-000

 NRM (Network Remote)

• The run containing the NRM statement remains active while the
statement executes at the remote site.
• To maintain the transparency of a run executing at a remote site, be
sure to include error and abort routines in the remote run. See RAR and
RER in this section for information on abort and error routines.
The routine should return the run user to the local site via an NRT
statement in case of an error.
Example
Sign on to remote host SYS15, MAPPER site k, then use the NRM
statement to execute a run named abc:
@net ,SYS15, k, newuser ,7, newuser .
@nrm "abc" .

7831 9274-000 7-199

NRN (Network Run)

NRN (Network Run)

This section does not apply to the BTOS II MAPPER System.
The Network Run (NRN) statement allows a local MAPPER system user to
pass run statements to a remote MAPPER system to be executed. Before
using the NRN statement, you must first sign on to the remote system by
using the Network Sign On (NET) statement.
Format
@NRN[,lab] " ►un statements" [vmsg] .

Following is a description of the fields and subfield:

Field Description

lab Label to go to if an error occurs on the remote system.

"run statements" MAPPER run statements to be executed on the remote MAPPER

system. Remember to include the at sign (@) as the first character.
Enclose the run statements in quotation marks. You can pass up to 256
characters in the run statements.

vmsg Variable to contain an 80-character system message if control goes to

the label.

Comments
• To process the results generated from an NRN statement, rename the
results.
• Using the NRN statement to execute statements that load variables
may cause conflicts with the INTER_RUN run that processes NRN
requests. Do not use variables v1 through v15 in the NRN statement
because they are reserved for the INTER_RUN run.
V' 1100: On OS 1100 MAPPER Systems, the name of the run is
INTER-RUN.
V • 1100: Passing a run statement that terminates control of a run causes
the INTER-RUN run to end. Examples of this category of run
statements are RUN and GTO RPX.

7-200 7831 9274-000

 NRN (Network Run)

Example

Perform a Totalize (TOT) statement in the remote MAPPER system and

renames the result -2 for further processing:
@nr n,099 "tbtot ,O,c , 1 " 18-6,25-7,65-8 ,+,-,=
rnm -2" <error>s80 .

You can then use a Network Read (NRD) statement to read the result into a
report on the local MAPPER system.
See NWR in this section for more examples.

7831 9274-000 7-201

NRT (Network Return)

NRT (Network Return)

'This section does not apply to the BTOS II MAPPER System.
The Network Return (NRT) statement returns control to the local site that
executed the run with a Network Remote (NRM) statement. Before using
the NRT statement, you must use the NRM statement to start a run or
manual function at the remote site.
Use the NRT statement in an error routine of a remote run to maintain the
transparency of executing a run at a remote site. The NRT statement
returns the run user to the local site in case of an error.
Format
(NRT 1"cmd " 1 .

Following is a description of the field:

Field Description

"cmd" Run name or manual function call to execute at the local site, including input
parameters to be sent to the run or manual function. Enclose the request in
quotation marks ( " ). If no "cmd" is specified, the run returns control to the
local site and continues at the statement following the NRM statement.

Example
A run named abc has been executed from another site. The last line of run
abc includes an NRT statement to return control to the local site. Once
control is returned to the local site the run that executed abc via an NRM
statement continues executing at the next line:
@n r t .

7-202 7831 9274-000

 NWR (Network Write)

NWR (Network Write)

This section does not apply to the BTOS II MAPPER System.
The Network Write (NWR) statement enables a user to send a report or
result from a local MAPPER system to a remote MAPPER system. Before
using the NWR statement, you must first sign on to the remote system by
using the Network Sign On (NET) statement.
Format
@NWR,1c,ld,lr,rc,rd,rrklab vmsg] .

Following is a description of the field and subfields:

Field Description

ic,id,ir Issuing report on the local MAPPER system.

rc,rd,rr Receiving report on the remote MAPPER system.

lab Label to go to if an error occurs.

vmsg Variable to contain an 80-character system message if control goes to the

label.

Receiving Report Entries

Enter the following information in the receiving report ( r r) subfield:

Entry Description

0 Duplicates the report within the drawer. STAT2$ contains the report
number of the new report.

Receiving Replaces the issuing report into the receiving report.

report number
(positive)

-1 through -8 Creates a renamed result, which you can use with the Network Run
(NRN) statement.

7831 9274-000 7-203

NWR (Network Write)

Examples
Write report 2B0, to report 3B0, on the remote MAPPER system (if an error
occurs, go to label 99):
@nwr,O,b,2,0,b,3,099 <error>s80 .
Send report 1CO, to the remote MAPPER system and rename it -1 in
cabinet 0, drawer C. Use the NRN statement to execute a Match (MCH)
statement between the renamed result and report 1DO, and rename the
result -2. Send the -2 result back to the local MAPPER system via the
Network Read (NRD) statement and display the result:
@nwr,0,c,1,0,c,-1,099 v1s80 .
@Mrn,099 "@mch,O,d,1,-1 " 12-9,31-8 ,1,a
2-9,33-8 ,1,a rnm -2" v2s80 .
@nrd,0,c,-2,0,c„099 v3s80 .
@Wsp,-0 .

7-204 7831 9274-000

 OK (Acknowledge Message)

OK (Acknowledge Message)
The Acknowledge Message (OK) statement acknowledges any outstanding
message queued to your station.
Format
@Olq,lab,vrsp] .

Following is a description of the subfields:

Field Description

lab Label to go to if no message is queued to your station.

vrsp Variable to send as a response message.

Examples
Acknowledge an outstanding message and continue the run at the next
statement (if there are no queued messages, go to label 3):
titok , 003 .

7831 9274-000 7-205

OK (Acknowledge Message)

1100: The following example does not apply to OS 1100 MAPPER Systems.
As an example of how you might use an OK statement in a run, suppose
your terminal beeps, notifying you of a message. You start a run that saves
the message in a report.
First the run executes a Wait (WAT) statement with the M option to
suspend the run while the system passes information to it that a message is
waiting. If you started this run without a message waiting, the run waits for
1000 milliseconds, expecting the message, but then continues at the next
line; otherwise, the run continues at the label, where it acknowledges the
message and saves it in a report. Then the run displays information about
the saved message. Here is the run:
@65:wat,m,60 1000
@brk .
No message was received.
@gto end .
@60:ok dup,-0 idv,pw v1i4=cab$,v2a1=adrw$,v3i4=rpt$ .
@brk .
The message is in report v3v2v1.
@brk out,-0,2,5,1,1,y .
V 1100: The following example applies only to OS 1100 MAPPER Systems.
As an example of how you might use an OK statement in a run, suppose
your terminal beeps and you press Message to acknowledge the message.
You start a run that duplicates the message into a report and captures the
report number, drawer, and cabinet number where the system has added
the new report. The run then acknowledges the message (OK) and displays
the information. Here is the run:
@dup,-0 idv,pw v1i4=cab$,v2a1=adrw$,v3i4=rpt$ .
@ok brk .
The message is in report v3v2v1.
@brk out,-0,2,5,1,1,y .

7-206 7831 9274-000

 0S2 (Operating System Interface)

0S2 (Operating System Interface)

This section applies only to the Personal Computer MAPPER System.
The Operating System Interface (0S2) statement interfaces with the
operating system and allows the execution of native PC operating system
commands.
Condition
This statement should be used only by experienced MS-OS/2TM users.
Format
@C62[,c,d„,lab] o '[cmd]' .
Following are descriptions of the fields and subfields:

Field Description

c,d Drawer into which the result is to be returned.

lab Label to go to if the command fails.

0 Options field (see Options). Enter options in lowercase characters. If you do not
specify options, you must designate the options field with two apostrophes (' ').

cmd Command to be performed. Standard path searching is done to find the

command. Enclose commands containing embedded spaces in apostrophes ( ').
If you do not specify a command, designate its position with two
apostrophes (' ).

MS-OS/2 is a trademark of Microsoft Corporation.

7831 9274-000 7-207

0S2 (Operating System Interface)

Options
-b Executes the command in the background and is minimized as an
icon on the screen.
-f Causes the output of the command to be returned as a result in
drawer A. If you enter a file name immediately following the
-f option, the statement places a copy of the output from the
command into that file. (You cannot use this option with the
-w option.)
-w When the command is finished executing, the MAPPER system
pauses until you enter the exit command in the active window to
return to the active screen. (You cannot use this option with the
-f option.)
Comments
• If you use the -b option but do not specify a command, the operating
system command interpreter (CMD.EXE) session is displayed as an
icon. You must open the icon, execute any commands, and exit back to
your MAPPER session. Your MAPPER session shows a WAIT message
until you exit from the CMD.EXE session.
• If you use a reverse slant ( \ ) to define a directory path in an 0S2
statement, it must be enclosed in apostrophes. This prevents the
directory path from being misinterpreted as a MAPPER run statement
that continues on the next line.
Example 1: Accessing the Operating System
This statement accesses the native OS/2 operating system (you must enter
the apostrophes to preserve the positions of options and commands):
@os2 " " .
Example 2: Listing the Contents of a Directory
This statement lists the contents of the \mapper directory on drive C: and
places the output in a cabinet 0, drawer B result:
tbos2,0,b -f 'di r c:Irnapper ' .

7-208 7831 9274-000

 OUM (Output Mask)

OUM (Output Mask)

The Output Mask (OUM) statement displays a blank function mask on the
basis of the headings defined for the specified cabinet and drawer. In the
mask, the run user can enter options and parameters, which your run can
capture.
Format
CPRAdedd[dr,11,re,rd,rr,rl,title]

Following is a description of the subfields:

Field Description

k,id,ir Report that contains the headings to be used in the mask (single mask) or of
the issuing report (double mask). Default = report 0.

if Format in which to display the mask (single mask) or of the issuing report
(double mask). Default = basic format.

rc,rd,rr Receiving report (double mask). Default = report 0.

rf Format of the receiving report mask (double mask). Default = basic format.

title Title (up to 12 characters) to be displayed above the mask.

Reserved Word
INMSV$ captures user input from the function mask screen. Use these
guidelines:
- Use INMSV$ only with an OUM statement.
- Place INMSV$ before the variable names in the Change Variable (CHG)
statement.
- Place the CHG statement before the OUM statement.
Use string (type S) variables. You can use alphanumeric (type A) or
Hollerith (type H) if the data fits in them.

7831 9274-000 7-209

OUM (Output Mask)

Comments
• Use the blank function mask to load run parameter data into a variable.
For a single mask, an OUM statement returns the option line and up to
four decoded parameter lines. For a double mask, it returns the option
line and up to two decoded parameter lines.
• The first variable initialized by INMSV$ contains the entire option line.
In a single mask, you can capture up to four parameter lines. In a
double mask, you can capture the two parameter lines allowed (one each
for the issuing and receiving masks). Each parameter line requires
three variables.
The first variable contains the starting column numbers of the fields
where the run user entered parameters. Each starting column
designation in the variable is three characters long, right-justified,
and filled with zeros. The three-character designations for all
starting columns are packed to the left in the variable. For example,
parameter entries starting in columns 2 and 45 in the mask yield a
variable containing 002045.
Whenever you use a format other than basic, the column numbers
are those defined in report 0 for the format. For example, if format 1
displays a field that actually starts in column 126, the variable
contains 126 for the starting column number, not the column
number where the field was displayed on the screen.
Use a 120-character variable to hold the maximum 40 fields
possible. The system fills unused character positions with blanks.
The second variable contains the corresponding field sizes, three
characters each, packed to the left in the variable.
The third variable contains the entire parameter line expanded
according to the format of the mask.
The run stalls until the user presses Transmit, then it continues with the
data in the specified variables.
Note: To use field names in your run rather than column positions, use the
first and second parameter line variables with the Load Field Name
(LFN) statement.

7-210 7831 9274-000

 OUM (Output Mask)

• The screen display contains a function key bar. You can customize the
function key bar so that you can include operations not available with
the standard function key bar. See FKY in this section.
' 1100: On OS 1100 MAPPER Systems, the function key bar may or may
not be available at your site.
Example 1: Using a Single Mask
Display a single function mask:
@chg inmsv$ v1s80,v2s120,v3s120,v4s132,v5s120,1
v6s120,v7s132 .
Citum,0,d,1,1 „„„ 'TEST' .
where:
@chg inmsv$ Loads INMSV$ with variables
v 1 s80 Loads vl with the option line
v2s 120 Loads v2 with the first parameter line field starting
columns
v3s 120 Loads v3 with the first parameter line field sizes
v4s 132 Loads v4 with the first parameter line
v5s 120 Loads v5 with the second parameter line field
starting columns
v6s 120 Loads v6 with the second parameter line field sizes
v7s 132 Loads v7 with the second parameter line
oum,O,d,1 ,1 Displays a blank function mask derived from
report 1DO, format 1, to receive user input
' TEST' Displays the title TEST above the mask

7831 9274-000 7-211

OUM (Output Mask)

Example 2: Extracting Parameters

Capture the parameters entered from a function mask displayed by an OUM
statement:
1. @ Idv v10i3=1 .
2. @ def,c v1113,v2 .
3. Q001:1dv v12i3=v2(v10-3) .
4. @ Idv v13i3=v3(v10-3) .
5.@ Idv v14s18=v4(v12-v13)

. Save variables here so loop

. can capture more information.

6. @ INC,3 V10 .
7. @ IF V10 < V11 GTO 001 .
Here is a description of each line:
1. Initialize the column-character position.
2. Determine the number of fields selected based on the number of
characters in v2.
3. Obtain the starting column number.
4. Obtain the field size.
5. Obtain the field from the parameter line.
6. Increase the column-character position by 3.
7. Loop back if there are more columns.
You now have all the options, column-character positions, and parameter
entries in variables. Use these variables in statements such as Sort (SOR),
Search (SRH), and Totalize (TOT), depending on the kinds of parameters
the run user enters in the mask. An SOR statement does not get far, for
example, if your variables contain search parameters.

7-212 7831 9274-000

 OUM (Output Mask)

Example 3: Using a Double Mask

Display a double function mask:
@chg inmsv$ v1s80,v2s120,v3s120,v4s132,v5s120,1
v6s 120, v7s 132 .
@oum,0,b „ 1 0, c
where:
v 1s80 Loads vl with the option line
v2s 120 Loads v2 with the issuing mask parameter line field
starting columns
v3s 120 Loads v3 with the issuing mask parameter line field
sizes
v4s 132 Loads v4 with the issuing mask parameter line
v5s 120 Loads v5 with the receiving mask parameter line
field starting columns
v6s 120 Loads v6 with the receiving mask parameter line
field sizes
v7s 132 Loads v7 with the receiving mask parameter line
oum,0,b„ ,0, c Displays a double function mask derived from
reports OBO and OCO, basic format (using default
report 0 and basic format for both reports)

7831 9274-000 7-213

OUT (Output)

OUT (Output)
The Output (OUT) statement clears the output area, clears any defined
function key bar, and displays lines from a report or result on the screen.
You can use it to display an entire screen or overlay an existing screen.
You may also use the Screen Control (SC) run statement to display data on
the screen. The SC statement provides many features not available with the
OUT statement. See SC in this section.
Format
@DUT,c,d,r,1 ,q[,out I ,tabp,erase?,interlm?,pdq,protect ,Ixmt?,
outsp1,61 I nk1,sn,lab] .

Following is a description of the subfields:

Field Description

c,d,r Report from which to display data.

I Line number in the report or result from which the output is to start.

q Number of lines to display.

outl Line on the screen where the output is to start. Default = top line of the
screen.

tabp Tab character after which to position the cursor. A positive number is the
number of tab positions to advance (maximum is 100) and a negative number
is the number of positions to move back (maximum is 100) from the home
position. Default = home position.

erase? Erase the screen from the outl, Y or N. Default = Y.

interim? Interim display (the run continues without the user resuming), Y or N.
Default = N.

pdq Number of lines to push down on the screen (push down quantity).

protect Protected format option (see "Options for Protect Subfield" in this
subsection).

continued

7-214 7831 9274-000

 OUT (Output)

continued

Field Description

fxmt? Force transmit (the run continues and you can load variables with ICVAR$,
1NPUT$,INSTR$, INVAR$, or INVR1$), Y or N. Default = N.

outsp Determines how data is sent to the screen. A, B, or space. Default = space.

A Sends data, including all spaces.

B Sends data, but not spaces. (If data exists on a line, only the
columns containing new data are overwritten. The old and new
data is blended together on the same line.)

space Sends the data, including spaces, if fewer than six consecutive
spaces appear between the characters. If six or more spaces
appear between the characters, the data is sent, but not the
spaces. This allows the screen to be painted faster.

blink? Change the less than (<) sign to a left blink character and the greater than (>)
sign to a right blink character before displaying data, Y or N. Default = N.
Hardware capabilities of supported terminals may not allow blinking.
V BTOS and PC MAPPER: Blinking display is not supported. This subfield
is not used.

V 1100: sn Station number where output is to be displayed. If you omit this field or
specify 0 (zero), output is displayed at the station executing the run.

V 1100: lab Label to go to if the output to another station cannot be completed

successfully. If you omit this field and the run cannot be successfully
completed, it is terminated with an error. See "Reserved Word" for the
STAT1$ error codes.

7831 9274-000 7-215

OUT (0 utp ut)

Options for Protect Subfield

E Erases only unprotected fields. Use this option to clear
input fields in a display.
V 1100: F Allows full-screen Input. Use only with IBM® Series 3270
terminals.
Edits input characters in unprotected fields by character
type. Use one of the following edit codes in the first
character position of the unprotected field in the output
area. The numeric codes allow users to see the data as they
type it in; the letter codes make the entered data
transparent (it does not appear on the screen):
0/A or
Space Any data, no editing
1/B Alphabetic data, no editing
2/C Numeric data, left-justified
3/D No data
4/E Any data, right-justified
5/F Alphabetic data, right-justified
6/G Numeric data, right-justified
Numeric data includes plus and minus signs and the period.
The presence of the I option assumes output protect
features. See the P option.
P Protects fields (for use when displaying data). Enter one of
the following codes in column 1 of the output lines or
immediately after the comma that ends an unprotected field:
0 or
Space Normal intensity
1 No intensity

IBM is a registered trademark of International Business Machines Corporation.

7-216 7831 9274-000

 OUT (Output)

2 Low intensity
3 Blinking characters, alternating low and
normal intensities
If protected and unprotected fields appear on the same line,
start the unprotected field with a tab character and end it
with a comma. To use different intensities on the same line,
place an unprotected field between the protected fields.
V BTOS: Hardware display intensity is not supported. For
four-to-one output, leave line 3 blank. For five-to-one
output, leave line 4 blank. The P option for the protect
subfield is not used
4 Fields are defined on four lines for one output line (see
"Four- and Five-to-One Output" in this section):
• Line 1 contains M control characters.
• Line 2 contains N control characters.
• Line 3 contains emphasis characters.
• Line 4 contains the data to display.
(See your display terminal documentation for more
information on controlling emphasis.)
5 Fields are defined on five lines for one output line (see
"Four- and Five-to-One Output" in this section):
• Line 1 contains M control characters.
• Line 2 contains N control characters.
• Line 3 is the color line, with one of the codes listed in
Table 7-10.
• Line 4 contains emphasis characters.
• Line 5 is the data to display.

7831 9274-000 7-217

OUT (Output)

Reserved Word
V 1100: If you use the i a b subfield and the OUT statement cannot be
completed, the run goes to the label. Examine STAT1$ for the status code:
1 Station does not exist or it is a batch port, remote run, or
background station.
2 Station is not available because it is not currently connected to the
MAPPER system.
3 No one is signed on at the specified station and interim? was not
specified.
4 User at the specified station did not respond to the message wait
signal within one minute.
5 User answered the signal and received the screen, but did another
operation rather than supply input.
Comments
• An OUT statement places lines from a report or result on the screen,
then clears the output area.
• The OUT statement stalls the run until the user presses Transmit,
unless you specify a Y in the interim? or txmi t? subfields.
• In an OUT statement, you can specify:
- Where to display the data
V 1100: (includes displaying data on a different terminal)
- Where to position the cursor
- Which fields to protect
• You cannot use an OUT statement in a run started in background (BR
statement) or from a remote site (RRN statement).
V 1100: On OS 1100 MAPPER Systems, you can use an OUT statement in
background runs if you send the output to another terminal using the
sn subfield.

7-218 7831 9274-000

 OUT (Output)

• When the output is displayed, you can load input variables using
INPUT$, INSTR$, ICVAR$, INVAR$, and INVR1$. See "Capturing
Input" in Section 4 for more details about these reserved words. To
resume the run after the output is displayed, press Transmit. You can
also press Resume to resume the run, but the data entered on the
screen is not captured.
• Put reserved words before the variable name in the Change
Variable (CHG) statement, and be sure the CHG statement precedes the
OUT statement (INSTR$, INVAR$, INVR1$).
• Initialize variables with INPUT$ following the OUT statement.
• Do not put other run statements on the same line after an OUT
statement. The logic scan of the line terminates after executing the
OUT statement.
• The I/O and LLP counts are reset following a noninterim OUT
statement.
Examples
Display five lines of the current result, starting at line 2, on the first line of
the screen:
@out,-0,2,5,1 .

7831 9274-000 7-219

OUT (Output)

The following statement uses several options:

@out,-0,4,1,1„n,y,2

where:
-0 Displays lines from the current (-0) result
4 Starts at report line 4
1 Displays one line
1 Starts the display on the first line of the screen
n Does not erase the screen
Y Specifies interim display (the run continues even if the user
does not respond)
2 Pushes currently displayed data down two lines before
displaying this line

Displaying Information At Another Terminal

V This section on displaying information at another terminal applies only to the
OS 1100 MAPPER System.
Use the s n and la b subfields to display information and obtain input from
terminals other than the one executing the run. You can use background,
batch port, and remote runs to solicit and obtain input just like normal runs,
but you must send the output to a real terminal.
You cannot obtain exclusive use of any station. When more than one run is
sending output to the same station, the output may be intermixed and not
displayed in the same order as they were sent.

7-220 7831 9274-000

 OUT (Output)

If the User Is At the Terminal

Sending information to a terminal where a user is signed on activates a
message wait signal on that terminal and stalls your run. If the user
responds to the signal, the information is displayed on the user's screen.
If you specify N or blank in the interim? subfield, your run stalls until the
user at the terminal presses any key. If you specify Y in the interim?
subfield, your run continues automatically.
If the user at the other terminal does not respond to the signal within one
minute, your run either continues at the specified label or terminates with
an error (STAT1$ = 4). If the user does respond to the signal, but enters a
new command or function rather than supplying input, your run continues
at the specified label or terminates with an error (STAT1$ = 5).

If the User Is Not at the Terminal

If no user is signed on at the specified station, you must specify a Yin the
interim? subfield. In this case, the message wait signal is not activated,
the output information is displayed on the screen, and your run continues.
This is particularly useful if you want to use a terminal as a system monitor,
with a scheduled background run periodically updating the display. If you
do not specify an interim display, your run continues at the specified label or
terminates with an error (STAT1$ = 3).

Four- and Five-to-One Output

If your display terminal lets you control emphasis for special editing and
presentation techniques, you can use either the four- or the five-to-one
output. Four-to-one is for monochrome displays and five-to-one is for color.
MAPPER software ignores the color feature on a monochrome terminal.
Four-to-one output consists of three edit code lines and one data line for
each output line. Five-to-one output contains four edit code lines and a data
line for each output line.

7831 9274-000 7-221

OUT (Output)

Each line in a four-to-one or five-to-one output contains an edit code

character. These characters are:
Four-to-One Five-to-One
M character M character
N character N character
Emphasis character Color character
Emphasis character
The following tables describe all possible combinations of the M and N
characters for the four- and five-to-one displays. The first table shows the
characteristics for the expanded edit code characters. The second illustrates
the characteristics of the conventional edit code characters.
You cannot combine an M code from the expanded edit code character set
with an N code from the conventional edit code character set, or vice versa.
The characteristics for the expanded M include the following:

Y (Yes) Entry N (No) Entry

On Video Off Video

Normal Intensity Low Intensity
Tab Stop No Tab Stop
Emphasis Protected Emphasis Not Protected

Table 7-8 lists characteristics for the expanded M.

7-222 7831 9274-000

 OUT (Output)

Table 7-8. Characteristics for the Expanded M

M Code Protected Emphasis Tab Stop Field Changed* Low Intensity Video On

B N Y Y N Y
A N Y Y N N
B N Y Y Y Y
C N Y Y Y N
D N Y N N Y
E N Y N N N
F N Y N Y Y
G N Y N Y N
H N N Y N Y
I N N Y N N
J N N Y Y Y
K N N Y Y N
L N N N N Y
H N N N N N
N N N N Y Y
0 N N N Y N
Y Y Y N Y
a Y Y Y N N
b Y Y Y Y Y
c Y Y Y Y N
d Y Y N N Y
e Y Y N N N
f Y Y N Y Y
g Y Y N Y N
h Y N Y N Y
i Y N Y N N
j Y N Y Y Y
k Y N Y Y N
I Y N N N Y
m Y N N N N
n Y N N Y Y
o Y N N Y N

Y = Yes, N = No.

V 11013: * FIELD CHANGED used only for IBM 3270 terminals.

The characteristics for the expanded N include the following:

7831 9274-000 7-223

OUT (Output)

The characteristics for the expanded N include the following:

Y (Yes) Entry N (No) Entry

Not Alpha Only Alpha Only

Not Numeric Only Numeric Only
Normal Field Right-Justified Field
No Blink Blinking
Normal Video Reverse Video

Table 7-9 lists characteristics for the expanded N.

7-224 7831 9274-000

 OUT (Output)

Table 7-9. Characteristics for the Expanded N

N Code Reverse Video Blink Right-Justify Number Only Alpha Only

9 N N N N N
A N N N N Y
B N N N Y N
C N N P P P
D N N Y N N
E N N Y N Y
F N N Y Y N
G N N P P P
H N Y N N N
I N Y N N Y
J N Y N Y N
K N Y N Y Y
L N Y Y N N
M N Y Y N Y
N N Y Y Y N
0 N Y P P P
P Y N N N N
Q Y N N N Y
R Y N N Y N
S Y N N P P
I Y N Y N N
U Y N Y N Y
V Y N Y Y N
W Y N P P P
X Y Y N N N
Y Y Y N N Y
Z Y Y N Y N
E Y Y P P P
\ Y Y Y N N
] Y Y Y N Y
Y Y Y Y N
- Y Y P P P

Y = Yes, N = No, P = Protected input field; no input allowed.

7831 9274-000 7-225

OUT (Output)

Some of the intensity settings may not be valid because of limitations in the
terminal hardware.
V U Series: The following is a description of the attributes of each terminal:
• SVT-1210 Reverse video, no distinction between normal and low
intensity
• SVT-1220 Normal intensity definition appears as high
and intensity
UVT-1224 Normal/high intensity
Reverse video
Blinking characters
• PC Refer to your PCU emulation documentation for PC
capabilities

Color Characters
The third line in a five-to-one output contains the color code. Find the
appropriate code in Table 7-10. Color codes sent to a monochrome terminal
are ignored by MAPPER software.
Note: Note that if you select the same color for background color and
character color, the result is "invisible" characters.
V BTOS: Seven colors, plus black, are supported in the text mode. The only
available background color is black. If you select black as the character
color, the selected background color is used instead against a black
background. If you select the same color for characters and background,
green characters on a black background are used instead.

7-226 7831 9274-000

 OUT (Output)

Table 7-10. Five-to-One Color Codes

BACKGROUND

B R G Y B M C W
l e r l l g y h
k d n w u t n t

Black @HPX h p x
C
H Red A I Q Y a i q y
A
R Green B J R Z b j r z
A
C Yellow C K S [ c k s C
T
E Blue D L I \ d l t 1
R
Magenta E M U ] e m u )

Cyan F N V f n v —

White G 0 W _ g o w ?

Emphasis Characters
Emphasis characters consist of the column separator, the underscore, and
the strike-through.
Because of hardware limitations of the supported terminals, MAPPER
software ignores all emphasis characters. The emphasis characters are
described here because the code character line is required for four-to-one or
five-to-one displays.
V 1100: On OS 1100 MAPPER Systems, emphasis characters are sent to the
terminal, but hardware capabilities vary among terminal types. See your
display terminal documentation for more information on controlling
emphasis.
Table 7-11 lists the applicable codes for emphasis characters.

7831 9274-000 7-227

OUT (Output)

Table 7.11. Emphasis Characters

Code Strike Through Underscore Column Separator

space
Yes
Yes
Yes Yes
-Yes
Yes Yes
Yes Yes
Yes Yes Yes

For example, if you want your input fields to be displayed with underscores,
select a $ from the table above. If you wish to create a vertical line, select a
series of ! characters.
Now that you have had a brief look at edit codes and emphasis characters,
you are ready to see how MAPPER software defines screens that use them.

Four-to-One Screens
These screens make full use of edit codes and emphasis characters. They
allow you to specify the following:
• An M code
• An N code
• An emphasis character
• A displayable character
All can be specified for the same screen position.
You must place each of the codes and characters in the same column of four
successive lines of source code. The M code must be on the first line, the N
on the second, the emphasis character on the third, and the displayable
character on the fourth.

7-228 7831 9274-000

 OUT (Output)

Examples

For example, suppose you want the name of a field to be low intensity,
reverse video, with protected fields. First, you would select an N from the M
table, an S from the N table, and code the four lines as follows:
N (M byte)
S (N byte)
(Emphasis character)
State: (Displayable character)

If you would like the input field to contain a tab stop, have normal intensity,
be left-justified, and allow alpha characters only, select a lowercase d from
the M table and an uppercase A from the N table:
N d (M byte)
S A (N byte)
(Emphasis character)
State: (Displayable character)

When MAPPER software receives a four-to-one screen, it scans the source

lines four at a time, vertically combines the four codes or characters of each
column, and generates one line of output. The output line contains the edit
codes, emphasis characters, and displayable characters ready for
transmission to the terminal.
The following is an expanded edit code sequence:
D L L (M byte)
A B C (N byte)

Changing an unprotected field causes initialization of a new variable even

though no tab character was specified.
Note: When redefining the editing code, even though no tab character was
specified, the contents are placed into the next variable.
If you intend to display a four-to-one screen, enter a 4 as the protected
format option on the OUT statement as follows:
v
@brk out,-0,2,16,1,1,,,,,4 -

7831 9274-000 7-229

OUT (Output)

Now you are ready to code a simple data entry screen. Suppose you need to
enter the name, street, city, state, zip, and phone of a new customer. The
state field should allow only alphabetic input. The input fields should be
normal intensity, have tab stops, and be filled with underscores. The field
labels should be low intensity and protected.
This example illustrates the four-to-one coding for a data entry screen.
1. abrk .
2. N
3. S
4. $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
5. Name:
6.
7.
8. $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
9. Street:
10.
11.
12. $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
13. City:
14. dN d N d Nd Nd N
15. AS BS B SB SB S
16. $$ $$$$$ $$$ $$$ $$$$
17. State: Zip: Phone:( )
18. @brk .

When the OUT statement executes, source lines 2 through 5 combine to

form the first output line. Lines 6 through 9 combine to form the second
output line, and so on. The following data entry screen is displayed:

Name:
Street:
State: Zip: Phone ( ) -
City:

The underscored areas are unprotected and of normal intensity. Because

the underscores are protected emphasis characters, they are continuous and
are not overwritten by input from the keyboard. The field labels are
protected and of low intensity. The State field allows only alphabetic input.
The Zip and Phone fields allow only numeric input.

7-230 7831 9274-000

 OUV (Out Variable)

OUV (Out Variable)

The Out Variable (OUV) statement displays literal data and the contents of
variables, constants, or reserved words on the screen.
Format
WOV[,scl,co ► ] vld .

Following is a description of the field and subfields:

Field Description

sc/ Line number of the screen at which to begin the display. Default = current screen
line.

col Column position at which to begin the display. Default = current column position.

(Row 1 [sc/ = 1], column 1 [col = 1] is home position.)

vld Data to display. The data can be a variable, constant, literal, reserved word, or any
combination.

Comments
• Enclose literal data containing spaces in apostrophes.
• It is more efficient to use the OUV statement followed by a Wait (WAT)
or Input Variable (ITV) statement than it is to use the Break-Output
(BRK-OUT) sequence.
• Use the OUV statement while debugging your run to display the
contents of variables while the run is executing.
• If an ITV statement immediately follows the OUV statement, the ITV
statement stalls the run until input is entered.
Example
Display the contents of <output> on line 23 starting in column 10:
titouv,23,10 <output>

7831 9274-000 7-231

PRT (Print)

PRT (Print)
The Print (PRT) statement prints reports and results on the system printer.
The PRT statement does not create a result.
Format
tiVRT,c,dkr,dinos?,f,prtsite,cys,a111,1sp,dstn„hdgs?' .

tIPRT,c,dkr,dinos?,1,prtsite,cys,a1 1?,Isp,bonner,formsld,hdgsn .

Following is a description of the subfields:

Field Description

c,d,r Report to print.

dlnos? Delete line numbers, Y or N. Default = Y.

f Report format to be printed. Default = basic format.

V 1100: On OS 1100 MAPPER Systems, default = basic format or, if a report
was on display, the fields currently displayed by means of the VIEW function
nr thrica coital-4nd by an FMT nr SFC n in et.t.rn.nt

prtsite MAPPER site at which to print the report (valid entries are A-Z).
Default = local site.
V 1100: On OS 1100 MAPPER Systems, device name or number of any printer
available to the system. Default = first available printer in the printer group
configured as the default.

cys Number of copies to print (maximum of 64). Default =1.

V 1100: On OS 1100 MAPPER Systems, the maximum is 63 copies

all? Print all the reports of the specified drawer, Y or N. Default = N. Leave the
report field blank if you use this subfield.

Isp Line spacing, 1, 2, or 3. Default = 1.

continued

7-232 7831 9274-000

 PRT (Print)

continued

Field Description

dstn Destination printer model. The model defines how the report is to be printed.
You can set up special forms with different models. See the MAPPER system
coordinator for available models. You can select a specific printer in this
subfield, or you can let the MAPPER system select the default printer.
V 1100: This subfield is not available on OS 1100 MAPPER Systems.
V BTOS: Uses a complete, valid BTOS printer name (for example, [LPT]) or
spool name for the dstn field. Consult the MAPPER system coordinator for
configured devices and spoolers.

V 1100: banner Print banner name. Embedded tab codes or spaces are not permitted when
using this subfield.

V 1100: formsid Indicates the predefined or special forms identification. See also the
PRINTFORM run (enter printform,help).

hdgs? Print report headings? Choose one of the following:

Y Print headings on first page only (default).

N Do not print headings.
A Print headings on every page.
V 1100: When printing on special forms paper, the banner page, report
headers, and end-of-report line are not printed. To override, enter *A.

Example
Print report 2B0:
@pr t ,O,b,2„ „2
where:
0,b ,2 Prints report 2B0
I7 Prints all columns without line numbers in basic format
2 Prints two copies

7831 9274-000 7-233

 RAR (Register Abort Routine)

RAR (Register Abort Routine)

The Register Abort Routine (RAR) statement registers or names a routine to
be executed if the user aborts a run by pressing Abort.
Since all variables, temporary results, and the current output area remain
unaltered and are accessible to the abort routine, the routine can capture
information currently being processed even though the user aborted the run.
Format
giAllf,c,d,r lab I lab} .

Following is a description of the field and subfields:

Field Description

c,d,t Report containing an external routine.

V 1100: The report containing the external routine must be in the same character
set type as the calling run control report.

lab Label in the report where an abort routine begins. To begin the routine at the first
line of the external run control report, use LIN1 in this field.

Reserved Words
The following reserved words contain zero until a run aborts. The system
resets them to zero whenever the run executes a noninterim display with a
Display Graphics (DSG), Display Message (DSM), Display Report (DSP),
Output (OUT), or Screen Control (SC) statement.
AXDRW$ contains the drawer letter of the run control report where the run
aborted.
XDRW$ contains the drawer of the run control report where the run
aborted.
XFUN$ contains the name of the last statement (the statement call)
executed before the run aborted.
)(LINES contains the line number in the run control report where the run
aborted.
XRPT$ contains the report number of the run control report where the run
aborted.

7831 9274-000 7-235

RAR (Register Abort Routine)

Comments
• If a run user aborts a run and the run has an abort routine registered,
the system runs the abort routine and cancels any previously registered
abort and error routines and update locks.
• Place the RAR statement as close as possible to the beginning of the run.
If the user aborts the run before the run executes an RAR statement, the
run has no abort routine to go to.
• The system cancels the abort routine when the run terminates, but you
can also use the Clear Abort Routine (CAR) statement to cancel the
routine.
• The abort routine cannot contain the statements GTO RPX, RAR, RER,
or RUN. You can use an RSR statement only if it starts an internal
subroutine.
• If a user presses Abort while an abort routine is executing, the run
aborts.
• I/O and LLP limits and cabinet restrictions from the aborted run also
apply to the abort routine.
• A noninterim display specified by any of the following statements in
your abort routine continues normal run processing when a user tries to
abort a run:
DSG, DSM, DSP, OUT, SC
This feature prevents users from terminating a run prematurely.
• The values of reserved words 10$ and LLP$ reflect the number of I/Os
and LLPs used in the abort routine and the run.
V 1100: On OS 1100 MAPPER Systems, 10$ and LLP$ reserved words in
an abort routine reflect the I/Os and LLPs in the abort routine itself.

7-236 7831 9274-000

 RAR (Register Abort Routine)

• Abort routines registered in called routines (via the CALL statement)

override previously registered abort routines; however, when control
returns to the calling run, the system automatically reregisters the
original abort routine.
V 1100: On OS 1100 MAPPER Systems, the system does not
automatically reregister the original abort routine; you must reregister
it yourself.
• If you do not register an abort routine in the called routine and a user
aborts the run, control goes to the abort routine in the calling run.
V 1100: On OS 1100 MAPPER Systems, control does not go to any abort
routines previously registered in the calling run.
Example
This statement registers the external abort routine at label 5 in report 4E0:
@rar,0,e,4 005 .

7831 9274-000 7-237

RDB (Run Debug)

RDB (Run Debug)

7 This section does not apply to the OS 1100 MAPPER System. See "RDB (Run
Debug): OS 1100" in this section for a description of the RDB statement as it
applies to the OS 1100 MAPPER System.
The Run Debug (RDB) statement helps you locate and correct any errors in
a run while it is executing. Use the RDB statement in a run instead of the
manual function request to start the debugging at a specific point in a run.
This is especially useful for debugging large or complex runs.
With the Run Debug (RDB) utility, you can step through your run to do the
following:
• Display the contents of a variable or reserved word.
• Change the value of a variable.
• Display a line or range of lines in the run control report.
• Pause at a specified variable, run statement, or label.
• Make corrections to the run control report.
Condition
You must be the one who last updated the run control report; otherwise the
system ignores the RDB request.
The run must not be registered in the Global Run Registration report if you
want to execute RDB manually. (However, you can use the RDB statement
in the run.)
Format
@MB .
Manual Function Request
RDB run[,v,...v]
where run is the name of the run to debug and v , . . . v is data supplied to
the run to be initialized via INPUT$.

7-238 7831 9274-000

 RDB (Run Debug)

RDB Commands and Function Keys

Use RDB commands and function keys Fl, F2, and F4 to view different
kinds of information in your run. Table 7-12 describes the RDB commands
and function keys.

Table 7-12. RDB Commands and Function Keys

Command/Function Key Description

B[Uabl@rfclv] Stops the run at the point (breakpoint) specified in the

parameter. You can have 13 breakpoints active at one time. If
you do not specify any parameters, the B command stops on
the lines examined using the E command (maximum of 10 lines
set for breakpoint).

Uab Letter L followed by the label number after which to

interrupt the run (maximum of one label set for
breakpoint).

@rfc Run function call after which to interrupt the run

(maximum of one run function call set for
breakpoint).

✓ Variable name after which to interrupt the run

(maximum of one variable set for breakpoint).

Cv vld Changes the value of v to the variable, constant, reserved

word, literal data, or expression contained in vkl. Use the
same kind of expressions you use with the Change Variable
(CHG) statement.

D Deletes all breakpoints.

E n Examines line n of the run control report.

continued

7831 9274-000 7-239

RDB (Run Debug)

Table 7-12. RDB Commands and Function Keys (cont.)

Command/Function Key Description

Fl Steps through the run by executing a line at a time, including

any continuation line.

F2 Steps through the run by executing one statement at a time

(use when multiple statements occur on one line).

F4 Continues the run normally until one of these occurs:

- The run encounters a breakpoint or an RDB statement

- The run completes
- The run aborts

My Monitors the contents of variable v whenever the value

changes.

P[reswd] Displays the contents of the specified reserved word. (You

can also use this command to display the contents of named
variables, as with the V command.)

reswd Reserved word.

Hyphens (-) on either side of the displayed contents denote

the boundaries of the variable so that you can see significant
characters and the justification of the contents within the
variable (for example, - 0-).

If you do not specify a parameter, the function displays the

contents of all initialized variables on the next statement to
execute.

R Continues the run (same as F4).

S[nmbr-of-Ins] Sets streaming mode, which means that the run executes one
logic line (or one statement if you had been pressing F2) at a
time in a scrolling, uninterrupted manner. To stop streaming
mode, press Abort.

nmbr-of-Ins Number of lines used, as a window at the

bottom of your screen, for scrolling your run
as it executes. The upper portion of the
screen remains stationary.

7-240 7831 9274-000

 RDB (Run Debug)

Table 7-12. RDB Commands and Function Keys (cont.)

Command/Function Key Description

U Displays the run control report for updating (the run control
report becomes the current -0).

Vn Displays the contents of the numbered variable n or the

named variable nmvar (include < and > in nmvar). Hyphens (-)
on either side of the displayed contents denote the
boundaries of the variable so that you can see significant
characters and the justification of the contents within the
variable (for example - 0-).

To display the contents of named variables, you can use the

P command or type the named variable.

Inc,d,r,11,-n,1] Displays a window (10 lines) of a report or result beginning at

a specified line.

c,d,r Report to display. Default = run control report.

/ First line to display. Default = line 1.

-n Result to display.

erfc Executes any run statement you specify (instead of executing

statements in the run control report). For example,
@Idv v099=123 . loads v099 with 123. Processing continues
on the next line.

rfc Run function call.

A Exits RDB mode. If in streaming mode, press Abort first, then
type A and transmit.

7831 9274-000 7-241

RDB (Run Debug)

Comments
• When you start the RDB utility, it displays line 3 of your run control
report and the RDB prompt. Your run is now under control of the RDB
utility.
• When the run encounters an error, it stops and displays a system
message but leaves you in RDB mode. All variables and results are
available for you to examine.
• When the run encounters a statement that displays output, such as an
Output (OUT) or Display Report (DSP) statement, the RDB utility
repaints the previous output screen and displays the current statement.
• When the run encounters a Run Start (RUN) statement, the RDB utility
terminates. To continue the RDB utility, the run started via the RUN
statement must contain an RDB statement.

7-242 7831 9274-000

 RDB (Run Debug)

Examples
After requesting a display of the contents of v3 (space, space, 1, 5):
8 @lzr,O,v2,1 v3i4 .
9 @lok,O,v2,1 .
MEI* v3
- 15-

After requesting a display of the contents of <drawer> (B):

8 @Izr,O,<drawer>,1 v3i4 .
MEI* <drawer>
-B-

After requesting the contents of v2 be changed to d:

8 @lzr,O,v2,1 v3i4 .
MEI* c v2 d

Examine line 42 of your run control report:

8 @Izr,O,v2,1 v3i4 .
FIDE* e 42

Line 42 is displayed. Transmit again to display line 43. Press Fl or F2 to

continue the run at the statement displayed before you used the E
command.
Display a window of your run control report (four lines preceding and five
lines following the current line):
MEI* w

Display a 10-line window starting at line 1 of the -0 result:

MI* w,-0

7831 9274-000 7-243

RDB (Run Debug): OS 1100

RDB (Run Debug): OS 1100

'This section applies only to the OS 1100 MAPPER System. See "RDB (Run
Debug)" in this section for a description of the RDB statement as it applies to
other MAPPER systems.
The Run Debug (RDB) statement helps you locate and correct any errors in
a run while it is executing. Use the RDB statement in a run instead of the
manual function request to start the debugging at a specific point in a run.
This is especially useful for debugging large or complex runs.
With the Run Debug (RDB) utility, you can step through your run to do the
following:
• Display the contents of a variable or reserved word; display renamed
reports and results.
• Pause at a specified variable, run statement, line, or label.
• Make corrections to the run control report.
• Dynamically execute run statements, for example, to change the
contents of a variable.
Condition
You must be registered as a run designer and you must be the one who last
updated the run control report; otherwise the system ignores the RDB
request.
Format
RDB .
Manual Function Request
RDB run[,v,...v]
where run is the name of the run to debug and v , . . . v is data supplied to
the run to be initialized via INPUT$.

7-244 7831 9274-000

 RDB (Run Debug): OS 1100

RDB Commands and Function Keys

Use RDB commands and function keys Fl through F4 to view different
kinds of information in your run. Table 7-13 describes the RDB commands
and function keys.

Table 7-13. RDB Commands and Function Keys: OS 1100

Command/Function Key Description

B prm Stops the run at the point (breakpoint) specified in prm. Only
one breakpoint can be active at a time, and the previous
breakpoint is cleared when you set a new one. Enter one of
the following commands or B to clear the breakpoint:

B n Line number at which to interrupt the run. The

run stops before executing line n.

B Llab Letter L followed by the label number at which

to interrupt the run. The run stops before
executing the line at label lab.

B v Variable at which to interrupt the run. The run

stops after executing any statement that refers
to variable v (variable name or number).

B @rfc Run function call at which to interrupt the run.

The run stops before executing run function
call rfc.

Fl Steps through the run by executing a line at a time, including

any continuation line.

F2 Steps through the run by executing one statement at a time

(use when multiple statements occur on one line). Note that
the utility considers the period-space terminator a run
statement.

Returns the run to normal execution speed. To stop the run,

press F3 a second time.

Sets streaming mode, which means that the run executes one
logic line (or statement, if you had been pressing F2) at a time
in a scrolling, uninterrupted manner. To stop the run, press
F4 a second time.

continued

831 9274-000 7-245

RDB (Run Debug): OS 1100

Table 7-13. RDB Commands and Function Keys: OS 1100 (cont.)

Command/Function Key Description

PA {vl$) Monitors a variable or reserved word by displaying its

contents whenever the run stops (between line steps or
statement steps).

Only one item can be monitored at a time, and the previous

monitor is cleared when you set a new one. Enter one of the
following commands or PA to clear the monitor:

Mv Variable to monitor. The size, type, and

contents of variable v (variable name or
number) are displayed whenever the run stops.

reswd$ Name of the reserved word to monitor (for

example, USER$ or LLP$). The contents of
reswd$ are displayed whenever the run stops.

-n Displays renamed report or result n.

R Displays your run control report.

You can manipulate this report or result on the screen (for

example, roll or shift it) and you can update it with a line
change or SOE update. However, you cannot use manual
functions such as Search (S) or Locate (LOC). Press
Resume to return to the run.

reswd$ Displays the name of the reserved word you specify (for
example, USER$ or LLP$), followed by its contents enclosed
in slant characters.

v Displays the variable size and type of variable v, followed by its

contents enclosed in slant ( / ) characters. You can enter a
variable name or number, for example, <data> or v3. You do
not need to enter the less than and greater than (< and >)
symbols to display a named variable.

7-246 7831 9274-000

 RDB (Run Debug): OS 1100

Table 7-13. RDB Commands and Function Keys: OS 1100 (cont.)

Command/Function Key Description

@rfc Dynamically inserts a temporary run statement to execute.

Processing continues uninterrupted on the current line.

@rfc Run function call followed by the remaining fields

needed in the statement. For example,
@iclv v099=123. loads v099 with 123.

? Displays a summary of RDB commands. Press Resume to

return to the run.
A
Exits RDB mode, terminates the run, and releases the screen.

Comments
• When you start the RDB utility, it displays the RDB prompt followed by
a line containing the name and location of the run. Below this
information, line 3 of your run control report appears (up to 70
characters of the line on an 80-character screen; up to 122 characters on
a 132-character screen).
Note: If you request the RDB utility using the RDB run statement, the
utility displays the first statement following the RDB statement.
Your run is now under control of the RDB utility. The next statement to
execute is displayed at the lowest displayed line on your screen.
• When the run encounters an error, press Resume to activate RDB error
mode. In error mode, you can examine all variables, reserved words,
and renamed reports and results as they existed when the run erred.
While in error mode, only the RDB commands that display information
(-n, R, Vv, reswd$) are allowed. See Table 7-13.
• When the run encounters a statement that displays output, such as an
Output (OUT) or Display Report (DSP) statement, the RDB utility
displays the screen as requested. When you resume the run, it clears
the screen and displays the RDB prompt.

7831 9274-000 7-247

RDB (Run Debug): OS 1100

• When the run encounters a Run Start (RUN) statement, if you were the
last person to update the newly started run, the RDB utility continues to
be active in that run.
• When the run executes a Defer Updates (DFU) statement, the RDB
utility skips to either the Commit Updates (CMU) or Decommit Updates
(DCU) statement, whichever comes first. The system executes any
intervening statements and displays them in streaming mode, that is, in
a scrolling, uninterrupted manner.
Examples
After requesting a display of the contents of v3 (RDB prompt line request
was RDB• v3 ):
RDB•
RUN=RUN IT REPORT=10F0

5 • @lzr,O,v2,1 v3i4 .
6 • @lok,O,v2,1 .
V314=/ 31/
After requesting a display of the contents of <drawer> (RDB prompt line
request was RDB• <drawer>):
RDB•
RUN=RUN IT REPORT=10F0

5 • (01 zr ,0,<drawer>, 1 v3i4 .

6 • @lok,0,<drawer>, 1 .
<DRAWER>H1=/b/
After requesting a run statement be dynamically inserted (RDB prompt line
request was RDB•@I dv v2=d ):
RDB•
RUN=RUN IT REPORT=10F0

5 • @lzr,O,v2,1 v3i4
INSERT-• @I dv v2=d
5 • @I zr ,O,v2,1 v3i4 .

7-248 7831 9274-000

 RDB (Run Debug): OS 1100

After requesting that v3 be monitored (RDB prompt line request was

RD134m v3):

RDB•
RUN=RUN I T REPORT=10F0 MON I TOR=V3

5 ♦ Calzr ,O,v2,1 v3i4 .

V3 - UNDEFINED
V314=/ 31/
6 ♦ COI ok,O,v2,1 .

7831 9274-000 7-249

RDC (Read Continuous)

RDC (Read Continuous)

The Read Continuous (RDC) statement reads report or result lines or line
segments.
Format
@RDC,c,d,r[,1,q,Itypdab] cc vdata

Following is a description of the fields and subfields:

Field Description

c,d,r Report from which lines are to be read.

I Line number at which to start reading. Default = line 1.

q Number of lines to read. Default = all lines.

Ityp Line type to process (leave this blank if all types are to be read).

lab Label to go to if no lines exist.

cc Column-character positions or names of the fields to be read.

vdata Variables (up to 40) to capture the data. To initialize a variable to the size of a
field, specify only the variable name and type (for example, v1h, v2s, and so
on).

Comments
• You must follow the RDC statement with an output line because an
RDC statement does the following in sequence:
Reads a line
Places the data read in variables
Writes the data to the output area
Reads the next line
• Use only one line in the output area for the variables to be written by
the RDC statement.
• The column-character fields do not have to be specified from
lower-numbered to higher-numbered columns.

7-250 7831 9274-000

 RDC (Read Continuous)

• An RDC statement generates one line in the output area for each line it
reads from the input report.
• You can define the size of a variable to load in an RDC statement or you
can define the variable to match the size of a corresponding report field.
This is especially useful with a named field, because the name does not
directly specify the field size; it also allows the RDC statement to adjust
to a change in the size of a field.
Example 1: Reading All Lines
Read all lines of the current result, capture the data in vl, and include the
variable in the output:
@r dc , -0 1-256 v1s256 .
v1
Example 2: Reading Data from Two Fields
Read data from two fields and capture the data in vl and v2:
@rdc,O,b,2 'custcode','shipdate' v1h,v2i
v1 v2
where:
0,b,2 Reads lines in report 2B0
'custcode' , Reads data from the Cust Code and Ship Date
'shipdate' fields
vlh Initializes vl as a type H variable to the size of the
Cust Code field to capture the data read from that
field
v2 i Initializes v2 as a type I variable to the size of the
Ship Date field to capture the data read from that
field

7831 9274-000 7-251

RDC (Read Continuous)

Example 3: Reading Data and Placing Under Headings

Read data from two fields, capture it in vl and v2, and place it in the output
area under the headings of SHIPPING ORDER and DATE LAST STATUS
CHANGE:
SHIPPING ORDER DATE LAST STATUS CHANGE

@rdc,0,b,2,6,50,U,099 'status','shiporder' v1i,v2h

v2 vl

where:
0, b , 2 Reads lines in report 2B0
6 Starts reading at line 6
50,0 Scans 50 lines, but reads tab lines only
099 Goes to label 99 if line 50 or the report does not exist
'status' Reads data from the Status Date field (column 5 for
six characters)
'shiporder' Reads data from the Ship Order field (column 71 for
five characters)
v1i Initializes vl as a type I variable to the size of the
Status Date field to capture the data read from the
field
v2h Initializes v2 as a type H variable to the size of the
Ship Order field to capture the data read from the
field
v2 v1 Places the data in the output area in this format
under the headings SHIPPING ORDER and DATE
LAST STATUS CHANGE

7-252 7831 9274-000

 RDC (Read Continuous)

Example 4: Reading Data and Reformatting

Read the drawer D heading lines from report ODO, read data from
report 2B0, and reformat it in the output area:
@brk,O,d .
@rdc,O,d,O,18,4 1-132 v1s132 .
v1
@rdc,O,b,2,6 1-80 v1s80 .
v1(1-3)v1(38-6) v1(14-11) v1(44-6)
ttbrk .

7831 9274-000 7-253

RDL (Read Line)

RDL (Read Line)

The Read Line (RDL) statement reads a report or result line or segments of
a line.
Format
CaRDL,c,d,r,1[,106] cc vdata .
Following is a description of the fields and subfields:

Field Description

c,d,r Report from which to read the line.

Line number to read.

lab Label to go to if the line or report does not exist.

CC Column-character positions or names of the fields to be read.

vdata Variables used to capture data (up to 40).

When you load variables of a specified size, the size of the variable
determines how many columns are read. For example, in the following
statement, v1 contains a value of the line starting in column 5 for 10 positions:

@rd1,0,b,2,v10,099 5-6 v1h10

To define a variable to the size of a field, specify only the variable name and
type (for example, v1 h, v2s, and so on).

Reserved Word
LINE$ contains the next line number to read. If the last line read was
beyond the end of the report, LINE$ contains a zero.

7-254 7831 9274-000

 RDL (Read Line)

Comments
• The column-character fields do not have to be specified from
lower-numbered to higher-numbered columns.
• If you need to read a series of lines in the same report, read the first line
using the RDL statement; read subsequent lines using the Read Line
Next (RLN) statement. See RLN in this section.
• You can define the size of a variable to load in an RDL statement or you
can define the variable to match the size of a corresponding report field.
This is especially useful with a named field, because the name does not
directly specify the field size; it also allows the RDL statement to adjust
to a change in the size of a field.
• See also RDC and RLN in this section.
Example 1: Reading Lines from a Field
Read lines from one field in report 2B0:
tbrd1,0,b,2,6 'custcode' vlh .

where:
0,b,2 Reads lines in report 2B0
6 Reads line 6
'custcode' Reads data from the Cust Code field
vlh Initializes vl as a type H variable to the size of the
Cust Code field to capture the data read from that
field

7831 9274-000 7-255

RDL (Read Line)

Example 2: Reading Data from Two Fields

Read lines from two fields in report 2B0:
@ird1,0,b,2,<Iine>,099 'status','shiporder' \
<status>i,<ord>h .
Or

@rdl,0,b,2,<Iine>,099 5-6,71-5 <status>i,<ord>h

where:
0,b,2 Reads a line in report 2B0
<I i ne> Reads the line number in <line>
099 Goes to label 99 if the line or the report does not
exist
' s tat us ' Reads data from the Status Date field (column 5
5-6 for six characters)
' sh i por der ' Reads data from the Ship Order field (column 71
71-5 for five characters)
<status>i Initializes <status> as a type I variable to the size of
the Status Date field to capture the data read from
the field
<or d>h Initializes <orb as a type H variable to the size of
the Ship Order field to capture the data read from
the field

7-256 7831 9274-000

 REH (Retrieve from History)

REH (Retrieve from History)

This section applies only to the OS 1100 MAPPER System.
The Retrieve from History (REH) statement retrieves the version of a
MAPPER report prior to the last system purge or merge process.
Format
@REH,c,d,rklabl .
Following is a description of the field and subfields:

Field Description

c,d,r Report to retrieve.

lab Label to go to if an error occurs.

Reserved Word
If the run continues at the label, STAT1$ contains an error code indicating
the reason (if any) why the data cannot be retrieved by the system. If you do
not use the 1 a b subfield and an error occurs, the run errs.
Error codes:
4 Drawer was added since last purge (prior version does not exist).
13 Prior version does not exist.
16 Internal software error.
17 Specified MAPPER file is being merged.
Example
Retrieve report 2A0, and go to label 99 in case of error:
@reh,O,a,2,099 .

7831 9274-000 7-257

RER (Register Error Routine)

RER (Register Error Routine)

The Register Error Routine (RER) statement registers a routine to be
executed if the run encounters an error.
Since all variables, temporary results, and the current output area remain
unaltered and are accessible to the error routine, use the routine to help
debug the run.
Format
@RER(,c,d,r lab I lab] .

Following is a description of the field and subfields:

Field Description

c,d,r Report containing the external routine.

7 1100: The report containing the external routine must be in the same cha—^,--
set type as the calling run control report.

lab Label in the report where the error routine begins. To begin the routine at the first
line of the external run control report, use LIN1 in this field.

Reserved Words
The following reserved words contain zero until a run errs. The system
resets them to zero whenever the run refers to CERR$ or executes a
noninterim display with a Display Graphics (DSG), Display Message (DSM),
Display Report (DSP), Output (OUT), or Screen Control (SC) statement.
V 1100: On OS 1100 MAPPER Systems, the system resets them to zero
whenever the run executes a noninterim display with the DSG, DSM, DSP,
OUT, or SC statements.
AXDRW$ contains the alphabetic drawer of the run control report where the
run erred.
XDRW$ contains the numeric drawer of the run control report where the
run erred.
)(ERRS contains the message number of the error — use this number to
retrieve the message with a Load System Message (LSM) statement.

7-258 7831 9274-000

 RER (Register Error Routine)

)(FUNS contains the failing statement call when the run erred.
)(LINES contains the line number in the report where the run erred.
XRPT$ contains the report number of the run control report where the run
erred.
Comments
• If an error occurs, the system runs the registered error routine and
cancels anypreviously registered abort and error routines and update
locks.
• Place the RER statement as close as possible to the beginning of the run.
If an error occurs before the run executes the RER statement, the run
has no error routine to go to.
• The system cancels the error routine when the run terminates, but you
can also use the Clear Error Routine (CER) statement to cancel the
routine.
• The error routine cannot contain the statements GTO RPX, RAR, RER,
or RUN. You can use an RSR statement only if it starts an internal
subroutine.
• If an error occurs while an error routine is executing, the run terminates
with a normal system message.
• I/O and LLP limits and cabinet restrictions from the run also apply to
the error routine.
• A noninterim display specified by any of the following statements in
your error routine continues normal run processing:
DSG, DSM, DSP, OUT, SC
• Any reference to the reserved word CERR$ sets CERR$ and )(ERRS to
zero and continues normal run processing.
V 1100: On OS 1100 MAPPER Systems, any reference to CERR$ reserved
word clears CERR$ and continues normal run processing.

7831 9274-000 7-259

RER (Register Error Routine)

• The values of reserved words 10$ and LLP$ reflect the number of 1/0s
and LLPs used in the error routine and the run.
V 1100: On OS 1100 MAPPER Systems, 10$ and LLP$ reserved words in
an error routine reflect the U0s and LLPs in the error routine itself.
• Error routines registered in called routines (via the CALL statement)
override previously registered error routines; however, when control
returns to the calling run, the system automatically reregisters the
original error routine.
V 1100: On OS 1100 MAPPER Systems, the system does not
automatically reregister the original error routine; you must reregister it
yourself.
• If you do not register an error routine in the called routine, in case of an
error, control goes to the error routine in the calling run.
V 1100: On OS 1100 MAPPER Systems, control does not go to any error
routines previously registered in the calling run.
V • 1100: Use the RUNERR error subroutine as a debugging tool during
development of your runs or as an error notification routine in
production runs. See the online help system (HELP,@RER) for more
information.
Example

This statement registers the external error routine at label 5 in report 2E0:
ther,0,e,2 005 .

7-260 7831 9274-000

 RET (Retrieve File)

RET (Retrieve File)

w This section does not apply to the OS 1100 MAPPER System. See "RET
(Retrieve File): OS 1100" in this section for a description of the RET
statement as it applies to the OS 1100 MAPPER System.
The Retrieve File (RET) statement retrieves a native data file as a result.
Format
@RET,c,c1[,mapperf?,hdgs?,1812] In .

Following is a description of the field and subfields:

Field Description

c,d Cabinet and drawer into which the report should be placed.

mapperf? File is in MAPPER format, Y or N. Default = N. If file is in binary format,

enter B.

hdgs? Add headings from the receiving drawer to the result, Y or N. Default = N.

lab Label to go to if the file is not found.

fn Name of the file to retrieve.

V U Series and UNIX: Include the full path name. File names can be
uppercase or lowercase but must exist exactly as typed. For example, Abc
must be accessed with an uppercase A and lowercase b and c.

V' A Series: Include a usercode and pack family (optional). File names must
be uppercase.

V BTOS: Use the full path name: [volume]<directory>filename. File names are
not case sensitive.

V PC MAPPER: Include the complete path name. The directory you specify
for the file must exist.

If you use a reverse slant ( \ ) to define a directory path in an RET statement, it

must be enclosed in apostrophes. This prevents the directory path from
being misinterpreted as a MAPPER run statement that continues on the next
line.

7831 9274-000 7-261

RET (Retrieve File)

Comments
• If the line length of the drawer into which you are retrieving a
MAPPER-formatted file is less than that of the file, any extra characters
in the file are truncated. If the file is not in MAPPER format, extra
characters are wrapped to the next line.
• If you created a file with headings and retrieved it with headings, the
result contains two sets of headings. Conversely, if you create a file with
no headings and retrieved it with no headings, the result contains no
headings, only the date line.
• When you retrieve a file that is not in MAPPER format, the RET
statement always adds the date line to the result. A report created with
headings and not in MAPPER format always contains two date lines
when you retrieve the file.
Example
' PC MAPPER: The following example does not apply to the Personal
Computer MAPPER System.
Retrieve a file that is not in MAPPER format:
&et,O,b,n,n KW/PROD/STATUS .
The file WORK/PROD/STATUS is created as a result in cabinet 0, drawer B,
with no headings.
PC MAPPER: The following example applies only to the Personal
Computer MAPPER System.
This statement retrieves the status.new file in the \ work \ prod directory,
which is not in MAPPER format. The statement does not add headings to
the cabinet 0, drawer B result.
&et,O,b,n,n '\work\prod\status.new' .

7-262 7831 9274-000

 RET (Retrieve File): OS 1100

RET (Retrieve File): OS 1100

This section applies only to the OS 1100 MAPPER System. See "RET
(Retrieve File)" in this section for a description of the RET statement as it
applies to other MAPPER systems.
The Retrieve File (RET) statement retrieves OS 1100 program or data files.
The retrieved file becomes the -0 result.
Note: When bringing large volumes of data from the batch environment,
retrieve the data with a RET statement instead of sending it through
the batch port.
Condition
The file must be a sector-formatted file with no read or write keys.
Format
@RET,c,dklaid [qual],In[,cyc,e1t,ver,mapperl2,hdgs?,1,ststr,q]

Following are descriptions of the fields and subfields:

Field Description

c,d Cabinet and drawer into which the report should be placed.

lab Label to go to in case the file cannot be retrieved.

qua/ Qualifier.

fn Name of the file to retrieve.

cyc Relative or absolute file cycle number.

elt Element name. Leave this field blank for a data file.

ver Version.

mapped? File is in MAPPER format? Y or N. Default = N. (A Y here overrides a Y for

hdgs?).

hdgs? Add headings from the receiving drawer to the result, Y or N. Default = N.

Line number at which to start the retrieval.

ststr Character string to locate. The retrieval starts on the line that contains this
character string.

q Number of lines to retrieve.

7831 9274-000 7-263

RET (Retrieve File): OS 1100

Reserved Words
STAT1$ contains the following status codes if the statement is not able to
retrieve the file:
1 Insufficient data.
2 Improperly formatted name (such as an illegal character).
3 Facility reject.
4 File does not exist.
5 File rolled out.
6 File exclusively assigned to another run.
7 Facilities currently unavailable.
8 Private file, under different project-id.
9 File may not be read (write only or missing key).
10 File is not sector-formatted mass storage file.
11 File is not program file (if element specified).
12 Element requested does not exist.
13 Report requested did not exist yesterday.
14 File is MAPPER file: Use the manual Retrieve File (RET) function.
15 Specified MAPPER file is being merged.
16 Internal software error.
17 Cannot retrieve report while file is being merged.
18 Locate string is not found.
19 Program file must include element name.
20 File exists but is not readable.
Example
Retrieves the file myqual*myfile starting at line 100:
@ret,0,a,099 myqual,myfile 100 .
where:
0,a Places the result in cabinet 0, drawer A.
099 Goes to label 99 in case of error.
myqua I Retrieves a file with a qualifier of MYQUAL.
my f i I e Retrieves the file named MYFILE.
100 Starts retrieving at line 100.

7-264 7831 9274-000

 RFM (Reformat Report)

RFM (Reformat Report)

The Reformat Report (RFM) statement moves columns of data from a report
to a newly formatted report or result containing only heading lines. The
RFM statement creates a result containing the same line types and number
of lines as the issuing report.
Format
@RFM,ic,Iddr,rc,rd,rr o icc rcc ,rp

Following is a description of the fields and subfields:

Field Description

ic,id,ir Issuing report.

rc,rd,rr Receiving report.

o Options field. Designate no options (' '). No options are available.

icc Column-character positions or names of the fields of the data to be moved in

the issuing report.

ip Parameters of the issuing report data (A-M).

V 1100: On OS 1100 MAPPER Systems. you can use parameters A through Z.

rcc Column-character positions or names of the fields in the receiving report.

rp Parameters of the receiving report data (A-M).

V 1100: On OS 1100 MAPPER Systems, you can use parameters A through Z.

7831 9274-000 7-265

RFM (Reformat Report)

Comments
• The RFM statement moves the columns specified and the line type
designator from the issuing report to the receiving report. If the issuing
report contains any period type lines, the entire period type line is
moved to the receiving report.
• The RFM statement processes all line types.
• Note that you can also use a Read Continuous (RDC) statement to
reformat a report using the output area of the run (see RDC). Use the
Match (MCH) statement if you want to conditionally move and extract
data from two different reports or between a displayed result and a
specified report, where both contain matching data (see MCH).
Example
Move data from report 2B0 to report 2D0:
tbrfm,0,b,2,0,d,2 " 'product' ,a 'product' ,a .
Or

tbrfm,0,b,2,0,d,2 " 15-9 ,a 12-9 ,a .

where:
0,b,2 Moves data from report 2B0 to report 2D0
0,d,2
'product' Moves line type and data from the Product Type
15-9 field (column 15 for nine characters) in report 2B0
a
'product' to the Product Type field (column 12 for nine
12-9 characters) in report 2D0
a

7-266 7831 9274-000

 RLN (Read Line Next)

RLN (Read Line Next)

The Read Line Next (RLN) statement continues reading from the report or
current result from which a Read Line (RDL) or Find and Read Line (FDR)
statement was just executed.
Condition
An RLN statement must follow a successful FDR or RDL statement.
Format
@IILNI,I,lab] cc vdata .

Following is a description of the fields and subfields:

Field Description

Line number to read. Default = next line number.

lab Label to go to if the specified line does not exist.

CC Column-character positions or names of the fields to read. You do not have to

specify fields in order from left to right, but be sure to assign the variables that
capture the data in matching sequence.

vdata Variables (up to 40) to capture the data. To initialize a variable to the size of a field,
specify only the variable name and type (for example, v1h, v2s, and so on).

Reserved Word
LINE$ contains the next line number to read. If the line read is beyond the
end of the report, LINE$ contains a zero.

7831 9274-000 7-267

RLN (Read Line Next)

Comments
• Since the RLN statement continues processing a previously specified
report, the only statements allowed between RDL and RLN (or FDR and
RLN) statements are those that do not end the processing on the report,
such as IF, CHG, and LDV.
• When most other statements, such as those with a manual function
counterpart, begin processing, they signal to MAPPER software that the
run has finished processing the previous report. Some of these
statements include ART, DC, DEV, FND, LZR, MCH, SRH, SOR, TOT,
and WRL.
• When you load variables of a specified size, the size of each variable
determines the number of columns the statement reads.
For example, in the following statement <data> contains ten characters
of data starting with column 5, even though you specified 2 characters in
the cc field:
@r I n„099 5-2 <da ta>h10 .
• To have the run automatically initialize a variable to the size of a field,
specify only the variable name and type (for example, <datalh>,
<data2s>, and so on). The RLN statement initializes the variables the
appropriate size for the fields it reads.
Example 1: Reading Data from a Field
Read data from the Cust Code field and capture the data in vl:
@r In 'custcode' viii .
where:
'custcode' Reads data from the Cust Code field
v1h Initializes vl as a type H variable to the size of the
Cust Code field to capture the data read from that
field.

7-268 7831 9274-000

 RLN (Read Line Next)

Example 2: Reading Data from Two Fields

Read data from two fields in report 2B0:
*d1,0,b,2,<line>,099 'status','shiporder'
<status>i,<ord>h .

thin „099 'status','shiporder' <status>,<ord>

where:
0, b,2 Reads a line in report 2B0
< I i ne> Reads the line number in <line> (the following RLN
statement automatically reads the line in <line> + 1)
099 Goes to label 99 if the line or the report does not
exist
'status' Reads data from the Status Date field
'shiporder' Reads data from the Ship Order field
<status>i Initializes <status> as a type I variable to the size of
the Status Date field to capture the data read from
the field
<o r d>h Initializes <ord> as a type H variable to the size of
the Ship Order field to capture the data read from
the field

7831 9274-000 7-269

RPW (Read Password)

RPW (Read Password)

The Read Password (RPW) statement assigns up to two read passwords to a
run. Use the RPW statement to access reports with read passwords that
you plan to process in a run.
Format
@RIAN{,pwli,pwl,pw21„pw2} .
Following is a description of the subfields:

Field Description

pwl First read password.

pw2 Second read password.

Comments
• You can assign different passwords to access different reports many
times in the run. For example, this statement assigns two read
passwords to a run:
@rpw,xxx,yyy .
• This statement changes the second read password (from the previous
example) so the run can access a different report. The first read
password remains assigned:
@rpw„zzz .
Example 1: Using One Read Password
Use a read password of readme:
ek pw, r eadme .
thrh,O,b,2 " 'custcode' 0,amco .

7-270 7831 9274-000

 RPW (Read Password)

Example 2: Using Two Read Passwords

Use two read passwords (this is useful, for example, in a statement that
must access two reports):
@rpw,readme,readit .
n 'product' 0,1 .
Example 3: Capturing the Password with INPUT$
For greater security, solicit the password from a user and conceal it in the
run:
@chg input$ v1h6 .
@rpw,vl .

7831 9274-000 7-271

RS (Run Status)

RS (Run Status)
This section applies only to the OS 1100 MAPPER System.
The Run Status (RS) statement creates a -0 result listing the status of runs
being executed with your user-id.
Format
tIRS[,0,run,sn] .

Following is a description of the subfields:

Field Description

0 Options field (see Options).

run Run name (leave blank for the status of all runs).

sn Station number (for the status of only those runs at this station).

Options
Blank All active and suspended runs
A Active runs only
B Background runs only
S Suspended runs only
Examples
Obtaining the status of all runs:
s
Obtaining the status of the background run myrun:
@rs,b,myrun .
Obtaining the status of all runs at station 123:
@r s „ , 123

7-272 7831 9274-000

 RSI (Remote Symbiont Interface)

RSI (Remote Symbiont Interface)

'This section applies only to the OS 1100 MAPPER System.
The Remote Symbiont Interface (RSI) statement initiates an interactive
demand program through a MAPPER run.
When a MAPPER run calls the RSI function, the run terminates; then the
MAPPER system signs the user on to the operating system in demand
mode, and gives the user manual control of the display terminal.
Note: The RSI interface of the Exec is text oriented. Therefore, the
MAPPER system cannot determine whether the parameters in the RSI
statement are causing an error. For example, an invalid user-id,
password, or a nonexistent ADD file may cause an error.
Condition
If the MAPPER software user is not a valid RSI user (as defined in the user
registration report), no @ or @@ commands (except for @@TERM and @@X)
are allowed.
Format
@RSIE,site•Id,tmo] user,pw[,acct,qual,ln,cyc,eltofer,q] .

Following is a description of the subfields:

Field Description

site-id Site identifier (six characters) for this display terminal.

tmo Number of seconds to wait for demand input at the terminal. If left blank, no
timeouts occur. Pressing Abort before receiving manual control aborts the
RSI statement.

user Demand mode user-id.

pw Demand mode password that validates the user-id.

continued

7831 9274-000 7-273

RSI (Remote Symbiont Interface)

continued

Field Description

acct Account number. If specified, the MAPPER system submits an executive

control language (ECL) RUN statement in this format:

@RUN run-id,acct/,proj-id

run-id Active site-id.

acct Account number.
proj-id Qualifier (qua! from the RSI statement). If you did not specify
qua!, this field is left blank.

qua! File name qualifier.

fn File name. If specified, the MAPPER system submits an ECL ADD statement
after demand mode sign-on is complete.

If omitted from the RSI statement, the following file-related subfields are left
blank.

cyc File cycle number.

e!t Element name.

ver Element version name.

q Number of text lines to display before giving manual control to the user.
Default =1 (minimum). Maximum = one less than the vertical screen size of
the display terminal. If a demand program executes a control command that
the Communications Control Routine (CCR) for the MAPPER system
interprets before it solicits input from the terminal, it discards everything that
preceded the control command.

7-274 7831 9274-000

 RSR (Run Subroutine)

RSR (Run Subroutine)

The Run Subroutine (RSR) statement executes an external or internal
subroutine starting at a specified label.
Format
@RS131,c,d,r lab I lab} .

Following is a description of the field and subfields:

Field Description

c,d,r Report containing the external subroutine.

V 1100: The report containing the external routine must be in the same
character set type as the calling run control report.

lab Label where the subroutine starts. This field is required. To begin the routine
at the first line of the external run control report, use LIN1 in this field.

Reserved Words
Use the reserved words ACDRW$ and CRPT$ in an external subroutine to
determine the drawer and report number of the calling run control report.
Comments
• To save the contents of all currently defined variables and pass control to
a subroutine, use the Call Subroutine (CALL) statement. You can pass
variables to the subroutine, manipulate them, and pass them back to the
calling run without affecting any of the other currently defined
variables.
• You can refer to all variables and results in the calling run from
subroutines. When you return to the calling run, newly created
variables and results in the subroutines become available. However, if
in the subroutine you reinitialize variables or rename results from the
calling run, the subroutine overwrites them.
• You can nest subroutines in a run. Internal subroutines can call
subroutines that call other subroutines up to 10 levels. However, you
can call only one external subroutine.

7831 9274-000 7-275

RSR (Run Subroutine)

• Use an End Subroutine (ESR) statement to exit the subroutine and

return control to a specified line in the run control report relative to the
line containing the calling RSR statement.
• Use a Clear Subroutine (CSR) statement in an external subroutine to
execute another external subroutine. A CSR statement allows an
external subroutine to call another external subroutine but does not
allow a return to the original calling run control report with an ESR
statement.
• When registering your run, inform the MAPPER system coordinator of
any other run control reports containing external subroutines.
• Do not place other run statements on the same line after the RSR
statement. Other run statements following it on the same line are
ignored. Put the next run statement on a new line.
Example 1: Using an Internal Subroutine
Use an RSR statement to execute the subroutine at label 1 (when the
subroutine ends, it returns to the calling RSR+1 line, which is run
statement a):
• rsr 001 .
• . run statement a .
tb . run statement b .
tb . run statement c .
• gto end .
@001: subroutine run statement a .
• . subroutine run statement b
• . subroutine run statement c
@ es r .
Example 2: Using an External Subroutine
Use an RSR statement to execute an external subroutine in report 2E0,
starting at label 2:
@rsr ,0,e,2 002 .

7-276 7831 9274-000

 RSR (Run Subroutine)

Example 3: Nesting Subroutines

This example uses an RSR statement to execute the subroutine at label 2.
That subroutine uses another RSR statement to execute a subroutine at
label 3. When the second subroutine completes, it uses an ESR statement to
return to the second part of the first subroutine. When that completes, it
uses another ESR statement to return to the original run statement
(run statement a):
• rsr 002 .
@001: run statement a .
run statement b
tb run statement c
@ GTO END .
47002: first subroutine run statement a
tb . first subroutine run statement b .
• . first subroutine run statement c .
• RSR 3 .
• . second part of first subroutine d
tb . second part of first subroutine e
• . second part of first subroutine f
• ESR .
@003: second subroutine run statement a
• . second subroutine run statement b
tb . second subroutine run statement c
• ESR .

7831 9274-000 7-277

RUN (Run Start)

RUN (Run Start)

The Run Start (RUN) statement terminates the current run and starts
another run at the same MAPPER station.
Format
(RUN frunkvid]l"cmd") .

Following is a description of the field and subfield:

Field Description

run Name of the run to start.

vld Variables, literal data, reserved words, or any combination of these, to

transfer to the run. Use INPUT$ to initialize these variables.

"cmd" Run name or manual function call to execute, including input parameters to be
sent to the run or manual function. The quotation marks ( " ) are required.

V 1100: This field is not available in limited character set (LCS) run control
reports.

Comments
• The manual equivalent of the RUN statement is to start a run by
entering the name of the run.
• You can identify up to 40 variables to capture in the started run with
INPUT$ (see Table 4-1 for maximum variable sizes). If you plan to use
these variables as parameters in report processing functions such as
Binary Find (BFN) or Search (SRH), you should use the Load Variable
(LDV) statement with the P option to pack the variables (see LDV).
• Do not put other run statements on the same line after a RUN
statement. The logic scan of the line terminates after executing the
RUN statement.
• You can also start utility runs such as chart runs. See the online help
system (HELP,@RUN) for details.

7-278 7831 9274-000

 RUN (Run Start)

Example

Start the run named test and send the variables vl and v2 and the character
string SAM to that run (the run initializes these as variables with INPUT$).
The current result (-0) is also available to the run:
@run test,vl,v2,SAM .

7831 9274-000 7-279

SC (Screen Control)

SC (Screen Control)
Use the Screen Control (SC) statement to create menus, input screens, and
overlays using screen commands.
You can use screen commands to perform basic screen operations, which
include positioning the cursor, clearing the screen, defining fields, and
defining screen attributes. You can also use screen commands to design
reports that define fields, box data in a specified area, and map function
keys. See "Screen Commands" in this subsection for more information.
When the SC output is displayed, the run is suspended until the user
presses Transmit or a function key, unless the statement options indicate
an interim output or a forced transmit.
You can also design your screens using a menu-driven screen generator
called the SCGEN run. For more information, see Section 5, or enter ap t
on the control line, tab to SCGEN, and press Help.
The SC statement has two formats. Use format 1 to directly specify screen
commands, or use format 2 to access a report containing screen commands
(also referred to as a form).
Condition
If you use format 2, a report containing executable screen commands must
exist.
Formats
@6C[ tabp,sn,lab] o scmnd .

@ISC,c,d,r[,1,q,tabp,sn,lab] o [fldtxt] .

;•••-",,‘

7-280 7831 9274-000

 SC (Screen Control)

Format 1
@SCE tabp,sndab] o scmnd .

Following is a description of the fields and subfields:

Field Description

tabp Tab position at which to place the cursor, where a positive number is the
number of tab positions forward (maximum of 100) from the home position
and a negative number is the number of tab positions backward (maximum of
100) from the home position.

1100: sn Station number where output is to be displayed. If you omit this field or
specify 0 (zero), output is displayed at the station executing the run.

V 1100: lab Label to go to if the output to another station cannot be completed

successfully. If you omit this field and the run cannot be successfully
completed, it is terminated with an error.

o Options. See Options.

scmnd Screen command or commands to be executed. See "Screen Commands" in

this subsection.

7831 9274-000 7-281

SC (Screen Control)

Format 2
tiSC,c,d,r[,1,q,tabp,an,lab] o [fldtxt] .

Following is a description of the fields and subfields:

Field Description

c,d,r Report containing screen commands (also referred to as a form).

Line number in the specified report at which to start reading screen control
commands. Default = 2.

q Number of lines to read in the specified report. Default = all lines to the end of
the report.

tabp Tab position at which to place the cursor, where a positive number is the
number of tab positions forward (maximum of 100) from the home position,
and a negative number is the number of tab positions backward (maximum of
100) from the home position. Default = home position.

V 1100: sn Station number where output is to be displayed. If you omit this field or
specify 0 (zero), output is displayed at the station executing the run.

17v17 1100: lab Label to go to if the output to another station cannot be completed
successfully. If you omit this field and the run cannot be successfully
completed, it is terminated with an error.

o Options. See Options.

fldtxt Field text — text to be inserted into unprotected fields (see the FLD and
DFLD/AREA commands under "Screen Commands"). This field can contain a
list of items separated by commas. The first item is placed in the first field,
the second item in the second field, and so on. Note that this field is not
interpreted unless the T (field text) option is specified in the SC statement.

Options
B Blink. Changes the less than (<) and greater than (>) signs to the
left and right blink characters in all literal text. The blink
characters may vary from terminal to terminal. See also the LB and
RB commands in "Text Handling Commands" in this subsection.
C Center. Allows screen output (such as menus) designed to be
centered on standard 80-character display terminals to be centered
on terminals of other widths.

7-282 7831 9274-000

 SC (Screen Control)

H Home Cursor Bypass. Bypasses the initial home cursor (HC)

command that is automatically performed by the SC statement prior
to executing the first screen command.
I Interim Output. Resumes the run automatically when the output is
completed. Input is not accepted. See also the Q option.
K Key Mapping. Does not disable any current function key mapping.
By default, the SC statement disables any currently mapped
function keys prior to executing the first screen command.
L Line Control. Allows you to regain line control on the previously
displayed report using the Paint key.
M Mask. Sends the data, but not spaces. (If data exists on a line, only
the columns containing new data are overwritten. The old and new
data are blended together on the same line.)
O Overlay menu. This option reprocesses the screen commands, but
only repaints the text. It efficiently repaints or puts new data onto a
menu that is already on the screen.
Q Quick Output. Resumes the run automatically when the output is
displayed. This option is similar to the I option except that the run
does not suspend, pending completion of the output, but rather
continues as soon as the output is displayed.
S Sends the data including all spaces. (The default method of sending
characters is that if fewer than six consecutive spaces appear, the
system sends the data, including spaces. If six or more spaces
appear, the cursor skips over the positions where the spaces would
have been placed.)
T Field Text. Inserts text supplied in the 1 Idtxt field into
unprotected screen fields created with the FLD command. See the
FLD and DFLD commands under "Screen Commands." Using this
option, you can add values to menu fields. The T option is valid only
when a report is specified in the SC statement (see Format 2).

7831 9274-000 7-283

SC (Screen Control)

U Update Control. Overlays a current report with data (for example,

to display a message) but allows the user to perform manual SOE
updates by holding update control of the report. This option is only
meaningful when a report is on display.
X Causes a screen to be transmitted as it is displayed, just as if the
user had pressed Transmit.

Reserved Words
Use reserved words to tailor screens to the site, user, and terminal. Using
reserved words also enhances the portability of screens.
You can use the following reserved words with the SC statement. (See
Appendix B for the contents of each word.)
- ADRW$ - DEPT$ - RPT$
- AKEY$ - DLINE$ - STNUM$
- CAB1$ - F1$ through F10$ - T1C$
- CAB$ - KKEY$ - TIME$
- DATEO$ through DATE8$ - LRRSD$ - USERS
- DAY$ - MAPER$ - )(KEYS
- DEPN$ - MKEY$
The following reserved words are recognized only by the SC statement:
ALERT$ The current site alert message text.
DBASE$ The current site database size threshold message text.
V 1100: The DBASE$ reserved word is not available on
OS 1100 MAPPER Systems.
V 1100: DMSG$ System down or purge time message text.
DUPLX$ The current site duplex file integrity error message text.
V 1100: The DUPLX$ reserved word is not available on
OS 1100 MAPPER Systems.
LOGO$ Site-defined text for the sign-on and active screens.
STERR$ The current site startup error message text.
V 1100: The STERR$ reserved word is not available on
OS 1100 MAPPER Systems.

7-284 7831 9274-000

 SC (Screen Control)

Error Status Reserved Words

If the run errs while processing an SC statement, it loads STAT1$ and
STAT2$ with the following information:
• STAT1$ contains the column number where the error occurred. If
screen commands are being read from a report, STAT1$ contains a
report column; otherwise, it contains the character position in the
interpreted screen command string (from the s cmn d field) of the SC
statement.
• STAT2$ contains the report line number where the error occurred in the
screen command report (format 2 only).

Screen Commands
There are six categories of screen commands. Each category comprises a
unique set of commands; the commands are described in the subsections
that follow.
• Cursor control commands
• Screen editing commands
• Field and attribute commands
• Text handling commands
• Screen printing commands
V PC MAPPER: Screen printing commands are not available on Personal
Computer MAPPER Systems.
• Setup commands
How Screen Commands Are Interpreted
• To provide a known starting point, the system automatically moves the
cursor to the home position before the first screen command is
interpreted.
• Screen commands are executed in the order they are specified.

7831 9274-000 7-285

SC (Screen Control)

• When commands are read from a report, a trailing space in any subfield
or a space in column 1 terminates the scan of the current report line.
You can use the remaining portion of the line for comments.
• Not all screen commands produce the same results on all types of
display terminals. Whenever possible, screen commands that cannot be
executed on a particular terminal are ignored.
How Data Is Interpreted
• By default, the SC statement disables any current function key mapping
before executing the first screen command. Use the K option to keep the
current function key mapping enabled.
• Any string of data that is not the name of a valid screen command is
treated as literal text.
Syntax Rules for Screen Commands
• Use semicolons ( ; ) to separate commands.
• If a screen command is too long to fit on one report line, you can
continue it on the next line. Any command subfield that specifies text,
such as field or message text, recognizes the reverse slant ( \ ) as the
continuation character when it occurs outside of literal delimiters.
• Follow these guidelines when specifying screen coordinates:
If you omit a value, the current cursor position is used.
If you specify a signed value (for example, +3 or -10), it is assumed to
be relative to the current cursor position.
The home position is 1,1 (row 1, column 1).
• Enclose attribute parameters in parentheses. This is necessary because
the attribute parameters together are actually one subfield. For
example:
at t ,(rv,whi/red)

del ,1,(pr ,rv,tc); at t ,1

See Using Inline Attributes, ATT Command and DEF Command under
"Field and Attribute Commands" for more information.

7-286 7831 9274-000

 SC (Screen Control)

• Literal text, such as field or message text, that contains spaces, commas,
or semicolons must be enclosed in apostrophes ( ' ) or whatever literal
delimiter is in use. See the TIC command under "Text Handling
Commands." When using format 1 of the SC statement, the TIC$
reserved word is usually the easiest way to accomplish this.
• If you are building screen commands in a run output area, use a
sequence of two apostrophes to produce one apostrophe in your data.
• Literal text that contains spaces must be enclosed in a double set of
literal delimiters.
This example statement uses format 1 and displays "Glen Ellyn." The
delimiters are % and'. Note that the TIC command defines % as a
literal delimiter.
@sc " prep;tic,%;'96Ien Ellyn96'
• When using format 2 of the SC statement, use a sequence of two
apostrophes to produce one apostrophe in your data.
When using format 1, define the literal delimiter to be a character other
than an apostrophe and use the reserved word TIC$ to equal an
apostrophe in the literal text. This example statement defines the
delimiter as % and displays "We've".
@sc " prep; i c ,%;94NeAti c$36-ve96 .
• To insert variables in literal text, follow the general guidelines set for
literal text and place the variable name in the literal text.
For example, this statement places the value of v2 in the literal phrase.
@sc " prep;tic,%;'96Let %'v2'% out%'

7831 9274-000 7-287

SC (Screen Control)

Cursor Control Commands

Table 7-14 lists the commands that control the position of the cursor on the
screen.

Table 7-14. Cursor Control Commands

Command Description

HC Home Cursor. Moves the cursor to the home position.

PC,r,c Position Cursor. Moves the cursor to the specified row (r) and column (c)
position. When specifying relative cursor coordinates, the cursor wraps
around the edges of the screen as if you were moving the cursor manually.

CR[,n] Cursor Return. Sends a cursor return to move the cursor to column 1 of the
next screen line. Repeat n times. Default =1.

TAB[,n] Tab Cursor. Tabs the cursor forward n positions. Default =1. If n is
negative, the cursor tabs backward. Note that when you use the TAB
command, the cursor position becomes unknown by the SC statement.
Therefore, after you use the TAB command, you cannot use a command that
references the current cursor position until you use a command that
reestablishes the cursor location (such as HC, PC, FLD, or MSG).

7-288 7831 9274-000

 SC (Screen Control)

Screen Editing Commands

\--, Table 7-15 lists the commands that perform on-screen editing operations.

Table 7-15. Screen Editing Commands

Command Description

CS Clear Screen. Erases the entire display and moves the cursor to the home
position.

ED Erase Display. Erases the display from the current cursor position to the end
of the screen.

EUD Erase Unprotected Display. Erases the unprotected portion of the display
from the current cursor position to the end of the screen. Attributes and
protected fields are not erased.

PD Protect Display. Protects the display beginning at the cursor position and
continuing to the end of the display. Using PD does not alter the text and
attributes that you are planning to display. You can also use PD to prepare
the screen for overlaying.

DIL[,ri] Delete in Line. Deletes the unprotected character under the cursor, shifting
succeeding characters, up to the end of the field or line (whichever occurs
first), to the left. Repeat n times. Default =1.

DID[,n] Delete in Display. Deletes the unprotected character under the cursor,
shifting succeeding characters, up to the end of the field or display
(whichever occurs first), to the left. Repeat n times. Default =1.

IIL[,n] Insert in Line. Inserts a space at the current cursor position, shifting the
character under the cursor and all succeeding characters up to the end of
the field or line (whichever occurs first), to the right. Repeat n times.
Default =1.

11D[,n) Insert in Display. Inserts a space at the current cursor position, shifting the
character under the cursor and all succeeding characters up to the end of
the field or display (whichever occurs first), to the right. Repeat n times.
Default =1.

continued

7831 9274-000 7-289

SC (Screen Control)

Table 7-15. Screen Editing Commands (cont.)

Command Description

DL[,n] Delete Line. Deletes the line the cursor is located on, moving the remaining
lines up. Repeat n times. Default =1.

IL[,n] Insert Line. Inserts a blank line at the cursor location, moving the line the
cursor is located on and all remaining lines down. Repeat n times.
Default =1.

DUP[,n] Duplicate Line. Duplicates the line the cursor is on onto the line directly
below it. The cursor is positioned on the duplicated line. Repeat n times.
Default =1.

EEL Erase to End of Line. Erases from the current position to the end of the line
or field, whichever occurs first. Attributes and protected fields are not erased.

Field and Attribute Commands

Use field and attribute commands to define fields, areas, and their
attributes. You can place attributes anywhere on the screen. The attribute
you define extends forward to the immediate left of the next attribute or to
the end of the screen, whichever occurs first. See "Field Attribute
Parameters" in this subsection for more information.
- Attribute (ATT)
- Define Attribute (DEF)
- Field (FLD)
- Message (MSG)
- Prepare Screen for Painting (PREP)
- Define Field (DFLD) and AREA

7-290 7831 9274-000

 SC (Screen Control)

Attribute (ATT) Command

Use the ATT command to output an attribute at the current or designated
cursor position.
Format
ATT, attrkr,c1
Following is a description of the subfields:

Field Description
attr Attribute to be output. See "Field Attribute Parameters" in this subsection.

r,c Cursor position where attribute begins. See Syntax Rules for Screen
Commands under "Screen Commands" for rules on specifying attributes.

Example
This example positions the cursor to row 2, column 1, and outputs to the
screen an attribute that has protected input and a color of white on blue:
att,(pr,whi/blu),2,1

7831 9274-000 7-291

SC (Screen Control)

Define Attribute (DEF) Command

Use the DEF command to define a numbered attribute for subsequent use in
other screen commands. Once defined, you can use a numbered attribute
anywhere an attribute is required.
Format
DEF,nhat t 11

Following is a description of the subfields:

Field Description

n Number with which to identify the attribute (1 through 20).

attr Attribute to define. See Field Attribute Parameters under "Field and Attribute
Commands" in this subsection.

Example
This example defines attribute number one as having protected input and a
color of white on blue:
def,1,(pr,whi/blu)

7-292 7831 9274-000

 SC (Screen Control)

Field (FLD) Command

Use the FLD command to generate a field on the screen.
Format
FLD[,r,c,raiz,caiz,o,attr,end•attr,text]

After the statement executes the FLD command, the cursor appears on the
last line of the field, two columns beyond the end of the field.
Following is a description of the subfields:

Field Description

GC Cursor position of the upper left corner of the field. See Syntax Rules for Screen
Commands under "Screen Commands" for rules on specifying screen
coordinates.

rsiz Vertical field size in rows (lines). Default =1.

csiz Horizontal field size in columns (characters). Default =1.

0 Options.

Border options:

A Attributes. Outputs field attributes even if the field is being boxed. Use this
option to produce a highlighted box around a field. Use only with the B
option.

B Box. Draws a box around the field if the terminal supports box drawing
characters. The box is drawn inside the perimeter of the field reducing the
effective size of the field by two rows and columns. See also the A option.

F Frame. Frames the field with emphasis. This option is terminal dependent.

S Sides. Draws lines on the left and right sides using emphasis. This option is
terminal dependent.

T Top. Draws a line at the top of the field using emphasis. This option is
terminal dependent.

U Underline. Draws a line under the field using emphasis. This option is
terminal dependent.

V BTOS: The border options (F, S, T, U) are not supported.

continued

7831 9274-000 7-293

SC (Screen Control)

continued

Field Description

Justification options:

C Centers the text in the field.

L Left-justifies the text in the field.

R Right-justifies the text in the field.

✓ Varies the size of the field to fit the text supplied. Default (no text) and
maximum size is csiz. The field is left-justified within the columns bounded by
c and csiz; use this with the R or C options to alter justification.

Miscellaneous options:

E Empty. If the field is empty (no text), do not display it. Use this option for
status fields that should only be displayed if relevant.

P Protect. Two conditions apply:

1. If a field is not defined with the PR parameter and is empty when placed
on the screen, protect it from user input.

2. If a field is defined with the PR parameter, allow data that is supplied on

the SC run statement via the statement option T.

attr Attribute that defines the characteristics of the field. (See Attribute Parameters.) If
no attribute is specified, no attributes are output.

end-attr Attribute that terminates the field. This parameter is not required.

text Literal text to be inserted into the field. If you do not specify text, the data within
the boundaries of the field remain unaltered. If you use the T option on the SC
statement, text supplied in the fldtxt field of the SC statement is used instead. See
also the P option.

7-294 7831 9274-000

 SC (Screen Control)

Example
This example shows how the FLD command is used to create the Add
Report (AR) function form. The A, B, and F options in the first FLD
command create a highlighted border if permitted by the terminal type. The
second FLD command places the menu title in the center of the top line of
the border. Execute the AR function to see the result.
prep,(pr,bac)
fkey,1,Resume,rsm
fkey,2,Paint,pnt
fkey,4,Return,formret,7
FKEY,8,Help,dsphelp,1
fkey,10,Quit,"
PC,1,61;'AR'

FLD,2,6,6,69,afb,(PR,boc)
FLD,2,6„69,cv,(PROc)„' Add Report

dfld,inp,u,(ts,ai,fc);dfld„,(co,fc)
area„3,8,4,65„(pr,mc)

Report or drawer __ inp

Title inp
end
(continued)

7831 9274-000 7-295

SC (Screen Control)

Message (MSG) Command

Use the MSG command to display a message or prompt line.
Format
MSG,r,o,attr,text

After the statement executes the MSG command, the cursor appears in
column 1 of the line on which the message is displayed.
Following is a description of the subfields:

Field Description

Row on which to place the message.

0 Options:

Blank Displays message text as given.

B Blink. Allows blink characters to be used on non-error messages.

See the LB and RB commands in "Text Handling Commands."

E Presents the text in system message format. That is, center the
message text on the line and translate the < and > characters to left
and right blink characters.

L Left-justifies the message text.

R Right-justifies the message text.

C Centers the message text on the line.

attr Attribute to be used on the message line. The default attribute is reverse video
(RV) and the user's configured system message color from the user registration
report.
V 1100: Default = white on rec.,
RTfIC• rlami tit = Whit= nn 1,10,4
V
text Literal text for the message (up to 79 characters).

7-296 7831 9274-000

 SC (Screen Control)

Example

This example displays a message on line 1 using the text supplied. The
user's default message attribute is used.
msg,1,e„'that input is not valid'

Prepare Screen for Painting (PREP) Command

The PREP command prepares the screen for painting an input menu. The
PREP command clears the screen and outputs an attribute on row 2,
column 1.
If you do not specify an attribute, (PR,WHI/BLA) is assumed. The PREP
command is equivalent to this sequence of commands:
CS;ATT,(attr),2,1.

Format

PREP[,attr]

Following is a description of the subfield:

Field Description

attr The attribute to use in place of the default. See Field Attribute Parameters
under "Field and Attribute Commands" in this subsection.

Example
This example protects the input menu being created by subsequent screen
commands and displays the background colors as defined by the Terminal
Definition Report for the terminal type.
V 1100: On OS 1100 MAPPER Systems, displays tne Dacxgrouna colors as
defined by the terminal type.
prep,(pr,bac)

7831 9274-000 7-297

SC (Screen Control)

Define Field (DFLD) Command

The DFLD command defines field characteristics for later use by the AREA
command. The DFLD command supplies all the information necessary to
output a field, except screen location and field size which is supplied by the
AREA command. After an AREA command is processed, all field definitions
are discarded. See "DFLD and AREA Commands Example" in this section.
You can define up to 40 named and 40 unnamed fields using the DFLD
command.
Format
DFLD[,name,opt,attr,text]

Following is a description of the subfields:

Field Description

name The name of the field you are defining. You can use a maximum of 12
characters.

opt Options.

Border options (terminal dependent):

F Frame. Frames the field with emphasis.

S Sides. Draws lines on the left and right sides using emphasis.

T Top. Draws a line at the top of the field using emphasis.

U Underline. Underlines the field using emphasis.

Justification options:

C Centers the data in the field.

L Left-justifies the data in the field.

R Right-justifies the data in the field.

✓ Varies the size of the field to fit the text supplied. Default (no text) and
maximum size is determined by the length of field as specified in the
AREA command data. The field is left-justified (use with R or C options
to alter justification).

continued

7-298 7831 9274-000

 SC (Screen Control)

continued

Field Description

Miscellaneous options:

E Empty. If the field is empty (no text), do not display it.

P Protect. Two conditions apply:

1. If a field is not defined with the PR parameter and is empty when

placed on the screen, protect it from user input.

2. If a field is defined with the PR parameter, allow data that is

supplied on the SC run statement via the statement option T.

at& Attribute that defines the characteristics of the field. (See Attribute
Parameters.) If no attribute is specified, no attributes are output.

text Literal text to be inserted into the field. If you use the T option on the SC
statement, text supplied in the fldtxt field of the SC statement is used instead.
See also the P option. If you do not supply text, the field will be blank.

7831 9274-000 7-299

SC (Screen Control)

Area (AREA) Command

Use the AREA command to lay out an entire region (area) of the screen
including both its text and fields.
The data that defines the contents of the area begins in column 1 of the
report line immediately following the AREA command. The text is
displayed exactly as it appears. The locations and sizes of fields within the
area are indicated by low line characters ( _ ).
The AREA command recognizes reserved words, inline attributes, and
literal delimiters in its data.
Note: The AREA command is valid only if screen commands are being read
from a report.
Condition
The characteristics of the fields indicated with the AREA command must be
previously defined with DFLD commands.
Format
AREM,name,r,c,rsiz,csiz,opt,attr]

7-300 7831 9274-000

 SC (Screen Control)

Following is a description of the subfields:

Field Description

name The name of the area you are defining. You can use a maximum of 12 characters.
The MAPPER system stores up to 10 named areas in memory. Naming an area
alters the way input is received from the screen. When XKEY$ or a function key is
pressed with the cursor in a named area, only the input from that portion of the
screen is received. If the area is output from a run:

AREA$ contains the name of the area from which input occurs.

FIELD$ contains the field number within the area in which the cursor is
located.

CURV$/CURH$ contains the cursor coordinates relative to the upper left

corner of the area.

r,c Cursor position coordinates for the upper left corner of the area. See Syntax
Rules for Screen Commands under "Screen Commands" for specifying screen
coordinates.

rsiz Vertical area size in rows (lines). Default = 1.

csiz Horizontal area size in columns (characters). Default =1.

opt Options.

Border options:

A Attributes. Displays the background attributes of the area even if the area is
being boxed. Use only with the B option.

B Box. Draws a box within the outer edge of the area if the terminal supports
box drawing characters. See also the A option.

F Frame. Frames the area with emphasis. This option is terminal dependent.

U Underline. Underlines the area using emphasis. This option is terminal

dependent.

Miscellaneous options:

D Delimiter. Marks fields with a field delimiter character only. Named fields are
not recognized. Allows you to place text immediately following a field.
attr Attribute that defines the background characteristics of the area.

7831 9274-000 7-301

SC (Screen Control)

How Field Definitions Work

If a named field is indicated in the area data, the characteristics of the field
come from the DFLD command specifying the same field name. A named
field definition may be referenced more than once.
The characteristics of unnamed fields in the area are supplied by DFLD
commands that specify no field name. The first unnamed field indicated in
the area uses the first unnamed definition; the second unnamed field uses
the second unnamed definition, and so on. If there are more unnamed fields
indicated than there are unnamed definitions, the last unnamed definition
is used to satisfy the remaining fields.
After the AREA command is performed, all field definitions are discarded.

7-302 7831 9274-000

 SC (Screen Control)

DFLD and AREA Commands Example

This example uses the DFLD and AREA commands to lay out an input
menu. Note that each field begins with at least one low line character.
When named field references are indicated in the area data, the name is
included in the size of the field.
The first unnamed field (Drawer let ter) uses the first unnamed definition;
the second unnamed field (User- i d) uses the second unnamed definition.
The last menu field (the single-character field following the Last Repor t
field) uses the third unnamed definition. The FLD commands put the
border and title around the menu; this must be done before the AREA
command.
fld,3,9,10,60,afb,(pr,rv,boc)
fld,3,9„60,cv,(pr,tc)„' Index User '

dild,num,u,(ts,no,fc)
dild,date,u,(ts,ai,fc)
dfld„u,(ts,ao,fc)
dfld„u,(ts,ai,fc),user$
dfld„,(co,fc)
area„4,11,8,56„(pr,mc)

Number of lines from each report _num_

Drawer letter _
User-id (ALL for all) _
Last update start date (DDMMMYY) _date__
Last update end date (DDMMMYY) _date__
First report _num
Last report _num _
end

7831 9274-000 7-303

SC (Screen Control)

Field Attribute Parameters

Attributes control the type of input allowed in a field (alpha, numeric,
cursor, protected), and they control intensity, color, text justification, tab
settings. There are six categories of field attribute parameters.
• Input control
• Intensity
• Text input justification
• Tab stop
• Emphasis protection
• Color
Input Control Parameters
AI Any input allowed (default).
AO Alphabetic input only.
NO Numeric input only.
CO Cursor only — no input allowed. The user can move the cursor into
the field, but cannot type any input. Use to create menu selection
items.
V 1100: The CO parameter is not available on OS 1100 MAPPER
Systems.
KO Kanji input only allowed. This parameter is only meaningful for
terminals that support Kanji.
V 1100: The KO parameter is not available on OS 1100 MAPPER
Systems.
PR Protected — cursor cannot be placed in field.
Intensity Parameters
BL Blinking.
LI Low intensity.
NI Normal intensity (default).
RV Reverse video.
VO Video Off. Use to make text invisible.
V BTOS: BL, LI, NI, and RV parameters are not supported.

7-304 7831 9274-000

 SC (Screen Control)

Text Input Justification Parameter

RJ Right-justify data entered by the user.
Tab Stop Parameter
TS Tab stop. Unlike a tab character, an attribute tab stop does not
require a screen location, so the cursor stops at the attribute position
rather than immediately after it.
Emphasis Protection Parameter
UE Unprotected emphasis. Overrides the normal protection given to
emphasis. The UE parameter causes the emphasis to be destroyed if
the data at that location is erased or typed over.
Color Parameters
Specify color parameters in pairs, separated by a slant ( / ). For example,
WHI/RED specifies white characters on a red background. If you do not
specify a color, white characters on a black background is assumed.
BLA Black
BLU Blue
CYA Cyan
GRE Green
MAG Magenta
RED Red
WHI White
YEL Yellow
V BTOS: Seven colors, plus black, are supported in the text mode. The only
available background color is black. If you select black as the character
color, the selected background color is used instead against a black
background. If you select the same color for characters and background,
green characters on a black background are used instead.

7831 9274-000 7-305

SC (Screen Control)

Terminal Defined Color Parameters

The following parameters determine the foreground and background colors
of menus, reports, fields, or field text defined by the terminal type in the
Terminal Definition Report or in the User Registration Report. These
parameters free the screen designer from having to choose the color for each
element on the screens.
V 1100: On OS 1100 MAPPER Systems, these parameters determine the
foreground and background colors as defined by the terminal type.
BAC Background color.
BOC Border color.
TC Title color.
MC Menu color. (The background color inside the menu border.)
FC Field color. Use this parameter with the input editing
parameters (AI, AO, NO, CO, KO, and PR) to select a color.
RC Report color. This parameter selects either the user's configured
report or result color based on the current report (-0) of the
station.
V 1100: Selects the color based on the current report (-0).
Using Inline Attributes
Use inline attributes in freeform text to highlight words or phrases. Create
inline attributes using the tilde (—) character followed by any valid field
attribute parameter. See Field Attribute Parameters under "Field and
Attribute Commands" in this subsection for a complete list of parameters.
Inline attributes apply only to the DATA and AREA commands.
Example
In this example, the freeform text appears as reverse video and yellow on
black. When the text is displayed, it starts at the cursor position of the
previous tilde.
—(rv,yel/bla)SC uses inline attributes.—(whi/bla)

7-306 7831 9274-000

 SC (Screen Control)

Text Handling Commands

Table 7-16 lists the text handling commands that display literal text on the
screen. You can also use them to substitute characters.

Table 7-16. Special Commands

Command Description

SOE[,c I ,n] Places a start-of-entry (SOE) character at the current cursor position. The
value supplied for n is the number of SOEs to display. Default =1. The value
supplied for c is the special character that you are using to redefine the SOE
character. The following example shows & as the special character to
represent the SOE character. For example:

soe,&;'Enter new value &'

LB[,c I ,n] Places a left blink character at the current cursor position. The value supplied
for n is the number of left blinks to display. Default =1. The value supplied
for c is the special character you are using to represent the left blink
character. See the RB command for an example.

RB[,c I ,n] Places n right blink characters at the current cursor position. Default = 1.
The value supplied for c is the special character you are using to represent
the right blink. For example:

lb,*; rb,%; MSG,1,e„.* Valid operators are <,>,= %'

produces the following:

< Valid operators are <,>,= >

TIC[,c I ,n] Places n current literal delimiter characters at the current cursor position.
Default = 1. Redefines the literal delimiter character, which is initially the
apostrophe, to a special character supplied by c. This is useful when
apostrophes are used in text. For example:

@sc " lic,"; "It is a sunny day."'

tic,"; "It's a sunny day."

7831 9274-000 7-307

SC (Screen Control)

EMP Command
Use the emphasis command to highlight or emphasize text on the screen.
You can place emphasis anywhere on the screen.
Format
EMPI,P,P,...,P1

Following is a description of the subfield:

Field Description

P Emphasis parameter or parameters, as follows:

Blank Tums off emphasis

C or I Separates columns

U or _ Underscores

Strikes through

' BTOS: Hardware display intensity is not supported.

Example
This example underscores the text enclosed in the literal delimiters.
emp,_; 'This text is underscored'
emp; 'This text has no emphasis'

7-308 7831 9274-000

 SC (Screen Control)

DATA Command
Use the DATA command to display a specified number of lines of text data
starting at a specified screen position.
The text data to display begins in column 1 of the report line immediately
following the DATA command. The text is displayed exactly as it appears;
spaces or commas within the data do not terminate the scan.
Note: The DATA command is valid only if screen commands are being read
from a report.
Format
DATM,r,c,rslz,csiz,pn,o]

Following is a description of the subfields:

Field Description

r,c Cursor position at which to start displaying the text. See Syntax Rules for Screen
Commands under "Screen Commands" for rules on specifying screen
coordinates.

rsiz Number of rows on the screen for the displayed text (paged text if the pn
parameter is specified). Default =1.

csiz Number of columns on the screen for the displayed text (paged text if the pn
parameter is specified). Default = report line length, or screen width, whichever is
smaller.

pn Page number. Indicates that the following report lines consist of page-formatted
data, and specifies the default initial page to be processed. This page number
may be overridden. See DSPFORM Action and PAGE Action in this subsection.

Use paged data to handle multiple menus within the same report, or for textual
information too lengthy for a single screen, such as application documentation.

o W option. Interpret reserved words, inline attributes, and literal delimiters in DATA
text.

7831 9274-000 7-309

SC (Screen Control)

#PAGE Identifier
A page identifier that marks the beginning and end of a form page.
Format
#PAGEhn]

Following is a description of the subfield:

Field Description

n Optional page number.

Comments
• The identifier must begin in column 1 of the report and the word PAGE
must be in uppercase (#page does not work).
• Pages may be numbered or unnumbered. However, only a numbered
page can be used as the initial page. Once the initial page is displayed,
the PAGE action allows access to any page.
Example
Page data can be structured as follows:
SC format Section description
#P AGE , 1 Page identi fier

Screen commands Pretext sect ion

END End of pretext sect ion

Number of I i nes specified Page text section (optional)

by rsiz on DATA command

Screen commands Post-text section (optional)

#PAGE,2 Page identifier

7-310 7831 9274-000

 SC (Screen Control)

How the SC Statement Interprets Paged Data

• Processing of paged data always stops when the next page identifier is
encountered.
• If the DATA command specifies a row size (raiz) or column size (c• 1 z)
of zero, the pages are assumed to consist only of a single command
section.
• Run statement options in effect at the start of the initial page remain in
effect with each new page. See the FKEY action PAGE.
• Begin context-sensitive help (help for a form field) for a specific page
after an END command and before the next page identifier.
• When moving from one page to the next,
- Current function key mapping is retained.
- Individual function keys can be mapped or remapped.
Paged DATA Example
In this example, the DATA command displays page 1 unless a DSPFORM
action specifies a different page number. The pn field in the DATA
command contains the value for the default page.
data 1
'PAGE ,1
I Id, 1, 1„65„ „' MAPPER Online Documentat ion'
fld,1,66„14„„'Screen 1 of 1'

(more screen commands)

#PAGE,END

7831 9274-000 7-311

SC (Screen Control)

Screen Printing Commands

V This section on screen printing commands does not apply to the BTOS II
MAPPER System or the Personal Computer MAPPER System.
The following screen printing commands control output to a printer:
PRT Sends protected and unprotected data to the attached print
device. It sends all data from the home position up to and
including the character under the cursor. The station number of
the device must exist in the MAPPER configuration report.
PRF Sends unprotected data to the attached print device (such as
COP). The PRF command is the same as the PRT command, but
it sends only unprotected data.
LF[,n] Places n line feed characters at the current cursor position.
Default = 1. Use this command with the PRT and PRF screen
commands.
FF Places a form feed character at the current cursor position. Use
this command with the PRT and PRF screen commands.

Setup Commands
The setup commands perform a variety of tasks such as sounding a beep at
the terminal, altering terminal setup, stopping the scan for screen
commands, controlling graphic display modes, overriding current options,
and mapping function keys.
BEEP Command
The BEEP command causes the terminal beeper to sound once. Use it to
signal the terminal user that an error or other special condition has
occurred.
Format
BEEP

After your run executes the BEEP command, it places the cursor at the
home position. You can execute only one BEEP command for each SC
statement.
Note: Not all terminals support this functionality.

7-312 7831 9274-000

 SC (Screen Control)

CP Command
V This section on the CP command does not apply to the BTOS H MAPPER
System or the Personal Computer MAPPER System.
The CP command alters the terminal setup (control page).
Format

CP I , P 1
The CP command accesses the terminal setup and inserts the text string p .
Any special sequence (control string introducer) required is inserted
automatically.
Note: Be careful when altering the terminal setup; it may affect the ability of
the MAPPER system to communicate with the terminal. See your
terminal documentation before using this command.
END Command
The END command stops the scan for screen commands and displays the
terminal output.
Format
END
MODE Command
The MODE command selects the display mode of a graphics terminal.
(Nongraphics terminals ignore the MODE command.)
Format
MODE I , p 1
The valid entries for the p field are as follows:
A Alpha only display.
G Graphics only display.
M Mixed mode display (graphics and alpha). This mode is terminal
dependent.

7831 9274-000 7-313

SC (Screen Control)

OPTS Command
The OPTS command overrides a subset of SC statement options that may be
in effect from the calling run. It allows the screen command report to
specify a subset of the screen control statement options independent of the
calling run.
Format
OPTS,[+ -Jo
If the first option character is a plus (+) the specified options are added to
the caller's options; a minus (-) removes the specified options. Allowable
options are B, C, H, K, L, M, S, U. See Options in this subsection for a
description of each allowable option.
Example
This example holds line control and displays all blank spaces. All other
options are deselected.
opts, is

7-314 7831 9274-000

 SC (Screen Control)

FKEY Command
The FKEY command specifies an action to be performed at the next input if
a particular function key is pressed. This is called function key mapping.
You can map actions to function keys 1 through 10 as well as Transmit. If
one or more keys are mapped, the remaining unmapped function keys are
disabled.
The FKEY command also displays a function key bar at the bottom of the
screen that shows the current mapping of function keys 1 through 10. The
current mapping remains in effect until the next output (see the K option
under Options).
Format
FKEY,n,title,action

Following is a description of the fields:

Field Description

n Function key number (0 = Transmit).

title Text to display with the function key number on the function key bar. The title
must be six characters or less. Enclose it in apostrophes. For example:

fkey,8,'Ex hip',"

action The action to take when the function key is pressed. The action can be any valid
command (control line) input that a user might enter, such as a ^ to display the
active screen or an x to sign off MAPPER software. See "Special FKEY Actions" in
this subsection for other possible actions.

7831 9274-000 7-315

SC (Screen Control)

Special FKEY Actions

The possible actions that may be specified with the FKEY command are as
follows:
Display Help (DSPHELP)
Display Form (DSPFORM)
Return to Previous Form (FORMRET)
Drawer Select (DRWSEL)
PAGE
SELECT
KEY
DSPHELP Action
Use the DSPHELP action to display context-sensitive help text (help for a
form field). The context-sensitive help text must be in the same report as
the FKEY command using the DSPHELP action and is preceded by the
HELP identifier.
Format
DSPHELP
Example
This example displays context-sensitive help for the field where the cursor is
positioned when the F8 key is pressed.
fkey,8,Help,dsphelp
Note: See "HELP Identifier."

7-316 7831 9274-000

 SC (Screen Control)

HELP Identifier
Use the HELP identifier to identify help text in your screen command report
and to determine where the context-sensitive help should be placed on the
screen.
Format
HELP,Ild,...fld row

Following is a description of the fields:

Field Description

f Id,...f Id The field number for which the following context-sensitive help refers.

row The row (screen line) where the help text display should start.

Example
In this example, the END command separates the commands used to build
the screen from the help text. The DSPFORM action specifies another form
to display if the user presses Help while the context-sensitive help (help for
a form field) is already displayed. The I character on the first HELP
identifier determines the width of the help window.
END
DSPFORM,49H , 1
HELP , 1 15 I
First Field

This is the text for the first field on

the screen. It is freeform text.
HELP,2
Second Field

This is the text for the second field on

the screen.
HELP

7831 9274-000 7-317

SC (Screen Control)

DSPFORM Action
Use the DSPFORM action to access a report containing screen commands
(also referred to as a form) when a function key is pressed.
While using the DSPFORM action, a stack of forms, built up in the order in
which they are displayed, is created. The stack grows this way until it is
cleared or rearranged using the DSPFORM or FORMRET FKEY actions.
The form at the top of the stack is the currently displayed form.
This stack is called the forms return stack and identifies which form
MAPPER software should return to if a FORMRET action is used. A stack
holds a maximum of 20 forms.
A form on the stack can include a saved context so that it can be returned to
the top of the stack or recalled at any time while a function is still active.
The forms that were stacked on top of it are discarded.
Format
DSPFORM, r[dc],pn,t abp,opt

Following is a description of the fields:

Field Description

r[de] The report, drawer, and cabinet containing the form. If the drawer or cabinet or
both are omitted, DSPFORM action assumes the cabinet number and the drawer
letter of the report containing the DSPFORM action. (This allows forms to be
created for maximum portability.) The system begins reading commands on line 4
of the report you specify (be sure to take this into account when entering
commands in the output area).

pn The form page number of text to display. This is valid only if the report specified
by rdc uses paged data. See "DATA Command" in this subsection.

tabp The tab position at which to place the cursor, where a positive number is the
number of tab positions forward (maximum of 100) from the home position and a
negative number is the number of tab positions backward (maximum of 100) from
the home position. Default =1. 0 = no positioning.

continued

7-318 7831 9274-000

 SC (Screen Control)

continued

Field Description

opt An option to set the return to this form if requested by a later form. Use one of
these values to specify the action for the return stack:

0 Puts this form on the top of the stack.

1 Clears the stack and puts this form on the bottom.

2 Marks the current stack position and then puts this form on the top of the
stack.

3Saves the context of the current form so a return restores the screen as it
currently exists. This is useful for help displays.
V 1100: This option is not available on OS 1100 MAPPER Systems.

4 Does not put an entry on the return stack for this form.

5 Overwrites the current entry on the return stack with this form.

Example
This example allows the user to display page 4 of the form in 202E by
pressing the Readme key (the F6 function key).
fkey,6,Readme,dspform,202e,4

7831 9274-000 7-319

SC (Screen Control)

Displaying a Form and Returning Control to the Run

V This section on displaying a form and returning control to the run applies
only to the OS 1100 MAPPER System.
Use the Display Form (DSF) statement to display a report containing screen
commands (form) from within a run. Use the DSF statement instead of the
SC statement to display a form starting at a particular page number.
Format
WSF,c,d,r,pn,tabp,opt .

The subfields for the DSF statement are the same as the DSPFORM action,
with the exception of the c , d, r subfields (cabinet, drawer, and report
containing the form).

7-320 7831 9274-000

 SC (Screen Control)

FORMRET Action
Use the FORMRET action to return to a previous form as determined by the
forms return stack. See "DSPFORM Action" in this subsection for more
information on stacking.
Format
FORMRET, cmd

Following is a description of the field:

Field Description

cmd A value that acts on the display. The values are

0 Returns to the previous entry on the return stack.

1 Returns to the start of the stack and clears the stack.

2 Returns to a mark previously set by a DSPFORM action with an opt value of 2

(see "DSPFORM Action" in this subsection).

3 Returns to a saved context set by a DSPFORM action with an opt value of 3

(see "DSPFORM Action" in this subsection). Note that only one saved
context applies for a user at any time.
V iinn • Thic volno is not mfmilminict nn nc 1 i MAPPPP Systems
4 Returns to the top entry on the stack. This is used if the current command
does not put anything on the stack.

5 If there is a report on display, repaints the report before redisplaying the form.
This is used to clean up a screen that has several menus on it.

6 If there is a report on display, either repaints it, or does a formret,0.

7 If there is a report on display, either repaints it, or does a formret,4.

Example
In this example, pressing the Return function key returns the user to the
previous entry on the return stack.
f key ,4,Re t ur n , f ormret ,0

7831 9274-000 7-321

SC (Screen Control)

PAGE Action
Use the PAGE action to page forward or backward in a form, after the initial
page of a form is displayed.
Format

PAGE , p

Following is a description of the field:

Field Description

p Use a plus (+) to move forward to the next page, a minus (-) to indicate the
previous page, or a number to go to a particular page. Default = +.

Example
In this example, pressing the RollFw key advances the user to the next
page of paged data.
f key ,2,Ro I IFw, page ,+

SELECT Action
Use the SELECT action to select one of a group of actions or commands,
based on the relative position number of the field that the cursor is in at the
time the key is pressed.
Format
SELECT

Note: The SELECT command must be in uppercase letters and the field
number must not start in column one.
Example
This example displays form 1.1e if the cursor is in the first field when the
Transmit key is pressed, and sorts the report on display if the cursor is in
the second field when the Transmit key is pressed.
f key ,0„SELECT
1,dspform,11e,1,1,0
2,sort -

7-322 7831 9274-000

 SC (Screen Control)

V 1100: The following example applies only to OS 1100 MAPPER Systems.

This example displays form lle if the cursor is in the first field when the
Transmit key is pressed, and returns control to the run if the cursor is in
the second field when the Transmit key is pressed. FKEY$ contains zero
and FIELD$ contains 2.
f key ,0„SELECT
1,dspform,11e,1,1,0
2, KEY
KEY Action
Use the KEY action to allow the function key to be passed directly to a run.
This action allows function keys to be interpreted by the run instead of by
the controlling form.
Format
KEY
Notes: 1. The KEY action must be in uppercase letters.
2. The FKEY$ reserved word can be used by the run to determine
which key was pressed.
Example
This example passes the Fl key to the run.
fkey,1,Cont.,KEY

7831 9274-000 7-323

SCH (Schedule Runs)

SCH (Schedule)
Ji7 This section dots not apply to the OS 1100 MAPPER System or the BTOS II
MAPPER System.
The Schedule Runs (SCH) statement allows you to establish a time for the
execution of a specified run statement. The SCH statement can queue any
of the following run statements for execution at a later time:
• Auxiliary (AUX) • Send Report (SEN)
• Background Run (BR) • Send Report to User (SNU)
• Print (PRT) • Start (STR)
• Remote Run (RRN)
Format
@SCH[,date,time] rst

Following is a description of the field and subfields:

Field Description

date Date to schedule the queuing function in YYMMDD (DATE1$) format.

Default = current date.

time Specifies the time of day to schedule the queuing function in HHMMSS
format where HH is the hour, MM is the minute, and SS is the second.
Default = current time.

rst Run statement to queue: AUX, BR, PRT, RRN, SEN, SNU, STR.

Example 1: Schedule a Background Run

Schedule the background run named status, with input data apr and
monthly, for execution at 7:00 p.m. on June 3, 1990:
@sch,900603,190000 br status,apr,monthly .
Example 2: Schedule a Print
Schedule the current -0 result to be printed on the current date at
10:00 p.m.:
tbsch„220000 prt,-0 .

7-324 7831 9274-000

 SEN (Send Report)

SEN (Send Report)

The Send Report (SEN) statement sends an entire report as a message to a
station. You can send reports only to configured stations.
If you send a report to a station within your site, the SEN statement creates
a result in the same drawer as the original report. If you send a report to a
remote site, the statement creates a result in cabinet 0, drawer F.
' 1100: On OS 1100 MAPPER Systems, you cannot send messages to a
remote site.
Format
@SEN,c,d,r,sn[,sl,ackl,lab] .

Following is a description of the subfields:

Field Description

c,d,r Report to send.

sn Station number to which to send the report.

sl Site letter. Default = local site.

V 1100: This subfield is not available on OS 1100 MAPPER Systems.

ack? Return acknowledgement when the message is received, Y or N. Default = N.

lab Label to go to if the station is not configured.

7931 9274-000 7-325

SEN (Send Report)

Examples
Send report 1AO, to station number 5:
@sen,0,a, 1,5 .
Send result -2 to station number 22 and return an acknowledgement after
the message is accepted (go to label 99 if the station does not exist):
then , -2,22„y , 099 .
V' 1100: The following example does not apply to OS 1100 MAPPER Systems.
Send report 2CO3 to station number 5 at MAPPER site j (go to label 3 if the
station does not exist):
then ,O,c ,2,5, j „003 .

7-326 7831 9274-000

 SFC (Set Format Characters)

SFC (Set Format Characters)

The Set Format Characters (SFC) statement establishes the format for a
following output display, such as that created by a Display Report (DSP) or
Output Mask (OUM) run statement.
'' 1100: On OS 1100 MAPPER Systems, you can also select columns to print
the next time you call the Auxiliary (AUX) or Print (PRT) run statements.
Format
@GFC[,c,d,r] vid .

Following is a description of the field and subfields:

Field Description

c,d,r Report on which to set the format. Default = -0.

vld The columns of the report you want to include in the display format. Use
variables, literal data, or both to specify the format you want to set.

Comments
• You can restore a display format previously saved with a Load Format
Characters (LFC) statement or build your own customized format with
an SFC statement. The x characters (or any characters other than
spaces) become displayed column positions; spaces are column positions
not displayed.
• You must use a DSP, DSX, OUM, or OUT statement after an SFC
statement.
• If a report is specified on the SFC statement, that report becomes the
current -0.
Example
Set the format for columns 1 through 10 and 16 through 20 in the current
result and display it:
@sfc 'xxxxxxxxxx xxxxx' .
@dsp,-0 .

7831 9274-000 7-327

SNU (Send Report to User)

SNU (Send Report to User)

The Send Report to User (SNU) statement sends an entire report or result
as a message to another user.
If you send a report to a station within your site, the SEN statement creates
a result in the same drawer as the original report. If you send a report to a
remote site, the statement creates a result in cabinet 0, drawer F.
V 1100: On OS 1100 MAPPER Systems, you cannot send messages to a
remote site.
Format
@SNU,c,d,r,user[,dept,s1,ack?,lab] .

Following is a description of the subfields:

Field Description

c,d,r Report to send.

user User-id to send the report to.

dept Department number of the user. Default = all departments.

sl Site letter. Default = local site.

1100: This subfiela is not availaoie on OS 11uu mArrER Systems.

ack? Acknowledgment requested after the message is received, Y or N.

Default = N.

lab Label to go to if the user-id or department does not exist.

7-328 7831 9274-000

 SNU (Send Report to User)

Comments
• The label is taken only if the user-id or department does not exist on the
local site. For remote sites, a message is returned informing you that
the user-id or department is invalid.
V 1100: On OS 1100 MAPPER Systems, you cannot send messages to a
remote site.
• If you do not specify a department number, the message is sent to that
user-id in all departments. The first user to accept and acknowledge the
message clears the message for all users.
Examples
Send report 1CO, to all users with the user-id of newuser (go to label 3 if
newuser is not a valid user-id):
tbsnu,O,c,l,newuser „ „003 .

V 1100: The following example does not apply to OS 1100 MAPPER Systems.
Send report 2B0, to mapcoord user-id in department 2 at site z, requesting
an acknowledging response:
@snu,0,b,2,mapcoord,2,z,y .

7831 9274-000 7-329

SOR (Sort)

SOR (Sort)
The Sort (SOR) statement sorts report or result data and creates a result.
1100: On OS 1100 MAPPER Systems, the system places a.. update lock on
the report to prevent other users from updating it while your run is sorting
it.
You can use the Sort and Replace Report (SRR) statement to replace the
sorted data into the original report. You cannot use the SRR statement on
results, and the SRR statement does not create a result.
Format
@SOR,c,d,r o cc Ityp,p .

Following is a description of the fields and subfields:

Field Description

c,d,r Report to sort.

0 Options field (see Options).

CC Column-character positions or names of the fields to sort.

Ityp Line type to sort (if you specify the A option, you can leave this subfield
blank, but enter the comma).

p Sort parameters (1 through 5, N, D). Enter sort parameters (1-5) in ascending

order starting with 1. You can also use the N and D parameters:

N = numeric sort
D = descending order

7-330 7831 9274-000

 SOR (Sort)

Options
A Processes all line types.
C(S) Distinguishes between uppercase and lowercase letters.
V 1100: C(x) Alters the sort process based on the character set order.
Ordinarily the system processes the report based on the
character set of the drawer. The C option allows you to choose
the character set type on which to base the sort. Use one of the
following:
C(F) Full character set (FCS)
C(L) Limited character set (LCS)
C(S) Strict comparison; distinguishes between uppercase
and lowercase letters.
V' 1100: X+ Sorts the data using the OS 1100 Sort/Merge product (if
installed at your site), regardless of the report length.
V 1100: X- Sorts the data using the normal MAPPER software process,
regardless of the report length.
If you do not specify X+ or X-, the sort process is determined by
the report length. See the coordinator for more information.
Example 1: Sort by Field in Ascending Order
Sort a report in ascending order by the Cust Code field:
@sor,0,b,2 " 'cost' 0 ,1 .
where:
,, Uses no options
'cust ' Sorts the Cust Code field (column 45 for four characters)
❑ Processes tab lines only
1 Sorts one level in ascending order

7831 9274-000 7-331

SOR (Sort)

Example 2: Sort a Report by Two Fields

Sort a report first by the Cust Code field, then by the Product Type field:
tbsor,O,b,2 " 'cust','product' ❑ ,1,2 .

or
@sor,O,b,2 " 45-4,15-9 ❑ ,1,2 .

where:
Uses no options
'cust ' Sorts the Cust Code field (column 45 for four
45-4 characters) first
1
' prod u c t ' Sorts the Product Type field (column 15 for
15-9 nine characters) second (that is, within the
2 Cust Code field)
❑ Processes tab lines only

Using the ISOR Run to Create an SOR Statement

This section on using the ISOR run applies only to the OS 1100 MAPPER
System.
You can use the Iterative Sort (ISOR) run to create an SOR statement. For
information on how to use the iterative runs, see the Manual Functions
Reference.

7-332 7831 9274-000

 SRH (Search)

SRH (Search)
The Search (SRH) statement searches vertically through one or more
reports or one result and creates a result of items found.
To create an update result that allows you to blend the changed lines back
into the original report or delete lines from the original report, use the
Search Update (SRU) statement. The SRU statement uses the same fields
and subfields as the SRH statement. See the online help system
(HELPASRU) for more information.
Format
@SRH,c,d[,r,l,q,lab] o cc Ityp,p [vlines,v1s,vrpt] .

Following is a description of the fields and subfields:

Field Description

c,d,r Report to scan.

Line number at which to begin the scan.

q Number of lines to scan.

lab Label to go to if no data is found.

0 Options field (see Options).

cc Column-character positions or names of the fields to scan.

ltyp Line type to scan (if you specify the A option, you can leave this subfield
blank, but enter the comma).

p Search parameters.

vlines Variable to capture the number of lines found with the search parameters.

vis Variable to capture the number of lines that were scanned. If a start scan line
is specified, all lines scanned (not just line type specified) are included.

vrpt Variable to capture the report number where the find was made.

The vrpt variable is useful only with the B[(n)] option to capture the number of
the report containing the last find made before bailing out. Note that if you do
not use the B option, vrpt = 0.

7831 9274-000 7-333

SRH (Search)

Options
A Processes all line types. Do not use this option with the T or
U options.
B[(n)] Stops a search after the nth find. Default = first find. The
search continues until n items are found or until the end of
the report.
C(S) Distinguishes between uppercase and lowercase letters.
V 1100: C(x) Alters the search process based on the character set order.
Ordinarily the system processes the report based on the
character set of the drawer. The C option allows you to
choose the character set type on which to base the search.
Use one of the following:
C(F) Full character set (FCS)
C(L) Limited character set (LCS)
C(S) Strict comparison; distinguishes between
uppercase and lowercase letters.
D Omits search information lines from the result.
V 1100: En Estimates the number of lines in the result, where n is an
integer. This option improves the efficiency of the search
when the output result contains more than 500 lines.
F Searches for a numeric value instead of a character string.
To search for a range of negative or floating point numbers,
use this option.
H In a multiple report search, includes the heading lines of the
first report only.
L(x) Omits lines of type x from the result. Note that you can use
any line type here. For example, L(*.a) indicates that
asterisk lines, period lines, and A-type lines are to be
omitted from the result.

7-334 7831 9274-000

 SRH (Search)

N Includes only those lines not meeting search criteria. For

example, if you search the column for the letter A, the result
contains all lines that do not contain the letter A in the
column. Do not use this option with the T or U options.
P Extracts paragraphs from the report. A paragraph consists
of data on a specified line type and all subsequent lines until
the next occurrence of that line type.
Q[(n)] Extracts the first n paragraphs from the report; stops the
search after the nth paragraph. Default = first paragraph.
Rx{-y I ','y) Scans a range of reports from report x through report y;
scans reports x,y,...y. (Note that the format Rx,y requires
apostrophes around the comma.)
V 1100: On OS 1100 MAPPER Systems, you do not need to
enclose the comma in apostrophes.
Examples:
r2','5 Scan reports 2 and 5
r2-10 Scan reports 2 through 10
r2-10','14 Scan reports 2 through 10 and 14
V 1100: S Groups lines found in search parameter order. (Use the S
option with the H option to avoid repeating report headings
for each group.) This option does not apply to the SRU
statement.
T[(x)] Includes data found on the line type you are processing and
on the preceding x type line. Default = tab line. Do not use
this option with the A, N, or U options.
A common use for the T option is to include the tab line
preceding the asterisk line found.

7831 9274-000 7-335

SRH (Search)

U[(x)] Includes data found in the type of line you are processing
and its surrounding data unit. A data unit consists of a
group of lines starting at line type x up to the next line of
that type. Default = tab line. Do not use this option with the
A, N, or T options.
With the U option, you specify the paragraph boundary as
the x line type. In contrast, the P option automatically uses
the line type you are processing as the paragraph boundary.
Searches for spaces or a specific line type when used with
the @ parameter.
Searches for a slant character as data when used with the /
parameter.
Example 1: Searching a Field for an Item
Search for amco in the Cust Code field:
@srh,O,b,2 d 'cust' 0 ,amco
where:
d Uses the D option to delete search information lines
'cust ' Searches the Cust Code field for the character string
amco amco
❑ Processes tab lines only
Example 2: Searching a Field for Items within a Range
Search the Order Number field for all numbers in the range 80000 to 90000:
tbsrh,O,b,2 d 39-5 ❑ ,80000/r,90000 .
where:
d Uses the D option to delete search information lines
39-5 Searches the Order Number field (column 39 for five
characters)
❑ Processes tab lines only
80000/ for all numbers in the range 80000 to 90000
r ,90000

7-336 7831 9274-000

 SRH (Search)

Example 3: Searching a Field for Two Items

Search for status codes sh or sc in the St Cd field and capture the number of
lines found and the number of lines scanned:
@srh,O,b,2 d 2-21:1,sh/O,sc <found>i3,<scanned>i3 .

where:
d Uses the D option to delete search information lines
2-2 Searches the St Cd field (column 2 for two
characters)
0,sh/1],sc for sh or sc on tab lines
<found>i3 Captures the number of lines found in <found>
<scanned> i3 Captures the number of tab type lines scanned in
<scanned>

Using the ISRH Run to Create an SRH Statement

V This section on using the ISRH run applies only to the OS 1100 MAPPER
System.
You can use the Iterative Search (ISRH) run to create an SRH statement.
For information on how to use the iterative runs, see the Manual Functions
Reference.

7831 9274-000 7-337

STN (Station Information)

STN (Station Information)

The Station Information (STN) statement provides information about a
specific station.
Format
@STN[,sn, lab vuser,vdepn,vdept ,vttyp,vvsiz,vhslz,vaspect ,
vcolor,vgraph] .

Following is a description of the subfields:

Field Description

sn Station number or terminal type you want information about.

lab Label to go to if the station does not exist.

*
vuser Variable to capture the user-id of the station.
*
vdepn Variable to capture the department name of the user.
*
vdept Variable to capture the department number of the user.

vttyp Variable to capture the terminal type name of the station. (These names are
identical to those provided by the TTYPE$ reserved word.)

vvsiz Variable to capture the vertical screen size of the station.

vhsiz Variable to capture the horizontal screen size of the station.

vaspect Variable (F type) to capture the aspect ratio of the specified station. (Same
as the value of the ASPECT$ reserved word.)

vcolor Variable to capture the graphics color flag or terminal. (Same as the value of
the COLOR$ reserved word.)

vgraph Variable to capture the graphics type. (Same as the value of the GRAPH$
reserved word.)

* If a user is not currently signed on to the terminal, vuser and vdepn are filled with spaces, and
vdept is set to zero.

7-338 7831 9274-000

 STN (Station Information)

Comments
• If the station number you specify does not exist or is inactive, the run
goes to the label specified in the t ab subfield; otherwise, the run errs.
If you do not specify a station number, or if the station number is zero,
the STN statement assumes the number of the station where the run
was started.
• If you specify a terminal type in the sn subfield, vuser and vdepn are
blank; vdept contains 0.
• Note that the STN statement does not create a result. Any result that
exists before the STN statement is executed is still the current (-0)
result.
Example
Capture information about station 100:
(gts tn, 100, 199 <user>h11,<dname>h12,<dnurn>14,<term>h7, \
<vs i ze> i 2 ,<hs i ze> i 3
where:
100 Provides information about station 100
199 Goes to label 199 if station 100 does not exist.
<user>h 11 Captures the user-id of the person currently signed
on in <user>
<dname>h12 Captures the department name in <dname>
<dnurn>i4 Captures the department number in <dnum>
<t e rm>h7 Captures the terminal type (for example, PCHR) in
<term>
<vs i ze> i 2 Captures the vertical screen size (for example, 24) in
<vsize>
<hs i ze> i3 Captures the horizontal screen size (for example, 80)
in <hsize>

7831 9274-000 7-339

STR (Start)

STR (Start)
This section does not apply to the BTOS II MAPPER System.
The Start (STR) statement collects data and uses this data as input to a job
or processes this data as a job itself. It can also start jobs that produce files
that can be returned to the MAPPER system with the Retrieve File (RET)
statement.
V PC MAPPER: The STR statement executes the command shell
(CMD.EXE) contained in a MAPPER report.
Format
@STR,c,d,d,s1,11c,logon,psw] .

7Z7' 1100:

@STR,c,d,d,runid,acct] .

Following is a description of the subfields:

Field Description

c,d,r Report that contains the job or the report to pass to a job.

s/ Site letter. Default = local site.

ifc Interface name of the job to which to pass the report.

V A Series: Default = blank (execute the data as a WFL job). See the
MAPPER system coordinator for the interfaces configured on your system.

U Series and UNIX: Default = blank (/bin/sh — UNIX shell).

logon Valid system logon to use at a remote site.

psw System logon password. Required if the system logon has a password
assigned.

V 1100: runid Batch run identifier. Default = the run-id in the Exec RUN statement.

V 1100: acct Batch run account number. Default = the account number in the Exec RUN
statement.

7-340 7831 9274-000

 STR (Start)

Comments
V • U Series and UNIX: When starting a job at a remote site, you must
specify a valid system logon and password for the remote site.
• IBM® start requirements follow the examples.
V • A Series: Some files generated by a WFL job can be returned to
MAPPER software with the RET statement. You may also use the
MAPPER sign-on command RUN OBJECT/MAPPER( " - fIl I ename") using
the name of a file containing a BPRUN$ statement to pass that file to
MAPPER software for execution. If an interface name is used, a file
title containing the data is given as a STRING parameter to the WFL
job.
• If starting a batch job, the job must have been previously entered in a
report or result.
• See the Manual Functions Reference and the online help system
(HELP,START) for information on the BPRUN$ and ENDRD$
commands.
• To include more than one report or drawer, use the $INCL$ command.
See Appendix C for information on data control commands.
• To control the format of the data in reports you transfer to the host, use
the data control commands described in Appendix C.
Example 1: Starting a Job on the Local Site
V 1100: Start the runstream in report 101A0 and identify the batch run as
bch10:
@str,O,a,101,bch10 .
V U Series and UNIX: Start the batch runstream located in report 3B0 (the
UNIX shell [/bin/sh] processes the runstream):
@str,O,b,3 .
V A Series: Start the WFL job located in report 3B0:
Cbstr,O,b,3„NBAUSER,LCCAL .

IBM is a registered trademark of International Business Machines Corporation.

7831 9274-000 7-341

STR (Start)

Example 2: Starting a Job on a Remote Site

U Series and UNIX: Pass report 101A0, to the job named filer on remote
MAPPER site w. Use the logon of newuser with a password of remote:
@str,O,a,101,w,filer,newuser,remote .
V A Series: Pass report 101A0, to the job named filer on remote MAPPER
site w. Use the logon of NEWUSER with a password of REMOTE:
@str,O,a,101,w,filer,NEAUSER,REMOTE .

IBM Start Requirements

This section on IBM start requirements applies only to the U Series MAPPER
System and UNIX MAPPER Systems.
If you intend to return output from the execution of the IBM jobstream, you
must include an IBM ROUTE statement in the jobstream. See the UNIX
system administrator for the remote address of the BSC or SNA connection.
If there is an error in the execution of the jobstream (that is, if BPRUN$
through ENDRD$ does not get built), the output from the IBM host is sent
(through the BPERRIBM run) to the user MAPCOORD on the default site.

7-342 7831 9274-000

 SUB (Subtotal)

SUB (Subtotal)
The Subtotal (SUB) statement subtotals report data.
Format
@GUB,c,d,r[,lab] o cc Ityp,p vrolts .

Following is a description of the fields and subfields:

Field Description

c,d,r Report in which data is to be subtotaled.

lab Label to go to if no lines exist to be subtotaled.

0 Options field (see Options).

CC Column-character positions or names of the fields to subtotal.

Ityp Line type to process (if you specify the A option, you can leave this subfield
blank, but enter the comma).

p Subtotal parameters:

Add
Subtract
Multiply
Divide
Move to this field
A Average
C Cumulate
M Move this field
S Subtotal (required)
S1-S5 Hierarchical Subtotals

vralts Variables to capture the results. Select the E option if you want the first
variable to capture the entry count for each subgroup. Substrings are not
allowed.

To initialize a variable to the size of a field, just specify the variable number
and type (for example, v1h, v2s, and so on). If you are using the E option, the
variables must be fully defined (for example, v2i6).

7831 9274-000 7-343

SUB (Subtotal)

Options
A Processes all line types.
C Looks for case changes in the subtotal key field values. Whenever
the value in the subtotal key field changes, a subtotal is displayed.
Use with the S parameter only.
V 1100: On OS 1100 MAPPER Systems, this option applies only to full
character set (FCS) reports.
E Counts the number of entries processed for each subtotal and enters
that count in the first defined variable. For example, if a subtotal
includes four values, the statement loads the first variable with 4.
I Ignores headings: processes report even though asterisk lines or
heading divider line may not exist.
J(x) Justifies numeric result values in variables to x; x is one of the
values listed below. Leading zeros appear to the left of a value,
nonsignificant zeros to the right. Neither affect the value.
C Eliminates leading and nonsignificant zeros. Inserts
commas every three digits in the integer portion of the
result. Right-justifies values.
L Eliminates leading and nonsignificant zeros. Left-justifies
values.
R Eliminates leading and nonsignificant zeros. Right-justifies
values.
X Eliminates leading zeros, left-justifies values, then fills
variable with nonsignificant zeros.
Z Eliminates nonsignificant zeros, right-justifies values, and
fills variable with leading zeros.
Comments
• Follow a SUB statement with an output line, since it creates one line of
output for each item subtotaled. Do not use variable substrings in the
output line.
• Define parameters as you would for a Totalize (TOT) statement (see
TOT in this section).

7-344 7831 9274-000

 SUB (Subtotal)

• Place the variable defined for the subtotal field in the output area.
• To provide a space for an asterisk whenever nonnumeric values are
encountered during subtotaling, a space is forced in the output line after
any variable created by an arithmetic operator. To eliminate the space,
use the * option.
• Even though you can predefine the size of a variable to load in a SUB
statement, you can also initialize the variable to match the size of a
corresponding report field. This is especially useful with a named field
because the name does not directly specify the field size; it also allows
the SUB statement to adjust to a change in the size of a field.
Example 1: Subtotaling Subgroups
Subtotal the subgroups in the Cust Code field and add the values in the Ord
Qty field:
@sub,O,d,1 " 'custcode','ordqty' v1h,v2i .
vt v2
where:
Uses no options
'custcode' Subtotals on the subgroups in the Cust Code
s field
'ordqty' Adds the values in the Ord Qty field

v lh Initializes v1 as a type H variable to the size of

the Cust Code field, to capture the name of the
subgroup
v2 i Initializes v2 as a type I variable to the size of
the Ord Qty field, to capture the subtotals for
each subgroup

7831 9274-000 7-345

SUB (Subtotal)

Example 2: Counting Entries and Omitting Error Flag

Count entries in report 1CO:
tbsub,O,c,1 e* 12-5,33-8 0,s,+ v1i,v2h,v3i6 .
v2 v1 v3
where:
0* Uses the E option to count the entries and the * option to
omit the error flag
12-5 Subtotals on the subgroups in the Sub Key field
s (column 12 for five characters)
33-8 Adds the values in the Retail $$$$ field (column 33
+ for eight characters)
0 Processes tab lines only
v 1i Captures the entry count for each subgroup in vl
v2h Captures the character from the Sub Key field in v2
v3 i 6 Captures the subtotals for each subgroup in v3
v2 v1 v3 Places the data in the output area in this format

7-346 7831 9274-000

 TOT (Totalize)

TOT (Totalize)
The Totalize (TOT) statement performs arithmetic and move operations on
fields within a report or result (and creates a result if you do not specify
variables to capture the resulting values).
Format
WOT,c,O,r[,iab] o cc ityp,p [vrsits] .

Following is a description of the fields and subfields:

Field Description

c,d,r Report to process.

lab Label to go to if no data is found.

o Options field (see Options).

cc Column-character positions or names of the fields to process.

ltyp Line type to process (if you specify the A option, you can leave this subfield
blank, but enter the comma).

p Parameters:

• Add (or multiplicand for multiplying)

Subtract
• Multiply (multiplier)
Divide
Move to this field
A Average
C Cumulate
D Delete commas from results
E Count entries when using the S option
Insert commas in the results
• Move this field
S Subtotal
S1-S5 Hierarchical Subtotals

watts Variables to capture the totals (if you use this field, the TOT function does not
create a result).

7831 9274-000 7-347

TOT (Totalize)

Options
A Processes all line types.
C Displays a subtotal if the value in the subtotal key field changes
case. For example, with the C option, if the value in the key field is
Rate on the third line and RATe on the fourth, a subtotal is shown
after the third line. Use this option with the S parameter only.
V 1100: On OS 1100 MAPPER Systems, this option applies only to full
character set (FCS) reports.
E Counts entries (see also the R option). In the TOT run statement,
the first variable contains the entry count.
H Cumulates horizontally.
I Ignores headings: processes the report even though asterisk lines or
the heading divider line may not exist.
J(x) Justifies numeric result values in fields to x; x is one of the values
listed below. Leading zeros appear to the left of a value,
nonsignificant zeros to the right. Neither affect the value.
C Eliminates leading and nonsignificant zeros. Inserts
commas every three digits in the integer portion of the
result, if the field is large enough. Right-justifies values.
L Eliminates leading and nonsignificant zeros. Left-justifies
values.
R Eliminates leading and nonsignificant zeros. Right-justifies
values.
X Eliminates leading zeros, left-justifies values, and fills fields
with nonsignificant zeros.
Z Eliminates leading and nonsignificant zeros, right-justifies
values, and fills leading spaces with zeros.
N Omits the grand total.
O Omits all data lines from the result, displaying only subtotal and
grand total information.

7-348 7831 9274-000

 TOT (Totalize)

Rn Rounds numbers to the nearest n. Use with the E option to round

entry counts. The range for n is .0000000000000001 to 100000.
For example if you type r.001, the values are rounded to the nearest
thousandth. If you type r10000, the values are rounded to the
nearest 10 thousand.
S Places subtotals in vertical operation fields.
=x Changes the line type indicator in column 1 to x, where x is an
asterisk, period, or alphanumeric character.
* Omits asterisk flags following results of vertical operations, except
for grand totals, when some of the data was invalid (nonnumeric or
blank).

7831 9274-000 7-349

TOT (Totalize)

Example 1: Adding a Field and Capturing Entry Count and Total

Add a field in report 1CO:
@tot,O,c,1 e 42-7 IL+ <count>i4,<total>i7
where:
Uses the E option to count entries
42-7 Adds the Sales Commiss field (42 for seven
characters)
<count>14 Captures the entry count in <count>
<total>17 Captures the total in <total>
Example 2: Multiplying Two Fields
Multiply the Spaces Req field by the Demo Quantity field, place the product
in the Demo Results field, and display the grand total of the Demo Results
field at the end of the result:
@tot,O,c,1 " 'space','demoquantity','demores' 1
1:1,+,*,=/13,,,+ .
where:
I
Uses no options
'space' Multiplies the Spaces Req field (column 50 for
five characters)
'demoquantity' by the Demo Quantity field (column 56 for
eight characters)
' demor es' and places the product in the Demo Results
field (column 65 for 15 characters)
Vertically sums the Demo Results field and
displays the grand total at the end of the result
0 Processes tab lines only

7-350 7831 9274-000

 TOT (Totalize)

Using the ITOT Run to Create a TOT Statement

V This section on using the ITOT run applies only to the OS 1100 MAPPER
System.
You can use the Iterative Totalize (ITOT) run to create a TOT statement.
For information on how to use the iterative runs, see the Manual Functions
Reference.

7831 9274-000 7-351

UNX (UNIX Interface)

UNX (UNIX Interface)

This section applies only to the U Series MAPPER System and UNIX
MAPPER Systems.
The UNIX Interface (UNX) statement executes UNIX commands.
Format
ONM,c,d,logon,pw,lab] o cmd [ergs] .

Following is a description of the fields and subfields:

Field Description

c,d Drawer into which the result is to be returned (-f option).

logon UNIX logon. Default = UNIX logon of the current run user.

pw UNIX logon password. Default = UNIX logon password of the current run
user.

lab Label to go to if the UNIX shell cannot be started.

o Options field. Enter options in lowercase characters. If you do not specify

options, you must designate the options field with two apostrophes (' ').

cmd UNIX command to be performed. Standard UNIX searching is done to find

the command. If the path is defined in your shell variable PATH, you do not
need to enter the full path name. Enclose commands containing embedded
spaces in apostrophes ( '). If you do not specify a command, designate its
position with two apostrophes (' ').

args Arguments passed to the UNIX command. Enter full path names only if the
command requires them. When entering arguments, enclose the command
and argument in apostrophes.

7-352 7831 9274-000

 UNX (UNIX Interface)

Options
-c Clears the screen after the statement finishes processing and
returns to the MAPPER system.
-f Returns the output of the command as a result in drawer A. If
you enter a file name immediately following the -f option, the
function places a copy of the output from the UNIX command
into that file. Do not use the -f option when executing an
interactive UNIX process such as vi and ed. (Do not use this
option with the -w option.)
-p Executes the user's .profile before executing the UNIX
command.
-w Allows the run user to press Resume to resume the run once the
command is executed and the output has been displayed. (Do
not use this option with the -f option.)
Comments
• If the run user entered the MAPPER system through the UNIX shell,
the user can execute any UNIX commands normally available through
that logon. When the UNIX command completes, the MAPPER run
continues.
• If the run user entered the MAPPER system directly from the UNIX
logon prompt (with a logon of mapper), the run terminates with an error.
(The mapper logon allows access only to MAPPER software.)
To prevent the run from terminating, be sure the UNX statement
contains a valid logon and password for all users of the run. You may
want to prompt the user for a valid logon and password before executing
the UNX statement.
When the command completes, the MAPPER run continues.
• If you use UNIX statements in runs that are to be executed in the
background from a remote site (RRN, NRN, NRM, BPRUN$ command
with the STR statement), you must specify a valid UNIX logon and
password for the remote site.

7831 9274-000 7-353

UNX (UNIX Interface)

a You may want to use the Refresh Screen (PNT) statement following a
UNIX command to reestablish screen attributes when the run user
returns from the UNIX environment.
• UNIX commands, arguments, and file names are case sensitive. For
example, the command /BIN/LS -L does not execute the /bin/ls -1
command.
Examples
Access the UNIX system shell; the I ogon and pw fields are specified by
<runlogon> and <runpw>:
@unx„<runlogon>,<runpw> " " .
Note: You must preserve the positions of options and commands.
The user can return to the MAPPER system by pressing Exit.
List the contents of the /usr/work/newuser directory and place the output in
a cabinet 0, drawer B result:
@unx,O,b -f '/bin/Is -I /usr/work/newuser ' .
Execute the UNIX cat command on file prod_status, and put the output in
file tmpfile and in the cabinet 0, drawer E result:
@unx,O,e -f/tmpfile '/bin/cat 'X
'/usr/work/newuser/prod_status' .

7-354 7831 9274-000

 USE (Use Variable Name)

USE (Use Variable Name)

The Use Variable Name (USE) statement assigns a variable name to a
specific variable number. See Section 4 for a description of named variables.
Format
USE name=q,name=v,...,name=v] .
Following is a description of the subfields:

Field Description

name Name to associate with the variable.

v Numbered variables to which to assign a name. If you want to initialize the

variable, include the type and size (such as v2h12).

Comments
• Normally, when you assign a name to a variable, you can refer to it only
by the name and not a variable number. However, if you assign the
variable with the USE statement, you can refer to it by either its name
or number.
• As a rule, you should not use named and numbered variables within the
same run. There may be certain cases, however, in which it is necessary.
For example, you may need to call an external subroutine containing
numbered variables from a run that uses named variables.
• You can assign several names with a single USE statement and
optionally initialize the variables at the same time. If you want to
initialize the variable while naming it, include the variable type and size
with the variable number.
Examples
Assign the name <station> to v190:
@use station=v190i5 .
Assign the name <designer> to v191:
@use designer=v191s77 .

7831 9274-000 7-355

WAT (Wait)

WAT (Wait)
The Wait (WAT) statement temporarily suspends the execution of a run.
Format
@NATI ,M, I al)) ms .
1100:
@NAT ms .

Following is a description of the field and subfields:

Field Description

V 1100: The M option and the lab subfield are not available on OS 1100 MAPPER Systems.

M Option that suspends the run until an outstanding message is received or

until the time specified by ms elapses.

lab Label to go to if an outstanding message is received.

ms Time in milliseconds to suspend the run. Specify an integer from 0 to

600,000. (600,000 milliseconds equal 10 minutes.)
V 1100: On OS 1100 MAPPER Systems, specify an integer from 0 to 60,000.
(60,000 milliseconds equal 60 seconds.)

Comments
• The M option on the WAT statement allows the run to stall until an
outstanding message is received or until the wait time is reached. If a
message is received and a label is specified, the run continues at the
label. If a message is not received within the wait time limit specified,
the run continues at the next statement.
1100: The M option is not available on OS 1100 MAPPER Systems.
• Use WAT statements interspersed with extensive logic loops to reduce
the impact on the MAPPER system.

7-356 7831 9274-000

 WAT (Wait)

• You can also use a WAT statement to hold an interim display (DSM,
DSP, OUV, and OUT) on the screen long enough to read it.
• Do not place any run statements on the same line following the WAT
statement. The logic scan of the line terminates after executing the
WAT statement.
Examples
The run waits 100 milliseconds before resuming:
wat 100 .
'V 1100: The following example does not apply to OS 1100 MAPPER Systems.
This example sends a report to <user>, uses the WAT statement with the
M option to wait for the user to receive the message, and displays status
messages on the run user's screen:
@020: . Send Report
@ snu,O,b,2,<user>,<dept>,<site>,y,199 .
@ wat,m,099 500000 . **Wait for user to receive msg***
@ ouv,1,1 ers$ .
@ ouv,15,15 'Message not received' .
@ wat 4000 . ***Suspend OUV display****
@ rel .
@099: . Process Response
@ .
@ . (other processing based on response)
@ rel .
@199: . Error Routine
@ ouv,1,1 ers$ .
@ ouv,15,15 'Problem with user-id, dept, or site'
@ wat 4000 . ***Suspend OUV display***
@ rel .

7831 9274-000 7-357

WRL (Write Line)

WRL (Write Line)

The Write Line (WRL) statement updates up to 23 lines of a report. The
WRL statement updates the report, renames that report -0, and releases
any previous -0 result.
Condition
Precede all WRL statements with an Update Lock (LOK) statement unless
you are processing a result. Enter an Unlock (ULK) statement following the
WRL statement to release update control.
Format
tl,c,d,r,1[,ntuid?,wpw,ccpyl] cc Ityp,vld .

Following is a description of the field and subfields:

Field Description

c,d,r Report to update.

I Line number to update.

ntuid? Do not update the time and user-id in the date line, Y or N. Default = N. If
you specify Y and the update date on the report is not the current date, the
system overrides your request and writes the update time, date, and user-id.

wpw Write password to place on the report. Use this subfield to set a password
on a report. Note that the fields after wpw are all mandatory; you cannot set a
write password without updating the report.
Vy 1100: ccpy? (This subfield applies only when using the Deferred Update [DFU] statement
on the OS 1100 MAPPER System.) Write a complete copy of the report if this
is the first WRL statement since executing the DFU statement, Y or N.
Default = N.

Writing a complete copy of the report may cost additional I/O overhead to
update the report; however, it can considerably decrease the cost of other
users attempting to access the same report while it is under a deferred
update lock.

continued

7-358 7831 9274-000

 WRL (Write Line)

continued

Field Description

cc Column-character positions or names of the fields in which to write data.

V 1100: Note that starting with level 35R1, the WRL statement writes data on
period lines in the columns you request in the cc subfield. In previous levels,
the data would always be written starting in column 2.

Ityp Line type designator to write. Updated lines will be changed to the line type
you specify. (In other run statements, the Ityp subfield specifies the type of
line to process; however, the Ityp subfield in the WRL statement specifies the
line type to be written.)

vld Content of variables, literals, reserved words, constants, or any combination

of these, to write.

Examples
Use the LOK statement to lock report 3B0, for update, then use the WRL
statement to write a tab line in line 6 of the report, placing the characters sh
in column 2 for two characters. Use the ULK statement to release update
control:
@lok,O,b,3 wr1,0,b,3,6 2-2 ❑ ,sh ulk .
For a multiline write, expand the parameters field, as in this example:
@lok,O,b,3 .
@wr 1 ,0 , b ,3, 6 5-6,77-3 0 , 900605, TUE/0 ,900613,KED .
@u 1 k
This WRL statement writes two tab type lines (lines 6 and 7) in the report
with 900605 (line 6) and 900613 (line 7) in column 5 for 6 characters, and
TUE (line 6) and WED (line 7) in column 77 for 3 characters.

7831 9274-000 7-359

XQT (Execute)

XQT (Execute)
The Execute (XQT) statement executes one or more run statements,
including data for output areas. You can execute up to 132 characters of
data.
' 1100: On OS 1100 MAPPER Systems, you can execute up to 640 characters
of data.

Format
WIT(,lab I vld} .
Following is a description of the field and subfield:

Field Description

lab Label or line number to execute.

vld Variables, literals, constants, reserved words, or any combination of these,

from which to formulate and execute a run statement.

Comments
• You can use the I a b subfield to execute a line already containing one or
more run statements, or you can formulate the statement to execute
within your run, using variables, for example, containing data captured
from an input screen that you want to include in a run statement.
• After interpreting the XQT statement, the system executes either the
data at the specified label or line number or the data specified in the
v 1 d field.
• If the data you want to execute is a run statement, the first character of
the data must be an at sign (@); otherwise it is treated as data for the
output area and the run continues at the next line in the run control
report. (The at sign [@] tells the MAPPER interpreter that the
information that follows is a run statement.)
• You can include any characters in the data you want to execute except
the reverse slant ( \ ). You need not enclose commas ( , ) or slants ( / ) in
apostrophes.

7-360 7831 9274-000

 XQT (Execute)

• If the statement being executed errs, the run goes to the label given on
the executing statement. If the executing statement does not contain a
label, the run terminates in error with the XQT statement, and a system
message appears.
• You can nest XQT statements. That is, one XQT statement can execute
another XQT statement, which, in turn, can execute another XQT
statement, and so on.
• After executing the XQT statement, the run continues execution at the
line following the XQT statement, unless the executed statement
transfers control to a new location (for example, through a GTO, RUN,
or XIT statement).
• An XQT statement terminates the scan of the current line in the run
control report.

7831 9274-000 7-361

XQT (Execute)

Example 1: Reading and Executing a Line from Another Report

Read and execute a line from report number 2 in EDRW$:
@rdl,edrw$,2,<Iine>,099 1-80 <data>s80 .
@xqt <data> .
Example 2: Executing a Line Computed from a Screen Menu
Selection
Determine the line to execute from an input screen:
1. @out,-1,2,10,1,1„„5
2. @chg v1i2 curv$ +3 if v1 ge 3 & le 5 gto lin+1 ; \
gto 001 .
3. &qt,lin v1 .
4. @dsp,-0 .
5. @rel .
6. @srh,-0,,,099 dh 'status date' ,861225 .
7. @srh,-0,,,099 dh 'ship date' ,870614 .
8. @sor,-0 " 'product type' ,1 .
1. Display the menu to the user.
2. Capture, in v1, the user's menu selection based on the vertical cursor
position and adjust it to form the bias to the line that will be executed to
handle this menu selection.
3. Execute the relative line pointed to by CURV$+3.
4. Display the result of the user's selection.
5. Release the display if the user resumes the run.
6. Execute this line if the user presses Transmit from line 1 of the screen.
7. Execute this line if the user presses Transmit from line 2 of the screen.
8. Execute this line if the user presses Transmit from line 3 of the screen.

7-362 7831 9274-000

 XUN (Exit MAPPER System)

XUN (Exit MAPPER System)

'This section does not apply to the OS 1100 MAPPER System or the Personal
Computer MAPPER System.
The Exit MAPPER System (XUN) statement exits the user to the previous
environment.
Format
@XUN .
Comments
• The XUN statement terminates the active run, signs off and terminates
MAPPER software for that station, and exits to the previous
environment.
V • U Series and UNIX: The user receives a UNIX logon prompt if
MAPPER software was executed with the mapper logon. If MAPPER
software was executed from a UNIX shell, a UNIX shell prompt is
displayed.
Example
Terminate the run and MAPPER software at the station and exit to the
previous environment:
@xun .

7831 9274-000 7-363

*cmd (Local Code)

*cmd (Local Code)

'' This section does not apply to the OS 1100 MAPPER System or the Personal
Computer System.
The Local Code (*cmd) statement executes a site-defined run statement. See
Appendix G for more information.
Format
(*cmd .

Following is a description of the call:

Field Description

cmd Run function call of a site-defined local run statement.

Your site is responsible for documenting the name and format of each
site-defined run statement. See your coordinator or the person responsible
for maintaining the MAPPER system software and databases for
information on the site-defined local run statements available for your use.

7-364 7831 9274-000

Glossary

A
A Series data file
A file formatted in such a way that it can be read by an A Series editor, such
as Command and Edit language (CANDE).
abort
To terminate execution of a MAPPER function or run.
abort routine
A subroutine to be executed if a user aborts the run during execution. It can
be an internal or external subroutine. See also external subroutine, internal
subroutine, subroutine.
accesscode
An identification code subordinate to a usercode. An accesscode is used to
further establish a user's identity, control security, and restrict access to
disk files. See also log on.
accounting log
A summary of data containing a record of every transaction compiled while
a run executes. The Log for Analysis (LOG) run statement produces an
entry in the accounting log for each function executed in the run. Synonym
for log list.
active screen
The screen that shows you have signed on. Although the active screen looks
like the sign-on screen, your user-id takes the place of the word Idle, and the
bottom line indicates which cabinet you are accessing. Contrast with sign-on
screen. See also caret, sign on.

7831 9274-000 Glossary-1

Glossary

alphanumeric variable
A variable that contains one or more alphabetic, numeric, and special
characters, such as the tab character. See also variable, variable type.
American Standard Code for Information Interchange (ASCII)
A set of numeric codes that defines a character set. The ASCII character set
used in MAPPER software is called full character set (FCS). See also
character set, full character set.
application
See MAPPER application.
apostrophe
A special character ( ' ) used in run statements to delimit literal data that
contains spaces, slants, or commas. See also run statement.
argument
An item of data passed to a computer program. See also parameter.
arithmetic expression
A single numeric value or a combination of two or more values and one or
more arithmetic operators. See also arithmetic operator.
arithmetic operator
A special character (such as +, -, *, and =) that specifies a mathematical
relationship between two values. See also arithmetic expression, expression.
ASCII
See American Standard Code for Information Interchange.
asterisk line
A line beginning with an asterisk (*) in column 1; it can be used as a
comment line. It is not controlled by the tab positions and input edit codes
of report 0. It has these characteristics: it can be shifted, it can extend to
256 characters, and it can be displayed and processed in different formats.
See also line type.
auxiliary device
A peripheral device connected to a terminal, such as a printer. See also
peripheral device.

Glossary-2 7831 9274-000

 Glossary

B
B20 operating system (BTOS)
The operating system used when running INFOVIEW II applications on
Unisys B20 series systems. See also INFOVIEW II.
background run
A MAPPER run that frees your terminal for other uses while it executes.
basic format
The unshifted columns of a report as defined in report 0 from left to right.
On 80-character screens, the basic format contains the leftmost 80
characters of a report; on 132-character screens, the basic format includes
the leftmost 132 characters of a report.
binary find process
A method of finding an item quickly in a sorted list. Instead of scanning
data line by line, a binary find process samples the data at midpoint and
continues dividing and sampling the data until it finds the target item.
binary synchronous communications (BSC)
A communications protocol for sending data to an IBM host computer.
Boolean logic
A system of logical comparisons named after mathematician George Boole.
Boolean logic uses relational operators to evaluate expressions as true or
false. See also conditional statement, IF/THEN/ELSE statement, relational
expression, relational operator.
branch
To bypass the usual sequence of run statements and jump forward or
backward from the current location in a run. See also conditional branching,
label.
breakpoint
A place in a run, specified by a Run Debug (RDB) command, at which the
run execution is interrupted for debugging purposes.

7831 9274-000 Glossary-3

Glossary

BSC
See binary synchronous communications.
BTOS
See B20 operating system.
BTOS II
The Unisys workstation operating system for the B2x and B3x series
workstations.

C
cabinet
A group of eight drawers (B through I), referred to by number and usually
used by a department. Each user signs on into a specific cabinet, assigned
by the MAPPER system coordinator. Users in a particular department may
have one or more cabinets to work in. See also department, drawer.
cabinet password
See password.
calculator
A feature of MAPPER software used by the Arithmetic (A) function that
allows you to perform calculations. It can be used with a report containing
predefined equations or independently, similar to a pocket calculator.
call
The abbreviation you use to specify a function, run, or run statement. For
example, CAL is the call for the Calculate function.
CANDE
See Command and Edit language.
caret
A special character (^) that releases a displayed report or message, then
displays the MAPPER active screen. See also active screen.

Glossary-4 7831 9274-000

 Glossary

case sensitivity
Pertaining to the differentiation between uppercase and lowercase letters.
When the option that determines case sensitivity is used, an uppercase
letter is treated as a different character than its lowercase letter.
character hierarchy
The relationship of characters to one another. For example, in limited
character set, numeric characters have higher values than alphabetic
characters. In sort or search-in-range processes, alphabetic characters come
before numeric characters.
character set
The characters allowed in the reports in a drawer. See also American
Standard Code for Information Interchange, Fieldata, full character set, full
character set upper, limited character set.
character string
A series or group of connected characters.
chart input report
A report that you fill in with data you want to chart. After you have finished
filling in the chart input report, it is called a completed input report.
See also completed input report.
CMS 1100
See Communications Management System.
COBOL
See Common Business Oriented Language.
column
A character position in a report; for example, the first character position on
the left side of a report is column 1.
column-characters (cc) field
The part of a run statement that specifies which fields in a report are used
by that run statement. For example, column-characters field 15-9 is the
field that starts in column 15 and is nine characters long. Note that field
names may be used in place of the column-characters field of a run
statement. See also field name.

7831 9274-000 Glossary-5

Glossary

column-formatted report
A report having a layout identical to other reports in the same drawer. The
fields are separated by tab characters. Contrast with freeform report.
command
An instruction entered into a report to carry out operations with a function,
such as GOC commands processed by the Generate Organization Chart
(GOC) function, or data control commands used with the Create File (FILE)
function or Create File (FIL) run statement.
Command and Edit language (CANDE)
A message control system (MCS) that prepares and updates files in an
interactive, terminal-oriented environment. See also message control
system.
comment
The part of a run statement that follows the space-period-space sequence
and summarizes what the run statement or subroutine is doing at that point
in the run. It documents the run for later reference.
Common Business Oriented Language (COBOL)
A high-level computer language used mainly in the business environment.
Communications Management System (CMS 1100)
The communications software product that provides the structure for all
communications and network capabilities for OS 1100. CMS 1100 software
allows a site to establish remote connections from an OS 1100 system to
other hosts, terminals, and networks.
Communications Management System (COMS)
A general message control system (MCS) that supports a network of users
and provides them with a consistent online interface to the host system.
See also message control system, online.
communications output printer (COP)
Any type of printing device connected to a terminal.

Glossary-6 7831 9274-000

 Glossary

completed input report

A report that contains data to be charted by a specific color graphics run,
such as PIEG. See also chart input report.
COMS
See Communications Management System.
concatenated variables
Variables that are joined together in a specific sequence. See also variable.
conditional branching
A method of controlling the sequence in which run statements are executed.
At the branching point, a specific factor (such as the value of a variable or
reserved word) determines which statement is executed next. See also
branch.
conditional statement
(1) A statement that sets up a condition to determine the subsequent
functions a run performs. (2) A statement of the Calculate (CAL) run
statement that tests expressions and controls processing of individual
equations, depending on whether a specified condition is true or false. The
four conditional statements are IF:, THEN:, ELSE:, and FIRST:. See also
Boolean logic, IF/THEN/ELSE statement.
console
A display terminal used to execute functions for an operating system.
constant label
A value label that has a predefined value, such as PI. It is used in
mathematical run statements such as the Calculate (CAL) run statement.
See also field label, value label.
control characters
The characters entered in a run control report to control the output area
displayed by the run. They are used to generate four-to-one and five-to-one
output with the Output (OUT) run statement. These characters control the
kind of data that the user enters in fields of the screen presented by the run.
See also five-to-one output, four-to-one output.

7831 9274-000 Glossary-7

Glossary

control line
The top line of the screen containing control positions. See also control
position.
control line procedure
The method of executing a function in which you type the function format on
the control line and transmit. Contrast with menu procedure. See also
control line.
control position
The position on the top line of the screen following the SOE character ( )
after the Line and Roll fields. See also control line.
coordinator
See MAPPER system coordinator.
COP
See communications output printer.
counter
A tally number, generated by a run, that records the number of times an
event occurs. It is commonly used to escape a loop after a certain value is
reached.
cumulation
The process of adding a quantity to a total and saving the new total in
another field, repeated a number of times. For example, the Totalize (TOT)
run statement can be used to cumulate a field. See also subcumulation.
current position
The point on the screen from which your next command originates when
using graphics primitive code and expanded syntax commands. See also
expanded syntax commands, graphics primitive code.

Glossary-8 7831 9274-000

 Glossary

current result
The most recent result, called -0 (minus zero), when using run statements.
See also renamed result, result, temporary result.
cursor
The character ( 1) on the screen that can be moved anywhere to show where
to enter data. The cursor shows your current location on the screen.

D
data line
Any report line below the heading divider line. See also line type.
data name
The name of a cabinet, drawer, or report that has been defined by using the
NAME run. This name is stored in the system directory. See also system
directory.
Data Transfer Module (DTM)
A software package that provides a fast, flexible method of transferring data
between applications on OS 1100 computers.
data unit
A unit of related information consisting of a tab line and the following lines
up to the next tab line. A data unit can start with other line types when
using the Search function or run statement with the U option. See also
paragraph.
database
The cabinets, drawers, and reports maintained in files by the MAPPER
system.
date format
A format that defines how a date is to be displayed. For example,
DD MMM YY displays a date as 06 JUN 90.

7831 9274-000 Glossary-9

Glossary

date input specification

The code to specify the format of a date to process.
date line
The first line (line 1) of each report, showing the date and time of the last
update, report number, report creation date, and user-id of the last person to
update the report. The date line is a period line and is counted as one of the
heading lines. Synonym for line 1.
date output specification
The code used to represent the format of a result date.
DDP
See distributed data processing.
debug
To test a run and solve errors in the run statements or in the logic of the
run.
decode
To translate an encoded report into a readable report, using the Decode
Report (DCR) run statement. See also encode.
decrement
To decrease the value of a variable by an integer amount.
default
A preset value or condition that the system uses whenever you do not choose
a specific selection.
default MAPPER site
The MAPPER site installed first on a host computer. See also site.
delimiter
A character placed on each side of a character string to indicate the
beginning and ending of the character string. The delimiter can be any
character other than those in the character string.

Glossary-10 7831 9274-000

 Glossary

demand program
A program executed in demand mode, which processes data as quickly as it
becomes available or ready.
demonstration database
The reports, usually in cabinet 0, in which you can practice manual
functions and run statements.
department
A group of MAPPER system users specified by a number. You specify your
department number when you sign on to the MAPPER system. See also user
registration.
device
See peripheral device.
disk pack
A disk that consists of multiple platters stacked vertically on a central
spindle. Data on a disk pack are accessed by movable read/write heads.
Some disk packs are removable. Synonym for pack. See also pack family.
display
(1) The terminal screen you look at while using MAPPER software. (2) To
present data on the screen.
distributed data processing (DDP)
A network consisting of two or more computers at different locations. These
computers are connected by data communications and are capable of
interfacing with each other to perform a job, task, or application.
distributed MAPPER application
An application that uses runs or data residing on more than one MAPPER
system. See also MAPPER application.
downline load
To copy a file or other information from a computer system to your own
terminal.

7831 9274-000 Glossary-11

Glossary

drawer
A group of reports in a cabinet. All reports within a drawer have the same
headings and line length. Each drawer of a cabinet is identified by a letter
from B to I. Drawer A is accessible to all cabinets in a MAPPER system.
See also cabinet, freeform drawer, report 0.
drawer letter
A letter (A through I) used to identify a drawer in a cabinet. See also
cabinet, drawer.
drawer number
The octal number that identifies the drawer and cabinet within the system.
Each drawer has a unique number, such as 0010 for drawer E in cabinet 0.
See also cabinet, drawer.
drawer password
See password.
DTM
See Data Transfer Module.

E
ECL
See Executive Control Language.
edit function
A function, such as SOE Update and Add Line, used to alter report lines.
empty report
A report that contains headings but no data.
encode
To transform a report into code using the Encode Report (ECR) run
statement, making it unreadable unless the correct key is specified. See also
decode.

Glossary-12 7831 9274-000

 Glossary

end report line

The last line of a displayed report or result.
equation
Two arithmetic expressions separated by an equal sign (=).
equation operator
See operator.
equation set
The function mask and equations used with the Iterative Calculate (ICAL)
run. See also function mask.
error message
See system message.
error routine
A subroutine to be executed if a run encounters an error. It can be an
internal or external subroutine. See also external subroutine, internal
subroutine, subroutine.
Exec
See Executive system.
execute
To process a particular instruction or task. Manual functions, runs, and run
statements can be executed.
Executive Control Language (ECL)
The computer language used to communicate with the Executive system
(Exec). See also Executive system.
Executive system (Exec)
A program that controls the execution of other routines. As the operating
system, the Exec is the principal interface between the user and the system
as a whole. See also Executive Control Language.

7831 9274-000 Glossary-13

Glossary

expanded syntax commands

A set of graphics commands translated by the Graphics Scaler (GS) function
or run statement into graphics primitive code to create charts or modify
existing charts. See also graphics primitive code.
exponential notation
The use of symbols to indicate the number of places to move the decimal.
For example, 12000 in exponential notation is 12E3.
expression
A series of one or more field labels, values, or operators that produces a
single arithmetic or logical value. For example, in the Calculate (CAL)
function, an expression is the sequence of field labels and arithmetic
operators (+,-,*, or /) that completes an equation. See also arithmetic
expression, relational expression, relational operator.
external subroutine
A subroutine in another run control report to which your run temporarily
transfers control. Contrast with internal subroutine. See also abort routine,
error routine, subroutine.

F
fast access
A form of function or run requests that allows you to bypass the function
forms or menus. See also function form, menu.
FCS
See full character set.
FCSU
See full character set upper.

Glossary-14 7831 9274-000

 Glossary

field
(1) A series of one or more columns of a report that are defined as an entity,
such as a status code or a shipping date. (2) A selection from a menu or a
position in a system message where data is entered (for example, the
Report field in a function form). (3) A defined part of a run statement
format. Fields are separated from one another by a space. See also subfield.
field headings
The column headings for report fields. These titles appear above each field
at the beginning of a report, immediately preceding the heading divider line.
Synonym for headings. See also heading divider line.
field label
A single alphabetic character that identifies a single field or several fields
for equations in mathematical functions or run statements. See also
constant label, value label.
field name
A name that identifies a field of a report. The name is derived either from
the two heading lines preceding the heading divider line of the report or
from report 0 if the entire drawer is being processed. See also heading
divider line, report 0.
Fieldata
A set of codes that define a character set. The Fieldata character set used in
MAPPER software is called limited character set (LCS). Contrast with
American Standard Code for Information Interchange, full character set.
See also character set, limited character set.
five-to-one output
Screen output produced by lines in a run that use control characters and
emphasis characters to control special editing and presentation effects. Five
lines in the run are used to define one line of output. Five-to-one output is
used with color displays; four-to-one output is used with monochrome
displays. See also control characters, four-to-one output.

7831 9274-000 Glossary-15

Glossary

flowchart
A diagram of procedures, subroutines, and branches used to plan a run.
form
A report containing screen control commands. See also screen control
commands.
format
(1) One of many variations of a report within a drawer (for example, basic
format, format 1, format 2, and so on), each of which displays a different
selection of columns of data in the report. The formats are defined in the
report 0 of that drawer. (2) The specific fields and subfields used in run
statements, which vary from one statement to another. See also report 0.
format lines
The lines in report 0 of a drawer that specify the report columns displayed
in many different report formats. See also drawer, format, report 0.
format sensitive
Pertaining to a run that processes a displayed report in a specific format.
The run must be registered as format sensitive. See also format.
four-to-one output
Screen output produced by lines in a run that use control characters and
emphasis characters for special editing and presentation effects. Four lines
in the run are used to define one line of output. Four-to-one output is used
with monochrome displays; five-to-one output is used with color displays.
See also control characters, five-to-one output.
freeform drawer
A drawer used for freeform reports. Drawer A is a freeform drawer
accessible from all cabinets in the system. See also drawer, freeform report.

Glossary-16 7831 9274-000

 Glossary

freeform report
A report without a columnar structure determined by the report 0 of its
drawer. You can use freeform reports for memos, bulletins, run control
reports, or informal columnar reports. Contrast with column-formatted
report. See also report 0.
full character set (FCS)
The character set that allows uppercase and lowercase letters, stored
internally as ASCII characters. Contrast with Fieldata, limited character
set. See also American Standard Code for Information Interchange,
character set, full character set upper.
full character set upper (FCSU)
The set of ASCII codes in uppercase only. See also American Standard Code
for Information Interchange, character set, full character set.
function
An operation you perform on one or more reports or on a result. Examples
of functions are Match (MA), Search (S), or Sort.
function bar
An information bar at the bottom of the MAPPER active screen. The ten
key names correspond to the Fl to F10 function keys. See also function keys.
function call
See manual function call, run function call.
function form
A screen, resembling a menu, that contains fields in which you supply
information needed to perform a manual function. See also fast access,
menu.

7831 9274-000 Glossary-17

Glossary

function keys
The set of keys on your terminal keyboard (for example, Fl or F2)
programmed to perform operations when you press them. See also function
bar.
function mask
A screen of field headings for a report; you enter options above the field
headings and parameters below the headings as instructions for a manual
function. See also parameter.

G
granularity
A measurement used when allocating storage space to a mass storage file.
For example, the Element (ELT) statement assigns a file with a maximum
granularity of 262,143 tracks. See also mass storage file.
graphics primitive code
A set of commands that allows the MAPPER system to display charts on
different types of output devices. You can design your own graphics by
entering graphics primitive code in a freeform report. Graphics primitive
code can be stored in MAPPER reports. See also expanded syntax
commands, packed graphics primitive code, unpacked graphics primitive
code.

H
heading divider line
The line beginning with an asterisk and made up of equal signs and periods
that separates the field headings from the data; counted as one of the
heading lines. Many functions rely on the heading divider line to determine
where field headings end and data begins. See also field headings, field
name, heading lines.

Glossary-18 7831 9274-000

 Glossary

heading lines
The lines including and following the date line that show the drawer letter
and report number, the names of fields, and the heading divider line.
Synonym for report headings.
headings
Synonymous with field headings.
HELP run
A MAPPER run that supplies online information about functions, run
statements, system messages, and other MAPPER operations. See also
online, run target.
Hollerith variable
A variable that can hold alphabetic, numeric, or special characters. See also
variable, variable type.
home position
The upper left corner of the screen.
horizontal operation
A computation performed in one or more fields across each data line in a
report. See also vertical operation.
HOST1100 run
A run residing on the host OS 1100 MAPPER System that controls data
transfer between the OS 1100 MAPPER System and the U Series MAPPER
System. See also INSTALL1100 run.
host computer
The computer that holds the database and software of a particular MAPPER
site. See also site configuration.

7831 9274-000 Glossary-19

Glossary

I
I/O
See input/output.
I/O request
A request for input from or output to system storage. Synonym for I/0.
IF/IHEN/ELSE statement
A conditional statement that controls further processing based on the value
of the expression in the IF: statement. If that expression is true, the
expression in the THEN: statement is processed. If the expression is false,
then the ELSE: expression is processed. See also Boolean logic, conditional
statement.
increment
To increase the numeric value of a variable by an integer amount.
INFOVIEW II
A sophisticated and flexible software tool that allows a workstation to
interface to a host computer. Your PC or B20 workstation uses
INFOVIEW II to access the A Series MAPPER System. See also B20
operating system.
initialize
To assign a type, size, and initial value to a variable. See also variable.
input edit code
A numeric code (0 through 9) in report 0 of each drawer specifying what
kind of data is allowed in each character position of the report. The person
designing the drawer enters the input edit codes on the input edit line of the
experimental report. See also report 0.
input/output (I/0)
(1) Information coming from or going to system storage. (2) An operation in
which the system reads data from or writes data to a peripheral device such
as a disk drive.

Glossary-20 7831 9274-000

 Glossary

input parameters
The variables, literal data, reserved words, or any combination of these, to
be processed in a MAPPER run. See also literal representation, reserved
word, variable.
INSTALL1100 run
A run provided with the U Series MAPPER System that sends the complete
HOST1100 run to the OS 1100 MAPPER System and replaces the
temporary HOST1100 reception run. See also HOST1100 run.
integer
A whole number with no fraction or decimal part. For example, the
numbers 1 and 2.
integer variable
A variable that contains integer numbers. See also integer, variable.
interactive
Pertaining to a process that can take place during another process.
interim display
Information displayed on the screen for a given length of time; the run then
continues automatically.
internal subroutine
A subroutine within your run control report to which your run temporarily
transfers control. Contrast with external subroutine. See also abort routine,
error routine, subroutine.
issuing report
The report from which data is taken when using a run statement that
processes two reports, such as the Append Report (ADD) or Match (MCH)
run statements. Contrast with receiving report.

7831 9274-000 Glossary-21

Glossary

J
JDOE database
See demonstration database.
job
A group of one or more tasks, usually processed from and under the control
of a single program. A job is assigned a number by the system and treated
as a discrete unit of work by the computer.
justify
To position data within a field, variable, or report. For example, if data in a
field is left-justified, it begins in the leftmost column of that field.

K
Kanji characters
A character set used by several Asian languages, including Japanese and
Chinese.
known trailing substring
A substring in which you specify the starting character position and use the
remaining characters in the field. For example, V1(2-0) specifies the
substring beginning with the second character through the end of Vl.
Contrast with unknown trailing substring. See also substring.

L
label
(1) A number, preceded by an at sign (@) and followed by a colon ( : ), used to
identify a run statement line. Labels organize sections within a run,
allowing branching. (2) A name for a data value in an arithmetic expression.
See also branch, label table definition lines.
label table definition lines
The lines at the beginning of a run that indicate the location of each label in
the run. See also label.

Glossary-22 7831 9274-000

 Glossary

LCS
See limited character set.
limited character set (LCS)
The character set that allows uppercase letters only, stored internally as
Fieldata characters. Contrast with American Standard Code for Information
Interchange, full character set. See also character set, Fieldata.
line 0
The first line of a report, never visible on the screen, containing system
information about the report: the drawer letter, report number, write
password, read password, number of heading lines, language of the report,
and number of lines of the report. This information is stored with the report
and can be displayed with the Line Zero (12) function or LZR run statement.
line 1
Synonymous with date line.
line type
A type of data line in the MAPPER database, specified by a line type
designator in column 1. See also data line, line type designator.
line type designator
A character in column 1 of a report line that specifies the line type. There
are four designators, indicating four line types: tab (0) — column-formatted,
edited line (0 represents a tab character); asterisk (*) — column-formatted,
nonedited line; period ( . ) — comment, nonedited line; and special (any valid
character) — column-formatted edited line (may not start with a tab
character, asterisk, or period). See also line type.
literal representation
The explicit and actual value of an item; information is interpreted exactly
as it appears. For example, the literal representation of variable V11 is the
characters V11, not the value that the variable holds.
LLP
See logic lines processed.

7831 9274-000 Glossary-23

Glossary

load
To initialize a variable with a value.
log list
Synonymous with accounting log.
log on
To access the A Series system by entering information that identifies you to
the system. This data includes a valid usercode, password, and accesscode.
Note that this is not the same as sign on, which is a procedure used to access
the MAPPER system. See also accesscode, usercode.
logic lines processed (LLP)
The lines in a run control report processed during run execution. Each scan
of a line counts as one LLP. See also run control report.
logic scan
The processing of each run statement line by the MAPPER system during
execution of a run. See also run statement line.
logo
See active screen, sign-on screen.
loop
A sequence of run statements that execute repeatedly until a specified
condition is met.

M
manual function
A MAPPER software command, such as Search (S) or Totalize (TOT).
manual function call
The abbreviation used to request a function (for example, LOC for the
Locate function).

Glossary-24 7831 9274-000

 Glossary

MAPER files
OS 1100 mass storage files that make up the system database.
MAPPER application
A set of related tasks accomplished by one or more runs and the database
processed, for example, an inventory system. See also distributed MAPPER
application.
MAPPER calculator
See calculator.
MAPPER format
The arrangement of data in a native system file that has a fixed line length
and contains a transparent line 0, line numbers, and end-of-line control
characters. The last line is the visible end report line.
MAPPER site
See site.
MAPPER software
The multiactivity real-time program that creates an end-user environment
for file management and report generation. See also MAPPER system.
MAPPER system
A file management system that allows the user to maintain and manipulate
a large amount of data in a report-structured database.
MAPPER system coordinator
The person who manages the database of the MAPPER system. This person
configures the system, registers new users and new or updated runs, and
coordinates the system user group.
MAPPER system logo
See active screen, sign-on screen.
MAPPER system operator
The person responsible for daily operations including mounting recovery
tapes, performing the purge and cycle/merge processes, starting the
MAPPER system, and executing the PREMAP or PRESTR runstreams. The
system operator's responsibilities are specifically defined at each site.

7831 9274-000 Glossary-25

Glossary

MARC
See Menu-Assisted Resource Control.
mass storage
Peripheral devices that can store large amounts of data. See also peripheral
device.
mass storage file
A file used as a secondary storage device that provides current report
information on a specific program segment.
MCS
See message control system.
menu
A list of items on a screen from which one item can be selected, either by
tabbing to the selection and transmitting, or by typing in a letter, number,
or character string, and then transmitting. See also fast access.
Menu-Assisted Resource Control (MARC)
A menu-driven interface and transaction processor for users and operators
of Unisys A Series systems.
menu procedure
The method of executing a function in which you select the function from a
menu. Contrast with control line procedure. See also menu.
message control system (MCS)
A program that controls the flow of messages between workstations,
application programs, and the operating system. See also Command and
Edit language, Communications Management System.
message wait signal
A signal indicating that your workstation has a incoming message. When a
message wait signal occurs, MSG is displayed at the upper right corner of
the screen and the terminal beeper sounds. You press the Message key to
display the incoming message.
multiple field label
A label that identifies more than one report field when using mathematical
functions or run statements. Contrast with single field label.

Glossary-26 7831 9274-000

 Glossary

N
named report
A report that has been named using the NAME run. For example,
report 6B0 could have a name of Inventory.
named variable
A variable that is designated by a name rather than by a number. Greater
than and less than characters are placed before and after the name, for
example, <sum>. Contrast with numbered variable. See also variable.
nested statement
A run statement contained within another run statement. See also run
statement.
nested subroutine
An internal subroutine referenced by another subroutine. Note that
external subroutines cannot be nested. See also external subroutine,
internal subroutine, subroutine.
NEWUSER database
See demonstration database.
nontab line
Synonomous with special line.
null
A blank character (not 0 and not a space) used to fill data lines.
numbered variable
A variable that is designated by the letter V followed by a number; for
example, vl. Contrast with named variable. See also variable.

0
object code file
The executable code produced by a compiler.

7831 9274-000 Glossary-27

Glossary

online
Pertaining to the availability of a process or operation while another is in
progress. For example, while using the Sort function, you may access online
HELP.
operating system (OS)
A collection of computer programs that control the operation of a computer
and peripherals.
operator
(1) A MAPPER system operator. (2) A symbol that specifies a calculation or
comparison to be performed in a function such as Calculate (CAL). See also
arithmetic operator, relational operator.
operator display terminal (ODT)
The system console device that allows the operator to enter commands
directly to the operating system to perform various functions.
option
A selection that you can make for special operation of a manual function or
run statement. If no option is used, the default operation occurs.
organization chart
A chart created with the Generate Organization Chart (GOC) function or
run statement that shows how a company or other organization is
structured.
OS 1100
See Executive system, operating system.
output area
A scratchpad or storage area used in a run that temporarily stores data
collected during run execution. See also output lines.
output lines
The lines in a run control report that do not start with at signs (@) or
colons ( : ). Output lines are placed in the output area and can be displayed
when the run terminates. They can also be placed in a result by using the
Break (BRK) or Break Graphics (BRG) statement and can be displayed or
processed at any time during the run. See also output area, result.

Glossary-28 7831 9274-000

 Glossary

P
pack
To eliminate leading and trailing spaces from a value held by a variable. See
also disk pack, pack family.
pack family
A disk or a collection of disk packs on which physical files are stored. It is
given a name of up to 17 alphanumeric characters assigned during
installation and is generally designated for specific applications and users.
See also disk pack.
packed graphics primitive code
One format for graphics primitive code in a result or report. In this format,
the commands are strung together, not separated by spaces or other
characters. Contrast with unpacked graphics primitive code. See also
graphics primitive code.
packed variable
A variable in which the leading and trailing spaces have been deleted.
See also variable.
paragraph
A group of data lines starting at either the type of line you are processing or
the type of line specified with the Search U option. This includes
subsequent lines up to, but not including, the next occurrence of the type of
line processed or specified. See also data unit, line type.
parameter
An item of information supplied to a run statement to indicate specific
values or fields to process. See also argument.
password
A character string used as a security feature to prevent unauthorized access
to information on the MAPPER system. There are five kinds of passwords:
the sign-on password restricts access to the MAPPER system; the write
password restricts updates to reports; the read password restricts users
from reading a report; the drawer password restricts access to specific
drawers within a cabinet; and the cabinet password restricts access to a
specific cabinet. See also user registration.

7831 9274-000 Glossary-29

Glossary

path
The logical course or line of direction taken by the system in the execution of
a run or part of a run.
path name
The complete UNIX file identifier, including all directories, subdirectories,
and the file name.
period line
A line beginning with a period in column 1; it can be used as a comment line.
It is not controlled by the tab positions and input edit codes of report 0. It
cannot be shifted, it is limited to the screen display size, and it cannot be
displayed or processed in different formats. See also line type, save flag.
peripheral device
Any data communications or input device attached to a terminal or host
computer. For example, an AUX printer is a peripheral device attached to a
terminal; a modem is a peripheral device attached to the host computer. See
also auxiliary device.
predefined lines
The lines in report 0 that contain tab positions, preset data, or reserved
words. Each report 0 can have multiple predefined lines for which you can
specify data or values that automatically appear when a new line is added to
a report. These are data lines that have certain fields already filled in for
permanent unchanged data and other fields left blank for entering
changeable data. See also data line, report 0.
primitive graphics code
See graphics primitive code.
protected field
An area of a display terminal screen from which no input is accepted; the
user cannot place the cursor within the area. Protected fields are defined by
control characters using the Output (OUT) run statement. See also control
characters.

Glossary-30 7831 9274-000

 Glossary

Q
queue
To send output to an auxiliary device. For example, a report can be queued
to a printer. See also requeue.

R
read password
See password.
receiving label
A name or alphabetic field label into which the result of a MAPPER
operation is stored. For example, a generated count of records in a report
could be assigned to the COUNT receiving label.
receiving report
The report to which data is sent when using a manual function or run
statement that processes two reports, such as the Append Report (ADD) or
Match (MCH) run statements. Contrast with issuing report.
receiving variable
The first variable in an equation and the variable that contains the result of
a calculation.
registration
A procedure done by the MAPPER system coordinator to add new users or
runs to the system.
relational expression
A sequence of operands and relational operators used to compare values or
character strings. When evaluated, it produces a value of 1 if the
comparison is true or 0 if the comparison is false. See also Boolean logic,
expression, relational operator.

7831 9274-000 Glossary-31

Glossary

relational operator
A special character used to compare values, such as =, >, <=, >=, or <>
(equal to, greater than, less than, less than or equal to, greater than or equal
to, and not equal to). See also Boolean logic, expression, relational
expression.
relative line number
A line number specified by indicating the number of lines following or
preceding the current line in a run control report. See also run control
report.
remote file
A data communications file associated with any remote device attached to
the system by way of a network communications processor. An object
program that receives data from one or more remote devices and sends data
to those devices regards the devices as a remote file.
remote run
A run that starts a run on another MAPPER system.
renamed result
A temporary result made by using the Rename (RNM) run statement to
rename the current result (-0); for example, result -0 can be renamed to -1.
These results are lost when the run ends or the terminal is released.
See also current result, result, temporary result.
replacement string
A string of characters with which to replace the target string. See also target
string.
report
The set of data that you work with in the MAPPER system. Reports are
identified either by a unique report number or by a meaningful name you
have given the report using the NAME run. See also report name.

Glossary-32 7831 9274-000

 Glossary

report headings
Synonymous with heading lines.
report identifier (RID)
A specific report identified by a unique report number and drawer letter.
For example, RID 2B refers to report 2 in drawer B.
report name
The characters used to refer to a report: either the report number and
drawer letter or a meaningful name you have given the report using the
NAME run. See also report.
report 0
A report that resides in each drawer in the MAPPER system. It serves as a
template for the reports in its drawer when the Add Report function or run
statement is used. See also drawer, format, function mask.
requeue
To send output already queued to an auxiliary device that failed to print the
first time. See also queue.
reserved word
A character string reserved for specific use. The system supplies the
information stored in the reserved word. For example, DATE1$ is a
reserved word that supplies the current date in the format YYMMDD.
restricted access function
A function requiring special permission from the MAPPER system
coordinator before it can be used. Applies to functions that require
advanced knowledge of MAPPER software or the operating system.
result
A temporary copy of data obtained by executing a manual function or run. It
is held in scratch storage until released, duplicated, or replaced into a
permanent report. See also current result, renamed result, temporary
result.

7831 9274-000 Glossary-33

Glossary

resume
To continue a function or run that was halted by a display. Press Resume
to resume an operation.
retrieve
To bring a MAPPER report that has been filed into a native file back into
the MAPPER database.
reverse slant
A special character ( \ ) used to indicate that a run statement continues on
the next line.
reverse video
Pertaining to highlighting on a screen where the background and character
colors are reversed.
RID
See report identifier.
roll
To move vertically through the data in a report; to move a report forward or
backward on the screen.
run
A series of instructions (run statements) stored in a run control report that
the MAPPER system interprets to produce a report or perform other tasks,
such as updating reports. See also run control report, run statement.
run call
Synonymous with run name.
run control report
A MAPPER report containing sequential run statements of step-by-step
instructions for processing reports, results, or other data. See also run, run
statement.

Glossary-34 7831 9274-000

 Glossary

run function call

An abbreviation used to request a function in a run statement (for example,
SRH for Search). See also run statement.
run name
A name assigned to a run; used to access the run and execute it (for
example, HELP). Synonym for run call.
run registration
The process used by the MAPPER system coordinator to authorize and
enable a run. The coordinator specifies in the run registration report the
run name, the location of the run control report, and the person responsible
for the run. See also run control report, run name.
run statement
A string composed of a run function call, options, fields, and subfields used
to format an instruction that can be processed in a run. When the run
statement is entered into a run control report, it can be processed to direct
execution of MAPPER functions and other operations. See also run, run
control report, run function call.
run statement format
See format.
run statement line
A line that contains one or more run statements, beginning with an at sign
(@) and ending with a period. See also run statement.
run target
An item in a list of topics in the HELP run menu for run design. See also
HELP run.

7831 9274-000 Glossary-35

Glossary

S
save flag
A date you place on line 2 starting at column 2 of a MAPPER report to
prevent the report from being deleted before or on the date specified. Line 2
must be a period line in order to contain a save flag. Use the format
@YYMMDD. See also period line.
screen control commands
A set of commands, used with the Screen Control (SC) statement, that
perform basic screen operations, which include positioning the cursor,
clearing the screen, defining fields, and defining screen attributes. These
screen commands can also be used to design reports that define fields, box
data in a specified area, and map function keys. See also form.
search information lines
The lines displayed at the top of a result, showing how many lines were
found by the search, the total number of lines searched, and the search
parameters.
semicolon
(1) A special character ( ; ) used in run statements as field delimiters. (2) A
special character used in Arithmetic (ART) and Calculate (CAL) statements
to separate expressions. (3) A special character used in IF: statements to
control more than one decision on the same line.
sign off
To terminate MAPPER software at your terminal. The sign-on screen
appears on the screen. Contrast with sign on. See also sign-on screen.
sign on
To initiate MAPPER software at your terminal by entering data that
identifies you to the system. This data includes your user-id, department
number, and password (if applicable). The active screen appears on your
screen. Contrast with sign off. See also active screen.

Glossary-36 7831 9274-000

 Glossary

sign-on cabinet
The cabinet a user enters automatically when signing on to the MAPPER
system and in which the user primarily works. It is set by the MAPPER
system coordinator as part of user registration. See also user registration.
sign-on password
See password.
sign-on screen
The screen you see before signing on to the MAPPER system. It shows your
system name, your station number, and the level of MAPPER software. The
word Idle in your sign-on screen shows your station is inactive. Contrast
with active screen. See also sign off.
single field label
A label that identifies one report field when using equations in
mathematical functions and run statements. Contrast with multiple field
label.
site
MAPPER software can support multiple databases referred to as sites. See
also default MAPPER site.
site configuration
The devices (terminals, printers, or other MAPPER systems) connected to
the host computer. See also host computer.
site letter
An alphabetic designator assigned to each MAPPER system.
slant
A special character ( / ) used to separate multiple parameters in a run
statement.
SOE
See start-of-entry character.

7831 9274-000 Glossary-37

Glossary

special characters
The set of characters (such as I and *) on your keyboard that are not
alphabetic or numeric characters.
special line
A line starting with any character except tab, asterisk, or period. It acts as a
tab line although an alphabetic or numeric character appears in column 1.
Synonym for nontab line. See also line type, line type designator, tab line.
stack
A data structure that stores variables on a last-in/first-out basis. As data is
added, the stack moves down, with the last item added taking the top
position. You can save (PSH), restore (PEK), restore and remove (POP),
replace (POK), remove (RMV), and exchange (XCH) items from the stack.
start-of-entry (SOE) character
The character represented on the screen by this symbol: •. It is used with
the SOE Update function and other edit functions. See also edit function.
statement
See run statement.
station
A terminal, workstation, or PC on the MAPPER system.
station number
The unique identifier for your terminal on the MAPPER system.
station sign-on screen
See sign-on screen.
string
See character string.
string variable
A variable that can contain up to 256 alphabetic, numeric, and special
characters. See also variable, variable type.

Glossary-38 7831 9274-000

 Glossary

subcumulation
To cumulate using the Totalize (TOT) run statement until a key field value
changes so that the result yields two result fields. See also cumulation.
subfield
A part of a run statement field. For example, i t yp is a subfield of the
I t yp,p field. Subfields are separated by a comma. See also field.
subroutine
A subset of a run that contains run statements performing a specific task
within the run. See also abort routine, error routine, external subroutine,
internal subroutine.
substring
A subset of characters within a character string. See also character string.
subtotal
A sum of data for groups of related lines.
system coordinator
See MAPPER system coordinator.
system directory
Reports that contain data names for cabinets, drawers, and reports. These
are updated using the NAME run when adding, changing, or deleting a data
name. See also data name.
system message
A message the MAPPER system displays on the top line of the screen to
alert you to a possible or actual problem.
system logo
See active screen, sign-on screen.

7831 9274-000 Glossary-39

Glossary

T
tab
To move the cursor from one tab character position to another.
tab character
(1) A special character in MAPPER reports indicating a tab position on the
screen. In this manual, a tab character on the screen is usually represented
by a vertical bar ( I ) or center dot (•) but may be configured for your
terminal as another character. (2) A special character used to specify tab
lines. In this manual, a tab character is represented by a quadrate (Q.
tab line
A line beginning with a tab character, usually a data line. It is controlled by
the tab positions and input edit codes of report 0 and can extend up to 256
characters. See also input edit code, line type, line type designator, report 0.
target list
(1) A list of function calls in the HELP run. (2) A list of target words in an
issuing report or list of words specified when you execute a function. The
Word Locate (WL) and Word Change (WC) functions and run statements
use target lists. See also HELP run, issuing report.
target string
The character string to be located or changed by a MAPPER function or run
statement. See also character string, replacement string.
temporary result
A result created by a MAPPER function and given a new name using the
Rename (RNM) run statement. The current result (-0) is renamed to -1, -2,
and so on. A temporary result is released when the run ends. See also
current result, renamed result, result.
time format
A format that defines how a time is to be displayed; for example, HHMMSS
displays a time as 121500.

Glossary-40 7831 9274-000

 Glossary

time input specifications

The codes used to define the format of a time to process.
time output specifications
The codes used to define the output format of a time.
TIP
See Transaction Processing.
toggle
To switch between two modes of operation using the same key. For
example, pressing the key activates one mode; pressing the key again
returns to the original mode.
trailer line
A line automatically attached to a data line when certain functions or run
statements, such as the Totalize (TOT) function, are used. Asterisk and
period type lines are trailer lines to tab lines. See also asterisk line, line
type, period line, tab line.
Transaction Processing (TIP)
A part of the Executive system (Exec) used for real-time transaction
processing.
transmit
To type information and press the Transmit key, sending the information
to the host computer.
transparent character
A character that occupies a position in a string. When the string is
compared to another character string, the transparent character allows all
characters in that position to be accepted. For example, the $ in the
character string A$C allows ABC and Al C to be accepted. See also character
string.
truncate
To cut off or shorten; to exclude. For example, when using the Add On
(ADON) function to add a report that has lines longer than those of the
receiving report, the new lines are truncated.

7831 9274-000 Glossary-41

Glossary

U
Universal Terminal System (UTS)
A family of terminals and related hardware, for example, UTS 400.
UNIX
The operating system for the host computer that supports the U Series
MAPPER System.
unknown trailing substring
A substring in which you specify the number of ending characters to use,
regardless of the specific starting character position. For example, V1(0-2)
specifies the last two characters of Vl. Contrast with known trailing
substring. See also substring.
unpacked graphics primitive code
One format for graphics primitive code in a result or report. In this format,
each command is on a separate line. Contrast with packed graphics
primitive code. See also graphics primitive code.
update control
The ability of MAPPER software to guarantee that only one user at a time
may be updating a given report.
update password
See password.
update result
A result that can be used to replace or delete lines in the original report
from which it was produced. See also result.
user input
Any information you are instructed to type. In this manual it is shown in
color and in lowercase letters.

Glossary-42 7831 9274-000

 Glossary

user registration
The process by which the MAPPER system coordinator enters into the user
registration report a user-id, sign-on password, sign-on department number,
sign-on language, and sign-on cabinet for each user. See also department,
password, sign-on cabinet, user-id.
user-id
A unique code assigned to each MAPPER software user for security reasons.
User-ids are set up by the MAPPER system coordinator to allow access to
certain functions and runs. See also user registration.
usercode
An identification code used to establish user identity on the A Series system,
control security, and provide for segregation of files. See also log on.
UTS
See Universal Terminal System.

V
value label
A name of up to six characters that identifies a single numeric or text value
in mathematical functions or run statements. See also constant label, field
label.
variable
A labeled entity (for example, V11 or <finds>) that can assume different
values. Values can be assigned by the user or by MAPPER software.
See also variable type.
variable table
A table created at the end of a run control report displaying the location of
all variables in your run control report. You create a variable table with the
Build Variable Table (BVT) run. See also run control report.

7831 9274-000 Glossary-43

Glossary

variable type
One of five types of variables. Each variable type specifies the kind of data
the variable may hold. See also alphanumeric variable, Hollerith variable,
integer variable, string variable, variable.
vertical bar
A special character ( I ) that represents a tab character in MAPPER reports.
On some terminals, the tab character appears as a space. See also tab
character.
vertical operation
A summary calculation (for example, sum or average) performed on a single
field across all data lines. See also horizontal operation.
vertical operator
A special character (such as + or /) that identifies the type of arithmetic
operation to be performed on all values in a specified field.
vertical summation
The process of adding fields of data in a report and listing the totals at the
end of the result. It is used with the Totalize (TOT) run statement.

w
WFL
See work flow language.
word processing
A group of functions that process text to create documents, memos, and
other kinds of reports containing textual data.
work flow language (WFL)
(1) A language used for constructing jobs that compile and run programs.
WFL includes variables, expressions, and flow-of-control statements that
offer the programmer a wide range of capabilities with regard to task
control. (2) A language used to write jobs that control the flow of programs
and tasks on the operating system.
write password
See password.

Glossary-44 7831 9274-000

Index

A arithmetic
and trigonometric functions, 7-27,
A Series file 7-52
creating, 7-125 computations (See calculations),
retrieving, 7-261 7-23
A Series programs, executing, 7-28 expressions, formulating, 7-24
A Series Run (ASR) statement, 7-28 operations, priority of, 7-24, 7-50
abort routines, registering, 7-235 operators, 7-24
Acknowledge Message (OK) statement, using CHG, 7-69
7-205 Arithmetic (ART) statement, 4-15,
ADD (Append Report) statement (See 7-23
HELP,@ADD in the online array
help system) definition, 4-2
ADR (Add Report) statement (See handling, 7-166
HELP,@ADR in the online help passing, 4-24
system) ART (Arithmetic) statement, 4-15,
analysis, run 7-23
by the MAPPER system coordinator, ASCII, list of characters, D-2
6-3 ASR (A Series Run) statement, 7-28
guidelines for, 6-14 assistance, obtaining, 5-2
using RUNA run for, 5-19 asterisk line, C-2
AND operation, 7-51 ATT command (SC), 7-291
apostrophe ( ' ), use of in run attribute
statements, 2-16 commands, field, 7-290
Application Power Tools (APT), 5-6, parameters, 7-304
5-8 using inline, 7-306
applications AUX (Auxiliary) statement, 7-31
developing source-protected, F-1 auxiliary devices, 7-31
interfacing other, 7-18 averages (See calculations)
AREA command (SC), 7-300 AXDRW$, 7-235, 7-258

7831 9274-000 Index-1

Index

B BRK (Break) statement, 7-44

buffer, temporary
Background Run (BR) statement (See
BVT run, 4-19
BR statement)
background runs, 7-40, 7-324
background runs on OS 1100, 7-42 C
backslash (See reverse slant)
BAT run, 5-6 CAB (Cabinet Switch) statement (See
batch processing guidelines, 6-18 HELP,@CAB in the online help
system)
batch runs, starting, 7-340
BEEP command (SC), 7-312 cabinets, naming, 3-2
BFN (Binary Find) statement, 7-33 CAH (Cache Report) statement (See
BLT (Build Label Table) statement HELP,@CAH in the online
(See HELP,@BLT in the online
help system)
help system) CAL (Calculate) statement, 7-46
BLT (Build Label Table) statement, Calculate Update (CAU) statement
(See HELP,@CAU in the online
F-2
Boolean logic, 7-51 help system)
calculations
border, creating, 7-293, 7-298, 7-301
box (0), use of as tab character, vii date, 7-86
multiple, 6-16
BR (Background Run) statement, 7-40
BR (Background Run) statement: on literal data, report data, dates
OS 1100, 7-42 and times, 7-12
braces (0), use of to show required time, 7-86
fields, vi using ART, 7-23
brackets ([1), use of for optional entries, using CAL, 7-46
vi using CHG, 6-15, 7-69
branching within runs, 7-138, 7-143 using CNT, 7-78, 7-82
using DC, 7-91
Break (BRK) statement, 7-44
breakpoints, setting in runs, 7-239, using SUB, 7-343
7-245 using TOT, 7-347
BRG (Break Graphics) statement (See CALL (Call Subroutine) statement,
HELP,@BRG in the online help 6-12, 7-58, F-2
system) CAR (Clear Abort Routine) statement
(See HELP,@CAR in the online
help system)

Index-2 7831 9274-000

 Index

CAU (Calculate Update) statement CHG (Change Variable) statement,

(See HELP,@CAU in the online 4-11, 4-16, 7-68
help system) Clear Abort Routine (CAR) statement
CC run, 5-10 (See HELP,@CAR in the online
center dot (-), use of as tab character, help system)
vii Clear Error Routine (CER) statement
CER (Clear Error Routine) statement (See HELP,@CER in the online
(See HELP,@CER in the online help system)
help system) CLK (Clear Link) statement (See
Change Variable (CHG) statement, HELP,@CLK in the online help
4-11, 4-16, 7-68 system)
character $CLRT$ data control command,
color codes, 7-226 (table) C-2
continuation ( \ ), 2-15 CLT (Clear Label Table) statement
emphasis, in OUT, 7-227 (See HELP,@CLT in the online
hierarchy, D-9 help system)
maximum number in a run, CLV (Clear Variables) statement (See
registering , 4-23 HELP,@CLV in the online help
processing system)
in run statements, 2-16 *cmd (Local Code) statement, 7-364,
with CAL, 7-54 G-1
with SC, 7-287 CMP (Compare Report) statement,
set processing (OS 1100), D-9 7-72
sets, 6-13 CMU (Commit Updates) statement
special, 2-14 (See HELP,@CMU in the
strings, locating, 7-180 online help system)
translation, C-4 CNT (Count) statement, 7-78
characters color
list of ASCII, D-2 codes, (OUT), 7-227
list of Fieldata, D-5 specifying with OUT, 7-226
chart runs, linking to, 7-179 use of in book, xi
charts (See graphics) columns
CHD (Command Handler) statement, displaying count of, 5-10, 5-11
7-65 moving, 7-250, 7-265
checkpoint displays, 6-9 specifying those to process, 2-13

7831 9274-000 Index-3

Index

Command Handler (CHD) statement, coordinator, MAPPER system, 1-4

7-65 Count (CNT) statement, 7-78
commands counting entries (See entry count)
data control, (table) C-2 CP command (SC), 7-313
executing UNIX, 7-352 CPY (Copy) statement (See
screen printing (SC), 7-312 HELPACPY in the online help
setup (SC), 7-312 system)
text handling (SC), 7-307 Create File (FIL) statement, 7-125
Compare Report (CMP) statement, CSR (Clear Subroutine) statement
7-72 (See HELP,@CSR in the online
computations (See calculations) help system)
conditional branching, 6-10 cursor
console, sending messages to system, control commands, 7-288
7-192 symbol for, vii
constant labels
in CAL, 7-47
in CNT, 7-84
D
in DC, 7-91 DAT (Date) statement, 7-86
definition, 4-3 data
including defined, 4-43 capturing from screen, 4-28
using predefined, 4-39, 6-3 changing, 7-8, 7-155
contents of variable as variable name comparing, 7-8
or number, 4-13 displaying at another terminal,
context-sensitive help, displaying (SC), 7-220
7-316, 7-317 extracting, 7-79
continuing a run statement on the next finding, 7-8, 7-33, 7-121, 7-133,
line, 2-15 7-155, 7-180, 7-333
control moving, 7-250, 7-265, 7-343, 7-347
commands, data, (table) C-2 paged, how SC interprets, 7-311
key, E-2 reformatting, 7-8
line sorting, 7-8, 7-330
accepting input from, 4-32, 7-65, summarizing, 7-81
7-149 transferring to remote MAPPER
customizing, 7-129 system, 7-197, 7-198
page, altering (SC), 7-313 translating, C-4

Index-4 7831 9274-000

 Index

DATA command (SC), 7-309 DCU (Decommit Updates) statement

data control commands, (table) C-2 (See HELP,@DCU in the online
data naming help system)
cabinet, drawer, and report, 3-2 DDI (Data Definition Information)
converting run to use, 7-177 statement (See HELP,@DDI in
description, 3-1 the online help system)
displaying information about, 7-100 DEC (Decrement Variable) statement
efficiency considerations in, 3-8 (See HELP,@DEC in the online
fields, 3-4 help system)
importance of heading divider line Decode Report (DCR) statement, 7-95
in, 3-4 DEF (Define Attribute) command (SC),
partial fields, 3-6 7-292
results, 3-3 DEF (Define) statement, 4-17, 7-97
using to specify fields to process, DEF (Definition) statement, (CAL),
2-13 7-53
using to specify reports to process, deferred updating guidelines
2-12 (OS 1100), 6-17
variables, 4-19 DEFINE (Define Constant) statement,
database, demonstration, viii 4-39, F-1
Date (DAT) statement, 7-86 Define Variable Size (DVS) statement,
Date Calculator (DC) statement, 7-91 3-7, 7-110
date formats definition lines, label table, 2-10
in CNT, 7-80 DEL (Delete) statement (See
in DAT, 7-86 HELP,@DEL in the online help
in DC, 7-92 system)
date key fields, specifying, 7-78 delimiter, equation, 2-15
date processing, 7-54, 7-86, 7-91 delta (h), use of as space character, vii
DC (Date Calculator) statement, 7-91 demonstration database, before using,
DCPY (DDP Copy) statement (See viii
HELP,@DCPY in the online DEV (Device) statement (See
help system) HELP,@DEV in the online help
DCR (Decode Report) statement, 7-95 system)
DCRE (DDP Create) statement (See
HELP,@DCRE in the online
help system)

7831 9274-000 Index-5

Index

devices drawers
auxiliary, 7-31 indexing reports in, 7-141, 7-148
cassette (OS 1100), 7-31 naming, 3-2
diskette (OS 1100), 7-31 obtaining information about, 7-102
handling, 7-17 DRW (Drawer) statement, 7-102
DFLD (Define Field) command (SC), DSF (Display Form) statement, 7-320
7-298 DSG (Display Graphics) statement
DFU (Defer Updates) statement (See (See HELP,@DSG in the online
HELP,@DFU in the online help system)
help system) DSM (Display Message) statement,
differences among systems, how they 7-104
are shown in this manual, vii DSP (Display Report) statement,
DIR (Directory) statement, 7-100 7-107
DIS (Diskette) statement (See DSPFORM action, 7-318
HELP,@DIS in the online help DSPHELP action (SC), 7-316
system) DUP (Duplicate Report) statement
Display Message (DSM) statement, (See HELP,@DUP in the online
7-104 help system)
Display Report (DSP) statement, DVS (Define Variable Size) statement,
7-107 3-7, 7-110
distributed data processing, 7-18,
7-194
DLL (Downline Load) statement (See
E
HELP,@DLL in the online help ECR (Encode Report) statement,
system) 7-112
DLR (Delete Report) statement (See editing operations, in SC, 7-289
HELP,@DLR in the online help efficiency considerations
system) in data naming, 3-8
documentation, obtaining a list of using RUNA run to point out, 5-19
available, xv when writing runs, 6-13
dot ( - ), use of as tab character, vii EL- (Element Delete) statement,
DPUR (DDP Purge) statement (See 7-115
HELP,@DPUR in the online elements
help system) creating, 7-117
deleting, 7-115
retrieving, 7-263

Index-6 7831 9274-000

 Index

ELT (Element) statement, 7-117 FCSU (full character set upper), D-9
EMP (Emphasis) command (SC), FDR (Find and Read Line) statement,
7-308 7-121
emphasis field attribute commands, 7-290
characters in OUT, 7-227 field definitions, how they work in SC,
commands in SC, 7-308 7-302
controlling, 7-221 field names
protection parameter, 7-305 converting to, 3-8
Encode Report (ECR) statement, in variables, 3-6, 7-176
7-112 Fieldata characters, D-5
END command (SC), 7-313 fields
entry count abbreviations defined for, A-12
using BFN, 7-35 attribute parameters for, 7-304
using CNT, 7-78, 7-82 creating border for, 7-293, 7-298,
equation delimiter, 2-15 7-301
error handling, 1-5, 6-8, 7-342 defining
error routines, registering, 6-9, 7-258 characteristics of, 7-298
ESR (Exit Subroutine) statement (See size of, 3-7
HELP,@ESR in the online help displaying column-counts for, 5-11
system) format for, 3-5
Execute (XQT) statement, 7-360 generating on screen, 7-293
Exit MAPPER System (XUN) justifying values in, 7-48
statement, 7-363 moving, 7-343, 7-347
expressions, formulating arithmetic, named (SC), 7-302
7-24 naming partial, 3-6
EXT (Extract) statement (See reordering in results, 7-80
HELP,@EXT in the online help selecting for display, 3-8, 7-131
system) separating in run statements, 2-5
unnamed (SC), 7-302
F using named, 3-4
FIL (Create File) statement, 7-125
FCC run, 5-11 files
FCH (Relational Aggregate Fetch) creating, 7-117, 7-125
statement (See HELP,@FCH deleting (OS 1100), 7-115
in the online help system) retrieving, 7-261, 7-263
FCS (full character set), D-9

7831 9274-000 Index-7

Index

Find (FND) statement, 7-133 forms

Find and Read a Line (FDR) displaying, 7-318, 7-320
statement, 7-121 handling (SC), 7-316
five-to-one paging forward and backward in,
color codes, 7-227 7-322
output, 7-221 return stack, 7-318
FKEY command (SC), 7-315 returning to previously displayed,
FKEY$ 7-321
with CHD, 7-66 four-to-one output, 7-221
with KEY, 4-32 full character set (FCS), D-9
FKY (Function Key) statement, 7-129 full character set upper (FCSU), D-9
FLD command (SC), 7-293 Function Key (FKY) statement, 7-129
FMT (Format) statement, 7-131 function key bar, customizing, 7-129,
FND (Find) statement, 7-133 7-315
FORM run, 5-12 Function Key Input (KEY) statement,
format 7-154
capturing report, 7-175 function keys
changing in reports, 7-250, 7-265 capturing which one pressed, 4-32,
date, 7-80, 7-86, 7-92 7-66, 7-154
displaying customizing, 7-129, 7-315
selected fields in a, 7-131 passing to run (SC), 7-323
using FORM run, 5-12 (table) E-5
using FORMC run, 5-13 used with RDB, 7-239, 7-245
field name, 3-5 function mask
initial input parameters, 4-33 capturing data from OUM, 4-31
label, 2-9 displaying blank, 7-209
run statement, 2-2, A-3 displaying run statements for, 5-13
scientific notation, 4-14 functions
setting characters in, 7-327 functions
time, 7-80, 7-87, 7-92 adding your own, G-1
Format (FMT) statement, 7-131 arithmetic and trigonometric, 7-27,
FORMC run, 5-13 7-52
FORMRET action (SC), 7-321 local code, G-1
MAPPER (See run statements)
scheduling queuing, 7-324

Index-8 7831 9274-000

 Index

G HRD (Host Read) statement (See

HELP,@HRD in the online
Go To (GTO) statement, 6-10, 6-11,
help system)
7-138, F-2
HRN (Host Run) statement (See
GOC (Generate Organization Chart)
HELP,@HRN in the online
statement (See HELP,COGOC
help system)
in the online help system)
HSH (Hash) statement, 7-140
graphics terminal, selecting display
HST (Host Sign-on) statement (See
mode of, 7-313
HELP,@HST in the online help
GS (Graphics Scaler) statement (See
system)
HELP,@GS in the online help
HWR (Host Write) statement (See
system)
HELP,@HWR in the online
GTO (Go To) statement, 6-10, 6-11,
help system)
7-138, F-2

H i
IBFN run, 7-39
Hash (HSH) statement, 7-140
hash value, assigning, 7-140 IBM start requirements, 7-342
ICAL run, 7-54
heading
$ICML$ data control command,
divider line, used in data naming,
(table) C-2
3-4
ICNT run, 7-84
lines, eliminating, 6-15
icon, use of in this document, vii
including in output area, 6-17
headings, displaying function mask ICVAR$, capturing data from the
control line using, 4-32, 7-65
with, 7-209
IDAT run, 7-90
HELP identifier (SC), 7-317
HELP run, 5-2 IDU (Index User) statement, 7-141
IF (If Conditional) statement, 4-17,
help, displaying context-sensitive (SC),
6-10, 7-143
7-316, 7-317
$IFFL$ data control command,
hexadecimal codes, D-2
HOF (Host Sign-off) statement (See (table) C-2
HELP,@HOF in the online IFND run, 7-137
INC (Increment Variable) statement
help system)
(See HELP,@INC in the online
help system)

7831 9274-000 Index-9

Index

$INCL$ data control command, INVR1$, capturing data from screen

(table) C-3 using, 4-31
INCLUDE (Include Report) statement, ISOR run, 7-332
4-43, F-2 ISRH run, 7-337
IND (Index) statement, 7-148 italics, meaning of, xi
Index User (IDU) statement, 7-141 ITOT run, 7-351
INFO run, 7-179 ITV (Input Variable) statement, 7-149
initial input, capturing, 4-26, 4-33
inline attributes, 7-306
INMSV$, capturing an OUM
J
display using, 4-31, 7-209 jobs, 7-340
input justifying
accepting, 4-27, 7-149 contents of variables, 7-151
assigning a number based on, 7-140 values in fields, 7-48
control parameters, 7-304 JUV (Justify Variable) statement,
passing to run, 4-33 7-151
Input Variable (ITV) statement, 7-149
INPUT$, capturing input using, 4-28
INS (Insert Variable) statement (See K
HELPRINS in the online help Kanji characters, checking for, 7-98
system) key
installation of mouse, E-8 fields, specifying, 7-78
INSTR$, capturing data from screen functions, (table) E-4
using, 4-29 names, (table) E-1
intensity operations, E-2
parameters, 7-304 KEY (Function Key Input) statement,
screen, 7-216, 7-226 7-154
interfaces, defined, G-1 KEY action (SC), 7-323
intervals keys
displaying all, 7-82 control, E-2
scaling, 7-79, 7-80 for encoded reports, 7-96, 7-114
INTER_RUN/INTER-RUN run, 7-196, function, E-4
7-200 obtaining online help for, x, 5-5
invalid data, handling, 7-49, 7-82 paint, (table) E-1
INVAR$, capturing data from screen resume, (table) E-1
using, 4-30 return, (table) E-3
SOE (4), (table) E-1

Index-10 7831 9274-000

 Index

L limited character set (LCS), D-9

line 0, obtaining information from,
label tables
7-184
building, 2-10
line control, regaining, 7-283
clearing, 2-11
line key fields, specifying, 7-78
definition lines in, 2-10
Line Zero (LZR) statement, 7-184
using with DEFINE statements,
LINE$, 7-254, 7-267
4-39, 6-13
lines
labels
adding, 6-16
constant
in CAL, 7-47 displaying (SC), 7-309
reading, 6-16, 7-121, 7-250, 7-254,
in CNT, 7-84
in DC, 7-91 7-267
terminating scan of, 2-3, 2-6
description, 2-9
updating, 7-16
using relative line numbers instead
writing, 7-358
of, 2-10
Link to Another Run (LNK) statement,
LCH (Locate and Change) statement,
7-178
7-155
LINK$, 7-178
LCS (limited character set), D-9
LISTS run, 5-6
LCV (Locate and Change Variable)
literal
statement, 4-17, 7-158
data, specifying in run statements,
LDA (Load Variable Array) statement,
2-16
7-166
representation of variables and
LDV (Load Variable) statement, 4-11,
reserved words, 2-8, 4-38, B-2
4-15, 7-169
text, handling
LFC (Load Format Characters)
in CAL, 7-54
statement, 7-175
in SC, 7-287
LFN (Load Field Name) statement,
LLN (Last Line Number) statement
3-8, 7-176
(See HELP,@LLN in the online
LGF (Logoff Relational System)
help system)
statement (See HELP,@LGF
LMG (List Merge) statement (See
in the online help system)
HELP,@LMG in the online
LGN (Logon Relational System)
help system)
statement (See HELP,@LGN
in the online help system)

7831 9274-000 Index-11

Index

LN+ (Add Line) statement (See Load Variable Array (LDA) statement,
HELP,@LN+ in the online help 7-166
system) LOC (Locate) statement, 7-180
LN- (Delete Line) statement (See Local Code (*cmd) statement, 7-364,
HELP,@LN- in the online help G-1
system) Locate and Change (LCH) statement,
LNA (Append Line) statement (See 7-155
HELP,@LNA in the online help Locate and Change Variable (LCV)
system) statement, 4-17, 7-158
LNG (Language) statement (See lock, update, obtaining, 7-189, 7-284
HELP,@LNG in the online LOG (Log for Analysis) statement (See
help system) HELP,@LOG in the online help
LNI (Insert Line) statement (See system)
HELP,@LNI in the online help logic
system) controlling, 7-14
LNK (Link to Another Run) statement, guidelines for improving, 6-17
7-178 using in run design, 6-10, 7-143
LNM (Move Line) statement (See logical operators, 7-51
HELP,@LNM in the online LOK (Update Lock) statement (See
help system) HELP,@LOK in the online help
LNP (Put Line) statement (See system)
HELP,@LNP in the online help LSM (Load System Message)
system) statement, 7-183
LNX (Duplicate Line) statement (See LZR (Line Zero) statement, 7-184
HELP,@LNX in the online help
system)
LNY (Yank Line) statement (See
M
HELP,@LNY in the online help M characteristics, 7-222
system) MAPPER system, remote
Load Field Name (LFN) statement, interfacing other, 7-18
3-8, 7-176 sending reports to, 7-203
Load Format Characters (LFC), 7-175 signing off, 7-196
Load System Message (LSM), 7-183 signing on to, 7-194
Load Variable (LDV) statement, 4-11, transferring
4-15, 7-169 data to, 7-197, 7-198
run statements to, 7-200

Index-12 7831 9274-000

 Index

MAPPER system coordinator, 1-4 N

MARS run, 5-14
N characteristics, 7-223
masks (See function mask)
Match (MCH) statement, 7-187 named reports, 7-100
math calculations (See calculations) named variables
assigning name with USE, 7-355
MAU (Match Update) statement (See
description, 4-4
HELP,@MAU in the online
naming (See data naming)
help system)
maximums (See calculations) National Character Set (NCS)
terminals, 7-96, 7-114
MCH (Match) statement, 7-187
nesting subroutines, 7-277
menus, creating, 5-8, 7-280
NET (Network Sign On) statement,
Message to Console (MSG) statement,
7-192 7-194
messages networking statements, 7-194
new features, obtaining information
acknowledging, 7-205
displaying, 7-104 about, xvi
displaying with SC, 7-296 NOF (Network Off) statement, 7-196
notation, scientific, format for, 4-14
loading system, 7-183
sending NRD (Network Read) statement,
7-197
to other users, 7-328
and receiving, 7-17 NRM (Network Remote) statement,
7-198
reports as, 7-325
to system console, 7-192 NRN (Network Run) statement, 7-200
NRT (Network Return) statement,
waiting for, with WAT, 7-356
minimums (See calculations) 7-202
numbered variables, 4-4
MODE command (SC), 7-313
numeric sorting, 7-330
mouse, using with MAPPER software,
E-1, E-8 NWR (Network Write) statement,
7-203
MSG (Message to Console) statement,
7-192
MSG command (SC), 7-296 O
multiple
decisions, separating logic, 2-15 octal codes, D-2, D-5
expressions, 2-15 OK (Acknowledge Message) statement,
parameters, specifying, 2-14 7-205
run statements on a line, 2-3, 2-5,
2-15

7831 9274-000 Index-13

Index

online output area

assistance, 5-1 creating new, using BRK, 7-44
help system, 6-8 definition, 2-8, 6-6
information about displaying, 7-214
available documentation, xvi estimating size of, 7-44
keys, x, 5-5 including heading divider line in,
new features, xvi 6-17
operating system, interface, 7-18, literal representation of variables
7-207, 7-273, 7-352 and reserved words in, 2-8,
Operating System Interface (0S2) 4-38, B-2
statement, 7-207 Output Mask (OUM) statement, 7-209
operation, AND/OR, 7-51 OUV (Out Variable) statement, 7-231
operators OUV output, accepting, 7-149
arithmetic, 7-24
in CNT, 7-82
logical, 7-51 P
relational, 7-51 packing variables, 7-172
optional entries, symbol for, vi Page (*PAGE) identifier (SC), 7-310
options, summary of, A-20 PAGE action (SC), 7-322
OPTS command (SC), 7-314 paged data, 7-311
OR operation, 7-51 parameters
0S2 (Operating System Interface) attribute, 7-304
statement, 7-207 CNT, 7-78
OS 1100 data files color, 7-305
creating, 7-117 description, general, 2-2
deleting, 7-115 emphasis protection, 7-305
retrieving, 7-263 input control, 7-304
OS 1100 MAPPER System, character intensity, 7-304
set processing on, D-9 multiple, specifying, 2-14
OUM (Output Mask) statement, 7-209 tab stop, 7-305
OUT (Output) statement, 7-214 text input justification, 7-305
Out Variable (OUV) statement, 7-231 partial fields, naming, 3-6

Index-14 7831 9274-000

 Index

passwords Q
read, 7-270 QCTL (Queue Control) statement (See
write, 7-358 HELP,@QCTL in the online
PEK (Peek Variables) statement (See help system)
HELP,@PEK in the online help QREL (Release Message) statement
system) (See HELP,@QREL in the
percentages (See calculations) online help system)
performance, guidelines for improving QRSP (Send Response Message)
run (See efficiency considerations) statement (See HELP,@QRSP
period line, C-2 in the online help system)
PNT (Refresh Screen) statement (See QSND (Send Message, No Response)
HELP,@PNT in the online help statement (See HELP,@QSND
system) in the online help system)
POK (Poke Variables) statement (See QSNR (Send Message, Expect
HELP,@POK in the online help Response) statement (See
system) HELP,@QSNR in the online
POP (Pop Variables) statement (See help system)
HELP,@POP in the online help
quadrate (0), symbol for, vii
system)
populations, calculating, 7-83
predefined constants, using, 4-39, 6-3 R
PREP command (SC), 7-297 RAM (Relational Aggregate Modify)
Print (PRT) statement, 7-232
statement (See HELP,@RAM
printing in the online help system)
reports and results, 7-31, 7-232 RAR (Register Abort Routine)
statements available for, 7-13 statement, 7-235, F-2
priority of arithmetic operations, 7-24, RDB (Run Debug) statement, 6-9,
7-50 7-238
programs, executing, 7-28 RDB (Run Debug) statement:
prompt line, displaying with SC, 7-296 OS 1100, 7-244
protected fields, 7-216 RDC (Read Continuous) statement,
PRT (Print) statement, 7-232 7-250
PSH (Push Variables) statement (See RDL (Read Line) statement, 7-254
HELP,@PSH in the online help Read Line Next (RLN) statement,
system) 7-267

7831 9274-000 Index-15

Index

Read Password (RPW) statement, reports (cont.)

7-270 indexing, 7-141, 7-148
Reformat Report (RFM) statement, information about, obtaining, 7-184
7-265 manipulating, 7-9
Register Abort Routine (RAR), 7-235 matching, 7-187
Register Error Routine (RER), 6-9, named, 7-100
7-258, F-2 naming, 3-2
REH (Retrieve from History) obtaining information about, 7-11
statement, 7-257 performing arithmetic on, 7-347
REL (Release Display) statement (See printing, 7-13, 7-31, 7-232
HELP,@REL in the online help read passwords on, 7-270
system) reading lines in, 7-250, 7-254, 7-267
relational operators, 7-51 reformatting, 7-250, 7-265
remote MAPPER system retrieving earlier version of
sending reports to, 7-203 (OS 1100), 7-257
signing off, 7-196 sending
signing on to, 7-194 to another user, 7-328
transferring to remote MAPPER system,
data to, 7-197, 7-198 7-203
run statements to, 7-200 to stations, 7-325
Remote Symbiont Interface (RSI) setting format of, 7-327
statement, 7-273 sorting data in, 7-330
REP (Replace Report) statement (See specifying which to process, 2-12
HELP,@REP in the online help transferring
system) update control of, 7-189, 7-284
report key fields, specifying, 7-78 updating, 6-16, 7-16, 7-358
reports write passwords on, 7-358
adding lines in, 6-16 RER (Register Error Routine)
changing data in, 7-155 statement, 6-9, 7-258, F-2
comparing, 7-72 reserved words
decoding, 7-95 available with Screen Control,
displaying, 7-107 7-284
displaying lines from, 7-214 definition, 4-2
encoding, 7-112 description, 4-38
finding data in, 7-8, 7-33, 7-121, displaying contents of, 7-240, 7-246
7-133, 7-180, 7-333 examples using, 2-7
handling, 6-5 literal representation of, 2-8, 4-38,
B-2

Index-16 7831 9274-000

 Index

reserved words (cont.) Retrieve from History (REH)

loading variables with value of, statement, 7-257
7-170 RETURN (Return Call Routine)
sizing suggestions, B-2 statement (See
substrings of, example, 2-7 HELP,@RETURN in the online
summary of, B-3 help system)
testing contents of, 7-97 Reverse slant ( \ ), use of in run
using in run statements, 2-6 statements, 2-15
results RFM (Reformat Report) statement,
changing data in, 7-155 7-265
comparing, 7-72 RLN (Read Line Next) statement,
definition, 6-7 7-267
displaying, 7-107 RMV (Remove Variables) statement
estimating size of (OS 1100), 6-16, (See HELPRRMV in the online
7-334 help system)
finding data in, 7-8, 7-33, 7-121, RNM (Rename) statement (See
7-133, 7-180, 7-333 HELPARNM in the online
handling, 6-5 help system)
manipulating, 7-9 ROUTE statement, (IBM), 7-342
naming, 3-3 routines, registering
obtaining information about, 7-11 abort, 7-235
performing arithmetic on, 7-347 command handler, 7-65
printing, 7-13, 7-31, 7-232 error, 7-258
reading lines in, 7-250, 7-254, 7-267 RPW (Read Password) statement,
sending 7-270
to another user, 7-328 RRN (Remote Run) statement (See
to remote MAPPER system, HELPARRN in the online
7-203 help system)
to stations, 7-325 RS (Run Status) statement, 7-272
setting format of, 7-327 RSI (Remote Symbiont Interface)
sorting data in, 7-330 statement, 7-273
update (See update results) RSL (Create Result Copy) statement
updating, 7-16, 7-358 (See HELP,@RSL in the online
resume, (table) E-1 help system)
RET (Retrieve File) statement, 7-261 RSR (Run Subroutine) statement,
RET (Retrieve File) statement 7-275, F-2
(OS 1100), 7-263

7831 9274-000 Index-17

Index

RTN (Return Remote) statement (See run statements (cont.)

HELP,@RTN in the online help listed by name, 7-2
system) multiple on a line, 2-3, 2-5, 2-15
RUN (Run Start) statement, 7-278 options summary for 10 common,
run control reports, 1-3, 6-13 A-20
Run Debug (RDB) statement (See RDB reverse slant ( \ ) as continuation
statement) character in, 2-15
run design aids (See online assistance) scheduling, 7-324
run function calls semicolon ( ; ) as equation delimiter
definition, 1-3 in, 2-15
list of, 7-2 separating fields and subfields in,
run function names, list of, 7-2 2-5
run registration, 1-4, 4-22, 5-17, 6-3, site-defined, 7-364, G-1
6-14 slant ( / ) to specify multiple
RUN run, 5-15 parameters in, 2-14
Run Start (RUN) statement, 7-278 special characters in, 2-14
run statements summary of formats for, A-3
apostrophe ( ' ) to specify literal data transferring to remote MAPPER
in, 2-16 system, 7-200
continuing on next line, 2-15 using to define variables, 4-11
creating, 7-39, 7-54, 7-84, 7-90, using variables in, 4-12
7-137, 7-332, 7-337, 7-351 Run Status (RS) statement, 7-272
using MARS run, 5-14 Run Subroutine (RSR) statement,
using RUN run, 5-15 7-275, F-2
definition, 1-3 run-timed applications, F-1
displaying format for using RUNA run, 5-19, 6-14
FORM run, 5-12 runs
FORMC run, 5-13 APT, 5-6, 5-8
dynamically inserting, 7-242, 7-247 background, 7-40, 7-324
example, 2-4 background, on OS 1100, 7-42
executing, 7-360 BAT, 5-6
format, 2-2 batch processing and, 6-18
formulating, 2-1, A-2, 7-360 batch, starting, 7-340
functions of, 1-3 branching in, 6-10, 7-138
guidelines regarding use of, 6-15 BVT, 4-19

Index-18 7831 9274-000

 Index

runs (cont.) runs (cont.)

CC, 5-10 run-timed version, F-1
chart, linking to, 7-179 RUNA, 5-19, 6-14
controlling logic paths in, 7-14 SCGEN, 5-8
converting to use data naming, scheduling background, 7-324
7-177 source-protected, F-1
creating new, 1-4 starting, 1-5, 7-178, 7-278
debugging, 6-8, 7-238 stopping, 1-5
debugging on OS 1100, 7-244 suggestions for improvement, 6-13
definition, 1-2 suspending execution of, 7-238
executing, 1-4 suspending execution of OS 1100,
FCC, 5-11 7-244
FORM, 5-12 suspending temporarily, 7-356
FORMC, 5-13 terminating, 7-278, (table) E-1
HELP, 5-2 utilities for writing, 7-14
IBFN, 7-39 utility, linking to, 7-179
ICAL, 7-54 VALIDATE, 5-7
ICNT, 7-84 VARIABLE, 4-18
IDAT, 7-90 runstreams, 7-340
IFND, 7-137
improving logic in, 6-17
INFO, 7-179
S
INTER_RUN/INTER-RUN, 7-196, samples, calculating, 7-83
7-200 SC (Screen Control) statement, 7-280
ISOR, 7-332 scaling, CNT statement, 7-79, 7-80
ISRH, 7-337 SCGEN run, 5-8
ITOT, 7-351 SCH (Schedule) statement, 7-324
linking, 7-178 scientific notation, format for, 4-14
LISTS, 5-6 screen commands
MARS, 5-14 accessing report containing, 7-318,
obtaining information about, 7-11, 7-320
7-272 syntax rules for, 7-286
planning, 6-2 screen input, capturing, 4-26
registering, 1-4, 4-22, 5-17, 6-3, 6-14 screen intensity, 7-216, 7-226
RUN, 5-15 screen printing commands (SC), 7-312

7831 9274-000 Index-19

Index

screens site-defined local run statement,

clearing, 7-297 7-364, G-1
commands for handling, in SC, slant ( / ), use of in run statement, 2-14
7-285 SNU (Send Report to User) statement,
coordinates in, 7-286 7-328
creating input, 5-8, 7-280 SOE character (•), vii, E-1
designing with AREA command, SOE Update (WRL) statement, 7-358
7-300 SOR (Sort) statement, 7-330
differences in, ix sorting
editing commands for, 7-289 character processing order, D-7
laying out entire, 7-300 data, 7-330
manipulating, 7-10 order with C(S) option, D-7
overlaying data on, 5-8, 7-280 order with C(x) option and FCS
redisplaying, (table) E-1 (OS 1100), D-13
Search (SRH) statement, 7-333 order with C(x) option and LCS
security considerations (OS 1100), D-11
in run registration, 6-4 order without C(S) option, D-8
with DCR, 7-96 source-protected applications, F-1
with ECR, 7-114 spaces
with GTO RPX, 7-139 in literal text
with RPW, 7-270 with CAL, 7-54
with WRL, 7-358 with SC, 7-287
SELECT action (SC), 7-322 significant, 2-16
semicolon ( ; ), use of in run symbol for, vii
statements, 2-15 special characters, 2-14, E-1
SEN (Send Report) statement, 7-325 special commands in SC, 7-307
Send Report to User (SNU) statement, SQL (Submit SQL Statement)
7-328 statement (See HELP,@SQL in
setup commands (SC), 7-312 the online help system)
significant spaces, handling in run square (:1), use of as tab character, vii
statements, 2-16 SRH (Search) statement, 7-333
signing off remote MAPPER system, SRR (Sort and Replace Report)
7-196 statement (See HELP,@SRR in
signing on to remote MAPPER system, the online help system)
7-194

Index-20 7831 9274-000

 index

SRU (Search Update) statement (See STR (Start) statement, 7-340

HELP,@SRU in the online help string space limits (OS 1100), 4-23,
system) 4-24
stack strings, locating character, 7-180
forms return, 7-318 SUB (Subtotal) statement, 7-343
using the variable, 4-24 subfields
standard deviation, calculating, 7-83 abbreviations defined for, A-12
start requirements, IBM, 7-342 separating in run statements, 2-5
Start (STR) statement, 7-340 subroutines
start-of-entry character, vii, E-1 called by CALL, 6-12, 7-58
STAT1$ called by RSR, 7-275
contents, BFN, 7-37 description, 6-12
contents, CAL, 7-50 nesting, 7-277
contents, DRW, 7-103 run statements available for
contents, IND, 7-148 handling, 7-14
contents, LFN, 7-176 writing modular (OS 1100), 4-23
contents, LZR, 7-185 substrings
contents, MCH, 7-189 format for variable, 4-12
contents, OUT, 7-218 testing contents of, 7-97
contents, SC, 7-285 trailing characters, format for, 4-12
STAT2$ subtotal (See calculations)
contents, CAL, 7-50 Subtotal (SUB) statement, 7-343
contents, CNT, 7-82 summaries, calculating total data,
contents, IND, 7-148 7-81
contents, LZR, 7-185 syntax
contents, MCH, 7-189 run statement, 2-2
contents, NWR, 7-203 screen command, 7-286
contents, SC, 7-285 system directory, 3-1
STAT3$ system coordinator, 1-4
contents, CNT, 7-82 system messages loading into variable,
contents, LZR, 7-185 7-183
station, obtaining information about,
7-338
STN (Station Information) statement,
7-338

7831 9274-000 Index-21

Index

T TIME constant label, 7-91

tab characters time formats
in CNT, 7-80
clearing translation of, C-2 in DAT, 7-87
symbol for, vii
translating, C-3 in DC, 7-92
time key fields, specifying, 7-78
tab stop parameter, 7-305
$TABA$ data control command, time processing, 7-54, 7-86, 7-91
TODAY constant label, 7-91
(table) C-3 TOT (Totalize) statement, 7-347
tables
APT, 5-6 total (See calculations)
TRC (Trace) statement (See
label, 2-10, 4-39, 6-13
TCS (Tape Cassette) statement (See HELP,@TRC in the online help
system)
HELP,@TCS in the online help
triangle, use of in this document, vii
system) trigonometric functions, 7-27, 7-52
terminal
$TRNA$ data control command,
color, 7-221
displaying information at another, (table) C-4
7-220
graphics, selecting display mode of U
(SC), 7-313
intensity settings on, 7-216, 7-226 ULK (Unlock) statement (See
key functions, (table) E-4 HELP,@ULK in the online
key names, (table) E-1 help system)
keys operations, E-2 UNIX file
monochrome, 7-221 creating, 7-125
National Character Set (NCS), retrieving, 7-261
7-96, 7-114 UNIX Interface (UNX) statement,
sending messages to, 7-325 7-352
setup, altering (SC), 7-313 UNIX system
text exiting to, 7-363
displaying (SC), 7-309 interfacing, 7-352
highlighting on screen (SC), 7-308 unprotected fields, 7-216
text handling commands (SC), 7-307 UNX (UNIX Interface) statement,
text input justification parameter, 7-352
7-305

Index-22 7831 9274-000

 Index

UPD (Update) statement (See variables (cont.)

HELP,@UPD in the online decreasing value of, 4-15, 6-15, 7-69
help system) default justification of, 4-8
update lock, obtaining, 7-189, 7-284 defining, 4-10
update results defining size for report fields, 3-7,
with CAU, 7-46 7-110
with LCH, 7-156 definition, 4-2
with LOC, 7-181 displaying contents of, 7-231, 7-240,
with MAU, 7-187 7-246
with SRU, 7-333 examples using, 4-35
USE (Use Variable Name) statement, field names in, 3-6
7-355 group of (array), 7-166
user input, accepting, 4-27 guidelines for loading, 6-15
utility runs, linking to, 7-179 increasing value of, 4-15, 6-15, 7-69
initializing, 4-10, 7-68, 7-149, 7-169
V justifying contents of, 7-151
limits of, working with, 4-22
VALIDATE run, 5-7 literal representation of, 2-8
VARIABLE run, 4-18 loading
variables an array of, 7-166
addition using, 7-69 based on content, 7-172
array of, 7-166 with control line input, 4-32
assigning names to, 4-5, 7-355 with data, 6-15, 7-169
building tables of, 4-19 with data naming information,
capturing 7-100
format of displayed report in, with field names, 7-176
7-175 with format of displayed report,
input in, 7-149 7-175
changing with function key input, 4-32
contents of, 4-15 with line 0 information, 7-184
strings in, 7-158 multiple, 7-171
comparing and testing, 7-158 with number of characters, 7-102
converting to and from named, 4-5, with system messages, 7-183
4-19 with user input, 4-26, 4-33
data names in, 3-3 with value of reserved words,
7-170

7831 9274-000 Index-23

index

variables (cont.) w
locating strings in, 7-158 WAT (Wait) statement, 7-356
manipulating, 6-12, 7-13, 7-58 WDC (Word Change) statement (See
maximum number allowed, 4-22 HELP,@WDC in the online
maximum number of characters help system)
used in, registering, 4-23 WDL (Word Locate) statement (See
monitoring, 7-239, 7-246 HELP,@WDL in the online
naming, 4-4 help system)
numbered, 4-4 work flow language (WFL) jobs,
octal (OS 1100), 7-70 7-340
packing, 7-172 WPR (Word Process) statement (See
passing arrays, 4-24 HELP,@WPR in the online
performing arithmetic on help system)
dates/times in, 7-91 write passwords, 7-358
redefining, 4-11, 7-68, 7-169 WRL (Write Line) statement, 7-358
setting another with same contents,
7-97
stacking, 7-167 X
string space limit in (OS 1100), XCH (Exchange Variables) statement
4-23, 4-24
(See HELP,@XCH in the online
substrings (See substrings) help system)
subtraction using, 7-69 XDRW$, 7-235, 7-258
testing contents of, 4-17, 7-97 )(ERRS, 7-258
types and sizes, 4-6, 4-9 )(FUNS, 7-235, 7-259
using contents to act as name or XIT (Sign off MAPPER Software)
number of, 4-13 statement (See HELP,@XIT in
using in run statements, 4-12 the online help system)
using named and numbered XLINE$, 7-235, 7-259
(OS 1100), 4-5 XQT (Execute) statement, 7-360
using scientific notation in, 4-14
XRPTS, 7-236, 7-259
using the stack, 4-24 XUN (Exit MAPPER System)
variance, calculating, 7-83 statement, 7-363
vertical bar (I), use of as tab character,
vii

Index-24 7831 9274-000

 Index

0, meaning of, vi
\ (reverse slant), use of in run
statements, 2-15
0, meaning of, vi
' (apostrophe), use of in run
statements, 2-16
/ (slant), use of in run statement, 2-14
; (semicolon), use of in run statements,
2-15
I (vertical bar), use of as tab character,
vii
A (delta), use of as space character, vii
0 (quadrate), symbol for, vii
•(center dot), use of as tab character,
vii

7831 9274-000 Index-25

Help Us To Help You
Publication Title

Form Number Date

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:
❑ Addition ❑ Deletion ❑ Revision ❑ Error

Comments

Name

Title company

Address (Street, City, State, Zip)

Telephone Number

Help Us To Help You

Publication Title

Form Number Dare

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:
❑ Addition ❑ Deletion ❑ Revision ❑ Error

Comments

Name

Title Company

Address (Street, City, State, Zip)

Telephone Number
 NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

BUSINESS REPLY MAIL

FIRST CLASS PERMIT NO. 1145 ST. PAUL MN 55164

POSTAGE WILL BE PAID BY ADDRESSEE

Unisys Corporation
Attn: MAPPER® Product Information
P.O. Box 64942 M.S.: 4792
St. Paul, MN 55164-0942 USA

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

BUSINESS REPLY MAIL

FIRST CLASS PERMIT NO. 1145 ST. PAUL MN 55164

POSTAGE WILL BE PAID BY ADDRESSEE

Unisys Corporation
Attn: MAPPER® Product Information
P.O. Box 64942 M.S.: 4792
St. Paul, MN 55164-0942 USA
I I I IIIIIII III I I I I
78319274-000