Endevor fails with LOAD OF MODULE (BC1PKRNL) ERROR RESULT: (STORAGE)

Products

• Endevor

Issue/Introduction

Endevor foreground initialization fails with U0004 abend and message

Message LOAD OF MODULE (BC1PKRNL) ERROR RESULT: (STORAGE) is displayed at the user screen, followed by a traceback of called routines

MVS SYSLOG messages for the TSO session suggest an I/O error when MVS tries to load the module

IEW4009I FETCH FAILED FOR MODULE BC1PKRNL FROM DDNAME -LNKLST- BECAUSE OF AN I/O ERROR.
IEW4005I FETCH FOR MODULE BC1PKRNL FROM DDNAME -LNKLST- FAILED BECAUSE IEWFETCH ISSUED RC 0F AND REASON 40

 

 

Environment

Release : 18.0

Component : Endevor Software Change Manager

Cause

The messages suggest a permanent I/O error. However, the ddname of -LNKLST- indicates that the fetch was tried from the MVS linklist. In this case, another possibility is that the LLA started task has outdated information about the library where the module resides.

 

Resolution

First attempt would be an LLA refresh (command /F LLA,REFRESH at the MVS console). This command refreshes the in-storage copies of the library directories maintained by the LLA started task and may solve the situation.

If this doesn't help, then the whole linklist may need to be rebuilt. This may be done dynamically. Most probably your systems programmer is familiar with the procedure. Document How To Rebuild The Link List When An Extend Has Been Taken? may be used as a reference.

Additional Information

A very simple way to determine whether the problem is with the linklist or the library itself would be to try to load the program from STEPLIB DD.

For example, run a JCL like:

//STEP1  EXEC PGM=BC1PKRNL
//STEPLIB DD DISP=SHR,DSN=your.CSIQAUTH.library

This JCL will abend. However, if it does NOT fail to load the module into storage, it confirms that the problem is with the LLA and not with the library itself