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: u2-users-boun...@listserver.u2ug.org 
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of lar...@wcs-corp.com
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: u2-users-boun...@listserver.u2ug.org
> [mailto:u2-users-boun...@listserver.u2ug.org] 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
>> U2-Users@listserver.u2ug.org
>> http://listserver.u2ug.org/mailman/listinfo/u2-users
> _______________________________________________
> U2-Users mailing list
> U2-Users@listserver.u2ug.org
> http://listserver.u2ug.org/mailman/listinfo/u2-users
> _______________________________________________
> U2-Users mailing list
> U2-Users@listserver.u2ug.org
> http://listserver.u2ug.org/mailman/listinfo/u2-users
>


_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to