ESD TR 70 278_Users_Manual_JOVIAL_Compiler_Validation_System_Jul70 278 Users Manual JOVIAL Compiler Validation System Jul70

ESD-TR-70-278_Users_Manual_JOVIAL_Compiler_Validation_System_Jul70 manual pdf -FilePursuit

ESD-TR-70-278_Users_Manual_JOVIAL_Compiler_Validation_System_Jul70 ESD-TR-70-278_Users_Manual_JOVIAL_Compiler_Validation_System_Jul70

User Manual: ESD-TR-70-278_Users_Manual_JOVIAL_Compiler_Validation_System_Jul70

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

Download
Open PDF In Browser	View PDF

ESD ACCESSION LIST
ESTI Call No.

G.

o
o

ESD-TR-70-278

,

^^) ^5^2-

Copy No.

UJ

F
CO
UJ

USER'S MANUAL
JOVIAL COMPILER VALIDATION SYSTEM

ESD RECORD COPY
RETURN TO
SCIENTIFIC & TECHNICAL INFORMATION DIVISION
(ESTI), BUILDING 1211

July 1970

DIRECTORATE OF SYSTEMS DESIGN & DEVELOPMENT
HQ ELECTRONIC SYSTEMS DIVISION (AFSC)
L.G. Hanscom Field, Bedford, Massachusetts 01730

This document has been
approved for public release and
sale; Its distribution is
unlimited.

I

LEGAL NOTICE

When U.S. Government drawings, specifications or other data are used for any
purpose other than a definitely related government procurement operation, the
government thereby incurs no responsibility nor any obligation whatsoever; and
the fact that the government may have formulated, furnished, or in any way supplied the said drawings, specifications, or other data is not to be regarded by
implication or otherwise as in any manner licensing the holder or any other person
or conveying any rights or permission to manufacture, use, or sell any patented
invention that may in any way be related thereto.

OTHER NOTICES

Do not return this copy.

Retain or destroy.

ESD-TR-70-278

USER'S MANUAL
JOVIAL COMPILER VALIDATION SYSTEM

July 1970

DIRECTORATE OF SYSTEMS DESIGN & DEVELOPMENT
HQ ELECTRONIC SYSTEMS DIVISION (AFSC)
L.G. Hanscom Field, Bedford, Massachusetts 01730

This document has been
approved for public release and
sale; its distribution is
unlimited.

FOREWORD
The JOVIAL Compiler Validation System (JCVS) Users Manual is intended as
the reference manual for on-site operations.
The system was developed as a part of Project 6917 under Contract F1962868-C-0301 for the Electronic Systems Division (AFSC) by Data Dynamics,
Inc., Los Angeles, California 90045. The project monitor was Captain
Martin J. Richter, ESMDA. The work was performed during the period
March 1968 through February 1969.
This technical report has been reviewed and is approved.

WILLIAM F. HEISLER, Colonel, USAF
Director, Systems Design & Development
Deputy for Command and Management Systems

li

ABSTRACT
This technical report consists of detailed specifications for the use of
the JOVIAL Compiler Validation System (JCVS). The system is designed to
measure the compliance of a specific JOVIAL J3 compiler against the language
specifications in Air Force Manual 100-24, "Standard Computer Programming
Language for Air Force Command and Control Systems". This report describes
the card input formats, deck structures, tape requirements, test modules,
and operator procedures required to use the system.

ill

TABLE OF CONTENTS
Page
FOREWORD
ABSTRACT

II

?ii

SECTION I

INTRODUCTION

1

SECTION II

SYSTEM DESCRIPTION
2.1
The JOVIAL Standard
2.2 JCVS Test Concepts
2.2.1 JCVS Scope
2.2.2 Data Concepts
2.2.3 Procedural Concepts
2.3 JCVS Computer Program System Capabilities
2.3.1 The JCVS Data Base
2.3.1.1
Environmental Hardware/Software
2.3.1 .2 Test Modules
2.3.1.3 Identification
2.3..2 Population File Maintenance Module
2.3..3 The Selector Module
2.3.4 Source Program Maintenance Module
2.3.5 The Test Program

2
2
3
3
3
4
6
6
6
7
7
7
7
8
8

SECTION III

SYSTEM USAGE
3.1
Hypothetical JCVS Operational Philosophy
3.2 System Initiation
3.3 Test Program Generation
3.4 Test Program Execution
3.5
Test Result Evaluation

9
9
9
10
11
11

SECTION IV

FUNCTION DESCRIPTION
4.1
Population File Maintenance Module (POPFM)
4.1.1 Purposes and Uses
4.1.2 Preparation of Inputs
4.1.2.1
System Module
4.1 .2.1 .1 System Header Card 1
4.1 .2.1 .2 System Header Card 2
4.1.2.1.3 Environmental Hardware
Card 1
4.1.2.1.4 Environmental Hardware
Card 2
4.1.2.1.5 Environmental Hardware
Card 3

13
13
13
13
13
14
15
16
17
17

TABLE OF CONTENTS (Continued)
Page
4.1.2.1.6
4.1.2.2

4.1.3

4.1.4

4.2

Selecti
4.2.1
4.2.2

4.2.3
4.2.4

Environmental
Software Cards

Test Modules
4.1.2.2.1
Test Header Card
4.1.2.2.2
JOVIAL Statement Card
4.1.2.3
Packet Cards
4.1.2.3.1
Control Card - PF
4.1.2.3.2
Delete Card
4.1.2.4 Input Files
4.1.2.4.1
Population File
4.1.2.4.2
Current File - PF
Function Operation
4.1.3.1
Create Population File
4.1.3.2 Update Popul ation File
Description of Expected Results
4.1.4.1
Output Card Formats
4.1.4.2 Output Files
4.1.4.2.1
Population File
4.1.4.2.2
Audit File - PF
4.1.4.2.3
Punch File - PF
r Module (SJCVS)
Purposes and Uses
Preparation of Inputs
4.2.2.1
Input Card Formats
4.2.2.1.1
Test Selector Card
4.2.2.1.2
Control Card-S
4.2.2.2
Input Files
4.2.2.2.1
Population File
4.2.2.2.2
Test Selection File
Function Operation
Description of Expected Results
4.2.4.1
Output Card Formats
Environmental Software
4.2.4.1.1
Card
4.2.4.1.2
Test Header Card
4.2.4.1.3
JOVIAL Source Program
Card
4.2.4.2 Output Files
4.2.4.2.1
Source Program File
4.2.4.2.2
Audit File - S
4.2.4.2.3
Punch File - S

VI

18
18
19
21
21
21
22
22
23
23
25
25
25
27
27
27
27
27
29
29
29
29
29
30
30
31
31
31
31
33
33
33
33
34
35
35
36
38

TABLE OF CONTENTS (Continued)
Page
4.3

4.4

4.5

Source Program Maintenance Module (SOPMM)
4.3.1 Preparation of Inputs
4.3.1 .1
Card Inputs
4.3.1.1.1
Control Card-SP
4.3.1.1.2
Other Card Inputs
4.3.1.2
Input Files
4.3.1.2.1
Source Program File
4.3.1 .2.2
Current File - SP
4.3.2 Function Operation
4.3.3 Description of Expected Results
4.3.3.1
Output Card Formats
4.3.3.2 Output Files
4.3.3.2.1
Source Program File
4.3.3.2.2
Audit File-SP
4.3.3.2.3
Punch File-SP
Initiate Population File Module (INIPOP)
4.4.1 Purposes and Uses
4.4.2 Preparation of Inputs
4.4.2.1
Card Inputs
4.4.2.1.1
Control Card - IP
4.4.2.1.2
Other Card Inputs
4.4.2.2
Input Files
4.4.2.2.1
Population File
4.4.2.2.2
Current File - PF
4.4.3 Function Operation
4.4.4 Description of Expected Results
4.4.4.1
Output Card Formats
4.4.4.2 Output Files
4.4.4.2.1
Population File
4.4.4.2.2
Audit File-IP
4.4.4.2.3
Punch File - IP
JCVS Report Writer Module (JCVSRP)
4.5.1 Purposes and Uses
4.5.2 Preparation of Inputs
4.5.2.1
Card Inputs
4.5.2.1.1
Control Card - RP
4.5.2.2
Input Files
4.5.2.2.1
Population File
4.5.3 Function Operation
4.5.4 Description of Expected Results
4.5.4.1
Audit File-RP

VII

38
39
39
39
40
40
40
40
41
42
42
42
42
42
43
43
43
44
44
44
46
46
46
46
46
46
46
47
47
47
47
48
48
48
48
48
49
49
49
49
49

TABLE OF CONTENTS (Continued)
Page
SECTION V

USAGE INSTRUCTION
5.1
JCVS Operating Philosophy
5.2 JCVS Function
5.3
Preparation of JCVS Input
5.3.1 Current File - PF
5.3.2 Current File - SP
5.3.3 Test Selection File
5.4 Functional Processing
5.5
Results of Operations
5.5.1 Printed Output
5.5.1.1
Population File
5.5.1.2 Audit File-PF
5.5.1.3 Audit File-S
5.5.1.4 Audit File-SP
5.5.1.5 Audit File-IP
5.5.1.6 Audit File - RP
5.5.2 Punched Output
5.5.2.1
Punch File-PF
5.5.2.2
Punch File - S
5.5.2.3
Punch File - SP
5.5.2.4
Punch File-IP
5.5.3 Magnetic Tape Output
5.5.3.1
Population File
5.5.3.2
Source Program File

TABLE OF CONTENTS for APPENDIX 1
/PPENDIX1
APPENDIX ii
APPENDIX in
/PPENDIX IV
/PPENDIXv
/PPENDIX VI

51
51
51
52
52
52
52
52
52
52
58
58
58
58
58
58
58
67
67
67
67
67
67
67
68
71
171
173
175
177
lal

VIII

SECTION I
INTRODUCTION

The purpose of this manual is to :
1.
2.

Introduce the JOVIAL Compiler Validation System
Describe how the system may be used to validate JOVIAL Compilers

This manual is organized into five sections. Foliowing Section I, the Introduction,
Section II describes the JOVIAL Compiler Validation System. Included in this Section
is a brief discussion of the current JOVIAL J3 Standard, the AFM 100-24 document,
some insight into the design criteria which guided the development of the system and a
discussion of the functions performed by components of the system. Section III suggests
how the JCVS may be used as a package to validate JOVIAL compilers. Section IV
presents the details of each of the system components. Sufficient material will be
included in this section to completely describe the uses of each component in the
system. In addition, details of programs and their relationship to data are fully described.
Although the AFM 100-24 document defines specific input/output statements for
the JOVIAL J3 language, discussions with implementors of this language have established
that of the existing JOVIAL compilers none have adhered to these input/output specifications.
Most current JOVIAL compilers use either the input/output capabilities provided by the
operating system in which JOVIAL is embedded or an associated ancillary system within
the software environment. There is currently little control over the form of the JOVIAL
associated input/output statements. In addition only the GE-635 JOVIAL Users Manual
is currently available. These two facts when taken together present considerable difficulty
to those JOVIAL support statements that concern themselves with printing the results of the
execution and comparison of JOVIAL test statements. Until a firming of the input/output
specifications to the JOVIAL language has been established, this fact is a major obstacle
to the successful usage of this system.
Section V will discuss the JOVIAL Compiler Validation System as it applies to the five
computers upon which the system will reside. Because of the absence of information
relating the JOVIAL compiler to its operating system, the requirements relating the two
will be discussed in general terms only. This section will describe how the JCVS must be
used by defining input deck structures and tape mountings, providing the required
instructions to operate the system, and giving examples of the results obtained from the
various modules comprising the JCVS.

SECTION II
SYSTEM DESCRIPTION

The JOVIAL Compiler Validation System (JCVS) is designed to evaluate the extent
of compliance of any JOVIAL compiler with the current JOVIAL Standard Computer
Programming Language for Air Force Command and Control Systems Manual,
AFM 100-24.
Depending on the extensiveness and depth of testing, the user may either select a
representative collection of test statements or the complete test repertoire. If the
user is interested in a particular capability as provided by the JOVIAL compiler,
he may desire to execute test statements exclusively in the area of that particular

capability.
Having decided upon the particular collection of test statements to be executed, the
user specifies his intent to the JCVS by means of test selector cards. These cards
are interpreted by the JCVS and are used to select the desired test statements to be
included in the generated test program. The resulting JOVIAL test program will be
produced for compilation in card image form on magnetic tape or on cards.
2.1

The JOVIAL Standard

The JOVIAL J3 language is completely specified in AFM 100-24, Standard Computer
Programming Language for Air Force Command and Control Systems, 15 June 1967.
The JOVIAL language has the basic elements required by most languages, namely, the
ability to define simple data items and basic item structures and the capability to
reference this data from within procedural statements. The procedural statement
repetoire is adequate, consisting of the following procedure types:
1 .
2.
3.
4.

5.

Data Transmission
Algebraic Expression Formulation
Logical Expression Formulation
Transfers of Program Control
4.1
Conditional
4.2 Unconditional
4.3
Switching
4.4 Looping
Input/Output

There are other odds and ends in the language that are useful but computer dependent and
srrve to confound the intent of this specification, namely, standardization.

Another section of this manual is devoted to establishing standards for the development
of compilers of JOVIAL J3. Elements of this standard are, on occasion, ignored by
the implementors of the language. This is particularly true in the case of the input/output
specifications provided by the language. These specifications are rudimentary in
character and are, generally, replaced by comprehensive (but non-standard) input/output
procedures more closely associated to the operating system within which the compiler
is embedded. Unless a more stringent attitude toward the development of JOVIAL
compilers is maintained it is impossible to write JOVIAL input/output statements with
the conviction that they will be compatable from one computer-compiler configuration
to another.
For purposes of this system, the entire JOVIAL language will be treated as a single
module. Because of the size and pointedness of the language, no submodularization
will be required.
2.2

JCVS Testing Concepts

The following sections discuss briefly the scope of the JCVS and the tests selected for
inclusion in the Population File.
2.2.1

JCVS Scope

For purposes of the JCVS, the JOVIAL system to be tested is assumed to consist of a
processor that compiles standard JOVIAL source program statements called the JOVIAL
compiler, and all programs and subroutines used by the JOVIAL object code generated
from standard JOVIAL statements. The JCVS is designed to test both the compilation
and execution of specific JOVIAL features.
2.2.2

Data Concepts

JOVIAL language organization has guided the identification of language features to be
tested. In order to validate the JOVIAL compiler ideally, each of the specific
language features must be validated. The validation of each feature of a language,
however, is not always possible. For example, how can one determine that any value
stored in a floating point item is truly stored as a floating point number; how can one
determine that a fixed point constant has actually been converted to a fixed point
binary point constant. Looking at information as it resides in the internal storage
medium, we may observe a string of bits, however, the interpretation of this content
is inconclusive. Consequently, some of the features provided by the JOVIAL language
are not susceptibleto validation independently. These features are generally the more
basic notions in the language and will be used constantly in the Test Modules comprising
the Population File. With repeated correct usage of these basic concepts, it is hoped
that the credibility of their required implementation will be considerably improved.

With these thoughts in mind, the following aspects of the data definitional
capabilities of the JOVIAL language will not be tested independently and will be
assumed present in the language and correctly implemented:
1 .
2.
3.

The ability to specify any item type and have it retained according
to its defining attributes.
The ability to formulate any constant type and have it retained according
to its defining attributes.
The ability to specify any data structure type (table, array, etc.)
and have it retained according to its defining attributes.

The JOVIAL language provides the user with a myriad of options to form constants,
simple items, tables, and arrays. There are so many data defining attributes possible
in JOVIAL that exercising each option in an independent test is quite impossible. As
a compromise, the test repertoire will use a subset of data definitions that exercise, at
least once, all of the data attributes available to define data items and structures.
In addition, the repertoire will utilize every variation provided to formulate constants
with the exception of the dual item definitions which will be exercised in part, only.
It goes without saying that the formation of acceptable JOVIAL symbols (names, labels,
etc.) will be exercised every time a symbol is formed.
2.2.3

Procedural Concepts

The JOVIAL language provides the user with the ability to process formulas and
relations; it provides for program organization and it provides certain compiler directing
features. Every variant of each of these features will be tested at least once. Further
substantiation of the ability of a feature to perform its intended function will be supplied
by its correct use as a support statement in other test modules.
With these thoughts in mind, the following aspects of the procedural capabilities of the
JOVIAL language will be assumed to be present in the language and correctly implemented:
1 .
2.

The ability to name a statement with a label.
The fact that normal procedural control passes from One JOVIAL statement
to the next.

Comprehensiveness
The variants provided in the data base form a nucleus from which tests may be created.
Selected data statement variants and all procedure statement variants will be included
in the data base. Selected values for variant operands will also be a part of the data base.
Since the collection of values comprising the complete range for each variant operand may
be extremely large, only a representative number of values for each operand may be included,
These factors, of course, indicate that individual variants may be tested only for a subset of
their possible operand values.

This subset of operands will be large enough, however, to associate a large
degree of confidence with the evaluation of each variant.
A JOVIAL compiler is said to be validated if each individual data base variant with
its appropriate subset of operand values has been executed and results compared
successfully. The collection of variants and operands on the data base necessary
to validate the compiler will be referred to as the "nominal" data base. The JOVIAL
source test program that may be used to validate the entire JOVIAL compiler is called
the nominal "test case".
The design reflects the following:
a)
b)
c)
d)

e)

f)

A careful sampling of selected operands from possible combinations of
operand types available to the statement.
No tests are made of erroneous statements.
All possible variants of procedural statements are performed.
Tests are not designed to indicate how a function is implemented.
Thus, there is no attempt to distinguish between efficient and
inefficient implementations.
No testing of non-standard extensions to JOVIAL is made. However,
such tests and extensions can be added to the system by the user through
the add, change and delete option cards in the Population File program.
No test of direct code is attempted.

Openendedness
Modification to the data base may become necessary as changes are made in the JOVIAL
Standard. Variants and operand values may be added to the data base to test user-specific
extentions to the JOVIAL language. Variants and operand values may be deleted or
modified because of reinterpretations of existing JOVIAL language features. The JCVS
will provide the means to add, change or delete any data base variants and operand values
in the Population File.
Ease of Use
Complete and detailed input and test configurations facilitate ease of use. In Section 4
the input cards to each program are described in detail. Each input card is defined, card
columns are specified, and all mandatory cards are so designated. In Section 5, the order
of all the cards from each program needed for a JCVS run is graphically portrayed. The
collection of test statements provided by the JCVS is shown in Appendix6 together with their
individual test serial numbers. Trm test aerial number permits the user to select, eliminate or
add specific tests.

Additional features that make the JCVS easy to use are:
a)

A test can be specified by a user without detailed knowledge of
JOVIAL.
Test Results which show discrepancies are output. An option exists
for viewing an indication of the results of all tests (see Section 3.5).
Program modules are machine independent.

b)
c)
2.3

JCVS Computer Program System Capabilities

The JCVS consists of a collection of three major program modules and a data base
that provides the user with a simple technique to generate a JOVIAL source program
capable of testing some particular aspect of the compiler or the entire compiler itself.
The data base, called the Population File, contains all of the test statements that are
potential candidates for inclusion in subsequent generated source programs. A particular
test may be created including specific functions and excluding those functions that are
not provided, for one reason or another, by the particular compiler. A comprehensive
test package may be developed by the user for each compiler.
The Population File is maintained by the Population File Maintenance Module.
Population File test modules are added, deleted or replaced by means of this routine.
The Selector Module extracts user-specified test modules from the Population File, distributes
the necessary operating system control cards and support statements and generates a self
contained JOVIAL source program for subsequent processing. The Source Program
Maintenance Module may be used to update a generated JOVIAL source program.
2.3.1

The JCVS Data Base

The Population File contains the following types of information:
1 .
2.
3.

Environmental - Hardware/Software
Test Modules
Identification

This information is presented to the Population File on cards whose descriptions are given
in Section 4.
2.3.1.1

Environmental -Hardware/Software

Environmental data, both hardware and software, for all computers of interest is carried
in the Population File. Hardware specific information such as printer control codes,
magnetic tape designations and memory size and software specific information such as
operating system control card descriptions and computer-compiler specific JOVIAL
control card descriptions offset by one column are carried in the first few records of the
Population File.

2.3.1.2

Test Modules

A Test Module is a collection of JOVIAL statements that test a particular feature of the
JOVIAL compiler. The feature may be a JOVIAL concept, a single JOVIAL statement
or a collection of JOVIAL statements. Included in each Test Module are the:
1 .
2.
3.
4.
5.
6.
7
8.

Test identification field
Input test data fields
Test Results fields
Expected Result fields
Initialization procedures
Test statements comprising the test
Results analysis procedures
Output procedures

Test Modules are located on the Population File in order of their test serial number,
the DDI-NO. With each test statement is associated a sequence number within the
DDI-NO that specifies the ordering of the statements within the DDI-NO.
2.3.1.3

Identification

The first 80 characters of the Test Module are devoted to information describing several
aspects of the test. These 80 characters, called the Test Module Header, contain the
name of the test, its test serial number, any CED AFM 100-24 numbers associated
with the test, and any required references to other test modules.
2.3.2

Population File Maintenance Module

This module operates on a Population File and permits the user to add, delete, replace,
or change logical records on the Population File. This feature is the means by which
the user updates the Population File with current information. Environmental, test, and
identification information may be augmented by means of this module.
This module will be used to modify the contents of the Population File to incorporate
new tests resulting from extensions to tfie JOVIAL compiler, to delete current tests when
particular aspects of the compiler have not been implemented, or to include information
describing the environment in which the JOVIAL tests will be conducted.
2.3.3

The Selector Module

The Selector Module performs the major task of assembling and organizing test and
support statements for the JOVIAL test program.
1)

Using the input specifications obtained from the user, appropriate
variants and operand values may be selected.

2)
3)

2.3.4

The resulting test and support statements are placed in the order needed
for compilation.
Operating system control cards are placed before and after the JOVIAL
source test program.

Source Program Maintenance Module

This program is used to modify a JOVIAL source program either generated by the
Selector Module or previously modified by the Source Program Maintenance Module.
This module may be used if:
1)
2)
3)
2.3.5

One or more tests did not compile correctly (therefore deletions of
erroneous statements or changes to existing statements can be made).
The user wished to change a test in order to compare with a previous
run using different user defined operand values (parametric study).
The user wishes to add non-standard tests to the JOVIAL source program.

The Test Program

The JOVIAL source program generated by the Selector Module is a self contained
JOVIAL J3 program in compilable form. The test structure and content of the
particular source program has been completely specified by the user. All statements
sjpporting the test are provided automatically by the JCVS.
Each test within the source program exercises one or more of the features provided by
the JOVIAL compiler by actually compiling and executing those JOVIAL statements
that provide the feature. The results of this procedure stating the outcome of this
execution may be displayed.
It was originally intended to display expected versus actual results. Lack of adequate
capabilities of the input/output portions of the JOVIAL language , coupled with an
inability to acquire input/output information about the JOVIAL implementations themselves,
reduces the comparison printout to a message stating whether the test has passed or
failed together with an identification of the associated DDI-NO.
Test results printed under these constraints do not fully reveal the causes of errors in
tests devoted to the accuracy of arithmetic operations;. The results of syntax-semantic
testing, however, are not affected by this constraint.

8

SECTION
SYSTEM USAGE

3.1

Hypothetical JCVS Operational Philosophy

DDI hypothesized that the JCVS may be utilized operationally in any of several ways:
1 .

2.

3.

The entire system, including the Population File, can be distributed
to JOVIAL J3 implementors for use in validating their JOVIAL
implementation.
JOVIAL source programs may be developed by a central agency
and the source programs sent to JOVIAL implementors for compilation
and execution. Results of these runs could be returned for processing
by the sarm oqency.
A team of personnel could accompany the JCVS to a specified
computer upon which the JOVIAL compiler is to be exercised. The
JCVS is then made operational on the computer system and the particular
JOVIAL compiler is tested.

Any of the above operational philosophies could be followed, however, based upon
the work statement description of the problem, the third philosophy appears to be
the most probable approach.
If operational philosophy one or three is followed, all the program modules will
be required to execute on the computer for which the JOVIAL compiler has been
prepared.
If philosophy two is followed, the Population File Maintenance Module and the
Selector Module will be processed on a single compurer (possibly not one of the
target computers in this contract) while the Source Program Maintenance Module will
be processed, at a minimum, on the computer upon which the JOVIAL compiler has
been implemented.
For the remainder of this document we shall assume that philosophy three is to be
followed and all JCVS modules must be operational on each computer containing the
JOVIAL compiler to be tested.
3.2

System Initiation

For each specified computer a Population File and three source decks will be provided.
Each of the source decks must be compiled and a resultant binary deck of each program

module obtained. All JCVS program modules will have been written in a subset of
COBOL to ensure that the program will, after changes to the input/output characteristics
of each program module and appropriate control cards, compile into a useable program.
Once the Population File Maintenance Module has been established on one of the
target computers, the Population File may be developed for this computer. Since
certain aspects of the JOVIAL language may be specified by the implementor there
muy be idiosyncracies of the JOVIAL implementation that could necessitate
modifications to the JOVIAL test statements or the JOVIAL test statement formats.
It is impossible at this time to predict what form these idiosyncracies might take;
consequently, the user must be aware of this situation and be capable of adjusting the
test statements, if required, to conform to the specific compiler.
A notable example of this problem occurs because the reference format as specified by
the AFM 100-24 document indicates that a JOVIAL source program statement may
occupy any of the 80 columns on a card. Specific implementors, in general, do not
permit this free field interpretation and specify margins within which a JOVIAL statement
must be written.
Once the program modules have been compiled and the Population File has been
created, the user may proceed to the next step, the generation of a test program.
3.3

Test Program Generation

The selection of tests necessary to validate a JOVIAL compiler may vary widely
depending upon the testing philosophy.
More than likely, the particular compiler features to be tested depend entirely on the
uses to which the compiler will be exposed and the environment in which the compiler
will reside. The JCVS user, presumably knowing this, will have produced specifications
to which the compiler must adhere. In order to ensure that the compiler does, indeed,
adhere to these specifications, the user selects from the Population File those tests that
exercise those features whose correct execution will result in a verification of the stated
specifications.
A second approach to the validation of the compiler might consist of selecting for
testing all of the features stated as standard by the AFM 100-24 document. Using this
approach would give the user a "look see" at what features were implemented.
Having chosen the tests to be processed, the user submits this information to the
Selector Module by means of Test Selector Cards. The Selector Module Program
de :k must be augmented by the operating system control cards for the particular computer
upan which the Selector Module is being run.

10

The exact job deck structure for each computer required to achieve a Selector Module
run is given in Appendix 1.
There are occasions when the generated JOVIAL source program will exceed the
limitations of either the compiler or the hardware environment. In order to remedy
compiler violations, consult the JOVIAL compiler users manual to establish the cause of
the trouble.
In order to remedy excessive core storage requirements, segment the generated JOVIAL
source program by selecting several smaller programs rather than one large program.
3.4

Test Program Execution

The JOVIAL test program resulting from the Selector Module run is then compiled. If
the program compiles with error, these errors should be recorded by the user. By means
of the cross referencing mechanism provided with each test, DDI-NO versus CED-NO's,
all references to the test may be located in the AFM 100-24 document.
The Source Program Maintenance module may then be used to eliminate from the
source program those elements causing the compilation errors. The compilation and
element removal process is continued until an error-free compilation has been achieved.
Following a successful compilation, the object program is executed. If the execution
terminates abnormally, a study of the partial results obtained by the run will be required
to locate the offending test elements. If the execution terminates normally, a glance
at the results of the test will provide information signifying individual feature compliance
with AFM 100-24 standard.
3.5

Test Result Evaluation

The notion of what constitutes a validated JOVIAL compiler is a function of the
requirements to be levied on the compiler. Consequently, the user, based upon the
compilation and execution of one or more test programs, must formulate his decision
with the information gathered as a result of these test runs.
Within each generated source program there may be tests of two types: Those that test
the various syntax-semantics relationships present in the language and those that test the
accuracy of arithmetic computations provided by the algebraic expression capabilities
of the language.
The syntax-semantics tests are logical in character and can be answered by monitoring
the semantic response the compiler provides for a syntactic type.
For example, a reasonable test for the GOTO statement could consist of: Does it go
where it says it is going to go? The result is either yes or no. If yes is the case, an

11

appropriate message is printed out and if not is the case, another message results. As a
general rule, the results of logical tests may be indicated by a yes or no decision only.
The tests for accuracy, on the other hand, require that computed results be compared with
expected results; that both results, if possible, be converted and printed together with a
decision stating that the feature either passed or failed to pass its accuracy requirements.
Accuracy tests, in general, depend upon the ability of the compiler-computer configuration
to represent and process correctly numbers exercising the extreme capabilities of the
hardware. Given that these operations have been performed correctly (in binary) the
problem of converting these numbers to printable form (decimal) requires the application
of some JOVIAL output procedures. Since no standard JOVIAL formatting conversion
and output procedure exists machine language or other higher level language coding must
be utilized in order to view the results. This foreign conversion process, however, can
introduce non JOVIAL compiler computational errors into the computed results and render
the accuracy considerations of the tests useless.
In the absence of input/output specifications for four of the five JOVIAL compilers
in question, only the statement indicating that the feature has passed or failed its test will
be printed. When the JOVIAL language provides proper formatting capabilities the ability
to display computed and expected results may be added to the output sections of the test
modules.

12

SECTION IV
FUNCTION DESCRIPTION

4.1
4.1.1

Population File Maintenance Module (POPFM)
Purpose and Uses

The POPFM module may be used to generate a new Population File either by
initiating the file from cards or by updating an old Population File with current
additions to the information contained in the old file. This information consists of
Environmental Data or Test Statements. These information types are organized into
4000 character physical records for recording on magnetic tape. Each physical record
consists of either a System Module or a Test Module.
The modules are stored in numerically ascending sequence by serial number, the DDI-NO,
associated with each of the modules in order to facilitate the processing to be applied to
the Population File. This processing permits addition, deletion, or replacement of
user specified information to this file.
All physical records are treated identically and the updating functions provided by
the JCVS regard only the items (DDI-NO, CARD-TYPE and SEQ-NO) to control the
updating process.
Input to the POPFM consists of a current file of information called the Current File-PF,
an optionally present old Population File and a control card requesting specific options
provided by the module. The Current File-PF is a card file, while the old Population File
and the new Population File are magnetic tape files.
Output from this routine consists of an updated Population File, an Audit File-PF
consisting of diagnostics, trace messages with an optional listing of all of the card images
on the Population File containing information, and an optional Punch File consisting of
a card deck of all card images on the new Population File containing information.
4.1.2

Preparation of Inputs

4.1.2.1

System Module

Each computer-compiler configuration will contain environmental data describing
specific aspects of the hardware environment in which the JCVS will reside.

13

Information identifying the hardware configuration, the facility, the user, etc.,
will be supplied to the Population File by means of System Header cards. Environmental
hardware information such as printer codes, magnetic tape designations, etc., will
be supplied to the Population File by means of Environmental Hardware cards.
The aforementioned information will be carried as descriptive material only and will not
participate in the generation or will not become a part of any of the generated JOVIAL
source programs.
On the other hand, the environ mental-software information supplied to the Population
File by means of Environmental Software cards will become an integral part of the
generated JOVIAL program. This software information consists of operating system
control cards and the JOVIAL START and TERM cards. Some of these cards precede
and others follow the generated program.
4.1.2.1.1

System Header Card 1

System Header Card 1 occupies the first 80 character positions in the System Module
(the first 4000 character physical record on the Population File).
Columns

Name

Description

1-12

Users Name

13-24

Facility

25-34

Computer-Name

These 12 columns may be used
to identify the agency or
organization using the JCVS .
The name may be positioned any
place within the field,
(Example: bbUSAF-ESDbb, or
USAF-ESDbbbb.)
These 12 columns may be used
to identify the facility at which
the JCVS is being utilized. The
name may be positioned any
place within the field.
(Example: bbHANSCOMbbb, or
bHANSCOM AFB.)
These 10 columns may be used to
identify the computer manufacturer
and machine serial number. The
name may be positioned any place
within the field.
(Example: bCDC-6600b, or GE-635

bbbb.)

14

Columns

Name

35-45

Data of Basic
File Creation

46-47

Modification
Number

48-58

Date of Creation
of this File

59-72
73-76

Not Used
DDI-NO

77

Card Type

78-80

Sequence Number

4.1.2.1.2

Description
These 11 columns may be used
to identify the date om which the
basic form of the Population File
has been created. The month, day,
and year are specified YYYYbMM
MbDD. (Example: MAYbl 2bl 968, or
SEPbl3bl967).
These 2 columns may be used to
identify the number of times that
the basic file has been modified.
(Example: Second modification
02, tenth modification 10).
These 11 columns may be used to
identify the date that this file
was created. The month, day, and
year are specified YYYYbMMM
bDD.
(Example: DECbl7bl968, or
MAYb25bl968).
These 14 columns are not used.
These 4 columns contain the
test serial number, the DDI-NO,
0001.
This column contains the character
A that indicates that this card is
a non-test statement card.
These 3 columns contain 001
indicating that this card occupies
the first 80 columns in the System
Module.

System Header Card 2

System Header Card 2 occupies the second set of 80 character positions in the System
Module and contains the following information:
Colu mns

Name

1-35

Validation System
Name

Description

15

These 35 columns may be used to
identify the particular modification
of the validation system.
(Example: bbbbbbbbbbbJCVSbMAYb
1968bbbbbbbbbbb, or
JOVIALbCOMPILERbVALIDATIONb
SYSTEMb5).

Columns

Name

36-72

Operating System
Name

73-76

DDI-NO

77

Card Type

78-80

Sequence Number

Description
These 37 columns are used to
identify the operating system
within which the JCVS is imbedded,
(Example: bbbblBM-360bDISKb
O PERATI NGbSYSTEMbbbb).
These 4 columns contain the test
serial number, the DDI-NO, 0001 .
This column contains the character
A that indicates this card is a
non-test statement card.
These 3 columns contain 002
indicating that this card occupies
the second 80 columns in the
System Modi le.

See Appendix 2 for complete description of all of the System Header Card 2 card types
used on the five computer-compiler configurations.
4.1 .2.1 .3

Environmental Hardware Card 1

Environmental Hardware Card 1 occupies the third set of 80 character positions in the
System Module and contains the following information:
Columns

Name

1-30

System Input

31-60

System Output

61

Space Code

62

Double Space Code

63

Page Eject

64-70

Memory Size

71-72
73-76

Not Used
DDI-NO

Description
These 30 columns contain the
acceptable hardware name for the
system input unit.
These 30 columns contain the
acceptable hardware name for the
system output unit.
This column contains the printer
single space code.
This column contains the printer
double space code.
This column contains the printer
page eject code.
These 7 columns contain the core
memory size.
These 2 columns are not used.
These 4 columns contain a DDI-NO
= 0001.

Colu mns

Name

77

Card Type

78-80

Sequence Number

4.1.2.1.4

Description
This column contains the
character A that indicates this
card is a non-test statement card.
These 3 columns contain a sequence
number = 003.

Environmental Hardware Card 2

This card occupies the fourth set of 80 character positions in the System Module and
contains the following information:
Columns

Name

1-30

System Punch

31-60

Scratch 1

61-72
73-76

Not Used
DDI-NO

77

Card Type

78-80

Sequence Number

Description
These 30 columns contain the
acceptable hardware name for
the system punch unit.
These 30 columns contain the
acceptable name for a scratch
unit 1 .
These 4 columns contain a DDI-NO

= 0001.

4.1 .2.1 .5

This column contains the character
A that indicates that this card is a
non-test statement card.
These 3 columns contain a sequence
number = 004.

Environmental Hardware Card 3

This card occupies the fifth set of 80 characters in the System Module and contains the
following information:
Columns

Name

1-30

Scratch 2

31-60

Scratch 3

61-72

Not Used

Description
These 30 columns contain the
acceptable hardware name for
tape scratch unit 2.
These 30 columns contain the
acceptable hardware name for
tape scratch unit 3.

17

Colu mns

Name

73-76

DDI-NO

77

Card Type

78-80

Sequence Number

Description
These 4 columns contain the
DDI-NO = 0001 .
This column contains the character
A that indicates this card is a
non-test statement card.
These 3 columns contain a sequence
number = 005.

See Appendix 3 for a complete description of the Environmental Hardware Cards for the
five computer configurations.
4.1 .2.1 .6

Environmental Software Cards

These cards provide specific operating system control cards that may be used to specify the
functions to be performed by the operating system and the JOVIAL START and TERM cards
that bracket the JOVIAL source program. These cards have SEQ-NO's greater than 005 and
are stored in the System Module shifted right one column.
Colu mns

Name

Description

Not Used
Environmental Software These 71 columns provided contain
Statement
a request of the operating system to
perform a specific task.
These 4 columns contain the test
DDI-NO
serial number, the DDI-NO, 0001 .
Card Type
This column contains either the
character L that indicates this card
precedes the JOVIAL source program
or the character F that indicates
this card follows the JOVIAL source
program.
Sequence Number
These 3 columns may contain the digits
005 through 050 which serves to indicate
the relative position of this card in the
System Module.

2-72

73-76
77

78-80

A current list of the Environmental Software cards excepting the JOVIAL START and TERM
cards (GE-635 only) used by the JCVS is given for each computer configuration in Appendix 4,
4.1.2.2

Test Modules

/ test module is a collection of JOVIAL statements that test a particular feature of the
JOVIAL compiler. The feature to be tested may be a JOVIAL concept, a single JOVIAL

18

statement or a collection of JOVIAL statements.
1 .
2.
3.
4.
5.
6.
7.
8.

Included in each test module are the:

Test identification field
Input test data fields
Test result fields
Expected result fields
Initialization procedures
Test statements comprising the test
Results analysis procedures
Output formatting procedures

The tests are carried in the Population File in order of ascending DDI-NO. Within
each DDI-NO the test header and the JOVIAL test statement cards are carried in order
by ascending Sequence Number. The DDI-NO identifies each test module to all of the
JCVS program modules and the user. Population File test modules may be assigned a
four digit DDI-NO between 0500and 9997.
Each Test Module begins with a Test Header Card that contains the DDI-NO, the
Sequence Number, the test name, one or more references to the associated paragraphs
in the AFM 100-24, and, if required, a number called the Mandatory DDI-NO of a
module called the Mandatory Module upon which the current module depends. Additional
JOVIAL comment cards may be included anywhere in the Test Module. See Appendix 5
for samples of these cards in the Typical Test Module.
The Mandatory Module could contain data or support statements required by the dependent
module and, hence, must be present in any JOVIAL source program including the dependent
module; or the Mandatory Module could contain another feature test whose validity must
be established before a successful execution of the dependent module feature test may be
considered valid. See Appendix 5 for some typical Population File modules.
4.1.2.2.1

Test Header Card

The Test Header Card occupies the first 80 characters in a JOVIAL Test Module record
in the Population File and contains information about the test statements that follow.
Columns

Name

Description

1-2
3-22

Open Quotes
Test Name

19

These 2 columns contain quote marks.
These 20 columns describe what
feature the JOVIAL statements test.
(Example: THREEbFACTORbFOR
bbbb, orGOTObSTATEMENTbbbbbb).

Columns

Name

Description

23-27

CED-NOl

28
29-33

Not Used
CED-N02

34
35-39

Not Used
CED-N03

40
41-45

Not Used
CED-N04

46
47-51

Not Used
CED-N05

52
53-57

Not Used
CED-N06

58
59-62

Not Used
Mandatory DDI-NO

63-64

Close Quotes

65-72
73-76

Not Used
DDI-NO

77

Card Type

78-80

Sequence Number

These 5 columns identify a
reference in the AFM 100-24 to the
feature being tested.
These 5 columns identify a
reference in the AFM 100-24 to
the feature being tested.
These 5 columns identify a
reference in the AFM 100-24 to
the feature being tested.
These 5 columns identify a
reference in the AFM 100-24 to
the feature being tested.
These 5 columns identify a
reference in the AFM 100-24 to
the feature being tested.
These 5 columns identify a
reference in the AFM 100-24 to
the feature being tested.

20

These 4 columns identify the
DDI-NO of a Mandatory Module
upon which the current test
module depends.
These 2 columns contain quote
marks.
These 4 columns contain the test
serial number, the DDI-NO.
(Example: 4500, 7500, 1410).
This column contains either the
character A or B or C that indicates
this card is a non-test statement can
These 3 columns contain 001,
indicating that this card occupies
the first 80 columns of the Test
Module on the Population File.

4.1 .2.2.2

JOVIAL Statement Card

The JOVIAL Statement Card contains one or more JOVIAL statements to be used in a
generated JOVIAL source program. Only the first seventy-two card columns may be
used for the statement. Columns 73-80 will be used for card identification.
Columns

Name

1-72

JOVIAL Statements

73-76

DDI-NO

77

Card Type

78-80

Sequence Number

4.1.2.3

Packet Cards

4.1.2.3.1

Control Card - PF

Description
These 72 columns may contain
one or more JOVIAL statements.
These 4 columns contain the test
serial number, the DDI-NO.
(Example: 2100, 4500, 7600).
This column contains the character
J that indicates this card is a test
statement card.
These three columns contain a
number, 002-050, specifying the
position of the JOVIAL Test Statement
Card within the Test Module.
(Example: 015 indicates that this
card occupied the 15th 80 column
position in the Test Module.)

The various options permitted by the Population File Maintenance Module may be
requested by means of the following control card:
Columns

Name

1

Control Card
Indicator

2-4

Control Card
Indentifier

Description

Mode Designator

This column must contain the
character C denoting the card as
a control card.
These 3 columns may be assigned
any 3 digits by the user to identify
the control card.
This column is used to signify the
run type
C = CREATE run
U= UPDATE run

21

-

Columns

Name

Description

Print Option

This column may be used to
request the printing of the new
Population File on the Audit File-PF
non-space - Print
space - Do not print
This column may be used to
request the punching of the new
Population File.
non-space - Punch
space - Do not punch

Punch Option

8-80

Not Used

When submitting this card to the Population File Maintenance Module the Control Card - PF
directly precedes the card deck comprising the Current File - PF.
4.1.2.3.2

Delete Card

The Delete card is used to signal the Population File Maintenance Module to eliminate
a record or a specific card from the Population File.
The form of the Delete card follows:
Columns

Field Size

Description

1-72
73-76
77
78-80

72
4
1
3

Not Used
DDI-NO
Update Function = D
Sequence Number

When this card is used to delete a module from the Population File, it must be included in
the Current File - PF with the DDI-NO equal to the DDI-NO of the record to be
eliminated from the Population File and the Sequence Number equal to 000. When
this card is used to delete a card image from a record in the Population File it must be
included in the Current File - PF with the Sequence Number and DDI-NO equal to the
corresponding Sequence Number and DDI-NO of the card image to be eliminated from
the Population File.
4.1.2.4

Input Files

The Population File Maintenance Module operates upon two input files, an optionally
present Population File and the Current File - PF.

22

4.1.2.4.1

Population File

The Population File is organized into equal size logical records. Each logical record
is composed of 4000 characters and consequently can accomodate fifty 80-column cards.
Each logical record is recorded on one physical record.
The first few records on the Population File are System Modules and each contains all
of the environmental and indicative information pertinent to various hardware configuration
operating systems and JOVIAL compilers. A System Module may be assigned any DDI-NO
between 0001 and 0499.
The remainder of the records (excepting modules 9998 and 9999) contain the individual test
modules. The first eighty characters of the module are cal led the Test Module Header and
contain information pertinent to the specific test module. Column 77 of the Test Module
Header contains either the characters A, B, or C. The character B present in a Test Module
Header indicates the module is an extension of the previous module and the two physical
test modules act as a collection of physical modules. The character A or C present in a
Test Module Header indicates the module is the beginning of a new physical module or a
collection of physical modules. The character C present in a Test Module Header indicates
the physical module or collection of physical modules is a mandatory module that must be
present in every generated source program. Figure 4-1 gives a physical layout of the
Population File.
4.1.2.4.2

Current File-PF

The Current File-PF, which directs the Population File Maintenance Module to update
the Population File consists of card packets containing environmental, test, indicative or
functional information. Environmental information (e .g ., hardware configuration descriptions,
operating system control cards, etc.) is presented by means of the Environmental Packets, test
information (e.g., JOVIAL test statements) by means of the Test Packets and functional
information (the Population File Maintenance Module update command, delete) by the Delete
Packets. Indicative information (e.g., DDI-NO, Sequence Number, etc.) is included where
required in all packets. A test serial number, the DDI-NO, is assigned to each packet and each
card within the packet contains this number in columns 73-76. In addition, ordering the car^s
within each packet is controlled by the Sequence Number in columns 78-80. The Environmental
Packet consists of the following cards in the order specified:
Number of Cards
1)
2)
3)
4)

System Header
System Header
Environmental
Environmental

Card 1
Card 2
Hardware Cards
Software Cards

1
1
3
M

The total number of Current File-PF cards in one packet acceptable to the Population File
cannot exceed 50; consequently, M, the number of Environmental Software Cards, must
be less than or equal 45.

23

gO c/A-'v/4 A.T £.'•<->/" I'•-'V '

— Lf.Au

4$2C Cr.on'c/rrS
£0 ehtinrJsr t /card

FILLED

7"^sr tf£AJ?££. I

M&DUIJE it

80 chartcUrS/OarDULt£ I
40QO cA

TesT MOOULB JL
3920 cJ,fir#c£n

TE£>T~
-5 7~/f r£M£MTS

TESr ^£/tC?£/e /

MOLULE KJ

MODULE N

4OQ0 cka.ado.
6C carcic

JbvlfiL

TLsr MODULE A/

TEST

&1ZO cJ,*racfc^

£>7*ir£M£tJ7Z3

Figure*4rl'

Population File

The Test Packet consists of the following cards:
Number of Cards
1)
2)
3)

Test Header Card
JOVIAL Statement Cards
DELETE Cards

1
N.
N^

The total number of cards in one packet acceptable to the Population File cannot exceed 50;
consequently, N. + NL, the number of JOVIAL Statement Cards plus DELETE cards may not
exceed 49.
The DELETE Packet consists of one card, the DELETE Card.
The Current File - PF consists of a collection of the above mentioned packets in order
of Sequence Number within DDI-NO. Only those cards that are to effect elements in
the old Population File need to be included in the Current File - PF.
4.1.3

Function Operation

The Population File Maintenance Module operates either to initiate a Population File
completely from the Current File-PF or to update an existing Population File by means
of information residing on the Current File-PF. In each case, the control card permits
the user to specify options to print and/or to punch the resulting new Population File.
4.1 .3.1

Create Population File

When the Population File Maintenance Module is used to initiate a Population File
the Current File - PF may contain only information to be added to the file. Consequently,
no DELETE cards are permitted in the Test Packets that comprise the Current File-PF.
The packets are placed in order by DDI-NO to form the Current File - PF. The Mode
Designator in the control card is set to C and the appropriate print/punch options are
selected. The control card precedes the Current File - PF when submitted to the Population
File Maintenance Module.
Since no old Population File is required for this run, all the test modules in the Current
File - PF utilize the update function ADD and are ADDed to form the Population File.
4.1.3.2

Update Population File

When the Population File Mai ntenance Module is used to update an existing Population
File, DELETE cards may be present in the packets comprising Current File-PF. Each Current
File - PF packet is composed of a collection of cards, each card invoking an update function
which performs one of the following operations:

25

1)
2)
3)
4)

Add a card to a new or an existing test module
Replace a card on an existing test module
Delete one or more existing test modules
Delete a card from an existing test module

The update functions are controlled on the basis of two items included in every card
in the Population File:
1)
2)

DDI-NO (columns 73-76)
Sequence Number (columns 78-80)

The packets in the Current File-PF may contain no more than 50 cards and must be in
order within the packet by Sequence Number within DDI-NO. The Sequence Numbers,
however, need not be consecutive.
In order to reduce the card preparation requirements of the system, the ADD feature and
REPLACE feature are invoked automatically. Specifically the update functions adhere to
the following rules:
1 .

ADD
If an ADD (a card to be ADDed to the Population File) card is included in a packet
on the Current File-PF and no card with the same DDI-NO (columns 73-76) and
Sequence Number (columns 78-80) is present in the old Population File, the card in
the Current File-PF is automatically added to the Population File in its proper sequence.

2.

REPLACE
If a REPLACE card (a card intended to REPLACE another card on the Population File) is
included in a packet on the Current File-PF and a card with the same DDI-NO (columns
73-76) and Sequence Number (columns 78-80) is present in the old Population File, the
card in the Current File-PF automatically replaces the corresponding card on the new
Population File.

3.

DELETE
The DELETE option is invoked by means of a DELETE packet included in the Current File-PF.
This packet may instruct that either an entire record or a card within a record not be recorded
on the new Population File. If the Sequence Number on the DELETE packet is 000 and the
DDI-NO matches a DDI-NO in the old Population File the entire record and any suceeding
records with B in column 77 of the Test Module Header are not recorded on the new Population

File.
If the Sequence Number on the DELETE packet is a number between 001 and 050
and the DDI-NO and Sequence Number match a DDI-NO and Sequence Number

26

in the old Population File, the matched card is not recorded on the new
Population File. If a match is not effected, a diagnostic is printed.
Consequently, a packet in the Current File - PF may contain ADD,
REPLACE, and DELETE functions applicable to a specific record on the old
Population File. When card images on the old Population File are to be altered,
only the cards that are to provide the changes need be included in the Current
File - PF packets.
On the other hand, an entire record may be deleted by the inclusion in the
Current File - PF of the appropriate DELETE packet.
The Population File Maintenance Module only changes those card images on
records in the existing Population File that have been specified by the user.
The packets are placed in order by Sequence Number within DDI-NO to
form the Current File - PF. The Mode Designator in the control card is set
to U and the appropriate print/punch options are selected. The control card
precedes the Current File - PF when submitted to the Population File Maintenance
Module.
4.1.4

Description of Expected Results

4.1.4.1

Output Card Formats

The output card formats correspond to the formats for cards as described in Section
4.1.2.
4.1.4.2

Output Files

The Population File Maintenance Module produces three output files, the Population
File, the Audit File - PF, and the Punch File - PF.
4.1.4.2.1

Population File

The results of either a CREATE or an UPDATE run will always produce a new Population
File which is completely described in Section 4.1 .2.
4.1.4.2.2

Audit File - PF

The Audit File - PF contains a listing of all diagnostics and trace messages originating
from this module. As an optional feature, the user may request to print on the Audit File - PF
a working listing of the card images on the new Population File by selecting the print option
on the Control Card - PF. Since the Audit File - PF is only a working listing, diagnostic and

27

tracing information will be interspersed with the Population File card irrages on the
Audit File - PF.
Following is a list of the diagnostic messages to be printed in the Audit File-PF together
with their explanations:
Diagnostic Message

Explanation

NO UPDATE FUNCTION CARD
RECORD TO BE DELETED NOT ON
OLD MASTER FILE

CURRENT FILE CARDS ARE OUT OF
SEQUENCE
INITIAL RUN CARD NOT PRESENT

OVERFLOW MASTER RECORD BUFFER

•
There is no control card
preceding the Current File-PF.
The Current File-PF contains a
DELETE packet referencing a
DDI-NO not on the old
Population File.
The cards in the Current File-PF
are not in sequence by DDI-NO.
The control card preceding the
Current File-PF contains an
incorrect Mode Designator.
The Current File-PF contains a
card whose sequence number is
greater than 50.

Following is a list of the trace messages to be printed on the Audit File-PF.
The following messages are all paragraph names printed from within each named paragraph:
1)
2)
3)
4)
5)
6)

IUC
UPDATE CONTROL
OLD MASTER FILE READOUT
END OF CURRENT FILE
END OF OLD MASTER FILE
END OF OLD MASTER FILE 4

The following typical trace message is printed whenever the WRITE-ERROR paragraph
is entered;
LAST CARD KEY
LAST CURRENT FILE KEY
LAST OLD MASTER FILE KEY

0002A005
0002A003
0005A004

The information opposite the LAST CARD KEY represents the control field (columns 73-80)
of the last Current File-PF card read.

28

The information opposite the LAST CURRENT FILE KEY represents the control field
of the next to last Current File-PF card read.
The information opposite LAST OLD MASTER FILE KEY represents the control field
of the first card image in the last physical record read from the old Population File.
This trace information is printed on one line in the Audit File-PF.
4.1.4.2.3

Punch File - PF

Yet another option, the punch option, may be selected by the user to obtain a card
deck of all card images on the Population File containing information.
4.2

Selector Module (SJCVS)

4.2.1

Purposes and Uses

The Selector Module performs the major task of assembling and organizing test and
support structures for the JOVIAL test program.
1 .
2.
3.

Using the input specifications obtained from the user, appropriate
test and support structures may be selected.
The resulting test and support structures are placed in the order
needed for compilation.
Environmental Software cards are placed before and after the JOVIAL
source test program.

Input to the Selector Module consists of the Population File, the Test Selection File,
(a collection of user specified cards which control the identity of the tests selected
from the Population Fi le) and a control card requesting the specific options provided
by the module.
Output of the Selector Module includes a Source Program File consisting of the generated
JOVIAL Source program, the Audit File-S consisting of a diagnostics, trace message
with an optional listing of the Source Program File and an optional Punch File-S consisting
of a card deck of the Source Program File.
4.2.2
4.2.2.1

Preparation of Inputs
Input Card Formats

Following is a description of the card types and formats input to the Selector Module.

29

4.2.2.1.1

Test Selector Card

The Test Selector Card permits the user to specify the selection of one or more test
modules from the Population File. The user specifies the DDI-NO identifying the first
test module to be selected, the increment to be added to the DDI-NO identifying the
first test module, and the DDI-NO identifying the last test module to be selected. If
only one test module is to be selected at a time, the increment may be set to 0000 or
|i;ft blank. The following describes the format of the Test Selector Card.'
Columns

Name

1-4

Control Word

5-10
11-14

Not Used
Starting DDI-NO

15-20
21-24

Not Used
Increment

25-30
31-34

Not Used
Final DDI-NO

35-80

Not Used

4.2.2.1.2

Description
These 4 columns must contain
the control word TEST.
These 4 columns contain the
DDI-NO identifying the first
Population File Test Module
to be selected by this Test
Selector Card.
These 4 columns contain the value
to be added to the starting DDI-NO
and succeeding DDI-NO's until
the final DDI-NO has been
selected.
These 4 columns contain the
DDI-NO identifying the last
Population File Test Module to
be selected by this Test Selector
card.

Control Card-S

The various options permitted by the Selector Module may be requested by means of
the following control card:
Columns

Name

Description

Control Card
Indicator

This column must contain the
character C denoting the card
as a control card.

30

Columns

Name

2-4

Control Card
Identifier

5-6

Margin A

7-8

Margin B

Description
These 3 columns may be assigned
any 3 digits by the user to identify
the control card.
These 2 columns are used to
designate the column number of
Margin A on the Source Program File
card images.
These 2 columns are used to designate
the column number of Margin B
on the Source Program File card images.
This column may be used to request
the printing of the Source Program File
on the Audit File-PF.
non-space - Print
space - Do not print
This column may be used to request
the punching of the Source Program File.
non-space - Punch
space - Do not punch
The DDI-NO of the appropriate System
Module to be selected from the Population
File.

Print Option

10

Punch Option

11-14

System Module
DDI-NO

15-80

Not Used

4.2.2.2

Input Files

The Selector Module operates upon two input files: the Population File and the Test
Selection File.
4.2.2.2.1

Population File

The Population File has been thoroughly described in Section 4.1 .2.
4.2.2.2.2

Test Selection File

The Test Selection File consists of a collection of Test Selector cards that direct the
generation of a JOVIAL source program. One or more tests may be selected by means of a
Test Selector card. The collection of Test Selector cards may be submitted to the Selector
Module in any order.
4.2.3

Function Operation

The Selector Module, under the direction of the Test Selection File, operates on the Population
File to produce a single JOVIAL source program consisting of 80 column card images from one
or more JOVIAL test modules residing on the Population File.
31

The Test Selection File controls the identity of the Population File test modules that are
recorded on the Source Program File. For example, suppose the Test Selection File
consisted of the following Test Selector card information with no Mandatory DDI-NO's
involved.

Card Number

Starting DDI- -NO

Increment

Fi nal DDI-NO

1
2
3
4

4100
3000
6000
8100

0010
0005
0000
0001

4200
3010
8105

The Source Program File would consist of the following sequence of selected test modules
as identified by their associated DDI-NO's:
3000, 3005, 3010, 4100, 4110, 4120, 4130, 4140, 4150, 4160, 4170,
4180, 4190, 4200, 6000, 8100, 8101, 8102, 8103, 8104, 8105
Notice that the test modules selected as indicated by the list of DDI-NO's are not in the
same order as they appear on the Test Selection File, but are in ascending order by DDI-NO,
the same order that they appear on the Population File. All mandatory and environmental
software cards supporting the generated test, and modules 9998 and 9999, are automatically
selected or generated by the Selector Module.
In the following example, suppose the Test Selection File consisted of the following
Test Selector Card information:
Card Number

Starting DDI-NO

Increment

1
2

4100
3000

0010
0005

3

6000

0000

Final DDI-NO
4120
3010

Suppose further that the Mandatory DDI-NO's associated with each of the above DDI-NO's
ore given in the following list:
DDI-NO

Mandatory DDI-NO

4100
4110

2500

4120
3000
3005
3010
6000

1200
2215
2210
2210
4000

32

Suppose also that the Test Module headers for modules 2000 and 8000 have C's in column 77
and that the Test Module headers for modules 2216, 4101, 4102, and 8001 have B1 s in
column 77. Assuming this, when the Test Selection File is submitted to the Selector Module,
the following test modules will be selected and placed on the Source Program File in the
following order:

Test Module

DDI-NO

1
2
3
4
5
6
7
8
9

Test Module

1200
2000
2210
2215
2216
2500
3000
3005
3010

10
11
12
13
14
15
16
17
18

DDI-NO
4000
4100
4101
4102
4110
4120
6000
8000
8001

Mandatory test modules will be supplied only once in the output of the Selector Module.
Notice that again the test modules are placed on the Source Program File in order of
ascending DDI-NO. In addition the mandatory modules supporting the generated test,
modules 0001 , 9998 and 9999 are selected or generated by the Selector Module. All modules
with a C in column 77 are automatically selected by the Selector Module. Modules with a
B in column 77 should not be selected by the user.
4.2.4

Description of Expected Results

4.2.4.1

Output Card Formats

Following is a description of the card types and formats output by the Selector Module.
4.2.4.1.1

Environmental Software Card

These cards provide communication between the generated JOVIAL source program and the
operating system of the particular computer. These cards both precede and follow the JOVIAL
source program and are operating system specific. For a description of the operating system
cards for the five computers used by the JCVS see Appendix 4. For a complete description of
this card see Section 4.1 .2.1 .6.
4.2.4.1.2

Test Header Card

These cards are placed in the JOVIAL source program as comment cards. They serve to identify
the test and provide cross referencing information between the DDI-NO and associated AFM 100-24
references, the CED-NO's. A complete description of this card is given in Section 4.1 .2.2.1 .

33

4.2.4.1.3

JOVIAL Source Program Card

The JOVIAL Source Program Card contains one or more JOVIAL statements to be used
in a generated JOVIAL source program. As with most cards associated with the JCVS
columns 73-80 will be used for card identification.
Columns 1-72, however, will be subdivided into a maximum of three sections as
indicated in the diagram.
72

1

Margin B

Margin A

Margins A and B specify card columns selected by the user between which is contained
as much of the content of a JOVIAL Statement Card as permitted by the margin
specifications. Card column 1 from the JOVIAL Statement Card is transferred to the
card column specified by Margin A in the JOVIAL Source Program Card; Column 2 is
transferred to column Margin A+l , etc. If column k is transferred to Margin B,
columns k+1 through 72 of the JOVIAL Statement Card are not transferred and, hence,
lost. These margin specification features are provided to the user because of the
lack of standardization of JOVIAL J3 reference formats.
The two margins must adhere to the following inequality:
column 1 £•

Margin A

*-

Margin B — column 72

If no Margins are specified, Margin A will nominally be set to 1 and Margin B to 72.
Notice that the character string signifying the JOVIAL statement must be short enough to
fit between the margin. Specifically the character string must adhere to the following
inequality:
Length of character string

Margin B - Margin A + 1

T le form of the JOVIAL Source Program Card follows.

34

Columns

Name

1 -Margin A
Margin A - Margin B

Not Used
JOVIAL Statement

Margin B-72
73-76

Not Used
DDI-NO

77

Card Type

78-80

Sequence Number

4.2.4.2

Description

These (Margin B - Margin A)
columns contai n one or more
JOVIAL statements.
These 4 columns contain either
the DDI-NO (e.g., 2100, 4500,
7610) or the number 9999.
This column contains the character
J that indicates this card is a test
statement card.
These 3 columns contain a number,
002-051 specifying the position of
the JOVIAL Source Program Card
within the card images from the
selected Test Module.

Output Files

The Selector Module produces three output files: The Source Program File, the Audit
File-S, and a Punch File-S.
4.2.4.2.1

Source Program File

The Source Program File contains the JOVIAL source program. The generated source
program consists of, in part, JOVIAL statement card images from Test Modules in the
Population File. Preceding and following the source program are operating system
cards that form the linkage between the JOVIAL source program and the operating system.
In addition, every test present in the Source Program File may be identified by the Test
Header card preceding the JOVIAL test statements comprising the test.
The Source Program File is recorded one output card image per physical record.
Since the Source Program File is in the same order as the Population File, by Sequence
Number within DDI-NO, the DDI-NO and Sequence Number act as the control items
for this file.
Since the environmental software cards that follow the generated JOVIAL source program
originate from the System Module; these cards would normally have a DDI-NO equal to
0001 in the Source Program File. As a result, these cards would be out of order in a
generated JOVIAL source program. In order to alleviate this situation, all trailing
environmental software cards are automatically assigned a DDI-NO = 9999. Sequence
numbers in these cards, however, remain unchanged.

35

The START card will contain the DDI-NO of the selected System Module and the same
Sequence Number it possessed in the System Module. The TERM card is assigned the
DDI-NO = 9999 but contains the same Sequence Number it possessed in the System Module.
Figure 4-2 gives a physical layout of the Source Program File.
4.2.4.2.2

Audit File-S

The Audit File-S contains a listing of all diagnostics and trace messages emanating from
this module. As an optional feature, the user may request to print on the Audit File-S,
a working listing of the card images on the new Source Program File by selecting the
print option on the Selector control card. Since *he Audit File-S is only a working
listing, diagnostic and tracing information will be interspersed with Source Program File
card images on this file.
Following is a list of the diagnostic messages to be printed on the Audit File.
Diagnostic

Explanation

EXCEEDED DDI-NO TABLE

There exists on the Population File
a DDI-NO greater than 9998.
Check the Population File for cause
of error.
In processing the Population File
the DDI-NO on the current
Population File record is less than
the DDI-TABLE index. Probable
cause: Machine malfunction.
An unexpected end of file has been
triggered on INFILE. Check the
Control Card-S and the Test Selection File for cards that could cause
the end of file and restart the progr<
An unexpected end of file has been
encountered on the Population File
Check to see if the Population File
has been rewound properly and
restart program. This diagnostic is
probably triggered by a machine
error.
There is no Control Card-S or an
incorrect Control Card-S present
in the INFILE. Supply the correct
Control Card-S and restart.

DDI-NO AND INDEX NOT
SYNCHRONIZED

UNEXPECTED EOF INFILE

UNEXPECTED EOF POP-FILE

NO CONTROL CARD

36

L£AO PEpAr/fi'C,3/i>TTrM CAiWL
LEAD 4f>£tj4r-iM6 SYfrs-'V C*£PZ

Lf/ID fr-C&TjNG SYSTEM C/>fDK

irsr
JOVIAL ri?TS7#7ZH£xA'<:'V<'0 I
j$y/*L T£*rsr*r£-M£A/r a^jcp 2
JdVIAL 7*3rsr*r£M/rAJT **& $

1

MODULE

/esr
JbviAL •msrsmrEH£NT

OVJ>

(

J&V/AL 7£ST 5>TX7£MChtr C*A? 2.

EXECUTTON
MOJX/JLJT

Z

JdVI/IL 7tST SntTZMtrrir CA&. 3

7Y^r HE4/PC* CAKU • A/

£y.£C6/7TOA/
MODULE

roiLaii 
RXJJOW

SM&TLH

cA/ecji

ci>l£JiriN6> SVCTIH &££> &

Figure ,4-;2-

Source Program File
37

FOLLOW

N

OPL4ATIMG>

Diagnostic

Explanation

INCORRECT TEST SELECTOR CARD

There is an incorrect Test Selector
Card in the INFILE. Correct the
card and restart the program.
The Control Card-S margin specifications
are incorrect. Correct specifications and
restart program.

INCORRECT CONTROL CARD

Following is a list of trace messages to be printed on the Audit File-S.
The following trace messages are all paragraph names printed from within the named
paragraphs:
1 .
2.

BDT1
BUILD-SPF

The following trace messages are values that monitor the contents of key items together
with the paragraph names printed from within the named paragraphs.
Message

Originating Paragraph

1 .
2.
3.

BDT2
BMT1
ERR-PROC-6

4.2.4.2.3

Contents of item DDI-NUMBER
BMT1 , Contents of item DUMP
Contents of record CARD
Punch File-S

Yet another option, the punch option, may be selected by the user to obtain a card
deck of all card images on the Source Program File.
4.3

Source Program Maintenance Module (SOPMM)

The Source Program Maintenance Module is used to modify either the JOVIAL source
program generated by the Selector Module or a JOVIAL source program previously
modified by SOPMM. Modifications may be necessary because:
1)
2)
3)
4)
5)

One or more tests did not compile correctly; therefore, deletions of
erroneous statements or changes to existing statements can be made.
The user wishes to change a test in order to compare with a previous run.
The user may wish to add self contained non standard tests.
Certain areas of the JOVIAL compiler have not been debugged completely.
The user may wish to eliminate partially implemented features.

38

Input to the Source Program Maintenance Module consists of a Source Program
File, the Current File-SP, and a control card requesting specific options provided
by this module.
Output from the Source Program Maintenance Module includes an updated Source Program
File consisting of the modified JOVIAL source program, the Audit File-SP consisting of
diagnostics, trace messages with an optional listing of the Source Program File and an
optional Punch File-SP consisting of a card deck of the updated Source Program File.
4.3.1

Preparation of Inputs

4.3.1 .1

Card Inputs

4.3.1.1.1

Control Card-SP

The various options permitted by the Source Program Maintenance Module may be
requested by means of the following control card:

Colu mns

Name

1

Control Card Indicator

2-4

5

Description

Control Card Identifier

Mode Designator

Print Option

Punch Option

39

This column must contain the
character C denoting the card as a
control card.
These 3 columns may be assigned any
3 digits by the user to identify the
control card.
This column is only referenced
descriptively and does not influence
the run type which is always an
UPDATE run. It should be set to
U for documentary purposes.
This column may be used to request
the printing of the new Source
Program File
non-space - Print
space - Do not print
This column may be used to request
the punching of the new Source
Program File.
non-space - Punch
space - Do not punch

Columns

Name

Description

8

Trace Option

9-80

Not Used

This column may be used to requesi
printing on the Audit File-SP of al!
ihe trace messages originating in this
module.
non-space - Print messa jes
space - Do not print me .sages

When sjbmitting this card to the Source Program i'/taintenance Module the Control Card-SP
directly precedes the card deck comprising the Current File-SP.
4.3.1.1.2

Other Card Inputs

A complete description of all other card forms contained in either the Source Program
File or the Current File-SP is given in Sections 4.1 .2.3.2 and 4.2.4.
4.3.1 .2

Input Files

4.3.1.2.1

Source Program File

The Source Program File has been completely described in Section 4.2.4.2.1 .
4.3.1.2.2

Current File-SP

The Current File-SP which directs the Source Program Main enance Program to update
the Source Program File is composed of individual cards tha*" provide the capability to
add, delete, and replace information on the Source Program File.
The following card types may appear in the Current File-SP:
1 .
2.
3.
4.

Environmental Software Card
Test Header Card
JOVIAL Source Program Card
DELETE Card

The information content of the aforenentioned cards has be. n completely specified in
Sections 4.1 .2 and 4.2.4.1 .3.
A seria1 number, the DDI-NO, is present in columns 73-76 of each card in this file, and
a Sequence Number in columns 78-80. The cards in this file are placed in order by
Sequence Number within DDI-NO.

40

4.3.2

Function Operation

The Source Program Maintenance Module operates on an existing Source Program
File directed by a Current File-SP to update and generate a new Source Program File.
The control card associated with this program permits the user to specify options to print
and/or punch the resulting new Source Program File.
The Source Program Maintenance Module provides the user with the ability to add
information to the Source Program File, delete information from the Source Program File
or replace information on the Source Program File on a card image by card image basis.
The Current File-SP consists of individual cards ordered by DDI-NO and Sequence Number.
Each card invokes an update function implicitly or explicitly. The cards within the Current
File-SP permit the user to change any card in the Source Program File. The control card
precedes the Current File-SP when submitted to the Source Program Maintenance Module.
Each card in the Current File-SP specifies an update function which performs one of the
following operations:
1 .
2.
3.
4.

ADD a card to the Source Program File
REPLACE a card on the Source Program File
DELETE one or more test modules from the Source Program File
DELETE an entire test module from the Source Program File

The update functions are controlled on the basis of two items included in every card in
the Source Program File.
1 .
2.

DDI-NO (columns 73-76)
Sequence Number (columns 78-80)

In order to reduce the card preparation requirements of the system, the ADD feature
and REPLACE feature are invoked automatically. Specifically, the update functions
adhere to the following rules.
ADD
If an ADD card (a card to be ADDed to the Source Program File) is included in the Current
File-SP and no card with the same DDI-NO (columns 73-76) and a Sequence Number
(columns 78-80) is present in the old Source Program File, the card on the Current File-SP
is automatically added to the Source Program File in its proper sequence.
REPLACE
If a REPLACE card (a card intended to REPLACE another card in the Source Program File) is
included in a packet on the Current File-SP and a card with the same DDI-NO (columns
73-76) and Sequence Number (columns 78-80) is present on the old Source Program File,
the card on the Current File-SP automatically replaces the corresponding card on the new
Source Program File.

41

DELETE
The DELETE option is invoked by means of a DELETE card included in the Current File-SP.
This card causes a card with the same DDI-NO and Sequence Number not to be recorded on
tie new Source Program File. If the Sequence Number equals 000, the entire module
sfecified by the DDI-NO and any directly succeeding modules with a B in column 77 in the
Tost Module Header are deleted.
4.3.3

Description of Expected Results

4.3.3.1

Output Card Formats

A complete description of all of the card forms contained in either the Source Program File
or the Punch File-S is given in Section 4.1 .2 and 4.2.4.1 .3.
4.3.3.2

Output Files

The Source Program Maintenance Module produces three output files: The Source Program File,
the Audit File-SP, and a Punch File-SP.
4.3.3.2.1

Source Program File

The Source Program File has been completely described in Section 4.2.4.2.1 .
4.3.3.2.2

Audit File-SP

The Audit File-SP as an optional feature may contain a listing of all diagnostics and trace
messages originating from this module. A second optional feature the user may request is to
print on the Audit File-SP a working listing of the card images on the new Source Program File
by selecting the print option on the Control Card-SP. Since the Audit File-SP is only a working
listing, diagnostic and tracing information will be interspersed with the Source Program File card
images on the Audit File-SP.
Following is a list of the diagnostic messages to be printed in the Audit File-SP together with
their explanations:
Diagnostic Message

Explanation

NO UPDATE FUNCTION CARD

There is no control card
preceding the Current File-SF.
The Current File-SP contains a
DELETE card referencing a DDI-NC
not on the old Source Program File.
The cards in the Current File-SP
are not in sequence by DDI-NO.

RECORD TO BE DELETED NOT ON
OLD MASTER FILE
CURRENT FILE CA *DS ARE OUT OSEQUENCE

42

Following is a list of the trace messages to be printed on the Audit File-SP.
The following messages are all paragraph names and are printed upon entering the
paragraph:
1.
2.
3.
4.
5.
6.

IUC
UPDATE CONTROL
OLD MASTER FILE READOUT
END OF CURRENT FILE
END OF OLD MASTER FILE
END OF OLD MASTER FILE 4

The following typical trace message is printed whenever the WRITE-ERROR paragraph
is entered:
LAST CARD KEY
LAST CURRENT FILE KEY
LAST OLD MASTER FILE KEY

0002A005
0002A003
0005A004

The information opposite the LAST CARD KEY represents the control field (columns 73-80)
of the Current File-SP card read. The information opposite the LAST CURRENT FILE KEY
represents the control field of the next to last Current File-SP card read. The information
opposite LAST OLD MASTER FILE KEY represents the control field of the card image
in the last physical record read from the old Source Program File. This trace information
is printed on one line of the Audit File-SP.
4.3.3.2.3

Punch File-SP

Another option, the punch option, may be selected by the user to obtain a card deck
of all card images on the Source Program File containing information.
4.4
4.4.1

Initiate Population File Module (INIPOP)
Purposes and Uses

This module may be used to assign new test serial numbers, DDI-NO's on the Population
File. Renumbering the Population File might be required if the Test Modules were to be
reorganized and placed in a different sequence or if within the current organizational structure
of the Test Modules a new Test Module may not be assigned a convenient number relating it
to its associated Test Modules.
Whatever the reason, INI POP eliminates the necessity for re-keypunching the
Population File card deck by automatically reassigning new DDI-NO's. The user is
permitted to select the first new number to be assigned and an increment which will be
added to successive assigned numbers to form new numbers for assignment. All DDI-NO

43

references on the Test Header card (including all mandatory DDI-NO's) and JOVIAL
statement cards (including all mandatory DDI-NO references) will be updated to reflect
tl e new number assignments.
Input to I NIPOP consists of a Population File, in the form of a card deck or a magnetic
tcpe, and a control card requesting specific options provided by the module.
C utput from I Nl POP includes a renumbered Population File, the Audit-File-IP, that
contains diagnostic messages, an optional working listing on the Audit-File-IP consisting
o those Population File card images containing information, and an optional Punch File-IP
consisting of a card deck of all card images on the Population File containing information.
Population File modules recorded on cards may be renumbered in groups if desired. This
feature of I NIPOP is invoked on the card deck modules by placing control cards in the card
d :ck before each independent group of modules to be renumbered. Each of the card deck
modules following the control card will be renumbered according to the values given on
tre control card.
When invoking this feature on a Population File residing on tape, control cards designating
the various renumbering conventions must also contain the DDI-NO of the last test module
tc which the current control card applies.
When a portion of the Population File is to be renumbered, the entire Population File
slould be submitted to I NIPOP in order to ensure a correct resequencing of all embedded
DDI-NO references. For those modules of the Population File not requiring renumbering,
tie control card must include the information that the following modules are to be included
ir the renumbering process but are not to be themselves renumbered.
4 4.2

Preparation of Inputs

4 4.2.1

Card Inputs

4 4.2.1.1

Control Card-IP

The various options provided by INIPOP may be requested by means of the following
control card:
Columns

Name

Description

1

Control Card Indicator

2-4

Control Card
Identifier

44

This column must contain the
character C denoting the card
as a control card.
These 3 columns may be assigned
any 3 digits by the user to identify
the control card.

Colu mns

Name

Description

Renumber Option*

6-8

Card/Record

9-12

Initial Number

13-16

Increment

17

Print Option

18

Punch Option

19

Old Population
File Option

20-23

Record Maximum

24-80

Not Used

The column is used to indicate to
INI POP that a renumbering of the
Population File is required.
non-space - Renumber
space - Do not renumber
These 3 columns are used to
designate the number of card
images present in each record of
the Population File.
These 4 columns are used to
designate the first four digit
DDI-NO to be assigned.
These 4 columns are used to designate
the increment representing the
difference between two successively
assigned DDI-NO's.
This column may be used to request
the printing of the generated
Population File
non-space - Print
space - Do not print
This column may be used to request
the punching of the new Population
File
non-space - Punch
space - Do not punch
This column may be used to signify
that an old Population File residing
on magnetic tape will be used as
input.
non-space - Magnetic tape
input
space - Card input
These 4 columns are used to designate
the DDI-NO of the last record to be
incremented using the current initial
number and increment.

*lf renumbering is not selected, INI POP may be used to initiate a Population File from
a card deck or to copy an old Population File from one magnetic tape to the other. Print and
punch options still apply.

45

When submitting this card to INI POP, it precedes the Current File-PF if the Population File
is to be generated from a card deck or it replaces the Current File-PF if the Population File
is to be generated from an old Population File.
1.4.2.1.2

Other Card Inputs

A complete description of all other card forms contained in either the Population File
or the Current File-PF is given in Section 4.1 .2.
4.4.2.2

Input Files

he Initiate Population File Module operates on either of two input files, the Population
File or the Current File-PF.
-1.4.2.2.1

Population File

"he Population File has been completely described in Section 4.1 .2.4.1 .
4.4.2.2.2

Current File-PF

The Current File-PF has been completely described in Section 4.1 .2.4.2.
4.4.3

Function Operation

lhe Initiate Population File Module operates to initiate and, at the users option, renumber
a Population File from either a Current File-PF or from an existing Population File.
Additional features selectable from the control card include the options to print a working
listing of the generated Population File and/or to punch the resulting new Population File.
The Population File is renumbered by assigning to the first DDI-NO the value as stated
on the Control Card-IP for the Initial Number; to the second DDI-NO, the Initial
Value + Increment as stated on the Control Card-IP; the third DDI-NO, the Initial Value + 2
* Increment. For example, if the Initial Value was specified as 5 and the Increment was
specified as 10, then the values assigned to the DDI-NO for each Test Module would be
'>, 15, 25, etc., until the Test Modules had been exhausted.
•'-.4.4

Description of Expected Results

'•.4.4.1

Output Card Formats

The output card formats correspond to the formats for cards described in Section 4.1 .2.

46

4.4.4.2

Output Files

The Initiate Population File Module produces three files: The Population File, the
Audit File-IP, and the Punch File-IP.
4.4.4.2.1

Population File

The Population File is completely described in Section 4.1 .2.4.1 .
4.4.4.2.2

Audit File-IP

The Audit File-I P contains a listing of all diagnostics originating from the module. As
an optional feature, the user may request to print on the Audit File-IP, a working listing
of the card images on the new Population File by selecting the print option on the
Control Card-IP. Since the Audit File-IP is only a working listing, diagnostic information
will be interspersed with the Population File card images on the Audit File-IP. If no
diagnostics occur, however, the Audit File-IP will consist entirely of a listing of the
Population File.
Following is a list of the diagnostic messages to be printed in the Audit File-IP together
with their explanations:
Diagnostic Message

Explanation

UNEXPECTED EOF INFILE

There is an unexpected end of file
encountered on the unit contai ning
the control card and Current File-PF.
Successive incrementing of the
originally assigned Initial Number
have generated a number greater
than 9997. There are too many
Test Modules being renumbered given
the particular assigned values for
Initial Value and/or Increment.
Reduce either value or both and try
again.
The control card has not been submitted
to INI POP.

DDI-NO LARGER THAN 9997

NO CONTROL CARD

4.4.4.2.3

Punch File-IP

Another option, the punch option, may be selected by the user to obtain a card deck
of all card images on the Population File containing information.

47

4.5

JCVS Report Writer Module (JCVSRP)

4.5.1

Purposes and Uses

This module may be used to produce a finished listing of a Population File and/or a
listing of the Test Header Cards in a Population File.
Input to this module consists of a Population File and a control card specifying the options
available to the user.
Output from JCVSRP may include a listing of either the Population File or the collection
of Test Header Cards on the Population File or both. These reports are printed on the
Audit File-RP together with any diagnostics and trace messages originating from this module,
4.5.2

Preparation of Inputs

4.5.2.1

Card Inputs

4.5.2.1.1

Control Card-RP

The various options provided by JCVSRP may be requested by the following control card:
Columns

Name

1

Control Card
Indicator

2-3

Report Selection

4-13
14-19

Not Used
Date

Description
This column must contain the
character C denoting the card as
a control card.
These 2 columns are used to select
the two reports generated by ths
module.
Column 2: non-space - Population
File Listing
space - No Population
File Listing
Column 3: non-space - Cross Referencing Listing
space - No Cross Referencing Listing
These six columns specify the date
as follows:
14-15 Month
16-17 Day
18-19 Year
(Example: 040968)

48

Columns

Name

20-61

Test Identification

62-63

Control Tape Size

64-65

Line/Record

66-80

Not Used

4.5.2.2

Description
These 42 columns are used to
specify the computer name. The
name may be positioned any place
in the field.
These two columns are used to
specify the number of lines per
printer page that are available to
be printed on.
These two columns are used to
specify the number of cards per
record on the Population File.
In this case of JCVS this value
is 50.

Input Files

The JCVS Report Writer Module operates on one input file, the Population File.
4.5.2.2.1

Population File

The Population File has been completely described in Section 4.1 .2.4.1 .
4.5.3

Function Operation

The JCVS Report Writer Module operates on a Population File to produce two reports, a
listing of the Test Modules on the Population File and/or a listing of the Test Header Cards
on the Population File. The JCVSRP is directed by means of user options selected on the
Control Card-RP.
4.5.4

Description of Expected Results

The JCVSRP produces one file, the Audit File-RP.
4.5.4.1

Audit File-RP

The Audit File-RP may contain either a listing of all the Test Modules on a Population File
or a listing of all of the Test Header Cards on a Population File or both. This is a formal
listing in that no diagnostics or trace messages are interspersed. A trace message does,
however, precede the writing of each report on a separate page.
Following is the diagnostic message to be printed in the Audit File-RP together with its
explanation:

49

Diagnostic Message

Explanation

UNEXPECTED EOF INFILE

This problem results from
attempting to read the Control
Card-RP and getting an end of file
condition. Check input to make sure
the control card is present and is not
preceded by any extra end of file cards.

Following is the trace message that is printed out on a separate page at the beginning of the
writing of each report:
REPORT WRITER.

50

SECTION V
USAGE INSTRUCTION

Since the JCVS will operate on several different computers it would be advisable if the
user availed himself of the following documents:
1 .
2.
3.
5.1

Implementors COBOL Manual
Implementors Operating System Manual
Implementors JOVIAL J3 Manual

JCVS Operating Philosophy

Although the JCVS is to operate on various computers, the functions that will be
performed on each computer to utilize the JCVS will be identical. Each of the JCVS
program modules is processible by either of the following two methods:
1 .

Compile Source Program and Go
Using this technique, the appropriate control cards, source program
and data are submitted to the computer system. The system then compiles
the source program and writes the resulting object program on the
operating system's Load and Go unit. This object program is then loaded
from the Load and Go unit and progron executing follows.

2.

Load Binary Deck and Go
Using this technique, the appropriate control cards, object program
binary deck, and data is submitted to the computer system. The system
then loads the object program from the object program binary deck and
program execution follows.

5.2

JCVS Function

There are seven functions that are available to the user of the JCVS.
in the following list:
1 .
2.
3.
4.
5.

Create a new Population File
Update an old Population File
Generate a JOVIAL source program
Update a Source Program File
Initiate a Population File from a
Population File card deck

51

POPFM1
POPFM2
SELECT
SOPMM
INIPOP1

They are given

6.
7.
5.3
5.3.1

Initiate a new Population File from
an old Population File on magnetic tape
Write reports from Population File

INIPOP2
JCVSRP

Preparation of JCVS Input
Current File-PF

The Current File-PF which is used to update the Population File has been described in
Section 4.1.2.4.2. An example of this file is given in Figures 5-la, 5-1 b, and 5-1 c.
Notice all packets are in order by DDI-NO and that there are no DELETE packets.
5.3.2

Current File-SP

The Current File-SP which is used to update the Source Program File has been described in
Section 4.3.1 .2.2. An example of this file is given in Figure 5-2.
Notice that all of the cards in this file are in order by sequence number, columns 78-80
within DDI-NO, columns 73-76.
''.3.3

Test Selection File

The Test Selection File which directs the selection of the appropriate test modules has been
described in Section 4.2.2.2.2. An example of this file is given in Figure 5-3.
This particular set of Test Selector Cards select the following test modules.
example, it is assumed that no Mandatory DDI-NO's are involved.
f .4

In this

Functional Processing

Diagrams will be proficed describing the status of the computer system at input time
and again at output time for each function performed by the JCVS modules applying
each operating philosophy and on each computer.
A complete list of these diagrams is given in Appendix 1 .
5.5

Results of Operations

The JCVS modules generate magnetic tape output, printer listings and punched decks.
The files associated with this output have already been completely described previously
in this document. Actual samples of computer generated output will now be presented.
5.5.1

Printed Output

52

T^ST MPPI'LF
TF5T MOO I F.
ST MOPULF NAMF
TFST MODULE
Tr.sT MODULF
TFST MpnULF
TFST MODULE
TFST MODULF
TFST MODULE
TFST ^00\ iLF
TFSr MODULF
TTST MODULE
TFST MODULF
TrST MODULE
TFST MODULF
TFST MODULE
jtrc,j
TP^T

vOP!!Lr
WPHI 'L F

TEST
TrST
TFST
TFST
rrsT
TFST
TFST
TrST
TFST
TFST

MOPULE

Trr,T

Mpni '| r

MpnuLF
MOPULF
MOPULF
MODULE
MODULE
MOpULF
MOPULF
MOP! Mr
Mpn(i[ F

TF^T MOF: 'I F
TFST MPO'SLF
TFST Mpoi'LF
TFST MOPi'LF
TFST MPPULE
TFST MOPI'LF
TFST MODULE
TFST MOPULF
T^ST MODULE
TFST MOPULF
TFST MoniiLF
Tr.sT MOPIILF
TFST MOP! iLF
TF^T MODULF
TFST MOPIILT
T^ST MOPULF
TFST MPPULT
TFST MOPULF
T FST MOPULF
TFST MOPI'I r
TFST Monni.F
TFST Monin F
TFST MODHl r
TFST MOPULF
TFST MOPULF
TFST MOPULE
ST MOPULF NAMF

0^02 JOVIAL STATEMENT
oo^g JOVIAL STATEMENT
10 2427 242 8 242^
on
JOVIAL STATFMFNT
nn
JOVIAL STATFMFNT
nn
JOVIAL STATFMFKJT
00 0 JOVIAL 5TATEMFMT
M
0
JOVIAL STAT^r-TNT
on
JOVIAL STATFMTNT
no
JOVIAL STATFMFNT
oo
JOVIAL STATFMFNT
oo
JOVIAL STATFMFNT
oo
JOVIAL STATcMrNT
or
JOVIAL STATTMENT
00
JOVIAL STATFMFNT
nn
JOVIAL STATFMFNT
JOVIAL STATi-^r^T
r
JOVIAL 5. T A T M r N T
oo
JOVIAL STATFMFNT
en
JOVIAL STATFMFNT
on
JOVIAL STATEMENT
on
JOVIAL STATFMFNT
oo
JOVIAL STATFMFNT
00
JOVIAL STATFMFNT
00
JOVIAL STATFMFNT
00
JOVIAL STATFVTMT
nn
JOVIAL STATFMTNJT
nn
JOVIAL 5TATrMf-MT
M
or
JOVIAL STATF TNT
nn
JOVIAL STATFMTMJ
00
JOVIAL STATFMFNT
nn
JOVIAL STATFMFNT
rn
JOVIAL STATFMTNT
00
JOVIAL STATTM^NT
CO
JOVIAL STATFMFNT
00
JOVIAL STATFMFNT
00
JOVIAL STATFMFNT
oo
JOVIAL STATFMFNT
00
JOVIAL STATFMFNT
oo
JOVIAL STATEMENT
oo p JOVIAL STATEMTNT
or n JOVIAL STATFMFNT
ro r JOVIAL STATFMFNT
nn r JOVIAL STATTMFNT
00 0 JOVIAL STATFMFNT
on o JOVIAL STATFMFNT
On 0 JOVIAL STATFMFNT
on 0 JOVIAL STATFMFNT
op o JOVIAL STATFMFNT
on o JOVIAL STATFMFNT
00 0 JOVIAL STATFMFNT
OO P JOVIAL STATTMFNr
in 1 JOVIAL STATFMFNT
00 2 JOVIAL STATFMFNT
nn 3 JOVIAL STATFMTNT
14 2437
Figure 5-la

of 3
ObO

APP
APP

0if•• 2 jr 0,-

CARP
CARP

nnn'yj"', (
1 1

001

nr2
003
004
005
0 06

On] oj or

nn 1 r J o i 0
n,n
JO] 1

no ir J 0

53

i ?

nn
on

JO\--

^n
nn

r.JO 1'

J'• 11.

OO O J - 1 7
nn

oj " 1 t.

OJr jr,
0J02F
nn oj-2 ;
nn

nn

nn

n

no

oJ" 2 •

Jn22

00 OJ" 2/(
nn 0JO2*'
nr ojo26
nn ojo27
nn njnp «

nr 0J~29
nn

0J o 3 o

nn OJ" il
"0 0JOJ2
0^ 0 J 0 j 3
OO 0JPJ4
nn PJ035
0 0 OJ^ 36
On 0J037
0 o 1 ^JO'lR
o
pJA:>9
n 0 ] OJ^ZjO
o 01 '-jo/, 1
0 o I nj 0 4 3
00 1 0J044
noinjo4'j
0010JO46

On]0J047
0 010J"4H
Oo]0J^49
OP ] o j r • <, n

PEPLACT A CAPI)
^TPLACF A CA^P
DELETE MODULF 13
1 •

Current File-PF

'•

0010
r\ r\ ~t
0010J
^^ 1 OJ nn >•
On i 0 J - CM,

no 7
008
009
010
Oil
012
013
014
01 5
016
0]7
01 R
oi9
02 0
021
"22
023
o24
02 5
^26
n
27
028
029
030
031
032
033
034
035
036
037
038
039
040
041
042
043
044
04 5
046
047
04 8
04 9
015
004

0010 i 01
no] oj r r p
o o 10 J n n '.
0 o 1 0 J -04

nn ] ljr|'OO 1 2J.'W,
0 O ] 3 r. o o 0

0O14AOO]

TEST MODULE
TF5T MODULE
TEST MODULE
TEST MODULE
TEST MOD JLE
TCST MODI ILF
TFST MOD' ir
TFST MODULF
TEST MOD JLE
TEST MODULF
TEST MODULE
TFST MOD1 ILF
TEST MODULE
TEST MODULE
TEST MODJLE
TEST MODULE
TEST MODULF
TFST MOFiULF
TFST MODULE
TEST MODULE
TEST MODULE
TPM MODI'I F
TEST MODULF
TFST MODULE
TEST MODULE
TFST MODULE
TEST MODULE
TFST MODULF
TFST MODULE
TFST MOnuLF
MODI LF NAME
TFST MODULF
TFST MODI LE
TEST MODULF
TFST MODULE
TEST MODULE
TFST MODULE
TEST MODULE
TEST MODULE
TEST MODULE
TEST MODULE
TFST MODULE
TFST MODULF
TFST MODULE
TFST MODULE
TEST MODULF
TFST MODULE
TEST MODULE
TEST MODULE
TEST MODULE
TEST MODULE
TEST MODULE
TFS"1 MODULF
TFST MODULF
TFST MODULF
TFST MODULE

0014 JOVIAL
0014 JOVIAL
0014 JOVIAL
0014 JOVIAL
CO14 JOVIAL
C014 JOVIAL
0014 JOVIAL
0014 JOVIAL
0014 JOVIAL
0014 JOVIAL
0014 JOVIAL
0014 JOVIAL
0014 JOVIAL
0014 JOVIAL
0014 JOVIAL
0014 JOVIAL
0014 JOVIAL
O014 JOVIAL
0014 JOVIAL
00 14 JOVIAL
0014 JOVIAL
<~014 JOVIAL
00]4 JOVIAL
0014 JOVIAL
0014 JOVIAL
0015 JOVIAL
0C16 JOVIAL
0017 JOVIAL
0017 JOVIAL
OOiR JOVIAL
19 2445
0019 JOVIAL
!^019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0019 JOVIAL
0021 JOVIAL

STATEMENT
STATEMFNT
STATEMENT
STATEMENT
STATFMFNT

001
003
005

STATFMCMJ

on

O0 14JC0 2
nnl4J0n4
00 14JC06
0014JO08
Onl4Jflp
^n14J' 1 ?
0^14Jr J u
0014J0 16
0M4J"18

007
009

STATFMFNT
STATFMFNT
STATEMFNT
STATFMFNT
STATEMFNT
STATEMFNT
STATEMFNT
STATEMENT
STATEMENT
STATEMENT
STATEMENT
STATFMFNT
STATFMFNT
STATEMFNT
STATEMFNT
STATrMrMT
STATFMrNT
STATFMFNT
STATEMFNT
STATEMENT
STATEMFNT
STATEMFNT
STATEMFNT

013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
003
020
006
021
STATFMPMT 007

0 0 14 J 0 2 n
0014J;122
0 0 14 J ( 124
0^ L4J026
0014J028
0014J030
0014JC32
00 14JO 34

1

0M4J036
0014JT38
0014JC^O
0014J042
nr>l4J0 44
o0 1 4J046
O014JO48

DELETE A CARD
REPLACE A CARD
ADD A CARD
REPLACE A CARD
ADD A CAPD
0016»•

002
004
006
008
010
012
014
016
018
020
022
024
026
028
030
032
034
036
038
040
042
STATFMCNT 044
STATEMFNT 046
STATEMFNT 048
STATEMENT

STATFMFNT
STATFMFNT
STATFMFNT
STATEMENT
STATEMENT
STATEMENT
STATEMENT
STATEMENT
STATFMFNT
STATEMFNT
STATFMFNT
STATFMFNT
STATEMENT
STATEMFNT
STATFMFNT
STATFMFNT
STATEMFNT
STATEMFNT
STATEMFNT
STATEMENT
STATEMFNT

Figure 5-1 b

Current File-PF
54

0014J05 0
0O15DO03
0016J020
00]7J( 06
0017JO21
OOlRJf'07
0O19A001
0j
n
o ? 1J r ] r>

0^21 JO?*r>2 i jo«, n
n

^?2r^i?
o2 3 Dnr 7

n

i"> O 2 A D 0 2 (•>

0025^000

TFST
TTST
TFST
TFST
TFST
TFST
TFST
TFST
TFST
TFST
TFST
TFST

MODULF
MODULF
WCDULF
MODULE
MODULE
MODULE
MODULF
MCDULF
MODULE
MODULE
MODULF
MODULF

00 03
0003
00^8
0008
0009
0011
0012
0013
0024
0024
0024
0O?5

JOVIAL
JOVIAL
JOVIAL
JOVIAL
JOVIAL
JOVIAL
JOVIAL
JOVIAL
JOVIAL
JOVIAL
JOVIAL
JOVIAL

STATFVFNT
STATFMFM
STATEMENT
STATEMENT
STATEMENT
STATEMENT
STATEMENT
STATEMENT
STATEMENT
STATFMENT
STATEMrNT
STATEMENT

Figure 5-2

0P<*

005
024
036
02 0

017
031
021
020
025
050
017

A!">D A CARD
DELrTE A CARD
DELETE A CAPD
PEPLACE A CAPD
ADD A CARL
REPLACE A CARD
ADD A CARD
REPLACE A CARD
DFLETE A CARD
ADD A CARD
PEPLACE A CApD
DFLFTE A CAPD

Current File-SP
56

r\oo3j^p/(

r*rp3r?P5
PP08P^'4
0*08J03 6
0OP9JC*0
0011JCI7
0O12J0 :-l
PO 13 JO'l
pnJA'0^
»

Q.
O

IT

o
UJ

I

»-

o

or
r>
o.

o
o

-3I

o

KD

LU

a

Q
O

<->

o

©

u.

V

»-

I

o
o
UJ

»—
3

a
•-

s
t

O)

^

-\

•>

-^

.,~\

• i

en

o
I

o
o
o
ir\  o> o
<4rl t(HHN
3 « > O O O

(MI>1* IT -O
m flu CM  >C P» «D
WKIBIOK)

o -rt OJ K5 •»

«o r^ oo o> o

OOOOO

OOOOO

UJ

T

:£:

ooooo
CD O O O CD

l

a_.

OOOC>00000<>000000000
OOOpOOOOOOOOOOO«>000

~n
-,

ooooooooooooooooooo * —
•«-»-»-»-»-»-> ~»-»-r»-» ~>-»->-> T» ~»-»-> u-

i\a\»\r>«\v\iNrt^irir>«M\ir\irMnMMr\tftir>m«Mrvirtit n Ml «r> «f> ir\
I ۥ<
Ol>00000l>000

n
H(M»eoo(MT
• oooooOooooo

UJ

I- ui- •- I- l- »- »'Z3TZZZZZ
1 UJ UI Ul UJi ui ui UJ Ui ui Ui ui

•u

CEtXtXtXtX

lUJUJUJUJUJUJUJUJUJUJUJ

i an cn

zzzzzzzzzzzzzzzzzz

UiUiUJUJUJUJUiUiUJUJUiUJUJUJUJUJUiUI
IXTXXXXXXXXTXIXXXI
UlUJUlUJUJUJUJUIUJUJUjJJUJUjaJLJJIlJdJ
»-»-H-U-»-l-l-»-N-»-»-t-l-»-H-»-t-l-

J D- 7
jUJ
i
i

er
3

I
a> j> >• > a> i
OOOOO

m
<

•g •> as n w> m m

h-»-i(-»-h-t-ij-»-»-»-»-»-t-i-i»-i-i-ijc\j «r>  •> *> an •> in tn «n «n •> *> n m ff> a> •) HniJMlOriKll(MN»,(r'jK\
OOOOOHriHXNIMNNNIUnnn
oooooooopoooooOooo
I

_I_I^J_I_I_I_I_I^J_I_J_I_I_J-J_I_I_I

— — .»- — —
»..
.
. -. ~
>•>•>>•>•>•>•»>»>>•>•>>•>•>»

«HOOpOGOOOOOOOOOOOOO

'r->->T>->->->->->T>->T->->-r>->->->
irvuM|\irtifiir\irtinir>i

O i> O <
• a o o o i
muuiiuui
J i -J _• _i
33 3 3 5 3
i a o j o Q o
i3 O O O O O
IE * r x X x

• • o «e m an
mill ummui

o o <
o o '

'

«M

I
'
I
I
i

-o
*"*
O
O

© o o o o o ! CD
I p o © o o o
—J

uj UJ ui ui ui
_l -J) -I J _l -J _l
3 3 3333333
Q O Q O O Cl O Q O
o o 0 o o o o o o
UJ UJ

_I

1 ITtXtl © >or UJ
•-se

•> •» •» SMiaaictowcancninninwtaeincnnincniniaincncaao z
ui in in
UJUJUJUJUJUJUJUJUJUJUJUJUJUJUJLJUUJUJUJUJUJUJUJ11JUJ OO

60

OCX
41
KIU
»•« Io w

* -

3 -J

Hrt*-t-»-»-»-»-»-»-»-»-»-»-»«-i-i-i-

o«nena>in«a
OUJUJUJUJUJUJIlJUJIAiUJUJUJUJUJUJUJUJUJ
xl-U-»-»-»-»-l-l-«-»-»-»-»-l-l-»-l-l»l/l
111
•-

•

•

!

•»

CM »- OH- O -1 w I
O O OO O Old I

I

M • *l

X X X X X!=>

61

I

I

!

I

!

I

I
i

-o

I
LU

o
I

 OO O

OOOOOOOOOOOOOOOOOOOOOOOOO

O

<
Q

ED

>Oi<

«M

O O O O »4
ooooooooooooi

IHMHa Mi— U»IM III'

-t-l-»->-H-l-l-H->.|-hH-l-l-K

XXXXiXXXX

wxxxxxxxxxxxx'xxxxxxxxxxxx

-'•
W1

ooooo o oo oo oo 0000000000

o

» > > »•

>•!» >

»

» » »:>• »»»>•»

o ooo oo o oo o oo o oooo oo o o o o o

' o ooooooooooo

o oo ooooepooo
ooooooooo ooo

OOOOO'OOOOO O O OOOO O O o o o o o
ooooooooooooooooooooooo
ooooooooooo oooooooooooo

UI UI UI Ui UI UJ Ui UI1 UlUtUIUIUIUIUIUIUiultillllUIUI

UI UI UI UI UI UI UI LU UIUIUIUIUJUJUIUIUIUIUIUJUIUI UI ill UI

oooooo

33 33 3313 33 3
* O O O 0000001000000 oooooooooo
ooo ooo ooo oooo oo oooooooooo
X X X X
X X X X X XX XXX
Oj Win »

*4

in at

LO WMW

wnnn in m m in in m

in

33333333333333333333333
OOOOOOOOOOOOOOOOOOOOOOCli
OOOOOOOOOOOOOOOOOOOOO OOl

xxxxxxxxxxxxxxxxxxxxx xx:

omwioMww«)«)u>
o IM MM• M MM mm m ui in • M in m •nui M ui ai m m

:

r

^2

o

I

I

!

I

I

!

i

!

n

i

I

CM •* •©

oooooooooooooooooooo odooooo

rt »o w •
TflTlOOOOOOOOO'"*--*'-'*-'
o o o o o a o Oooooooooo*

HHrlHHr)HHH^H(MOOC3CDOOOOOCDO*=>OCDOOOOOC300

OOOOOOOOOOOC^OOOOOOOOOO
00000000000000000c>0000

UJ

a.
i in r- UJ
>r •» or

2 Z
1 UJ M

rli
o i

Z
s> UJ

r x

IUIOI

oooooooooo

m i
» 111



CO (A (n in n ij) in i/> n

•- •- O CM *~
« < tt\
-»
»- k- O
•-

l/> M

n«m4>N^»OHiv
00OO0CJ>0«Hr-l«-l

•- fr-«

•<
ID

_I -I -J_l_l_ll_l_l_»_l
-c-«-4«-«iujr\j-«-«-«-«

> » UJ

>

-> ~> •* in

->-!-»-»

O O t- rs. o
*4 anin
CM CM
CM

e o _i in e

BOv\
CM CM CMCMCMCMCMCMCMCM
o o oooooooo
oooooooo

UJUI>UJUJLJUJUJUIUJUJUJUJUJUJUJ
_l JO X _l

o r> -» •« o

o e
711
o o •*
o
X X CM UJ X

3333>33r>z3
o a oootbaooo
o o ooocpoooo
x x xxxxxxxx

»- »- o 3 »v> u>
a c/>
UJ UJ UJ O UJ

UJ UJ UJUJUJUJUJUJUJUJ

a iO (/)
X UJ

in win ui in in ui o)

lO
CO
I
LU

o
r • B\ « ri O O O r->

r- to o> «>
O «« i-l •* W

od o© o
O O © O ©
© o a oi >
o o © o 

I O CD O I

Hnin«(\«r>eg>e>H«nvii>«Ki)»or4(Mn^ir«Nao>
(MfO»»
oooooooooooliooooob

OOCD©OOOOOCpOOOI O 1

rll<)>\

o> o

O

1

o- •H fO Q_
o «r* •H
1
C» «1
OJ

—

© © oa CJ

«> o o o © <0©0©OOCDCj>OOCDC>0.©

rl

w

W •H aH a-t

© © o ©o O

IOO0I
© o e> ©© <
6oeooo«o«ovopoootteeo«ei>oeo«oiiooooof ooooo*

o o

O

o

O

o

«-* u_

CJ
O

'"C
D

Ul

<

-»

2 •

o •

;

^
»-«

-1
3

O O O O CD
OOOOD

r I ^ Z r
Ul W HI W HI
HI Ul Ul Ui Cli
43

•*•«-••«•«

o << Nil »• »> o r. i
o o
CD © CD © €D
ioco<
JE * JT * Z
Ul 111 Ul UI HI

XJfcirixUJ Ul 111 Ui Ul

hlh if I-

Ui Ul Ui UU UJ

ritit

r. « O. o •<
CM CM CM fO m nonnnioioi
i>oo©©o©©©o©o © o I • O CD O © O O O © o ©

3
Q
O

111 in UJ uiujuiuiuiuiuiuiiii ui ujuiuiuiiiiuiujuiuiuiujiuiuiuauiuiui
iirirtriiirtrrmlrnri:* rrrirz

Or
O
t~

I CM CM CM CU CM

9oeoit>o

Ul Ul Ul Ul UJ
»- If »- •- §- .

UJUlUJUJUJUJUJUJUlUIUIUIUJUJUJUJUIUJUIUJUJUJIIJUJUIUIUlUJUIltl
•-H-I— H-»-H-»-»-»-»-»->Jfl>-l— •- I— I— »-»-l-»-l>-l-»fl— l-l-l—»-H-

00

i

>-

a>
c
i

(M» «eow
O O © © •-• <-<
© o © tz> o o

Z Z Z 2 Z Z

HI Ui HI Ui Ul M
J » » I I J
Ul Ul Ul UJ Ul UJ

-«-*-<••«"«-*

»- •- If »- *- «-

»-»»»-»*l-H-»-»-»-»-l-i)-»-»-»-»-l-H-l(-l-»-»-l(-H-»-»-»-»-»-»^

•••••>*>•>••

III1

•««a9*n«!«>«)*)
X CM

J-IJJJ-IJ-IJJJJ^IJJJJJJJJJJJ^JJJJJJ

ii

3»»»»»>:»»>»>'»3»>5f»»»»»»>'3f»3f»»»»»»>»»»>»»»»»»»»>'»»»>
©©ooooooo
© O O CJ
i O O I
© O O O €3 O O
l->^ •

oooooooocsooooocboorioooooooo

c\iiikmi«\u\toijn«kri«\ijAaSijAiiif%tf\ij>i*viij|>ijni4\ijn

nofionon
CM -> -> ~>~> ->->

ilvf«tHMHilvl«Tl^fltlvlrfT4«lvlJlTl«lvl«l*1fH«IH«4HI1H«IHHHf*l«4HdriMT4HTlfiHv<
nciooooocioooocKioooooooeooooooooooooooovoooooooooooO
*<0©©0©©00©0©000©0©OcboOO©OcpO©0©0©©©0©©©©©0©0©00©©©©

o o © o o o
ooooooo
O © O © CD © O

aj*uiuiuJUjujLCuiHjuiujujt»iuiaJUJUitumLyu]ttiui
J_I_I-J-J_J_J-»_J_U-J_J_»_J_I.
<:ID333D:)D

Ul UJ UJ UJ UJ UJ UJ
X _1 _l_l_l _l -I
••333333
Z Q O O O O, Q
O © © O O ©

ittjnujiijitiujujujaituiiiuiujujuiujujujujujujuji

'33333333
5353:i33333333353: 133 3 33333333333:
ziiaaaoaiiaoaaaciooaaatsaooiaocaaaoaaooaoaomaaaaaoaaaooo
?ocococcooooeooooooocc)Ooc
oo«>oc>oi>oc>oeoa)oo
i © r
:5rxixjfcjr3)t:rxjrjfcj)r

Diia*
OH I Hi

HI

HI |1|
UI mi
I
in
I m Ml

MI

SSS!

zxxiztiiiixxzrxxxir-

• •••••••••^••••nMiiiiaanti •ininBiaiiiiniAinww
||| "i
HI '*•
ntln
in ill
\m HI
tit "'
HI i|i
DM in ' i IB Ul
I*I in
ttj tit
'" m
*" HI
111 tli
Ml m
Ul HI
Ul HI
Ul m
Ul HI
HI ifri
III ^|i
^l1 m
'I1 Ul
'I1 ill
Ul HI '*'
I Ul "* "' Ul Ul 141 Ul

64

1
u~>

mirtiTt

DH«««WH
O Ul Ul UJ UJ UJ Ul

->
a

~4 CW
O O

-* tr\ o r- (Ti
O O CT O O

ooooo

O.H(\JKl» US>OMI)(>Orl  K>

ooooo

*•»->">->->

io irv m \rs \c\

o o oo o

OOOOOOOOOOO
OOOOOQOOOOO

O O O O O

ooo oo

-wiro'-vOo,_«r\jK']'wijfN,or- 
00000<£OOOOOC»00000

UN m U\ UN ifi

tf\tf\u>tf\ir\u?ktf\if\inirvir>wKu>tnmir\tf\

O O O CD O

OOOOOCDOOOOOOOOOOO
OOOOOOOOOOOOOOOOO

oo o oo

Q.
I

<
o
O

41
t-o
Ik. —
or
* *•
ou

A
1>
<>
«r«

oooo
O4>00

•-UI Cb
•
< -f
« UJ

t> O ,-*
to O r- <> o o
* *o -o
OOOO O «H H »-t *H *« vH «H «-t *•( *-t cw <\j
ooo e> o o
ooo

: 7 z z a

IUIUIUI

-i
3 _i 
in <4> N«ODH«MtO'OH
tv rvi ru ru m
o o o r~> CO oonooftnnoocionoo

> C» CD CD

—

z z z z
z z z z
ui
UlUIUIUIUlUlUJUIUIUIUlUlUIUIUJUIUIUlUl Ul IU Ul Ul
X z z z z zzzxzZzzzzzzzzrzzzz Z I I 1
ui ui ui ui ui UlUIUIUIUItilUlUIUIUIUIUIUIUJUIUIUIUIUI Ul Ul Ul Ul

—

Ul Ul Ul Ul Ul

a*

Ul Ul Ul LJU Ul Ul UJ Ul Ul UIUI

inKin»wi»ini>jin0u)onnii)((i»(flii)(
U>  M U»
C* VI

I- IJ -i» -J> j

I* VI l/l v> in V) Ul (!) (/icoiflcouDcoiootocoofooocooin
-l_lj_lj_lj*j

> 3> 3> 5> »

o o o oo

• >•>•>•

:• 3> >•

i

i

»

D> D> »

i

I

J

i

i

•

i

i

t

i

i

i

i

i

w

i o o o c> o o OOO Q O ooo ooooooooc->o"ooo

-> ~» "»

-»->->-> "p -> "»

mm m n in •fkmmmmmmiiNiin>un lii

T* ri -r* <-# .-I
• O O CD
> O O O

3

ooo (boo <
I O O CD C> O O I

mininiMn I*
I ^H •
i
O O O ( > a> OOOOOC^OC^OOOi
i
>oo O CD O I i Ct> COCiO^OO'OCDO-O^OO

I

lUIUtUlUlUJUIUIUIUlUlUIUIUIUI
I Ul Ul
I_J_I-1J_I_IJJ
_l -I -J -I _l -I _l

ooociooaaocicioor-. en
IOOOOOOOOOOOOOOO
ZZZ3#ZXZZZJ:TZZXZ

3 Z> 3
OOO
OOO
Z X z

ivni)v>f»utvbu>Lu»uivnooiv>uiu>u>v> (/>i/>U)<
IIAIIJIIMMIUiUIUIIllUIUIUIIAIMIUpilll/JUIUJUIlJIUIUIUJUIUIkJIUJUl uiuiuiiiuiiuuimi

UJ

65

c

c

c

05

>o r~ <*> o

ru ro

o

o

lUJIUUJUJLlllUUflULLiUJ
IJJ_I_I_J_J-I_I-I_J
lOOQOQOCkOOO
IOOOOOOOOOO

IC/lCAt/IIAt/tUpVltjAl/lCAl/)
I Ul Ul Ul Ul UJ (Jl Ul 111 Ul UJ Ul

f\£'

f I CM t>) I
c> o ci <
Cl O Cl I
IIOCII

O O Cl o

a:

mm
-*«
mo
•«
•- u m
LUtr 0
zu
III ui o
_i ei
Ul-I
i/>2
OUJ
acts
u

o

r

Q
Ul
u

;
I
I

o
z
i
a

» CM
o w

•O »llf>
CM K» M

«o w

l

u
a

1

!

CM

I

ei

« m r.
ic\ Ji
in
«« r>
wra
•w*
CM CM ncMrtioK»iO'*'»^»in«\iniri • i
I* 1
CM

CM

m c« CICMriCMCllCMCVCMCUCMCMCMCaCM

riHnniti

O O O I

ul
X.

-O • I
cr\ u

•« i • •«
CM Ct CM ! CM

in m ai i

-

Zz

Ul

3
a
o
*

o
t
o
x

X x X x 3:
•*•«<•«••

?f

z z Z z
I UlLUUlUlUlLtlUlUILU
i* Ul
ui ui
jl-IJI J JJ J J Jl
o i OOOOOCIOOOCI
O I OOOOOOOOOCI
x^xixixjEx
*-ci-f—»f»-iJ-»-H»-»c/>tAt/>u>c/)U>(/>bt>cni>
cuciiicifiiajUiuiMiuiU)

(A «/) b i  to to
141 u 11 ai ui ui

a

~ 1'

><>oO>oe><>oc>ooo
oorteDooooclioooooc.

C

66
I

j

i
f~\

r~\

c

o

.

J

5.5.2.1

Punch File-PF

The Punch File-PF, a card deck which contains the created or updated Population File,
is identical in appearance to the Audit File-PF with the exception that there are no trace
or diagnostic messages or blank cards. Only cards with information content are punched
by POPFM.
5.5.2.2

Punch File-S

The Punch File-S, a card deck which contains the generated JOVIAL source program, is
identical in appearance to the Audit File-S with the exception that there are no trace or
diagnostic messages or blank cards. Only cards with information content are punched by SJCVS.
5.5.2.3

Punch File-SP

The Punch File-SP, a card deck which contains the updated JOVIAL source program,
is identical in appearance to the Audit File-SP with the exception that there are no
trace or diagnostic messages or blank cards. Only cards with information content are
punched by SOPMM.
5.5.2.4

Punch File-IP

The Punch File-IP, a card deck which contains the resequenced Population File, is
identical in appearance to the Audit File-IP with the exception that there are no
trace or diagnostic messages or blank cards. Only cards with information content are
punched by INI POP.
5.5.3

Magnetic Tape Output

5.5.3.1

Population File

A Population File is always generated by either of two programming modules, INI POP and
POPFM. The Population File is recorded on magnetic tape for subsequent processing.
5.5.3.2

Source Program File

A Source Program File is always generated by SJCVS. This file contains the generated
JOVIAL test program and is submitted directly to the operating system for compilation
and execution.

67

TABLE OF CONTENTS
for
APPENDIX 1

fage
CDC-6400
POPFM1
Compile Source Program and Go
Load Binary Program and Go

73
75

Compile Source Program and Go
Load Binary Program and Go

11
79

Compile Source Program and Go
Load Binary Program and Go

81
83

Compile Source Program and Go
Load Binary Program and Go

85
87

Compile Source Program and Go
Load Binary Program and Go

89
91

Compile Source Program and Go
Load Binary Program and Go

93
95

Compile Source Program and Go
Load Binary Program and Go

97
99

Compile Source Program and Go
Load Binary Program and Go

101
103

Compile Source Program and Go
Load Binary Program and Go

105
107

Compile Source Program and Go
Load Binary Program and Go

109
111

Compile Source Program and Go
Load Binary Program and Go

113
115

POPFM2

SELECT

SOPMM

JCVSRP

INI POP!

INIPOP2

UNIVAC-1108
POPFM1

POPFM2

SELECT

SOPMM

68

Table of Contents for Appendix 1 (Continued)
Page
JCVSRP
Compile Source Program and Go
Load Binary Program and Go

117
119

Compile Source Program and Go
Load Binary Program and Go

121
123

Compile Source Program and Go
Load Binary Program and Go

125
127

Compile Source Program and Go
Load Binary Program and Go

129
131

Compile Source Program and Go
Load Binary Program and Go

133
135

Compile Source Program and Go
Load Binary Program and Go

137
139

Compile Source Program and Go
Load Binary Program and Go

141
143

Compile Source Program and Go
Load Binary Program and Go

145
147

Compile Source Program and Go
Load Binary Program and Go

149
151

Compile Source Program and Go
Load Binary Program and Go

153
155

Compile Source Program and Go

157

Compile Source Program and Go

159

Compile Source Program and Go

161

INIPOP1

INIPOP2

GE-635
POPFM1

POPFM2

SELECT

SOPMM

JCVSRP

INIPOP1

INIPOP2

IBM 360-50
POPFM1
POPFM2
SELECT

69

Table of Contents for Appendix 1 (Continued)
Page
SOPMM
Compile Source Program and Go

163

Compile Source Program and Go

165

Compile Source Program and Go

167

Compile Source Program and Go

169

JCVSRP
INIPOP1
INIPOP2

70

APPENDIX

1

USAGE INSTRUCTIONS

Appendix 1 describes on the following pages usage instructions for each function on each
computer. Usage instructions depict the status of the hardware configuration before the
run (INPUT) and after the run (OUTPUT). All input/output considerations are fully
described for both the INPUT stage and the OUTPUT stage. In addition, the exact form
of an input card deck necessary to invoke the function is provided.
Each JCVS Usage Form contains the JCVS function to be performed, the computer, the
operating philosophy and the program stage. All input/output functions and devices are
specified over the six boxes on each form. On the top of each of these boxes is the logical
system name associated with the input/output device.
For example, on the 6400 the logical tape designations are TAPE! , TAPE2, and TAPE3;
the logical card input designation is INPUT, etc.
For those input/output units that are to be active for the current function, some indication
of their participation is indicated. For those tape units that are to contain a switch tape
for the subsequent processing, the word SCRATCH is placed at the bottom of the appropriate
box; for those tape units that are to contain a JCVS input or output file, the file-name is
placed in the bottom of the box; and for those tape units whose participation is not
required, a N/A (not applicable) is placed at the bottom of the box.
In all cases, a job deck will be submitted through the card input unit which should be
empty at the termination of the run. The printed output unit will always contain a
standard form and standard carriage control tape and will contain the various audit files
at the termination of a run. The card output unit will contain any punched output
originating from any of the runs.
A complete description of the job deck structure required to process the function is
given on each INPUT stage usage form. The (1) below the words JOB DECK STRUCTURE
indicates column 1 of each card.
Logical Unit Names
The logical unit names for each computer will now be stated:

71

""-""-Configurati on CDC-6400
Units
-«u^^

UNI-1108

GE-635

IBM 360-50

Card Input

INPUT

Card Reader Eighty

A1

SYS001

Card Output

PUNCH

Card Punch Eighty

A5

SYS003

Printed Output

OUTPUT

Printer

A2

SYS002

Tape Number 1

TAPE1

UNI SERVO A

A3

SYS004

Tape Number 2

TAPE2

UNI SERVO B

A4

SYS005

Tape Number 3

TAPE3

UNISERVOC

A6

SYS007

Special Cards
Certain configurations contain one or two special cards that act as end of record or
end of file cards. The following table gives a list of these cards together with the
characters that signify the EOR or EOF functions.
"Confiauration
End

CDC-6400

UNI-1108

EOR

7,8,9 punch
Column 1

No Entry

EOF

6,7,8,9 punch
Column 1

@bFIN
Column 1 -5

72

GE-635
$bbbbbbENDJOB
*** EOF

IBM 360-50
No Entry

JCVS USAGE FORM
Function:

POPFM 1

Computer:

CDC - 6400

Operating Philosophy: Compile Source Program and Go
Stage:

INPUT
TAPES
TAPE 1

TAPE 2

TAPE 3

\^ i
SCRATCH"'

CARD INPUT
INPUT

PRINTED OUTPUT
OUTPUT
""]
| Standard
| Standard
Carriage
Form
Control
I Tape
[*"

A
/
JOB DECK

j

i

L

JOB DECK STRUCTURE
(1)
SEQUENCE, 14156, SMA
JOB, 930u7, 10, 10, 35000.
REQUEST, TAPE 2, HI.

POPFM 1

CG

(ASSIGN/RING)

REWIND (TAPE 2)
COBOL (LXRM).
LGO.
(End of Record Card)
(CCBOL Source Poryram Deck FOPF M
(End of Record Card)
(Control Card - PF)
(Current File - PF Deck)
(End of File Card)

73

N/A""

CARD OUTPUT
PUNCH
!
CARD PUNCH
READY

JCVS USAGE FORM
Function:

POPFM 1

Computer: CDC -6400
Operating Philosophy:
Stage:

Compile Source Program and Go
OUTPUT
. TAPES

TAPE 1

N/A

CARD INPUT
INPUT
CARD
READER

TAPE 3

TAPE 2

; -J,

j New Population File

__PRINTED OUTPUT_
"OUT j PUT
AUDIT
FILE-PF

EMPTY

! Standard
. Carriage
! Control
'Tape
j

(Optional)

74

N/A

i

CARD OUTPUT
PUNCH"

/
/.

. ...

i PUNCH F LE-PF /
V
v
(Optional)

JCVS USAGE FORM
Function: POPFM 1
Computer:

CDC - 64u0

Operating Philosophy:

Load Binary Deck and Go

Stage:

INPUT
TAPES
TAPE 1

TAPE 3

TAPE 2

i

)

L
N/A"

SCRATCH

N/A

CARD INPUT
INPUT

i •

PRINTED OUTPUT
OUTPUT"
:
Standard
Standard
Caniage
Form
Control
Tape

i JOB DECK

CARD OUTPUT
PUNCH
CARD PUNCH
READY
I

J
JOB DECK STRUCTURE

(D
SEQUENCE, 14156, SMA
JOB, 93007, 10, 10, 35000. POPFM 1

LG

REQUEST, TAPE 2, HI. (ASSIGN/RING)
REWIND (TAPE 2)
LOAD (INPUT)
EXECUTE (POPFM)
(End of Record Card)
(Binary Program Deck - POPFM)
(End of Record Card)
(Control Card - PF)
(Current File - PF Deck)
(End of File Card)

75

—«

JCVS USAGE FORM
Function:
Computer:

POPFM 1
CDC - 6400

Operating Philosophy:
Stage:

Load Binary Deck and Go
OUTPUT
TAPES
"TAPE 2

New Population File

CARD INPUT
INPUT
CARD
READER
EMPTY

PRINTED OUTPUT^
OUTJPUf'
! Standard
AUDIT
Carriage
FILE-PF | | Control
Tape

y

CARD OUTPUT
PUNCH

/

!
PUNCH FILE-PF-

V

__(Oprtona ]}

(Optional)

76

JCVS USAGE FORM
Function:

POPFM 2

Computer:

CDC - 6400

Operating Philosophy:

Compile Source Program and Go

Stage:

INPUT
TAPES _
TAPE 2

TAPE 1

TAPE 3

j

Old Population File

CARD INPUT
INPUT

1

|

SCRATCH

PRINTED OUTPUT^
"OUTfPUT
"1
j Standard
Standard
Carriage
Form
Control
Tape

JOB DECK
._

JOB DECK STRUCTURE
(1)
SEQUENCE, 14156, SMA
JOB, 93007, 10, 10, 35000.

POPFM 2

CG

REQUEST, TAPE 1, HI. (REEl/NO RING)
REQUEST, TAPE 2, HI. (ASSIGN/RING)
REWIND (TAPE 1).
REWIND (TAPE 2).
COBOL (LXRN).
LGO
(End of Record Card)
(COBOL Source Program Deck - POPFM)
(End of Record Card)
(Control Card - PF)
(Current File - PF Deck)
(End of File Card)

77

CARD OUTPUT
PUNCH
CARD PUNCH
READY

JCVS USAGE FORM
Function:

POPFM 2

Computer: CDC - 6400
Operating Philosophy:
Stage:

Compile Source Program and Go
OUTPUT
TAPES
TAPE 3

i

CARD INPUT
INPUT
CARD
READER
EMPTY

PRINTED OUTPUT_

OUTPUT "

1

Standard
; Carriage
! Control
Tape

ILL

L

j

I PUNCH FILE-PF

I

78

CARD OUTPUT
PUNCH

L.

(Optional)

/

V

JCVS USAGE FORM
Function:

POPFM 2

Computer: CDC - 6400
Operating Philosophy:
Stage:

Load Binary Deck and Go
INPUT
•

TAPE 2

TAPE 1

Old Population File

|I

—

- A

----- _J

TAPE 3

SCRATCH

CARD INPUT
INPUT

[f JOB DECK

TAPES

PRINTED OUTPUT
OUTPUT
; Standard
Standard
Carriage
Form
Control
Tape

i

JOB DECK STRUCTURE
(1)

SEQUENCE, 14156, SMA
JOB, 93007, 10, 10, 35000.

POPFM 2 LG

REQUEST, TAPE 1, HI. (REEL/NO RING)
REQUEST, TAPE 2, HI. (ASSIGN/RING)
REWIND (TAPE 2).
LOAD (INPUT)
EXECUTE (POPFM)
(End of Record Card)
(Binary Program Deck - POPFM)
(End of Record Card)
(Control Card - PF)
(Current File - PF Deck)
(End of File Card)

79

J
CARD OUTPUT
PUNCH
CARD PUNCH
READY

JCVS USAGE FORM
Function: POPFM 2
Computer: CDC - 6400
Operating Philosophy:

Load Binary Deck and Go

Stage:

OUTPUT
TAPES
TAPE 1

Old Population File

CARD INPUT
INPUT"'
CARD
READER
EMPTY

TAPE 3

TAPE 2

l

j New Population File

PRINTED OUTPUT
" OUf PUT
AUDIT
FILE-PF

—i

80

1

CARD OUTPUT
PUNCH"

I Standard
; Carriage
Control
Tape

(Optional)

N/A

PUNCH FILE-PF
(Optional)

JCVS USAGE FORM
Function:

SELECT

Computer: CDC - 64*ju
Operating Philosophy:
Stage:

Comoile Source Program and Go
INPUT
TAPES

a

TAPE 1

TAPE 2

Pooulation File

CARD INPUT
INPUT

PRINTED OUTPUT
OUTPUT
!
| Standard
' Standard
Carriage
Form
Control
Tape

A\

/:

N/A

SCRATCH

JOB DECK

L

L_

»

JOB DECK STRUCTURE
(1)
SEQUENCE, 14156, SMA
JOB, 93u07, 10, 10, 3500u.
REQUEST, TAPE 1, HI.

SELECT

(REEL/NO RING)

REQUEST, TAPE2, HI. (ASSIGN/RI NG)
REWIND

(TAPE 2) .

COBOL (LXRM).
LGO.
(End of Record Card)
(COBOL Source Program Deck - SJCVS)
(End of Record Card)
(Control Card - S)
(Test Selection. File Deck)
(End of File Card)

81

J

CARD OUTPUT
PUNCH
CARD PUNCH
READY

JCVS USAGE FORM
Function:
Computer:

SELECT
CDC - 6400

Operating Philosophy:
Stage:

Corrmile Source Program and Go
OUTPUT
TAPES
" TAPE 2

TAPE 1

TAPE 3
/

V__ ;i
Population File

I

V- 1. :

Source Program File

M/A

U—

CARD INPUT_
INPUT
CARD
READER
EMPTY

L

PRINTED OUTPUT

OUTPUT
AUDIT
FILE-S

I Standard
Carriage
Control
~'• Tape

| (Optional)

...A

82

CARD OUTPUT
PUNCH"
/

•
/

PUNCH FILE-S
(Optional)

JCVS USAGE FORM
Function:

SELECT

Computer:

CDC - 6400

Operating Philosophy: Load Binary Deck and Go
Stage:

INPUT
TAPES
TAPE 2

TAPE 1

Pooulation File

CARD INPUT
INPUT

L
' JC
JOB DECK

PRINTED OUTPUT
OUTPUT
]
| Standard
! Standard
Carriage
Control
Form
Tape

1

-/I
|

SCRATCH

_.i

J

I
JOB DECK STRUCTURE
(1)
SEQUENCE, 14156, SMA
JOB, 93J07, 10, 10, 35000.
REQUEST, TAPE 1, HI.

SELECT

(REEL/NO RING)

REQUEST, TAPE 2, HI. (ASSIGN/RING)
REWIND, (TAPE 2).
LOAD (INPUT)
EXECUTE (SJCVS)
(End of Record Card)
(Binary Program Deck - SJCVS)
(End of Record Card)
(Control Card - S)
(Test Selection File Deck)
(End of File Card)

83

TAPE 3

N/A

CARD OUTPUT
PUNCH
CARD PUNCH
READY

JCVS USAGE FORM
Function:
Computer:

SELECT
CDC - 64U0

Operating Philosophy:
Stage:

Load Binary Deck and Go
OUTPUT
. TAPES

Population File

PRINTED OUTPUT

EMPTY

CARD OUTPUT
PUNCH

OUTPUT

r

READER

N/A

j Source Program File

CARDJNPUT
INPUT '
CARD

TAPE 3

TAPE 2

TAPE 1

AUDIT
FILE-S
y

Standard
Carriage
i . Control
Tape

(Ootional)

r
L
1

84

/

S PUNCH FILE-S
1.. ._.
- . .V
(Ootional)

JCVS USAGE FORM
Function:

SOPMM

Computer:

CDC - 6400

Operating Philosophy:

Comoile Source Program and Go

Stage:

INPUT
•

TAPES

TAPE 1

TAPE 2

Q

SCRATCH

[Old Source Program File

CARD INPUT
INPUT

1_

PRINTED OUTPUT^
OUTF|UT
i Standard
! Standard
Carriage
Form
Control
I Tape

/:
JOB DECK

TAPE 3

CARD OUTPUT
PUNCH
CARD PUNCH
READY

V
|

>

I

J

I -._

i

JOB DECK STRUCTURE
(1)
SEQUENCE, 14156, SMA.
JOB, 93007, 10, 10, 35000.
REQUEST, TAPE 1, HI.

SOPMM

(REEL/NO RING)

REQUEST, TAPE 2, HI. (ASSIGN/RING)
REWIND (TAPE 2).
COBOL (LXRM).
LGO.
(End of Record Card)
(COBOL Source Program Deck - SOPMM)
(End of Record Card)
(Control Card - SP)
(Current File - SP Deck)
(End of File Card)

85

_l

JCVS USAGE FORM
Function: SOPMM
Computer: CDC - 6400
Operating Philosophy:
Stage:

Comoile Source Program and Go
OUTPUT
TAPES

TAPE 1

i

TAPE 2

TAPE 3

Old Source Program FileJ New Source Program Filej

CARD INPUT

_ PRINTED OUTPUT
OUTJPUT

INPUT
CARD
READER
EMPTY

N/A

1

I Standard
AUDIT ! Carriage
FILE-SP | j Control
Tape
y

L(Optional)

86

CARD OUTPUT
PUNCH
/"

—
./

1 PUNCH FILE-SP

!

(Ootional)

V

JCVS USAGE FORM
Function:

SOPMM

Computer:

CDC-6400

Operating Philosophy:

Load Binary Deck and Go

Stage:

INPUT
TAPES
TAPE1

TAPE2

v
Old i.oy rce_ Progra ml i Lei

CARD INPUT
INPUT

TAPE 3

L
JU/A

SCRATCH

PRINTED OUTPUT
OUTPUT
! Standard
Form

/"

Standard
Carriage
Control
Tape

JOB DECK

JOB DECK STRUCTURE

0)
SEQUENCE, 14156, SMA.
JOB, 93007,10,10,35000. SOPMM
REQUEST, TAPE1, HI. (REEL/NORING)
REQUEST, TAPE2, HI. (ASSIGN/RING)
REWIND (TAPE2)
LOAD (INPUT)
EXECUTE (SOPMM)
(End of Record Card)
(Binary Program Deck-SOPMM)
(End of Record Card)
(Control Card-SP)
(Current File-SP Deck)
(End of File Card)

87

i

CARD OUTPUT

1

PUNCH
CARD PUNCH
READY

i

i

JCVS USAGE FORM
Function:
Computer:

SOPMM
CDC-6400

Operating Philosophy:
Stage:

Load Binary Deck and Go
OUTPUT
TAPES

TAPE1

>

TAPE2

J

i

^

TAPE3

11

.Qid_So.y rss- Program JEi W New_Soiu:ce..PcpgrairLJEill

CARD [NPUT_
INPUT
CARD
READER
EMPTY

PRINTED OUTPUT
,

--N/A

1

CARD OUTPUT

OufpUT

j
I
} Standard
! AUDIT
, Carriage
FILE-SP i i Control
Tape
1

88

u,
PUNCH

-

-V

PUNCH FILE-Sp
V

JCVS USAGE FORM
FmcKon:

JCVSRP

Computer:

CDC-6400

Operating Philosophy:

Compile Source Program and Go

Stage:

INPUT
•
TAPE1

TAPES
TAPE2

TAPE 3

V

_N/A

„N/A

INPUT

OUTPUT
Standard
Form

/::::z?j
JOB DECK

PopulolLojifile.

PRINTED OUTPUT

CARD [NPUJ_

j

!

CARD OUT PUT

Standard
Carriage
Control
Tape

PUNCH
CARD PUNCH
READY

)
\

I—

L _..

JOB DECK STRUCTURE

0)
SEQUENCE, 14156, SMA.
JOB, 93007, 10, 10, 35000. JCVSRP.
REQUEST, TAPE3, HI. (XXXX/NORING)

XXXX = Population File Reel Number

COBOL (LXRM).
LGO.
(End of Record Card)
(COBOL Source Program Deck - JCVSRP)
(End of Record Card)
(Control Card-RP)
(End of File Card)

89

•<'/!•

JCVS USAGE FORM
Function:

JCVSRP

Computer:

CDC-6400

Operating Philosophy:
Stage:

Compile Source Program and Go
OUTPUT
TAPES

TAPE1

TAPE2

TAPE3

I
._N/A_

CARD INPUT
INPUT
CARD
READER
EMPTY

J

M/A

JL

PRINTED OUTPUT
OUTPUT
! Standard
AUDIT
, Carriage
FILE-RP j i Control
Tape

J

pQpuloiLgri File.. _

CARD OUTPUT
PUNCH

PUNCH FILE
„._

/

N/A

90

JCVS USAGE FORM
Function:

JCVSRP

Computer:

CDC-6400

Operating Philosophy:

Load Binary Deck and Go

Stage:

INPUT
TAPES
TAPE1

TAPE2

TAPE 3

_N/A

PQp.u.lotiQo_Eile_.

CARD INPUT

J>RINTED OUTPUT^

INPUT

zz:

OUTPUT
Standard
Form

A

JOB DECK

Carriage
Control
I Tape

CARD OUTPUT
PUNCH
CARD PUNCH
READY

,.

j

L

|standard

—i

I

JOB DECK STRUCTURE

0)
SEQUENCE, 14156, SMA.
JOB, 93007, 10, 10, 35000.
REQUEST, TAPE3, HI. (XXXX/NORING)

XXXX = Population File Reel Number

LOAD (INPUT)
EXECUTE (JCVSRP)
(End of Record Card)
(Binary Program Deck - JCVSRP)
(End of Record Card)
(Control Card - RP)
(End of File Card)

91

JCVS USAGE FORM
Function:

JCVSRP

Computer:

CDC-6400

Operating Philosophy:
Stage:

Load Binary Deck and Go
OUTPUT
TAPES
TAPE3

TAPE2

/

._n
_[

CARD INPUT

Pggyja tion F i I <

PRINTED OUTPUT

CARD OUTPUT

JDUITPUT
:

! AUDIT
FILE-RP

L

;

PUNCH

Standard
Carriage
Control
Tape

y

/

/.

/
j

..i

92

_.__

,
i

PUNCH FILE

M4L_

JCVS USAGE FORM
Function:

INIPOP1

Computer:

CDC-6400

Operating Philosophy:

Compile Source Program and Go

Stage:

INPUT
TAPES
TAPE1

TAPE 2

TAPE3

V
N/A._

r

CARD INPUT

PRINTED OUTPUT

INPUT

z:

/

-iCMCH

SCRATCH-—.

OUTPUT
! Standard
Form

n

! Standard
Carriage
Control
Tape

' JOB DECK

L_ _
JOB DECK STRUCTURE

0)
SEQUENCE, 14156, SMA.
JOB, 93007, 10, 10, 35000. INIPOP1.
COBOL (LXRM).
LGO.
(End of Record Card)
(COBOL Source Program Deck - INI POP)
(End of Record Card)
(Control Card - IP)
(Current File - PF Deck)
(End of File Card)

93

i

CARD OUTPUT
PUNCH
CARD PUNCH
READY

JCVS USAGE FORM
Function:

INIPOP1

Computer:

CDC-6400

Operating Philosophy:
Stage:

Compile Source Program and Go
OUTPUT
__..

_L

TAPES

TAPE2

TAPE 1

TAPE3

!

Ml

Population File

PRINTED OUTPUT

CARD INPUT
INPUT

AUDIT
FILE-IP

READER

L

! Standard
Carriage
Control
Tape

.._!

PUNCH

I

J

94

i

..SCRATCH

CARD OUTPUT

Out PUT

— - —, ;

CARD

EMPTY

j_

/

r

PUNCH FILE-IP

__

V

„--»..». . *»•/

JCVS USAGE FORM
Function:

INIPOP1

Computer:

CDC-6400

Operating Philosophy:

Load Binary Deck and Go

Stage:

INPUT
TAPES
TAPE1

TAPE 2

7.1
_SCRATCH

...... ......N/A

CARD INPUT

OUTPUT
Standard
Form

Z:::ZL7
I

SCRATCH

PRINTED OUTPUT

INPUT

JOB DECK

TAPE3

CARD OUTPUT _
PUNCH

Standard
Carriage
Control
Tape

CARD PUNCH
READY

J

I

_..

L

•

JOB DECK STRUCTURE

0)
SEQUENCE, 14156, SMA.
JOB, 93007, 10, 10, 35000.
LOAD (INPUT)
EXECUTE (INIPOP)
(End of Record Card)
(Binary Program Deck - INIPOP)
(End of Record Card)
(Control Card-IP)
(Current File-PF Deck)
(End of File Card)

95

1

I

JCVS USAGE FORM
Function:
Computer:

INIPOP1
CDC-6400

Operating Philosophy:
Stage:

Load Binary Deck and Go
OUTPUT
TAPES
TAPE 2

TAPE1

N/A_

Q

Population File

CARD INPUT
CARD

INPUT

READER
EMPTY

TAPE3

PRINTED OUTPUT
^

OUTPJUT
I Standard
AUDIT
; Carriage '
FILE-IP
Control \
Tape

96

11
SCRATCH

CARD OUTPUT —I
PUNCH

/
PUNCH FILE-lp;/
,/

JCVS USAGE FORM
Funcfion:

INIPOP2

Computer:

CDC-6400

Operating Philosophy:

Compile Source Program and Go

Stage:

INPUT
TAPES
TAPE 1

TAPE 2

L
Old Population File

CARD INPUT

PRINTED OUTPUT_

INPUT

OUTPUT
Standard
Form
i

I'

JOB DECK

SCRATCH

i

V

| standard ]
Carriage
Control
I Tape

TAPE3
>

SCRATCH

J

CARD OUTPUT
PUNCH
!

CARD PUNCH
READY

i

l_.

JOB DECK STRUCTURE

0)
SEQUENCE, 14156, SMA.
JOB, 93007, 10, 10, 35000. INIPOP2.
REQUEST, TAPE1, HI. (XXXX/NORING)

XXXX = Population File Reel Number

COBOL (LXRM).
LGO.
(End of Record Card)
(COBOL Source Program Deck - INI POP)
(End of Record Card)
(Control Card-IP)
(End of File Card)

97

JCVS USAGE FORM
Function:
Computer:

INIPOP2
CDC-6400

Operating Philosophy:
Stage:

Compile Source Program and Go
OUTPUT
_^ TAPES
TAPE2

TAPE3

SCRATCH

PRINTED OUTPUT
"OUTRJT

CARD OUTPUT
PUNCH

I Standard
AUDIT
| Carriage
FILE-IP I j Control
Tape

/

r

PUNCH FILE-IP/
i

i

98

. A

JCVS USAGE FORM
Function:

INIPOP2

Computer:

CDC-6400

Operating Philosophy:

Load Binary Deck and Go

Stage:

INPUT
TAPES
TAPE1

TAPE2

Old Population File

SCRATCH

CARD INPUT

PRINTED OUTPUT

INPUT

OUTPUT
I Standard
Form

z::z:

Standard
Carriage
Control
' Tape

TAPE 3

SCRATCH

CARD OUTPUT
PUNCH
CARD PUNCH
READY

JOB DECK

J

I

JOB DECK STRUCTURE

0)
SEQUENCE, 14156, SMA.
JOB, 93007, 10, 10, 35000. INIPOP2.
REQUEST, TAPE1, HI. (XXXX/NORING)

XXXX = Population File Reel Number

LOAD (INPUT)
EXECUTE (INIPOP)
(End of Record Card)
(Binary Program Deck - INI POP)
(End of Record Card)
(Control Card-IP)
(End of File Card)

99

JCVS USAGE FORM
Function:
Computer:

INIPOP2
CDC-6400

Operating Philosophy:
Stage:

Load Binary Deck and Go
OUTPUT
TAPES

TAPE1

TAPE 2

TAPE 3

v
ri
SCRATCH

.1

_Old P°fwlaJrfo2)_FjJe_

CARD INPUT_

i_ NewPopulation File

PRINTED OUTPUT

CARD
READER
EMPTY

CARD OUTPUT

OUTPUT

INPUT

] j
! AUDIT
,
FILE-IP
j
.•
j

L-

PUNCH

Standard
Carriage
Control
Tape

I PUNCH FILE-IP
V
i

100

i

—I

JCVS USAGE FORM
Function:

POPFM1

Computer:

UNI VAC - 1108

Operating Philosophy:
Stage:

Compile Source Program and Go
INPUT
•

UNISERVO A

TAPES

I UNISERVO B

UNISERVO

C

v. I
L

N/A

SCRATCH

CARD INPUT
[CARD READER EIGHTY!

JOB DECK

L

L-

_

i| i:

V
_J

PRINTED OUTPUT
'"PRINTER" ' |
"1
: Standard
Carriage
Standard
Form
Control
Tape

L

JOD DECK STRUCTURE
(1)
<5> RUN 1 POPFM 1, DDCG, 5, 300
fo'ASG B-SAVE
(o-BREI COB POPFM1
(COBOL Source Porgram Deck - POPFM)
<9> XQT POPFM 1
(Control Card - PF)
(Current File - PF Deck)

Co FIN

101

N/A

-1

CARD OUTPUT
"A'RD
PUNCH EIGHTY]
p
CARD PUNCH
READY

JCVS USAGE FORM
Function:
Computer:

POFfMl
UNIVAC-1108

Operating Philosophy:

Compile Source Program a no Go

Stage:

OUTPUT
TAPES
UNISERVO

UNISERVO

B

UNISERVO

I
N/A

t New Population File

CARD INPUT
; CARD READER EIGHTY
I
CARD
I
;
READER
!

EMPTY

N/A

PRINTED OUTPUT
PRINTER
i
j Standard
! AUDIT
Carriage
FILE-PF j Control
J Tape

i

—<

L

CARD OUTPUT
(CARD PUNCH EIGHTY1
I

I L
i

102

/

PUNCH FILE-PF

/

(Optional)

I

(Optional)

JCVS USAGE FORM
Function:

POPFM1

Computer:

UNIVAC-1108

Operating Philosophy:

Lcxid Binary Deck and Go

Stage:

INPUT
TAPES
UNISERVO

UNISERVO

/.
J

- /[

i JOB DECK

....

I

PRINTER
Standard
Form

CARD OUTPUT

'standard
Caniage
Control
Tape

I,

'/

I

...I
JOB DECK STRUCTURE

0)
RUN1 POPFM1, DOLG,5,300
ASG B = SAVE

(Binary Program Deck - POPFM)
@XQT,POPFMl
(Control Card - PF)
(Current File - PF Deck)
@ FIN

103

i

N/A

PRINTED OUTPUT

'CARD READER EIGHTY

i

\

SCRATCH

_.

CARD INPUT

: /

UNISERVO

/

( 1
N/A

B

CARD PUNCH EIGHr
CARD PUNCH
READY

1

JCVS USAGE FORM
Function:
Computer:

POPFM1
UNIVAC -1108

Operating Philosophy:

Load Binary Deck and Go

Stage:

OUTPUT
TAPES
UNISERVO

N/A

CARD INPUT
(CARD READER EIGHTY
CARD

EMPTY

UNISERVO

I

1

READER

B

UNISERVO

( New Population File

PRINTED OUTPUT

ifi

N/A

1

PRINTER
Standard
i AUDIT
Carriage
FILE-PF
Control
Tape
!
i

i
J

(Optional)

104

CARD OUTPUT
CARD PUNCH EIGHTY

/I PUNCH FILE-PF{
(Optional)

JCVS USAGE FORM
Function:

POPFM2

Computer:

UNI VAC -1108

Operating Philosophy:

Compile Source Program and Go

Stage:

INPUT
TAPES
UNISERVO

!

V

A

(

! UNISERVO

>

%

1

[ Old Population File

B

\

(

PRINTED OUTPUT

CARD READER EIGHTYj

PRINTER
Sta nda rd
Form

z. ::.

/

>

SCRATCH

CARD INPUT

UNISERVO

Standard
Carriage
Control
Tape

N/A

CARD OUTPUT
CARD PUNCH EIGHTY*
I
CARD PUNCH
READY

f JOB DECK

V

J

•

JOB DECK STRUCTURE

0)
@RUN1 POPFM2,DDLG,5,300
@ ASG,B,A=XXXX
@ 3REI COB POPFM2

XXXX = POPFILE1 reel number

(COBOL Source Program Deck - POPFM)
@ XQT POPFM2
(Control Card - PF)
(Current File - PF Deck)
@FIN

105

j

JCVS USAGE FORM
Function:
Computer:

POPFM2
UNIVAC -1108

Operating Philosophy

Compile Source Program and Go

Stage:

OUTPUT
TAPES
A

UNISERVO

UNISERVO

B

UNISERVO

..n
[

f CARD

READER EIGHTY
CARD
READER
EMPTY

1

V

Old Population File j New Population File

CARD INPUT

C

1

PRINTED_OUTPUT_

CARD OUTPUT

| PR]
PRINTER

|
I Standard
! AUDIT
Carriage
FILE-PF I | Control
Tape
(Optional)

106

N|/A

CARD PUNCH EIGHTY
/
/

4—

/

PUNCH FILE-PF
1

(Optional)

JCVS USAGE FORM
Funciion:

POPFM2

Computer:

UNIVAC-1108

Operating Philosophy:

Load Binary Deck and Go

Stage:

INPUT
TAPES
UNISERVO
(

UNISERVO

CARD INPUT
• CARD READER EIGHTY'

j

PRINTED OUTPUT
[ PRINTER
!standard
Carriage
Control
Tape

i
f JOB DECK

:

^

SCRATCH

Standard
Form
:

UNISERVO

C i

\

[ Old Population File

B

.',
1/ •

N/A

CARD OUTPUT
["'

"" 11

'CARD PUNCH EIGHTY
CARD PUNCH
READY

i

L_

i

JOB DECK STRUCTURE

0)
@RUN1 POPFM2,DDLG/5/300
@ ASG B A = XXXX

XXXX = POPFILE1 reel number

(Binary Program Deck - POPFM)
XQT POPFM2
(Control Card - PF)
(Current File - PF Deck)
© FIN

107

JCVS USAGE FORM
Function:
Computer:

POPFM2
UNIVAC - 1108

Operating Philosophy:

Load Binary Deck and Go

Stage:

OUTPUT
TAPES
UNI SERVO

3
Old Population File

CARD INPUT
CARD READER EIGHTY
CARD
READER
EMPTY

UNISERVO

B

v
rj
| New Population File

PRINTED OUTPUT
PRI hflTER
! Standard
AUDIT
; Carriage
FILE-PF j | Control
Tape

UNISERVO

N/A

CARD OUTPUT
CARD PUNCH EIGHTY
r~
I PUNCH FILE-Pf

L-

-. .v

(Optional)

(OpHonol)

108

i

JCVS USAGE FORM
Function:

SELECT

Computer:

UNIVAC-1108

Operating Philosophy:

Compile Source Program and Go

Stoge:

INPUT
TAPES
UNISERVO

A

UNISERVO

Q

f

Population File

B

UNISERVO

N

I

SCRATCH

CARD INPUT

C

v I

\

N/A

i

CARD OUTPUT

PRINTED OUTPUT
i

CARD READER EIGHTY!

/

PRINTER
! Standard
Form

Standard
Carriage
Control
Tape

'CARD PUNCH EIGHTY

1

CARD PUNCH
READY

' JOB DECK

t -

JOB DECK STRUCTURE

(D
XXXX = POPFILE1 reel number
YYYY = JOVSP reel number

@ RUN 1 SELECT,DDCG,5,300
@ ASG A = XXXX,B = YYYY
@ BREI COB SELECT
(COBOL Source Program Deck - SELECT)
@ XQT SELECT
(Control Card - S)
(Test Selection File Deck)
@FIN

109

JCVS USAGE FORM
Function:
Computer:

SELECT
UNI VAC -1108

Operating Philosophy:

Compile Source Program and Go

Stage:

OUTPUT
TAPES
UNISERVO

UNISERVO

B

UNISERVO

i

Population File

Source Program File

PRINTED OUTPUT

CARD INPUT
IcARD READER EIGHTY
CARD
READER
EMPTY

N/A

;

CARD OUTPUT

J>RI!NTER
| ! Standard
AUDIT
Carriage
FILE-S
j Control
,,— Tape

CARD PUNCH EIGHTY

r

~

/

/

j PUNCH FILE-S1

: /

!

IQgHonallJ

-i

110

_ .IQefilogal)

JCVS USAGE FORM
Function:
Computer:

SELECT
UNIVAC-1108

Operating Philosophy:

Load Binary Deck and Go

Stage:

INPUT
TAPES
UNISERVO

UNISERVO

UNISERVO

( I

^

v....

Population File

CARD INPUT

\

. i

/]'•
!

Standard
Carriage
Control
Tape

i

N/A

SCRATCH

PRINTER
Standard
Form

~\

S^

CARD OUTPUT

PRINTED OUTPUT

•CARD READER EIGHTY

JOB DECK

{

(

I" "
i

CARD PUNCH EIGHTY
CARD PUNCH
READY

i

l,'

JOB DECK STRUCTURE

0)
@ RUN SELECT,DDLG^^OO
@ ASG A = XXXX B = YYYY

XXXX = POPFILE1 reel number
YYYY = JOVSP reel number

(Binary Program Deck - Select)
XQT SELECT
(Control Card - S)
(Test Selection File Deck)
@ FIN

111

JCVS USAGE FORM
Function:
Computer:

SELECT
UNIVAC-1108

Operating Philosophy:

Load Binary Deck and Go

Stage:

OUTPUT
TAPES
UNISERVO

UNISERVO

UNISERVO

C

I
Population File

CARD INPUT
I

CARD READER EIGHTY
CARD
READER
EMPTY

i_j>ource Program File_ j

PRINTEDOUTPUT

CARD OUTPUT

PRINTER^
AUDIT
FILE-S

[CARD PUNCH EIGHTY
| I Standard
Carriage
j Control
Tape

!

L

N/A

t
i

|

UOfitionall

_i

112

r

7

/
/
t—

/

PUNCH FILE-S
\»

(Optional)

JCVS USAGE FORM
Function:

SOPMM

Computer:

UNIVAC-1108

Operating Philosophy:

Compile Source Program and Go

Stage:

INPUT
TAPES
UNISERVO

I

UNISERVO

B

UNISERVO

rv. ^/,

D
V

Old Source Program Ft]

SCRATCH

N/A

PRINTED OUTPUT

CARD INPUT
ICARD READER EIGHTYl

I

!
JOB DECK

C

PRINTER
Standard
Form

Standard
Carriage
Control
Tape

J

CARD OUTPUT
!CARD PUNCH EIGHTY

j

i

CARD PUNCH
READY

J

JOB DECK STRUCTURE

(D
@ RUN SOPMM,DDLG,5,300
@ ASG A = XXXX,B
@ BREI COB SOPMM

XXXX = JOVSP reel number

(COBOL Source Program Deck - SOPMM)
@ XQT SOPMM
(Control Card - SP)
(Current File - SP Deck)

@FIN

113

!

JCVS USAGE FORM
Function:
Computer:

SOPMM
UNIVAC-1108

Operating Philosophy:

Compile Source Program and Go

Stage:

OUTPUT
TAPES
UNI SERVO

A

UNISERVO

B

Old Source Program File) New Source Program Fil^

CARD INPUT

PRINTED OUTPUT

CARD READER EIGHTY
CARD
READER
EMPTY

.

J

PRINTER
! Standard ;
I AUDIT
; Carriage
FILE-SP j | Control
Tape

UNISERVO

C

Q
N/A

CARD OUTPUT
CARD PUNCH EIGHTY

/

iPUNCH FILE-SP,

L
jLQptlonaJl

^Optional)

114

/

JCVS USAGE FORM
Function:

SOPMM

Computer:

UNIVAC-1108

Operating Philosophy:

Load Binary Deck and Go

Stage:

INPUT
TAPES
UNISERVO

A

I

V

I UNISERVO

i

K

Old Source Program File

'CARD READER EIGHTYl

/

L

B

i

SCRATCH

PRINTED OUTPUT

CARD INPUT

f JOB DECK

...

:

I PINTER

!

Standard
Form

|standard
Carriage
Control
Tape

UNISERVO

V. (
N/A

CARD OUTPUT
iCARD PUNCH EIGHTH
CARD PUNCH
READY

j.

-..- V I
i. .

JOB DECK STRUCTURE
(1)
@ RUN SOPMM, DDLG^^OO
@ ASG A =XXXX,B

XXXX = JOVSPreel number

(Binary Program Deck - SOPMM)
@ XQT SOPMM
(Control Card - SP)
(Current File - SP Deck)
@ FIN

115

1

JCVS USAGE FORM
Function:
Computer:

SOPMM
UNI VAC - 1108

Operating Philosophy

Load Binary Deck and Go

Stage:

OUTPUT
TAPES
UNISERVO

I UNISERVO

B

UNISERVO

.1

Old Source Program File! New Source Program Filje

„CA!*D INPUT

N/A

_PRINTED OUTPUT

CARD READER EIGHTY
CARD
READER
EMPTY

PRINTER
! Standard '
AUDIT
; Carriage
FILE-SP i I Control
'— Tape

L...y
i

CARD OUTPUT

A
//
I PUNCH FILE-S(>

I

tlonaljj

116

1

CARD PUNCH EIGHTY

-. ....

(Optional)

'/

JCVS USAGE FORM
Function:

JCVSRP

Computer:

UNIVAC-1108

Operating Philosophy:

Compile Source Program and Go

Stage:

INPUT
TAPES
UNISERVO

UNISERVO

B

UNISERVO

C

/"" "\

L
N/A

u.

CARD INPUT
f"
•CARD READER EIGHTY
:

L

i

I

£_

/

/,

N/A

PRINTED OUTPUT
PRINTER
Standard
Form

Standard
Carriage
Control
Tape

Population File

CARD OUTPUT
r
•1
[CARD PUNCH EIGHTY^
CARD PUNCH
READY

[ JOB DECK
/ !
i

L

JOB DECK STRUCTURE

0)
@ RUN 1 JCVSRP,DDCG^^OO
@ ASG C = XXXX
@ BREI COB JCVSRP

XXXX = POPFILE1 reel number

(COBOL Source Program Deck - JCVSRP)
@ XQT JCVSRP
(Control Card - RP)
@ FIN

117

JCVS USAGE FORM
Function:
Computer:

JCVSRP
UNIVAC-1108

Operating Philosophy:

Compile Source Program and Go

Stage:

OUTPUT
TAPES
I

]

UNISERVO

UNISERVO

1

N/A

N/A

CARD INPUT

EMPTY

UNISERVO

j Population File Reports |

I

CARD OUTPUT

PINTER
! AUDIT
!
FILE-RP
!

I

CARD PUNCH EIGHTY

! Standard '
Carriage
! Control
Tape
!

...i

1

118

C

c l

PRINTED OUTPUT

CARD READER EIGHTY
CARD
READER

B

/
<

PUNCH FILE-RP
N/A

JCVS USAGE FORM
Fu -.ctior:

JCVSRP

Ccinputcr:

UNIVAC-1108

Op^rati.ig Philosophy:

Load Binory Deck and Go

Stage:

INPUT
TAPES
JNISERVO

UMISERVO

)

_ CARD INPUT

JOB DECK
L

UNI5ERVO

v.. i

!

N/A

j

(

»
!

i PRINTER
I Standard
Form

II

)

Popu ation File

PRINTED OUTPUT

CARD READER EIGHTY

/:

B

CARD OUTPUT
;

CARD PUNCH EIGHTY

Standard
Carriage
Control
Tape

CARD PUNCH
READY

>,

J/ i

...j

I

!

JOB DECK STRUCTURE

0)
XXXXX = POPFILE1 reel number

(§ RUN 1 JCVSRP, DDLG,5,300
(5 ASG C = XXXX
(Binary Program Deck - JCVSRP)
<9 XQT JCVSRP
(Control Card - IP)
(5 FIN

llv

JCVS USAGE FORM
Function:
Computer:

JCVSRP
UNIVAC«1108

Operating Philosophy:

Load Binary Deck and Go

Stage:

OUTPUT
! UNISERVO

A

UNISERVO

C

_1

N/A

CARD INPUT

Population File

PRINTED OUTPUT

CARD READER EIGHTY
CARD
READER

PRINTER
i
AUDIT
FILE-RP

EMPTY
y

I Standard
Carriage
Control
Tape

CARD OUTPUT

1

[CARD PUNCH EIGHTY
/
/

/

"

1 PUNCH FILE

j

/)
/
J j
1/

y

N/A

120

•

JCVS USAGE FORM
Function:

INIPOP1

Computer:

UNIVAC-1108

Operating Philosophy:

Compile Source Program and Go

Slage:

INPUT
TAPES
UNISERVO

A

UNISERVO

B

UNISERVO

\
\
N/A

SCRATCH

CARD INPUT

zz::: 7i

i

\
.i„..

PRINTED OUTPUT

iCvRD READER EIGHTY

f JOB DECK

I

| PRINTER
Standard
Form

CARD PUNCH EIGHTY;

I
CARD PUNCH
READY

.J/'

<

JOB DECK STRUCTURE

0)
@ RUN T INI POP, DD100,5,300
@ ASG B,C
@ BREI COB INI POP
(COBOL Source Program Deck - INI POP)

(Control Card - IP)
(Current File - PF Deck)
@FIN

121

SCRATCH

CARD OUTPUT

! standard
Carriage
Control
Tape

@XQT INI POP

L

\

JCVS USAGE FORM
INI POP!
UNI VAC - 1108

Function:
Computer:

Operating Philosophy

Compile Source Program and Go

Stage:

OUTPUT
TAPES
UNISERVO

B

UNISERVO

UNISERVO

i

I
Population File

CARD INPUT
CARD READER EIGHTY
CARD
READER
EMPTY

L_

i

SCRATCH

i

PRINJEDOUTPUT_

CARD OUTPUT

PRJNTER
! Standard
I AUDIT
Carriage
FILE-IP
; Control
Tape

CARD PUNCH EIGHTY

(Optional)

122

~J

f- ~ 7
! PUNCH FILE-IP -'
(Optional)

JCVS USAGE FORM
Function:

INIPOP1

Computer:

UNIVAC-1108

Operating Philosophy:

Load Binary Deck and Go

Stage:

INPUT
TAPES
UNISERVO

i

UNISERVO

v.

')

N/A

B

UNISERVO

t

SCRATCH

CARD INPUT

r CARD READER EIGHTYl
!

ZZIZTi!

SCRATCH

PRINTED OUTPUT
i PRINTER
: Standard
Form

CARD OUTPUT
r ""
1
'CARD PUNCH EIGHTY1

Standard
Carriage
Control
Tape

CARD PUNCH
READY

! JOB DECK
(

JOB DECK STRUCTURE

0)
@RUN1 INI POP, DD1LG,5,300
@ ASG BfC
(Binary Program Deck - INI POP)
@XQT INI POP
(Control Card - IP)
(Current File - PF Deck)
(?> FIN

123

JCVS USAGE FORM
Function:

INIPOP1

Computer:

UNIVAC-1108

Operating Philosophy:

Load Binary Deck and Go

Stage:

OUTPUT
TAPES
UNISERVO

UNISERVO

SCRATCH

CARD INPUT

PRINTED OUTPUT_

PRINTER

CARD READER EIGHTY
CARD
AUDIT
FILE-IP

READER

CARD OUTPUT

EMPTY

CARD PUNCH EIGHTY

i Standard
Carriage
Control
Tape

r~
/
•

.1

(Optional)

i

124

i

/

PUNCH FILE-IP
;/
i'

(Optional)

JCVS USAGE FORM
Function:

INIPOP2

Computer:

UNIVAC-1108

Operating Philosophy:

Compile Source Program and Go

Stage:

INPUT
TAPES
UNISERVO

UNISERVO

B

UNISERVO
\

L
Old Population File

SCRATCH

PRINTED OUTPUT

CARD INPUT
CARD READER EIGHTY!

f JOB DECK

j....

r

PRINTER
Standard
Form

f""

Standard
Carriage
Control
Tape

j

SCRATCH

...i

CARD OUTPUT

'•

CARD PUNCH EIGHTY
CARD PUNCH
READY

._<

JOB DECK STRUCTURE

0)
@ RUN 1 INI POP, DD2CG,5,300
@ ASG A=XXXX/B/C
@ BREI COB INI POP

XXXX = POPFILE1 reel number

(COBOL Source Program Deck - INI POP)
@XQTINIPOP
(Control Card - IP)
FIN

25

JCVS USAGE FORM
INIPOP2

Function:
Computer:

UNIVAC - 1108

Operating Philosophy

Compile Source Program and Go

Stage:

OUTPUT
TAPES
UNISERVO

A

UNISERVO

B

UNISERVO

v

Old Population F[le

i^Ne** P°pyl°TL°_n ':''e

CARD INPUT
CARD READER EIGHTY
CARD
READER
EMPTY

L

C

ri

SCRATCH

PRINTED OUTPUT

CARD OUTPUT

PRINTER
! Standard
i AUDIT
Carriage
! FILE-IP i Control
Tape

CARD PUNCH EIGHTY

r

1

r ~~f

/1 PUNCH FILE-IP{

l^

i

J9s&sss^L

i

126

1...

i'
(Optional)

JCVS USAGE FORM
Function:

INIPOP2

Computer:

UNIVAC-1108

Operating Philosophy:
Stage:

Load Binary Deck and Go
INPUT
TAPES
UNISERVO

UNISERVO

B

UNISERVO

s..

i Old Population File

SCRATCH

PRINTED OUTPUT

CARD INPUT
CARD READER EIGHTY

Z.

/)

! PRINTER
' Standard
Form

Standard
Carriage
Control
Tape

SCRATCH

CARD OUTPUT
CARD PUNCH EIGHTY^
CARD PUNCH
READY

JOB DECK

_J

'.

-...

JOB DECK STRUCTURE

0)
XXXX = POPFILE1 reel number

@ RUN 1 INI POP, 00210,5,300
@ ASG A=XXXX,B,C
(Binary Program Deck INI POP)
@XQT INI POP
(Control Card - IP)
@FIN

127

JCVS USAGE FORM
Function:
Computer:

INIPOP2
UNIVAC - 1108

Operating Philosophy:

Load Binary Deck and Go

Stage:

OUTPUT
TAPES
UNISERVO

A

UNI SERVO

J2

CARD READER EIGHTY
CARD
READER
EMPTY

UNISERVO

V

v—n

Old Population File (

CARD INPUT_

B

New Population File j

C

:;

SCRATCH

PRINTED OUTPUT_

CARD OUTPUT

PRINTER

CARD PUNCH EIGHTY

! Standard
I AUDIT
Carnage
FILE-IP
If Control
^— j Tape

/

4-. -

1 PUNCH FILE-II

!

L_.

__{OeHoni)__

128

..-1

V

{Optional)

JCVS USAGE FORM
Function:

POPFM1

Computer:

GE-635

Operating Philosophy:

Compile Source Program and Go

Stage:

INPUT
TAPES
A3

A4

1

A6

^"'-

\

v.... s
SCRATCH

i

CA >RD INPUT

PRINTED OUTPUT

Al

i

j

1
/

L

"f

A2

Standard
Carriage
Control
Tape

Standard
Form

/i!

JOB DECK

!

NA

|j

V \1

L... ...

!

1

1

JOB DECK STRUCTURE

0)

(8)

06)

$
$
$

IDENT
COBOL
INCODE

3154203, DATDY
I BMC

(COBOL Source Program Deck - POPFM)
$
S
$

s
s
$

EXECUTE
LIMITS
SYSOUT
TAPE
SYSOUT
DATA

DUMP
15,32000
A2
A3,X3S,,POPFILEl#/SAVE
A5
Al

(Control Card - PF)
(Current File - PF Deck)
$

*** EOF

ENDJOB

129

N/A

i

CARD OUTPUT
A5
CARD PUNCH
READY

JCVS USAGE FORM
Function:

POPFM1
GE-635

Computer:

Operating Phil osophy:

Compile Source Program and Go

Stage:

OUTPUT
TAPES
A3

A6
/

New Population File

r ^

CARD INPUT

|

CARD

READER
EMPTY

N/A

PRINTED OUTPUT

...i

CARD OUTPUT

A2

!
I Standard
AUDIT | | Carriage
FILE-PF
Control
Tape

A5

i

/

-

I PUNCH FILE-PF

I
«...

„.

(Optional)

._!

130

/

(Optional)

JCVS USAGE FORM
Function:

POPFM1

Computer:

GE-635

Operating Philosophy:
Stage:

Load Binary Deck and Go
INPUT
TAPES

A3

A4

A6

f" "

/"

I

(
c. _ -

SCRATCH

N/A

PRINTED OUTPUT

CARD INPUT
Al

i

/
JOB DECK

:"""
i_.

-

N/A

A2
Standard
Form

CARD OUTPUT
A5

Standard
Carriage
Control
Tape

CARD PUNCH
READY

i ).
!/ ;

i
„.J

.

«

JOB DECK STRUCTURE

0)

(8)

(16)

$

IDE NT
OPTION

3154203, DATDY
COBOL

s

(Binary Program Deck - POPFM)
$
$
$
$
$

s

EXECUTE
LIMITS
SYSOUT
TAPE
SYSOUT
DATA

DUMP
15,32000
A2
A3,X3S,,POPFILEl,,XXXX
A5
Al

(Control Card - PF)
(Current File - PF Deck)
$
*** EOF

ENDJOB

131

XXXX = reel number

JCVS USAGE FORM
Function:
Computer:

POPFM1
GE-635

Operating Philosophy:

Load Binary Deck and Go

Stage:

OUTPUT
TAPES
A3

A4

1

;i

N/A

New Population File |

CARD INPUT
Al

A6

PRINTED OUTPUT
A2

CARD OUTPUT

I

CARD
READER

N/A

A5
Standard
Carriage
Control
Tape

AUDIT
FILE-PF

EMPTY
(Optional'

132

r
./-

/

I PUNCH FILE-PF/

j

(Optional)

JCVS USAGE FORM
Function:

POPFM2

Computer:

GE-635

Operating Philosophy:
Stage:

Compile Source Program and Go
INPUT
TAPES

A3

r
V

! "
*

^

SCRATCH

/

!

j

i

A4
i

--

l

Old Population File

*

!

j

PRINTED OUTPUT

CARD INPUT

Al
/

A2
Standard
Form

A6

Standard
Carriage
Control
Tape

v

-

N/A

CARD OUTPUT
A5
CARD PUNCH
READY

JOB DECK

JOB DECK STRUCTURE
(1)

(8)

06)

$

I DENT
COBOL
INC ODE

3154203, DATDY

S
$

I BMC

(COBOL Source Program Deck - POPFM)

s
$
$
$

s
s
$

EXECUTE
LIMITS
SYS OUT
TAPE
TAPE
SYSOUT
DATA

DUMP
15,32000
A2
A3,X3S
A4,X4D POPFILEl,,XXXX
A5
AT

(Control Card - PF)
(Current File - PF Deck)

*** EOF

END JOB

133

XXXX = reel number

JCVS USAGE FORM
Function:
Computer:

POPFM2
GE-635

Operating Philosophy:

Compile Source Program and Go

Stage:

OUTPUT
TAPES
A3

A4

A6

a a

New Population File
,
'

CARD INPUT
Al

Old Population File

PRINTED OUTPUT
A2

CARD
READER

N/A

! AUDIT
FILE-PF

EMPTY

Standard
; Carriage
Control
Tape

1

CARD OUTPUT
A5

(PUNCH FILE-Pf

.v

I

IQptionaJl

(Optional)

134

JCVS USAGE FORM
I

Function:

POPFM2

Computer:

GE-635

Operating Philosophy:

Load Binary Deck and Go

Stage:

INPUT
TAPES
A3

A4

f

1
SCRATCH

j Old Population File

CARD INPUT

PRINTED OUTPUT

Al

A2
Standard
Form

l- .

- i

J OB DECK

i

A6

i .

!

Standard
Carriage
Control
Tape

N/A

.. j

CARD OUTPUT
A5
CARD PUNCH
READY

; }
!/
~

J

JOB DECK STRUCTURE
(1)

(8)

06)

$

IDE NT
OPTION

3154203, DATDY
COBOL

(Binary Program Deck - POPFM)

s
$

s
s
$
$
$

EXECUTE
LIMITS
SYSOUT
TAPE
TAPE
SYSOUT
DATA

DUMP
15,32000
A2
A3,X3S
A4,X4D,,POPFILEl,,XXXX
A5
Al

(Control Card - PF)
(Current File - PF Deck)
$

END JOB

***EOF

135

XXXX=reel number

JCVS USAGE FORM
Function:

POPFM2

Computer:

GE-635

Operating Philosophy:

Load Binary Deck and Go

Stage:

OUTPUT
TAPES

New Population File

CARD INPUT
Al
CARD
READER

A6

A4

A3

j

OldJ'opulation File J

PRINTED OUTPUT

~~« "1
AUDIT
FILE-PF I

EMPTY

-,

i Standard
Carriage
Control
Tape

(Optional)

136

.J

... .71
N/A

CARD OUTPUT
A5

PUNCH FILE-PF,
...........:

. ... . .A'/

(Optional)

JCVS USAGE FORM
Function:

SELECT

Computer:

GE-635

Operating Philosophy:
Stage:

Compile Source Program and Go
INPUT
TAPES

A3

A4

A6

r

\

K

SCRATCH

CARD INPUT

Population File

N/A

PRINTED OUTPUT

CARD OUTPUT

i

Al

L
!

:

/I:

A2
Standard
Form

! Standard
Carriage
Control
Tape

JOB DECK

-J

..-«

JOB DECK S TRUCTURE

0)
s
$
$

(8)

(16)

IDE NT
COBOL
INCODE IBMC

3154203, DATDY

(COBOL Source Program Deck - SJCVS)
EXECUTE
LIMITS
TAPE
SYSOUT
SYSOUT
DATA

$
$
$
$
$
$

DUMP
15,32000
A3,X3S,,SAVE,,JOVSP
A5
A2
Al

(Control Card - S)
(Test Selection File Deck)
ENDJOB
>EOF

137

A5
CARD PUNCH
READY

JCVS USAGE FORM
Function:
Computer:

SELECT
GE-635

Operating Philosophy:

Compile Source Program and Go

Stage:

OUTPUT
TAPES
A3

A4

A6

i

CARD INPUT_

PRINTED OUTPUT

Al

A2

CARD
READER
EMPTY

L.__

CARD OUTPUT

! AUDIT
FILE-S
t

A5
Standard
Carriage
i Control
Tape

(Optiorwl)

_..!

138

/"
/

""
/

1

I PUNCH FILE-S;
i.
V
(Optional)

JCVS USAGE FORM
Function:

SELECT

Computer:

GE-635

Operating Philosophy:
Stage:

Load Binary Deck and Go
INPUT
TAPES
I

A3

A4

A6
/"

SCRATCH

CARD INPUT

i -

PRINTED OUTPUT

Al

L

Population File

/

A2
Standard
Form

Standard
Carriage
Control
Tape

JOB DECK
!/ ;

JOB DECK STRUCTURE
(1)
$
$

(8)

(16)

IDE NT
OPTION

3154203, DATDY
COBOL

(Binary Program Deck - SJCVS)
$

s
$
$
$

s

EXECUTE
LIMITS
TAPE
SYSOUT
SYSOUT
DATA

DUMP
15,32000
A3,X3S,,SAVE,,JOVSP
A5
A2
Al

(Control Card - S)
(Test Selection File Deck)
$

ENDJOB

***EOF

139

N/A

CARD OUTPUT
A5
CARD PUNCH
READY

JCVS USAGE FORM
Function:
Computer:

SELECT
GE-635

Operating Philosophy:

Load Binary Deck and Go

Stage:

OUTPUT
TAPES
A3

A4

A6
\

WA.

Source Program File

CARD INPUT

PRINTED OUTPUT

Al

A2

CARD
READER
EMPTY

CARD OUTPUT

AUDIT
FILE-S

L

y

A5
! Standard
Carriage '
| Control
jTape
j

/
/

j PUNCH FILE- •S

A
/

. . V

(Optional) j

i

140

(Optional)

JCVS USAGE FORM
Function:

SOPMM

Computer:

GE-635

Op3rating Philosophy:

Compile Source Program and Go

Stage:

INPUT
TAPES
!
A3

A4

A6

/'

/

I

1

/

SCRATCH

PRINTED OUTPUT

CARD INPUT
Al

A2

/!!
f JOB DECK

j Old Source Program FiIej

•

Standard
Form

Standard
Cairiage
Control
Tape

N/A

CARD OUTPUT
A5
CARD PUNCH
READY

>

1/ ;

JOB DECK STRUCTURE
(1)

(8)

(16)

$
$
$

IDENT
COBOL
INCODE

3154203, DATDY
IBMC

(COBOL Source Program Deck - SOPMM)
EXECUTE
LIMITS
SYSOUT
TAPE
TAPE
SYSOUT
DATA

$

s
$
$
$
$
$

DUMP
15,32000
A2
A3,X3S
A4/X4S//JOVSP,/XXXX
A5
Al

(Control Card - SP)
(Current File - SP - Deck)
END JOB
'EOF

141

XXXX = reel number

JCVS USAGE FORM
Function: SOPMM
Computer: GE-635
Operating Philosophy:Compile Source Program and Go
Stage:

OUTPUT

A6

A3
\

i

[

)
New Source Pgm

CARD INPUT
AT

CARD
READER
EMPTY

File jOld Source Pgm

File

_..n

N/A

PRINTED OUTPUT
A2
r
Standard
! AUDIT . Carriage
FILE ~SP j ; Control
Tape
(Optional)

CARD OUTPUT
A5

/
1

PUNCH FILE-SP

(Optional)

142

JCVS USAGE FORM
Function:

SOPMM

Computer:

GE-635

Operating Philosophy:

Load Binary Deck and Go

Stage:

INPUT
TAPES
A3

SCRATCH ._

CARD INPUT
Al

i;

JOB DECK

a
A4

i

A6
\

IQld Source Program File

PRINTED OUTPUT
;—
-i
1
A2
i Standard
• Standard
Carriage
Form
Control
i
Tape

CARD OUTPUT
A5
CARD PUNCH
READY

.1 v

L

JOB DECK STRUCTURE
(1)

(8)

(16)

$

IDE NT
OPTION

3154203, DATDY
COBOL

$

(Binary Program Deck - SOPMM)
EXECUTE
LIMITS
SYSOUT
TAPE
TAPE
SYSOUT
DATA

$

s
s
$
$
$
$

DUMP
15,32000
A2
A3,X3S
A4,X4S,,JOVSP,,XXXX
A5
Al

(Control Card •-SP)
(Current File - SP Deck)
ENDJOB
'EOF

143

XXXX = reel number

JCVS USAGE FORM
Function:
Computer:

SOPMM
GE-635

Operating Philosophy:

Load Binary Deck and Go

Stage:

OUTPUT
TAPES
A3

New Source Pgm File

CARD INPUT
Al

A4

Old Source Pgm File

N/A

PRINTED OUTPUT

CARD OUTPUT

A2

A5

CARD
READER

A6

i Standard
Carriage
| Control
Tape

I AUDIT
FILE-SP

EMPTY

t
PUNCH FILE-SP/

L_.(9pt'°nn!L

144

J

(Optional)

v

JCVS USAGE FORM
Fi notion:

JCVSRP

Computer: GE-635
Operating Philosophy: Compile Source Program and Go
Stage:

INPUT
TAPES
A4

A3

r^

/'

i Population File

CARD INPUT
Al

A6

N/A

N/A

PRINTED OUTPUT
A2
Standard
Standard
Carriage
Form
Control
Tape

""I

/

CARD OUTPUT
A5
CARD PUNCH
READY

JOB DECK

_l

.

«

JOB DECK STRUCTURE
(I)

(8)

(16)

$
$

IDENT
COBOL
INCODE

3154203, DATDY

s

IBMC

(COBOL Source Program Deck - JCVSRP)
$
$
$

s
s

EXECUTE
LIMITS
SYSOUT
TAPE
DATA

DUMP
15,32000
A2
A3, X3D, ,POPFILEI, ,XXXX
Al

(Control Card - RP)
$
*** EOF

ENDJOB

14:

XXXX - reel number

JCVS USAGE FORM
Function: JCVSRP
Computer: GE-635
Operating Philosophy:
Stage:

Compile Source Program Deck and Go
OUTPUT
TAPES

A3

A4

A6

)
Population File

CARD INPUT

"AT

N/A

PRINTED OUTPUT
A2

CARD
READER
EMPTY

N/A

AUDIT
FILE-RP

CARD OUTPUT
A5

Standard
Carriage
Control
Tape

L

/•

x

146

i

"

I PUNCH FILE

. ,

I

V

_

N7A

JCVS USAGE FORM
Function:

JCVSRP

Computer:

GE-635

Operating Philosophy: Load Binary Deck and Go
Stage:

INPUT
TAPES

A3

()
Population Fife

CARD INPUT
Al

A4

A6

N/A

N/A

PRINTED OUTPUT
A2
Standard
Standard
Carriage
Form
Control
Tape

i

/:

CARD OUTPUT
A5
CARD PUNCH
READY

( JOB DECK
•/

. . .. .•

JOB DECK STRUCTURE

0)

(8)

S
$

IDENT
3154203, DATDY
OPTION
COBOL
(Binary Program Deck - JCVSRP)

S

EXECUTE
LIMITS
SYSOUT
TAPE
DATA

s
s
s

(16)

DUMP
15,32000
A2
A3,X3D,,POPFILEI,, XXXX
Al

(Control Card - RP)
*** EOF

ENDJOB

147

XXXX - reel number

JCVS USAGE FORM
Funcfion:

JCVSRP

Computer:

GE-635

Operating Philosophy:
Stage:

Load Binary Deck and Go
OUTPUT
_TAPES

A6

A4

...JTJ

K/A

CARD INPUT
Al

PRINTED OUTPUT

A2"

CARD
READER
EMPTY

AUDIT
FILE-RP

CARD OUTPUT
A5

T
] Standard
, Carriage
1 Control
Tape

/:::v

i

i

i

-

148

:
:

1

I PUNCH FILE

L_ _.
IS/A

!

V

'

JCVS USAGE FORM
Function:

INIPOP1

Computer:

GE-635

Operating Philosophy:
Stage:

Compile Source Program and Go
INPUT
TAPES

A3

v..

A4

A6

I

SCRATCH

CARD INPUT

SCRATCH

PRINTED OUTPUT

Al

A2
Standard
Form

/
:: /
JOB DECK
j

CARD OUTPUT
A5

' Standard
Carriage
Control
Tape

...._. J

t -

N/A

CARD PUNCH
READY

t

JOB DECK STRUCTURE
(1)

(8)

(16)

$

IDE NT
COBOL
INC ODE IBMC

3154203, DATDY

$
$

(COBOL Source Program Deck - INI
IN POP)
$
$
$
$
$

s
$

EXECUTE
LIMITS
SYSOUT
TAPE
TAPE
SYSOUT
DATA

DUMP
15,32000
A2
A3,X3S
A4,X4R
A5
Al

(Control Card - 1P)
(Current File- PF Deck)
$

ENDJOB

***EOF

149

JCVS USAGE FORM
Function: INIPOPl
Computer: GE-635
Operating Philosophy: Compile Source Program and Go
Stage:

OUTPUT
TAPES
A3

A6

A4

f
\
Population File

CARD INPUT
AT
CARD
READER
EMPTY

N/A

SCRATCH

CARD OUTPUT
A5

PRINTED OUTPUT
! Standard
, Carriage
: Control
Tape

t~

150

!

/__

A

j PUNCH FILE-•ip
1
V
(Optional)

JCVS USAGE FORM
Function: INIPOP1
Computer: GE-635
Operating Philosophy: Load Binary Deck and Go
Stage:

INPUT
TAPES
A3

I
I

(

\

CARD INPUT
Al

.1.

PRINTED OUTPUT
|
A2
Standard
! Standard
Carriage
Form
Control
Tape

./

.

/

SCRATCH

SCRATCH

/

A6

A4

JOB DECK

V
JOB DECK STRUCTURE
(1)

(8)

(16)

S

IDENT
OPTION

3154203, DATDY
COBOL

$

( Binary Program Deck - INIPOP)
S
$
$
$
$
$
$

EXECUTE
LIMITS
SYSOUT
TAPE
TAPE
SYSOUT
DATA

DUMP
15,32000
A2
A3,X3S
A4,X4R
A5
Al

(Control Card - IP)
(Current File - PF Deck)
$
***EOF

ENDJOB

151

/

\
/

N/A

CARD OUTPUT
A5
CARD PUNCH
READY

JCVS USAGE FORM
Function:
Computer:

INIPOP1
GE-635

Operating Philosophy: Load Binary Deck and Go
Stage:

OUTPUT

A3

Q

Population File

CARD INPUT

A4

Q

SCRATCH

PRINTED OUTPUT

Al
CARD
READER

A6

1

i AUDIT
FILE-IP

EMPTY

Standard
Carriage
Conl rol
Tape

N/A...

CARD OUTPUT

PUNCH FILE-IP
:/

(Optional)

(Optional)

152

JCVS USAGE FORM
Function:

INIPOP2

Computer:

GE-635

Operating Philosophy: Compile Source Program and Go
Stage:

INPUT
TAPES
i

A4

A3

A6

/'
C,

/.

SCRATCH

SCRATCH

CARD INPUT
Al

/

/.'"
JOB DECK

1

[Old Population File

PRINTED OUTPUT
A2
Standard
Standard
Carriage
Form
Control
Tape

:

CARD OUTPUT
A5
CARD PUNCH
READY

i

/

JOB DECK STRUCTURE
(1)
$
$
S

(8)

(16)

IDE NT
COBOL
INCODE

3154203, DATDY
IBMC

(COBOL Source Program Deck - INIPOP)
S

s
s
$
$
$
$

EXECUTE
LIMITS
SYSOUT
TAPE
TAPE
TAPE
DATA

DUMP
15,32000
A2
A3,X3S
A4,X4R
A6,X6R,,POPFILEl,,XXXX
Al

(Control Card - IP)
(Current File - PF Deck)
$

ENDJOB

***EOF

153

XXXX - reel number

JCVS USAGE FORM
Function:
Computer:

INIPOP2
GE-635

Operating Philosophy:
Stage:

Compile Source Program and Go
OUTPUT
TAPES
A6

A4

\

I
Old Population File

SCRATCH

CARD INPUT
" A1
CARD
READER
EMPTY

PRINTED OUTPUT
" A2
r

Ii

CARDOUTPUJ
A5"

Standard
Carriage
Control
Tape

AUDIT
i FILE-IP

L

l

J

(Optional)

154

i

/

PUNCH FILE-IP /
V
(Optional)

JCVS USAGE FORM
Function:

INIPOP2

Computer:

GE-635

Operating Philosophy:
Stage:

Load Binary Deck and Go
INFJT
TAPES

a
A3

l '

CARD INPUT

i"

A4

A6

PRINTED OUTPUT
;
A4
Standard
Standard
Carriage
Form
Control
Tape

Al

CARD OUTPUT
A5
CARD PUNCH
READY

JOB DECK

[..

_J

JOB DECK STRUCTURE

(D

(8)

(16)

$

IDENT
OPTION

3154203, DATDY
COBOL

$

(Binary Program Deck - INIPOP)
S
$
$
$
$
$
$
$

EXECUTE
LIMITS
SYSOUT
TAPE
TAPE
TAPE
SYSOUT
DATA

DUMP
15,32000
A2
A3,X3S
A4,X4R
A6,X6R,,POPFILEl,,XXXX
A5
Al

(Control Card - IP)
(Current File - PF Deck)
$
***EOF

ENDJOB

55

XXXX - reel number

JCVS USAGE FORM
Function:
Computer:

INIPOP2
GE-635

Operating Philosophy: Load Binary Deck and Go
Stage:

OUTPUT
TAPES
A3

A4

A6

~N

I

—rj
New Population File

CARD INPUT
Al
CARD
READER
EMPTY

J

SCRATCH

!
| Old Population File

PRINTED OUTPUT

CARD OUTPUT
A5

Standard
Carriage
Control
Tape

/
I PUNCH FILE-IP' /

I

_1

156

L

(Optional)

J/

JCVS USAGE

ORM

F motion: POPFMl
C omputer: IBM 360-50
C perating Philosophy:

Compile Source Program ar d Go

S age:

INPUT
TAPES
" ~'i
!

SYS004

SYS005

i

s

SYS007

/"

i

!

I

C,
N/A

SCRATCH

N/A

i

CARD INPUT

PRINTED OUTPUT

SYS001

/:
JOB DECK

SYS002
Standard
Form
'

c

i

Stanc'urd
Carriage
Control
Tape

CARD OUTPUT
SYS003
CARD PUNCH
READY

J/

J DB DECK STRUCTURE
/ 'POPf Ml, JOB (799,028,010,1084,10,5),ANT<3HAGNO,MSGLEVEL = 1
/ 'SI E> EC COBFCLG
/ 'COB SYSIN DD*
(COBOL Source Program Deck - POP :M)
//GO.
//GO.
/ /GO.
/ /GO.
//GO.

SYS002 DD SYSOUT = A
SYS003 DD SYSOUT = B
SYS005 DD UNIT = 2400, LABEL =(,NL),DISP = (, CEtP),DSN = POPFILE1
SYSDUMP DD SYSOUT = A
SYS001 DD*
(Control Card - PF)
(Current File - PF2 Deck)

/

]57

1

JCVS USAGE FORM
Function: POPFMl
ComputenlBM 360-50
Operating Philosophy: Compile Source Program and Go
Stage:

OUTPUT
TAPES
SYS007

SYS005

_.:n
) Population File

CARD INPUT_
SYS001

PRINTED OUTPUT
SYS002

CARD
READER
EMPTY

! AUDIT
FILE-PF

Ly

Standard
; Carriage
Control
Tape

(Optional)

N/A

CARD OUTPUT
SYS003

/-

I PUNCH FILE-PJ^I.
_....
V
(Optional)

158

JCVS USAGE FORM
F' notion: POPFM2
Computer: IBM 360-50
Cperating Philosophy: Compile Source Program and Go
Sage:

INPUT
TAPES
SYS004

SYS005

C i

Old Population File

CARD INPUT

SCRATCH

PRINTED OUTPUT

SYS001

z:

SYS007

| SYS002
' Standard
Form
"i

\\

Standard
Carriage
Control
Tape

(
N/A

CARD OUTPUT
SYS003
CARD PUNCH
READY

JOB DECK

JOB DECK STRUCTURE
//POPFM2 JOB (799,028,010,1084,10.5),ANTCHAGNO, MSGLEVEL = 1
//SI EXEC COBFCLG
//COB. SYS IN DD*
(COBOL Source Program Deck - POPFM)
//GO .SYS002 DD SYSOUT = A
//GO .SYS003 DD SYSOUT = B
//GO.SYS004,DD UNIT = 2400,LABEL = (,NL), DISP =OLD, VOL - SER= 000649
//GO.SYS005, DD UNIT = 240Q/LABEL = (,NL),DISP = (,DELETE)
//GO.SYSDUMP DD SYSOUT - A
//GO .SYS001 DD*
(Control Card - PF)
(Current File - PF2 Deck)

/'

159

JCVS USAGE FORM
Function:

POPFM2

Computer: IBM 360-50
Operating Philosophy:

Compile Source Program and Go

Stage:

OUTPUT
TAPES
SYS004

L

Old Population File

SYS005

SYS007

New Population File

CARD INPUT

J>RnvJTED OUTPUT

SYS001
CARD

SYS002

READER

AUDIT
I FILE-PF

EMPTY

N/A

CARD OUTPUT
SYS003

Standard
Carriage
Control
Tape

/

{
i PUNCH FILE-Pf/'

I

(Optional)

L._

160

(Optional)

- A*

JCVS USAGE FORM
Function:

SELECT

Computer: IBM 360-50
Operating Philosophy:
Slage:

Compile Source Program and Go
INPUT
TAPES

SYS004

SYS007

SYS005

r 1
s

\

\
L

SCRATCHJ

Population File

CARD INPUT

PRINTED OUTPUT

SYS001

L

SYS002
/«!

/
JOB DECK

N/A

Standard
Carriage
Control
Tape

Standard
Form

i i:
L

l...

CARD OUTPUT
SYS003
CARD PUNCH
READY

i

L.

•j

JOB DECK STRUCTURE
//SELECT JOB (799,028,010,1084,10,5), ANTCHAGNO, MSGLEVEL = 1
//SI EXEC COBFCLG
//COB. SYS IN DD*
(COBOL Source Program Deck - SJCVS)
//GO .SYS002 DD SYSOUT = A
//GO .SYS003 DD SYSOUT = B
//GO.SYS004 DD UNIT = 2400, LABEL = (,NL), DISP = OLD, VOL -SER = 000649
//GO.SYS005 DD UNIT = 2400, LABEL = (,NL), DISP = (,KEEP), DSN - JOVSP
//GO.SYSDUMP DD SYSOUT = A
//GO.SYS001 DD*
(Control Card - S)
(Test Selection File Deck)

A

161

JCVS USAGE FORM
Function: SELECT
Computer: IBM 360-50
Operating Philosophy:
Stage:

Compile Source Program and Go
OUTPUT
TAPES

SYS004

SYS005

SYS007
/

.... :j

Population File

CARD INPUT
SYS001
CARD
READER
EMPTY

[Source Program File

_PRINTEDOUTPUT_
SYS002
AUDIT
FILE-S

s

j
| Standard
Carriage
;
Control
Tape

(Optional)

162

V

L

N/A

CARD OUTPUT
SYS003

f

{

I PUNCH FILE- S1 /
!
/
(Optional)

JCVS USAGE FORM
Function: SOPMM
Computer:'BM 360-50
Operating Philosophy: Compile Source Program and Go
Slage:

INPUT
TAPES
SYS004

SYS007

SYS005

f N

V i
Old Source Pgm

_

File j

CARD INPUT
SYS001

I

! z:::zz A
Jj
V I
L:

SCRATCH

PRINTED OUTPUT
SYS002
Standard
Carriage
Standard
Form
Control
Tape

N/A

i

CARD OUTPUT
SYS003
CARD PUNCH
READY

JOB DECK

4

L~.

JOB DECK STRUCTURE
//SOPMM JOB (799,028,010,1084,10,5), ANTCHAGNO, MSGLEVEL = 1
//SI EXEC COBFCLG
//COB. SYS IN DD*
(COBOL SOURCE PROGRAM DECK)
//GO .SYS002 DD SYSOUT = A
//GO .SYS003 DD SYSOUT = B
//GO.SYS004 DD UNIT = 2400, LAB EL = (,NL),DISP-OLD,VOL = SER = 000570
//GO.SYS005 DD UNIT = 2400,LABEL = (,NL),DISP= (,DELETE)
//GO .SYSDUMP DD SYSOUT = A
//GO.SYS001 DD*
(Control Card -SP)
(Current File -SP2 Deck)
/*

163

JCVS USAGE FORM
Function: SOPMM
Computer: IBM 360-50
Operating Philosophy: Compile Source Program and Go
Stage:

OUTPUT
TAPES
SYS004

Old Source Pgm File

CARD INPUT
SYS001

i

(New Source Pgm

File j

PRINTED OUTPUT
SYS002

CARD
READER

SYS007

SYS005

AUDIT
FILE-SP

EMPTY

r

N/A

CARD OUTPUT
SYS003

Standard
Carriage
Control
Tape

r
1 PUNCH FILE-

/

t
I'

(Optional)

(Optional)

164

JCVS USAGE FORM
Function:

JCVSRP

Computer:

IBM 360-50

Operating Philosophy: Compile Source Program and Go
Stage:

INPUT
TAPES

a
SYS004

v I

L

SYS002
Standard
Form
/

JOB DECK

Population File

PRINTED OUTPUT

SYS001
/

i

CARD OUTPUT
SYS003

! Standard
Carriage
Control
Tape

CARD PUNCH
READY

},
!./ !
.. J

-

t

N/A

N/A

CARD INPUT

SYS006

SYS005

t

JOB DECK STRUCTURE
//JCVSRP JOB (799,028,010,1084, 10,5),ANTCHAGNO, MSGLEVEL = I
//SI EXEC COB FCLG
//COB. SYS IN DD*
(COBOL Source Program Deck - JCVSRP)
//GO .SYS002 DD SYSOUT = A
//GO.SYS002 DD UNIT = 2400,LABEL = (,NL),DISP = OLD,VOL = SER = 000649
//GO .SYSDUMP DD SYSOUT = A
//GO.SYS001 DD*
(Control Card - RP)

/*

165

JCVS USAGE FORM
Function:
Computer:

JCVSRP
»M 360-50

Operating Philosophy: Compile Source Program and Go
Stage:

OUTPUT
SYS006

SYS004

\

Population File

CARD INPUT_

PRINTED OUTPUT

CARD OUTPUT

r

CARD

I AUDIT

READER

i FILE-RP

EMPTY
!

Standard
Carriage
Control
Tape

r

—i

166

./

PUNCH FILE

./

J

/

/

4...

N/A
I...

JCVS USAGE FORM
Function:
Computer:

INIPOP1
IBM 360-50

Operating Philosophy:

Compile Source Program and Go

Stage:

INPUT
TAPES

a
SYS004

N/A

'

SYS007

r ,

!

V

I

/.

SCRATCH

SYS001
/, •

SYS002
Standard
Form

/:

V.

I.

SCRATCH

CARD OUTPUT

PRINTED OUTPUT

_ CARD INPUT
f

SYS006

\ standa,d
Carriage
Control
Tape

SYS003
CARD PUNCH
READY

JOB DECK
!/
I

i

.

..t

JOB DECK STRUCTURE
//INIPOP,JOB,(799,028,OLD, 1084,10,5), ANTCHAGNO,MSGLEVEL=l
//SI,EXEC COBFCLG
//COB.SYSIN DD*
(COBOL Source Program Deck - INI POP)
//GO.SYS002 DD SYSOUT = A
//GO.SYS003 DD SYSOUT = B
//GO.SYS006 DD UNIT = (2400, DEFER), LA BEL = (,NL),DISP = (,DELETE),
//
DSN = MSTRFILE
//GO.SYS007 DD UNIT = 2400,LABEL = (,NL),DISP= (,DELETE)
//GO.SYSDUMP DD SYSOUT = A
//GO.SYS001 DD**
(Control Card - IP)
(Current File- PF Deck)

167

JCVS USAGE FORM
Function:
Computer:

INIPOP1
IBM 360-50

Operating Philosophy:

Compile Source Program and Go

Stage:

OUTPUT
TAPES
SYS004

SYS006

SYS007

/

V._ ..'1
.New Population. File

CARD INPUT
SYS001
CARD
READER
EMPTY

PRINTED OUTPUT

CARD OUTPUT

_SYS002

i
I Standard
AUDIT
Carriage
FILE-IP i Control
/'-"•

SYS003

t

IT

Tape

168

//

"""
-

/

1 PUNCH FILE- -IP
!
[

(Optional^

/

>

i
i. .

(Optional)

! /

JCVS USAGE FORM
Function:

INIPOP2

Computer:

IBM 360-50

Ox-rating Philosophy:
St 

L.
(Optional )j

1

170

/
I

L

......

...... i'

(Ojstional)

APPENDIX II

SYSTEM HEADER CARD 2

This appendix contains the System Header 2 cards which contain the JCVS model
number and the operating system name for each of the five computers.

171

GE-635
OVIAL COMPILFP VALIDATION SYSTEM 1

GTCOS

'"^r' J Ar "."

SCOPT

P•1A'

MCP

P.'Ti/-." •;•

FXFC2

O^nj/

CDC-640C
OVIAL COMPILER VALIDATION SYSTEM 1

,'

B-5500
OVIAL COMPILEP VALIDATION SYSTEM I
UN I VAC-11 OB
OVIAL COMPILER VALIDATION SYSTEM 1

">;•

IBM 360-ljO
OVIAL COMPILER VALIDATION SYSTEM 1

HASP

System Header Card 2

172,

nr^i//

.

APPENDIX III

ENVIRONMENTAL HARDWARE CARDS

This appendix contains a listing of the three environmental hardware cards associated
with each of the five computers. These cards contain tape designations, core sizes and
print control character designations when applicable.

173

GF-635
VI

vs FOP CAPPS
Wf

A2 FC^ LIST I Mr,
A3
A6

65K

or^]AOP
p o p 1A 0 0'
onpiArtAt

CPC-6400
[NPUT
>UNCH
rAPC?

OUTPUT
TAPF1
TAPF3

01137K

oro ] A^^'
or^\;. r n /
n r o l A o f '.

R-5500

rAPF

PPINT^P
TAPF
TAPF

65K

o r r l /'••:'• •
00 01 Aoo/
n^r<) ,\ -> r i

UNIVAC-]108
rAPD-RFAHFP-FIGHTY
CAPD-PUNCH-FIGHTY
JNISEPVO 13

65K

PRINTFP
UNISERVO A
UNISERVO C

or" ] AfO'
0 00 i AoO<
0 0 0 1 A • > C'•'

IBM 360-50
• SYS 001 • UNIT-RFCORH 2540R
» SYS003» UNIT-PFCORO 25A0P
»SYS0P*« UTILITY ?uon UNIT

•SYS002• UNIT-RFCORD ?5U0P
»SYS004« UTILITY ?AP0 UNIT
»SYS006« UTILITY ?/+00 UNIT

Environmental Hardware Cards

17*

6 5K

000 1 A 'C
r\ n 0 ] A i"' O i
onr]A ' 0'

APPENDIX iv

ENVIRONMENTAL SOFTWARE CARDS

This appendix contains a listing of the opercring system control cards and the JOVIAL
control cards required to signify a JOVIAL source program.

175

Gr-633
- ^,-JL
-. -. ,iL
- - ,- i L
nrnir" 1:
'' r > I T' i •

IDFNT
3154203»PATDY
JOVIAL
FOPTPAM
r
xrcuTF nt'MP
LIMITS 1[J,35000
r
^njon

••

;.

,-. •.:

*EOF

Environmental Software Cards

176

.•

- -^ir

17

- •>.-, j r •

1 •

APPENDIX V

TYPICAL MODULES

This appendix contains a listing of a few typical Population File modules.

177

'•MODULE 5220
••TEST USE OF
ITFM FA522C F
ITEM FC5220 F

- CED 2454 '•
FLOATING CONSTANTS.VARIABLES "
P 1.0$ ITEM FB5220 F P 4.OS
P 0.0$

IFEITH FA5220 EQ rB5220$ GOTO LZ5220$
0R1F 1.0 EO FA52205 FC5220=3.0$
ORIF FA5220 EQ FC'J220$ GOTO LZ5220$
LA522^9 ORIF 1$ GOTO LZ5220S END
IFFITH FB5220 EO 1.0$ GOTO LA522PS
ORIF FA5220 EO 1.0$ GOTO LB5220$
ORIF 1$ GOTO LZ5220S FND
GOTO LZ5220$
LB52209 IFEITH 1.0 EO 2.OS FC5220=1.0$
ORIF 2.0 EO FA522PS FC5220=1.P$
ORIF FB5220 EQ 2.0$ GOTO LC52201
ORIF 1$ GOTO LZ5220$ END ''ERROR IF HFRF"
GOTO L7522P$
LC522P9 GOTO LY5220$
LZ5220.
0UT1=40H( MODULE 5220 TEST FAILED. CED2454
)$
OUTERR(OUTl)$ GOTO LX5220$ ''EXIT''
LY5220.
OUT1=40H{ MODULE 5220 TEST SUCCESSFUL.
)$
OUTERR(OUTl)$
LX5220.
••MODULE 5230 - CFD 2454 ••
••TEST USE OF STATUS CONSTANTS•VARIABLFS••
ITFM SA5230 S V(A) V(R) V(C) P V(R)$
ITFM SB5230 S V(X) V(Y) V(Z) P V(Z)$
ITEM SC523H S v(NO) V(YES) P V(vfS)$
ITEM SD523C S V(NO) V(YFS) V(MAVBE) P V(YES)$
IFEITH V(A) EQ SA5230$ GOTO LZ5230S
ORIF SB523P EO V(X)$ SC>230 = V ( NO) $
ORIF SB5230 EQ SA5230$ GOTO LZ5230S
ORIF 1$ GOTO LA5230$ END
GOTO LZ5230$
••ERROR••
LA5230. IFEITH SD5230 EQ V(YES)$ GOTO LB5230S
ORIF V(A) EQ SA5230$ GOTO LZ5230S
LB5230. ORIF V(YES) EQ SD5230$ SC5230=V(NO)$
ORIF 1$ GOTO LZ5230$ END
»»rRPOP"
IFEITH SB5230 EQ V(Z)$ GOTO LC5230$
ORIF 1$ GOTO L252305 END
"ERROR"
LC52309 GOTO LY5230$
LZ5230.
0UT1=4PH( MODULE 5230 TEST FAILED. CED2454
)$
OUTFRR(OUTl)$ GOTO LX5230$
"EXIT"
LY5230.
0UT1=40H( MODULE 5230 TEST SUCCESSFUL.
)$
0UTFRR(0UT1)$
LX5230.
"MODULE 5240 - CED 2454 "
"TFST USE OF TRANSMISSION CONSTANTS»VARIABLFS "
ITEM TA5240 T 2 P 2T(AA)$
ITFM TB5240 T 2 P 2T(BB)$
ITEM TC5240 T 2 P 2T(
)$ ITFM TD5240 T 2$

i7a'a7

522PAO0:
522?JCC'<
52<>CJCP:
5?20JC>^'
5?20J^r'
522PJ00<
5220J00'
5220J0PI
522nJ^P<
522^J0li
5220JO1
b?2fsJn\'.
522PJ^1
522pJPl<
(
j22"J^il
522CJM.<
5?2rjny
5?2"JM I
5220J^1'
5?20J02i
5220^2
522PJ02,
5220J02
5220J02
5?20Jn2
5220^2'
523PAPP
5?3pJnp
5??r»Jnp
•»23pJ(,P'
5730J•
523nJrpi
52'J0J'0
S?3ojMp
523"J('P
523PJ' i
523pJ< 1
523PJri
5230J: 1
5230JP1
523PJP1
523*JP1
52'50j:>]
523PJP1
523PJM
523PJ"2
523pJo2
5230J'*2
523^J"2
5?3PJ'^2
523PJ02
5240A00
524OJ0P
524PJP0
5?4"

i

i

2.4

Executable Statements
2.3.1 Control Statements
2.3.1.1
Unconditional Control Transfers
GOTO
STOP
2.3.1.2 Conditional Control Transfers
IF
IFEITH
ORIF
2.3.1 .3 Iteration Control
FOR
TEST
2.3.2 Input/Output Statements
INPUT
OPEN INPUT
SHUT INPUT
OUTPUT
OPEN OUTPUT
SHUT OUTPUT
2.3.3 Replacement Statements
2.3.3.1
Assignment Statement
2.3.3.2 Exchange Statement
Compiler Directing Concepts
2.4.1 DEFINE
2.4.2 LIKE
2.4.3 OVERLAY
2.4.4 MODE
2.4.5 DIRECT, JOVIAL

JCVS Testing Concepts
The following sections discuss briefly the scope of the JCVS and the tests selected for
inclusion in the Population File.
JCVS Scope
For purposes of the JCVS, the JOVIAL system to be tested is assumed to consist of a
processor that compiles standard JOVIAL source program statements called the JOVIAL
compiler and all programs and subroutines used by the JOVIAL object code generated from
standard JOVIAL statements. The JCVS is designed to test both the compilation and
execution of specific JOVIAL features.

186

Test Assumptions - Data
The foregoing JOVIAL language organization has guided the identification of language
features to be tested. In order to validate the JOVIAL compiler ideally, each variant of
a specific language feature should be validated. The validation of each feature variant of
the JOVIAL language, however, is not always possible. For example, how can one
determine that any value stored in a floating point item is truly stored as a floating point
number; how can one determine that a fixed point constant has actually been converted
to a fixed point binary point constant. Looking at information as it resides in the internal
storage medium, we may observe a string of bits, however, the interpretation of this content
is inconclusive. Consequently, some of the features provided by the JOVIAL language are
not susceptible to validation independently. These featur es are generally the more basic
notions in the language and will be used constantly in the Test Modules comprising the
Poulation File. With repeated correct usage of these basic concepts, it is hoped that the
credibility of their required implementation will be considerably improved.
With these thoughts in mind, the following aspects of the data definitional capabilities
of the JOVIAL language will not be tested independently and will be assumed present in
the language and correctly implemented:
1 .
2.
3.

The ability to specify any item type and have it retained according to its
defining attributes.
The ability to formulate any constant type and have it retained according to
its defining attributes.
The ability to specify any data structure type (table, array, etc.) and have
it retained according to its defining attributes.

The JOVIAL language provides the user with a myriad of options to form constants, simple
items, tables, and arrays. There are so many data defining attributes possible in JOVIAL
that exercising each option in an independent test is quite impossible. As a compromise,
the test repertoire will use a subset of data definitions that exercise, at least once, all of
the data attributes available to define data items and structures. In addition, the
repertoire will utilize every variation provided to formulate constants with the exception
of the dual item definitions which will be exercised in part only. It goes without saying
that the formation of acceptable JOVIAL symbols (names, labels, etc.) will be exercised
every time a symbol is formed.
Test Assumptions - Procedures
The JOVIAL language provides the user with the ability to process formulas and relations;
it provides for program organization and it provides certain compiler directing features.
Every variant of each of these features will be tested at least once. Further substantiation
of the ability of a feature to perform its intended function will be supplied by its correct
use as a support statement in other test modules.

187

With these thoughts in mind, the following aspects of the procedural capabilities of the
JOVIAL language will be assumed to be present in the language and correctly implemented:
1.
2.

The ability to name a statement with a label.
The fact that normal procedural control passes from one JOVIAL statement
to the next.

Test Hierarchy
Although the language organization serves to compartmentalize the various features of the
language, it remains for the test hierarchy to specify the order in which these features are
to be tested. This order must be specified to insure that the supporting JOVIAL statements
used to compare test modules in which they participate may be validated.
A further ordering must be prescribed when testing out data and procedural language
elements. Since procedural statements, for the most part, make reference to pieces
of data, it seems reasonable to assume that data declarations should be validated before
procedural statements. As a general rule, when a data concept is to be validated, it
will be defined, structured, preset, and referenced since these are the only data oriented
concepts languages provide. When a procedural statement is to be tested, it will be invoked
in order to examine whether the procedure performs its stated functions.
There exist language concepts that are inexorably linked together; switch declarations and
switch invocations; procedure declarations and procedure calls, etc., that individually serve
little useful function but when utilized in combina ion provide a powerful programming
tool. These notions will be validated fully.
Axioms
The validity of JOVIAL test features must be detemined by the execution of a number of
JOVIAL statements called support statements. Since these statements are themselves JOVIAL
statements, they must be validated as is any other JOVIAL statement. Once a JOVIAL
statement has been validated, however, the statement may be used to check the results
of the validations of other JOVIAL statements.
Following is a list of these JOVIAL concepts that are required as basic axioms.
to:
1 .
2.
3.
4.
5.

The ability
•

Define and preset a hollerith item.
Assign a hollerith constant to a hollerith variable.
Execute the GOTO statement-name.
Define a procedure, invoke a procedure, and return from a procedure; input
parameter list, one variable.
IF clause.

These axioms will be validated first.

188

Following the Axiom validation will be the validation of the data and procedures. The
complete order for listing including all DDI-NO references and all CED-NO cross
references is given in the Test Hierarchy Outline.
Test Modules
Although the concept of test modules has been described in section 2.3 of the Users
Ktanual, that description will be repeated here.
A Test Module is a collection of JOVIAL statements that test a particular feature of the
JOVIAL compiler. The feature may be a JOVIAL concept, a single JOVIAL statement
or a collection of JOVIAL statements. Included in each Test Module are the:
1 .
2.
3.
4.
5.
6.
7.
8.

Test identification field
Input test data fields
Test results fields
Expected results fields
Initialization procedures
Test statements comprising the test
Results analysis procedures
Output procedures

Tost Modules are located on the Population File in order of their test serial number, the
DDI-NO. With each test statement is associated a sequence number within the DDI-NO
that specifies the ordering of the statements within the DDI-NO.
In most cases, a Test Module can be considered as an independent JOVIAL source program.
There are instances, however, when the data to be operated upon by one Test Module resides
in another Test Module. Consequently, in these cases, the JOVIAL source program is not
independent. Exit from all modules passes through the last statement of the module to the
first statement of the following module or the TERM statement. Because of this feature,
a JOVIAL test module may follow any other JOVIAL test module.
Mandatory Modules
Seme test modules are not independent in the sense that they may be included by themselves
in a generated JOVIAL source program. These test modules depend upon other test modules
cc lied mandatory modules in the Population File for either of two reasons:
1 .
2.

The mandatory test module contains data definitions that are required by the
dependent test module, or
The mandatory test module contains support statements whose validity must be
established before a successful execution of the dependent module feature may
be considered valid.

189

the five support statement Axioms are considered to be constantly mandatory and consequently
are included in every generated JOVIAL source program.
All other mandatory maodules will be invoked by specific test modules. Every mandatory
module will be invoked by at least one test module and the relationship between test modules
and mandatory modules, if any exist, will be enumerated in the Test Hierarchy Outline.
Test Module Content
Each Test Module will be identified by a test serial number called the DDI-NO occupying
columns 73-76 of every card in the T -^
o

•£

CO

- ?0)

U

I2 -o*

o
I

**• -o

CM

g> 91

.O

D
C

*•

c

00
1

<
>

CO
1
CO

00
1
-O

CO
1

•—

•—

CO
1

i—

1—

-st

00
1
^T
1
O

CO
1

CO
1

CO
1

00
1
•*
1

1
CN

0

1—

CO
1

1

-*1
CN
1—

CO

0
CO
1
-0

1
CM

.—

hen
rese

— o
c -^
E Z

ver
leri

£ «°c c
.2-c
3; *•
CO

<

t—

U
<
C£
<
X
U

I

8"o

y

0)

u

u X
V

,£ _c
Qi
UJ

o
o
co
CM

CO

1

1
CO

r—

hs
1
CM

1—

•—

00

CO

co

^r

1

"v

c

b
z

8. n
b

<>

n

o ~o
u <1>
n
ni

• I)—
u
o

c >*
o -*>

3

V "O
O

z> o
o_ o
o •-

CL T3

C

«.

CO

o
zI

IT)
00

a

CO
CO

-B.?

CO

_ p

CO

t o

=5

o

c

X

l/>

_

<
LU

X

*•

CN TJ
<0 c
CO o

-o ^

owing syntax will be performe
reference to some of the uses <

c •£

CO
LU

1—

X
<

—

z

a)

>
LO

•

«—

u•*-

0)
1—

0)

0)

il

_s

O

o
c

IT)
CO
—
«0

O
CN
V)
CO

"8o

II

IT)

0)

o
a>

•O IT)

O lO lO
V) — CN
IOOO
>o CO •£ — 't TT

1)

o

so

so

V

^ In
>o CO

o o o u
C
io o ©
o
— •*• Tf

io io

IO If) IO

o o

1

—o

CO IT)
ir> co

—

-<*

•*

8oo 2 8.« 8io oo2 oco°
CN

8.
CO

00 IO _c

•0 V? ion

o_
u

0)

a>

4-

••-

-o
c „

lO o
-O -*J"

o

"2
-te
c Q.

•*-

I"

0)

» —

co

o
O lO o c
o
COiiO
IO •O
«0 CO o

3 8

o

o o

i-

CL
0)
V

"* Tl" —

o
^8
^- ^ ^- -* —

1-

-u
c
o
-•-

lO

^ CN

IO
O
IO
—

IO

C

IO IO IO lO <1J
CN N (N Tf t
CO CO 00 ^ 3
lOlOIOr- •£

a>

a>

1
^oooooo
*!
.2 Tf 5 CN CN (N r- .2
«-coiococococo_c

^ — I- lO — IO IO IO IO I—

in

in

f>

O
c

c*: co Z u

u

O

sts of
ovide

h—

0

">
4)

-O 7=

a)

a)

1—

fl)
_5

TJ

•—
>
o

c

he VG riou
spec ifiec

>

in

1

•te

o

-*—

O

_J
1—

T>
0)

in

cT

CQ_I^.Q£coijt>X_JUjSEZ
<<<<•

zzo
LU UJ LU

§2
-r
LL. *LU

[LOGO

3o
CO

o
o
o

CO

m
in
o

m
o

o o

m u->
MD oCO CO

R

m 10

o o

co co

I

11

in .jo
co w

• in
73 CO 73

73

o '?
— o

•fc
CO

•4—

>

*
,/,

o "°

2 a
0)
o

o £ o
CM
O
-

O CN
u
—
© "t

CM

o

^

c
0)
"D
C

o

CN
CM

u

O

«!-

— .E oo
° •= 3
in

c

Q
o «*o

8

a>

°l

-8

• "i

c

01 CN
w> ^*
ID

1c
u

I

co in in

co

•— CO CO
TJ- in in

D

in
N
—
t

o
CN
CO
in

o
CN
CO
in

Q

73

!»
co ^
o

Q.

, om

•Jj — CO
£ CM —
•* o

CO CO CO
M3 o  hi
MD

73

in
in

§12

73
C
o
-*—
o_
noininin coo

in co in co o >o in o in ^ •* i- in in t— MD
5 ^- In t—

2CN

,2 .!2 8

o
•<»•
in
CM

o o o

2
8

c
— in
— CM

m

•TJ

v

i|8_s
CO
tv

o
c
•O
CM

-fc
CO

o

2

O
c

MJ

o
-"t
o
CO

m in in
co co co
MD o in
co CO CM

73

co r^ co

0)

S-8

o
"
o
o

8>o

o o
o o

o

x
u

g

m in
co

9

in m
o
CO

o
cs

in in
in

CM

"<* -<*

o in o co
co co CM o in

>n in

5

<

o
u. I— UJ oo y o
o
oc ex. 3 >
oo oooo o

O- Z

E

5* 2 l-

X h- h- i— S <. LU LU
DC OO OO OO OO OO
UJ

c?
3£
CM

197

«

in in

+

o
. o
v> to
0) <0

lO lO

m o

"*t "*t

 "^" "*t"

o

o to
E
•O lO ^_ to
CO

o o

3
"0
o
o o
o
E
lO -O .,_
in

V

 «o <

to o *• o o IT) U") *CN
r- O >o o —
IT) CN
f) iO< IT) <0

o
O
•**•
"«t

o
O
-*t
"4

O O
oo oo

to

o
o
in
«o

O

lO

E
4)

o

to

o
E
>-

_Q

C

^i w

to

lO

o
o
«o
v>

k>

=

OJ

co

0)
-*-

i

lO

lO

oo

^*o «

5
S?

o
ro
—

5 52

o
D

ir> u-> in
CN CN —
ui Op Op
O
,

^-^- tt>ioo o> "^ v •—

D

IT)

c
o

~



>

_Q

O
O

<

_l

198

a;
C

o
o

Z

oo

ro

i/>

o

>—

CN

ro

CO

•*

—

CN

•*

^t

oz
1

•~~

1-1

o
o
lO
o

'O

o
>o
o

o
,—
u->
o

LO
lO

o

o
z

o
CN
in
o

I

Q
Q

OiOOU-)OU-)OLO

oooooooo

_0J
D

"§
E

o

<

a

I

Q
LU

z
fi

'5
cr
B

?

2
UJ
1—

T
LU

co
UJ
Qi
I I I

c

X
LU

(—

•—

LL.
LU

1-

<

i—
oo
h-

z

LU

2

7

z

O

u_

co

a

<

5
z1

<

<
h-

z
£

Q
Li

3

u

LU

o

LU
LU
CO

3

0
h-

LU

<

U

u

a

Z>

LL.

LU
Of
LU
LL.

CO

8 8 S=^
D O


a.

b

E

LO

a>
c

CN

CO

CN

CN

u-

D

0)

is>

7

n

lO
CN

CN

CO

CO

199

c
o i_
11
n _u
o fc

-+-

u-

O

CM


o

1.3

/

2c

co

E g
0) *-

LU

c£

CO

o
o

0)
XI

LU
CO

CO

a
U

^•MfO'fiOONCO

cocororocooooooo

o
z
Q

o
zI

OlOOiOOiOOU")
OO-i-NNOlCO
CNNCNCNNCNNN

OlOOiOOiOOLO
OOr-^CM(NCOn

Q

a

E

E
0)

E

0)

_0)

i3

E |

Q.

_E
in
-*-

— m z. a>
a>

Si

g
—

£ 8
STL

I

E
a> c
^ o E £
"J» a> —

T:

c
a>

.e
2 **: c
E „ o
w

5 _cu

.* § O el §
L_ Q X — to oQ

E
0)

E
a)

2

I

CO

"ID
C
D

c

E

E
0)

g
8
Ll_

E E
r
a;
-•—

u
c
o E

-i-

X

u_

E(^

i/i

2L

E
a)

en
c

c
o

'~0

8
"O
i_

0

200

0)

_c
-*—

O
i/i

V
_Q
D

fc"

D
C

l_

o
u
c

o

U

CN

_Q

_Q
D

o
c

D

cocooooococooooo

a

0)

i/>

c
o

"E
Q
(so-^tNco

8.
-»_Q

s
CD
C

•—

V> V* */* *A V* */» W V* V* V* W tA W W «/* «/V V> V> 4a** V» V* «/} V> V> V>

j

Z5QIQ5Z,5OZ5ZQ5Z2QZ5O...i
v) w io i 1/ii/xni/iQ-O-o.a.Q.Q.o.
I

I

I

I

I

I

I

I

I

I

I

I

I

I

I

I

I

i

i

i

i

I

I

I

I

I/O Q-

I

I

I

o

l

0

I

'c'c'c'c'c'c'c'c'c'c'iE'c^'c'c'c'c'c'c'c'c'c'c c c
c
o
o
u

>>>>a£c£a;a;>>>>a;a:a£££ci£a£>>>a:>>c£
-I-

0) 0) U V

o

9)
a> v a> a>
a> a>
E E
E E
E E E E
E E
ooooooooooonnooooooooo
o

I g 1 g
g g g
o o o
zzzzzzzzzzzzzzzzzzzzzz z z z
ill

III

I t 1

I

>OISNCOO.O.— 

fl>
jj

—

-^
C

"P
C

;;;:;;;;:;:;;;:;„;;;;:;;

j

CMCNCN(NCN(NCNCNNMCNNMWCNMCNtNMCNMMCN(NCN

"g

&

m n (o n (ri co n n ri n n co n co ri n to ri ti n «' ci n <*) cn

O

£

CN

£

~
co

%
Q

u

201

•

LO

<>
'
o in o
o o
o
o 1
r

o
z

~~

_l_

OiOOiOOU->OiO
OO — — CM CM CO CO

Q
Q



oinomoioou-)
cocooooo.— .—

OU-)OiOOiOO>0

NNNNNNNN

•

o

o

CM CM CO
00 00 co

NNNN0OCO0OCD

OO

OO

oo

E
0>

E
u
i:
E *.
_ r
o 0)
^ »/»
E .t:
O

> I

>- E

2i

E
i
„_
c
-n

01

£ 8
o 2 £ LZH

co

<
c
o
•-

in -7
m Z.

T

E

£

I
c:

0)

E

o
E

d)
 c P "" •=

UJ
_l

"8

Ol-EttJ_.-«nD

X (— — LL U. I/I CO Q

CO

o
X

<

CM

CO

CM

CM

CM

CM

CM

CM

CM

CO

CO

CO*

CO

U

202

c
o

E^l^ E
2-2
— i; n
in
n
co

in in

~"

o

Q

m in
o o
m

in in in
r
1

I—

o
zI

CN
in

in

'

5

in
in

1

1

~~

o o
'"""•

^~

m
o
c
o

in in
in in
in in
1—

*+—

88

CN CM

z

D
0)

o o o o o
in m o •n
CO
o O o
00
•n >n in <> in in in in
in in

o
-o
co

O

in

I—

in o
co -<*
in in

o

Q
Q

in

8

in o
o —
m u->

CN CN CN

o
-»—

Q-

'l_

o

in



0)
"D

CN CN CN
i
1
1

_4>
r>
D

g

c

~5

O

9i

E
a;

E
E*

S *-

E

"8

E 2z
— c

E U
« c
^ o

c «£ E «
o
°- r-

0

0) —

-^ T;
Ho"??
U_ LL. CO CO Q

o E =
s. 0)
L7" *•

o

x _o

UL LL.

c

co
c

E
E

-oa> ^
n

•*-

1

1

c

c

,—

1—

c

c

4—

o
o_
. co

—
-*-1

&.
>»

4)

4-

o_ CO

1

i/i

-4-

— c

1

Z>

CD
C

w to

5
4O

CO

0)

c
o
-*-

- E
c £
o —

it0)

"° S
<2o

a
 Z.

u4)

-a
0)
c

3

E

^ro
co"

g i

1 zf

-*M-

o

UJ
_1
CO

in

_0)

I— 1— h-

o
1—
c-*—

c

LU

-*-

c

"O
V

c
0)

c

co

u0)

CO*

Q

LU LU
_l _l
CO CO

< < <

Q

O

Q

203

o

~o

'E

 > >

'*

o
!•

•— CN CO

o

0)

.

iZ.

E

in
in

o

D

z

•

p_

•

,

•

CO CO CO
CO

co co

o

8L
X
E

O
Q-

o

O

LO
CN
LO

oo

O

z
Q
Q

LO
CN

O

z

IO
.—
LO
CN

O
CN
lO
CN

IT)
CN
IT)
CM

O
CO
lO
CN

O
-4—

8LO

Q

IT)

CN

o

O

CN

CN

o
o o
CN CN CN

LO
LO
CN

—

u">

O

CN
lO
CN

LO lO LO
CN CN CN

CO
LO
CN

c

.1

CO CO VI CO

u0)

CN CN CN CN
I
I
I
I

Q

c c c c

co Q-

I

I

I

co

«/>

CO

CO

CO

CO

CN

CN

CN
1

CN
1

CN
1

•+-

CN
1

CN

-4C

c

C

1

1

Q_

CO

-|__

_o
"o

I

I

c

D

1

Z

c

c
o

1c

'

8.
E E E
o o o

U

E

5

E

r Item
me
V

>

V

Z Z Z Z

0)

o

°>Z
c

CO

CO

CD

CO

< < < <

»— 1— 1— I—

'Z.

u

1—

c
«-

II

in -7

"t LO

o t^

r—

^—

•

•

1—

r—

CO CO

ro

00

CO CO CO

oo

•

•

LU
_J
CQ

_Q

fr
c
o

c

<

c

1

J! b

c
o

b
T)
0)
X

0)

o

Z

E
d)

D

z

X

b c
E o u

c
o
i-

Z

o
o -*-

CO

CD
4)

Z

C

•"*•

LO

CN

CN

CN

00

CO
CO

co
oo

oo

oo

oo
oo

00

Io

u_

Q

b

H-

<
t—

o

l\

CN

CN

oo

0)

o

<

•
•
oo
•

oo

CN

1—

b
~o

LU
_l
CQ

<

o
b

-z
8Z

LU
_I
CO

1—

Osj

204

O

1—

CN

u
c
Q o

b

D

4)

CQ

0)

LU
_J
CQ

^—

IV

-*—

LU
—1
CQ

<

U

b

b

L1J
_J
CQ

<

h-

E

"in

u_
LU
_J
CO

•5
on

<

H-

LU

c

g

b

a; a; oi a;

e
o

c

•+—

c

C

1


co

o

co CO

o

LO

8
O

CN

<>

o
co

CO

CO

|
M-



_Q
D

c

LU

c
o

"o

«-

2-5-5
E^ I?•
.5 Ja S
oJ
I- _ u. u. w m Q

l/>

4*
to

c

u

CD
C

1

O)
0)

>

E
D

O
1—

LU

-o

£c I

J

u-

3

U-

O

8.
"5

co

|

CO

c£

co'

E

LU
_J

o
z

CD

ac

<

iH
LU

CO

c

CO

K- CO

c
o
i-

—

,_—
•
r—

c

1

"c

•-—

0)

CO
1

Q
D-

c
E

0)

c

u
c
o

E
co

-»-

c -*-1

D
CO

> "5

_c

c
a

'E
CO

O

CO

t/1

o

> E



"D

az



co
m

co

E
a>

E
a)

<*1

CN

^J.*->

"—

z

co

c
—
' *
c E

1

c c

1

1

"»_
•4—

.5 „ o —

-*c

0)

i

t •*-

E «

co

c

E

IE

.2 || £ E '

CO
1

CO

-<*

CO

c
E
E*
± c

CN
1

"*
"*c

-•_ _!_
C c
•— •—

~o

E

CO

Mo
co

0
CO

I

o

LO

"*
-o
co

"Nt

CO

to

U")


Si

-

•»

oVo

LO
I

O

I

z

"£ -y 1=
.EZ.

Q

»h- to ._ to "5
•2: <
»— to

en
I—
to

en
I—
CO

Q

£ a

to

—
to to

•—
"O >o

CM
>o

hs t-X

CO CO
co' CO
co' co"

co

CO CO

CO

CO
co'

CO CO
co" CO

co'

CO CO
CO CO
co" CO*

CN
to
CO
co'
co

"8

E £

E 2
£ .5
.E •- '== E 535 _ ± „ g .5

Z •£

LU

E
0)

a> c a. E i:
«o no E"
* *r
tt> — E
' E I a) ^£ S —
0)

it
If
.1
z
o
Z

CO j^

I

oooooooo

2 <•>

-o

zo •Ez — no Z. z
z
f
in
o Vo V o
i.C
-z .1 z
•ISLS
I—
< I—
< i— c tt

0)
CO

CO
0>

4)

>

17

COCOCOCOCOCOCOCO

i

o
c

I

o

0)

.x

*.

o

E
0)

CO

CM

co
CO

o

E

—

CN

CO

CO
I

4

z

CO

OOiOOQLOiOlO
— CMOCOOi— CN CO

?

c

nE

IT)

-o
co

o

o
o

>o
^o
CO

I

c
o

o o

IT)
O
CO CO

<

CN

u

206

CO

in

8
o
CO
m
00

LO in
CN -*
in

8

co

UO

o
**

lO lO
CO CO

UO lO

O

o

UO lO lO
CO CO CO

o

zI

Z

Q

•O Q o
CO O
in ir> lO

3
3

5

9uo

CO

Q
Q

•

co
o

lOQuomoiooinoio
inionouoioioiououoio
cocococococooocococo

CO

CO

on $
escription

$

&

X

c
o
-»-

•bO

E

Q_

E

"C
o
(/>

<

V

C

-o
E

o
•u
—

a

.9- E co
h
« -*—
C
u *:
v»

a>
T3

'5

C

uo

r-~

i—

1

1

1

-t-

-*-

c
o

•*-

>- >- >
C£ Qi. C£

< < <

~o
'E

<->-

o

e
<

-;;

o

1

1)

c

E

1

•

•

z

Si
C

D

in
O

CO CO*

co

C

i

<

U
CM

«*

<*

u-

"+"

CO

00*

&

co'

c

S5
.E
O) CO .«_

i:

a>

i

o

CO

-^iii*-

"
E
•-T3
""
a> a>CO

i — •£

i

CO

o
>>>>>>>>>>£
2 2 2 S 2 & 2 2 2 2 f> *
<<<<<<<<<<< u

e
u-

— CM CO

E

X

<

<

1/1

c

14-

0

D)CM CMCNCMCN () CN M M M
0) I
I
I
I
I — I
I
I
I

13

o
It
o
c

232

o

8

£ £ £ ~ .£ 2 JC 1 -I £ .£

X
"4—
E
0
•-

c c c

CD

c

«* " " a> "• •£

CN
1

t—

«~ ~ ** £

o

c
_c

(J

«
*/>

S

g d) » £ JJ

*•

•—

E7
i! c

I

j

•z ^

c
o

c

L-

c

o
tz «-

o—

1*1
^ 5

CN CN CN CN CN CN CN CN CN CN CN

8 Z
_o
U

t*-

0)

207

•*

"t

•<(•

^1" •^t

•M-

-*

•*

•t "«t "

11 § if
fI?i £ £ Z ft
s. oo c

0)
T3

 Co

c
0)

u

CD

I •- £

«.

I |

0)

•r o Si

*: to

tO

*

.t *

CD
C

E

£ 2 SL- £•£ jpl I

5^

E

u

*

CO
LO
CO

-8

0)

a o "a

X

u
t—

D O
to to _ to 1/1

1

»

o

_C _C _c

X

•*-

o
/

•*-

to to to to t/1 to

U

Z

X

LU

8• -i Q§ to-fc-n coo° z -8-8-8-8-8
c c c c c

T3

UJ
UL-

"»

——

UJ

XXX

X

c

<
I—

c

r-Mr)Ttio

-£>

-C
U

S
i)

-

SI3

g

0)

-4_

-*-

-8
4>
CD

to

in

oL

a)

E E

f f-«= f f 1
o

O 1/1

_c
E v> „ r-' °
« E -c y 'N.

0)

0)

E E

o

* «"

o

0)

c

merit
teme

1

to b J.

c
a)

o
-a
c
o

I

mentment-

0)

'o
c

Swit

CD
C

o

mentment-

CD
c

1-

r-



<

u

LU
Q_
CO

CD
0)

o
D

>

208

4>

•u
—

O

E

C

o
z
I

Si

o
o
o
^t-

If
4J

O
O
•*

i?
c
'o

T
p

eger
ed p

."tz



O

o
o

M-

to

_D

-8c

^_ J_
c c
4)
c
o o
CL a.
E E
o o
o o
o a;
* c

s

!
C

'i
in

c

_4>

X


? c

s

o
0)

?
4)

ua>
i_
— CM 00 T}-

UJ
1—

E

D

U

"* "* •«*•

T}-

UJ
1—

en

>-

4)

CM

1
IZ

"*

>

CO

5f

-C

 E
c

i-

o

•£ 2
Urn
0)

d)

11

X X
0) 0)
"D "O

X X
0) 0)
"D TO

T3
4)

wv>

c
a>
c
o
a.
E
o
o

-D

s

-2

J

-4-

c
a)
c
o
a.
E
o
o

o o

a> o

£ £

§£

c
—

1
-C

-^
c

c
o
-1c

8.
-8
8
lc
o

1

i_
— CM
CM CM

•

CO ^t
CM CM*

•

•

ac
<
X

u

u

oo

D

209

Li

D

o

0)
ui/>

u_

IE

c
o
> c

•—

at.

f

z

c
f—

z

ULJ

c
o
>•

4)

o
-*-

4>

•o

EFFE

E

• —

"5

-8c
LU

-*c

8

O

c
o

•

4)



C _c

•*-

ol

J!

CO CO ._ 00 CO ._

•—

CM

SI

E

.t 5

>>£>>• «

lassi fica
Nu mbe

c
o

o

o
«t

Co Co

UJ

u
c
4>
c

o
c

lO
CS

c
o

c c
^_ -t~
c c
8o 0)co
a. Q.
E E
o o
u U

"l-

en ca co co

Z

•*

E

*•* *« tA*

1\

o
o o
IT)

00 CN

c "C
o 0)
"tO
to ~o

-o
c
o

a

X
4>
"D
C

1"
JU

4-

Q

o
00
o
^

-C

T

X

X

Si

E
o
o
o

<•> vo t<» «^v
X
(1)
T3
C

o
zI

8
8.

an

t—

z
LU

jz

"*•

1—

^J"

LU

4)
4)

t4_

E
>•

an

I—

z
UJ

4)
O
"O

—
o
>

c
o
o
u
to

_o
CJ

IE

1

i
E

z

"*
•<*

•«t
^J-

O

z

Q

I

CN Tj- >0 00
CN (N M CN

^t ^ ^ 5

O (N t vO CO
CO CO CO CO CO

^ ^ ^ ^ ^

X
X

"O
c
n

>Ci

£•

c_
« c 1
a,

5 I £
S 1"-

I i s>°
a CD_? o
•» "w o x
_ < UJ _

c c cS!
o o o —
c c c c

x

E

4)

-*- o
CL
c

0) E
c o
o u

o

c E
a, o
c
o o

It
Is
° to
II
o o

0

d) —-

•a

i

2

c
0)

o

I£

CD
C

I

c c

1 |
fT

O 5 m - ^ _Q _Q
o a
j_ —'
O c °° "o it:
«



a,

CL

0)

o

c
l_

f-

O

-•—

o o

o

CN CO Tfr lO

o Jj
1)
l/>

-4—

=

**•

C

l/>

E

I
0) _tt)

I

0)

§ I

00

E

C

ai —'

.E

•8

c

c

15

c
o

~

oo J>

D

*•

££££

«•> Z

c

erne
erne

8.

a>
u
c

D

7

— CN CO •«*• in
4)
_£)

E

"* •* "«t •*
<* -*r -^

D

z

TJ-"

u

u

CN CN CN CN CN
•>*

"*•

-*

^f Tf

"^

<* Tf

-*

•*

c

l—

~o

LU

z

a,

CN

CO

8

D

210

>-

io

CN

5

o
zI
Q
Q

0
O N Tf •OOO O
-** -^ -«t -* ^ lO

1

^ TF ^ ^ ^ -5

Q

I

I

IflO.

I

I

I
I

I

I

I

CM "*J- >Q CO O CM
IT) IT) Ifl IO >0 O

LO CL.

I

I

I

GO Q-

I

i

I

i

I
I

i

I

I

00 CL.

i

i

CO 00
Tt > > > oc &. a

> > > oc at at

0)

E

g

2i

'g g g g g g

E
E

UJ LU UJ UJ LLl UU
J J J J J J
rcy rfi rf\ ff\ rf\ rf\

LU UJ UJ UJ UJ 11 I
—I —I —I _J —J —J
m ff\ rn cCi rO flQ

<<<<<<

<<<<<<

—• CM CJ

o

u

T|-

IT) »0

CO CO CO CO CO CO

c
o
-*o
o

w "

O OO O
O)

p- (N CO t "1 O

%

y

a>
_n
n -*—
n
*—<•
*—* *—'
U U U U

8>

c
o

5

LO CO

Q

^ ^ ^ ^F Tf ^*

I

I

Si V Si Si Si Si

to -r

o

^

z

w v» v* <»o w

II

00 CO

o
^

u
O

c

c

_i

LU

OJ
u-

?

?

££
CL.

0)
D

LO

—

^4"

>

O

c
o
*~

1-

•^ _
E

14-

•-

D

S3 Z
O
_

u

.— CM oo ^
IT) LO to ir>
"*

•*

"*

-<*

O
I
Q
Q

z

Tf NO
00 00 O-

5

^ ^ -5

Q

8u-> o m o u->

e

V
-C
•a

fe*V  v* */>

8.

i

i

I

i

i

Ji/i D.w a. i
_Q
O

i-

tt) « c

CD

'i
_o
"5

c
o

aj

U U U
—1 —1 —1

c
o

K Z
_o
U

-3

u

2

e

-C

4)
>-»-

1

h-

u

lO >0 hs
•

t

•

•* -M- •**•

LO Q-

O
CD
C

'5

_o
~o

Z_J_J_J_J_J_I'7_J_J

2L

ooo

io m >o

g1

A????? 8 ,s> 8 8

a

IT

•

8
„ V O i i
4, JL J. A 2. i. 1 * *. 4

c

T5

8.

"_«?«?
%C. •11
— •—

dinary ta
me R
me R
me V
me V
me V
me V
"ined Enti
me V
me V

E

o
c

CO CO
CM CM

-a _ _

-*-

li?

o in

O — — CM CN
CN CN CN CM CN CN
•

y—

Z
<
5

Hi

o•

u>

<*

3

O

_c
1—

1—

Z
LU

z

tN

•

•«t

LU

z
0)

u
c

E

•^•t— i— t— t— i— i— -*-»— i—

OJ

fi
Z

c

o

8-8
•- E

it1/1 —75
20 z

p- (N CO '"t U1 O

— CM

— — ,— .— — ,— _ CM CM CM

Z

IsNNNNNIsNNS

co

u

LU
CO

Q

o

—
o
>

00

212

5

o
zI
5

o
z

O
o in o ir>

zI

-*

Q
Q

o
o——
CO CO ro CO

Q lO O
^ Tj- lO

"* ^t "*

«^» *<«V  > c- >

n
~>

l_

I g I g

4)

O

CQ 00 CD 00

c

it §
s Z
_o
U

•

c

O
-D

c
o

o

CO CO 00 CO

Q
O

O
o

QO

_o

O

Q Q Q
Q Q Q

•

-«t "<* "* •^r

•*-

c
'u
c

— CM CO -<*

•

>

ooo

o
•

JS

o

a> a>
x o
c
o
<**~-^ ^•^

Q

< < < <

_Q

n

O

D) T3

g g 2 g

-D

a> at

JQ

o
c

c
o

•— CM CO

5!

OS CN OV

0)

~

«>

7",

"** •<* "^

o

Cs
CO

CO CO CO

i.

o
O

D

>

213

c
o

*—

3

ifl -7
in Z.

a

U

>o

10 u">

o
z1

^ ^

Q
Q

ON ON

o

4

i

o
m
^
<*

«0
00

3

o o-

5

5^

Q

O
tX

*-c s-£

u

o c

Io

*:

0>
U

0>

°E
S -5

o

O "O

O)

s.

3

1—

1-

9

_0>

2

'5.
E
o
u

<

O
Od

o

C£

_c

2
o
o

Qi
Q-

>
m

<

o
o

O

•

lO

v>
3

-u

v>

15
o

o

0)

u

0)
1—

E

v>

3

Z

lO lO

CO

o_
"O
4>

c

"O

tfc

u
c

r— CM

3
O-

O
i_

T>

1

-4-

"O
9)
O

Q- Q-

o

Q-

CXL
Q.

lO

e3

8 2

o

8.
i

•

0)

UJ

2

i

i e

c
o

^r

cc:

U


-*-

o

e

3
"O
4)

u
o

3

3

uO

c
o

0>

o

3
-C

E

CN

"O

lO

IZJ

(I)

ii

(1)

LO

3

o
a> u_^

i—
i
V)

Li
0)

iE £i

£

E
a
c

U

O

8£

3
o_
c an
CL.

v>
v>
O

o
L-

3
O3

o

0>
_Q
O

8.
3
Q- 4-^¥

C

^
0)

E
a
c

V»
0)

VI
0)

c c
fi fi
a>

U-

d)

HJ
L-4-

0)

C£ Q£
>N 0)

*'

i

i

v>

V>

VI

_l —1
U i_
0) 0) 0)

_l

O

a.

-i

00

^r

3

CN

CM

CM

CM

Z

lO*

UO

»0

lO

O _5

3E -°
.2
i_

i_

aj

aj

1

1

-4—

-4~

V)

v>

IZJ Hi
a>

at

—

—

ii

- E 1 E E E
jjj E E E £ £
nj a_ a_ Q_

U

d) 4)
t^ e*

£

1

ai

a> g
0) JJ

3 o o

o
> < i—

E

CM

214

0)
Qi

i

—

o
0)
_c
(J

c

ar IT

-4-

Q-

3

u

U

Q-

CM

•4VI

u
c

*-4-

eE 2tt)o
3

0)

Q.
-*-

3i
O)

to

C

1

o
c

v>

0)

E > 8.

ROGRAM
ROGRAM

z
o

-4-

OC name
OC name

E

>-4-

^t "Nf "Nt "Nf 'Nf
-Nf "Nf ^ ^ Tt

<«•

>*

0> -Q

o —

e

z

O

S o

V

c
|o>
o
o
-4-

•*vi
—

u-> o o in o
tO ON 00 ON NO

U")
I^N

^

OO

c

>N

^

Z

c OO

""

IT)
OO

P
«-

-4-

•*-

^ 3 3 *. ir
Q- D_ Q. 3 3

8.£

c c

OO

I

Q
Q

z
I

o o
CO o

o m o io

E E
oi
u
c

o>
u
c
0) a)
l_
i_
a> a>
w- i-i_
ai oi

O

3

o
LU
Di

Oi Qi

x

.*-

L-

<

II

E

D
"D
0)
O
O

Q. CL
-4-

-*—

oo

01

c

01

D
O

0)
O)

01

E
O

z

i-

i_

0)
CD
0

01
CD
0)

C

C

C

T

*»

o

D

c

01
C
M4)
T3

0)

Q
O

i_

i_

i_

1-

0)
CD
01

01
CO
0)

0>

01

c

C

o
a;

co CD
a> 0)
c c

— -—-

en

oooo

?

52

s



c
_o

22

o
c

an Di a; o;

D
U-

CM CN CN CN

-o
01
c
«:
01
Q

oi

c
o
o>
o

.2-|
a Z

CN CN CN CN

IO IO ") IO

in

C

o

U

o
c

d,

t3

c

13

3

D

Si
c
o

2E

01
CD

CO

CO

in

in

z

0)

_c
-X

215

8

0)

o

o
01
_c

D_ O

qj

I-

E ^_2! S) JJ —
o£ c oo t9 so ^S
o oo _ X Q

8

u

CN

c
o
D

3 3 3 3

U

LO

a)
•*-

-—-

0)

D

CN

C

"_"

E E E jfl

oi

o

e

i_

0)
O)
0)

o
o
i
oi
CD
«.

•—

c
o
0)

o
c c o
o CD

o
Q_

o

o
D

u
c

D
u_

CD

c

1/1

-*-

eJ
c

Ll_

0)
X

<
CD

c

l-

0)
CO

c
o

t3

c

•4-

3.
c

u

i
E
r>

Z

CM

_
CO

m

C

o

0>
CD
0>

t3

(1)
C

8,

o

CD

c
o

^oo
„, co

c

E
ai

E
0)

E
OJ

^
n

•

D
CD
C

•<

O

u

•*c

o

0)
CD

oo

- —
I

o

-D

III III III LLI

a; a; o£ c£

c
o
LU

oo

O

1-1-

o
CD

8

c

3

u

0)

c
o

4)

o
c
r>

si

c

Ll_

D

0)
•— CM CO

c

1-

•— CM CO CO CO CO

1E

<1)

CM CM CM CM CN CM

Q

c
o
o
(J

D

1/1

-C

t>

i

0)

—I

u

*

_v°T 7 7 P.
"O
0)

•
LU

_i

-

-•c

c

OO
CO

3

c

o

-4-

'E

CD
C

c
o

<

nteger it<
ger = A
integer it
integer it
integer it
integer a

a.

Para mete r List
Boolean Formula

"O

O
w>

o

z

o
OJ

8

CO CO CO CO CO CO
lO lO IT) o

a)

3

u
oo

0)
_C

CM

o

co

4)

CO

U
0)

U

in

u

216

in
OJ

3

"8

E
_

_o
'u

8-c
o >
c —

O)

s.

SJR

o
1

uS

o

o

* 1

o
 ._

_c
«*.

r- CM CO

8.

o

o _2 5 "Ic

.*- "7?

o a
o <*.S

\—

_c

i Hi E J

O g

OJ

E

E|

V)

z
o

OJ

a>

a £
O

—I

u

E

I

CD

i- ? £."£

t*

£ "O

Qi fl£ Q£

u

o
u

•*-

Z Z Z

o

I

8""

£

E E £
o o o

D

OJ
y
c

oo <*:

«
o -o K
O
0)
o
I1/1 MM
Q. 3

OJ

«,

E
..
OJ

-B-8
«

E

O

•*-

o
I—
o
o

•*-

CO

%>'CO *D ">
3 *•

_0J

c
o
o
(J

^
"oi

0) £

O

*• TJ

U

-D
(/i

— CM CO •<*•

Q_

"l *~. "~. "I

»—

O O O O

LO

U

_c
U

o

217


«

u -3

CN

>o

8.

3
D
(J

<£

O
o

zI

CO
CN

Q

a

o 10 O lO

w> m >o o
oo ^ t -«i- -

0)

0)

1
—
— i

i o>
_2 -2
•4—

Si

D
O

i«._»

±t

_Q

5

o

 E 
E O P

c5

 ± .2 o
P 0) .= IA E TJ
J> co +: D >2 0)

2

o

o * 8 o p .?<

tn

o

Z

O

*

m

8.

Q-

J

l/>

>.

-o
*- o
4_
c £ __
92 .2 o
O t*.

E

E
o
u

35
3
r> ^

X

8.

io

"D

0) U_

oo

.4-

J: IL

w i- <
0)

c
o

8
U

a;

CO

a
0)

o
0)

u

II
_o
U

c
o

a:

CM

en

•

ro

o'

o
V

X
h•UJ
II

a)

CO

8D
_

u_

>*•
o

I E
jo
U

r- CN ro ^ io >o
*0 ^) ^O ^ 'O *o

a.
o
o

4)
CO

SID

O
_y

o
0)

-d

U

218

u


* io cococooocooooooo

Q

00
lO
CO
lO

O
O
CO
lO

3

-OOOOM

CM
<0 OO CO
lO IT)

c
o
o

oPO

at

o
at

OO

»9 99gg

u

O

£

i
ui

o
c

— --&&
I
' at at
I a;

^
SO O

00

21

Q;

0 ^ oo

"- LL. O O LL. LI-

u_

^=o

O LL. OO

P ° 0>«
0)

s

U c

o

u u_

4) LL. LL.
0> 01

?s

\7> O

c

"io

F

c
o
u

0)

L_

•—•—•£
•DTJ'J

?*£

C C >
O O at
at at O

(J •

OOu-

Z LL. LL.

Q;

o

at c£ at

I

C)

o o
8. u t3 t3 o
o o o o o

o

o

0 O O
O

u

Li_

I E
it 5
S Z

tf)ioioioioioioinioinioinioioioioio«nioio

c
o
U
a
o
o

•O *0 ^) *0 ^) ^) •O >0'0^N0'^*0*OsOsO,OsOsO>0

o
c
o
o
o
01

_c

^
o

219

01

_c

U

11

o
^~
u
o

*

4-

* *
a)

a>

_Q _Q

O
1-

o

O
u

o

> >
O
O

O
O

c
o
01
a _Q
o
t4-

O

U

_J

Di

o

01 Ll_
U
-C

01
-C
+•
u*_

o
L-

.— CM CO -*f lO

Ll_

01

O

^-

Q£

OO
LL. LL.

c

c

.C JC

— CM CO "**•

^CMCO-^J-lOOt^OO

c

'

c

o

—> _i

D

Oil

O .^xi^.j.j.j

a. o.
o o
o o

c

O

LL. LL.

1_

o

> >

01

U-U-O OU.LL.-DO O O o "- _0 LL. LL. LL. LL.
a, 0)"-  "" LL. LL. LL. j,
o> ID 0) 01
o£ oi 4) g c

Z JE -c

o

01

c o o 2 2

0)

0) 0>
JD ^3
D O

0)

LL.  .
T5 -7; ° °
*r -Q -Q — —

1

o •£ p
LL. O U
° o
J> u- tu

O
O
LL.

D Xl

_J_

•- •-

i I .£ 11 i * 11
I 1« Ini ioi II £Is ee° °ifi

s 8 -o

atatO

O U- u_
ro

io u-> uo m

Q.

D

«=

O^ O^ o o

o

o

TO .E .E

a

CO CO CO CO

_o

u_
1= ^ ^

25
2>
.E

O CN Tj- O

Q

•4-

O
o
LL.

z

CO CO CO CO

g

C
o

o

c
o

E
n

Z

r- M CO Tf

o o o *o
•o ^o -o >o

o
z

o 10 o
o o —

Q
Q

>*

"**

iooiOir)ioioir)iOio

in ir> in

IT) IT) IT) IT) IT) to in

M(Y)C)-O

•*!-

if) IT) lO

N N 00

(DCM>OO^r"uO.°
E

1—

1

c
o

O

in
m

Ll_
LU
Oi

3

s

LU

y

o

£

2

e

o

8.3 o
O .2 > c p
u

z
o
o;

O

0)
tQX

c
o

p

i-i
= 3

3

o
U

1-

e

z

S3l

2L.2>

8. Oo>

o c
> "5

^- in _Q

•

•»

.5 **-P
O



O

> _» -c
C o >

£|l=

O

.«•;: £O;-E rj-8
.5 .2 >
"5
a. "*o •*-c

+

I

* <:
I

*

m

n

+'

I JJ

in

a

o

O

_Q
u> O

D
D

c -P tt) 'z ' _0) -c >
. o
_Q O
O _Q
<_ «*. TJ
c o ~a S -2
o">.E .2 •>
a °
\~
• o *C <- O
'o 
o
£ o> >
u CL. c
i; -O 0) 0)
5 '•£ O 5
4)
— D)
8o o
O 0)

S>

l>
o>
c *- £
°"Z b
8 g •5 £ % 8 -S S i8 £^% • I 2
I x 8
TL£IL ix. tx. ca £ Z ^£
Z> 5£uZ
O)
C

>

IX.

LU
U

<" -n

••£ J» %

O m a

I*

I

P^
ON
•^p-^^rNnonno,)P)co(,3Pioo^,

IO
00

o >o O IO o

(N CM (•) tO Tf

co oo oo oo oo
io in in in u->

in LO

«, -Q

c
D
t/>

c/>

0)

c
o

C

C
O
t/>

C
O
i/i

.- "O TJ

~o c c c

3 O O O
Q *in **ft *«

i

-Q_i» «»
O

'£ 8,

a)
o o
E E E
CO
ID

o

c
o
>-

assifica
Numbe

*JI

o >© o >o o

c
o o n o o o
c c c c c tj
o o o o o ^

c
D
V)

C

o

DODO

o

8.
h

8.
E
o
o

o
U
Q-

E

0)

I

CN

c c

c
o

c
o

c
o

8_

o ±

E
o
u

o o o
D
cr

~o
!

N N N N

TJ-

E
o
U

o
_c
u
o

"D
0)
C
D

Jr

u

u

I/O

1

s

a> a>
oi a: cScScSO

c

0>

I**.* IN r«." rC t>»* tv r^

1

i

O OOOO 2 O-o

o

CO CO

i

in

X H=
i

8. 8. 8.8.8. e 8.-E

u o o
c c c
H  T
0)  > -(o o o
Q
Q Q aj o) a)
 a>

i

*!_
o
>

52 v> £ >2 i«

>

O TJ
C 0)
Q)
T> 0)
 .E > E
°> s "S — cn
J> x 8 g £

8
?

•TOO

QX

o «c > .2 £

c

o c c
o O U

3
£

£

_Q
O

O
4)

o

U

U

221

LO
CO CO

<>

^o

LO

o
CN

^ <>
co

o
r—

'O
O

<> 5 <>
o in
CO

o
zI
Q

a

o
O
o
>o

u->
O
o
*0

o
—
o
'•O

10
ro
"O

o
CN
o
>0

w>
CM
o
*o

o
zI

c
o

o
CO
o
*o

Q
Q

B.

O

o

5

CO
LO

in
CN

o o
CN
00 00
LO

>o

8

1

c
o

o
o

CO

e

o_

^~o
0)
>

•*-•I

•8
ot

Irt

0)

fl]

er Variable
1 Variables
ing Variabl
Variables

l/>

°> ^

•*-

^B.

£ s 8 g

£ LZ H Q

-Q
D
"i_

O

>

o
1_

-*-tnC
-*-o

o

c
o
U

D

Q

c "o

<

'

C

o

i

c
o
1-

11
o8 Z

J

r—
CO

CN
CO

CO -*t

tx

LO

CO CO CO CO CO

fx tx tx r-s tx

IX

rx

oo
h-

X
LU

c
o
4>

o
o

c
o

CD

o
o

o
o

•— Q

2
LU

z! rx
LU
Qi

CO

<

o
o

•
in

<

o

c

1Z a5

E

D

c
o

-<-c



-;

o

CO

5

.—

CN

CO

o

o
o

o
Z

I

8iOOiOOiOOU-)C?
Q

in o

O iO O U-)

5 «o

"*
v6 3 ^
-o ^
o

-o ^o r^ rx

5

_4)

_D
O _4>

_4>

c
o

_4>

8
58

o

-O

_4>
-Q

•

CD

.21-

—

o

a

o •£

>i. -cO -cII

u
o
>
c
o

4> > =

_4>

4> T3 -f
*: 4) -1-

O
O
OO

»!, o

'a

a

-£ .* 4>
4) "- 3
o o •£ •s §^ .2 15 _4> £
O

4> >

> -z -c:

O

«- O
0) >
CO _


4) H _Q
ja « .2
LU

o
z

II

o

ii

CO

4)

II
.2 _4>
_Q

J! > .«o
.2
.2
*i- "in
O

">

D

||

4>

JD
O

15  .t:
1

4)

-

4)

$ =

II

||

"§

"

•c

O

1>

O

J>

o J;

a
>
in
D

D
-*—

co

.2

LU

u-

X

D

<

X

o

4>

u

»—
-a

o o
> "
^ o

Q_
LU

U

CL

Z

zz

n
u

E
o
o

£>
i— i—
LU LU

4)

^3

I—

0

z
u

a
4)

LU

—
a

C

0

o
z

"•4-

LO

LU

4)

_>

a _2?

a •Z -Q

•.22'i£
> c
4>

4>

II .D
II
_4)
^3

0) _Q

w>

a

4> "S

>3
.2
c

4)

z
5

CO

oi
«
 2
o
O

o

S

_Q
D

_4>

c > £ U- X

*- > E
4> 4) 4)
4)
3
_Q _D _a
8
v
^
•£ .* o
6 B o.o o
_ u_ X Q i- oo on

X

I—
II
II
_4)
-O

_Q

4)

u

_4>

> -Q

2 >- °

_4>

Q

•II

O

D

II
4) -^
"3N
«

i-

c
o

o

o
u

»-»-

-5
E

z

4)

o

r— cs

co

Tf m o

(N(N(N(NCN(N(NCNM(N

CMCM

CM

CM M (N

oooocooocococdcococo'

00 CO

CO

CO coco

u

4)
CO

LU

z
o

LL.
LU

Q
o

u
CM

aD

4>

0)

o

CO

223

o

<©

o

>o

1

o

z

Q
LJ

o
z
I

LO

o o
o

o in o
o o —
NNN
•o *o «o

a

o •o

I

8

4)

C>CN

w *y> in

I

CN CN CN
I
I

°

g

| |

tO */>

0)

II
CN

II

li

(O
_Q

n

h-

a

0)

E
o

-O

n

i—

n

0)

15

£*-

o

4)

D

I

I

i-

0)

u

c

o

Q;

c^

Q;

ct:

D^

a
c

"

I

e i 11 g

gi gi gI gI gI

j) _«
.£> -a

X X 0)

•

c^ c£

p

c

o
u

3 *° °

E E3
2 2 o o 2
CN

c£ c£ ex:

_Q

a

c
o
c
o
o

F o

>- g>2 gs

•-

— CN CO Tf

iO>ON00O>

—

.2"!
it I

co co co co co

CO CO CO CO CO

CO

o

X

LU

V LU

c

o

•J:
CN CN
LU

>

o

u
c
o

a z

O^

_o

0>

c
0)

Io

S2 LU LU LU LU LU

it-

CN

P

O

>>>>> gooooo
£>>>>> \g O> 32 O> -St
ooooo

>

c
o

pa z
u

n

CN
I
CO

8I

UJ LU LU LU LU

UJ

— CN

o

n

R

o

1i

S32S3CNS33SS

'Q.

E
o
u

ll

ll

o

u->
^i-

hv

CN

>

m m

_0)

gi

E
0)
Q -*-

^ 15

g

E

_a _a E o O O ^O

E

c

CN
I

in o in o in

r- M N CO n

a

224

ON

O* 0s O*

CN

CN

CO

co

I si
U- _£ O
O 0 ^

file *

6!S

P o c
escri
f the
nsequ

tL*- v

TJ

O

Q

o

E_g>U

.et of
d be
chec

o
" £^

o

z
10
in
rv

Q
Q

o
"O
tv

^o

in
vo
hs

^o

p
tv
r>.

^

u->
i\
K

^o

*o

O
00

in o
00 cs

in
o»

<0

sQ >o

o

o

^

s§°°
o

-*-

•*•
•- _*

4)

8I

8 8
8 _?2

4>

E
11

8i

2i

7

T

e

"

e

8i

E

o
c
o
t»
c
o
o

c
D
to
C

o
u

2
c

c

c
o

p

c
o
o

c
o
u

•»-

c
o
v

p &* p <& p
o CM

><

_l
UJ

V

O CM

5 «* O

|

l>- 1 >- I

O

I OS

J

ii i

0) .•- II

i

I

-Q

E 2
t> T
11

7

a

1
4>

?2 85
•"*•* LU

i

o 2

b
o

II

II

a-

E E
D

3

>•

>•

c

o

I

£ .t:

JJJI

c

II

_g JS

E E

D
C

D
C

>>

° O °"
o c fi

-Q
O

ST
K Z

Q,

«

e

.-

1o

-8 8-5

II

c a) .r
.- _c *-

1

C

C

<_ UJ

2o

« 3 O

J!
S4)

o

*• M-

L.

« _y

^ 1 8
S !•€

<

'5.^

<

T>

0)

C

*>

O .- _C

CN

CM

CN

CN

co

CO CO*

CO CO

co'

CO

CO

co
o'

CO

CO

CO

CO CO

CO CO

CO

o"

o" cs

CS O*

o'

co
o"

o"

o"

u

z
o

l£%
•»-

co
o

I—
QUJ

E « .
o
> c
O 
u_ *-

>
> E>
O .tOiOS O oO §O9OO~OOYOVO
c
o

o

|J-8
5~S

I
_4)

—J

C OH Oi.
UJ UJ

D
w

.* TJ

8i

II

v~>

o
c

8I 8I
I

> %> E>

is is ? 5
I OS

CM
I
IT)

_Q
O

o
II

o
-*m

E
E 4>

i

8i

2i

_4>

4>

8I

f

o

spe
che
uire

I

I

D o
O _c

.2 J-u
O

CM

1

o

U

ggfi

poP

I

.

to

— E -o

3

o

4)

225

c
o
c
4>

JC

4)

Z

o -JZ - -*—
a* o_ 2 O
L_

z

"*• E Z
cs

-8c
o

2 « r "O
*- -a x 4)

CO -*f

4)
-*—
U
o
u
o
J:

.« D E
? *2 a>
t- o .- J

2

o
o

.8

Security Classification
KEY WORDS

JOVIAL
J-3 (J3)
compiler
validation

Security Classification

Security Classification

DOCUMENT CONTROL DATA

R&D

(Security classification of title, body of abstract and indexing annotation must be entered when the overall report Is classified)
I

ORIGINATING

A c T i V l T Y (Corporate author)

2a. REPORT SECURITY CLASSIFICATION

Directorate of Systems Design & Devefopment
Hq Electronic Systems Division
L G Hanscom Field, Bedford, Mass. 01730
3

UNCLASSIFIED

2b. GROUP

N/A

REPORT Tl TLE

USER'S MANUAL JOVIAL COMPILER VALIDATION SYSTEM
*

NOTES (Type ot report and Inclusive dates)

DESCRIPTIVE

None
V

AU

THORI3I (First name, middle Initial, last name)

None
6

REPORT DA TE

/«. TOTAL NO. OP PAGES

7b. NO. OF RE FS

234

July 1970

8a. CONTRACT OR GRANT NO.

IN-HOUSE
6. PROJEC T NO.

6917

»e. ORIGINATOR'S REPORT NUMBER(S)

ESD-TR-70-278
9b. OTHER REPORT NO(S> (Any other numbers that may be assigned
this report)

10

DISTR BUTION STATEMENT

This document has been approved for public release and sale; its distribution is unlimited,
II

SUPPLEMENTARY NOTES

12- SPONSORING MILITARY ACTIVITY

Hq Electronic Systems Division (AFSC)
L. G. Hanscom Field, Bedford, Mass. 01730
13

ABSTRACT

This technical report consists of detailed specifications for the use of
the JOVIAL Compiler Validation System (JCVS). The system is designed to
measure the compliance of a specific JOVIAL J3 compiler against the language
specifications in Air Force Manual 100-24, "Standard Computer Programming
Language for Air Force Command and Control Systems". This report describes
the card input formats, deck structures, tape requirements, test modules,
and operator procedures required to use the system.

DD

FORM

1473
Security Classification



File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : Yes
Page Count                      : 234
Page Mode                       : UseNone
XMP Toolkit                     : XMP Core 4.1.1
Metadata Date                   : 2010:09:02 16:48:55-04:00
Creator Tool                    : LuraDocument PDF Compressor Server 5.5.50.41
Create Date                     : 2010:09:02 16:48:55-05:00
Modify Date                     : 2010:09:02 16:48:55-05:00
Producer                        : LuraDocument PDF v2.41
Part                            : 1
Conformance                     : B
Document ID                     : uuid:uuid:00d38b9a-c0cf-a63f-e396-619dd292cbf0
Version ID                      : 1
Creator                         : LuraDocument PDF Compressor Server 5.5.50.41