In our current environments Developers have access to compile in Test/Model/Production and serve as support for nightly cycles. After upgrading to EE the plan is that Developers only can compile in Dev and code will be promoted through change control with appropriate signoffs into Test/Model/Production but still will be responsible for supporting cycles.
Developers have concerns about supporting daily cycles. Basically if a Production job aborts and requires some type of code change to continue the cycle it can't be done.
Does anyone have suggestions for handling emergency situations?
Production Support
Moderators: chulett, rschirm, roy
Re: Production Support
1)
This how life will move. Now a days cost cutting is the main factor to the companies and they need a resource who can do more multi tasks.
I know it is a pain, working at late hours / mid night! In general there will be a support team (He is also like you and he might not want to do late hour job
) who will maintain the jobs. But if the Jobs are moved and new to Prod and still under warranty then you guys also responsible!
You can express your concern to the manager. Either your manager need to agree with your feelings / you need to disagree (You know what would be the result) .
The advantage is, you may see the real time failures and issues. Those failures could be totally new to you and that may help you get more hold on Datastage.
Net result is, no one cant advise in this matter and this should be your decision.
2)
It seems to be poor testing / uat could be the reason for code changes, after a job moved to prod.
If that is the case, that day job will not run, next day fix the code migrate and then do the catch-up (depends).
Code change in prod is hot fix and that should be a rare case and that wont be for day to day life!
Good luck.
This how life will move. Now a days cost cutting is the main factor to the companies and they need a resource who can do more multi tasks.
I know it is a pain, working at late hours / mid night! In general there will be a support team (He is also like you and he might not want to do late hour job
) who will maintain the jobs. But if the Jobs are moved and new to Prod and still under warranty then you guys also responsible! You can express your concern to the manager. Either your manager need to agree with your feelings / you need to disagree (You know what would be the result) .
The advantage is, you may see the real time failures and issues. Those failures could be totally new to you and that may help you get more hold on Datastage.
Net result is, no one cant advise in this matter and this should be your decision.
2)
It seems to be poor testing / uat could be the reason for code changes, after a job moved to prod.
If that is the case, that day job will not run, next day fix the code migrate and then do the catch-up (depends).
Code change in prod is hot fix and that should be a rare case and that wont be for day to day life!
Good luck.
Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.