PQ63024: BBONMC FAILS AND BBONMS HAS ERROR MESSAGE GLD5004E REGARDING A SUFFIX PARAMETER

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When running BBONMC the following error messages were generated:
BBOU0401E and BBOU0127E.  In the output from BBONMS (the naming
server region) the following error message is seen:
GLD5004E suffix parameter is missing or has no value in the
configuration file. And in the bboslapd.conf file there is this:
  racf database definitions
 ---------------------------------------------------------------
database sdbm  GLDBSDBM
suffix ""
Local fix
1) Edit the bboslapd.conf file to change: suffix ""
   to                                     suffix "o=WASLRAC"
2) Using the "WAS Instllation and Customization" book (Chapter 4
Performing post-installation tasks-> Adding a new administration
application -> Steps for updating the acl for LDAP) update the
ACL for the two ACL entry lines below to include "o=WASLRAC" so
they look like:
aclentry:
access-id:racfid=CBADMIN,profiletype=user,o=WASLRAC:normal
aclentry:
   access-id:racfid=CBSYMCR1,profiletype=user,o=WASLRAC:normal
3) When you have finished updating (not adding) the two above
  ACL entries, then run BBONMC again.
4) To prevent this from happening on future uses of the WAS
  Customization panels, do the following:
   a) Enter "S" for  "Save customization variables." and enter
        a dataset name.
   b) Enter "L" for "Load Customization Variables" and on the
      next screen for Dsname enter the IBM-supplied defaults
     (the dataset name is displayed,usually *.SBBOEXEC(BBOWVARS)
      then press enter.
    c) Finally, choose "L" again, but this time load the data
       you previously saved in step a) above.  These steps a-c
       are to insure that your Customization Panels have a
       current version of IBM variables.  (The original problem
       was caused because an 'older' level of IBM variables had
       been loaded - never replaced by a more current level).
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: When running a newer version of the     *
*                      "WebSphere for z/OS Customization"      *
*                      dialog that introduces new variables,   *
*                      the default value for those new         *
*                      variables will not be loaded            *
*                      automatically. Currently, the customer  *
*                      is required to do the load to get the   *
*                      values for these new variables.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a new version of the the "WebSphere for z/OS
Customization" dialog that introduces new variables is shipped,
the default value for those new varibles will not be loaded.
In this case, in the associated dialog generate files, a null
string will be generated in place of those newly introduced
variables.

The correct this, the dialog should be modified such that
the IBM supplied defaults will be loaded at the dialog
start-up.  A given variable should only be loaded if it cannot
be found in the profile (application environment pool).
This will ensure that we will always load the newly introduced
variables and do not override any existing variables value that
the customer might have customized.
Problem conclusion
The "WebSphere for z/OS Customization" dialog has been modified
to load the IBM supplied defaults at start-up. This will allow
newly introduced varibles to be loaded with their default
values. This will eliminate the generation of null strings in
place of new variables in the generated files.

APAR PQ63024 is associated with SERVICE LEVEL W401091 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ63024
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-07-10
Closed date 2002-07-31
Last modified date 2002-09-04

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOUBINF BBOWCPYR BBOWMAIN BBOW02    

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ68624    UP02/08/07 P F208

  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.


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ63024
IBM Group: Software Group
Modified date: Sep 4, 2002