Developer- or Site-supplied Stored Procedures

This topic provides information on stored procedures you may want to create. It also supplies some example code.

The Acu4GL for Sybase interface checks for these stored procedures when opening a file and will use them in certain circumstances, such as when A_SYB_NO_23_ON_START is set to “ No.”

These stored procedures are

tablename_insert (where tablename is the name of the table being accessed)
tablename_delete
tablename_read
tablename_update
tablename_startnnn (where nnn is the key number to start on)

Note:

The Acu4GL for Sybase product does not create these stored procedures or check their accuracy. Thus, it is possible to create stored procedures in such a way as to make the Acu4GL for Sybase product completely inoperable.

The Acu4GL product uses these stored procedures for performance reasons only.

Sample XFD

Sample code for developer-supplied stored procedures is based on the following example of an XFD:

 
XFD,03,FTEST2-FILE,FTESTDAT
# ftestdat.xfd - generated by ACUCOBOL-GT v4.2 Alpha 1 
   (8/22/99)
# Generated Sun Aug  22 07:54:28 1999
00031,00031,003
01,0,004,00000
01
FTEST2-KEY
01,1,004,00004
02
FTEST2-KEY1-SEG1
FTEST2-KEY1-SEG2
01,0,004,00008
01
FTEST2-ALTKEY2
000
0006,00006
00000,00004,16,00004,+00,000,000,FTEST2-KEY
00004,00002,16,00002,+00,000,000,FTEST2-KEY1-SEG1
00006,00002,16,00002,+00,000,000,FTEST2-KEY1-SEG2
00008,00004,16,00004,+00,000,000,FTEST2-ALTKEY2
00012,00009,00,00009,+00,000,000,FTEST2-NUMBER
00021,00010,16,00010,+00,000,000,FTEST2-INFO