SQL/MX Programming Manual for C and COBOL (G06.24+, H06.03+)

COBOL Program Compilation
HP NonStop SQL/MX Programming Manual for C and COBOL—523627-004
16-44
Running the SQL/MX Program File
Running the SQL/MX Program File
An SQL/MX program can run in the OSS or in the Guardian environment. You can use
the GTACL command to start a Guardian program from OSS. You can use the osh
command to start an OSS program from a Guardian TACL session.
•
From the OSS environment, enter the program file name at the OSS shell prompt.
You can also use the OSS run command to run the program file by using specific
Guardian attributes (for example, a CPU or priority for the process).
•
From the Guardian environment, use the TACL osh command to run the program.
For more information, see Building SQL/MX COBOL Applications to Run in the
Guardian Environment on page 16-40.
For more information on the run or osh command, see the Open System Services
Shell and Utilities Reference Manual or the OSS reference pages.
Understanding and Avoiding Common Run-Time Errors
The details of how a COBOL executable is linked with its module or modules are
handled by the system and take place in the background. However, by understanding
this process and why certain run-time errors occur, you can avoid some common
SQL/MX application development issues.
Module File Errors
Error 8809 Unable to open module file
This error occurs if module files are deleted from the application’s base directory or
from the /usr/tandem/sqlmx/USERMODULES directory and then the associated
application is executed.
This error can also occur if the named module file exists but is not readable. Ask the
module file’s owner to change the permission attributes so that an application can read
the module file.
Error 8808 Module file name contains corrupted or invalid data
This error occurs when the timestamp encoded in the module file does not match the
timestamp passed from the application to the CLI. These timestamps are initially
generated by the preprocessor and are used to ensure that the version of the
application is synchronized with the version of the module file. This error can occur if
you run the preprocessor on your embedded SQL, compile the annotated COBOL
output file, but fail to SQL compile the module definition file that the preprocessor
generates. If the SQL/MX compiler has previously compiled a different instance of the
module definition file, a module exists whose name corresponds to the application
module but has a mismatched timestamp.