| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
hi there -
have a customer here that wants to track how who, when and how often
their users access an application from within ALL-IN-1 V2.4.
the application resides in form library. it contains scripts, forms
and calls to c functions. the application itself is an executable
image.
users have access to it either by having the form libary on their form
lib line in the profile. or an oaini.scp is run when they access
ALL-IN-1.
this would be on both ALL-IN-1 2.4 and Starter 2.4.
i've looked at metering and logging. i don't think they'll work.
ann
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 325.1 | Add your own Meter? | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Thu Mar 26 1992 10:14 | 6 |
Metering as standard might not work, but you could always add an extra
meter for your application.
I'm sure the Management Guide will tell you how to do this somewhere.
Graham
| |||||
| 325.2 | Metering should work | SHALOT::NICODEM | Who told you I'm paranoid??? | Thu Mar 26 1992 13:12 | 32 |
� the application resides in form library. it contains scripts, forms � and calls to c functions. the application itself is an executable � image. OK, Ann; as usual, I'm confused. If the application is an executable image, do you mean it's *invoked from* a form in the form library? I'm not sure what you mean when you say a) it's an executable image, b) it contains scripts and forms, and c) it resides in a form library. Let me make a *very* broad jump, and ass/u/me that a) the "root" code is an executable image, coded in C, b) a "shell" has been built around it to provide an ALL-IN-1 user interface (consisting of scripts and forms), and c) it is invoked from an ALL-IN-1 menu. I'd go along with Graham and say that you can certainly declare your own meters, and use those to do exactly what you want. Now, as to how to start/stop and so forth, it would appear that you could add all of that either to the form that invokes the application, or to the scripts built around it. In fact, if the executable image can be designed appropriately, and installed as a VMS shared image, you could even invoke the image directly from your scripts (using the INSTALL and EXECUTE functions). BTW, how are you doing it now? Using the subprocess? Spawning to another process? Look at the metering functions, and also the INSTALL and EXECUTE functions. You could even invoke your installed image with CALLBACK, and have *it* ask ALL-IN-1 to do the various metering at the appropriate times... from *within* the executable image! F P.S. How'dja like those Grammies? Nice goin', Natalie! | |||||
| 325.3 | thanks | NCBOOT::HARRIS | oooppps | Thu Mar 26 1992 20:54 | 11 |
thanks for the suggestions.
i was talking to a VMS guru here and he suggested to install the image
with /accounting.
i think i might go that way.
re .2
yes frank, you're right on how its used (for more info on it (if
you;re interested) see bob h.)
ann
| |||||
| 325.4 | Straight forward stuff | SHALOT::HUNT | Go Hoos !!! | Tue Mar 31 1992 08:51 | 6 |
Pretty sure that metering can do what you want here, Ann. And, if not, you can always look at TEXT_FILE and just have the scripts open up a flat ASCII text file and log lines to it. Bob Hunt | |||||