[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2343
  • Last Modified:

Connect direct file corruption

I am sending a file using connect direct from a windows platform to a UINIX platform. I firstly found that we would get a small box in place of the carridge return which would throw out the fixed length file we then added an additional sysopts to the script and this has improved the file but i am still getting a few boxes t random points in the file.

Is anyone a connect direct expert and able to help?

here is mock copy of the script


SUBMIT MAXDELAY=UNLIMITED
SENDX PROCESS
SNODE=DEST
STEP1 COPY  
FROM (PNODE FILE= C:\MyFile.txt)
SYSOPTS="DATATYPE(BINARY) XLATE(NO)"
TO (SNODE FILE= /mailbox/test/myfile.txt)
SYSOPTS="DATATYPE=BINARY XLATE=NO"
PEND;  
QUIT;
0
LBGUC04
Asked:
LBGUC04
  • 2
1 Solution
 
arober11Commented:
Once transfered you could run the file through: dos2unix else you might want to try changing the BINARY for ASCII on the SYSOPTS line, assuming "Connect direct" or whatever protocol your using is similar to FTP.

0
 
arober11Commented:
Try:

SYSOPTS="DATATYPE=TEXT XLATE=YES"

If still no luck then then manual may be of some help, see: http://www.scribd.com/doc/36139478/NDM-RefGuide

As you haven't specified the code page / encoding of your Windows file or the character-set / code page on your Unix system I can only guess.

0
 
LBGUC04Author Commented:
I have the answer now, the snode sysopts part of the C:D script should have read SYSOPTS=":DATATYPE=BINARY:XLATE=NO:" with the added colons
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now