|
I imagine there is a better way, but I haven't seen any answer to your question yet, so here goes: You might look into displaying user job logs to an outfile and look for CPC1221 (completion message received when a user submits a job) in the QMHMID field. The message data field QMHMDT seems to show the job queue the job was submitted to, and the QMHJOB field shows the submitting (offending) job. You might also want to include checking for change job messages in a similar way. Roger Boucher Standard Pacific Corp. rboucher@stanpac.com 714-668-4326 -----Original Message----- From: Graap, Ken [mailto:keg@exchange.gasco.com] Sent: Tuesday, September 21, 1999 3:55 PM To: 'Midrange' Subject: Finding where a job ran... Hello - I would like to know what subsystems and/or job queues are being used for submitted batch jobs. I know the name of the subsystem a job started in is included as part of the CPF1124 message on message queue QSYSOPR, but it is difficult to retrieve this information, and it doesn't include the job queue name. I also know that the WRKUSRJOB command displays the job queue a job was run from when it is executed with an "Assistance level" of *BASIC. However, this information is only available on the system while the job is still in the system, i.e. ... on a job queue, active or has output on an output queue and it isn't listed on the report when *PRINT is specified.. What I want to be able to do is create a process that will let me find users who "cheat" by doing things like submitting batch jobs to subsystem QINTER or QCTL instead of QBATCH. Has anyone written a program or know of one, that can gather up this kind of information? If not, does anyone have any ideas on how I might begin to write one? Kenneth **************************************** Kenneth E. Graap IBM Certified Specialist AS/400 Professional Systems Administrator NW Natural (Gas Services) keg@nwnatural.com Phone: 503-226-4211 x5537 FAX: 603-849-0591 **************************************** +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.