• Aucun résultat trouvé

FUNCTIONAL SPECIFICATION CHANGE ORDER

N/A
N/A
Protected

Academic year: 2022

Partager "FUNCTIONAL SPECIFICATION CHANGE ORDER "

Copied!
6
0
0

Texte intégral

(1)

F .

, ~ ~

r

. *'

m t "

NAVAL TACTICA Q A~'A NOT SYSTEM REMOVE

FUNCTIONAL SPECIFICATION CHANGE ORDER

NO. ONE

for

TECHNICAL NOTE NO. 240

REPERTOIRE of INSTRUCTIONS for the

PX 1343-36

DIVISION OF SPERRY RAND CORPORATION UNIVAC PARK, ST. PAUL 16, MINNESOTA

NAVY DEPARTMENT CONTRACT: NObsr 72769

BUREAU OF SHIPS ELECTRONICS DIVISIONS

NTDS NO. U-6090 ,15 FEBRUARY 1961

(2)

PUBLICATION:

PX NUMBER:

TECHNICAL NOTE NO. 240

Repertoire of Instructions for the AN; USQ-20 Unit Computer

_13_4_3-_3_6 _ _ _ REVISION NO: One DATE: 15 February 1961

INSTRUCTIONS:

staple Change Order to Document or Enter Revisions in Text.

,4~:~,;P.~

L. D. Findley Manager

Naval Tactical Data System

PAGE LOCATION I CORRECTION

1

3

5

8

9

Paragraph 2 line 3

Line 5 from top of page

Remove liD" after both" 14" and "12"

Table 1 Add "(OCTAL)" after HCODE" in both instances at the top of Table 1

Under liB.

FUNCTION CODE DESIGNATOR - f", line 4

Replace "00014" with "00000"

Line 5 Replace "00014" with "00000"

Under "H.

MAGNETIC CORE MEMORY ASSIGN- MENT", line 2

Line 3

Lines 1 through 7

Replace word, "three" with "two" and replace word,

"eight" with "seven"

Delete the third line, "1) The starting address from MASTER CLEAR "

Replace "2)" with "1)", "3)" with "2)", "4)" with

"3)", "5)" with "4)", "6)" with "5)", "7)" with

"6)", and "8)" with "7)"

- - DIYISION 0. s . . . . . . . L

P

, ."ND cO.'O.""ON '&If

~W8!..---1IIIIi1 Pa~e

1

of

4

UNIVAC 'All. n. PAUL . . . . 'NNnOtA

(3)

FUNCTIONAL SPECIFICATION CHANGE ORDER (Cont.)

PAGE LOCATION I CORRECTION

9

10

11

12

--i Page

2

of

4

Under "STORAGE FUNCTION"

Under

ADDRESS 00000:

Under

ADDRESS 00014:

Under

ADDRESS 00017:

Under IISTORAGE FUNCTION"

Under

ADDRESS 00036:

Line 5 Line 6 Line 7 Line 8 Line 9 Line 10 Line 21 Line 22 Line 23 Line 24 Line 25 Line 26

Line 3 Line 4 Line 5 Line 6 Line 7 Line 8 Line 19 Line 20 Line 21 Line 22 Line 23 Line 24

Line 1 Line 2 Line 3 Line 4

Replace "Initial Starting Address from MASTER CLEAR" with IIFault Entrance Register"

Replace IIFault Entrance Register" with "Memory Word"

Replace IIReal-Time Clock Register with IIMemory Word"

Replace IIMemory Word" with IIReal-Time Clock Register"

Remove

"0"

at end of line

Remove 110" at end of line

Remove 110" at end of line

t

.... ---Z' --. ...

DIVISION OF SPUI' RAND COI'ORATION

Pm'IIL~-

UN.VAC 'AI", n. 'AUL I., M.N.U.OTA

(4)

12 Line 5 Line 6

Under Iti. WIRED MEMORY"

Line 1 Line 2 4th line from bottom of page 2nd line from bottom of page

Remove ltD" at end of line Remove liD" at end of line

Remove ltD" after 16

Remove the second word in the line, It core"

Replace "00014" with HOOOOO"

Replace 1t14" with "00"

- - - r--- - - -

14 Last line Remove liD" after "59"

- - - - I " " " - - - - - - - - - - - - -

15 Last line

- - - - r - - - -

16 After I I STORE

en"

Footnote

Remove uD" after "59"

- - - - - - - - - - - - - - - - -

Place an asterisk (*) after "STORE

cf"

Add the following:

"*Instruction 17, STORE

en

is intended for use in the computer's reply to an interrupt; consequently, it is not synchronized with the input buffering proc- ess.

Therefore, the execution of n sequential Instruction 17's on the same channel, will not place n sequential Input Acknowledge signals on the Input Acknowledge line associated with that channel. It will, in fact, generate a signal which is n x 14.8 microseconds wide on that Input Acknowledge line. Moreover, it is obvious that the execution of an Instruction 1 7 on a given channel while an Input buffer is in progress on that channel will, in most cases, ser- iously interfere with the buffered transfer of data.

It should be noted however, that any other instruc- tion executed between two Instruction 17's will allow the Input Acknowledge line to return to the logical zero state for a time consistent with Input/Output specifications before it rises a second time."

- Z ' ... DIVISION Of spun .AND co.rO.A"ON

~---"I Pa~e

3 of 4 UIIIVAC 'AI'. 11. PAUL ... MINIIUOtA

t-

(5)

FUNCTIONAL SPECIFICATION CHANGE ORDER (Cont.)

PAGE LOCATION I CORRECTION

20 1153 SELECTIVE

SUBSTITUTE' ,

I - - - - 1 - - -

23 Line 1

Under tlRETURN JUMP (Manual)' ~

line 7 Footnote

Add the following after the last line in paragraph tlIn this instruction repeated, K = 0 or K = 4 should

not be used."

- f - - -

- - -

Place an asterisk {*} at end of line Place an asterisk {*} at end of line

tI*This instruction is the normal sequence of events;

that is, this sequence occurs when the Return Jump instruction is executed in the context of a program which is proceeding from one instruction· to the next by way of skips, jumps, or any programmed

branching.

However, if the Return Jump immediately follows recognition, by the Control Section of the computer, of an interrupt (that is, if the Return Jump is the instruction stored at the Interrupt Entrance Reg- ister), then it must be described as follows:

tlStore {P}p in the lower half of memory address Y. Then jump to Y+e'

The p-designator controls the modification of {P}

and it is set up by the instruction immediately preceding the Return Jump caused by the interrupt.

Therefore, the Return Jump causes the storage of the address of the next sequential instruction which would have been executed if the interrupt had not occurred.

In fact, the general description of the Return Jump is the latter, with the understanding that, in the non- interrupt case, p is set to one, which causes the storing of P+l in Y."

-....-.II Page

4

of

4

.... ---p .-. ...

~~­

DIVISION OF spun UND CORPOUTION UNIVAC ' A l l . sr. 'AUL . . . . INNUOtA

(6)

BuShips Code 687E NEL Code 1800 NEL Code 2800 st. Paul Central File San Diego Central File A. P. Hendrickson L. D. Findley G. G. Chapin C. W. Glewwe R. A. Hileman C. J. Homan M. M. Koschmann G. E. Pickering J. A. Kershaw F. E. McLeod R. P. Fischer H. K. Smead T. O. Robinson C. J. Haggerty

Contracts Department

(8) (20) (6) (250) (50)

(2) (2) (2)

Bureau of Ships Technical Representative - St. Paul W. G. Haberstroh

E. G. Runyon R. L. Burkholder G. R. Kregness H. D. Wise

Références

Documents relatifs

Application support for QOS-based link level service requires that the following types of ATM information be mappable (or derivable) from the higher level protocol(s) such as

The NamedType in a SequenceOfType or TypeWithConstraint that is subject to a LIST encoding instruction MUST NOT be subject to an ATTRIBUTE, ATTRIBUTE-REF, COMPONENT-REF,

Receipt of the IP TELNET command causes the higher level protocol interpreter to be interrupted, enabling it to scan the data stream (up to and including the HDM) for commands

The PDP-9 at the Institute of Computer Science also simulates a 1130 with 2 card readers, 2 card punches, two line printers, three MAST consoles, and a system console.. The

Note that due to aforementioned recommendations in [RFC2131], valid downstream DHCP packets (DHCPOFFER, DHCPACK, and DHCPNAK) from the server MAY get dropped at the DHCP

In addition, when an echo request is received, if the egress LSR does not know the Reply Mode defined in this document, an echo reply with the return code set to "Malformed

[The very first data message to be transmitted over a newly established connection will have the sequence number one; until this data message is correctly

However the advent of semi-automated message answering, in which a receiver’s message system prepares address lists for reply messages by copying appropriate fields from the