Endevor package ship ( PGM NDVRC1 / PARM C1BMX000 ) fails with rc=12 message is C1BMX09E MEMBER NOT FOUND
Article ID: 215693
Updated On:
Products
Issue/Introduction
The first job of package ship failed with cc=12.
At the bottom of the listing we do not see any indication what went wrong.
I can see in the Endevor Shipment Log that the staging of the members failed. I only see the error message C1BMX09E that indicates that Package Ship failed in the staging process.
The bottom of the listing looks like it was cut short. I didn't see any error messages.
Environment
All supported releases
Resolution
In the listing found a message like this:
The message is saying that it could not find the member. This member must have the correct footprint that matches the footprint in the package.
The message " RC=12 MEMBER NOT FOUND " starts in column 95.
The member may be a backout member.
To resolve the problem, restore the member if it was deleted. If that is not possible you may have to re-run a package to create the member and ship that package.
Additional Information
The first part of the Shipment listing contains the "Endevor Package Shipment Log" and looks like this:
14:59:05 C1BMX70I MODEL PARM: C1BMX000 $CURR_DT $CURR_TM FUNC >>--VARIABLE-DATA-->
14:59:05 C1BMX70I ACTUAL PARM: C1BMX000,20210522,14590445 SHIP xxxxxxx
14:59:05 C1BMX76I PACKAGE DATASET IS iprfx.ENDEVOR.PACKAGE
14:59:05 C1BMX01I INPUT VERIFICATION COMPLETED
14:59:30 C1BMX04I PACKAGE STAGING COMPLETED
14:59:32 C1BMX54I C1BMXJCG WAS ENTERED FOR DESTINATION DEST1 AND RETURNED WITH CODE 00000000
15:02:28 C1BX106I DSN=uprfx.ENDEVOR.PKSCRHxx.xxxx HAS BEEN IDENTIFIED AS A SCRIPT DATA SET FOR DEST DEST1
15:02:44 C1BX106I DSN=uprfx.ENDEVOR.PKSCRHxx.xxxx HAS BEEN IDENTIFIED AS A SCRIPT DATA SET FOR DEST DEST1
15:03:11 C1BMX98I &HJOBCARDS WAS CREATED - DDNAME=C1BMXHJC
15:03:11 C1BMX98I &HCONFJCL WAS CREATED - DDNAME=C1BMXHCN
15:03:11 C1BMX98I &RCONFJCL WAS CREATED - DDNAME=C1BMXRCN
15:03:11 C1BMX98I &HDELJCL WAS CREATED - DDNAME=C1BMXDEL
15:03:11 C1BMX98I &HLIBS WAS CREATED - DDNAME=C1BMXLIB
15:03:11 C1BMX98I &RJOBCARDS WAS CREATED - DDNAME=(NONE)
15:03:11 C1BMX98I &RJOBCARDS WAS CREATED - DDNAME=(NONE)
15:03:16 C1BMX09E SHIPMENT STAGING FAILED - RC 0012
15:03:16 C1BMX00I END OF RUN - ENDEVOR RC 0012
In this case it indicates that the Staging process failed.
To check if the member exists:
In the package ship job you will see a listing like this
SHIPMENT OF MODULES FROM <lev1>.<lvl2>.COPY TO LPARP
ACTION MBR-NAME OPTION (PACKAGE NAME ) ASSOCIATED BACKOUT DATA AND PKG NAME COMMENTS, MESSAGES, ETC.
====== ======== ======= ================== ====================================== ===============================
COPY MEMCOPY OUTPUT (PACKAGE1 ) RC=12 MEMBER NOT FOUND
1) Run report CONRPT80 (foorprint report) against the entire dataset <lev1>.<lvl2>.COPY on the host LPAR(the LPAR that the first ship job ran)
2) Go to the package that ran and get the footprint from the listing.
SYSTEM / SUBSYS / TYPE / STAGE / VVLL
The member may be a backout member if another package ran and updated the member.
Feedback
