ML20202B113

Nonproprietary Suppl 1,Rev 3, CPC Protection Algorithm Software Change Procedure

ML20202B113
Person / Time
Site:	Arkansas Nuclear
Issue date:	04/30/1986
From:	ABB COMBUSTION ENGINEERING NUCLEAR FUEL (FORMERLY
To:
Shared Package
ML19298D851	List: LD-86-022, Forwards Proprietary Suppl 1,Rev 3 to CEN-39(A)-P & Nonproprietary Suppl 1,Rev 3 to CEN-39(A)-NP, CPC Protection Algorithm Software Change Procedure. Affidavit Encl.Proprietary Rept Withheld (Ref 10CFR2.790).Fee Paid ML20202B113
References
CEN-39(A)-NP, CEN-39(A)-NP-S01-R03, CEN-39(A)-NP-S1-R3, NUDOCS 8604110132
Download: ML20202B113 (97)

Text

ARKANSAS NUCLEAR ONE - UNIT 2 DOCKET 50-368 CEN-39(A)-NP e

SUPPLEMENT 1-NP l '

REVISION OSNP CPC PROTECTION ALG0RITHM SOFTWARE CHANGE PROCEDURE SUPPLEMENT APRIL , 1986 Combustion Engineering, Inc.

Nuclear Power Systems Power Systems Group Windsor, Connecticut e

Revision 03 R604110132 860408 PDR ADOCK 05000368 P PDR

ARKANSAS NUCLEAR ONE - UNIT 2 DOCKET 50-368 CEN-39(A)-NP e

SUPPLEMENT 1-NP REVISION 03 NP ,

CPC PROTECTION ALGORITHM SOFTWARE CHANGE PROCEDURE SUPPLEMENT APRIL, 1986 Combustion Engineering,'Inc. -

Nuclear Power Systems Power Systems Group Windsor, Connecticut L

Revision 03 O

. TABLE OF CONTENTS Section Title Page No.

1.0 IMPLEMENTATION OF SOFTWARE CHANGES 6 1.1 PURPOSE 6

1.2 REFERENCES

6

, 1.3 IMPLEMENTATION OF AN SCR 7 1.3.1 Preparation of Software Change Package 7 1.3.2 Design of Software Changes 7 1.3.3 coding of software Changes 9

1.3.4 Implementation and Assembly of Software Changes 10 1.3.5 Debug of Software Changes 11 1.3.6 Quality Assurance of software Changes 11 1.4 QUALITY ASSURED OBJECT DISK GENERATION PROCEDURE 21 1.4.1 Input 21 1.4.2 Output 21 1.4.3 Procedures 22 1.4.4 Generation of Master Test Disk 23 1.4.5 Generation of Disks for On-Line Operation ,

24 1.5 CONTROL OF QUALITY RECORDS 47 2.0 PROJECT DISK GENERATION PROCEDURE 94

! 2.1 PURPOSE 94 l 2.2 REFERENCES 94 2.3 PROJECT DISK GENERATION 94 LIST OF APPENDICES Appendix Title Page No.

lA Software Organization and Design Considerations 48 18 Command Substitution System Files 58

. 1C Source Updater Commands 69 10 Automated CPC Integration 74 1E Periodic Test Disk Generation 85

, 2A Project Disk Generation 96 J

I Revision 03 Page 3 of 97

a- - -- - -

TABLE OF CONTENTS (Cont.)

LIST OF FIGURES Figure Title Page No.

1.3-1 Change Applicability Form 15

. 1.4-1 Data Flow for Disk Generation, Software 25 Development System 1.4-2 CPC Disk Generation Log 26

, 1.4-3 CPC System 37 J 1.4-4 CEAC System 40 1,4-5 CPC Test System 42 1.4-6 -

CPC Files 44 l 1A-1 CPC Program Title Block 57 l

LIST OF TABLES 4

Table Title Page No.

1.3-1 Core Protection Calculator. System 16

LIST OF ATTACHMENTS l Attachment Ti tle Page No.

1.3-1 CPC Source Update Checklist 13 1.4-1 CPC Intermediate Disk Generation 30 1.4-2 CPC Reference Disk Generation 32 1.4-3 CPC Load and Test Disk Generation 36 2.3-1 'CPC Project Disk Generation Checklist 95 i

. Revision 03 Page 4 of 97

1 ABSTRACT l

This document presents procedures to be followed during the process of implementation of modifications to the CPC/CEAC software for all CPC systems utilizing the INTERDATA (Perkin-Elmer, Concurrent) minicomputer.

l Additionally, this document presents procedures to be followed during the

, process of generating CPC/CEAC software for application to a new project for these same CPC systems. Section 1.0 of this document contains procedures describing the process of implementing changes to the CPC System software and data base. Section 2.0 contains procedures applicable to the process of generatingnewprojectsoftware.([

l e

I 1

Revision 03 Page 5 of 97

_______ A

1.0 IMPLEMENTATION OF SOFTWARE CHANGES-1.1 PURPOSE 1

The purpose of Section 1.0 is to present the procedures required to j implement a design modification to the CPC/CEAC software system.

Adherence to this procedure is intended to avoid the introduction of errors during the revision of a quality assured software system.

1.2 REFERENCES

1.2.1 Software Change Procedure for CPC/CEAC Protection Algorithms, CEN-39-P, Rev. 03.

1.2.2 Quality Assurance of Design Manual for C-E Nuclear Power Systems l .

1.2.3 CPC Disk Utility Program (DSKUTL) User's Manual.

1.2.4 0S/32 System Support Utilities Reference Manual, Perkin Elmer, Inc.,

a Publication Number 48-031.

~

1.2.S L. .

1.2.6 Perkin-Elemer Common Assembly Language,48-050.

~

Revision 03 Page 6 of 97

_ L '

_ _ _ . -- .m . _ _ . _ .-. ._ _ _ . - . _ . _ . _ _ . _ _ _ _ . _ _ _ .

I

.1.2.7 0516 Operator's Manual Publication Number 29-430.

l I 1.3 IMPLEMENTATION OF AN SCR i

i

! 1.3.1 Preparation of Software Change Package

{.

I, When an SCR is ready for implementation, the implementor will i

prepare the Software Change Package by filling out and attaching a l Change Applicability fonn (Figure 1.3-1) for each plant to which the i

SCR is applied. Table 1.3-1 lists all elements of the software system. The implementor must list those items which are affected by ,

l the SCR on the Change Applicability form and must date and initial 1

i each item when the required changes are completed.

I l ,

j If the implementor determines that additional informatfor is i required, he will contact the originator to obtain the required j .

clarification. All pertinent information received verbally will be ,

recorded on the SCR and dated and initialed by the originator.

i

?

1.3.2 Design of Software Changes i

l After preparing the Software Change Package, the engineer will

.i

. design and implement the required change as follows

i t 4 1 l

l i ,

i I Revision 03 Page 7 of 97

1) The most recent working copy of the affected calculation descriptions, flowcharts, input / output lists, variable lists, cross reference lists, and constant lists of the System Software Specification will be marked up to reflect the change and initialed by the engineer.

, 2) The required coding changes will be marked on the most recent ,

working copy of the assembly listings. To ensure that the -

listings being used are the latest version, the date and time on the listing will be checked against the latest date and time l

I posted for that listing in the automated CPC log file ,

CPCL OG.DAT. Also, when a new listing is created, the previous version of the listing will be marked " superseded."

l 3) The Phase I Test Cases will be modified as required to meet the 4

recuirements of Reference 1.2.1.

i l

l 4) If the change affects scaled-fixed-point coding, the i

appropriate scaling recorded calculations will be revised '

accordingly.

The software change will be designed to be consistent with Appendix

. 1A of this document entitled " Software Organization and Design Considerations".

i 1

4 Revis.fon 03 Page 8 of 97 .

I

. The software change will then be incorporated in a specification revision. The revised software design will then be independently reviewed in accordance with Reference 1.2.2.

1.3.3 Coding of Sof tware Changes The CPC Source Update Checklist (Attachment 1.3-1) outlines the procedure to be used in the coding, implementation and assembly of software changes. The required coding changes, as marked on the assembly listings, will be converted.into a series of Source Updater Utility program commands (Appendix IC) and an 80/ byte record file created using ascending sequence numbers. The last record in the file must be the "ENDUP". In the course of coding the changes, the following documentation will be performed.

1) A. revision to CPC software consists of one or more SCR's.

In the initial updating of a source file during a revision, the revision number of the source file is incremented by 1.00 and the decimal part of the number is reset to .00. In the implementation of subsequent SCR's within this revision, which result in another'updatingaof this source file, the revision j

, number of the source file is incremented by 0.01.

1 Revision 03 Page 9 of 97

c 4

, L j /

. 2) An "SCR Implementation' Record" line will be inserted into the -

i

source file. This line is a coment of the form:

• REV n.nn, SCRs: f, j ,' k , .

.f i

where: n.nn is the new revision number i, j, k are SCR numbers imple:nented in this revision.

g

! These lines will never be removed from the file and will thus i'

provide a running account of the SCRs implemented in a partic-ular program.

l 1.3.4 Implementation and Assembly of Software Changes i

The softwdre change will be implemented in the appropriate source <

t file using the UPDATE or the RESEQCPC comands (Appendix 18). The l appropriate project disk is marked ons.- The Source Update comand

~

l file is then invoked by' entering the UPDATE or RESEQCPC command on

{ the console. After successful termination of the procedure, the i Source Update comand listing will be attached to the software .

! change package. '

i g

i Should a new source file be required as a result of the implementa-l tion of an SCR, the INITIAL comand!(Appendix 18) will be used. The

, procedure for using, the INITIAL comand is the same as the Source Update procedure,with the following exceptions. "TNITIAL" is

~

entered instead of " UPDATE" and; a so0rce file replaces the Source

)

Updater comand file. ,

Revision 03 Page 10 of 97 .

I

. 1.3.5 Debuo of Software Changes i

To complete a Software Change Package and the implementation of an SCR, the implementor will fully test the generated obje-t module (s).

If a program error is detected during debug it will be corrected and i all affected documentation', including the software change package,

,, will be modified as required. The revision level, however, will not be incremented for changes to correct errors in the SCR

implementation uncovered during debug testing.

If a program error is detected during Phase I Testing it will be

] ,

corrected and all affected documentation, including the software change package, will be modified as required. The revision level of the program will be incremented by .01 prior to re-testing.

When the object module has been fully tested, the implementor will j complete the change package by attaching any debug test cases generated, filling in the applicable columns in the Change l

Applicability Form and initieling and dating the SCR.

i j 1.3.6 Ouality Assurance of Software Changes 4

. The Software Change Package will be maintained by the implementor until the change has been implemented and tested. The package will i' then be transmitted to the functional desion group and other appropriate design groups for the review of the implementation to

}

1 Revision 03 Page 11 of 97

verify correct interpretation of the SCR. Signatures of the "Impl.

Reviewed by" and "Other Reviewer (as appropriate)" will indicate the approval of the implementation.

The Software Change Package transmitted shall contain the annotated SCR, revised flow charts, Change Applicability Form, and details of

, the implementation necessary for clarification.

Upon completion of the reviews, the functional design group will resolve comments by reviewers and will transmit the package to the cognizant software design group engineer who will then file the ,

Software Change Package in the CPC design file.

Revision 03 Page 12 of 97 I

. Attachment 1.3-1 CPC Source Update Checklist

1) Create the Source Update command file a) Increment revision level on " PROG" record >

b) Add "SCR Implementation Record" line c) Place commands in order of ascending sequence numbers d) "ENDUP" record is the last record in the connand file

2) Mark on the appropriate portion of the CPC disk MARK disk:,0N, R = acct, CD = ALL where disk is the name of the project disk, acct is the account number of the project.

3) Enter UPDATE (project. volume name), (file name), (rev. #), (initial) a) If error occurs in execution of Source Updater commands, enter

$ CLEAR; CANCEL. The run is aborted. Correct the file and repeat this step.

4) Debug the software change

, 5) Attach the Source Updater command listings to the software change package Revision 03 Page 13 of 97

. l l

\

l

. Attachment 1.3-1 (Cont.) l CPC Source Update Checklist i i

1 l

6) Initial and date the appropriate columns in the Change Applicability Form (Figure 1.3-1)

7) Initial and date the SCR Log i

.i I.

i i

')

4

• r f

i

. Revision 03 ,

Page 14 of 97

Figure 1.3-1

!Peet of CHANGE APPLICABIL *Y CORP SC28:

CPC SYSTEM Date:

Plant:

, initials:

Caange Caspietion Qate ana Initials 4 oiicani. -

sar war it ust$n, s=ce. coa.cs so.ct rication l

i Revision 03 Page 15 of 97

4 Table 1.3-1 CORE PROTECTION CALCULATOR SYSTEM ho.

Software Item 1

! 2

! 3 4 .

5 6

7 8

l 9

l 10 11

~

12 13 Revision 03_ Page 16 of 97

J Table 1.3-1 (Cont.)

i CORE PROTECTION CALCULATOR SYSTEM i

l No. Software Item

~

i Data Base (cont.)

14 15 16 17 ,

18 19 20 21 22 23 24 25 .

26 27 28

. 29 t

, Revision 03 Page 17 of 97

Table 1.3-1 (Cont.)

CORE PROTECTION CALCULATOR SYSTEM No. Software Item O

30 31 32 33 ,

34 35 36 1

37 38

- 39 40 i

41 i

Revision 03 Page.18 of 97

Table 1.3-1 (Cont.)

CORE PROTECTION CALCULATOR SYSTEM h Software Item F-I i

42 43 44 45 ,

46 47 48 49 50 51 52 53

< Revision 03 Page 19 of 97-I

Table 1.3-1 (Cont.)

CORE PROTECTION CALCULATOR SYSTEM No. Software Item 54 55

~

56 57 ,

58 59 60 61 62 d gi O

t Revision 03 Page 20 of 97

1.4 QUALITY ASSURED OBJECT DISK GENERATION PROCEDURE This procedure applies to the integration of object modules and.the generation of load modules on disks. Portions of this procedure have been automated as described below. Details of the automated aspects are outlined in Appendix 1D.

1.4.1 Input The input to this procedure shall be from two sources:

1) Revised (i.e. newly assembled) object code.

2) Quality Assured object code from a previously generated and tested reference disk.

1.4.2 Output The output of this procedure shall be a memory image load module on disk. The load module shall be tested as required by Reference 1.2.1.

- Revision 03 . Page 21 of-97 e - g- v. - y: --g---w- =w /-. y--ray  !-- - m-

1.4.3 Procedures The memory image load module will be written to disk in 4 KB blocks.

Each block will occupy one disk track. A disk track may be generated entirely from revised object code, copied entirely from the reference disk, or copied from the reference disk with a revised object overlay.

The CPC Intermediate Disk Generation procedure (Attachment 1.4-1) is used to create an absolute load module on an intermediate Perkin-Elmer disk. .

The CPC Reference Disk Generation procedure (Attachment 1.4-2) is used to create a reference disk from a previous reference disk on an intermediate Perkin-Elmer disk.

Figure 1.4-1 shows the data flow for disk generation. The following paragraphs describe the processes involved in this figure. All tracks of a new disk will be initialized to all binary zeroes before any programs are written to the disk.

Source files shall be modified and assembled on the Software

. Development System (Perkin-Elmer 32-bit minicomputer) according to the procedures described in Section 1.3 of this document to produce

~

one ob.iect module per source file on.a project disk. The object modules will be combined to form load modules by a task image Revision 03 Page 22 of 97

l generator (currently TET). These load modules will be built to a Perkin-Elmer intermediate disk and then will be copied from the Perkin-Elmer disk to a site disk on the CPC single channel using a special disk utility DSKUTL according to the CPC Disk Generation Procedure.

4

).

All disk generations must be logged on the Disk Generation Log (or directory) (Figure 1.4-2) associated with each disk. ,

All programs and overlays must undergo Phase I and Phase II testing in accordance with Reference 1.2.1 of this document after being .

written to disk. A disk which has successfully undergone all l testing required by the above reference shall become the new reference disk for the software system.

1.4.4 Generation of Master Test Disk Once a reference disk has been established for the software system a master test disk may be generated. This is accomplished by restoring the project backup to disk and re-assembling the source files for the system to generate new object modules. The details of this procedure are outlined in Appendix 1E. An entire system load a module will be generated from these object modules and written to i

disk using the Periodic Test Disk Generation Procedure (Appendix IE).

Revision 03 Page 23 of 97

-~ _. --__._. _, __ _ .-_.._. _ _ . _ _ _ . . .

When all of the tracks of the test disk have been generated, the master test disk will be compared to the reference disk using the verify feature of the CPC Disk Utility Program, DSKUTL.

If differences are encountered the error in the test disk will be determined using the verify option of DSKUTL (Reference 1.2.3). The error will be corrected and the faulty disk will be regenerated in accordance with all- applicable procedures for test disk generation and testing.

1.4.5 Generation of Disks for On-Line Operation ,

Disks for shipment to customer sites for on-line operation will be generated using the duplicate and verify features of DSKUTL (Reference 1.2.3). These disks will be duplicated from the system reference disk which will be maintained by the Software Design group. The test disks will be similarly generated by duplicating the master test disk generated above. The master test disk will be

maintained by the Software Design group. The procedure for duplicating a disk is found in Attachment 1.4-3.

O Revision 03 Page 24 of 97

FIGURE 1.4-1 DATA FLOW FOR DISK GENERATION SOFTWARE DEVELOPMENT SYSTEM i

i

'~J ~.

. SOURCE m CAL m F ASSEMBLER 5 0BJECT FILES

- MODULES

. ./

O' '

/ .CD

/

J /

/

/ .

32-BIT DEVELOPt1ENT SYSTEM OBJ CT ' TASK ESTABLISHER &

l MODULES p

/

c == /

/

/

/

/

/

/

f CPC SUPPORT SYSTEM N

LOAD NEW

> DSKUTL > REFERENCEl py

. MODULES DISC OLD REFEREl4CE DISC Revision 03 Page 25 of 97  ;

l

Figure 1.4-2 CPC Disk Generation Log Track Software Revision Date Engineer 0

1 2

3 4

5 6

7 8

l 9

10 11- ,

12 i

13 14

. 15 16 17 18 Revision 03 Page 26 of 97

- - - - - . . , - , - - e.-, .~,

- Figure 1.4-2 (Cont.)

CPC Disk Generation Log Track Software Revision Date Engineer 19 I

20 21 22 23 24 25 26 4

27 28 29 30 i 31 32 33 Revision 03 Rage 27 of 97

-- - ., ,--,,.n .,, - , , + . . , , , , -e ..<.-m

Figure 1.4-2 (Cont.)

CPC Disk Generation tog Track Software Revision Date Engineer

- ~

34 35 36 37 38 39 40 ,

41 42 43 44 45 46 47 48 49 50 51

. 52 53 a -.

Revision 03 Page 28 of 97

l l

1 Figure 1:4-2 (Cont.)

1 I

CPC Disk Generation 1.og Track Software Revision Date Engineer

~

7 54 55

. 56 57 58 59 60 ,

61 62 63 ,

4 '

1 4

1 1

i i

I .

)

i J

Revision 03 Page 29 of 97

Attachment 1.4-1 CPC Intermediate Disk Generation

Purpose:

To generate an intermediate disk to be used in generating a reference disk.

. System Configuration

,

}

s i

d Procedure:

i j

s I

I .

i Revision 03 Page 30 of 97

Attachment 1.4-1 (Cont.)

CPC Intermediate Disk Generation

4) Enter the command l

Revision 03 ,

Page 31 of 97

Attachment 1.4-2 CPC Reference Disk Generation

Purpose:

To generate a new reference disk, given an existing reference disk and a tape containing revised object modules.

l 4

System Configuration:

i i

i

• ==

, Procedure:

i I

i I.

j

~

l 3

l i

) Revision 03 Page 32 of 97 L

Attachment 1.4-2 (Cont.)

CPC Reference Disk Generation e

4 i

t f

t D

Revision 03 Page 33 of 97

I d

. Attachment 1.4-2 (Cont.)-

1 i CPC Reference Disk Generation e

i t

4 i

i i

J 4 .

j t i

J i

i i

t i

1 i . ,

1 i

i 1

,i Revision 03 ,

Page 34 of_97 l

Attachment 1.4-2 (Cont.)

CPC Reference Disk Generation 4

i l

i i

4 4

i Revision 03 Page 35 of 97

. Attachment 1.4-3 CPC Load and Test Disk Generation.

Purpose:

To generate a load or test disk using DSKUTL.

Procedure: _

l

{

)

i l

i 4

O I

f Revision 03 Page 36 of 97

.-- __ ~-

O -

- Figure 1.4-3 CPC System Contents Memory Locations Disk Track .

l

.i o

This map provides typical addresses for information only, actual addresses for specific plants may vary. This information reflects the system implementation as of the date of issue of this document.

. Revision 03 Page 37 of 97

l

. Figure 1.4-3 (Cont.)

CPC System.

Contents Memory locations Disk Track _

+

A

.s 4

n Revision 03 Page 38 of 97

4 Figure 1.4-3 (Cont.)

i 2'

CPC System 1

Memory Locations Disk Track Contents i

F 4

1 .

i l

I 1

2 I

^

4 4  %

t j -

i i

4 1

4 i Revision 03 Page 39 of 97 p.,- ,,r -- , - - y --m---,----o, --.,-.g--- -<g++ ---,,~e- - - --> e -~~y a,~rn ~:,, -

- rw. - -

r-m ,e.-. ,~-w- - -- rm-, - -,.n. - , , , ,7,-,

- - Figure 1,4-4 CEAC System Contents Memory locations Disk Track

' /

4 o

This map provides typical addresses for information only, actual addresses for specific plants may vary. This information reflects the system implementation as of the date of issue of this document.

Revision 03 ,< Page 40 of 97 e

m w

- e ,

Figure 1.4-4 (Cont.)

CEAC System Contents Memory locations Disk Track _,

4 7 ,

t Revision 03 Page 41 of 97 i

oes - , ..

1 Figure 1.4-5 l

CPC Test System Contents Memory Block Disk Track i

l i

1 e u

1 Revision 03 Page 42 of 97

. . _ . . , _ . . . _ . . . . _ . . . , _ _ . . _ . . . . , ~ . . . , , , _ _ , . . . . ,__, . - . . - - , _ _ . , - - - - . _ _ .,, . . . - - - . . - .

i Figure 1.4-5 (Cont.)

! CPC Test System Contents Memory Block Disk Track

~

O i

t 4

1 i

i I

~ _6 f

J f

I i

1 4

E l

4 ,

r i

(

i 3

4  !

0 I

f t

i 1

Revision 03 . Page 43 of 97

4 Figure 1.4-6 CPC Files Name Object Label File Name t

d.

i l

k 4

, 4 a l i

Revision 03 Page 44 of 97 g* -- == ----ewr- w- ------

e yan---- ----.y. -& . -- i e.. e - wr e m e. -w. .--.- i-- , e ey ytw e-

Figure 1.4-6 (Cont.)

CPC Files Name Object label File Name r

Revision 03 Page 45 of_97 l

I . Figure 1.4 (Cont.) t CPC Files 1

L t

Name Object Label File Name -

t i

J I

M' 1

4 k

i 4

1-3 4

i 1

1 i

i 1

4 i

)

l 1

4 1

r 3  !

1 1 I i

Revision 03 Page 46 of 97-

_ _ _._--.,,,.,__.,,,,._...__.--...~,.__--,_.,.---_..,.4

1.5 CONTROL OF QUALITY RECORDS -

Generic and Project documentation of software systems will be maintained in accordance with Reference 1.2.2.

In addition, a duplicate of the revised master source files shall be maintained in a separate location from the master source files under controlled access and with suitable environmental provisions.

The duplicate will be generated whenever a new reference disk is generated. After the duplicate is generated, its source files will ,

be assembled without listings. The resulting object code will be used to generate the periodic test disks to be sent to the project.

This is accomplished using the commands described in Appendix 1-E.

Project disks will be part of the normal backup program. Two magnetic tapes will be assigned to each disk. The BACKUP utility (Reference 1.2.4) will be used to perform the backup, with alternate tapes used each backup. The date of backup and the contents of the disk will be'obtained in accordance with established operating procedures.

, Revision 03 . Page 47 of 97

APPENDIX 1A Software Organization and Design Considerations Revision 03 Page 48 of 97

_: _._ =  :. _ _ .

APPENDIX 1A 1A.0 SOFTWARE ORGANIZATION AND DESIGN CONSIDERATIONS To achieve modular, structured, and standardized software, several constraints shall be adhered to in the design. These constraints are intended to allow modification to be performed with minimum impact and to simplify the testing of the software.

lA.1 SOFTWARE ORGANIZATION 1

1A.1.1 Modular Structure i

I lA.I.2 Program-to-Program Interface Strict control of program-to-program interface allows each program to be developed and tested in a stand-alone mode and to be integrated into the system at a later time.

~

Revision 03 Page 49 of 97

,. .. 4 , .p., e,..u-w.- -

• = e w --

• 9 -

1A.I.3 Data Base Structure .

JN Revision 03 Page 50 of 97

- :- .~ . . . _ -

i 1

i i .

.l I

l j

I 1

.i .

i t

4

,f Revision 03 Page 51 of 97 1 *

.,e. - - . * - e-+:4,>-+ <e- .

.-c- - ~ , . ,,.:. . .- - n -.. ., , . _ - ,, , , . . - . . - - - - - - .

lA.1.4 Timing and Processor Loading The design goal for the processor loading for all applications programs in the on-line software system is less than or equal to 60 percent.

i i

e J

d 1

3 J

I i

I

Revision 03 Page 52 of 97 r , 4 . , - - ,- --.-e . _-,--_.e.--.* .-., .,r- - - ,, .-4 ry, , , - - ~,-. ~.r --- , . . . ~ + ,-.,---., , , --- ,s-

-- -  :-. = - . . - . -

1A.2 DESIGN CONSIDERATIONS AND DOCUMENTATION i

i 1A.2.1 Flow Charting Conventions Standard flow charting symbols are to be used for all program documentation flow charts.

1A.2.2 Program Identification The following guidelines shall be followed to uniquely identify each program: .

1

1. The program must adhere to Perkin-Elmer CAL assembler conventions so that the program may be assembled with the CAL assembler at the current revision level. Programs must have no errors. See Ref. 1.2.6.

2. Every line in the source file shall be identified by a sequence number in positions 73 through 80. The sequence numbers shall be of the form:

ccennnnn where:

- ccc is a unique three letter code assigned to the software system under consideration.

4

- nnnnn is a 5 digit decimal number which should initially be assigned in increments of 10 to allow for later insertions.

Revision.03 Page 53 of 97

- - - - _ _ _ - - - - - - - - - - - _ _ - - - - _ _ - - - - - -.------,----a- - - . - - - - - - - - - - - - - _ -

All programs shall be assembled with the sequence check option enabled.

3. Each program shall be organized into the following sections, in

, the order listed below:

- Title Block (See Figure lA-1)

- SCR Records

- Entry Point Definition or External References

- Global Data Base References

- Mnemonic Equates .

- Main Program

- Program Modules

- Initialized Storage Definition

- Scratch Storage Definition Note that not all of the sections listed above will be required in all files in the system (e.g. constant files). The title block, however, is mandatory.

4. A prototype of the Title Block is shown in Figure IA-1. The i

lower case information will be replaced with infonnation specific to each program. The upper case data shall be entered

)

as given. The complete program name shall include the plant or utility name or the word " GENERIC" if the program is common to all plants which contain a specific software system.

. j

\

Revision 03 Page 54 of 97

,%,ng+w, ,.,mw,,m.-

1. _ weg, .g,

^ ^ - ^

1A.2.3 Coments Every line of code shall contain a comment where such a comment is of benefit in explaining the operation. Such coments should be

, functional in nature and shall not elaborate upon the machine instruction, as it is assumed that the program is reviewed by qualified personnel.

l Full line coments should be inserted freelf to delineate and explain sections of the code and data base.

i 1A.2.4 DISK Identification

• 4 Each disk generated shall contain a unique identifier consisting of a plant code and the revision number of the software contained on the disk.

1A.2.5 Arithmetic Fault Detection 5

Every arithmetic operation other than simple array .index calculations shall be checked for arithmetic fault either by program logic or by hardware trap features.

i M

l M

Revision 03 Page 55 of 97

==-

Revision 03 Page 56 of 97 l

g

Figure IA-1 CPC PROGRAM TITLE BLOCK

- PROGNAME PROG the plant & progra nues - up to 45 char. REV. N.nn CCC00000 CROSS CCC00010 SQCHK CCC00020

, TARGT 16 CCC00030

• CCC00040

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • CCC00050

• CCC00060 -

• the plant nme and the complete progra nue - up to 61 char. ** CCC00070

• CCC00080

• CCC00090 -

PROPRIETARY INFORMATION

• CCC00100

• CCC00110

• C0180STION ENGINEERING, INC.

• CCC00120

• CCC00130 WINDSOR, CONNECTICUT 06095

• CCC00140

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • CCC00150

• CCC00160

• CCC00170 ASSEMBLY DATE:

• CCC00180

• CCC00190 ASSEMBLY TIME:

• CCC00200

• CCC00210

• PROGRA!94ER:

• CCC00220

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • CCC00230 TITLE C01BUSTION ENGRNG., WINDSOR CT. PROPRIETARY INFORMATION CCC00240 ORG X'nnnn' CCC00250 Revision 03 Page 57 of 97

- .. .. _ _ . . _ . . ~ . . .

--w -_

I l

l t

. APPENDIX 18 Comand Substitution System Files I

Revision 03 Page 58 of 97

=

4 k

- UPDATE A SOURCE FILE r >

I i

)

j 1-i 4

1 1

t

'I.

?

i i

i i

4 I

1 I

1 e

i +

A 3.

f i

I f

i i

I 1

N i

i 4

i 1

l f

1 i,

Revision 03 Page 59 of 97

• e

' ' - * * * .w.me_, ,

I y *w,y-wy w ~r- y-yy- w - m yv-gr- -- y -,.

.-v-M- -'

.-%*y,my s---wym-. . _+%e-i g er -w ,# e<-, *+-- .- e , w w- -r m.m.-pw.4 y-w+ .- -+ +---

I a

I 1

4 d

1 4

._ i

)

l i

Revision 03 Page 60 of 97

• N** -

,.w me m.g om e. m. m, .. ,.%.w..

- - . . ,, , , . ~ . . , , - - , ,, . , . . , , - . , , - .,-L..._-- - . . . ,n- ,--,.~,r.,n - ..,,

f 1

i Revision 03 Page 61 of 97 9

'N4 e

+ ~- o---,

v-w

UPDATE AND RESEQUENCE A SOURCE FILE 1.

F r

i f

1 I,

I 1

1 1

l 1

1 1

i i

i i

i i

1 t

i ,

i i . -

I I

.i

. \

1 I

i f

i

• r l Revision 03 Page 62 of 97 l

,~ _

i I

o Revision 03 Page 63 of 97 l

-p

- . w -- -

1 1

1 1

f 4

• J e

j J

l 1

3, i

l i

4 i

t f

i -

i 4

)

e i

j 1, -

g i

l i

i

)

, Revision 03 Page 64 of 97 i ,

l

. .-.. , _ g 4 -4 g g

'w ,m .

% --r - - g 7. , ,

.+-g m- -.e~-a -

• • • • 'M- 6 '-B.%- -' - - -wT i-- y w crw> --

-- e '-Nvs= Awhg - - -

UPDATE THE REVISION LOG I,

l l

I t

r Revision 03 Page 65 of 97 a

I

.. 4,-. . . , _ ,. ..m_.- -

... .------wi-** *

. - - - = _ ----,r , ,_,,,..,._-.-.m-. - -

O O

Revision 03 Page 66 of 97

-~ -

_= = _ . - _= . . __. ;___.

t 1

- CREATE A SOURCE FILE 5

i 1

t 2

i 1

4 1

• i i

i I '

I 4

1 4

L 4

1 1

I, 1

1 4,

4 ir i

I I

. t 4

0*

l 4

i i

1 i i

,a 1

I.

t i ,

1 1 -

1 i

i i

1 1

Revision 03 Page 67 of 97

1. ' ** - . - - . ..%.. . , , * * - awm p, 1

_ . - , , - . . . . ,-. . , - . . - - , _ -.w.,,-~---. ,.-

,,.-,__.,,._#,-__-.,,, ,,.w-~_.,,....,,,,,w.,..~,..,-.w.,,_,-,w.,.., ,.ec-..,-,.~,, yw,----- , ,-*w, . , .

9 Revisign 3 Page 68 of 97

= .- - - - ---m--- e --.

APPENDIX 1C SOURCE UPDATER COMMANDS

. Revision 03 Page 69 of 97

-1 The following is a description of the six update commands which can be used in the Source Updater command file to update a source file. Note that all updates must be made in order of ascending sequence numbers. i

1. INSERT Command The INSERT Command is used to insert one or more new statements into an existing source program. The records following the INSERT Command are inserted in the new file until a record with a '/*' in positions 1 and 2 is read from the source update file, The format of this command is:

INSERT segnbr ,

where 'segnbr' is the sequence number after which one or more new statements are to be inserted. If, before 'segnbr' is found, a sequence number on the old file is detected that is larger than 'segnbr','or an E0F/E0M is detected, the error message:

SEQUENCE NUMBER NOT FOUND is printed and the operation is aborted.

To. insert two statements between XXX00150 and X.XX00160, the following statements must be placed in the Source Updater command file:

INSERT XXX00150

- statement #1 -

. - statement #2 -

/*

Revision 03 Page 70 of 97

_. . _i_ _ , _ - - - - _ ,

._ . .a l

2.. DELETE Comand ,

The DELETE Comand provides the capability to delete a single statement or multiple statements from the input source file. The format of the comand is:

DELETE segnrl, segnr2 where 'segnrl' specifies the sequence number of the first statement to be deleted. If 'segnr2' is omitted, only the statement specified by

'segnrl' is deleted. If 'segnr2' is specified, statement ~s between

'segnrl' and segnr2', inclusively, are deleted.

If, before 'segnrl', is found, a sequence number is detected on the old file that is larger than 'segnrl', or, before 'segnr2' is found, a sequence number is detected on the old file that is larger than 'segnr2',

the error message:

SEQ NBR NOT FOUND for 'segnrl' or the error message:

SECOND SEQNBR NOT FOUND

. for 'segnr2' is printed. The operation is aborted when a sequence number is not found.

v.

To delete statements FLWO1010 through FLWO1500, the following comand is placed in the Source Updater comand file  ;

. 1 DELETE FLWO1010, FLWO1500 l l

Revision 03 Page 71 of 97 )

- -. a _ ._ - . - - _ .--.-

3. MODIFY Comand The MODIFY Command is used to delete a single statement and insert a new statement in its place. The fonnat of the comand is:

MODIFY segnbr where 'segnbr' indicates the sequence number of the statement to be modified. If the sequence number cannot t,e found the error message:

SEQ NBR NOT FOUND is printed.

To use the MODIFY comand to delete statement FLWO1000 and replace it with a new statement, the following sequence must be placed in the Source Updater command file:

MODIFY FLWO1000

- new statement -

4. REPLACE Command The REPLACE C'omand is used to both modify a specified statement and insert statements thereafter. The format of the command is:

e REPLACE segnbr where segnbr indicates the sequence number of the statement where the i insert procedure is to begin. If the sequence number cannot be found an error message is generated. Replace is. terminated by a statement with a /* in positions 1 and 2.

Revision 03 Page 72 of 97

__e,y._y .,.m v-,.w- w *. **-mw-&% ~"" *^ ~ * * * '**W' '~"'*

O 5 .- SELECT Command This command is used to modify or insert source lines at selected locations specified by sequence numbers. The format of the command is:

SELECT Line 1 segnumbi Line 2 segnumb2 Line 3 segnumb3

/* .

where segnumbl, segnumb2, etc. start at position 73 in an 80 byte record.

When a sequence number is found in the old file that matches the sequence number specified, then a ' modify' is in effect; if a sequence number is fo'und that is larger than the one searched for, then an ' insert' of one line is done before the larger sequence number. Select is terminated with a record with /* in positions 1 and 2.

6. ENDUP Command This command terminates the U.PDATE mode. If the old file has not reached the 'ending string' specified in the Update command or EOF /EOM, this command copies the rest of the old file, until the 'ending string' or EOF /EOM, onto the new file.

Revision 03 Page 73 of 97 l . __ . _ . . _._________ _ _

APPENDIX ID Automated CPC Integration

/

Revision 03 Page 74 of 97

. APPENDIX 1D Automated CPC Integration for 3410 Systems A) Portions of the procedures needed to perform an integration of a CPC system on disk have been automated. While the Attachments describe the application of these automated procedures, this Appendix outl'ines the operation of specific modules.

B). The' documentation covers three functional procedures. The CPC Log Print procedure prints the CPC Program Update Log in a formatted manner. The output is grouped by the name of the program that was changed.

Revision 03 Page 75 of 97 .

. CPCLOGPT. CSS

Purpose:

Produce an organized formatted report based on the CPC Change Log.

m e

Revision 03 Page 76 of 97 i .

__.__- . : . u=- -- - -

. CPCLOGPT.FTN

Purpose:

Read the log file on LU S and produce a report on i.U 6.

'N Revision 03 Page 77 of 97

l l

i i

TASK GENERATION l

CPCTET. CSS l

Purpose:

Link the object files that make up a complete CPC/CEAC system.

. . 4 I

l Revision 03 Page 78 of 97

9

- . _.J Revision 03 Page 79 of 97 l . - _ . . . - . _ - -. -- -- ..- - - -

- TASK GENERATION II l l

i Name: PERTET

Purpose:

Build a task image file for a system test case.

k f

d 1

Revision 03 Page 80 of 97

"***"'"***W

l l

Revision 03 Page 81.of 97

DISK GENERA' TION SYSTEM BLD3410. CSS

Purpose:

Create CPC or CEAC load module on floppy disk.

l -

f i

J I ,

Revision,03 Pege.82 of 97

...== u----am4--oc-.

'+w *  %- & w cm , m----+s- 4 mev, y y v,-- w e,-,y ,, , ,~ ,p-pi, e -

qt- p e 4

1 1

Revision 03 Page 83 of 97 l

.r,- m - = * = - .em>*

~ '

DISK GENERATION SUPPORT Name: PERBLD. CSS or TSTBLD. CSS

Purpose:

To create specific sectors on floppy disk of periodic test cases or support programs. _

i i

t 1

Revision 03 Page 84 of 97

APPENDIX 1E Periodic Test Disk Generation T

Revision 03 Page 85 of 97

.- . - _ . ~ .. .- .-- .

e

_ _ _ . . _ . .._= . . _ .

1 APPENDIX lE Periodic Test Disk Generation - Tape Creation

Purpose:

To create a Periodic Test disk from a project disk. ,

E e

o 0

O

1. 1 i

Revision 03 Page 86 of 97

1 1

i Periodic Test Disk Generation - Backup Tape Generation

Purpose:

To create a backup tape of the system project disk for purposes of generating a periodic test disk.

~

9 Revision 03 Page 87 of 97

. Periodic Test Disk Generation - Tape Restoration

Purpose:

To build a scratch disk with the source files of all project software elements, by deleting old files and restoring new images from the system backup tape.

e J

i

- , l 1

l

. Revision 03 Page 88 of 97

- __ _ l

r M

Revision 03 Page 89 of 97 j -

-~ --- - . . _ _ . _ - . _

- I --

'~ ~ ~' ~

^ ~

- - - - = ^ .

I Periodic Test Disk Generation - Project Assembly l

i

Purpose:

To create a new object file for each source element of the CPC/CEAC system.

m i

(

k 4

l l

1

- s 1

i Revision 03 Page 90 of 97

- - - - * * , , - _ ee w-ww,w, ,

'O

-- ~

. . , - r - -- , .w,, , e . , - . .- -

9

--1._. _ . _. . _- __

Periodic Test Disk Generation - Task Generation

Purpose:

To create task files of the CPC/CEAC system elements by linking all related object files together and resolving all EXTRN-ENTRY 1

statements. -

)

i I

Revision 03 Page 91 of 97

-- ,- , , - - . - - e v - - - - e ,e

. Periodic Test Disk Generation - Disk Integration

Purpose:

To generate a Periodic Test disk from t'he tasks generated in the task generations and compare to reference disk.

O s

Revision 03 ,

Page 92 of 97

, , , , . . , ..m - .- i.-pe-<ow=**-'s- *-

- m_ ___ _ ._ ,

4 o

1 l

l..

1 w ~

l Revision 03 Page 93 of 97

__ _ - .= - . . . . -

2.0 PROJECT DISK GENERATION PROCEDURE 2.1 PURPOSE The purpose of Section 2.0 is to present the procedures required to generate a new project disk. '

2.2 REFERENCES

2.2.1 0S/32 Fastcheck Reference Manual, Perkin-Elmer Inc., Publication

Number 48-064, Section 3.2.2. .

i 2.2.2 05/32 System Support Utilities Reference Manual, Perkin-Elmer Inc.,

Publication Number 48-031, Section 3.

2.2.3 0S/32 Operator Reference Manual, Perkin-Elmer Inc., Publication Number 48-030, Section 3.37.

2.3 PROJECT DISK GENERATION The CPC Project Disk Generation Checklist (Attachment 2.3-1) outlines the procedure to be used in the generation of a new project disk. The new project disk volume is cleared. The source files on the generic disk are then moved to source files on the new project e

disk. This is done using the 32-bit Backup utility.

Revision 03 Page 94 of 97

._ . _ . _ _ =..2 _ ___1-

. Attachment 2.3-1 -

CPC PROJECT DISK GENERATION CHECKLIST l

1. Check the integrity of the disk (Reference 2.2.1).

a) Load the FASTCHEK utility:

LOAD FASTCHEK,80 a TASK FASTCHEK

~

b) Start the program:

START,CH=devn:,L=PR:,READCHECK where devn is the disk name ,

i

2. Move all necessary files to the project disk using the Backup utility.

This procedure is detailed in Appendix 2A.

i l

4 4

Revi:: ion 03 . Page 95 of 97 l m,e -- "

y

APPENDIX 2A PROJECT DISK GENERATION This procedure describes the generation of a project disk from a previous project disk. The project mnemonic and disk volume share the same name for identification purposes.

To create a project disk, all applicable files are read from a previous project disk and written to the project disk.

1. Mark the source project disk on protected (Ref. 2.2.3) ,

MARK dev1:,0N,P,CD=ALL where dev1: is the device name containing the source project disk.

2. Mark the new project on unprotected MARK dev2:.,0N,,CD=ALL where dev2: is the device name containing the new project disk.

3. Load the 32-bit utility backup and start.

s L0 BACKUP ST,IN=dev1:,0VT=dev2:,L =PR:,ACC=new account,VE l

1 Revision 03 Page 96 of 97 i

4. Mark the new project disk off then mark it on Protected.

MARK dev1:,0FF MARK devi:,0N,P,CD=ALL Revision 03 Page 97 of 97 3

_ne.

4 a

f P

i i

COMBUSTION ENGINEERING, INC.

l l

f I

a :

r 1

_ , , , _ , _ _ _ _ _