Re: Reduce large amount of logicals in SUBFL pgm, take in another direction

Sharon wrote:

There are 12 different fields a user can fill in to search for the info
they
want. Plus there are fields they can check off for other criteria. Total
about 25 different fields on the screen.

Currently, there are about 80 logicals that are used for all the different
combinations of fields to search on. The first SUBR of the pgm does
various
validations against all the possible fields, then depending on that result
does a SETLL for the appropriate logical. Then a second SUBR checks the
fields again and depending on that does a READ, READE or READP against the
logical that was staged.

They want to select the data the first time through to a type of work
file,
then as more information is filled in by the user, query or read against
that work file, drilling down further for each field that is populated by
the user. They want to reduce CPU and the amount of logicals.

My thoughts:

1) Reduce the number of logicals by making logicals with
"wider key paths" (more key fields).

2) Eliminate select/omit logicals, replacing the most critical
with appropriate key paths

3) Load the work file with SQL