CAOPS/MVS Archive GDG alloaction error

Document ID : KB000093536
Last Modified Date : 07/05/2018
Show Technical Document Details
Issue:
Our OPS/MVS admin has created a new OPS/MVS Archive GDG. However, when F OPSS,RESTART(ARCH) is issued the following error occurs:

OPS0158S IKJ56879I DATA SET ABC.OPSMVS.BBB.ARCHIVE NOT ALLOCATED, REFERENCED DATA SET NAME IS A GDG GROUP NAME

Other messages:
IGD17272I VOLUME SELECTION HAS FAILED FOR INSUFFICIENT SPACE DATA SET

@OPS0158S IKJ56894I DATA SET ABC.OPSMVS.BBB.ARCHIVE NOT ALLOCATED+
@OPS0158S IKJ56894I STORAGE MANAGEMENT SUBSYSTEM DETECTED AN ERROR, EITHER MESSAGES WERE NOT REQUESTED OR A SYSTEM ERROR OCCUR +OPS8300O RC=33, The archive OPSLOG data set could not be allocated +OPS8330I OPSLOG archive creation request processing completed
+OPS8320O OPSLOG (OPSLOG) archive creation completed, MAXRC=33

 
Environment:
CA OPS/MVS Event Management and Automation release 12.3
z/OS
Cause:
Insufficient space to create the dataset on the disk volume.
Resolution:
RO96471 Title: OPSLOG ARCHIVE MAXIMUM SPACE REQUESTED 
Additional Information:
Things to check when there is an allocation error:
  • Check the Archive parameters are correct by going to OPSVIEW 4.1.1
  • Check the OPS/MVS parameter member OPSPPA00 for the archive dataset high level qualifier being set and verify the name.
  • Check to see if the ARCHIVEMODEL parameter was updated with the correct(New) dataset name.The ARCHIVE HLQ(GDG BASE)and MODEL cannot be the same name.
  • Review the complete JCL for setting up the data definitions. Check the proclib for ARCHPROC and the correct datasets for the STEPLIB and SYSEXEC.
  • Recycle OPS/MVS to pickup the changes in OPSSPAxx.
  • Restart of the ARCHIVE subtask. Stop and start OPSS then issue F OPSS,RESTART(ARCH) from the OPSLOG in OPSVIEW.