Ian,
You said you didn't have a wrapper program. How do your programs get
executed?
Charlie
On 01-06-2014 7:23 PM, Baakkonen, Rodney A (Rod) 46K wrote:
What we did was have a cron run every 10 minutes that executed a Unidata
program. The Unidata program did a PCPERFORM sbcsprogs to capture everything
that was running out of the global catalog. It parses up the output of
sbcsprogs and builds a Unidata file. This file has the program name as the key
and the following attributes:
DR DoctoR (Display Record) File: CBH.PROGRAM.TRACKING
ATB ATB Name Conv Value Item: CLM101
1 Last Update D2/ 01/06/14
2 First Recorded D2/ 11/16/00
3 No of Times Captured 4254
End of Defined Attributes
If something consistently runs and finshes within 10 minutes, it will never be
recorded. You could have the threshold set to whatever you want. But we thought
10 minutes was good enough for our usage.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Wjhonson
Sent: Monday, January 06, 2014 7:07 PM
To: [email protected]
Subject: Re: [U2] Logging program execution in Unidata?
I believe there is something wrong with this suggestions.
IIRC you don't get the time and date it was last RUN, only the date it was last
"Accessed".
I suspect this is the "touch" date, which could mean that just looking at it in a
directory scan, "touches" it.
Along with a host of other things that don't actually *run* the code.
So it wouldn't answer the Q as to whether it's "actively" executed.
You also get the number of times is has run since being catalogued, which
always seemed to be an odd choice for me.
It may have been run a thousand times, but not run at all in the past ten years.
But if I ruled the world, things would be different.
Not better just different.
Anyway, let us know how it works for your purpose.
-----Original Message-----
From: McGowan, Ian <[email protected]>
To: U2 Users List <[email protected]>
Sent: Mon, Jan 6, 2014 4:55 pm
Subject: Re: [U2] Logging program execution in Unidata?
Larry/Wol, thanks for this. Trying it now on a dev server. Not sure how I've
missed this all these years, but glad to learn something new!
-----Original Message-----
From: [email protected]
[mailto:[email protected]]
On Behalf Of [email protected]
Sent: Monday, January 06, 2014 4:44 PM
To: U2 Users List
Subject: Re: [U2] Logging program execution in Unidata?
MAKE.MAP.FILE
We catalog all our programs - locally (so they end up in CTLG in the
current account) for programs specific to a particular account, as
well as globally (so there is a pointer in CTLGTB) for generic programs.
Unfortunately, unidata seems to have _MAP_ file in $UDTHOME/sys/_MAP_
(as well as a MAP command) but at least for us it's not populated.
Thanks for the suggestion,
Ian
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of dale kelley
Sent: Monday, January 06, 2014 4:13 PM
To: U2 Users List
Subject: Re: [U2] Logging program execution in Unidata?
Ian,
In universe the map file contains the most recent execution date for
cataloged programs. Programs that are just "RUN" I don't know of any way.
Dale
On 01/06/2014 06:08 PM, McGowan, Ian wrote:
We're looking into a major conversion late this year, which will
involve checking out several thousand programs (mostly opens, reads
or
writes).
Some programs are run many times a day, whereas some were throwaway
and haven't been touched in years. It would be great to get some
sense of which ones are active.
We unfortunately don't have a wrapper program, wondering if anyone
has run into this before - is it possible to somehow log when a
program is executed in Unidata? Any magic triggers, directory flags
or other audit flags that can get turned on?
Any ideas gratefully received,
Ian
-----------------------------------------
IMPORTANT NOTICE: This message is intended only for the addressee
and may contain confidential, privileged information. If you are not
the intended recipient, you may not use, copy or disclose any
information contained in the message. If you have received this
message in error, please notify the sender by reply e-mail and delete
the message.
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: If you have received this email in error,
please immediately notify the sender by e-mail at the address shown.
This email transmission may contain confidential information. This
information is intended only for the use of the individual(s) or entity to
whom it is intended even if addressed incorrectly. Please delete it from
your files if you are not the intended recipient. Thank you for your
compliance. Copyright (c) 2013 Cigna
==============================================================================
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
