• Aucun résultat trouvé

APPENDIX E: S~ANDARD TAPE FILE LAIELS

Dans le document Systems Reference Library (Page 160-165)

1& ignored

APPENDIX E: S~ANDARD TAPE FILE LAIELS

~---ro-r-r-r-.-r---l;~..--.--r--t-...".-.---.----.--t--o- T-~+~~~-+

Number Number Number

Label

FilE SEQUENCE NUMBER 4 bytes

uniquely identifies the entire file, may contain only printable characters.

uniquely identifies a file/volume relationship. This field is identical to the Volume Serial Number in the are numbered in consecutive sequence by the OPEN (R) macro on output and thus checked in that manner on input.

assigns numeric sequence to a fi Ie within a multi - file set.

numerically identifies the various editions of the file.

indicates the version of a generation of a file.

Position Code Meaning

1 blank none multifi Ie reel, processed sequentia Ily all files are considered to expire on the same day.

indicates security status of the fi Ie.

o = no security protection 1 = security protection.

Addi-tiona identification of the file is required before it can be processed.

indicates the number of data blocks written on the fi Ie from the last header label to the first trailer label exclusive of tape marks. Count does not include checkpoint records.

This field is used in Trailer Labels.

uniquely identifies the programming system.

Reserved for American Standards Association (A.S.A.). At present, should be recorded as blanks.

Reserved For A.S.A.

APPENDIX F: VTOC LISTINGS

For a complete description of the various label formats, refer to IBM System/360 Disk Operating System, Data Management Concepts, Form C24-3427. These displays can be

o1:::tained by replying CANCELV or DSPLYV to certain LIOCS messages. (Refer to the section, LIOCS (Disk) and Corrmon Open/Close Messages, in this manual.

CANCELV DISPLAY

VOLUME SERIAL NUMBER IS 111111 11/04/66

00C7000001 FORMAT 4 LABel

040"0404 01t01t0404 04040404 0401t0404 0~.0401t04 01t040404 04040404 04040404 04040404 0,.040404 04040"04 FltOOOOOO 0000009E 00000000 001E9001 OOOOOOCB OOOAOE29 51141401 02191JOA 00000000 00000000 00000000 00000000 0000)000 00000000 00000000 00010000 C7000000 C7000400 00000000 00000000 00000000 00000000 00000000 00000000

00C7000002 FORMAT 5 LASH

05050505 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 F5000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

00C7000003 FORMAT 1 LABEL

FILEA SERIAL ~O. 111111 VOL NO. 0001 420043-420043 010000 Sys. CODE IS

POINTER IS

16 K DISK 80S 0000000000 0000000000 0000400000 0000000000 0000000000 0000000000 0000000000

0100 00330000-006E0009 0000 00000000-00000000 0000 00000000-00000000 00C7000004 FORMAT 1 LABEL

SYSTEM WORK FI.LE NO. 1 SERIAL NO. 111111 VOl NO. 0001 42006E-630160 0000000000 0000400000 0000000006 ooOOOOBOOO 0000000000 0000000000

0100 00970000-00900009 0000 00000000-00000000 0000 00000000-00000000 00C7000005 FORMAT 1 LABEL

010000 SYS. COOE IS POINTER IS

ODS 0000000000

2311 OTFPH-SEQUENTIAL OPEN 'NO' USER LABELS. SERIAL NO. 111111 VOL NO. 0001 410140-~2012C 030000 SYS. CODE IS •• StMONIK ••

0000000000 0000400000 0000000000 0000000000 0000000000 0000000000

0100 00AFOOOO-00AF0002 0101 00AF0003-00AF0003 0102 00AF0004-00AF0004 POINTER IS 0000000000

VTOC LISTING COMPLETED

DSPLYV option provides identification information and XTENT boundaries for Format 1 and/or 3 labels.

This information is extracted from the VTOC and appears in the following format.

~---~

DSPLYV DISPLAY

VOLUME SERIAL NO. IS 111111 FILEA

0100 oo330000-006E0009--.,. Xtent Infonnatlon SYSTEM WORK FILE NO. I

0100 00970000-00900009

Serial No. Volume No.

\ I

11/04/66

1111111 0001 420043-420043--.... Creation & Expiration Dates

1111111 0001 42006E-63016D

2311 DTFPH-SEOUENTIAL OPEN 'NO' USER LABELS.lllllll 0001 410140-42012C 0100 00AfOOOO-00AF0002 0101 00AF0003-00AF.OO03 0102 00AF0004-00AF0004 VTOC LISTING COMPLETED

L ____________________________ ---_________________________ ~

Figure 19. VTOC Listings

Appendix F 161

APPENDIX G: SEREP

SEREP (System Environment Recording, Editing, and Printing) is a program distributed as part of the diagnostic package for each System/360 installation.

The program, with its operating procedures, is available to the installation's IBM customer Engineer. (Each System/360 model has a different version of the SEREP

program. Operating procedures, however, are the same for all versions.)

SEREP provides a means of printing the system status information stored in main storage at the time of a machine

malfunction. When a condition occurs requiring the use of SEREP, the wait state is entered, and main storage byte 1

contains an S. The SEREP program must be loaded via the standard IPL procedure.

Malfunction information is produced as output on an online printing device. The SEREP printout indicates the environment of the error and the device involved.

The address of the I/O device printed on the SEREP report is compared with the valid device addresses available to the system.

The printing of a valid address indicates that a machine malfunction has occurred.

The printing of an invalid device address indicates that a programming error has occurred. After SEREP is completed, the system is restarted via the IPL procedure.

APPENDIX H: DEFAULT OPERATION WITHOUT A 1052 PRINTER-KEYBOARD

If the 1052 Printer-Keyboard is inoperable, limited operations (refer to Syst;em

OFerating Without a 1052) may continue, under some circumstances, by displaying messages in low core and entering the proFer reply directly in core. In this aFpendix, IPL messages and device error recovery messages are described.

IPL ERROR MESSAGES

If the machine enters the wait state during an IPL procedure, the operator smould

display the first five bytes of low core.

The IPL error message number and action code are displayed in hexadecimal in these bytes (see Figure 11). For example:

Message OI11A appears in low core bytes 0-4 as

FOC9F1F1Cl

The operator should look up this message (refer to System-to-Operator Messages) and perform the indicated action.

DEVICE ERROR RECOVERY MESSAGES

Figure 11 shows the information that might be found in the low core error bytes. If byte 0 contains a binary number 08-60, i t indicates a (OP) device error recovery message. If the 1052 is inoperable when an error recovery message is issued, the

system immediately enters the wait state until the operator replies. The operator should display the contents of byte 1 to obtain the action code, in BCD.

If code is A (Cl):

If code is

D (C4):

The operator should refer to System-to-Operator Messages. If the operator decides to try to continue operations, i t will be

necessary to display the next two bytes (2 and 3) of low core to obtain the channel and unit number of the device.

The operator should then:

1. Perform any manual recovery procedures implied by the error condition. (Refer to component description and operating procedures manual for the device.) 2. Ready the device. No

response is necessary. If the operator wishes to cancel, he should insert X'03' in byte 4 and press INTERRUPT.

A trial-and-error procedure must be performed. The operator should first store X'Ol' (RETRY) in byte 4, then press INTERRUPT on the

console. If the system accepts this reply, the machine exits from the wait state. If not, store one of the following replies in byte 4:

• X'02' (IGNORE)

• X' 03' (CANCEL)

Then press INTERRUPT. When the reply is accepted by the system, the machine will exit from the wait state.

Appendix H 163

r---T---T---T---T---,

, Byte 0 , , I , ,

, (Binary) , Byte 1 , Byte 2 'Byte 3 , ,

,Message , (BCD) , (Binary) , (Binary) , Action ,

~---+---+---+---+---~

, 00 , S , Not used' Not used' Machine Check. System must be IPL'ed. Load,

, , , I , SEREP. ,

~---,---+---+---+---+---~---~

, 01 , S , Reserved , Reserved , Channel Failure: Interface Control Check, ,

, , , , , or Channel Control Check. System must be ,

I , , , 'IPL'ed. Load SEREP. ,

~---+---+---+---+---~

, 02 , , , , Reserved ,

~---+---+---+---+---~

, 03 , W ,Channel, Unit , DOS - Irrecoverable disk error during ,

, , , I , program fetch. The first six sense bytes ,

I , I I I are placed in hex Bytes 5-A. System must be'

, I , , , IPL' ed. I

~---+---+---+---+---~

, 04 , W , Not used I Not used , Cancel condition has occurred while ,

I , , , , performing a Supervisor fUnction. (Not a ,

, , , I I Supervisor detected problem-program error.) ,

I , , , , Normally a Program Check while in supervisor'

, , , , I State. System must be IPL'ed. I

~---+---+---+---+---~

, 05 I W 'Channel I Unit 'I/O Error Queue has overflowed as the result, , , I I I of an I/O error on a program fetch channel I

I I , I I program. System must be IPL'ed. ,

~---+---+---+---+---~

I 06 I I I I Reserved ,

~---+---+---+---+---~

, 07 I W I Channel ,Unit I IPL I/O error. Channel and unit indicate I

I , I I I whether SYSRES or communication device. I

I I I I I system should be re-IPL'ed. I

~---+---+---+---+---~

I 08-60 ,Action I Channel I Unit I Error recovery messages. Refer to OP I

, I Indi- I I , messages in message section. I

I ,cator I , , I

L ___________ ~ ________ ~ __________ ~ __________ ~ _____________________________________________ J

Figure 20. Lew Core Error Bytes

The complete text for message OSO L~I is:

ILLEGAL SVC - HEX LOCATION nnnnnn -SVC CODE nn

where nn is in hexadecimal notation.

This message can result from the following causes.

1. When nn is 02: The phase name given does not start with $$B, or

For LIOCS, macros called in invalid sequence. As a result, an SVCS is issued after an SVC2 before an SVC9 has been issued to free the transient area, or

For other conditions, the user

s~ecified a temporary exit (SVCS) for a logical transient. In the temporary exit routine, another routine is called

(by an SVC2) before an SVC9 is issued to free the transient area.

2. When nn is 05: The "to" range

s~ecified in the MVCOM macro is invalid, or

MVCOM macro was issued by a foreground program, operating under single program initiation.

Dans le document Systems Reference Library (Page 160-165)

Documents relatifs