We have a trading partner who sends/receives X12 messages without the ~ segment terminator via Geis. Gentran's xprocess is not functioning as it is supposed to. I.E manual execution by hand is handled successfully but when run from unattended mode , it failed. In the mean time , we are manually adding & removing the ~ by hand. <br>
<br>
To recap the situation, in outbound, Geis expects the message to be terminated with CRLF. Running xprocess with -8 , -2 in unattended mode, did not result in removing of the ~, in fact no transformation of the file at all. Running xprocess from command mode, the utility ran successfully but with side effects. <br>
<br>
-2 parameter resulted in line terminated with CR <br>
-8 parameter resulted in line terminated with= LF<br>
<br>
According to Gentran knowledgeBase, -2 is supposed to result in CRLF, but the manual and our experience shown that it resulted in CR only. When the message sent to Geis, Geis aborted the transmission due to line terminator was not CRLF. As a last resort, we used -1, but found out later that the -1 parameter replaced a character with another character, but not drop a character. e.g. before ~CRLF , after xprocess, CRCRLF, which do not solve the transmission to Geis problem.<br>
<br>
In inbound, Gentran expects the message to be terminated in ~ for translation to begin. Our client receives both X12 & EDIFACT, Xprocess -1 or -3 automatically adds the ~ to both X12 & EDIFACT messages, not X12 messages only. <br>
<br>
so, our questions are <br>
1- why the xprocess failed in unattended mode? anyway to make it work or workaround it?<br>
2- anyway for xprocess to add CRLF to text<br>
3- anyway for xprocess to add ~ to x12 messages only<br>
<br>
To recap the situation, in outbound, Geis expects the message to be terminated with CRLF. Running xprocess with -8 , -2 in unattended mode, did not result in removing of the ~, in fact no transformation of the file at all. Running xprocess from command mode, the utility ran successfully but with side effects. <br>
<br>
-2 parameter resulted in line terminated with CR <br>
-8 parameter resulted in line terminated with= LF<br>
<br>
According to Gentran knowledgeBase, -2 is supposed to result in CRLF, but the manual and our experience shown that it resulted in CR only. When the message sent to Geis, Geis aborted the transmission due to line terminator was not CRLF. As a last resort, we used -1, but found out later that the -1 parameter replaced a character with another character, but not drop a character. e.g. before ~CRLF , after xprocess, CRCRLF, which do not solve the transmission to Geis problem.<br>
<br>
In inbound, Gentran expects the message to be terminated in ~ for translation to begin. Our client receives both X12 & EDIFACT, Xprocess -1 or -3 automatically adds the ~ to both X12 & EDIFACT messages, not X12 messages only. <br>
<br>
so, our questions are <br>
1- why the xprocess failed in unattended mode? anyway to make it work or workaround it?<br>
2- anyway for xprocess to add CRLF to text<br>
3- anyway for xprocess to add ~ to x12 messages only<br>
