IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

SFTP Issue - destination file record ending with Junk # char


IBM Mainframe Forums -> All Other Mainframe Topics
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
shalva.krish

New User


Joined: 30 Aug 2023
Posts: 3
Location: USA

PostPosted: Sat Feb 17, 2024 1:35 am
Reply with quote

Hi ,

We are currently having FTP where we transfer FTP to SFTP. As part of testing, we processed SFTP job to post the mainframe file to AWS. Job went fine and file posted to AWS. But when we open the file, we can see junk ‘#’ character at the end of each line.
Then we used same mainframe file, posted to AWS using ftp job and that file is not having any junk character.

We validated mainframe file with Hex on - no junk character
we validated the OMVS file with Hex on - No Junk character
we validated the file in AWS after the transfer using SFTP - shows # junk character at the end of each record . While researching I found
this link

community.sap.com/t5/application-development-discussions/how-to-remove-symbol-output-inbound-file-from-sftp-with-write-statement/m-p/12063048

Do SAP has to put any notes for this issue ? Please advise
Back to top
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1743
Location: Tirupur, India

PostPosted: Mon Feb 19, 2024 7:23 pm
Reply with quote

Are you sending from Mainframe dataset to USS(OMVS) and from OMVS to AWS?

What product are you using to send from USS to AWS?
FTPS or SFTP? - Names may look same, but different.
Show the statements used in the transfer?

The problem is most likely CR LF - EOL characters being messed up in different platforms. To indicate End of a record, Mainframe user CR, Windows has CR LF, Unix has LF.

One other suggestion would be to look at the file in Mainframe with HEX ON, then note down the HEX values of 2 records.

Then look how the file looks in OMVS, with HEX ON and note down the HEX values.

Then look at the file in AWS, NOTEPAD++ has a plugin to view the HEX values.

With these steps you can confirm if it's related to CR LF translation, which it most likely is.
Back to top
View user's profile Send private message
shalva.krish

New User


Joined: 30 Aug 2023
Posts: 3
Location: USA

PostPosted: Wed Feb 21, 2024 11:29 pm
Reply with quote

Are you sending from Mainframe dataset to USS(OMVS) and from OMVS to AWS? - Yes using SFTP

we tried using EOL=nl and EOL=not .

For both options it is working without the # character .

Thanks for your help
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> All Other Mainframe Topics

 


Similar Topics
Topic Forum Replies
No new posts sort to find out the char which repea... Mainframe Interview Questions 10
No new posts Format Binary file to EBCDIC JCL & VSAM 4
No new posts Binary File format getting change whi... All Other Mainframe Topics 7
No new posts Compare 2 files and retrive records f... DFSORT/ICETOOL 3
No new posts FTP VB File from Mainframe retaining ... JCL & VSAM 8
Search our Forums:

Back to Top