The aspects described below must be observed in order to ensure safe execution of the applications.
Unless it is ascertained that the file has been recalled by a preceding /SECURE-RESOURCE-ALLOCATION command, the contents of the catalog entry for a file before opening the file must not be compared with the contents after opening it. This applies to the attributes:
coded file ID (CFID)
locality description (VOLUME, extent count and extent list)
Applications using the internal file name (CFID) for checking and processing files (e.g. with UPAM) must not determine the CFID until any recall operation has been completed.
Migrated files may not be renamed. Corresponding actions are rejected with error messages.
If an application wants to rename files that have not previously been processed, a SECURE-RESOURCE-ALLOCATION command must be issued, for example, to ensure that the file has not been migrated.