During IPL OPS3126E DYNAMIC ALLOCATION FAILED; DSNAME=SYS1.OPS.OPAMSVDB, RC=4, ERROR CODE=X'1708', INFO CODE=X'0002'
search cancel

During IPL OPS3126E DYNAMIC ALLOCATION FAILED; DSNAME=SYS1.OPS.OPAMSVDB, RC=4, ERROR CODE=X'1708', INFO CODE=X'0002'

book

Article ID: 57045

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

At IPL time OPS/MVS could produce the following error message:

OPS3126E DYNAMIC ALLOCATION FAILED, RC=4, ERROR CODE=X'1708', INFO CODE=X'0002', DDNAME=OPAMSVDB, DSNAME=SYS1.OPSMVS.OPAMSVDB

 

 

 

Environment

OPS/MVS-Event Management & Automation-for JES2

Resolution

The OPSMAIN Address Space shows the dynamic allocation (SVC 99) class 7 error reason code x'1708' for the OPAMSVDB VSAM dataset. The family of x'17xx' reason codes are normally related to "Catalog Locate" errors. This dataset may not have been allocated yet. The OPAMSVDB member in the installation provided SYS1.OPS.CCLXCNTL dataset provides a sample JCL to run the IDCAMS utility as well DEFINE control statements to create it. An IDCAMS REPRO will initialize this VSAM KSDS dataset. Tailor and run this JCL to create this VSAM dataset and restart the OPSMAIN task when time permits.
 
This information can be found in the Installation Guide under DASD Requirements for a Shared VSAM Database (optional).