COBOL has such a facility, although I have been unable to find anyone at
my company who has ever used it, and I have just started to. Also, this
feature has been identified as obsolesced, but HP has no definite plans
to obsolesce it. You can add a USE FOR DEBUGGING section to
DECLARATIVES, and define both identifiers and paragraphs that you would
like tracked, and normal code for what you want to happen in those.
There is as well a DEBUG-ITEM special register that contains the line
number, the paragraph being debugged, and whether that item is PERFORMed
or FALL THROUGH, among other things. And this is turned on by setting
SW15, as in RUN PROGRAM;PARM=%000001; otherwise, the default is off, and
you just have slightly larger code than you might otherwise. The manual
is less than detailed about this; I had to resort to a very old college
textbook to find just some of what I needed to use this (so feel free to
send me any questions you might have).

Another alternative is use SOURCE COMPUTER. HP 3000 WITH DEBUGGING MODE,
and debugging lines identified with D in column 7. When compile without
the WITH DEBUGGING MODE clause, these are treated as comments, but this
requires recompiling the code when you want it enabled. However, since
the problems one might use this for are likely to change with time, you
might need to recompile anyway...

> -----Original Message-----
> From: Hermann Drdxler [SMTP:[log in to unmask]]
> Sent: Thursday, May 14, 1998 9:53 PM
> To:   [log in to unmask]
> Subject:      Re: [HP3000-L] Hung Sessions and Jobs
>
        <snip>
> 2. If you are not using to much different applications you could write
> a
> smal program to add a debug function to your cobol sources. For
> example,
> place a debug statement at the begin of a section, at goto markers,
> before
> and after locking, io's, and so on. The debug statement is only to
> write on
> line to a file showing what the program has done already. For example
> "will
> WRITE FILE", ok WRITE FILE", "will DBGET DATASE", "ok DBGET DATABASE",
> and
> so on. Use different files for every program, job and session. Be sure
> to
> have a "global switch" to be able to turn debuging on or off because
> this
> will slow down your system a lot.
        <snip>