Security features provide integration of MCP based system software security with security in both your built applications.
Access to Ispecs might be restricted, based on the current user security details, which are established when a user station logs on to any application that is using Security features.
The built-in attribute Glb.UserCode enables record-level or attribute-level security to be implemented within your Ispec logic.
To implement more comprehensive security for an application, you can generate a Security Module (LSM) for that application, and use it to gather and store security information for your application. This security information is stored in the application database.
Using LSM, you can set up usercodes for an application, to provide access to different combinations of Ispecs or Reports, depending on the visibility awarded to the usercode. Various combinations of Ispecs or Reports can be grouped into lists. One or more such lists can be allocated to one or more different usercodes.
Notes:
Only the LSM program can be used to load and unload the LSM Security details.
User security information for built applications (as maintained by LSM) is not copied across hosts by the System Transfer process.
You can also use COMS usercode/transcode security to limit access.