Author: Rohit Umarjikar
Posted: Fri May 06, 2016 7:19 pm (GMT 5.5)
untrained Robots.
Too dangerous to go with this approach, what if a new prod region gets added tomorrow, you will simply lose the file and again change this logic and keep doing as and when a new region adds up. most importantly,you need to have a proper process in place which is the cause of such issues and it will be there till you don't create separate jcls for test and prod regions keeping the same proc though.
_________________
Regards,
Rohit Umarjikar
"Some things Man was never meant to know. For everything else, there's Google"
Posted: Fri May 06, 2016 7:19 pm (GMT 5.5)
| Quote: |
| Changing proc and JCL Libraries may not be taken care by resources |
untrained Robots.
| Quote: |
| With this approach, I managed to create a small sas program to validate the first 8 character of SYSJOBID automatic macro and if it is not equal to production job id, then it will suppress execution of STEP04 in test region. Same job when it runs in production run, the job id matches and it continue to execute the STEP04. With this approach I hope user/tester/developer need not do bulk of change in the job/proc. |
Too dangerous to go with this approach, what if a new prod region gets added tomorrow, you will simply lose the file and again change this logic and keep doing as and when a new region adds up. most importantly,you need to have a proper process in place which is the cause of such issues and it will be there till you don't create separate jcls for test and prod regions keeping the same proc though.
_________________
Regards,
Rohit Umarjikar
"Some things Man was never meant to know. For everything else, there's Google"