ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Impact of changing IBM i security levels on CA2E
Article ID: 129470
Updated On:
Products
CA 2E
Issue/Introduction
What is the impact on CA2E if you raise the security level of IBM i running CA2E from 20 to 30?
Environment
Release:
Component: C22E
Component: C22E
Resolution
Regarding security level, there is no particular problem in normal usage (management with user profile).
However, although this is the IBM i security world, since objects in the model LIB and generated LIB are objects on IBM i, you can use the user authority to secure each object individually.
By raising the security level, you may not be able to access it if you have different permissions from the security level.
2E provides management of model authority (model access) by changing object authority for data area YMDLLIBRFA in MDL. It can be done with No.30 in the designer menu or EDTOBJAUT OBJ (YMDLLIBRFA) OBJTYPE (*DTAARA).
However, although this is the IBM i security world, since objects in the model LIB and generated LIB are objects on IBM i, you can use the user authority to secure each object individually.
By raising the security level, you may not be able to access it if you have different permissions from the security level.
2E provides management of model authority (model access) by changing object authority for data area YMDLLIBRFA in MDL. It can be done with No.30 in the designer menu or EDTOBJAUT OBJ (YMDLLIBRFA) OBJTYPE (*DTAARA).
<Please see attached file for image>
id="_x0000_i1025" src="http://comm.support.ca.com/csupport/servlet/servlet.ImageServer?oid=00D300000006yn4&esid=0180c000012K52y">Attachments
Feedback
Yes
No
Powered by
