Re: Logicals Over Group Files

[CRPence <CRPbottle@xxxxxxxxx>]

On 3/3/11 8:02 AM, Jerry C. Adams wrote:
> 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.
>
> <<SNIP>>

  As externally described single member group files the SQL CREATE 
INDEX could be a reasonable replacement for a CRTLF:
   create index "A.IVMASTIX" on "A.IVMAST" (fldname)

  Other options do exist, but I would not expect any would be any 
easier than using SQL CREATE INDEX or the multiple source member 
approach already in use.  Other options include one model file for each 
group file then CRTDUPOBJ at run-time instead of creating the LF from 
source, or one model logical file combined with RNMOBJ of the model 
physical group file before CRTDUPOBJ, or allocating and updating one 
specific source member before each CRTLF.

Regards, Chuck