Re: Logging when child-server jobs start and end

There use to be a taatool called cvtqhst

On Thu, Jun 2, 2011 at 2:37 PM, James Lampert <jamesl@xxxxxxxxxxxxxxxxx

wrote:

rob@xxxxxxxxx wrote:

If it truly launches a separate job, isn't it already logged?

DSPLOG PERIOD((*AVAIL 060111)) JOB(ROBS1)
Job 548056/ROB/ROBS1 started on 06/01/11 at 07:08:48
Job 548056/ROB/ROBS1 ended on 06/01/11 at 08:54:45;
Job 548496/ROB/ROBS1 started on 06/01/11 at 09:40:49
Job 548496/ROB/ROBS1 ended on 06/01/11 at 15:35:27;
Job 552573/ROB/ROBS1 started on 06/02/11 at 08:36:24

There are API's to get that info also.

Dear Rob, Jack, et al.:

It is indeed a separate job, and it is indeed logged in QHST. And WOW,
we even get the circumstances under which it ended.

But it seems that the customer wants us to take that information, and
make it available within Wintouch itself. Is there a way we can have a
program monitor QHST for new entries fitting the desired pattern? If we
could do that, we could define an Extended Profile (basically, a file of
records containing a 17-digit record-ID, creation and modification
stamps, and up to 1000 bytes of user-defined fields, optionally
including a parent record in another file), tied to the user contact
record, that would capture the particulars.

But can QHST be easily monitored for activity?

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.