Hi All,
I was wondering if it is possible to make some or all of the job (sequence) parameters mandatory to fill it in, otherwise the job should not proceed, ( abort as soon as it runs). The reason I need this, our QA testers are testing the jobs by clearing out some of the default parameters and see what happens when it runs. I know it is kind of not a good test case but they have it.
They want it the job ( sequences) should abort as soon as possible when those parameters not filled in. I have a lot of parameters so I was wondering if there is an easy way to do these checks?
I appreciate all the potential responses.
Thanks,
Chad
is it possible to make some job parameters mandadatory ?
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Empty parameter value should be invalid - and prevent a job from running - for all parameter types except String and Encrypted.
You can check for job parameter values in a before-job subroutine and immediately abort the job (by setting ErrorCode) if any is invalid, if that is a requirement.
If it wasn't originally a requirement, then it's a change and billable time.![Wink :wink:](./images/smilies/icon_wink.gif)
You can check for job parameter values in a before-job subroutine and immediately abort the job (by setting ErrorCode) if any is invalid, if that is a requirement.
If it wasn't originally a requirement, then it's a change and billable time.
![Wink :wink:](./images/smilies/icon_wink.gif)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.