Question & Answer
Question
Why am I receiving message DWW267I with reason code 73050090 followed by a RC=3999 when running the CICS VSAM Recovery for z/OS (CICS VR) V5.1installation verification procedure (IVP) job DWWRUNBL to verify CICSVR batch logging?
I recently upgraded my Parallel Sysplex to z/OS V2.2 and if I run the DWWRUNBL job on another LPAR it runs successfully so I suspect some type of configuration or setup problem, but the error message codes do not provide me much to go on.
The DWWRUNBL job ends with messages:
DWW259I LOGGING NOT PERFORMED FOR ADDRESS SPACE.
ASID (IN HEX): 0044
RETURN CODE (IN HEX): 00000024
REASON CODE (IN HEX): 717053D0
DWW269I BATCH LOGGING REQUESTED: FRLOG(REDO)
SPHERE: CICSVR.IVP510.CUSTOMER
REDOS: 0
UNDOS: 0
DWW267I VSAM BATCH REDO LOGGING FAILED.
ASID (IN HEX): 0044
RETURN CODE (IN HEX): 00000024
REASON CODE (IN HEX): 73050090
$HASP395 DWWRUNBL ENDED - RC=3999
Answer
A SLIP dump showed the CICSVR server was loading modules from CICSVR 4.3 from LINKLIST and the DWWRUNBL batch job was loading CICSVR 5.1 modules. This mismatch between the CICSVR server and the DWWRUNBL batch job resulted in the batch logging failure messages and CC 3999 completion.
It was determined that the LPAR where DWWRUNBL failed had conacatenated a PARMLIB data set ahead of the 'normal' PARMLIB data set that had the CICS VR 4.3 data sets in a PROGxx member. After removing this old PARMLIB with the old PROGxx member from the concatenation and re-IPLing, the DWWRUNBL job ran successfully on this LPAR.
Product Synonym
CICSVR CICS VR
Was this topic helpful?
Document Information
Modified date:
27 February 2020
UID
dwa1230985