Re: Application Architecture/Design Question

I'm not sure what dynamic SQL gets me here -- the calls to any particular file are always going to be the same. But I asked for ideas, and I'll think about it. Thanks!


Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> writes:

Sounds like a case for dynamic SQL to me. No file definition at all. Each routine (Rtn37) builds the sql it needs to get to the file. All keyfield sizes, etc are abstracted away into the dynamic select or insert.

Still, I'd make it modular. Compile each Rtn as it's own NOMAIN module. Then maintenance on one routine requires only re-compiling that module and rebinding the service program. Yes, I'd make PgmB a service program. Export all the routine names.

All those routines will need protypes in PgmA. Great use for /COPY. Use the same prototype within the module file in each routine that will be in PgmB in the source for PgmA.

I think I'd look for a way to gather some of those files into a smaller set of files where records have similar characteristics. You can sparsely load columns in the file if needed (null when a particular type of record doesn't have a 5.3 keyfield for
example). Let the database do a lot of the work for you. Include a "type" column. So your selects look like:

SELECT templateField from FileA where type='Rtn37' and decimalColumn = 5.7 and stringColumn='Some Value'
And
SELECT templateField from FileA where type='Rtn38' and integerColumn = 22 and stringColumn='Hello'

Receive the SQL results into a data area you can differentiate for the result sets from the query. Each module has its own data area. Keep the size of the PASA down by ALLOC'ing the memory for the data area before the call and deleting it after.

Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA 01376
413-676-3144
Internal: x 444
mnaughton@xxxxxxxxxxxx
****************************************
NOTICE: This e-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that any use is
strictly prohibited. If you have received this e-mail in error, please notify us immediately by replying to it and then delete it from your computer.