In BS2000, ZIP containers are always PAM files. They can be transferred to other BS2000 systems or to systems with other operating systems (MS/Windows, Unix, Linux, zOs). In non-BS2000 systems only ZIP containers in WinZip-compatible format can be used.
A ZIP container in PAM file format can be transferred to another system using ftp or openFT V11.0 and higher. Binary mode must be set for the transfer.
When a file is to be transferred to or from a non-BS2000 system using openFT,
openFT < V11.0 only accepts SAM files with RECORD-FORMAT=U. A ZIP container in PAM file format can be converted to a SAM file with RECORD-FORMAT=U or vice versa using the //CONVERT-ZIP-CONTAINER statement. In this case the converted file is stored as a copy in the output file.
If no name is specified for these output files, BS2ZIP generates standard file names for these output files as follows:
<name>.SAM[.ZIP] or <name>.PAM[.ZIP]
where <name> is a basename with a limited length.
Examples
Name of the ZIP container | File format of the ZIP container | Name of the copy |
XYZ | PAM | XYZ.SAM |
XYZ | SAM (with RECORD-FORMAT=U) | XYZ.PAM |
XYZ.PAM | PAM | XYZ.SAM |
XYZ.SAM | SAM (with RECORD-FORMAT=U) | XYZ.PAM |
XYZ.ZIP | PAM | XYZ.SAM.ZIP |
XYZ.ZIP | SAM (with RECORD-FORMAT=U) | XYZ.PAM.ZIP |
XYZ.PAM.ZIP | PAM | XYZ.SAM.ZIP |
XYZ.SAM.ZIP | SAM (with RECORD-FORMAT=U) | XYZ.PAM.ZIP |
Notes
When the resultant file name, including catalog and user IDs, exceeds 54 characters, BS2ZIP truncates the basename (XYZ in the example).
The converted file is created with the userid and the default cat-id of the user, even if the original file is on another userid or catid.