Pathmaker Programming Guide

Modifying a Server Skeleton or Service Skeleton
Advanced Pathmaker Programming Topics
067868 Tandem Computers Incorporated 9–41
For example, you could add a global procedure to convert dates. Assume you have
stored the code for this global procedure in a file called $DATA.SALES.COPYLIB.
Assume that the section name for this procedure is ?SECTION CONVERT-DATE. To
add this global procedure to the server skeleton, add a copy statement at the
appropriate spot in the server skeleton, as shown in the following example:
T9154-WRT-$#Service-Short-Name$.
*
IF T9154-POET-HEADER
WRITE T9154-REP-$#Service-Short-Name$
ELSE
WRITE T9154-RPM-$#Service-Short-Name$
.
*
*
% end-iterate label-024 ! #Services
! BEGIN CHANGE JH
COPY CONVERT-DATE OF $DATA.SALES.COPYLIB. <-- COPY statement
for global
procedure
! END CHANGE JH
% iterate #Services thru lines until tag label-026
?HEADING "$#Service-Name$"
/
*************************************************************
* *
* *
* *
* S E R V I C E *
Modifying the COBOL
Server Skeleton for
NonStop SQL Applications
There are three ways that you can modify the COBOL server skeleton for a
NonStop SQL application:
Change the format of the default error message
Add to the list of Level 88 condition clauses
Change the logic of the SQL error handling portion of the skeleton
Changing the Format of the Default Message
The following excerpt shows the portion of the COBOL server skeleton that sets the
format of the default message, slightly reformatted for reproduction in this manual:
% if #Any-Service-Uses-SQL = "Y" use lines until
tag label-11
*
02 T9154-SQL-ERROR-MSG.
03 FILLER PIC X(08)
VALUE IS
"SQL err:".
03 T9154-SQL-SQLCODE PIC -----9
VALUE IS ZEROS.