{
{    The purpose of this procedure is to relink a file from the client to the
{ server during server job recovery.  This involves going over to the server,
{ and verifying that the file is still attached on the server.  If the file IS
{ still attached on the server, all the information required to update the
{ device manager and file manager tables on the client is returned back to the
{ client.  The result of the operation on the server (see
{ pfp$relink_file_to_client) is to mark the file as no longer waiting for the
{ client job to recover.  As a result of this operation the lifetime of the
{ file on the client is advanced to the lifetime of the now active server, and
{ access may proceed to the file.  The file manager must set the memory manager
{ access_state to mmc$sas_allow_access.
{
{       PFP$RELINK_SERVER_FILE (OLD_APFID, INTERNAL_NAME, OLD_SFID, NEW_APFID,
{             NEW_SFID, STATUS)
{
{  OLD_APFID:  (Input) This parameter specified the attached permanent file
{        identifier previously associated with the file.
{
{ INTERNAL_NAME:(Input) This parameter specified the global file name for the
{       cycle.
{
{ OLD_SFID:  (Input) This parameter specified the system file identifier that
{       is used to describe the file on the client mainframe.
{
{ NEW_APFID:  (Output) This parameter returns the new attached pf table entry
{       used.
{
{ NEW_SFID:  (Output) This parameter returns the new sfid.  For now this is
{       assumed to be the same as the old sfid and it is not required to
{       replace if.
{
{ STATUS: (output) This parameter returns the request status.
{   If status is abnormal then the file must be changed to indicate that
{    access to the file is terminated.
{
