Re: Retrieve Program References

[CRPence <CRPbottle@xxxxxxxxx>]

  A damned poor database it would be, if you could not write to an 
opened database file; i.e. write to a file already opened for read 
or even update access.  So (probably) one can DSPPGMREF to the file 
that is already opened.  I am actually confused why anyone would 
even suspect that DSPPGMREF OUTFILE(outputdbf) OUTMBR(named *ADD) 
would not be able to add records to the named member of the 
outputdbf if already opened.  Anyhow, there should be no difficulty 
at accomplishing the described.

  Also as Carel already noted, it would be those API which use a 
user space that are more likely to complicate for inability to just 
add to the end like with a database file member.

Regards, Chuck

Dennis Lovelady wrote:
> > > I was shocked to see that, at V5R3 there is no Retrieve 
> > > Program References API that I can find. I do know about 
> > > DSPPGMREF to an output file, and all that, but this surprises
> > >  me.
> >
> > Dennis, I didn't know about this API. What advantages are there
> >  in using it over DSPPGMREF?
>
> I've grown accustomed to the List ... APIs, I guess. This case 
> shows an API advantage, I think. Remember I want to find all the 
> things impacted by altering this program. Since a program can 
> reference other programs I will need DSPPGMREF output from those 
> programs as well. So here's a vision:
>
> Display Program References to an output file. Now in RPG open 
> that output file, begin reading. Ack, my first record refers to 
> PROGRAMB, so I need its references. I (probably) cannot DSPPGMREF
>  to the file I've opened, so I'll need to go to an alternate. OK,
> can handle that. But when I'm processing the alternate file, I
> see that there's a reference to PROGRAMC. Et cetera.
>
> With recursion and APIs, this would all be SOP. But it gets 
> complex with DSPPGMREF.