PQ68137: 390FY TOOL GENERATES INCORRECT MANIFEST FILE IN EBCDIC

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
The DDT(390fy) inserts new files in a .ear to create a
"resolved" .ear for WAS z/OS. These files application-xdd.xml,
MANIFEST.MF, and mangled name files are written in EBCIDC and
not ASCII or UTF-8. New code from developer,
fixed most of the problems, but the MANIFEST.MF file is still
in EBCIDC. This works correctly under Windows NT4 but under
USS the files are badly writtne.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: Customers running 390fy on USS/390 is   *
*                      running into a runtime problem within   *
*                      web container init due to MANIFEST.MF   *
*                      file being generated in EBCDIC.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Running 390fy under USS/390 currently generates MANIFEST.MF file
in EBCDIC. Previous drivers were able to cope with this problem
in the ejb runtime as well as web container runtime even though
information stored within MANIFEST.MF file such as Class-Path:
was being lost. As a result, web container code is failing
during the initialize step of the webapps that contain  a
EBCDIC manifest file.
Problem conclusion
390fy processing should always generate all meta-data file
including MANIFEST.MF file in ASCII instead of EBCDIC to avoid
this runtime error even when run under USS/390.

APAR PQ68137 is associated with SERVICE LEVEL W401406 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ68137
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-11-12
Closed date 2002-12-10
Last modified date 2003-01-04

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 UQ72501    UP02/12/17 P F212

  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 #: PQ68137
IBM Group: Software Group
Modified date: Jan 4, 2003