Outbound IDOC status is not turning to 03, stuck at 18(call_SAP, startrfc diff??)

[Steve Johnson]

Hello,
 
>From last few weeks in my Production SAP system all
the IDOC which go through Gentran EDI system were not
turning to 03 and all of them stuck with the status as
18. The logs shows the following information.
 
We could able resolve the problem but we are not about
the root cause.....
 
> >
 
sop:8871:04102003:194806:  0:
Begin:
sop:8871:04102003:194806:
0:Commandline:idoc=.SAPEDG010.000IL3.00009513:
sop:8871:04102003:194806:  0:
edi=.SAPEDG010.000IL3.000095137.xltr:
sop:8871:04102003:194818:  1:Unable to dequeue SAP
archivable status
IDOCs:
sop:8871:04102003:194818:  1:Abnormal Termination:
> >
> >     sox:9104:04102003:194814:  0:Begin:
> >     sox:9104:04102003:194814:
> 0:Commandline:idoc=.ARROW810.000IL3.000095139:
> >     sox:9104:04102003:194814:
0:edi=.ARROW810.000IL3.000095139.xltr:
> >     sox:9104:04102003:194826:  1:Unable to de-queue
SAP archivable
> status IDOCs:
> >     sox:9104:04102003:194827:  1:Abnormal
Termination:
> >
> >     sapdeq:9051:04102003:194812:  0:Begin:
> >     sapdeq:9051:04102003:194812:
0:Commandline:direction=out:
> >     sapdeq:9051:04102003:194812:  0:tpcode=ARROW810
port=SAPEDG010:
> >     sapdeq:9051:04102003:194812:
0:STATUS.000IL3.002ST2:
> >     sapdeq:9051:04102003:194817:  1:startrfc: failed
to call_sap for:
> >     sapdeq:9051:04102003:194817:
1:STATUS.000IL3.002ST2.:
> >     sapdeq:9051:04102003:194817:  1:Abnormal
Termination:
> >
> >     **** 20030410 194817 PDT 21H  : Trace file opened
: PID 9186
> >     ==== Error RFCIO_ERROR_SYSERROR in abrfcpix.c :
246
> >
 
We tried to push with the SAP standard programs
"rseout00", with this we used to successfully push the
idoc's now we are getting the same above error and the
status stands there at 18.
 
Finally we did the following chnage and all the idoc
status for last few weeks turned to successful. We
would like to find the root cause and find the dff
between CALL_SAP and STARTRFC. Where are these
programs residing under gentran server, do we need to
update them like kernel updagrade on EDI servers?
 
>>
Because the call_sap program was failing in the
/bin/sapdeq.status_idocs script, We decided to revert
back to the original RFC program, namely startrfc.
For some reason, previous team lead had changed
startrfc to call_sap back in August of 1998.  The
program worked fine until the end of last week.
 
Here's the new/original command in that sapdeq script:
 startrfc $RFC_ARGS -E PATHNAME=$SPOOL/`basename
$FILE.
 
When we repushed a Status 18 IDoc, it went to
completion.  Now all IDocs in PRD SAP that were stuck
in Status 18 are pushed out and loaded into Advantis.
 
 
Please advise, Thank you in Advance.
 
Steve.
 
__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com