Difference between 'always' and 'only one' Autosubmit options in Wait event

[former_member206885]

Hi All,

I tested some jobs with  'always' and 'only one' Autosubmit options by placing some files. Whenever the file is placed, the instance of the job is getting submitted irrespective of the previous instance of the job is running or not.

Can one please explain is there any much difference between the two options 'always' and 'only one' Autosubmit options in Wait event tab.

Thanks,

Tinku

[Former Member · Accepted solution]

This is from SAP CPS Admin guide.

Only one - Only submits a job when there is no job of the same job definition in a pre-running state, a job that has not yet reached status Running yet.

Always - A job will always be submitted regardless of any pre running state.

Hope this helps.

Rick.

[former_member206885 · Accepted solution]

Hello Rick,

I have tested the jobs with  'always' and 'only one' Autosubmit options by placing 4 files. For both Autosubmit options, 4 instance of the job are submitted irrespective of the previous instances of the job are running or not. I am not able to see any difference. As mentioned in the admin guide, the second instance of the job didn't wait for the first instance of the job to complete. Might be as Gerben said, 'only one' option is not reliable at the moment.

Thanks,

Tinku

[gmblom · Accepted solution]

Hello Tinku,

In your scenario 'Only One' should behave the same as 'Always'. However, due to timing issues in the 'Only One' case it is possible that the previous job is not started quickly enough by the system, in that case, it will see a pre-running job, causing the Autosubmit NOT to happen. Now no additional job is started that can clear the Raised event. And now the process gets stuck as there is an event in status Raised, and all new files will put their Event in status Pending until the Raised Event gets cleared, which will never happen. So here you want to avoid using the 'Only One' option but use 'Always' instead.

The only reason to use 'Only One' (and still you might run into this deadlock scenario due to timing issues) is when the job waiting on the file is sometimes already Scheduled/Waiting/EventWait and sometimes has to be started by the File Event. Because when the job is already waiting, the Always will kick off the waiting job AND autosubmit a new job.

Regards Gerben

[former_member206885 · Accepted solution]

Thank you very much Gerben.

Regards,

Tinku

[gmblom]

Hello,

The 'only one' will check if there is already a job waiting for the event. If not, it will autosubmit the job anyway.

Note that the 'only one' is unreliable at the moment, so stick with the Autosubmit option for now. Especially if you do not notice a big difference.

Regards Gerben

[former_member206885]

Gerben, little confused. Do you mean if one instance of the job definition is in active state for example due to arrival of a file and the second instance of the job definition will not be submitted unless the first instance completes?

Thanks,

Tinku