MAINT Command

Contents
vmx32besp
Contents
Use the MAINT command to allow users to make directory changes for their own directory entries, and to allow directory managers to define, modify, and manage directory entries.
MAINT {"Parms"}   Parms:   Account 
newacct
 [NEXTLOG | TEMP | IMMED] | DEFine 
oldvaddr
 
newvaddr
| Delete 
vaddr
| DIstrib 
newdist
HELP
 | ? | Ipl [
sysname
 | 
vaddr
 ] [PARM 
parameters
] | Link  
ownerid
 v
addr1 vaddr2
 [ mode] | MACHINe [XA | ESA | XC | Z] | Manage 
entry subfunction
| MDpw [
vaddr
] | MGrid | MInidisk
vaddr
| Option 
attribute
 {ON | OFF}  | Password | Review |
RLink
vaddr
|
SCratch
vaddr
|
Storage
{
sizeK
|
sizeM
} |
Terminal
symbolname
{ON
|
OFF
|
char
|
hex
}
Authorizations
To perform user functions on your own user ID, you must have MAINT
subfunction
authorization through a GRANT MAINT
subfunction
record in the AUTHORIZ CONFIG file, where
subfunction
is the specific subfunction you want to use.
To perform user functions on another user ID, you must have MAINTMAN
userid
USER
subfunction
authorization through a GRANT MAINTMAN
userid
USER
subfunction
record in the AUTHORIZ CONFIG file, where
subfunction
is the specific subfunction you want to use.
To perform management functions, you must have MAINTMAN
userid subfunction
authorization through a GRANT MAINTMAN
userid subfunction
record in the AUTHORIZ CONFIG file.
Definitions
  • [Account
    newacct
    [ NEXTLOG | TEMP | IMMED]]
    Changes your primary account number. If
    CA VM:Secure
    is interfaced with VM:Account,
    CA VM:Secure
    allows only immediate (IMMED) changes to account numbers. Otherwise, NEXTLOG is the default.
    Important:
    CA VM:Secure
    requires the OPTION D84NOPAS record in its directory entry if the following conditions are true:
    • MAINT MANAGE is being used to change a user account number and the ACCOUNT TEMP or ACCOUNT IMMED options are specified.
    • The
      CA VM:Account
      interface is not implemented.
    • The user ID whose account number is being changed is an LBYONLY user.
  • [DEFine oldvaddr newvaddr]
    Changes the virtual address of one of your minidisks from
    oldvaddr
    to
    newvaddr
    .
    CA VM:Secure
    updates directory links to
    oldvaddr
    to reflect the new virtual address. Minidisk passwords for the minidisk remain unchanged.
  • [Delete
    vaddr
    ]
    Deletes the directory link to the minidisk at
    vaddr
    .
  • [DIstrib
    newdist
    ]
    Changes the distribution code associated with your spooled output to
    newdist
    .
  • [
    HELP 
    | ?]
    Displays a brief list of the MAINT command functions and their operands. HELP is the default if you do not enter a function.
  • [Ipl [
    sysname
    |
    vaddr
    ] [PARM
    parameters
    ]]
    Changes the entire content of your IPL statement. The variable
    sysname
    is the system to IPL at logon. The variable
    vaddr
    is the virtual device address of the device to IPL at logon. If no values follow IPL,
    CA VM:Secure
    removes any existing IPL statement from your directory entry.
  • [Link
    ownerid vaddr1 vaddr2
    [
    mode
    ]]
    Defines a directory link to another user’s minidisk. Directory links are performed for you at logon. To define a directory link, you must specify the minidisk password for the ownerid’s minidisk (
    vaddr1
    ) and specify a virtual address (
    vaddr2
    ) not used by your virtual machine. You can specify the link mode to use through
    mode
    , or use the default mode "R".
    CA VM:Secure
    with the Rules Facility will prompt or not prompt for a password based on the behavior of the CP LINK command for the system on which it is running.
    If the Rules Facility is installed, a rule must exist that allows you to link to the other user’s minidisk. If no rule is found, the site-defined default is applied.
  • [MACHINe [ XA | ESA | XC | Z ]
    Switches your MACHINE architecture between the available options. The default is determined by the setting in the
    VMSECURE
    GLOBALS file.
  • [Manage
    entry subfunction
    ]
    For directory managers; defines USER or IDENTITY directory entries or manages existing USER, IDENTITY, or SUBCONFIG entries. You can manage only one
    entry
    per session and cannot manage your own directory entry. When you use this parameter you are placed in a VM READ state, from which you can enter one of the MAINT MANAGE command subfunctions listed below.
    MAINT MANAGE subfunction
    Purpose
    ?
    Displays the MAINT MANAGE subfunctions
    Activate
    Activates a USER entry that is on hold and enables any file spaces in all file pools that
    CA VM:Secure
    controls
    Comments
    Invokes XEDIT to edit comment records in a user directory entry.
    DISKMove [
    vaddr
    ]
    Moves a minidisk in a USER, IDENTITY, or SUBCONFIG directory entry to a new location.
    The default virtual address is 191
    End
    Terminates the MAINT MANAGE function and returns control to CMS
    Hold
    Places an existing USER directory entry on hold.
    Disables any user file spaces in all file pools that
    CA VM:Secure
    controls.
    Newdisk [
    vaddr
    ]
    Defines and optionally formats a new minidisk in a USER, IDENTITY, or SUBCONFIG directory entry.
    The default virtual address is 191
    NEWUser
    Creates a USER or IDENTITY entry and optionally enrolls the user in file pools that
    CA VM:Secure
    controls. You can identify a sample PROFILE EXEC file to copy to the 191 minidisk or top-level directory. To do so, place the
    *SP=
    special comment in the skeleton or input file. If a sample profile is available or specified on a *SP= special comment, that profile is copied to the top-level directory for the user as PROFILE EXEC. If a PROFILE EXEC file already exists in the user’s top-level directory, a sample profile specified on a *SP= special comment is not copied.
    For more information about special comments, see Special Comment Reference.
    REMove
    Removes a USER or IDENTITY entry from the directory and deletes any user file spaces from all file pools that
    CA VM:Secure
    controls. With this subfunction, when the command deletes a minidisk that is on a pack that is under 
    CA VM:Secure
    control,
    CA VM:Secure
    deletes links to the deleted that minidisk from the directory. An IDENTITY entry can only be removed if it has no BUILD statements.
    REView
    Invokes XEDIT to display a directory entry
    Scratch [
    vaddr
    ]
    Removes and formats a minidisk from a USER, IDENTITY, or SUBCONFIG directory entry; the default virtual address is 191. With this subfunction, when the command deletes a minidisk that is on a pack that is under
     
    CA VM:Secure
    control,
    CA VM:Secure
    deletes links to that deleted minidisk from the directory.
    User
    parameters
    Invokes the MAINT subfunctions for the directory entry being managed by the MAINT MANAGE function
  • [MDpw [
    vaddr
    ]]
    Displays the passwords for your minidisks. If
    vaddr
    is not specified, the command displays passwords for all your minidisks. Passwords may be masked at your site.
  • [MGrid]
    Displays the user ID of your directory manager.
  • [MInidisk
    vaddr
    ]
    Prompts you for a new link mode and read, write, or multiple passwords for your minidisk at virtual address
    vaddr
    . If you enter a null at a prompt,
    CA VM:Secure
    sets all values that were not previously set to nulls. The values can include link mode, read password, write password, and multiple write password.
  • [Option
    attribute
    ON | OFF]
    Selects (ON) or removes (OFF) various attributes, specified by
    attribute
    , associated with your user ID.
    Supported attributes are:
    • CONCEAL
    • MIH
    • TODENABLE
    • CPUID
    • NOVF
  • [Password]
    Changes your logon password. If you are using traditional passwords, you may change your password to anything that does not include spaces, a left or right parenthesis, or one of the IBM reserved passwords.If you are using password phrases, your password might contain blanks and can contain any character that you can type on your keyboard.
  • [Review]
    Creates a read-only XEDIT session of all directory control statements in your directory entry. It provides information you need for the DEFINE, DELETE, LINK, MINIDISK, MDPW, RLINK, and SCRATCH functions, such as existing directory links and all virtual addresses associated with your user ID.
  • [RLink
    vaddr
    ]
    Reviews and optionally removes any directory links that other users may have defined to your minidisk at virtual address
    vaddr
    . This function is particularly useful when you determine that data on your minidisk should no longer be shared with other users. Review any existing directory links to determine if the user still has access to your minidisk.
  • [SCratch
    vaddr
    ]
    Deletes your minidisk at virtual address
    vaddr
    .
    CA VM:Secure
    automatically removes directory links to the minidisk being scratched from other users’ directory entries.
  • [Storage
    size
    K |
    size
    M]
    Changes the amount of virtual storage your user ID is set up with at logon. Virtual storage can be modified after logon with the CP DEFINE STORAGE command.
  • [Terminal
    symbolname
    { ON | OFF |
    char
    |
    hex
    }]
    Selects or removes values for various line editing symbols associated with your user ID. ON with a symbol name selects the default character to use for that line editing symbol; a character (char) or a hexadecimal value (hex) with a symbol name uses that character or hexadecimal value for that line editing symbol. OFF with a symbol name removes that line editing symbol. Changeable line editing symbols are:
    • CHardel
    • LINEDel
    • EScape
    • LINENd
Description
Some forms of the MAINT command depend on line-mode interaction with the issuing user ID.
Valid replies to prompts are documented in
Messages
.
If you prefer a full-screen interface for management functions, use the MANAGE command. If you want to use commands that do not require interaction with the issuing user ID, use the API commands.
For a list of API commands, see Application Programming Interface Commands.