The Ultimedia Application/IBM_UCD_101.ISO/os2se20/disk_12/rexx/OS2_SYSTEM_REXH.MSG

OS/2 Message File | 1992-07-15 | 18.0 KB | 299 lines

MKMSGF
537/8
;!;$;';*;-;0;3;6;9;<;?;B;E;H;K;N;Q;T;W;Z;];`;a=
>1@bA
BhC;D!E
HEXPLANATION: There are currently too many files open for this
             session.
ACTION: Close files which are open but no longer in use.
HEXPLANATION: An attempt was made to access a program which was
             either non-existent or locked by another process.
ACTION: Verify file's existence and make sure no other process
        has it locked.
HEXPLANATION: The system interrupted execution of a program
             because of some error, or by user request.
ACTION: Trap interrupts via CALL ON HALT or SIGNAL ON HALT.
HEXPLANATION: While attempting to execute a program, the language
             processor was unable to obtain the resources it
             needed to continue execution.
HEXPLANATION: A comment or literal string was started but never finished.
             This may be detected at the end of the program (or the end
             of data in an INTERPRET instruction) for comments, or at
             the end of a line for strings.
HEXPLANATION: Within a SELECT construct, at least one WHEN construct
             (and possibly an OTHERWISE clause) is expected.
ACTION: Look for any instruction other than WHEN (or no WHEN construct
        before the OTHERWISE) in the SELECT construct.
HEXPLANATION: A THEN or an ELSE has been found that does not
             match a corresponding IF (or WHEN) clause.
ACTION: Look for a missing END or DO...END in the THEN part
        of a complex IF...THEN...ELSE construction.
HEXPLANATION: A WHEN or an OTHERWISE has been found outside of a SELECT
             construct.  It may have been enclosed unintentionally
             in a DO...END construct by leaving off an END
             instruction, or an attempt may have been made to
             branch to it with a SIGNAL instruction.
HEXPLANATION: There are more END's in the program than DO's and SELECT's,
             or the END's are wrongly placed so they do not match
             the DO's and SELECT's.  This error will also be
             generated if an END immediately follows a THEN or an
             ELSE.
ACTION: Try using "TRACE Scan" to show the structure of the program
        and hence make it more obvious where the error is.  Putting
        the name of the control variable on END's that close
        repetitive loops can also help locate this kind of error.
        A common mistake that causes this error is attempting to
        jump into the middle of a loop using the SIGNAL instruction.
        Since the previous DO will not have been executed, the END
        is unexpected.  Also, since SIGNAL deactivates any current
        loops, it may not be used to jump from one place inside a
        loop to another.
HEXPLANATION: An interpreter limit of levels of nesting of control
             structures (DO...END, IF...THEN...ELSE, etc.) has
             been exceeded.  This could be due to a looping
             INTERPRET instruction, which could loop forever.
             Similarly, a recursive subroutine or internal
             function that does not terminate correctly could
             loop forever.
HEXPLANATION: The length of the internal or external representation of
             a clause has exceeded the interpreter's limit.
HEXPLANATION: The program includes a character outside of a literal
             (quoted) string that is not a blank or one of the valid
             alphanumeric/special characters.
HEXPLANATION: On reaching the end of the program (or end of the string
             in an INTERPRET instruction), it has been detected that
             there is a DO or SELECT without a matching END, or an IF
             that is not followed by a THEN clause to execute.
ACTION: It may be helpful to use "TRACE Scan" to show the structure
        of the program and hence make it more obvious where the
        missing END should be.  Putting the name of the control
        variable on END's that close repetitive loops can also
        help locate this kind of error.
HEXPLANATION: Hexadecimal strings may not have leading or trailing blanks,
             and may only have embedded blanks at byte boundaries.  Only
             the digits 0-9 and the letters a-f and A-F are allowed.
             Similarly, binary strings may only have blanks added at the
             boundaries of groups of four binary digits, and only the
             digits 0 and 1 are allowed.
             This error may also be caused by following a literal string by
             the one-character symbol "X" (for example the name of the
             variable X) when the string is not intended to be taken as a
             hexadecimal specification, or by the symbol "B" when the
             string is not intended to be taken as a binary specification.
ACTION: Use the explicit concatenation operator, "||", in situations where
        the "X" or "B" is intended to represent a variable.
HEXPLANATION: A SIGNAL instruction has been executed (or an event for
             which a trap was set has occurred), and the label specified
             cannot be found in the program.
HEXPLANATION: A PROCEDURE instruction was encountered which was not
             the first instruction executed after a CALL or function
             invocation.
ACTION: Check for the possibility of "dropping through" into an internal
        routine rather than invoking it properly.
HEXPLANATION: All IF clauses and WHEN clauses in REXX must be followed
             by a THEN clause.  Some other clause was found when a
             THEN was expected.
HEXPLANATION: Following either the keyword CALL or the sequence
             SIGNAL ON or SIGNAL OFF, a literal string or a
             symbol was expected but neither was found.
HEXPLANATION: In the clauses CALL ON, END, ITERATE, LEAVE, NUMERIC,
             PARSE, PROCEDURE, and SIGNAL ON, a symbol can be
             expected.  Either it was not present when required,
             or some other token was found.  Alternatively,
             DROP, and the EXPOSE option of PROCEDURE, expect
             a list of symbols.  Some other token was found.
HEXPLANATION: A clause such as SELECT or NOP is followed by some
             token other than a comment.
HEXPLANATION: This error results if a literal string contains character
             codes that are not valid in the interpreter.  This might
             be because some characters are "impossible", or because
             the character set is extended in some way and certain
             character combinations are not allowed.
HEXPLANATION: This error results if a data string (result of an
             expression, etc.) contains character codes that are
             not valid in the interpreter. This might be because
             some characters are "impossible", or because the
             character set is extended in some way and certain
             character combinations are not allowed.
HEXPLANATION: The setting specified on a TRACE instruction starts with
             a character that does not match one of the valid TRACE
             settings (i.e., A, C, E, F, I, L, N, O, R, or S).  This
             error is also raised if an attempt is made to request
             "TRACE Scan" when inside any kind of control construct.
HEXPLANATION: An unexpected token has been found in the position in an
             instruction where a particular sub-keyword was expected.
             For example, in a NUMERIC instruction, the second token
             must be DIGITS, FUZZ, or FORM, and anything else is an
             error.
HEXPLANATION: One of the following did not evaluate to a whole number:
                - the positional patterns in parsing templates
                - the power value (right-hand operand) of the power operator
                - the values in a DO instruction after the FOR modifier
                - the values given for DIGITS or FUZZ in the NUMERIC
                  instruction
                - the number used in the TRACE setting
             This error is also raised if the value is not permitted (for
             example, a negative repetition count in a DO instruction), or
             when the division performed during an integer divide or
             remainder operation does not result in a whole number.
HEXPLANATION: Some syntax error has been found in the DO instruction.
             This might be by using BY, TO, or FOR twice, or using BY,
             TO, or FOR when there is no control variable specified, etc.
HEXPLANATION: A LEAVE or ITERATE instruction was encountered in an invalid
             position.  Either no loop is active, or the name specified
             on the instruction does not match the control variable of
             any active loop.  Note that since internal routines and
             the INTERPRET instruction protect DO loops, they become
             inactive, and therefore a LEAVE in a subroutine cannot
             affect a DO loop in the calling routine.  A common cause
             for this error message is attempting to use the SIGNAL
             instruction to transfer control within or into a loop.
             Since SIGNAL terminates all active loops, an ITERATE or
             LEAVE would then be in error.
HEXPLANATION: The environment name specified by the ADDRESS instruction
             is longer than permitted for the system under which the
             interpreter is executing.
HEXPLANATION: A variable name or a label name (or the length of
             a literal string) has exceeded the interpreter's
             limit.
HEXPLANATION: A value may not be assigned to a variable whose name
             starts with a numeric digit or a period (since if it
             were permitted one could re-define numeric constants).
HEXPLANATION: The result of an expression in an instruction was
             found to be invalid in the particular context in
             which it was used.
ACTION: Check for an illegal FUZZ or DIGITS value in a NUMERIC
        instruction (FUZZ may not become larger than DIGITS).
HEXPLANATION: The expression in an IF, WHEN, DO WHILE, or DO UNTIL
             phrase must result in a '0' or a '1', as must any
             term operated on by a logical operator.
HEXPLANATION: This is due to a grammatical error in an expression,
             such as ending it with an operator, or having two
             operators adjacent with nothing in between.  It may
             also be due to an expression that is missing when
             one is required.
ACTION: Check for special characters (such as operators) in an
        intended character expression which are not enclosed
        in quotes.
HEXPLANATION: This is due to not pairing parentheses correctly
             within an expression.  There are more left
             parentheses than right parentheses.
HEXPLANATION: Either a comma has been found outside a function
             invocation, or there are too many right parentheses
             in an expression.
HEXPLANATION: Within a parsing template, a special character that
             is not allowed (for example, "%") has been found,
             or the syntax of a variable pattern is incorrect
             (i.e., no symbol was found after a left parenthesis).
             This error may also be raised if the WITH sub-keyword
             is omitted in a PARSE VALUE instruction.
HEXPLANATION: The expression is too complex to be evaluated by the
             language processor.
ACTION: Check for too many nested parentheses, functions, etc.
HEXPLANATION: The specified built-in or external routine does exist,
             but it has been used incorrectly.  Either invalid
             arguments were passed to the routine, or the program
             invoked was not compatible with the language
             processor, or more than an implementation-limited
             number of arguments were passed to the routine.
HEXPLANATION: One of the terms involved in an arithmetic operation
             is not a valid number, or its exponent exceeds the
             implementation limit (often 9 digits).
HEXPLANATION: The result of an arithmetic operation requires an
             exponent that is outside the range supported by the
             interpreter.  This can happen during evaluation of
             an expression (commonly an attempt to divide a
             number by 0), or possibly during the stepping of a
             DO loop control variable.
HEXPLANATION: A function has been invoked within an expression (or
             a subroutine has been invoked by a CALL) but it
             cannot be found.  No label with the specified name
             exists in the program, it is not the name of a
             built-in function, and the language processor has
             been unable to locate it externally.
ACTION: Check for:  - a mis-typed label or name
                    - a symbol or literal string adjacent to a '('
                      when it should have been separated by a
                      blank or some other operator (this would
                      be understood as a function invocation)
HEXPLANATION: An external function has been invoked within an
             expression, but even though it appeared to end
             without error, it did not return data for use
             within the expression.
HEXPLANATION: The program has been called as a function, but an
             attempt is being made (by RETURN;) to return
             without passing back any data.  Similarly, if an
             internal routine is called as a function then
             the RETURN instruction that ends it must specify
             an expression.
HEXPLANATION: Within a DROP, PARSE or PROCEDURE instruction, the syntax
             of a variable reference is incorrect.  This may be due to a
             missing parenthesis or an incorrectly coded variable within
             the parentheses.
HEXPLANATION: A label appeared as part of the instructions
             executed by an INTERPRET instruction.
          ACTION: Remove the label from the interpreted data.
HEXPLANATION: A system service used by the language processor
             (such as stream input or output, or manipulation
             of an external data queue) has failed to work
             correctly and hence normal execution cannot
             continue.
HEXPLANATION: Some kind of severe error has been detected within
             the language processor or execution process
             during internal self-consistency checks.
HEXPLANATION: RXSUBCOM accepts the following parameters:
To Register a subcommand environment
   RXSUBCOM REGISTER ENVIRONMENT_NAME DLL_NAME ENTRY_POINT
To Query a specific subcommand environment for existance
   RXSUBCOM QUERY [ENVIRONMENT_NAME [DLL_NAME]]
To Drop a subcommand environment handler
   RXSUBCOM DROP ENVIRONMENT_NAME [DLL_NAME]
To Load a subcommand environment from disk
   RXSUBCOM LOAD ENVIRONMENT_NAME [DLL_NAME]
ACTION: Check the RXSUBCOM parameters and retry the command.
HEXPLANATION: RXSUBCOM REGISTER requires all of the following parameters:
  RXSUBCOM REGISTER ENVIRONMENT_NAME DLL_NAME ENTRY_POINT
    ENVIRONMENT_NAME   is the name of the subcommand environment.
    DLL_NAME           is the Dynalink Module name.
    ENTRY_POINT        is the name of the function to be executed when called.
ACTION: Check the RXSUBCOM parameters and retry the command.
HEXPLANATION: RXSUBCOM DROP requires the environment name be specified.
   RXSUBCOM DROP ENVIRONMENT_NAME [DLL_NAME]
    ENVIRONMENT_NAME   is the name of the subcommand environment.
    DLL_NAME           is the Dynalink Module name (optional).
ACTION: Check the RXSUBCOM parameters and retry the command.
HRXSUBCOM LOAD requires the environment name be specified.
   RXSUBCOM LOAD ENVIRONMENT_NAME [DLL_NAME]
    ENVIRONMENT_NAME   is the name of the subcommand environment.
    DLL_NAME           is the Dynalink Module name (optional).
ACTION: Check the RXSUBCOM parameters and retry the command.
HEXPLANATION: The REXX queuing system is not initialized.
  The queuing system requires a housekeeping program to run.  This
  program usually runs under the Presentation Manager shell.  The
  program is not running.
ACTION: Report this message to your IBM service representative.
HEXPLANATION: The data supplied to the RXQUEUE command is too long.
  The RXQUEUE.EXE program accepts data records containing 0 - 65472
  bytes.  A record exceeded the allowable limits.
ACTION: Use shorter data records.
HEXPLANATION: The queuing system is out of memory.
  No more storage is available to store queued data.
ACTION: Delete some queues or remove queued data from the system.
        Then retry your request.
HEXPLANATION: The queue name contains an invalid character.
  Only the following characters may appear in queue names:
     'A' .. 'Z', '0' .. '9', '.', '!', '?', '_'
ACTION: Change the queue name and retry the command.
HEXPLANATION: An internal error occurred in RXQUEUE.
  RXQUEUE.EXE tried to access a queue with an incorrect access mode.
  Correct access modes are LIFO and FIFO.
ACTION: Report this message to your IBM service representative.
HEXPLANATION: The command attempted to access a nonexistent queue.
ACTION: Create the queue and try again, or use a queue that has been
        created.
HEXPLANATION: RXSUBCOM QUERY requires the environment name be specified.
   RXSUBCOM QUERY ENVIRONMENT_NAME [DLL_NAME]
    ENVIRONMENT_NAME   is the name of the subcommand environment.
    DLL_NAME           is the Dynalink Module name (optional).
ACTION: Check the RXSUBCOM parameters and retry the command.