If the receive file is not yet present then it is set up by openFT (BS2000). When library members are received, any libraries that are not present are also implicitly set up. The file or library cannot be set up under the following circumstances:
if the file belongs to a file generation group that has not yet been cataloged.
if the file or library member is specified in fully qualified form and the user ID present in the name does not match the user ID to which the transfer admission refers (possibly via an FTAC admission profile) unless the transfer admission refers to $TSOS
Library members that are not yet present are also implicitly set up. If the member name does not specify a version then the highest possible version number is assumed. The specification WRITE=NEW in the FT request protects existing members in the receive library with TYPE, NAME and VERSION definitions against being overwritten.
A receive file that has been newly set up by openFT (BS2000) or an implicitly created receive library possesses the following file protection features:
no file password
write and read access permitted
not shareable and
no period of protection against modification
Special receive file properties:
If a file is transferred to an NK pubset using BLKCTRL=PAMKEY then it is implicitly converted to BLKCTRL=DATA. In this case, openFT (BS2000) offers the same functionality as the PAMCONV utility (see the “Utility Routines (BS2000)” manual).
PAMKEY cannot convert files with BLKSIZE (STD,16) to DATA.
In the case of transfer to an NK4 pubset it may be necessary to perform conversion with PAMCONV. If no conversion is performed then only evenly blocked files can be transferred to NK4 pubsets. ISAM files must additionally possess an NK4 format (BLKCTRL=DATA(NK4)).
If the receive file is password-protected and if the buffer size of the send file BLKSIZE ≥ 2 (PAM blocks) then the primary allocation of the send file must be sufficiently large. The required primary allocation is dependent on the BS2000 version and can be found in the current DMS manuals.
The secondary allocation for receive files that did not previously exist or are not password-protected has, following transfer, approximately the value
Size of send file / 4.The secondary allocation of password-protected receive files that have already been set up remains unchanged.
PAM files with empty blocks (coded file-id on OPEN
!=coded file-id of the PAM block) are transferred together with the empty blocks if the number of successive empty blocks satisfies the following conditions:Receive file not set up or not password-protected:
Number of empty blocks≤(M / 4) - 3,where M = 72 or is equal to the block number of the last PAM block written in the send file if this block number > 72.Receive file is password-protected:
Number of empty blocks≤secondary allocation of receive filebefore file transfer - 3