Mapper 34R1 Rundesign
Mapper 34R1 Rundesign
Mapper 34R1 Rundesign
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 remark form
in this manual, or remarks may be addressed directly to Unisys Corporation, MAPPER
System Test and Publications, P.O. Box 64942 MS: 4792, St. Paul, Minnesota,
55164-0942, U.S.A.
Page Status
Page Issue
UP-9662.5 PS-1
About This Manual
PURPOSE
SCOPE
AUDIENCE
The Run Design Reference is for all run designers —from beginning run
designers to advanced users who design sophisticated applications.
PREREQUISITES
UP-9662.5 ATM-1
About This Manual
If you are a novice run designer, read the first six sections before
beginning to write your own runs. Then use Section 7 and the
appendixes as references. In addition, you may want to review the
sample runs in Appendixes B and C for more insight into MAPPER
runs.
Use the EXAM run to check your MAPPER run-writing skills on line.
See the OS 1100 MAPPER Manual Functions Operations Training Guide
for more information.
Conventions
To help you understand this manual and find MAPPER software easy
to use, certain style conventions are used. Following is a description of
how this manual handles run statement syntax, tab characters, examples,
key names, uppercase letters, italics, color, and important terminology.
ATM-2 UP-9662.5
About This Manual
❑ The call is capitalized (for example, CHG). However, you can type
it in either uppercase or lowercase letters.
❑ Fields and subfields are italicized whenever they call for variable
data. Variable data is information you supply according to the
explanation that follows the statement.
@AUX,O,B,2,123,COP,Y„,Y„2 .
❑ Braces around items separated by a vertical bar mean that you may
choose from among the items listed; for example:
(item] I item2)
Tab Characters
UP-9662.5 ATM-3
About This Manual
Examples
The key names used in this manual are based on the UTS family of
keyboards. If you need definitions for keys other than those on a UTS
keyboard, refer to your terminal documentation.
Uppercase Letters
ATM-4 UP-9662.5
About This Manual
Italics
❑ The italicized letter N (ii or N) stands for a numeral (nn calls for
two digits; nnn for three, and so on).
❑ Words in bold italics are key terms that are defined in the glossary.
Color
Run statement formats and information that you are instructed to type
are shown in color.
The term "enter" means type the necessary information and press XMIT.
"Resume" means press Fl (you must use the UPPER FUNCTION key at
the same time) or enter rsm.
UP-9662.5 ATM-5
About This Manual
ORGANIZATION
Section 2. Using the Data Directory describes the Data Directory and
how to use it.
Section 5. Using Online Runs describes how to use HELP and other
online run design aids.
ATM-6 UP-9662.5
About This Manual
E. Character Sets lists the Limited Character Set and the Full
Character Set.
This manual is part of the MAPPER software level 34R1 library, which
contains documents that you may find helpful while using MAPPER
software. The following list provides the exact title of each document
in the library, followed by its short title in parentheses and its previous
title. The documents are listed in the order a new MAPPER site might
use them. A separate list describes how to order copies of the MAPPER
software level 34R1 manuals. In addition, there are several documents
of related Unisys products that are referenced throughout this manual;
these are listed under "Related Unisys Documents."
UP-9662.5 ATM-7
About This Manual
This reference card lists the most commonly used runs, functions,
run statements, and reserved words for coordinators.
ATM-8 UP-9662.5
About This Manual
This reference card lists and describes all word processing control
parameters, control characters, and commands.
UP-9662.5 ATM-9
About This Manual
ATM-10 UP-9662.5
About This Manual
Optional Documents
These documents are not part of the standard MAPPER library and
must be ordered separately.
This guide is for users who have never written a run. It covers
only basic information and should be read and followed, step by
step, at a MAPPER terminal. When you need more details than are
given in this manual, see the Run Design Reference.
UP-9662.5 ATM-11
About This Manual
ATM-12 UP-9662.5
About This Manual
Standard Library
UP-9662.5 ATM-13
About This Manual
Optional Documents
These are optional documents that do not come with the standard
library and must be ordered separately:
This guide describes how to transfer files and jobs from terminals
in a DDP network.
ATM-14 UP-9662.5
Contents
1. Introduction 1-1
New Run Design Features 1-2
New Run Statements 1-2
Enhancements to Existing Statements 1-3
New Reserved Words 1-4
Other New Features 1-4
Discontinued Runs 1-6
What Is a MAPPER Run? 1-7
UP-9662.5 Contents-1
Contents
Contents-2 UP-9662.5
Contents
UP-9662.5 Contents-3
Contents
Contents-4 UP-9662.5
Contents
UP-9662.5 Contents-5
Contents
Contents-6 UP-9662.5
Contents
Appendixes
UP-9662.5 Contents-7
Contents
Glossary
Index
Evaluation Card
Contents-8 UP-9662.5
Tables
UP-9662.5 Contents-9
I. Introduction
This manual contains reference information about new and existing run
statements. By using this manual, you can write and update complete
runs, obtain quick access to statement syntax, and learn about
efficiency techniques by following examples.
UP-9662.5 1-1
New Run Design Features
SC (Screen Control)
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.
1-2 UP-9662.5
New Features
DSG Allows you to send DSG displays to other terminals. You can
specify a label or line number to go to in case of error.
LDV Allows you to specify only the receiving variable when loading
a variable with its own contents.
MAU Added the A option to allow match updates on all line types.
OUT Allows you to send OUT displays to other terminals. You can
specify a label or relative line number to go to in case of error.
UP-9662.5 1-3
New Features
SRH Added the vrid variable to capture the RID number where the
find is made when doing a range search. This is useful when
using the B(n) option.
TYP Added the vrlmt variable to capture the highest RID number
allowed in the form type; the vllmt variable to capture the
highest number of lines allowed per report in the form type;
and the vrids variable to capture the total number of reports in
the form type.
❑ The new LIMITS run displays the highest RID number and lines
per report that are allowed for the mode and type you are
currently in.
❑ The SCHEDULE run can now be called from a run control report
using the LNK (Link to Another Run) statement.
1-4 UP-9662.5
New Features
❑ Chart runs can now be called from a run control report using the
LNK (Link to Another Run) statement.
❑ The DEMO, EDIT, and MARK sample runs have been updated to
show the use of named variables.
❑ The BVT (Build Variable Table) run allows you to build or rebuild
a variable table displaying the location of variables and convert
variables in your run control report. The BVT run replaces the
VAL run, which is no longer supported.
❑ The RUN run now includes function keys that allow you to control
the operation of runs and a screen that allows you to display,
execute, and register results or exit the run.
UP-0662.5 1-5
New Features
❑ The FKEY$ reserved word now allows you to capture the number
of up to 22 function keys.
DISCONTINUED RUNS
❑ The FORMD run has been discontinued. However, you can now
use the new HELP @rfc to display a run statement format.
❑ The VAL run has been discontinued and is replaced by the new
BVT run.
1-6 UP-9662.5
What Is a MAPPER Run?
You can format reports in your MAPPER runs to suit your needs.
UP-9662.5 1-7
2. Using the Data Directory
The Data Directory is a run design tool that allows you to dynamically
identify fields, modes, form types, and reports in run statements by
naming them.
Database naming has its own special syntax; however, it does not
replace standard run syntax. You can use both conventions in the same
run, even within the same run statement.
❑ Naming Fields
UP-9662.5 2-1
Naming Fields
You can process fields in reports by name. The names are derived
either from the headers of the report, or from RID 0 if you're
processing the entire form type. Field names, therefore, are an integral
part of the database.
For example, in standard run syntax, this statement searches the report
for customer code AMCO:
You don't have to specify the starting column number or the field size;
only the field name is required.
If a field moves within a report or if the size of the field changes, you
don't have to change the reference to it.
When a run reads the first named field in a statement, it scans the
report for a header-divider line (*=). The report must contain a header-
divider line within the first 16 lines of the report.
The run derives starting columns and field sizes from the grouping of
equal signs on the header-divider line, extracting field names from up
to two asterisk lines immediately preceding it. If the report has more
than two asterisk lines, the run recognizes only the last two.
2-2 UP-9662.5
Naming Fields
Examples
ST CD (2-2)
STATUS DATE (5-6)
BY IN (12-2)
PRODUCT TYPE (15-9)
SERIAL NUMBER (25-6)
This example shows the first fields of a report with three asterisk lines
containing field headers:
* MONTHLY. ANNUAL .
* I NTEREST . D I SCOUNT .
* RATE . STATUS .
Therefore, if you're using named fields for reports with three or more
asterisk type header lines, keep the important information in the two
header lines immediately preceding the header-divider line.
UP-9662.5 2-3
Naming Fields
FIELD NAMES
You can use any characters in your field names. However, the run
considers only alphanumeric characters (A to Z and 0 to 9) when
comparing the field name to the report header; it ignores any other
characters, such as spaces or special characters. For example,
'CUSTCODE', 'CUST-CODE', and 'CUST CODE' are all acceptable field
names.
For example, you can specify a search of the CUST CODE field like
this:
This makes the run statement shorter, which generally makes it more
efficient.
This example searches the CUST CODE field for AMCO; notice that
there are no spaces or other characters between the apostrophes in 'VV:
2-4 UP-9662.5
Naming t mins
To process a named field from any column to the end of the field,
specify the starting column and define the number of characters as
zero.
UP-9662.5 2-5
Naming Fields
FIELD ORDER
You can list multiple named fields in any order; they don't have to be
in the same order in which they appear in the report, as long as the
parameters and named fields are in the same order.
For example, these two statements perform the same search and have
identical results:
You can use the DVS (Define Variable Size) statement to create
variables equal to the size of the report fields (see DVS in Section 7).
When the run executes, it defines the size of the variable; any input
parameter or screen using that variable dynamically adjusts to a change
in the size of the field.
You can also define the variable to a field size in these statements that
load variables with data from report fields: RDC (Read Continuous),
RDL (Read Line), RLN (Read Line Next), and SUB (Subtotal). See
RDC, RDL, RLN, and SUB in Section 7.
Use the FMT (Format) statement to select which fields you want to
display in a following DSP, OUT, or OUM statement (see FMT in
Section 7).
2-6 UP-9662.5
Naming Fields
EFFICIENCY CONSIDERATIONS
When a run encounters a field name, it must read the report header,
which requires one additional I/O access. However, it does not read the
header for other field names in the same run statement. Also,
succeeding run statements that specify the same report, or a result
derived from it, do not cause the run to read the report header again.
In this example, the SRH statement causes the run to read the headers;
the SOR and TOT statements do not.
UP-9662.5 2-7
Naming Modes, Form Types, and Reports
You don't have to specify the mode, form type, and report number —only
the name of the report.
Mode, form type, and report names are defined in the System
Directory, which you can access and update using the NAME run. (See
"NAME—Updating the System Directory" in this section.) Before using a
named mode, form type, or report, you must enter it in the System
Directory.
You can also assign a name to a range of reports in a form type. With
BFN (Binary Find), FND (Find), and SRH (Search), the system
automatically adds the R option to the run statement if you use a name
that defines a range of reports.
2-8 UP-9662.5
Naming Modes, Form Types, and Reports
Enclose the names of modes, form types, and reports within apostrophes
('). Names must start with an alphabetic character (A to Z), can be
either uppercase or lowercase, and can contain from 1 to 16 characters.
You can use any characters in your data names. However, the run
considers only alphanumeric characters (A to Z and 0 to 9) when
comparing the name to the System Directory; it ignores any other
characters, such as spaces. For example, 'ORDERSTATUS', 'ORDER-
STATUS', and 'ORDER STATUS' are all acceptable names.
NAMES IN VARIABLES
This example searches the ORDER STATUS report for AMCO in the
CUST CODE field; notice that there are no spaces or other characters
between the apostrophes in 'VV.
NAMING RESULTS
Wherever you specify the current result (-0) or a renamed result (-1 to
-4), you can omit the mode and type (rn and t) fields.
@DSP 0 , B , - .
@DSP - 0 .
UP-9662.5 2-9
Naming Modes, Form Types, and Reports
The System Directory is a report that contains data names for modes,
form types, and reports. You can use data names in run statements to
define modes, types, and reports to process.
The NAME run updates the System Directory. You can enter a new
name, delete an existing name, or change the definition of an existing
name.
Name
Mode
Type
RID Number(s)
Department (your department) (ALL.All)
USER-ID (your user-id) (ALL=AtL)
Function ADD (ADD,CHG,DEL)
Update Directory Y (Y or N)
2-10 UP-9662.5
Naming Modes, Form Types, and Reports
In field: Enter:
* To name a mode, leave the Type and RID Number fields blank. To name a form type, leave only the
RID Number field blank. When deleting a name, you can leave the Mode, Type, and RID Number fields
blank.
UP-9662.5 2-11
Naming Modes, Form Types, and Reports
NAME namel,m,t,r,dept,user,junc,update?)
In field: Enter:
2-12 UP-9662.5
Naming Data Using Reserved Words
You can use reserved words directly in run statements, which means
you don't have to load them in variables beforehand. Because many
reserved words represent data entities, such as form types, this is also a
form of data naming.
In addition, you can use reserved words that represent numeric form
types to replace the mode and type (m and t) fields of run statements.
@OSP.TYPE$,R1D$ .
UP-9662.5 2-13
3. Formulating Run Statements
❑ Labels
❑ Special Characters
UP-9662.5 3-1
Run Statement Format
This SRH (Search) statement uses data from mode 0, type C, report 1:
where:
@ control character
0 mode number
3-2 UP-9662.5
Run Statement Format
❑ Type an @ in column 1.
❑ Enter multiple run statements on one line and separate them with
spaces. Use just one @ per line.
`....../
UP-9662.5 3-3
Run Statement Format
O The required fields and subfields for a run statement vary from
statement to statement. Include all required fields. Enter two
apostrophes (") if you're not entering options in the o (options)
field.
3-4 UP-9662.5
Run Statement Format
❑ Run statements that access or lock reports (IDU, LOK, RDL, SOR,
SRH) cannot access their own run control report.
UP-9662.5 3-5
Labels
You can identify any statement line in a run with a label. Use labels
in these situations:
Format
or:
where is a line label number from 1 to 199 (or 1 to 399 if your system
is set up to handle up to 399 labels; check with your coordinator).
3-6 UP-9662.5
Labels
Label table definition lines predefine label locations (that is, they tell the
run which lines have labels).
Use label table definition lines in larger, more stable production runs,
but not in runs that change frequently.
:L 22=13.33=26,44=39
Label 22 is on line 13, label 33 is on line 26, and label 44 is on line 39.
Format
:L label-number=line-number, .
where:
Use BLT to build label tables. See BLT in Section 7. See also the BLT
function in the Manual Functions Reference.
UP-9662.5 3-7
Special Characters
and:
3-8 UP-9662.5
Special Characters
Use a reverse slant (\) whenever a run statement is too long for one
line. For example:
The reverse slant at the end of the first line tells the system that this
statement continues on the second line.
For readability, use the reverse slant at the end of a subfield, and if
possible, avoid starting a second or succeeding line with a space.
UP-9662.5 3-9
Special Characters
3-10 UP-9662.5
4. Variables and Reserved Words
❑ Reserved Words
UP-9662.5 4-1
Variables—Names, Types, and Sizes
When you use a variable, you must first initialize it. This means that
you assign it a name, a variable type, a size, and an initial value.
NAMING VARIABLES
You can use these named variables anywhere you would use
numbered variables in a run. When a named variable is defined,
the system assigns it the lowest unused variable number. Therefore,
the first variable in a run is assigned to VI, the second is assigned
to V2, and so on. After a name is assigned to a variable, it can no
longer be referenced by its variable number.
4-2 UP-9662.5
Variables —Names, Types, and Sizes
When you use a variable for the first time, you must assign it a type
and a size. There are six types of variables:
A Alphanumeric
F Fraction
H Hollerith (any characters)
I Integer (whole numbers)
0 Octal
S String
V9 i3
<PHONE>A8
Table 4-1 shows types and sizes of variables used in ART, CHG, and IF
statements.
UP-9662.5 4-3
Variables—Names, Types, and Sizes
USING VARIABLES
variable-name(position-characters)
You can also use zeros in substrings to specify known trailing substrings
and unknown trailing substrings. To use a known trailing substring, you
specify the starting character position, then a zero to indicate the
remaining characters of the field. For example, this means start at
character position 3 for the remaining characters in VI:
V1(3-0)
V1(0-2)
You can use another variable that has a number from 1 through 199 to
name a variable. For example, if VI contains the value 2, this
references variable V2:
VV1
4-4 UP-9662.5
Variables—Names, Types, and Sizes
«ONE»
You can use another variable that contains a valid number (depending
on the type of variable) to specify the size of a variable. For example:
VliV2
You can use variables in many places and for many purposes in
MAPPER runs. As you become increasingly familiar with MAPPER
run statement syntax and special commands, you are better able to
determine where a variable might be useful.
Here are just a few places you can use variables in place of hard-coded
data:
Table 4-1 lists the maximum size, examples, and contents of each type
of variable. It also describes the contents of each type when used with
ART, CHG, and IF statements.
UP-9662.5 4-5
Variables—Names, Types, and Sizes
Type A (Alphanumeric):
Maximum Size: 16
Examples: V10a16 <PHONE>a8
Contents: Alphanumeric and special characters.
Type F (Fraction):
Maximum Size: 18
Examples: V10f18.10 <TOTAL>f 18.10
Contents: Fractional numbers, positive and negative.
Positive numbers may be unsigned; that is, they
don't need a plus sign (+). The maximum size of
18 includes the sign and decimal point. The
fractional portion may be up to ten characters. In
the above example, 18 characters are allowed —7
before the decimal point, the decimal point, and 10
after the decimal point. If more positive numbers
are added to the left of the decimal point, the
decimal portion is truncated.
(continued)
4-6 UP-9662.5
Variables—Names, Types, and Size:
Type H (Hollerith):
Maximum Size: 18
Examples: V10h16 <CODE>h18
Contents: Hollerith, any characters.
Type I (Integer):
Maximum Size: 16
Examples: V10i12 <FINDS>i3
Contents: Integer (whole numbers), positive and negative.
Positive numbers may be unsigned; that is, they
don't need a plus sign (+). Include the sign in the
variable size —it is a significant character.
(continued)
UP-9662.5 4-7
Variables —Names, Types, and Sizes
Type 0 (Octal):
Maximum Size: 12
Examples: V5o12 <TYPE>o12
Contents: Numbers 0 through 7.
Type S (String):
Maximum Size: 132
Examples: vlOs132 <ADDRESS>s40
Contents: Alphabetic, numeric, and special characters, any
combination (for a total of 2,016 characters in all
string variables combined).
4-8 UP-9662.5
Initializing and Redefining Variables
NOTE: You can also initialize and redefine variables with a colon.
However, this method is no longer recommended because it is
less efficient and more difficult to use.
@LDV V112=1 .
@LDV V1A1=A,V212.10 .
UP-9662.5 4-9
Initializing and Redefining Variables
@CHG «ONE»12 2 .
4-10 UP-9662.5
Initializing and Redefining Variables
This example shows how to use an RDL statement to place the data in
column 5 for six characters in <DATE> and the data in column 71 for
five characters in <ORDER>:
This example uses a FND statement to place the RID number of the
report where the find was made in <RID> and the line number in
<LINE>:
UP-9662.5 4-11
Changing the Contents of Variables
@LDV V12S15=0123456789ABCDE .
The following statement loads the first three character positions of V12
with V10:
Note that this INS statement does the same as the preceding LDV
statement, but it is slower and less efficient:
This LDV statement initializes V13 to 4 and changes VIO to equal the
three character positions starting in column V13 of V12:
4-12 UP-9662.5
Using Exponential Notation with Variables
If the numbers in a variable get too large for the variable, the system
changes the value to exponential notation if variables are defined as A,
I, or F type. For example:
UP-9662.5 4-13
Examples Using Variables
@DSP,V1.V2.113 .
❑ You could load the variables earlier in the run so that if the data
you want to display is moved to another mode or report, you need
to change that information only once in your run control report —at
the place where you initialized VI, V2, and V3. This is especially
useful if the report is processed repeatedly in the run, and is much
easier than changing every applicable statement in the run.
4-14 UP-9662.5
Examples Using Variables
@LDV V113.0,V2A1=D .
@FND,V1,V2 " 22-3 ❑ ,' 1' V3I5 .
In the last statement, V5, which is the line number of the find, is
the line the display is started on.
UP-9662.5 4-15
Examples Using Variables
@LDV V113=0,V2A1=D,V314=1,V415=6
@LZR,V1,V2,V3 V5I5 . V5=NR.LINES
@fND,V1,V2,V3,V4,196 " 22-3 0,' 2' ,V4 .
@DSP,V1,V2,V3,V4 . V4=LINE
@INC V4 IF V4 NOT > V5 GTO LIN -2 .
@196: .
No More Finds
@GTO END .
In this example, V4 is the counter for the line to start the find on,
as well as the line number of the find for use in the display. V5 is
the number of lines in the report. As V4 is increased, the find
process begins further into the report. When V4 becomes greater
than V5, the entire report has been processed and the run ends.
You can use loops and counters like these in many other ways. In
the same example, you could execute a find across reports and
display the correct report at the appropriate line by using more
variables and checks.
4-16 UP-9662.5
Loading Variables with Screen Input and Initial
Input Parameters
You can load variables with the contents of these reserved words to
capture initial input (run call) parameters or information the user has
entered on the screen:
ICVAR$ Captures input the user has entered at the control line
(used only with the CHD [Command Handler] run
statement)
FKEY$ Captures the number of the function key the user pressed
❑ To resume the run after the output is displayed, press XMIT with
the cursor below the control line. You can also press Fl or enter
to resume the run, but any data you entered on the screen is
not captured.
UP-9662.5 4-17
Loading Variables with Screen Input and Initial Input Parameters
NOTE: All input captured from the screen using these reserved words
is in the character set of the run control report.
When using INPUTS to capture data from the screen, remember these
guidelines:
❑ The data entered in variables starts from a tab character: the data
after the first tab character in the first variable, the data after the
second tab character in the second variable, and so on.
1. @BRK,O,A .
2. ENTER APPROPRIATE DATA AND TRANSMIT .
3. ❑ ,ENTER START DATE IN FORMAT YYMMDD
4. ❑ ,ENTER END DATE IN FORMAT YYMMDD
5. PLACE CURSOR HERE ->❑ , AND TRANSMIT .
6. @BRK OUT,-0,2,6,1,1,Y .
7. @CHG INPUT$ <STDATE>16,<ENDATE>16 .
4-18 UP-9662.5
Loading Variables with Screen Input and Initial Input Parameters
1. The first BRK statement defines the next output area (that is, the
lines that follow) as mode 0, type A. (See "Handling Reports and
Results" in Section 6 for an explanation of the output area.)
6. The second BRK statement places the preceding lines from the
output area into the -0 result. The OUT statement displays the new
-0 result on the screen.
7. CHG 1NPUT$ loads <STDATE> with the start date and <ENDATE>
with the end date that is entered.
❑ Information the user enters after the run name (for example,
runname.ab,1234,99.99)
UP-9662.5 4-19
Loading Variables with Screen Input and Initial Input Parameters
2. @BRK , 0 , A .
3. ENTER PART NUMBER El ,
4. ENTER QUANTITY a
5. @BRK OUT,-0,2,2,1,1,Y .
6. @CHG INPUT$ V1H14,V2I8 .
1. The first statement in the run captures three variables from initial
input parameters.
2. The first BRK statement clears the output area and defines the
next output area as mode 0, type A.
5. The second BRK statement places the output area in a result (-0);
the OUT statement displays the new -0 result on the screen.
6. CHG 1NPUT$ loads the value of the part number into VI and the
value of the quantity into V2.
4-20 UP-9662.5
Loading Variables with Screen Input and Initial Input Parameters
When using INSTR$ to capture data from the screen, remember these
guidelines:
This example loads variables with two lines of data on the screen:
When using INVAR$ to capture data from the screen, remember these
guidelines:
UP-9662.5 4-21
Loading Variables with Screen Input and Initial Input Parameters
❑ The data entered in variables starts from a tab character: the data
after the first tab character in the first variable, the data after the
second tab character in the second variable, and so on.
In this example, after the user enters the solicited information, the run
continues at the statement that follows the OUT statement. VI, V2, and
V3 contain the information the user entered.
4-22 UP-9662.5
Loading Variables with Screen Input and Initial Input Parameters
In this example, after the user enters the solicited information, the run
continues at the statement that follows the OUT statement. V1 contains
both the first and last name the user entered. Note that protected
format is not used.
First Last
ENTER NAME ❑ ❑
@BRK OUT.-0,2,4,1,1,Y
When using ICVAR$ to capture data from the control line, remember
these guidelines:
This example displays a report and loads VI with input the user
transmitted from the control line:
@CHD 100 .
@CHG ICVAR$ V1S80 .
@OSP.0,8,2 .
UP-9662.5 4-23
Loading Variables with Screen Input and Initial Input Parameters
@KEY .
@OSP,O,B,2 .
@LDV,W V112=FKEY$ .
4-24 UP-9662.5
VARIABLE Run—Testing Contents of Variables
The VARIABLE run determines how variable types and input methods
affect a variable's content.
variable
UP-9662.5 4-25
VARIABLE RUN
4-26 UP-9662.5
BVT Run —Building Variable Tables and Converting
Variables
Use the BVT (Build Variable Table) run to build or rebuild a table that
displays the location of all the variables in your run control report.
You can also use it to name variables so you can easily convert to or
from named variables. (See "Variables—Names, Types, and Sizes" in this
section for information about named variables.) The variable table
result is displayed at the end of your run control report.
To use the BVT run, display your run control report and enter one of
these requests:
BVT,Q The Quick build lists only the variables that are defined
(for example, V1A3 rather than V1).
Note that each of the previous requests also calls the BLT (Build Label
Table) function, which builds or rebuilds the label table.
When you rebuild a variable table, the new table is matched with the
existing table to preserve any user-defined names or comments.
UP-9662.5 4-27
BVT Run
.VARIABLE TABLE
Name .Vnum.Sq. Line Numbers Comment
*
Field Description
Line Numbers The line number where the variables are located. The
line numbers containing defined variables are flagged
with asterisks.
4-28 UP-9662.5
BVT Run
❑ When you use CVT or CVT,N to convert variables, you are not
notified when a variable/variable is converted. For example, if
you convert VV199 to «name», it may not execute correctly.
❑ When you use CVT, CVT,N, or CVZ, and the size of the new
variable causes the run statement to extend beyond the end of the
line, the original report is displayed at that line number. No
changes are made to the run control report until you change that
run statement line.
Example
The run control report for the MARK Run, shown in Appendix C, is in
RID 3E of mode 0. After the BVT run is executed against this run
control report, this information is displayed at the end of the run
control report:
.VARIABLE TABLE
* NAME .VNUM.SQ. LINE NUMBERS COMMENT
* •
UP-9662.5 4-29
Reserved Words
You can initialize a variable with the value of a reserved word using
CHG and LDV statements. For example, this CHG statement initializes
V2 as an SOE character:
@LDV,W <MODE>14=MODE$,<TYPE>16=TYPE$,‹RID>14=RID$ .
You can also use reserved words directly —where you might otherwise
use a variable —in these subfields of a run statement:
171 Mode
t Form type
r RID number
1 Line number
f Format
p Parameters
NOTE: You cannot use reserved words in the output area, where
MAPPER software reads them literally. You can use
variables in the output area, however. (See BRK and OUT in
Section 7 and "Handling Reports and Results" in Section 6 for
more details.)
See Appendix B for a list of all reserved words and more examples.
4-30 UP-9662.5
5. Using Online Runs
This section contains information about online help and MAPPER runs
you can use to help you write your own runs. For more information
about the runs in this section, enter help,run,aid,
❑ HELP Run
UP-0662.5 5-1
HELP Run
ielp run
System Response
RUN Information
This screen lists run targets. A target is an item on the screen that you
can get information about. Notice that the cursor is located after
ROLL. Just press XMIT to roll through the target list.
Here's how to get more information about a target from the list:
5-2 UP-9662.5
HELP Run
If you know the target you want help with, you can enter the target on
your help call:
help run,target
oeip run,au.
This takes you directly to the online help for the ADD statement and
tells you how to append one report to another.
You can now use HELP to display a run statement format on the
control line while you are writing a run. With a run control report on
display, enter:
help grfr
where rfc is the run function call you want the format for. You can use
this format as a reference while supplying the fields for your own run
statement. If you need more information about the run statement, press
Fl or enter rsm to display detailed HELP information. Press Fl or
enter rsm again to return to your run control report.
help
UP-9662.5 5-3
LIMITS Run—Displaying Report and Line Limits
Use the LIMITS run to display the highest RID number and the
maximum number of lines per report allowed for the current mode and
type. This information is displayed on the first line of the report,
overlaying the control line.
System Response
This example shows the system's response if you execute the LIMITS
run with mode 0, RID 2B on display:
5-4 UP-9662.5
CC Run—Displaying Horizontal Column Count
Positions
The CC run gives a horizontal column position count for a form type.
The column numbers appear in lines 2 and 3 of the screen. Since the
CC run is format sensitive, the column numbers are correct no matter
which format you display.
System Response
This example shows the system's response if you execute the CC run
with mode 0, RID 2B on display:
I
11111111112222222222333333333344444444445555555555666666666677777777778
12345678901234567890123456789012345678901234567890123456789012345678901234567890
*ST.STATUS.BY. PRODUCT .SERIAL.PRODUC.ORDER.CUST.PRODUC.PRODUC. SHIP .SHIP .SPC.
*CD. DATE .IN. TYPE .NUMBER. COST .NUMBR.CODE.PLAN .ACTUAL. DATE .ORDER.COD.
* •
where n is the line number on your display terminal where the column
count lines are to start.
UP-9662.5 5-5
FCC Run—Examining Report Fields
The FCC run displays field headers, the position of the first character
in each field, and the size of each field.
System Response
This example shows the system's response if you execute the FCC run
with mode 0, RID 2B on display:
2-2 12-2 25-6 32-6 39-5 45-4 50-6 57-6 64-6 71-5 77-3
5-6 15-9
END REPORT
5-6 UP-9662.5
FORM Run—Displaying Statement Fields and
Subfields
The FORM run displays the format of run statements (fields and
subfields). You get the @ control character, the function call, and the
abbreviated fields and subfields. It fills in all open function calls in
the report.
To execute the FORM run, type the function calls you want the formats
for in your run control report, and enter:
form
Example
@SRN
@SCR
@MCH
IDSP
END REPORT
UP-9662.5 5-7
FORM Run
System Response
END REPORT
5-8 UP-9662.5
FORMC — Creating Statements for Functions that
Use Function Masks
The FORMC run creates run statements for functions that use function
masks, as well as for RDC, RDL, and WRL.
❑ Roll the line with the desired statement to the top of the screen.
The function mask or masks appear on your screen. Fill in the options
and parameters and modify the mask, if necessary, just as you would
for the equivalent manual function.
For RDC, RDL, and WRL, fill in the variables in the desired fields.
The system writes the statements in your run control report. Modify
the statements as needed.
UP-9662.5 5-9
MARS — Creating Statements in Run Control Report
The MARS run creates MAPPER run statements and places them in a
run control report. If you don't have a run control report, the MARS
run adds one for you.
The MARS run is especially useful for capturing functions you use
repeatedly in a run control report. You can name the run and execute
it at any time. Call your coordinator for more information.
The MARS run prompts you for the information it needs to write the
run statements. It writes the statements in the run control report as it
creates them.
lars[4]
or
lars*[,rt]
where rt is the RID number and form type (if you already have a run
control report), and means use Directory field names instead of
column-character positions in affected statements.
❑ Enter the function call at the top of the menu after Enter call.
mars,help
If you have the MARS run menu on your screen and you want help
with any function, tab to the call you want help with and enter a .
5-10 UP-9662.5
RUN Run—Automatically Generating and
Registering Runs
The RUN run automatically generates a run as you perform the manual
functions. The manual functions appear to execute normally, but the
RUN run converts them to run statements and accumulates them in a
result.
When you finish typing the sequence of manual functions, you can
register the run statements accumulated in the result as a separate run
or you can append them to an existing run.
Or
You can now begin entering manual functions in the sequence in which
you want them saved as a run. Each function is converted into a run
statement until you exit the RUN run.
UP-9662.5 5-11
RUN Run
When you press F4 to end the automatic run generation, this screen is
displayed:
RUN
Place the cursor in one of the fields and press XMIT, or if you want to
register your run, enter the form type (B-1) in which to register it.
Field Description
Display the result Display the run as a result. If you want to return to
this menu, press Fl.
Execute it Execute the run that has been generated. Note that you
must press Fl for each DSP in the result. After the run
has finished executing, the menu is redisplayed.
Register it in Type Place the generated result in the form type you specify
and register it as a run. The run name is your user-id
and only you can execute it. Because the system deletes
any runs previously generated with the same name, you
may want to ask your coordinator to change the name.
* Note that the RUN run may be restricted on some systems; contact your coordinator if you have
problems registering the run.
5-12 UP-9662.5
RUIN Kun
A Arithmetic
AL Alarm
CALL Interactive message switching
CUT (PASTE) Cut (Paste)
LANG Language
LZ Line Zero
PC Phrase Change
PL Phrase Locate
PUNCH Punch
PSW Password
RPSW Read Password
RSI Remote Symbiont Interface
(demand mode)
SP Spelling Check
SS Station-to-Station Message
WP Word Process
OK Acknowledge a message
UP-9662.5 5-13
RUN Run
These functions work when you are entering them as manual functions,
but do not generate run statements:
FUN Function
L Line Control
PNT Paint
RSM Resume
T Type
The RUN run does not generate a DSP statement for each function
result. For example, if you execute the S (Search), SORT (Sort), and
TOT (Totalize) functions, the generated run statements are entered into
your run and only the final result is displayed. If you want your run
to display each result, enter d - after each result is displayed.
You can also display a result at a specified line number and in any
format. To display the result at a specific line, roll the line to the top
of the screen. To display the result in a different format, enter the
format in the control line. Remember to enter d - if you want your run
to display this result.
5-14 UP-9662.5
RUN Run
LIMITATIONS
❑ You can use only the first three control line fields: LINE, FMT,
and RL. The system ignores the others.
❑ The system does not save the report number produced by the AR
(Add Report) or XR (Duplicate Report) function. The report
becomes the current result (-0) for further processing.
❑ You cannot generate output screens or obtain user input from any
other source (for example, by using the reserved words INPUT$ or
INVAR$).
UP-9662.5 5-15
RUNA Run—Analyzing Your Run
Even if your run passes the RUNA run analysis satisfactorily, it may
not be ready for use in production. Your coordinator must still
approve your run.
The RUNA run has its own built-in online HELP. To read it, enter:
runa.
or
runa,help
(Note that if you enter without a log list on display, you get the
RUNA run's online HELP.)
Before executing the RUNA run against your own run, do the
following:
❑ Make sure you have a LOG statement (see LOG) at the beginning of
the run (but after the label table, if there is one).
❑ Replace the REL statement (if used) with a GTO END statement to
keep the log list intact after the run completes.
5-16 UP-9662.5
RUNA Run
At this point, you can print the result, or go to the next step.
❑ If you don't want to print the result, you can press Fl to return
to the log list.
UP-9662.5 5-17
6. Designing and Debugging Runs
Before writing a run, it's important to know how to handle reports and
results. In addition, you should follow a step-by-step procedure in
creating your run. Finally, you need to know some debugging methods
in order to create an error-free run.
UP-9662.5 6-1
Handling Reports and Results
You can process several reports in a single MAPPER run. The simplest
run acts on a report or result from a previously executed function and
produces a result or updated report, as shown in this figure:
/Report/Result
Input
Run
Report/Result
Output
You can use several reports and results from different modes for input,
provided your coordinator has registered the modes for access. This
figure shows a run using reports and results from different modes:
Run
6-2 UP-9662.5
Handling Reports and Results
The output area is a temporary scratch area that you build in your run
control report to hold information. This information is composed of
output lines, which are lines of data that do not have @ signs or colons
in column one (and are not continuations of run statement lines). They
may be, for example, messages or special screen displays you create that
you want to display later in the run.
To examine the output area at any time during the run, enter a GTO
END statement. This displays the contents of the output area as a
result.
You can use output area data as a result at any time by executing a
BRK statement (see BRK in Section 7). The BRK statement places the
output area into the current result and clears the output area. You can
then use the DSP or OUT statement to display the result. The output
area is now empty, so you can place new data in it.
RESULTS
To access results, specify the result identifier (the renamed result, such
as -1, or the current result, -0) in the appropriate subfields of a
MAPPER run statement. To access a report or result on display before
the run started, refer to it as -0 until your run creates another result.
UP-9662.5 6-3
Handling Reports and Results
Do not confuse the output area with a result. You create a result using
a function or run statement, such as SRH or TOT. You create the
output area by adding output lines to your run control report. You can
create an output area without affecting the current result or previously
renamed results.
The following figure shows how runs use the output area and results:
Run
Output
,.__ Area ....„i
/ Results Result
/
For more detailed information about the output area and results, see
the Run Design Training Guide.
6-4 UP-9662.5
Designing and Registering a Run
When you're ready to write a MAPPER run, follow this logical step-by-
step procedure:
START
/
STATEMENT
1
STATEMENT
2
STATEMENT
3
STATEMENT
4
I
EN
UP-9662.5 6-5
Designing and Registering a Run
If you're unsure what effect a run statement has in a run, you can
usually test the statement by running it separately. If it uses a
manually executable processing function, test it manually first.
3. Enter the required run statements in the run control report. With
manual updating, natural pauses between transmissions disperse
the processing load; but in a run, where the statements are
executed rapidly one after the other, virtually no pauses occur
between the execution of statements. A run that executes several
individual functions may put a severe load on the MAPPER
system. You should consider loading effects of the run and adjust
run user response expectations accordingly.
After accepting your run and obtaining a final log list, your
coordinator registers it by its name. The coordinator may restrict
user accessibility, mode accessibility, time of execution,
input/output quantity, logic line count, and station numbers for
your run.
6-6 UP-9662.5
Designing and Registering a Run
5. You should give the run control report a report password and a
save flag in this format:
.vpyyhandd
The save flag must start in the first column of line 2 (the line
below the date line) and must be a period line (notice the period
beginning in column 1).
UP-9662.5 6-7
Debugging Your Run
There are several methods you can use to debug your run:
❑ Interactive debugging
❑ HELP run
❑ Checkpoint displays
INTERACTIVE DEBUGGING
When your run is halted because of an error, you see a one-line error
message and the erring run statement line at the top of the screen. You
can interactively correct the error instead of returning to the run
control report. This technique works well for simple errors, such as an
incorrect form type or variable name.
With the halted run on display, correct the erring line, move the cursor
to the end of the line and press XMIT. The change is added to your
run control report. To test the corrected run, execute it again.
You can also use the HELP run to debug your run. When the run stops
because of an error, an error is displayed on the control line. If you
need more information, enter .ie1p to show a screen with a detailed
explanation. Press Fl or enter rsm when you are ready to continue.
The screen shows the line where the error occurred.
6-8 UP-9662.5
Debugging Your Run
CHECKPOINT DISPLAYS
If your run has several stages of processing, add DSP (Display Report)
run statements to display intermediate results. You can check the
results to see if the previous run statements have executed properly. If
you write your run in modules, where each module performs a specific
task, you can easily run each module with a checkpoint display to test
it. As you debug the run, take the checkpoint displays out.
You can use the RDB (Run Debug) function or run statement to debug
your run while it executes. This is different from interactive
debugging because you can do the following:
See "Using RDB (Run Debug)" in this section for more information.
UP-9662.5 6-9
Using RDB (Run Debug)
The RDB utility is a powerful run design tool. Use it to debug your
run interactively, examining the contents of variables, reserved words,
and renamed reports and results —all as the run is being executed. You
can step through the run one line or command at a time, or you can set
a breakpoint to halt the run at a specific line number, label, run
command, or variable.
You can use RDB manually or in a run. In either case, you must be a
registered run designer and the last person to update the run control
report; otherwise, the RDB request is ignored.
To use the manual function, this is the format to enter on the control
line:
RDB run(,v v]
In field: Enter:
@RDB .
6-10 UP-9662.5
Using RDB
If you use the manual function, the run halts before executing line 3 of
the run control report and displays a screen. If you use the run
statement, the run halts when it encounters the RDB statement and
displays a screen. The following example illustrates the lines from the
screen that is displayed:
RDB
RUN=testrun MODE=0 RID=2E
❑ The first line is the RDB prompt line; you enter RDB commands
after the SOE (►) on this line.
❑ The second line is the RDB Status Line. It displays the run name,
mode number, report name, and other information.
❑ The fourth line contains the line in the run control report to
execute. It contains the line number and up to 70 characters of the
line (up to 122 characters on a 132-character terminal). If you used
the manual function, this line contains the first line (line 3) of the
run control report. If you used the RDB run statement, this line
contains the line in the run control report following the RDB
statement.
The lines that follow the fourth line of the screen contain subsequent
run statements as they are executed. Whenever a run halts, the next
statement to execute is always the bottom line on the screen.
UP-9662.5 6-11
Using RDB
RDB COMMANDS
You execute RDB commands by entering information on the RDB
prompt line or by pressing function keys. Table 6-1 describes the RDB
commands.
(continued)
6-12 UP-9662.5
Using RDB
(continued)
UP-9662.5 6-13
Using RDB
(continued)
6-14 UP-9662.5
Using RDB
RDBI@LDV V114=1234 .
UP-9662.5 6-15
7. Run Statements
UP-9662.5 7-1
List of Statements by Name
Name Call
7-2 UP-9662.5
List of Statements by Name
UP-9662.5 7-3
List of Statements by Name
7-4 UP-9662.5
List of Statements by Name
UP-9662.5 7-5
Statements with No Corresponding Manual
Function
7-6 UP-9662.5
Functions and Statements
UP-9662.5 7-7
Add (Append Report)
The ADD statement appends the issuing report to the end of the
receiving report and creates a result.
If the receiving report has longer lines than the issuing report, the
system fills the lines in the issuing report with spaces. If the receiving
report has shorter lines, the system truncates the lines in the issuing
report.
Format
@ADD,im,it,ir,rm,rt,rr .
In field: Enter:
im,it,ir the mode, type, and RID number of the issuing report.
rm,rt,rr the mode, type, and RID number of the receiving report.
Example
@ADD , 0 , B , 2 , 0 , B , 1
@OSP , - 0 .
7-8 UP-9662.5
ADR (Add Report)
The ADR statement adds a new report in a specified form type. You
can specify the number of the report to be added. If you specify a
report number, that report is added, provided that it does not already
exist. If it does exist, the run continues at the label or relative line
number specified; if you did not specify a label or line number, the
run errs.
If you don't specify a report number, the MAPPER system selects the
next available report number in the form type and puts the RID
number in R1D$.
Format
@ADR,m,d,rjab] .
In field: Enter:
UP-9662.5 7-9
ADR
Reserved Word
Word Content
@ADR.0.8 .
@ILDV,PW <RID>13=RID$
The following example adds RID 10B to mode 0. The run goes to label
99 if 10B already exists or if type B is full.
@ADR.0.13,10.99 .
7-10 UP-9662.5
ART (Arithmetic)
Format
In field: Enter:
UP-9662.5 7-11
ART
OPERATORS
Table 7-1 lists arithmetic operators that you can combine to form an
expression.
NOTE: Values a and b are real integers and numbers and can include
decimal fractions or expressions composed of such numbers.
7-12 UP-9662.5
ART
Example
This statement raises 3 to the 4th power, divides the result into 2, and
places the answer in VI:
MULTIPLE EXPRESSIONS
Evaluating multiple expressions in a single statement is more efficient
than using a separate ART statement for each expression. This example
adds V33 to V34 and puts the answer in V36I3. It then subtracts V34
from V33 and puts the answer in V37I3. Note that a semicolon (;)
separates the expressions.
UP-9662.5 7-13
ART
INTERNAL COMPUTATION
NEGATIVE NUMBERS
If it's 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:
7-14 UP-9662.5
ART
Function Description
UP-9662.5 7-15
AUX (Auxiliary)
Format
@AUX,m,t,r,sn,devLdlnos?,f,tabs?,dhdrs?,d1char?,Isp,transp?,unit,s1,spcc] .
In field: Enter:
(continued)
7-16 UP-9662.5
AUX
( continued )
In field: Enter:
Example
This statement prints RID 2B, mode 0, at station 123, on device name
COP, with deleted line sequence numbers, deleted headers, and double
spacing:
@AUX.0,13.2,123.COP.Y.„Y.,2 .
UP-9662.5 7-17
BFN (Binary Find)
The BFN statement finds items very quickly in a sorted list. It does so
by sampling the data at midpoint in the report or series of reports to
determine whether or not the data to find precedes or follows this point
(thus, the term "binary"). BFN ignores blank lines within the report. It
continues sampling, dividing, and sampling until it finds the first
occurrence of the data. With the N or 0 option, it creates a result.
The data in a report must be sorted on the fields the find is to be done
on. If you want to perform a binary find on a range of reports, make
sure the data is sorted across all reports.
If you specify a range of reports, make sure there are no empty reports
(containing no valid data or headers 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 error message is
supplied because a valid find is made.
. 7-18 UP-9662.5
BFN
Format
o cc ltyp,p [vrid,vinol .
In field: Enter:
m,t,r the mode, type, and RID number of the report to scan.
o options:
(continued)
UP-9662.5 7-19
BFN
(continued)
In field: Enter:
7-20 UP-9662.5
BFN
(continued)
In field: Enter:
UP-9662.5 7-21
BFN
(continued)
In field: Enter:
7-22 UP-9662.5
BFN
(continued)
In field: Enter:
UP-9662.5 7-23
BFN
Reserved Word
Code Error
where:
7-24 UP-9662.5
BFN
The following example uses the Q option and captures the line number
where the find was made in <LINE>:
where:
UP-9662.5 7-25
BLT (Build Label Tables)
Use a BLT statement to build label tables in a run control report and
create a result.
At the start of a run, label tables indicate on which lines labels are
located in the run control report. When the run reaches a statement that
directs it to a label, the run already knows where the label is. This
saves on overhead.
You can use the BLT statement to implement label tables in a database
made up entirely of runs. Label tables increase the efficiency of runs
with GTO statements that branch to labels (see GTO).
A new BLT statement in a report clears any old label tables before
creating new ones.
NOTE: You will most of ten use the manual BLT function rather than
the run statement. To use the manual function, simply
display your run control report, enter bit, and replace the
result. See the Manual Functions Reference for more details.
Format
@BLT,m,t,r[,1ab] .
In field: Enter:
m,t,r the mode, type, and RID number of the run control report
to build label tables in.
7-26 UP-9662.5
BLT
Example
@BLT,O,E,10,99 .
where:
UP-9662.5 7-27
BR (Background Run)
When you execute a BR statement, the system removes the current result
(-0) from your run, if one exists, and passes it to the background run.
Your original run continues executing.
Format
@BR[,snjab] run[,vId] .
In field: Enter:
7-28 UP-9662.5
BR
Reserved Word
Word Content
ORSTAN$ Station number from the BR statement that started the run, or originating
station number if not supplied in the BR statement. ORSTAN$ always equals
zero for nonbackground runs.
Example
@BR.123,99 K1SMET,USER$ .
UP-9662.5 7-29
BRG (Break Graphics)
Use a BRG statement to pack data in the output area and place it into
a result. It is particularly useful for packing primitive graphics code
and processing the result with MAPPER chart runs. The BRG
statement packs leading and trailing spaces from a single line, but does
not pack spaces embedded within the line.
The BRG statement is similar to a BRK statement (see BRK). When the
run encounters a BRG statement, it places all data in the output area
into a scratch result (-0) and clears the output area.
If you don't specify a mode and type for the output area, they are the
same as those of the run control report. You can change the mode and
type of the output area with a BRG statement without affecting the
current result. You do, however, change the mode and type of the
output area for subsequent results created by another BRG statement.
Format
@BRGLm,t,q] .
In field: Enter:
m,t the mode number and form type of the output area. The
t field is required if you specify a mode.
7-30 UP-9662.5
BRG
In this example, the first BRG statement places the current output area
into a scratch result. (Note that a BRK could also be used here.) The
primitive graphics code then becomes the current output area in the
same mode and type as the run control report. The second BRG
statement packs the primitive code and places it into a result that can
be processed by MAPPER chart runs.
@BRG .
@BRG .
This statement places the output area into a result and estimates that
the following output area will be 2,500 lines:
@BRG„2500 .
This statement places the output area into a result. The next output
area will reside in mode 2, type B.
@IBRG.2,8 .
UP-9662.5 7-31
BRK (Break)
Use a BRK statement to place the run's output area into a result. The
run builds the output area automatically (see Section 6 for more
details).
When the run encounters a BRK statement, it places all data in the
output area into a scratch result (-0) and clears the output area.
If you don't specify the mode and type for the output area, they are
the same as those of the run control report. You can change the mode
and form type of the output area with a BRK statement without
affecting the current result. You do, however, change the mode and
form type of the output area for subsequent results created by another
BRK statement.
Format
@BRIO,m,t,q1 .
In field: Enter:
m,t the mode number and form type of the output area. The
t field is required if you specify a mode.
7-32 UP-9662.5
Example
1. @BRK .
DATA1
2. @BRK , 0 , B .
DATA2
3. @BRK „ 2500 .
DATA3
4. @BRK .
1. The output area that follows resides in the same mode and type as
the run control report.
2. DATA] is now the -0 in the same mode and form type as the run
control report; the output area that follows resides in mode 0, type
B.
UP-9662.5 7-33
CAL (Calculate)
Format
In field: Enter:
options:
(continued)
7-34 UP-9662.5
CAL
(continued)
In field: Enter:
(continued)
UP-9662.5 7-35
CAL
(continued)
In field: Enter:
(continued)
7-36 UP-9662.5
CAL
(continued)
In field: Enter:
(continued)
UP-9662.5 7-37
CAL
(continued)
In field: Enter:
Ityp the line type to process. (If you specify the A option,
leave this subfield blank.)
receiving-label Loptionsi=expression1; .
where:
(continued)
7-38 UP-9662.5
CAL
(continued)
In field: Enter:
partial-receiving-label=receiving-label( x-y)
option,
expression!:
UP-9662.5 7-39
CAL
Reserved Words
Word Content
STAT1$ Number of lines processed (i.e., number of lines of line type specified)
If you use apostrophes in a CAL statement, use TICS if the run control report
is in Limited Character Set (LCS). Use TICS or quotation marks (") for FCS and FCSU
reports.
Second ** Exponentiation
7-40 UP-9662.5
CAL
Table 7-5 shows the priority by which the MAPPER system evaluates
relational operations.
<= or =< Compare not greater than (Less than or equal to)
>= or => Compare not less than (greater than or equal to)
Third OR (Boolean)
NOTE: The operators ampersand and comma (& and ,) don't perform
a numeric comparison, but are based on a true/false concept.
UP-9662.5 7-41
CAL
Table 7-6 shows the result of all possible true/false conditions. value]
and value2 are usually relational expressions (such as a>1000).
Function Description
7-42 UP-9662.5
CAL
(continued)
Function Description
DEF(field-label)
UP-9662.5 7-43
CAL
The contents of a report field can include either just the characters indicated or both the characters
indicated and spaces.
IF:expression1; . . .
and:
THEN:equationi; . .
and:
ELSE:equationt; . .
7-44 UP-9662.5
CAL
Using the DATE functions, you can process dates from January 1, 1944,
through December 31, 2043.
Using the TIME functions, the CAL statement translates times into
numbers of hours relative to midnight. You can also process minutes
and times in computations; just convert them into hours by dividing
minutes by 60 and seconds by 3,600. All times are based on a 24-hour
clock.
There are two constant labels, which you can use directly in equations
when you want to perform calculations or comparisons with the current
date or time:
UP-9662.5 7-45
CAL
Input Functions
Dn(x)
where:
Tn(x)
where:
7-46 UP-9662.5
CAL
Output Functions
receiving-label,D(x)=expression
where:
receiving-label,T(x)=expression
where:
UP-9662.5 7-47
CAL
If you specify a receiving label that is not large enough to contain the
output format or if the result value of the expression isn't a valid time,
CAL fills the field with asterisks (*) and assigns it a value of zero.
Table 7-9 shows all available input and output formats for dates and
times. The Min Size field specifies the minimum number of columns
required to display that specific format.
7-48 UP-9662.5
CAL
UP-9662.5 7-49
CAL
In addition to the date and time equation options (Dn and Tn), you can
use one of two W options in your equations:
You can use the ICAL run to create a CAL statement. For information
on how to use the ICAL run, see the Manual Functions Reference.
CAL EXAMPLES
NOTE: All CAL examples except the last one process tab lines in RID
IC, mode 0.
7-50 UP-9662.5
CAL
where:
9.1
Use no options.
The following example moves all values that exceed 24,000 from one
field into another field:
where:
99
Use no options.
UP-9662.5 7-51
CAL
where:
The following example uses CAL in an LCS run control report. (Notice
the apostrophes around the string BLACKBOX; these are necessary for
the MAPPER system to distinguish between the string and the reserved
word TIC$):
7-52 UP-9662.5
CAL
Here is the same example using an FCS/FCSU run control report. (Note
that if the string contained a space, it would need to be enclosed in
apostrophes as well as quotation marks.)
where:
UP-9662.5 7-53
CAL
where:
7-54 UP-9662.5
CAL
where:
UP-9662.5 7-55
CAR (Clear Abort Routine)
Format
@CAR .
7-56 UP-9662.5
CAU (Calculate Update)
Format
In field: Enter:
m,t,r the mode, type, and RID number of the report to process.
(continued)
UP-9662.5 7-57
CAU
(continued)
In field: Enter:
eceiving-label Loptions1=expressionr; . . . I
where:
(continued)
7-58 UP-9662.5
CAU
(continued)
In field: Enter:
options
expressionl; .
Reserved Words
Word Content
STAT1$ Number of lines processed (i.e., number of lines of line type specified)
UP-9662.5 7-59
CAU
Example
where:
7-60 UP-9662.5
CER (Clear Error Routine)
Format
@CER .
UP-9662.5 7-61
CHD (Command Handler)
The command handler routine can be in the same run control report
(internal) or in another run control report (external). External
command handler routines must be in the same character set type as the
calling run control report.
NOTE: Don't use the CHD statement unless you're an advanced run
writer. Its use is intended primarily for intercepting and
interpreting commands that normally go to MAPPER software.
Whenever a run user transmits with the cursor on the control line, the
run continues at the label for the report specified in the CHD
statement and cancels any active subroutines. For example, if a
subroutine contains a DSP, OUT, or SC statement, an ESR statement
won't work (see ESR).
7-62 UP-9662.5
CHD
Format
@CHD[,m,t,r,rel?] lab .
In field: Enter:
lab the label where the command handler routine starts (use 0
to cancel the currently registered command handler
routine).
You can also put a line number in the lab field. For
external routines, use the absolute line number (LIN n,
where n is 1 or greater); for internal routines, use the
relative line number (LIN nI LIN -11).
UP-9662.5 7-63
CHD
Reserved Words
ICVAR$ works only with a CHD statement; FKEY$ works with a CHD or KEY statement
Word Content
ICVAR$ Captures user input from the control line. Remember to put ICVAR$ before
the variable in the CHG statement, and put the CHG statement before the
DSP, OUT, or SC statement. If you specify Y in the forced transmit
(fxmit?) subfield of an OUT statement, it has the same effect as pressing
XMIT. If the cursor is on the control line, it also affects ICVAR$ input.
You should use string variables (type S), but you can use type A or type H
variables if the data fits in them. The system copies all input (except
leading tab characters) into the specified variable up to the end of the
variable.
Other reserved words used to capture input (INMSV$, INPUTS, INSTR$, INVAR$,
and INVR1$) are not affected if the user transmits with the cursor below
the control line.
FKEYS You can find out which key the user pressed with the reserved word FKEYS,
whose value is always 0 if a CHD or KEY statement hasn't been used.
Whenever the user presses a function key, the run continues executing at
the statement following the DSP, OUT, or SC statement--not in the CHD
routine--and FKEY$ contains a number indicating the key pressed:
7-64 UP-9662.5
CHD
Examples
If the user presses XMIT from the control line, go to label 52 in this
run control report:
@CHD 52 .
If the user presses XMIT from the control line or enters a release
character, go to label 100:
@CHD„,Y 100 .
If the user presses XMIT from the control line, go to the current line
plus 3 in this run control report:
@CHD LIN +3 .
@CHD 0 .
@CHD 10 .
@CHG ICVAR$ V1S80
@CHG INVAR$ V2Al2,V3A8
@OUT,O,A,-0,2,1,„Y .
@CHG V412 FKEY$ .
@IF V4 = -1,(20),0,(30),1,(40),2,(50),3,(60),4,(70)
❑ If the user presses XMIT from the control line, the run goes to label
10, with VI capturing command input (entire control line).
If the user presses MSG WAIT, the run goes to label 20.
❑ If the user presses XMIT with the cursor below the control line, the
run goes to label 30, with V2 or V3 capturing data input.
UP-9662.5 7-65
CHD
7-66 UP-9662.5
CHG (Change)
Also use a CHG statement for simple arithmetic computations. You can
add, subtract, multiply, divide, and integer divide numbers or the
contents of variables.
Format
@CHG v vld .
In field: Enter:
Examples
UP-9662.5 7-67
CHG
The following statement creates V3 from the computation. Note that the
CHG statement evaluates the computations from left to right.
@CHG V316 5 / 2 .
@CHG V316 5 // 2 .
@CHG V3F5.2 5 / 2 .
NOTE: Precede and follow each operator (+, *, /, //) with a space.
Put reserved words that capture user input be fore the variable. These
reserved words capture user input:
Here's an example:
7-68 UP-9662.5
CHG
A logical AND
0 logical OR
X exclusive OR
L left shift
R right shift
C circular shift
@CHG V104 2 .
@CHG V1 V1 A 7 .
@CHG V1 V1 C -1 .
UP-9662.5 7-69
CLK (Clear Link)
Format
@CLK .
7-70 UP-9662.5
CLT (Clear Label Tables)
Use a CLT statement to delete label tables in a run control report and
create a result.
NOTE: You will most of ten use the manual CLT function rather than
the run statement. To use the manual function, simply
display your run control report, enter clt, and replace the
result. See the Manual Functions Reference for more details.
Format
@CLT ,m,t,r[lab] .
In field: Enter:
m,t,r the mode, type, and RID number of the run control report
in which to clear label tables.
UP-9662.5 7-71
CLT
Example
@CLT,O,E,10,99 .
where:
7-72 UP-9662.5
CLV (Clear Variables)
Format
@CLII,stvno,q1 .
In field: Enter:
Examples
@CLV , 1 . 1 0 .
@CLV .
UP-9662.5 7-73
CMU (Commit Updates)
Use a CMU statement after a DFU statement if you want to commit the
updates made since the DFU statement executed.
Format
CMU .
7-74 UP-9662.5
CPY (Copy)
If the receiving file does not exist, the Executive System (Exec) creates
it with a maximum granularity of 6400 tracks.
Format
In field: Enter:
0 options:
A Absolute element
O Omnibus element
R Relocatable element
S Symbolic element
(continued)
UP-9662.5 7-75
CPY
(continued)
In field: Enter:
Example
7-76 UP-9662.5
CSR (Clear Subroutine)
Once you use a CSR statement, you can no longer return to the calling
run control report. You must use a CSR statement in the external
subroutine run control report before calling another external
subroutine. (See also RSR.)
Format
@CSR .
UP-9662.5 7-77
DAT (Date)
Format
@DAT,m,t,r o cc Ityp,p .
In field: Enter:
options:
(continued)
7-78 UP-9662.5
DAT
(continued)
In field: Enter:
the parameters:
A ymmdd + add
B yymmdd subtract
C dd mmm yy = move result to this field
D yddd K constant (integer)
E yyddd place day of week here
F ddmmyy
G mm/dd/yy
I mmddyy
UP-9662.5 7-79
DAT
or:
where:
Use no options.
7-80 UP-9662.5
DAT
where:
Use no options.
UP-9662.5 7-81
DC (Date Calculator)
Format
@DC eq vrslts .
In field: Enter:
For each date you use in an equation, specify its format first. Enter
dates in this format:
Dn (x)
where:
7-82 UP-9662.5
DC
Tn (x)
where:
UP-9662.5 7-83
DC
Your answer appears in the same format as the date you use in the
equation, unless you specifically change the format.
(DIT)(n1w).-:expression
where:
is the date.
is the time.
Examples
7-84 UP-9662.5
DC
V1 equals the day of the week that January 25, 1980, was; V2 equals
850125 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:
@LDV V516=831007 .
@OC D1(V5)+60;DW=A;D7=A;C-2 V116.V2H10,113H18.1/4H18 .
UP-9662.5 7-85
DCPY (DDP Copy)
Format
@DCPYLIabl host,fn,rhostin,typel,pos,transl] .
In field: Enter:
(continued)
7-86 UP-9662.5
DCPY
(continued)
In field: Enter:
(continued)
UP-9662.5 7-87
DCPY
(continued)
In field: Enter:
These are the valid entries (you need to specify only the
first three characters):
Please refer to the DDP-FJT Operations Guide, Vol. 1: IPF Interface for
more information about each field of the DCPY run statement.
Reserved Words
The reserved words STAT1$, STAT2$, and STAT3$ contain error codes.
These codes are listed in the DDP-PPC/DDP-FJT Messages Reference
Manual.
Word Content
STAT2$ CLASS-CODE
7-88 UP-9662.5
DCPY
Example
This statement copies all symbolic elements from the file A*B. located
on host RSL2 to the file D*E. on host TOC. The elements replace any
existing elements on host TOC. If there was an error in the statement
or DDP configuration, STAT1$, STAT2$, and STAT3$ contain the
status code and the label 1 exit is taken.
fOCPY.1 RSL2,'A*B.',TOC.'D*E.',SYM,REP .
UP-9662.5 7-89
DCR (Decode Report)
Use a DCR statement to decode a report that has been encoded with the
ENCODE function or ECR run statement (see ECR). The decoded report
becomes the current (-0) result.
Use caution when encoding and decoding reports. Here are some
important things to remember:
❑ 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. In addition, you may not be able to decode a
report that contains special NCS characters from a normal ASCII
terminal.
7-90 UP-9662.5
DCR
Format
@DCR,m,t,r,key .
In field: Enter:
m,tl the mode, type, and RID number of the report to decode.
Examples
This statement decodes RID 10B of mode 0, which was encoded using
the key JMT6077:
WR,O,B,10.0.4T6077 .
UP-9662.5 7-91
DCRE (DDP Create)
Format
In field: Enter:
host the name of the host configured in DDP 1100 where the
file is to be created or allocated. Specify the host
here as you specify it in the IPF environment.
J..
the name of the file to be created or allocated. If the file
name contains special characters, enclose the field in
single quotation marks.
init the initial file size in bytes. (Default = 0.) Note that on
an 1100 host, this number multiplied by the granularity
and divided by 7168 gives the number of tracks to
allocate.
gran the granularity of the file that specifies the size (in 9-bit
bytes) of the units used in the hilt and maxfz subfields.
(Default = 7168 bytes, which is one track.)
(continued)
7-92 UP-9662.5
DCRE
(continued)
In field: Enter:
access the access type for the file (you need to specify only the
first three characters):
Please refer to the DDP-FJT Operations Guide, Vol. 1: IPF Interface for
more information about each field of the DCRE run statement.
Reserved Words
The reserved words STAT1$, STAT2$, and STAT3$ contain error codes.
These error codes are listed in the DDP-PPC/DDP-FJT Messages
Reference Manual.
Word Content
STAT2$ CLASS-CODE
UP-9662.5 7-93
DCRE
Example
This statement creates the file A*B in host RSL2 on an 8450 disk with
a movable head. The file is public and has an initial size of 10 tracks
with a maximum of 500 tracks.
@OCRE.1 RSL2,'A*B.',F50M.10..500„PUB .
This Exec control statement creates the same file in a batch or demand
program:
@CAT,P A*B.,F50M/10/TRK/500 .
7-94 UP-9662.5
DCU (Decommit Updates)
Format
@Dcu .
UP-9662.5 7-95
DEC (Decrement Variables)
You cannot use a DEC statement with string (type S) variables. Also, if
the variable you're trying to change contains alphabetic or special
characters, the variable remains unchanged. A DEC statement is more
efficient than a CHG statement, and it requires fewer characters.
Format
qp,DECi,n1 v I,v,...v] .
In field: Enter:
Example
@DEC V3 .
instead of:
@CHG V3 V3 - 1 .
@DEC,5 cCOST>,<TOTAL>
7-96 UP-9662.5
DEF (Define)
Format
In field: Enter:
(continued)
UP-9662.5 7-97
DEF
(continued)
In field: Enter:
A 1
F 2
S 3
I 4
H 5
O 6
(continued)
7-98 UP-9662.5
DEF
(continued)
In field: Enter:
Note that the contents of testy can include either just the
characters indicated or both the characters and spaces.
UP-9662.5 7-99
DEF
Examples
@DEF V1 V2
This statement sets V5 to equal the alphabetic form type of the valid
numeric form type in V6:
@DEF,A V5A1,V6 .
@DEF,V V199H12 V1 .
7-100 UP-9662.5
DEL (Delete)
CAU
LCH (with the OU option)
LOC (with the OU option)
MAU
SRU
Format
@DEL .
Examples
In this example, the SRU statement searches tab lines for IP in column
2 for two characters. The DEL statement deletes all lines found in the
search update from the report:
To save a logic line, put both statements on one line, as in this example:
UP-9662.5 7-101
DEV (Device)
The DEV statement lists auxiliary devices and their status for a
specified station. It creates a type A result if the device type you
specify exists at the station number specified, and you do not specify a
unit name.
Format
@DEV,snLdev,unit,lab] .
In field: Enter:
C printers
D 5 1/4" diskette
T tape cassettes/diskettes
If you use the dev field, you must also use the unit field.
7-102 UP-9662.5
DEV
Reserved Words
Word Content
Examples
@DEV.123,C.COP.99
UP-9662.5 7-103
DFU (Defer Updates)
If the run fails or aborts, the system restores all updates to the reports
to their state before the DFU statement.
If the system fails during a run before the CMU statement executes,
associated report updates are also decommitted.
You can control up to five reports with a DFU statement. Follow each
DFU statement with a CMU or DCU statement before specifying
another DFU statement.
If your run terminates for any reason, the system executes a DCU
statement automatically and terminates the run with an error. Once a
DFU statement executes, you must decommit or commit updates before
you end a run normally.
You cannot specify just the mode and type in an attempt to lock an
entire type.
7-104 UP-9662.5
DFU
Format
@DFUllabi .
In field: Enter:
Example
@DFU,99 0,6,2.0.C.1 .
UP-9662.5 7-105
DIR (Directory Information)
Use the DIR statement to load 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 (mode, form type, or
report).
Format
In field: Enter:
name the data name to define. The data name can include
nonsignificant characters, such as spaces or punctuation.
The name need not be enclosed within apostrophes unless
it contains embedded spaces.
vhiridr * the variable to capture the higher RID number if the data
name defines a range of reports.
* A data name can represent a mode, a form type, a report, or a range of reports. Variables that do not
apply for a particular data name are loaded with spaces.
7-106 UP-9662.5
DIR
Reserved Word
If the data name supplied is invalid, the run continues at the label.
Examine STAT1$ for error codes. If there is no label, the run errs.
Code Error
Example
where:
UP-9662.5 7-107
DIR
7-108 UP-9662.5
DIS (Diskette)
Use a DIS statement to write data to and read data from a 5-1/4-inch
diskette drive connected to a Unisys UTS 30 display terminal.
Format
@DIS.m,a,r,f,labl code,dev,fn[,ext,tabs?,hdrs?,transp?1 .
In field: Enter:
(continued)
UP-9662.5 7-109
DIS
(continued)
In field: Enter:
Reserved Word
,
Ree'rVed Word: STAT1$ (error codes)
Code Error
If you don t use a label, the run terminates and you get an error message (unless you
have an RER statement in the run to register an error routine).
7-110 UP-9662.5
DIS
Example
@OIS,0,B,2 W,DS1,FILE1 .
UP-9662.5 7-111
DLL (Downline Load)
Format
@DLL,m,t,r,trfadr,deitproglab] .
In field: Enter:
Example
This statement downline loads the program in RID 10A into the
terminal's memory and transfers control to address A018 after loading:
@OLL,O,A,10,A018,MEM .
7-112 UP-9662.5
DLR (Delete Report)
Format
@DL R,m,t,r[jab] .
In field: Enter:
Examples
The following statement deletes the current result; the run goes to label
99 if the result does not exist:
@OLR,-0,99
UP-9662.5 7-113
DPUR (DDP Purge)
❑ You can remove all evidence of a file's existence with the DPUR
statement.
❑ You can delete only one file with each DPUR statement.
❑ You can use the DPUR statement to delete only entire program or
data files; you cannot delete elements of a file.
Format
@DPUR[Jabl host,fn .
In field: Enter:
host the name of the host configured in DDP 1100 where the
file is to be deleted or purged. Specify the host here as
you specify it in the IPF environment.
7-114 UP-9662.5
DPUR
Reserved Words
The reserved words STAT1$, STAT2$, and STAT3$ contain error codes.
These error codes are listed in the DDP-PPC/DDP-FJT Messages
Reference Manual.
Word Content
STAT2$ CLASS-CODE
Example
UP-9662.5 7-115
DSG (Display Graphics)
NOTE: The DSG statement clears the output area after executing.
Format
@DSG,m,tAdisplay,interim?„sn,labl .
In field: Enter:
m,t,r the mode, form type, and RID number of the report
containing the primitive graphics code.
7-116 UP-9662.5
DSG
If you do not specify lab and the DSG statement cannot be successfully
completed, the run is terminated with an error. Examine STAT1$ for
the status code.
Reserved Word
Code Error
3 Either no one is signed on at the specified station and interim was not
specified, or the terminal is not a graphics terminal.
4 There is no answer. The user at the specified station did not respond to
the message wait signal within one minute.
When you send a DSG to another terminal where a user is signed on,
that user's message wait signal is activated and your run stalls. If the
user responds to the message wait signal, the DSG information is
displayed on the user's screen. If you specified N in the interim?
subfield, your run stalls until the user at the receiving terminal presses
any key; if you specified Y in the interim? subfield, your run continues
automatically.
UP-9662.5 7-117
DSG
If the user at the other terminal does not respond within one minute,
your run either continues at the specified label or terminates with an
error (STAT1$=4). If subsequent DSGs are sent to that station, the user
must respond to each message wait signal.
You cannot obtain exclusive use of any station. When more than one
run is sending a DSG to the same station, the outputs may be
intermixed and not displayed in the same order as they were sent. In
addition, the one minute time limit may elapse for the second DSG
before the first DSG is completed.
Examples
This statement displays text from the primitive graphics code in RID
1A, mode 0. The user must press Fl or enter rsm to continue:
00SG,O,A.1 .
The following statement displays text and graphics from the primitive
graphics code in RID 2B, mode 0. The run continues automatically:
alOSG.O.B.2.M.Y .
WSG,O,C,3„Y„123 .
7-118 UP-9662.5
DSM (Display Message)
Use a DSM statement to display your own one-line message at the top
of the screen in place of the control line. You can use DSM in one of
two ways:
The DSM statement stalls the run until the user transmits or resumes,
unless you specify the interim display, in which case the run continues
automatically. Note that the DSM statement clears the output area.
❑ Less than (<) and greater than (>) signs are translated into blink
characters.
UP-9662.5 7-119
DSM
Format
@DSM,m,t,rimsetabp,erase?,interim?,pdq,dm,d1.dr,dspl,dspfl .
In field: Enter:
M,t,r the mode, type, and RID number of the report or result
containing the message.
7-120 UP-9662.5
DSM
Examples
This statement displays a message at the top of the current screen. The
message is located on line 4 of the current result.
@OSM,-0,4 .
@OSM.O.A.12,4,10„„0.D,2 .
UP-9662.5 7-121
DSP (Display Report)
You can use the DSP statement to display and manually update reports
during run execution or to print the reports that are on display.
NOTE: Don't put other run statements on the same line after a DSP
statement. The logic scan of the line terminates after
executing the DSP statement.
Format
@DSP,m,t,r1,1,tabp,f,interim?,hold,msg80] .
In field: Enter:
m,t,r the mode, type, and RID number of the report to display.
tabp the tab character after which to position the cursor in the
report. Keep in mind that if you are displaying a report
with a control line, the default cursor position is in the
RL field.
(continued)
7-122 UP-9662.5
DSP
(continued)
In field: Enter:
Examples
UP-9662.5 7-123
DUP (Duplicate Report)
Format
@DUP,m,t,r[,rm,rt] .
In field: Enter:
rm,rt the receiving mode and type to duplicate the report into.
Reserved Word
Word Content
7-124 UP-9662.5
DUP
Example
@OUP,20,B,1,0,B .
@CHG <RID>13 RID$ .
UP-9662.5 7-125
DVS (Define Variable Size)
Use the DVS statement to create variables equal to the size of report
fields. For example, use it 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.
In a DVS statement, you specify the variable number and its type; you
don't specify the variable's size. The run assigns a size to the variable
equal to its corresponding report field, then fills it with spaces.
Format
In field: Enter:
m,t,r the mode, form type, and RID number of the report or
result where the fields reside. (Default = -0.)
field the field whose size you want to define (can be field
names or column-character positions).
7-126 UP-9662.5
DVS
Examples
This example initializes a variable to the size of the CUST CODE field
in RID 2B, mode 0, for use as an input parameter:
UP-9662.5 7-127
ECR (Encode Report)
You decode an encoded report with the DECODE function or the DCR
run statement (see DCR).
Use caution when encoding reports. Here are some important things to
remember:
❑ You cannot move encoded data between form types with different
report widths because you will not be able to decode it. If a form
type width is changed, all encoded reports in that type will be
corrupted and they will not be able to be decoded.
❑ 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. In addition, you may not be able to decode a
report that contains special NCS characters from a normal ASCII
terminal.
7-128 UP-9662.5
ECR
Format
@ECR,m,t,r,key[,hdrs?] .
In field: Enter:
m,t,r the mode, type, and RID number of the report to encode.
Example
@ECR,0.13,10.JMT6077,Y .
UP-9662.5 7-129
ELT (Element)
If the file you're copying is not a currently assigned file, the ELT
statement assigns it with a maximum granularity of 6400 tracks.
Format
In field: Enter:
m,t,r the mode, type, and RID number of the report to copy.
(continued)
7-130 UP-9662.5
ELT
(continued)
In field: Enter:
L Fieldata
F ASCII (default)
U ASCII, uppercase
newcyc? a Y to create a new cycle (+1) for the file, and ignore 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
Code Error
(continued)
UP-9662.5 7-131
ELT
(continued)
Code Error
Use an ISM statement to read the message. Place the number in STAT2$ in the msgno
subfield in an LSM statement (see LSM).
7-132 UP-9662.5
ELT
Example
This statement creates qualifier MYQUAL file MYFILE and copies the
data in RID 2B, mode 0, to it; or the run goes to label 99 if there is an
error and the system cannot copy the data:
@ELT,O,B,2,99 MYOUAL,MYFILE .
Enter these commands on any line in the report; they take effect from
that point on in the data.
UP-9662.5 7-133
EL- (Element Delete)
Format
@EL-[,lab] qual,f4cyc,elt,ver] .
In field: Enter:
7-134 UP-9662.5
EL-
Reserved Words
Code Error
(continued)
UP-9662.5 7-135
EL-
(continued)
Code Error
Use an LSM statement to read the message. Place the number in STAT2$ in the msgno
subfield in an LSM statement (see LSM).
Example
7-136 UP-9662.5
ESR (Exit Subroutine)
NOTE: Don't put other run statements on the same line after an ESR
statement. The logic scan of the line terminates after
executing the ESR statement.
Format
@ESRICq1,-q)] .
In field: Enter:
Example
This example shows a series of statements that could be used to run and
execute a subroutine:
UP-9662.5 7-137
ESR
7-138 UP-9662.5
EXT (Extract)
Use the EXT statement with updatable results to extract processed lines
from the report. The system deletes these lines from the report; these
lines become the current result (-0).
CAU
LCH (with the OU option)
LOC (with the OU option)
MAU
SRU
Format
@EXT .
Example
In this example, all lines found in the Search Update result are deleted
from the report; these lines become the current result (-0):
UP-9662.5 7-139
FDR (Find and Read)
Use an FDR statement to find a line. Follow it with one or more RLN
statements (or an RDL statement) to read the line or lines.
@FND . . . RDL...
Format
In field: Enter:
(continued)
7-140 UP-9662.5
FDR
(continued)
In field: Enter:
options:
Examples:
Find spaces
Find slashes
Ityp the line type to scan. (If you specify the A option, leave
this subfield blank.)
UP-9662.5 7-141
FDR
where:
7-142 UP-9662.5
FDR
where:
Use no options.
UP-9662.5 7-143
FMT (Format)
❑ 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.
Format
In field: Enter:
m,t,r the mode, form type, and RID number of the report or
result from which to display fields. (Default = -0.)
7-144 UP-9662.5
FMT
Examples
This statement displays the ST CD, SHIP DATE, and CUST CODE
fields of the current -0:
WMT 'ST-CD','SHIP-DATE','CUST-CODE' .
@OSP,-0
@FMT,O,B,2 2-3,45-5,64-7 .
@OSP,O,B,2 .
UP-9662.5 7-145
FND (Find)
Format
In field: Enter:
m,t,r the mode, type, and RID number of the report in which
to find data.
o options:
(continued)
7-146 UP-9662.5
FND
(continued)
In field: Enter:
Examples:
Find spaces.
ltyp the line type to scan. (If you specify the A option, leave
this subf ield blank.)
UP-9662.5 7-147
FND
where:
7-148 UP-9662.5
FND
This statement searches a field for spaces and captures the line number
where the find was made:
@F N D , 0 B 2 . 9 9 @ 25-6 0 @NW@ . V 1 I6 .
where:
UP-9662.5 7-149
GOC (Generate Organization Chart)
Format
In field: Enter:
(continued)
7-150 UP-9662.5
GOC
(continued)
In field: Enter:
vbuffz the variable to capture the size of the buffer used to hold
chart information.
UP-9662.5 7-151
GOC
Reserved Words
If the run encounters an error in the data RID, it goes to the label in
the lab subfield and loads STAT1$ and STAT2$ with information about
the error.
Word Content
Example
@GOCA,H,81 N N .
See the Color Graphics Guide for more details about generating
organization charts.
7-152 UP-9662.5
GS (Graphics Scaler)
Use the GS statement to increase or decrease the size of your charts and
to create custom graphics using the expanded syntax.
See the Color Graphics Guide for more details about the GS statement
as well as information about using primitive graphics code.
Format
@GS,m,t,r[lab] maxyf,o,ige?,unp?,aga?,expand?,ighitxt?,outrs1t1
sfl,offx,offy] angle[,absx,absy vci,vco,vminx,vmidx,vmaxx,
vminy,vmidy,vmaxyl .
In field: Enter:
m,t,r the mode, form type, and RID number of the report
containing the primitive graphics code.
o options:
(continued)
UP-9662.5 7-153
GS
(continued)
In field: Enter:
(continued)
7-154 UP-9662.5
GS
(continued)
In field: Enter:
UP-9662.5 7-155
GS
Reserved Words
If the run encounters an error in the data RID, it goes to the label in
the lab subfield and loads STAT1$ and STAT2$ with information about
the error.
Word Content
STAT2$ One less than the Line number in report being processed where error
occurred.
Example 1
@GS,0,A,1 20000 1 0 .
where:
0 Rotate angle to 0.
7-156 UP-9662.5
GS
Example 2
where:
UP-9662.5 7-157
GS
7-158 UP-9662.5
GTO (Go To)
Format
In field: Enter:
(continued)
UP-9662.5 7-159
GTO
(continued)
In field: Enter:
* +n, -n, and r may 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 Vi contained 5, you could use @GTO LIN V1. Here's
another example: @GTO LIN V2, where V2 contains the value -5, is the same as saying @GTO LIN -5.
Examples
@GTO 7 .
The following statement continues the run at the line with the label
equaling the contents of V6:
@GTO V6 .
This statement stops the run and displays the contents of the output
area:
@GTO END .
This statement continues the run two lines beyond the current statement
line:
@GTO L IN +2 .
7-160 UP-9662.5
GTO
@GTO RPX 2
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 mode and
form type 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. Labels are not valid.
UP-9662.5 7-161
IDU (Index User)
NOTE: You cannot use the IDU statement to index a mode and type
in which your run control report is located.
Format
@IDU,m,t1,q,user,stdate,endate,strid,endrid vrids,v1ines,vridst,vhiridt1 .
In field: Enter:
stdate the starting date for a date range (in format ddmmmyy).
This is the date of the most recent update to the report,
or the creation date if there are no updates.
endate the ending date for a date range (in format ddmmmyy).
This is the date of the most recent update to the report,
or the creation date if there are no updates.
(continued)
7-162 UP-9662.5
IDU
(continued)
In field: Enter:
Examples
This statement indexes all of this user's form type A reports, including
header lines from each report in the result:
@IOU, 0.A .
@IDU,0,13,7,JDOE,01JAN87,31DEC87,5,10 V113,V219,X
V314,V4I4 .
where:
UP-9662.5 7-163
[DU
7-164 UP-9662.5
IF (Conditional)
Format 1 —Common
Format 2—Logical OR
@IF[,C] vall op va12 & op va13 [& op vain ... & op vain] stmt ; .
In field: Enter:
(continued)
UP-9662.5 7-165
IF
'continued)
En field: Enter:
= or EQ Equal
NE Not equal
(continued)
7-166 UP-9662.5
IF
(continued)
In field: Enter:
If the conditions of the IF statement are not met (FALSE), the run
continues executing at the next logical line. The next logical line
begins after the run encounters either a semicolon (;) or the end of the
actual line. Note that all examples contain a semicolon.
UP-9662.5 7-167
IF
Examples
If V22 is greater than 10 AND less than 50, go to label in V99; or else
continue:
@IF V1 = A IF V2 LT B GTO 1 ;
7-168 UP-9662.5
IF
If V1 equals 2, execute the LDV statement (load V3 with the value 4),
go to label 1 and continue; if V1 does not equal 2, go to label 2:
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
on the next logical line.
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 FRI, go to label 26:
UP-9662.5 7-169
INC (Increment Variables)
Format
@INCI,n1 v[,v,...v] .
In field: Enter:
Examples
@I NC V2
instead of:
@CHG V2 V2 + 1
@INC,3 V1.1/3 .
7-170 UP-9662.5
IND (Index)
NOTE: 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.
Format
@IND,m,t,q[jab] .
In field: Enter:
Reserved Words
Word Content
UP-9662.5 7-171
IND
Example
This example indexes mode 0, type A, and creates a result that has the
first four lines from each report in the form type. If no reports exist,
the run goes to label 99.
• IND.0.A.4,99 .
7-172 UP-9662.5
INS (Insert)
Use an INS statement to insert data from one variable into another.
Format
vld substry .
In field: Enter:
Examples
UP-9662.5 7-173
JUV (Justify Variables)
Format
@JUV,o v[,v,...vJ .
In field: Enter:
(continued)
7-174 UP-9662.5
JUV
(continued)
In field: Enter:
Examples
UP-9662.5 7-175
JUV
7-176 UP-9662.5
KEY (Function Key Input)
Format
Reserved Word
R6Set'VOd* word:
The run continues executing after the DSP, OUT, or SC statement, and FKEY$ contains:
Example
In this example, the KEY statement requests function key input, the
DSP statement displays RID 2B in mode 0, and the LDV statement loads
VI with the contents of FKEY$. VI can then be tested for its contents,
and the run can be processed accordingly.
@KEY .
@OSP,0.8.2 .
@LDV,PW V112=FKEY$ .
UP-9662.5 7-177
LCH (Locate and Change)
Format
@LCH,m,14,1,1ab] o cc tgtstr/replstrI,v1ines,vridl .
In field: Enter:
m,t,r the mode, type, and RID number of the report in which
to locate and change data.
(continued)
7-178 UP-9662.5
LCH
(continued)
In field: Enter:
(continued)
UP-9662.5 7-179
LCH
(continued)
In field: Enter:
vlines the number of lines located that contain the target string.
vrid the RID number where the target string was located.
7-180 UP-9662.5
LCH
Example
where:
UP-9662.5 7-181
LCV (Locate/Change Variable)
You can use an LCV statement to literally compare the contents of one
variable to another. Using an IF statement and a GTO statement to
compare the contents of variables limits you to 18 characters in the
variables. Using an LCV statement with a label lets you compare up to
132 characters, and it is more efficient than using IF and GTO
statements.
You can use an LCV statement on all variable types, and you can use
substrings.
Format
In field: Enter:
options:
(continued)
7-182 UP-9662.5
LCV
(continued)
In field: Enter:
(continued)
UP-9662.5 7-183
LCV
(continued)
In field: Enter:
V1=DOGHORSECOWPIGBIRDCATCATCATCATMOUSE
column 15 column 34
I locate columns I
7-184 UP-9662.5
LCV
where:
CATdogCATDOGCATDogCATDOGCATdog
where:
UP-9662.5 7-185
LCV
In this example, the bail-out count was set to a value higher than the
number of occurrences of DOG because we didn't want to bail out. V3
continues to count each occurrence of DOG. After the statement
executes, V3 contains 5.
*CATDOGCATDOGCATDOGCATDOGCATDOG
where:
V1 Scan VI.
7-186 UP-9662.5
LCV
<STRING1>=ABC123
<STRING2>=ABC+++
where:
VI V2 Variables to compare.
Remember, if you use the N option, the run does NOT go to the label
unless the two variables are equal.
UP-9662.5 7-187
LCV
BLACKBOX1*BLACKCAN1*BLACKBAG1*BLACKCUP I
where:
GREENBOX2*GREENCAN2*GREENBAG2*GREENCUP2
7-188 UP-9662.5
LCV
FEATURE010101
This statement uses an unknown trailing substring and bails out after
the second find:
where:
UP-9662.5 7-189
LCV
$$$DOLL ARS
where:
Use no options.
7-190 UP-9662.5
LDV (Load Variables)
❑ Initialize variables
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, @LDV,P V1,V2 rather than
@LDV,P V1=V1,V2=V2. 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.
UP-9662.5 7-191
LDV
Format
In field: Enter:
options:
* Don't use the v=vld subfield with these options. See further explanation in this subsection for the
format.
(continued)
7-192 UP-9662.5
LDV
(continued)
In field: Enter:
In the following example, the first LDV statement loads VI through V4;
the second LDV statement then loads these four variables into V5:
64_13V V1A5=THIS,V2A3.1S,V3A3=AN,V4A8=EXAMPLE .
@LDV V5S40=V1V2V3V4 .
The H option tests the remote run link between two sites to see whether
the remote site is online or offline.
NOTE: With a non-GCS remote run link, the H option only indicates
whether or not the remote site is configured.
UP-9662.5 7-193
LDV
Format
@LDV,H v=rms .
In field: Enter:
0 site is offline.
1 site is online.
7-194 UP-9662.5
LDV
Format
@LDV,N v=v1d,minmax
In field: Enter:
Example
❑ Line (b) executes the LDV,N that produces a number between 1 and
20, which the run uses later on as the report number. This number
is based on the data entered and remains the same as long as the
LDV,N statement remains unchanged. Line (b) also checks to see
whether the user is attempting to add or display an item.
❑ Part (d) finds a blank line to write and writes the line with the
new product name, whenever requested by the user. The number
produced by LDV,N for the product name is always the same, and
is used as the report number to write the new product name into.
UP-9662.5 7-195
LDV
❑ Part (e) displays an error message when the user attempts to display
a product that does not exist.
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'll lose the extra characters.
7-196 UP-9662.5
LDV
@LDV V112=1 .
@ILDV V1A1=A,V212=10 .
@LDV,C V1=2 .
@LDV,P V1=2 .
@LDV,R V1S20=1
@LDV,RZ V1=1 .
@LDV,R V1=-1 .
@LDV,F1Z V1=-1 .
UP-9662.5 7-197
LDV
@LDV.FI V1(1-4)=2 .
.I.DV,RZ V1(1-4)=2 .
@IDV,U V1=abc .
@CDV,W <MODE>14=MODE$,<TYPE>16=TYPE$,<R1D>14=RID$ .
61-DV,PW V4S20='ABC'USER$(1-3)STNUM$XYZ
7-198 UP-9662.5
LFC (Load Format Characters)
Format
@LFC v
In field: Enter:
Example
LFC V1S80 .
UP-9662.5 7-199
LFN (Load Field Name)
Use the LFN statement to load variables with the names of report
fields that correspond to the column-character positions supplied. See
Section 2 for a general description of named fields.
7-200 UP-9662.5
LFN
Format
In field: Enter:
Reserved Word
Code Error
5 Field name was truncated because of variable size, and name is not unique
in report header.
UP-9662.5 7-201
LFN
Example
where:
7-202 UP-9662.5
LLN (Last Line Number)
Use an LLN statement to set a variable equal to the last line number of
the specified report or result.
Format
@LLN,m,t4,1ab] vlines .
In field: Enter:
UP-9662.5 7-203
LLN
Reserved Words
Word Content
If report exists. ..
STAT1S 0
STAT2S Disregard
STAT1S 0
STAT2$ Disregard
If neither the report nor form type exists, the LLN statement goes to the label in the
lab subfield. If you don't specify a label, the run continues at the next statement.
Example
This statement determines the number of lines in RID 1B, mode 0, and
places that quantity in <LINES>. If the report or form type does not
exist, the run goes to label 99:
@tLN,0,13,1,99 <LINES>I3 .
7-204 UP-9662.5
LMG (List Merge)
Format
@LMG,im,it,ir,rm,rt,rrl,lab] .
In field: Enter:
im,it,ir the mode, type, and RID number of the issuing report.
rm,rt,rr the mode, type, and RID number of the receiving report.
UP-9662.5 7-205
LMG
Example
This statement merges lines and partial lines from RID 7H into RID
8H, both in mode 0:
g_MG.O.H.7.0,H,8 .
7-206 UP-9662.5
LNI (Line Insert)
Unless you are processing a result, you must precede an LNI statement
with a LOK statement. See LOK.
Format
@LNI,m,t,r1b4[,x],11,0 .
In field: Enter:
m,t,r the mode, type, and RID number of the report in which
to insert lines.
IF' the line number before the inserted lines. (The inserted
lines follow this line.)
Example
This statement inserts line 8 one time for two lines (lines 8 and 9) in
mode 0, RID 3B, after line 6:
VA1,0,13.3.6.1,8,2
UP-9662.5 7-207
LNK (Link to Another Run)
The linked run can return up to three status codes and the current
result of the linked run to the original run via a GTO END statement
(see GTO). Following the LNK statement in the original run, you can
examine the reserved words STAT1$, STAT2$, and STAT3$ to obtain
the status codes.
7-208 UP-9662.5
LNK
Format
@LNK run[,vldl .
In field: Enter:
Reserved Word
Word Content
Example
This example executes a run, TEST, with the contents of VI, V2, and
SAM as input parameters to be picked up via INPUTS, and continues at
the next statement when TEST executes a GTO END:
@LNK TEST,V1,V2,SAM .
UP-9662.5 7-209
LNK
This statement examines the status codes returned by the linked run:
601-DV,PN V116=STAT1$,V216=STAT2$,V316=STAT3S .
You can also use the LNK statement to call the SCHEDULE run from
within a run. The SCHEDULE run schedules a registered background
run for execution at a later time. See the Manual Functions Reference
for more information on the SCHEDULE run.
Format
@LNK SCHEDULE,run,extime[,exdate,sn] .
In field: Enter:
7-210 UP-9662.5
LNK
Reserved Word
Code Error
Example
This example calls the SCHEDULE run to schedule the run called
"myrun" at 1:30 P.M. on July 5, 1988. It notifies station 123 when the
SCHEDULE run execution is complete.
UP-9662.5 7-211
LNK
You can also use the LNK statement to call a chart run from within
your run control report. You receive a result containing the primitive
graphics code; the chart is not displayed. The primitive graphics code
is then sent to the linking run via the -0 result. If you are linking to
the MULTI run, see "Linking to the MULTI Run" in this subsection.
See the Color Graphics Guide for more information on graphics runs.
Format
@LNK chartrun,r1[,sn,psiz?,transpcy?] .
In field: Enter:
chart run the name of the chart run to link to (for example, PIEG
or BARG).
rt the RID number and form type of the chart input report
(leave this subfield blank if you want the current -0
result).
7-212 UP-9662.5
LNK
@LN K MULTI,o,f,sn,psiz?,transpcy?1,m,t,r,m,t,d,m,t,r,...] .
In field: Enter:
UP-9662.5 7-213
LNM (Line Move)
The LNM statement moves lines within a report or result. It deletes the
lines from their original location and moves them to the new location.
Unless you are processing a result, you must precede an LNM statement
with a LOK statement.
Format
@LNM,m,t,r1b41,4/1,q1 .
In field: Enter:
1b4 the line number before the moved line or lines. (The
moved lines follow this line.)
Example
This statement moves line 8 one time for two lines (lines 8 and 9) in
mode 0, RID 3B, after line 6:
WAM.0,13.3,6,1,8.2 .
7-214 UP-9662.5
LNX (Line Duplicate)
Unless you are processing a result, you must precede an LNX statement
with a LOK statement.
Format
@LNX,m,t,r,1,44] .
In field: Enter:
m,t,r the mode, type, and RID number of the report in which
to duplicate lines.
Examples
@LNX.O.B.3,12,5 .
WAX.0,B,3,6,5,3 .
UP-9662.5 7-215
LN+ (Line Add)
The LN+ statement adds lines to a report or result. The report expands
to make room for the new lines. The system automatically inserts tab
characters in the locations defined for the form type.
Unless you are processing a result, you must precede an LN+ statement
with a LOK statement.
Format
@LN+,m,t,r1b4,q1,pred111 .
In field: Enter:
m,t,r the mode, type, and RID number of the report in which
to add lines.
!b4 the line number before the added lines. (The added lines
follow this line.)
Example
This statement adds one type 2 predefined line to mode 0, RID 3B,
after line 5:
ftN+.0,B.3.5.1,2 .
7-216 UP-9662.5
LN- (Line Delete)
Unless you are processing a result, you must precede an LN- statement
with a LOK statement.
Format
@LN-,m,t,r,l,q
In field: Enter:
mix the mode, type, and RID number of the report from
which to delete lines.
Example
This statement deletes one line from mode 0, RID 3B, starting at line
15:
UP-9662.5 7-217
LOC (Locate)
Format
In field: Enter:
m,t,r the mode, type, and RID number of the report in which
to locate a string of characters.
(continued)
7-218 UP-9662.5
LOC
(continued)
In field: Enter:
(continued)
UP-9662.5 7-219
LOC
(continued)
In field: Enter:
vcol the column number where the target string was located.
This variable contains one less than the column number if
you use the F option; add one to get the actual column
number.
vrid the RID number where the target string was located.
7-220 UP-9662.5
LOC
Example
where:
UP-9662.5 7-221
LOG (Accounting Log)
Normally, whenever a run is executed, the system logs only one entry in
the accounting log, which is a summary of the data compiled while the
run is executing.
Enter a LOG statement in the run control report ahead of all other
statements (except :L statements, if your run has them). If the run
contains a REL statement, replace it with a GTO END statement. This
keeps the log list intact after the run completes.
When you're finished evaluating the log result, reinstate the REL
statement and delete the GTO END statement (if you added one).
Format
@LOG .
You can evaluate the general quality of your run by studying the log
result produced by the LOG statement. You can also submit your log
result to the RUNA run (see Section 5), a run analyzer.
7-222 UP-9662.5
LOK (Update Lock)
LNI
LNM
LNX
LN+
LN-
WRL
If another user already has update control of the report and if the LOK
statement in your run has no label, the run stalls until the other user
releases update control; otherwise, the run continues at the label
specified in the lab subfield.
UP-9662.5 7-223
LOK
Format
@LOK,m,t,r[fab] .
In field: Enter:
m,t,r the mode, type, and RID number of the report in which
to get an update lock.
Reserved Word
lesOved itord: MT 1$
Word Content
Example
@LOK,O,B,6 .
7-224 UP-9662.5
LSM (Load System Message)
Messages can be up to 132 characters long, but usually take up one line
of data. They are formatted so that columns 1 through 80 have the
message and columns 82 through 88 have the message mnemonic.
Format
@LSM,msgnoLlabi vmsg .
In field: Enter:
Example
This example loads V I with the message number and V2 with the
message:
UP-9662.5 7-225
LZR (Line Zero)
The LZR statement does not create a result. Results (-0) existing before
LZR executes continue to exist after LZR executes.
Format
@LZR,m,ty[,lab vlines,vcpl,vhdrs,vcs,vupds,vdept,vuser,vrpw,vwpw] .
In field: Enter:
m,t,r the mode, type, and RID number of the report that
contains the information.
(continued)
7-226 UP-9662.5
LZR
(continued)
In field: Enter:
UP-9662.5 7-227
LZR
Reserved Words
Word Content
If report exists. . .
STAT1S 0
STAT2S Disregard
STAT1S 0
STAT2S Disregard
If neither the report nor form type exists, the LZR statement goes to the label in the
lab subfield. If you don't specify a label, the run continues at the next statement.
Example
@LZR,O,B,2,99 <LINES>I5 .
7-228 UP-9662.5