040

I-

. .

REPORT DOCIUMENTATION . * N. .-. S. Recipled. Acco I oe.

-PROGRAMMING SUPPORT JIBRARY (PSL), My 78

Operations Manual, i ..__ "" 2-A -d/7 - 5'-

7. "h ) f4 n Peefeim n aen len Rept. No.

9. Pe fe.nmlng Oonlastien Name afd Add~me 0. I V /Te&sk/Wek Uit N.

Federal Systems DivisionInternational Business Machines Corporation IL CO ,, X. Gtn(GN.Gaithersburg, Maryland !"F303-77-C-0249

IM senW Organization Name and Adeee I Tie t Reget Period Coverd

Rome Air DeVelopment CenterRADC/COEEGriffiss Air-Force Base, NY 13441

£Supplementary Note _~-

or magnetic tape, see fTphIe~ou c4' n t ~ deral a d re0

*ihe Programming Support Library (PSL) is a software system which providesthe tools to organize, implement, and control computer program develcp-ment. This involves the support of the actual programming process andalso the support of the manaqement process. The PSL is desiqned tosupport Top Down Design and Structured Programming (TDDSP).

IL The objective of the Operations Manual for the PSL is to provide computercontrol and computer operator personnel with a detailed operational.description of the system and its associated environment.

•,-a . -.- . 4-- ..

Software Configuration ControlStructured Programming Support ToolSoftware Development Support

8L. Gett~ Cutse (Thie Pawl J2.PH1NCT.ASSTITED

ee ANSI91S s eeqr elo en "WW e 4-pn

i DMA

Programming Support Library (PSL)

Operations Manual (FINAL)

I I

~I

Submitted to:

ARome Air Development Center

Griffiss Air Force Base, New York

I May 1978

I

j Under Contract F30602-77-C-0249

I

I Federal. Systems DivisionINTERNATIONAL BUSINESS MACHINES CORPORATIO - ,on ro-

Gaithe'rsburg, Maryland I. A-

I j.. _ . _---

... - . r --I

r 12

TABLE OF CONTENTS

SECTION PAGE

1 GENERAL DESCRIPTION 1-11.1 Purpose 1-1

1.2 System Application 1-2

1.3 System Operation 1-2

2 SYSTEM CONTROL 2-1

2.1 Control Requirements 2-1

2.2 Data Retention 2-2

3 OPERATING PROCEDURES 3-1

3.1 Equipment Configuration 3-1

3.2 Input Nedia3-3.3 Output 3-2

3.4 Procedures 3-3

4. NON-ROUTINE OPERATION 4-1

4.1 System Backup 4-1

4.2 System Restore 4-1

4.3 System Maintenance 4-1

LIST OF FIGURES

SF IGUREK PAGE

-1 BACKUP PROCEDURE 4-2

2 RESTORE PROCEDURE 4-3

3 STRUCTURED COBOL COMPILATION 4-5

4 PSL SYSTEM COLLECTION 4-6

I'I

SECTION 1. GENERAL DESCRIPTION11.1 Purpose of Computer Operation Manual

The objective of the Computer Operation Manual for theProgramming Support Library System, developed under contractnumber F30602-77-C-0249, is to provide computer control andcomputer operator personnel with a detailed operationaldescription of the system and its associated environment.

The manual is organized into four sections as follows:

a. SECTION 1 - GENERAL DESCRIPTION. This sectiondescribes the purpose and use of the PSL system; theoperation of the system, in regards to how thevarious operations are related; and the associatedinput data and output information for each operation.

b. SECTION 2 - SYSTEM CONTROL. This section presentsinformation on how the operations and environmentassociated with the system are controlled. It alsodescribes the responsibilities and interactions ofcontrol personnel in the scheduling of operations;assignment of equipment; and the management of inputdata, output data and other output information in anorderly way.

L c. SECTION 3 - OPERATING PROCEDURES. This sectiondescribes the procedures and material required toperform each of the individual operations of the PSL.This description will be illustrated by defining ahypothetical project and itemizing the logicalsequence of actions to be taken.

d. SECTION 4 - NON-ROUTINE OPERATIONS. This sectionprovides control information and operator proceduresto cover non-routine PSL operations.

'1

tI$ , N

1.2 System Application

The DMA PSL is a comprehensive system softvare package whichsupports the growth and maintenance of structured programmingprojects in a top-down development environment. The systemprovides:

a. A framework for the organization of a project.

b. Simple functional statements to interface betweenthe programmer and the machine.

C. Structural and statistical reports for control ofthe development process and for communicationbetween programmers.

The DMA PSL system provides special structured programmingsupport for the Structured COBOL and Structured FORTRANlanguages. However, unstructured program may also be storedand maintained under the system.

1.3 System Operation

The PSL is primarily a self-contained software system with mostfunctions being performed by programs contained within thesystem. The PSL does however, interface with several externalsupport programs as follows:

a. UNIVAC 1108 Executive System. The execution of the

P SL programs and the processing of Job ControlIL' statements stored in the library are controlled bythe Executive System.

b. File Control Processor. The reading and writing oflibrary data sections on the direct access storagedevice is supported by the File Control Processor.

C. Language Processors. Compiles the program source

language statements.

d. Collector. The collector is designed to provide theuser with the means of collecting and linkingrelocatable subprograms to produce an absoluteprogram in a form ready for execution under controlof the Executive System.

1-2

I'I

The PSL system in the batch mode is invoked by an ADD statementand is directed to perform specific functions by PSL Functioncards. The general functional capabilities available under thePSL are:

a. Initialize a project.

b. Create sections in a library.

c. Add, change, move, replace or purge a unit of code.

d. Print, punch or write (to tape) a unit of code.

e. Print an index listing.

f. Print the top-down structure of a program.

g. Compile, link, execute.

h. Delete a section, a library or a project.

i. Backup a project, library or section.

J. Restore a project, library or section.

k. Collect and print management data.

. 1. Print text data.

m. Print by author or character string.

The PSL is used to maintain the current status of all code inmachine readable form. The current status of the PSL includes,at the least, library sections which contain source and objectcode and control data. Other user generated data such asprogram design language statements, test data and textual datamay also be maintained in the PSL. It is also used to maintainthe current status and past history of all code generated in aproject in a human readable form. For human readability, thevarious types of source data, test data and control data sectionsare represented by listings of their members. The object codeis represented by the assembler/compiler listing produced whenthe object code was created.

A PSL library consists of one or more data sections. Thedefined sections are:

1-3

a. SOURCE - This section is used to store sourcestatements. It serves as input tothe precoinpilers during compilationof a program.

b. OBJECT - This section contains object moduleindexes and accounting records. Theobject code generated from a compile/assembly is located in the PROGRAMsection. (See k.)

c. LINK - This section is used to store controlstatements for combining one or moreobject and load modules recorded inthe OBJECT and LOAD sections into anexecutable load module. The resultingload module is recorded in the LOADsection and stored in the PROGRAMsection.

d. LOAD - This section contains load moduleindexes and accounting records.

e. PDL - This section is used to store ProgramDesign Language statements. Data fromthis section may be used for design orprogram documentation.

f. TEXT - This section is used to store anytextual type information. Data from

II this file may be used for various typesof program or system documentation.

g. JOB - This section is used to store jobcontrol statements which are used tocontrol execution of programs beingdeveloped and other programs used bythe programming project. Data fromthe section is used to build a jobstream for input to the computer.

h. TEST - This section is used to store data tobe used in testing programs underdevelopment or maintenance.

i. MGMT - This section is used to store manage-ment data to be used in producingmanagement data reports.

1-4

LI

I

J. USER This section contains data generatedby non-PSL functions.

k. PROGRAM This section contains all object andload modules (relocatable andabsolute elements).

The PSL system manipulates the data for each system appropriatelyfor that type of section.

Data is stored in the various library sections in the form ofunits. A unit is composed of one or more lines of data (a lineis equivalent to seventy-two characters of data plus sequencenumber) except in the case of object and load modules, text data,and when the data compaction option is being used. Compacteddata consists of variable length records. Object and load modulesare generated by system facilities and stored automatically. Allother data units are user generated and stored as a result of auser PSL update run.

The Batch Control Function, BCTL, provides control for the PSLin a batch environment. Its primary functions are:

a. Process the input card.

b. Perform job request verification.

c. Call the program to be executed, passing controlinformation entered via the control card to theprogram.

BCTL is loaded into core storage from the computer's systemresident file and executed when a PSL job is initiated by a jobcontrol statement. As PSL control cards are read, BCTL processesthe input card and passes control to one of the functionalprocessors. When a functional processor completes its processing,

* control is returned to BCTL. The Batch Control Function continuesto load control cards and execute functional processors until ang end-of-file condition is encountered.

The BCTL FuAction uses the first parameter on the PSL controlcard to determine which functional processor to execute. It isthe function of each processor to check for its required keywordparameters.

1-5

III

SECTION 2. SYSTEM CONTROL

2.1 Control Requirements

The PSL is a repository for the storing of data created duringthe development of computer programs. The data repository isin two forms: data stored in machine readable form accessibleby the computer and identical data stored in hard copy form inproject notebooks. The necessary computer and office proceduresfor manipulation of this data is also included as a part of thetotal PSL system. The purpose of the PSL is to support theprogram development process. This involves the support of theactual programming process and the management of the programmingprocess. Participation by management, programmers and librarianis required to effectively utilize the capabilities of the totalsystem.

The programming project manager is responsible for defining andmonitoring a set of office procedures and computer proceduresused to control the PSL library. Detailed instructions fortheir use and for preparing inputs and outputs must be provided.

The contents of the PSL are maintained by a programming librarianand determined by programmer. Except for normal housekeepingfunctions, clerical operations are to be carried Out in the PSL

only on the direct request of the programmers. Under suchdirection, the programmer librarian carries out any of theoperations in the PSL without assistance or direct supervision.Directions from programmers to the programming librarian maycome through marked up members, original code sheets or notationson directories. If a programming librarian is not used, anappropriate standard set of machine and office procedures shouldbe employed by the programmers.

The management process consists of the following four basicfunctions:

a. Planning. The Function of determining the projectobjectives and the policies, programs, procedures andmethods for achieving them. The planning must provideIa framework for decision making.

b. Organizing. The Function of determining the activitiesrequired to achieve the objectives of a programmingproject, the departmentation of these activities andthe assignment of authority and responsibility fortheir performance.

2-1

* 1r -

c. Control. The Function of assuring that the variouscomponents of a project are performing in accordancewith the plan. Control is essentially the measure-ment and modification (if necessary) of componentactivities to assure the accomplishment of theoverall plan.

d. Communications. The Function of transferring infor-mation among decision makers throughout the project.

The PSL may be used to support the management of the programmingprocess by providing a means to:

" Collect and report management data related toprogram development.

" Control the integrity and security of the datastored in the PSL.

* Separate the clerical activity related to theprogramming process.

The management statistical data stored in the PSL should bemaintained by a programming librarian under the supervision ofproject management. Except for normal housekeeping functions,clerical operations for the maintenance and reporting ofmanagement statistical data should be carried out in the PSLonly on the direct request of managers or on a previously

defined management approved request procedure.

2.2 Data Retention

An external library consisting of a set of current statusnotebooks, archives and run notebooks which reflect the contentsof the internal PSL library and provide a history of theprogramming project should be maintained as an integral part ofthe total development process. For each internal file maintainedby the PSL system there should be a corresponding external filein the form of printed listings stored in notebooks or binders.

Each of the external libraries should also contain a directory(list of unit names) and a control listing related to theI physical attribute of the file. The contents are filed inalphabeticall sequence by unit name with the directory and controllisting preceding the unit listing.

2-2

Archives are maintained for each of the current status note-books. These provide a history of the development process, abasic backup and management control of resources. Eacharchive is a chronological collection of old listings for anotebook.

A Housekeeping archive and a General archive are alsomaintained. The Housekeeping binder contains output from thePSL system maintenance functions (See Section 4) and is filedin chronological sequence. The General archive contains anyoutput which is not filed in one of the other archives. itis also maintained in chronological order.

The length of time for which material is maintained in eacharchive is a project-dependent consideration.

Run notebooks contain the output from executions of systemtest runs. The run notebook provides a chronological historyof the execution status of the modules it represents. Thenumber of different run books kept is a project-dependentconsideration.

2-3

SECTION 3. OPERATING PROCEDURES

3.1 Equipment Configuration

The PSL system operates on a Sperry Univac 1100 series computer

under the EXEC 8 Operating System using a standard DMA software

and hardware configuration. Libraries are maintained on direct

access storage devices. The system utilizes the standard cardreader and printer, one tape drive, and approximately 43K wordsof core.

The PSL system utilizes the File Control Processor todynamically create, allocate, deallocate and purge file storagespace. Interface with the File Control Processor is madethrough the Executive Request command using the Univac AssemblyProgram Language.

3.2 Input

The input to the PSL system consists of directives on cards(PSL Function cards) and data from the user's libraries. A PSLdirective which is submitted as a batch-input data card via thecard reader or as terminal input, contains the name of thefunction requested and, if appropriate, sets of keywords andvalue entries. The user's own program and data cards may beinterspersed with the PSL Function cards.

The format of the input card is:

** function keyword-parameterkeyword-parameter,...

where

** - Present in positions 1 and 2 andfollowed by one or more blanks.These characters identify all PSLcontrol cards.

Ifunction - Must be present and followed by oneor more blanks. This entry definesthe particular PSL function orsubfunction to be performed.

keyword-parameter - Additional control informationrelated to the function performed.Multiple keyword parameters areseparated by commas and may occur inany order. The keyword parameters

3-1

• I I

are defined in the descriptions ofthe PSL function processors. The

format of a keyword parameter is

Keyword-value

The entire KEYWORD need not bespecified. Only those charactersneeded to distinguish between key-words are required.

If the keyword parameters will not fit on a single punchedcard, continuation cards are permitted. Continuation cardsare identified as follows:

a. The control card preceding the continuation cardmust contain a comma as the last character on thecard.

b. A continuation card must contain a ** in columns 1and 2 followed by one or more blanks and theadditional. keyword parameters. The keywordparameters are formatted exactly as on the standardPSL control card.

When a required keyword parameter is missing or in error, theprocessing for that function is terminated with an errormessage. Normal processing is continued for any additionalfunctions requested.

3.3 Output

The output of the PSL system consists mainly of user data which

are stored according to data format in pre-defined files (PSLsections), and management data reports.

The Output Processing functions (Section 3.1.5, PSL Users Manual)provide the facility to output data stored in the PSL library.First, the PRINT INDEX Function provides a control listingwhich reports on the status of each section. Informationrelated to physical storage including storage space allocatedand used, ty'pe of storage'unit, data identification and similartype information is included. Next, the PRINT SOURCE Function

provides either a listing, tape or card deck for either asingle unit or each unit in a section'. The PRINT AUTHOR

Function provides the capability to list the name of each unitin a section generated by a specific programmer. The PRINT

3-2

DOCUMENT Function prints document text incorporating card-image

unit stored in PSL sections. The SCAN STRING Function provides

the capability to scan for and list each appearance of a

specified character string in a section.

In addition to the above functions, a unit listing is producedautomatically each time a unit of code is either added orupdated within the SOURCE, JOB, TEST, MANAGEMENT, TEXT and PDLsections. Units added to either the SOURCE or PDL sectionswill be listed with indentation, if appropriate.

Manaqqment data reports print the contents of one or moremanagement data units in a pre-defined report format. Manage-

ment data units may contain a combination of automaticallycollected data and manually input data combined according tothe specifications in an associated user-defined format unit.

The Management Data Report Function allows the user to requestthe generation of reports containing management information onactive programming projects or historical programming projects.All reports are produced upon request. The makeup of theselected set of reports, variances between data items (ExceptionChecking), and the reporting cycle are determined by the projectpersonnel.

3.4 Procedures

The following is an example of how the PSL may be used to developa segment of code by an individual programmer. These proceduresmay be extended to encompass the development of an entire systemby many programmers.

A description of the operation (PSL Function) to be performed isgiven, followed by a sample of the input needed to implementeach operation.

3-3

-

0 a

E-4E-4 0

0 > z

W C

-4CzE-4

Z oo

.04.

,-4C

r>4 U >14 4 w

En m0

:3 M E-4Cd 1-4 f -4U2

~~E-1

41 -1 -,S dE- -

-%- 4 -4H-40w

A 0n E- r

w- '--4E4 -

V) 0 E-4 E-491.z~ 2 Enu 00 P4

-x Cl u n T 4

co c!3-Z

E-4

-44

0- 0 -

2-.4H 0 z- 1-i

E-4 W 0

w -C W -U &4aw*** .14 0- -4 21-

C13z E-4 0

I1-4 0

0 pz

-H 0 " -4H u-4

94'- H 41

:11- I414 0 4PIn p9 4~ = d 1-4 9.)c:1 14 = 02 a-. toZ0

4 ) u 0 Pr.a ..

4) 91) 14>I> IQ IA I P Zp -Q)UI' mJ)4 adWw 40

n P E-4 -4-4 40 1-4 p -~4 E-4U r0

1 Cz1hz x0 c000w 0 014 >4 f0.4 H)s w~40u14 ma caatl za E-4 0OU3 O2

41 F4O02fU 00O000 O E-4 Z X* z Con0 m awU)U) ( 00 0 w a 4 >4 4C O3

-$a.~ Z CA U 0O4 4 noU HaH ) E- -caA 4 U -Q = 4 A 4 0 4 W 4 A

ca r.t I - 1 014= Nn E4 H i

4)-zH

H C641 a

4-4

hii1-4

r. 94 0

0 1 4-PCZ4 > En

to0 H H{n z. *4 >tI 0 0 0

Kz-4 (n tA z =P4 w0) Z 6 - b -

0 0) :: 04 0

1-4 )P "- 0 tP4 :tPLA H4 0 ci)od w .z H I I > 0 H I

11-4 >4 -4 0 : H .C , z a *r.- 0 0l 04 0-P 0 w&Ci tn C

Z WH ~ 1-4 1-4 1-4 H E-4 iHA 1-2--

EnZ z 1- 4 1- 4 H 1- 4 P4 5-:: ) a w000. 0) O 5- 4 z - - > E- -4 E '4-4 -I E-1 P4

U)U)H 0. H 'o~-~.4~ 01-J ~ ~ ~ ~ -H 0 z z 4 =OI 4 P -

_ ) H 1-4 g4 g in 14 0 E, Hk 0 -

0.. 1. A > .I05-41M) u z u 0-4 H I

4 1 * .rl " N 1 . Hz0 z z 9 0 C A P 4 E -

) *.4 ~ 0 U). . P. H- a

0

Itt

3-6

1-4

-4

0

0 03 -

I.4

'-4

>4 u

(14 a o

A H

P:. -4 020E- 24 .. J T

u-4 E- 4

>H 0 U 0 A E4

~~~;4 (Ufl -

~ U0'-4U240 fz E-4~x H

09 0 1 z 0CUH4~4 1- > 4

A4~~ -C4 W01- CE4 -E-4 A 4P 1 A Q

1-'4 0 -4 E-4 t, K-.)- 0- o 0 . r

.~z 4e.4H 04iJ pCA

U>.4 H L) C p. .4 U W 4P4 04 U-i pa4 0v

.~. Vz w~~ pi~) 3 V

> 3-7

1*'0 Z *4 P U

0

E-4

p pE- HL

Co E-

H ~ 0 4

0z

W Uw E-4 - 4 C-

44 w Ldod -

44 ve 0Z L)PL

4'

a 0 0Q

0 >r0) 0 - -

I, gcn

0 :3

0 OH H4

-4 t4H

0. 41 :j CZ -

0 '40ki0f

0- al w H

04 c 0 0 d

&1 4)* 2Z H

if 00 , ~ Oi0l 1 0

toiG 00 w4f r.2 (A 94 ,

00 wo t4U u~ U 0a'

o vG s-a4 E4O ~ o -

qc 4'I'MZ.U.4-OH4 H HP.-

-T4 'C .661. :,

041 )c)1 4 9 94 CW Q1

.1-

H

z -4

I-4

CI 0 z 9

H ry z 0 0

0 Pd z X-r 1-4 -c w H

C: 4 u*J CL

H 4z~ E-4 H-

0~ ~ 4 0)~4 0 4.4=

E- 0 0 C) -C04 4 W#- -j w E40EH 0~ m XZ 4 Z

E-V 4

Z-4~

41 w

z. CAlH H t

C'" -Zif z-4'. .i 0,-4HH~-4,~E-..

H.0 H P~ ~-

4 ~L- E4 - Z ~

tnz 4 4 - -4 4E4-

E-4O'4 ")~~4- z AZO'4 -4 H zA4 C/ 0 0Z ^ p 0N 44 Q 9=

UA 0--e'. Z ad K4 0 K 0 I = . a

1- 4 IO. p1- 41- H E- 0 z394.

0 I 4w F c ..L41 F -l H 4 z QC

z

z H

> z

W - H En r

41 1n H

E-4 .)

H4 0

r. 40 C3 - 0

CfHOOH wI a4 z

4-4 i 40~ -414 -

14 0 - 4I0 N 1-4 Z 114 z

;r. 0 u H -0 x H W -4P

0 1 Z 4 4

0~ 10C~- OCA4 wH~ W4 Hz x u

0 4HM x ZZ H II 4

< ~H C".)OP

:D tA V Hza H

w, < # t,*4%44 4t 4 t i(2 4c -it O 4 -~Cx.-

1.4 HOH4O3HH10

SECTION 4. NON-ROUTINE OPERATIONS

The entire PSL system in source, relocatable and absolute form is containedin a single program file named DMA*PSLPRG. This file contains the sourcecode, acceptance test and installation test data, JCL used to maintain andexecute the PSL system plus an independently executable COBOL Precompiler.The program file is normally kept only on tape and is restored onlywhen modifications are to be made to the system. This file is normallyreferred to by the use relationship PSLPRG.

The installed version or 'floor' version of PSL uses the program file-DMA*PSL. to contain the absolute form of the PSL system. In additionthere are four related files which complete the floor version of PSL.These are:

DMA*XPROJECT.DMA*JPSL.DMA*SPSL.DMA*PSL-STUB.

These files, used by the PSL-system to support spawned job operationswere generated using the facilities of the BCTL 'nodule. The floorversion of PSL is normally referred to by the USE relationship PSL.

This section details the following Thr-routine operations:

a. System Backupb. System Restorec. System Maintenance

4.1 System Backup

The PSL system is backed up onto tape by using the Univac 1100 seriesFile Utility Routine and Program File Utility Routine (FURPUR). @COPY,Cmcommands are used to copy the PSL files to tape (see Figure 1).

4.2 System Restore

Similarly, @COPY command can be used to restore the PSL system fromtape (see Figure 2).

4.3 System Maintenance

If it becomes necessary to modify PSL code or add new modules, theprogram file DMA*PSLPRG must be restored from tape. The @COPYcommand can be used to create a working copy ot the PSL system under anew Project ID normally a working file called DMA*PSL:IODS is allocatedto contain a version of the PSL system. This file is referred to bythe USE relationship M. in the JCL contained in DA*PSLPRG. Correctionsare thn made using the Univac 1100 or University of Maryland editor.The majortv of the PSL modules are written in Structured COBOL,and thost,. modules must be

4-I

m U__

0RUN <RUN ID>, <ACCOUNT-t>, <PROJECT ID>

V JIASG,CP SAVFJ*PSL. ,U9V,<rcel-number>

OASG,CP DNMPSLPRG.

I :,\SG,,% DMA*PSL.

~ASCADMA*XPROJECT.

I. :A'GADAMN'SPSL.

A ~ DiMPSL-STUB.

IJCOPly,GM DMA*PSLPRC. ,SAVE*PSL.

COPY, CN DMA~pSi- ,SAVI-.PSI,.

t COly ,G' DXMA*PROJECT. , SAVE11S L.

@COPY,Gm I)MA*JPSL. ,SAVE*:PSl..

(')OPY ,G'M DMALSPSL. ,SAVE*PS1..

Iocopy, Cm 1)MNA*PS L-STrUI. , SAVL:*PS..

OFI

FIGURE 1. BACKUP PROCEDURE

4-2

LIRUN <rni><con-><rjc-d

0ASG,A SAVE:*PSL. ,U9V,<reel-number>

@ASG,A DMA*PSLPRG.

[ @ASGA DMA*PSL.

OASG,A DM.%*XPROJECT.

ICASG,A\ DA.PL

@ASG,A\ DMA*SPSL.

L2ASG,,\ DNA\PSL-STUB.

I QCOI'YG SAVE*PSL. ,DMA*PSLPRG.

@COPY ,G SAV17*PSL. , DlNUPSL.

I@COPY,G SAVE*PSL.,M*P0ET

OCOPY * SA\Vl:),IISL. DM-NAJPSL,

COlPy, SAVE*PSL. ,DNIA*SPSL.

OCOPY ,G SzVE7PSL. ,'l,%*PSl-S'lUB.

FIGURE 2. RESTORE PROCEDURE

4 -3

precompiled as shown in Figure 3. After the changed modules have been

recompiled, the system must be collected. The collector control cards

are stored in PSLPRG.BCTLNAP. If new modules have been added to the

system, the elements must be listed in PSLPRG.BCTLMAP. The system can

then be collected (see Figure 4). It is recommended thst both the new

PSL and the new PSLPRG be backed up onto tape.

I4I I

I

I

4-4

k~i i

@RUN -

@ASG,A DMA*PSLPRG.

@USE PSLPRG.,DMA*PSLPRG.

@ASG,T PR,F///I

@ASG,T PI,F///100 Temporary Files required by

the COBOL Precompiler

@ASG,T PO,F///100

@ASG,T LS,F///100

@DATA,I PI.

@ADD,D PSLPRG. <element name> Precompile Input

N IFile

@XQT PSLPRG.PRECOMPILER

@ACOB,ITVSEC mTPP$,PSLPRG PSLPRG <element name>

@ADD PO. }Precompiler Output File@EOF

@FINwhere:

T Reverses display meaning defaul' fieldataV = Subproblem

S = Source list of

PC = Output all diagnosticsC = List library text

M = Suppress the COBOL monitor option

- Z = compile debug on<element name> = name of element to be changed

FIGURE 3. STRUCTURED COBOL COMPILATION

4-5

I

f

I.

@RUN --

@ASG,A DMA*PSLNODS.

@USE M., DMA*PSLMODS.

@MAP PSLPRG.BCTLMAP, M .BCTL MAP options may be used

@EOF (Except I option)

i

I. I

L

FIGURE 4. PSL SYSTEM COLLECTION

I4-6

it