ML20147F298

From kanterella
Jump to navigation Jump to search
CPC Protection Algorithm Software Change Procedure Suppl. Rept Presents Procedures to Be Followed During Mod to Cpc/ Ceac Software & Procedures for Generating Cpc/Ceac Software Application to New Project
ML20147F298
Person / Time
Site: Arkansas Nuclear Entergy icon.png
Issue date: 09/29/1978
From:
ABB COMBUSTION ENGINEERING NUCLEAR FUEL (FORMERLY
To:
Shared Package
ML20147F289 List:
References
CEN-039(A)-NP-1, CEN-39(A)-NP-1, NUDOCS 7810190090
Download: ML20147F298 (96)
v • d • e


Text

.

-- m D**D *D'T}

ood o JId];d j C, v'

-ARKANSAS NUCLEAR ONE - UNIT 2 DOCKET 50-368 CEN-39(A).NP SUPPLEMENT 1-NP C' ' PROTECTION ALG0RITHM SOFTWARE CHANGE PROCEDURE SUPPLEMENT f^s L)

SEPTEM.BER 29, 1978 L

Combustion Engineering, Inc.

1.1 fluclear Power Systems Power Systems Graup Windsor, Connecticut 7 3 )619 00h0

. ., r .,

~

/ .- . .. l

,i; .

(. m .

3

-V , ,

.s. .

l '

. . . . _ . m. . . . ..

' ~

LEGAL ll0TICE .

' This report was prepared as an account of work sponsored by Combustion Engineering, Inc. Neither .

Combustion Engineering nor any person acting on its behalf: .

.. a. liakes sny warranty'or . representation, expre::s or implied including the warranties of fitness for a .

.O-particular purgese or merchantability with respect  !

4 -

to the accuracy, ccmpleteness, or usefulness of the .

information contained in this report, or that the use of any infomation, ap.caratus, method, or process dis-closed in this report may not infringe privately' owned ,i rights; or

b. Assuces any liabilitics with respect.to the' ~

use of, or for damages resulting frca the use of, any -

infomation, appartus, method or process disclosed in. -

this report. '

p

  • g 4 .

e .

. , . e+ . *

- O g. , ,

nq g .

g. O- 4

(

,-e =w rw ., 3w.w..ry.- ,rir. - yy vy-y>,, ,,,r'-w- - , , . ,"w -w,,---- -

we -w y v w g

TABLE OF CONTENTS L]' Page No.

Section -Title 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 8 ,

1 1.3.3 coding of Software chan,n,es 9 1.3.4 Implementation and Assembly of Software Changes ~ 10 1.3.5 Debug of. Software Changes 11

.1. 4 QUALITY ASSURED.0BJECT DISC GENERATION PROCEDURE 20 1.4.1 Input 20 1.4.2 Output 20 1.4.3 Procedures 21 '

1.4.4 Generation of Master Test Disc 23 l.4.5 Generation of Discs for On-Line Operation 23 1.5 CONTROL OF QUALITY RECORDS 47 2.0 PROJECT DISC GENERATION PROCEDURE 89

(]).

2.1 PURPOSE 89

2.2 REFERENCES

89

2. 3 ' PROJECT DISC GENERATION. 90 LIST OF APPENDICES Appendix Title Page No.

lA- Software Organization and Design Considerations 48 1B CSS Files 58 '

l 1C Source Updater Commands 66 i i

10 Automated CPC Integratio'n -

71 1E Periodic Test Disc Generation 81 2A Project Disc Generation 95 t l

-('N.

u e

. Page 3 of 96 w v g - + ,  % y

4 L

o.

. TABLE OF CONTENTS-(Cont.)

r,h,. '

LIST OF FIGURES

~ ~~

Page No.

Figure Title Chahge'ApplicabilityForm 14' 1.3-1 .

.25: _

1.4-1 . Data Flow for Disc Generation 26 1.4-2' CPC Disc Generation Log CPC SystemL 38 j 1.4-3 .

40

~1.4-4 CEAC System CPC Test System' 42 1.4-5 ..

44  ;

.1.4-6 CPC Files CPC Program Title Block 57- J 1A .

LIST OF TABLES l

l Page No. ,

Table Title DNBR/LPD Calculator System- 15 1,3-1

() LIST OF ATTACHMENTS Page No.

Attachment Title CPC Source Update Checklist for Batch Processing 12 1.3-1 29 1.4-1 CPC Object Tape' Generation 31 1.4-2 CPC Disc Generation CPC Disc Duplication 37 1.4-3 91 2.3-1 CPC Project Disc Generation Checklist

.y.

I O s_/ _

' Page 4 of 96

6

- ABSTRACT.

e ,

Q.- '

-This document presents procedures to~be followed during the process of implementation of modifications to the IPC/CEAC sof tware. Additionally. :

~this document presents procedures to be followed during.the process of ,

generating'CPC/CEAC software for application to a new project. 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 generating new project software.

O .

4 0

~

- - Page 5 of 96 V .

I 1.0 IMPLEMENTATION OF SOFTWARE CHANGES h

!O 1 1 ~.1 PURPOSE ,

1

~

~ The purpose.of.Section 1.0 is to present the procedures required j

- to 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, f r

1.2 REFERENCES

\

r 1.2.1 Software Change Procedure for CPC/CEAC Protection Algorithms, CEN-39(A)-P, Revision 01.

j O l 1.2.2 Quality Assurance of Design Manual for C-E Nuclear Power Systems  :

1.2.3 Series 40 Disc Drive Maintenance Man'ual, Diablo Systems' Incorporated, Publication No. 81601 >

l . 2. 4 CPC Disc Utility Program User's Manual k

05/32 MT Operator's Reference Manual, Interdata Publication No.  ;

1.2.5  ;

,m._

~29-574, Section 7.5 r

I l

5 i

i

%>- l i

- Page 6 of 96 l t< g 5- r- , . - *y , m c 2 _ -, .-- y e a y ~ e y g-- --

, . + , -a. w ww g i .9Pt e

. . . ._=

1.2.6 ANSI Standard Flowcharting Symbols and Their Use in Information<

LO erocessing. x.3s.

- 1. 3 IMPLEMENTATIOJt0F AN SCR _

1.3.1 Preparation of Software Change Package When an SCR is ready for implementation, the implementor will prepare the software change package by filling out and attaching a Change Applicability form (Figure 1.3-1) for each plant to which the SCR pertains. Table 1.3-1 lists all. elements of the software system. The implementor must list those' items which are affected by the SCR on the Change Applicability form and must f

date and initial each item when the required changes are completed.

If the implementor determines that additional information is required, he will contact the originator to obtain the required clarification. All pertinent information received verbally will be recorded on the SCR and initialed by the implementor.

The Sof tware Change Package will be maintained by the impic=ntor until the change has been implemented and tested. The package

- - - wi.11-then be returned to the originator for review.

Upon comple-

,y tion of his review, the originator will transmit the package to the cognizant engineer who will then file the Software Change

=

l. Package in the CPC design file.

O 1- .

'Page.7;of 96'

___ . ~_ . - . .

._ . _ . .< m _ .

N

- .. . _ _ j i

I

.1.3.2 Design of Software-Changes' N . a

/^J ;.

A. ..

After preparing the Software Change' Package, the engineer will design and~ implement the requi_ red change as follows: 1

~

1) Th'e most'recent working copy of the affected calculation _

descriptions, flowcharts,' input / output lists, variable lists, EQU' lists,-and constant lists of the System Software Specification will be marked up toireflect 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 f-s '

q on the listing will'be checked against the latest date and T  ;

time posted for that listing in the automated CPC log CPCLOG.DAT.

Also, when.a new listing is cre~ated, the previous version of the listing will be marked " superseded."  ;

3) The Phase I Test Cases will be modified as required to meet the requirements of Reference 1.2.1.

i l'

1

- 4) . -If the change affects scaled-fixed point coding, the appropriate L scaling recorded calculations will be revised accordingly. s; I

() .

! t Page'8'of-96

~

l .

I-

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

The! software change will be designed to be consistent with Appendix

-'1Aof this document entitled " Software Organization and Design Considerations."  ;

i

_ 1

. The sbftware' change will then be incorporated in a specification revision. 7he revised software design will then be independently.

~

reviewed in accordance with Reference 1.2.2.

1.3.3 Coding of~ Software 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 p the assembly listings,.will be converted into a series of Source d Updater Utility program commands-(Appendix 1-C) and punche'd on cards in order of ascending sequence numbers. The last card!in- x

~

the deck must be the "ENDUP" card.

In t.he 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 initia1' updating of a' source file during'a revision, H

_the revision number of the source file is incremented by

.:= -

1.00 and the decimal part of the number is reset ton 00. In n' .

the implementation of subsequent SCR's within this revision, l which resul't in another updating of this source file, the-revision number of the source file ~is incremented by.0.01.

h' Page 9 of.96 o -Aa

IW' 2). An "SCR Implementation Record" line will beLinserted into the

'T source' file. This line is a comment of the form:

'* REV n.nn, SCRs: 1, j , k , . . . .

~

where: Jn.nn is the new revision number i, j,'k are SCR numbers implemented in this revision._

These lines will never be removed from the file and will.thus provide a running' account of the SCRs implemented;in a partic-ular program,-

1.3.4 Implementation and Assembly of Software Changes .

The software change will be implemented in the appropriate source file using the UPDATE command (Appendix.18). The appropriate.

C The project disc is mounted (Reference 1.2.3) sand marked on.

Source Update command deck is placed in the card reader and the UPDATE command is entered on the' console.After successful termination of the procedure, the Source Update command listing

-r will be attached to the software change package.

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

  • - ~2

'h'c T procedure for using the INITIAL command is the same as the

" INITIAL" Source Update procedure with the-following exceptions.

i-

'is entered instead of " UPDATE"; a source deck replaces the Source Updater command deck; and "/*" is.the last card in the source

)O l ~ ,

s: . deck.

Page 10.of 96 r'  :

i .c._. .

1.3.5 Debug of Software Change es N.]

To complete a Software Change Package and the implementation of an SCR, the implementor will fully debug the generated object module (s). If a program error is detected during debug it will be corrected and 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.

When the object module has been fully debugged, the implementor .

w'ill complete the change package by attaching the debug test cases, filling in the applicable columns in the Change Applicability n Form and initialing and dating the SCR. The implementor will C) then return the change package to the originator and will initial and date'the SCR Log. The originator,will review the change pack-The cog-age and transmit the pac,kage to the cognizant engineer.

nizant engineer will check the change package for completeness and file the completed package in the system design file.

~

i 1 3 -

i t

o V

Page 11 of 96 j

t , -

Attachment.1.3-1:

CPC Source Update Checklist _for. Batch Processing

1) Punch the Source Update command deck

~)'

a ' Increment revision level on." PROG" card j

b) Add "SCR Implementation Record" line c) Place commands in order of ascending sequence numbers d) "ENDUP" card is last card in command deck .

2) Mount the appropriate project disc (Reference 1.2.3)

, 1

3) Merk disc:,0N wheae disc is the device the project disc was mounted in.
4) Place the Source Update command deck in the card reader a) Depress RESET on the card reader. ..

^

5) Enter UPDATE (project volume name), (file name), (rev. #), (initial) a) If error occurs in execution of Source Updater commands, enter T.BG; CANCEL. The run is aborted. Correct the deck and continue at step 4. ,

. 6) Debog'the software change

'7) ' Attach the Source Updater command listings to the software change package Page 12 of 96

Attachment 1.3-1 (Cont.)

CPC Source Update Checklist for Batch Processing

8) Initial and date the appropriate columns in the Change Applicability

~ Form (Figure 1.3-1) _ _

9) Initial and date the SCR Log A

U

~

l .u .

'O 4

Page 13 of 96 i

SC M ,

Figure 1.3-1 Sheet' of- Date: i

- Plant:

Initials: __ ___

' ('~T 4 V CHAffGE APPLICABILITY FORM DflBR/LPD CALCULATOR SYSTEM

~ ~

. Change Completiona D'te and Initials

' Applicable Object Specification Software Item Li[ ting Source e

8 e

e E

F

=

V

'e e

b e

k F

L

. 3 .

1 I

t 1 .

, __ L .

-= - -..

. . . - _ -m- , m,

Table 1.3-1 onna/teo catcutn1oa systen

-O-i

^l Software Item _ l No .- _

_ 1

.- ~

.i l

1 t -

l l

1

-Ii i

2

. 3 i

'{4 ,

5 6

OJ 8

.i

'f ?

  • f .

9 10 -

! 11-l12 -

1

-O .--

R l

Page 15 of 96 f-IJ .

Table.1.3-1 (Cont.)-

V DNBR/LPD CALCULATOR' SYSTEM No. Software Item- _

r ,_ .

i  !

'i l

. n .13 ,

' 14  !

i 15 i.

16

  • i.

17 18 .

19

'Q. ._

20 21 ..

22 .

23 24 25 1 26 *

.;= .

27

. 28 O<

'Page 16 of-95

j Table 1.3-1 (Cont.)

1

/% '

(.) DNBR/LPD CALCULATOR SYSTEM i

0 No. Software Item _

i i

1

- l 29 l 30 31 O

33 34 -

35 36 l

37 3&- -

n'.

<J

- Page 17 of 96 l

l -

1 i

  • _ _._m

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

pr

~

. .. _ . . t, t

i 1

Table 1.3-1 (Cont.)  :

) . DNBR/LPD CALCULATOR SYSTEM-i F

,t

' No. Software Itenr- -

4 t

.t ,

i

__ - t

39 ,

40 .

41 a : ,

42 ~

i 43 .

. 44 4 e

45  :

l O" t I

i 3 . .

-i t

4- . .

- ,i 46 47 ,

3 r,

e

+

i I

l' t

-482 .

]

3

[

249 .

i

. l ;

t i

1

- Page 18 of 96 ,

O w arr- e.--mm ..2.6,.e.... .....,,....,-..mmw,w..r,%.m-w .+=%,.sw., e. -w we- e .3 4 weve- m .--y < p+,w y--"9.--*. eps .., w yy p p W i y -d y, r- --

4 Table 1:3-1 (cont.)

O oNan/teo catcutaron systen 0

- No. Software Item _

50 1 I,

51' l 52 53 . a

  • i O! 54 55 .

{ 56 57 58 noi

(: .

Page 19 of.96 I

I -

4

'1.4 QUALITY ASSURED OBJECT DISC GENERATION PROCEDURE-

rq g-This procedure applies to the integration of object modules and the generation' of l'oad modules _on flexible discs'. Portions of- P

'~~this procedure b' ave been automated'as described below; - Details of.theaut[ mat','spectsareoutlinedinAppendix1D. l 1.4.1 Input ~ -

1

- The input'to this procedure shall be from two sources:  !

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

2h Quality Assured object code from a' pre /iously generated and tested reference disc. .

^

1.4.2 Output l

The output of this procedure shall be a core image load module on c mass storage media. The load module shall be tested as required  ;

. i by Reference 1.2.1. 4 1 ,

I i t

i.  !

i i

L I'

}

r Page 20'of 96 l I! -

c. .- - .. .- . - ._ __ _ _ _ _

X 1.4.3 Procedures em U '

i The core image load module will be written to disc in 4 KB blocks.

Each block wi11 occupy one disc track. A disc track may be generated entirely from revised object code, copied entirely from the reference disc, or copied from the reference disc with a revised object overl ay.

The CPC Object Tape Generation procedure (Attachment 1.4.1) is used to load the proper object modules, in' correct sequence, onto a magnetic tape. It also provides a guide to creating the abso-lute load module on the CPC Support System.

A iheCPCDiscGenerationprocedure(Attachment 1.4.2)isusedto

'z) create an absolute load module, which is then written to disc to obtain a new reference disc. ..

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

~

programs are written to the disc.

~

l l

.,y - Source files shall be modified and assembled on the Software Development System (Interdata 7/32) according to the procedures described in Section 1.3 of this document to produce one object module per source file on a project disc. The object modules will

,n be copied onto magnetic tape in the order which they will- be Page 21 of 96

loaded in core. Magnetic Tape is used as it is the only medium common to the Software Development System and the CPC Support System.. Any program object module which contains external references must be followed immediately by the object module containing the

-~codewi[ichresolvesthereferences. This is assured by use of

^ the CPC Object Tape Generation . Procedure.

Using the Library Loader on the {PC Support System, an absolute load module will be generated on a second tape. This process'is.

~

. described in the CPC Disc Generation Procedure. (Attachment 1.4.2). .

The load module on magnetic tape and the core. image on reference disc shall then be merged onto a target disc using the CPC Disc

~

Generation Procedure. -

i All disc generations must be logged'on the Disc Generation Log (Figure 1.4-2) associated with each disc.

/

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 disc. A disc which has successfully undergone

~:., all testing required by the abeve reference shall become the new reference disc for the software system.

" Oi Page 22 of 96

. , neo.weesse**

0 p.w

-.1

. ~.

_. 1.4.4 Generation of Master Test Disc

()

Once a reference disc has been established-for the software system a master test disc may-be generated. This is accomplished by restdring the project backup to disc and re-assembling the

_ source files for the system to generate new object modules. .The details' of this procedure are outlined in Appendix lE. - An entire system load module will be generated from these object modules and written to disc .using the Periodic Test Disc Generation Pro-

-cedure (Appendix l-E).

1 When all of the tracks of the test disc have been generated, the master test disc will be compared to the reference disc using the verify feature of CPCDUP. If differences are encountered, it will

(])

be determined whether the error is in the reference disc (i.e. an error missed by required testing) or the test disc. The error will be corrected and the faulty disc will be regenerated in accordance with all applicable procedures for reference or master test disc generation and testing.

1.4.5 Generation of Discs for On-Line Operation -

t I

32' ~ ' Discs for. shipment to customer sites for on-line operation will be generated using the duplicate and verify features of the CPC h

1

! Disc. Utility Program (Reference 1.2.4). These discs will be .

L

,0 i

  • Page 23 of 96

- . y*

sw vr..rw et

^

3J -~  !

3;. ,,,, .. _ .

i

~

' duplicated from the system reference disc which will be maintained by the Software Design group. The' test. discs will.be similarly generated by' duplicating the master test disc generated above.

The master test disc will.be maintained by.the Software Design'.

group. - The= procedure for_ duplicating a disc is found in Attachment ,

- .1 4

~ --

  • ~

1.4.3.

i R

1 I

i O

l TO

.- Page 24 of 96

.. ,.. . , . , _ , ,g,, . .f

-- n --+%wW aa... g. p 2 .a s ., 4 y - 3r

~

.. _ T

- -- c

~

Figure'1.4-1l . . .

Q, . DATA FIM FOR DTSC GI90*n4TIO:1

' - SOFWAl!E DI"ELOPME!!T SYSTM4 O .. .

V '..

3 -

ASSN 4 BIER CAI, 32 BIT REVISED SOUdCE p1Lg3 h 11 - 1 OR IATER

/

bN 140DULES I

OS/32gp

/ -

, 7 O / . .

-/

. / 1

+ / .

/

/

/

/ CPC SUPlORT SYSTM4 .

.A

. REVISED LIDRARY IOt.DDt IDAD A

. OBJECT 140DUI.ES j). LIBLDR 6 071 IATEt 03/16!C2 h

/ jggyp;

( . /.

/.

y, _

/

~

,/ .. ,

. / ~

/ ' -

1 / ,

/

/

. / CPC SUPIORT SYSTD4 d.f q

[- " }[]T.? .\

t

! ICAD -

, es OS/16Mr2 .-

$[

FDDUI.E CPC DUP .'!s n-, hj[ic.r p

l l

i- ,' , . .f 1.

{ ;-

REvi'nENen

/s fg ; din i

d Page 25 of 92

} ..

, r 1 1

.s- . . ... ,,

i e

t

' Figure 1.4-2 {

CPC Disc Generation log -1.

~

-C ,

' Software- Revision. Date Engineer .q Track- _

i 0 --

i ll 1  ;

p .

.r

.2 l

1 3 -

F ,

, i4 r 4 5  :

)  :

6 .:

1 .

i 7  ?

1 8

\ .

9 O <

10 -

r 11 .

i 12. .

13 i

14 15 i

16 17 l d

18; 19- ,

< L 20  :

j ._

't} -

l Page 26 of 96 1 ,

"^  % . - - + . - - - . . . , , .  ? , #?~l

.s

.. r... ,

i t'

f Figure'1.4-2 (Cont.)

0,

. O- CPC Disc Generation Log'-2 h

~ -

' Revision Date Engineer

. Trac .k' -.- . Software __

21-4 f

22 -

23 ,

' < 24 25'-

26 .
27 ,

28 -

'29' ..

O so l

31

,j 32 ..- '

33' -

R

'34 1 t

35 36 37 -

t 38

.a - t 39  :

4 I40 I 1

, 41 - I 1

, . 42 i

43-  !

.j- - -

l

- - Page 27 of 96

. -J

__.J,,-,..., -.,.,,~.------.,-.....,_e.,u.e'

Figure 1.4-2 (Cont.)

CPC Disc Generation Log -3 Q

Revision Date Engineer Track Software- _ -

l

.. 44 .,

- s 45 i

, 46 47 -

48 49 4

l 50 .

51 52 53 O 54

, - , 55 ..

56 ' 1 57 58 59 60  !

61 62 -

.- l k, 63 h

h k il-tO Page 28 of 96 i . , -

l -

Attachment 1.4-1 .

p. CPC Object Tape Generation V. -

Purpose:

.To. gene, rate E magnetic tape containing the correct number and

.seqilencs o,f object modules in order to generate a new reference disc.

l System Configuration:

.O _

Procedure: -

- ;J 1

1

h. )

~

, Page 29 of 96 C-- - _ __*_ _____ _ __ _ _ _ __

Attachment 1.4-1 (Cont.)

O .

cec 083ect Tene ceneretion 4

O 1

1

  • Page 30 of 96

. .. . . . . = . . . . . . . . . .. ii = = ryou sw=4s

i Attachment 1.4-2 CPC Disc Generation

Purpose:

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

. System Configuration: _

1 i

u i

a

.O l

^

l Procedure: <

10 -

Page 31:of 96

-^-

mm A,. <+my

i

. . , 4 _ ,

-i

~ Attachment.1.4-2-(Cont.) ,

i CPC Disc Generation 0 -

. ,I

. .I

. 1

-I s

f

+

LO .

P v

e .

s

?

-t

i.  ;

t i

F

)

3

.1 I t i

s i .

Lo e i

1 t.

.. r e

i Page 32 of.96; ,

i h

e

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

- j_,,,,, _ ,y,;. ., gl7,7'; y7 ' F

. v.-.. ,.

. .i s

n Attachment 1.4-2 (Cont.)  ;

'+ 4 CPC Disc Generation  :

- .i t

-l o- . ,

' l.

i i

g 4

4 L

i

- i 1

- t t

. O ,

i

.i

-f+

4 '

'i l-i >

l ..

i 4 i f i F u

t l

(

\

. . _.~: - .

i;

~

.. i i 1 i

^

.'}

)

(~ . ,

- )

j l' Page 33 of 96

- 1 eTv'ey--u-v- e --ew. s -

t-m vrv- v =4e- v w e '- v< r et-f y ve .r-~**= 4er- m a' yairer-- ee wr +v ew + = es w w w e.< w -t-4 m g*----,ew- T - ww ee e-g 5 a-yrwyr+ww en' + +% tw W -v m eme-w eiee st te-g ww w d newdem 1lF-4 @(@8W##W9 NN'bTN

Attachment 1.4-2 (Cont.)

3 CPC Disc Generation O

I i

l i

o e

Page 34 of 96

] 4 L .. , . . , - . . . . , , - - . ......,-._,...x... -

Attachment 1.4-2 (Cont.)

O cec oisc ceoeretsoo I

1 O .

I

_(h -

J Page 35 of 96

s a ww - . . , . . ~ , - - -

1 1

I Attachment 1.4-2 (Cont.').

O cec 04sc ceaeretiea-O s

~

1 i i 5

6 l

l

- t, e 'l

, O i ,

> t 1

- t t

' r e i s

, t

! - .-f 3 .

t E

4 a

. - I, 5

~ '

O-1 t

s L

o

- Pago 36 of 96 1

4 .p

?

..~~- - .._.. . ___ _ ,.' .__ ,_ ._. _ ._... _._,,,,,_,_,_,_.

~

i

'I

. '* .' , l Attachment 1.4-3 1 cec 04sc ougiscet4en l

-O l

1 l

Purpose:

To duplicate-a disc using CPCoVP.  !

~ \

4 e==

4 j

O

~

i O

Page 37 of 96 l

1 - -.

s

' Figure 1.4-3~

t CPC System'-1 0

Contents- -

. Core-Locations- Disc Track

- I I

A O

~

l l

Tg _

U _

w' .s -

  • Page'38 of:96-O' -
  • c e-- M M t _m ., m

- . . ~ . . - . . . .. .. .. . . - -- . . . . -

4 Figure 1.4-3 (Cont.) i O cec syste -2 o

Contents- -

. Core-Locations Disc Track.

4 e

i

~

10 4

{

i i

3

)

i 4-e f

1 0 ,

. Page 39 of 96

., -w 4

~ _, _ . _. .

,' f e .

0 i

4 Figure 1.4-4' ,

, CEAC System

' Disc Track Contents' -Core Locations

+ .

O Page 40 of 96

. .e u s + -w t ,-n% as ,,, , i s,,- o,4 3,u o uw,i _ , s' .f., , ,, g .; , ,,. E . w a y 'H .% #, A a ++ - + -e + ^wm me w4.

. - , - . . . - - - .- . . . . y -#

3

~

Figure 1.4-4 (Cont.)

CEAC System O

Contents -

Core-Locations Disc Track

- ~

~

1

~

..- 1 O

cG f

4 Page 41 of 96

__--_ _ ____ _ _ _ _ _ _ - - - - _ _ _ _ _ _ _ _ _ _ _ _ _ . __ _____J

l l

Figure 1.4-5 (O CPC Test System u)

Contents _

Core Block Disc Track

+g.

f S

e L) e 09 l

e ,

!x_/ w 6

Page 42 of 96 f

=!%,,w.c.,_

A

1 Figure 1.4-5 (Cont.)

n U CPC Test System Contents - Core Block Disc Track

- I r

.O l

t 1

(, '

i Page 43 of 96 O

hhwe=4%* * +.*.e... ..

~ , ._ ..

' Figure l.4-6 CPC F'iles -1 0

Name _ ._ Object Label File Name 9

s

- .1 1O womme - .

Page 44 of=96

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

rrs

. 1 j

i Figure 1.4-6 (cont.)  :

O cec riies -2 l 1

Name _

_ Object Label File Name

)

.m ON./

. .= .

~

I

/()T -. ~

Page 45 of 96

Figure 1.4-6 (Cont.) )

. i

]

CPC Files -3 1

O l Name _ Object Label File Name I

i A

U Page 46 of 96 m,,..., . . . .

4 "1 5 . CONTROL 0F QUALITY RECORDS Q

Generic and Project documentation of software systems will be maintained irt 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 disc is

~

sent to a project. After the duplicate is generated, its source files will be assembled without listings. The resulting object l code will be used to generate the periodic test discs to be sent to the project. This is accomplished using the commands described Q

in Appendix 1-E.

Two Project discs will be part of the normal backup program.

The BACKUP utility magnetic tapes will be assigned to each' disc.

(Reference 1.2.5) will be used to perform the backup, with alternate tapes used each backup. The date of backup and the contents of the disc will be obtained in accordance with established operating procedures.

. ~.: .

~

I 4

?

l s

  • Page 47 of 96 8

L .

J

t t

i E

E APPENDIX 1A P

Software Organization and Design Considerations

=

9 I

I

- l l

1 1

1 l

l O

l l

- Page 48 of 96 i 1

I

- , - - - -~ . ~ . . . . . . ......ms.

. . .. ,y,n., . . g, c ,7, , , . . . . , , , ,

\

k APPENDIX 1A I

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

1A.1 ' SOFTWARE ORGANIZATION 1A.1.1 Modular Structure a

~

. i.

~~-

- i 1A.1.2 Program-to-Program' Interface '

t

.?"

~Stric~t control of program-to program interface allows each program to be developed and tested in a sth~nd-alone mode and to.be integrated into the-system at a! 1atertime.[

~~

'l .

q Page.49 of 96 l

. :l m- __ ,,,.:.y.,_,._ _.

..c..y. i

.t

'y 7

n .

s 4

4.. . .__

-3 1

j h I, t

.n. -

l

. r

. i .

, \

. ._3 . .

a >

t T

T B

O: -

i[

. r e-

. r 1.

i 1 .1.3- Data Base structure ,

. -f "To 2illow plant- dependent data to be changed without irapacting the '

program code,.' application programs silltbe divided into two separateassemblies.[ '

o- ,

J.\

O

~

.o -

r.. . - t.

Page 50 of 96 1p h*s^ f >-A r.. ,. .. + . , , , > ,

. .,9,.-- - % - y .n s- g e 99 ,g , " - - - - .--

., ,,n,.a 4.w 1 w, , n i

'I O

c O

I 4

I

',s l

)'

( .

LO ' '

Page 51 of.96

~

.....%..i. . i su i swa .

1A.1.4- -Timing and Processor Loading -

. - r '

eO= -

The design goal for the . processor loading for all applications , .

I '

programs.in the on-line; software system is less than or equal to

~

~60 percent. l P

1

. -s -

LO Page 52-of.96

u " . i-my. . ,

1A.2 DESIGN' CONSIDERATIONS AND DOCUMENTATION-x

9 1A.2.1 Flow Charting Conventions t _ _

ANSI standard flow charting symbols are to be used for all program documentation flow charts. These symbols and guidelines are

_ defined.in Reference 1.2.6.

1 A. 2. 2 .

Program Identification The following guidelines shall be followed to uniquely identify ,

each program and the statements within the program:

-1. The program must adhere to Interdata CAL assembler conventions so that the program may be assembled with the CAL assembler at the current revision level. ..

2. Every line in the source file shall be identified by a sequence number in positions 73 through 80. The sequence j ,

numbers shall be of the form:

CCCnnnnn where:

~'

Oc cc is a three letter code assigned to the software system under consideration.

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

p G

~

Page 53 of 96  ;

.------.-.------..______.._-----.__.--.---_-------__.---.~.--.--.-------__a__.----_.--__-------._ . -

'^~I$

~

'All programs shall be assembled with the sequence check th is ,/ option' enabled.

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

^

in-the: order listed below:

-Title Block (See Figure 1 A-1)

-Entry Point Definition or-External References 9

-Global Data Base References (EQUs)

~

- ~-Main Program .

-Program. Modules .

-Initialized Storage Definition

-Scratch Storage Definition s

~

- ()

Note that not all of the sections listed above will be required in all files in the sys. tem (e.g. constant files).

The title block, however, is mandatory.

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

The lower. case information will be replaced with information 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.

()

4 Page 54 of 96

, ',WW

l 1A.2.3 . Comments l0' Every line of code'shall contain a comment where such a comment

..is of benefit-in explaining the operation. Such comments 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.

Full line comments should be inserted freely to delineate and

. explain sections of the code and. data base.

1A.2.4 Arithmetic Fault Detection.

A Every arithmetic operation other than simple array index calculations o,

shall be checked for arithmetic-fault either by program logic or ~

by hardware. trap features.~ , ,,

,y -

~

OL i o -

l' _ .-

Page.55 of.96

. . , m-e s A-- > ;_= '

a. .m

e l.

i i

n Page 56 of 96 MI' 'SN12'^f_*_*M1_ __ _ J_

  • 1 - .1 ?1 '-'1____ _' .ma - - . .L . -

TMT;AM COD!WC fMPUT C.-be+i Da.w _-

to & - -

n y

. u.ir,

,__s

o. ss __

M M4L 6647 73 :s f 5l?tf t::?l?i;!

57 53 59 d 61' 43 as 45h5 47 43 .9 53 51l52 54l55h5 62l53l64 65 55{5?f0 f tf2 fC l2 !!la !5 p !?l5 l* l 2l?i 2'h3ltsltsltsft7h3l19l Ohtl 2h3l2sl25f6f27hth 30h132l33h43435 37l33f39ftcht

.m! c;cic.6.7p c c 42.- up ta n (c ha<r REv1 A

!proryname, :pgcci l y h;e; ipta;n q ll pr oL7 cc;m p anels c!c;c:ooo/c l ! * ' I i ! I i iS.c!EiAiri i i l ll  !

l

_c:cs_ _ ?_..f2

.c_. _ _;

iiii i ! I l lce 05131 l l l . '

- - - - = O.cic C.O CJC l I i:~.'S ili.ti l l

_..C.__ CP4] m l C!c'c:u s.__F_ _:.C.,C _ ~C

)

.lI!IIl }I l_' M niiUTFl_{f((i 4_

c!cic oCc5c l ,1 l ! l i l l l !TW'E6!71 1/6,l {._.g m . _[. ,

l._ l l

Z /!,f5Rf!f 7'70

,i u _. _ _._., ,

cicCGOC6L

[RC PREiE ~VTARY

.7 C 7*. N t,

._4 ..

E A!G . , n1AtD 30 R ,

c'c;c.C C C 7t il!I.,;Il\;TiIl+Gli.!_{Ei

.t

1 l l 1 l !C.R l sC:Ci x 1 njnn'n 30,JfT"fC//

C

--+-

{. l EV/@

ll i e o .: -

elc;c c w -

-if  ! ! l Lt* i -L l_ 'Li_

8

[~j. l ,__.,_m ..l. l uj.. . ._;__,_..__ . . . ._ . . . .

. _4 _ _ , _ _._ _ . . _ . _ _ . .

..;_ _ __ .. _ J_ l -

c c ic p c c.7_t a- -_ .

aph*MyMyp;w'p yh,xh ._%%*:+f eqn%+ 3 yc+FJ-wL1c.% s w g y.I np:py:pI ,

f MWM'KXFW,d'4;qT-'XR4.*N:&3}'+; 'W c C;C p d / ,' -

7l1 l! d'Yir;e I 7 .l f- l l

k

'IIi! I l h

i t jropdTm n ame up to 6 c ba.r fcfc~;.'c/y, tv 's f,h,e If.f.cs~f rjafne' an bing

' c /e te - / .

e k clc:00 /'2.

  • i il.ili -

} ll [

' k c,cic l C J 5L h' t iPRO P 2.ZiE7f2 Y ((NfQVV T]I'Of 43, l 'cid& cB -' '1/ :- .

_ li f

b. '* i i i l i_.:! J a _iwl- -s_.l T~ .[_ , .lt_..i_ + bc;c'g(Y.s't V i C Ga.*30$lrT,0?! \EV'GIA_AELyeiZA_b. . ,_ __. I}d C_- . _ _ _ ._f.. ._ q_%.

(W C;clc'CC./'6s p[ ,,3III,,3'  ; I

_b _ _ __ __ . . . , _ _ _

%, c;c;o. p /:7 Cg y.-!C O!///.!ErirEC,u7'gp6'# 95 i

'N ! :'/JF.O: . ,

'llN'1 CI,C LC'f C / .3 .

Iil!ll}1' ._ lll l[

.! fI 7*.

._ u l _ _

.w g p G 4 g y gl.i.; c c;cjg,0 flf i

per ge i_

___._f____.____._t :g p x w ; w n W WWxWja <M.eNyg.g)j.+Wv_ . _ . .2.y.= h. _ 74 N w n M g+: Me:q:g mi , dc;c,-7E.=

i j

II I ,

xi iii! !II i yq  ! c;ctcp.c g;:

-[- -l-

.SJ l 'A33lEP3 LlYl p/TE' -- -- - - --- - - - - - -

jy E[d!_cT5fff.

~Wiiil1i!iIl1l

-Ilf -_ _ _ _

><3 c c.c;.c z

+~ t
AS3EA!3.LlY; T TAIEQ cfdicr4F/

_ _- M

' ~~~

f fc'd^f~~lj W ! I ' I l ! ! I I {_k :

ik ' 'P R O G R D !,:1,

~

m-[-

~ ~~

,- ._ _ - _ _: _ - - - - -.~_

' cicp ?p 2p_

M ii uM*yenVpm qWpWal I l

[ P*P.Y, p !:;,;, p p ppjs p'M9%DWM%pjnl:>ph jhWWr%gl up3p4p5pg3.w, y m ,$ 47 l4: j.,

.o sa si s2 53js4l53 s6 >> se >q,.oj. :j.3j.. as .q.7ps e, 7a rij : r 3ji. l7,p, j::,,q. , i

,  ; pplGh>lspl'ipsp:;np2 pppopi 3 . 43 4i i

m,

'a=4 3 <t a:s sz .ts tst Figure IA-1 o -

a CPC PROGRAM TITLE BLOCK -

e e

.! _ __=_- _ - - - -

_ /

APPEt1 DIX 1B O

- CSS Files 0

e. *-

a O

O v

- Page 53 of 96 o

          • y *- + tree *,'"* 'P'"N

___--_.___.__.___m. m. mu,, _ _ _ , . , . _ , _ _ . _ _ _ g .g'_, ,._.., _ _ _ _ _ _ __=_e _

- t,

. r' -

, ,T i

UPDAT$ A SOURCE FILE-

D -

.Name:. UPDATE.

Purpose:

Update a CPC source file and p_erform a CAL assembly-

< \

~

.O 1

1 I

e

- Page 59 of 96 l y ..g

. 4 e

n s

~

a -

O I

I I

(

l O

r

- Page 60 of 95

<'T-v"p--=--< u s.w g, , , -- , , , , , , . . ,, , . , ,. ,, ,. ,ye.. .. . . . , , . . ,,,, ,,,, , , , , . , , . ., 3,..g ,,.,,-y, ., ,.. . . . , , , - - .,, ,- #

. . 1, 6

- W' ,

Example:

1 4

4

~

I 94-1 Page 61 of 96 Hy? * *; ymeM %qq. g ema y , .r p.., y gy g y ,,,y. ,, , ,_

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

i

' UPDATE THE REVISION LOG p^V- -

r Name:- UPDLOG  !

Purpose:

. Add a record ~of any revision to CPC software onto the revision log. i

' This CSS ~is not called by the user, but by UPDATE and INITIAL.

+

r i

4 ~{

5

- i

)

i I

k I.

t i

l

.a l

l

( l-e b

  • i Page 62 of 96:  ;

., , a<,wn-.vn. -

l .

1 l

1 f

5

~

e i

i i

4 1

\

l

\

i 1

. 1

- Page 63 of 96 f ewe ** * - ,- we a ,y e._ y

. ~

-4 h

.. . . i, t.

T..

CREATE A' SOURCE FILE j 9

Name: INITIAL' i

-Purpose: Create a CPC source file and. perform a CPYA and CAL assembly f

1

- f

- r i

1

-i +

1 h

( -

-t i

i 1

~

.Q _

-}

t i

5 .

i 5

r t

7 t

i

.4 i Page 64.of'96 l

t

  • i e

,..+,y.--,.-iw a ,.4_,., .~.; , , _ , _ , . . , _ , ,.,mm._,, , . , _ _ _ , , _ . , , , y,,y.., , , ,. , , , . ,,, ,,, ..g, , ,- , y*N,*f,y_' y

.ss'.

s ,

t v.

- 4.

F 4

a

,f r

. (4

- - 2

'f

.. .. . t

. t P

s t

1 t

o p

4 1

O . .

.L

. . . .,P 1

i 1

t i

0 1

F

.V i

! t.

. t, i f t

1 LO; ,

F f

,4 r

.,- . t t

t Page 65,of 96' 'l L

.'g.,

gs '. . s I'- t t V I- - - - - _ ....w,.'..-~.-.%.4..,,...,,,,.._,-..,.

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

, . , ~ , , , - , , , , , , . , . .. --m - . , , . ~ , . . .

f

-APPENDIX IC O

- SOURCE UPDATER COMMANDS

~

-O l . .. - -

j i

1 0 1 1

1 Page 60 of 96

  1. #~~~' '

C- l_L*J."L 2. .u. 21._d t hunLtant. n __x. . _.m t2 m_ _ _.m. .

4

'The following-is a description.of the six update commands which can be used-O in the Source u n deter c-end me to update a source me.

Note thet eu updates must be made.in order'of ascending sequence numbers.

~

~~~ ~17-~ INSERT Command -

The INSERT Command is used to insert one or more new statements ~into an existirig-source program. The records following the INSERT Command ]

are inserted in'the new master entil 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 If, before 'seqnbr' is found a sequence

~

state [nents are to be~ inserted.

number..is detected on the old master that is larger than 'segnbr' or an l' EOF /E0M or the ending string is detected, the error message:

' SEQUENCE NUMBER NOT FOUND is printed on the line printer and the operation is aborted.

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

,. -# ' INSERT XXX00150

~

- statement #1 -

- statement #2 -

/*

!O' -

Page.67 of 96

~

2. DELETE' Command

.01 The DELETE Command-provides the capability to delete a single statement or multiple statements;from the input source file. The format of the:

command isf ,

DELETE se'qnrl, 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,. statements between

~

'segnrl' and segnr2' inclusively are deleted.

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

'segnr2', the error message: .

i SEQ NDR ,NOT FOUND for 'segnrl' or the error message: - ' '

I SECOND SEQNBR NOT FOUND for 'segnr2' is printed on the-line printer. The operation is aborted when a sequence number is not found. _

.?

To delete statements AAA01010 through AAA01500,'the following command is p_ laced _in the L.ucce Updater command file DELETE AAA01010, AAA01500 -

O

. Page 68 of 96

= r,

_..-.-_....m.~.;_ ,

..-!..  : 7 a , -

. -7., ~ .c , e. , . . . . , . _ , , ~ _ . . - . . -

m.

- _ _ - _ _ - _ . _ =

l..

. i

3. MODIFY Command 0

The. MODIFY Command is used to delete a single statement and insert a-

- new statement in _its place. The format of the command is:

~

. MODIFY'pegnor -

wherei'segnbr' indicates the sequence number of the statement to be

~

modified. If the sequence number cannot be found the error message:

SEQ NBR,NOT FOUND is printed on the line. printer.

To use the MODIFY command to delete statement. AAA01000 and replace it with a new st'atement, the following sequence must be placed in the Sourci Updater command file:

O MODIFY AAA01000 _

- new st.atement -

4. REPLACE Command The REPLACE Command.is used.to both modify a specified statement and insert statement . thereafter. The femat of the command is:

~

REPLACE segnbr

_, wher.e.segnbr indicates the sequence number of the statement where the 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 Columns 1 and 2.

O
  • ~

Page 69 of 96 L _. _ . _ . _ _ _ _ _ . _ . . . . . __

_ _ . _ . _ _ _ ._ a

~.

5. SELECT Command O

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 segnumb1 Li.ie 2 segnumb2 Line.3 segnumb3 L

{

l

/* .

where sconurabl, segnumb2, etc. start at position 73 in an 80 byte  :

record. When a sequence number is found in the old master that matches the sequence number specified, then a ' modify' is in effect; Q

if a sequence number is found 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 UPDATE mode. If the old master file has l .~" not~reache~d the 'ending string' specified in the Update command or EOF /E0M,.this command' copies the rest o'f tha old master until the I 'ending string' or EOF /E0M onto the new master.

.O.

Page 70 of.96

APPENDIX 10 O Automated cec Integration 4

O

. ,u . ,

O

~ .

Page 71 of 96 t=______ *<s'a 4 .-n. amg,_ _ _

,g_;_. .. __

, , _. .- 's 1

APPENDIX-10 (O Automated CPC Integration A) Portions of the procedures needed to perform an integration.of a CPC-system on disc have been automated. While the' Attachments describe the applicatico of these automated-procedures, this Appendix outlines I

the operation of specific modules.

The-documentation covers three functional procedures. The CPC Log B)

- 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. The CPC Integration procedure produces a magnetic. tape with the necessary object files, in the correct order, for subsequent final integration at the CPC Support System. It also prints the steps to be performed at the Support System in order to create an absolute load mcdule. The CPC Label procedure will scan a magnetic tape, such as ,

~

i that produced by the Integration procedure, and list the object file labels contained on it. This is useful for identifying the contents' l of magnetic tapes when the complete integration process does not occur l

l at one time. A list of program, file name, and object file label is provided in Figure 1.4-6. .

z O

- Page 72 of 96

i l

CPCLOGPT. CSS t~'

U).

Purpose:

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

O ~

t W'

_se e .

e O

Page 73 of 96 t

  • a CPCLOGPT o i

Purpose:

Read the. log file on LU 5 and produce a report on LU 6.

.m e

  • .a..,.--

O _

^

L 1 -

l l

.Oa l

Page 74 of 96

r h CPCINT. CSS

.0L

Purpose:

Output the object files needed to integrate a given CPC program, and print further instructions.

~ _

O

^

i 4

l l

l

.a-O- -

~

.Page 75 of 96'

l l

O

~,. --

Pa e 76 of 96 s .-

CPCINT

,]1 i

Purpose:

Read LU 10 for-the name'of the program to be integrated. . Find- J,

'this'name~in_the. directory file on LU 12, and obtain the names of

--othe$filestobeincludedintheintegration,andthenameof the' instruction file. , Create a CSS file to copy the needed object files and print the instructions.

- I O -

w.

l O

Page 77 of 96

s:<- . .

O -

N e

O -

m l

l O

~

- .Page 78 of 96

~ ' - -- ---- __

rP l

. CPCCOPYB. CSS- 1

O

Purpose:

. Copy an. object file of' record: length 108..

'l l

m O .

LOL

" ~'

Page 79 of 96

$ ??" .Y*.  ? * * - _

- . _t 2:LL_--_.__.-.--.:- .y 42. _.h.u-.__=_xu --__s_-._----._.--_.___._--_.___-------------___-__ -

7 W

f

- t,

. l.

' CPCLABEL. CSS.

.m 4.) .

i

Purpose:

' Print a' list of 16 bit object labels from a' magnetic tape contain.ing 16 bit' object modules.

+

J.* .

h

(

0 -

- i f

l i ..

I.

i i.

l.

l

-,._ [

7

. Page 80 of'96 ,

.t wa -ie'. . . . = * ~ , - . . , - .e'--.,r = = e w e' e,e --'#-#*VT*Fe"**W+***'NC"*~-**4

1 I

APPENDIX lE l O Periodic Test oisc ceneration  !

O -

i l

1 -

O

- Page 81 of 96

,y ,,,.. .- ,, -. . , - ve, , , , -%, ,--

. ,, - ~

._ ,.+,sa, APPENDIX lE O- eeriodic Test-.oisc ceneration - Tape. creation  !

0

Purpose:

To create a magnetic tape bac'kup of a: project disc, for purposes of generating a Periodic Test disc. _ _

~

l O -

3 -

N V

l.

6-

~

, Page 82 of 96

l

% 1 1

1

- _ .t w

4 1 -

i 1

i

\

l 1

O Page 83 of 96 e

  1. f

,W F Periodic Test Disc Generation -' Tape Restoration

Purpose:

- To create a magnetic tape containing the CPC system object modules

- by reassembling from a backup. tape.

l O -

~

. . . ~.: ~. ,

.i 4

0 Page 84 of 96

I

. ... 1

. o.

il

'O l

4 4

0 -

P

~

  • Page 85 of 96 4 ., .-. . - ,. - - - - . . - . . ,, ,_ ,--.y.,. . , , , ., .,..%,, . , - . - - - , _,,.yy3,.,, ...-..-,....,-,-.,w.----, ,-.yy,-.-y

.. = - .. ... .- -, - _ . .

4* ,g Periodic Test Disc Generation - Disc Integration-O

Purpose:

To generate a' Periodic Test disc from a reference disc and object modules produced by the Tape Restoration process.

~

OL

'I h.:.

~

I-

-u. (~) -. .,

t Page 86 of 96-t

  • 5

. . . , - .._-....._.;_....-_-_., . .a . .~.--_._.-..-....:-,....-2._._.,,-.._,.. - _ . ~ .

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

h

__ i i

O O

.+

O Page 87-of 96 I - - - _ - - - _

.m a

J .

v i .

i l .

O -

Page 88 of 96 F1 M 4 * "' . , , , ,

y ... . . .

lu' ., t ...  !.

c

'.' J i

' 2. 0 PROJECT DISC GENERATION PROCEDURE- ]

l

.r}

2.1 PURPOSE-Thehur' pose.ofSection2.0istopresenttheproceduresrequired to generate a new project disc from the generic source disc.

r

2.2 REFERENCES

~ _ .

~

2.2.1 Series 40 Disc Drive Maintenance Manual Diablo Systems Inc.,

-Publication No. 81601 2.2.2 OS/32 MT Operator's. Reference Mariual, Interda'ta. Inc. , Publication

- Number 29-574,-Section 7.2.

_f - - - ,

2.2.3 Common D.isc Test / Formatter Program, Interdata Inc., Publication -

~

Number 06-173. -

4

-2.2.4 OS/32 MT Operator's. Reference Manual, Interdata Inc., Publication 1 Number 29-574, Section 7.3.

2. 2. 5; 0S/32 MT Operator's Reference Manual, Interdata Inc., Publication

, .,__..- - Number 29 _574, Section 7.5.5.

e w..

. x. , . . - -

p g

-m_a w uw rg t s. e p 3_<w --+em+ *-'W

~~

  • ~ ~

2.3 PROJECT DISC GENERATION

(~)

v 1 l

The CPC Project Disc Generation Checklist (Attachment 2.3-1) l outlines the procedure to be used in the generation of a new project ~ disc. A new disc'is formatted and initialized using the

. Common Disc Formatter program (Appendix 2-A), the Disc Initializer (Reference 2.2.2), and the Disc Integrity Check (Reference 2.2.4).

The source files on the generic-disc are then moved to source files on the new project disc. This is done using the command

" PROJECT" (Appendix 2-A).

A reference disc is generated for the project by copying the generic reference disc using the CPC Disc Duplicaticn Procedure

(]) - (Attachment 1.4-3).

l .

l i

3 -

~

b

'J

~~

Page 90 of 96

Attachment 2.3 .

O CPC PROJECT DISC GENERATION CHECKLIST

~~

1 . Mount the new disc onto USR2 (Reference 2.2.1).

l 2' Format the disc-(if it hasn't already been formatted) (Reference'2.2.3) a) Mount the Multimedia Diagnostic _ Tape on the magnetic tape drive.

b) Load the 50 sequence through the hexadecimal panel:

Address Value Enter on Hexadecimal Panel 30 0000 DTA 30 ADD - DTA 0 WRT 32 0000 ,

WRT

~

34 0000 WRT O- 36 0050 ,

DTA 50 WRT 50 D50,0 DTA 50 ADD DTA 0500 WRT

~~

52 00CF- DTA CF- WRT.

~

54 4300 DTA 4300 WRT 56 0080 DTA 80 WRT-78 85A1 DTA 78 ADD DTA 85A1 WRT 7A 0000 DTA 0 WRT

. 70 0000 WRT 7E . 0001 ,

DTA 1 WRT LO

~. Page 91 of 96

~

- -w - -;'. . _ _ , ,.ad

t

. - . (

~

i Attachment'2.3-1 (Cont.)

. C- CPC PROJECT DISC GENERATION CHECKLIST ,

c) Start the loader: _

~ '. DTA 30 ADD RUN a.

- FFFF should be displayed on the hex panel, d) Load the Formatter program sequence number:

DTA 412 RUN e) Place the format switch on the disc controller in the "FMT"  ;

position.

f) Make.sure the protect' light for USR2 is off g' Start the Disc Formatter Program:

DTA- A00 ADD RUN

~

h) Enter the following Formatter commands:

bs

~

LOCYL 0 _

HICYL 197

~

PACTYP 1 DISC 0N 86 TFILE 1 FILE 2 TRKDEN 1 DEFSEC 1

- .FMREAD 1 .

TIMCON 140 -

RUN

.'OT

~ ~ ~

^

,} . _

Page 92 of 96

_ _ - _m.2,,wg g gamp

  • a-e*n-- * - .,-r,_ _

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

Attachment 2.3-1 (Cont.)

O- CPC PROJECT DISC GENERATION CHECKLIST ,

O

?

3 Initialize the oist: (Reference 2.2r2) ,

a) Mark SYS1 on: ..

MARK SYS1: ON, PROTECT

?

b) Load the Disc Initializer Utility:

~

LOAD .BG,DISCINIT, 12

- TASK- .BG

- c) Mark all discs off:

MARK USR1: , 0FF MARK USR2: , 0FF MARK SYS1: , 0FF .

Q -

MARK SYS2: , 0FF d) Start the program:

START, DISC =USR2:,. VOLUME = volume.name, CLEAR, BLOCK =64/203 Volume name is a four character mne$nonic for the project.

4 Check the integrity of the disc (Reference 2.2.4).

a) Load the disc check utility; f MARK SYS1:, ON, PROTECT LOAD .BG,DISCHECK, 12

~ ~

.~"- TASK.BG -

1 b) Mark the disc off:

MARK USR2: , 0FF c) Start the program:

.< ], .

START, USR2:, PR:

Page'93 of 96

' ' ~

e w w wr,nr y er- < > v + r# v w e ==W+-s wr' r w --

tt v w #f ,a e reaJ <ct 2--.* + e v4 . -, wv9 -O- ~S

'% e < r

Attachment 2.3-1 (Cont.)

CPC PROJECT DISC GENERATION CHECKLIST 5 Move all neeessary-files to the project disc by entering:

PROJECT (project name)

This procedure is detailed in Appendix 2-A.

O v

.y.

t Page 94 of 96

~ ~~

' ' ~

t APPENDIX 2A This procedure describes the generation of a project disc from a generic disc. The project mnemonic and disc volume share the same name for identification purposes. The generic software is assumed to reside on volume CPC1.

To create a project disc, all applicable files are read from the generic disc and written to the project disc. This process is invoked as follows:

1) MARK USRl:,0N, PROTECT Put the generic disc on-line ,

in device USR1:

2) MARK USR2:,0N Put the project disc on-line

(',') . in device USR2:

s

3) Enter the command PROJECT proj Where proj is the four character project mnemonic Some errors which may occur are:
    • VOLUME proj IS NOT ON-LINE **

The disc volume whose name is the project mnemonic is not on-line.

    • GENERIC DISC VOLUME CPC1 IS NOT ON-LINE **

. ; .: The di'sc v61ume containing the generic files is not on-line.

O

%/

e

  • ~

~

~

Page 95 of 96

. v ,,w. .. , , g -- e

e ASSIGil ERROR FILE filename E) -

The file called filename is already on the project disc. This disc should have been empty. o Other errors"are possible; refer to Reference 2.2.5. _

4) When the process is completed, the message ** CPC PROJECT DISC proj CREATED ** is displayed.

4 o ~

V

~

'w/

~~

Page 96 of 96

..

Retrieved from "https://kanterella.com/w/index.php?title=ML20147F298&oldid=3363309"