{    This procedure executes on the server mainframe and rebuilds the attached
{ permanent file table from the old attached permanent file table that is
{ recovered in the client_mainframe_file.  This code takes place during system
{ recovery on the server mainframe.
{
{    The old attached permanent file table must not be written by this
{ procedure, but is copied to a new attached permanent file table.  All new
{ structures are allocated.  This procedure must assign the same apfid in the
{ new attached permanent file table as was assigned in the old.  Valid
{ attached file entries found, must be re-attached in the catalog.  This
{ reattach is performed by pfp$reattach_permanent_file.  A new device manager
{ system_file_id is assigned and stored in the new attached permanent file
{ table entry.  The new attached permanent file table entry is left in the
{ awaiting_client state.
{
{    If a file cannot be reattached it will be removed from the new attached
{ file table.  The job will detect this file when in performs
{ fmp$recover_server_files.
{
{       PFP$REATTACH_FILES_FOR_CLIENT (CLIENT_MAINFRAME_ID,
{             P_OLD_ATTACHED_PF_TABLE, FILES_REATTACHED, FILES_NOT_REATTACHED,
{             STATUS)
{
{ CLIENT_MAINFRAME_ID: (input)  This parameter specifies the mainframe for
{       which the attachment is being done for.
{
{ P_OLD_ATTACHED_PF_TABLE: (input)  This parameter specifies location of the
{       old attached permanent file table.  This table may be referenced but
{       must not be changed.  Pointers pointed to from this table may be
{       referenced directly.
{
{ FILES_REATTACHED: (output)  This parameter returns how many files in the job
{       were reattached.
{
{ FILES_NOT_REATTACHED: (output)  This parameter returns how many files in the
{       job were NOT reattached.
{
{ STATUS: (output) This parameter returns the request status.
{
