Note on IEBCOPY behavior when copying from PDSE to PDS and x37 abends occur.

Products

• Endevor
• Endevor Natural Integration
• Endevor - ECLIPSE Plugin
• Endevor - Enterprise Workbench
• CA 2E

Issue/Introduction

This document describes a phenomenon observed when using IEBCOPY.
x37 abends during IEBCOPY operation are resulting in just a RC=8 when copying from a PDS/E to a PDS.

Resolution

x37 abends during IEBCOPY operation are resulting in just a RC=8 when copying from a PDS/E to a PDS.

For example, if IEBCOPY is used in a processor, it will return just a RC=8 when it experiences a SD37-04 abend, while writing to a PDS, with a PDSE as the source. It will issue these messages in SYSPRINT when copying from PDSE to PDS:

IGW01001T ABEND D37-00000004 IN MODULE ???????? AT OFFSET ????
IEB1130E A TERMINATING MESSAGE FROM PDSE PROCESSING APPEARS ABOVE - DIAGNOSTIC INFORMATION IS X'28010001'
IEB147I END OF JOB - 8 WAS HIGHEST SEVERITY CODE

When IEBCOPY sets the return code to 8, you should be aware that the copy operation is at best partially completed. We recommend that you set the MAXRC for IEBCOPY steps not higher then 4, to ensure that the processor execution gets marked as failed.

Note that this IEBCOPY behavior is different when copying from PDS to PDS.

In that case, a RC=16 will result, and SYSPRINT will show:

IEB1163E SYSTEM ABEND X'D3700000' OCCURRED, TERMINATING IEBCOPY.
IEBCOPY behaves as described above both inside and outside Endevor processors.
BSTCOPY, however, will propagate the SX37 abend, an NDVR RC=16 will be returned and the processor step will show a U0500.

For this reason it is advisable to use BSTCOPY instead of IEBCOPY if possible. For other IEBCOPY considerations see the Extended Processor Guide, as well as TEC471023.