PQ77356: FAILING TO GENERATE PLUGIN-CFG.XML FILE FROM BOTH ADMINCONSOLE AND USING THE GENPLUGINCFG.SH SCRIPT.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Customer is in an ND environment. He tries to generate or
update his plugin-cfg.xml file via the AdminConsole :
Environment -> Update WebServer Plugin -> OK
The plugin-cfg.xml file is not generated. It should be found in
/WebSphere/V5R0M0/DeploymentManager/config but, it is not.
   We tried running GenPluginCfg.sh and it fails also. If you
run this shell script with the -debug option,
GenPluginCfg.sh -cell.name your_cell_name -debug yes
The output shows a java stacktrace:
Exception caught while generating plugin configuration:

Could not get web container configuration for server nodeagent.

com.ibm.websphere.plugincfg.exception.PluginConfigException:
Could not get web container configuration for server nodeagent.
The exception is thrown at
.../../../setServerData(ConfigurationParser.java:637)
   Additionally, this APAR will addresses the fact that the
generated PLUGIN xml file, plugin-cfg.xml file is generated
as ASCII , while the 390 WebServer requires the file in
EBCDIC format. As a circumvention, convert the generated
plugin-cfg.xml to EBCDIC.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: The plugin-cfg.xml file is generated    *
*                      at the wrong HFS location in the wrong  *
*                      code page.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The IVT JSP test compares a number totalled in the client code
with a number generated by a JSP.  The IVT JSP test was failing
because a comment and space on the same line as the generated
number were interferring with the compare subroutine.
Problem conclusion
The comment was moved to the line above the change and the
space was removed from the ivtDate.jsp file.

APAR PQ77356 is associated with SERVICE LEVEL W501000 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ77356
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-08-11
Closed date 2003-09-17
Last modified date 2003-10-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ80305    UP03/09/25 P F309

  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


Current web document: swg1PQ77356.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ77356
IBM Group: Software Group
Modified date: Oct 3, 2003