Why did I get a D37-04 abend when I started CA Alchemist DS?
search cancel

Why did I get a D37-04 abend when I started CA Alchemist DS?

book

Article ID: 55102

calendar_today

Updated On:

Products

Alchemist TPX - Session Management Vman Session Management for z/OS

Issue/Introduction

Description:

On startup of an Alchemist/DS task with a new or empty checkpoint data set, you can see this error:

 ZCBD190I - DC.QM{AS5311A} QUEUE MANAGER TASK STARTING
 ...
 ZCBD153E - DC.QM CHECKPOINT DATA SET ZDCCKPTA IS BEING FORMATTED
 IEC031I D37-04,IFG0554P,AS5311A,DS$CP,ZDCCKPTA,23BD,APCD15, CYB 1.AS5311. DSCP .ZDCCKPTA
 ZCBD154E - DC.QM CHECKPOINT DATA SET ZDCCKPTA FORMATTING COMPLETED
 ZCBD153E - DC.QM CHECKPOINT DATA SET ZDCCKPTB IS BEING FORMATTED
 IEC031I D37-04,IFG0554P,AS5311A,DS$CP,ZDCCKPTB,23BD,APCD15, CYB 1.AS5311. DSCP .ZDCCKPTB
 ZCBD154E - DC.QM CHECKPOINT DATA SET ZDCCKPTB FORMATTING COMPLETED
 ZCBD191I - DC.QM{AS5311A} QUEUE MANAGER TASK ACTIVE

Solution:

You will see a D37-04 abend when you start any CA Alchemist DS task with an empty or reallocated checkpoint dataset (ZDCCKPTA or ZDCCKPTB, or both).

Checkpoint datasets must only be given a primary space allocation which reflects the desired size. A secondary allocation should never be specified. This is because of the dataset formatting process that occurs whenever a checkpoint dataset is first accessed. This process causes empty blocks to be written to the dataset until a dataset full condition occurs.

D37-04

A data set opened for output used all the primary space, and no secondary space was requested. Change the JCL specifying a larger primary quantity or add a secondary quantity to the space parameter on the DD statement.

So a D37-04 is normal to see under this circumstance.

You may see this error on any of the control point ("local" Alchemist/DS) or remote ("remote" Alchemist/DS) started tasks.

Environment

Release: NVINAM00200-5.2-TPX-Session Management-Access Management package
Component: