Security system values: Security level
The Security level system value is also known as QSECURITY. You can use this system value to set the level of security for your system.
| Quick reference | |
|---|---|
| Location | From IBM® Navigator for i, select . Right-click on Security and click Properties, then select the General tab. |
| Special authority | All object (*ALLOBJ) and security administrator (*SECADM). |
| Default value | Protect from undocumented system interfaces (40). |
| Changes take effect | At the next restart of the system. |
| Lockable | Yes. |
What can I do with this system value?
You have the following options:
- No passwords are needed and users have authority to all resources (10)
- The system does not require a password to sign on. The user has access to all system resources. Security level 10 is not available unless your system is already running at this level. If you change from security level 10 to 20, 30, 40 or 50, you cannot change back to level 10.
- Passwords are required and users have authority to all resources (20)
- The system requires a user name and password to sign on. The user has access to all system resources. Only a security officer or someone with security administrator (*SECADM) authority can create user profiles.
- Passwords are required and users' access is based on their authority (30)
- All requirements of security level 20 are met. The user must have the specific authority required to access all system resources. Only user profiles created with security officer (*SECOFR) security class are given all object (*ALLOBJ) authority automatically.
- Protect from undocumented system interfaces (40)
- All requirements of security level 30 are met. Programs fail if they try to access objects through interfaces that are not supported. If a job specifies a user profile, users must have the use authority attribute to the profile in addition to the use authority attribute to the job they want to use.
- Enhance protection of system interfaces (50)
- All requirements of security level 40 are met. Programs fail if they try to pass unsupported parameter values to supported interfaces or if they try to access objects through interfaces that are not supported.