Skip to content

File Formats Page

Each data set has a local file format associated with it. The file format specifies what type of conversion is performed when data is transferred between the server and your computer. The native character code for z/OS servers is EBCDIC; for personal computers it is ASCII.

The file formats are:

  • ASCII Text

  • ASCII Data

  • EBCDIC Text

  • EBCDIC Data

  • Unicode Text

  • Unicode Data

  • UTF-8 Text

  • Binary

  • Binary CRLF

Note

These file formats apply to record format "F" and "V" data sets only. Record format "U" data sets always use binary format.

Load modules cannot be uploaded because the directory entries contain embedded pointers that are not supported by SerNet.

ASCII File Formats (Data and Text)

Data is converted from EBCDIC to ASCII when it is transferred from the server to your PC; the data is converted back to EBCDIC when it is transferred back to the server. This is usually the desired behavior so that the data is usable on both the server and your PC.

EBCDIC File Formats (Data and Text)

Character conversions are not performed: the data remains in EBCDIC format on both the server and your PC. The data on your PC is only usable by special programs designed to process EBCDIC data. SPF/PC is a text editor that can be used to edit EBCDIC data on your PC.

'Text' File Formats (for ASCII, EBCDIC, Unicode, and UTF-8)

When Text formats are transferred from the server to your PC, trailing spaces are trimmed and a carriage return/line feed (CR LF) sequence is appended to the end of each line. The CR and LF characters are stripped off when the data is transferred back to the server. This is usually the desired behavior for files that contain text, since CR LF is the standard way of delimiting lines of text on a PC.

'Data' File Formats (for ASCII, EBCDIC, and Unicode)

Data formats are transferred without appending CR LF characters and without stripping any trailing spaces. The record length of the Windows file is fixed and is the same as that on the server. These formats can be used when the data is being read by an application that expects fixed length records and does not use CR LF as line terminators.

This format is appropriate for record format "F" data sets only, and not for record format "V", data sets. The reason for this restriction is that, when downloading from a record format "V" data set, the records must be padded with spaces to produce fixed length records. Thus, when uploading the file again, you would find spaces inserted into the data.

'Binary' File Format

The "Binary" format is for record format "V" or "U" data sets that contain binary data. When the file is downloaded to Windows, no character translation is performed and no line terminator characters are inserted. No changes at all are made to the binary data.

When data is uploaded, records are filled to the maximum length, except the last record, which may be a short record.

This format is appropriate for record format "V" or "U" data sets only, and not for record format "F", data sets. The reason for this restriction is that, when uploading into a record format "F" data set, there can be no short record at the end, and the last record must be padded with spaces to fill the fixed length record. Thus, when downloading the file again, you would find blanks appended to the end of the binary data.

'Binary CRLF' File Format

The "Binary CRLF" format is for record format "V" data sets that contain binary data. When the file is downloaded to Windows, line terminator characters (CR LF) are appended to the end of each record. No changes are made to the actual binary data.

This format is appropriate for record format "V" data sets only, and not for record format

"F", data sets. The reason for this restriction is that, when uploading into a record format "F" data set, the records must be padded with spaces to fill the fixed length records. Thus, when downloading the file again, you would find blanks inserted into the binary data.

The "Binary CRLF" format is available for SerNet 7.1.1+ servers only.

File Format Usage

The table below summarizes how data is represented on the client and server for each of the file formats:

File Format Client Server
Char Code Line Term Char Code Line Term
ASCII Text ASCII CR LF EBCDIC None
ASCII Data ASCII None EBCDIC None
EBCDIC Text EBCDIC CR LF EBCDIC None
EBCDIC Data EBCDIC None EBCDIC None
Unicode Text Unicode CR LF EBCDIC None
Unicode Data Unicode None EBCDIC None
UTF-8 Text UTF-8 CR LF EBCDIC None
Binary CRLF Binary CR LF Binary None
Binary Binary None Binary None

Note

Binary format is used automatically for record format "U" data sets.

File formats are mapped to data set names using data set name patterns. For example, you could specify that all data set names which match the pattern **.UNICODE.TXT contain Unicode Text. A format may also be mapped to a specific data set name. The default file format is ASCII Text.

ZMF Components

For ChangeMan ZMF components, the file format is determined by the ZMF component library type. File formats for ZMF components are specified as properties of the ChangeMan ZMF instance.

Note

File formats can also be configured using the ChangeMan ZDD Wizard application, which allows you to configure multiple servers in a single step.

The File Formats page of the DataSets folder properties.

The default file format (for pattern **) is ASCII Text. To associate file formats with specific data set names or patterns, add entries to the list.

Field Description
Data set name pattern Type a data set name or pattern. For example: **.CNTL would apply to all data sets that end with CNTL. The following data sets would be affected: - TSOID.CNTL - TSOID.TEST.CNTL *.CNTL would apply to data sets that have only two qualifiers and the second one is CNTL: TSOID.CNTL would be affected. TSOID.TEST.CNTL would not be affected. See Data Set Name Patterns for more information about data set pattern names.
File format Select a format from the drop-down menu.
Import Click to retrieve file format associations from a file.
Export Click to save file format associations to a file.

Click to add a file format association.

Back to top