FILELOG abend SB37 during IXMAINT or batch process.

Products

• Disk Backup and Restore - MVS
• DISK BACKUP AND RESTORE- ADD-ON OPTIO
• DISK BACKUP AND RESTORE

Issue/Introduction

During an IXMAINT run, received SB37 abend on FILELOG data set name:
IEC030I B37-04,jobname,stepname,IXMAINT,FILELOG,volser,diagcode,dsname,DMS.FILELOG.A*.Djuliandate.Thhmmss

What can be done to address this?

Environment

Release: Disk™ Backup and Restore

Resolution

The FILESPAC sysparm controls the number of blocks allocated when the files log data sets are created. The default value is 15000U, causing 15000 blocks to be allocated. You can specify this sysparm with any 5-digit numerical value followed by a character U, K or M, where the character indicates the multiplier to be used with the 5 digit value (U for 1, K for 1024 and M for 1,048,576).
An internal allocation rule makes the default to 15000U creating 15,000 records to be allocated for primary and secondary. That means you get FB 300 300 allocation in blocks. The block size is coded to be 300 but can be changed by any allocation tool.

About the FDS LOG processing:

I - Indicates that the log was generated from an ISPF interactive request, or from a restore request (that is an explicit batch restore or a DMSAR auto restore)
B - Indicates that the log was generated from a batch job, with the exception of the explicit restore.

A date/time stamp generated during dynamic allocation of the data set follows this. One batch log data set will be created for each Disk job run, but only one ISPF log data set will be created daily.
The B37 may be solved by adjusting the FILESPAC setting or using a product like Allocate or DFSMS to change the primary and secondary allocation to increase the size and create multi-volume. Notice that activating Compression in SMS can also be used to avoid X37 abends. Space is automatically released at normal close for all Batch "B" filelogs. In case of abend or job cancel then the data set is not closed and so the space can't be released.
The "I" File logs are not released because one is created for the day for all ISPF queries to be accumulated into it. This is the only one that is in MOD disposition.

Consider the following:
If there are no problems, then it would be good to increase the FILESPAC default value by a small amount to avoid the X37 problems. Use SMS or ALLOCATE or other allocation product to modify allocation when X37 occurs.

Additional Information

Refer to the Disk tech guide for the sysparm details.