IBM Support

PI67253: CORRECT PROBLEMS WITH SETTING A MAXPCF DEFAULT IN IGYCDOPT USERMOD

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 4 issues exist surrounding the setting of the MAXPCF=0 value in
    the IGYCDOPT compiler option usermod.
    
    With OPTIMIZE=*2 FIXED or OPTIMIZE=*1 FIXED and no
    specification for MAXPCF in the usermod:
    
    If a customer sets their compiler default usermod to force
    OPT(1/2) on for all programs (not-overridable), the
    Customization Guide says that MAXPCF will be forced to
    MAXPCF(0).
    
    Problem 1) The usermod output (from SIGYMAC(IGYCOPI)) does not
    issue a message stating that MAXPCF(0) is in effect due to
    OPTIMIZE(1/2) FORCED.
    
    Problem 2) With OPT(1/2) forced on, programmers can use any
    value of MAXPCF in their compile that they choose.  The
    compiler output says that this value is used.
    
    
    With OPT(1/2) not specified and MAXPCF=*0 FIXED in the usermod:
    
    Problem 3) If OPT(1/2) is not forced on in the usermod, but
    MAXPCF=0 is forced on, the message generated in the usermod
    output indicating that MAXPCF(0) is in effect is confusing.
    
    Problem 4) If OPT(1/2) is not forced, but MAXPCF(0) is forced
    on, customers can use any value of MAXPCF in their compile that
    they choose and the compiler output does not issue a warning
    message stating that MAXPCF(0) is in effect.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Enterprise COBOL V5.1 using the     *
    *                 OPTIMIZE and the MAXPCF compiler options and *
    *                 also setting the default settings for these  *
    *                 2 options in IGYCDOPT.                       *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Compiler customization is missing some  *
    *                      conflicting compiler options messages:  *
    *                      1. During option customization phase    *
    *                      if the OPTIMIZE(1|2) option is fixed    *
    *                      and the MAXPCF is set to non-zero,      *
    *                      there should be a terminating message   *
    *                      issued indicating that the options      *
    *                      conflict.                               *
    *                      2. If OPTIMIZE(1|2) is fixed by         *
    *                      installation control and a non-zero     *
    *                      MAXPCF option is specified as an        *
    *                      invocation or CBL/PROCESS option, the   *
    *                      compiler does not generate a warning    *
    *                      message indicating that the options     *
    *                      conflict and that MAXPCF(0) is          *
    *                      enforced.                               *
    *                      3. If MAXPCF(0) is fixed by             *
    *                      installation control and a non-zero     *
    *                      MAXPCF option is specified as           *
    *                      invocation or CBL/PROCESS option, the   *
    *                      compiler does not issue a warning       *
    *                      message indicating that the MAXPCF(0)   *
    *                      option can not be overridden.           *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    *                                                              *
    ****************************************************************
    The compiler was not correctly diagnosing options conflicts
    with the MAXPCF compiler option, both at option default
    customization time and later at compiler invocation time.
    

Problem conclusion

  • The compiler was modified to enforce the rules for option
    conflict resolution between the OPTIMIZE and MAXPCF options at
    option customization and at compile time.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI67253

  • Reported component name

    ENT COBOL FOR Z

  • Reported component ID

    5655W3200

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-09

  • Closed date

    2016-10-19

  • Last modified date

    2016-11-02

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

    PI66265

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

Modules/Macros

  • IGYCOPI
    

Fix information

  • Fixed component name

    ENT COBOL FOR Z

  • Fixed component ID

    5655W3200

Applicable component levels

  • R510 PSY UI41798

       UP16/10/26 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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS6SG3","label":"Enterprise COBOL for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510","Edition":"","Line of Business":{"code":"LOB17","label":"Mainframe TPS"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 November 2016