OPSLOG Archive Getting OPS8300O RC=33

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

The OPSLOG Archive process fails with the following error message: +OPS8300O RC=33, The archive OPSLOG data set could not be allocated

This error typically occurs when the archive subtask (ARCHPROC) attempts to create a new generation of the archive dataset (GDG).

Environment

• Product: OPS/MVS Event Management & Automation
• Release: 14.0 and higher

Cause

The primary cause for RC=33 is an allocation failure. In this specific case, the started task user ID associated with OPSLOG archiving lacked the necessary security authority to create the output archive dataset on the sandbox LPARs. This situation often arises after migrations (e.g., to v14.0) if security permissions are not synchronized across all environments.

Resolution

To resolve the allocation failure and clear the error state, follow these steps:

1. Verify Security Authority: Ensure that the user ID assigned to the OPSLOG Archive started task has ALTER authority to the High-Level Qualifier (HLQ) of the archive dataset.
2. Allocate New OPSLOG: If the primary OPSLOG is in a pending or error state, allocate a new, empty OPSLOG dataset.
3. Recycle OPSMAIN: Restart the OPSMAIN address space to initialize the new OPSLOG and refresh the environment.
4. Check Archive Parameters: Navigate to OPSVIEW 4.1.1 and verify:
   • The ARCHIVEHLQ is correct.
   • The ARCHIVEMODEL dataset name is not identical to the GDG base name.
   • The ARCHIVEUNIT is set to a valid group (e.g., SYSALLDA).
5. Restart Archive Subtask: Issue the following command to pick up parameter changes: F OPSS,RESTART(ARCH)