COPY:FILESYS:FILE,SRC ="/no5text/rcv/aimrc.tmp", DEST
="/no5text/rcv/aimrc2";
Response: COPY FILESYS FILE COMPLETED
41. Type and enter:
CLR:FILESYS:FILE,FN="/no5text/rcv/aimrc.tmp";
Response: CLR FILESYS FILE COMPLETED
42. Type and enter:
DUMP:FILE:ALL,FN= "/no5text/rcv/aimrc";
Response: DUMP FILE ALL COMPLETED 1 no5dodd1 is the current disk odd
43. Was no5dodd1 printed in the previous step?
Note: At this point in the procedure, the loading of the AM text and AM ODD
tapes is completed. The next step is to perform a system initialization while
requesting a backout of recent changes. The reason for requesting the backout of
AM recent changes is that any recent change log files which may exist on the
disk will be inconsistent with the Office Dependent Data (ODD) disk image just
read into the system. Before performing the system initialization, be sure that
the Backup Root indicator is SET and the Min Config indicator is clear on the
EAI page.
If YES, continue with the next step.
If NO, seek technical assistance.
44. On the EAI page, type and enter: 42;h;54; to boot the AM.
45. Did the EAI Page respond with one of the following:
Boot? (y/n) or
BkRt Set! Boot (y/n)?
If YES, type and enter: y and continue with the next step.
If NO, continue with the next step.
46. Did the AM initialization complete (Page 111/112 displayed)?
If YES, continue with the next step.
If NO, seek technical assistance.
47. The AM is now running on the backup root file system with a different AMODD.
Now do post-AM recovery actions to recover the switching module ODD and
switching module text (if necessary), and return to the primary root file system.
Go to “Post AM Recovery Cleanup,” Procedure 7.2.
48. STOP. YOU HAVE COMPLETED THIS PROCEDURE.
235-200-150
January 2003
SYSTEM RECOVERY
Procedure 7.1.4
Issue 3.00 Page 7.1.4-5
To Next Page
Loading...