IBM Mainframe Forum

by **quantum_85** » Thu Aug 30, 2018 6:18 pm

Hello,
I am trying to get a text file from mainframe to Solaris system via ftp (ftp client on Solaris) in ascii mode.
But after transfer was done I am getting the extra character (^Z) instead of new line and new lines is disappeared. It looks like following
---
asfdasdfsaf:safdsafdsafd:asdfsafdsf:sadfasdfasdf:^Zsfasafd:sadfsafdsadf:sadfsadfsa:^Zsdfsadfsaf:sadfsdfsaf^Z
----
But it should be like
asfdasdfsaf:safdsafdsafd:asdfsafdsf:sadfasdfasdf
asfdasdfsaf:safdsafdsafd:asdfsafdsf:sadfasdfasdf
asfdasdfsaf:safdsafdsafd:asdfsafdsf:sadfasdfasdf

I have tried different ftp site commands like:
quote site trail
quote site sbsendeol=lf

quote site sbsendeol=none

quote site en=mbcs mb=(IBM-1047,UTF8)

But it did not help, could you please suggest what ftp command should I use?
Thanks in advance!

P.S. Sorry for my English

by **NicC** » Thu Aug 30, 2018 7:53 pm

What are the mainframe data set (not file) characteristics? Also, is it from the zOS or the USS side of the mainframe.

by **quantum_85** » Fri Aug 31, 2018 1:39 pm

Hi NicC,
The problem is I have never worked with mainframe I more familiar with Unix OSs. I have started reading a documentation about ISPF so I will try answer to your questions ASAP, right after I understand how to navigate in ISPF and get needed information

But, thing is, the same file (dataset) is ftping correctly from the same mainframe but from another one "system" (on unix side that file treats like simple ascii text file which includes technical information for a program ). I talked to the mainframe support and they told me that ftp server and systems configurations the same. But the issue still in place so I decided to ask someone else.

Thank you.

by **enrico-sorichetti** » Fri Aug 31, 2018 2:06 pm

ftping correctly from the same mainframe but from another one "system"

OK ... the Mainframe is the same, but
the other ( clent ) system is it a SOLARIS or what else ?

if not a SOLARIS,
You - Your support will have to do some digging to find out what happens on the SOLARIS

Remember
from Your explanation looks like the mainframe is the server, the SOLARIS issuing the get is the client
but if the mainframe is issuing a put to the SOLARIS , then it is the other way around and a different can of worms

by **quantum_85** » Fri Aug 31, 2018 2:38 pm

The client system always the same OS Solaris with UTF-8 locale. Under the "systems" I meant mainframe virtual part, I'm not sure about correct terminology (LPAR, Control Units etc), sorry about that. I meant that we have one Solaris server and two LPAR of mainframe from which we are getting the same dataset(sequential dataset I suppose). Let's called mainframes virtual parts LPAR1 and LPAR2, so when we are getting this file from LPAR1 via ftp it has correct unix Line Feed "\n", actually, If I understand correctly EBCDICT x'25' symbol is converted in Unix LF (\n) correctly. But from LPAR2 we are getting a "one line" file that converts this symbol into ^Z.
Guys from mainframe support team told me that LPARs configuration the same, but I'm not pretty sure about that... I just ask your assistance to help me find in what direction I should digging:)

by **quantum_85** » Fri Aug 31, 2018 6:53 pm

NicC wrote:What are the mainframe data set (not file) characteristics? Also, is it from the zOS or the USS side of the mainframe.

I've got dataset characteristics from ISPF -> 3.4 and then used 's' option does this information enough?

Select all

Data Set Name . . . . : xxx.xxx.xxx.xxx                       
                                                                             
General Data                           Current Allocation                    
 Management class . . : MIGML2          Allocated cylinders : 1              
 Storage class  . . . : STANDARD        Allocated extents . : 1              
  Volume serial . . . : SMN731                                               
  Device type . . . . : 3390                                                 
 Data class . . . . . : **None**                                             
  Organization  . . . : PS             Current Utilization                   
  Record format . . . : U               Used cylinders  . . : 1              
  Record length . . . : 0               Used extents  . . . : 1              
  Block size  . . . . : 10000                                                
  1st extent cylinders: 1                                                    
  Secondary cylinders : 60             Dates                                 
  Data set name type  :                 Creation date . . . : 2018/08/09     
                                        Referenced date . . : 2018/08/31     
                                        Expiration date . . : ***None***     
  SMS Compressible  . : NO                                                         
 

And I can assume that it is from the zOS side.

Also, in 3270 terminal dataset also is displayed like one line file with ":" and "." delimiters inside , it looks like folowing:

dsfasdf asdfsdf asdfasdf:asdadsfsadf:sdfsdfsadf:.sdfsadfsadf sadfsadf asdfsadf:.safdsadfsda sadfsadf asdfsadfsdf:.

So problem is that when we frping this file from LPAR1 this dot "." is replaced in LF (new line \n) on Unix side
When getting it from LPAR2 dot "." is replaced into ^Z

What could be the reason?

Thanks in advance!

by **quantum_85** » Wed Sep 05, 2018 7:17 pm

Maybe someone can help me... Is there any way I could check code page ( CCSID ) configuration, might it be related to the issue?
Thanks in advance!

IBM Mainframe Forum

FTPED from Mainframe to Solaris text file newline issue

FTPED from Mainframe to Solaris text file newline issue

Re: FTPED from Mainframe to Solaris text file newline issue

Re: FTPED from Mainframe to Solaris text file newline issue

Re: FTPED from Mainframe to Solaris text file newline issue

Re: FTPED from Mainframe to Solaris text file newline issue

Re: FTPED from Mainframe to Solaris text file newline issue

Re: FTPED from Mainframe to Solaris text file newline issue