|
|
Some STORE, RESTORE and VSTORE errors cause the
program not to store, restore, or verify a particular file. Others cause the
program to stop running. When STORE, RESTORE or
VSTORE cannot transfer files that you named in your command, it lists
the names of those files on your terminal as part of its standard progress
listing.
When STORE or VSTORE aborts because of an error, you see
specific error messages followed by a general error message (which is the same
for both commands):
STORE ABORTED BECAUSE OF ERROR
When RESTORE aborts because of an error, you see specific error
messages followed by a general error message:
RESTORE ABORTED BECAUSE OF ERROR (CIERR 1091)
You can use the STOREJCW job control word (JCW) to determine the cause
of an error and a proper recovery procedure. Each time you issue a
STORE or RESTORE command, the system updates the value
assigned to STOREJCW.
When STOREJCW is equal to 0, the command executed successfully.
STOREJCW values greater than 0 alert you to the cause of an error.
 |
NOTE: Issuing the VSTORE command also results in the system
updating the value assigned to STOREJCW.
|
To view the value assigned to STOREJCW, use the following
SHOWVAR command:
:SHOWVAR STOREJCW
The system reports the current value. For example:
STOREJCW=4
The value of STOREJCW after you issue a STORE,
RESTORE, or VSTORE command tells you the cause of any errors
in storing, restoring, or verifying the files you named. To determine the cause
of an error:
Use the SHOWVAR command to view the value of
STOREJCW.
Look up that value in Table A-1
"STOREJCW Values". In addition to the cause of an error,
Table A-1 "STOREJCW Values"
displays recommended recovery procedures.
Table A-1 STOREJCW Values
Value |
Cause |
Recovery Procedure |
0 | No errors. | None. |
1 | Syntax error. |
Correct and reenter command. |
2 | Error in opening system resource allocation. |
Purge some files or perform disk space recovery. |
3 | Error in opening an indirect file. |
Does the indirect file you named exist? Do you have adequate access to
it? Is it in use? Is the redirect file an EDIT file? |
4 | Error in opening the file. |
Is the FILE command describing the correct device? Is the media
on the device you named? Unload and reload the media. If you are
restoring or verifying files, check whether or not you have adequate
access to them. |
5 | Error scanning the files. |
Make sure the file names are syntactically correct and correctly
spelled. |
6 | Error in actually storing, restoring, or
verifying files. |
Enter the command again. After a second failure, contact your system
manager. |
7 | A file you attempted to store does not exist
on disk, or a file you attempted to restore or verify does not exist in the
STORE files, or the system could not find files that matched the
pattern you specified (for example, FEB@). |
Did you name the files correctly in the STORE, RESTORE,
or VSTORE command? Do the files you want to store, restore,
or verify exist? |
8 | A file that you tried to store, restore, or
verify was in use, or unable to quiesce a certain TurboIMAGE database. See
the $STDLIST for further information. |
Wait until the file is no longer in use. Enter the command again. STORE
may have timed out trying to quiesce an open transaction. |
9 | Media Manager Service error encountered. |
Check the STORE listing for the media manager error message.
Look up the message in Appendix A of the Magneto-Optical Media
Manager User's Guide and follow the suggested action. |
A complete listing of all possible STORE and RESTORE errors,
along with the probable cause and recommended action can be found in the
MPE/iX Error Messages Manual Volumes I, II, and III.
|