BS2000 files

In accordance with the different file structures, a distinction is made between the following BS000 file types:

• Cataloged files

  • DMS files (these include SAM, ISAM, and PAM files, PLAM libraries and cataloged generations of a file generation group)

  • POSIX files

• Elements of a cataloged PLAM library

  • Printable or user-definable elements of type D, J, M, S and possibly X

  • Elements with BS2000-specific binary code of type C, L, R and possibly X

In order to be able to transfer POSIX files using openFT, POSIX must be started. The POSIX file system essentially corresponds to the layout and structure of the Unix file system.

The following overview shows the relationship between file name syntax and file type in BS2000.

File name syntax	File type
Starts with $userid or :catid:$userid and does not contain ’/’	DMS file, fully qualified
Starts neither with ’/’ nor with ’./’ nor with $userid nor with :catid:$userid and does not contain ’/’	DMS file, path relative to transfer admission
Starts with ’/’	POSIX file, fully qualified
Starts with ’./’	POSIX file, path relative to transfer admission
Starts with $userid or :catid:$userid and contains at least one ’/’	Name of a PLAM element, fully qualified
Starts neither with ’/’ nor with ’./’ nor with $userid nor with :catid:$userid but contains at least one ’/’	Name of a PLAM element, path relative to transfer admission

BS2000 files may be located either on common disks or on private disks. For processing of files on private disks, the files must be cataloged and the private disks must be properly connected to the system.

Transferring library members

FT systems transfer precisely one library member with an FT request. In the case of transfers between library members, the library organization, the access method and the record structure are retained, whereas in the event of transfers between library members and SAM files only the record structure is preserved.

• During file transfer with FTAM partners, library elements that are located in the remote system can only be accessed using a C-string (and not by using *LIB-ELEM()).

• Library members of a specific type (e.g. load modules) cannot be transferred unless the FT product in use at the partner system permits the transfer of members of this type.