PQ81868: CREATE SYSTEM FAILS WITH BBON3199E AND BBON3113E WHEN USING THE SYSTEMS MANAGEMENT SCRIPTING API (SM API)

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When using the Systems Management Scripting API (SM API) to
define a new system, the following messages are observed:
BBON3199E Method createsystem failed.
BBON3113E Attribute systemname = X starts with non OS/390 letter
where X is a system name that begins with a numeric (i.e. 0-9).
This same system name, one that starts with a numeric, can be
successfully defined using the Administration Tool (SM EUI).
The SM API validity check of the system name is too
restrictive.  It should allow a system name beginning with a
number.  Alphabetic, numeric, #, $, or @ as first character are
allowable for a system name on 390.
Local fix
If possible, use the SM EUI to define the system.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 version 4.0.1 for z/OS and OS/390            *
****************************************************************
* PROBLEM DESCRIPTION: System Management API (SMAPI) does not  *
*                      allow the specification of a system     *
*                      name beginning with a numeric           *
*                      character.  This is not consistent      *
*                      with the SMEUI and is too limiting.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The SMAPI scripting interface requires that system names
appearing on various commands begin with an alphabetic
character.  This is inconsistent with the SMEUI interface,
which places no restriction on the first character of system
names, besides the general requirement that names be composed
of alphabetic and numeric characters, #, @, and $.  This SMAPI
restriction is too limiting and should be made consistent with
the SMEUI.
Problem conclusion
This fix changes the validation checking done for system names
in the SMAPI, making the SMAPI and SMEUI consistent.

APAR PQ81868 is associated with SERVICE LEVEL W401607 of
WebSphere Application Server version 4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ81868
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-12-08
Closed date 2003-12-15
Last modified date 2004-01-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ83165    UP03/12/18 P F312

  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 #: PQ81868
IBM Group: Software Group
Modified date: Jan 3, 2004