You might be able to implement this capability from within the programs
themselves without a huge amount of effort.  We have a small program
tracking subroutine and a companion utility that automatically installs
a call to it from every program.  The original purpose was to determine
which code was still in use for our initial conversion from Ultimate to
UV 15 years ago, but it's come in handy for isolating anomolies over the
years.  The call statement is simply:


The utility goes through all programs on a weekly basis during nightly
batch processing, adds that line at the top if it doesn't exist
(following the "SUBROUTINE" line), and recompiles the program.  The
tracker program writes a log record where the ID is the user and the
data is a sequential list of programs as well as a record where the ID
is the program and the data is a sequential list of users.  For your
lock issue, you could take this a step further and:

1) Check to see if this session is still hanging onto locks from the
previously called subroutine
2) Figure out what subroutine was previously called from the log record
and log the locks still being held

You will also have to come up with a method of insuring you only log the
initial instance, but I think that should be do-able.


-----Original Message-----
[] On Behalf Of Kevin King
Sent: Thursday, September 08, 2011 1:01 PM
To: U2 Users List
Subject: Re: [U2] Lock Status

Thank you goes out to everyone for the input.  We were able to identify
as of this moment it would appear correct) a couple of suspects by
at the code that had been compiled within the last 2 weeks and
each routine separately.  I still think it'd be cool to be able to see
program set which locks retrospectively, though I completely understand
Wally's perspective about the effort involved to make that happen.

U2-Users mailing list
U2-Users mailing list

Reply via email to