MDSEC – Division of Responsibilities

MDSEC security codes determine the access that a MDCMS user will have.  These are grouped into Security Roles for easy management.  The User Security Report available via the MDSEC menu is the best way to view what access has been granted.  For instance, developers typically have a good deal of access at the test levels but that access can be removed as they move closer to production.

Below are the typical breakdown of responsibilities and the security codes for each.  For a full description of each code as well as a listing of all additional codes available to control project and send functions within MDCMS, please refer to the MDSEC User Guide available in the Customer Portal.

Developer Responsibilities- Ability to change source

Code#:

28   Request to Add, Modify or Delete Objects in MDCMS

29   Request to Add, Modify or Delete Objects in MDOpen

33   Request Source from different Location

30   Request to Re-compile or Update Objects (does not involve code changes, only dependencies).

Optional Developer Responsibilities

34   Retrieve Archived Source or Object (rollbacks)

31   Edit/Delete other’s Object Requests

32   Change programmer for Object Request

47   RFP Rollback

Ability to change objects in a target (i.e. test or production) Environment

Stage One – Request (Building and submitting compilations of objects)

40   RFP Maintenance

41   RFP Submission   (request for change but no change allowed until install stage)

Stage Two - Approval

52   RFP Approval when submitted by same user

42   RFP Approval when submitted by different user

43   RFP Approval for manually changed Objects

Stage Three – Installation into target environment

44   RFP Installation when approved by different user

53   RFP Installation when approved by same user