RE: Who held *JOBQ?

["M. Lazarus" <mlazarus@xxxxxxxx>]

Rob,

 What release did this exit point become available?

 -mark

At 1/19/10 10:04 AM, you wrote:
> ... then there's the command exit point program... see WRKREGINF,
> QIBM_QCA_CHG_COMMAND
>
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:   "Dennis Lovelady" <iseries@xxxxxxxxxxxx>
> To:     "'Midrange Systems Technical Discussion'"
> <midrange-l@xxxxxxxxxxxx>
> Date:   01/18/2010 06:45 PM
> Subject:        RE: Who held *JOBQ?
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> >   This and the journaling idea are good ideas, assuming that I have
> > control over the system.  I was hoping that this info would be part
> > of the *JOBQ attributes, retrievable by an API.
> >
> >   A commercial utility or even a full blown application would be hard
> > pressed to assume that they could install a VCP on an OS command or
> > to set up auditing for the command.
>
> One approach (which may be as much taboo as altering the OS command, but
> is
> actually much less risky) is to put commands named RLSJOBQ, HLDJOBQ and
> whatever else floats your boat into a separate library.  These commands
> would be attached to your own programs that do the logging, then execute
> QSYS/RLSJOBQ (etc.).  Actually, there's good reason to do the QSYS thing
> before your logging.  In any case, then put this library ahead of QSYS in
> the system library list.  The only things that would have to reside in
> that
> library would be the *CMD objects.  This works very well.  In fact, I
> would
> avoid any alteration to IBM-supplied objects even if the system is under
> my
> control.
>
> Dennis Lovelady
> http://www.linkedin.com/in/dennislovelady
> --
> "We can't all be heroes, because somebody has to sit on the curb and clap
> as
> they go by."
>         -- Will Rogers
>
>
>
> --
> 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.