ARMOR

Synopsis

HELP:   Write ASCII armored output
TYPE:   OBJECT
SYNTAX: ARMOR(FORMAT=OFF/STD/EXT,CHRSET=NONE/SYSTEM/ASCII/UCS1/UTF8/EBCDIC/UCS2BE/UTF16BE/UCS2LE/UTF16LE/UCS4BE/UTF32BE/UCS4LE/UTF32LE/LOCAL,DELIM/RECDLM=HOST/BIN/TXT/NL/USS/LF/UNIX/CR/OLDMAC/CRLF/WINDOWS/DLM/SYSTEM,COMMENT='str')

Description

The ARMOR object activates ASCII armor encoding. It also supports EBCDIC as charset. ASCII-armored data is Base64 encoded binary data with a line length of 76 character followed by an optional checksum, surrounded by a header and trailer. The component in whose context the ARMOR object is used (usually PGP) defines the header and trailer information like in the example below:


-----BEGIN header string-----
Version: version string
Comment: comment string

yDgBO22WxBHv7O8X7O/jygAEzol56iUKiXmV+XmpCtmpqQUKiQrFqclFqUDBovzS
vBSFjNSiVHsuAA==
=njUN
-----END header string-----

The ARMOR support adds by default several file attributes which allows FLAM to restore host datasets from such an armored file. The keywords below are supported:

The printed values are decimal numbers or keywords used by FLCL. You can find a detailed description for each keyword if you search for it in this document. Below you can see an example for a VSAM Relative Record Dataset (RRDS) archived in a BZIP2 file using a binary delimiter to separate each record:

flcl conv
   read.record(file='TST.IDAT.RRDS')
   write.record(file='.ODAT.BZ2ARMOR.RRDS' recdelim=x'FE03FF'
   prnc=retain comp.bzip() encode.armor(delim=host))

-----BEGIN BZIP2 FILE-----
Version: FL-CNVBZ2 5.1.16.13587
Comment: created with FLUCv5.1.12.13587 (www.flam.de)
Platform: z/OS on SystemZ with 31 bit (zosz31d0)
BinaryDelimiter: FE03FF
FileOrganization: RDS
BlockSize: 18432
RecordFormat: FR
RecordLength: 60
SlotNumbers: Yes

QlpoMTFBWSZTWVfxaJMAAAD0B9nAQAAABkAAIiAIIBkgAAGgAEDapBpp6ho2nqhQNNDIyYjKJDNl
bfpIZgkbO3n6iXJZxDK6wlOU8H4u5IpwoSCv4tEm
=XvA6
-----END BZIP2 FILE-----

Arguments