Authorization
The user is responsible for integrating changes into
MICS
.rm
Required roles: systems programmer, security administrator, database administrator |
|---|
These changes apply to vendor-supplied maintenance and user-generated modifications.
The final responsibility at most
MICS
installations for authorizing the production implementation of MICS
changes rests with the MICS
System Administrator, or some member of the organization's management staff at an even higher level.Before arranging authorization, ensure:
- The changes do not affect the operation ofMICS, except in the documented way.
- The changes do not affect the content ofMICSdata, except in the documented way.
- The changes do not increase the dependence of your site on a particularMICSor operating system release to a level that you think is unreasonable.
The integrity of the
MICS database
is the prime consideration. That, after all, is a major reason behind the acquisition of the product. The criticality of the integrity of data in the MICS database
is self-evident, especially if the MICS
data is used in chargeback applications. Lost data can mean lost revenue.The
Broadcom Support
Group is available to present objective arguments you may use in formulating the decision to implement or not implement a change. Any negative response from the Broadcom Support
Group should be considered carefully.