search cancel

Receiving a B37-04 error abend for ddname PRUWF2 when running the Prefix Resolution&Update Utility (PRU) with Logical Related Databases.

book

Article ID: 19082

calendar_today

Updated On:

Products

CA Distributed Database Management CA Database Analyzer for DB2 for Oracle Database Analyzer (IMS Tools) Mainframe Configuration Manager for IMS for z/OS IMS TOOLS - MISC Compress Data Compression (IMS Tools) Database Analyzer for IMS for z/OS Database Copier for IMS for z/OS Database Organizer for IMS for z/OS Mainframe Extended Terminal Manager (IMS Tools) High Performance Recovery for IMS for z/OS Database Organizer (IMS Tools) Mainframe Program Restart Manager for IMS for z/OS Secondary Index Builder for IMS for z/OS Secondary Index for IMS for z/OS

Issue/Introduction

Description:

When executing PRU a B37-04 abend is being issued for DDNAME PRUWF2:

IEC030I B37-04,IFG0554A,jobname,stepname,PRUWF2,VIO , ,dsname

What is DD PRUWF2 and how do we resolve this B37 failure?

Solution:

The PRUWF2 file is a temporary work file allocated by PRU when we are not using a Dataspace. The file space allocation is based on the size of the SORTIN/DFSURWF1 input file.

In the job control cards SMDSPACE=NO is specified.

To resolve this error you have two options:

  1. Use a Dataspace by either specifying SMDSPACE=YES or by allowing PRU to default to SMDSPACE=YES by removing SMDSPACE=NO.

  2. Hard-code a PRUWF2 DD in the JCL (see sample JCL member JCLPRU5).

Sample PRU JCL is provided in the highlevel.CIMTSAMP library. Members JCLPRU1-5 provide examples of using a DATASPACE and alternatively using a PRUWF2 DD; either by hard-coding in the JCL or through dynamic allocation.

Environment

Release:
Component: DBO