Reference Guide › Command Reference › GENHS Command

GENHS Command

Use the GENHS command to add rules history special comments (*HS=) to or delete rules history special comments from a directory entry. The GENHS command is valid only if the Rules Facility is installed at your site and only for active user IDs.

GENHS userid [number]

Authorizations

When the GENHS command is used in a CMS EXEC, the issuing user ID should have NOPASS GENHS authorization in the AUTHORIZ CONFIG file. This authorization prevents the issuer from being prompted for a password for each change.

Definitions

userid

Specifies the user directory entry in which *HS= special comments are to be added or deleted. The user ID must be an active user ID.

number

Is the number of *HS= special comments the directory entry contains. This can be any integer from 1 to 99, or blank to remove all history special comments from the user directory entry.

Description

The GENHS command adds the specified number of *HS= (rules history) special comments to the specified user directory entry. *HS= special comments are optional. They contain information about LOGONBY Facility, AUTOLOG, LINK, LOGON, LOGON BY, and XAUTOLOG attempts to a user’s virtual machine or minidisks if attempts are controlled by a CA VM:Secure rule with the HISTORY option specified.

If you specify a number of special comments that is greater than the number currently in the directory entry, CA VM:Secure adds the number it needs to total the number you specified. For instance, if you specify 5 history special comments for a user ID and that user ID currently has none, CA VM:Secure adds 5; if you specify 5 and that user ID currently has 4, CA VM:Secure adds 1.

If you specify a number of history special comments that is less than the number currently in the directory entry, CA VM:Secure removes as many as it needs to leave the number you specified. For instance, if you specify 5 history special comments for a user ID and that user ID currently has 10, CA VM:Secure removes 5; if you specify 5 and that user ID currently has 8, CA VM:Secure removes 3. If you specify 0, CA VM:Secure removes all history special comments from that user directory entry.

If you include *HS= special comments in directory entries, you must also plan for an initial increase in the size of the directory entries.

Use *HS= special comments and rules with the HISTORY option with care since they add overhead to the rules evaluation process. A larger block size for the DRCT minidisk may improve performance or reduce disk space if the addition of history special comments causes the majority of directory entries to use an additional data block at the current block size.

Examples

• To make sure that user ID LILITHS’s directory entry contains five *HS= special comments, enter:

  vmsecure genhs liliths 5
  

• To make sure that several directory entries have just three *HS= special comments, do the following:
  1. Create an EXEC file named CMS EXEC:

     vmsecure query users (manager carlat exec
     

  2. Modify the EXEC file created by the QUERY command:

     copyfile cms exec a (spec
     

     CMS prompts:

     ENTER SPECIFICATION LIST:
     

     Enter the following to specify three special comments:

     1‑15 1 /3/ 17
     

  3. Enter the command:

     cms vmsecure genhs
     

Note: For more information about using the Rules History special comment, see the section, "*HS= (Rules History), in the chapter "Special Comment Reference" of the Administration Guide.