File attribute handling

ARCHIVE saves not only the data part of files and job variables, but also the metadata part (catalog entry) containing the attributes. These attributes can be divided into four groups:

• Password attributes

  These are defined using the following operands in the /CREATE-FILE and /MODIFY-FILE-ATTRIBUTES commands:

  IO-ATTRIBUTES, DISK-WRITE, WRITE-PASSWORD, READ-PASSWORD, EXEC-PASSWORD, SPECIFY-ACCESS, DESTROY-BY-DELETE, AUDIT, SPACE-RELEASE-LOCK, BACKUP-CLASS, SAVED-PAGES and MIGRATE

  In the macro, the following operands are used in addition:
  ENCRYPT, FTINFO, NTBEIMC and OPNBACK

  All attributes processed with COPY-FILE PROTECTION=SAME are processed by ARCHIVE as well.

• Attributes for access protection

  These attributes relate to file protection and are defined by the owner environment (user ID and catalog ID):

  GUARDS, BACL, ACCESS and USER-ACCESS

  The attributes for access protection are handled likewise via the command /COPY-FILE PROTECTION=SAME.

• Date attributes

  These include the creation date, expiration date and last-access date.

• Other file attributes

  These relate to the contents of the data part (e.g. FCBTYPE, BLKCTRL, ...).

Handling of these four attribute groups depends on the desired application (backup or transfer):

• Backup

  This application is effected by SAVE/RESTORE runs without any change of the owner environment, i.e. the catalog ID and user ID stay the same.
  For backup, ARCHIVE attempts to retain the attributes valid at the time of saving.

• Transfer

  This application is effected by EXPORT/IMPORT runs or SAVE/RESTORE runs with a change of the environment, i.e. the catalog ID and/or user ID are modified.
  For transfer, ARCHIVE attempts to reset the password, access protection and date attributes and to retain the other file attributes.

How ARCHIVE handles the attributes in accordance with the considerations mentioned above and with existing compatibility restrictions is described below.

• If a file is not protected with GUARDS or BACL, the access protection and password attributes for RESTORE are reset to the values they had when the file was saved.

  In the case of an EXPORT run with ATTRIBUTES=RESET, the access protection and password attributes in the save file are reset; during a subsequent IMPORT, they are then set to match the status of the disk.
  In an IMPORT run, the access protection and password attributes are either reset to the DMS default values (if the file to be replaced does not exist) or they are set to the same values as the existing file. 

• If a file is protected with GUARDS or BACL, handling of the attributes for access protection depends on the type of application:

  • For a backup (i.e. without renaming the catalog ID or user ID), all attributes for access protection are reset to the values they had when the file was saved.

    For restoring to a private disk, the attributes for access protection are reset.

  • For a transfer, the attributes for access protection are either reset to the DMS default values (if the file to be replaced does not exist) or they are set to the same values as the existing file.

    Exception
    The operand ENVIRONMENT-ATTRIBUTES=FROM-ORIGIN of the RESTORE statement permits a file to be restored while renaming the user IDs. The system support may rename both the catalog ID and the user ID, the nonprivileged user only the catalog ID. The attributes for access protection are then reset to the values they had when the file was saved.

• If a file is protected with GUARDS or BACL, the password attributes always retain the values they had at the time of saving.

• The date attributes are retained for a backup, but are reset for a transfer.

• In save runs with SAVE-ACL=NO, the access control list is not saved on the tape. In this case, the behavior of the attributes for access protection described above applies.

• The other file attributes are retained: the data part is not affected by a change of environment or by the type of application.

The two following tables summarize the values assumed by the attributes in a RESTORE or IMPORT run:

1. Attributes of files/job variables which are not protected with GUARDS or BACL in the case of SAVE/EXPORT or save file created via EXPORT with the operand ATTRIBUTES=RESET.

   Value	Save version processed with RESTORE	Save version processed with IMPORT
   		Is there a file with the same name on the disk?
   		Yes	No
   Values of the password attributes	same as for save file	same as for save file or disk file 1	same as for save file
   Value of ACCESS USER-ACCESS, BACL and GUARDS	same as for save file	same as for save file or disk file 1	same as for save file
   Values for last-access, creation and expiry dates	same as for save file	current date	current date

   ¹ Save file created via EXPORT with the operand ATTRIBUTES=RESET

2. Attributes of files/job variables which are protected with GUARDS or BACL in the case of SAVE/EXPORT; the save file was not created via EXPORT with the ATTRIBUTES=RESET operand.

   Value	Save version created with SAVE, without renaming the catalog ID and user ID
   	File is restored to
   	PUBLIC	private disk (saved from PUBLIC)
   Value of the password attributes	same as for save file	same as for save file
   Value of USER-ACCESS	same as for save file	OWNER-ONLY
   Value of ACCESS	same as for save file	WRITE
   Value of BACL and GUARDS	same as for save file	OFF
   Values for creation, expiration and last-access dates	same as for save file	same as for save file

   Value	Save version created with EXPORT or SAVE (with renamed catalog ID or user ID in the case of SAVE)
   	Is there a file with the same name on the disk?		RESTORE with ENVIRONMENT- ATTRIBUTES= FROM-ORIGIN
   	Yes	No
   Value of the password attributes	same as for save file	same as for save file	same as for save file
   Value of USER-ACCESS	same as for disk	OWNER-ONLY	same as for save file
   Value of ACCESS	same as for disk	WRITE	same as for save file
   Value of BACL and GUARDS	same as for disk	OFF	same as for save file
   Values for creation, expiration and last-access dates	current date	current date	same as for save file