ROLLBACK NOT EXECUTED after SD37 abend in Datacom MUF
search cancel

ROLLBACK NOT EXECUTED after SD37 abend in Datacom MUF

book

Article ID: 445352

calendar_today

Updated On:

Products

Datacom Ideal

Issue/Introduction

An Ideal batch program abends with an SD37 abend  but the Datacom Multi-User Facility (MUF) does not trigger an expected rollback (BACKOUT). This typically occurs when the environment is significantly behind on maintenance or uses obsolete or incorrect  User Requirements Table (URT) parameters.

Symptoms

  • Batch job fails with SD37 abend.
  • MUF log shows missing job messages: DB00120I - MISSING JOB-######## NUMBER-##### and DB00102I - ENDED JOB-######## NUMBER-#####
  • Expected BACKOUT message DB00103I does not appear.

Environment

Z/OS

Datacom 15.1 

Ideal 15.1 

Cause

  1. Outdated Maintenance: Running a MUF environment that is significantly behind on maintenance for Datacom/IPC/Ideal can lead to unexpected behavior during abends.
  2. Obsolete URT Parameters: The use of ACCESS=RANSEQ in the DBURTBL macro is obsolete (removed since version 8.1) and can interfere with standard processing.
  3. Missing TXNUNDO=YES in the URT .

Resolution

Follow these steps to ensure proper rollback processing:

  1. Bring the Datacom, IPC, and Ideal maintenance current. Maintenance that is several years behind is not supported for root cause analysis of rollback failures.
  2. Recreate the URT used by the failing job.
  3. Remove the ACCESS parameter from the DBURTBL macro. Refer to the  for current syntax.
  4. Verify that TXNUNDO=YES is specified in the URT to allow for transaction undo (rollback) processing.
Powered by Wolken Software