In our production Datastage 11.5 environment we submit all of our jobs by using the command line from Linux scripts so that should only be submitted via an external scheduled job. This gives a degree of control over accidental updates to the production database.
Currently our support analysts need to be able to read jobs in order to debug them, so they have been given a super operator role. This means that they could also run a job from the Director or Designer that updates the production database which we don not want them to be able to do.
Obviously there will be some sites this wouldn't be a useful feature, and so would suggest it should be controlled by a project config parameter.
Equally it would be useful if developers could run jobs for possible de-bugging of jobs. We only give this access to a few SME's and for a limited time period.
Somehow our previous Datastage 8.5 production environment was set up so that no-one could use the Run Now, Stop or Reset functions - no errors were generated; just nothing happened. This was done by Cap Gemini when they installed it for us (we think)
|Who would benefit from this IDEA?||This idea is to reduce the risk of the production database getting corrupted by jobs being run against be mistake or maliciously. As data custodians we are expected to maintain data quality.|
How should it work?
As mentioned above probably should include a project level parameter that can disable the Run Now and Stop buttons and menu options from Datastage Director and Datastage Designer.
If the parameter is set, either the option is greyed out, or an error message is received if the options are selected for Operator and Super Operator users.
Developers would not be impacted.
|Priority Justification||We are regulated by the FCA in the UK, and data quality is taken seriously. Obviously the longer we run with this risk, the greater the chances of an incident|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions