View previous topic :: View next topic
|
Author |
Message |
Susanta
Active User
Joined: 17 Nov 2009 Posts: 126 Location: India
|
|
|
|
Hi
When my job gets a file by c:n all records are getting a trailing low-value character(ne line character) from unix. By which C:N option can we stop these new line character .
Please help.
Thanks, |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Have you looked at the documentation for c:n (whatever THAT is)? You should start with the product documentation. |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
Even in English the only thing is this thread. Site specific (or typo). |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
A "low-value" is not a newline character as far as i know. . .
What is C:N? Who is the vendor. What does this connect to on the mainframe or is this a mainframe product? Is the data being "pushed" by the unix system or "pulled" by the mainframe?
The better info you provide, the more someone can help. |
|
Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004 Posts: 4652 Location: Raleigh, NC, USA
|
|
|
|
All I can comment on is that I hope the TS realizes that data is stored in different manners on different machines. I'd hope that his site's data transmission team would know this and could help with this issue.
On Unix machines, text data is stored in ASCII with just a single carriage-return (x'0d') to mark the end of each record. In the world of Windows/Mac, text data is stored in ASCII with a carriage-return/line-feed paid (x'0d0a') to mark the end of each record. This is usually referred to as either the "PC" or "DOS" format. The mainframe stores data in EBCDIC. When transferring ASCII-based text files to the mainframe, the mainframe needs to know how long a record is so it can be properly stored. To accomplish this, the mainframe requires the full carriage-return/line-feed specification (i.e. the DOS or PC format).
For any shop with a variety of server types, it's best to mandate that only the "DOS" or "PC" format will be supported for transmission. |
|
Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011 Posts: 556 Location: USA
|
|
|
|
If your receiving file is pre-allocated, I'd bet it is one byte too long.
In some parts of the Unix world, null (x'00') is used as a string terminator. So it's possible the file is 100 bytes on the Unix side, but 101 bytes on the mainframe side.
Are you also getting and extra line at the bottom, with only a x'3F' in the first byte? |
|
Back to top |
|
|
|