SB37 abends during Quickedit session for dataset userid.CTLInnnn.BACKUP

Products

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

Issue/Introduction

During a Quickedit edit session, user gets a SB37 abend in a dataset named <userid>.CTLInnnnn.BACKUP, where <userid> is the user's ID and nnnnn is a five-digit number.

Literal CTLI is the factory default for NEWAPPL parameter in the QuickEdit startup CLIST. If the site has changed it, the user will get the changed value in the dataset name.

May happen especially when a very high number of changes have been done to the element during a given EDIT session.

Cause

During a Quickedit session, Endevor extracts the element to a work dataset and invokes ISPF edit services to edit it. When the ISPF edit profile specifies (or changes to) RECOVERY ON, the ISPF editor allocates the <userid>.CTLInnnnn.BACKUP dataset (known as "edit recovery dataset) in order to record each and every update made to the data being edited.

The size of the recovery dataset is set by the ISPF administrator in the ISPF/PDF configuration table. User will get the SB37 abend whenever EITHER

• The size defined by the administrator is too small
• An unusually large number of changes are done to the element in a single session.

Resolution

Any ISPF user facing a SB37 abend in that file can try the following to solve it:

• Split the update into smaller parts. Note that the backup file adds a record for each line updated in the file being edited.
• Issue RECOVERY OFF command during the edit session. This will stop writing data to the backup file
• Note the exact DSN of the file raising the abend and pre-allocate it with a larger size before entering the EDIT session.

Additional Information

Any ISPF user can use the following steps in order to see the allocation parameters for the recovery dataset:

• From any ISPF screen, issue command TSO ISPVCALL
• ISP responds with message ' Loading CALL trace. To end, reinvoke this command.'
• Enter TSO ISPVCALL command again
• User is placed into an EDIT session of dataset <userid>.<sysid>.ISPVCALL.TRACE
• Do a find for 'edit backup'
• The allocation parameters (block size, primary blocks and secondary blocks) are shown under heading 'edit backup' in the section named 'PDF Configuration table'.