$HASP708 CAJMRnn SYS01351 OPEN ERROR - DATA SET WAS NOT CLOSED in CA JMR from Broadcom

Products

• JMR

Issue/Introduction

CA JMR from Broadcom is spooling selected output from the JES spool and occasionally experiences the following error message:

$HASP708 CAJMRnn  SYS01351 OPEN ERROR - DATA SET WAS NOT CLOSED 
RC=06 I/O ERROR READING DATA BUFFER                             
DSNAME=  random dsname   .JESYSMSG                 

Environment

z/OS any supported level

JMR 4.6 at any maintenance level

Resolution

OA64101: HASP708 RC06 OR SPOOL DATA ERROR IN SDSF WHEN OPENING A SYSOUT DATA SET.

ANALYSIS: 

A residual DSET for the same job key is written into a track for a SPIN data set, which is going to a trckcel outclass. That is, when the SPIN interval hits and the dataset is spun the DSET gets written from storage on top of HDB2 since they both have the same track address. This breaks the HDB chain. Now when the data set is opened again a buffer-ID mismatch occurs because the second record has a buffer-ID of DSET instead of HDB. 

For CA JMR this is not a critical error and CA JMR will continue to process entries normally. The message issued says the following:

$HASP708 CAJMR08  SYS01351 OPEN ERROR - DATA SET WAS NOT CLOSED 

All OPEN processes were completed but the sysout entry was unable to be CLOSED properly. However, since all the data was spooled to the CA JMR DAILY file, there was no longer a viable spool entry. The entry is deleted normally from the spool and is available in the DAILY file.

This error can be ignored when discovered in the CA JMR started task output.

No production impact will be experienced and no data will be lost.