OPS8300O RC=33, The archive OPSLOG data set could not be allocated
search cancel

OPS8300O RC=33, The archive OPSLOG data set could not be allocated

book

Article ID: 218269

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

question regarding the ARCHIVEHLQ and ARCHIVEMODEL parms -  how they differ and to be used with new proclib OPSLOG archiving function.

Our current OPSLOG archiving is used the batch job process with has the following:
GDG Base: SYS4.OPSMVS.MVST.OPSLOG         
GDG GV00: SYS4.OPSMVS.MVST.OPSLOG.GnnnnV00

I ran the ARCHGDG job to create a new ARCHIVEMODEL dataset (which I am presuming is like the base gdg?). 

The archive process now is failing with the following:

OPS8324I  ARCHIVE START(AUTO) TRACK(225 225) DSNAME(SYS4.OPSMVS.MVST.OPSLOG) GDGMODEL(SYS4.OPSMVS.MVST.ARCHLOG)   STORCLAS(STAND  
OPS9998I X'2486384680' | 0 | AUTO | 0 |                                                                                           
OPS9998I AUTO values: 1 AUTO 252827                                                                                               
OPS8300O RC=33, The archive OPSLOG data set could not be allocated                                                                
OPS8330I OPSLOG archive creation request processing completed     

Environment

Release : 14.0

Component : OPS/MVS

Cause

 A new archival procedure was established back before release 13.0, and then deprecated as of release 14.0

Resolution

Some possible resolutions:

1) If using SMS, the ARCHIVEMODEL parameter can be removed

2) One of parameters below may be causing the dynamic allocation to fail:

ARCHIVEUNIT     
ARCHIVESTORCLAS 
ARCHIVEVOLSER