Re: RE: User logons? -- MIDRANGE-L

You probably do not really need the CPF1124. More on that below. For better specifics on the CPF1164 see the Work Management manual at http://publib.boulder.ibm.com/pubs/html/as400/v5r1/ic2924/books/c4153063.pdf - it's actually the V4R4 manual starting at page 147 - it has a program example with detailed layout of the message data that you never see on the screen. There is even an indicator of job type, so you could filter for interactive. You read the various QHST* files. Individual messages are spread across multiple records, so it is not the prettiest file to process - but doable.

BTW, this message even has the start time for jobs, so you don't really need the CPF1124. And there are both the date/time the job entered the system (could be still on a job queue) and the date/time the job started. For interactive jobs these will probably be no more than a second or two apart, if that. But use the "started" date/time, not the "entered" date/time.

HTH
Vern

At 11:38 AM 1/21/2005, you wrote:

maybe the following post will help

http://archive.midrange.com/rpg400-l/200312/msg00028.html


http://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/c4157215.pdf
page 275

----------------------------
Bryan Dietz

Aktion Associates
Technical Consultant

7716 Rivers Edge Drive, Suite B
Columbus, Ohio 43235
614.840.9880  x406
614.840.9886 (fax)
614.419.5079 (cell)
bdietz@xxxxxxxxxx
www.aktion.com


midrange-l-bounces@xxxxxxxxxxxx wrote on 01/21/2005 11:47:17 AM:

> I will explain a little more on this project.   I have about 18
> users that the customer   wants to know when the user signed on and
> off, nothing else. He wants this supplied to him weekly in report form.
> Hopefully I can use the output in print form and them convert it to
> a database format and then prepare my report
>
> TIA
> Dave Willenborg
> WIT Consulting
> >
> > From: rob@xxxxxxxxx
> > Date: 2005/01/21 Fri AM 11:18:54 EST
> > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > Subject: RE: User logons?
> >
> > If that's all that's needed you can tailor dsplog for
> > DSPLOG MSGID(CPF1124 CPF1164)
> > Too bad DSPLOG MSGID(CPF1124 CPF1164) JOB(userid/*N) is not supported
> >
> > Rob Berendt
> > --
> > Group Dekko Services, LLC
> > Dept 01.073
> > PO Box 2000
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> >
> >
> >
> >
> >
> > "Barton, Mike" <Mike.Barton@xxxxxxxxxxxxxxxxx>
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 01/21/2005 10:46 AM
> > Please respond to
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> >
> >
> > To
> > "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
> > cc
> >
> > Subject
> > RE: User logons?
> >
> >
> >
> >
> >
> >
> >                                  >I have been asked by a client to
provide
> > a list of selected
> > users signon and signoff times. The users can >signon from various
> > devices.
> > The company does  have QAUDJRN turned on. Is there a way to find it
> > >QAUDJRN
> > or will I have to do a search through the dsplog in order to get the
> > information.
> >
> > Dave
> >                  The History log ought to be able to supply this info.
> > Look for 'Job 99999/User/Job started on ...... in subsystem QINTER
> > And the appropriate ended message.
> >
> > HTH
> >
> > Mike
> > ###########################################
> >
> > This message has been scanned by F-Secure Anti-Virus for Microsoft
> > Exchange.
> > For more information, connect to http://www.F-Secure.com/
> >
> > **********************************************************************
> > This communication and the information it contains: - (a) Is intended
for
> > the person(s) or organisation(s) named above and for no other person(s)
or
> > organisation(s). Access to this mail by anyone else is unauthorised.
(b)
> > Is confidential, and may be legally privileged or otherwise protected
in
> > law. Unauthorised use, circulation, copying or disclosure of any part
of
> > this communication may be unlawful. (c) May be susceptible to
> > interference, and should not be assumed that it has come in its
original
> > form and/or from the stated sender or PinkRoccade UK accepts no
> > responsibility for information, errors or omissions in this e-mail or
use
> > or misuse thereof or any act done or omitted to be done in connection
with
> > this communication. If you are not the intended recipient, please
inform
> > postmaster@xxxxxxxxxxxxxxxxx immediately and delete it and all copies
from
> > your system.
> >
> > www.pinkroccade.co.uk
> > **********************************************************************
> >
> > --
> > 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.
> >
> >
>
> --
> 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.