COLLATE - Specify Display Character set
Syntax
COLLATE |
[ ANSI | source-name | ? ] |
Operands
ANSI |
Requests use of the standard ANSI character set |
source-name |
Requests use of the codepage called source-name. |
? |
Display the current status of the setting. |
Abbreviations and Aliases
ANSI can also be spelled as ASCII
Description
There are times when it can be useful to “pretend” that the edit data is another codepage than that specified by the SOURCE setting. For example, if you were looking at a SYSOUT file from a mainframe (let's say, an EBCDIC-based MVS job stream file containing JCL, compiler listings and user program output), which had been translated back to ANSI when sent to the PC, it is difficult to treat this as EBCDIC data, since it no longer is encoded as EBCDIC.
By specifying COLLATE EBCDIC, when display mode is set to HEX, you will see EBCDIC hex equivalents rather than ANSI. Similarly, the SORT command will use EBCDIC for the collating sequence rather than ANSI.
The COLLATE EBCDIC command allows you to have the “experience” of treating a file as though it were EBCDIC, even when it really isn't.
The source operand can be any value for which a valid source-name.SOURCE file exists in the SPFLite data directory. SPFLite is distributed with a default translation table called EBCDIC.SOURCE. You can create additional translation tables to meet specific requirements, including tables which translate from one variant of ASCII to another.
It is possible, though not recommended, to directly modify the standard EBCDIC.SOURCE file.
The COLLATE setting by default is the same as the SOURCE setting. It is associated with individual file types and is stored in the Profile for that file type.
Created with the Personal Edition of HelpNDoc: Full-featured Help generator