actually the backtrace is needed in order to locate the 1 program in
2500 which is screwing up a database update; each of the other 2499 does
it fine.  

the solution will likely be to sed a line into each program creating the
WS item PROG-ID with the proper value, make a couple of copylib changes
and recompile everything.

again, thanks all!

Tracy Pierce
 

> -----Original Message-----
> From: HP-3000 Systems Discussion 
> [mailto:[log in to unmask]] On Behalf Of Lars Appel
> Sent: Monday, January 09, 2006 2:45 PM
> To: [log in to unmask]
> Subject: Re: PROCINFO (for all Cobol gurus out there...)
> 
> Tracy,
> 
> I don't recall the exact beginning of this thread,
> but if the "backtrace" is mainly needed to display
> some diagnostic messages, a call to the intrinsic
> "stackdump" might provide some useful info already.
> 
> It might be possible to not send this to $STDLIST,
> but to a file and the parse programmatically... but
> this depends on the individual neccesities.
> 
> Lars.
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *