| 1 |
<pre>Network Working Group James E. White |
| 2 |
Request for Comments: 105 Computer Research Lab. |
| 3 |
Category: Informational University of California |
| 4 |
Santa Barbara, California |
| 5 |
March 1971 |
| 6 |
|
| 7 |
<span class="h1">Network Specifications for</span> |
| 8 |
<span class="h1">Remote Job Entry</span> |
| 9 |
<span class="h1">and</span> |
| 10 |
Remote Job Output Retrieval |
| 11 |
at UCSB |
| 12 |
|
| 13 |
|
| 14 |
In the discussions that follow, 'byte' means 8 bits, with those |
| 15 |
eight bits numbered 0-7 from left to right. |
| 16 |
|
| 17 |
I - Remote Job Entry (RJE) |
| 18 |
|
| 19 |
UCSB will accept input of pseudo card files for batch processing |
| 20 |
at socket number x'200', site 3. Network users should obtain an |
| 21 |
account number from the UCSB Computer Center; account #1025, |
| 22 |
programmer names 'UCLA', 'SRI', 'UTAH', etc. may be used during |
| 23 |
checkout. The 360/75 runs under OS MVT and HASP. Users submit jobs |
| 24 |
to HASP for scheduling and subsequent execution by OS through an |
| 25 |
intermediary process hereafter called RJE which is addressed as socket |
| 26 |
number x'200' and can be invoked through the Logger. This section is |
| 27 |
intended to provide programmers with the information necessary to |
| 28 |
communicate with RJE; the is assumed familiar with the batch services |
| 29 |
offered by the Computer Center, and with its job control language |
| 30 |
(JCL) requirements. |
| 31 |
|
| 32 |
RJE conducts all Network transactions through the NCP, which |
| 33 |
operates under the Host-Host protocol of 3 August 1970. It expects |
| 34 |
the first message it receives to be Type 0, discards the first eight |
| 35 |
bits (the message type) assuming them to be zeros, and thereafter for |
| 36 |
the life of the connection takes no notice of IMP-message boundaries. |
| 37 |
|
| 38 |
I.A - Logging into RJE |
| 39 |
|
| 40 |
To submit one or more jobs for batch processing, the Network user |
| 41 |
must establish a simplex connection with RJE. RJE is core resident |
| 42 |
only while such a simplex connection is established (i.e., while a |
| 43 |
user is transmitting a file). At all other times, it resides on |
| 44 |
direct-access storage and must be invoked through the Logger. A login |
| 45 |
sequence can always be initiated by requesting connection to socket |
| 46 |
x'200'. RJE does not serve multiple users simultaneously. This if a |
| 47 |
connection request is made to that socket while RJE is in use, the NCP |
| 48 |
will queue the request. When the current file transmission is |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">White [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc105">RFC 105</a> RJE at UCSB March 1971</span> |
| 55 |
|
| 56 |
|
| 57 |
complete, RJE will listen for and accept the next request (if any) in |
| 58 |
its queue; if no requests are queued for it, it will terminate |
| 59 |
execution, releasing the main storage it occupied. At times when RJE |
| 60 |
is not in core, the Logger listens on socket x'200', and will reject |
| 61 |
the first call it receives, read RJE into core, and dispatch it. RJE |
| 62 |
will then list on that socket. Thus to initiate a login sequence, the |
| 63 |
user requests connection to socket x'200'. If accepted, he is in |
| 64 |
contact with RJE. If rejected, he should reissue the connection |
| 65 |
request; when accepted, he will be connected to RJE. A second |
| 66 |
rejection would indicate that the NCP's resources were exhausted. |
| 67 |
Once the connection has been established, RJE will consider the user |
| 68 |
logged in. |
| 69 |
|
| 70 |
To prevent RJE from being monopolized by a single user, provision |
| 71 |
is made within the software for terminating a connection if RJE is |
| 72 |
ever required to wait more than a certain amount of time for a |
| 73 |
transmission from the connected user. For now, this time limit has |
| 74 |
been set at one minute per record, but it may be shortened or |
| 75 |
lengthened as required in the future. Barring such termination, RJE |
| 76 |
will maintain its connection to the user indefinitely. Card images |
| 77 |
will be accepted over the connection, and each one will be passed to |
| 78 |
HASP as it is received. The user is expected to close the connection |
| 79 |
once his file has been transmitted. RJE will interpret that action as |
| 80 |
an end-of-file indication, and the user will be considered logged off. |
| 81 |
|
| 82 |
I.B - The RJE Connection |
| 83 |
|
| 84 |
RJE expects the first byte of data it receives over the |
| 85 |
connection established with it to be zeros, indicating message Type 0; |
| 86 |
it discards this byte unexamined, and thereafter, attaches no |
| 87 |
significance to IMP-message boundaries. The second byte of data |
| 88 |
received is interpreted as flags specifying the format of the data |
| 89 |
(file) to follow. The byte is interpreted as follows: |
| 90 |
|
| 91 |
Bits 0-1 = 00: file follows as Class A (stream-oriented) |
| 92 |
input. |
| 93 |
= 01: not defined, should not occur. |
| 94 |
= 10: file follows as Class B (variable-length |
| 95 |
record) input. |
| 96 |
= 11: file follows as Class C (fixed-length record) |
| 97 |
input. |
| 98 |
Bits 2-7 : not examined, should be zeros. |
| 99 |
|
| 100 |
Once made, this declaration prevails for the life of the connection. |
| 101 |
|
| 102 |
Regardless of the input class specified, the user transmits his |
| 103 |
file as card images, each of which will be padded on the right with |
| 104 |
blanks or truncated on the right to 80 bytes if necessary. The file |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">White [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc105">RFC 105</a> RJE at UCSB March 1971</span> |
| 111 |
|
| 112 |
|
| 113 |
transmitted must be structured exactly as if it were being placed on |
| 114 |
the card reader at the Computer Center. A job card and all the other, |
| 115 |
usual JCL must be present for each job in the file (batching of jobs |
| 116 |
is permissible and is transparent to RJE). For any job which requires |
| 117 |
that special (non-resident) disk(s) and/or tape(s) to be mounted, a |
| 118 |
special JCL card must be inserted immediately after the job card for |
| 119 |
that job, and it must have the format: |
| 120 |
|
| 121 |
/*SETUP vol-ser , vol-ser ,... |
| 122 |
1 2 |
| 123 |
|
| 124 |
where 'vol-ser ' is the volume serial number of a volume requiring |
| 125 |
i |
| 126 |
mounting. '/*SETUP' begins in column 1; 'vol-ser ' must begin in |
| 127 |
1 |
| 128 |
column 16. The job will then enter the System in a HASP hold status |
| 129 |
until the required volume(s) can be mounted by the operator. If the |
| 130 |
user neglects to declare all such required volumes, his job is subject |
| 131 |
to immediate cancellation. All cards of the file which are not |
| 132 |
contained in a SYSIN data set must consist of valid, EBCDIC |
| 133 |
characters. |
| 134 |
|
| 135 |
I.B.1 - Class A (Stream-Oriented) Input |
| 136 |
|
| 137 |
If input to RJE has been declared as Class A, the third byte of data |
| 138 |
received over the connection by RJE is interpreted as a break character |
| 139 |
declaration. Each byte received thereafter is compared to that |
| 140 |
character. Any other character is taken to be the next byte of the |
| 141 |
current card image. Whenever the break character is encountered, the |
| 142 |
previous byte is taken to be the last byte of the current card image, |
| 143 |
which is then padded or truncated as required and passed to HASP. Zero |
| 144 |
or more non-break characters may occur between occurrences of the break |
| 145 |
character. Thus when Class A input is specified, data transmitted to |
| 146 |
RJE shall have the following form: |
| 147 |
|
| 148 |
1 1 1 variable 1 |
| 149 |
+-------+-------+-------+ / +------//--------+-------+ \ |
| 150 |
| | | BREAK | / | | BREAK | \ |
| 151 |
| x'00' | x'00' | CHAR. | \ | CARD IMAGE | CHAR. | / ... |
| 152 |
+-------+-------+-------+ \ +------//--------+-------+ / |
| 153 |
|
| 154 |
where the length of each field has been specified in bytes. Zero or |
| 155 |
more occurrences of the quantity in parentheses [angle brackets] may be |
| 156 |
transmitted before the connection is closed by the user. |
| 157 |
|
| 158 |
I.B.2 - Class B (Variable-Length Record) Input |
| 159 |
|
| 160 |
If input to RJE has been declared as Class B, then all input after |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">White [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc105">RFC 105</a> RJE at UCSB March 1971</span> |
| 167 |
|
| 168 |
|
| 169 |
the initial two bytes is expected to consist of a contiguous string of |
| 170 |
variable length records, each consisting of a one-byte op code (the op |
| 171 |
code should be x'01'), a two-byte length field which specifies the |
| 172 |
unsigned length in bits of the variable-length text field which follows. |
| 173 |
The text field may be zero or more bytes in length; the length field |
| 174 |
must contain an integer which is a multiple of 8. The text field |
| 175 |
represents one card image, which is padded or truncated by RJE as |
| 176 |
required and passed to HASP. Thus when Class B input is specified, data |
| 177 |
transmitted to RJE shall have the form: |
| 178 |
|
| 179 |
1 1 1 2 L bits |
| 180 |
+-------+-------+ / +-------+-------+-----//-----+ \ |
| 181 |
| | | / | | | TEXT | \ |
| 182 |
| x'00' | x'80' | \ | x'01' | L | card image | / ... |
| 183 |
+-------+-------+ \ +-------+-------+-----//-----+ / |
| 184 |
|
| 185 |
where the length of each field has been specified in bytes, except where |
| 186 |
stated to the contrary. Zero or more occurrences of the quantity in |
| 187 |
parentheses [angle brackets] may be transmitted before the connection is |
| 188 |
closed. |
| 189 |
|
| 190 |
I.B.3 - Class C (Fixed-Length Record) Input |
| 191 |
|
| 192 |
If input to RJE has been declared as Class C, then all input after |
| 193 |
the initial two bytes is expected to consist of a contiguous string of |
| 194 |
fixed-length, 80-byte card images. Thus, when Class C input is |
| 195 |
specified, data transmitted to RJE shall have the form: |
| 196 |
|
| 197 |
1 1 80 |
| 198 |
+-------+-------+ / +--------------------+ \ |
| 199 |
| | | / | | \ |
| 200 |
| x'00' | x'C0' | \ | card image | / ... |
| 201 |
+-------+-------+ \ +--------------------+ / |
| 202 |
|
| 203 |
where the length of each field has been specified in bytes. Zero or |
| 204 |
more occurrences of the quantity in parentheses [angle brackets] may be |
| 205 |
transmitted before the connection is closed. |
| 206 |
|
| 207 |
II - Remote Job Output Retrieval (RJOR) |
| 208 |
|
| 209 |
Class A SYSOUT output from jobs submitted through RJE for batch |
| 210 |
processing at UCSB may be obtained by contacting socket x'300', site 3, |
| 211 |
provided that when the job was submitted, the character 'T' appeared as |
| 212 |
the eighth positional accounting parameter on the job card. Output is |
| 213 |
retrieved upon request and relayed to the Network user by a process |
| 214 |
hereafter called RJOR which is addressed as socket x'300'. RJOR can be |
| 215 |
invoked through the Logger. This section is intended to provide |
| 216 |
programmers with the information necessary to communicate with RJOR. |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">White [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc105">RFC 105</a> RJE at UCSB March 1971</span> |
| 223 |
|
| 224 |
|
| 225 |
RJOR conducts all Network transactions through the NCP, which |
| 226 |
operates under the Host-Host protocol of 3 August 1970. RJOR expects |
| 227 |
the first message it receives to be Type 0, discards the first byte, |
| 228 |
assuming it to be zeros, and thereafter for the life of the connection |
| 229 |
takes no notice of IMP-message boundaries. Similarly, the first message |
| 230 |
sent by RJOR is of Type 0: the first byte consists of zeros, and |
| 231 |
thereafter for the life of the connection, IMP-message boundaries are |
| 232 |
not significant. |
| 233 |
|
| 234 |
II.A - Logging into RJOR |
| 235 |
|
| 236 |
To obtain output from a batch-mode job, the Network user must |
| 237 |
establish a full duplex connection with RJOR. RJOR is core resident |
| 238 |
only while in use (i.e., while control information or a file is being |
| 239 |
transmitted to or from a user, or while RJOR is waiting for a previously |
| 240 |
requested output file (or files)). At all other times, it resides on |
| 241 |
direct-access storage and must be invoked through the Logger. A login |
| 242 |
sequence can always be initiated by requesting connection to socket |
| 243 |
x'300'. If a connection request is made to that socket while another |
| 244 |
user is being logged in, the NCP will queue the request. After the |
| 245 |
current connection is terminated, RJOR will listen for and accept the |
| 246 |
next request (in any) in its queue; if no requests are queued for it and |
| 247 |
if it has fulfilled all of its output file requests, it will terminate |
| 248 |
execution, releasing the main storage it occupied. At times when RJOR |
| 249 |
is not in core, the Logger listens on socket x'300', and will reject the |
| 250 |
first call it receives, read RJOR into core, and dispatch it. RJOR will |
| 251 |
then listen on that socket. Thus to initiate a login sequence, the user |
| 252 |
requests connection to socket x'300'. If accepted, he is in contact |
| 253 |
with RJOR. If rejected, he should reissue the connection request; when |
| 254 |
accepted, he will be connected to RJOR. A second rejection would |
| 255 |
indicate that the NCP's resources were exhausted. Once this first half |
| 256 |
of the required duplex connection has been established, RJOR will |
| 257 |
consider the user logged in. |
| 258 |
|
| 259 |
Over this first connection (hereafter called the Input Connection), |
| 260 |
the user transmits flags designating the function(s) to be performed by |
| 261 |
RJOR, and the name of the job to which the function(s) is(are) to be |
| 262 |
applied. RJOR then closes this connection. RJOR transmits control |
| 263 |
information specifying the disposition of the user's request and the |
| 264 |
output file (if requested) over a secondary connection involving RJOR's |
| 265 |
socket number x'301', site 3, and the socket at the user's site whose |
| 266 |
socket number is one less than that on which RJOR was contacted by the |
| 267 |
user. The user's request may or may not be immediately executable. If |
| 268 |
the former is the case, RJOR issues a connection request to the |
| 269 |
designated user receive socket, and when the connection is established |
| 270 |
transmits whatever control information is appropriate along with the |
| 271 |
user's output (if required); RJOR then closes the connection and the |
| 272 |
user is considered logged out. If the user's request cannot be |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">White [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc105">RFC 105</a> RJE at UCSB March 1971</span> |
| 279 |
|
| 280 |
|
| 281 |
immediately satisfied (e.g., the job whose output is sought hasn't been |
| 282 |
submitted yet or hasn't finished execution), the second connection is |
| 283 |
opened by RJOR just long enough to inform the user of the delay, and |
| 284 |
then closed. Then when the request can be serviced, the connection is |
| 285 |
reopened, the required data transmitted, and the connection closed; the |
| 286 |
user is then considered logged out. |
| 287 |
|
| 288 |
To prevent RJOR from being monopolized by a single user, provision |
| 289 |
is made within the software for terminating a connection if RJOR is ever |
| 290 |
required to wait more than a certain amount of time for completion of a |
| 291 |
transmission to or from the connected user. For now, this time limit |
| 292 |
has been set at one minute per record, but it may be shortened or |
| 293 |
lengthened as required in the future. |
| 294 |
|
| 295 |
II.B - The Input Connection |
| 296 |
|
| 297 |
RJOR expects the first byte of data it receives over the Input |
| 298 |
Connection to be zeros, indicating message Type 0; it discards this byte |
| 299 |
unexamined, and thereafter, attaches no significance to IMP-message |
| 300 |
boundaries. The second byte of data received is interpreted as flags |
| 301 |
specifying the function(s) to be performed. Following the flag byte, |
| 302 |
RJOR expects an eight-byte, EBCDIC job name, padded on the right with |
| 303 |
blanks if necessary. The flag byte is interpreted as follows: |
| 304 |
|
| 305 |
Bit 0 = 1: transmit the output generated by the specified job. |
| 306 |
Bit 1 = 1: purge the output file created by the specified job. |
| 307 |
Bit 2 = 1: wait as long as is required to execute the |
| 308 |
function(s) specified by Bits 0-1. |
| 309 |
= 0: if the function(s) specified by Bits 0-1 cannot be |
| 310 |
executed immediately, simply return an indication of |
| 311 |
that fact. |
| 312 |
Bit 3 = 1: an earlier request pertaining to the specified job |
| 313 |
which exercised the wait-for-output (Bit 2) option |
| 314 |
is to be canceled. |
| 315 |
Bits 4-7: not examined, should be zeros. |
| 316 |
|
| 317 |
Any combination of Bits 0-2 is permissible. If Bit 3 = 1, no other bits |
| 318 |
are examined. If Bit 0 = 1 and Bit 1 = 1, the output file is |
| 319 |
transmitted before it is purged. If two jobs with the same name are |
| 320 |
executed in succession, output from the second job will overlay that |
| 321 |
produced by the first. In such cases, the user should purge the output |
| 322 |
from the first job after it has been transmitted to him so that a |
| 323 |
request for output from the second job will not simply return a second |
| 324 |
copy of the first job's output. |
| 325 |
|
| 326 |
II.C - The Output Connection |
| 327 |
|
| 328 |
RJOR may open the output connection either one or two times as the |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">White [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc105">RFC 105</a> RJE at UCSB March 1971</span> |
| 335 |
|
| 336 |
|
| 337 |
result of a single transmission on the Input Connection. In each case, |
| 338 |
the first byte transmitted will consist of zeros indicating message Type |
| 339 |
0, and thereafter for the life of the connection, IMP-message boundaries |
| 340 |
are not significant. Following the first byte, RJOR will transmit the |
| 341 |
name of the job to which the response applies. The job name will be |
| 342 |
contained in an 8-byte field identical to that supplied by the user over |
| 343 |
the Input Connection. Following the job name, RJOR will transmit zero |
| 344 |
or more variable length logical records. Each will consist of a one- |
| 345 |
byte op code, a two-byte length field which specifies the unsigned |
| 346 |
length in bits of the variable length text field which follows. The |
| 347 |
text field may be zero or more bytes in length; the length field will |
| 348 |
contain an integer which is a multiple of eight. |
| 349 |
|
| 350 |
The op codes presently defined are listed in Figure 1. An op code |
| 351 |
of x'01' indicates that the text field contains one record of one of the |
| 352 |
SYSOUT data sets created by the job whose output was requested. The |
| 353 |
length fields of all logical records with an op code of x'01' will be |
| 354 |
identical. For data sets with record lengths other than this value, |
| 355 |
records are padded on the right side with blanks or truncated on the |
| 356 |
right to this standard record length. Carriage control characters which |
| 357 |
would ordinarily appear in column 1 for printer-destined output have |
| 358 |
been discarded and do not appear.* The records are transmitted to the |
| 359 |
user in the same sequence as they would be printed on the printer, and |
| 360 |
collectively include everything that would appear in printed output with |
| 361 |
the exception of HASP separator sheets. |
| 362 |
|
| 363 |
In all logical records but those with an op code of x'01', the |
| 364 |
length field contains the value zero, and the op code conveys the entire |
| 365 |
meaning of the logical record. |
| 366 |
|
| 367 |
|
| 368 |
|
| 369 |
|
| 370 |
|
| 371 |
|
| 372 |
|
| 373 |
|
| 374 |
|
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
________________________________________________________________________ |
| 383 |
*This restriction is temporary; a fix is in the works and will be |
| 384 |
announced. |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">White [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc105">RFC 105</a> RJE at UCSB March 1971</span> |
| 391 |
|
| 392 |
|
| 393 |
Figure 1. Output Connection Op Codes |
| 394 |
--------- -------------------------- |
| 395 |
|
| 396 |
Op Code |
| 397 |
(Hex) Name Explanation |
| 398 |
------- ---- ----------- |
| 399 |
|
| 400 |
00 End-of-File. All output from the job has been |
| 401 |
transmitted (follows last op-code-x'01' |
| 402 |
logical record). |
| 403 |
01 Output. The text field contains one record of |
| 404 |
one SYSOUT data set generated by the |
| 405 |
job. |
| 406 |
02 Output file purged. Output from the job has been purged as |
| 407 |
requested. |
| 408 |
03 No core for buffer. Insufficient main storage is available |
| 409 |
for transmitting output from the job. |
| 410 |
The transmission request has been |
| 411 |
aborted and the purge request (if any) |
| 412 |
has been suppressed. |
| 413 |
04 I/O Error reading An irrecoverable I/O error was |
| 414 |
file. encountered reading the output file. |
| 415 |
The transmission request has been |
| 416 |
aborted and the purge request (if any) |
| 417 |
suppressed. |
| 418 |
05 I/O Error purging An irrecoverable I/O error was |
| 419 |
file. encountered purging the output file. |
| 420 |
The purge request was aborted. |
| 421 |
06 No queue space for Output from the job was not available |
| 422 |
request. and the wait-for-output option was |
| 423 |
specified, but RJOR's resources were |
| 424 |
insufficient to queue the request, |
| 425 |
which was suppressed. |
| 426 |
07 Waiting for output. Output from the job is not available |
| 427 |
and the wait-for-output option was |
| 428 |
specified. RJOR is waiting for the |
| 429 |
job's output. |
| 430 |
08 Canceled request not The user requested that a previously |
| 431 |
found. made request specifying the |
| 432 |
wait-for-output option be canceled. No |
| 433 |
such request was found by RJOR. |
| 434 |
09 Request canceled. At the user's request, a previously |
| 435 |
made request specifying the |
| 436 |
wait-for-output option has been |
| 437 |
canceled. |
| 438 |
0A I/O Error seeking An irrecoverable I/O error was |
| 439 |
file. encountered attempting to locate output |
| 440 |
from the job. The user's request was |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">White [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc105">RFC 105</a> RJE at UCSB March 1971</span> |
| 447 |
|
| 448 |
|
| 449 |
aborted. |
| 450 |
0B Output not found. Output from the job was not found. The |
| 451 |
wait-for-output option was not |
| 452 |
specified by the user. |
| 453 |
|
| 454 |
[ This RFC was put into machine readable form for entry ] |
| 455 |
[ into the online RFC archives by Randy Dunlap 4/97 ] |
| 456 |
|
| 457 |
|
| 458 |
|
| 459 |
|
| 460 |
|
| 461 |
|
| 462 |
|
| 463 |
|
| 464 |
|
| 465 |
|
| 466 |
|
| 467 |
|
| 468 |
|
| 469 |
|
| 470 |
|
| 471 |
|
| 472 |
|
| 473 |
|
| 474 |
|
| 475 |
|
| 476 |
|
| 477 |
|
| 478 |
|
| 479 |
|
| 480 |
|
| 481 |
|
| 482 |
|
| 483 |
|
| 484 |
|
| 485 |
|
| 486 |
|
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
White [Page 9] |
| 501 |
</pre> |