I totally agree with the negative impact of setting the number of uses to one. Don't want to but I have these land mines sitting out there just waiting for the next job to step on. We have identified the connection that was specifying the libraries parameter and messing up the jobs library list. Tonight we will install the change to Not use the libraries parameter but instead qualify the library of the file to update. Also to use the correct user ID with an updated job description. That should stop more land mines from being planted.
Director of Information Services
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Tuesday, April 01, 2014 6:13 PM
To: Midrange Systems Technical Discussion
Subject: RE: QZDASOINIT prestart job tuning
I think setting the uses to 1 is going ti have an impact on overall system CPU use. I think initial job startup is one of the more resource intensive tasks.