|
View previous topic :: View next topic
|
| Author |
Message |
saikat
New User
Joined: 23 Jun 2008
Posts: 26
Location: pune
|
|
|
|
I am using below connect direct script:-
| Code: |
SISBICDE PROCESS PNODE=&PNODE SNODE=&SNODE
SYMBOL &DATAFL="&DATA.:KEYWORDREPLACE=YES"
SYMBOL &PARMFL="&RQST"
STEP1 COPY FROM(PNODE DSN=&DSN1 -
DISP=SHR) -
TO(SNODE DSN=&DATAFL -
sysopts=\":datatype=text:xlate=yes\ || -
\:xlate.table=ebcdic-to-ascii\ || -
\:strip.blanks=yes:"\ -
DISP=RPL) -
COMPRESS -
EXT -
CKPT=100K
IF (STEP1=0) THEN
STEP2 COPY FROM(PNODE DSN=&DSN3 -
DISP=SHR) -
TO(SNODE DSN=&PARMFL -
DISP=RPL) -
COMPRESS -
EXT -
CKPT=100K
EIF
|
Here STEP1 issues return code 0 just after process submission whereas I want to execute step2 only after file is successfully copied into destination node. I have tried with MAXDELAY=UNLIMITED option still it's producing same result. Could you please advise if I want to implement your 1st solution how can I amend the above connect direct script. |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
the moderators are getting fed up of inconsiderate people who tailgate 6 years old topics with unrelated questions
WHEN YOU HAVE A NEW QUESTION START A NEW TOPIC
topic split and moved 
( it was also code' d for better readability ) |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Suggest you redesign . . . There is no good reason to "hang up" resources waiting for an external process to complete.
You could send the file as you do now and on the remote send back a confirmation when the transfer is successful. When the confirmation is received, automatically start the second process? |
|
| Back to top |
|
|
|
|
