Download FLCL - User Manual

FLCL - User Manual
71 / 764
The enforcement of base decoding can even be used if no auto decoding is activated.
See below for the decoding possibilities.
ARGUMENTS
• SWITCH:BASE64/OPGP -Base64 decoding (RFC4648)
• SWITCH:BASE32 -Base32 decoding (RFC4648)
• SWITCH:BASE16 -Base16 decoding (RFC4648)
4.2.70
PARAMETER CCSID
SYNOPSIS
HELP:
PATH:
TYPE:
SYNTAX:
Conversion from this CCSID (enables text handling if set)
CONV.READ.RECORD
STRING
CCSID=’str’/DEFAULT/ASCII/EBCDIC/BOMUTF/BOMUCS
DESCRIPTION The FROM code defines the encoding string or CCSID for the input text stream. If no CCSID is provided, the
default handling (DEFAULT) is used. When reading, the input data’s charset is auto-detected. The charsets below can currently
be detected:
• ASCII (the finally used code page depends on the language code)
• EBCDIC (the finally used code page depends on the language code)
• UTF-8 == US-ASCII
• UTF-16LE == UCS-2LE
• UTF-16BE == UCS-2BE
• UTF-32LE == UCS-4LE
• UTF-32BE == UCS-4BE
If the data is encoded in ASCII or EBCDIC, the corresponding CCSID will be derived from the appropriate environment variable
LANG. On non-ASCII systems, the ASCII-CCSID is derived from the language identifier (e.g. en, de , ..). The same holds true
for non-EBCDIC systems if EBCDIC is detected. When ASCII is detected on an ASCII system, the CCSID from the LANG
environment variable is used (e.g. de_DE.UTF-8 ⇒ UTF-8), if present. If the LANG variable contains no CCSID, then the
language identifier is used (e.g. de_DE ⇒ ISO-8859-1). The same holds true for EBCDIC systems if EBCDIC is detected.
On modern platforms, the CCSID for a resource may be saved in the file system and can also be given by the FIO module. In
general, however, it is recommended to set this parameter to its correct value. For default handling, the keywords DEFAULT,
ASCII and EBCDIC as well as (for multibyte characters) the BOM keywords stated below can be used to help finding the correct
CCSID on read operations.
Character conversions at write operation are also possible, but in this case, the BOM keywords are not supported. When writing,
the FROM CCSID is usually known and does not need to be specified.
In order to use the BOM keywords, a BOM sign must be part of the input data. All unique BOM characters are supported in
principle, but for UTF-16/USC-2 and UTF-32/UCS-4 the same BOM sign is used. You can define by yourself which family is
used.
To get a list of supported encoding strings, please use the command below:
flcl INFO GET.ENCODINGS
Depending on the platform, this function lists all known encoding strings. Some encodings may not be supported. To determine
the supported CCSIDs and corresponding encoding strings and charsets please use: