Re: Scouring job descriptions for soon-to-be deleted libraries

Hi

I've done this in the past by using the QWDRJOBD information to create a
table with job description and Library in it; 1 row per Library and Job
description. Then I queried that table to see if the libraries in question
were in there. You may be able to do this in CL (even easier in recent
releases) but probably not beginner level stuff; I used RPG but might look
at Java now if you have skills there.

Depending on how many Job Descriptions you have and how many libraries are
being deleted for a one off exercise you may find a brute force approach
just as easy:
Just do a WRKJOBD *ALL/*ALL and place 5 against all the entries, press
enter a couple of times and eyeball the library list for each one.

Depending on what release you are on I think the system is a bit more
forgiving about libraries not being found in job descriptions (V7R1 or
better if memory serves)

Last refuge of the desparate is to clear the library and leave the empty
library there and maybe change the description to indicate what is going on.


On Thu, Oct 12, 2017 at 6:29 AM, Kelly Beard <kenverybigliar@xxxxxxxxx>
wrote:

Is there a query or anything I can run to take a list of job descriptions
and see if they contain a library in them that we want to remove from the
system? I am formulating a shell script to do this but in order to improve
my CL and general command use, I'd like to do it that way instead.

--
Kelly Beard
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD