Applied PTF RO98234 and now getting error message EVSE580E.

Document ID : KB000120670
Last Modified Date : 09/11/2018
Show Technical Document Details
Issue:
When I bring up EXPLORE on VSE 5.2 after applying RO98234, I get the following: 

V1 0047 // JOB EXPLORED INITIALIZE EXPLORE/VSE ON DEVELOPMENT MACHINE 12:56:33 
DATE 11/07/2018, CLOCK 12/56/33 12:56:33 
V1 0047 EVSE590I LMP KEY FOR EXPLORE/VSE PROD(EY) IS VALID RC=0000 12:56:33 
V1 0047 EVSE580E VENDOR.NEWPROD M=EVSECINT.O *GSSLBGP MEMBER NOT FOUND IN 
LIB 12:56:33 
V1 0047 EVSE549E INVALID LIBRARY SPECIFIED ON PARM CARD 12:56:33 
V1 0047 EOJ EXPLORED MAX.RETURN CODE=0000 12:56:33 
DATE 11/07/2018, CLOCK 12/56/33, DURATION 00/00/00 12:56:33 



 
Environment:
Here is the JCL which is the exact same JCL used without the fix applied. To back out fix, I renamed the fixed module which is in a temporary VSE sublib. 

* $$ JOB JNM=EXPLORED,DISP=L,PRI=9,CLASS=V,USER='ERG GENERATED 
* $$ LST CLASS=V 
* $$ PUN CLASS=V 
// JOB EXPLORED INITIALIZE EXPLORE/VSE ON DEVELOPMENT MACHINE 
/* ID STATEMENT SUPPRESSED */ 
// OPTION DUMP 
// ASSGN SYS000,UA LOCAL 3270 TERMINAL 
// ASSGN SYS001,UA LOCAL 3270 TERMINAL 
// ASSGN SYS002,UA 
// ASSGN SYS003,UA 
// ASSGN SYS004,UA 
// DLBL EVSEARC,'EVSEDEV.ARCHIVE.FILE',,VSAM,CAT=DBDC36 
// DLBL EVSEFBK,'EVSEDEV.FLASHBCK.FILE',,VSAM,CAT=DBDC36 
// EXEC EVSEIBAT,SIZE=EVSEIBAT 
/* 
/& 
* $$ EOJ GENERATED 



**
 

 
Resolution:
Explore/VSE expects the configuration members to be in the same sublibrary as the EVSEIBAT phase.

If you are executing EVSEIBAT from a temporary library then add a PARM card to indicate where the configuration members should be loaded from.

Example:

// EXEC EVSEIBAT,SIZE=EVSEIBAT,PARM='lib.sublib'


 
Additional Information:
See the description of EVSEIBAT in the Utilities Guide for more information.