HP 3000 Manuals

Run-Time Messages [ HP COBOL II/XL Migration Guide ] MPE/iX 5.0 Documentation


HP COBOL II/XL Migration Guide

Run-Time Messages 

Even if your program compiles and links with no errors, you may encounter
one of the following error messages when you try to run the program.

68       MESSAGE           **** Data memory protection trap (TRAPS 68)

         CAUSE             A misaligned parameter was passed to a subprogram that
                           expects a parameter that is aligned on a 32-bit (16-bit)
                           boundary.

         ACTION            Relink with the PARMCHECK value set to 3 (the default).  An
                           error message should appear for each call that passes a
                           misaligned parameter.  See the "Link Editor Message"
                           (earlier in this chapter) change calls to subprograms that
                           have misaligned parameters.

---------------------------------------------------------------------------------------

57       MESSAGE           **** Instruction memory protection (TRAPS 57)
         CAUSE             Issuing an illegal GO TO statement or exiting at a common
                           point from multiple PERFORM statements caused this error.  A
                           GO TO statement is illegal if it is used to leave a
                           paragraph that was PERFORMed without returning to that
                           paragraph.

         ACTION            Use the $CONTROL BOUNDS option when compiling the program to
                           detect this error.

---------------------------------------------------------------------------------------

512      MESSAGE           UNRESOLVED EXTERNALS: <external name> (LDRERR 512)

         CAUSE
                           a.  CALLing COBOLLOCK or COBOLUNLOCK; or

                           b.  CALLing a subprogram with a name that does not match the
                               subprogram's name because embedded hyphens are no longer
                               removed, the names are downshifted, or because COBOL
                               II/XL recognizes the first 30 characters of external
                               names; or

                           c.  CALLing an intrinsic without using the keyword
                               INTRINSIC.

         ACTION
                           a.  Change COBOLLOCK and COBOLUNLOCK calls to EXCLUSIVE and
                               UN-EXCLUSIVE statements, respectively.

                           b.  Change the main program or the subprogram names to
                               match.

                           c.  Change the call to an intrinsic to explicitly use the
                               keyword INTRINSIC or use $CONTROL CALLINTRINSIC.

---------------------------------------------------------------------------------------



MPE/iX 5.0 Documentation