Re: Debugging in System 36 environment

[CRPence <CRPbottle@xxxxxxxxx>]

  Could probably verify that the specific program named is actually 
being called within that same job, by using either the TRCJOB *ON 
then TRCJOB *OFF to generate a call trace, or use both the STRDBG & 
ADDBKP '/1' requests.  Unlike STRISDB [which supports only certain 
program types], the STRDBG with ADDBKP '/1' should be capable of 
stopping [in] any OPM program type.

Regards, Chuck

Sharon wrote:
> Good afternoon all, I am trying to step through an old QS36SRC
> print program.
>
> It is called from a CL.  I set up the debug of the program I want
> with an STRISDB command, upprod *YES, invoke *NO.  I get into the
> source and set break points.  I then call the CL program.  I get
> an input screen for what I want to print, and never get into the
> program to step through it.
>
> Thinking the source attributes may be off, I copied it and
> renamed it and recompiled it with *SOURCE.  I copied the CL to
> call my new program.  When I attempt Debug again I still cannot
> get into this program.
>
> I have gotten the environment set up to what I think I need with
> the STRS36 command to get me into the S36 environment, after
> hitting several snags on that.
>
> I have looked in the archives and can't see anything that would
> be helpful.
>
> I know it's an oldie but a goodie, but any help would be
> appreciated.  Thanks in advance.