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

G.

o

UJ

F

CO

UJ

ESD-TR-70-278

ESD

ACCESSION

LIST

ESTI

Call

No.

,

^^)

^5^2-

Copy

No.

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

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

sup-

plied

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

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

F19628-

68-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

SECTION

I

SECTION

II

SECTION

III

SECTION

IV

INTRODUCTION

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

Population

File

Maintenance

Module

The

Selector

Module

Source

Program

Maintenance

Module

The

Test

Program

.2

.3

2.3.

2.3.4

2.3.5

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

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

II

?ii

1

2

3

4

6

7

8

9

10

11

13

14

15

16

17

TABLE

OF

CONTENTS

(Continued)

4.1.3

4.1.4

4.2

Selecti

4.2.1

4.2.2

4.2.3

4.2.4

Page

4.1.2.1.6

Environmental

Software

Cards

18

4.1.2.2

Test

Modules

18

4.1.2.2.1

Test

Header

Card

19

4.1.2.2.2

JOVIAL

Statement

Card

21

4.1.2.3

Packet

Cards

21

4.1.2.3.1

Control

Card

-

PF

21

4.1.2.3.2

Delete

Card

22

4.1.2.4

Input

Files

22

4.1.2.4.1

Population

File

23

4.1.2.4.2

Current

File

-

PF

23

Function

Operation

25

4.1.3.1

Create

Population

File

25

4.1.3.2

Update

Popul

ation

File

25

Description

of

Expected

Results

27

4.1.4.1

Output

Card

Formats

27

4.1.4.2

Output

Files

27

4.1.4.2.1

Population

File

27

4.1.4.2.2

Audit

File

-

PF

27

4.1.4.2.3

Punch

File

-

PF

29

r

Module

(SJCVS)

29

Purposes

and

Uses

29

Preparation

of

Inputs

29

4.2.2.1

Input

Card

Formats

29

4.2.2.1.1

Test

Selector

Card

30

4.2.2.1.2

Control

Card-S

30

4.2.2.2

Input

Files

31

4.2.2.2.1

Population

File

31

4.2.2.2.2

Test

Selection

File

31

Function

Operation

31

Description

of

Expected

Results

33

4.2.4.1

Output

Card

Formats

33

4.2.4.1.1

Environmental

Software

Card

33

4.2.4.1.2

Test

Header

Card

33

4.2.4.1.3

JOVIAL

Source

Program

Card

34

4.2.4.2

Output

Files

35

4.2.4.2.1

Source

Program

File

35

4.2.4.2.2

Audit

File

-

S

36

4.2.4.2.3

Punch

File

-

S

38

VI

TABLE

OF

CONTENTS

(Continued)

Page

4.3

Source

Program

Maintenance

Module

(SOPMM)

38

4.3.1

Preparation

of

Inputs

39

4.3.1

.1

Card

Inputs

39

4.3.1.1.1

Control

Card-SP

39

4.3.1.1.2

Other

Card

Inputs

40

4.3.1.2

Input

Files

40

4.3.1.2.1

Source

Program

File

40

4.3.1

.2.2

Current

File

-

SP

40

4.3.2

Function

Operation

41

4.3.3

Description

of

Expected

Results

42

4.3.3.1

Output

Card

Formats

42

4.3.3.2

Output

Files

42

4.3.3.2.1

Source

Program

File

42

4.3.3.2.2

Audit

File-SP

42

4.3.3.2.3

Punch

File-SP

43

4.4

Initiate

Population

File

Module

(INIPOP)

43

4.4.1

Purposes

and

Uses

43

4.4.2

Preparation

of

Inputs

44

4.4.2.1

Card

Inputs

44

4.4.2.1.1

Control

Card

-

IP

44

4.4.2.1.2

Other

Card

Inputs

46

4.4.2.2

Input

Files

46

4.4.2.2.1

Population

File

46

4.4.2.2.2

Current

File

-

PF

46

4.4.3

Function

Operation

46

4.4.4

Description

of

Expected

Results

46

4.4.4.1

Output

Card

Formats

46

4.4.4.2

Output

Files

47

4.4.4.2.1

Population

File

47

4.4.4.2.2

Audit

File-IP

47

4.4.4.2.3

Punch

File

-

IP

47

4.5

JCVS

Report

Writer

Module

(JCVSRP)

48

4.5.1

Purposes

and

Uses

48

4.5.2

Preparation

of

Inputs

48

4.5.2.1

Card

Inputs

48

4.5.2.1.1

Control

Card

-

RP

48

4.5.2.2

Input

Files

49

4.5.2.2.1

Population

File

49

4.5.3

Function

Operation

49

4.5.4

Description

of

Expected

Results

49

4.5.4.1

Audit

File

-RP

49

VII

TABLE

OF

CONTENTS

(Continued)

Page

SECTION

V

USAGE

INSTRUCTION

51

5.1

JCVS

Operating

Philosophy

51

5.2

JCVS

Function

51

5.3

Preparation

of

JCVS

Input

52

5.3.1

Current

File

-

PF

52

5.3.2

Current

File

-

SP

52

5.3.3

Test

Selection

File

52

5.4

Functional

Processing

52

5.5

Results

of

Operations

52

5.5.1

Printed

Output

52

5.5.1.1

Population

File

58

5.5.1.2

Audit

File

-PF

58

5.5.1.3

Audit

File-S

58

5.5.1.4

Audit

File

-SP

58

5.5.1.5

Audit

File

-IP

58

5.5.1.6

Audit

File

-

RP

58

5.5.2

Punched

Output

58

5.5.2.1

Punch

File

-PF

67

5.5.2.2

Punch

File

-

S

67

5.5.2.3

Punch

File

-

SP

67

5.5.2.4

Punch

File

-IP

67

5.5.3

Magnetic

Tape

Output

67

5.5.3.1

Population

File

67

5.5.3.2

Source

Program

File

67

TABLE

OF

CONTENTS

for

APPENDIX

1

68

/PPENDIX1

71

APPENDIX

ii

171

APPENDIX

in

173

/PPENDIX

IV

175

/PPENDIXv

177

/PPENDIX

VI

lal

VIII

SECTION

I

INTRODUCTION

The

purpose

of

this

manual

is

to

:

1.

Introduce

the

JOVIAL

Compiler

Validation

System

2.

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

.

Data

Transmission

2.

Algebraic

Expression

Formulation

3.

Logical

Expression

Formulation

4.

Transfers

of

Program

Control

4.1

Conditional

4.2

Unconditional

4.3

Switching

4.4

Looping

5.

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

.

The

ability

to

specify

any

item

type

and

have

it

retained

according

to

its

defining

attributes.

2.

The

ability

to

formulate

any

constant

type

and

have

it

retained

according

to

its

defining

attributes.

3.

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

.

The

ability

to

name

a

statement

with

a

label.

2.

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)

A

careful

sampling

of

selected

operands

from

possible

combinations

of

operand

types

available

to

the

statement.

b)

No

tests

are

made

of

erroneous

statements.

c)

All

possible

variants

of

procedural

statements

are

performed.

d)

Tests

are

not

designed

to

indicate

how

a

function

is

implemented.

Thus,

there

is

no

attempt

to

distinguish

between

efficient

and

inefficient

implementations.

e)

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.

f)

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.

b)

Test

Results

which

show

discrepancies

are

output.

An

option

exists

for

viewing

an

indication

of

the

results

of

all

tests

(see

Section

3.5).

c)

Program

modules

are

machine

independent.

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

.

Environmental

-

Hardware/Software

2.

Test

Modules

3.

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

.

Test

identification

field

2.

Input

test

data

fields

3.

Test

Results

fields

4.

Expected

Result

fields

5.

Initialization

procedures

6.

Test

statements

comprising

the

test

7

Results

analysis

procedures

8.

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)

The

resulting

test

and

support

statements

are

placed

in

the

order

needed

for

compilation.

3)

Operating

system

control

cards

are

placed

before

and

after

the

JOVIAL

source

test

program.

2.3.4

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)

One

or

more

tests

did

not

compile

correctly

(therefore

deletions

of

erroneous

statements

or

changes

to

existing

statements

can

be

made).

2)

The

user

wished

to

change

a

test

in

order

to

compare

with

a

using

different

user

defined

operand

values

(parametric

study).

3)

The

user

wishes

to

add

non-standard

tests

to

the

JOVIAL

source

program.

2.3.5

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

.

The

entire

system,

including

the

Population

File,

can

be

distributed

to

JOVIAL

J3

implementors

for

use

in

validating

their

JOVIAL

implementation.

2.

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.

3.

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

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

Population

File

Maintenance

Module

(POPFM)

4.1.1

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

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.)

13-24

Facility

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.)

25-34

Computer-Name

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

Description

35-45

Data

of

Basic

File

Creation

46-47

48-58

59-72

73-76

77

78-80

Modification

Number

Date

of

Creation

of

this

File

Not

Used

DDI-NO

Card

Type

Sequence

Number

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.

4.1.2.1.2

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

1-35

Name

Validation

System

Name

Description

These

35

columns

may

be

used

to

identify

the

particular

modification

of

the

validation

system.

(Example:

bbbbbbbbbbbJCVSbMAYb

1968bbbbbbbbbbb,

or

JOVIALbCOMPILERbVALIDATIONb

SYSTEMb5).

15

Columns

Name

Description

36-72

73-76

77

78-80

Operating

System

Name

DDI-NO

Card

Type

Sequence

Number

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

1-30

31-60

61

62

63

64-70

71-72

73-76

Name

System

Input

System

Output

Space

Code

Double

Space

Code

Page

Eject

Memory

Size

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

Description

77

78-80

Card

Type

Sequence

Number

This

column

contains

the

character

A

that

indicates

this

card

is

a

non-test

statement

card.

These

3

columns

contain

a

sequence

number

=

003.

4.1.2.1.4

Environmental

Hardware

Card

2

This

card

occupies

the

fourth

set

of

80

character

positions

in

the

System

Module

and

contains

the

following

information:

Columns

1-30

31-60

61-72

73-76

77

Name

System

Punch

Scratch

1

Not

Used

DDI-NO

Card

Type

78-80

Sequence

Number

4.1

.2.1

.5

Environmental

Hardware

Card

3

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.

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.

This

card

occupies

the

fifth

set

of

80

characters

in

the

System

Module

and

contains

the

following

information:

Columns

1-30

31-60

61-72

Name

Scratch

2

Scratch

3

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

Description

73-76

77

78-80

DDI-NO

Card

Type

Sequence

Number

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

2-72

73-76

77

Description

Statement

DDI-NO

Card

Type

78-80

Not

Used

Environmental

Software

These

71

columns

provided

contain

a

request

of

the

operating

system

to

perform

a

specific

task.

These

4

columns

contain

the

test

serial

number,

the

DDI-NO,

0001

.

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.

These

3

columns

may

contain

the

digits

005

through

050

which

serves

to

indicate

the

relative

position

of

this

card

in

the

System

Module.

Sequence

Number

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.

Included

in

each

test

module

are

the:

1

.

Test

identification

field

2.

Input

test

data

fields

3.

Test

result

fields

4.

Expected

result

fields

5.

Initialization

procedures

6.

Test

statements

comprising

the

test

7.

Results

analysis

procedures

8.

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

Open

Quotes

These

2

columns

contain

quote

marks.

3-22

Test

Name

These

20

columns

describe

what

feature

the

JOVIAL

statements

test.

(Example:

THREEbFACTORbFOR

bbbb,

orGOTObSTATEMENTbbbbbb).

19

Columns

Name

Description

23-27

CED-NOl

These

5

columns

identify

a

reference

in

the

AFM

100-24

to

the

feature

being

tested.

28

Not

Used

29-33

CED-N02

These

5

columns

identify

a

reference

in

the

AFM

100-24

to

the

feature

being

tested.

34

Not

Used

35-39

CED-N03

These

5

columns

identify

a

reference

in

the

AFM

100-24

to

the

feature

being

tested.

40

Not

Used

41-45

CED-N04

These

5

columns

identify

a

reference

in

the

AFM

100-24

to

the

feature

being

tested.

46

Not

Used

47-51

CED-N05

These

5

columns

identify

a

reference

in

the

AFM

100-24

to

the

feature

being

tested.

52

Not

Used

53-57

CED-N06

These

5

columns

identify

a

reference

in

the

AFM

100-24

to

the

feature

being

tested.

58

Not

Used

59-62

Mandatory

DDI-NO

These

4

columns

identify

the

DDI-NO

of

a

Mandatory

Module

upon

which

the

current

test

module

depends.

63-64

Close

Quotes

These

2

columns

contain

quote

marks.

65-72

Not

Used

73-76

DDI-NO

These

4

columns

contain

the

test

serial

number,

the

DDI-NO.

(Example:

4500,

7500,

1410).

77

Card

Type

This

column

contains

either

the

character

A

or

B

or

C

that

indicates

this

card

is

a

non-test

statement

can

78-80

Sequence

Number

These

3

columns

contain

001,

indicating

that

this

card

occupies

the

first

80

columns

of

the

Test

Module

on

the

Population

File.

20

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

1-72

73-76

77

78-80

Name

JOVIAL

Statements

DDI-NO

Card

Type

Sequence

Number

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.)

4.1.2.3

Packet

Cards

4.1.2.3.1

Control

Card

-

PF

The

various

options

permitted

by

the

Population

File

Maintenance

Module

may

be

requested

by

means

of

the

following

control

card:

Columns

1

2-4

Name

Control

Card

Indicator

Control

Card

Indentifier

Mode

Designator

Description

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

8-80

Print

Option

Punch

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

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

1-72

73-76

77

78-80

Field

Size

72

4

1

3

Description

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

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)

System

Header

Card

1

2)

System

Header

Card

2

1

3)

Environmental

Hardware

Cards

3

4)

Environmental

Software

Cards

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

4$2C

Cr.on'c/rrS

40QO

cA<ir*e/cr£>

4OQ0

cka.ado.

6C

carcic

i-Vl'/*>A-'v/4

A.T

£.'•<->/"

I'•-'V

'

—

Lf.Au

FILLED

7"^sr

tf£AJ?££.

I

M&DUIJE

it

Me>DULt£

I

TE£>T~

-5

7~/f

r£M£MTS

TESr

^£/tC?£/e

/

MOLULE

KJ

MODULE

N

JbvlfiL

TEST

£>7*ir£M£tJ7Z3

gO

c/<r*.;r-'

Cr

.\/ca,c/

80

char*'

//

•

/

'

•

/

Carc(

£0

ehtinrJsr

t

/card

80

chartcUrS/Oar<i

TesT

MOOULB

JL

3920

cJ,fir#c£n

TLsr

MODULE

A/

&1ZO

cJ,*racfc^

Figure*4rl'

Population

File

The

Test

Packet

consists

of

the

following

cards:

Number

of

Cards

1)

Test

Header

Card

1

2)

JOVIAL

Statement

Cards

N.

3)

DELETE

Cards

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)

Add

a

card

to

a

new

or

an

existing

test

module

2)

Replace

a

card

on

an

existing

test

module

3)

Delete

one

or

more

existing

test

modules

4)

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)

DDI-NO

(columns

73-76)

2)

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

There

is

no

control

card

preceding

the

Current

File-PF.

RECORD

TO

BE

DELETED

NOT

ON

The

Current

File-PF

contains

a

OLD

MASTER

FILE

DELETE

packet

referencing

a

DDI-NO

not

on

the

old

Population

File.

CURRENT

FILE

CARDS

ARE

OUT

OF

The

cards

in

the

Current

File-PF

SEQUENCE

are

not

in

sequence

by

DDI-NO.

INITIAL

RUN

CARD

NOT

PRESENT

The

control

card

preceding

the

Current

File-PF

contains

an

incorrect

Mode

Designator.

OVERFLOW

MASTER

RECORD

BUFFER

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)

IUC

2)

UPDATE

CONTROL

3)

OLD

MASTER

FILE

READOUT

4)

END

OF

CURRENT

FILE

5)

END

OF

OLD

MASTER

FILE

6)

END

OF

OLD

MASTER

FILE

4

The

following

typical

trace

message

is

printed

whenever

the

WRITE-ERROR

paragraph

is

entered;

LAST

CARD

KEY

0002A005

LAST

CURRENT

FILE

KEY

0002A003

LAST

OLD

MASTER

FILE

KEY

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

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

.

Using

the

input

specifications

obtained

from

the

user,

appropriate

test

and

support

structures

may

be

selected.

2.

The

resulting

test

and

support

structures

are

placed

in

the

order

needed

for

compilation.

3.

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

Preparation

of

Inputs

4.2.2.1

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

Description

1-4

5-10

11-14

15-20

21-24

25-30

31-34

Control

Word

Not

Used

Starting

DDI-NO

Not

Used

Increment

Not

Used

Final

DDI-NO

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.

35-80

Not

Used

4.2.2.1.2

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

Description

2-4

5-6

7-8

10

11-14

15-80

Control

Card

Identifier

Margin

A

Margin

B

Print

Option

Punch

Option

System

Module

DDI-NO

Not

Used

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.

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

4100

0010

4200

2

3000

0005

3010

3

6000

0000

4

8100

0001

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

Final

DDI-NO

1

4100

0010

4120

2

3000

0005

3010

3

6000

0000

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

2500

4110

4120

1200

3000

2215

3005

2210

3010

2210

6000

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

B

1

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

Test

Module

DDI-NO

1

1200

10

4000

2

2000

11

4100

3

2210

12

4101

4

2215

13

4102

5

2216

14

4110

6

2500

15

4120

7

3000

16

6000

8

3005

17

8000

9

3010

18

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.

1

Margin

A

72

Margin

B

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

Description

1

-Margin

A

Margin

A

-

Margin

B

Margin

B-72

73-76

77

78-80

Not

Used

JOVIAL

Statement

Not

Used

DDI-NO

Card

Type

Sequence

Number

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.

4.2.4.2

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

EXCEEDED

DDI-NO

TABLE

DDI-NO

AND

INDEX

NOT

SYNCHRONIZED

UNEXPECTED

EOF

INFILE

UNEXPECTED

EOF

POP-FILE

NO

CONTROL

CARD

Explanation

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

Selec-

tion

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.

36

L£AO

<f>PEpAr/fi'C,3/i>TTrM

CAiWL

LEAD

4f>£tj4r-i

M

6

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

**&

$

/esr

JbviAL

•msrsmrEH£NT

OVJ>

(

J&V/AL

7£ST

5>TX7£MChtr

C*A?

2.

JdVI/IL

7tST

SntTZMtrrir

CA&.

3

7Y^r

HE4/PC*

CAKU

•

A/

roiLaii

<t*'iwn*iG>

SM&TLH

cA/ecji

RXJJOW

ci>l£JiriN6>

SVCTIH

&££>

&

Figure

,4-;2-

Source

Program

File

37

MODULE

1

EXECUTTON

MOJX/JLJT

Z

£y.£C6/7TOA/

MODULE

N

FOLLOW

OPL4ATIMG>

Diagnostic

Explanation

INCORRECT

TEST

SELECTOR

CARD

There

is

an

incorrect

Test

Selector

Card

in

the

INFILE.

Correct

the

card

and

restart

the

program.

INCORRECT

CONTROL

CARD

The

Control

Card-S

margin

specifications

are

incorrect.

Correct

specifications

and

restart

program.

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

.

BDT1

2.

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

.

Contents

of

item

DDI-NUMBER

BDT2

2.

BMT1

,

Contents

of

item

DUMP

BMT1

3.

Contents

of

record

CARD

ERR-PROC-6

4.2.4.2.3

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)

One

or

more

tests

did

not

compile

correctly;

therefore,

deletions

of

erroneous

statements

or

changes

to

existing

statements

can

be

made.

2)

The

user

wishes

to

change

a

test

in

order

to

compare

with

a

3)

The

user

may

wish

to

add

self

contained

non

standard

tests.

4)

Certain

areas

of

the

JOVIAL

compiler

have

not

been

debugged

completely.

5)

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

1

2-4

5

Name

Control

Card

Indicator

Control

Card

Identifier

Mode

Designator

Print

Option

Punch

Option

Description

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

39

Columns

Name

Description

8

Trace

Option

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

9-80

Not

Used

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

.

Environmental

Software

Card

2.

Test

Header

Card

3.

JOVIAL

Source

Program

Card

4.

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

seria

1

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

.

ADD

a

card

to

the

Source

Program

File

2.

REPLACE

a

card

on

the

Source

Program

File

3.

DELETE

one

or

more

test

modules

from

the

Source

Program

File

4.

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

.

DDI-NO

(columns

73-76)

2.

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.

RECORD

TO

BE

DELETED

NOT

ON

The

Current

File-SP

contains

a

OLD

MASTER

FILE

DELETE

card

referencing

a

DDI-NC

not

on

the

old

Source

Program

File.

CURRENT

FILE

CA

*DS

ARE

OUT

O-

The

cards

in

the

Current

File-SP

SEQUENCE

are

not

in

sequence

by

DDI-NO.

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.

IUC

2.

UPDATE

CONTROL

3.

OLD

MASTER

FILE

READOUT

4.

END

OF

CURRENT

FILE

5.

END

OF

OLD

MASTER

FILE

6.

END

OF

OLD

MASTER

FILE

4

The

following

typical

trace

message

is

printed

whenever

the

WRITE-ERROR

paragraph

is

entered:

LAST

CARD

KEY

0002A005

LAST

CURRENT

FILE

KEY

0002A003

LAST

OLD

MASTER

FILE

KEY

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

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

Initiate

Population

File

Module

(INIPOP

)

4.4.1

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

This

column

must

contain

the

character

C

denoting

the

card

as

a

control

card.

2-4

Control

Card

These

3

columns

may

be

assigned

Identifier

any

3

digits

by

the

user

to

identify

the

control

card.

44

Colu

mns

6-8

9-12

13-16

17

18

19

20-23

24-80

Name

Renumber

Option*

Card/Record

Initial

Number

Increment

Print

Option

Punch

Option

Old

Population

File

Option

Record

Maximum

Not

Used

Description

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

UNEXPECTED

EOF

INFILE

DDI-NO

LARGER

THAN

9997

NO

CONTROL

CARD

Explanation

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.

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

Description

1

Control

Card

This

column

must

contain

the

Indicator

character

C

denoting

the

card

as

a

control

card.

2-3

Report

Selection

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

Refer-

encing

Listing

space

-

No

Cross

Refer-

encing

Listing

4-13

Not

Used

14-19

Date

These

six

columns

specify

the

date

as

follows:

14-15

Month

16-17

Day

18-19

Year

(Example:

040968)

48

Columns

Name

Description

20-61

Test

Identification

These

42

columns

are

used

to

specify

the

computer

name.

The

name

may

be

positioned

any

place

in

the

field.

62-63

Control

Tape

Size

These

two

columns

are

used

to

specify

the

number

of

lines

per

printer

page

that

are

available

to

be

printed

on.

64-65

Line/Record

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.

66-80

Not

Used

4.5.2.2

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

.

Implementors

COBOL

Manual

2.

Implementors

Operating

System

Manual

3.

Implementors

JOVIAL

J3

Manual

5.1

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.

They

are

given

in

the

following

list:

1

.

Create

a

new

Population

File

POPFM1

2.

Update

an

old

Population

File

POPFM2

3.

Generate

a

JOVIAL

source

program

SELECT

4.

Update

a

Source

Program

File

SOPMM

5.

Initiate

a

Population

File

from

a

INIPOP1

Population

File

card

deck

51

6.

Initiate

a

new

Population

File

from

INIPOP2

an

old

Population

File

on

magnetic

tape

7.

Write

reports

from

Population

File

JCVSRP

5.3

Preparation

of

JCVS

Input

5.3.1

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.

In

this

example,

it

is

assumed

that

no

Mandatory

DDI-NO's

are

involved.

f

.4

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

TFS

T

MODULF

TFST

MODULE

TFST

^00\

iLF

TFS

r

MODULF

TTST

MODULE

TFST

MODULF

T

r

ST

MODULE

TFST

MODULF

TFST

MODULE

jtrc,j

vOP!!L

r

TP^T

WPHI

'L

F

TEST

MOPULE

TrST

MpnuLF

TFST

MOPULF

TFST

MOPULF

rrsT

MODULE

TFST

MODULE

TFST

MOpULF

T

r

ST

MOPULF

TFST

MOP!

Mr

TFST

Mpn(i[

F

Tr

r

,T

Mpni

'|

r

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

on

nn

n

00

M

0

on

no

oo

or

00

nn

oo

en

on

oo

00

nn

or

nn

00

nn

rn

00

CO

00

0

oo

00

oo

or

ro

nn

00

on

On

on

op

on

00

OO

in

00

nn

14

0

0^02

JOVIAL

oo^g

JOVIAL

10

2427

242

JOVIAL

p

n

r

0

o

0

o

0

P

1

2

3

2437

STATEMENT

8

242^

STATFMFNT

STATFMFKJT

5TATEMFMT

STAT^r-TNT

STATFMTNT

STATFMFNT

STAT

c

MrNT

STATTMENT

STATFMFNT

STATi-^r^T

5.

T

A

T

r

M

r

N

T

STATFMFNT

STATEMENT

STATFMFNT

STATFVTMT

STATFMTNJT

5TATrMf-MT

STATF

M

TNT

STATFMTMJ

STATFMFNT

STATFMTNT

STATTM^NT

STATFMFNT

STATEMENT

STATEMTNT

STATFMFNT

STATTMFNT

STATFMFNT

STATTMFNr

STATFMFNT

STATFMTNT

of

3

ObO

001

nr2

003

004

005

0

06

no

7

008

009

010

Oil

012

013

014

01

5

016

0]7

01

R

oi9

02

0

021

"22

023

o24

0

2

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

APP

CARP

1

0

PEPLACT

A

CAPI)

^TPLACF

A

CA^P

DELETE

MODULF

13

1

•

J

01

r

p

n

'.

-04

or

'

•

r\

~t

nn

>•

-

CM,

r.

0if

•

2

j

r

0

,

-

nnn'yj"',

(

0010

i

no]

oj

o

10

J

0

o

1

0

J

On]

oj

0010

0010J

^^

1

OJ

On

i

0

nn

1

r

n,n

no

ir

nn

on

^

n

OO

nn

no

00

nn

nr

nn

nr

nn

"0

0^

OO

nn

0

On

0

o

n

o

J

o

i

0

JO]

1

J

0

i

?

JO\--

J'

•

11.

JO

1'

O

J

-

1

7

oj

"

1

t.

OJr

jr,

0J02F

oj-2

;

n

Jn22

o

J

"

2

•

OJ"

2/

(

0JO2*'

ojo26

ojo27

njnp

«

0J~29

0

J

o

3

o

OJ"

il

0JOJ2

0

J

0

j

3

0JPJ4

PJ035

OJ^

36

0J037

o

1

^JO'lR

pJ

A

:>9

0

]

OJ^ZjO

01

'-jo/,

1

o

I

n

j

0

4

3

00

1

0J044

noinjo4'j

0010JO46

On]

0J047

0

010J"4H

Oo]0J^49

OP

]

o

j

r

•

<,

n

nn

]

ljr|'-

OO

1

2J.'W,

0

O

]

3

r.

o

0

0O14AOO]

Figure

5-la

Current

File-PF

53

TEST

TF5T

TEST

T

C

ST

TFST

TEST

TFST

TEST

TFST

TEST

TPM

TEST

TFST

TEST

TFST

TEST

TFST

MODI

TFST

TEST

TFST

TEST

TFST

TEST

TFST

TEST

TFST

TEST

TFS"

1

TFST

MODULE

MOD

JLE

MODI

ILF

MOD'

ir

MODULF

MOD

JLE

MODULF

MODULE

MOD

1

ILF

MODULE

MODJLE

MODULE

MODULF

MOFiULF

MODULE

MODI'I

F

MODULF

MODULE

MODULF

MODULE

MOnuLF

LF

NAME

MODULF

MODI

LE

MODULF

MODULE

MODULF

MODULE

MODULF

MODULE

MODULF

MODULE

0014

JOVIAL

0014

JOVIAL

0014

JOVIAL

0014

JOVIAL

CO

14

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

001

O0

14JC0

2

STATEMFNT

003

nnl4J0

n

4

STATEMENT

005

00

14JC06

STATEMENT

007

0014JO08

STATFMFNT

009

Onl4Jf

lp

STATFMCMJ

on

^

n

14J'

1

?

STATFMFNT

013

0^14Jr

J

u

STATFMFNT

015

0014J0

16

STATEMFNT

017

0M4J"18

STATFMFNT

019

0

14

J

0

2

n

STATEMFNT

021

0014J;

1

22

STATEMFNT

023

0

14

J

(

1

24

STATEMFNT

025

0^

L4J026

STATEMENT

027

0014J028

STATEMENT

029

1

0014J030

STATEMENT

031

0014JC32

STATEMENT

033

00

14JO

34

STATFMFNT

035

0M4J036

STATFMFNT

037

0014JT38

STATEMFNT

039

0014JC^O

STATEMFNT

041

0014J042

STAT

r

MrMT

043

nr>l4J0

44

STATFM

r

NT

045

o

0

1

4

J

0

4

6

STATFMFNT

047

O014JO48

STATEMFNT

049

0014J05

0

STATEMENT

003

DELETE

A

CARD

0O15DO03

STATEMFNT

020

REPLACE

A

CARD

0016J020

STATEMFNT

006

ADD

A

CARD

00]

7J(

06

STATEMFNT

021

REPLACE

A

CARD

0017JO21

STATFMPMT

007

ADD

A

CAPD

OOlRJf'07

0016»

•

0O19A001

STATFMFNT

002

0<M9J003

STATFMFNT

004

0019J005

STATFMFNT

006

oo]

9Jn07

STATEMENT

008

0019J009

STATEMENT

010

0019J011

STATEMENT

012

0

19JO

13

STATEMENT

014

00

19J015

STATEMENT

016

0019J017

STATFMFNT

018

0019JO19

STATEMFNT

020

0019J021

STATFMFNT

022

D019JO23

STATFMFNT

024

00

1

9J^2

r

-

STATEMENT

026

0O19JO27

STATEMFNT

028

0O19J029

STATFMFNT

030

oo]9J"31

STATFMFNT

032

0

19Jo

3°

STATEMFNT

034

00

19Joj

[

.

STATEMFNT

036

0O19JO37

STATEMFNT

038

0019JO39

STATEMENT

040

0019J04

1

STATEMFNT

042

0

L9J043

STATFMCNT

044

00

1

9

Jo

i

t

',

STATEMFNT

046

on

19J047

STATEMFNT

048

0019JO49

STATEMENT

REPLACE

MODULE

21

0021D0OO

Figure

5-1

b

Current

File-PF

54

TEST

T

C

ST

TFST

TEST

TFST

TTST

MODULE

MOHULF

MODULE

0021

ro?i

0021

°°21

0021

JOVIAL

STATEMENT

STATFMFNT

STATEMENT

STATFMFNT

001

002

003

004

005

010

025

jr^j

N'pnulF

0021

JOVIAL

STATFMTNT

050

TTST

MODULE

0022

JOVIAL

STATFMFNT

032

TFST

^OPDLF

0023

JOVIAL

STATTMTNT

007

TFST

MODULE

0024

JOVIAL

STATFMFNT

026

TFST

MODULE

0025

JOVIAL

STATFMTNT

REPLACE

MODULE

TPLACF

MODULE

REPLACE

MODULE

REPLACE

MODULE

REPLACE

MODULE

REPLACE

MODULE

PFPLACF

MODULI"

°rPLACF

MODULE

DTLFTE

A

CAPD

DFLFTF

A

CARD

DTLET

1

"

A

CA"R

DFLFTF

MODULE

21

?]

21

25

0

A

7

1A

0

f

1

0O21JOO2

0^21JC0

3

002

U?0/»

o

r\

2

1J

^

0

>j

n

o

?

1J

r

]

r>

0^21

JO?-

*r>2

i

jo«,

n

^?2r^i?

n

o2

3

Dnr

7

i">

O

2

A

D

0

2

(

•

>

0025^000

Figure

5-lc

Current

File-PF

55

TFST

MODULF

00

03

JOVIAL

STATFVFNT

0P<*

A!">D

A

CARD

r\oo3j^p/

(

TTST

MODULF

0003

JOVIAL

STATFMFM

005

DEL

r

TE

A

CARD

r*rp3r?P5

TFST

WCDULF

00^8

JOVIAL

STATEMENT

024

DELETE

A

CAPD

PP08P^'4

TFST

MODULE

0008

JOVIAL

STATEMENT

036

PEPLACE

A

CAPD

0

*

0

8

J

0

3

6

TFST

MODULE

0009

JOVIAL

STATEMENT

02

0

ADD

A

CARL

0OP9JC*0

TFST

MODULE

0011

JOVIAL

STATEMENT

017

REPLACE

A

CARD

0011JCI7

TFST

MODULF

0012

JOVIAL

STATEMENT

031

ADD

A

CARD

0O12J0

:-l

TFST

MCDULF

0013

JOVIAL

STATEMENT

021

REPLACE

A

CARD

PO

13

JO'l

TFST

MODULE

0024

JOVIAL

STATEMENT

020

DFLETE

A

CARD

pnJA'0^<?n

TFST

MODULE

0024

JOVIAL

STATFMENT

025

ADD

A

CARD

OOP^JO^

1

'

TFST

MODULF

0024

JOVIAL

STATEM

r

NT

050

PEPLACE

A

CA

p

D

0P24J05P

TFST

MODULF

0O?5

JOVIAL

STATEMENT

017

DFLFTE

A

CAPD

0H2

5DP1

1

Figure

5-2

Current

File-SP

56

r

v;

r

n

p

"a

no^

c,

0

n

7

/

4

OPOC

nor?

on?

on

l?

Figure

5-3

Test

Selection

File

57

5.5.1.1

Population

File

Figure

5-4

shows

portions

of

a

tape

dump

of

the

Population

File

from

the

GE-635.

Exact

positions

of

the

test

statements

within

the

block

should

be

noted.

Since

this

is

test

information,

the

content

of

the

various

cards

in

the

record

are

not

actual

JOVIAL

statements

but

indications

as

to

where

Population

File

information

would

replace

the

checkout

statements.

5.5.1.2

Audit

File-PF

Figure

5-5

presents

a

portion

of

the

listing

of

the

Audit

File-PF

generated

by

POPFM

on

the

GE-635.

Notice

diagnostic

and

trace

messages

interspersed

with

the

list

of

the

new

Population

File.

5.5.1.3

Audit

File-S

Figures

5-6A

and

5-6B

present

a

portion

of

the

Audit

File-S

generated

by

SJCVS

on

the

GE-635.

5.5.1.4

Audit

File-SP

Figure

5-7

presents

a

portion

of

the

Audit

File-SP

generated

by

SOPMM

on

the

GE-635.

Notice

that

no

trace

messages

appear

in

the

listing

giving

the

user

a

"clean"

listing

of

the

new

Source

Program

File.

5.5.1.5

Audit

File-IP

Figure

5-8

presents

a

portion

of

the

Audit

File-IP

generated

by

I

NIPOP

on

the

GE-635.

The

diagnostic

messages

'MANDATORY

MODULE

NOT

ON

POPULATION

FILE'

are

printed

but

processing

is

permitted

to

continue.

Notice

that

no

trace

messages

appear

on

the

listing

giving

the

user

a

"clean"

listing

(except

for

diagnostics)

of

the

new

Population

File.

5.5.1.6

Audit

File-RP

Figures

5-9A

and

5-9B

present

a

portion

of

a

listing

of

the

Audit

File-RP

generated

by

JCVSRP

on

the

GE-635.

The

trace

message

appears

on

a

separate

page

thereby

giving

the

user

a

"clean"

listing

of

the

two

reports:

The

POPULATION

FILE

and

the

CROSS

REFERENCE

TABLE.

5.5.2

Punched

Output

58

UJ

IT

o

I

»-

or

r>

o.

LU

r

»

t

UJ

a

•

i

a

o

i

UJ

O

jr

i

•

o

Q

O

<->

»-

I

u.

V

o

UJ

»-

—

a

3

•-

T

UJ

o

I

»

I

o

u

OS

I

•

I

UJ

o

X

I

>

»

UJ

o

a

o

©

s

t

I

J.J

a

r

D

C)

8.

o

c

o

Q.

O

-3-

I

K

D

O)

^

-\

•

>

-^

.,~\

•

i

ir\

<o

t

<r>

o>

o

<4rl

t(HHN

3

«

>

O

Ol>00000l>000

i\a\»\r>«\v\iNrt^irir>«M\ir\irMnMMr\tftir>m«Mrvirtit

I

€•<

O

i>

O

<

•

a

o

i

muuiiuui

J

i

-J

_•

_i

33

3

5

3

i

a

o

j

o

Q

o

i3

O

IE

*

r

x

X

x

•

o

«e

m

an

mill

ummui

(MI>1*

m

flu

CM

IT

-O

<MCW

oo

T

•>

•»

•

»

ui

in

oo

o»

o

n

<\i

NMnnn

ooooo

•

l»>

>C

P»

«D

WKIBIOK)

:£:

o

-rt

OJ

K5

•»

OOOOO

ooooo

CD

O

CD

«o

r^

oo

o>

o

OOOOO

n

Ml

«r>

«f>

ir\

OOOOO

o

UJ

or

UJ

»-

CO

en

o

I

o

n

l

H(M»eoo(MT<ieoiM«'Oec(\n«

a_.

OOobOv4v4HrltfN(V(MNNrf)tOnH)

ooooooooooooooooooo

*

—

•«-»-»-»-»-»->

~»-»-r»-»

~>-»->->

T»

~»-»->

u-

OOOC>00000<>000000000

~n

OOOpOOOOOOOOOOO«>000

-,

T'

a

-i

o

a

or

•

<

in

ID

I

in

D

i

o-

owcum

J

fun<o«veo>

•

oooooOooooo

I-

ui-

•-

I-

l-

»-

•-

'Z3TZZZZZ

u

i

ui

UJ

Ui

ui

Ui

ui

1

UJ

UI

Ul

UJ

CEtXtXtXtX

lUJUJUJUJUJUJUJUJUJUJUJ

i

an

cn

»-lii

•

g

•>

as

n

w>

m

I

O

©

I

a>

j>

>

•

>

a>

OOOOO

irvuM|\irtifiir\irtinir>i

o

<

o

'

3

Q

O

o

©

o

I

p

o

©

o

UJ

uj

UJ

ui

_l

-J)

-I

J

_l

-J

_l

3333333

Q

O

Cl

O

Q

O

0

o

1

ITtXtl

S

Miaaictowcancninninwtaeincnnincniniaincncaao

UJUJUJUJUJUJUJUJUJUJUJUJUJUJUJLJUUJUJUJUJUJUJUJ11JUJ

60

;

i

UJ

j

V

HMIJMN(>HniJMlOriKll(MN»,(r'jK\

OOOOOHriHXNIMNNNIUnnn

UJ

oooooooopoooooOooo

I

zzzzzzzzzzzzzzzzzz

UiUiUJUJUJUJUiUiUJUJUiUJUJUJUJUJUiUI

J

D-

IXTXXXXXXXXTXIXXXI

-

7

UlUJUlUJUJUJUJUIUJUJUjJJUJUjaJLJJIlJdJ

jUJ

»-»-H-U-»-l-l-»-N-»-»-t-l-»-H-»-t-l-

i

er

h-»-i(-»-h-t-ij-»-»-»-»-»-t-i-i»-i-i-ij-

i

3

c\j

«r>

<r>

•>

*>

an

•>

in

tn

«n

•>

*>

n

m

ff>

a>

•)

<n

«

_I_I^J_I_I_I_I_I^J_I_J_I_I_J-J_I_I_I

I

m

—

.»-

—

»..

.

-.

~

i

<

>•>•>>•>•>•>•»>»>>•>•>>•>•>»

!

_l

«HOOpOGOOOOOOOOOOOOO

'r->->T>->->->->->T>->T->->-r>->->->

'

«M

Hrt*<HrtH^rl«<rlrtHTlH^rfrtrt

!

CD

«OOOOOOOOOOQOOOOOOO

—J

vHOOOOOOOCDOOOOOOOOOO

I

-o

'

*"*

QJUJUJIlJUJUJUJUJUJttlUJUJUJUIIlJI&JllJUIUJ

I

O

X

J

_l

J

-J

_l

-I

_l

J

_l

_»

-I

_l

-J

J

_»

-I

I

O

«333333333333333333

i

Z

O

O.

O

Q

O

Q

o

Q

O

Q

O

o

_I

OOOOOOOOOOOOOOOOOO

©

>-

UJXXXXXXXXXXXXXXXXJJ

or

UJ

_J

•-se

3»-i-i>-t-»-»-»-»-»-»-»-»-»-»-»«-i-i-i-

z

o«nen<n<ndninoncnanan«n*B«aD4r>a>in«a

OO

OUJUJUJUJUJUJIlJUJIAiUJUJUJUJUJUJUJUJUJ

OCX

xl-U-»-»-»-»-l-l-«-»-»-»-»-l-l-»-l-l-

41

KIU

»-

l/l

•«

I-

111

o

w

•-

*

-

•

3

-J

•

!

I

!

I

CM

»-

OH-

O

-1

w

I

O

OO

O

Old

I

•

»

M

•

*l

X

X!=>

61

!

I

i

>

O

OOOOOOOOOOOOOOOOOOOOOOOOO

O

>Oi<

«M

MMUI

ui

Jjufluuiumiuj

ui

W

1

*4

O

»4

ooooooooooooi

IHMHa

Mi—

U»IM

III'

<M

WWIUUIUIUIUJ

HIUI

UIIUIiJUIIUUlUJIlllDUU

LU

III

UI

1U

tu

XXXXiXXXX

wxxxxxxxxxxxx'xxxxxxxxxxxx

til

Ui

til

LULU

UI

UJ

LU

^

Ui

111

UI

Ui

III

UI

ill

UI

UJ

UI

-

»-»-»-

•

-!»-»-»-

•

-

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

-'•

-o

I

LU

o

I

<u

<

Q

E

D

ooooo

o

oo

0000000000

o

ooo

oo

»

>

»•

>

•

!»

>

»

»:>

•

»»»>•»

o

oo

o

oooo

oo

o

'

o

ooooooooooo

o

oo

ooooepooo

ooooooooo

ooo

UI

Ui

UI

UJ

Ui

UI

1

UlUtUIUIUIUIUIUIUiultillllUIUI

UI

OOOOO'OOOOO

O

OOOO

O

o

ooooooooooooooooooooooo

oooooooooo

o

ooooooooooo

UI

LU

UIUIUIUIUJUJUIUIUIUIUIUJUIUI

UI

ill

UI

in

*

O

ooo

0000001000000

ooo

oo

o

X

oooo

oo

33

3313

33

3

oooooooooo

X

XX

XXX

Oj

Win

»

33333333333333333333333

OOOOOOOOOOOOOOOOOOOOOOCli

OOOOOOOOOOOOOOOOOOOOO

OOl

xxxxxxxxxxxxxxxxxxxxx

xx:

in

at

LO

WMW

wnnn

in

m

in

m

omwioMww«)«)<fluuiuluvitfiviviuii««i»)

nv>u>

o

IM

MM

•

M

MM

mm

m

ui

in

•

M

in

m

•nui

M

ui

ai

m

o

:

r

^2

I

!

I

oooooooooooooooooooo

odooooo

HHrlHHr)HHH^H(M<M<MCM<M(MC\»W(M(VaiN(V{MWN

OOOOOOOOOOOOOOOOOOOOOOOOOOO

CDOCDO(Z>OOC3CDOOOOOCDO*=>OCDOOOOOC300

n

rt

»o

w

•

o

i

I

TflTlOOOOOOOOO'"*--*'-'*-'

Oooooooooo*

CM

•

*

•

©

o

a

o

CMCMCMCMCMcSlCMCMCMCMCVICMCMCMOICIJCMCVCMCMCMCM

OOOOOOOOOOOC^OOOOOOOOOO

00000000000000000c>0000

UJ

a.

i

in

r-

UJ

rli

>r

•»

or

o

i

2

Z

1

UJ

M

s>

UJ

r

x

m

i

IUIOI

»

111

•

-

•

-

O

CM

*~

«

<

tt\

-»

»-

k-

O

•

-

l/>

M

oo

C/>

n«m4>N^»OHiv

00OO0CJ>0«Hr-l«-l

oooooooooo

<ll

UJ

I

X

UJ

Ul

•-

fr-

-«

•

<

CO

(A

_I

-I

-c-«-4«-«iujr\j-«-«-«-«

>

»

UJ

>

O

t-

rs.

o

->

~>

•

*

in

->-!-»-»

»-

o

3

»-

v>

u>

a

c/>

UJ

O

UJ

a

i-

O

(/)

X

UJ

u

UJ

xxxxxxxx

UIUJUJUJUJUJUIUJ

r\

id

CM

o

(n

in

n

ij)

in

i/>

n

ID

-J_l_l_ll_l_l_»_l

oooooooo

ini»B\M\i(\ijnv>v\

CMCMCMCMCMCMCMCM

oooooooo

*4

anin

CM

e

o

_i

in

e

BO<NO

UJUI>UJUJLJUJUJUIUJUJUJUJUJUJUJ

_l

JO

X

_l

o

r>

-»

•

«

o

e

711

o

•*

o

X

CM

UJ

X

o

a

o

x

3333>33r>z3

oootbaooo

ooocpoooo

xxxxxxxx

UJ

in

win

ui

in

ui

o)

UJUJUJUJUJUJUJUJ

r

•

B\

«

r-

i

O

r->

O

©

O

©

o

a

oi

>

o

©

o

<t>

O

CD

OOOOD

r

I

^

Z

r

Ul

W

HI

W

HI

Ul

Ui

Cli

43

•*•«-•

•

«•«

©©ooooooo

©

O

CJ

<:ID333D:)D

Diia*

HI

UI

I

O

««

i-l

•*

W

od

o©

o

I

O

CD

O

I

IOO0I

6oeooo«o«ovopoootteeo«ei>oeo«oiiooooof

ooooo*

o

<<

Nil

»

o

CD

©

CD

©

€D

JE

*

JT

*

Z

Ul

111

Ul

UI

HI

XJfcirix-

UJ

Ul

111

Ui

Ul

hlh

if

I-

-«-*-<•

•

«"«-*

»-

•

-

If

»-

*-

«-

••••

•

>*>

•

>

•

i

O

I

l->^

•

o<po<po<>o«>oc>oi>oc>oeoa)oo

:5rxixjfcjr3)t:rxjrjfcj)r

r-

to

o>

«>

•

»>

o

r.

i

ioco<

Ui

Ul

Ui

UU

UJ

ritit

Ul

UJ

»-

If

»-

•

-

§-

.

OOCD©OOOOOCpOOO

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

(M<viv«N(tiNNNnnmnnn»ni

oooooooooooliooooob

I

O

1

«>

o

©

<

©

o

e>

©©

<

I

CM

CU

CM

9oeoit>o

r.

«

O.

o

•

<

CM

fO

m

i>oo©©o©©©o©o

r>fO»<r*»'^«^«r«>»

0©0©OOCDCj>OOCDC>0

.©

nonnnioioi

©

o

I

•

O

CD

O

©

O

©

o

©

111

in

UJ

uiujuiuiuiuiuiuiiii

ui

ujuiuiuiiiiuiujuiuiuiujiuiuiuauiuiui

iirirtriiirtrrmlrnri:*

rrrirz

UJUlUJUJUJUJUJUJUlUIUIUIUJUJUJUJUIUJUIUJUJUJIIJUJUIUIUlUJUIltl

•

-H-I—

H-»-H-»-»-»-»-»->Jfl>-l—

•

-

I—

»-»-l-»-l>-l-»fl—

l-l-l—»-H-

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

III

1

J-IJJJ-IJ-IJJJJ^IJJJJJJJJJJJ^JJJJJJ

3»»»»»>:»»>»>'»3»>5f»»»»»»>'3f»3f»»»»»»>»»»>»»»»»»»»>'»»»>

oooooooocsooooocboorioooooooo

ii

©

O

€3

O

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

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©©©©

aj*uiuiuJUjujLCuiHjuiujujt»iuiaJUJUitumLyu]ttiui

J_I_I-J-J_J_J-»_J_U-J_J_»_J_I.

5353:i33333333353:

ittjnujiijitiujujujaituiiiuiujujuiujujujujujujuji

133

3

33333333333:

'33333333

ziiaaaoaiiaoaaaciooaaatsaooiaocaaaoaaooaoaomaaaaaoaaaooo

i

©

r

SSS!

?

ocococcooooeooooooocc)Ooc

zxxiztiiiixxzrxxxir-

•

•••

•

••

•

•^

•

•nMiiiiaanti

|||

HI

nt

in

\m

HI

in

tit

m

HI

tli

m

HI

m

HI

ifri

^

|i

m

tit

HI

i|i

ill

•ininBiaiiiiniAinww

OH

I

Hi

HI

in

|1|

mi

I

m

Ml

MI

DM

in

'

i

IB

Ul

"i

'*

•

ln

ill

I*I

ttj

'"

*"

111

Ml

Ul

HI

III

^

l

1

'I

1

Ul

"'

'I

1

Ul

HI

'*'

I

Ul

"*

"'

Ul

141

Ul

64

lO

CO

I

LU

o

;

^

rll<)>\

1

o-

•H

fO

Q_

o>

o

O

o

«r*

•H

—

©

oa

CJ

C»

«1

1

OJ

rl

w

W

•H

aH

a-t

«-*

u_

©

o

©o

O

CJ

o

O

o

O

o

O

'"C

D

Ul

-»

<

00

2

•

1

o

•

i

u~>

»-

a>

-«

c

-1

->

3

i

a

3

(M»

«eow

Q

O

©

•-•

<-<

O

©

o

©

tz>

o

>-

Z

2

Z

Or

HI

Ui

HI

Ui

Ul

M

O

J

»

I

J

t~

Ul

UJ

Ul

UJ

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

X

CM

nofionon

CM

->

~>~>

->->

o

©

o

ooooooo

O

©

O

©

CD

©

O

Ul

UJ

X

_1

_l_l_l

_l

-I

••333333

Z

Q

O

O,

Q

O

©

O

©

mirtiTt

DH«««WH

O

Ul

UJ

Ul

~4

CW

O

41

t-o

A

Ik.

—

1>

or

<>

*

•

«r«

ou

•-UI

Cb

•

<

-f

«

UJ

-i

3

_i

<b

a

-«

v

o

»

O.UI

UJ

-*

tr\

o

r-

(Ti

O

CT

O

o

io

irv

m

\rs

\c\

o

oooo

O4>00

to

O

r-

<>

OOOO

O.H(\JKl»

US>OMI)(>Orl

OOOOOOCDOOOO

OOOOOOOOOOO

OOOOOQOOOOO

<M

h*

v

Hh

O

CM

OJ

ru

cu

O

C

'

.

j

O

o

COO

O

HN

(\J

CM

IO

K>

o

*

•

»->">->->

UN

m

U\

UN

ifi

O

CD

O

o

-wiro'-v<r>Oo,_«r\jK']'wijfN,or-

<ri

o

r

>

00000<£OOOOOC»00000

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

OOOOOCDOOOOOOOOOOO

OOOOOOOOOOOOOOOOO

o

O

«H

H

»-t

*H

ooo

*

*o

-o

*«

vH

«H

e>

o

«-t

*•(

t>

O

,-*

*-t

cw

<\j

ooo

CU

K>

•»

in

<4>

tv

rvi

ru

m

o

r~>

CO

Z

X

I

111

ill

Ml

I

:

7

z

a

IUIUIUI

I!

Ul

UJ

z

Ul

UJ

2

Z

UJ

HI

Ul

i

z

Ul

Z

z

LJU

Ul

z

UJ

Ul

1

a

*

Ul

UIUI

N«ODH<tin«U>«MtO'OH

oonooftnnoocionoo

ru

ro

>o

r~

<*>

o

>

C»

CD

—

Q.

I

<

o

O

05

z

Ul

X

z

ui

z

ui

z

ui

UlUIUIUIUlUlUJUIUIUIUlUlUIUIUJUIUIUlUl

zzzxzZzzzzzzzzrzzzz

UlUIUIUIUItilUlUIUIUIUIUIUIUJUIUIUIUIUI

z

—

Ul

IU

Ul

Z

I

1

Ul

i

DM

I-

IJ

U>

</>

M

U»

C*

VI

-i»

-J>

j

inKin»wi»ini>jin0u)onnii)((i»(flii)(

I*

VI

l/l

v>

in

V)

Ul

(!)

-l_lj_lj_lj*j

ivni)v>f»utvbu>L<u>u»uivnooiv><Avtut</>uiu>u>v><jatf)tpviu>

IIAIIJIIMMIUiUIUIIllUIUIUIIAIMIUpilll/JUIUJUIlJIUIUIUJUIUIkJIUJUl

>

3>

5>

»

o

oo

mm

m

n

in

T*

ri

-r*

<-#

.-I

3

•

>

•

>

•

>

•

i

o

:•

3>

>

•

c>

o

-»->->->

"p

->

"»

•

fkmmmmmmiiNiin

•

O

CD

>

O

ooo

I

O

CD

(boo

<

C>

O

I

lUIUtUlUlUJUIUIUIUlUlUIUIUIUI

I_J_I-1J_I_IJJ

ooociooaaocicioor-.

en

IOOOOOOOOOOOOOOO

ZZZ3#ZXZZZJ:TZZXZ

c

65

o

(/icoiflcouDcoiootocoofooocooin

I

i

»

i

J

i

•

i

t

i

OOO

Q

O

D>

»

ooo

->

~»

"»

ooooooooc->o"ooo

>un

lii

>oo

I

Ul

_l

-I

-J

-I

(/></></)M)</i(/>i/>U)<

uiuiuiiiuiiuuimi

mininiMn

O

(

O

CD

O

I

_l

-I

_l

3

Z>

3

OOO

Z

X

z

w

I*

I

^H

•

>

a>

i

Ct>

i

OOOOOC^OC^OOOi

COCiO^OO'OCDO-O^OO

lUJIUUJUJLlllUUflULLiUJ

IJJ_I_I_J_J-I_I-I_J

lOOQOQOCkOOO

IOOOOOOOOOO

IC/lCAt/IIAt/tUpVltjAl/lCAl/)

I

Ul

UJ

(Jl

Ul

111

Ul

UJ

Ul

mm

-*«

mo

•«

•

-

u

m

LUtr

0

zu

III

Ul-I

a:

ui

o

_i

ei

o

r

Q

Ul

u

i/>2

;

o

OUJ

I

z

acts

I

i

u

a

u

a

ul

X.

-

Ul

a

C

O

Cl

o

»

CM

o

w

«o

w

I

*

1

CM

Zz

3

o

a

t

o

*

x

~

1'

!

in

Ji

•

w*

CM

m

c«

l

•«

i

•

•«

CM

Ct

CM

!

CM

•O

»llf>

CM

K»

M

ic\

««

r>

wra

CM

ncMrtioK»iO'*'»^»in«\iniri

CICMriCMCllCMCVCMCUCMCMCMCaCM

O

I

in

m

ai

i

?f

(A

«/)

b

i

</>

to

141

u

11

ai

ui

f

I

CM

t>)

I

c>

o

ci

<

Cl

O

Cl

I

IIOCII

1

-O

•

I

cr\

u

CM

ei

«

m

r.

•

i

i*

ui

Ul

I

o

i

O

I

riHnniti

X

x

X

x

3:

•*

•

«<

•

«

•

z

Z

z

UlLUUlUlUlLtlUlUILU

jl-IJI

J

JJ

J

Jl

OOOOOCIOOOCI

OOOOOOOOOCI

x^xixixjEx

*-ci-f—»f»-iJ-»-H»-»-

c/>tAt/>u>c/)U>(/>bt>cni>

cuciiicifiiajUiuiMiuiU)

><>oO>o<t>e><>oc>ooo

oorteDooooclioooooc.

I

i

66

f\

I

£'

j

.

J

f~\

r~\

c

o

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

CDC-6400

POPFM1

POPFM2

SELECT

SOPMM

JCVSRP

INI

POP!

INIPOP2

UNIVAC-1108

POPFM1

POPFM2

SELECT

SOPMM

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

fage

73

75

11

79

81

83

85

87

89

91

93

95

97

99

101

103

105

107

109

111

113

115

68

Table

of

Contents

for

Appendix

1

(Continued)

GE-635

IBM

360-50

JCVSRP

INIPOP1

INIPOP2

POPFM1

POPFM2

SELECT

SOPMM

JCVSRP

INIPOP1

INIPOP2

POPFM1

POPFM2

SELECT

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Load

Binary

Program

and

Go

Compile

Source

Program

and

Go

Compile

Source

Program

and

Go

Compile

Source

Program

and

Go

Page

117

119

121

123

125

127

129

131

133

135

137

139

141

143

145

147

149

151

153

155

157

159

161

69

Table

of

Contents

for

Appendix

1

(Continued)

Page

SOPMM

Compile

Source

Program

and

Go

163

JCVSRP

Compile

Source

Program

and

Go

165

INIPOP1

Compile

Source

Program

and

Go

167

INIPOP2

Compile

Source

Program

and

Go

169

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

Units

-«u^^

CDC-6400

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

EOR

EOF

CDC-6400

7,8,9

punch

Column

1

6,7,8,9

punch

Column

1

UNI-1108

No

Entry

@bFIN

Column

1

-5

GE-635

$bbbbbbENDJOB

***

EOF

IBM

360-50

No

Entry

72

JCVS

USAGE

FORM

Function:

POPFM

1

Computer:

CDC

-

6400

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

INPUT

TAPE

1

TAPES

TAPE

2

SCRATCH"'

TAPE

3

\^

i

N/A""

CARD

INPUT

JOB

DECK

/

A

PRINTED

OUTPUT

[*"

OUTPUT

""]

|

Standard

|

Standard

Carriage

Form

Control

I

Tape

j

L

i

CARD

OUTPUT

PUNCH

!

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(1)

SEQUENCE,

14156,

SMA

JOB,

930u7,

10,

35000.

POPFM

1

CG

REQUEST,

TAPE

2,

HI.

(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

JCVS

USAGE

FORM

Function:

POPFM

1

Computer:

CDC

-6400

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

OUTPUT

.

TAPES

TAPE

2

TAPE

1

N/A

;

-J,

j

New

Population

File

TAPE

3

N/A

i

CARD

INPUT

CARD

READER

EMPTY

__PRINTED

OUTPUT_

"OUT

j

PUT

!

Standard

AUDIT

.

Carriage

FILE-PF

!

Control

'Tape

j

(Optional)

CARD

OUTPUT

PUNCH"

/

/.

.

...

i

PUNCH

F

LE-PF

/

v

V

(Optional)

74

JCVS

USAGE

FORM

Function:

POPFM

1

Computer:

CDC

-

64u0

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

INPUT

TAPE

1

)

N/A

TAPES

TAPE

2

SCRATCH

i

TAPE

3

L

N/A"

—«

CARD

INPUT

i

JOB

DECK

i

•

PRINTED

OUTPUT

OUTPUT"

:

Standard

Caniage

Form

Control

Tape

J

I

CARD

OUTPUT

PUNCH

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(D

SEQUENCE,

14156,

SMA

JOB,

93007,

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:

POPFM

1

Computer:

CDC

-

6400

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

OUTPUT

TAPES

"TAPE

2

New

Population

File

CARD

INPUT

CARD

READER

EMPTY

PRINTED

OUTPUT^

OUTJPUf'

!

Standard

AUDIT

Carriage

FILE-PF

|

Control

Tape

y

(Opti

onal)

CARD

OUTPUT

PUNCH

/

!

PUNCH

FILE-PF-

V

__(Oprtona

]}

76

Function:

POPFM

2

Computer:

CDC

-

6400

Operating

Philosophy:

Stage:

TAPE

1

JCVS

USAGE

FORM

Compile

Source

Program

and

Go

INPUT

TAPES

_

TAPE

2

Old

Population

File

j

SCRATCH

TAPE

3

CARD

INPUT

JOB

DECK

1

|

PRINTED

OUTPUT^

"OUTfPUT

"1

j

Standard

Carriage

Form

Control

Tape

._

CARD

OUTPUT

PUNCH

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(1)

SEQUENCE,

14156,

SMA

JOB,

93007,

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

JCVS

USAGE

FORM

Function:

POPFM

2

Computer:

CDC

-

6400

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

OUTPUT

TAPES

TAPE

3

i

CARD

INPUT

CARD

READER

EMPTY

PRINTED

OUTPUT_

OUTPUT

"

1

Standard

;

Carriage

!

Control

Tape

ILL

I

CARD

OUTPUT

PUNCH

L

/

j

I

PUNCH

FILE-PF

L.

V

(Optional)

78

JCVS

USAGE

FORM

Function:

POPFM

2

Computer:

CDC

-

6400

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

INPUT

•

TAPES

TAPE

1

Old

Population

File

TAPE

2

SCRATCH

TAPE

3

J

CARD

INPUT

f

JOB

DECK

|

[

-

A

I

—

-----

_J

PRINTED

OUTPUT

;

Standard

Carriage

Form

Control

Tape

i

CARD

OUTPUT

PUNCH

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(1)

SEQUENCE,

14156,

SMA

JOB,

93007,

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

JCVS

USAGE

FORM

Function:

POPFM

2

Computer:

CDC

-

6400

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

OUTPUT

TAPES

TAPE

2

TAPE

1

l

Old

Population

File

j

New

Population

File

TAPE

3

N/A

1

CA

RD

INPUT

INPUT"'

CARD

READER

EMPTY

PRINTED

OUTPUT

"

OUf

PUT

I

Standard

AUDIT

;

Carriage

FILE-PF

Control

Tape

(Optional)

—i

CARD

OUTPUT

PUNCH"

PUNCH

FILE-PF

(Optional)

80

JCVS

USAGE

FORM

Function:

SELECT

Computer:

CDC

-

64*ju

Operating

Philosophy:

Comoile

Source

Program

and

Go

Stage:

INPUT

TAPE

1

Pooulation

File

TAPES

TAPE

2

a

SCRATCH

N/A

J

CARD

INPUT

/:

L

JOB

DECK

A\

PRINTED

OUTPUT

CARD

OUTPUT

!

PUNCH

|

Standard

'

Standard

Carriage

Form

Control

CARD

PUNCH

Tape

READY

L_

»

JOB

DECK

STRUCTURE

(1)

SEQUENCE,

14156,

SMA

JOB,

93u07,

10,

3500u.

SELECT

REQUEST,

TAPE

1,

HI.

(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

JCVS

USAGE

FORM

Function:

SELECT

Computer:

CDC

-

6400

Operating

Philosophy:

Corrmile

Source

Program

and

Go

Stage:

OUTPUT

TAPE

1

V__

;i

Population

File

U—

TAPES

"

TAPE

2

I

V-

1.

:

Source

Program

File

TAPE

3

/

M/A

CARD

INPUT_

INPUT

CARD

READER

EMPTY

L

PRINTED

OUTPUT

I

Standard

AUDIT

Carriage

FILE-S

Control

|

(Optional)

~

'

•

Tape

...A

CARD

OUTPUT

PUNCH"

/

•

/

PUNCH

FILE-S

(Optional)

82

JCVS

USAGE

FORM

Function:

SELECT

Computer:

CDC

-

6400

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

INPUT

TAPES

TAPE

1

Pooulation

File

_.i

TAPE

2

SCRATCH

TAPE

3

N/A

CARD

INPUT

L

'

JC

-/I

1

JOB

DECK

|

J

PRINTED

OUTPUT

]

|

Standard

!

Standard

Carriage

Form

I

Control

Tape

CARD

OUTPUT

PUNCH

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(1)

SEQUENCE,

14156,

SMA

JOB,

93J07,

10,

35000.

SELECT

REQUEST,

TAPE

1,

HI.

(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

JCVS

USAGE

FORM

Function:

SELECT

Computer:

CDC

-

64U0

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

OUTPUT

TAPE

1

Population

File

.

TAPES

TAPE

2

j

Source

Program

File

TAPE

3

N/A

CARDJNPUT

INPUT

'

CARD

READER

EMPTY

PRINTED

OUTPUT

r

AUDIT

Standard

Carriage

FILE-S

i

.

Control

y

Tape

(Ootional)

1

CARD

OUTPUT

PUNCH

r

L

/

S

PUNCH

FILE-S

1..

._.

-

.

.V

(Ootional)

84

JCVS

USAGE

FORM

Function:

SOPMM

Computer:

CDC

-

6400

Operating

Philosophy:

Comoile

Source

Program

and

Go

Stage:

INPUT

•

TAPES

TAPE

1

Q

[Old

Source

Program

File

TAPE

2

SCRATCH

1_

TAPE

3

_l

CARD

INPUT

/:

JOB

DECK

|

>

V

I

-._

J

I

PRINTED

OUTPUT^

OUTF|UT

i

Standard

!

Standard

Carriage

Form

Control

I

Tape

i

CARD

OUTPUT

PUNCH

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(1)

SEQUENCE,

14156,

SMA.

JOB,

93007,

10,

35000.

SOPMM

REQUEST,

TAPE

1,

HI.

(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

JCVS

USAGE

FORM

Function:

SOPMM

Computer:

CDC

-

6400

Operating

Philosophy:

Comoile

Source

Program

and

Go

Stage:

OUTPUT

TAPE

1

i

TAPES

TAPE

2

TAPE

3

Old

Source

Program

FileJ

New

Source

Program

Filej

N/A

CARD

INPUT

CARD

READER

EMPTY

_

PRINTED

OUTPUT

OUTJPUT

I

Standard

1

AUDIT

!

Carriage

FILE-SP

|

j

Control

Tape

y

(Optional)

L

CARD

OUTPUT

PUNCH

/"

—

./

1

PUNCH

FILE-SP

!

V

(Ootional)

86

JCVS

USAGE

FORM

Function:

SOPMM

Computer:

CDC-6400

Operating

Philosophy:

Stage:

TAPE1

Load

Binary

Deck

and

Go

INPUT

TAPES

TAPE2

Old

i.oy

rce_

Progra

ml

i

Lei

L

v

SCRATCH

TAPE

3

JU/A

i

CARD

INPUT

/"

JOB

DECK

PRINTED

OUTPUT

!

Standard

Form

Standard

Carriage

Control

Tape

1

CARD

OUTPUT

PUNCH

i

CARD

PUNCH

READY

i

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

JCVS

USAGE

FORM

Function:

SOPMM

Computer:

CDC-6400

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

OUTPUT

TAPES

TAPE1

TAPE2

>

J

i

^

11

.Qid_So.y

rss-

Program

JEi

W

New

_Soiu:ce..PcpgrairLJE

ill

TAPE3

u,

--N/A

1

CARD

[NPUT_

INPUT

CARD

READER

EMPTY

PRINTED

O

UTPUT

OufpUT

,

j

I

}

Standard

!

AUDIT

,

Carriage

FILE-SP

i

Control

Tape

1

CARD

OUTPUT

PUNCH

-

-V

PUNCH

FILE-Sp

-

V

88

JCVS

USAGE

FORM

FmcKon:

JCVSRP

Computer:

CDC-6400

Operating

Philosophy:

Stage:

TAPE1

_N/A

Compile

Source

Program

and

Go

INPUT

•

TAPES

TAPE2

„N/A

TAPE

3

V

!

PopulolLojifile.

CARD

[NPUJ_

INPUT

/::::z?j

JOB

DECK

j

)

I

—

PRINTED

OUTPUT

Standard

Form

\

Standard

Carriage

Control

Tape

CARD

OUT

PUT

PUNCH

CARD

PUNCH

READY

L

_..

JOB

DECK

STRUCTURE

0)

SEQUENCE,

14156,

SMA.

JOB,

93007,

10,

35000.

JCVSRP.

REQUEST,

TAPE3,

HI.

(XXXX/NORING)

COBOL

(LXRM).

LGO.

(End

of

Record

Card)

(COBOL

Source

Program

Deck

-

JCVSRP)

(End

of

Record

Card)

(Control

Card-RP)

(End

of

File

Card)

XXXX

=

Population

File

Reel

Number

89

•

<'/!

•

JCVS

USAGE

FORM

Function:

JCVSRP

Computer:

CDC-6400

Operating

Philosophy:

Stage:

TAPE1

._N/A_

Compile

Source

Program

and

Go

OUTPUT

TAPES

TAPE2

I

J

M/A

JL

pQpuloiLgri

File..

_

TAPE3

CARD

INPUT

CARD

READER

EMPTY

PRINTED

OUTPUT

!

Standard

AUDIT

,

Carriage

FILE-RP

j

i

Control

J

Tape

CARD

OUTPUT

PUNCH

FILE

„._

/

N/A

90

JCVS

USAGE

FORM

Function:

JCVSRP

Computer:

CDC-6400

Operating

Philosophy:

Stage:

TAPE1

_N/A

Load

Binary

Deck

and

Go

INPUT

TAPES

TAPE2

TAPE

3

PQp.u.lotiQo_Eile_.

—i

CARD

INPUT

zz:

A

JOB

DECK

,.

J>RINTED

OUTPUT^

OUTPUT

|s

tandard

Standard

Carriage

Form

Control

I

Tape

L

j

I

CARD

OUTPUT

PUNCH

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

0)

SEQUENCE,

14156,

SMA.

JOB,

93007,

10,

35000.

REQUEST,

TAPE3,

HI.

(XXXX/NORING)

LOAD

(INPUT)

EXECUTE

(JCVSRP)

(End

of

Record

Card)

(Binary

Program

Deck

-

JCVSRP)

(End

of

Record

Card)

(Control

Card

-

RP)

(End

of

File

Card)

XXXX

=

Population

File

Reel

Number

91

JCVS

USAGE

FORM

Function:

JCVSRP

Computer:

CDC-6400

Operating

Philosophy:

Stage:

Load

Binary

Deck

and

Go

OUTPUT

TAPES

TAPE2

TAPE3

/

._n

_[

Pggyja

tion

F

i

I

<

CARD

INPUT

PRINTED

OUTPUT

JDUITPUT

:

Standard

!

AUDIT

Carriage

FILE-RP

;

Control

L

y

Tape

..i

CARD

OUTPUT

PUNCH

/

/.

_.__

,

/

i

PUNCH

FILE

j

M4L_

92

JCVS

USAGE

FORM

Function:

INIPOP1

Computer:

CDC-6400

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

INPUT

TAPE1

N/A._

TAPES

TAPE

2

SCRATCH-—.

TAPE3

V

-iCMCH

i

r

CARD

INPUT

z:

/

'

JOB

DECK

PRINTED

OUTPUT

!

Standard

!

Standard

Carriage

Form

Control

Tape

n

L_

_

CARD

OUTPUT

PUNCH

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

0)

SEQUENCE,

14156,

SMA.

JOB,

93007,

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

JCVS

USAGE

FORM

Function:

INIPOP1

Computer:

CDC-6400

Operating

Philosophy:

Stage:

TAPE

1

Ml

Compile

Source

Program

and

Go

OUTPUT

_L

TAPES

TAPE2

__..

!

TAPE3

Population

File

j_

..SCRATCH

i

.._!

CARD

IN

PUT

INPUT

CARD

READER

EMPTY

PRINTED

OUTPUT

Out

PUT

—

-

—,

;

I

!

Standard

Carriage

L

AUDIT

FILE-IP

Control

Tape

J

CARD

OUTPUT

PUNCH

r

/

PUNCH

FILE-IP

__

V

„--»..».

.

*»

•

/

94

JCVS

USAGE

FORM

Function:

INIPOP1

Computer:

CDC-6400

Operating

Philosophy:

Stage:

TAPE1

I

......

......N/A

CARD

INPUT

Z:::ZL7

JOB

DECK

J

_..

I

Load

Binary

Deck

and

Go

INPUT

TAPES

TAPE

2

7.1

_SCRATCH

PRINTED

OUTPUT

Standard

Form

Standard

Carriage

Control

Tape

L

TAPE3

SCRATCH

1

CARD

OUTPUT

_

PUNCH

I

CARD

PUNCH

READY

•

JOB

DECK

STRUCTURE

0)

SEQUENCE,

14156,

SMA.

JOB,

93007,

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

JCVS

USAGE

FORM

Function:

INIPOP1

Computer:

CDC-6400

Operating

Philosophy:

Stage:

TAPE1

Load

Binary

Deck

and

Go

OUTPUT

TAPES

TAPE

2

Q

N/A_

Population

File

TAPE3

11

SCRATCH

CARD

INPUT

CARD

READER

EMPTY

PRINTED

OUTPUT

^

OUTPJUT

I

Standard

AUDIT

;

Carriage

'

FILE-IP

Control

\

Tape

CARD

OUTPUT

PUNCH

—I

/

PUNCH

FILE-lp;/

,/

96

JCVS

USAGE

FORM

Funcfion:

INIPOP2

Computer:

CDC-6400

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

INPUT

TAPE

1

TAPES

TAPE

2

L

Old

Population

File

SCRATCH

TAPE3

>

SCRATCH

J

CARD

INPUT

I'

JOB

DECK

i

V

l_.

PRINTED

OUTPUT_

OUTPUT

|

standard

]

Standard

Carriage

Form

Control

I

Tape

CARD

OUTPUT

PUNCH

!

CARD

PUNCH

READY

i

JOB

DECK

STRUCTURE

0)

SEQUENCE,

14156,

SMA.

JOB,

93007,

10,

35000.

INIPOP2.

REQUEST,

TAPE1,

HI.

(XXXX/NORING)

COBOL

(LXRM).

LGO.

(End

of

Record

Card)

(COBOL

Source

Program

Deck

-

INI

POP)

(End

of

Record

Card)

(Control

Card-IP)

(End

of

File

Card)

XXXX

=

Population

File

Reel

Number

97

JCVS

USAGE

FORM

Function:

INIPOP2

Computer:

CDC-6400

Operating

Philosophy:

Stage:

Compile

Source

Program

and

Go

OUTPUT

_^

TAPES

TAPE2

TAPE3

SCRATCH

.

A

PRINTED

OUTPUT

"OUTRJT

I

Standard

AUDIT

|

Carriage

FILE-IP

I

j

Control

Tape

i

CARD

OUTPUT

PUNCH

r

/

PUNCH

FILE-IP/

98

JCVS

USAGE

FORM

Function:

INIPOP2

Computer:

CDC-6400

Operating

Philosophy:

Stage:

TAPE1

Load

Binary

Deck

and

Go

INPUT

TAPES

TAPE2

Old

Population

File

SCRATCH

TAPE

3

SCRATCH

CARD

INPUT

z::z:

JOB

DECK

J

PRINTED

OUTPUT

Standard

I

Standard

Carriage

Form

Control

'

Tape

I

CARD

OUTPUT

PUNCH

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

0)

SEQUENCE,

14156,

SMA.

JOB,

93007,

10,

35000.

INIPOP2.

REQUEST,

TAPE1,

HI.

(XXXX/NORING)

LOAD

(INPUT)

EXECUTE

(INIPOP)

(End

of

Record

Card)

(Binary

Program

Deck

-

INI

POP)

(End

of

Record

Card)

(Control

Card-IP)

(End

of

File

Card)

XXXX

=

Population

File

Reel

Number

99

JCVS

USAGE

FORM

Function:

INIPOP2

Computer:

CDC-6400

Operating

Philosophy:

Stage:

TAPE1

Load

Binary

Deck

and

Go

OUTPUT

TAPES

TAPE

2

.1

_Old

P°fwlaJrfo2)_FjJe_

i_

NewPopulation

File

TAPE

3

v

ri

SCRATCH

i

CARD

INPUT_

INPUT

CARD

READER

EMPTY

PRINTED

OUTPUT

]

j

Standard

!

AUDIT

,

Carriage

FILE-IP

j

Control

.•

j

Tape

L-

CARD

OUTPUT

PUNCH

—I

i

I

PUNCH

FILE-IP

V

100

JCVS

USAGE

FORM

Function:

POPFM1

Computer:

UNI

VAC

-

1108

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

INPUT

•

TAPES

UNISERVO

A

I

UNISERVO

B

L

N/A

SCRATCH

UNISERVO

C

v.

I

N/A

-1

CARD

INPUT

[CARD

READER

EIGHTY!

L

i

i:

JOB

DECK

|

L-

_

V

_J

PRINTED

OUTPUT

'"PRINTER"

'

|

"1

:

Standard

Form

L

Carriage

Control

Tape

p

CARD

OUTPUT

"A'RD

PUNCH

EIGHTY]

CARD

PUNCH

READY

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

JCVS

USAGE

FORM

Function:

POFfMl

Computer:

UNIVAC-1108

Operating

Philosophy:

Compile

Source

Program

a

no

Go

Stage:

OUTPUT

UNISERVO

N/A

TAPES

UNISERVO

B

t

New

Population

File

UNISERVO

I

N/A

CARD

INPUT

;

CARD

READER

EIGHTY

I

CARD

I

;

READER

!

EMPTY

PRINTED

OUTPUT

PRINTER

i

—<

i

I

j

Standard

!

AUDIT

Carriage

FILE-PF

j

Control

L

J

/

(Optional)

Tape

CARD

OUTPUT

(CARD

PUNCH

EIGHTY

1

I

L

i

/

PUNCH

FILE-PF

(Optional)

102

JCVS

USAGE

FORM

Function:

POPFM1

Computer:

UNIVAC-1108

Operating

Philosophy:

Lcxid

Binary

Deck

and

Go

Stage:

INPUT

UNISERVO

(

1

N/A

TAPES

UNISERVO

B

/

/.

J

_.

SCRATCH

UNISERVO

i

\

N/A

CARD

INPUT

'CARD

READER

EIGHTY

:

/

-

/[

i

JOB

DECK

I,

i

....

'/

I

PRINTED

OUTPUT

PRINTER

'standard

Standard

Caniage

Form

Control

Tape

1

CARD

OUTPUT

CARD

PUNCH

EIGHr

CARD

PUNCH

READY

...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

JCVS

USAGE

FORM

Function:

Computer:

Operating

Philosophy:

Stage:

POPFM1

UNIVAC

-1108

Load

Binary

Deck

and

Go

OUTPUT

TAPES

UNISERVO

1

N/A

UNISERVO

B

I

(

New

Population

File

UNISERVO

N/A

CARD

INPUT

(CARD

READER

EIGHTY

CARD

READER

EMPTY

PRINTED

OUTPUT

i

AUDIT

FILE-PF

(Optional)

ifi

PRINTER

1

Standard

Carriage

Control

Tape

!

i

J

CARD

OUTPUT

CARD

PUNCH

EIGHTY

/

{

I

PUNCH

FILE-PF

(Optional)

104

JCVS

USAGE

FORM

Function:

POPFM2

Computer:

UNI

VAC

-1108

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

INPUT

TAPES

UNISERVO

A

!

UNISERVO

B

!

V

(

>

(

1

%

>

[

Old

Population

File

SCRATCH

UNISERVO

\

/

N/A

CARD

INPUT

CARD

READER

EIGHTYj

z.

::.

f

JOB

DECK

V

J

PRINTED

OUTPUT

PRINTER

Sta

nda

rd

Form

Standard

Carriage

Control

Tape

•

CARD

OUTPUT

CARD

PUNCH

EIGHTY*

I

CARD

PUNCH

READY

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

JCVS

USAGE

FORM

Function:

Computer:

Operating

Philosophy

Stage:

POPFM2

UNIVAC

-1108

UNISERVO

Compile

Source

Program

and

Go

OUTPUT

TAPES

A

UNISERVO

B

..n

[

Old

Population

File

j

New

Population

File

UNISERVO

C

1

V

N|/A

f

CARD

INPUT

CARD

READER

EIGHTY

CARD

READER

EMPTY

1

|

PR]

PRINTED_OUTPUT_

PRINTER

|

I

Standard

!

AUDIT

Carriage

FILE-PF

I

|

Control

Tape

(Optional)

1

CARD

OUTPUT

CARD

PUNCH

EIGHTY

/

PUNCH

FILE-PF

/

4—

(Optional)

106

JCVS

USAGE

FORM

Funciion:

POPFM2

Computer:

UNIVAC-1108

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

INPUT

UNISERVO

(

\

[

Old

Population

File

j

TAPES

UNISERVO

B

C

i

SCRATCH

UNISERVO

^

N/A

CARD

INPUT

PRINTED

OUTPUT

•

CARD

READER

EIGHTY'

[

PRINTER

!

standard

:

f

JOB

DECK

.',

:

1/

•

Standard

Carriage

Form

Control

i

Tape

i

L_

i

JOB

DECK

STRUCTURE

0)

CARD

OUTPUT

["'

""

1

'CARD

PUNCH

EIGHTY

1

CARD

PUNCH

READY

@RUN1

POPFM2,DDLG

/

5

/

300

@

ASG

B

A

=

XXXX

=

POPFILE1

reel

number

(Binary

Program

Deck

-

POPFM)

XQT

POPFM2

(Control

Card

-

PF)

(Current

File

-

PF

Deck)

©

FIN

107

JCVS

USAGE

FORM

Function:

POPFM2

Computer:

UNIVAC

-

1108

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

OUTPUT

UNI

SERVO

TAPES

UNISERVO

B

UNISERVO

3

v

rj

Old

Population

File

|

New

Population

File

N/A

i

CARD

INPUT

CARD

READER

EIGHTY

CARD

READER

EMPTY

PRINTED

OUTPUT

PRI

hflTER

!

Standard

AUDIT

;

Carriage

FILE-PF

j

|

Control

Tape

(OpHonol)

CARD

OUTPUT

CARD

PUNCH

EIGHTY

r~

I

PUNCH

FILE-Pf

L

-

-.

.v

(Optional)

108

JCVS

USAGE

FORM

Function:

SELECT

Computer:

UNIVAC-1108

Operating

Philosophy:

Compile

Source

Program

and

Go

Stoge:

INPUT

TAPES

UNISERVO

A

Q

Population

File

CARD

INPUT

CARD

READER

EIGHTY!

/

'

JOB

DECK

UNISERVO

B

f

N

I

SCRATCH

PRINTED

OUTPUT

i

PRINTER

!

Standard

Form

Standard

Carriage

Control

Tape

t

-

UNISERVO

C

v

I

\

N/A

i

CARD

OUTPUT

'CARD

PUNCH

EIGHTY

1

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(D

@

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

XXXX

=

POPFILE1

reel

number

YYYY

=

JOVSP

reel

number

109

JCVS

USAGE

FORM

Function:

Computer:

Operating

Philosophy:

Stage:

UNISERVO

SELECT

UNI

VAC

-1108

Compile

Source

Program

and

Go

OUTPUT

TAPES

Population

File

UNISERVO

B

Source

Program

File

UNISERVO

i

N/A

CARD

INPUT

IcARD

READER

EIGHTY

CARD

READER

EMPTY

PRINTED

OUTPUT

J>RI!NTER

|

!

Standard

;

AUDIT

Carriage

FILE-S

j

Control

,,

—

Tape

!

IQgHonallJ

-i

CARD

OUTPUT

CARD

PUNCH

EIGHTY

r

~

/

j

PUNCH

FILE-S

1

:

/

_

.IQefilogal)

110

JCVS

USAGE

FORM

Function:

SELECT

Computer:

UNIVAC-1108

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

INPUT

UNISERVO

^

Population

File

{

TAPES

UNISERVO

(

I

v....

.

i

SCRATCH

UNISERVO

(

~\

\

i

S^

N/A

CARD

INPUT

•CARD

READER

EIGHTY

JOB

DECK

/]'

•

!

i

l,'

PRINTED

OUTPUT

PRINTER

Standard

Form

Standard

i

Carriage

Control

Tape

JOB

DECK

STRUCTURE

0)

@

RUN

SELECT,DDLG^^OO

@

ASG

A

=

XXXX

B

=

YYYY

(Binary

Program

Deck

-

Select)

XQT

SELECT

(Control

Card

-

S)

(Test

Selection

File

Deck)

@

FIN

CARD

OUTPUT

I"

"

CARD

PUNCH

EIGHTY

CARD

PUNCH

READY

XXXX

=

POPFILE1

reel

number

YYYY

=

JOVSP

reel

number

111

JCVS

USAGE

FORM

Function:

SELECT

Computer:

UNIVAC-1108

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

OUTPUT

UNISERVO

TAPES

UNISERVO

I

Population

File

i_j>ource

Program

File_

j

UNISERVO

C

N/A

I

CARD

INPUT

CARD

READER

EIGHTY

CARD

READER

EMPTY

!

L

PRINTEDOUTPUT

PRINTER^

|

I

Standard

AUDIT

FILE-S

UOfitionall

Carriage

j

Control

Tape

|

_i

CARD

OUTPUT

[CARD

PUNCH

EIGHTY

t

i

r

7

/

t

—

PUNCH

FILE-S

\»

(Optional)

112

JCVS

USAGE

FORM

Function:

SOPMM

Computer:

UNIVAC-1108

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

INPUT

UNISERVO

D

TAPES

I

UNISERVO

B

V

Old

Source

Program

Ft]

SCRATCH

UNISERVO

C

r

^

v.

/,

N/A

J

CARD

INPUT

ICARD

READER

EIGHTYl

I

!

JOB

DECK

J

PRINTED

OUTPUT

PRINTER

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

!CARD

PUNCH

EIGHTY

j

!

CARD

PUNCH

i

READY

JOB

DECK

STRUCTURE

(D

@

RUN

SOPMM,DDLG,5,300

@

ASG

A

=

XXXX,B

@

BREI

COB

SOPMM

(COBOL

Source

Program

Deck

-

SOPMM)

@

XQT

SOPMM

(Control

Card

-

SP)

(Current

File

-

SP

Deck)

@FIN

XXXX

=

JOVSP

reel

number

113

JCVS

USAGE

FORM

Function:

SOPMM

Computer:

UNIVAC-1108

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

OUTPUT

UNI

SERVO

A

TAPES

UNISERVO

B

Old

Source

Program

File)

New

Source

Program

Fil^

UNISERVO

C

Q

N/A

CARD

INPUT

CARD

READER

EIGHTY

CARD

READER

EMPTY

.

J

PRINTED

OUTPUT

PRINTER

!

Standard

;

I

AUDIT

;

Carriage

FILE-SP

j

|

Control

Tape

jLQptlonaJl

CARD

OUTPUT

CARD

PUNCH

EIGHTY

/

iPUNCH

FILE-SP,

L

/

^Optional)

114

JCVS

USAGE

FORM

Function:

SOPMM

Computer:

UNIVAC-1108

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

INPUT

TAPES

...

UNISERVO

A

I

UNISERVO

B

I

i

K

i

V

Old

Source

Program

File

SCRATCH

UNISERVO

V.

(

N/A

CARD

INPUT

'CARD

READER

EIGHTYl

/

!

f

JOB

DECK

:

j.

L

-..-

V

I

PRINTED

OUTPUT

I

PINTER

|

standard

Standard

Carriage

Form

Control

Tape

i.

.

CARD

OUTPUT

iCARD

PUNCH

EIGHTH

CARD

PUNCH

READY

1

JOB

DECK

STRUCTURE

(1)

@

RUN

SOPMM,

DDLG^^OO

@

ASG

A

=XXXX,B

(Binary

Program

Deck

-

SOPMM)

@

XQT

SOPMM

(Control

Card

-

SP)

(Current

File

-

SP

Deck)

@

FIN

XXXX

=

JOVSPreel

number

115

JCVS

USAGE

FORM

Function:

Computer:

Operating

Philosophy

Stage:

SOPMM

UNI

VAC

-

1108

UNISERVO

Load

Binary

Deck

and

Go

OUTPUT

TAPES

I

UNISERVO

B

UNISERVO

Old

Source

Program

File!

New

Source

Program

Filje

.1

N/A

„C

A

!*D

INPUT

CARD

READER

EIGHTY

CARD

READER

EMPTY

i

_PRINTED

OUTPUT

PRINTER

!

Standard

'

AUDIT

;

Carriage

FILE-SP

i

I

Control

L...y

'

—

Tape

tlonaljj

CARD

OUTPUT

CARD

PUNCH

EIGHTY

1

/-

/

I

PUNCH

FILE-S(>

I

-.

....

'/

(Optional)

A

116

JCVS

USAGE

FORM

Function:

JCVSRP

Computer:

UNIVAC-1108

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

INPUT

UNISERVO

u.

N/A

TAPES

UNISERVO

B

L

N/A

UNISERVO

C

/""

"\

Population

File

CARD

INPUT

f"

•

CARD

READER

EIGHTY

:

L

/,

i

I

£_

/

[

JOB

DECK

L

/

!

i

PRINTED

OUTPUT

PRINTER

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

r

•

1

[CARD

PUNCH

EIGHTY^

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

0)

@

RUN

1

JCVSRP,DDCG^^OO

@

ASG

C

=

XXXX

@

BREI

COB

JCVSRP

(COBOL

Source

Program

Deck

-

JCVSRP)

@

XQT

JCVSRP

XXXX

=

POPFILE1

reel

number

(Control

Card

-

RP)

@

FIN

117

JCVS

USAGE

FORM

Function:

JCVSRP

Computer:

UNIVAC-1108

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

OUTPUT

TAPES

I

UNISERVO

N/A

UNISERVO

B

1

N/A

]

UNISERVO

C

c

l

j

Population

File

Reports

|

CARD

INPUT

CARD

READER

EIGHTY

CARD

READER

EMPTY

I

1

!

I

PRINTED

OUTPUT

PINTER

!

Standard

'

Carriage

!

Control

Tape

!

AUDIT

!

FILE-RP

...i

CARD

OUTPUT

CARD

PUNCH

EIGHTY

/

<

PUNCH

FILE-RP

N/A

118

JCVS

USAGE

FORM

Fu

-.ctior:

JCVSRP

Ccinputcr:

UNIVAC-1108

Op^rati.ig

Philosophy:

Load

Binory

Deck

and

Go

Stage:

INPUT

JNISERVO

)

TAPES

UMISERVO

B

v..

i

N/A

UNI5ERVO

!

(

)

j

Popu

ation

File

_

CARD

INPUT

CARD

READER

EIGHTY

I

/:

JOB

DECK

L

»

II

!

>,

J/

i

...j

PRINTED

OUTPUT

i

PRINTER

I

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

;

CARD

PUNCH

EIGHTY

CARD

PUNCH

READY

!

JOB

DECK

STRUCTURE

0)

(§

RUN

1

JCVSRP,

DDLG,5,300

(5

ASG

C

=

XXXX

(Binary

Program

Deck

-

JCVSRP)

<9

XQT

JCVSRP

(Control

Card

-

IP)

(5

FIN

XXXXX

=

POPFILE1

reel

number

llv

JCVS

USAGE

FORM

Function:

JCVSRP

Computer:

UNIVAC«1108

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

OUTPUT

!

UNISERVO

A

_

1

N/A

UNISERVO

C

Population

File

CARD

INPUT

CARD

READER

EIGHTY

CARD

READER

EMPTY

PRINTED

OUTPUT

PRINTER

i

I

Standard

AUDIT

Carriage

1

CARD

OUTPUT

FILE-RP

y

Control

Tape

[CARD

PUNCH

EIGHTY

/

"

•

/

1

PUNCH

FILE

j

/)

/

J

j

1/

N/A

y

120

JCVS

USAGE

FORM

Function:

INIPOP1

Computer:

UNIVAC-1108

Operating

Philosophy:

Compile

Source

Program

and

Go

Slage:

INPUT

UNISERVO

A

N/A

TAPES

UNISERVO

B

\

I

\

SCRATCH

.i„..

UNISERVO

\

L

SCRATCH

CARD

INPUT

iCvRD

READER

EIGHTY

zz:::

f

JOB

DECK

7i

i

.J/'

PRINTED

OUTPUT

|

PRINTER

!

standard

Standard

Carriage

Form

Control

Tape

<

CARD

OUTPUT

CARD

PUNCH

EIGHTY;

I

CARD

PUNCH

READY

\

JOB

DECK

STRUCTURE

0)

@

RUN

T

INI

POP,

DD1

00,5,300

@

ASG

B,C

@

BREI

COB

INI

POP

(COBOL

Source

Program

Deck

-

INI

POP)

@XQT

INI

POP

(Control

Card

-

IP)

(Current

File

-

PF

Deck)

@FIN

121

Function:

Computer:

Operating

Philosophy

Stage:

UNISERVO

JCVS

USAGE

FORM

INI

POP!

UNI

VAC

-

1108

Compile

Source

Program

and

Go

OUTPUT

TAPES

UNISERVO

B

i

I

Population

File

UNISERVO

SCRATCH

i

CARD

INPUT

CARD

READER

EIGHTY

CARD

READER

EMPTY

L_

i

PRINJEDOUTPUT_

PRJNTER

!

Standard

I

AUDIT

Carriage

FILE-IP

;

Control

Tape

(Optional)

~J

CARD

OUTPUT

CARD

PUNCH

EIGHTY

f-

~

7

!

PUNCH

FILE-IP

-'

(Optional)

122

JCVS

USAGE

FORM

Function:

INIPOP1

Computer:

UNIVAC-1108

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

INPUT

UNISERVO

')

N/A

TAPES

i

UNISERVO

B

v.

t

SCRATCH

UNISERVO

SCRATCH

r

CARD

INPUT

CARD

READER

EIGHTYl

!

ZZIZTi!

!

JOB

DECK

PRINTED

OUTPUT

i

PRINTER

:

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

r

""

1

'CARD

PUNCH

EIGHTY

1

CARD

PUNCH

READY

(

JOB

DECK

STRUCTURE

0)

@RUN1

INI

POP,

DD1LG,5,300

@

ASG

B

f

C

(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:

Stage:

UNISERVO

Load

Binary

Deck

and

Go

OUTPUT

TAPES

UNISERVO

SCRATCH

CARD

INPUT

CARD

READER

EIGHTY

CARD

READER

EMPTY

.1

PRINTED

OUTPUT_

PRINTER

i

Standard

AUDIT

Carriage

Control

Tape

FILE-IP

(Optio

nal)

•

i

CARD

OUTPUT

CARD

PUNCH

EIGHTY

r~

/

PUNCH

FILE-IP

i

;

/

i'

(Optional)

124

JCVS

USAGE

FORM

Function:

INIPOP2

Computer:

UNIVAC-1108

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

INPUT

UNISERVO

Old

Population

File

TAPES

UNISERVO

B

L

SCRATCH

UNISERVO

j....

\

SCRATCH

...i

CARD

INPUT

CARD

READER

EIGHTY!

f

JOB

DECK

r

j

PRINTED

OUTPUT

PRINTER

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

f""

'•

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

(COBOL

Source

Program

Deck

-

INI

POP)

@XQTINIPOP

XXXX

=

POPFILE1

reel

number

(Control

Card

-

IP)

FIN

25

Function:

Computer:

Operating

Philosophy

Stage:

JCVS

USAGE

FORM

INIPOP2

UNIVAC

-

1108

Compile

Source

Program

and

Go

OUTPUT

TAPES

UNISERVO

A

UNISERVO

B

Old

Population

F[le

i^Ne**

P°pyl°

T

L°_

n

'

:

''

e

UNISERVO

C

v

ri

SCRATCH

L

CARD

INPUT

PRINTED

OUTPUT

CARD

OUTPUT

CARD

READER

EIGHTY

PRINTER

CARD

PUNCH

EIGHTY

CARD

r

1

!

Standard

READER

i

AUDIT

Carriage

r

~~f

!

FILE-IP

i

Control

/

{

1

PUNCH

FILE-IP

1...

i'

EMPTY

l^

Tape

i

J9s&sss^L

i

(Optional)

126

JCVS

USAGE

FORM

Function:

INIPOP2

Computer:

UNIVAC-1108

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

INPUT

UNISERVO

s..

i

Old

Population

File

TAPES

UNISERVO

B

SCRATCH

UNISERVO

SCRATCH

CARD

INPUT

CARD

READER

EIGHTY

Z.

JOB

DECK

/)

_J

PRINTED

OUTPUT

!

PRINTER

'

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

CARD

PUNCH

EIGHTY^

CARD

PUNCH

READY

'.

-...

JOB

DECK

STRUCTURE

0)

@

RUN

1

INI

POP,

00210,5,300

@

ASG

A=XXXX,B,C

(Binary

Program

Deck

INI

POP)

@XQT

INI

POP

(Control

Card

-

IP)

@FIN

XXXX

=

POPFILE1

reel

number

127

JCVS

USAGE

FORM

Function:

INIPOP2

Computer:

UNIVAC

-

1108

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

OUTPUT

TAPES

UNI

SERVO

B

UNISERVO

A

J2

v—n

Old

Population

File

(

New

Population

File

j

UNISERVO

C

V

:;

SCRATCH

CARD

INPUT_

CARD

READER

EIGHTY

CARD

READER

EMPTY

L_.

PRINTED

OUTPUT_

PRINTER

!

Standard

I

AUDIT

Carnage

FILE-IP

I

Control

f

^

—

j

Tape

__{OeHoni)__

..-1

CARD

OUTPUT

CARD

PUNCH

EIGHTY

/

4-.

-

1

PUNCH

FILE-II

!

V

{Optional)

128

JCVS

USAGE

FORM

Function:

POPFM1

Computer:

GE-635

Operating

Philosophy:

Stage:

Compile

Source

Program

and

Go

INPUT

TAPES

A3

A4

v....

s

SCRATCH

1

^"'-

\

i

NA

!

CA

>RD

INPUT

PRINTED

OUTPUT

L

L...

...

Al

i

j

A2

Standard

1

Standard

Carriage

/

/i!

Form

Control

JOB

DECK

"f

|j

V

\

Tape

1

!

1

A6

N/A

i

CARD

OUTPUT

A5

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

0)

$

S

$

s

$

***

(8)

IDENT

COBOL

INCODE

06)

3154203,

DATDY

I

BMC

(COBOL

Source

Program

Deck

-

POPFM)

EXECUTE

LIMITS

SYSOUT

TAPE

SYSOUT

DATA

DUMP

15,32000

A2

A3,X3S,,POPFILEl

#/

SAVE

A5

Al

(Control

Card

-

PF)

(Current

File

-

PF

Deck)

ENDJOB

EOF

129

JCVS

USAGE

FORM

Function:

POPFM1

Computer:

GE-635

Operating

Phil

osophy:

Compile

Source

Program

and

Go

Stage:

OUTPUT

TAPES

A3

New

Population

File

A6

/

N/A

...i

CARD

INPUT

r

^

|

CARD

READER

EMPTY

«...

„.

PRINTED

OUTPUT

A2

!

I

Standard

AUDIT

|

Carriage

FILE-PF

(Optional)

Control

Tape

CARD

OUTPUT

A5

._!

i

/

-

I

PUNCH

FILE-PF

I

/

(Optional)

130

JCVS

USAGE

FORM

Function:

POPFM1

Computer:

GE-635

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

INPUT

A3

f"

"

(

c.

_

-

SCRATCH

TAPES

A4

I

N/A

A6

/"

N/A

CARD

INPUT

Al

/

i_.

JOB

DECK

i

).

!/

;

:"""

i

-

„.J

PRINTED

OUTPUT

i

A2

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

A5

CARD

PUNCH

READY

.

«

JOB

DECK

STRUCTURE

0)

$

***

EOF

(8)

(16)

$

s

IDE

NT

OPTION

3154203,

DATDY

COBOL

(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)

ENDJOB

XXXX

=

reel

number

131

JCVS

USAGE

FORM

Function:

POPFM1

Computer:

GE-635

Operating

Philosophy:

Stage:

A3

;i

Load

Binary

Deck

and

Go

OUTPUT

TAPES

A4

New

Population

File

|

1

N/A

A6

N/A

CARD

INPUT

Al

CARD

READER

EMPTY

PRINTED

OUTPUT

A2

I

AUDIT

FILE-PF

(O

ptional'

Standard

Carriage

Control

Tape

j

CARD

OUTPUT

A5

r

./-

/

I

PUNCH

FILE-PF

/

(Optional)

132

JCVS

USAGE

FORM

Function:

POPFM2

Computer:

GE-635

Operating

Philosophy:

Stage:

A3

r

V

^

SCRATCH

Compile

Source

Program

and

Go

INPUT

TAPES

!

"

i

A4

A6

*

/

i

*

!

--

l

!

v

-

j

Old

Population

File

j

N/A

CARD

INPUT

Al

JOB

DECK

/

PRINTED

OUTPUT

A2

Standard

Carriage

Form

Control

Tape

CARD

OUTPUT

A5

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(1)

(8)

$

S

$

s

$

s

$

I

DENT

COBOL

INC

ODE

06)

3154203,

DATDY

I

BMC

(COBOL

Source

Program

Deck

-

POPFM)

EXECUTE

LIMITS

SYS

OUT

TAPE

SYSOUT

DATA

DUMP

15,32000

A2

A3,X3S

A4,X4D

POPFILEl,,XXXX

A5

AT

(Control

Card

-

PF)

(Current

File

-

PF

Deck)

END

JOB

XXXX

=

reel

number

***

EOF

133

JCVS

USAGE

FORM

Function:

POPFM2

Computer:

GE-635

Operating

Philosophy:

Stage:

Compile

Source

Program

and

Go

OUTPUT

TAPES

A3

A4

A6

a

New

Population

File

,

'

a

Old

Population

File

N/A

C

ARD

INPU

T

Al

CARD

READER

EMPTY

PRINTED

OUTPUT

I

A2

!

AUDIT

FILE-PF

(Optional)

1

Standard

;

Carriage

Control

Tape

CARD

OUTPUT

A5

(PUNCH

FILE-Pf

.v

IQptionaJl

134

JCVS

USAGE

FORM

I

Function:

POPFM2

Computer:

GE-635

Operating

Philosophy:

Stage:

.

i

A3

1

SCRATCH

CARD

INPUT

Al

l-

-

i

!

J

OB

DECK

;

}

!/

Load

Binary

Deck

and

Go

INPUT

TAPES

A4

f

j

Old

Population

File

PRINTED

OUTPUT

A2

Standard

Carriage

Form

Control

Tape

A6

i

.

~

J

N/A

..

j

CARD

OUTPUT

A5

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(1

)

(8)

06)

$

IDE

NT

3154203,

DATDY

OPTION

COBOL

(Binary

Program

Deck

-

POPFM)

s

$

s

$

EXECUTE

DUMP

LIMITS

15,32000

SYSOUT

A2

TAPE

A3,X3S

TAPE

A4,X4D,,POPFILEl,,XXXX

SYSOUT

A5

DATA

Al

(Control

Card

-

PF)

(Current

File

-

PF

Deck)

$

***EOF

END

JOB

XXXX=reel

number

135

JCVS

USAGE

FORM

Function:

POPFM2

Computer:

GE-635

Operating

Philosophy:

Stage:

A3

Load

Binary

Deck

and

Go

OUTPUT

TAPES

A4

New

Population

File

j

OldJ'opulation

File

J

A6

...

.71

N/A

CARD

INPUT

Al

CARD

READER

EMPTY

PRINTED

OUTPUT

~~«

"1

-,

i

Standard

AUDIT

FILE-PF

I

(Optional)

Carriage

Control

Tape

.J

CARD

OUTPUT

A5

PUNCH

FILE-PF,

...........:

.

...

.

.A'

(Optional)

/

136

JCVS

USAGE

FORM

Function:

SELECT

Computer:

GE-635

Operating

Philosophy:

Stage:

A3

r

K

SCRATCH

Compile

Source

Program

and

Go

INPUT

TAPES

A4

Population

File

A6

\

N/A

!

CARD

INPUT

Al

L

:

JOB

DECK

/I:

-J

PRINTED

OUTPUT

i

A2

!

Standard

Carriage

Form

Control

Tape

..-«

CARD

OUTPUT

A5

CARD

PUNCH

READY

JOB

DECK

S

TRUCTURE

0)

(8)

(16)

s

$

IDE

NT

3154203,

DATDY

COBOL

INCODE

IBMC

(COBOL

Source

Program

Deck

-

SJCVS)

$

EXECUTE

DUMP

LIMITS

15,32000

TAPE

A3,X3S,,SAVE,,JOVSP

SYSOUT

A5

SYSOUT

A2

DATA

Al

(Control

Card

-

S)

(Test

Selection

File

Deck)

ENDJOB

>EOF

137

JCVS

USAGE

FORM

Function:

SELECT

Computer:

GE-635

Operating

Philosophy:

Stage:

A3

Compile

Source

Program

and

Go

OUTPUT

TAPES

A4

A6

i

CARD

INPUT_

Al

CARD

READER

EMPTY

L.__

PRINTED

OUTPUT

A2

!

AUDIT

FILE-S

t

(Optiorwl)

Standard

Carriage

i

Control

Tape

_..!

CARD

OUTPUT

A5

/"

""

/

1

I

PUNCH

FILE-S;

i.

V

(Optional)

138

JCVS

USAGE

FORM

Function:

SELECT

Computer:

GE-635

Operating

Philosophy:

Stage:

A3

SCRATCH

Load

Binary

Deck

and

Go

INPUT

TAPES

I

A4

Population

File

A6

i

-

/"

N/A

CARD

INPUT

Al

L

JOB

DECK

/

!/

;

PRINTED

OUTPUT

A2

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

A5

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(1)

(8)

(16)

$

IDE

NT

3154203,

DATDY

OPTION

COBOL

(Binary

Program

Deck

-

SJCVS)

$

s

$

s

EXECUTE

DUMP

LIMITS

15,32000

TAPE

A3,X3S,,SAVE,,JOVSP

SYSOUT

A5

SYSOUT

A2

DATA

Al

(Control

Card

-

S)

(Test

Selection

File

Deck)

$

***EOF

ENDJOB

139

JCVS

USAGE

FORM

Function:

SELECT

Computer:

GE-635

Operating

Philosophy:

Stage:

A3

Load

Binary

Deck

and

Go

OUTPUT

TAPES

A4

Source

Program

File

A6

\

WA.

CARD

INPUT

Al

CARD

READER

EMPTY

L

PRINTED

OUTPUT

A2

!

Standard

AUDIT

Carriage

'

FILE-S

|

Control

jTape

j

y

(Optional)

j

CARD

OUTPUT

i

A5

/

j

PUNCH

FILE-

A

•

S

/

(Optional)

.

V

140

JCVS

USAGE

FORM

Function:

SOPMM

Computer:

GE-635

Op3rating

Philosophy:

Stage:

A3

/

I

1

Compile

Source

Program

and

Go

INPUT

TAPES

!

A4

/'

/

SC

RA

TCH

j

Old

Source

Program

FiI

ej

A6

N/A

CARD

INPUT

Al

f

JOB

DECK

PRINTED

OUTPUT

/!!

•

>

1/

;

A2

Standard

Form

Standard

Cairiage

Control

Tape

JOB

DECK

STRUCTURE

(1)

(8)

(16)

$

IDENT

3154203,

DATDY

$

COBOL

$

INCODE

IBMC

(COBOL

Source

Program

Deck

-

SOPMM)

CARD

OUTPUT

A5

CARD

PUNCH

READY

$

EXECUTE

DUMP

s

LIMITS

15,32000

$

SYSOUT

A2

$

TAPE

A3,X3S

$

TAPE

A4

/

X4S

//

JOVSP,

/

XXXX

$

SYSOUT

A5

$

DATA

Al

(Control

Card

-

SP)

(Current

File

-

SP

-

Deck)

XXXX

=

reel

number

'EOF

END

JOB

141

JCVS

USAGE

FORM

Function:

SOPMM

Computer:

GE-635

Operating

Philosophy:Compile

Source

Program

and

Go

Stage:

OUTPUT

A3

\

)

New

Source

Pgm

File

jOld

Source

Pgm

File

A6

i

[

N/A

_..n

CARD

INPUT

AT

CARD

READER

EMPTY

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:

Stage:

A3

Load

Binary

Deck

and

Go

INPUT

TAPES

A4

a

SCRATCH

._

IQld

Source

Program

File

A6

\

CARD

INPUT

Al

JOB

DECK

i

;

i

L

.1

v

PRINTED

OUTPUT

;—

-i

1

A2

i

Standard

•

Standard

Carriage

Form

Control

i

Tape

CARD

OUTPUT

A5

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(1)

(8)

(16)

$

IDE

NT

OPTION

3154203,

DATDY

COBOL

(Binary

Program

Deck

-

SOPMM)

$

s

$

EXECUTE

LIMITS

SYSOUT

TAPE

SYSOUT

DATA

DUMP

15,32000

A2

A3,X3S

A4,X4S,,JOVSP,,XXXX

A5

Al

(Control

Card

•

(Current

File

-

-SP)

SP

Deck)

XXXX

=

reel

number

'EOF

ENDJOB

143

JCVS

USAGE

FORM

Function:

SOPMM

Computer:

GE-635

Operating

Philosophy:

Stage:

A3

Load

Binary

Deck

and

Go

OUTPUT

TAPES

A4

New

Source

Pgm

File

Old

Source

Pgm

File

A6

N/A

CARD

INPUT

Al

CARD

READER

EMPTY

PRINTED

OUTPUT

A2

I

AUDIT

FILE-SP

_.(9pt'°nn!L

i

Standard

Carriage

|

Control

Tape

J

CARD

OUTPUT

A5

t

PUNCH

FILE-SP/

L-

v

(Optional)

144

JCVS

USAGE

FORM

Fi

notion:

JCVSRP

Computer:

GE-635

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

INPUT

A3

r

^

i

Population

File

TAPES

A4

/'

N/A

A6

N/A

CARD

INPUT

Al

""I

/

JOB

DECK

PRINTED

OUTPUT

A2

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

A5

CARD

PUNCH

READY

_l

.

«

JOB

DECK

STRUCTURE

(I)

$

IDENT

$

COBOL

s

INCODE

$

s

$

***

(8)

(16)

3154203,

DATDY

IBMC

(COBOL

Source

Program

Deck

-

JCVSRP)

EXECUTE

DUMP

LIMITS

15,32000

SYSOUT

A2

TAPE

A3,

X3D,

,POPFILEI,

,XXXX

DATA

Al

(Control

Card

-

RP)

ENDJOB

XXXX

-

reel

number

EOF

14:

JCVS

USAGE

FORM

Function:

JCVSRP

Computer:

GE-635

Operating

Philosophy:

Compile

Source

Program

Deck

and

Go

Stage:

OUTPUT

TAPES

A3

Population

File

A4

)

N/A

A6

N/A

i

CARD

INPUT

"AT

CARD

READER

EMPTY

L

PRINTED

OUTPUT

A2

AUDIT

FILE-RP

Standard

Carriage

Control

Tape

x

CARD

OUTPUT

A5

/

•

"

I

PUNCH

FILE

.

,

I

_

V

N7A

146

JCVS

USAGE

FORM

Function:

JCVSRP

Computer:

GE-635

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

INPUT

A3

()

Population

Fife

TAPES

A4

N/A

A6

N/A

CARD

INPUT

Al

i

/:

(

JOB

DECK

•

/

.

..

.•

PRINTED

OUTPUT

A2

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

A5

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

0)

(8)

(16)

S

$

IDENT

3154203,

DATDY

OPTION

COBOL

(Binary

Program

Deck

-

JCVSRP)

S

s

EXECUTE

DUMP

LIMITS

15,32000

SYSOUT

A2

TAPE

A3,X3D,,POPFILEI,,

XXXX

DATA

Al

(Control

Card

-

RP)

ENDJOB

XXXX

-

reel

number

***

EOF

147

JCVS

USAGE

FORM

Funcfion:

JCVSRP

Computer:

GE-635

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

OUTPUT

_TAPES

A4

...JTJ

A6

K/A

CARD

INPUT

Al

CARD

READER

EMPTY

i

PRINTED

OUTPUT

A2"

T

AUDIT

FILE-RP

]

Standard

,

Carriage

1

Control

i

Tape

i

:

-

1

CARD

OUTPUT

A5

/:::v

I

PUNCH

FILE

!

'

L_

_.

V

IS/A

148

JCVS

USAGE

FORM

Function:

INIPOP1

Computer:

GE-635

Operating

Philosophy:

Stage:

A3

v..

SCRATCH

I

Compile

Source

Program

and

Go

INPUT

TAPES

A4

SCRATCH

A6

N/A

CARD

INPUT

Al

/

::

/

JOB

DECK

j

t

-

...._.

J

PRINTED

OUTPUT

A2

'

Standard

Carriage

Form

Control

Tape

t

CARD

OUTPUT

A5

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(1)

(8)

(16)

$

IDE

NT

3154203,

DATDY

COBOL

INC

ODE

IBMC

(COBOL

Source

Program

Deck

-

IN

$

s

$

EXECUTE

DUMP

LIMITS

15,32000

SYSOUT

A2

TAPE

A3,X3S

TAPE

A4,X4R

SYSOUT

A5

DATA

Al

(Control

Card

-

1P)

(Current

File-

PF

Deck)

$

***EOF

ENDJOB

-

INI

POP)

149

JCVS

USAGE

FORM

Function:

INIPOPl

Computer:

GE-635

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

OUTPUT

TAPES

A3

Population

File

A4

SCRATCH

A6

f

\

N/A

CARD

INPUT

AT

CARD

READER

EMPTY

t~

PRINTED

OUTPUT

!

Standard

,

Carriage

:

Control

Tape

CARD

OUTPUT

A5

!

/__

j

PUNCH

FILE-

A

•

ip

1

(Optional)

V

150

JCVS

USAGE

FORM

Function:

INIPOP1

Computer:

GE-635

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

INPUT

TAPES

A3

A4

I

\

SCRATCH

(

SCRATCH

.1.

A6

/

\

/

N/A

CARD

INPUT

Al

/

.

JOB

DECK

./

V

PRINTED

OUTPUT

|

A2

!

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

A5

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(1)

(8)

(16)

S

$

IDENT

OPTION

3154203,

DATDY

COBOL

S

$

(

Binary

Program

Deck

-

INIPOP)

EXECUTE

DUMP

LIMITS

15,32000

SYSOUT

A2

TAPE

A3,X3S

TAPE

A4,X4R

SYSOUT

A5

DATA

Al

(Control

Card

-

IP)

(Current

File

-

PF

Deck)

$

***EOF

ENDJOB

151

JCVS

USAGE

FORM

Function:

INIPOP1

Computer:

GE-635

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

OUTPUT

A3

A4

Q

Population

File

SCRATCH

A6

N/

A

...

CARD

INPUT

Al

CARD

READER

EMPTY

PRINTED

OUTPUT

1

Standard

Carriage

i

AUDIT

FILE-IP

(Optional)

Conl

rol

Tape

CARD

OUTPUT

PUNCH

FILE-IP

:/

(Optional)

152

JCVS

USAGE

FORM

Function:

INIPOP2

Computer:

GE-635

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

INPUT

TAPES

i

A3

/'

C,

SCRATCH

A4

SCRATCH

A6

/.

[Old

Population

File

CARD

INPUT

Al

/.'"

JOB

DECK

PRINTED

OUTPUT

/

:

1

i

/

A2

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

A5

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(1)

(8)

(16)

$

S

IDE

NT

COBOL

INCODE

3154203,

DATDY

IBMC

S

s

$

(COBOL

Source

Program

Deck

-

INIPOP)

EXECUTE

DUMP

LIMITS

15,32000

SYSOUT

A2

TAPE

A3,X3S

TAPE

A4,X4R

TAPE

A6,X6R,,POPFILEl,,XXXX

DATA

Al

XXXX

-

reel

number

(Control

Card

-

IP)

(Current

File

-

PF

Deck)

$

***EOF

ENDJOB

153

JCVS

USAGE

FORM

Function:

INIPOP2

Computer:

GE-635

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

OUTPUT

TAPES

A4

I

A6

\

SCRATCH

Old

Population

File

i

CARD

INPUT

"

A1

CARD

READER

EMPTY

PRINTED

OUTPUT

"

A2

r

I

i

AUDIT

i

FILE-IP

L

(Optional)

Standard

l

Carriage

Control

Tape

J

CARDOUTPUJ

A5"

/

PUNCH

FILE-IP

(Optional)

V

/

154

JCVS

USAGE

FORM

Function:

INIPOP2

Computer:

GE-635

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

A3

a

INFJT

l

'

TAPES

A4

A6

CARD

INPUT

i"

Al

[..

JOB

DECK

_J

PRINTED

OUTPUT

A4

;

Standard

Carriage

Form

Control

Tape

CARD

OUTPUT

A5

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

(D

(8)

(16)

$

IDENT

OPTION

3154203,

DATDY

COBOL

(Binary

Program

Deck

-

INIPOP)

S

$

EXECUTE

LIMITS

SYSOUT

TAPE

SYSOUT

DATA

DUMP

15,32000

A2

A3,X3S

A4,X4R

A6,X6R,,POPFILEl,,XXXX

A5

Al

XXXX

-

reel

number

$

***EOF

(Control

Card

-

IP)

(Current

File

-

PF

Deck)

ENDJOB

55

JCVS

USAGE

FORM

Function:

INIPOP2

Computer:

GE-635

Operating

Philosophy:

Load

Binary

Deck

and

Go

Stage:

OUTPUT

A3

TAPES

A4

~N

I

A6

New

Population

File

J

—rj

!

SCRATCH

|

Old

Population

File

CARD

INPUT

Al

CARD

READER

EMPTY

PRINTED

OUTPUT

Standard

Carriage

Control

Tape

I

_1

CARD

OUTPUT

A5

/

I

PUNCH

FILE-IP'

/

L

J/

(Optional)

156

JCVS

USAGE

ORM

F

motion:

POPFMl

C

omputer:

IBM

360-50

C

perating

Philosophy:

Compile

Source

Program

ar

d

Go

S

age:

SYS004

s

N/A

C,

INPUT

"

~'i

!

i

!

TAPES

SYS005

/"

I

SCRATCH

SYS007

i

N/A

CARD

INPUT

SYS001

PRINTED

OUTPUT

/:

'

i

c

JOB

DECK

J/

J

DB

DECK

STRUCTURE

SYS002

Standard

Form

Stanc'urd

Carriage

Control

Tape

CARD

OUTPUT

SYS003

CARD

PUNCH

READY

/

'POPf

/

'SI

E>

/

'COB

//GO.

/

/GO.

/

/GO.

//GO.

Ml,

JOB

(799,028,010,1084,10,5),ANT<3HAGNO,MSGLEVEL

=

1

EC

COBFCLG

SYSIN

DD*

(COBOL

Source

Program

Deck

-

POP

:

M)

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)

1

/

]57

JCVS

USAGE

FORM

Function:

POPFMl

ComputenlBM

360-50

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

OUTPUT

TAPES

SYS005

)

Population

File

SYS007

N/A

_.:n

CARD

INPUT_

SYS001

CARD

READER

EMPTY

PRINTED

OUTPUT

SYS002

Standard

!

AUDIT

;

Carriage

FILE-PF

L

y

(Optional)

Control

Tape

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

SYS004

Old

Population

File

TAPES

SYS005

C

i

SCRATCH

SYS007

(

N/A

CARD

INPUT

SYS001

z:

JOB

DECK

"i

\\

PRINTED

OUTPUT

|

SYS002

'

Standard

Form

Standard

Carriage

Control

Tape

CARD

OUTPUT

SYS003

CARD

PUNCH

READY

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

SYS004

L

Old

Population

File

TAPES

SYS005

SYS007

New

Population

File

N/A

CARD

INPUT

SYS001

CARD

READER

EMPTY

J>RnvJTED

OUTPUT

SYS002

AUDIT

I

FILE-PF

(Optional)

Standard

Carriage

Control

Tape

CARD

OUTPUT

SYS003

{

/

L._

i

PUNCH

FILE-Pf/'

I

-

A*

(Optional)

160

JCVS

USAGE

FORM

Function:

SELECT

Computer:

IBM

360-50

Operating

Philosophy:

Compile

Source

Program

and

Go

Slage:

SYS004

r

\

s

1

L

Population

File

INPUT

TAPES

SYS005

\

SCRATCH

J

SYS007

N/A

CARD

INPUT

SYS001

/

L

JOB

DECK

/«!

i

i:

l...

PRINTED

OUTPUT

SYS002

Standard

Form

L

Standard

Carriage

Control

Tape

i

L.

•

j

CARD

OUTPUT

SYS003

CARD

PUNCH

READY

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:

Compile

Source

Program

and

Go

Stage:

OUTPUT

SYS004

TAPES

SYS005

Population

File

....

:j

[Source

Program

File

SYS007

/

V

L

N/A

CARD

INPUT

SYS001

CARD

READER

EMPTY

_PRINTEDOUTPUT_

SYS002

j

|

Standard

AUDIT

Carriage

FILE-S

;

Control

Tape

s

(Optional)

CARD

OUTPUT

SYS003

f

{

I

PUNCH

FILE-

S

1

/

!

/

(Optional)

162

JCVS

USAGE

FORM

Function:

SOPMM

Computer:

'BM

360-50

Operating

Philosophy:

Compile

Source

Program

and

Go

Slage:

INPUT

TAPES

SYS004

SYS005

f

N

V

i

Old

Source

Pgm

File

j

SCRATCH

SYS007

N/A

i

_

CARD

INPUT

SYS001

I

!

z:::zz

PRINTED

OUTPUT

L:

JOB

DECK

A

Jj

V

I

4

SYS002

Standard

Form

L~.

Standard

Carriage

Control

Tape

CARD

OUTPUT

SYS003

CARD

PUNCH

READY

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

SYS005

i

Old

Source

Pgm

File

(New

Source

Pgm

File

j

N/A

SYS007

CARD

INPUT

SYS001

CARD

READER

EMPTY

PRINTED

OUTPUT

SYS002

AUDIT

FILE-SP

r

(Optional)

Standard

Carriage

Control

Tape

CARD

OUTPUT

SYS003

r

/

1

PUNCH

FILE-

(Optional)

t

I'

164

JCVS

USAGE

FORM

Function:

JCVSRP

Computer:

IBM

360-50

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

INPUT

SYS004

a

N/A

TAPES

SYS005

v

I

N/A

SYS006

t

Population

File

CARD

INPUT

SYS001

/

L

-

/

i

JOB

DECK

},

!./

!

..

J

PRINTED

OUTPUT

SYS002

!

Standard

Carriage

Form

Control

Tape

t

CARD

OUTPUT

SYS003

CARD

PUNCH

READY

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:

JCVSRP

Computer:

»M

360-50

Operating

Philosophy:

Compile

Source

Program

and

Go

Stage:

OUTPUT

SYS004

SYS006

\

Population

File

CARD

INPUT_

CARD

READER

EMPTY

J

PRINTED

OUTPUT

r

I

AUDIT

i

FILE-RP

!

./

Standard

Carriage

Control

Tape

CARD

OUTPUT

—i

r

/

4...

./

/

I...

PUNCH

FILE

N/A

166

JCVS

USAGE

FORM

Function:

Computer:

INIPOP1

IBM

360-50

Operating

Philosophy:

Stage:

SYS004

a

N/A

Compile

Source

Program

and

Go

INPUT

TAPES

SYS006

'

r

,

!

V

/.

I

SCRATCH

SYS007

V.

I

.

SCRATCH

_

CARD

INPUT

f

SYS001

/:

JOB

DECK

i

/,

•

!/

PRINTED

OUTPUT

SYS002

\

s

tan

da,d

Standard

Carriage

Form

Control

Tape

I

.

CARD

OUTPUT

SYS003

CARD

PUNCH

READY

..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:

Stage:

SYS004

Compile

Source

Program

and

Go

OUTPUT

TAPES

SYS006

SYS007

/

V._

..'1

.New

Population.

File

CARD

INPUT

SYS001

CARD

READER

EMPTY

PRINTED

OUTPUT

_SYS002

i

I

Standard

AUDIT

Carriage

FILE-IP

i

Control

IT

/'-"•

Tape

!

(Optional^

[

CARD

OUTPUT

SYS003

/

"""

/

t

/

>

-

1

PUNCH

FILE-

i

/

-IP

!

/

i.

.

(Optional)

168

JCVS

USAGE

FORM

Function:

INIPOP2

Computer:

IBM

360-50

Ox-rating

Philosophy:

Compile

Source

Program

and

Go

St

<ge:

INPUT

SYS004

i

I

i

Old

Population

File

TAPES

SYS006

I

/

i

SCRATCH

SYS007

\

SCRATCH

CARD

INPUT

SYS001

/::.:

:

!

JOB

DECK

/

PRINTED

OUTPUT

SYS002

|

Standard

Carriage

Form

Control

Tape

t

CARD

OUTPUT

SYS003

CARD

PUNCH

READY

JOB

DECK

STRUCTURE

//POPFM2

JOB

(799,028,010,1084,10,5),

ANTCHAGNO,

MSGLEVEL

=

1

//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

LABEL

=

(,NL),DISP

=

OLD,VOL

=

SER

000649

//GO.SYS007

DD

UNIT

=

2400,LABEL

=

(,NL),

DISP

=(,DELETE)

//GO.SYSDUMP

DD

SYSOUT

=

A

//GO.SYS001

DD*

(Control

Card

-

IP)

/'

169

JCVS

USAGE

FORM

INIPOP2

IBM

360-50

Function:

Computer:

Operating

Philosophy

Stage:

SYS004

Compile

Source

Program

and

Go

OUTPUT

TAPES

I.

SYS007

....I

i

CARD

INPUT

CARD

READER

EMPTY

PRINTED

OUTPUT

I

""I

AUDIT

FILE-IP

(Optional

)j

Standard

Carriage

Control

Tape

1

CARD

OUTPUT

/

I

i

PUNCH

FILE-IP

>

L.

......

i'

L

(Ojstional)

170

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

"."

CDC-640C

OVIAL

COMPILER

VALIDATION

SYSTEM

1

SCOPT

P

•

1A'

,'

B-5500

OVIAL

COMPILEP

VALIDATION

SYSTEM

I

MCP

P.'Ti/-."

•

;

•

UN

I

VAC-11

OB

OVIAL

COMPILER

VALIDATION

SYSTEM

1

FXFC2

O^nj/

">;

•

IBM

360-

l

jO

OVIAL

COMPILER

VALIDATION

SYSTEM

1

HASP

nr^i//

.

System

Header

Card

2

172,

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

Wf

FOP

CAPPS

A2

A3

A6

FC^

LIST

I

Mr,

65K

or^]A

OP

p

o

p

1A

0

0'

onpiA

rtAt

[NPUT

>UNCH

rAPC?

CPC-6400

OUTPUT

TAPF1

TAPF3

01137K

oro

]

A^^'

or^\

;.

r

n

/

n

r

o

l

A

o

f

'.

R-5500

rAPF

PPINT^P

TAPF

65K

o

r

l

/'•

•

:'•

•

00

01

Aoo/

n^r<)

,\

->

r

i

rAPD-RFAHFP-F

IGHTY

CAPD-PUNCH-FIGHTY

JNISEPVO

13

UNIVAC-]108

PRINTFP

UNISERVO

A

UNISERVO

C

65K

or"

]

AfO'

0

i

A

o

O

<

0

1

A

•

>

C'•'

IBM

360-50

•

SYS

001

•

»

SYS003»

»SYS0P*«

UNIT-RFCORH

2540R

•SYS002•

UNIT-PFCORO

25A0P

»SYS004«

UTILITY

?uon

UNIT

»SYS006«

UNIT-RFCORD

?5U0P

UTILITY

?AP0

UNIT

UTILITY

?/+00

UNIT

6

5K

000

1

A

'C

r\

n

0

]

A

i"'

O

i

onr

]

A

'

0'

Environmental

Hardware

Cards

17*

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

G

r

-633

IDFNT

3154203»PATDY

JOVIAL

FOPTPAM

r

xrcuTF

nt'MP

LIMITS

1

[

J,

35000

r

^njon

*EOF

-

^,-JL

•

;.

-.

,

iL

,-.

•

.:

-

,-

i

L

.

•

nrnir"

1:

''

r

>

I

T'

i

•

-

-^ir

17

-

•>.-,

j

r

•

1

•

Environmental

Software

Cards

176

APPENDIX

V

TYPICAL

MODULES

This

appendix

contains

a

listing

of

a

few

typical

Population

File

modules.

177

'•MODULE

5220

-

CED

2454

'•

522PAO0:

••TEST

USE

OF

FLOATING

CONSTANTS.VARIABLES

"

522?JCC'<

ITFM

FA522C

F

P

1.0$

ITEM

FB5220

F

P

4.OS

52<>CJCP:

ITEM

FC5220

F

P

0.0$

5?20JC

>

^'

5?20J^r'

IFEITH

FA5220

EQ

r

B5220$

GOTO

LZ5220$

522PJ00<

0R1F

1.0

EO

FA52205

FC5220=3.0$

5220J00'

ORIF

FA5220

EQ

FC'J220$

GOTO

LZ5220$

5220J0PI

LA522^9

ORIF

1$

GOTO

LZ5220S

END

522nJ^P<

IFFITH

FB5220

EO

1.0$

GOTO

LA522PS

522^J0li

ORIF

FA5220

EO

1.0$

GOTO

LB5220$

5220JO1

ORIF

1$

GOTO

LZ5220S

FND

b?2

fs

J

n

\'.

GOTO

LZ5220$

522PJ^1

LB52209

IFEITH

1.0

EO

2.OS

FC5220=1.0$

522pJPl<

ORIF

2.0

EO

FA522PS

FC5220=1.P$

(

j22"J^i

l

ORIF

FB5220

EQ

2.0$

GOTO

LC52201

522CJM.<

ORIF

1$

GOTO

LZ5220$

END

''ERROR

IF

HFRF"

5?2rjny

GOTO

L7522P$

5?2"JM

I

LC522P9

GOTO

LY5220$

5220J^1'

LZ5220.

5?20J02i

0UT1=40H(

MODULE

5220

TEST

FAILED.

CED2454

)$

5220^2

OUTERR(OUTl)$

GOTO

LX5220$

''EXIT''

522PJ02,

LY5220.

5220J02

OUT1=40H{

MODULE

5220

TEST

SUCCESSFUL.

)$

5220J02

OUTERR(OUTl)$

5?20J

n

2

LX5220.

5220^2'

••MODULE

5230

-

CFD

2454

••

523PAPP

••TEST

USE

OF

STATUS

CONSTANTS

•

VARIABLFS••

5?3pJnp

ITFM

SA5230

S

V(A)

V(R)

V(C)

P

V(R)$

5??r»Jnp

ITFM

SB5230

S

V(X)

V(Y)

V(Z)

P

V(Z)$

•»23pJ(

,

P'

ITEM

SC523H

S

v(NO)

V(YES)

P

V(vfS)$

5730J

•

ITEM

SD523C

S

V(NO)

V(YFS)

V(MA

V

BE)

P

V(YES)$

523nJrpi

IFEITH

V(A)

EQ

SA5230$

GOTO

LZ5230S

52'

J

0J'0

ORIF

SB523P

EO

V(X)$

SC>230

=

V

(

NO)

$

S?3ojMp

ORIF

SB5230

EQ

SA5230$

GOTO

LZ5230S

523"J('P

ORIF

1$

GOTO

LA5230$

END

523PJ'

i

GOTO

LZ5230$

••ERROR••

523pJ<

1

LA5230.

IFEITH

SD5230

EQ

V(YES)$

GOTO

LB5230S

523PJri

ORIF

V(A)

EQ

SA5230$

GOTO

LZ5230S

5230J:

1

LB5230.

ORIF

V(YES)

EQ

SD5230$

SC5230=V(NO)$

5230JP1

ORIF

1$

GOTO

LZ5230$

END

»»rRPOP"

523PJP1

IFEITH

SB5230

EQ

V(Z)$

GOTO

LC5230$

523*JP1

ORIF

1$

GOTO

L252305

END

"ERROR"

52'50j:>]

LC52309

GOTO

LY5230$

523PJP1

LZ5230.

523PJM

0UT1=4PH(

MODULE

5230

TEST

FAILED.

CED2454

)$

523PJ"2

OUTFRR(OUTl)$

GOTO

LX5230$

"EXIT"

523pJo2

LY5230.

5230J'*2

0UT1=40H(

MODULE

5230

TEST

SUCCESSFUL.

)$

523^J"2

0UTFRR(0UT1)$

5?3PJ'^2

LX5230.

523PJ02

"MODULE

5240

-

CED

2454

"

5240A00

"TFST

USE

OF

TRANSMISSION

CONSTANTS»VARIABLFS

"

524OJ0P

ITEM

TA5240

T

2

P

2T(AA)$

524PJP0

ITFM

TB5240

T

2

P

2T(BB)$

5?4"<Jpn

ITEM

TC5240

T

2

P

2T(

)$

ITFM

TD5240

T

2$

524PJnr

i7a'a

7

APPENDIX

VI

This

appendix

defines

the

test

hierarchy

for

the

JCVS

as

well

as

some

highlights

of

JOVIAL

as

a

language

and

validation

in

general.

181

APPENDIX

VI

General

This

appendix

describes

the

development

philosophy

of

the

JOVIAL

J3

Population

File,

including

a

brief

history

of

the

JOVIAL

language;

an

exposition

of

all

validation

concepts

used

in

the

development

of

the

Population

File;

the

JOVIAL

language

organization

used

to

identify

features

to

be

tested;

the

JOVIAL

language

Test

Hierarchy;

and

problems

encountered

in

the

development

of

this

file.

Validation

A

JOVIAL

compiler

is

said

to

be

validated

if

each

feature

conforms

to

the

individual

language

specifications

called

features

as

described

in

the

AFM

100-24.

Each

feature

has

been

individually

considered

in

terms

of

its

intent

and

one

or

more

tests

have

been

developed

exercising

the

various

options

provided

by

this

feature.

Every

option

provided

by

every

feature

in

the

language

is

exercised

at

least

once

in

the

tests

comprising

the

Population

File.

When

combinations

of

feature

options

were

required

to

insure

the

validity

of

a

feature,

in

several

instances

only

a

subset

of

the

possible

combinations

were

included

in

the

Population

File.

JOVIAL

History

The

JOVIAL

language

was

originally

developed

in

1958,

four

years

after

the

development

of

the

first

programming

language,

FORTRAN.

It

is

a

procedure

oriented

higher-order

programming

language.

JOVIAL,

a

derivative

of

ALGOL

58,

was

designed

specifically

to

describe

computerized

solutions

to

command

and

control

problems.

As

stated

by

AFM

100-24,

"The

prime

motivation

for

the

development

of

JOVIAL

was

the

desire

to

have

a

common,

powerful,

easily

understandable

and

mechanically

translatable

programming

language

suitable

for

wide-range

applications."

In

addition

to

the

above

requirements,

the

language

was

to

adhere

to

the

following

design

goals?

1.

Centralized

data

communication

facilities

2.

Machine

independence

3.

Logical

and

Algebraic

expresseion

ccpabilities

4.

Symbol

manipulation

capabilities

182

5.

Readability

6.

Conciseness

7.

Training

Simplicity

8.

Ease

of

maintainence

Based

upon

the

aforementioned

requirements

and

goals,

the

JOVIAL

language

greatly

enhances

the

problem

definitional

capabilities

of

the

programmer.

The

following

paragraphs

illustrate

the

wisdom

of

the

JOVIAL

design.

Command

and

control

problems

are

in

general

extremely

large

in

terms

of

the

data

base

to

be

gathered,

manipulated

and

reported;

arJ

the

variety

of

computations

to

be

performed

on

the

data

base.

Consequently,

the

programming

system

necessary

to

solve

this

problem

is

so

vast

that

several

hundred

programmers

may

be

required

to

perform

the

individual

programming

tasks.

Because

of

the

number

of

individual

programs

and

programmers

involved

in

a

command

and

control

development,

program/programmer

communication

becomes

a

critical

problem.

In

order

to

alleviate

this

situation,

a

Communication

Pool

(COMPOOL)

was

developed

which

serves

as

a

central

souce

of

data

description.

Centralizing

all

global

data

descriptions

facilitates

changing

data

item

parameters

and

automatically

reflecting

these

changes

throughout

the

machine

language

programs.

This

feature

of

the

JOVIAL

language

alone

has

saved

enormous

amounts

of

time

and

money

in

several

command

and

control

system

developments.

A

pplication

Requirements

Programming

languages

are

created

in

order

to

respond

to

common

sub-solutions

within

application

areas.

Programming

languages

supply

capabilities

that

satisfy

these

common

sub-solutions

while

suppressing

the

repetion

and

details

of

solution.

Many

of

these

capabilities

are

present

in

most

languages

and

provide

for

general

application

requirements

such

as:

1

.

Program

Control

2.

Information

Transfer

3.

Input/Output

Communication

4.

Arithmetic

Operations

5.

Data

Item

Definitions

6.

Storage

Allocation

-

Static

to

name

a

few.

Additional

power

may

be

provided

by

a

language

by

adding

capabilities

of

a

general

nature

that

make

the

language

useful

problem

solving

tool

for

a

broader

class

of

problems

or

by

adding

more

extensive

capabilities

but

oriented

towards

specific

area.

183

Generally

oriented

features:

1

.

Algebraic

Expression

Evaluation

2.

Logical

Expressions

Evaluation

3.

Data

Structure

Definitions

Specifically

oriented

features:

1

.

Formula

Manipulation

2.

List

Processing

Language

Organization

The

JOVIAL

language

was

developed

to

respond

to

command

and

control

applications.

Each

feature

of

the

language

may

be

interpreted

as

a

language

response

to

a

programming

function

required

by

a

command

and

control

applications

programmer.

Using

this

notion

as

a.

point

of

departure,

the

JOVIAL

language

has

been

organized

into

the

following

programming

functions

in

order

to

organize

the

identification

of

features

to

be

tested.

1

.

Data

Concepts

1.1

Internal

Data

Concepts

1.1.1

Data

Definitions

1.1.1.1

Constant

Formulation

Integer

-

I

Fixed

Point

-A

Floating

Point

-

F

Octal

-

O

Dual

-

D

Transmission

Code

-

T

Hollerith

-

H

Boolean

-

B

Status

-

S

1.1.1.2

Simple

Data

Definitions

Integer

-

I

Fixed

Point

-

A

Floating

Point

-

F

Dual

-

D

Transmission

Code

-

T

Hollerith

-

H

Boolean

-

B

Status

-

S

1.1.1.3

Structured

Data

Definitions

Tables

Arrays

184

1

.1

.4

Control

Definitions

Item

Switch

Index

Switch

1.1.2

Data

Referencing

1

.1

.2.1

Simple

Items

1

.1

.2.2

Data

Structure

Items

Table

Items

Array

Items

1

.1

.2.3

Data

Structure

Table

Entries

1.1.2.4

Special

Referencing

ALL

BIT

BYTE

CHAR

ENT

ENTRY

LOC

MA

NT

NENT

NWDSEN

ODD

POS

1

.2

External

Data

Concepts

Procedure

Concepts

2.1

Procedure

Formations

2.1.1

Formulas

2.1.1.1

Numeric

2.1

.1

.2

Boolean

2.1.2

Relations

2.2

Program

Organization

Statements

2.2.1

PROGRAM

2.2.2

Subprogram

Organization

2.2.2.1

Procedures

User

Defined

PROC

CLOSE

Language

Defined

REMQUO

2.2.2.2

Functions

User

Defined

Language

Defined

ABS

REM

2.2.3

RETURN

185

2.3

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

i

OUTPUT

OPEN

OUTPUT

i

SHUT

OUTPUT

2.3.3

Replacement

Statements

2.3.3.1

Assignment

Statement

2.3.3.2

Exchange

Statement

2.4

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

T

est

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

.

The

ability

to

specify

any

item

type

and

have

it

retained

according

to

its

defining

attributes.

2.

The

ability

to

formulate

any

constant

type

and

have

it

retained

according

to

its

defining

attributes.

3.

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.

The

ability

to

name

a

statement

with

a

label.

2.

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.

The

ability

to:

•

1

.

Define

and

preset

a

hollerith

item.

2.

Assign

a

hollerith

constant

to

a

hollerith

variable.

3.

Execute

the

GOTO

statement-name.

4.

Define

a

procedure,

invoke

a

procedure,

and

return

from

a

procedure;

input

parameter

list,

one

variable.

5.

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

.

Test

identification

field

2.

Input

test

data

fields

3.

Test

results

fields

4.

Expected

results

fields

5.

Initialization

procedures

6.

Test

statements

comprising

the

test

7.

Results

analysis

procedures

8.

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.

M

andatory

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

.

The

mandatory

test

module

contains

data

definitions

that

are

required

by

the

dependent

test

module,

or

2.

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<?st

Module.

Within

each

Test

Module,

individual

cards

will

be

given

sequence

numbers

which

will

occupy

columns

78-80.

Identification

information

describing

various

aspects

of

the

test

module

is

provided

in

the

Test

Header

Card

(card

sequence

number

001,

see

Users

Manual

Section

4.1.2.2.1).

The

Test

Name

in

this

card

will

be

identical

to

the

name

used

in

the

various

section

headings

of

the

Test

Hierarchy

Outline.

For

example,

test

module

0500

will

have

the

Test

Name

DEFINE-PRESET

H

ITEM,

the

identical

name

used

to

entitle

Section

2.1

of

the

Test

Hierarchy

Outline.

Any

CED-NO's

to

which

a

test

module

refers

will

be

given

in

the

appropriate

positions

on

the

Test

Header

Card.

For

example,

test

module

0500

refers

to

both

CED-NO's

2463

and

2464.

These

numbers

are

included

in

their

respective

fields

on

the

Test

Header

Card.

Any

mandatory

DDI-NO

upon

which

the

test

module

depends

is

included

in

columns

59-62

of

this

card.

The

second

card

(card

sequence

number

002)

in

every

test

module

contains

the

classification

(section

number)

of

the

Test

Hierarchy

Outline.

Columns

3-22

contain

the

words

CLASSIFICATION

NUMBER.

Columns

26-33

contain

the

classification

number

in

the

following

form

XX.XX.XX.

The

third

card

(card

sequence

number

003)

in

every

test

module

contains

the

following

statement

from

column

3-50:

THIS

MODULE

TESTS

THE

ABILITY

OF

THE

COMPILER

TO.

.

The

fourth

card

and

subsequent

cards

in

the

test

module

are

used

to

expand

further

on

the

test

description.

Following

the

last

descriptive

card

in

the

test

are

the

test

and

support

statements

themselves.

190

Test

Module

Output

The

results

of

each

test

module

are

printed

in

a

standard

form.

At

least

two

printed

li

les

are

always

output.

The

first

line

always

consists

of:

TEST

MODULE

XXXX

where

XXXX

is

the

DDI-NO

of

the

module

under

test.

The

second

line

prints

either

of

two

messages:

TEST

SUCCESSFUL

(optional

commentary)

or

TEST

FAILED

(optional

commentary)

A

blank

line

is

automatically

supplied

by

the

JCVS

separating

consecutive

test

results.

JCVS

Input/Output

Characteristics

Since

the

implementation

of

the

JOVIAL

language

is

not

closely

monitored,

deviations

in

implementation

can

and

often

do

occur.

Implementors

take

it

upon

themselves

to

change

certain

of

the

language

specifications

for

any

of

many

reasons.

In

particular,

the

implementation

of

the

input/output

specifications

of

the

language

have

varied

markedly

in

the

past

from

implementor

to

implementor.

In

addition,

the

language

specifications

do

not

permit

the

user

to

apply

formatting

to

any

results

achieved

by

a

JOVIAL

program.

Consequently,

in

order

to

format

output

information

either

a

higher

order

language

that

permits

formatting

or

an

assembly

language

must

be

used.

It

was

originally

intended

to

display

actual

versus

expected

results.

Since

the

input/output

capabilities

of

JOVIAL

are

ill-defined

to

non-existent,

the

initial

plans

for

presentation

of

output

was

modified.

Since

FORTRAN

offers

excellent

formatting

capabilities,

it

was

decided

to

use

FORTRAN

subroutines

whenever

formatting

was

required.

The

notion

of

displaying

expected

versus

actual

results

was

abandoned

for

purposes

of

this

project

when

it

became

apparent

that

converting

internally

computed

numerical

JOVIAL

results

from

binary

to

decimal

would

be

accomplished

through

FORTRAN

conversion

programs

rather

than

JOVIAL

conversion

programs.

Consequently,

the

tests

would

be

invalid

because

certain

processes

would

be

carried

out

outside

of

JOVIAL

language

implementation.

As

a

re

ult

of

the

above

mentioned

JOVIAL

inadequacies,

the

following

only

qualitative

output

rm

ssages

were

printed.

Test

results

printed

out

under

these

conditions

do

not

fully

reveal

tho

causes

of

errors

in

tests

devoted

to

the

accuracy

of

arithmetic

operations.

The

results

of

syntax-semantics

testing,

however,

are

not

impaired

by

these

constraints.

191

r

.The

JOVIAL

input/output

specifications

described

in

AFM

100-24

do

not

adequately

describe

certain

aspects

of

the

file:declaration.

In

particular

it

is

left

to

the

implementor

to

specify

the

device:name.

It

is

unclear

precisely

what

constitutes

a

device:name

and

if

the

device:name

remains

inflexible

for

one

computer

configuration

or

precisely

how

it

varies.

In

addition,

the

relationships

that

exist

between

the

JOVIAL

defined

input/output

statuses

and

the

computer

configuration

software

or

hardware

is

not

clear.

It

may

be

impossible

to

reconcile

the

input/output

concepts

provided

by

JOVIAL

with

the

input/output

concepts

provided

by

the

hardware

or

software

environ-

ment.

Until

a

more

firm

relationship

can

be

established,

no

testing

of

the

filerdeclaration

and,

consequently,

of

the

JOVIAL

input/output

state-

ments

will

be

provided

at

this

time.

These

features

are

considered

to

be

non-standard

features.

FORTRAN

I/O

Usage

Test

module

9998

uses

the

FORTRAN

I/O

format

statement

PRT

(date-name)

$

For

each

computer

configuration

this

statement

must

be

provided

in

a

form

compatible

to

the

hardware

and

software

environment.

Population

File

Conversion

The

Population

File

is

keypunched

using

the

IBM

026

character

set.

Some

of

the

equipment

utilized

on

this

project

use

different

character

sets.

In

general,

only

the

card

punches

for

the

so-called

special

characters

vary

from

character

set

to

character

set.

A

complete

list

of

these

special

characters

together

with

their

punched

card

representations

is

given

in

the

accompanying

Character

Set

Table.

It

may

be

desireable

to

convert

the

Population

File

from

one

character

set

representation

to

another.

The

JCVS

provides

a

FORTRAN

routine

called

CONVER

that

performs

this

conversion.

This

routine

varies

slightly

from

configuration

to

configuration

but

performs

the

same

task.

In

general,

this

deck

is

submitted

to

the

computer

in

the

following

form:

1.

Leading

Operating

System

Control

Cards

2.

CONVER

Source

Program

Deck

3.

Data

Card

1

192

4.

Data

Card

2

5.

Data

to

be

Converted

(Card

Deck)

6.

Final

Operating

System

Control

Cards

Data

Card

1

contains

the

special

characters

in

the

data

deck

following

that

are

to

undergo

translation.

Data

Card

2

contains

the

special

characters

to

which

the

original

special

characters

encountered

in

the

Data

Deck

will

be

converted.

Eoch

character

of

each

card

in

the

Data

Deck

is

tested

for

possible

conversion.

If

a

conversion

is

to

be

made,

the

original

special

character

is

looked

up

in

a

table

developed

from

the

corresponding

special

characters

in

Data

Card

1

and

Data

Card

2.

If

a

match

is

accomplished,

the

new

special

character

is

substituted.

Every

character

in

Data

Deck

is

tested

in

this

way.

If

a

card

does

in

fact

contain

one

or

more

characters

to

be

converted,

the

converted

card

as

well

as

the

original

card,

is

printed.

If

a

card

contains

no

characters

to

be

converted,

only

the

original

card

is

printed.

Data

Card

1

and

Data

Card

2

have

identical

formats

described

as

follows:

Columns

Description

1-2

Number

of

special

characters.

3-80

Each

column

on

Data

Card

1

contains

a

character

to

be

converted

while

the

corresponding

column

on

Data

Card

2

contains

the

character

to

be

convered

to.

Following

are

the

deck

structures

for

the

four

computers

used

on

the

project:

1)

UNIVAC

1108

gRUN

1CONVER,

DOCG,

5,300

g

I

FOR

CONVER

(CONVER

Source

Deck)

gXQT

CONVER

(Data

Card

1)

(Data

Card

2)

(Data

Deck)

8

FIN

I

93

2)

IBM

360-50

//CONVER,

JOB(799,028,010,1084,10,5),

ANTCHAGNO,

MSGLEVE=1

//SI

EXEC

FORTGCLG

//FORT.SYSIN

DD

*

(CONVER

Source

Deck)

//GO.

SYS

IN

DD

*

(Data

Card

1)

(Data

Card

2)

(Data

Deck)

/*

3)

CDC-6400

JOB,

93007,10,10,35000.

CONVER

RU

N(S)

LGO.

(End

of

Record

Card)

(CONVER

Source

Deck)

(End

of

Record

Card)

(Data

Card

1)

(Data

Card

2)

(Data

Deck)

(End

of

File

Card)

4)

GE-635

$

I

DENT

3154203,

DATDY

$

FORTRAN

$

INCODE

IBMF

(CONVER

Source

Deck)

$

OPTION

FORTRAN

$

EXECUTE

$

LIMITS

15,32000

$

DATA

01

(Data

Card

1)

(Data

Card

2)

$

DATA

05

(Data

Deck)

$

ENDJOB

***

EOF

194

s

o

in

o

sO

MJ

ro

1

CO

1

CN

00

I

CO

I

co

I

CO

I

MD

I

CO

co

i

00

1

CO

1

i

1

SO

1

CN

i—

1

CN

.—

•

—

o

.—

CO

<

Qi

UJ

t—

U

<

C£

<

X

U

0,

0)

o

i-

"

E

2

o

•

£

o

u

...

-^

o>

o

-

?

0)

I

*

2

-o

**

•

-o

g>

91

.-

D

O

C

—

o

c

-^

E

Z

*

•

c

hen

rese

£

°-

«

c

.2-c

3;

*

•

ver

leri

8"o

u

X

0)

V

,£

_c

D

*"

CT

O)

e

.E

*.

1

8_g

i_

«

0)

+-

-*-

L-

8.8

E

0

-c

0

«

«.

_i

—

<

O)

_

c

81

-1

—

<u

,0

_c

"-

.4—

E

J

O

0)

«£

•

£

in

O

l_

0)

•

J".

-C

O

4-

2

ts

0

_C

*.

u

0

r^-C

f

«

—

O

*

•

0

i-

—

D

^

i

4)

E

_C

O

1—

0

CO

o

I

U

<

>

CM

00

1

00

1

00

CO

1

CO

-O

1

-*

0

CO

1

CO

^T

1

CO

1

•

—

•—

1

CN

1

CM

CO

i—

1—

-st

O

1—

-0

.—

o

I

y

u

CM

CO

1

CO

1

00

co

1

co

hs

1

"<t

CO

1

CO

•

*

1

r—

CM

1

CN

CO

1—

•—

^r

0

1—

CO

I

o

I

CM

CO

sO

I

CM

o

-

00

CO

00

CO

00

on

1

CO

1

CO

0

1

If)

IT)

SO

in

1

MO

1

CO

1

r—

1

CM

,—

1

CN

0

1—

0

1—

.—

SO

1—

c

E

o

U

CO

in

Ma

o

—

00

Qs.

_

o

1—

o

U

A

V

195

_Q

O

VI

C

b

>v

z

c

8.

n

b

n

<>

o

~o

u

<1>

n

I)

ni

•

—

u

o

c

>*

o

-*>

V

"O

O

CO

z>

o

o_

o

•-

CL

T3

C

<o

—

-E

in

*

•

O

wi

CL

UJ

0)

>«.

z

-B.?

_J

O

-*—

1—

t

o

=5

_

p

o

in

c

>

l/>

_

X

riou

ifiec

<

LU

he

VG

spec

X

*

•

a)

1—

c

•

£

CO

LU

-o

^

1—

owing

syntax

will

be

performe

reference

to

some

of

the

uses

<

X

—

in

<

0

f>

u-

O

h—

c

z

a)

u

>

•

*-

O

LO

sts

of

ovide

•

0)

u.

«—

1—

Q.

o

z

I

a

3

CO

IT)

00

CO

in

1

o

CO

CN

<0

CO

IT)

O

CO

CN

—

V)

«0

CO

•O

IT)

>o

CO

•

£

TJ

c

o

a)

"8

o

•

*-

o

a>

IT)

T>

0)

•

te

O

lO

V)

—

CN

IOOO

—

't

TT

o

^

In

>o

CO

io

—

o

CO

IT)

ir>

co

8

o

•

0

V?

o

CN

2

8.«

00

IO

_c

ion

K

o

io

o

©

—

•*

•

Tf

IO

If)

IO

—

-<*

•

*

8

2

°

o

co

io

o

^-

^

-«t

8.

1)

o

CO

s

o

s

o

u

V

1

C

o

•

—

>

o

fl)

">

_5

4)

-O

7=

I"

II

0)

o

"2

-te

c

Q.

il

O

c

o_

0)

u

»

—

So

iiO

lO

o

—

lO

o

-O

-*J"

lO

co

"*

Tl"

—

o

<o

•^

TJ-

_

O

lO

•O

CO

IO

«0

CO

e

io

—

-o

c

„

o

c

o

<o

o

CO

IO

»o

Jo

IE

Io

lO

o

IO

CO

<*

Tf

—

O

—

•

"<*•

o

IO

„

W

IO

~-

0)

a>

1-

i-

4-

••-

o

.2.J2

8

£

_E

"O

I—

>o

^8

o

io

IO

cs

o

IO

TJ

0)

_s

o

c

-u

c

o

-•-

CL

0)

V

3

8

IO

C

<1J

^-

^

^-

-*

—

^8

IO

o

^

CN

o

•o

^

—

I-

0)

CM

IO

lO

i;

t

O

CN

N

(N

Tf

t

2

n

IO

CO

00

^

3

•

glO

—

lOlOIOr-

•£

a>

^oooooo

1

*!

.2

Tf

5

CN

(N

r-

.2

«-coiococococo_c

lO

—

IO

I—

in

c*:

co

Z

u

CQ_I^.Q£coijt>X_JUjSEZ

cT

<<<<<fliinfflUUQCl

>

•

z

o

LU

UJ

LU

[LOGO

§2

LU

-r

LL.

*-

196

3

o

CO

o

CO

m

in

o

m

o

R

o

m

u->

MD

o-

CO

m

10

o

co

in

.jo

co

w

o

'?

—

o

S-8

11

0)

O

c

•O

*

CM

,/,

2

a

0)

o

£

o

CM

O

CN

O

u

—

-

©

"t

O

«!-

—

.E

oo

°

•

=

3

8

>

m

•TJ

CM

o

^

o

CN

CM

c

0)

"D

C

u

Q.

-8

•

"i

01

CN

w>

^*

ID

c

1c

u

I

73

•4—

2

o

c

73

!»

co

^

o

I

•

in

73

CO

73

co

r^

co

•

fc

MJ

-fc

CO

i|8_s

in

o

CO

tv

o

"°

c

—

in

—

CM

*

hi

>

MD

73

§12

c

o

Q.

a;

o

c

o

u

o

in

co

o

00

73

v

2

8

73

C

o

-*—

o_

<D

U

c

o

,

om

•Jj

—

CO

£

CM

—

•

*

o

in

c

Q

«*-

o

a>

°l

co

in

co

•—

CO

D

TJ-

in

Q

in

o

N

CN

—

CO

t

in

o

—•

—

in

c

co

n

in

o

in

—

^

in

o

—

in

o

C

N

O

a

Tj-

—

-t

•

*

in

<u>noininin

coo

^OCOCNO

t

SrOrf

2CN

-

co

.2

—

^<t

p

^i-

<o

<n

-<*

-«i-

\

o

—

o

a)

,2

.!2

8

inooo

„,

o

„,Q

CNMO-if.-CN^.l!!0

cN^conoxcocoxN

^t

>o

in

^

•

*

i-

in

t—

MD

co

in

co

o

>o

in

<u

^

O

irSOCO

br

•

g

MD

^

-*

in

"5

I)

CO

o

"<r

-"t

•

<»

•

•o

o

in

CO

CM

m

in

co

MD

o

in

co

CO

CM

o

CO

M3

o

<n

CO

CM

m

in

CM

M3

o

in

CO

CM

o

CM

-OCMO

CO

CM

•

in

73

—

co

"O

o

in

•

fe

co

CM

0)

o

IQ

JO

O

rt

5

^-

In

t—

o

c

M3

o

in

CO

co

CM

in

m

<D

in

CM

i_

o

D

•o

o

un

co

o

co

CO

CM

m

•i?

w>

8

o

g

o

cs

o

in

m

in

co

9

in

m

o

CO

in

«

>o

o

in

o

co

CM

o

in

CM

in

"<*

-<*

>n

in

u.

I—

UJ

oc

ex.

3

>

oo

oooo

oo

o

y

o

5

<

o

O-

Z

x

u

UJ

X

h-

i—

S

DC

OO

5*

2

l-

<.

LU

E

c?

3£

+

CM

197

<N

•O

o

-o

to

O

s

IT)

5

•

00

>o

oo

in

.

o

"<t

"*T

v>

to

lO

0)

<0

lO

m

o

ir>

u->

in

CN

—

"*t

</>

"^"

"*t"

ui

Op

O

^-^-

tt>ioo

o>

"^

,

v

•

—

o

CO

D

o

E

•O

lO

^_

to

o

to

CN

o

*

•

o

r-

O

IT)

CN

f)

iO<

IT)

<0

o

in

V

IT)

U")

*-

>o

o

—

3<

o

lO

-O

.,_

3

"0

o

O

r-

•**

•

-*t

o

"«t

"4

—

o

E

IT)

5

o

lO

S?

to

lO

to

o

to

co

lO

D

O

E

OJ

4)

<U

ir>

«o

<

O

oo

5

52

o

«o

in

v>

«o

^*o

«

i

=

^i

w

o

_Q

E

<D

>-

oo

c

o

_Q

k>

~

o

i/>

0)

D

'L-

a;

-*-

o

>

_Q

<

>

O

_l

o

C

o

oo

Z

>—

CN

—

CN

ro

CO

•

*

•

*

^t

198

o

z

o

'O

o

LO

o

1

o

,—

CN

•

~~

lO

>o

u->

lO

in

1-1

o

z

I

Q

OiOOU-)OU-)OLO

oooooooo

_0J

D

"§

E

o

I

fi

'5

cr

B

?

co

o

X

<

CN

c

•

—

2

c

o

u

</)

E

o

'x

a

a;

>

o

<

a

Q

LU

z

LL.

1-

LU

2

z

Q

UJ

1—

X

£

Li

LU

T

<

LU

5

CO

3

i—

<

c£

LU

(—

oo

z

LU

u

LU

h-

1

/

co

UJ

Qi

z

LU

2

<

h-

CO

LU

3

LU

CO

LU

Of

LU

LL.

I

7

a

Z>

LU

z

O

0

h-

LU

<

n

u_

co

o

U

u

z

a

<

o

LL.

<

CM

CN

CO

CN

lO

CN

LO

en

2

LL.

LU

O

CO

E

g

0)

*-

0)

XI

1.3

E

£.

CO

8

S=^

<D

v)

-,

C

—

r

-

D

O

c

o

in

0)

—

C

o

•

_i

E

5

8

1L

IL

Q

I

h

W

ffl

</)

E

4)

•4-

<D

a

E

0

—

LO

(1)

a>

c

a>

u-

0)

a.

n

b

c

o

i_

-+-

11

n

_u

o

fc

u-

D

is>

7

a

U

^

•

MfO'fiOONCO

cocororocooooooo

CO

199

o

z

Q

OlOOiOOiOOU")

OO-i-NNOlCO

CNNCNCNNCNNN

o

z

I

Q

a

OlOOiOOiOOLO

OOr-^CM(NCOn

E

_0)

Q.

_E

in

-*-

Si

I

a

-*-

C

E

S

o

U

E

i_

O

CN

co

—

m

z.

a>

T:

.e

*-

E

|

g

a>

—

£

8

STL

a>

.*

§

O

L_

Q

X

E

0)

i3

a>

c

^

o

"J»

a>

—

2

*:

c

E

„

o

a>

w

5

_cu

el

§

—

to

oQ

E

£

c

o

ill

in

—T

_o

U

CNCNCNCNCNCNCNCN

cocooooococooooo

E

0)

2

I

"ID

C

D

TJ

<D

C

QJ

U

C

e

C£

CO

00

c

o

1

E

D

z

U

i/i

E

a)

E

0)

E

r

u

c

o

E

a)

2L

en

CO

g

8

-i-

X

a;

-•—

3

E

(^

c

o

•*-

n

c

o

<D

O

o

CD

c

o

c

i

o

c

Ll_

u_

X

i—

OO

"E

a

1-1-

0)

_c

Q

-*—

<u

O

i/>

_Q

i/i

<D

a

V

i—

_Q

—

CN

co

•

*

IT)

o

r-s

CO

D

8

D

CO

co

fc>

fc"

o

"O

D

c

i_

C

CO

'~0

o

CN

CO

0

CM

CO

l_

o

u

c

Q

200

o

z

a

o

§

©

in

CO

CM

O'oo'oomo'ooioO'ooiooiooiootoooiooio

oo-'-N(Nn<

,

)'*ifinioooNscoooa>(so-^tNco

V>

V*

*/*

*A

V*

*/»

W

V*

W

tA

W

«/*

«/V

V>

4a**

V»

V*

«/}

V>

Z5QIQ5Z,5OZ5ZQ5Z2QZ5O.

..i

v)

w

io

i

1/ii/xni/iQ-O-o.a.Q.Q.o.

i

I/O

Q-

l

8.

-»-

_Q

s

CD

C

•

—

j

o

0

c

o

u

o

c

o

in

-7

u

I

'c'c'c'c'c'c'c'c'c'c'iE'c^'c'c'c'c'c'c'c'c'c'c

I

c

>>>>a£c£a;a;>>>>a;a:a£££ci£a£>>>a:>>c£

0)

U

V

<U

9)

E

I

g

1

g

a>

v

a>

E

a>

E

o

ooooooooooonnooooooooo

zzzzzzzzzzzzzzzzzzzzzz

g

o

z

-I-

E

o

ill

III

I

t

1

I

Ill

III

HI

III

111

III

I

Ill

III

-j

CQCQCQOQCQCQaCICQQQCQCOCQCQCOCOCOCQOQCQCQcQCQCClCOCQ

£

c

<<<<<<<<<<<<<<<<<<<<<<<<<

—

fl>

i—

•

—

i—

•

—

i—

•

—

i—

•

—

i—

_o>

jj

O

—

<NOOT)-U->>OI

S

NCOO.O.—

<NOO"<tlO

-^

"P

r-(NnTtlOONOO^r-^-i-^^^r-^-r-CNtNtNM(N(N

C

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

j

•

CMCNCN(NCN(NCNCNNMCNNMWCNMCNtNMCNMMCN(NCN

"g

&

m

n

(o

n

(ri

co

n

ri

n

co

n

co

ri

n

to

ri

ti

n

«'

ci

n

<*)

cn

O

£

CN

£

~

%

co

Q

201

o

z

_l_

Q

OiOOiOOU->OiO

OO

—

CM

CO

OU-)OiOOiOO>0

NNNNNNNN

oinomoioou-)

cocooooo.—

.—

NNNN0OCO0OCD

LO

<>

'

o

in

o

r

~~

•

1

o

CM

00

CM

00

o

CO

co

</>

OO

oo

>

I

E

0>

O

E

T

£

_

o

E

i

u

„_

i:

c

E

*.

-n

E

r

0)

E

.t:

2i

^

»/»

>-

E

o

2

01

£

8

0)

o

d)

c

-

.1

u

~

-°

I

c:

E

0)

"8

*

EU

o

E

£

LZH

co

<

E

<u

c

—

E

o>

c

P

""

•=

E«

-.°5cc2Ej»

io|t£Ei

„0

—

O

l

"EQ)_._

1

nO

—

O

l

-EttJ_.-«n

D

1

85

"5

||JJ|

8

|

Z

5

I|JJ1

8

oo

co

O

X

(—

—

LL

U.

I/I

CO

Q

I

h

±

U.IL

W

CD

UJ

_l

Oi

E

D

-*-

d)

"8

u

c

o

E^l-

2-2

^

E

—

i;

<u

CO

<

LU

_J

CO

<

o

X

C

c

o

•-

l_

=1

in

-7

m

Z.

U

CM

CO

CM

CO

CM

CO*

CM

CO

202

o

z

I

Q

o

00

m

o

m

in

>n

co

in

"n

t^

CO

in

1

,~—

,—

o

CN

in

m

o

m

in

o

in

o

in

o

O

o

in

«o

CN

O

o

in

o

in

o

in

m

CO

o

-o

in

o

-o

in

o

m

in

«o

in

I—

r

~"

1

f-—

•

r—

1

r—

1

r

~~

o

CN

O

in

CN

in

m

CN

m

o

CO

in

m

CN

o

co

in

o

CO

in

O

CN

in

o

CN

in

1

r—

1

•

p—

1

'"""

•

^~

o

t

CO

o

0*

o

m

in

o

in

m

in

m

o

CN

O

in

5

in

>n

in

<n

in

^

*

•

"

1

r

~

1

'

1

"

1—

I—

lO

IT)

CO

•

<*

CO

o

<n

co

CO

o

-o

co

in

o

•n

m

O

>n

o

in

•

n

<>

88

in

o

00

in

o

in

o

CO

o

in

g

O

CD

C

E

E*

S

*-

—

c

«£

E

«

0)

—

E

a;

-4-

0

"8

E

U

«

c

^

o

E

4)

E

2z

—

c

o

°-

r-

Ho"??

U_

LL.

CO

Q

-^

T;

o

E

=

o

o_

E

s.

0)

o

L7"

*

•

.

co

E

a

E

3

CO

f—

-o

^

5

a>

n

4-

x

_o

O

UL

LL.

CO

E

0)

-

E

c

£

o

—

<u

"°

S

<2o

c

II

u>

Z.

m

o

c

in

o

co

-<*

in

*+—

in

D

0)

O

z

CN

CM

o

Q

8

in

o

—

m

u->

in

Q

CN

o

-»—

Q-

'l_

o

in

<y>

w

to

0)

"D

_4>

CN

i

CN

1

r>

4-

•*-

D

c

~5

1

9i

1

o_

CO

Z>

i/i

—

,—

1—

&.

1

-*-

c

>»

4—

co

c

>

'*

c

o

-*-

~o

E

g

i

'E

it-

1

zf

0)

-*-

a

M-

<U

o

UJ

LU

in

_1

_l

_a

_0)

CO

o

Q

<

i—

o

I—

1—

h-

fr

1—

c

c-

c

O

LU

-a

-*—

c

LU

o

-*-

!

•

—

CN

CO

1—

0)

c

"O

o

0)

.

p_

,

"O

V

E

•

1

u-

3

c

0)

iZ.

in

o

z

CO

co

4)

O

Q

^-

c

D

ro

co

u-

0)

co"

CO*

Q

203

o

8L

X

E

O

z

Q

IO

O

IT)

O

.—

CN

CO

LO

lO

IT)

lO

CN

CM

CN

O

Q-

O

-4—

c

O

z

Q

o

LO

CN

LO

oo

LO

CN

8

LO

CN

IT)

O

o

—

CN

LO

CN

o

CN

LO

lO

LO

CN

u">

O

CN

CO

lO

LO

CN

c

o

'Z.

«-

II

in

-7

u

CO

VI

CO

CN

I

c

I

co

Q-

I

c

a;

oi

a;

e

V

II

V

E

o

Z

E

.1

u-

0)

Q

O)

c

_o

"o

1

c

1c

8.

E

CO

CD

CO

_Q

<

u

c

»—

1—

I—

1—

J!

fr

c

<u

LU

D;

"t

LO

o

t^

"O

•

U

c

r—

^—

1—

r—

c

o

CO

ro

00

^z

s

a)

CO

oo

Q

CN

oo

£

c

Q

IV

u

c

o

D

Z

c

o

U

c

o

•—

1-

it:

D

S

Z

_o

U

CO

co

«/>

CO

CN

1

CN

1

CN

1

CN

1

CN

1

c

-4-

•

+-

-|__

•

4-

-»—

•

+—

C

c

1

C

1

c

C

1

c

g

n

'

Q_

CO

1

CO

o_

1

<n

b

0)

•

5

>

r

Item

me

V

b

>

b

E

c

o

"in

on

b

E

0)

c

b

-*—

b

0)

b

ig

Item

me

R

b

0)

o

b

I

o

5

0)

o

°>Z

T)

0)

X

o

Z

d)

D

z

E

c

o

Z

u

4)

O

o

CQ

o

CD

4)

D

Z

-z

8

Z

~o

o

b

0)

c

u_

X

i-

-*-

CO

C

u_

Q

b

•

4—

LU

L1J

LU

y

_J

—1

_J

_I

_l

(P

CQ

CO

CQ

CO

CQ

F

n

<

o

n

H-

h-

1—

H-

t—

CO

(—

^—

Osj

oo

•

"*

•

LO

CN

00

CO

co

oo

CO

oo

00

oo

o

l\

•

CN

•

oo

co

•

oo

00

204

o

O

z

O

Q

LO

co

LO

CN

O

CN

LO

CN

OlOQiOlOOOO

—

p-OOCNCNCNCO

CNCNCNCNCNCNCNCN

E

i

E

E*

±

c

0)

_Q

D

.2

||

£

E

'

t

•

*-

«-

m

_0>

"o

E

«

.5

„

o

—

^

?•

a

2-5-5

E

I

.5

J

S

o

J

I-

_

u.

w

m

Q

c

LU

c

o

a

z

s.

£

0)

-Q

O

o

-*-

c

z

i

a

8

LO

o

LO

o

CN

8

UJ

-o

~o

<>

o

O

Q

co

CO

co

CO

co

CO

-a

|

M-

<D

Q

co

CO

co

?

CM

1*

"*

CN

1

-<*

1

CN

c

<*

1

'i

-•_

_!_

c

^J-

'

*

—

1

o

C

c

"*-

c

E

"c

•

—

•

—

c

"

—

.*->

•-—

~o

2

CO

1

co

z

co

c

Q

0)

CO

1

c

IE

c

E

0)

1

-*-

c

E

a)

CO

c

E

a>

CO

c

E

D-

0)

u

c

o

c

E

1

co

i

</>

CD

C

"»_

•4—

>

c

1

CO

u

O)

0)

c

CO

>

l_

"5

CO

-»-

D

O

CO

>

'E

c

E

1

-*-

c

a

<D

O

o

co

ci-

_c

t/1

_Q

l/>

_Q

E

vO

0)

E

1

0)

E

0)

E

o

E

a;

E

e

LO

1

E

O

1—

D

z

c

I

c

z

2

c

3

c

f*

c

5

4*

to

c

o

1

O

IT)

o

LO

o

LO

o

Q

0

LO

1

_0>

LU

_J

z

c

z

c

LU

z

-4—

c

z

c

LU

_J

Z

-^

Z

c

_Q

-o

CD

ac

M<

*

a;

•

CO

QC

,-,

~

a;

•

—

"

CO

Cri

o;

iH

I

<

K-

CO

z

I—

LO

z

<

I— 1—

co

z

1—

co

Z

<

1—

CO

c

co

a

£

c

,_—

CN

,^

CN

r^

CN

LU

U-

o

•

"D

O

i-

—

r—

—

CN

co

CO

J

8.

o

u

i

E

CO

co

•

co

ro

CO

co

CO

u-

3

"5

C|_

in

a

U

Z

CO*

CO

co

co'

CO

co

CO

co

CO

co

CO

co'

co

|

CO

c£

co'

2

205

o

z

a

O

IT)

co

<o

>o

CO

co

o

LO

"Nt

"*

0

-o

CO

co

o

to

o

U")

in

>o

<o

«o

^o

CO

o

CO

o

CO

IT)

O

CO

o

CO

o

-o

co

IT)

CO

OOiOOQLOiOlO

—

CMOCOOi—

CN

CO

oooooooo

COCOCOCOCOCOCOCO

u

•

"c

i

co

I

E

I

•-

C

TJ

—

0)

.x

CO

I

E

0)

t

o

f

z

o

-z

CO

£^

<

I—

tO

o

IE

1

•

E

z

Vo

.1

z

I—

I

to

CO

I

4

i

2

I

c

o

z

V

o

•IS-

CO

j^

<

i—

i

h-

to

-3-

c

CN

o

c

o

CO

I

c

-

o

7

E^

—

n

Z.

c

o

z

CN

Q)

-i-

0)

.

TO

I

CO

*.

co

c

i

£

L

S

c

t-

._

to

4)

•

2

?

7

CM

17

CO

-

.E

IE

i

O-

<•>

E

If

.1

z

in

o

Z

i.

oVo

C

LU

"5

<

»-

•2:

»—

to

LO

I

Z

•

£

en

I—

to

CO

0>

E

0)

>

-o

it

<

O

z

en

I—

CO

0)

CO

c

o

(1)

"O

CO

c

to

c

E

-o

«>

Si

-

•»

"8

«o

no

E"

E

0)

E

£

'

E

I

a)

^£

S

—

E

£

.E

•-

'=

E

5

a>

c

a.

E

i:

*

*r

tt>

—

E

0)

.5

2

.5

-

=

E

35

_

±

„

g

-

"£

-y

1=

Q

I

.EZ.

Q

£

a

to

c

o

n

E

z

•—

CN

CO

—

CN

to

•—

CM

"O

>o

CO

co"

CO*

CO

co'

co

CO

co'

CO

co'

co"

co

CO

co'

hs

t-X

CO

co"

CO

CN

CO

co'

206

in

8

o

CO

m

00

LO

in

CN

-*

8

in

co

UO

o

**

lO

CO

UO

lO

o

UO

lO

O

CO

Z

5

•O

Q

CO

O

o

in

ir>

lO

Q

on

$

3

escription

$

3

CO

c

o

-»-

Q_

"C

o

(/>

V

-o

E

•

CO

&

X

E

L-

<

C

j

o

c

•z

^

.9-

E

co

o

h

«

-*—

*

•

u

*:

C

c

v»

•—

o

a>

_c

u

T3

•

—

E7

CN

1

'5

a

i!

c

C

uo

(J

X

«

t—

r-~

i—

"

4—

*/>

1

-t-

-*-

1

•*-

E

c

0

•-

CD

>-

>

o

232

It

c

C£

Qi.

C£

o

~o

<

c

<->-

e

'E

1/1

u-

14-

o

c

o

1

—

CM

•

CO

E

Si

C

o

e

<

X

1

<

in

O

E

D

z

CO

CO*

co

i

<

1

<

-;;

1)

c

U

CM

.1

«*

<*

u-

"+"

t*-

CO

00*

&

co'

0)

o

z

I

Q

13

U

c

o

tz

«-

1*1

^

5

8

Z

_o

U

9

uo

co

lOQuomoiooinoio

inionouoioioiououoio

cocococococooocococo

o

CO

•bO

E

c

I

S

«~

~

**

£

c

8

g

d)

»

£

JJ

0

C

«*

"

a>

"•

•

£

-^iii*-

S5

.E

"

E

•-

""

c

O)

CO

.«_

CO

a>

a>CO

T3

CO

i:

a>

i

o

i

—

•

£

i

o

<ul

£

~

.£

2

JC

1

-I

£

.£

D)CM

CMCNCMCN

()

CN

M

0)

I

—

I

ccccccOc'Sc'c

TTTTTTTTTTT

ceccccccccc

._

—

._

g

>>>>>>>>>>>£

2

S

2

&

2

f>

*

<<<<<<<<<<<

u

o

—

CN

•

*

"t

•

<(

•

^1"

•^t

•M-

-*

•

*

•

t

"«t

"<t

cococococococococococo

207

o

z

Q

a

CD

C

'o

c

e

1>

c

a)

c

u

CD

C

-8

o

CO

o

co

O

CD

c

8

in

o

in

o

10

o

u-)

o

r-

^

M

CN

ro

cocococococococo

0)

ll

l

z

C

I

2

z

0)

T3

<U

CD

>-

-£>

4>

CD

SI

3

-C

U

u

*

<D

CO

-«—

-8

LO

—

o

CO

>

5^

0)

o

0)

«.

I

|

o

E

0)

I?

f

i

P

£

a>

Co

*:

to

11

§

£

Z

to

b

J.

s.

oo

c

•r

o

Si

I

•-

£

E

v>

„

«

E

-c

£

2

SL-

£

•

£

jpl

I

"

.E

E

±

*

•

"»

——

8

i

§

•

-

Q

O

lO

O

lO

o

lO

Tt

^J-

lO

in

-o

^o

CN

CS

CN

CK

CN

co

in

E

a>

£

c

Ll_

X

if

ft

1

c

0)

a)

merit

teme

E

f

f-«=

f

1

o

z

1

0)

o

O

1/1

tO

*

ment-

Swit

ment-

_c

0)

<D

S

0)

»

r-'

°

-4_

-I-

i)

a

o

"a

D

O

o

y

'N.

.t

*

X

to

_

to

1/1

O

*

«"

u

o

to

g

t—

_c

_C

_c

—

o

u

o

u

/

E

£

to

-*-

•*-

•

*-

*"

•*-

*-

0)

—

*

U

X

UJ

to

XXX

to

t/1

X

to

X

Z

LU

n

°

z

-8-8-8-8-8

T3

UJ

-fc-

o

c

UL-

to

co

c

o

°

1

si

in

-7

O

•E

U

co

r-Mr)Ttio<ONoo

r-

<N

n

^

io

o

F—

—

_,—

.—

,—

CNCNCNCNCNCSICN

LnioioioioioioLnioioioioioiou-)

COCOCOCOCOCOCOCOCOCOCOCOCOCOCO

u

c

<

I—

<

u

LU

Q_

CO

o

<J

o

1-

o

-a

c

o

oL

-£1

o

'l-

CD

c

•

—

p

•

—

o

c

s

4)

CD

0)

o

D

>

208

4>

u

•

—

C

O

E

o

z

I

Si

c

o

1\

E

D

Z

U

o

<o

O

^o

o

,—

o

O

o

^t-

5*

•

*

"*

If

4J

i?

T

c

T

4-

."tz

'o

p

Q

eger

ed

p

a

4>

o

c

X

O

o

M-

to

_D

<•>

vo

t<»

«^v

X

(1)

-8

4>

<u

T3

"D

-o

C

c

C

c

^_

J_

!

4_

c

C

c

s

4)

c

a;

c

s

o

CL

a.

Q.

a.

E

o

u

o

a;

o

4>

*

c

?

c

*•*

*«

tA*

en

ca

co

—

CM

00

T}-

"*

•«*

•

T}-

8

8.

E

o

-o

c

o

_4>

"l-

5

o

0)

?

o

z

I

Si

u

c

4>

c

4)

o

u-

a>

•—

i_

UJ

1—

fica

mbe

UJ

1—

>-

en

4)

lassi

Nu

CO

1

u

CM

IZ

D

"*

>

o

IT)

o

lO

00

CN

CS

o

^

•

*

5f

«t

1"

c

o

JU

-C

E

.12

c

"C

4>

E

o

0)

.t

5

c

"tO

to

'i

~o

•

£

2

Urn

in

<u

0)

d)

c

E

11

Co

wv>

X

0)

"D

"O

"D

TO

c

C

_c

^_

-t~

•*-

-4-

c

8

0)

a>

a)

c

o

a.

Q.

a.

E

o

u

U

o

a>

o

£

§£

UJ

LU

EFFE

>>£>>

•

«

CO

._

00

CO

._

—

CM

CO

^t

CM

CM*

•

o

c

-C

E

i-

o

SI

o

CM

ac

<

X

u

oo

J!

T3

ol

4)

</>

-D

-2

s

J

O

c

8

-*-

c

—

1

E

"5

•

—

4>

o

•

o

-C

-*-

c

-^

o

c

u_

-1-

c

-8

c

IE

•

—

>

c

o

c

8.

f

at.

IE

-8

c

z

LU

1

8

f—

4)

z

4)

lc

ULJ

t4_

c

o

E

o

1

4)

c

o

>

•

an

>

•

an

I—

z

o

u

i

E

z

"*

•

«t

Li

t—

UJ

to

•<*

^J-

D

z

4)

_o

o

LU

CJ

0)

O

u-

"O

i/>

"*

—

jz

•

o

1—

^J"

>

209

Q

CN

Tj-

>0

00

CN

(N

M

CN

^t

^

5

O

z

I

O

(N

t

vO

CO

^

c

o

~

l_

o

1)

Jj

f-

D

l/>

7

O

u

c_

1

«

c

a,

5

I

£

S

1"-

I

i

s>°

a

CD_?

o

•»

"w

o

x

_

<

UJ

_

c

cS!

o

—

c

££££

CN

CO

Tfr

lO

"*

•

*

"«t

•

*

<*

-*r

-^

TJ-"

8.

£•

«•>

Z

X

a>

"O

u

c

n

-*-

>-

c

Ci

0)

D

oo

J>

I

•

a

i

2

.E

•

8

O

5

m

=

j_

—'

O

c

°°

**

•

«

<

*

•

<u

s-8

3

5

c

E

o

CL

E

o

u

c

o

It

o

°

to

d)

—-

I

00

£

I

CD

C

E

-

^

"o

it:

iz-

3

uj

I

0)

_tt)

_Q

o

a

X

x

4)

c

o

E

o

c

a,

c

o

Is

0

o

ai

—'

§

I

1

|

f

T

-£l

_Q

:

a

o

&.

C£

***

zz

Jzz

LU

~D

LU

UJ

—

CN

.E

CO

"*t

c

o

4)

_£)

E

D

z

u

CN

c

C

0)

E

I

0)

C

0)

1

2

In

<"

Q

CO

LO

-*—

t

U-

-

•

—

c

l/>

o

—

CO

0)

-*—

erne

c

1

0,0

O)

-n

e

is

c

-4—

-•—

c

„

c

3

o

0)

_g

o

tx

CO

to

y

x

0)

(/l

U_

<

X

|-

UJ

D

C

c

CO

o

D

o

—

c

C

c

t/>

a,

CL

-»-

0)

-J=

_c

£

££££

15

o

—

CN

CO

•

«*

•

in

c

>-

CN

i

l—

-*

•

>*

"*

•

-*

•

*

o

z

^f

Tf

"^

<*

Tf

~o

a,

8

D

LU

CO

210

o

z

I

Q

0

z

O

N

Tf

•OOO

O

-**

-^

-«t

-*

^

lO

1

CM

"*J-

>Q

CO

O

CM

IT)

Ifl

IO

>0

O

^

TF

^

-5

Q

^

^F

Tf

^*

Q

CN

5

o

00

CO

o

^

5

LO

CO

00

Tt

><j-

Tt

"<t

I

IflO.

I

LO

CL.

I

w

v»

v*

<»o

w

4JO

I

GO

Q-

I

00

CL.

I

t

I

t

c

*

c

>

oc

&.

a

Si

V

Si

UJ

LU

UJ

LLl

UU

J

rcy

rfi

rf\

ff\

rf\

<<<<<<

i

c

l!

c

>

oc

at

'g

g

LU

UJ

11

I

—I

_J

—J

m

ff\

rn

cCi

rO

flQ

<<<<<<

O

0)

E

%

g

y

2

E

HI

E*

E

i

2

0)

E

•

~*

.

•

t:

E

8>

ID

Q-

i

a>

E

-L>

_n

n

-*—

*—<•

*—

*

*—'

U

O

OO

O

c

o

II

to

-r

o

u

—•

CM

CJ

T|-

IT)

»0

CO

w

"<t

"*

""t

•

<*

"*

^J"

•

"*

"fr

"«*

W

TT

c

o

-*-

o

£

z

u

p-

(N

CO

t

"1

O

-<t

-*

"^-

"*

""*

"<fr

-<*

•

**

Tf

-«*

O)

u

c

o

*~

1-

O

_i

c

•^

E

OJ

14-

_

LU

u-

•

-

D

?

S3

Z

O

££

0)

_

CL.

D

u

LO

—

O

^4"

>

.—

CM

oo

^

IT)

LO

to

ir>

"*

•

*

"*

-<*

211

I

Q

Tf

NO

00

O-

^

-5

O

z

5

Q

8

u->

o

m

o

u->

O

—

CM

CN

CM

CN

•

<t

•

*

•

*

^

t

•

<)

•

o

in

CO

CM

c

o

IT

K

Z

_o

U

li?

E

i

-

tt)

«

c

a

U

ooo

e

V

-C

•

a

o

c

T5

c

o

2L

8.

_Q

O

-*-

CD

c

'i

_o

"5

aj

—1

-3

u

2

e

4)

-C

>-»-

c

u

&

o

lO

>0

hs

1

h-

8-8

•

t

•

i/>

Z

•-

E

io

m

>o

y—

1—

LU

it

5

•

*

-M-

•

**

•

Z

Hi

Z

z

1/1

—7

2

z

<

3

LU

0

5

O

z

0)

u

o

u>

tN

—

•

_c

•

o

<*

1—

•

«t

>

fe*V

</v

«/>

v*

*/>

"_«?«?

i

I

i

%

11

C.

•

—

•

—

g

Ji/i

D.w

a.

i

•

1

LO

Q-

8

„

-a

_

V

O

i

4,

JL

J.

A

2.

i.

1

*

*.

4

dinary

ta

me

R

me

R

me

V

me

V

me

V

me

V

"ined

Enti

me

V

me

V

A?????

8

,s>

8

Z

_J_J_J_J_J_I'7_J_J

•

^

•

t—

i—

t—

i—

-*-»—

i—

p-

(N

CO

'"t

U1

O

—

CM

—

,—

.—

—

,—

_

CM

Z

IsNNNNNIsNNS

co

00

8.

O

CD

C

'5

_o

~o

u

c

E

OJ

fi

Z

LU

CO

Q

o

5

212

o

z

I

5

o

in

o

ir>

o

—

CO

ro

CO

-<J-

"*

^t

">*

O

z

I

Q

lO

O

^

Tj-

lO

CO

"*

^t

"*

o

z

o

Cs

CO

«^»

*<«V

<J*

W

I

1/1

O-

W

I

c

o

it

§

s

Z

_o

U

i

-*-

-*--*-

-*-

c

>

c-

>

I

g

I

g

2

g

CQ

00

CD

00

<

—

CM

CO

-<*

•

CO

00

CO

-«t

"<*

"*

•

^r

Q

O

c

'u

c

Q

O

o

O

D

>

4)

_Q

a>

n

at

"C

JQ

_Q

n

~>

l_

O

o

4)

>

D)

T3

a>

x

o

c

o

<*-

*~-^

^

•

^

Q

ooo

•—

CM

CO

OS

CN

OV

"**

•<*

"^

o

O

-D

JS

•

*-

O

c

-D

c

o

c

o

Q-

O

_o

O

o

c

5!

0)

c

o

i.

*—

«>

7",

~

3

ifl

-7

in

Z.

a

U

213

10

u">

o

z

^

1

Q

o

o-

ON

5

^

>o

«0

IT)

00

OO

o

4

3

^

Z

i

o

O

U")

u->

o

in

o

5

m

tX

I^N

tO

ON

00

ON

NO

^

<«

•

^t

"Nf

"Nt

"Nf

'Nf

Q

<*

>*

-Nf

"Nf

^

Tt

0>

3

0)

U

0>

Q.

u

c

OO

o

-*-

c

V»

VI

a>

g

>N

c

OO

v>

c

3

ii

c

0)

c

0)

JJ

d)

4)

""

*-

s

•*-

>-4-

0)

^r

(I)

*-4-

0)

fi

t^

e*

u

c

-£

vi

cc:

U

(1)

LO

Qi

a>

HJ

O

_5

3

-°

I

o

c

*:

O

—

<D

0>

-*-

ar

IT

0>

U-

L-4-

d)

0)

o

S

o

0>

-Q

e

tt)

_Q

C£

Q£

E

.2

V

o

—

-4-

o

2

O

>N

0)

i_

e

°E

i

E

8.

o

i—

i

o

£

3

<

i—

o

E

S

-

5

E

>

i

E

>

1

O)

o

O

"O

•

8.

1

-4-

3

V)

8.

1

i

-4—

-4~

V)

v>

s.

lO

e

3

i

-4-

•4-

VI

Q-

Li

v>

V>

VI

IZJ

Hi

c

i

e

3

O-

IZJ

3

o

0)

3

Q-

_l

4-^¥

_l

—1

a>

at

|o>

8

2

"O

9)

O

CO

C

a>

u_^

i

C

^

0)

U

i_

0)

i

z

o

1—

9

z

<

o

-4-

1-

_0>

'5.

E

ROGRAM

v>

3

-u

<u

o

tfc

O

i_

o_

"O

4>

c

OC

name

OC

name

i

E

£

3

o_

E

a

c

U

O

o

L-

£

3

O-

3

0)

E

a

c

U

O

*'

ai

aj

—

-

E

1

E

jjj

E

£

nj

a_

Q_

-4-

•*-

P

^

3

*.

ir

«-

Q-

D_

Q.

3

2

<

o

u

Q-

"O

8£

c

an

CL.

o

a.

8.£

c

OO

O

0)

T>

3i

Od

C£

_c

u

3

o

2

o

Q-

O

c

o

1

E

r—

CM

v>

e

3

c

u-

O

0>

O)

3

c

o

u

-i

—

CM

00

^r

o

UJ

2

15

o

»-4-

v>

o

3

Z

lO

"O

4)

u

o

to

3

v>

O

3

Z

CN

lO*

CM

UO

CM

»0

CM

lO

Qi

CXL

E

-C

Q-

Q.

0)

u

Q-

CM

CN

o

0)

U

>

•

0)

_c

m

lO

1—

"O

lO

(J

214

o

z

I

Q

c

o

D

O

o

CO

o

5

01

E

O

z

oi

o>

u

c

0)

a)

l_

i_

a>

w-

i-i_

ai

oi

Oi

Qi

x

ID

E

_n

L-

n

<

i—

0)

4)

II

e

E

Q.

CL

-4-

-*—

oo

D

"D

0)

O

01

c

01

0)

O)

o

D

c

D

CN

LO

O

3

o

LU

Di

D

01

O

o

01

C

M-

4)

T3

0)

en

s

?

oi

o>

o

u

U

O

z

I

c

o

.2-|

a

Z

U

o

m

o

io

fcfc

00

"t

-*

<*

^t

~

CN~

1

.*-

c

I

CNI

1

CN

o

E

c

01

oi

4)

o

-*-

o

i_

i-

i_

i

0)

01

oi

O)

CD

0)

0

0)

<u

-*-

C

c

*.

«*

*»

T

•

4-

C

T

"_"

E

jfl

oi

a)

0)

Q

•*-

O

i_

1-

0)

01

0>

01

CD

CO

co

CD

01

0)

a>

0)

c

C

c

-—-

—

-—-

oooo

3

52

2

o

z

i

a

4805

4810

4820

4845

an

Di

a;

o;

CM

CN

IO

")

IO

o

a;

</>

c

_o

o

c

D

U-

-o

01

c

o

c

D

13

0)

Si

d,

D_

O

qj

I-

E

^_2!

S)

JJ

—

o

9

s

S

£

c

o

t

o

^

o

oo

_

X

Q

8

«:

o

c

o

in

C

o

t3

c

D

CO

in

01

Q

3

CO

in

01

CD

8

0)

_c

-X

o

01

_c

2

E

z

u

ro

215

o

00

CO

oo

O

z

Q

o

in

oo

—

oo

9

o

9

o

to

o

m

O

^N

no

00

•

*

Tj-

-*

•

*

•

*

O

IT)

O

—

CM

00

CO

00

TJ-

-*t

^t

TT

-<fr

o

z

I

Q

O

Q

iO

O

lO

O

—

CM

LO

IT)

lO

LO

CM

LU

CM

O

Qi

1

w>

OO

E

c

*-N

"Cl

c

£

v

VI

o

t_

ha

0)

i

5

LU

oo

CO

<

item)

nteger

intege

•

LU

oo

O

Q£

C

_i

e

"O

o

0>

CD

-

*

-

—

u

a.

c

o

r

List

Formula

c

o

OO

CO

<

t3

c

"O

0)

0>

I

-•-

•*-

c

_v°T

7

P.

^oo

E

^

„,

co

ai

0)

OJ

n

LU

oo

O

i

u

c

o

c

o

t>

c

1

o

c

8.

>«.

•

—

c

o

c

o

0)

o

CD

c

'E

1/1

c

e

CD

C

-*-

J

Ll_

0)

X

Para

mete

Boolean

l-

0)

CO

<D

-#-

c

O

h—

E

<

CD

c

1

u.

</>

c

o

t3

c

-D

0)

CD

o

nteger

it<

ger

=

A

integer

it

integer

it

integer

it

integer

a

3

0)

c

4)

o

-4-

u

c

D

•4-

3.

c

(1)

D

CD

C

o

•

III

LLI

o

c

r>

Ll_

si

Q_

u_

C

•<

a;

o£

c£

D

3

0)

c

o

u

CM

8,

1-1-

o

c

o

1-

•

—

CM

CO

•

—

CM

CO

c

<1)

o

i

_

o

CD

o

(J

1

CM

CN

CM

Q

a)

OJ

D

E

r>

Z

CO

m

CD

c

o

—I

8

1/1

o

E

D

z

CO

lO

IT)

<o

lO

>o

3

8

0)

-C

_C

u

CM

co

o

4)

U

u

oo

CO

in

U

0)

u

216

o

z

1

O

a

MO

a

uS

1

o

00

<o

o

oo

o»

o

lO

to

lO

c

o

u

E

3

z

u

o

—I

u

co

IT)

Z

2

-*-

D

Z

OJ

a

D

o

_c

-*-

U

_c

U

c

o

"-

l_

ft

5

X?

Z

_o

U

c

o

c

-B-8

«

o

-o

K

O

0)

o

I-

1/1

MM

Q.

3

O

E

£

o

Z

Qi

fl£

Q£

LU

UJ

LU

r-

CM

CO

"*

•O

IT)

O

\—

z

o

2

o

CL.

o

I—

o

in

OJ

3

"8

E

_

_o

'u

8-c

o

>

c

—

O)

s.

SJR

1

=

*

1

«£

OTO

featu

O

•-

_c

0)

*-

c

01

•

—

D

3

"5

^

"§1

E

4-

O

in

•

*-

Q

«,

E

OJ

..

y

OJ

c

g

£

oo

<*:

£

•

*-

t*

£

"O

E

a>

a

£

V)

O

g

o

a

o

S

<*.

o>

</>

_c

._

*

•

_c

«*.

•

*-

c

°

CO

o

%>'-

o

CO

*-

(J

D

">

^

3

*

•

"oi

0)

£

O

*

•

TJ

U

<u

>

7^

«

u

-3

o

Q

CM

o

Q

in

o

-o

o

^t

Tfr

lO

CO

I

oo

I

s

8

""

_c

i-

?

£."£

E

|

4/)

I

i

Hi

E

J

o

_2

5

"I

.*-

"7?

-J-

c

o

oo

I—

t—

h-

o

—

CM

CO

•

<*•

Q_

"l

*~.

"~.

"I

»—

O

LO

•

a

.8

o

c

e

3

o

aj

E

OJ

CD

8.

o

OJ

"^

c

o

_0J

-D

(/i

8.

3

D

CN

(J

>o

<£

217

o

CO

CN

O

z

I

Q

a

o

10

O

lO

w>

m

>o

o

oo

^

t

-«i-

-<t

oo

in

—

in

8

U

Si

D

O

a;

CO

a

0)

o

0)

u

c

o

II

_o

U

to

_0)

D

•

4-

c

"O

in

1

i

s

O

s

0)

o

io

5

i;

"D

IS

^

4J

c

3

0)

c

O

o

a.—

>

0)

E

o

u

E

-a

'in

35

3

1

X

>.

r>

^

—

_Q

0)

—

i

<D

i

o>

m

*

_2

-2

•

4—

O

t*.

-o

I

O

"o

*-

o

<J-

4-

_

.+_

c

£

__

c

92

.2

o

1

i

»

8.

to

CO

V

2

«._

o

tn

±t

Z

0)

.4-

U_

en

a:

o

CM

•

V

ro

X

o'

h-

UJ

u_

>*

•

o

8.

E

l/>

O

5

o

"2

o

a)

CO

8

D

•

II

_

o

0)

U

E

g

E

a>

E

<u

c

o

I

E

jo

U

i/>

C

n

E

O

P

<U

'«

P

c

~

2>

±

.2

o

P

0)

.=

IA

E

TJ

J>

co

+:

D

>2

0)

o

*

8

o

p

.?<

oo

J:

IL

w

i-

<

r-

CN

ro

^

io

>o

*0

^)

^O

^

'O

*o

a.

o

O

-d

Q-

J

en

o

O

e

c5

o

0)

4)

CO

SI

D

_y

u

<u

_c

U

218

o

z

I

Q

c

o

I

E

it

5

S

Z

*<t

-<t

3

-^F

^

u->

io

-

cococooocooooooo

3

^O

00

O

CM

lO

O

<0

-

CO

OO

CO

lf>

lO

IT)

3

g

•4-

o

D

u_

1=

^

oPO

C

o

2>

LL.

.E

»9

9

gg

O

25

TO

.E

«=

ro

•-

i

I

.£

11

i

*

11

I

U

c

i

ui

SO

I

i

I

s

e

i

1

i

I

e

fi

«

n

o

s

£

°

O

£

4)

O

U-

u_

u

u_

P

°

«

LL.

0>

0)

0>

01

0)

o

c

—

I

--&&

'

at

I

a;

Q;

^

00

0

^

oo

O

"-

LL.

O

LL.

LI-

21

^=o

•—•—

•

£

•

DTJ'J

C

>

O

at

O

OOu-

o

•

£

p

LL.

O

U

°

o

J>

u-

tu

?s

\7>

O

U-U-O

OU.LL.-DO

O

o

"-

a,

0)"-

<U

«

0>

""

LL.

j,

Z

JE

-c

O

.^xi^.j.j.j

-OOOOM

CO

at

atatO

OO

o

O

LL.

D

Xl

u_

c

_J_

o

F

u

0)

LL.

<yi

s

8

-

O

LL.

OO

£

<U

4>

.

T5

-7;

°

*r

-Q

—

c

o

2

?*£

(J

•

'

c

Q;

at

0

O

Z

LL.

1

O

8.

u

t3

o

_0

LL.

o>

ID

o£

oi

4)

Oil

o

LL.

O

LL.

c£

at

OO

LL.

o

t3

o

LL.

0)

01

g

c

^CMCO-^J-lOOt^OO

.—

CM

CO

-*f

lO

—

CM

CO

"**

•

tf)ioioioioioioinioinioinioioioioio«nioio

•

O

*0

^)

*0

^)

•

O

>0'0^

N

0'^*0*O

s

O

s

O

,

O

s

O

s

O

>

0

c

o

c

o

Q.

o

_o

at

o

c

"i

o

01

c

D

I

01

o

z

Q

a

01

-C

+

•

u*_

o

c

o

L-

c

o

a

o

U

a

o

t4-

o

01

O

o

_c

_J

U

^

01

_c

o

U

01

_Q

E

n

Z

O

CN

Tj-

O

O^

o

CO

io

u->

uo

m

0)

0>

JD

^3

D

O

L_

1_

o

>

a.

o.

o

—>

_i

c

.C

JC

Q£

^-

4-

C)

Di

*

Ll_

o

a)

a>

11

o

_Q

o

O

^~

1-

u

o

Li_

01

o

Ll_

>

U

O

-C

*

O

r-

M

CO

Tf

o

*o

•o

^o

-o

>o

219

o

z

Q

o

10

o

—

>*

"**

•

*!-

if)

IT)

lO

ioo<ooinoioQio

omo

M(

Y

)C)-<t'*if)iON0>O

N

00

iOir>iOir)ioioir)iOio

in

ir>

in

loomoiooio

(DCM>OO^r-

"<t

"*

lO

"O

IT)

to

in

*

z

o

1—

1

c

o

o;

O

in

m

Ll_

0)

t-

LU

Q-

Oi

X

3

LU

s

U

LU

1-

y

o

e

3

£

z

c

o

p

i-i

=

3

o

U

I

~

in

O

<U

E

m

O

8.3

o

O

.2

>

u

o

c

X

>

°

J

uO.

E

<"

-n

•

£

J»

%

O

2

e

c

o

p

u

8.

O)

C

O

"Z

b

8

g

IX.

Z>

P^

1-

^.D

O

m

a

S3l

2L.2>

O

o

c

o>

>

"5

•

5

£

%

5£uZ

*

+

_Q

^-

in

.5

**-P

O

</>

O

>

_»

-c

C

o

>

£|l=

8

-S

S

*

•

I

_Q

•

•»

O

<n

O

>.«•;:

.5

.2

>

"5

"*-

•*-

a.

o

c

o>

>

£

c

*-

°-

i

^

8

£

%

TL£IL

si

•

s

P

£O;-E

<_

«*.

TJ

c

o

~a

'o

<u

<

c

o

c

o

Q-

X

rj-8

S

-2

S>

Z

z

5

I

*

I

+'

<:

*

I*

I

+

*

m

n

i;

-O

0)

5

'

•

£

8

o

•

I

2

ix.

tx.

ca

0)

£

Z

c

-P

O

_Q

*£

°

a

\~

l>

O

5

—

D)

O

0)

^£

.

o

in

a

o

tt)

'z

'

">.E

•

o

c

Q.

>

£

o>

I

x

8

I

JJ

D

_Q

u>

O

_0)

-c

_Q

O

.2

•

>

*C

<-

o

c

>

o

u

CL.

4)

"

X

c

r-

D

>

O

CL.

c

8

^-CNCO

—

<NCO-*t-in*orv.COO

^

M

00

i-

WfTt

lO

>ON

•^p-^^rNnonno

,

)P)co(

,

3Pioo^

,

<t'*'^'ininir)ioioio'oin

220

Q

o

in

o

»o

o

in

CM

to

n

-^

Tj-

IT)

If)

IT)

10

io

10

in

10

o

z

1

8

IO

o

IO

Q

o

,—

00

en

CO

00

O

in

</->

in

LO

o

>o

O

IO

o

(N

CM

(•)

tO

Tf

co

oo

io

in

u->

3

£

Q-

X

~o

c

3

O

Q

*in

**ft

*«

C

O

C

t/>

i/i

o

c

•TOO

o

O

U

.-

"O

TJ

-Q_i»

«»

O

<D

O

C

Q)

T>

<D

U

>

Q

TJ

0)

U

E

CO

>

Q

-o

-a

a>

ID

a)

o

E

CO

'£

8,

.2

M

12

-(-

u-

o

aj

o)

a)

u

o

c

H

<D

0)

•

D

"D

-O

<D

0)

<U

u

o

c

o

8.

*JI

>-

,—

CN

oo

•

»*

•

in

o

h

assifica

Numbe

o

>o

>©

o

>o

o

U

I**.*

IN

r«."

rC

t>»*

tv

r^

0>

Q-

E

<J

I/O

c

o

c

8

?

c

D

V)

C

o

8.

E

o

0)

c

o

II

z

CN

O

4)

U

u

t/>

c

D

c/>

0)

o

«c

>

.2

£

S

>

.E

>

E

°>

s

"S

—

cn

J>

x

8

g

£

i

52

v>

£

>2

i«

o

E

«,

8.

8.8.8.

e

O

OOOO

2

c

o

n

o

c

tj

o

^

£

c

o

DODO

a>

oi

a:

_Q

O

*!_

o

>

Z>

<

i

«,

-Q

"i

in

T

1

0)

<A

—

c

0

E

X

H=

1

I

2

5

E

IT

8.-E

O-o

o

±

o

cr

c

o

1

s

cScScSO

o

D

cr

o

.—

CN

CO

TJ-

if)

vOtVCOO

CMCNCNCNCN

CN

M

CM

CN

r^N.'rvrN!r>!

N

8.

E

o

U

"D

0)

C

D

Jr

u

c

o

8_

E

o

u

~o

<u

c

o

_c

u

o

U

221

o

z

I

Q

a

o

u->

o

10

o

w>

o

O

—

r-

CN

CM

CO

o

>o

*0

'•O

"O

>0

*o

c

o

B.

8

o

z

I

Q

LO

CO

<>

^o

LO

o

CN

^

<>

co

o

r—

'O

O

<>

5

<>

o

CO

5

in

CO

LO

O

o

in

CN

o

00

LO

o

CN

00

>o

1

o

CO

c

o

o_

o

e

^~

•I

0)

•*-

>

•8

-<-

<v

c

i/>

_c

1

ot

-Q

c

Irt

0)

o

•

—

O)

l/>

fl]

er

Variable

1

Variables

ing

Variabl

Variables

-Q

D

"i_

O

>

1_

o

>

c

o

'<n

E

tn

-*-

C

o

-*-

c

o

U

o

c

D

Q

z

oo

h-

z

LU

2

8

<

c

•

—

i

c

1

°>

^

•

*-

^B.

d)

i/»

"o

<

•—

Q

LU

o

c

£

s

8

g

~o

c

E

t5

l/>

s,

Oz<^

1—

<

1—

i?

£

LZ

H

Q

X

O

C

1—

z

<

o

"l/>

in

o

CO

-*-

<

°i/5

Z

1—

C

o

c

o

-

1-

11

r—

CN

CO

-*t

CO

LO

CO

tx

CO

i

X

LU

c

o

CD

5

D

c

o

i

E

3

—

CN

CO

"*

-*

-N""

z

LU

u

c

e

c

2

c

o

8

CN

O

1

5

Z

a

E

c

D

<D

O

CO

D

in

-4-

C

LU

8

Z

o

fx

tx

r-s

tx

IX

rx

4>

o

z

ix*

r>!

rx

LU

CO

J

CQ

U

Qi

<

_0)

D

.—

CN

CO

1-

LO

o

•

<t

01

-;

o

IX

U

00

CO

5

222

CM

CO

c

o

CD

O

<u

LU

o

z

u

X

LU

u

0)

o

Z

Q

LU

4)

C

0

o

u-

z

o

u

<

4>

»-»-

X

D

X

4)

-5

E

z

u

8

iOOiOOiOOU-)C?

in

o

5

«o

_4>

-Q

•

.2

—

1-

O

4>

>

o

•

£

>

-z

-c:

«-

O

4)

0)

>

=

CO

_

o

*Z

4)

-

1

-

.*

II

"-

II

_4>

4)

H

_Q

ja

«

.2

4)

*-

8

v

^

•

£

.*

o

_

u_

X

_4>

-O

u

o

>

c

o

'a

•=£

•

s

§^

.2

4)

-^

"3N

«

_4)

_D

O

_4>

o

•

£

>

-c

i.

O

II

4>

>

=

»!,

o

4>

T3

-f

*:

4)

-

1

-

-£

.*

4>

4)

"-

3

15

_4>

£

II

•-

II

o

ii

.2

4)

||

o

.£

CO

D

4>

II

_4>

II

_Q

0)

o

*1

c

>

4)

3

J!

>

.«

.2

*i-

"in

O

">

>

E

_Q

15

<u

.2

•Si

o

_

>

.t:

4)

1

-

4)

$

=

£

U-

X

O

iO

O

U-)

-o

^o

r^

rx

"*

3

^

v6

-o

o

Q

i-

6

B

oo

on

4>

4)

_Q

_D

_a

o.o

o

a

D

Q

_4>

JD

O

I—

II

_4)

-O

O

4)

O

II

c

o

_4>

O

OO

_4>

_Q

D

_4>

a

i-

2

CO

o

>

-Q

>-

°

1>

S

4>

"S

_4>

||

"§

"

•c

J>

O

0)

_Q

>3

.2

c

o

J;

•

2

'i£

.2

>

c

O

II

.D

oi

«

2

</>

o

w>

4>

a

>

in

D

-*—

co

4)

II

_4)

^3

.2

^3

a

_2?

LO

•Z

-Q

I—

o

Q_

>

"

LU

^

o

U

£>

Z

i—

n

z

u

LU

0

z

o

r—

cs

co

Tf

m

o

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

CMCM

CM

M

(N

oooocooocococdcococo'

00

CO

coco

u

LU

—

a

LU

o

z

LL.

LU

Q

o

I

5

8

58

o

z

5

a

4>

_>

"

•

4-

u

»

—

-a

CL

E

o

a

4)

CO

a

D

o

4>

223

<©

o

>o

z

1

o

LO

Q

o

LJ

o

•o

o

z

I

a

o

in

o

in

o

in

o

in

o

u->

o

—

r-

M

N

CO

n

^

^i-

NNN

NNNNN

r^

hv

•o

*o

«o

"O

>o

O

^O

-o

o

R

O

CN

0)

u

_0)

'Q.

E

o

u

o

0)

c

o

a

z

p

u

_Q

0)

n

-O

h-

n

i—

^

15

g

0)

c

15

£*-

i-

o

4)

D

I

m

—

CN

LU

>

o

CN

I

8

<

15

0)

E

o

>

UJ

>

o

u

c

o

0>

c

it-

a

c

o

•J:

•-

.2"!

it

I

a

z

_o

c

I

C>CN

E

4)

tO

*/>

•

g

i

E

0)

II

SEE

8

8?

II

CN

table-

array-

:

item-

(O

li

ll

"

a

n

Q

E

g

i

E

0)

-*-

item-name

table-name

w

*y>

in

CN

I

?

_a

a

o

ll

n

I

CN

°

g

|

kg

E

<u

n

P

e

i

g

i

j)

_«

.£>

-a

2

1

i

I

o

11

g

I

X

0)

E

E3

o

2

CN

O

I

CN

S32S3CNS33SS

Q;

c^

Q;

ct:

D^

•

c^

c£

ex:

UJ

LU

S2

LU

X

>>>>>

£>>>>>

\

ooooo

gooooo

g

—

CN

CO

Tf

co

CO

O^

ON

O*

0

s

O*

CN

I

CO

a

c

p

c

o

u

3

*°

°

>-

g>-

2

gs

LU

V

LU

>

3

>

O

2

O

iO>ON00O>

—

CO

8

I

_Q

a

c

o

c

o

F

o

-St

CN

CO

CN

co

224

I

si

U-

_£

O

0

^

file

*

6!S

o

z

Q

c

o

ST

K

Z

U

10

o

in

p

u->

in

"O

vo

tv

i\

rv

tv

hs

r>.

K

^o

^

^o

*o

11

T

e

8

i

o

2

i

E

4>

8

i

7

"

e

i

2

i

o

II

8

i

_4>

_Q

O

c

D

to

C

o

u

c

o

t»

c

o

c

o

-*-

m

c

o

v

c

o

•

»-

c

o

c

p

c

o

u

o

>-

<

_l

UJ

>

O

p

&*

p

<&

p

V

O

CM

5

«*

O

|

l>-

1

>-

I

is

?

I

OS

I

OS

J

.tOiOS

O

i

o

>

%>

5

?2

ii

i

•"*•*

LU

>

E>

O

oO

CM

I

IT)

I

a

4>

1

E>

85

O

in

o

in

00

cs

o»

<0

sQ

>o

o

s§°°

4>

E

8

I

E

CM

I

8

I

E

4>

0)

.-

•-

II

£

.t:

II

8

_?2

I

-Q

E

2

t>

T

11

7

8

I

o

2

II

I

f

o

c

I

o

v~>

I

_4)

-Q

O

i

e

8

i

a-

b

o

1

o

II

D

3

c

D

C

JJJI

_g

JS

iJ

1

E

C

>

•

>

•

>>

C

OH

Oi.

UJ

C

<

—J

UJ

V*

UJ

vo

§O9OO~OOYOVO

CM

CO

CN

CM

to

CN CN

co

—

CM

CO

CO*

CO

-*f

CO

co'

CO

co

o

CO

o"

co

o'

CO

o"

CO CO

o"

CO

o"

cs

CO

CS

O*

CO

o'

co

o"

o

cs

P

o

c

tL*-

v

escri

f

the

nsequ

TJ

O

Q

E_g>U

o

"

£^

.et

of

d

be

chec

D

o

^

O

_c

.2

J-u

•*

•

D

•-

_*

w

O

o

spe

che

uire

°

O

°"

o

c

fi

.*

TJ

|J-8

5~S

O

Q,

«

ii

~

=>

O

u_

*-

Ecu)

0)

o

l

*-

.-

<_

UJ

«

3

O

-8

8-5

c

a)

.r

.-

_c

*-

o

*

•

M-

«

«*

•

°

4)

o

L.

«

_y

^

1

8

S

!

•

€

'5.^

<

E

«

.

o

>

c

O

<D

E

T>

0)

l£%

•

»-

C

*>

O

.-

_C

.

2

«

r

"O

*-

-a

x

4)

—

E

-o

to

4)

ggfi

4)

poP

o

-JZ

-

-*—

O

a*

o_

2

"*•

E

Z

L_

.«

D

E

?

*2

a>

t-

o

.-

J

I—

Q-

UJ

u

z

o

3

o

Z

z

o

1

-*-

4)

o

3

a.

2

o

J!

S

4)

JC

4)

-*—

U

o

u

o

J:

-8

c

o

I

c

o

c

4>

JC

o

2

.8

225

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)

Directorate

of

Systems

Design

&

Devefopment

Hq

Electronic

Systems

Division

L

G

Hanscom

Field,

Bedford,

Mass.

01730

2a.

REPORT

SECURITY

CLASSIFICATION

U

NC

LASSIF

I

ED

2b.

GROUP

N/A

3

REPORT

Tl

TLE

USER'S

MANUAL

JOVIAL

COMPILER

VALIDATION

SYSTEM

*

DESCRIPTIVE

NOTES

(Type

ot

report

and

Inclusive

dates)

None

V

AU

THORI3I

(First

name,

middle

Initial,

last

name)

None

6

REPORT

DA

TE

July

1970

/«.

TOTAL

NO.

OP

PAGES

234

7b.

NO.

OF

RE

FS

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

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

Navigation menu

Versions of this User Manual:

Views

Navigation