PM11828: MSGDFS2503W DYNAMIC ALLOCATION FAILED, REASON CODE 1708

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DDNAME and DSNAME of a database are incorrectly
  specified in DFSMDA.  /STA DB receives MSGDFS2499W invalid
  allocate request for reason 1.  The DDNAME and DSNAME in DFSMDA
  are corrected.  MDA gen is done, and the member copied to
  USERLIB.  /STA DB receives MSGDFS2503W dynamic allocation
  failed reason code 1708.
       The incorrect database dataset is allocated by the DLI
  region even though the USERLIB has the correct database
  dataset name.  The residual name in memory is used instead.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IMS V11 customers using dynamic allocation.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Incorrect dynamic allocation members    *
  *                      cannot be corrected while IMS is        *
  *                      running.                                *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  When dynamic allocation is requested for a database, the MDA
  member for that database will be loaded to facilitate the
  allocation.  In this case the MDA member did not match the
  dataset names established on the DBD gen for the database.
  Message DFS2499 is issued to display the error.  The MDA member
  is then deleted due to bit MDADLMBR being set in the routine
  that builds the DFS2499 message (label MDA0710 in DFSMDA00).
  
  A second /STA command for the database results in another
  dynamic allocation request.  Again, the MDA member is loaded
  into storage, the mismatch between the MDA member and the DBD
  gen is detected, but this time, the DFS2499 is bypassed.  This
  is done to prevent DFS2499 from flooding the operator console
  when multiple failures occur for the same database.  This also
  bypasses the setting of bit MDADLMBR and thus the MDA member is
  left in storage.
  
  At this point we are stuck with the bad MDA member and
  attempting to correct it and replace it in the library that
  contains the MDA members will not help.  We will never attempt
  to reload the new member because any subsequent dynamic
  allocation requests find the residual, bad MDA member and
  attempt to reuse it.  The same error occurs, but the storage
  will not be deleted at this point because we will continually
  bypass setting the MDADLMBR bit.
  

Problem conclusion

• GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  Code was altered in DFSMDA00 to set the MDADLMBR bit each time
  through the dynamic allocation failure path, whether or not
  DFS2499 is issued.
  

Temporary fix

Comments

APAR Information

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

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

  UK56656

Modules/Macros

• DFSMDA00
  

Fix information

• Fixed component name

  IMS V11

• Fixed component ID

  5635A0200

Applicable component levels

• R100 PSY UK56656

     UP10/05/06 P F005

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.