HP 3000 Manuals HP 3000 Manuals
#RJCONTINUE Procedural Interface
The #RJCONTINUE command identifies a user procedure to be executed when
RJE detects an error. The purpose of this procedure is to evaluate error
conditions as they occur and to determine what action may be taken in the
condition as it is described.
RJE expects the user-written #RJCONTINUE procedure to conform to the
formal procedure specification indicated in SPL.
PROCEDURE procedurename
(filenum,errors,comimage,newfname,action);
INTEGER filenum,action;
INTEGER ARRAY errors;
BYTE ARRAY comimage,newfname;
Within RJE the parameters are declared as follows:
INTEGER filenum, action;
INTEGER ARRAY errors (0:2);
BYTE ARRAY comimage (0:255);
BYTE ARRAY newfname (0:35);
RJE will pass the following parameters to the user-written procedure:
filenum is the MPE file number of the current command file.
errors is a three field array denoting the event that took place. The
values in this array are described in table E-1.
comimage is a copy of the RJE subsystem command image that was executing
when the error took place.
The user-written procedure will return the following parameters:
newfname, if the action parameter has been set to 2 by the user-written
procedure, is the name of a command file. The command file name must be
stored beginning in newfname(0) and followed by a blank character.
action is a variable which RJE expects to be set to one of these values:
1 = Retry the failed operation.
2 = Branch to a new command file.
3 = Go to the next command in this command file.
4 = Exit this command file.
CAUTION Certain error conditions may occur when an ACTION = 1, to retry
the failed operation, takes place in the absence of any commands
to retry. These include:
**** COMMAND FILE ERROR x,yy
**** INPUT FILE ERROR 1,yy
**** COMMAND ERROR 0 No prompt character
**** COMMAND ERROR 1 Unable to open command file
The user-written procedure must insure against infinite error
loops.
For further information on interpreting messages, refer to
Appendix A, "Interpreting Messages."
Table E-1. Errors Definition
----------------------------------------------------------------------------------------------
| | | |
| errors(0) | errors(1) | errors(2) |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| 0 = File System | 0 = List File | MPE File System Error |
| | 1 = Punch File | Number |
| | 2 = Out File | |
| | 3 = Command File | |
| | 4 = In File | |
| | 5 = Source File | |
| | 6 = Message File | |
| | 7 = Statistic File | |
| | | |
| 1 = CS | 0 = COPEN Intrinsic | CS Error Number |
| | 1 = CREAD Intrinsic | (0:8) = Recoverable |
| | 2 = CWRITE Intrinsic | (8:8) = Irrecoverable |
| | | |
| 2 = Line Error | 0 = Line not specified | |
| | 1 = Unable to open any line based | |
| | onDEV or NODE parameter | |
| | 2 = Specified node not in network | |
| | database | |
| | 3 = Database access problem | |
| | 4 = Network database intrinsic | |
| | error | |
| | 5 = Unable to map DEV or NODE into | |
| | network database | |
| | | |
| 3 = RIN Error | 0 = Invalid RIN value | -1, Not used |
| | | |
| 4 = Procedure | 1 = Invalid Procedure | -1, Not used |
| | Identification | |
| | | |
| 5= Command Error | 0 = Invalid Command | -1, Not used |
| | 1 = Invalid Command Length | |
| | 2 = Invalid Number of Parameters | |
| | | |
| 6 = Routing | 0 = Routed list output data set | -1, Not used |
| | received when not expected | |
| | 1 = Routed punch output data set | |
| | received when not expected | |
| | | |
| 7 = Syntax Error | 0 = Invalid keyword | Byte position of the |
| | 1 = Duplicate keyword | command string error |
| | 2 = Invalid construct | |
| | 3 = Invalid parameter | |
| | 4 = Invalid numeric parameter | |
| | 5 = Required parameter | |
| | | |
| | Example of errors parameter: | |
| | | |
| | errors(0)=0 File System error | |
| | errors(1)=1 Punch file | |
| | errors(2)=52 Non-existent | |
| | permanent file | |
| | | |
----------------------------------------------------------------------------------------------