Logicals Over Group Files

["Jerry C. Adams" <midrange@xxxxxxxx>]

I have an old S/36 application here that I am slowly trying to convert.
I.e., the files are not externally described, except for the few I have
converted so far.  All of the files (physical and logical) are contained in
the same library (QS36F).

 

The application uses the old S/36 group file designation to differentiate
between companies, such as A.IVMAST and D.IVMAST.  I replace the BLDFILE
commands with a CRTwhatever command to build the physical, and the group
file is not an issue at that time.

 

However, when I replace the BLDINDEX command with an equivalent CRTsomelf
command, the group file is a problem because the DDS for the LF wants to
know the name of the parent, such as:

 

R IVMASTR                   PFILE(A.IVMAST)

 

So far I have wound up creating multiple DDS definitions; one for each
possible parent.  In the CRTsomelf program I know which group I'm operating
on so it's relatively easy to ascertain which DDS member to use.

 

I was just wondering if there isn't an easier way to do this.  

 

Of course, it would have been a lot easier (and more logical) if the s.o.b.
that designed the system had actually known how to create multi-company
applications, but that's water under the bridge.

 

Jerry C. Adams

IBM i Programmer/Analyst

Being with a woman all night never hurt no professional baseball player.
It's staying up all night looking for a woman that does him in. -Casey
Stengel

--

A&K Wholesale

Murfreesboro, TN

615-867-5070