Text

CPC Protection Algorithm,Software Change Procedure, Suppl 1-NP,Revision 1.Nonproprietary Version of C-E Rept
	ML20037A292
Person / Time
Site:	Arkansas Nuclear
Issue date:	01/05/1979
From:	; ARKANSAS POWER & LIGHT CO.
To:	;
Shared Package
ML19289A134	List: ML20037A287; ML20037A289; ML20037A292;
References
	CEN-039(A)-NP, CEN-039(A)-NP-S01R01, CEN-39(A)-NP, CEN-39(A)-NP-S1R1, NUDOCS 7907120606
	Download: ML20037A292 (96)
	v • d • e

lO ARKAllSAS flVCLEAR 0:lE - UIIIT 2 i

DOCKET 50-368 CErl-39(A)-flP i

SUPPLEf tEllT 1-!!P REVISI0tl 01 CPC PROTECTIO:t ALG0RITil'1 SOFTWARE CHA!!GE PROCEDURE SUPPLEf1EilT O

JAflUARY 5, 1979 l

Combustion Engineering, Inc.

fluclear Power Systems Power Systems Group Windsor, Connecticut O

Revision 01 79071544em

/

~

s LEGA1. Il0TICE This report 1:as prepared as an acceunt of iark sponsored by Ctr.bustion Engir.eering, Inc. i!either Combustica Engineering r.or any person acting on its behalf:

^/,

a.

liakes Ony starrar.ty or representation, expres:

p or implied ir.clucing the.:arranties of fitness for a particuler pur::se or nerchentability,. tith respect to the accuracy, cer.:oleten. ss, or usefulness of the 4

' infonaatica ccn'. air.ed in this report, or that the use of any infoma*.icn, apuaratus, nethod, or process dis-closed ir, this re;; ort cay not infringe privately c.!ned rights; or b.

Assur.cs cny liabilities with respect to the

~

use of, or for damages resultir.; frca the use of, any infon:ation, appertus, method or process disclosed in this report.

e g

L__-)'

l

's Rev. 01 e

J

(-,g l

TABLE OF CONTEtiTS Section Title Page rio.

1.0 Il1PLEMENTATION OF SOFTWARE CHANGES 6

1.1 PURPOSE 6

1.2 REFEREt.CES 6

1.3 IMPLEMEllTATICN OF AN SCR 7

1.3.1 Prena, ration of Software Chance Packace 7

1.3.2 Det. ion of sort..are tnar.aas 8

1.3.3 codino of Soft are channes 9

1.3.4 lyp_lementation anu Assenaiy of Software Chances 10 1.3.5 Debuo et sottvare Chances 11 1.4 QUAlliY ASSUKLO 00JECi DISC GEliERATIOil PROCEDURE 20 1.4.1 Input 20 1.4.2 Out;mt 20 1.4.3 Proct 2nres 21 1.4.4 Generation of f' aster Test Disc 23 1.4.5

'Generition or Discs for On-Line

~

Operation 23 3

1.5 C0!ilROL OF QUALITY RECORDS 47

)

('- ~

2.0 PROJECT DISC GEtiERAT10?! PPCCEDURE 89 2.1 PURPOSE 89 2.2 REFEREliCES 89 2.3 PROJECT DISC GEriERATI0ti 90 LIST OF APPENDICES Appendix Title Page flo.

lA Software Organization and Design Considerations 48 18 CSS Files 58 1C Source Updater Comm.:nds 60 10 Automated CPC Integration 71 lE Periodic Test Disc Generation 81 2A Project Disc Generation 95 I

)

s;

':e'. J:

Pace 3 c' ?G

l TABLE OF CONTEllTS (Cont.)

J i

LIST OF FIGURES 1

Figure Title Page No.

4 l

1.3-1 Change Applicability Form 14 1.4-1 Data Flow for Disc Generation 25 1.4-2 CPC Disc Generation tog 26 1.4-3 CPC System 38 1.4-4 CEAC System 40 j

1.4-5 CPC Test System 42 1.4-6 CPC Files 44 1A-1 CPC Program Title Block 57 i

LIST OF TABLES Table Title Page No._

l.3-1 DNBR/LPD Calculator System 15

(

LIST OF ATTACHMENTS Attachment Title Page No.

1.3-1 CPC Source Update Checklist for Batch Processing 12 1.4-1 CPC Object Tape Generation 29 1.4-2 CPC Disc Generation 31 1.4-3 CPC Disc Duplication 37 2.3-1 CPC Project Disc Generation Checklist 91 Rev. 01 m

ABSTRACT This document presents procedures to be followed during the process of implementation of modifications to the CPC/CEAC software.

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.

7,

(

)

RJ

(

)

v qcy, 71 Page 5 of 95

g 1.0

_ IMPLEMENTATION OF SOFTWARE CHANGES 1.1 PURPOSE The purpose of Section 1.0 is to present the procedures required 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.

1.2 REFERENCES

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

1.2.2 Quality Assurance of Design Manual for C-E Nuclear Power Systems 1.2.3 Series 40 Disc Drive Maintenance Manual, Diablo Systems Incorporated, Publication No. 81601 1.2.4 CPC Disc Utility Program User's Manual 1.2.5 OS/32 MT Operator's Reference Manual, Inten data l'ublication No.29-574, Section 7.5 0

1.2.6 ANSI Standard Flowcharting Symbols and Their Use in Information Processing, X.35.

1.3 IMPLEliENTATION OF AN SCR 1.3.1 Preparation of Software Change Package When an SCR is ready for implementation, the iaplementor 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 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 imn19monta" The Software Change Package will be maintained by the implementor until the change has been implemented and tested.

The package will then be returned to the originator for review.

Upon comple-tion of his review, the originator will transmit the package to the cognizant engineer who will then file the Software Change I

Package in the CPC design file.

Q Page 7 of 96 aev, 01

1.3.2 Design of Software changes After preparing the Software Change Package, the engineer will design and implement the required change as follows:

1)

The most recent working copy of the affected calculation descriptions, flowcnarts, input / output lists, variable lists, EQU 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

(

i y'

listings being used are the latest version, the date and tiriie on the listing will be checked against the latest date and time posted for that listing in the automated CPC log CPCLOG.DAT.

Also, when a new listing is created, 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,?.l.

4)

If the change affects scaled-fixed point coding, the appropriate scaling recorded calculations will be revised accordingly.

\\__,/

i Rev. 01 Page 8 of 95

The software change will be designed ti be consistent with Appendix O

lA of this document entitled " Software Organization and Design Considerations."

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 Software Changes The CPC Source Update Checklist (Attachment 1.3-1) outlines the procedure to be used in the coding, implementation, and ast.mbly of software changes.

The required coding changes, as marked on the assembly listings, will be converted into d series of Source Updater Utility program commands (Appendix 1-C) and punched on cards in order of ascending sequence numbers.

The last cards l

l the deck must be the "EiibuP" card followed by a "/&" card.

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, b

which result in another updating of this source file, the V

revision number of the source file is incremented by 0.01.

Rev. 01 Page ? c' 95

2)

An "SCR Implementation Record" line will be inserted into the source file.

This line is a comment of the form:

REV n.nn, SCRs:

i,j,k,...

where:

n.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 sof tware change will be irrplemented in the appropriate source file using the UPDATE command (Appendix 1B).

The appropriate The project disc is mounted (Reference 1.2.3) and 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 will be attached to the software change package.

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

l The procedure for using the IllITIAL command is the same as the

" INITIAL" Source Update procedure with the following exceptions.

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

Rev. 01 Page 10 of 96

I

1.3.5 Debuo of Software Channe

'^(j(j

~

To conplete a Sof tware 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 The revision change package, will be modified as required.

level, however, will not be incremented for changes to correct errors in the SCR impicmentation uncovered during debug testing.

When the object codule has been fully debugged, the implementor will complete the change package by attaching the debug test cases, filling in the applicable columns in the Change Applicability

.s

[\\ /

Form and initialing and dating the SCR.

The implementor will

\\

then return the change package to the originator and will initial The originator will review the change pack-and date the SCR Log.

The cog-age and transmit the package to the cognizant engineer.

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

(n) v Page 11 of SG 7ev. c1 m

r f

!.3-1 C1 CPC Source Update Checklist for Batch Processing 1)

Punch the Source Update command deck a)

Increment revision level on " PROG" card b)

Add "SCR-Implementation Record" line c)

Place commands in order of ascending sequence numbers i

d)

"ENDUP" card followed by a "/&" card are last cards in command l

l deck

2) Mount the appropriate project disc (Reference 1.2.3) t l'

i-

3) Mark disc:,0N j

where 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) f a)

If error occurs in execution of Source' Updater commands, enter

..BG;

$ CLEAR; CANCEL.

The run is aborted.

Correct the deck

.[

{

and continue at step 4.

6) Debug the software change l

s.

i

7) Attach the Source Updater command listings to the software change i

package

!\\

i

.Rev. 01 Page 12 of 96

!.3-1 (Cont.)

CPC Source Update Checklist for Batch Processing Initial and date the appropriate columns in the Change Applicability 8) d form (Figure 1.3-1) i l

l 9)

Initial and date the SCR Log i

1 i

k O

\\.

Rev. 01 Page 13 cf 96 l

.. ~..

Figure 1,3-1

, Sheet of Date:__

Plant:

Initial $: __

CitAt(GE APPLICABILITY FORii DlBR/LPD CALCULATOR SYSTEl1 Change Ccr.pletion Date and initials Software Item Listing Source Object Specification Applicable O

G 6

_E_---------------_

Rev. 01

1 i

t, A

i E'

Table 1.3-1 t

DNBR/LPD CALCULATOR SYSTEM 1

(

No.

Software Item I

1 1

N l

i 1

1 1

l r

2 i.

i

).

3 1

i-j 4

i t

4 5

i t

i 6

4 7

~ 8 4

i i

t j

r j

1 l

l i

i 9

1 10 i

t i

i i

11 12 1

ii 1

i i_.

l Rev. 01 Page 15 of 96 i

+

w.

.____._,-mw,,e+,_

e-----

_---~~e,~

e--

t.

i I

e Table 1.3-1 (Cont.)

Dl48R/LPD CALCULATOR SYSTEM i

l l

No.

Software Item l

l l

i 13 14 i

t 15 16~

l I

17 18 l

19

(

20 21 22 i

23 l

24 f

25-i i

26 r

27 i

i 28 L

,Rev. 01 Page 16 of 96 4

c-.

Tabic 1.3-1 (Cont.)

(

DiBR/LPD CALCULATOR SYSTEM No.

Software Item 29 30 31 32 33 34 35 36 37 38 Rev. 01 Page 17 of 96

i.

i k

1 i

f I.

{

Table 1.3-1 (Cont.)

j DNBR/LPD CALCULATOR SYSTEM i

1 i

No.

Software Item s

4 i

1

}

39 4

1 40 41 42 43 I

44 45 4

1 i

i

)

46 47 l

I i

l I

i i

48 l

l 49 i

~

t I-i Rev. 01 Page 18 of 96 L -

1 i.

1 i

Tabic 1.3-1 (Cont.)

{

DNBR/LPD CALCULATOR SYSTEM No.

Software Item t.

{i 50 51 i

52 l

53 i

i I

i 1

54 55 F

j --

56 l

57 I

58 l

1 I

l i

I i

1 i

Rev. 01 Page 19 of 96

1.4

. QUALITY ASSURED OBJECT DISC GENERATION PROCEDURE

~

This procedure applies to the integration of object modules and the generation

~f load modules on flexible discs.

Portions of r

this procedure have been automated as described below.

Details of the automated aspects are outlined in Appendix ID.'

i 1.4.1 Input k

1 The input to this procedure shall be from two sources:

1)

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

t.

)

2)

-Quality Assured object code from a previously generated and tested reference disc.

4 1.4.2 Output i

The output of this procedure shall be a core image load module on mass storage media.

The load module shall be tested as required by Reference 1.2.1.

i O t

Rev. 01 Page 20 of 96 I._,-._.,_...-.__

1.4.3 Procedures V

lhe core Inage inad module will be written to disc _in 4 KB blocks.

Each block will 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 overlay.

The CPC Object Tape Generation procedure (Attachment 1.4.1) is used to load the proper object modules, in correct sequence, cnto a magnetic tape.

It also provides.a guide to creating the abso-lute load module on the CPC Support System.

O)

The CPC Disc Generation procedure (Attachment 1.4.2) is used to g

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 All paragraphs describe the processes involved in this figure.

tracks of a new disc will be initialized to all zeroes before any programs are written to the disc.

Source files shall be modified and assembled on the Software Development System (Inte. data 7/32) according to the procedures described in Section 1.3 of this docu.uent to produce one object module per source file on a project disc.

The object modules will be copied onto maOnetic tape in the order which they will be Rev. 01 Page 21 of 96

loaded in core. Magnetic Tape is used as it is the only medium common to the Sof tware Development System and the CPC Support System. The object module of any program containing external ref-erences or entry points (i.e., containing CAL EXTRf1 or ErlTRY state-ments) must be linked to the object r.todules of all programs resolv-ing these references using the Interdata Library Loader.

To accom-plish this, these object modules must be' contiguous on the tape.

This is assured by use of the CPC Object Tape Generation Procedure.

Using the Library Loader on the CPC 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).

Ak)

The load module on magnetic tape and the core iuage on reference disc shall then be i..arged onto a target disc using the CPC Disc Generation Procedure.

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 11 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 above reference shall become the new reference disc for the sof tware system.

Page 22 of 96 Rev. 01

1.4.4

.Generationof.jiasterTestDisc Once a reference disc has been established for the software system a master test disc may be generated. This is accomplished by restoring 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 1E.

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

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 O

O verify feature of CPCDUP.

If differences are encountered the error in the test disc will be determined by 'exanining the contents of the dis-similar tracks and matching the contents to the object code on the 1

final listing of the program contained on that track.

The error will i

be corrected and the faulty disc will be regenerated in accordance with all applicable procedures for test disc generation and testing.

1.4.5 Generation of Discs for On-Line Operation Discs for shipment to customer sites for on-line operation will n

be generated using the duplicate and verify features of the CPC v

Disc Utility. Program (Reference 1.2.4).

These discs will be W.

Pase 23 of 96

?

duplicated from the system reference disc which will be maintained i

by the Software Design group.

The test discs will be similarly.

f generated by' duplicating the master test disc generated above.

i l

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

The procedure for duplicating a disc is found in Attachment i

1.4.3.

t I

l i

(

Page 24 of 9G Rev, 01 l

figure 1.4-1 DATA Flu.! FO!! I:1SC CIG!!T:hTIO:!

l fiOPR?A!G: Di:Vl:LOPMi't:T SYSTEM v'

ASSEi:SLMt IIU3 ED so'.;;icg CAI. 32 IllT h - 1 Olt IATE b,OWT i

l f

} ILEs

~~'s l

OS/32KP y

10 DULL:S

/

~ /

v

/

. 7

/

i

/

/ CPC SU?}O!iT SYSTEM l

/

7,

i. t Ill:VISI:p LII'.!!AltY I/yADER MAD f

OBJi:01'

[/..

LIILLI:11 6 OI! T1.T:01

_ __ 2>

VODULi; V.OI;UI2.S 03/16!a'2

d

/

x

/

~

/

i

/

CPC SUPP01 T SYCTEM f /.

tjp.,

t OS/3 6M1'2

5. IlEFF -i!CE IDAD t

MODULE a;.'

CPC DUP DISC t

-J 1

la:rwr:4ct:

D1"C i

2 Rev. 01 Page 25 of 92

.--w...s-.-e-c.e.,~.4,..,,.,..e,m,.,.,r-,,-...,,-_,---,,---,y.,--,m.myr w,,

,p,e..,._y_.,,,p.,

,_,.,m,.._.g,

.,,-.,,_.,,yp--.-%--.,

,y,,,w-.e.,,.

yy*_.._-._--ymn--,.e,-

.I i

(

)

Figure 1.4-2 CPC Disc Generation Log -1 i.

Track Software Revision Date Engineer s

0 I

1

/

i 1

i l

2 i,

3 i

4 5

6 i

i i

7 8

9 N

l i 10 11 i

12.

13 14 15 16 17 18 19 20 l

5 i

Rev. 01-Page 26 of ?S r *w==--ww -v 7www-m r-ww-er=w, m _

ew--

= = = = = = = - -

-*e----**--**v--

- - =

s a

l Figure 1.4-2 (Cont.)

l[

CPC Disc Generation Log -2 i

' Revision Date Engineer Track Software t,

21 i

\\~

22 23 24 25 26 i

27 i

28 29 1

30 31 32 33' 34 35 36 37 38 39 40 41 O

42 43 Rev. 01 Page 27 of 96

~

Figure 1.4-2 (Cont.)

CPC Disc Generation Log -3 Track Software Revision Date Engineer 44 45 46 47 48.

49 50 51 52 O

sa

(

54 55 56.'

57 58 59 60 61 62 63 O

'Rev, 01 Page 28'of 96 I

I l

l.4-1 i'

CPC Object Tape Generation i

Purpose:

To generate a magnetic tape containing the correct number and sequence of object modules in order to generate a new reference disc.

p 1

I System Configuration:

l l

4

?

Procedure:

I i

l i

. t i

Rev. 01

~

Page 29 of 96

.4-1 (Cont.)

CPC Object Tape Generation i

l O

O Rev. 01 Page 30 of 96

p t

il' t.4-2 I

(

CPC Disc Generation p

i

Purpose:

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

4 l

i System Configuration:

r i

k 1

l 1

i l

1 i

i i

1 e

i t

f Procedure:

4 i

i i

i t

l i

1 f

'}.

i i.

i j

i-i

!l

{

Rev. 01 Page 31 of 96 i

L.-..

~

_._ _. _ _ _ 3 I

i

+

i

.4-2 (Cont.)

'D CPC Disc Generation 1

1 i

s l

+

1 i

i

(

1 J

i j

1 l

4 i

i!G l

i i

1 i

t i

i l

e i

I i

f i

l 1

e i

r i

i k

4 i

i l

i

,4 i

4 Rev. 01 Page 32 of 95 i

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

J i.

1 1

r t.4-2 (Cont.)

i j

CPC Disc Generation l

t I

{

I i

=

?

i i

l, 4

1 i

(

1 i

l I

I 1

i 1

I t

I i

.i i

i l

t

(

l i

i i

i e

i Rev. 01 Page 33 of 96

Attachtnent 1.4-2 (Cont.)

CFC Disc Generation O<

O Rev. 01 Page 34 of 96

j-l J~

{.4-2 (Cont.)

CPC Disc Generation i.

I

~

l i

1

!5.

i

).

i l

4 ii i

1 6

I i

i l

Rev. 01 PaDe 35 of 96

I l

i l

t i

i t.4-2 (Cont.)

i j

CPC Disc Generation I

t

(

i

+

t i

i i

I l

(

l 1

L9 i

l I

f b

2 l

l l

j.

i i

i 4

i i

1 l

1 1j.

r P

e i

i -

I l

t

.b t

b t

Rev. 01-Page 36 of 96

i i

4 s.

j 1.4-3 i

CPC Disc Duplication 1

t if

Purpose:

To duplicate a. disc using CPCDUP.

t I

1 l

r i

i f

.}

I O

i t

i i

I i

-I l

I O

i Rev. 01 Page 37 of 96

- i

i Figure 1.4-3 CPC System -1 Contents Core Locations Disc Track Memory Block 1

d s

i l

Rev. 01 Page 38 of 96

Figure 1.4-3 (Cont.)

CPC System -2 Contents Core Locations Disc Track Memory Block O

i I

i i

}

i i

l I

t!O Rev. 01 Page 39 of 96

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

t

\\

i

(

1 i

I t

i l

Figure'1.4-4 1

i 4

p 4

CEAC System I

Contents Core locations Disc Track Memory Block j

l i

?

l I

i l

1 i

l

~

i i

s r

l I

l9 i

l 1

I 4

e i

I i

i l

l i

i t

I i

l i

1 a

\\@

l Rev. 01

'Page 40 of 96' i

l

_ ~,,

E i

t 1

4 i-i Figure 1.4-4 (Cont.)

l CEAC System 4

Contents Core Locations Disc Track tiemory Block 4

I t

E f

I l

l I

l i

I 5

1 l

l l

l t

Rev. 01 Page 41 of 96

i

\\

Figure 1.4-5 CPC Test System i

l l

Core Block Disc Track j

Contents

)

1 l

r 1

1 i

(-

1 l

1 i

j l

I i

1-1 i

t

+

1 s

i E

L f

i I

t.

i i

t t

i i

t 4

,i i

i 1

i t

?

4:.

t

+

1 l

Rev. 01 Page 42 of 96 i

.,,w..._____._.

=_.

figure 1.4-5 (Cont.)

(

CPC Test System i

Contents Core Block Disc Track 1

l i

i

\\

i l

I i

l I

i j

Rev. 01 -

1 Pa0e 43 of 96

Figure 1.4-6

([d CPC files -l flame Object Label File Name l

I O(N

~

Rev. 01 Page 44 of 96

i' i

Y l.

{

- i I

Figure 1.4-6 (Cont.)

l 1

4 i

CPC Files -2 t

l a

l Name Object label File Name 1

i

)

i l

2 i.

l i

- i I

~

t i

i i

i f

I i

i i

l i

.i I

i I

t l

i i'

l l

i 3

y L@

I i

~

I Rev, 01 Page 45 of SS 1

l I.

.- n..

e

Figure 1.4-6 (Cont.)

CPC Files -3 l

i l

Name Object tabel File llame O

t O

I!cv. 01 Page 46 of 96

C0ll1ROL Of QUALITY RECORDS

, q 1.5 b

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 e separate location from the master source files under controlled access and with suitable environmental provisions.

The duplicate will be generated whenever a new reference dfsc is sent to a project.

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 discs to be sent O

to the project.

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

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

magnetic tapes will be assigned to each disc.

The BACKUP utility (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.

G Rev. 01 Page 47 of 96

w n=.wmwm:ssw.

APPEliDIX 1A Software Organization and Design Considerations i

l

\\

O Rev. 01 Page 48 of 96

APPENDIX 1A SOFTWARE ORGANIZATION AND DESIGN CONSIDERATIONS 1A.0 To achieve modular, structured, and standardized software, several i

I constraints shall be adhered to in the design.

These constraints I

are intend J to allow modification to be performed with minimum I

impact and to simplify the testing of the software.

i 1A.1 SOFTWARE ORGANIZATION i

i 1A.1.1 Modular Strecture

{

~~

f

~~

J I

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

f Strict control of program-to program interface allows each program j

to be developed and tested in a stand-alone mode and to be integrated s

l intothesystematalatertime.[

O a

Rev. 01 Page 49 of 96

~ ' - '

l'

1 l

~

l 4

i -

I i

i i

4 3

i 1

i l

T 1

I 1

l i

1

}

I t

i r

i i

t i

1A.l.3 Data Base Structure r

i J,

To allow plant dependent data to be changed without irapacting the program code, application programs will be divided into two c.

separate assemblics. L i

~

\\

i f

itev. 01-Page 50 of 96 c

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

i Rev. 01 Page 51 of 96

lA.l.4 Timing and Processor Loading The design goal for the processor loading for all applications programs in the on-line sof tware syste is less than or equal to r-60 percent. L O

O Rev. 01 Page 52 of 9G

DESIGN CONSIDERATIONS AND DOCUMENTATION lA.2 (t

1A.2.1 Flow Charting Conventions 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.

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

[~\\

The program must adhere to Interdata CAL assembler conventions b,

/

1.

so that the program may be assembled with the CAL assembler at the current revision level.

Every line in the source file shall be identified by a 2.

The sequence sequence number in positions 73 through 80.

numbers shall be of the form:

ccennnnn where:

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

Rev 01 Page 53 of 96

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

Each program shall be organized into the following sections, i

3.

in the order listed below:

1

. Title Block (See Figure IA-1) j

-Entry Point Definition or External References

-Global Data Base References (EQUs)

-Main. Program I

-Program Modules

-Initialized Storage Definition I

-Scratch Storage Definition t

O i

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

The title block, however, is mandatory.

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

4.

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.

O

.Rev. 01

-Page 54 of 96

"i 1A.2.3 Comments 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 coda and data base.

lA.2.4 Arithmetic Fault Detection n/

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

\\

O g.-

Rev. 01 Page 55 of 96

f i

i l

i 1

l O

i I

I f

4, i

)

i I

t i

1-r i

o, f

l

]

1 i

l I

i I

L.

l 1

c i

1 i

i 1

f' t

6 l

i l

t l

\\

i l

Rev. 01 Pa0e 56 of 96 i

i s

- Mven.

..W

-e

-e~---**"--

.3

. fl..,s,...s

.le ;. 7_. in.,, 1. m.N *.., n. o.e)...rAe g l.',Mi l

~t

't

.' ' 6 ' + '.')

. ' 'U. N. t' s. 3, ; 7

%L,Cig'U{N[NINlNlN. h.-,...... _,Nl61;ftpfl[J,Li fJ [ i',

..)

s N l %. l % ' N g

( ) : D 'd g ' ;,D i )

t 5

l 4 o.t s ju.. i_.

lr,_[@ ;. i?. u.. >.. c. ' t p _.,i s,9 ;' >;'g,f,),t sj'y

.u 'a L.*a u.u u ;'.i.* ',i r. ':

')

y 's

) y &

u_

o.. i..s) ', u., y, v, s >, v.,. u.. v.,. t 1_ Lu l. >.' t> > u_ ' v..i.u. U.. d; _>..'.t.> I.V..g e.

,.t.i133 (., p ;O O ' i >. ' a ;O t s. ; ' 2 G.t ) pi,tij u 3 U. u o.JU I.U lty..

g t

u j u t u s u t s ' u j u I U u. O f(u i ~

2 f.

y V..uu i;.v. u V ju o i., 4 4;I i i, o o. o u :ts l u gt;10 W.i.;N A r:v Uunt, ? y 'Qrou o y-G U{io o

u i

u

_i_u_

_ u

.4_

T

__.,_.1,.. L, _ _ L, ;_..__.' _ t, y _

=

(

n.

_,_m,__,__

2 l

- tr1.-Qtn{-

r,-

(

t Ql !

l b

W Q

y' c_ r

-r r.a_

i m i

_1 y._ _ _. L-._

. v._i...

.,(-,,_

_ _.,,.., u __.

q _.i _ _. s... _ i...__r. _,...,..

+-

.__.4__,+

. y v_. 7... yi. J.

.. : y

_ _ qL._-lq.__ _

.,3g.i_(

._,<.-e.y..__

g. i p_

i a;

i

_x_

p gg_

L__7_ g_ __ g__._., __ _--pg r

_p._

.i.i f.._

A i '_

_ i

)

.~

E. -

I { < t1 _._,, _.i t.. l

_ L__.* _;

}._ I

!*l '- i. L __ N..N_I

- @.l_

...t'. l a.

_ e.__

O,. { _

,,g.'_,.._(l 1

0.:_.Ly

__'s,(, i_

I

-i l

i

t ' M'L

.. j I

7 k q

t i *;

---.i 1. -

9 i

I i 6

1

{ -.# _ _.1_A_tI p

.,c, i

_.f, I. _y_-

I _:_I'

. _i t. L. b l j l 14I i I tai;

4

A l

i j

. i g

n

(

)

4o I

e t

A__

- -.I _~ I _.;N_ 6._ d __ i 4.i_

4___.I _ i. - - i l l

I~

. -. b_.i 't_

W

.f l.>k_.i

-.i i 1 i

N i l

i mL p

i ;

I-i4 l l

W.I i l 1 'I

.i m 4

- i 6

I

- i.

1.,.1 I_-t

\\_.i_._.i _* A e l

l

.9 l

e I

~, -

t a

l

$i l

.,t.

i t_

6 e

i i I i

--,- ~

i i i

'ai AG s t i i i

)

6 iS 6 I

t I igO

(

i i

(.r

=

A

((4

i i i r @, l ',

P~'G. i~ i

. 's,

X,__4 i _ t i

i i l

l 4.[-,I '

i I

i i

g U

-.f Ie.,.

L f

l t i

,qi i

). i 4

i I I l 3 l

'..{ _f - i i e,

1; i

1

- I

% 10 4 li 5t

Q i l

t t

4 f

-y I

I I

e*

-fT w

I t

I i

i 4r"l

}

l g

gi i 7'I'~ M l

i 4

i t

e-_. y%-+i '.~t T

Vi~~~~ ~'

i I

i 1 I

-Q.

la\\'si i~~ iT._'lQ ~

~N.

.i

,wi l

g y

'ti i : :s. i I

I=.~

i i 4

I i

. n[IT ib.,. I i I l 1

j

(

l r

i l

l*...-

u'i

. A..._. __ I

- i -- i

,6 i&1 e

ty O

l l

1 i

-.m i I

i I )*-

l ':

e i l i i i i -7 g

is e i i i eI i

etI

'O i iVI I

i i ik l0 i i i is eli'4~iT d

ik i 4

'k i i

I a

l i Mi

(" ic I i i i t

i i M. i. - ji i

s i i t'. -_.

o l

l

?__g _-' _- l i i

.n i I TiW T d

i.

d I

t i ; i 9i i

.+i

' 'l.._v.'

_I'ti ei, g

~~

] i ! i, i. A.

i-i l

e I

i i i i

i l.i v. _i ~1-t.aj

-ti L,i s 4_

.__.__l__

,_,___i-i

. i

)

i. -

. f_. __..,.

-.d.t I i li' i l i d l 'a J

i i

.qi

,, n 6 i

.ti Ei

~3 ;

I I

e i o \\j

~E

'~

l -

.vii. _ -

~[~[~ 1 j I

{' ;i XT

-9 t--

y_

h. f~

i,gl-- Ii e

)

l i

l l l i

i j

}

g ;

f f -r i ';

4

4*

i1 i

v

._3 i

e 1

IQf

.wI

O, e

^'- "'~ I M ~ Jg r4 T 7 C e

' ;Ei iIj III l I i W l '2 Y

y, Q' I

i i I

C8 N

7 I I N,1 e d

T h

i r

+:E

.Ii

.i lI I

I I

{

l

{.

s__

e

___N_i~ i Mi t (. I T b i

lI+

5 g

i t

t J

NI _ 1 4;

.Q i 1

1 1

I i if #

1 Il 4 l}

(lYlT CD O

i

I i i i t~~ Q. ;

fi efI f

.e

((-~~'

I7'7-~ M.~_~_I si 2

cc A'

< !N.LZ At

'O i

l i 1 6

s,f Ii i i 4 i u.

c.

i 1 I,/- l 'E~

'. i i

i,

I e

1 i i 7f,,i-~ II I. I-l l

O e.

(._ i_...

l 1 i t/) :-.f~l iAi S

1 l d_E I._._.

+

g

~

t j i.

n_

%.. i Q _,#

s.U_j-lI i li

.s 1

i

,. A I,

_r r-p i

f,N I i

i i

I t l i.,L, l

} } l.

. i I -.! A'-

r.

l --

i t

- ' __ ! _P i '.

14 t

i t

..- O e.. _. p__.'4, __i i iV i 1

i _:4, e

[_l I

- I i - A..

2

[

' i 1 ?*

%i

4 I I II --i

.O t2_,__

f e

r a

_ 3, - I e

I!

' I l '.i

(

I i4I l'b l.

i i ~

-Q:

i:4 s.

l!I If ~ l'I.'r.N' 5-__

p O

t. i l 6A.

Q~ f..

(

l I

f KIWI~~i'.

lti II 1)~

-_ i i ff70 i

i T~ i

.___ _{[

I s T(f 4 i i n

t i 1

!ka ] -,,

t 1f

%3,,.~

l 4

al i f'~ i

.Q-ed di

'l i i tI{

l I

i k_' ___' 3I III I!h. $

l ! kI if l h94 DI Q:

Ri_

1_

II Ili I f 3.. I%

'M_T.

O{

tI'

8 11 - !

n u 4

i ;Ql t i 14

't t II,. 5 NI t

0 i ~ M. h...c _4' _j.M. i

.N I I

,_cu.q s

l l

i

)

'..e

-+-

L j

. Y_Z-f-

$4.,$

I I

,\\

Ii

[I-I _i n'. D

'k :

t.J ' __..:. 4.,.,'

1 3

+-

,d,1

.1

' n*

\\..

I t

D(Qv t '.1 i

II

', I l.

e I i IQ Lt.#.,8._sq-.

,t.- _. h, '.N{.l-.A, -

_et f

i

. s. _. #

.M _.

n Q,

a o

i i i c9 q i _,. x. _.J

',,. p' s

. q._

4 i.. e

_,I N.

.._t

...q:

I i %..

.y ia

_-r_h _.,J t e i--

i%.-. X..I g

i M,. ii.s f,~~ q.i

_ _._ _ %..,. m o. s_._.i

,f_i __I, O.

o

.s

Rt b_-v._.e h.l" L_ t. _w._l.b._.I _1._ a. _ _ [ _I.___,. mQ-_.--_. _.,(

l._ _ O i

4..
.- u I
_ )
I'~
f
. C...I._I ! :
d
,U h i _._ qi i k_ __- N r # ^-
.#.4
, l 1 i o..
tA i
i :,.s i _ _e t i
s q ! _ ~ s..s.
y - 1. - -
, y., %.._T.. L i g..,,q L -. ~..$.,.d_ _.N w
L
'~
D
-_.J 6 j
_ A. _ _. f. {,S. i. _.-
'4l0 %O.O S.T.'. @ L, _; %,_ f.__.I,3_i_.J
..m a -s-
.e,(l0.
e L_
4,.. _,N.I.__I.4:i._,y..,- I,s..
.n._,.y A
- e i
. I.__ I,y rt.i v.. n., o.S.. k s
iii, s
tt
%. I _,L._.i...
I ',q
.rq r_ i k
1.x i. _ k l._1 i.
...ia
~
_14.
%_: U_ m_ _:. i.... i,u_.... _..t l
. %.(( i. --
i _i p
g i..,. o...,. r.
_ 1 I [ i 4
.i
, -' y (
q,.....i., j - {.%
%; N '.I, c(,--Ir 1 ~-
g
.+ i I e-4
,. _ __J.cA in1 %_.'.q.
1 e.-g i
i
_g o
4 4
i,
._.t y..__
m.:
41
+
v) t 89-
,O,p.
-e o
q I, __.,4-.. Fr.,...sc3 -
6 6 -x A
_.N
_ r
. N [.<. -_
u
,I 3 i.
.;r l _ @.. %
t
_. t l
,.t i.(..p;
_Aitj-
_...-..i i
4, L,.,.
g
., g.?{ ~
h-;{~j,ts
- l '
~ ~
~
"-~f'~ Y'i
. _. g
, 3, _.~
l'
}
..x k
y
. j...
_., _...,.. ' t 't i
- wel.y:q :.h3 y v:r. y m:c.1,Yv 2-u
.: ner
i 1
4 1
1 APPENDIX IB
!O j
CSS Files i
b i
d 1
4 4,
1 1
5 i
1 i
i i
.i t
.I i
i i
l i
t 4
i i
i i
i l
l l
i L
f i
5 i
G Rev. 01 Page 50 of 96
~-..
,_.. _ _ _. _ _ _ _ _ _ _ _ _ = _.. _. - _
4 l
t i
i
-l 6
UPDATE A SOURCE FILE
O I'
Name:
UPDATE i
l
Purpose:
Update a CPC source file and perform a CAL assembly i
l l
l 4
1 i
i l-i i
1 1
I i
4 1
4 1
I l
l l
l i
l t
Rev. 01 Page 59 of 96
i i"
i
.i l
I i
i f
i 1
i i
l 1
4 5
e I
3 i
t J
i t.
4 i
s 1
e t
6 i
t.
I 1
I i
i I
1 s.
I I
6 l
t J
j I
t 1
i i
I 4
i
+
{
i I
)
)
t t
i i
i t
i i
1 L
j.
l Rev. 01 Page 60 of 96
[
4
~ ~ - - - - -
m--w
1 t.
a l
Exampic:
i 4
j
.)
.I i
l 1
l l
1 1
4 i
i Rev. 01 Page 61 of 96
.. w ww w. w ww--
vew g w
-y e w e-ywww,
._, vw-w w w-w-
--+s--
- - - - ' = - -
F UPDATE THE REVISI0ft LOG p
c,sg)
Name:
UPDLOG
Purpose:
Add a record of any revision to CPC software onto the revision 109 This CSS is not called by the user, but by UPDATE and If41TIAL.
l l
l 1
(
(
I
(
I l
l t
1 l
1 L
Rev. 01 Page G2 of 96
ce O
O Rev. 01 Page 63 of 96
CREATE A SOURCE FILE g~3 V
Name:
IllITIAL
Purpose:
Create a CPC source file and perform a CPYA and CAL assembly 0
1 i
~
\\
t i
i
\\
l s
10
' V Rev. 01 Page 64 of 96
-- ~
1 j
I t
1 l
il 1
i 4
t
.r t
i t
I i
I i
i I
i 4
L i
2 1
l t
t I
4 i
I I
i
)
e i
i l
t i
i t
i i
f a
i 4
4 I
i l
i i
i I
i i
s.
1 t
.t i
i f
Rev, 01 Page 65 of 96
j i
APPft; DIX IC I
i i
1 SOURCE UPDATER C0telANDS 1
I j
1 1
l i
r b
t
~
Rev. 01 Page 66 of 96
The following is a description of the six update commands which can be used A
Note that all U in the Source Updater command file to update a source file.
updates must be made in order of ascending sequence numbers.
1.
INSERT Command The INSERT Command is used to insert one or more new statements into The records following the INSERT Command an existing source program.
are inserted in the new master 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 is detected on the old master that is larger than 'segnbr' or an EOF /EOM or the ending string is detected, the error message:
SEQUENCE NUMBER NOT FOUND is printed on the line printer and the operation is aborted.
l To insert two statements between XXX00150 and XXX00160, the following statements must be placed in the Source Updater command file:
INSERT XXX00150 l
- statement #1 -
- statement #2 -
f*
V Rev. 01 Page 67 of 9G
2.
DELETE Command n(Q The DELETE Command provides the capability to delete a single statement The format of the or multiple statements from the input source file.
command is:
DELETE segnrl, segnr2 where 'segnrl' specifies _the sequence number of the first statement to If 'segnr2' is omitted, only the statement specified by be deleted.
'segnrl' is deleted.
If 'segnr2' is specified, statements between J
'segnrl' and segnr2' inclusively cre 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 l
sequence number is detected on the old master that is larger than
'segnr2', the error message:
SEQ flBR f!0T FOUND l
for 'segnrl' or the error message:
SEC0 TID SEQtlBR tiOT F0uttD for 'segnr2' is printed on the line printer.
The operation is aborted when a sequence number is not found.
.t To delete statements AAA01010 through AAA01500, the following comman.1 is placed in the Source Updater command file DELETE AAA01010, AAA01500 A
! U l
\\
f Rev. 01 Page 68 of 96
3.
MODIFY Command 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 segnbr indicates the sequence number of the statement to be where 'segnbr' modified.
If the sequence number cannot be found the error message:
SEQ tJBR fl0T FOUtID is printed on the line printer.
To use the MODIFY command to delete statement AAA01000 and replace it with a new statement, the following sequence raust be placed in the Source Updater command file:
MODIFY AAA01000
- new statement -
4.
REPLACE Command The REPLACE Command is used to both modify a specified statement and insert statements thereafter.
The format of the command is:
REPLACE segnbr where 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 I
)
with a /* in Columns 1 and 2.
l
?
Rev. 01 Page 69 of 96
b d.
SELECT Command A5 This command is used to modify or insert source lines at selected locations specified by sequence numbers.
The fermat 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 When a sequence number is found in the old master that record.
(%)
matches the sequence number specified, then a ' modify' is in effect; if a sequence number is found that is larger than the.one searched i
for, then an ' insert' of one line is done before the larger sequence Select is terminated with a record with /* in positions 1 and number.
2.
6.
ENDUP Command This command terminates the UPDATE mode.
If the old master file has not reached the 'ending strin0' specified in the Update command or E0F/E0M, this command copics the rest of the old master until the
'ending string' or EOF /E0M onto the new master.
O na 01 Page 70 of 96
.I 1
t APPEtJDIX 1D Automated CPC Integration 4
i.
i i
l 1
O i
1 a
i i
i.
i i
e i
4 4
.!O I
Rev. 01 Page 71 of 96
. ~.
APPE!401X 10
(
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 application of these automated proceaures, this Appendix outlines 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 The output is grouped by the name of the program that was manner.
changed.
The CPC Integration procedure produces a magnetic tape with the necessary object files, in the correct order, for subsequent final s
)
integration at the CPC Support System.
It also prints the steps to be x-performed at the Support System in order to create an absolute load module.
The CPC Label procedure will scan a magnetic tape, such as that produced by the Integration procedure, and list the object file labels contained on it.
This is useful for identifying the contents of magnetic tapes when the complete integration process does not occur at one time.
A list of program, file name, and object file label is provided in Figure 1.4-6.
l t
8 i
l Rev, 0I Pa0e 72 of 96
CPCLOGPT. CSS O
Purpose:
Produce an organized formatted report based on the CPC Change Log.
I I
W' O
Rev. 01 Page 73 of 96
CPCLOGPT
Purpose:
Read the log file on LU 5 and produce a report on LU 6.
P l
l l
O.
Pa rTi M ___-_ _ ____----- ge 74 of 96- - - - _ - - - - - - - - - - - -
R
03 ma
CPCINT. CSS 9
Purpose:
Output the object files needed to integrate a given CPC program, and print further instructions.
O l
t l
h'~
Rev. 01 Page 75 of 96
i 1
E I
)
f l
1 4
1
-l l
m Page 76 of 96
CPCINT
,e-'s (4%_,]
Purpose:
Read LU 10 for the name of the program to be integrated.
Find this name in the directory file on LU 12, and obtain the names of other files to be included in the integration, and the name of the instruction file.
Create a CSS file to copy the needed object files and print the instructions.
)
I 1
O-LLJ l
Rev. 01 Page 77 of 96
(
F
I
~
f i
i I
l i
i i
i i
l
\\
f I
i i
i r
=
L I
I l
i, f
Rev. 01 Page 78 of 96
CPCCOPYB. CSS
Purpose:
Copy an object file of record length 108.
1 l
l 1
Rev. 01 Page 79 of 96
CPCLABEL. CSS
Purpose:
Print a list of 16 bit object labels from a magnetic tape containing 16 bit object modules.
~
I I
(
Rev. 01 Page 80 of 96
APPEllDIX 1E (O
Periodic Test Disc Generation O
O Rev. L Page 81 of 96
APPENDIX lE Periodic Test Disc Generation - Tape Creation
Purpose:
To create a magnetic tape backup of a project disc, for purposes of generating a Periodic Test disc.
l l
O'.!
Rev. 01 Page 82 of 96
(
)
i l
J i
i l
l l
1l (
l l
-w N'w. 01 Page 83 of 96
Periodic Test Disc Generation - Tape Restoration (i
p.__
(~-.A To create a magnetic tape containing the CPC system object modules
Purpose:
by reassembling from a backup tape.
I l
(
n\\a,i Rev. 01 Page 84 of 96
S $$
unm3 0
hmme O
O O
[
sc. o1 page as e 96
Periodic Test Disc Generation - Disc Integration
Purpose:
To generate a Periodic Test disc from a reference disc and object modules produced by the Tape Restoration process.
O WJ I
i l
,O
\\J l
Rev. 01 Page 86 of 96
98 6
4 O
O SElIlhe 9
e
, Rev. 01 Page 87 of 96
f.
I l
b l,
4
(
i e
l Rev. 01 Page 88 of 96
/
2.0 PROJECT DISC GEllERATIO!! PROCEDURE o
2.1
'URPOSE The purpose of Section 2.0 is to present the procedures required to generate a new project disc from the generic source disc.
2.2 REFERENCES
Series 40 Disc Drive Maintenance Manual Diablo Systems Inc.,
2.2.1 Publication No. 81601 OS/32 MT Operator's Reference :1anual, Interdata Inc., Publication 2.2.2 Number 29-574, Section 7.2.
Common Disc Test / Formatter Program, Interdata Inc., Publication 2.2.3 Number 06-173.
OS/32 MT Operator's Reference Manual, Interdata Inc., Publication 2.2.4 Number 29-574, Section 7.3.
05/32 MT Operator's Reference Manual, Interdata Inc., Publication 2.2.5 Humber 29-574, Section 7.5.5.
O Rev. Ol' Page 89 of 96 j
~enTL..
2.3 PROJECT DISC GEllERATI0tt The CPC Project Disc Generation Checklist (Attachment 2.3-1) 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 Duplication Procedure j
(Attachment 1.4-3).
t Y
j%
-/
e Rev. 01 Page 90 of 96 f8 "4 T
'.3-1 s
Is
.D)
CPC PROJECT DISC GENERATION CHECKLIST 1
Mount the new disc onto USR2 (Reference 2.2.1).
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 36 0050 DTA 50 WRT 50 D500 DTA 50 ADD DTA D500 WRT 52 00CF DTA CF.
WRT 54 4300 DTA 4300 WRT 56 0080 DTA 80 WRT 76 85Al DTA 78 ADD DTA 85Al WRT 7A 0000 DTA 0
WRT r
7C 0000 WRT 7E 0001 DTA 1
WRT Verify that the 50 sequence was loaded correctly by reading these
" ~ -
same locations.
This is done by entering the following on the hexadecimal panel:
'( j DTA 30 ADD RD RD RD RD DTA 50 ADD RD RD RD RD DTA 78 ADD RD RD RD RD Rev. 01 Page 91 of 96. - _ - _. _ - _
I
..3-1 (Cont.)
CPC PROJECT DISC GENERATION CHECKLIST i
l c)
Start the loader:
1 DTA 30 ADD RUN FFFF should be displayed on the hex panel.
d)
Load the Formatter program sequence number:
DTA 412 RUN Place the format switch on the disc controller in the "FMT" i
I e) 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:
LOCYL 0 HICYL 197 PACTYP 1 DISCON B6 I
TFILE 1 FILE 2 TRKDEN 1 DEFSEC 1 i
FMREAD 1 TIMCON 140 l
RUN O+,
Rev. 01 Page 92 of 96 e
w*-e-re e-gy-yw%-as.--e e
-myee-y w.r y-,-w-veww y
wgetyem-.,g
.-9m-ym,--e.g--y%m.g..,q-,gy-+gg-.y=_
_ e
-w egy yg,g,m.9%,W y -psyn.--,-v,,--,,--.m.L-Tt-*PWT'?*
"T'-
-*'P^e-Tw*
I
..3-1 (Cont.)
()l CPC PROJECT DISC GENERATI0t1 CHECKLIST Initialize the disc (Reference 2.2.2) 3 a)
Mark SYS1 on:
MARK 'SYSl: Oft, PROTECT b)
Load the Disc Initializer Utility:
LOAD
.EG,DISCINIT, 12 TASK
.BG c)
Mark all discs off:
MARK USRl:,0FF MARK USR2:,0FF MARK SYSl:,0FF
/")
tx_/
MARK SYS2:,0FF d)
Start the program:
START, DISC =USR2:, VOLUME = volume name, CLEAR, BLOCK =64 Volume name is a four character mnemonic for the project.
Check the inteOrity of the disc (Reference 2.2.4).
4 a)
Load the disc check utility; MARK SYS1:, ON, PROTECT LOAD
.BG,DISCHECK, 12 TASK.BG b)
Mark the disc of f:
MARK USR2:, OFF g3 t
)
\\'
c)
Start the program:
START, USR2:, PR:
Rev. 01 Page 93 of 96
t
.t j
I
+
b.
}.3-1 (Cont.)
CPC PROJECT DISC GENERATION CHECKLIST 1
i9 Move all necessary files to the project disc by entering:
l 5
PROJECT (project name) j
,s 1
This procedure is detailed in Appendix 2-A.
l:
i t
1
?
l l-i.
!O 1
1 I
l t
i i
1 i
Lg o
i-Rev,. 01 Page 94'of 96 4
l:-
APPENDIX 2A
/hl 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 CPCl.
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 USRl:
2)
MARK USR2:,0N Put the project disc on-line l'
)
in device USR2:
x_ /
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 CPCl IS NOT ON-LINE **
The disc volume containing the generic files is not on-line.
7( yl x.
Rev.'01 Page 95 of 9G
.,,.x,
?'E cs
ASSIGN ERROR FILE filename O
The file called filename is already on the project disc.
This disc 4
should have been empty.
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.
O i
O Rev. 01
~
Page 96 of 96
_

ML20037A292

Text

1.2 REFERENCES

Purpose:

Purpose:

Purpose:

Purpose:

Purpose:

Purpose:

Purpose:

Purpose:

Purpose:

Purpose:

Purpose:

Purpose:

Purpose:

Purpose:

Purpose:

2.2 REFERENCES

Navigation menu

Search