PQ62159: EAR FILE IS DELETED AFTER SM SCRIPTING API CB390CFG -ACTION "PROCESSEARFILE"

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
The CB390CFG utility which is part of the Systems Management AP
(SMAPI) can be used to deploy an EAR file into a J2EE server.
One unexpected side effect is that the original EAR file is
deleted from the HFS after it is deployed. The original EAR fil
should not be removed by CB390CFG. EAR file deployment via SMEU
on the workstation is not affected by this problem.
Local fix
If the EAR file to be deployed is called /tmp/deployed_app.ear,
issue the following command to create a second link to it befor
issuing the CB390CFG command.
ln earfile /tmp/symlnk_earfile;
.
.  (gen your xml to actually deploy symlnk_earfile)
.
CB390CFG -action processearfile \
         -xmlinput inputprocessearfile.xml \
         -input <your input xml file> \
         -output <your output xml file>
.
.  (the original earfile remains)
---------
When using REXX, the command which creates a link to the ear
file is
 address syscall 'symlink' /tmp/earfile symlnk_earfile
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: When the Systems Management Scripting   *
*                      API (SMAPI) is used to install a J2EE   *
*                      application, the EAR file is deleted    *
*                      from the HFS on the customer's system.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If the Systems Management Scripting API (SMAPI) is used to
install an application on a J2EE server, the application EAR
file is deleted from the HFS as part of the EAR file
processing.

This is the same behavior that occurs when the Systems
Management Enhanced User Interface (SMEUI) is used to install
a J2EE application on a server. The SMEUI uploads the EAR file
to a temporary directory on the HFS, performs the EAR file
processing, and then deletes the EAR file from the temporary
directory. The original EAR file on the client workstation,
however, does not get deleted.

The functionality of the SMAPI when installing a J2EE
application needs to be modified to not delete the EAR file
from the HFS.
Problem conclusion
Support was modified to detect when an EAR file
installation is done via the SMAPI, and to not delete the EAR
file from the HFS for such installations.

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

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOUBINF BBOZ0689 BBOZ0773 BBOZ0814    

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ68443    UP02/08/01 P F207

  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 #: PQ62159
IBM Group: Software Group
Modified date: Aug 4, 2002