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-40
Building SQL/MX COBOL Applications to Run in the
Guardian Environment
Building SQL/MX COBOL Applications to Run
in the Guardian Environment
To build SQL/MX COBOL applications that run in the Guardian environment, choose
one of these approaches, depending on your preferred development environment:
•
Building SQL/MX Guardian Applications in the Guardian Environment on
page 16-40
•
Building SQL/MX Guardian Applications in the OSS Environment on page 16-42
Building SQL/MX Guardian Applications in the Guardian
Environment
•
Using the OSS Pass-Through Command at a TACL Prompt on page 16-40
•
OSS-to-Guardian File Naming on page 16-40
•
Steps for Building an SQL/MX Application in the Guardian Environment on
page 16-41
•
Using a TACL Macro to Build an SQL/MX Guardian Application on page 16-42
Using the OSS Pass-Through Command at a TACL Prompt
Most commands for building an SQL/MX Guardian application can be issued directly at
a TACL prompt. However, the SQL/MX preprocessor, mxsqlco, and the SQL/MX
compiler, mxcmp, run as OSS processes and must be started in the OSS environment.
In the Guardian environment, you can work around this limitation by using an OSS
pass-through command at a TACL prompt.
To run the SQL/MX preprocessor and the SQL/MX compiler in the Guardian
environment, use the OSS pass-through command by specifying the osh -c option at
a TACL prompt. The osh -c option executes one command line at a time in the OSS
environment. When you use the osh -c command, remember to enclose the entire
command string after osh -c in double quotes.
OSS-to-Guardian File Naming
When you issue OSS commands from a TACL prompt to preprocess and SQL compile
an application, the Guardian file names change automatically. In the Guardian
environment, the period is automatically dropped from the file name.
Note. When using OSS pass-through commands in the Guardian environment, be aware of
the effect of #INFORMAT TACL on those commands. If #INFORMAT TACL is in effect for your
session, you must put a tilde (~) before the pipe (|) symbol. Otherwise, the pipe symbol cannot
reach the shell for execution because it has a programming function within TACL.