OA50460: Support for three new binder APIs - NEW FUNCTION

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• new Binder API - more than two IDRLs
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Those using binder APIs for any of the       *
  *                 following scenarios:                         *
  *                 1. Call PUTD to add up to 5 IDRLs into       *
  *                    programs.                                 *
  *                 2. Call PUTD to put data into a private      *
  *                    section whose name is a 4-byte binary     *
  *                    number larger than 16.                    *
  *                 3. Call API BINDW multiple times against     *
  *                    a non-XPLINK WORKMOD.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: The binder currently does support       *
  *                      these scenarios and different error     *
  *                      may occur.                              *
  *                      In case 1, when the output is a         *
  *                      Program Object ABEND 0C4 may occur,     *
  *                      SYSTEM COMPLETION CODE=0C4 REASON       *
  *                      CODE=00000010                           *
  *                      When the output is a Load Module,       *
  *                      there is no ABEND but IDRLs after the   *
  *                      2nd one are lost.                       *
  *                      In case 2, the binder issues an error   *
  *                      message:                                *
  *                      IEW2214S  CANNOT ALTER BINDER-CREATED   *
  *                      SECTIONS WHEN INTENT IS BIND.           *
  *                      In case 3, ABEND806 may occur:          *
  *                      SYSTEM COMPLETION CODE=806  REASON      *
  *                      CODE=00000004                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  CASE 1: the binder currently supports 1-2 IDRLs.  If more
  than 2 IDRLs are attempted to be added, storage overlay can
  cause ABEND0C4 or IDRLs may not be added to the module.
  CASE 2: The binder assumes private names whose value are larger
  than 16 to be reserved names, so it issue error message
  IEW2214S.
  CASE 3: The binder currently does not support multiple BINDW
  against a non-XPLINK WORKMOD. If the 2nd BINDW is called,
  incorrect WORKMOD data may cause an bad module to be built
  leading to 806 or other ABENDs.
  
  The support in z/OS 1.13 is for CASE 1 scenario only. All
  3 cases described above are supported in z/OS 2.1 and up.
  

Problem conclusion

Temporary fix

Comments

• The binder has been updated to support these 3 scenarios.
  

APAR Information

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

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

  UA82866 UA82867 UA82868

Modules/Macros

• IEWBBARN IEWBBBIE IEWBBCDS IEWBBIE2 IEWBBIND IEWBBRBA IEWBDCON
  IEWBDPUT IEWBFRIN IEWBNAME IEWBXCLW IEWBXCPW IEWBXCRW IEWBXCSL
  IEWBXCSP IEWBXCWI
  

Fix information

• Fixed component name

  PROGRAM MANAGEM

• Fixed component ID

  5695PMB01

Applicable component levels

• R7A0 PSY UA82866

     UP16/10/05 P F610

• R780 PSY UA82867

     UP16/10/05 P F610

• R790 PSY UA82868

     UP16/10/05 P F610

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.