Re: Reg: Skipping Job Restart Process

Several options have been discussed on this and Midrange-L list over the years.

Most involve adding checking logic to the programs to compare (say) a built-in version number with one in a User Space and to exit and restart itself when there is a mismatch.

Unless ILE is involved and you can kill the Activation Group most methods involve using a variable name to contain the name of the program to be called so that resolution of the p[rogram to the new object can be forced.

I'm sure others will chime in but I suggest you search the archives for the earlier discussions.

On Jan 7, 2020, at 12:39 PM, Suren K <suren7437@xxxxxxxxx> wrote:

Hi All,

I was thinking about the Job restart process.

Whenever any changes we are applying to any program. If that program is
used in 10 never ending jobs, we will end those ten jobs and then install
the changed object and start those ten jobs again.

Is there any idea to skip restarting the jobs, Instead of restarting we
will code the job in a manner, it will automatically use the new object
once we installed?

Regards,
Surender K
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com