Re: JOBD analysis

[Evan Harris <auctionitis@xxxxxxxxx>]

Hi Joel

I've done this in the past.

My approach was to use the QWDRJOBD API, using a DSPOBJD to an outfile to
provide the input.

I produced 2 files:

- File1 had the details of the job description that I wanted to store (job
queue, outqueue etc.)
- File 2 had an entry for each library in the library recording job
description name and library name

I primarily used this for determining which job descriptions needed to be
edited if librares were removed or added to an application.




On Thu, May 9, 2013 at 2:41 AM, Stone, Joel <Joel.Stone@xxxxxxxxxx> wrote:

> I would like to dump all job descriptions to an *OUTFILE with their
> library list as a "normalized" file, ie one record for each lib in the
> *libl of the JOBD.
>
> Also include last-used date of the JOBD.
>
> The goal is to find out which JOBD's reference certain TEST libraries.
>
> Any ideas how to accomplish?
>
> Thanks
>
>
>
> ______________________________________________________________________
> This outbound email has been scanned for all viruses by the MessageLabs
> Skyscan service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
> --
> 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.