I have a connect direct process on AIX box,
that transfers a bunch of files using tar to
two different solaris boxes.The process was working fine until recently until one of the box got booted and cd server went down. Once the cd server is up, the cd step stopped working to that box complaining that there was there is "Possible pipe command
error".

The AIX box has C:D 3.3 and OS 4.3
and the both solaris boxes have C:D 3.4 and OS 5.8.

Since the both solaris boxes have the same versions and we have files coming from one AIX server, it doesn't make any sense to point the error to the comaptibility errors.

Anyways, here is the syntax of the CD statement that is not working anymore to one of the solaris box but work successfully to other solaris. The total size of the files vary from 20 MB to 300 MB

submit emcdstlogc process
snode=SLSUDV21
snodeid=(em0096,03saturn)
step01 copy from (file="cd /appl/emsa/data/tartlog/2004020/20/; tar -cf - *"
sysopts=":pipe=yes:"
pnode)
to (file="mkdir -p /appl/emsa/datafeed/tlog/2004020; mkdir -p /appl/emsa/datafeed/tlog/2004020/20;cd /appl/emsa/datafeed/tlog/2004020/20/; tar -xf -"
sysopts=":pipe=yes:"
snode)

pend;

Hi,

would be help full to see statistic & error information from direct.
Including the option detail=yes.

direct
sel stat detail=yes;

No Risk No Fun

Frank

Here are the detailed stats

------------------------
PROCESS RECORD Record Id => CTRC
Process Name => emcdstlogc Stat Log Date => 01/27/2004
Process Number => 1105 Stat Log Time => 15:34:11
Submitter Class =>
Submitter Id => em0097@sliudv03

Step Start Date => 01/27/2004 Step Start Time => 15:33:33
Step Stop Date => 01/27/2004 Step Stop Time => 15:34:11
Step Elapsed Time=> 00:00:38

Step Name => step01
SNODE => slsudv21
Completion Code => 8
Message Id => XSQF010I
Short Text => Possible pipe command error; &REASON.
Ckpt=>N Lkfl=>N Rstr=>N Xlat=>N Scmp=>N Ecmp=>N
Local node => P
From node => P
Src File => cd
Dest File => mkdir
Source Destination
Ccode =>0 Ccode =>8
Msgid =>SCPA000I Msgid =>XSQF010I
Bytes Read =>210644992 Bytes Written=>210644992
Recs Read =>9143 Recs Written=>9143
Bytes Sent =>210663278 Bytes Recvd =>210663278
Rus Sent =>51432 Rus Recvd =>51432
---------------------

2. Here is detailed stats when ran with trace option

---------------------
PROCESS RECORD Record Id => CTRC
Process Name => emcdstlogc Stat Log Date => 01/28/2004
Process Number => 1170 Stat Log Time => 11:22:44
Submitter Class =>
Submitter Id => em0097@sliudv03

Step Start Date => 01/28/2004 Step Start Time => 11:22:44
Step Stop Date => 01/28/2004 Step Stop Time => 11:22:44
Step Elapsed Time=> 00:00:00

Step Name => step01
SNODE => slsudv21
Completion Code => 8
Message Id => XSMG622I
Short Text => An exception response was received during process e
xec.
Ckpt=>N Lkfl=>Y Rstr=>Y Xlat=>N Scmp=>N Ecmp=>N
Local node => P
From node => P
Src File => cd /appl/emsa/data/tartlog/2004021/20/; tar -cf - *
Dest File => mkdir -p /appl/emsa/datafeed/tlog/2004021; mkdir -p /appl/emsa/datafeed/tlog/2004021/20;cd /appl/emsa/datafeed/tlog/2004021/20/; tar -xf -
Source Destination
Ccode =>8 Ccode =>0
Msgid =>XSMG622I Msgid =>
Bytes Read =>46080 Bytes Written=>0
Recs Read =>2 Recs Written=>0
Bytes Sent =>40960 Bytes Recvd =>0
Rus Sent =>10 Rus Recvd =>0
---------------------

I also opened a ticket with vendor. They just get away with the fact that they don't support that C:D version 3.3 on AIX anymore and it is versioning problem.

If that was the case,For boxes AIX , Solaris1 & Solaris 2, why does the same kind of CD process and same kind of enviornments on both solaris1 and solaris 2 act differently from the same source?

The help desk guy of the vendor doesn't say anything. Instead he want us to update C:D version on AIX to 3.4 .

If anybody can suggest what is happening here, that will be very helpful.

Thx..