PQ41394: EXECUTING WSCP(WEBSPHER CONTROL PROGRAM) WITH SPECIFIED PROPERTYFILE CAUSES FILE CREATION IN MS-DOS STYLE.


APAR

APAR status
Closed as fixed if next.

Error description
Sun Solaris V2.6
WAS Advanced V3.5
.
Executing WSCP with specified property file causes file
creation in ms-dos style. As example:
do->./wscp.sh -p was_wscp.rc
You will see, that the result of the above process, cause/create
1)c: (directory)
2)c: temp secbootrep (directory and file)
$ls -al (before execute "WSCP -p "property.file")
_______________________________________________________________
total 3272
drwxr-xr-x   3 wassys  tivas  2048 Aug 22 12:24 .
drwxr-xr-x  20 wassys  tivas  1024 Aug 21 10:52 ..
rwx------   1 wassys   tivas  3412 Aug 21 09:19 admin.config
-rwx------  1 wassys   tivas  2142 Aug 21 08:1  admin.config.bak
-rwxr-xr-x  1 wassys   tivas  1997 Aug  3 00:3  adminclient.sh
-rwxr-xr-x  1 wassys   tivas  678 Aug  3 00:38  reatedb2.sh

______________________________________________________________
$ls -al (after execute "WSCP -p "property.file")
_______________________________________________________________
total 3276
drwxr-xr-x   4 wassys  tivas  2048 Aug 22 12:24 .
drwxr-xr-x  20 wassys  tivas  1024 Aug 21 10:52 ..
rwx------   1 wassys   tivas  3412 Aug 21 09:19 admin.config
-rwx------  1 wassys   tivas  2142 Aug 21 08:1  admin.config.bak
-rwxr-xr-x  1 wassys   tivas  1997 Aug  3 00:3  adminclient.sh
-rwxr-xr-x  1 wassys   tivas  678 Aug  3 00:38  reatedb2.sh
rwxr-xr-x   3 wassys tivas    96 Aug 22 12:25c:creation in ms-dos style. As example:do->./wscp.sh -p was_wscp.rcYou will see, that the result of the above process, cause/create1)c: (directory)2)c: temp secbootrep (directory and file)$ls -al (before execute "WSCP -p "property.file")_______________________________________________________________total 3272drwxr-xr-x   3 wassys  tivas  2048 Aug 22 12:24 .drwxr-xr-x  20 wassys  tivas  1024 Aug 21 10:52 ..rwx------   1 wassys   tivas  3412 Aug 21 09:19 admin.config-rwx------  1 wassys   tivas  2142 Aug 21 08:1  admin.config.bak-rwxr-xr-x  1 wassys   tivas  1997 Aug  3 00:3  adminclient.sh-rwxr-xr-x  1 wassys   tivas  678 Aug  3 00:38  reatedb2.sh______________________________________________________________$ls -al (after execute "WSCP -p "property.file")_______________________________________________________________total 3276drwxr-xr-x   4 wassys  tivas  2048 Aug 22 12:24 .drwxr-xr-x  20 wassys  tivas  1024 Aug 21 10:52 ..rwx------   1 wassys   tivas  3412 Aug 21 09:19 admin.config-rwx------  1 wassys   tivas  2142 Aug 21 08:1  admin.config.bak-rwxr-xr-x  1 wassys   tivas  1997 Aug  3 00:3  adminclient.sh-rwxr-xr-x  1 wassys   tivas  678 Aug  3 00:38  reatedb2.sh
-rw-r--r-- 1 wassys tivas 1692 Aug 22 12:2c: temp secbootrep ______________________________________________________________ You will see, that the result of the above process, cause/create 1)c: (directory) 2)c: temp secbootrep (directory and file) The file "secbootrep" contains binary info what can not be read. . The wscp -p "property.file" result self is without error and successful. But this additional cause above can be seen.
rwxr-xr-x 3 wassys tivas 96 Aug 22 12:25c:-rw-r--r-- 1 wassys tivas 1692 Aug 22 12:2c: temp secbootrep______________________________________________________________You will see, that the result of the above process, cause/create1)c: (directory)2)c: temp secbootrep (directory and file)The file "secbootrep" contains binary info what can not be read..The wscp -p "property.file" result self is without error andsuccessful. But this additional cause above can be seen.
Local fix
No.
Problem summary
I think orb subsystem need a directory for
bootstrapRepositoryLocation, but it can not find it in "System
Property", which includes the properties defined in the
wscp.rc file.  So it selects  c:\temp\secbootrep as the default
directory, which is incorrect for UNIX.
.
If you define bootstrapRepositoryLocation in the wscp.rc, you
can avoid this defect.
.
bootstrapRepositoryLocation and secbootrep are in the ORB code.
.
It is intended to correct this problem in the next release of
the ORB, if any.  Note, no customer feedback was provided in
a timely fashion, so this APAR is being closed.
Problem conclusion
Temporary fix
Comments
APAR information
APAR numberPQ41394
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED FIN
PENoPE
HIPERNoHIPER
Submitted date2000-09-12
Closed date2000-12-19
Last modified date2000-12-19

APAR is sysrouted FROM one or more of the following:

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


Modules/Macros
ORB
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information

Applicable component levels
R350 PSNUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ41394
IBM Group: Software Group
Modified date: 2000-12-19