Browse Prior Art Database

Creating And Maintaining Extended Prep SQL Modules

IP.com Disclosure Number: IPCOM000102502D
Original Publication Date: 1990-Nov-01
Included in the Prior Art Database: 2005-Mar-17
Document File: 2 page(s) / 64K

Publishing Venue

IBM

Related People

Talley, TM: AUTHOR

Abstract

The speed and efficiency of "extended prep" SQL modules make their use very attractive for database RXSQL applications. Unfortunately, retaining the source for such commands and updating the modules as a result of maintenance can prove inconvenient. A facility was needed such that the source for extended prep commands could be saved with the application exec and an access module could easily be created or recreated.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 78% of the total text.

Creating And Maintaining Extended Prep SQL Modules

       The speed and efficiency of "extended prep" SQL modules
make their use very attractive for database RXSQL applications.
Unfortunately, retaining the source for such commands and updating
the modules as a result of maintenance can prove inconvenient.  A
facility was needed such that the source for extended prep commands
could be saved with the application exec and an access module could
easily be created or recreated.

      PREPPY is an exec which searches REXX execs for a block of SQL
source commands as comments, then creates an SQL access module based
on these comments.

      PREPPY is invoked with an exec name and, optionally, a SQL
connection id and password.   If only the name of the exec is
provided, PREPPY first searches for "name ESOURCE" (to allow for
compiled REXX execs), then "name EXEC".  The exec source is searched
for the "SQL Extended Prep Commands:" (the string is configurable),
then extracts each SQL command up to the next comment block delimiter
(here, the string "******").  SQL commands may span multiple lines.
Next, PREPPY connects to the SQL id, if specified.  The SQL access
module is the same name as the REXX exec and PREPPY first DROPS the
access  module, then preps each SQL command in the order specified on
the numbers preceding each command.  If errors occur, PREPPY prompts
the user to determine whether to continue prepping commands.  If all
commands are successfully pr...