Re: V5R2: Source now allowed in the IFS

["Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>]

Hello Rob,

You wrote:
<Quote>
Then I do a DSPPGM of ROB/AAXYZ, I see:
Oh crud, methinks they are missing something here!
Program  . . . . . . . :   AAXYZ         Library  . . . . . . . :   ROB
Module attributes:
  Module . . . . . . . . . . . . . . . . . . . . :   AAXYZ
    Library  . . . . . . . . . . . . . . . . . . :     QTEMP
  Source file  . . . . . . . . . . . . . . . . . :
    Library  . . . . . . . . . . . . . . . . . . :
  Source member  . . . . . . . . . . . . . . . . :
I also checked the API QBNLPGMI and there's nothing in there.  PMR is
opened.  They were wondering when DSPPGM, and the API, will catch up.
I was told that C had the ability to compile from IFS for some time
now.
</Quote>

I see that Mark beat me to the 'obvious' comment regarding losing the
source relationship.  What you see above is normal.  The C Programmer's
Guide states:

"   If you specify SRCSTMF, the *MODULE object contains no source file
    attribute information.    "

I suspect your PMR will be answered as Working as Designed/Documented
or Fixed in a Future Release.  I see no reason to expect different
behaviour from other compilers that support stream file source.  That
does not mean that IBM cannot alter the OIR in a future release to add
stream file source information in a manner similar to the way they
track where-used information -- or even store it directly in the module
object (which would seem a more senisble place for it).

Adding stream file support to the compilers is, I believe, part of the
reason IBM withdrew ADM.  They probably found it was too hard to
incorporate stream file support into ADM's build algorithm -- which is
a great pity because I really like ADM.  (I doubt I would ever
willingly hold AS/400 source in stream files but I would like the
ability to incorporate stream file data in an ADM build -- oh dear, how
sad, never mind!)

Losing the source information makes it very hard to correlate object
and source and no PC or Unix style CMS will handle this requirement.
The best they can do is some sort of version control system where the
compiled object is held/imported/commited at the same release level as
the source and the assumption is that the source and object at a given
level match.  Here is another example of dumbing down the AS/400 to
match less evolved platforms -- just because they don't have support
for matching source and object they don't think it useful so we lose
(again!).

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------