Re: Subfiles in COBOL

["R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>]

uh, you mean trip, right?  <VBG>

(gee, does the Dead reference mean anything about COBOL?!?!? ;-)

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - iSeries Administrator
 -- IBM Certified Specialist - RPG IV Developer

"There is a crack in everything,
  that's how the light gets in.
    - Leonard Cohen

----- Original Message -----
From: "Joe Pluta" <joepluta@PlutaBrothers.com>
To: <cobol400-l@midrange.com>
Sent: Saturday, July 27, 2002 1:15 PM
Subject: RE: Subfiles in COBOL


> > From: R. Bruce Hoffman, Jr.
> >
> > while it is not required, I have found that it is much easier to deal
with
> > one set of indicators rather than multiple images of those
> > indicators, each
> > in their own record space.
> >
> > That way I can map the indicators to meaningful names.
> >
> > For those reasons, I have always advocated using the SI in COBOL.
>
> And this is the issue I'm finding with COBOL.  It seems to this newbie
that
> COBOL affords much more flexibility in how one works with the workstation,
> some of which is not particularly intuitive (at least to me).  Because of
> that, the source modification portion of my tool is going to have to be a
> bit more intelligent to handle COBOL.
>
> My concern is that there are so many possibilities that it may not make
> sense to support them all, but then how do I triage which ones are
"common"
> and which aren't?  In order to decide that, I'm going to have to learn
about
> the different ways that things can be done.
>
> I can tell already it's going to be a long, strange road...
>
> Joe
>
> _______________________________________________
> This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
list
> To post a message email: COBOL400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l
> or email: COBOL400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/cobol400-l.
>