PQ59046: WEBSPHERE CMP IVP FAILING, CLIENT RECEIVES 'NESTED' EXCEPTION, IVP SERVER (BBOASR2S) SHOWS DB2SQLEXCEPTION: USERID.POLICYCMP

APAR status
Closed as documentation error.

Error description
CMP portion of the IVP fails with a 'nested exception' being
thrown back to the client.  The 'nested exception' indicates
that there was a problem in the IVP Server region (default name
is BBOASR2S).  The actual error will either be in the SYSPRINT
of the server region, or into CTRACE, depending on the
TRACEBUFFLOC= setting in the current.env of the IVP Server.
.
The actual error in the IVP Server will be a DB2JDBC exception,
and the top of the 'stack trace' will have:
com.ibm.db2.jcc.DB2SQLException: DB2JDBCCursor Received Error in
   Method prepare:
   <<DB2 7.1 ANSI SQLJ-0/JDBC 1.0>> userid.POLICYCMP
.at COM.ibm.db2os390.sqlj.jdbc.DB2SQLJJDBCCursor.setError
   (DB2SQLJJDBCCursor.java


.at COM.ibm.db2os390.sqlj.jdbc.DB2SQLJJDBCSection.prepare
   (DB2SQLJJDBCSection.jav
.at COM.ibm.db2os390.sqlj.jdbc.DB2SQLJConnection.
   prepareStatement(DB2SQLJConnect
.at com.ibm.db2.jcc.DB2LogicalConnection.prepareStatement
   (DB2LogicalConnection.j
.
The 'userid' in the exception will vary, and be the userid
associated with the user submitting the IVP from OMVS, or the
userid associated with the JCL, if the IVP was run in Batch.
.
The 'WebSphere Application server V4.01 for z/OS and OS/390
Installation And Customization' manual (GA22-7834-02)  is
incorrect on Page 120. In the 'Steps for adding the BBOASR2 J2EE
server' section of Chapter 3, Step 4 has a table of 'selections'
to make when defining the J2EE Server in the SM/EUI.
The 'Enable Setting OS Thread Identity to RunAs' should NOT be
selected.  The table indicates that it should.
.
By selecting this box, the 'identity' that the IVP will run
under will vary, depending on 'who' is running the IVP.
Another section of the install has set up an 'alias' of
'userid.POLICYCMP', where the 'userid' is the id defined to be
the BBOASR2S user identity, during the ISPF Installation Panels.
In 'xxx.CNTL(BBOICD)'
CREATE TABLE  BBO.POLICYDO
(
 PAMOUNT  FLOAT  NOT NULL  ,
 PNUMBER  INTEGER  NOT NULL  ,
 PPREMIUM  FLOAT
 , PRIMARY KEY
 ( PNUMBER ))
 IN BBOMDB01.POLICYTS;
CREATE UNIQUE INDEX POLICY01
       ON BBO.POLICYDO (PNUMBER ASC)
        CLOSE NO;
 CREATE ALIAS CBASRU2.POLICYCMP
        FOR BBO.POLICYDO;
Local fix
Go into the SM/EUI, and 'un-check' the 'Enable Setting OS Thread
Identity to RunAs' check box.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: The WebSphere for z/OS: Installation    *
*                      and Customization publication should    *
*                      be updated to state that "Enable        *
*                      Setting OS Thread Identity to RunAs"    *
*                      should be cleared.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The WebSphere for z/OS: Installation and Customization
publication says to check "Enable Setting OS Thread Identity to
RunAs" for the BBOASR2 IVP server. This causes the user ID
associated to be one of the following:

- The user ID of the OMVS user submitting
  the IVP as a batch job
- The user ID identified in the JCL
- The PUBLIC user ID when the IVP is run
  from the Web container.

This causes a DB2JDBC exception:

  com.ibm.db2.jcc.DB2SQLException: DB2JDBCCursor Received Error
  in Method prepare:<<DB2 7.1 ANSI SQLJ-0/JDBC 1.0>>
  <user_ID>.POLICYCMP

The WebSphere for z/OS: Installation and Customization
publication should be updated to state that "Enable Setting OS
Thread Identity to RunAs" should be cleared.
Problem conclusion
A change to V4.0.1 WebSphere for z/OS:  Installation and
Customization, GA22-7834-04 was  made available in March,
2002.  To access the latest online documentation, go to the
product library page at:

www.ibm.com/software/webservers/appserv/zos_os390/

The change is to the table on page 131, which now reads:

--------------------------------------------------
Enable Setting OS Thread    Clear the check box
Identity to RunAs
--------------------------------------------------
Temporary fix Comments
APAR information
APAR number PQ59046
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED DOC
PE NoPE
HIPER NoHIPER
Submitted date 2002-03-14
Closed date 2002-04-30
Last modified date 2002-04-30

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

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 #: PQ59046
IBM Group: Software Group
Modified date: Apr 30, 2002