|
View previous topic :: View next topic
|
| Author |
Message |
Vidya Bhama
New User
Joined: 17 Sep 2008
Posts: 41
Location: Chennai
|
|
|
|
I have a problem with my get FTP jcl. When i ran the below JCL my file got FTPed without line breaks. Can you please let me know how to add line breaks.
The dataset FTPed has records in continuous fashion as below
Ellen0100EE Mark0200SE
The mainframe dataset should have the records like below instead of the above,
Ellen0100EE
Mark0200SE
My JCL is as below,
| Code: |
//FTP10 EXEC PGM=FTP,REGION=4M,PARM='(EXIT'
//INPUT DD *
abc.xyz.com
username
password
cd /directory/File
ASCII
LOCSITE LRECL=215 RECFM=FB BLKSIZE=27950
GET Sample.DAT 'sample.dataset.new' (REPLACE
QUIT
//OUTPUT DD SYSOUT=*
|
|
|
| Back to top |
|
 |
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
There's nothing you can do from the mainframe side. The data MUST contain the proper record seperator values as documented here:
LOCSIte subcommand--Specify site information to the local host.
| Quote: |
SBSENDEOL
Specifies which end-of-line sequence to use when ENCODING is SBCS, the data transfer type is ASCII, and data is being sent to the server. The following are possible values:
CRLF
Append both carriage return (X'0D') and line feed (X'0A') end-of-line sequences to each line of translated text. This is the default and the standard sequence defined by RFC 959. The z/OS server can receive ASCII data in this format only.
CR
Append only a carriage return (X'0D') end-of-line sequence to each line of translated text.
LF
Append only a line feed (X'0A') end-of-line sequence to each line of translated text.
NONE
Do not append an end-of-line sequence to the line of translated text.
Rules:
Do not use an end-of-line sequence other than CRLF if the server is a z/OS FTP server. The z/OS FTP server supports only the CRLF value for incoming data.
|
|
|
| Back to top |
|
|
|
|
