PI56987: WLP_SKIP_UMASK=TRUE ISN'T WORKING WHEN LIBERTY SERVER IS STARTED FROM A STARTED TASK ON Z/OS

8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• WLP_SKIP_UMASK=true in the server.env doesn't take affect
  when
  the Liberty Server is started using a proc.  In order to get
  it
  work, it has to be added in a file pointed to by the STDENV
  DD
  in the started procedure.
  
  This works as expected, if the Liberty Server is started
  from
  the shell using the wlp/bin/server script.
  

Local fix

• Add WLP_SKIP_UMASK=true to the file used in the STDENV DD  in
  the Liberty Server started procedure
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile for z/OS             *
  ****************************************************************
  * PROBLEM DESCRIPTION: The variable WLP_SKIP_UMASK isn't       *
  *                      honored if it is set in server.env when *
  *                      the BBGZSRV proc is used to start the   *
  *                      server.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When starting a Liberty profile server on z/OS using the BBGZSRV
  proc, there are several places where environment variables can
  be specified.  When the WLP_SKIP_UMASK variable is specified in
  the STDENV DD of BBGZSRV, it functions correctly.  When
  WLP_SKIP_UMASK is set in a server.env file, and the proc is
  used, it is ignored.  This is incorrect, as the WLP_SKIP_UMASK
  variable functions correctly when the server is started with the
  wlp/bin/server script, and the WLP_SKIP_UMASK variable is
  defined in server.env.
  

Problem conclusion

• Code was added to honor the WLP_SKIP_UMASK variable when it is
  specified in a server.env file, and the server is started from
  the BBGZSRV proc.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.9.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Specify WLP_SKIP_UMASK in the STDENV DD of the BBGZSRV proc.
  

Comments

APAR Information

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

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

Fix information

• Fixed component name

  LIBERTY PROF -

• Fixed component ID

  5655W6514

Applicable component levels

• R850 PSY

     UP