Working with UAMS › Implementing Security for the First Time

Implementing Security for the First Time

When a region starts for the first time, the following UAMS definitions are automatically generated:

• Sample group definitions
• Sample model definitions

  Note: Sample group definitions and sample model definitions do not apply to CA SOLVE:FTS, CA SOLVE:Access Session Management, CA SOLVE:InfoMaster, and CA SOLVE:NetMail.

• Background user IDs

  Note: All background user definitions are linked to the $RMBUSER group definition.

If any of the default background group definitions are not defined in UAMS, you can create them by running $NMUAINI, which builds any of the definitions that do not already exist.

Note: For CA SOLVE:FTS, CA SOLVE:Access, CA SOLVE:InfoMaster, and CA SOLVE:NetMail, you must create your groups manually, because no default groups are created and the $NMUAINI procedure is not available.

To run $NMUAINI

1. Enter CMD from the primary menu to display the Command Entry panel.
2. Enter $NMUAINI at the command prompt (===>).

Sample Group Definitions

The following group definitions are created:

• $RMADMIN—administrators
• $RMOPER—operators
• $RMNOPER—network operators
• $RMMON—monitors
• $RMBUSER—background users

You can use these group definitions to simplify the creation of user definitions.

If used as distributed, these groups also implement resource-level security.

Sample Model Definitions

The following model definitions are created:

• $MDADMIN—corresponding to group $RMADMIN
• $MDOPER—corresponding to group $RMOPER
• $MDNOPER—corresponding to group $RMNOPER
• $MDMON—corresponding to group $RMMON

No model is defined for $RMBUSER, because modeling is not used with background users.

You can use the generated model and group definitions in conjunction with NMSAF.

Background User IDs

The following UAMS background user definitions (where nnnn is the domain ID) are defined when a region is started for the first time.

Note: The AOM procedure does not apply to CA SOLVE:FTS, CA SOLVE:Access, CA SOLVE:InfoMaster, and CA SOLVE:NetMail. The CNM procedure applies only to CA NetMaster NM for SNA.

Background User Considerations for Existing UAMS File

If you set up your region by using a pre-existing UAMS file in which the background users are already defined for your region, those background user definitions are not replaced. If this is the case, both of the following happen:

• The following message is displayed in the job log:

  N10107 USERID xxxxBSYS NOT AUTHORIZED FOR REQUESTED COMMAND
  

• Parameter group ABENDCMD fails.

To enable the new region to work correctly, you must update those background user definitions by associating the definitions to the $RMBUSER group ID. To do this:

1. Enter /UAMS to access the UAMS maintenance function.
2. Update each of the background user IDs by entering $RMBUSER in the Group ID field.
3. Press F3 to file the changes, and again to exit.
4. Enter CMD to display the Command Entry panel.
5. Enter the SUBMIT background-name SIGNON command at the command prompt to invoke the changes.

   Note: background-name is the last four characters of the background user ID, for example, BSYS.

6. Repeat step 5. for each of the background user IDs that you changed in step 2.
7. Press F3 to exit from the Command Entry panel.

The $RMBUSER group ID provides the minimum security settings needed for a background user. However, additional settings can be added to meet your requirements.

Note: This process can be done at any stage, including during initial customization when the region is first started.