When there is network or server slow/hiccup, some of the job run twice in process scheduler, which suppose to run once only, and the same job appear in $U console either No Success, or Submission Error, or Success.
a ) Why job has been triggering twice in Process Scheduler when there is server/network issue?
b) How can we prevent the job not to run more than once in process scheduler? Which means when server/network issue, only one job is trigger from $U?
c) Refer to $U node setting above, can help to explain “Maximum number of attempts to connect to the peoplesoft database”? (Will this be the cause of trigger more than one from $U)?
Release : 6.x
Component : DOLLAR UNIVERSE
The two parameters i.e. Delay between 2 connection retries (seconds) and Maximum number of attempts to connect to the PeopleSoft database, ), determine what happens when the Manager is unable to connect to Peoplesoft database to retrieve a Jobs Status or to submit a job. If the Manager is unable to connect to the Database after n trials with an interval of y seconds between each, it will consider that job has aborted.
Polling cycle Maximum Waiting time between 2 polling's : this is parameter is based on the polling cycle of the Peoplesoft scheduler (this is an internal Peoplesoft parameter). Normally the value of this parameter is 15 seconds. That is why the Parameter in DUAS is set to 35 sec (2x the Polling Cycle + 5 secs = 35 secs).
Please refer to document Manager for PeopleSoft Node Settings for more details.