Many jobs created with iSeries Nav collects inventory
Recently I installed iSeries Access service pak SI32972 on my PC. This includes updates to Navigator. Since the install, every time we collect inventory (fixes, users, etc) about 400 jobs are added to our iSeries. These jobs remain until we ENDTCPSVR *MGTC. These jobs also consume disk space which is released only when we ENDTCPSVR or re-IPL. At IBM's recommendation we have set max use on QSYS/QZRCSRVS to 1 but the system still creates 400 jobs when inventory collection runs.
Has anyone else experienced this?
Software/Hardware used:
Software/Hardware used:
ASKED:
July 10, 2009 5:05 PM
UPDATED:
July 13, 2009 3:23 AM
Answer Wiki:
I've used this feature for years. It's a system intensive process not to mention the bandwith consumption.
Sounds like you need to verify if your AS400's PTF levels match up to the service pack level.
Or your AS400 is extremely small or our DASD utilization is too high to be using this tool.
When you're using this utility to go out and download fixes for you don't for get that Group PTF updates
and Cumulatives come in on multiple CD's so you're talking 5-10+ GB of data.
This tool is going to require the same amount of disk space for temporary storage of downloaded fixes.
You'll need to ensure your network can handle the load as well.
It's probably worth the hour of reading to understand this product before you run out using it.
<a href="http://www-03.ibm.com/systems/i/software/access/">LINK</a>
*****
There are PTF's that address this problem.
Check this
<a href="http://www-01.ibm.com/support/docview.wss?uid=nas2a9726a3c5ed624a786256e5d0042179a">link</a>
To see all answers submitted to the Answer Wiki: View Answer History.
Hello Slack400,
I too have used iNav for years. That is why I know it is not normal for the number of jobs to increase by 400 every time inventory is collected. To put it politely, your condescendng attitude is not appreciated nor appropriate since you know nothing of our environment nor the expertise of our staff.
Friday I learned from IBM that there is a bug in V5R4 and 6.1. PTFs are being prepared to correct this problem but have not been released yet.