During VLSUTIL backup I am receiving these OUT OF SEQUENCE error messages:
MEMBER NAME IN THE INDEX IS OUT OF SEQUENCE AND HAS BEEN SKIPPED. NAME IS $IDDEMOPGMA 001R
MEMBER NAME IN THE INDEX IS OUT OF SEQUENCE AND HAS BEEN SKIPPED. NAME IS $IDDEMOPGMA 001L
MEMBER NAME IN THE INDEX IS OUT OF SEQUENCE AND HAS BEEN SKIPPED. NAME IS $IDDEMOPGMA 001P
Names included in that message are source member names from customer.
Messages displayed above are just an example about the message format you may get.
These messages are due to INDEX Corruption.
Resolution is to repair the VLS library via the following steps:
1. VLSUTIL BACKUP VLS source.
2. Allocate new data set VLSUTIL FORMAT/RESTORE from full BACKUP
3. VLSUTIL SELBKUP each VLS MEMBER flagged in BACKUP errors.
4. VLSUTIL RESTORE NOCLEAR(R) from the SELBKUP file.
If SELBKUP fails use IDEAL Source Transport EXPORT.
Note1: VLSUTIL with RESTORE NOCLEAR(R)
"R" to replace MEMBERs with same name
and "NOCLEAR" to not remove what is already in the VLS file.
For all those MEMBER NAME IN THE INDEX IS OUT OF SEQUENCE AND HAS BEEN SKIPPED
you need to do SELBKUP for each MEMBER then you can do a RESTORE NOCLEAR
The RESTORE is missing all these "out of Sequence" members.
The message is informing you of a corruption that occurred at some previous time.
Be sure to have IPC 15.0 APAR #: RO75397.
Take VLSUTIL backup on regular basis and fairly often and check output so any error can be corrected quickly.
Index corruption can be due to:
- Previous abends.
- Misuse of DEQUE commands.
- VLS Blocksize not matching the FCT definitions on all systems.
- The system should be QUIESED (down) when library functions are performed. The library functions are BACKUP, FORMAT, INIT, and RESTORE.
- Not using standard backup utilities; VLSUTIL is highly recommended because it performs additional file verification.