PM32837: DFHSM0002 SEVERE ERROR CODE 0315 AFTER A TASK SUSPENDED FOR UDSA STORAGE FOR A CONTAINER IS PURGED

APAR status

• Closed as returned (APAR cannot be resolved without additional info from IBM or customer.)

Error description

• You are running CICS Transaction server 4.1 and developing
  Webservice applications that use large containers. When testing
  this application, you go short on storage below the line in
  CICS.
  The task is suspended for UDSA storage. When you purge this task
  you receive the following error messages along with a system
  dump:
  DFHSM0002  A severe error (code X'0315') has occurred
             in module DFHSMGF.
  DFHPG0002  A severe error (code X'190A') has occurred
             in module DFHPGCR.
  The SOS condition occurred due to having DATALOCATION(Below)
  specified for the application program definition.
  Looking at the dump from the SM0002, you will see the following
  exception trace entry:
  .
  SM 0315 SMGF  *EXC* -
        Invalid_address_specified_with_storage_class_on_freemain
        FUNCTION(FREEMAIN) ADDRESS(26B236B8)
        FREE_LENGTH(64D990) REMARK(PGCRSET) STORAGE_CLASS(TASK)
  TASK-01303 KE_NUM-003E TCB-QR   /00AF0538 RET-A3616C4C
  .
  The address we are trying to free - 26B236B8, is already free,
  causing the exception. Module DFHPGCR is issuing this freemain
  and obtains the address from field CRCB_SET_ADDRESS.
  Looking back in trace we find this address was passed back on
  the getmain request when the task was purged. Here is that
  trace:
  SMGF  EXIT  - FUNCTION(GETMAIN) RESPONSE(PURGED)
                REASON(INSUFFICIENT_STORAGE)
                ADDRESS(26B236B8)
  This is actually a residual address in a parameter list, that
  DFHPGCR incorrectly moves into the field CRCB_SET_ADDRESS,
  before it checks the actual return code from the getmain
  request to see if it was successful.
  .
  Additional symptoms: GET CONTAINER SET
  KIXREVTGL
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is being closed with a code of RET/AU. This closing
  indicates that the Change Team has been unable to test the
  proposed fix for this APAR and that no Customer was able to test
  the fix and provide feedback within a reasonable amount of time.
  
  To ensure that only high quality fixes are distributed to all
  Customers, we require every fix to be tested either internally
  or at a Customer site which is experiencing the problem. This
  will minimize any exposure to a possible PTF error which could
  later be more detrimental to the Customer.
  
  The APAR fix is available upon application to the Change Team
  via PMR. Once the fix has been satisfactorily tested by a
  Customer experiencing the reported problem, the Change Team will
  accept a NO-DOC APAR (which must refer to this returned APAR) in
  order to provide the appropriate PTFs.
  
  If the fix does not correct the reported problem, please contact
  the Change Team via PMR with full details of the failure.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PM20899

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels