ERT Erase and Retain Temporary Files

ERT | NERT Erase Retain Tempfiles/Erase No Retain Tempfiles.

ERT The ERT mode results in those files/Job variables/library elements to be erased with Action Code E first being recataloged to temporary files or libraries. These temporary files will automatically be erased by BS2000 at the end of the task. From the users point of view, all those files erased with Action Code E still exist as physical files until the end of the task (they can be accessed by entering FSTAT #, or STAJV # in the FILENAME-SELECT field).

The name of the temporary file is constructed by prefixing the original name with the temporary file indicator (normally the # character), during the CAT command. Naturally this means that the ERT mode is inoperable when explicitly erasing temporary files.

Library elements will be copied as an identically named element to a temporary library before being erased. They will remain available until the end of the task. The name of the temporary library will be created, as for files, by prefixing the library name from which the element was erased with a # character.

The ERT option will not take effect if the files are erased with the Action Codes ED (Erase...,Data), EC (Erase ...,Catalog) or EN (Erase No Retain Tempfiles). The ERT option will also not work for files larger than 500 PAM pages residing on private volumes.

Deleted data objects are automatically removed from the file list (implicit '-' Action Code). The YANK command can be used to restore those files to the file list.

The ERT mode is set by default.

NERT The ERT mode is disabled with the NERT command (No Erase Retain Tempfiles), or using the SET mask.