{
{   The purpose of this procedure is to provide an attach which does NOT
{ modify the permanent file catalog.  This attach is to be used ONLY by the
{ system job, prior to normal permanent file recovery, and committment.
{ A call to pfp$validate_catalog may be made first to determine if the
{ catalog in which the file resides may be read.
{ If we were to write in the catalog prior to committment, modified pages
{ might not get flushed, and the memory image could NOT be used to extract
{ the pages, thus the possibility of a half updated catalog would exist.
{ This same possibility also exists when we are recovering without an
{ image file.  This attach could also be used by the system in cases where
{ the caller could be certain there would be NO subsequent conflicting
{ usage or no subsequent deletions. There is a slight performance improvement
{ associated with use of this attach.
{   The usage and share are NOT used to verify that the requested usage does not
{ conflict with prior usage.
{ Great care should be taken to insure that the file is NOT deleted during
{ the period the file is attached with the restricted attach.
{ When the file is returned no catalog access is made.
{ The file should be returned prior to recovery.
{ Volume overflow, or underflow of the file is prohibited, and a system error
{ is returned if this occurrs on amp$return. Update of the file label
{ (change_file_attributes) is NOT allowed.
{ The file must reside on the mainframe that is making the request.  This
{ request will NOT cause access to the file server to occur.
{
{
{  PFP$RESTRICTED_ATTACH (LFN, PATH, CYCLE_SELECTOR, PASSWORD, USAGE_SELECTIONS,
{             SHARE_SELECTIONS, STATUS)
{
