RRN 07292 IOS PERIPHERAL SERVICE ROUTINES

YSHNWT03

Message Triggering Condition

Result of the execution of the following command:
CRN 07835 DISP-HIS-FILE

Report Layout

   PERIPHERAL SERVICE ROUTINES
      (A).......................                           (B).................
                                         (C)...........................(D).(E)
      -------------------------------------------------------------------------
      DEVICE ID       = (1).....          VOLUME IDF = (2)...          (3)
      NBR OF RECORDS  = (4)..
      EXIST RECORDS   = (5)..
      HISTORY FILE ID = (6)..
      VMT FILE ID     = (7)..
      PARTITION IDF   = (8).....................
      COMMENTARY      = (9)..................................
      DB CPL CODE     = (10)........ / (11)
      IOS CPL CODE    = (12)...... / (13).....................................
      ERROR FILE ID   = (14).
      LOC IN HFM      = (15).
          MARKET SEGMENT    DLS / BASE MOD   CAE     PLS / SOKO       MOD
      -------------------- ----------------- --- -----------------  --------
      (17)................ (18).................................... (19)....
  REPORT REFERENCE NUMBER = 7292

Parameter Identification

Par. No. Meaning Remarks
(A) command name
(B) main execution result
(C) result part type
(D) result part number
(E) continuation indicator
(1) Logical device identity
(2) Volume identifier for (1)
(3) Indicator for a Data Load Partition (DLP) of an Optical Disk
(4) Number of records to be displayed
ALL Display the complete history
file(s)
MERGE Display the merged history
file(s)
(5) Number of existing records in the History File
(6) Logical file identity of the History File
(7) Logical file identity of the VMT file
ALL Display the history file of all
VMT files
(8) Partition identifier for (1)
(9) Commentary in the error case
(10) Data base error code Maincode
(11) See (10) Subcode
(12) IOS error code Maincode
(13) See (12) Subcode
(14) Logical error file identity
(15) Location in the History File Manager FMM, where this error was occured
(17) Market segment number
(18) Other numbers resp. entries :
- DLS (Data Load Segment) number
- Base modification
- CAE GDMH (ELT3/ELP3) number
- PLS (Patch Load Segment) number
- SOKO (Fast correction) number
(19) Modification

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(B) SUCCESSFUL . . . . . . . . . . . . . . . . . . . . Z
(9) BAD DEVICE INFO . . . . . . . . . . . . . . . . . B
(9) BAD GET PARTITION INFO . . . . . . . . . . . . . . A
(9) BAD GET R-HFIL-NB1 . . . . . . . . . . . . . . . . B
(9) BAD HISTORY FILE . . . . . . . . . . . . . . . . . C
(9) BAD LF-PRES REQUEST . . . . . . . . . . . . . . . A
(9) BAD MOUNT ODK . . . . . . . . . . . . . . . . . . B
(9) BAD OPEN FILE . . . . . . . . . . . . . . . . . . B
(9) BAD READ FILE . . . . . . . . . . . . . . . . . . B
(9) FORCE RELEASE . . . . . . . . . . . . . . . . . . A
(9) INVALID DEVICE . . . . . . . . . . . . . . . . . . D
(9) INVALID HISTORY FILE CHARACTERIZATION . . . . . . C
(9) INVALID HISTORY FILE ID IN R-HFIL-NB1 . . . . . . C
(9) JOB ABORTED BY OPERATOR . . . . . . . . . . . . . Z
(9) NO VMT FILES DO EXIST . . . . . . . . . . . . . . Z
(9) THE HISTORY FILE MANAGER FMM IS BUSY . . . . . . . E
(9) THIS IS NO VMT FILE . . . . . . . . . . . . . . . D
(9) TIME OUT (DEVICE INFO) . . . . . . . . . . . . . . A
(9) TIME OUT (GET PARTITION INFO) . . . . . . . . . . A
(9) TIME OUT (LF-PRES REQUEST) . . . . . . . . . . . . A
(9) TIME OUT (MOUNT ODK) . . . . . . . . . . . . . . . A
(9) TIME OUT (OPEN VMT FILE) . . . . . . . . . . . . . A
(9) TIME OUT (READ FILE) . . . . . . . . . . . . . . . A

Action Description

Action Meaning
A Re-submit the job. If unsuccessful again, call the system specialist for a fault clearing. After successful maintenance activity, re-submit the job.
B Pay attention to the error message. If necessary, re-submit the job. If the result is unsuccessful again, cause a fault clearing. After a successful fault clearing re-submit the job.
C Data failure on disk. Arrange a fault clearing.
D Check the input data. If necessary, correct the input data and re- submit the job. If the result is unsuccessful again, arrange a fault clearing. After successful maintenance activity, re-submit the job.
E Wait until the previous job is ended. Then re-submit the job.
Z No action necessary.