1177185_REPORTER_III_Report_Language_Operations_Reference_Manual_Jan85 1177185 REPORTER III Report Language Operations Reference Manual Jan85

1177185_REPORTER_III_Report_Language_Operations_Reference_Manual_Jan85 manual pdf -FilePursuit

1177185_REPORTER_III_Report_Language_Operations_Reference_Manual_Jan85 1177185_REPORTER_III_Report_Language_Operations_Reference_Manual_Jan85

User Manual: 1177185_REPORTER_III_Report_Language_Operations_Reference_Manual_Jan85

Open the PDF directly: View PDF .
Page Count: 592

Download
Open PDF In Browser	View PDF

•
UNISYS

REPORTER III
Report
Language
Operations

Reference Manual

Copyright © 1983, 1985 Unisys Corporation.
All Rights Reserved.
Unisys is a registered trademark of Unisys Corporation.

Relative to Release
Level 2.0
Priced Item

January 1985
Printed in U S America
1177185

Unisys cannot accept any financial or other responsibilities that may be the
result of your use of this information or software material, including direct,
indirect, special or consequential damages. There are no warranties extended
or granted by this document or software material.
You should be very careful to ensure that the use of this software material and!
or information complies with the laws, rules, and regulations of the jurisdic.
tions with respect to wh ich 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.
Comments or suggestions regarding this document should be submitted on a
Field Communication Form (FCF) with the Class specified as "2" (System
Software), the Type specified as "1" (F.T.R.), and the Product specified as the
seven-digit form number of the manual (for example, "1177185"). The FCF
should be sent to the following address: Unisys Corporation, Product Assurance and Support, 19 Morgan, Irvine CA 92718-9958 USA.

•

Product Information
Announcement

UNISYS

o New Release

0

Revision

•

Update

0

New Mail Code

Title

REPORTER III Report Language Operations Guide
This Product Information Announcement announces the release of Update 3 to the January 1985 publication of the

REPORTER III Report Language Operations Guide. This update is relative to the A Series Mark 4.0.2 System
Software Release, dated October 1993.
This update documents enhancements to REPORTER III to process and generate COBOl85 programs. These
enhancements are being made to support users migrating from V Series systems to A Series systems.

Remove

Insert

xi through xii
1-1 through 1-2
2-17 through 2-18
4-35 through 4-36
4-47 through 4-48
4-79 through 4-80
4-137 through 4-138
4-161 through 4-162
4-179 through 4-1828
4-241 through 4-242
4-333 through 4-334
6-1 through 6-16
A-I through A-4
C-25 through C-26
C--:39 through C-40

iiA through iiD
xi through xii
1-1 through 1-2
2-17 through 2-18B
4-35 through 4-36
4-47 through 4-48
4-79 through 4-80
4-137 through 4-138
4-161 through 4-162
4-179 through 4-182B
4-241 through 4-242
4-333 through 4-334
6-1 through 6-16
A-I through A-4
C-25 through C-26B
C-39 through C-40

Changes are indicated by vertical bars in the margins of the replacement pages.
Retain this Product Information Announcement as a record of changes made to the base publication.
To order additional copies of this document
•

United States customers, call Unisys Direct at 1-800-448-1424.

•

All other customers, contact your Unisys Sales Office.

•

U nisys personnel, use the Electronic Literature Ordering (ElO) system.

Announcement only:

Announcement and attachments:

AS244

System:
Release:

REPORTER III
Mark 4.0.2 October 1993

Part number: 1177185-003

•
UNISYS

Publication Change Notice (PCN)
Form-PeN number

Date

1o I
Title

1177185-()()2

pc::; IBB

REPORTER III Report Language Operations Guide
(Relative to the Mark 2.4 System Softw~re Release>

Description

This PCN provides revisions to the REPORTER III Report
Language Operations Guide, relative to the 2.4 Software
Release.
Revisions to the text are indicated by black vertical bars
on the affected pages.

Replace These Pages

Add These Pages
4-92A
4-94A
4-98A
4-148A
4-182A
4-242A
4-312A
C-40A

iii thl'''u xi
4-1
4-17 thl'"'u 4-19
4-23 tht"'u 4-25
4-91 thl'"'l_l 4-99
4-145 thl'"'u 4-147
4-153 thl'''u 4-155
4-163 thl'"'u 4-169
4-181
4-187
4-241
4-297
4-311
4-341 thl'"'u 4-347
C-7
C-21
C-27
C-39
IYldex 1 thl'"'u 9

Copyright © 1988 Unisys Corporation
All Rights Reserved

Retain the PCN cover sheet as a record of changes made to
the basic publication.
Distribution Codes SC, SD, SE
1177185-002
Printed in U S America

•
JNISYS

Publication Change Notice (peN)

te

Form-PeN number

)1/20/86

1177185-001

Ie

ErORTER III

Report Language User's Guide (J anu a r'y 1985)

'Scription

lis PCN provides reV1S10ns to the REPORTER III Report Language User's Guide,
~lative to the 2.1 Software Release.
Revisions to the text are indicated by
Lack vertical bars on the affected pages.
Replace These Pages

Add This Page
3-2A

3-1
3-3
4-91
4-151
4-177 thru 4-179
4-225
4-271
6-9
6-23
6-35
A-3
B-1 thru B-3
B-7 thru B-9
C-25
C-37
~tain

this PCN cover sheet as a record of changes made to the basic publication.

COPYRIGHT

© 1986

Unisys Corporation

peN J J77185-00 I
Pnnted In U S America

Page Status
Page

Issue

iiA through iiC
iiD
iii through x
xi
xii
1-1 through 1-2
1-3 through 1-5
1-6
2-1 through 2-17
2-18 through 2-18A
2-18B
2-19 through 2-35
2-36
3-1
3-2 through 3-2A
3-2B
3-3 through 3-4
3-5 through 3-19
3-20
4-1 through 4-2
4-3 through 4-16
4-17 through 4-20
4-21 th rough 4-22
4-23 through 4-26
4-27 through 4-35
4-36
4-37 through 4-46
4-47
4-48 through 4-79
4-80
4-81 th rough 4-90
4-91 th rough 4-92
4-92A through 4-928
4-93 th rough 4-94
4-94A through 4-948
4-95 through 4-98
4-98A through 4-988
4-99 th rough 4-100
4-101 through 4-137
4-138
4-139 through 4-144
4-145 through 4-148A

-003
Blank
-002
-003
Blank
-003
-000
Blank
-000
-003
Blank
-000
Blank
-000
-001
Blank
-001
-000
Blank
-002
-000
-002
-000
-002
-000
-003
-000
-003
-000
-003
-000
-002
-002
-002
-002
-002
-002
-002
-000
-003
-000
-002

continued
1177185-003

iiA

Page Status

continued
Page

4-148B
4-149 through 4-150
4-151
4-152
4-153 through 4-156
4-157 through 4-160
4-161
4-162
4-163 through 4-170
4-171 through 4-176
4-177 through 4-178
4-179
4-180 through 4-181
4-182 through 4-182A
4-182B
4-183 through 4-186
4-187 through 4-188
4-189 through 4-224
4-225
4-226 through 4-240
4-241
4-242
4-242A
4-242B
4-243 through 4-271
4-272
4-273 through 4-296
4-297 through 4-298
4-299 through 4-310
4-311 through 4-312A
4-312B
4-313 through 4-332
4-333
4-334 through 4-340
4-341 through 4-348
4-349
4-350
5-1 through 5-15
5-16
6-1
6-2
6-3 th rough 6-4
6-5 through 6-6
6-7
6-8 through 6-9
6-10
6-11
6-12
6-13 through 6-14
6-15

Issue
Blank

-000
-001
-000
-002
-000
-003
-000
-002
-000
-001
-003
-000
-003
-002
-000
-002
-000
-001
-000
-002
-003
-002
Blank

-000
-001
-000
-002
-000
-002
Blank

-000
-003
-000
-002
-000
Blank

-000
Blank

-000
-003
-000
-003
-000
-003
-001
-003
-000
-003
-000

continued

iiB

1177185-003

Page Status

continued
Page

Issue

6-16
6-17 through 6-23
6-24
6-25 through 6-34
6-35
6-36 through 6-37
6-38
A-I through A-3
A-4
B-1
B-2
B-3
B-4 through B-7
B-8 th rough B-9
B-10 through B-11
B-12
C-1 through C-6
C-7 through C-8
C-9 through C-20
C-21 through C-22
C-23 through C-24
C-25 through C-26A
C-26B
C-27 through C-28
C-29 through C-36
C-37
C-38
C-39 through C-40
C-40A
C-40B
C-41 through C-43
C-44
D-1 through D-4
E-1 through E-7
E-8
1 through 9
10

-003
-000
-001
-000
-001
-000
Blank
-003
Blank
-001
-000
-001
-000
-001
-000
Blank
-000
-002
-000
-002
-000
-003
Blank
-002
-000
-001
-000
-003
-002
Blank
-000
Blank
-000
-000
Blank
-002
Blank

Unisys uses an II-digit document numbering system. The suffix of the document
number (1234 5678-xyz) indicates the document level. The first digit of the suffix
(x) designates a revision level; the second digit (y) designates an update level. For
example, the first release of a document has a suffix of -000. A suffix of -130
designates the third update to revision 1. The third digit (z) is used to indicate an
errata for a particular level and is not reflected in the page status summary.

1177185-003

iiC

TABLE OF CONrENTS

INTR.OOOCI'IOO ••••••••••••••••••••••••••••••••••••••••
SECrION 1.
SY'S'I'm1

SYSTmM DESCRIPTION ••••••••••••••••••••••

E"FA.'l'lJRES..................................

INrERFACE 'ID SYSTEM •••••••••••••••••••••
REPORI' lANGUAGE AND SYSTEM OPERATICN •••••••••••••
~WLE REPORI'-~KruAGE SPECIFI~TION ••••••••••••

~UAGE

ix
1
1
1
1
1

1
1

2

1
1
2
2
2
3
3
3
3
3
4
7
7

2

3
4

SECI'IOO 2.

BASIC INFORMATICN ABOUI'
THE REPORT LANGUAGE •••••••••••••••••••••
CliARA.crm

SEI'................................ ....

SPOCIFICA.TION FORM •••••••••••••••••••••••••••••••
~ INDlCA.'IOR ••••••••••••••••••••••••••••••••
D~nlITION OF IDROO ••••••••••••••••••••••••••••••
RESm'VID IDRJ)S. • • • • • • • • • • • • • • • • • • • • • • • ••••••••

Ke}Words •••••••••••••••••••••••••••••••••••
Optional Words •••••••••••••••••••••••••••••
~

~~OD

........................................ .

OF LANGUAGE DEFINITION ••••••••••••••••••••

S'mI."'.AX DIAGRAl'1S •••••••••••••••••••••••••••••••
RESm'VED \\1ORJ)S. • • • • • • • • • • • • • • • • • • • • • • • • • • • ••••

2
2

2
2
2
2

2
2
2
2

P'UN'crtJATION •••••••••••••••••••••••••••••••••••

2
2

SYNTACTIC VARIABLES •••••••••••••••••••••••••••
Sa1:At.fl'IC R'UIE:S ••••••••••••••••••••••••••••••••

2
2

TEHMINOLOGY FOR DATA

••••••••••••••

2

DATA I'mi OR ITEM......................... ••••

2
2

IDENTIFI~TION

GROUP •••••••••••••••••••••••••••••••••••••••••
RECO.RD ••••••••••••••••••••••••••••••••••••••••
DATA S'l'R.UCIU'RE ••••••••••••••••••••••••••••••••

2

STATISTICAL DATA ITEM •••••••••••••••••••••••••
NONSTATISTICAL ~TA rrEM ••••••••••••••••••••••

2
2
2
2
2
2
2
2
2
2

I'ID1 ••••••••••••••••••••••••••••••••••

2

l.~.

2
2
2
2
2

DATA ~E •••••••••••••••••••••••••••••••••••••
I.£:X3ICA.I.. RECORD ••••••••••••••••••••••••••••••••

CONTROL-BREAK ITEM ••••••••••••••••••••••••••••
RANGE-BREAK I'lD1 ••••••••••••••••••••••••••••••
rnP'UT DATA I'I'H-1.................... •• '. • • • • • • ••
ACCE,Pl'ID DATA IrrEl1 ••••••••••••••••••••••••••••

DERIVED DATA I'I'H-1 •••••••••••••••••••••••••••••

~y

VOCABt.JI..AR.Y

• • • • • • • • • • • • • • • • • • • • • • • • • • • • ••••

DATA-I'l'n1

~.

GOOUP

••••••••••••••••••••••••••••••••••••

~

• • • • • • • • • • • • • • • • • • • • • • • • • • •••••

~CRO ~ ••••••••••••••••••••••••••••••••••••

roIDITlOO NMv1E. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
RECO.RD ~ •••••••••••••••••••••••••••••••••••
FIlE Nl~ •••••••••• •••••••••••••••••••••••••••
LINK ~ •••••••••••••••••••••••••••••••••••••
D.ATA~Bl\SE ~m

DATA-SEl'
SE'I'

...•..•...•...•.......•.••••..•.

~ •••••••••••••••••••••••••••••••••

NAl'1E..... #. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iii

2

2
2
2
2
2

8

9
10
10
10
11
11
11
11
13
14
16
16
16
16
16
17
17
17
18
18
18
19
19
19
19
20
20

peN 1177185-002

INPUT-PBOCEDURE NAME ••••••••••••••••••••••••••
EXAMPLES ••••••••••••••••••••••••••••••
SAMPLE Vcx:::ABUl.ARY 1: ..VOCEMP" •••••••••••••••••
II
~lE VClCABtJI..ARY 2: .. VOCAST •••••••••••••••••
SAM.I>I...E VOCABUI.J\R.Y 3: II ~I' • • • • • • • • • • • • • • • • •
~lE VOCABtJI..ARY 4: .. CLIENI'II •••••••••••••••••
SAMPLE VOCABt.JI.AR.Y 5: "CUSTV" ••••••••••••••••••
~lE VOCABu:LARY 6: .. SHIPV" ••••••••••••••••••

V~~

3. DESIGNIt~ REPORTS •••••••••••••••••••••••
REPORT SPECIFlCATI<::N' •••••••••••••••••••••••••••••
SINGlE-REPORT SPECIFICATION •••••••••••••••••••
MULTIPLE-REPORT SPECIFICATION •••••••••••••••••
SPECIFICATION CONSTRAINTS ••••••••••••••••••••••••
ORDER OF LANGUAGE STATEMENTS ••••••••••••••••••
CONI'ROL-BREAK I'lEMS AND ORDERING KEYS •••••••••
ABSTRACT STATEMENT ••••••••••••••••••••••••••••

2

2
2
2

SEC~ION

LANGUAGE

S[~T~mNTS ••••••••••••••••.•••••••••••••

BASIC LANGUAGE CONSTRUCTS ••••••••••••••••••••••••
FllN"CI'ION"S ••••••••••••••••••••••••••••••••••••••••

EXAMPLE REPORT SPECIFICATIONS ••••••••••••••••••••
EXAMPLE SINGLE-REPORT SPECIFICATION •••••••••••
EXAMPLE MULTIPLE-REPORT SPECIFICATION •••••••••
SECTION 4.

3

3
3
3
3
3
3
3
3
3
3
3
3
3

REPORT I.AOOUAGE STATEMENTS ••••••••••••••

4
4
4

ABSTRACI'STATEMENT •••••••••••••••••••••••••••••••

AcrnPI'

STA~.................................

STATEMENl' rn

USE OF ACCEPT
B 2000/B 3000/B 4000 SERIES •••••••••••••.••
ACc:::!E.:SS CIA.USE....................................
AGE EWCI'ION.......... • • • • • • • • . • • • • • • • • • • • • • • • • ••

ASSIGN LISTING STATEMENT •••••••••••••••••••••••••

l3l\.SE-DA'l"E OPI'ION............................... ..

BUILD INTERNAL ~BUTES CIA.USE •••••••••••••••••
BUILD SI'A~...............................
C-B-IfE'AI)I~

...
DEOC.......................... ...... .

C-B-SUBIiE:A.DING DESC..............................
OOOOL PICI'lJRE ••••••••••••••••••••••••••••••••••••
OO~ DESC ••••••••••••••••••••••••••••••••••••••

DEFAULT IDENTIFIERS •••••••••••••••••••••••••••
OO~S ••••••••••••••••••••••••••••••••••••••••••

LINE O~ •••••••••••••••••••••••••••••••••
PAGE O'VERE'LDW •••••••••••••••••••••••••••••••••
~It\IE srA~

••••••••••••••••••••••••••••••••

OOMPOUND-DATA-STRUCTURE CLAUSE •••••••••••••••••••
cnn?OUND-DATA-STRUCI'lJRE-cIAUSE LIST ••••••••••••••
CONDITIONAL PRINT SPECIFICATION ••••••••••••••••••
CONTROL-BREAK HEADINGS •••••••••••••••••••••••••••
DATA-BI\SE crAUSE •••••••••••••••••••••••••••••••••
DATA ~ ••••••••••••••••••••••••••••••••••••••••
DATA-PROCESSING-oPTI~l

STATEMENT •••••••••••••••••

DATA-8m' CI.A.USE..................................
DATA-STRUCTURE CLAUSE ••••••••••••••••••••••••••••

peN

1177185-002

iv

20
21
22
24
26
28
32
34

2
2
2
2

1
1
5
5
7
7
8
8

8
13
14
15
15
17
1
4

7

4 - 8

4
4
4
4

4
4
4
4
4

4
4
4
4
4
4
4
4
4
4
4
4
4
4
4

13
17
21
24

26
30
38
43
47
48

53
55
58
60
63
64

67
70
72
77
79
85
86
91

OMS II ~A-STRUCTURE CLAUSE ••••••••••••••••••••• 4
A SERIES OF gy-~ ••••••••••••••••••••••••••• 4
B 1000 SERIES OF SYSTEMS •••••••••••••••••••••• 4
B 2000/B 3000/B 4000 SERIES OF SYSTEMS •••••••• 4

92
96
99
99
99
105

EDITINCi A'rrR.IBlJI'ES... • • • • • • • • • • • • • • • • • • • • • • • • •••• 4

III

F'lJN'CI'IOO............. • • • • • • • • • • • • • • • • • • • • •• 4
:EXPRFSSIWS. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •• 4

112
114
114
117
117
117
118
120
121
124
126
127
127
128
129
131
137
143
145
149
151
154
157
161
163
170
174
178
180
180
181
181
182
182B
183
186
188
189
189
190
191
192
193
193
199
203

4
4

DATE-oaNVERT FUNCTION ••••••••••••••••••••••••••••

DATE

ro~

••••••••••••••••••••••••••••••••••••••

~

ARITHMETIC :EXPRESSION •••••••••••••••••••••••••
srR.IN(; :EXPRFSSlOO'.. • • • • • • • • • • • • • • • • • • • • • • • • • ••
BOOLEAN EXPRESSION ••••••••••••••••••••••••••••
S~le Boolean Expression ••••••••••••••••••
Basic Boolean ~ressian •••••••••••••••••••
0amp1ex Boolean Expression ••••••••••••••.••
Pattertl Matchirlg...........................

4

EXTENSI01~ ••••••••••••••••••••••••••••••••••••••••

4

EXTENSION

4

4
4
4
4

4

STATEMENT •••••••••••••••••••••••••••••• 4

FIlE NAl-1E ••••••••••••••••••••••••••••••• 4
A SERIES OF SYS~ ••••••••••••••••••••••••••• 4
B 1000 SERIES OF SY~ •••••••••••••••••••••• 4
B 2000/B 3000/B 4000 SERIES OF SYSTEMS •••••••• 4

~

EXTRACT-ITEM DESC •••••••••••••••••••••••••••••••• 4
EXTRACT S~TEMENT •••••••••••••••••••••••••••••••• 4
~ OF ~ srA~lI'S ••••••••••••••••• 4
FII.E MOD.. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •• 4
E"OOI'IOOS. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

roIf.1

4

ATrRI.BtJ'I'FS. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •• 4

~LENGTH

MONTH OPTION ••••••••••••••••••••••••• 4

GROtJP STATEMENT.................................. 4
INPt.1I' srATEMENT.................................. 4
INSmI'. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •• 4
INTERNAl." A'I"I'RIBlJI'FS •••••••••••••••••••••••••••••• 4
D~ ••••••••••••••••••••••••••••••••••••••••

4

ITn-1. SIZE............ • • • • • • • • • • • • • • • • • • • • • • • • • • ••
LI'I'ERAI.S. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ••
NlJl.1BERS. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ••
IN'I'EX3ERS. • • • • • • • • • • • • ..... • • • • • • • • • • • • • • • • • • • • • ••

4
4
4
4

srR.IN(;s •••••••••••••••••••••••••••••••••••••••

4

ITH1

~RY"

SIZE...................................... 4

NONSTATISTICAL EXPRESSION •••••••••••••••••••••••• 4
NUIL SPEC.. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •• 4

srA'ID1E:NI'..................... •••••••••••••
PASSWORD STATEMENT •••••••••••••••••••••••••••••••
PRESELECT BCX)LFAN :EXPRFSSlOO • • • • • • • • • • • • • • • • • ••••
SIMPLE BOOLEAN EXl?RESSIW •••••••••••••••••••••

ORDI!.~

4

4
4

4
BASIC AND CClvtPLEX BOOLEAN EXPRESSIONS ••••••••• 4

Valid Operators............................ 4
PRESELECT CI..A.USE ••••••••••••••••••••••••••••••••• 4

SINGLE DATA-STRUCTURE ACCESS •••••••••••••••••• 4
ONE-TO-ONE DATA-STRUCTURE ACCESS •••••••••••••• 4
OOE-rro-MANY DATA-STRUCIURE ACCESS.. • • • • • • • • • •• 4
PRI.NI' EXc::E:PI'IOOS ••••••••••••••••••••••••••••••••• 4
v

PCN 1177185-002

PRINI' SPECIFICA.TIONS •••••••••••••••••••••••••••••
STA~ ••••••••••••••••••••••••••••••••••
P~SINCi ~DDE ••••••••••••••••••••••••••••••••••
PROCESS-oPTION ASSIGN STA~ ••••••••••••••••••
PROCESS-oPTION SAVE STATEMENT ••••••••••••••••••••
PROCESS-oPTION SET STATEMENT •••••••••••••••••••••
PROCESS-oPTION STATEMENT •••••••••••••••••••••••••
PROCESS-oPTION SUPPRESS ST~ ••••••••••••••••
RANJX:>t.1-s.Mt1PI...E:

PRIm

DFSC...................... . . .. . . . . .

RANGE-BREAK-lTEM DESC ••••••••••••••••••••••••••••
RANGE STA~ ••••••••••••••••••••••••••••••••••
REIATIONA!J OPERA'IDR ••••••••••••••••••••••••••••••

REPl,ACE STA~ ••••••••••••••••••••••••••••••••
REPORI'- I~ MOD ••••••••••••••••••••••••••••••••••
REPORI'-oPTION SET STATEMENT ••••••••••••••••••••••
REPORI'-oPTION S~TEMENT ••••••••••••••••••••••••••
REPORT-oPTION SUPPRESS STATEMENT •••••••••••••••••
REPORI' STATEMENT................. ••••••••••••••••
R:>\\f IFSC. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
~LE STA~ •••••••••••••••••••••••••••••••••
SAVE ~STINCi STATEMENT •••••••••••••••••••••••••••
SEI.ECl' STATEMENT.............................. •••
SET SORT BDOCKING STATEMENT ••••••••••••••••••••••
SET SORI' ·SIZE, ST~ ••••••••••••••••••••••••••
STATISTI~ EXPRESSlOO •••••••••••••••••••••••••••
STATISTICAl. FUNcrIOO •••••••••••••••••••••••••••••
STAT P~ ••••••••••••••••••••••••••••••••••
SUMMARIZE STATEMENT ••••••••••••••••••••••••••••••
S~

STATISTICS ••••••••••••••••.•••••••••••••••
SUPPRESS SORT ST~ ••••••••••••••••••••••••••

SYSTEMATIC-SAMPLE DESC •••••••••••••••••••••••••••
SYSTEM-FILE-DATA-STRUCTURE CLAUSE ••••••••••••••••
T.PSLE STATEMENT............................ ••••••
~

............................................ .

TI'rI..E STA'I'EMWT............................. •••••

'IOI'.AIrPOPtJIA.TION •••••••••••••••••••••••••••••••••
VOCABULARY
SECI'ION 5.

STA~ •••••••••••••••••••••••••••••

EXAMPLES OF REPORrS ..................... .

:EX1\t-1PLE 1........................................
EXAMPLE 2 ••••••••••••••••••••••••••••••••••••••••
:EX1\t-1PLE 3....... . .. . . . . . . . . .. . . . . . . .. . . . . . . . . .. .
EXAMPLE 4 ••••••••••••••••••••••••••••••••••••••••
:EX1\t-1PLE 5........................................
EXAMPLE 6 ••••••••••••••••••••••••••••••••••••••••
:EX1\t-1PI..E 7......... . . . . . . . . . . . . . . . . . .. . . . .. . . . . . .
:EX1\t-1PLE 8........................................
~

~

PCN 1177185-002

vi

205
212
231
233
237
241
243
245
249
252
258
259
262
268
272
276
278
279
283
288
293
294
297
298
300
301
308
312A
320
323
324
327
335
339
341
348
349

4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
5
5
5
5
5
5
5
5
5

1
1
3
4
7
8

11
13
15

SEerION 6.

SYSTEM OPERATIONS ASSOCIATED
WITH REPORT PREPARATION •••••••••••••••••
A SERIES OPERA.TIONS ••••••••••••••••••••••••••••••
FILES REQUIRED FOR EXECUTION ••••••••••••••••••
INPUT REQUIRED FOR EXECUTION ••••••••••••••••••

Rt.JN' Statenen.t ••••••••••••••••••••••••••••••

FII..E Staternet1t (s) ••••••••••••••••••••••••••
DATA State!l'IleIlt •••••••••••••••••••••••••••••
Report-Specification File ••••••••••••••••••
?mD Statanen.t •••••••••••••••••••••••••••••
EXECUTION PBOCEDURE •••••••••••••••••••••••••••
Autanatic Execution Procedure ••••••••••••••
User-Gontrolled Execution Procedure ••••••••
Execution Using Work FION language (WFL} •••
B 1000 OPERATIONS ••••••••••••••••••••••••••••••••
FILES REQUIRED FOR EXECUTION ••••••••••••••••••
INPUT REQUIRED FOR EXECUTION ••••••••••••••••••
?EXECUTE Statanent •••••••••••••••••••••••••
?FII..E Staternen.t (s) •••••••••••••••••••••••••
?DATA. Staternen.t. • • • • • • • • • • • • • • • • • • • • • • • • • • •
Report-Specification File ••••••••••••••••••
?Erld Statanen.t............... ••••••••••••••
EXECUTION PHOCEDURE •••••••••••••••••••••••••••
Automatic Execution Procedure ••••••••••••••
User-OOntrolled Execution Procedure ••••••••
B 2000/B 30Do/B 4000 OPERATIONS ••••••••••••••••••
FII..ES REQUIRED FOR EXECUTION ••••••••••••••••••
INPUT REQUIRED FOR EXECUTION ••••••••••••••••••
?EXECUTE Statement •••••••••••••••••••••••••
?FlLE Statemen.t(s} •••••••••••••••••••••••••
?DATA Staternen.t ••••••••••••••••••••••••••••
Report-Specification File ••••••••••••••••••
?mD Staternen.t •••••••••••••••••••••••••••••

EXECUTION PROCEDURE •••••••••••••••••••••••••••
Automatic Execution Procedure ••••••••••••••
User-OOnt~lled Execution Procedure ••••••••
APPENDIX A.

REPORTER III SYSTEM FDDW •••••••••••••••

APPENDIX B.

~ITS

AND DEEAULTS ••••••••••••••••••••

ITEMS, FUNcrIONS, AND CONSTRUCI'S •••••••••••••••••
I'!'E'1t1S •••••••••••••••••••••••••••••••••••••••••

EUlerIaN'S •••••••••••••••••••••••••••••••••••••
BASIC LANGUAGE CONSTRUCTS •••••••••••••••••••••
OOOOL Picture ••••••••••••••••••••••••••••••
I>a.ta
Expression. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ••
Extenlal File NaIne •••••••••••••••••••••••••

NaIIle................................ ..

Uteral .•....•••••....•..•....•....•.••..••
~UAGE Sl'A~ •••••••••••••••••••••••
PROCESS-oPTION STATEMENTS ••••••••••••••••••••••••
DATA.-PROCESSING-oPTION STA~ ••••••••••••••••
REPORT-oPTION STATEMENTS •••••••••••••••••••••••••

REroRI'

vii

6
6
6
6
6
6
6

1
1
1
2
3
3

6

5
5
5
5
6
11
16
16
17
17
17
20
20
20
20
21
22
26
26
27
27
28
30
30
30
31
31
32

6
6
6
6
6
6

6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
A

4

1

B
1
B
1
B
1
B
1
B
1
B
1
B
2
B
2
B
2
B
3
B
3
B
7
B
9
B - 10
peN 1177185-002

MULTIPLE-REPORT SPECIFICATION ••••••••••••••••••••
APPENDIX

c.

B - 11

ERROR AND WARNING MESSAGES

AND EXCEPTIONS LJSTINGS ••••••••••••••••

c-

1

ERROR AND 'VlARNING MESSl\GES •••••••••••••••••••••••

C- 1

E>CCEPrlOOS. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

C - 39

APPENDIX D.

.RESE:R.V'ID WORm. • • • • • • • • • • • • • • • • • •••••••

D - 1

APPENDIX E.

Gr,DSSAR.Y • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

E - 1

INDEX. •••••••••••••••••••••••••••••••••••••••••••••••

1

peN 1177185-002

viii

INTRODUcrION

This manual defines the report language of the REroRl' writER III
(REPORI'ER III) system arxi its use in the system. The report language is
used in conjunction with the vocabulary language of the system to
prepare reports reflecting information in the user data files or data
bases.
Before a report can be prcx1uced, a vocabulary of tenns that
describe pertinent infonnation in the data files or data ba.ses must be
designed and ~eated.
When this vocabulary exists, a rep:>rt-Ianguage
specification which uses it can be designed and processed to produce the
desired reIOrt.
This manual is directed to all users of the report language.
It
presents basic infornation about the language arrl system to the
first-time or occasional user, while it is arranged to allCM easy
reference by the nore experienced user. It furnishes all users with the
detailed infonnation they need to design and specify their reports. It
is anticipa.ted that as the user gains experience in the report language,
the REPORrER III Reference Card will be increasingly relied on when
canposing report-language specifications.
The contents of the manual are organized as folICMS:
Section 1

Section I of this manual provides a general
description
of REPORTER
III, including
features of the system.

Section 2

Section 2 presents basic information
the report language.

Section 3

Section 3 is a guide
specifying reports.

Section 4

Detailed
e~lanations
of all
language
staterrents, clauses, language constructs,
and functions used to design and prepare
reports
are provided in Section 4, in
alIflabetical order.

Section 5

Examples of reIOrt-language specifications
and the reports produced are presenterl in
Section 5.

ix

for

about

designing

and

peN 1177185-002

Section 6

Section 6 contains information on
operations
associated
with
preparation.

Appendices

The four-phase system process of report
preparation
is depicted
and
discussed
briefly in Appendix A. Limits and defaults
associated
with
report-language
specification are indicated in Appendix B.
Error and warning messages associated with
system
analysis
of
report-language
specifications are listed and explained in
Appendix C. Exceptions also are listed and
explained,
separately,
in Appendix
C.
Appendix D presents a list of all reserved
words of the report language. Appendix E is
a glossary of tenns used wi thin this manual.

system
report

The follONing manuals explain the use of the REPORTER III system and the
optional On-Line REPORl'ER III nodule.
Operations Guide, REPORrER III Vocabulary Language (Relative to 2.4
Software Release), fonn 1177177.
Reference Card, REPORrER
fonn 1177318.

III (Relative

Capabilities Manual, REPORl'ER
Release), fonn 1177300.

III

User I s Guide, On-Line REPORI'ER
Release) ,fonn 1177151.

III

to 2.0 Software

( Relative
(Relative

Release),

to

2.0

Software

to

2.0

SOftware

Note that the "REPORI'ER III Vocabulary Language Operations Guide" was
formerly
titled "REPORl'ER III Vocabulary
Language
User I s Guide. II
SUbsequent references to the guide do not reflect its new title.
The REPORrER III System is designed for use with the following:
1.
2.
3.
4.

A
B
B
B

Series of Systems.
1000 Series of Systems.
2000/B 3000/B 4000 Series of Systems.
5000/B 6000/B 7000 Series of Systems.

peN 1177185-002

x

Note that throughout this guide, instructions for A Series also pertain
to B 5000/B 6000/B 7000 Series of Systems. Also note that when the word
"COBOL" is used, it refers to the appropriate ANSI-74 COBOL for each
system.
If you are using an A Series System, the term "COBOL" also
refers to ANSI-85 COBOL.

xi

1177185-003

SECrICN 1
SYSTEM DESCRIPTION
The REPORTER III System provides an effective means for creating a wide
variety of management reports reflecting information maintained on a
computer system in the Unisys A Series, and BlOOD through B 7000 Series
of Systems.
SYSTEM FEA'IURES
REPORTER III greatly facilitates the retrieval, analysis, and reporting
of data by using the power of the computer system to perform tasks such
as the following:
1.

Select data on the basis of simple to complex criteria.

2.

Match records on the basis of data field values.

3.

Sort data as specified in ascending and/or descending order
according to multiple keys.

4.

Automatically age data, using a variety of date formats.

5.

Determine statistics including count, total, average, maximum,
mlnlmurn, sum squares, mean squares, variance, and standard
deviation.

6.

Handle multilevel control breaks and ranges, and give summary
statistics for each control break or range.

7.

Automatically format information for printed reports.

8.

Automatically schedule phases of report processing,
providing override options.

9.

Create one or more files
processing or reporting.

of extracted data

for

while

subsequent

important aspect of REPORTER III is that its features can be used in
auditing applications.
The system is applicable to both internal and
external auditing activities. REPORTER III provides the auditor with an
effective means to test and evaluate the information maintained on the
computer system. It greatly aids the auditor's analysis by using the
power of the computer system to perform such tasks as the following:

An

1 - 1

1177185-003

1.

Test derived data items (extensions) and footings.

2.

Select and print audit samples.

3.

Examine records for
conditions.

4.

Summarize data.

5.

Compare duplicate or
consistency.

6.

Compare audit data with computerized records.

7.

Extract information for subsequent processing and evaluation.

8.

Print confirmation letters.

completeness,

related data

consistency,

for

and

correctness

valid

and

The REPORTER III System can produce multiple reports in one pass of the
input data.
Also, the system enables you to control the formatting of
reports as well as output information on preprinted forms, if desired.
REPORTER III can report information from data files contained on
magnetic tape, disk, and punched cards. The system also can report
information from DMS II data bases.
LANGUAGE INIERFACE 'ill SYSTEM
The REPORTER III System includes two free-form languages:
1.

Vocabulary Language - a language designed to create a
vocabulary (dictionary) of descriptions and definitions of the
data to be reported. The vocabulary language can accept an
independent description, or it can use existing COBOL record
descriptions and/or data-base directories.

2.

Report Language - a report-description language which enables
the specification of a wide variety of reports. The language
is easily used by non-programmers.

REPORTER III generates a COBOL program tailored to your exact reporting
requirements.
Note that whenever "COBOL" is referred to, it means the
appropriate ANSI-74 COBOL or ANSI-85 COBOL for A Series systems or the
appropriate ANSI-74 COBOL for any system other than A Series.
The generative approach

1177185-003

1 - 2

speeds recurrent reporting, and it also provides the flexibility needed
for cost-effective one-time reporting.
REPORl' ~ AND SYSTfM OPERATIW

'!he
REPORl'ER III report language provides a methcxi for quickly
specifying reports based on information ccntained in the data files or
data
bases.
With appropriate selection, grouping, ordering, and
sunmarizing, the information is fumished in a useful report fOIm by the
system.
Infonnation can be furnished as a printed report, or it can
easily be extracted in machine-readable fonn to a separate file for
further processing.
The report language is free-fonn, "English-like, II and concise. Little
writing is necessary to prepare the report-language specification, ~ich
describes
the contents
of the report.
Yet the report-language
statements are readable and self-documenting.
The language includes
many default features and thus does not require that you specify each
opticn. Each data item of infonnation is specified by name, and you are
not required to kfx)w its size or fonnat characteristics. The format of
the report, whether sinple or catplex, is detennined by REroRl'ER III,
unless you chcx:>se to specify the fonnat requirements.
'!he report-language specification which you have written (also referred
to as the "report specification") is input to the Report Language
Analysis Program (RP3REP) , which analyzes your request and prints a
listing of the specification as given. If the request is invalid, the
errors are indicated by means of appropriate messages, and you nust
oorrect the mistakes and resutmi t the specification. If the request is
valid, a parameter file is prcxiuced whiCh represents your specific
request
canplete with "physical
information
obtained fran the
referenced vocabulary.
'!'he rep)rt-program generator (RP3GEl'i) then is
run automatically to generate a COBOL source program based on the iqput
parameter file. '!be generated COBOL source program is then OClIpiled and
executed automatically, and the desired report is produced.
II

The generated report program can be treated either as a one-t..i.ne-only
report program or as a recurring report program which is run as often as
required without regeneration.
A nore detailed explanation of system operation, together with a diagram
representing the report-preparation process, is contained in Appendix A.

1 - 3

EXAMPLE REPORl'-LANGUAGE SPECIFlCATICN

The follO#ling is an exanple of a rep:>rt-language
together with the job caltrol language stateIrents
report.
The control statemnts are preceded by
This example assumes input of the specification as

specif ication, shewn
needed to produce the
a question mark (?).
a card deck.

?EXEOJ1'E RP3REP
?Dl\TA RP3CRD

VOCABUlARY IS "CLIENr".
INPl1I' AO-"'TS-REeV.
SELECT ~CE-DUE GRFATER '!HAN CREDIT-LIMIT.
TITLE uACCClJNrS 0VERDRAW1.~ ...
HEPORr CUST-I-D, BRANQi, CREDIT-LIMIT, ~CE-IX.JE.
SlH1ARIZE roarm:; BAlANCE-DUE.

?END

'llie six report language statements in tilis specification are explained
belcw.
The specification is designed to provide a report containing
infonnation reflecting all accounts which are overdrawn.
The VOCABUlARY statement identifies the vocabulary of names used in this
report language specification to describe t.he infonnation in the data
base.
The vocabJlary is created by the program RP3VOC.
(Figure 2-7
lists the vocabulary identified here.)
The

INPl1I' statenent specifies that all accounts recei vable informatioo
be input.
(ACCl'S-RFLV is a LMS II data set which can be thought of as a

file. )
The SELEL.~ statement specifies tllat only those accounts in which the
balance due is greater than the custaner credit limit be refOrted.

The

TITL£ statement describes the title to be placed at the top of eaCh

page of the report.
rrhe REFOR"f statement s}Jecifies that the custexoor nunber, branch nUItDer,
credit limit, and balance due be reported for each selected custaner
account.
The SU1~ZE statement specifies that the balance due colunn be footed.
This gives the total balance due of all overdrawn accounts.

I - 4

Figure 1-1 shows tbe report produced fran this specificatioo.
'!he
requested infonnatioo has been fonnatted autanatically into a readable
report.

PAGE 1

CRmIT
LIMIT

001302
002117
051231
081311>

0013
0020
0013

1000
1000

0008

2000
3000
500

100500

0034

101137
102800
120060

0130
0130

500

5000
500

0038

$ 1311.80
$ 1560.00
$ .732.00
$ 2016.80
$ 3810.21
$ 511.37
$ 6387.50
$ 643.70

$16973.38

Figure i-l.
Other

exanp1es of

Sanple Report

reprt-language

specifications are

Sections 2 and 5.

1 - 5

provided

in

SECl'ICE 2
BASIC INroNMATION ABaIr
'!HE REPORI' IAlGJAGE

The REPORl'ER III report language is a high-level language based 00
English and canpos~ of characters, 'NOI'ds, am statements. This section
documents basic elements of the report language and the method used to
define the language, and presents sane basic teI'1U:inology used for data
identification. It also describes the various types of vocabllary names
which can be specified in appropriate contexts in the report. language.
Finally, sanple vocabularies used in exarrples througlOlt this manual to
illustrate various language constructs dIld statements are presented.
For brief explanations of basic language oonstruct.s and functions used
in defining informaticxl in language statements, refer to Sectioo 3.
Detailed explanations of the oonstructs ~ functions are provided in
Sectioo 4.

The report. language dlaracter set consists of the digits 0 through 9,
the letters A through Z, the blank or space, and the following syni:x>ls:
Symtx?l

*

@

[
]

,
$

=
>
<

#
(
)

%

+
II

.,

/

Definitioo
-----.dsterisk or multiplication sign
at sign
bracket, left
bracket, right
colon
carma
dollar sign
equal sign
greater than symbol
less than syni:x>l
minus sign or hyphen
number sign
parenthesis, left
parenthesis, right
percent sign
pericxi or decimal point
plus sign
quotation mark
semioolon
slash or division sign

2 - I

SPECIFICATION FORM
The report language CdIl be written on any OOBOL-canpdtible a:xiing _....,LIll
to facilitate keypunching or data entry of card .images. You write the
free-for.m statenents between oolumns 8 dnd 72, usirlg one or nore spaces
or appropriate punctuation bO delimit elements of the language. Columns
1 through 6 can be used for sequence nurrt>ers. ColunulS 73 through SO are
available for optional use, such as identification, remarks, etc. The
sequence number fields can be used later to indicate the sequence
numbers corresponding to source language statements which dre to 00
updated. O:>lurm 7 is not used.
ClM-D:Nl' INDICATOR
-------

percent sign (%) placed in columns a through 72 indicates that tile
characters Which follow the sign are a part of a user COmlent.
Tnese
comnents are rx:>t part of the report language and, therefore, net..~ oot
follow the rules of the language. They are useful for docl.lIrentation of
the language specifications.

A

Exanples:
% AN EXAMPLE OF '!HE USE OF ~.
REPORr A, S, %  is a user-defined word. The  is defined as part of the
report language by its existence in a referenced vocabulary or its
definition in the report language specification.
In general, s
should not be chosen which are identical to reserved words in the report
language becduse I
in certain contexts, such  s might be mistaken
for the reserved words.
METHOD OF lANGUAGE DEFINITIOO
The report language is def~ned by rules of syntax and semantics.
The
syntactic
rules deter.mine the structure of valid report-language
statements.
The semantic
rules determine
which report-language
statements have valid meanings and what those meanings are.

2 - 3

SYl\1TAX DIAGRAMS

The syntactic rules of the report language are described by syntax
diagrams constructed of words and arrc:ws.
A syntactically correct
statement is produced by trdcing any path along tile direction of ~le
arrows in a given syntax diagram. Words and syrci::x:>ls are written as they
are encountered along the line paths.
The syntax diagrams occasionally must be continued on new line(s). In
this case, the break in an arrow is shown by means of connectors using
the same number at each end of the break.
An example syntax diagram (with connectors) is shown below.

Example:

+<- , <-+
1

1

----->ROW----->THE------->~T------------------>~~-->(l}

1
I
+->YOUR->+

(1)---->
1

I

1
1
+-->GENTLY-->+

- ---------------------------------->STREAM.
I
I
+-->+

1
1

1

I

1
I

1------------->+

I

1

I

I

+-->THE---->OID-----> , --->MILlr-->I
I
1
+------------------->+
Valid productions from this syntax diagram include:
IUd THE OOAT OOWN-STREAM.
IDIl, lOll, lUi YOUR B(lll.T GENTLY DJWN THE STREAM.
R)W, R)W, lUll, lO-l THE OOAT [Uti THE OLD S'I'REAL'1.
fOl YOUR BOAT IXJdN THE MIIL STREAM.
R)W THE OOAT IOIlN THE OID, MILL STREAM.

A bridge over a number indicates that the path can be traced a maximum
nwti::>er of times specified by the nuni:>er under the bridge.

2 -

4

ExaDple:
-)ACRlSS-)THE~----'

1

1<
I
I

, <--

1

I-~--)BIG----)I

I
I

I
1

I
I

I
I

I-~-)WIIE--)I

+-~-)KJDDY-)+

Valid productions fran this syntax diagram includea
ACa;S '!HE MIS&1JRI
ACRa;S THE BIG MISSDRI
~

'DE KIDDY, WIlE MISSClJRI
BIG, WIDE, KJDDY MISSlJRI

ACRa;S THE

but eX> not. include:
ACRa;S THE BIG, BIG MISSlJRI
~

'l1tE WIlE, BIG, WIlE MISSCXJRI

A bridge CNer a runber with an asterisk nuat be traced at least aloe,
but not IIDre than the maxinun nunIJer of times specified by the nUDber.

+<- , <-I 1*
I
I

/--+
I
I

-)ACRlSS-)THE----~-)BIG----- -----)MISSClJRI

I
1

1
I

I
I

I
I

I-~-)WIJE--)I

+-~-)f4JJDY--)+

2 - 5

Valid productions fran this syntax diagram include:
ACX>SS THE BIG, WIDE MISSOURI
ACROSS '!HE WIDE, KJDl)Y MISSOURI

but do not include:

ACROS5 '.tHE BIG Hl~RI
ACROS5 THE BIG, WIlE, HUlDY MIS&lJRI
ACROSS 'IHE BIG, BIG MIS9XJRI

Nunt>er bridges usually are used with loops, dB in tile pre<..~ing
exanples.
Once a loop is exited, all runber bridges within that loop
are .. rE:!set" for the next 4:!lltry into the loop.
Exanple:

+<-----------------------,
I

~<------------------------+

I
I

I

->~--->'I'liE_----------------!T7->MISfl:AJRI------->

1

I

1

I

I

I

I

I

1<---, < - - I 1
1
I
1 I-rrl->~--->I
I
I 1
1
I--f~-->BIG--->I 1
I
I
I 1-!T7->M!SSISSIPPI-> I
1-!T7->WllE--> I
I
I
I
1
+--!T7-->l-IJDl)Y->+

I
I
1-!T7->OHlo-------->I
1
I
I
I
+-/-r-,-->GULF--------->+

Valid productions fran this syntax diagram include:
Inti THE MISSOURI
IXJilN '!HE BIG CliIO
OOWN THE BIG ana, mro THE BIG, WIlE
IL~ THE BIG, WIDE, MUDIX GULF

2 -

6

~lISSISSIPPI,

but do not include:
ID'JN THE BIG OHIO, INI'O THE KJDDY, MUDDY I"iISSISSIPPI
.oowN THE BIG OHIO, INro '!HE MUDDY CIllO

RESERVID WORIX;

Words in uppercase letters are the reserved words in the language: these
words must be written exactly as shown in the syntax diagrams.
Keywords are ~le reserved words required to complete tile meaning of
language stateJtEnts.
Sane keywords can be qbbreviated by anitting
letters fran the end of the word. The mininun required abbreviaticn is
under linerl in the syntax diagram.
If a keyword must be used in its
entirety, the entire word is underlined in the diagram.
Optional words are reserved words having no semantic neaning. Optional
words are included in the language to ~rove the readability of tile
staten~nt
formats.
They are never underlined in the syntax diagrams
and, if used, cannot be abbrevidted.
Example:
-->VOCABULARY---------------------------->-->.

I

I

+-->Nru1E-->+

I

I

+-->15-->+

'nle reserved words are VOCABUIARY, NAME, and IS. VOCABUIARY is a
keyword and can be abbrevidted as VOCAB, Vtional words and ItUst be spelled out if
they are used.
PUNCI'UATION

Special characters such as the parenthesis, oolon, period, and corrma
must be written as they appear in the syntax diagrams.
Keywords,
optional words, names, numeric constants, and Character-string constants
must be separated fran each other by a blank or a special character.
Wherever a blank is r~uired, several blanks optionally can be used.
Blanks
optionally can be placed around special characters
for
readability. A blank immediately before a period is not required except
when a period immediately follows a numeric literal.
2 - 7

~ACl'IC

VARIABLES

Phrases set off by angle brackets ( <» are syntactic variables 'lthich
represent information to be supplied by you. A particular variable can
represent a sinple language element, such as an integer, character,
string, or name; or it can represent a relatively c:x:llplicated language
oonstruct, such dS a Boolean expression.
'lhese variables are defined
either by verbal description or by syntax diagrams of their cwn. In
either case, any valid language element or 1n'iN THE 

-->

:
-->MISSISSIPPI

>

I

I

I

I

1->CDIamIA---> I

+->HI.JDSCN----->+

:
--->ATIANTIC--->

I

I

l-->PACIFIC------1

I

I

+->GULF----+

In the first diagram, "river" and "ocean" are syntactic variables. Both
valid
are
defined by the diagrams
that follOri.
Syntactically
productions include:

mro '!HE GULF
THE ~IA Itm> THE PACIFIC
IXJiN 'DiE CDIJ.IeIA mro 'mE GULF
Inti THE MISSISSIPPI INro 'lHE PACIFIC
Inti 'lHE MISSISSIPPI
~

2 -

8

~IC

RUlES

Semantic rules are linked to the syntax diagrams by means of letters
label. the critical paths. '!he letters reference paragraphs which
explain the meaning associated with the oorrespooding syntax path, and
explain additional rules associated with a choice in paths. 'lhese rules
can make certain syntactically correct statements invalid.

~dl

Exanple:
->~I!l

- -

THE  INTO '!HE -->

__

_ _

-..::c::'!_

:
A

-->MISSISSIPPI---->

I
I

-

I
B
I
1->CDI.ll'-1BIA--->I
I
I
I C
I

+-->HJD&>N---->+
:
A

--->ATLANTIC--->

I

I

I B
1
1->PACIFIC---> I

1

1

I C

1

+->GULF---->+
sellBntic rules are written so thdt they pranpt you to choose the
oorrect. paths am supply the appropriate infonnation. Thus, by tracing
the syntax diagram paths and reading the "path pranpts," you supply the
information
fcc the report
specifications
Which
describe
the
application.
'!he

If the example above were actual syntax (such as the syntax described in
Sectioo 4), the semantic rules for  would be explained in
accanpanying paragraphs labeled A, H, and C. The semantic rules for
2 - 9



would be explained in accompanying paragraphs labeled A, B, and
paragraIils ~ld explain that the choice of river must
oorrectly match the choice of ocean so that the river flO\;lS into the
correct ocean. Semantically valid p~uctions include:

C.

These

~

'!HE MISSISSIPPI INrO THE GULF
In'lN THE li.UDSCN 1tm> THE ATIANl'IC
IXlWN '!HE lllMBIA Ii'lI'O 'l\iE PACIt'IC

but do not include:
00riN '!HE MISSISSIPPI INro THE PACIt'IC
0CNlN THE R

~TA

---- IDl:Nl'1t'1CATION
---

In specifying the semantic rules of the report language, various tenns
are used consistently to identify data or information. These t.enns are
defined in the follcwing paragraphs.
mTA ITEM OR ITEM
A data item or item is an elementary item of information.

In the report
language, data items are referenced by data names, numeric literals,
character strings, or expressions.
Examples of data items are tile
follOAfing: the number of parts on order, the name of the individual, the
total balance of aged accounts, and the percent utilization factor.
items are numeric, string, or Boolean.
numeric values; string items have character
have values of TRUE or FALSE.
Data

Numeric data items have
values, and Boolean items

GROUP

group is a collection of related data items which could be thought of
as a single data item. For exarrple, a date can be a group consisting of
the data items nonth, day, and year.
Or an address can be a group
consisting of the first, seoond, and third lines of the address. Groups
referenced in the report language are considered string-valued data
items.

A

2 - 10

RECDRD

A record is a collection of related data i terns and/or groups. The tenn
"record" is used to mean a record, list element, or meni;)er, dependirig 00
the teon which is appropriate for the type of data structure urxier
consideration.
A record might include all infonnation pertaining to a
client I s account, such as custaner name, account I'UJltt)er, aBi current
balance.
A record might consist of infonnation pertaining to an
employee, .such as name, age, sex, salary, and job grade.
DATA STRUC'ruRE

A data structure is a collection of records. . Access to infonnatioo
contained in' data structures is indicated in a rep'rt specificatioo by
the INPlJI' staterrent. A data structure might contain infonnation 00 all
client accounts, or it might contain records for all June order
transactions.
Valid data structures for the report language include
system files that can be described in COBOL, and OMS II data sets.
DATA BASE

A data base is a collect.ial
relationships between them.

of ooe or nore

data

structures

and tlle

u:x:ilCAL REa:>RD

A logical rt!COrd is a record or a group of associated records which
contains all pertinent information about a single entity.
Records
comprising a logical record can come from a single data structure,
multiple data structures, or a user input routine. Certain infonnatioo
wi thin a logical ret.~rd can contain null values indicating the absence
of related information.
The INPUT statement in a re~ specification
specifies what information eaCh logical record contains and l~ this
information is accessed.
an example, a logical record may ccnsist of infonnatioo alx>ut a
single transaction, including pertinent information about the account to
which the transaction applies. Ac another example, each logical record
may consist of information gathered from various sources about a single
employee. In addition to containing such infonnati~ as na.ne and salary
fran the payroll master file, the logical record ca.tld contain employee
address infonnation obtained fran the address file. Infonnation about
the employee's job grade and department ~ght be obtained from records
in separate but related files.
Of course, job grade and department
As

2 - 11

information within the logical record probably
many employees (see Figure 2-1).

would be identical

for

A logical record as defined by the INPtn' statement is an underlying
concept behind the report language description. Specifications can be
given to extend, select, sample, group, order, sUI'l1l\a.rize, extract, and
report the information contained in the logical records.
Logical records can be viewed also as rows within a large table (see
·Figure 2-1). A colunn in this table would represent a single item. The
tabl~ . is first defined
by the INPlIr statement
in the report
specification.
Subsequent
language
statements
in
the
report
specification can extend, select, sample, group, order, sunmarize,
extract., and report the infonnation contained in the rOVlS of the table.
A logical record can be accessed only once since only one pass is made
through the specified data per report specification when the report
program is run. In tenns of preparing a report specification, this
means that once you have specified access to·a logical record, you
cannot specify access to that logical record again.
Thus, for exanple, the following combination of physical records within
a
particular
logical
record cannot be reflected
in a report
specification because such a combination would involve more than one
pass through the specified data:
P~SICAL RERD
NECDRD
RroJRD

2
2
4
4

for the tenn "logical record" in various

2 - 12

JOB
SAIARY

AGE

532.00

21

101 HIGH sr.

3

EDP

0611

1,100.00

27

332

7

EDP

0611

632.05

27

1222 3RD sr.

7

ACCr

0232

BAKER, SUE

711.00

23

27 RIVER RD.

7

ACCr

0232

JAl-1ES, HELEN

883.00

37

1001 51 ST.

5

EDP

0611

930.00

41

531 PEACH sr.

5

MK'lG

0110

KElLY, MARY

650.30

33

011 3RD AVE.

5

EDP

0611

KEN

1,232.00

52

1311 CYPRESS

7

MK'lG

0110

766.45

24

303 WEST 8TH

7

MK'lG

0110

811.50

32

200

7

srAFF

0777

950.61

30

17

5

STAFF

0777

NAME
OOE,

Jan~

~lITH,

JOE

~,

BILL

OOB

JOOFS,

~,

SMITH, SUE

HIlL,

~

J~, KAREl~

Figur~

2-1.

ADDRESS

MADISJN

FAST 3RD

VAln~:Y

DR.

GRADE DEPARlMENT DEPr.NO.

Logical Records for Personnel

A control-break item is a data item used to group the infonnation to be
reported.
All logical records which contain the same value of the
c:x>ntml-break item are grouped together for purposes of reporting the
information and calculating statistics regarding the information.
For
exanple, all transactions can be grouped by account Ill.lI'Ci::>er.
For
purposes of reporting, the information aba.lt a transaction can then be
listed under the appropriate aOLuunt-number heading.
In addition,
sumnaries such as the average transaction anount for each account can be
obtained.
A control-break item can be suoordinate to another control-break item
which, in turn, can be suoordinate to yet another control-break item.
('nle limit en the nunber of levels of control-break items is nine.)
Information is then hierarchically grooped based on values of the
control-break i terns. For example, transactions can be grouped based 00
account number, am accounts can be grouped based on account type. Thus
for each account type there are many account nunbers and, for each
2 - 13

account number, there are lnany different transactions.
In Figure 2-2,
the persormel data shoNn in Figure 2-1 is grouped by department and job
grade.

-~-'.

DEPARI'MENI'

DEPr.NO. GRADE

NAME

SAlARY

AGE

......

ADDRESS

ACCr

0232

7

BAKER, BILL

632.05

27

1222 3RD ST.

Acc:r

0232

7

ilAKER, SUE

711.00

23

27 RIVER RD.

EDP

0611

3

ooE, JOHN

532.00

EDP

0611

5

JAl'rlES,

EDP

0611·

5

KEILY, MARY

~

101 HIGH S'f.

EDP

0611

7

SMITH, JOE

1"lK'ro

0110

5

JONES, OOB

MK'ro

0110

7

NE.'Nt-1AN, KEN

MlcrU

0110

7

grAFF

0777

srAFF

0777

HELEN

883.00

37

1001 51 ST.

33

011 3RD AVE •

1,100.00

27

3.32 l"1ADISON

930.00

41

531

1,232.00

52

1311

SMITH, SUE

766.45

24

303 WEST 8TH

5

J(NS, KAREN

950.61

30

17

7

HIlL,

811.50

32

200

650.30

-_ .....
...... .

...

lX)N

P~

ST.

~RESS

V~-y

~T

DR.

3RD
..

Figure 2-2.

Logical Records for Personnel
Grouped by Control Breaks

RANGE-BREAK ITl!M

A range-break item is a s~ial oontrol-break item which is based on
specified value ranges of a particular data i tern. This data item is
referred to as a ranged item. All logical records .which oontain values
of the ranged item within specified limits are grouped together for
puqposes of reporting the information and calculating statistics on the
infonnation.
To accanplish this, the infonnation is ordered in
ascending
sequence based on the ranged item.
For example, all
transactions can be grouped based on transaction anount such that all
transactions within the foll()INing ranges are grouped together: 0 to 1000
dollars, 1000 to 5000 dollars, 5000 to 10,000 dollars, and over 10,000

2 - 14

dollars.
A count of all transactions for each defined ancunt range can
be obtained.
range-break item itself is a string item whose values iOOicate a
10rler- arxl upper-limit of the ranged item. A range-break item value can
be assigned to each logical record to indicate the range to which it
belongs.
In Figure 2-3, the personnel data shown in Figure 2-1 is
grouped based on age, such that all enployees within the following age
groups are grcuped together: 20 to 29, 30 to 39, 40 to 49, and 50 to 59.
The

JOB
DEPAIt'rMDJ'l' DEPr.RO. GRADE

BAME

SALARY

AGE

ADDRESS

RAHGB

EDP

0611

3

DOE, JOHN

532.00

21

101 HIGH ft.

20-29

ACCT

0232

7

BAlCER, SUE

711.00

23

27 RIVER RD.

20-29

MKTG

0110

7

SMITH, SUE

766.45

23

303 WES,. 8TH

20-29

EDP

0611

7

SMITH, JOE

1,100.00

27

322 MADISOH

20-29

ACCT

0232

7

BAKER, BILL

632.05

27

1222 3RD S,..

20-29

STAPP

0777

5

JOBES, KAREN

950.61

30

17 VALLEY DR.

30-39

STAPP

0777

7

HILL, DOH

811.50

32

200 EAST 3RD

30-39

EOP

0611

5

KELLY, MARY

650.30

33

011 3RD AVE.

30-39

EOP

0611

5

JAMES, HELER

883.00

37

1001 51 ST.

30-39

MKTG

0110

5

JONES, BOB

930.00

41

531 PEACH ST.

40-49

MKTG

0110

7

NEWMAN, KEN

1,232.00

52

1311 CYPRESS

50-59

Figure 2-3.

Logical Records for Personnel
Grouped by Range Break

2 -

15

INPUT DATA ITEM

input data item is an item which is part of the infonnation to be
input for the report. For a single-report specification or the  of a multiple-repoct specification, ~ut data items are those
described in the specified vocarulary; these data i terns are defined by
reference to the appropriate data structures in the INPUT statement and
by
extensions.
For the 
of a nultiple-report
specification, input data items are defined in the  by
the INPUI' statement and in the  by extensions.
An

ACCEPTED mTA ITEM
-------.--

accepted data item is a data item which is defined in the ACCEPT
statement.
'!his data item ~erves as a run-tirre parameter for repn~
specificc.tion.
The actual value of the data item is read in by the
generated report program before any processing begins.

An

mTA ITEM
-DERIVED ----

derived data item is a data item which is described in tenus of other
data items via an . The value of this data item is "deri.ved"
fran input items, accepted items, constants, or other derived data
items.
aombinations of arithmetic operations, logical operations, and
REPORI'ER III intrinsic functialS can be used to canp.1te the derived data
i tern.
A derived data item represents an extension of the logical
rea::>rd.

A

----

STATISTICAL DM'A 1'1'&1

A statistical data item is a derived data item which is defined in tenns
of ooe or roore statistical functions or other statistical data items.
For example, the  in Section 4.)

2 - 17

GRaJP NAME

A  refers to a group of data items described in the
vocabulary. A  can be qualified and subscripted. (Refer to
the explanation of  in Section 4.)
When referenced in the report language, a group is treated as a
string-type item.
When using a vocabulary created prior to the 2.50
software release, all group items are assigned a default character
length that can be changed by the Process-option statement SET
STRING-SIZE. (Refer to the explanation of the Process-option statement
in Section 4.)
For a vocabulary created using the 2.50 or later software release, the
size of the group item reflects the size of data items subordinate to
that particular group item. Both the size of the group item and the
release level used to create the vocabulary can be found in the
vocabulary report.
MACRO NAME

A  refers to a permanent macro included in the vocabulary.
A permanent  can be referenced any number of times in the

report specification once the VOCABULARY statement is given. If formal
parameters were defined for the macro, the values of the actual
parameters must be specified whenever the macro is referenced.
The
appropriate macro text replaces each reference to the permanent .

1177185-003

2 - 18

CCNDITIOO

NAME

A  refers to a COBOL 88-level , which
represents one or more specific values of a data item. A  can be qualified. In the report language (except when using the
PRESELECT clause), a  may be referred to only in the
following context:


= 

or
 NOT

= 

For example, the  THIS-MONTH identifies the 12 months of a
year with subordinate s defined as JANUARY through
DECEMBER having assigned values of 01 to 12. The following statements
use the s present in the vocabulary.
SELECT THIS-MNrH = FEBRUARY OR THIS-MONTH
REPORT THIS-MONTH, AM:UNI'.

2 - 18A

= MAY.

1177185-003

preceding statements result in the nonth being made available for
reporting and the proper intemal oode being cxmpared for selection. An
example of the output resulting fran the statements follows.

The

Exanple:
THIS KlNl'H

10.50

2.75
89.96

12.24
18.95

A record name refers to a CXB)L 01 level record ~ch  refers to a (DOOL- represents the internal name rather than the
external name of the file.

A

LINK NAME
A  refers to an A Series I»tS II-defined link item.
name> can be qualified.
DATA-BASE NAME

A  is the name of a I»1S II data base.

2 - 19

The  refers to a DASDlrdefined (Data And Structure
Definition Language-defined) OMS II data set. A  can be
qualified.
SET NAME

A  refers to a DASDL-defined J:Io5 II set or subset which spans
a data set. A  can be qualified.

 designates a user-supplied CDooL input
procedure. An input procedure is defined to RP3VOC by the user in order
to access data structures not handled by standard REPORl'ER III-supplied
input routines.
One call 00 the input procedure returns one record.
That record oontains data fran cne or rrore records accessed fran one or
nore data structures by the procedure.
An

2 - 20

Figures 2-4 through 2-9 shew listings of six sanple vocabllaries used in
exanples
throughout
this manual to illustrate
various language
constlUcts and statements. It is assumed that RP3VOC was used to create
these vocabllaries.
All exanples in the manual that use one of these
six vocab.llaries identify the name of the vocaWlary.
Secticn 5
describes RD'ORl'ER III applicatioos that use the information described
by the vocabllaries.
While JIDSt of the vocab.llary listing is self-explanatory, various
entries rEqUire sane additiooal explanation.
Explanations of these
entries follow.
lAVE[, describes the hierarchical level of an element.
That is, it
describes which elements are actually part of other elements.
For
exanple, items in many instances are described as part of a group.

The level of an element in relatioo to other elements is indicated by a
mmi:ler (level Ill.IIdJer).
Elements assigned the same nunber are at the
same hierarchical level. Elements assigned larger I'l1lIl'i:lers are at lcwer
levels ani are actually part of the inmedi.ate preceding element assigned
a smaller nunber. For exanple, in Figure 2-6 PARl'-NC>-SltD and lAST-SALE
are at the same level; KNrH-SlID is part of IAST-SALE, am ~SALE is
part of PARl'-SALES-R!X:.

iDiicates the l'lllI'Iiler of subscripts required for an element.
If an  or  requires no subscripts, the entry in
this oolunn is blank.
SUBSCRIPl'S

describes
print the item.
UHi'lH

the I'lUIli:ler of characters

2 - 21

rEquired on the listing to

Figure 2-4 lists the vocabulary for an enployee file which is maintained
the Personnel Department.
There is one reoord in the file for each
enployee. The entries in each record used are as follon:

by

Name

~oo

EMPm-NAME

JOB-GRADE
DEPl'-OO

CBrCXDE
EMPIDYMafi'-YR·
EMPm-AGE
SEX
~

FIDERAL-TAX
STATE-TAX

&lC-SEX:-TAX
EMPm-NET-PAY

Descriptial
&tployee nuniJer
&tployee name
Code for enployee' s job level
Department nuniJer
Clarge oode
Year of euployment
Age of enployee
Sex of enployee
Salary of enployee
Federal inoane tax withheld
State incane tax withheld
Social Security tax withheld
&tployee' s net pay

2 - 22

RP3 N.lti

VOCABULARY

ID t-M1 YY
1
PAGE

''VOc»fp''

&YS'l'F.H FILES.
FILE &U?m-FlLE,
OIGANIZATION IS smuENrIAL,
rorAL-POPUI.ATI~ IS IEFAILTID 'ro 9999.

LEVEL

NAME WI'l'ti
(lJALIFIERS

1

&U?m-REXDRD

2
2
2
2
2
2
2
2
2

~-N)

2
2
2
2
2

SJEaUPI'S

GRXJP
ITEM NUMERIC

EMPYE-NAME

ITEM STRING
ITEM NUMERIC
ITJ:l.1 NlH:RIC
ITEM NUMERIC
I'lD1 L~C
ITEM NUMERIC
I'lD1 NlH:RIC
ITEM NUMERIC
mIDITION
CDNDITICti
ITr1-1 NlI£RIC
ITEM NUMERIC
I'lD1 NlI-tERIC
ITEM NUMERIC
ITEM NlH:RIC

EOOCATICE-u.vEL

JOB-GRADE
DEPT-a:>
OI:HDDE
~I.DYMENl'-YR

&U?m-AGE
SEX:

MME
EDWE
SALARY
FEDERAL-TAX
STATE-TAX
SOC-SEC-TAX
~NE:r-PAY

Figure 2-4.

'nPE

Vocabulary

LENmi

6

9(6)

10 X(30)
2 99
2
4

99
9(4)

6
2
2
6

99
99

10
10
10
10
10

Listing for ''VOc»fp''

2 - 23

mITIS:;
PICIURE

9(6)

9
$Z(6).99
$Z(6) .99
$Z(6) .99
$Z(6) .99
~Z(6)

.99

Figure 2-5 lists the vocabulary for a fixed-asset master file Which
WOlld be available at the end of each year cm:l as of the current balance
sheet date. There is ooe record in the file for each fixed asset. The
entries in each record are as follOl1S:

Name
ASSE'l'-R)

ASSET-IESC
ASSET-nPE
DEPT-li)

IDC-aDE
ACQUISITIC»-YR
ASSET-LIFE
~

CDS'l'
Aa:UM-IEPRE-BJCJ<
Im'RE-Yro-BXJ(
Aa:UM-DEPRE-TAX

Description
Asset nL1Ililer
Asset descriptioo
Asset type code
Associated department nunber
IDcatioo code
Year of a~sitiQ1
Asset useful life in years
Tax depreciation methcxl
original asset cost
AccuIrulated depreciaticn, beginning book
Depreciation, year-to-date book
AccUlrulated depreciatioo, begiming tax

2 - 24

RP3 N.NN

VOCABULARY

DO tMo1 yy
PAGE
1

"VOCASl'''
SYSTEM FILFS.

FILE ASSEl'-FILE,'
OIGAN1ZATICE IS S!UJENl'IAL,
TOl'AIrPOPUIATICE IS IU'AULTm 'ro 9999.

NAME WI'lH

I..E.VEL CJJALIFIERS

1
2
2
2
2
2

2
2
2
2
2
2
2
2

ASSEl'-ImDRD
ASSET-W
ASSET-IESC
ASSET-TYPE
OEPl'-OO
IDC-aDE
ACOUISITI~-YR

ASSET-LIFE
'lD1
STRAIGf1'-LINE
IXlJBLE-DEXL-BAL
CDS'!'
AalJt+-IEPRE-BD<
DEPRE-YTD-BXJ<
AallM-1EPRE-TAX
DEPRE-YTD-TAX

Figure 2-5.

SJBSaUPl'S

uxmi

'lYPE

EDITIm
PICIURE

GRJUP
l'lD1~C

l'.l'Dt STRING
ITEM NUMERIC
l'lD1 NlMERIC
ITEM NUMERIC
ITEM NlMERIC
ITEM NUMERIC
ITEM NUMERIC
ID

as

inventory file.
reoords contains
'!be part number
the sales record

follo.lS:

Descriptioo
Part. number
Manufacturing department number
Total quantity sold
Date of last sale
~nth of last sale
Day of last sale
Year of last sale

2 -

26

RP3 N.NN

VOCABULARY
"INVENT"

DD MMM YY
PAGE
1

PERMANENT MACROS (REPLACE STATEMENTS).
MACRO PART-INVENT-SALES-INFO.
TEXT: PARTMF, YTDSMF AT PART-NO •

RP3 N.NN

V 0 C ABU L A R Y
"INVENT"

DD MMM YY
PAGE
2

SYSTEM FILES.
FILE PARTMf,
ORGANIZATION IS INDEXED,
RECORD KEY IS PART-NO,
TOTAL-POPULATION IS 1000000.
LEVEL

NAME WITH QUALIFIERS

1
2
2
2
2
2
2
2
2

PART
PART-NO
DEPARTMENT
PART-DESC
MATERIAL-SOURCE-CODE
QUANTITY
UNIT-COST
INVENT-OOLLAR-VALUE
BIN-NO

SUBSCRIPTS

TYPE

LENGTH

GROUP
ITEM STRING
ITEM NUMERIC
ITEM STRING
ITEM STRING
ITEM NUMERIC
ITEM NUMERIC
ITEM NUMERIC
ITEM NUMERIC

6
4
20
1
5
6
11
3

EDITING
PICTURE
X(6)
9(4)
X(20)
X(1)
9(5)
Z(2)9.99
Z(7)9.99
9(3)

FILE YTDSMF,
ORGANIZATION IS INDEXED,
RECORD KEY IS PART-NO-SOLD,
TOTAL-POPULATION IS 1000000.
LEVEL
1
2
2
2
2
3

3
3

NAME WITH QUALIFIERS
PART-SALES-REC
PART-NO-SOLD
DEPARTMENT-NO
QUANTITY-SOLD
LAST-SALE
MONTH-SOLD
OAt-SOLD
YEAR-SOLD

Figure 2-6.

SUBSCRIPTS

TYPE

LENGTH

GROUP
ITEM STRING
ITEM NUMERIC
ITEM NUMERIC
GROUP
ITE~·NUMF.RIC

ITEM NUMERIC
ITEM NUMERIC

Vocabulary Listing ttINVENI'''

2 - 27

EDITING
PICTURE

6
4
5

X(6)
9(4)
9(5)

2
2

99
99
99

2

Figure 2-7 lists the vocabulary for three IMS II data sets: an accounts
receivable data set, a name and address data set, am an invoice data
set.
(A data set is a 1M3 II data structure Which can be oonsidered a
file. ) Each record in the accounts receivable data set corresponds to a
single custamr account and contains the following entries:
Nane

Descriptioo

BRANCH

Branch number

aJST-ID
CREDIT-LIMIT

Custaner nurrber

SALES-PERSON-cD

DISCXXJNl'-PERCENr
BILLIN3-TERMS-er

QJS'IOIER-NAME
STRml'-ADDRESS
CI'lY-STATE

CUstomer's full name
Street address
City and state
Zip code
Risk rating code

ZIP-a:>DE
RISK-RATnG

00

rec..~rd in the invoice data set deals with a particular
invoice ar¥i contains the follc:wing entries:

Each

2 -

28

custaner

Name

INVOlCE-Rl

Invoice rudJer

INV-aJS'l'-l«)

CUstaner n.mber
Due date
Terms of billing code

DUE-DATE

TElt&-BIILItG-OODE
'l'C71'AI.r-ND.JNl'
AKUll'-PAID
~DISCXlJHl'
~lA9l'-PAntI'

CHID<-l'D
INV-BRANQi-Y)

Each

aoc:amts receivable

Total anamt of invoice
Total anamt paid
cash discount taken
Date of last payment
Oleck runber
Branch n.mber

recom

is associated with one or

DDJ:e

invoices

the IM; II-mai.ntained set INVOICES.
Related al8taDer name ao:i
address infOl1lBticn can be obtained for each acoounta receivable recom
or invoice record via awIq>riate lookup in the IHt lI-maintained set.

via

lUEER-SEl' •

2 - 29

VOCABULARY
"CLIENl' II

RP3 N.NN

II> N+1 YY
2

PAGE

Il-SII DATA BASE QJST-ACCl'-INEO.
-----DATA 'SEl' ACCTS-RECV,

'lUl'AL-POPUIATlOO IS 200.
SET ACCTS-SET,
SPANS DM'A SEr Aa:!TS-RELV,
KE.Y IS QJST-NO.
SEl' .INVOICES,
SPANS I»\TA SEl' INVOICE-INFO,

KE.Y .IS .INVOICE-g).
L!.VEL

2
2
2
2
2
2

2
2
2
2
2
2
2

NAME WI'lH QUALIFIEH)

BRANCll
ClJST-NJ
CREDIT-LIMIT

SALES-PERSCN-CD
DISClXlNT-PERCENl'
BII..LIR3-TERMS-DE
~m-IASr-pAYl4iII'

DATE-IAST-PURCli
B1\LANCE-1XJE
aJRRENrLY-DUE
'lHIRIY-mYS-IlJE
SlX'lY-~S-DUE
NINmY-~S-OOE

Figure 2-7.

&UBSCRIPrS

'lYPE

11»1
l.'l'EM
'ITEM
IT&t
ITa-!
ITEM
1'1»1
I'lDt
ITEM
ITEM
ITEM
ITEM
1'1»1

L!H1.lH
NUMERIC
NUMERIC
NlHmIC
NUMERIC
NlHmIC
NUMERIC
NlI£RIC
NUMERIC
NlI£RIC
NUMERIC
NtHmIC
NUMERIC
NtHmIC

4 9(4)
6 9(6)
5 Z(4)9
5

9(5)

2

99

1

9

6 9(6)
6 9(6)
9 $Z(4)9.99
9 $Z(4)9.99
9 $Z(4)9.99
9 $Z(4)9.99
9 $Z(4)9.99

Vocabulary Listing for "CLI!Nl'"

(Sheet l'of 2)

2 - 30

IDITIH3
PIC'lURE

RP3 N.NN
OMSII DATA

VOCABULARY
·CLIENT·
~

DD MMM YY
PAGE
3

CUST-ACCT-INFO (CONTINUED)

DATA SET CUST-INFO,
TOTAL-POPULATION IS 200.
SET NAME-SET,
SPANS nATA SET CUST-INFO,
KEY IS CUSTOMER-NUMBER.
SET NUMBER-SET,
SPANS DATA SET CUST~INFO,
KEY IS CUSTOMER-NUMBER.
LEVEL
2
2
2
2
2
2
2

NAME WITH QUALIFIERS

SUBSCRIPTS

CUSTOMER-NUMBER
BRANCH-NUMBER
CUSTOMER-NAME
STREET-ADDRESS
CITY-STATE
ZIP-CODE
RISK-RATING

TYPE
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM

LENGTH
NUMERIC
NUMERIC
STRING
STRING
STRING
NUMERIC
NUMERIC

6
4
20
20
20
5
1

EDITING
PICTURE
9(6)
9(4)
X(20)
X(20)
X(20)
9(5)
9

DATA SET INVOICE-INFO,
TOTAL-POPULATION IS 5000.
SET INVOICE-NOS,
SPANS DATA SET INVOICE-INFO,
KEY IS INVOICE-NO.
LEVEL
2
2

2
2

2
2
2
2

2
2

NAME WITH QUALIFIERS
INVOICE-NO
INV-CUST-NO
DUE-DATE
TERMS-BILLING-CODE
TOTAL-AMOUNT
AMOUNT-PAID
CASH-DISCOUNT
DATE-LAST-PAYMT
CHECK-NO
INV-BRANCH-NO

Figure 2-7.

SUBSCRIPTS

TYPE

LENGTH

ITEM NUMERIC
ITEM NUMERIC
ITEM NUMERIC
ITEM NUMERIC
ITEM NUMERIC
ITEM NUMERIC
ITEM NUMERIC
ITEM--NUMERIC
ITEM NUMERIC
ITEM NUMERIC

Vocabulary Listing for "CLIENI'"
(Sheet 2 of 2)

2 - 31

6
6
6
1
8
8
8

EDITING
PICTURE
9(6)
9(6)
9(6)
9
$Z(3)9.99
$Z(3)9.99

$Z(3)9.99

6
8

9(6)
9(8)

4

9(4)

SAMPLE VOCABtlr.ARY 5:

"aJ&W"

Figure 2-8 lists the partial vocabulary for a magnetic tape file that
contains custaner remittances received during the ncnths of January and
February.
'!his file is. maintained in sequence by account nunber. Each
record represents a single, remittance and contains -the follOliing
entries:
DescriptiQ'l
REMIT-ACCT-ID

Accnmt rn.miler

aJS1'-NAME

Custaner name

IlM'E-RECD
YR-+I>-REXD
DAY-REO>

Date received
Year and nonth received

NEr-PAYMl'

Net payment

Day received

DISCNl'-'D\KEN

Discount taken

CBK-NJ

Clleck nunber

'!he file of remittances is used to update an open aCCXlWlt.s receivable
file ..u.ch is also maintained in ascending account-nunber order. Each
reoord -of the acoounts receivable file contains the followir¥J entries as
well as other account infonnation:
Name

Descript.ioo

Account rn.miler
AccCAlnt balance
Previous balance at ncnth end

2 - 32

RP3 N.W

VOCABULARY
"QBlV"

tMI yy;
PItGE
1

II)

smIDt FILES.

FILE maT-FILE,
OR3ANIZATICti IS SIUJ!Nl'IAL,
'l'C7mIrPOPUI.ATIaf IS 1000.

LEVEL

NAME WI'IH
QJALIFIms

1
2
2
2

REMIT-Rl:"XX)RD
REMIT--ACX:'l'-OO
C1JST-NAME
Dl\TE-REXD

3
3

YR-K>-REXD

2
2
2

SUECRIPl'S

'lYPE

3 9(3)

I'l'IH S'l'RI1«;

20 X(20)

I'l'fH lUERlC
I'l'Dt NlH:RIC
I'lDI WMERIC
:rl'Dt NlH:RIC

DISQfiVI'AKaI
CH<-l«)

mITDD
PIcruRE

GRClJP
IT!M lUERlC
GlDJP
I'lB4 NlH:RIC

mY-RB::D
NET-PA»I:lI'

LDImI

4 9(4)
2 9(2)
10 $Z(5)9.99
8 $Z(3)9.99
8 9(8)

FILE Aa:T-FIIE,
QR;;ANIZATIW IS S!XllBft'IAL,
TOl'AL-POPUIATICB IS 200.

LEVEL

NAME WI'IH
QJALIFIm8

SUBSaUPl'S

'.riPE

1

NXT-REXDRD

GlUJP

2

ACX:T-R>
BALANCE
OLO-BALANCE

1'1»1 NW£RIC

2
2

Figure 2-8.

ITEM lUERlC
I'lDt WMERIC

LDImI

3 9(3)
$Z(7)9.99
$Z(7)9.99

12
12

Vocabulary Listing for "QBlV"

2 - 33

mIT.IRi
PIcruRE

SAMPLE VOCABlJIARY 6:

"SHIPV"

Figure 2-9 lists the vocabulary for a detail transactiai file of
ac(X)UDts ~ivable and ac(X)UDts payable for a shipping CXDpany. Each
rEKX)rd of the file represents a transaction and contains the following
entries:
Name

NlI4Bm
.DA.TE-

Descripticn
Freight bill DUI'Iber
Date of billing
ftblth of billiDJ
Day of billing
Year of billing
Q:xies for shipnent origination points
Codes for shipnent destination Points
Receipt IlUIlber or disbursement. check
nunber
Acc:Dlnt IU.JIl.'ber

Transacticn
. type
O=payable)
Transactioo code
Dollar anount OIled

2 - 34

(l=receivable;

RP3 N.NN

VOCABULARY
"SHIPV"

JD M+l YY
1

lJ:~..7E

SYSTEM FILES.

FILE

~-T.RANS,

ORiANllATION IS INIEXID,
RECDRD KEY IS NllomER,
TOrAL-roPUlATIOO IS lEFAULTED ro 9999.

SUBI.i.VEL

1
2

NAME WI'IH QUALIFIERS

SCRIPl'S

"NPE

BIIL
tUmER
OF BILL

GRaJP
ITEM S'l'RnI;

2

Ill\TE-ofo'-BIIL:U~

3

MJN1'H~F-BILLIN3

GROOP
ITEM WMERIC

-)

D/1:i-oF-BIILIl-l;

IT&t NlMERIC

J
.)
"
2

2
2
2

YFAR-oF-BILLIM;
rolNTS OF SHIPMEllI'
SUB 1: MAX VALUE
IS 5
roINTS-oF-DESTINATION
RECEIPT-NO

TRANSI\CfION-'IYPE
TRANSACTlOO-1 NlHERIC

2
8

9(8)

ITEM NlHERIC
ITEM NUMERIC
ITEM NlHERIC

8

9(8)

6
4

9(6)

ITEM NLMERIC
InM NUMERIC
ITEM NUMERIC

1

1
10

9
9
-$(5) .99

Vc..1Cabulary Listing for "SHIPV"

2 -

EDITnG
PIC'lURE

99
99

ITEM I.'IDMERIC

1

ACX.Xmlr-W
OF BILL

2
2

LEHmi

35

9(4)

SECI'ION 3
DESIGNING REPORrS

This section is intended to help you determine the REPORI'ER III report
language statements you need, as well as the logical order of the
statements, to design and specify report(s).
Brief explanations of
"basic language constructs" and "functions" often used in constructing
report language statements are included in this section.
Detailed
explanations of all report language statements, clauses, basic language
constructs, and functions are provided in Section 4.
REPORr SPECIFICATION
A REPORrER III report specification describes one or nore reports.
report is defined in general to mean one of the following:
1.
2.
3.

A

An automatically formatted printed report.
A user-formatted printed report.
A machine-readable extract file.

The syntax diagram presented in Figure 3-1 shows the general processes
involved in use of REPORTER III report language statements to design and
specify either a single report or multiple reports.
In designing report(s), you use report language statements to define
what information is to be reported and what types of reports are to be
produced.
First

you indicate the password, if any is needed to reference the
vocabulary. Next you reference the vocabulary (created by the
RP3VOC program) which contains the description of the file(s) to be used
in specifying the desired report(s).
r~ired

3 - 1

---------------------->(1)
I
I statement>
I
I I
+--> +
statement>

I <---------------------1
I
I
I-->->I

I

I

+-->+
statement>

Figure 3-1.

General Syntax Diagram for
REPORTER III Report Specification
(Sheet 1 of 4)

3 - 2

+--> (2)

For Single Report:
+<--------------------------------------------------+

I

I

(l}------;-r-!--->--------------------------->

I

I-r-r-J--->------------------->

I
I--------->-->

I

I--------->--------------->

I
I-;-r-!--->----------------->

I
-r-r-J--->------------------->

I

I

+->->+
-r-r-J--->------------------->
-r-r-J--->------------------->
-r-r-J--->------------------->
-;-r-!--->------------------>
--------->----------------->
--------->----------->
-;-r-!--->------------------>
-~--->------------------>

-r-r-J--->--------------->
--------->------------------->
+-;-r-!--->