Re: Application Diagram RDP 8.0

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Charles

So far as I know, the application diagram comes from the same thing as 
the outline. I believe that is a compile listing, basically. Something 
like that, anyhow. It doesn't do the extensive source analysis that 
Hawkeye and the like do. Hawkeye takes a lot of time to follow rabbit 
trails in source, which the RDP tools simply won't do. As you are aware, 
that's why DSPPGMREF isn't enough for a thorough cross-reference.

And the app diagram isn't being positioned as a cross-reference tool - 
seems a stretch to ask it to be one of those.

I'm with Joe, though, about using QCMDEXC to do a CALL - there are 
better ways, like prototyping with EXTPGM. But that's a different thread.

JMHO
Vern

On 4/11/2011 7:34 AM, Charles Wilt wrote:
> Joe,
>
> You might be surprised....
>
> IIRC, Hawkeye crossed referenced variable program calls...
>
> In my case, the variable was set via a string constant as opposed to
> being looked up in a DB table.  I could see hawkeye or similar
> products having issues with a DB lookup....then again they've gotten
> pretty smart..
>
> Charles
>
> On Sun, Apr 10, 2011 at 9:32 PM, Joe Pluta<joepluta@xxxxxxxxxxxxxxxxx>  wrote:
> > If you're creating a call in a QCMDEXC string, are you hardcoding the
> > program name?  If so, why are you using QCMDEXC?  I've coded QCMDEXC
> > strings but most of the time the program name comes from a variable, and
> > I don't expect any cross-reference tool to get those.
> >
> > Joe