That's a good question - always get to what the user really needs, not what they say they want ;-)
I support a vendor supplied application. It runs from the LOGIN paragraph and provides a menu interface. Over the years we have written a lot of supporting code "around" the vendor app, so now we have (at least) four ways a custom program can be run: 1) We can add user-defined menu items and they get EXECUTE'd from the menu (by code I don't have access to) 2) Our operations people can drop to TCL and run a command directly from there 3) We have an elaborate cron setup that ends up running "streams" on a variety of schedules 4) We use uniobjects, and different external interfaces making calls into Unidata (mostly subroutine calls from java and .net clients) As a result of an upcoming upgrade (in > 1 year), we're likely going to have to touch all of the programs and make some modifications. Ideally we'd cut down the number by disregarding one-off programs that haven't run in ages. We have programs last compiled in 2004, but I know they run many times per day, so time-stamps don't cut it. -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Charlie Noah Sent: Monday, January 06, 2014 5:31 PM To: U2 Users List Subject: Re: [U2] Logging program execution in Unidata? 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: u2-users-boun...@listserver.u2ug.org > [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson > Sent: Monday, January 06, 2014 7:07 PM > To: u2-users@listserver.u2ug.org > 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 <james.mcgo...@bankofthewest.com> > To: U2 Users List <u2-users@listserver.u2ug.org> > 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: 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 > > > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > 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 > 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
