First PDSMAN startup under Z/OS v2R4 generates SVC DUMP and abend S0F4
Article ID: 188475
Updated On:
Products
PDSMAN
Issue/Introduction
Installed Z/OS V2R4 on our first testbed and start of PDSMAN generated svc dump:
DUMPID=002 REQUESTED BY JOB (PDSMAN )
DUMP TITLE=COMPID=DF115,CSECT=IGWIRPAD+1CCA,DATE=03/17/19,MAINT
ID=NONE NON,ABND=0F4,RC=00000024,RSN=1419A084
Pdsman continues its installation and seems ok.
Environment
Release : 7.7
Component : CA-PDSMAN for z/OS
Resolution
This is an exact match on an IBM APAR - OA46376.
At the time of this abend PDSMOPR (the stc control module) is invoking PDSM00, which sets the PDSMAN SVC hooks, among other things. The unusual thing about this is PDSM00 ran normally - evidenced by the PDSM00-1 PDSMAN BLDL/STOW INTERFACE INITIALIZATION COMPLETE message. And actually PDSMAN completed initialization normally.
So at the time of the abend, PDSMAN was not active in the system (the abend occurred before PDSM00 ran).
We now recommend REGION=0M be used for the PDSMAN STC.
We recommend you report this to IBM.
At the time of this abend PDSMOPR (the stc control module) is invoking PDSM00, which sets the PDSMAN SVC hooks, among other things. The unusual thing about this is PDSM00 ran normally - evidenced by the PDSM00-1 PDSMAN BLDL/STOW INTERFACE INITIALIZATION COMPLETE message. And actually PDSMAN completed initialization normally.
So at the time of the abend, PDSMAN was not active in the system (the abend occurred before PDSM00 ran).
We now recommend REGION=0M be used for the PDSMAN STC.
We recommend you report this to IBM.
Feedback
Yes
No
Powered by
