Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Workspace z/OS
Categories DFSMS HSM
Created by Guest
Created on Oct 23, 2025

Advanced Audit for DFHSM - FIXAUDIT volume too much for default HSM ODS Allocation

When there is a sizable amount of commands being issued to DFHSM by a FIXAUDIT process, the DFHSM ODS file quickly exhausts its default space allocation which leads to DFHSM receiving an S878-10 abend and shutting down.


In this example, once the ODS is exhausted, DFHSM is flooded with the following messages:


IEC030I B37-04,IFG0554A,DFHSM,DFHSM,SYS03182,657C,DCTW34

R0TTRA8.FIXAUDIT.F2111WB,

RC=X'00000000',RSN=X'00000000' .....................


One solution is to patch the DFHSM ODS allocation to a larger primary and secondary space values. This approach makes the allocation a one size fits all. We find this approach somewhat impracticable for a number of reasons.


Another solution would be to pre-allocate the ODS file with a size anticipatory of the record count to be processed.


Pre-allocation example of F2111WB with 11556 records expected:


//ALLOC EXEC PGM=IEFBR14

//DEFDSN DD DSN=R0TTRA8.FIXAUDIT.F2111WB,

// DISP=(NEW,CATLG,DELETE),UNIT=SYSDA,

// SPACE=(121,(11556,11556)),AVGREC=U,

// RECFM=FBA,LRECL=121,BLKSIZE=0,

// DSNTYPE=EXTPREF or LARGE


The main objective is to avoid DFHSM experiencing and abend and shutdown due to the ODS space being exhausted. It gets noticed when DFHSM shutdown outside of automation and outside of availability hours. Plus, its not a good look on Advanced Audit either.


It would be nice if the FIXAUDIT process would include an allocation step after the delete step in the generated FIX job. And that the space values be automatically included base on expected record count.

Idea priority Medium