Re: iProject reconciler and QZRCSRVS jobs

Hi Steve,

Yes, I'm aware of the serverside setting of prestart jobs. It is
*NOMAX with 200 re-uses for QZSCSRVS in our system, and we'll keep it
like that.
But I was looking for a way to limit the firing of those jobs from
RDi. I just don't understand why activating Remote Reconciler for an
iProject causes such an explosion of QZSCSRVS jobs. I am thinking that
literally for every sourcemember a QZSCSRVS job is fired. A "normal
push" does not cause such explosion, but reconciler does. I had 600+
sourcemembers in the iProject, and hundreds of QZSCSRVS jobs were
fired. I haven't counted them all, but it was at least 300 jobs.

Best regards,
-Arco


Op vr 7 sep. 2018 om 16:29 schreef Steve Ferrell
<Steve.Ferrell@xxxxxxxxxxxxxxx>:

Hi Arco,

QZRCSRVS jobs are run in QUSRWRK via a Prestart Job Entry. By default the QUSRWRK subsystem description has the QZRCSRVS set to Maximum number of jobs set to *NOMAX. These jobs are cleaned up by a cleanup thread that runs by default every hour on the IBM i, and will clear a job if it hasn't been used in the past 2 hours. So many of these jobs may just be idle remnant jobs. There are two common ways to tune QZRCSRVS jobs.

1) Set Maximum number of jobs to a fixed number.
2) Increase the Number of times used to a higher number so these jobs can be re-used more often.

To see what your settings are now, from a command line on an emulator issue the following IBM i command:
DSPSBSD QUSRWRK

Then select option 10 for Prestart job entries:
Then put option 5 on QZRCSRVS and review the current values. (Maximum number of jobs and Maximum number of uses.)

Yes, you can limit the number, but keep in mind it will impact your performance in RDi if you limit the number of jobs and several users are running on the same system. These jobs are used by other applications that connect to the IBM i using Java, so care is required when tuning these jobs.