System i: iDoctor for iSeries - Job Watcher | Forum profile

A customer asked me to pass this experience along with Symantec: I went back and forth through the problem reports at Symantec for this problem and although it appears that Symantec is very recalcitrant about how will not be fixed until the next release (6), someone posted a workaround – I tried it and it fixed the problem. The workaround is to disable the sysplant service by...

Hello Socket waits in Collection Services (viewable under iDoctor using Collection Services Investigator - CSI ) can be waits from any of the 4 socket buckets included with Job Watcher (23-26). You can find more details in the white paper on wait buckets https://www-912.ibm.com/i_dir/idoctor.nsf/3B3C112 F7FBE774C86256F4000757A8F/$FILE/Job_Waits_White_Pa per_V5R4.pdf But ...

Regarding the error I think it's a problem registering the procedures properly. A workaround is to delete them from qidrgui individually. In this case DLTPGM PGM(QIDRGUI/QIDRJWGRI) , etc. After deleting all that gave errors, restart the GUI. The latest builds actually provide a menu from the Connections view which clears out all the iDoctor stored procedures in QIDRGUI ...

Back to Thread List

Hi, The PEX guide gives examples of non-DB writes as "spool files, job logs, data area, data queues etc." and non-DB reads as "data areas, data queues, user profiles, loading programs, user spaces etc." Not a definitive list but maybe gives you enough of a steer. Regards,

Hi Steve While there can be numerous causes for DASD Space Usage Contention, my experience has been that it's typically most present when CPU utilization is very high. As with machine level gates and seizing, for example, the wait lasts longer because a basic resource is unavailable, whether that be CPU or disk response. If CPU usage wasn't high, then also review the synchronous ...

Yes, we just had a customer experience this and for the following error, the resolution shown below worked. I will be working on testing Windows 7 this month. Client Access is expected to provided support for Windows 7 in Decmeber (which iDoctor requires). It should be supported within the next couple of months at maximum. ERROR when launching iDoctor: Windows cannot access the ...