PM07852: FMN2PARM IN SYS1.PARMLIB WITH UACC=NONE IMPLIES PROBLEMS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Problems with  File Manager since the upgrade to V10.01.
  In the new release the member FMN2PARM is required to be present
  on SYS1.PARMLIB which doesn't work for us since we have
  SYS1.PARMLIB defined in RACF with UACC=NONE.
  Our initial thought was to concatenate SYS2.PARMLIB (which has
  UACC=READ) together with SYS1.PARMLIB to solve our problem,
  but this didn't work.
  

Local fix

• Temporarily changed UACC to READ for SYS1.PARMLIB to
  circumvent the problem.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All File Manager Users.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Parmlib member FMN2PARM cannot be       *
  *                      accessed by FM users when customers     *
  *                      have UACC(NONE) for 'SYS1.PARMLIB'.     *
  ****************************************************************
  * RECOMMENDATION: Apply the provided PTF.                      *
  ****************************************************************
  The problem arises because of auditing requirements at some
  sites that mandate UACC(NONE) to SYS1.PARMLIB and a ban on
  users (such as FM users) being given READ access to
  SYS1.PARMLIB.  FM/DB2 requires access to member FMN2PARM, which
  can be placed in any library in the site's logical parmlib
  concatenation.  When validating security access for a FM user
  to the logical SYS1.PARMLIB concatenation using the IEFPRMLB
  macro, READMEMBER form, a security validation check is done, to
  library SYS1.PARMLIB.  If the user does not have READ access to
  SYS1.PARMLIB, the access attempt is denied (and no further
  security checking is attempted).  This means that, if the user
  does not have READ access to SYS1.PARMLIB, no access is
  possible.  Note that this applies even if the required member
  (eg FMN2PARM) is placed in a library (eg LIBX) other than
  SYS1.PARMLIB, in the logical parmlib concatenation, AND the
  user has READ access to library LIBX.
  

Problem conclusion

• File Manager has been updated to provide an alternative method
  of placing the required FMN2PARM member into a library in the
  logical parmlib concatenation.
  Publication Closing Code: DEVCHNG
  For the documentation changes associated with this APAR,
  please refer to:
  ftp://ftp.software.ibm.com/software/websphere/awdtools/
      filemanager/fmv10apar.pdf
  
  The changes are to the following publications:
  
  PUB ID        PUB NAME
  ------------  ----------------------------------------
  
  SC19-2856-00  File Manager for z/OS V10R1 Customization
                Guide
  
  The latest published manuals can be found at:
  http://www.ibm.com/software/awdtools/filemanager/library/
         index.html.
  

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:

Modules/Macros

• FMN0LVL  FMN2LVL
  

Fix information

• Fixed component name

  FILE MANAGER ZO

• Fixed component ID

  5655V5200

Applicable component levels

• RA10 PSY UK57733

     UP10/06/16 P F006

• RA12 PSY UK57775

     UP10/06/17 P F006

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.