PQ73393: BBON3197 ERROR MESSAGE NOT DOCUMENTED

APAR status
Closed as documentation error.

Error description
Error message BBON3197 was not documented in WebSphere Documents
The text for BBON3197 is "UserID {0} not authorized for
administration". This APAR may also address other
messages that were not documented properly in WebSphere
Documentation.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: Error messsage BBON3197 is not          *
*                      documented.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Error messsage BBON3197 and others are not documented in the
V4.0.1 WebSphere for z/OS: Messages and Diagnosis publication.
Problem conclusion
APAR PQ73393 requires changes to documentation.

A change to V4.0.1 WebSphere for z/OS: Messages and Diagnosis
GA22-7837-06 will be available in the next refresh of the
documentation. To access the latest online documentation, go to
the product library page at:

www.ibm.com/software/webservers/appserv/zos_os390/library/
________________________________________________________________
BBON3016E Invalid format in parameter input file filename
on line linenumber: no separator found.
Explanation: This error occurs when the client reads the
parameter input file and does not encounter the expected
format. The script uses a parameter input file specified
by filename. The input file specifies attribute
name-value pairs and is expected to consist
entirely of lines of the form: name value, with
name and value separated by a single blank. However, on
the line specified by linenumber, a separating blank was
not found.
User Response: Check and correct the syntax of the
parameter input file on the line number specified in the
message text.
________________________________________________________________
BBON3130E Getting Administrator object failed. Administrator
administratorname not found.
Explanation:  During server side processing resolution of
the administrator reference produced an error. The
administrator administratorname was not found.
User Response: Make sure that the administrator
administratorname is allowed to use the "SM Scripting API".
________________________________________________________________
BBON3136E Conversation conversationname not found or not
owned by this administrator.
Explanation: The conversation indicated by conversationname
either does not exist or is not owned by the administrator
running the script.
User Response: Check your script to make sure the
conversationname is correct. Additionally, verify that
the conversation is owned by your administrator id.
________________________________________________________________
BBON3144E  Conversation status for conversation
conversationname is not valid for action.
Description: The conversation is not in a modifiable
state and therefore the requested action cannot be
performed on it.
User Response: Retry the action on a modifiable
conversation.
________________________________________________________________
BBON3194E No Attributes found for Sysplex.
Explanation: This error occurs when server side processing
checks the syntax of the input parameters. An error
occurred during reading of the Sysplex properties. No
attributes were found.
User Response: Contact the IBM Support Center.
________________________________________________________________
BBON3195E No Attributes found for System.
Explanation: This error occurs when server side processing
checks the syntax of the input parameters. An error
occurred during reading of the System properties. No
attributes were found.
User Response: Contact the IBM Support Center.
________________________________________________________________
BBON3196E No Attributes found for J2EE Server.
Explanation: This error occurs when server side processing
checks the syntax of the input parameters. An error
occurred during reading of the J2EE Server properties.
No attributes were found.
User Response: Contact the IBM Support Center.
________________________________________________________________
BBON3197E UserID userid not authorized for administration.
Explanation: This error occurs when the REXX script is
executed from a non-admin userid.
User Response: Verify that the userid is authorized for
administration.
________________________________________________________________
BBON3200E Getting XML parser reference for XML filename
failed.
Explanation: This error occurs when  the XML file for a
J2EE resource template or a J2EE resource instance is
processed. An error occurred during the generation of
a DOMParser object.
User Response: Contact the IBM Support Center.
________________________________________________________________
BBON3201E attributename is not a valid resource attribute
for J2EE resource type resourcetype.
Explanation: This error occurs when merging J2EE resource
attributes into a J2EE resource template XML file. The
resource template XML file specifies which attributes are
valid for J2EE resource instances of this type.
(For example, DB2PlanName is a valid attribute for J2EE
resources of type DB2datasource). The specified
attributename was not recognized as a valid attribute for
the specified resourcetype.
User Response: Check the  J2EE resource template XML files
of your intended resource type for supported resource
attributes, then correct your script to make use of
supported resource attributes only. The attributename
may have been misspelled or intended for a different
resource type.
________________________________________________________________
BBON3202E Unexpected syntax in filename XML: no expectedtag
node found below xmllocation.
Explanation: This error occurs when the XML files for J2EE
resource template is processed. A node with the specified
tag was expected, but not found.
User Response: This error should not occur with
IBM-provided resource template XMLs. If you are developing
your own resource template XML, make sure the XML adheres
to the (IBM-provided) DTD (document type
definition) for J2EE resource template XMLs.
________________________________________________________________
BBON3203E Unexpected syntax in filename XML: no child node
found under attributetype of attribute attributename.
Explanation: This error occurs when the XML files for
J2EE resource template is processed. An XML child node
was expected under the attributetype node for the
specified J2EE resource attribute, but none was found.
User Response: This error should not occur with
IBM-provided resource template XMLs. If you are developing
your own resource template XML, make sure the XML adheres
to the (IBM-provided) DTD (document type definition) for
J2EE resource template XMLs.
________________________________________________________________
BBON3204E Error modifying XML for J2EE resource type
resourcetypename: replaceText failed in selectedvalue
below xmllocation.
Explanation: This error occurs when the XML files for
J2EE resource templates are processed.  A text
replacement in a selectedvalue node below the specified
position xmllocation was attempted, but failed. This
should not happen unless the XML parser API createTextNode
fails or the parser generated document structure is invalid
(document node not found).
User Response: This error should not occur with IBM-provided
resource template XMLs. If you are developing your own
resource template XML, make sure the XML adheres to the
(IBM-provided) DTD (document type definition) for J2EE
resource template XMLs. Also, verify that your XML
passes the validation of a (validating) XML viewer.
________________________________________________________________
BBON3205E Parser exception during parsing of XML xmlname.
Explanation: This error occurs when  the XML file for a
J2EE resource template or a J2EE resource instance is
processed. An org.xml.sax.SAXException was thrown during
the generation of a DOMParser object.
User Response: Contact the IBM Support Center.
________________________________________________________________
BBON3206E Getting XML document reference for XML filename
failed.
Explanation: This error occurs when  the XML file for a
J2EE resource template or a J2EE resource instance is
processed. The XML parser's getDocument() API failed
after parsing the XML file(s).
User Response: Contact the IBM Support Center.
________________________________________________________________
BBON3207E Getting root element of XML filename failed.
Explanation: This error occurs when  the XML file for a
J2EE resource template or a J2EE resource instance is
processed. The XML parser's getDocumentElement() API
failed after parsing the XML file(s).
User Response: This error should not occur with
IBM-provided resource template XMLs. If you are developing
your own resource template XML, make sure the XML adheres
to the (IBM-provided) DTD (document type definition)
for J2EE resource template XMLs. Also, verify that your
XML passes the validation of a (validating) XML viewer.
________________________________________________________________
BBON3208E Unexpected syntax in filename XML: unrecognized
resource attribute type typename for attribute
attributename.
Explanation: This error occurs when  the XML file for a
J2EE resource template or a J2EE resource instance is
processed. The specified typename was not recognized as
a valid type for the specified J2EE resource attribute
attributename.
User Response: This error should not occur with
IBM-provided resource template XMLs. If you are developing
your own resource template XML, make sure the XML adheres
to the (IBM-provided) DTD (document type
definition) for J2EE resource template XMLs.
________________________________________________________________
BBON3209E No Attributes found for J2EE resource.
Explanation: This error occurs when server side processing
checks the syntax of the input parameters. An error
occurred during reading of the J2EE resource properties.
No attributes were found.
User Response: Contact the IBM Support Center.
________________________________________________________________
BBON3210E  Unexpected syntax in  XML filename: no text
found for node nodename.
Description: The indicated XML file does not contain any
text for the indicated node.
User Response: Correct the XML file to add the text and
retry the action.
________________________________________________________________
BBON3211E  The J2EE resource resourcename was previously
deleted in this conversation.
Description: The J2EE resource has been deleted previously
in this conversation and therefore cannot be processed.
User Response: None.
________________________________________________________________
BBON3212E  Instances of J2EE resource resourcenename are
used by the following Servers/Applications:
servername/applicationname. As long as these connections
exist, this J2EE resource cannot be deleted.
Description: The J2EE resource is currently referenced by
the listed servers/applications and therefore cannot be
deleted.
User Response: Change the listed servers/applications so
they no longer reference the J2EE resource, then retry the
J2EE resource delete.
________________________________________________________________
BBON3213E Unexpected syntax for parameter name parametername:
equal sign expected.
Explanation: This error occurs when a script parameter value
of the form name='value' name='value'... is processed. The
separating equal sign was expected and not found.
User Response: Check your script and correct the syntax of
the value for the specified parametername.
________________________________________________________________
BBON3214E Unexpected syntax for parameter name parametername:
single quote expected.
Explanation: This error occurs when a script parameter value
of the form name='value' name='value'... is processed. The
delimiting single quote was expected and not found.
User Response: Check your script and correct the syntax of the
value for the specified parametername.
________________________________________________________________
BBON3215E value is not a valid value for J2EE resource
attributename.
Explanation: This error occurs during creation or
modification of a J2EE resource instance. The specified
value is not a valid choice for the resource instance
attribute attributename.
User Response: Check your script and correct the value for
the resource instance attribute attributename. The valid
choices are defined by the template XML for this resource
type.
________________________________________________________________
BBON3216E The J2EE application applicationname was not found
on server servername.
Explanation: This error occurs during deleting an J2EE
application. The specified J2EE application applicationname
was not found on the specified J2EE server servername.
User Response: Make sure that the J2EE application
applicationname is installed on the J2EE server servername
you have specified.
________________________________________________________________
Temporary fix Comments
APAR information
APAR number PQ73393
Reported component name WEBSPHERE OS/39
Reported component ID 5655A9800
Reported release 401
Status CLOSED DOC
PE NoPE
HIPER NoHIPER
Submitted date 2003-04-21
Closed date 2003-07-16
Last modified date 2003-07-16

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels


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 #: PQ73393
IBM Group: Software Group
Modified date: Jul 16, 2003