|
View previous topic :: View next topic
|
| Author |
Message |
George Hayes
New User
Joined: 29 Oct 2007
Posts: 7
Location: Tennessee
|
|
|
|
I'm hoping that someone can help with this.
When tranferring a file from the mainframe to a windows server, the spaces at the end of the record are being coverted. I include an example:
On the mainframe:
YY
EE4444444444444
880000000000000
After the transfer. On the server:
YY
The 'YY' is followed by a tiny square, which I could not figure out how to copy, bit I believe is a carriage return character.
We suspect that using a SYSOPTS='DATATYPE(ACSII)' would send the data correctly. Can someone verify that? And do you have an example that I might use?
Thanks. |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
It appears as though your system is set up to truncate trailing spaces on the target system. |
|
| Back to top |
|
|
George Hayes
New User
Joined: 29 Oct 2007
Posts: 7
Location: Tennessee
|
|
|
|
| I neglected to mention that if using the mainframe FTP transfer manually, the file transfers perfectly. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
I do not know about NDM but I do know that there is a configuration option for FTP that controls whether or not trailing blanks are sent (TRAILINGBLANS TRUE sends them, TRAILINGBLANKS FALSE does not).
You probably need to consult your site support group about the NDM and FTP configuration options. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
Did you also set strip.blanks(no) as described in the Process Statement Guide?
| Quote: |
datatype(text|binary) specifies the type of data contained within the file.
text indicates it is a text file and that trailing blanks will be stripped unless you specify strip.blanks(no). Translation of the data is performed unless you also specify xlate(no). The default is text for all nodes, except Windows nodes.
strip.blanks(yes | no) determines whether trailing blank characters at the end of each record are removed from a line of text before it is written to the Windows text file.
Note: The strip.blanks parameter is ignored when datatype(binary) is specified.
yes removes trailing blank characters. The default is yes.
no does not remove trailing blank characters. The default is no for Windows.
strip.oneable(yes | no) strips ^Z from the end of old DOS files. If this character is not stripped from old DOS files, Connect:Direct Windows translates ^Z into 3F when files are sent to the snode.
yes removes ^Z from the end of old DOS files.
no does not remove ^Z from the end of old DOS files. The default is no.
xlate(no | yes) indicates whether character translation should be performed using the default or user-supplied translation table. Typically, this translation is between ASCII and EBCDIC.
no specifies the translation should not be performed. The default for Windows is no.
yes specifies the translation should be performed.
|
|
|
| Back to top |
|
|
George Hayes
New User
Joined: 29 Oct 2007
Posts: 7
Location: Tennessee
|
|
|
|
I hope you don't mind, but I have new task, replacing the previous one.
I simply need to add a CR/LF at the end of each record from within my COBOL program. It seems to me that I have done this before, maybe 20 years ago but, I cannot remember how. Can someone tell me how to define a CR/LF at the end of each record?
Thanks. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
x'0D0A' is a cr/lf.
You may still have an issue with the trailing blanks. |
|
| Back to top |
|
|
|
|
