PQ53110: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0 FOR Z/OS AND OS/390.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
This APAR addresses defects in WebSphere Application Server
V4.0 for z/OS and OS/390.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0 for z/OS and OS/390.                    *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ53110 addresses various problems *
*                      in WebSphere Application Server V4.0    *
*                      for z/OS and OS/390.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ53110 addresses the following problems in
WebSphere Application Server V4.0 for z/OS and OS/390:

(MD10821) System Management (SM) Scripting API needs support for
J2EE resources as it is already present in the WebSphere for
z/OS Administration Application (SM EUI).

(MD11129) When running a System Management(SM) Scripting API
script with a incorrectly formatted parameter input file
(missing separator blank), a Java
StringIndexOutOfBoundsException is thrown.

(MD12251) When calling the System Management(SM) Scripting API
listj2eeresource API to list a resource that was previously
deleted in the current conversation, the resource is listed with
return code 0. This should result in an error message and return
code 4.

(MD12257) J2EE resources created by the System Management(SM)
Scripting API are not offered as a choice in the J2EE resource
pulldown of the 'install J2EE application' dialog in the
WebSphere for z/OS Administration Application (SM EUI).
Problem conclusion
APAR PQ53110 provides the following problem resolution:

(MD10821) Support for J2EE resources added to the System
Management(SM)Scripting API.

(MD11129) System Management(SM) Scripting API code for reading
the parameter input file has been modified to recognize a
missing blank separator. A new message (BBON3016E) was defined
to alert the user of this kind of invalid input.

(MD12551) The System Management(SM) Scripting API code for
listing a J2EE resource was modified to check the SM dialog
token and write an error message if the resource was previously
deleted in this conversation.

(MD12257) The code for creating a J2EE resource was modified to
read and use resource's Connector Interface Class Name from the
template XML. A new message (BBON3210E) was defined for the
case of a missing (blank) Connector Interface Class Name."

The following publication was revised as a result
of APAR PQ53110:
_______________________________________________________________
WebSphere Application Server V4.0 for z/OS and OS/390
Messages and Diagnosis
GA22-7837-01
_______________________________________________________________
This APAR requires changes to documentation.

NOTE: Periodically, we refresh the documentation on our
Web site, so the changes might have been made before you
read this text. To access the latest on-line
documentation, go to the product library page at:


http://www.ibm.com/software/webservers/appserv/

_______________________________________________________________
Chapter 10, pg. 175 (new message)
BBON3016E Invalid format in parameter input file filename on
line linenumber: no separator found.
Explanation: This error occurs while the client reads the
parameter input file.
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.
_______________________________________________________________
Chapter 10, pg. 190 (new message)
BBON3194E No Attributes found for Sysplex.
Explanation: This error occurs while the server side checks the
syntax of the input parameters. An error occurred during
reading of the Sysplex properties. No attributes were found.
User Response: Follow your local procedures for contacting IBM
for support.
_______________________________________________________________
Chapter 10, pg. 190 (new message)
BBON3195E No Attributes found for System.
Explanation: This error occurs while the server side checks the
syntax of the input parameters. An error occurred during
reading of the System properties. No attributes were found.
User Response: Follow your local procedures for contacting IBM
for support.
_______________________________________________________________
Chapter 10, pg. 190 (new message)
BBON3196E No Attributes found for J2EE Server.
Explanation: This error occurs while the server side checks the
syntax of the input parameters. An error occurred during
reading of the J2EE Server properties. No attributes were found
User Response: Follow your local procedures for contacting IBM
for support.
_______________________________________________________________
Chapter 10, pg. 190 (new message)
BBON3197E UserID user-id 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.
_______________________________________________________________
Chapter 10, pg. 191 (new message)
BBON3200E Getting XML parser reference for XML xmlname failed.
Explanation: This error occurs while processing the XML for
a J2EE resource template or a J2EE resource instance.
An error occurred during the generation of a DOMParser object.
User Response: Follow your local procedures for contacting IBM
for support.
_______________________________________________________________
Chapter 10, pg. 191 (new message)
BBON3201E attribute-name is not a valid resource attribute for
J2EE resource type resource-type-name.
Explanation: This error occurs while merging J2EE resource
attributes into a J2EE resource template XML. The resource
tempate XML 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 attribute-name was not recognized as a valid
attribute for the specified resource-type.
User Response: Check the template XML of your intended resource
type for supported resource attributes, then correct your
script to make use of supported resource attributes only. The
attribute-name may have been misspelled or
intended for a different resource type.
_______________________________________________________________
Chapter 10, pg. 191 (new message)
BBON3202E Unexpected syntax in xmlname XML: no expected-tag-
name node found below xml-location.
Explanation: This error occurs while processing a J2EE resource
template XML. 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.
_______________________________________________________________
Chapter 10, pg. 191 (new message)
BBON3203E Unexpected syntax in xmlname XML: no child node found
under attribute_type of attribute attribute-name.
Explanation: This error occurs while processing a J2EE resource
template XML. An XML child node was expected under the
<attribute_type> 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.
_______________________________________________________________
Chapter 10, pg. 192 (new message)
BBON3204E Error modifying XML for J2EE resource type
resource-type-name: replaceText failed in <selected_value>
below xml-location.
Explanation: This error occurs while processing a J2EE resource
template XML. A text replacement in a <selected_value> node
below the specified position xml-location 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.
_______________________________________________________________
Chapter 10, pg. 192 (new message)
BBON3205E Parser exception during parsing of XML xmlname.
Explanation: This error occurs while processing the XML for
a J2EE resource template or a J2EE resource instance. An
org.xml.sax.SAXException was thrown during the generation of a
DOMParser object.
User Response: Follow your local procedures for contacting IBM
for support.
_______________________________________________________________
Chapter 10, pg. 192 (new message)
BBON3206E Getting XML document reference for XML xmlname failed
Explanation: This error occurs while processing the XML for
a J2EE resource template or a J2EE resource instance.
The XML parser's getDocument() API failed after parsing the XML
User Response: Follow your local procedures for contacting IBM
for support.
_______________________________________________________________
Chapter 10, pg. 192 (new message)
BBON3207E Getting root element of XML xmlname failed.
Explanation: This error occurs while processing the XML for
a J2EE resource template or a J2EE resource instance. The XML
parser's getDocumentElement() API failed after parsing the XML.
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.
_______________________________________________________________
Chapter 10, pg. 193 (new message)
BBON3208E Unexpected syntax in xmlname XML: unrecognized
resource attribute type <type-name> for attribute
attribute-name.
Explanation: This error occurs while processing the XML for
a J2EE resource template or a J2EE resource instance.
The specified type-name was not recognized as a valid
type for the specified J2EE resource attribute attribute-name.
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.
_______________________________________________________________
Chapter 10, pg. 193 (new message)
BBON3209E No Attributes found for J2EE resource.
Explanation: This error occurs while the server side checks the
syntax of the input parameters. An error occurred during
reading of the J2EE resource properties. No attributes were
No attributes were found.
User Response: Follow your local procedures for contacting IBM
for support.
_______________________________________________________________
Chapter 10, pg. 193 (new message)
BBON3210E Unexpected syntax in xmlname XML:
          no text found for node node-tag.

Explanation: This error occurs while processing the XML for
a J2EE resource template or a J2EE resource instance.
A node with the specified node-tag was found, but contained no
text.
User Response: This error should not occur with IBM-provided
resource template XMLs. If you are developing your own resource
template XML, check the XML and supply the expected text for
the specified node-tag.
_______________________________________________________________
Chapter 10, pg. 193 (new message)
BBON3211E The J2EE resource resource-name was previously
deleted in this conversation.

Explanation: This error occurs when an attempt is made to list
or delete (again)a J2EE resource that was already deleted in
this conversation. Until the conversation is activated, the
resource is logically deleted, but not physically removed
from the database.

User Response: In order to work with a J2EE resource with the
same name as the deleted resource, you have to activate the
current conversation first.
_______________________________________________________________
Chapter 10, pg. 193 (new message)
BBON3212E Instances of J2EE resource resource-name are used by
          the following Servers/Applications:
          server-name/application name ....
          As long as these connections exist, this J2EE
          resource cannot be deleted.

Explanation: This error occurs when an attempt is made to
delete a J2EE resource that is still connected to J2EE
applications.

User Response: First delete all J2EE applications connected to
the J2EE resource,then delete the J2EE resource itself.
_______________________________________________________________
Chapter 12, pg. 318 (new message)
BBOU0733W Unable to return response %s to method %s request
from %s

Explanation: WebSphere for z/OS experienced a communications
error attempting to send a response to a client. The first
string describes the response type (NO_EXCEPTION,
USER_EXCEPTION, LOCATION_FORWARD, or SYSTEM_EXCEPTION). If the
response type is SYSTEM_EXCEPTION then the string also includes
the exception typeand minor code. The second string is the
method name in the request for which a response was unable to
be sent. The third string is host name and port number of the
client for clients using TCP/IP. For a local client, this
string contains the jobname and asid of the client address
space.

User Response: This message is provided to document that the
server was unable to respond to a client. This may be because
the client has gone away, but it may also result in a client
that is in a hang waiting for a response. This message provides
you with the information needed to identify the problem in the
event a client appears hung and wants to know if the server has
failed trying to respond to a request.
_______________________________________________________________
Chapter 12, pg. 318 (new message)
BBOU0734W Returning response %s to method %s request from %s

Explanation: WebSphere for z/OS is returning a system exception
in a response to a client. The first string describes the
exception type and minor code. The second string is the method
name in the request. The third string is the host name and port
number of the client for clients using TCP/IP. For a local
client, this string contains the jobname and asid of the client
address space.

User Response: This message simply serves to document that a
system exception was returned to a particular client. In the
event the client reports a problem, the error log could be
searched using the client's hostname to find if a system
exception was returned which may be related to the reported
problem.
_______________________________________________________________
Chapter 13, pg. 338 (new message)
C9C20CEO

Explanation: comm_callback_inbound_request - input buffer
encountered an error.  Refer to other logged messages for
additional detail.

User Response: IBM Internal Only.
______________________________________________________________

APAR PQ53110 is associated with SERVICE LEVEL W400051 of
WebSphere Application Server V4.0 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ53110
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-10-04
Closed date 2001-12-06
Last modified date 2002-01-03

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOAPCEI BBOAPCWI BBOAPIAI BBOAPIOI BBOAPXLI BBOAXCEI
BBOAXIAI BBOBOA BBOCLSES BBOCORBA BBOCPOCB BBOCSESS
BBOCSMGR BBOCSMRL BBODDAUT BBOFRCGD BBOIBOIM BBOIDRMI
BBOIGTID BBOIIMA BBOIIMC BBOIKEYS BBOINSTR BBOIRDB
BBOIROOT BBOITLS BBOI3PLI BBOJJU BBOLRT BBOLSHCP
BBOLSS BBOOBOAI BBOOBOAT BBOOCOMM BBOOCRHT BBOOCSIT
BBOOEJSB BBOOJORB BBOOORB BBOOORBP BBOOORBR BBOOORBX
BBOOOUTP BBOORDTA BBOOSMF BBOOSMFT BBOOSMOI BBOOSRWT
BBOOTMOT BBOOTRD BBOPBO BBORAS BBOROBML BBOROBMS
BBOROMDL BBOROSMD BBORTRCD BBOSEC BBOSEXT BBOSLHM
BBOSNMO BBOSQ03 BBOTOTS BBOTTJCU BBOTTSR BBOUENUS
BBOWBRAC BBOZ0227 BBOZ0229 BBOZ0266 BBOZ0267 BBOZ0268
BBOZ0269 BBOZ0270 BBOZ0271 BBOZ0272 BBOZ0273 BBOZ0274
BBOZ0285 BBOZ0286 BBOZ0287 BBOZ0288 BBOZ0289 BBOZ0290
BBOZ0291 BBOZ0292 BBOZ0293 BBOZ0688 BBOZ0689 BBOZ0729
BBOZ0733 BBOZ0739 BBOZ0740 BBOZ0742 BBOZ0745 BBOZ0749
BBOZ0751 BBOZ0752 BBOZ0812 BBOZ0813 BBOZ0814 BBOZ0908
BBOZ0909 BBOZ0910 BBOZ0911 BBOZ0912 BBOZ0913 BBOZ0914
BBOZ0915          

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R400 PSY UQ60863    UP01/12/20 P F112

  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: 400
Software edition:
Reference #: PQ53110
IBM Group: Software Group
Modified date: Jan 3, 2002