ICSCMSGP06T/IDADERRP11

Products

Ideal

Issue/Introduction

Hi, We have these message ERROR since early this morning and the users can't use their Printer at all :

We have these message ERROR since early this morning and the users can't use their Printer at all :

B725 ***** START OF IDL ERROR LOG ON 18/10/03 AT 06:01:27 *****
B725 1-ICSCMSGP06T - INTERR: I/O ERROR WHILE ACCESSING MESSAGE LIBRARY 1-IDPSM
B725 SRVC=VLS FUNC=INIT RC=004-12 PGM=SC00MSGP14.0 -1476
B725 CALPGM=SC00MSGP14.0 -186A CURACT= ACTTYP= USER=O9O ERRID=
B725 SYS= ENTTYP= ENTNAM= ENTVER= ENTSTAT=
B725 LIB=ADRLIB MEM=ESCFMSGE
B725 ***** END OF IDL ERROR LOG ON 18/10/03 AT 06:01:27 *****

Environment

z/os Ideal/IPC 14.0

Cause

Something must have happened during the CICS session prior the problem or in batch before CICS was started up...or batch activity when CICS was up.
Need to check the CICS log for any error or storage violation prior the problem.

OR,

By the way, do you have that critical/hyper IPC APAR applied?:
APAR #: RO69919
Title: VLS CORRUPTION RESULTING FROM INCORRECT ENQUEUE CONVERSION

If not then it can be the reason. Apply it and follow the Holddata.

Resolution

It sounds that you will have to follow item 2 below unless you find out something else.

1---- This article may help you:

2---- Also have a look at documentation for SRVC=VLS FUNC=INIT RC=004-12

It is about VLS function INIT with an auxilliary return code 12.

Reason: The first block of the online library has an invalid format.
Action: Try again. A recurrence of this error means that the library was destroyed. To recover the library, ask your Site Administrator to restore it from a backup file. If this library was a new on-line library, reformat it.

3---- Note that meaning of IDADERRP11 says the same thing.

Reason: The first block of a VLS library has an invalid format. If the problem persists, it indicates that the library was destroyed.

AND you will have to recycle your CICS for the new Library to be on line

Additional Information

APAR #: RO69919 prevents new problems to occur, but it does not resolve or correct other VLS which may be already affected.

-This is why the Holddata steps are:

1. Apply PTF and recycle CICS.
2. Execute VLSUTIL BACKUP jobs for all VLS files and review output for exceptions.
3. If VLS BACKUP indicates a problem (i.e. "out of sequence"), execute VLSUTIL BACKUP/FORMAT/RESTORE to rebuild
the VLS index.

-The equivalent for 15.0 is APAR RO70961; but it is coming with the product at installation. In other words you don't have to apply it. (unless you got the beta version of the product).