Download FLCL - User Manual

FLCL - User Manual
4.7.173
570 / 764
PARAMETER PLATFORM
SYNOPSIS
HELP:
PATH:
TYPE:
SYNTAX:
Redefine environment variable FL_PLATFORM for read operation
DIFF.COMPARE.RECORD
STRING
PLATFORM=WIN/UNX/ZOS/USS/VSE/BS2/MAC
DESCRIPTION The parameter LANG (mainly for character conversion) and the parameter platform (mainly for text formatting)
can be used to overwrite corresponding environment variable LANG and FL_PLATFORM for the read and/or the write operation.
This is useful to emulate another system at read or for write and use the automatism implemented by FLAM for character
conversion and delimiter handling.
For example:
You have a file from a German Windows System on z/OS then it would be useful to set LANG=DE_DE.CP1252 for the read
operation and use the normal LANG environment variable defined in the FLCL configuration file for z/OS. If you want create a
file for Windows on ZOS then the platform definition WIN for write ensure that as default the delimiter CRLF is used.
On the other side if you write a file on a UNIX system for USS on z/OS it would be useful to set the environment variable LANG
for the write operation to EN_US.IBM1047 and platform to USS and use the normal environment variable on the UNIX system
for the read operation. In this case the file will be written in IBM1047 and the records are delimited with NL (0x15).
SELECTIONS
• WIN -Choose Windows as platform (CRLF)
• UNX -Choose Unix derivative as platform (LF)
• ZOS -Choose ZOS as platform (NL)
• USS -Choose USS of ZOS as platform (NL)
• VSE -Choose VSE as platform (NL)
• BS2 -Choose BS2000-OSD as platform (NL)
• MAC -Choose MAC as platform (CR)
4.7.174
OBJECT HASH
SYNOPSIS
HELP:
Generation or check of one way hash values of input data
PATH:
DIFF.COMPARE.RECORD
TYPE:
OBJECT
SYNTAX: HASH(ALGO=MD5/RIPEMD128/RIPEMD160/SHA1/SHA224/SHA256/SHA384/SHA512/CRC8/CRC16/CRC24 ←/CRC32/CRC32C/CRC40/CRC64,CHECK.{},FORMAT=GNU/BSD,OUTPUT=’str’/STDOUT/STDERR)
DESCRIPTION The hash component can be used to generate and check hash values (checksums). This can be useful to verify
data integrity of files after transmission or on a storage device.
If you do not specify the output filename, the output of this component is written to the log.
For the output file, all rules and replacements are valid which are described under "FILENAME HANDLING" above. For
example:
OUTPUT=STDERR
OUTPUT=’~.MYCHECK(HASH1)’
OUTPUT=’<SYSUID>.MYCHECK2’
OUTPUT=’~/mycheck3.txt’
OUTPUT=’<HOME>\hashs\mycheck4.txt’
;
;
;
;
;
is SYSPRINT on z/OS
PDS on z/OS
PS dataset on z/OS
Unix path name
Windows path name