 |
» |
|
|
|
Two UDCs for invoking the PASCAL preprocessor are provided with
ALLBASE/SQL in the HPSQLUDC.PUB.SYS file: PPAS, illustrated in Figure 2-15, invokes the preprocessor in
full preprocessing mode. You specify the source file name, a
DBEnvironment name, and a name for SQLMSG (if you do not want
preprocessor messages to go to $STDLIST). See Figure 2-16.
:PPAS SourceFileName,DBEnvironment
|
The PPAS UDC uses the following preprocessor parameters: ModuleName is the name of the source file.
OwnerName is the logon User@Account.
PRESERVE and DROP are in effect.
PPPAS, illustrated in Figure 2-16, invokes the preprocessor in
full preprocessing mode, then invokes the PASCAL compiler if
preprocessing is successful, and then the linker if compilation is
successful. To use this UDC, you specify the source file name, a
DBEnvironment name, and an executable file name. You can
specify a name for SQLMSG if you do not want preprocessor
messages to go to $STDLIST:
:PPPAS SourceFileName, DBEnvironmentName, ExecutableFileName
|
This UDC uses the following preprocessor INFO string parameters: ModuleName is the source file name.
OwnerName is the logon User@Account.
PRESERVE and DROP are in effect.
| | | |  | NOTE:
If you make your own version of the UDCs, do not modify the
record attributes for any of the preprocessor output files.
Only modify the file limit (disc=FileLimit) if required.
Because the UDCs purge the preprocessor message file, if
messages are sent to $STDLIST, an error message appears when you
use the UDCs, but preprocessing continues.
| | | | |
The example in Figure 2-17 illustrates the use of PPPAS on an
SQLIN that could be successfully preprocessed, but failed to
compile because a Pascal error exists in the file. |
Printable version
