RECOVERY PROCEDURES [ HP RPG/XL Utilities-Part 2 RISE ] MPE/iX 5.0 Documentation
HP RPG/XL Utilities-Part 2 RISE
Chapter 3 RECOVERY PROCEDURES
While using the RPG Interactive System Environment, you may encounter one
of six problem situations. They are:
* System failures.
* Terminal lockouts.
* Breaking out of Block Mode.
* Transmission errors.
* Loss of echo at the screen.
* Effects of :EOD.
For your information, RISE uses the following file designators during
operation:
* Wdddhhmm--KSAM data file for work file.
* WKddhhmm--KSAM key file for work file.
* Ldddhhmm--compilation listing file.
* Udddhhmm--Undelete file (in temporary domain).
If RISE abnormally terminates, because of system failure, use of the
Break key, or entering :EOD, you may find these files are permanent in
your group and account. The KSAM work file should be recovered, and the
compilation listing file and the UNDELete file can be purged.
Recovering from System Failures
If the system fails while you are editing a copy of a file (initiated by
the TEXT command), do the following:
1. Determine the designator of the file or files placed in jeopardy
by the failure.
a. The name of the work file, which is a permanent KSAM file, is
in the form Wdddhhmm, where "ddd" is the day of the year, "hh"
is the hour of the day, and "mm" is the minute of the hour.
b. The name of the associated key file is WKddhhmm, where K
overlays the first "d" in day of the year, and "ddhhmm" have
the same meaning as they do with the work file.
c. Perform a:LISTFW@######,2 to determine the designators of the
files.
2. After you have the name of the work file, enter the following
command:
:RUN KSAMUTIL.PUB.SYS
3. When you receive a ">" prompt at the terminal enter the following
two commands to KSAMUTIL:
>KEYINFO filename;RECOVER
(and, after recovery is made)
>EXIT
(In the above, "filename" is the name of the KSAM data file determined in
the LISTF command.)
This will recover the work file and take you out of KSAMUTIL. You can
then run RISE and continue editing after you TEXT in the recovered work
file name.
If the system fails while you are editing the file directly (initiated by
the FILE command), perform steps 2 and 3 above. In other words, use
KSAMUTIL and the KEYINFO command with the RECOVER option with the name of
the direct file to restore it for continued editing.
Recovery from Terminal Lockout
Terminal lockout is the term used to describe a state in which the
terminal is totally unresponsive to any key you press. To recover, do
the following:
1. If you are in Line Mode, just press the RESET TERMINAL key twice.
This is a hard reset.
2. If you are in Block Mode, press the RESET TERMINAL key twice, for
a hard reset. Then press softkey F7 to enter Line Mode. An
exception occurs when you are in Scroll set. If you are in Scroll
set (SHOW mode), the special function key F7 has a different
function. In order to return to Line Mode, you must first press
F1, which will take you out of Scroll set and into Master set.
You may then press F7 to enter Line Mode.
Recovery from Breaking out of Block Mode
If you hit the BREAK key inadvertently while in Block Mode, do the
following:
1. Do a hard reset (press the RESET TERMINAL key twice).
2. Type "ESC:" to turn echo on. (At this point you should be able to
communicate with MPE.)
3. Type RESUME to resume execution of the editor. MPE will respond
with "Read Pending."
4. Enter the carriage return.
5. If you are in Scroll set (SHOW mode), press F1 to reset the
special function keys to Master set.
6. Press softkey F8 to display the main menu.
7. Press softkey F8 to refresh the main menu. This will return you
to Block Mode.
NOTE Steps 6 and 7 may be skipped if you press softkey F7, which puts
you in Line Mode instead of Block Mode.
Recovery from a Transmission Error
Transmission errors usually bring to the screen a nonsensical clutter of
characters. The keyboard works but characters, such as escape
characters, appear on the screen erroneously. They cause incorrect
displays of forms in block mode.
To recover from the effects of transmission errors do the following:
1. If you are in Scroll set (SHOW mode), press F1 to reset the
special function keys to normal SHOW mode functions (Master set).
2. Press F8 to display the main menu.
3. Press F8 a second time to refresh the main menu.
You can also press F7 to enter Line Mode and reenter your command.
Recovering Echo After It Is Lost
When your screen remains blank everytime you type a key, your terminal
may have lost its echo. You can recover it in one easy step.
1. Press the ESCAPE key followed by the colon (:).
Recovery from :EOD
If you accidentally or intentionally enter :EOD (End of Data) while in
Line mode, RISE will immediately terminate. Your KSAM work file will not
be purged.
If you were editing a copy of a permanent file (TEXT) or had created a
new work file (ADD), you can locate the work file by typing the
following:
:LISTF W@######,2
See section A, above, for a discussion of this file designator.
To recover this work file, you simply TEXT in the KSAM data file and KEEP
it to a sequential permanent file. Then you use the KSAMUTIL to purge
the KSAM work file with the name located using :LISTF as described above.
If you entered :EOD while editing a file directly (FILE), no harm is
done, and the :EOD operates like the EXIT command. Your changes to the
file will be permanent.
MPE/iX 5.0 Documentation