(32 B .~
Input/Output Array A
B
C
D E
F G H
I
First Cycle
Input/Output Array H
G
D
Insignificant Data
PHASE ONE St ep 3
(16 Bits)
I
Register ReformatStep 1 (32 Bits)
PHASE TWO
Legend:
Step 6 (16 Bits)
Step 4 (32 Bits)
C D
G
A
Second Cycle
Input/Output Ar (Final) H
Step 5 Move
(32 Bits of Insignificant Data)
Insignificant Data Data fields involved in
moving or storing.
A Unmeaningful data after
conversion.
Begi n Phase Two End Phase Two
Figure 16. IKDGDCFI Reformatting in Place (From System/360 Integer to 1130 Integer)
CONVERT FROM 1130 INTEGER TO SYSTEM/360 STANDARD-LENGTH OR HALFWORD INTEGER (MODULE NAME IKDGDCTI)
Cha~: OA, OB, OC Function:
70
• Converts an array of integers in the 1130 format to an array of integers in
either the System/360 standard-length of halfword format.
• Converts an array of alphameric data in the 1130 format to an array of alpha-meric data in the System/360 halfword format.
Entry: GDCTI, from a call in the user's program.
Exit: To the calling program.
Input: In register 1, parameter lis·t containing follows: System/360 standard-length of halfword for-mat, or an array of 16-bit alphameric data in the System/360 format.
Operation: After sav.ing register contents, IKDGDCTI determines the number of elements to be converted by checking the nelcountn standard-length format. IKDGDCTI deter-mines the format of the output array elements havE~ been converted.
Except for the case described in the preceding palragraph, if the output data is to be in Syst:em/360 standard-length format, elements are reordered in the outpu"t: array
one at a time as they are reformatted. The reformatting process expands each two-byte input element by propagating the sign bit.
When conversion is to be done between arrays and reformatting is necessary, each element is reformatted (starting with the
360 halfword integer or alphameric format, conversion merely involves reordering the elements in the input array. This is done as shown in Figure 12. When reordering in place, IKDGDCTI saves elements from the bottom of the input array instead of from the top. This is shown in Figure 13.
CONVERT FROM SYSTEM/360 STANDARD-LENGTH REAL TO 1130 STANDARD-PRECISION REAL
(MODULE NAME IKDGDCFF) Charts: PA, PB
Function:
• Converts an array of real numbers in the System/360 standard-length format to an array of real numbers in the 1130 standard-precision format.
• Converts an array of alphameric data from the System/360 standard-length format to an array of alphameric data in the 1130 standard-precision format.
System/360 Conversion Routines 71
Input Array
Original Arrays
A B
C
D
F
f.- 16 Bits ---l
Output Array
Invert Arrays
"'-"'"
Output Array
Reordered Data
D
C B
f.-. 16 Bits
---l
Input Input
Array Array
Step 1 (16 Bits)
I
Reformatting I Registers I
Final Arrays
Original F Original E
Original D
D
c
B
A
I--16 Bi ts
----I
Output Array
Figure 17. IKDGDCTI Reordering and Reformatting Between Overlapping Arrays (From 1130 Integer to System/360 Standard-Length Integer)
EntfY: GDCFF, from a call in the user's program.
Exi!: To the calling prJgram.
Input: In register 1, the address of a parameter list containing the following:
+ 0 A(WuserarrayW)
address of input array conta1ning data to be converted.
+ 4 A(WtemparrayW)
address of output array into which the converted data is to be placed.
+ 8 A(WelcountW)
address of the integer that designates the number of elements to be converted.
+12 A(WtypeconW)
72
address of the integer that designates the type of conversion to be done.
output: An array of real numbers or alpha-meric data in the 1130 standard-precision format.
Operation: After saving register contents, IKDGDCFF determines the number of elements to be converted by checking the welcountW argument. If the number of elements to be converted is zero or less, IKDGDCFF immedi-ately returns to the calling program.
Next, if necessary, IKDGDCFF moves the input array. It then determines whether conversion is to be done in place or between arrays (see WDetermining Where Con-version is to be Done W).
At this point, IKDGDCFF determines the kind of conversion required by testing the value of the Wtypeconw argument. If the conversion involves alphameric data, con-version merely consists of reordering the elements in the array as shown in Figures 12 and 13.
FIRST CYCLE
Input Array
~_---, Step 3 (l6Bits) B
D
F Output I
Array G Reformatting I Registers
Step 5 (16 Bits)
SECOND CYCLE
Step 12 (32 Bits) Step 14 (32 Bits)
Step 4 1 - - - 1 (32 Bits)
B
\..-- 4 Bytes
-...J
B
A
Step 2 (32 Bits)
~-
4 Bytes---1
NOTE:
Shaded areas represent the first input data handled and its associated output data for both cycles.
I
Figure 18. IKDGDCTI Reordering and Refor-matting in Place (From 1130 Integer to System/360 Standard-I,ength Integer)
If the conversion involves real data, the elements must be reformatted as well as reordered.
To reformat real data, IKDGDCFF isolates the sign bit, the characteristic, and the fraction of an input element in registers.
It then normalizes the fraction portion and changes the characteristic to a binary excess 128 characteristic. The resulting fraction, characteristic, and sign bit are then stored in the appropriate portions of the output element. Conversion of the 24-bit System/360 hexadecimal fraction to the 23-bit binary fraction causes the loss of one low-order bit when there is a one in the high-order bit of the System/360 frac-tion to start with and no normalizafrac-tion is required.
If the reordering of the reformatted data is to be done in place, i t is done in two phases as shown in Figure 19.
In phase one, the first element of the input array is reformatted (step 1). Then, to prevent overlay, the last element of the input array is moved into the first loca-tion (step 2), and the reformatted first element is stored in the last location (step 3). The same sequence is followed with the second and next-to-Iast elements and so on until the middle of the array is reached.
At this point phase two begins. The elements which remain to be converted have already been properly ordered by phase one.
Phase two simply takes one element at a time starting at the middle of the array, reformats it, and stores i t back in the same location from which i t was taken
(steps 1 and 2).
If reordering of elements is to be done between arrays, data is reordered as shown in Figure 12.
CONVERT FROM 1130 STANDARD-PRECISION REAL TO SYSTEM/360 STANDARD-LENGTH REAL (MODULE NAME IKDGDCTF)
Charts: PA, PB Function:
• Converts an array of real numbers in the 1130 standard-precision format to an array of real numbers in the System/
360 standard-length format.
• Converts an array of 32-bit alphameric data in the 1130 format to an array of alphameric data in the System/360 standard-length format.
System/360 Conversion Routines 73
PHASE ONE St 2 Input/Output Array
ep Input/Output Array
Move
A
Step 1
H
Step 2 B
Step 1 Move
B
C C
D D
I
ReformattingI I
ReformattingI
Register Register
E E
F
G
' - - - - H
I...--
4 Bytes----..J
First Cycle
Input/Output Array H G
F
E
Reformatted D Reformatted C
Reformatted B Reformatted A
~
4 Bytes--l First CycleStep 3 Store
PHASE TWO
Step 1 Step 2
! I R.fo~ot';"g
IRegister
I
NOTE:
All data has b the time Phase
een reordered by Two is reached;
therefore, only reformatting of E through H is done by Phase Two.
F Step 3
Store
G
Reformatted A
~
4 Bytes---l
Second Cycle
Final Output Array H G
F E D
C B
A
~
4 Bytes~
End of Phase Two
Figure 19. IKDGDCFF and IKDGDCTF Reordering in Place (From System/360 Standard-Length Real to 1130 Standard-Precision Real and Vice Versa)
Ent!Y. : GDCTF, program.
from a call in the user's
To the calling program.
Input: In register 1, the address of a parameter list containing the following:
14
+ 0 A("temparray"}
address of input array containing the data to be converted.
+ 4 A("userarray"}
address of output array into which the converted data is to be placed.
+ 8 A("elcqunt W) alpha-meric data in System/36'0 standard-length format. hexa-decimal ex/cess 64 characteristic and reduces the :fraction proportionately. Nor-malization o:f the 23-bit 1130 binary frac-tion to a System/360 24-bit hexadecimal fraction may cause a loss of up to two low-order bi·ts in each converted nu:rober.
CONVERT FROM SYSTEM/360 DOUBLE-PRECISION REAL TO 1130 EXTENDED-PRECISION REAL
(MODULE NAME IKDGDCFE) Charts: QA
Function: converts an array of real num-bers in the System/360 double-precision format to an array of real numbers in the 1130 extended-precision format.
Entry: GDCFE, from a call in the user's program .•
Exit: To the calling program.
Input: In register 1, the addr'ess of a parameter list containing the following:
+ 0 A("userarray") 1130 extended-precision format.
Operation: After saving register contents"
IKDGDCFE determines the number of elements to be conv'erted by checking the 11/ elcount " arrays, IKDGDCFE reformats the elements in registers beginning with the last element of the input array, and reorders them in reformatted have already been reordered by phase one. Each unreformatted element is performing the conversion.
Reformatting is done in the same way as described in the discussion of the IKDGDCFF module, except that the size of the input fraction and the positioning of the refor-matted characteristic, fraction, and sign bit differ for the two modules as shown in Appendix D.
CONVERT FROM 1130 EXTENDED-PRECISION REAL TO SYSTEM/360 DOUBLE-PRECISION REAL (MODULE NAME IKDGDCTE)
Charts: RA
Function: Converts an array of real num-bers in the 1130 extended-precision format to an array of real numbers in the System/
360 double-precision format.
System/360 Conversion Routines 75
~3
(48~~Step 2 Move
"---Step 2 (48 Bits)
A B
C D E F
G H
~----8 Bytes Input Array (First Cycle)
t * - - 6 Bytes
- 1
I
H I
I I
G I F
I I
F I E
I
D
C
B A
~--- 8 Bytes
Input Array (Begin Phase Two)
~I
G
PHASE ONE
I
Reformatting I I RegistersI
I
Step 4 (64 Bits) Step 1
(64 Bits)
PHASE NlO
Step 1 (64 Bits)
1
I
Reformatting I I RegistersI
I
Step 6 (48 Bits)
r--
6 Bytes ~Reformatted H
B
C D E
F G A
~--
8 BytesInput Array (Second Cycle)
H
G F E D
C
B
A
I
I
~I
~ 6Bytes~
Output Array (End Phase Two)
Step 5 Move
Figure 20. IKDGDCFE Reordering and Reformatting (From System/360 Double-Precision Real to 1130 Extended-Precision Real)
76
Entry: GDCTE, from a call in the user's program.
Exit: To the calling program.
Input: In register 1, the address of a parameter list containing the following:
+ 0 A (W tempalrrayW )
address of input array containing the data to be converted.
+ 4 A(WuserarrayW)
address of output array into which the convert.ed data is to be placed.
+ 8 A(WelcountW)
address of the integer that designates the number of elements to be convert:ed.
Output: An array of real numbers in the System/360 double-precision format ..
Operation: After saving register contents, IKDGDCTE det:ermines the number of elements to be converted by checking the DelcountW argument. If t~e number of elements to be converted is zero or less, IKDGDCTU immedi-ately returns to the calling program.
IKDGDCTE determines if conversion is to be done in place or between arrays (see WDetermining Where Conversion is to be DoneW).. If i t is to be done between arrays, IKDGDCTE reformats the elements in registers bE~ginning with the last element of the input array, and reorders them in the output alrray.
When IKDGDCTE determines~that the input array and the output array overlap, i t may be necessary to move the input data before conversion is done.
If the input array has a greater start-ing address than the output array, the input data is moved so that the first input element is at the beginning of the output array before conversion takes place. This is shown in Figure 14 (Type 2 and Type 5).
otherwise, each element of the input array, starting wi th the last" is refor-matted and stored in the output array, starting at the bottom.
Reformatting is done as described in the discussion of the IKDGDCTF module, except that the size of the fraction portion of the output elements and the format of the input elements differ for the two modules.
The formats are shown in Appendix D.
FLOWCHARTS
This section contains autocharts showing the logic flow for the System/360 con-version routines. The charts are ordered alphabetically (according to identifica-tion) in the sequence in which the routines are described. Refer to Appendix G for an explanation of the symbols used on the autocharts.
system/360 Conversion Routines 77
Chart NA. GDCFI Routine (Part 1 of 2)
78
*****A3**********
****A2********* * *
* * * SAVE REGS. *
* GDCFI ENTRY * •••••••• X*SET SW1=O SW?=O*
* * * SW3=O *
*************** * *
*****************
FRAD ADDRESS OF ELEMENT TO BE
CONVERTED *****B3********** X
* FRAD=ADDR OF *
* INPUT ARRAY *
* TOAD=ADDR OF *
* OUTPUT ARRAY * TOAD ADDRESS IN WHICH
CONVERTED ELEMENT IS
TO BE PLACED * ***************** *
CONVERSION BETWEEN ARRAYS
x
.*. GDCFI190
C3 * •
• * *. ****C4*********
.* IS *. NO * *
*.'ELCOUNT' GT .* ... X* RETURN *
*. 0 . * * *
*. * •• * • * ************ ***
* YES
X
GDCFI007 .*. .*. GDCFIOIO .*.
02 *. 03 *. 04 * •
• * *. . * *. .* *.
NO .* DO *. LT .* IS INPUT *. GT .* DO *. NO
•••• *. ARRAYS .*x •••••••• *.ADDR = OUTPUT.* •••••••• x*. ARRAYS .* ••••
*. OVERLAP .* *. ADDR .* *. OVERLAP .*
* . . * * •• * * YES * . . * * •• * * EQ * . . * * •• * YES *
.CONVERSION .IN PLACE
X GDCFI040 X
*****G2********** *****G3**********
* * * SET *
* SET SW3=1 * * SWl=1 TO *
X
*****E4**********
* MOVE INPUT *
* DATA SO THAT *
* TOP OF INPUT *
* ARRAY=TOP OF *
* OUTPUT ARRAY *
*****************
X
*****F4**********
* *
* *
* SET FRAD=TOAD *
* *
* *
*****************
* TOAD=ADDR OF * •••••••• X* INDICATE IN *X •••••••••••••••••
* INPUT ARRAY * * PLACE *
* * * CONVERS ION *
***************** *****************
.
••••••••••••••••••••••••••••••••••••• x.x •.•••••••••••••••••••••••••••• : ••••••••. .
GDCFI050 X
*****H3**********
* *
*DETERMINE LAST *
* ELEMENT OF *
*1 NPUT ARRAY AND*
* ADJUST FRAD *
*****************
.*. x J3 * •
• * IS * •
• * IT *. NO
*.CONVERSION TO.* •••••• ~.
*. 2 BYTES .* X
* . . * *. .* * YES ***** *NB * Al* *
x
*****
*NB *
* H2*
* *
*
* * *
CONVERSION BETWEEN ARRAYS
Chart NB.
••• X*ELEMENT POINTED*
* TO BY FRAD *
System/360 Conversion Routines 79
Chart OA. GDCTI Routine (Part 1 of 3)
Chart OB. GDCTI Routine (Part 2 of 3) TO SYSTEM/360 STANDARD LENGTH FORMAT EITHER
IN PLACE OR BETWEEN ARRAYS.
System/360 Conversion Routines 81
Chart OC.
82
GDCTI Routine (Part 3 of 3)
THIS CHART SHOWS REFORMATTING AND INVERSION OF ARRAYS TO SYSTEM/360 STANDARD LENGTH FORMAT WHEN THE INPUT ARRAY ADDRESS IS LESS THAN THE OUTPUT ARRAY ADDRESS AND THE ARRAYS OVERLAP.
*****
*OC *
* B3*
* *
*
X
*****B3**********
* SET FRAD *
* = ADDR OF *
*BOTTOM ELEMENT *
*OF INPUT ARRAY *
* *
*****************
X
*****C3**********
* SET TOAD *
* = ADDR OF *
*BOTTOM ELEMENT *
*OF OUTPUT ARRAY*
* ***************** *
.x •••••••••••••••••••••••••
GDCTI207 X
*****D3**********
* *
* REFORMAT *
*ELEMENT POINTED*
* TO BY FRAD *
* *
*****************
X
*****E3**********
* *
* STORE *
* REFORMATTED *
*ELEMENT AT TOAD*
* *
*****************
x
SEE FIGURE 17 • •
.*. GDCTI208 •
F3 *. *****F4**********
.* ARE *. * *
.* ALL *. NO *UPDATE POINTERS*
*. ELEMENTS .* •... x* FRAD = FRAD-2 *
*.CONVERTED.* * TOAD = TOAD-4 *
* . . * *. .* * ***************** *
* YES
X
****G3*********
* *
* RETURN *
* *************** *
Chart PA. GDC:FF and GDCTF Routines (Part 1 of 2)
*****A3**********
****A2********* * *
* GDCFF * * SAVE *
*OR GDCTF ENTRY * •••••••• X*REGS. SET SW1=0*
* * * SW2=0 *
FRAD ADDRESS OF ELEMENT TO BE CONVERTED
*************** * *
*****************
TOAD ADDRESS IN WHICH CONVERTED ELEMENT IS TO BE PLACED
X
*****B3**********
* SET FRAD = *
* /IDDR OF INPUT *
* ARRAY. SET *
* TOAD=ADDR OF *
* OUTPUT ARRAY *
*****************
CONVERSION BETWEEN ARRAYS
.*. x GDCFF200
C3 *. GDCTF200
.* *. ****C4*********
.* IS *. NO * *
*.' ELCOUNT' GT .* .••••.•. X* RETURN *
*. 0 . * * *
* . . * ***************
* • . * YES *
.*. .*. x GDCFF030 .*.
02 *a 03 *. GDCTF030 04 *.
.* *. .* *. .* *.
NO .* DO *. LT .* IS INPUT *. GT .* DO *. NO
.•.. *. ARRAYS .*x •••••••• *.ADDR = OUTPUT.* •••••••• x*. ARRAYS .* ....
*. OVERLAP .* *. ADDR .* *. OVERLAP .*
* . . * * . . * * . . *
* •• * YES * * •• * * EQ * •• * * YES
X
*****E2**********
*MOVE INPUT DATA*
*SO THAT BOTTOM *
*OF INPUT ARRAY *
* = BOTTOM OF *
* OUTPUT ARRAY *
*****************
• CONVERSION
• IN PLACE
:GDCFF070 • GDCFF080 •
X
*****E4**********
* MOVE INPUT *
* ARRAY DATA SO *
* THAT TOP OF *
*INPUT ARRAY=TOP*
*OF OUTPUT ARRAY*
*****************
• GDC TF 070 X GDCTF080 X X
*****F2********** *****F3********** *****F4**********
* * * SET * * *
* SET * * SW1=1 TO * * SET *
* FRAD~ADDR OF * •••••••• x* INDICATE IN *X •••••••• * FRAD=AODR OF *
* OUTPUT ARRAY * * PLACE * * OUTPUT ARRAY *
* * * CONVERSION * * *
***************** ***************** *****************
. . .
•.••••.•.••••••••••••.•••••••.•••••• • x.x ••••••••••••••••••••••••••••.•••••.•.
GDCFF090 • GDCTF090 X
*****G3**********
* *
* SET TOAD=ADDR *
* OF BOTTOM OF *
* OUTPUT ARRAY *
*' *
*****************
.*. x
H3 * •
• * IS * • . * IT *. NO
*.CONVERSION TO.* ••••
*.REAL DATA.*
*. .*
* . • * YES *
***** x
*PB *
* A1*
* * *
x
*****
*PB *
* H1*
* * *
CONVERSION BETWEEN ARRAYS
System/360 Conversion Routines 83
Chart PB. GDCFF and GDCTF Routines (Part 2 of 2)
Chart QA. GDCFE Routine
System/360 Conversion Routines 85
Chart RA. GDCTE Routine
"'ELEMENT POI NTED*
'" TO BY FRAD *
This appendix illustrates and describes the storage areas which provide a means of communication among the PTOP data transmis-sion routines and between the systenls. The areas described are:
• 1130 telecommunications control block (GTCOM).
• System/360 telecommunications control block (G'l'CB).
• System/360 save area used wl'len the asynchronous routine is in control.
• System/360 unit displacements' (in decimal and hexadecimal) are shown at the left side of each illus-tration. These displacements indicate the location of the named field within the appendix are tables summarizing the pro-cessing of information in the GTCOM and the GTCB (see "Processing Informationl in Con-trol Blocks").
1130 Telecommunications Control Block (GTCOM)
Table 1. Contents of BITS Field
r---~---T---·---,
I Bit I Name I Meaning of Contents When Bit is Set to One (On) I
~---f---f---~
I 0 I RTBSY I An input/output request (other than a system read request) is active I
I I I or pending. I
r--·---f---f---~
I 1 I OSRED I System/360 user ready-to-read message has been received. I
~--.---f---_+---i I 2 I ASPND I A request for the 1130 user's asynchronous routine is pending. I
~--·---f---f---i I 3 I OKNIT I The 1130 PTOP transmission routines are initialized. I
r--·---f---+---i
I 4-5 I ERRST I Indicates the error status of the active message, as follows: I
I I I 0 No errors I
I I I 1 Unrecoverable error(s) I
I I I 2 Incorrect length I
I I I 3 Timeout I
~---f---+---i 1 6 I ASACT I System/360 asynchronous routine is active. I r---f---f---~
I 1 1 FNCTN I Indicates the currently active function, as follows: 1
1 I I 0 Transmit Initial, or Receive Initial I
I I I 1 Transmit End, or Receive Continue/Repeat I
~---f---f---i I 8-10 1 MSGTP I Identifies the message currently being transmitted, as follows: I
I I I 0 Initialization I
1 I I 1 Terminate communication link 1
I I I 2 Asynchronous routine request I
1 I I 3 Asynchronous routine ended I
I I 1 4 Data message I
1 I I 5 Ready-to-read message I
I 1 I 6 User read I
1 I 1 1 System read 1
r--·----f---f---·i
I 11 1 BIT11 1 Mainline program transmission status should be saved by GTPOl before I
I 1 I processing the next operation. 1
r---f---+---~
1 12 I BIT12 I If one, the 1130 asynchronous routine is active. If zero, the 1130 1
I 1 I asynchronous routine is inactive. 1
r---f---f---i
1 13-15 I 1 Reserved. 1
L ________ ~ ______ ~ _______________________________________________________________________ J
BITS (+0, /00)
contains the flags and switches used by the 1130 data transmitted routines.
Table 1 gives the name and the con-tents of each bit in the BITS field.
BITS2 (+1, /01)
contains bits used to queue PTOP requests. The bits are listed in Table 2 in the order of priority for honoring the requests.
LSTRD (+2, /02)
contains integer (1) the type of status of the last fied by the user.
codes are defined LSTWT (+3, /03)
codes that indicate data and (2) the read request speci-The meanings of the in Table 3.
contains integer codes that indicate (1) the data type and (2) the status of the last write request specified by 88
Table 2. Contents of BITS2 Field
r----T---,
IBit 1 Meaning of Contents When Bit is On 1
r----f---i
10-8 I Reserved. I
r----t---i
19 1 Initialization message is pending. I
r----t---~
110 1 Terminate communication link mes-I
I I sage is pending. 1
r----t---i
111 I Asynchronous routine request mes-I
1 I sage is pending. I
r----t---i
112 I Asynchronous routine ended message I
I 1 is pending. I
r----t---i
113 1 Data message is pending. I
~----f---i 114 I Ready-to-read message is pending. 1
~----+---i 115 1 User read request is pending. 1
L ____ ~ ____________________________________ J
the user. The meanings of the codes are defined in Table 3.
RDCNT (+4, /0,11)
contains the number of 1130 words to be transmitted (word count) from the last 1130 ready-to-read message.
WTCNT (+5, /05)
contains the word count from the last 1130 data message.
RDPTR (+6, /06)
contains the address of the first element (placed in the highest storage location) in the user's read a:rray,.
WTPTR (+7, /07)
contains the address of the first element (placed in the highest storage location) in the user's write array.
SAVST (+8, /08)
is an 8-word save area into which the transmission status of the mainline program is placed before execution of the as~'nchronous routine. The value of OSCN'I' is placed in the first word of this save area if OSRED is set to one when the 1130 asynchronous rou-tine is requested. Otherwise, the first word contains zero. The three low-ordE!r bits (13, 14, and 15) in BITS2 al:e saved in the second word, and thE~ six words from locations GTCOM+2 through GTCOM+7 are placed in the remainder of this save area.
Table 3. C<mtents of LSTRD and LSFfWT Fields
RDBUF (+16, /10)
contains the address of the user-specified read buffer.
WTBUF (+17, /11)
contains the address of the user-specified write buffer.
ASYNC (+18, /12)
contains the address of the user's asynchronous routine.
PSWRD (+19, /13)
contains the address of the password.
RDSEQ (+20, /14)
contains the sequence number of the next message to be read.
WTSEQ (+21, /15)
contains the sequence number of the next message to be written.
DSREF (+22, /16)
contains the data set reference num-ber passed by the System/360.
ASPRM (+23, /17)
contains the one-word integer data passed from the System/360 for the 1130 user's asynchronous routine.
ASDAT (+24" /18)
contains the one-word integer data passed by the 1130 user's program for the System/360 asynchronous routine.
NSI (+25, /19) is a save address
area used to of the next
store the sequential
r---T---...:---,
I Bits I Meaning I
~---t---~
I 0-7 ,A code that defines the type of data specified by the last transmission I
I I request, as follows: I
I I lOne-word integer I
I I 2 Standard-precision integer (2 words, only first word used) I I I 3 Extended-precision integer (3 words, only first word used) I
I I 4 Standard-precision real (2 words) I
I I 5 Extended-precision real (3 words) I
I I Not~: Alphameric data can be placed in any of the FORTRAN data types; i t is I
I I treated as data of that format. I
~---+---~
I 8 I For LSTWT, if on, this bit indicates that incorrect data length was specified. I
I I For LSTRD, this bit should never be on. I
~---+---.---~
I 9-15 I A code that indicates the ~tatus of the last operation, as follows: I
I I 1 Operation success:fully completed I
I I 2 Operation not started I
I I 3 Operation started, but not complete I
I I 4 Both systems are in ready-to-read status I
I I 5 System/360 has called GTEND I
I I 6 Transmission line error I
I L ______ ~ I __ . ____________________________________________________________________________ 7 Incorrect length J I
Appendix A: Control Block and Table Formats 89