PH22121: Z/OS EXPLORER 3.1 CARRIAGE RETURN OCCURRING (0X0D) WHEN TRANSFERRING FILE TO Z/OS UNIX FILES

APAR status

• Closed as program error.

Error description

• z/OS Explorer 3.1 Carriage Return occurring (0x0d) when
  transferring File to z/OS UNIX Files
  When a file is copied from the client to the USS file system my
  windows file has line breaks identified by carriage return +
  line feed as is customary in windows.
  
  After transfering the file to the mainframe in z/OS UNIX Files
  sometimes a carriage return hexcode is left over after transfer.
  When viewing it on the mainframe in ISPF edit with hex on it
  looks like
             if Not-Found in Current-Index then
  44444444444884D9A6C9A984894CA9989A6C988A4A889044
  000000000009605630664540950349955309545703855D00
                                               *
  This additional 0x0d seems to be occurring on page borders
  (0x1000 or 4096) which is the usual transfer size.
  

Local fix

• Preferences->Remote Systems->Files->File Transfer Buffer
  Size->Upload from the default (40K) to something much larger
  like 400K.
  

Problem summary

• When using text-mode to upload a file that is larger than the
  transport buffer size from Windows to z/OS, it is possible for
  the resulting file to contain carriage return characters.
  

Problem conclusion

• The '\r' chars can remain due to the line break conversion
  missing the case where the Windows \r\n sequence of characters
  is split across buffer boundaries.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  EXP FOR Z/OS CL

• Fixed component ID

  5655EXP00

Applicable component levels