# Compaq ACMS for OpenVMS
Managing Applications

Previous | Contents | Index

# LIST /PROXY Command (UDU>)

> Writes all the proxies in the ACMS proxy file to the output file ACMSPROXY.LIS. You can use the /OUTPUT qualifier to specify a different output file name.

## Format

> LIST /PROXY

Command Qualifier | Default
--- | ---
/OUTPUT=file-spec | ACMSPROXY.LIS

## Qualifiers

> ### /OUTPUT=file-spec

> Use this qualifier to specify a file name for the output listing file. Replace the parameter <file-spec> with the new output file name, which can be any valid OpenVMS file specification.

> By default, the listing file is created in the current directory with the name ACMSPROXY.LIS.

## Note

> Creates a listing file of all the proxies in the ACMS proxy file. You can use the optional /OUTPUT qualifier to override the default listing file specification.

##

### Examples

#1
    UDU> LIST /PROXY

> This command creates a listing file of all the proxies in the ACMS proxy file. The listing file is created in the current directory and is named ACMSPROXY.LIS.

#2
    UDU> LIST /PROXY /OUTPUT=DISK1$:[DATA]ALL_REMOTE_USERS.LIS

> This command creates the listing file ALL_REMOTE_USERS.LIS in the DISK1$:[DATA] directory. The listing file contains all proxies in the ACMS proxy file.

# MODIFY Command (UDU>)

Changes the user information by allowing you to change information in UDU definitions.

## Format

> MODIFY user-name

> Command Qualifiers | Default
> --- | ---
> /[NO]AGENT | From existing definition
> /[NO]DISPLAY_MENU | From existing definition
> /[NO]FINAL=(keyword[,...]) | From existing definition
> /[NO]INITIAL=(keyword[,...]) | From existing definition
> /LANGUAGE[=language-name] | From existing definition
> /MDB=menu-database-file | From existing definition
> /MENU[=menu-path-name] | From existing definition
> /PRINTFILE = print-file-spec spooled-device-name | From existing definition
> /[NO]SKIPMENULANGUAGE | From existing definition

## Privileges Required

> None

## Parameters

> ### user-name

> The OpenVMS user name in the definition you are changing. The user name can be $ALL.

## Qualifiers

> ### /[NO]AGENT

> The /AGENT qualifier enables an agent to submit a task that has a user name different from the user name of the agent process. You must use the /AGENT qualifier to authorize the CP and the QTI as agents. If your system has other agent programs that submit tasks of this type, you must also authorize them with the /AGENT qualifier. You must use the /AGENT qualifier for any user name that a detached task runs under. Use the /NOAGENT qualifier when an agent program no longer submits tasks for processing that run under user names other than the submitting agent program. The default is taken from the existing definition.

> ### /[NO]DISPLAY_MENU

> The /DISPLAY_MENU qualifier enables the menu display identified in the user's definition and the Selection: prompt once the user signs in. A menu is identified by a menu path name and a menu database file. If a user's definition has the NODISPLAY_MENU characteristic, ACMS displays only the Selection: prompt after the user signs in, without a full default menu. The /NODISPLAY_MENU qualifier disables the menu display. The default is taken from the existing definition.

> ### /[NO]FINAL=(keyword[,...])

> Specifies a task that is run when the user exits from ACMS. The default is taken from the existing definition.

> You can specify one or more of the following keywords. If you specify more than one keyword, you must enclose the keywords in parentheses.

> - APPLICATION=application-name
>   Specifies the application in which the final task is run. When you specify the APPLICATION keyword, you must also specify a task name with the TASK keyword.
> - [NO]IGNORE_ERROR
>   Specifies that errors in the final task are ignored. If an error occurs in the final task, ACMS does not display an error message or record information about the error in the audit trail log file.
> - [NO]SELECTION_STRING="string"
>   Specifies a parameter required by the final task. For example, if the final task is an editor, "string" is the file specification of the file to be edited. Enclose the string in quotation marks.
> - TASK=task-name
>   Specifies the name of the final task.

> ### /[NO]INITIAL=(keyword[,...])

> Specifies the task that is run when the user enters the ACMS environment. The default is taken from the existing definition.

> You can specify one or more of the following keywords. If you specify more than one keyword, you must enclose the keywords in parentheses.

> - APPLICATION=application-name
>   Specifies the application in which the initial task is run. When you specify the APPLICATION keyword, you must also specify a task name with the TASK keyword.
> - [NO]IGNORE_ERROR
>   Specifies that errors in the initial task are ignored. By default, if an error occurs in an initial task, an error message is displayed on the user's terminal, the reason for the error is recorded in the audit trail log, and the user is signed out of ACMS.
> - [NO]SELECTION_STRING="string"
>   Specifies a parameter required by the initial task. For example, if the initial task is an editor, "string" is the file specification of the file to be edited. Enclose the string in quotation marks.
> - TASK=task-name
>   Specifies the name of the initial task.

> ### /LANGUAGE[=language-name]

> Assigns a language to a user in a UDU definition. ACMS matches the language assigned to a user with the language assigned to a DECforms form layout and displays panels in the selected language. The default is taken from the existing definition.

> ### /MDB=menu-database-file

> Assigns a menu database file to a UDU definition. A menu database file is a file of run-time menu definitions created by the Application Definition Utility (ADU) BUILD command. The ACMS run-time system assumes ACMS$DIRECTORY as the default directory and .MDB as the default file type for menu database files in UDU definitions. The default is taken from the existing definition.

> ### /MENU[=menu-path-name]

> Assigns a menu to a UDU definition. The menu path name is the location of a run-time menu definition in a menu database file. Users cannot see menus whose path names are higher in the menu tree than their default menu path names. Path names for all menus except the highest menu consist of strings of menu keywords. If you do not know the path name to include with the /MENU qualifier, you can derive the menu path name from menu keywords, as explained in Compaq ACMS for OpenVMS ADU Reference Manual.

> You can define menu entries that contain slashes in the menu definition; however, you cannot specify menu paths containing these slashes in the UDU.

> For example, the following format is not allowed:

>     UDU> MODIFY SMITH /MENU="TOP/V32.SUBMENU"

> If you do not specify a menu path name, the user receives the path name defined in the existing definition. If there is no path name defined in the existing definition, a blank path name is assigned. When signing in with a blank path name assigned, the user receives the top menu in the menu database file.

> ### /PRINTFILE=print-file-spec
> /PRINTFILE=spooled-device-name

> Use this qualifier to specify a file name or spooled device name for a user. When a form is enabled, ACMS uses the Printfile specification for a device assigned in DDU, if it is available. If it is not, ACMS uses the Printfile specification for the user.

> To use the Printfile feature, you must also include a PRINT response step in the DECforms source IDFL file that contains the specifications of the panel that you want to print.

> ### /[NO]SKIPMENULANGUAGE

> Use this qualifier with the /LANGUAGE qualifier to specify that a language is to be assigned to a user for all DECforms forms except menu forms. For example, with the /SKIPMENULANGUAGE qualifier you can specify that DECforms display all panels in French except menu panels.

## Notes

> To change the $ALL definition, use $ALL as the user name.

> The UDU MODIFY command does not invoke an editor, unlike the MODIFY command of the ACMS Application Definition Utility (ADU).

##

### Examples

#1
    UDU> MODIFY CONNOR /MENU=PERSONNEL

> This command assigns CONNOR the menu path name PERSONNEL, a menu below the highest menu in the menu database file.

#2
    UDU> MODIFY CONNOR /MDB=WORKDISK$:[CONNOR]ACMS.MDB

> This command assigns CONNOR the menu database file ACMS.MDB on WORKDISK$:[CONNOR].

#3
    UDU> MODIFY ZEKE /INITIAL=(TASK=NEW_DATA_INFO)

> This command modifies the definition for ZEKE specifying NEW_DATA_INFO as the new initial task. The name of the application is taken from the existing definition.

#4
    UDU> MODIFY WINSTON /PRINTFILE=SPOOLDEV::TXA0:

> This command modifies the definition for WINSTON specifying SPOOLDEV::TXA0: as the spooled device on which any DECforms print files are to be printed.

# REMOVE Command (UDU>)

> Removes UDU definitions from the user authorization file.

## Format

> REMOVE user-name

## Privileges Required

> None

## Parameters

> ### user-name

> The OpenVMS user name in the definition you are deleting. The user name can be $ALL.

## Notes

> To prevent a user from signing in to ACMS, remove the $ALL definition if the database contains one, or remove the definition for the user.

> You cannot delete the DEFAULT definition.

##

### Examples

#1
    UDU> REMOVE CONNOR

> This command deletes the user definition for CONNOR.

#2
    UDU> REMOVE $ALL

> This command deletes the $ALL definition.

# REMOVE /PROXY Command (UDU>)

> Removes the specified proxy from the ACMS proxy file (ACMSPROXY.DAT).

## Format

> REMOVE /PROXY remote-node::remote-user

## Parameters

> ### remote-node

> Specifies a remote node name (1 to 6 alphanumeric characters). Specify an asterisk to remove a proxy that contains an asterisk for the remote node.

> ### remote-user

> Specifies the user name of a user at a remote node. A valid remote user name is a string of 1 to 12 alphanumeric characters and can contain underscores and dollar signs. Specify an asterisk to remove a proxy containing an asterisk for the remote user.

## Notes

> When you remove a proxy, UDU interprets the <remote-node>::<remote-user> and <local-user> parameters as text strings and removes the proxy as specified, including any asterisks. Specifying an asterisk for a parameter removes only a proxy that has an asterisk for that same parameter.

> You cannot partially wildcard any parameters with the REMOVE /PROXY command. For example, if a user specifies <remote-node>::<remote-user> as COMET::PERS*, UDU returns the error message, "Invalid remote user proxy specification."

> If the specified user is not in the file, UDU displays an error message stating that the user does not exist.

##

### Examples

#1
    UDU> SHOW /PROXY *::*
    Remote User: *::BICKFORD                 Local User: BICKFORD
    Remote User: COMET::*                    Local User: RENTAL_AGENT
    Remote User: COMET::BICKFORD             Local User: SUPERVISOR
    Remote User: COMET::PERSONNEL            Local User: PERSONNEL
    UDU> REMOVE /PROXY COMET::PERSONNEL
    UDU> SHOW /PROXY *::*
    Remote User: *::BICKFORD                 Local User: BICKFORD
    Remote User: COMET::*                    Local User: RENTAL_AGENT
    Remote User: COMET::BICKFORD             Local User: SUPERVISOR

> In this example, the REMOVE command removes the proxy for COMET::PERSONNEL from the ACMS proxy file. This deletion removes the specific ACMS proxy access for user PERSONNEL on node COMET.

#2
    UDU> SHOW /PROXY *
    Remote User: *::BICKFORD                 Local User: BICKFORD
    Remote User: COMET::*                    Local User: RENTAL_AGENT
    Remote User: COMET::BICKFORD             Local User: SUPERVISOR
    UDU> REMOVE /PROXY COMET::*
    UDU> SHOW /PROXY *
    Remote User: *::BICKFORD                 Local User: BICKFORD
    Remote User: COMET::BICKFORD             Local User: SUPERVISOR

> In this example, the REMOVE command removes the proxy for COMET::*. This deletion removes ACMS proxy access for all users on node COMET except for the user name BICKFORD, who has a separate proxy. The proxy for *::BICKFORD is not removed, because the proxy is interpreted as a separate entity.

#3
    UDU> SHOW /PROXY *
    Remote User: *::BICKFORD                 Local User: BICKFORD
    Remote User: COMET::BICKFORD             Local User: SUPERVISOR
    UDU> REMOVE /PROXY *::BICKFORD
    UDU> SHOW /PROXY *
    Remote User: COMET::BICKFORD             Local User: SUPERVISOR

> In this example, the REMOVE command removes the proxy for *::BICKFORD. This deletion removes ACMS proxy access for user BICKFORD on every node except COMET::BICKFORD, which is interpreted as a separate entity.

# RENAME Command (UDU>)

> Changes the user names and, with qualifiers, other information in UDU definitions.

## Format

> RENAME old-user-name new-user-name

> Command Qualifiers | Default
> --- | ---
> /[NO]AGENT | From old definition
> /[NO]DISPLAY_MENU | From old definition
> /[NO]FINAL=(keyword[,...]) | From old definition
> /[NO]INITIAL=(keyword[,...]) | From old definition
> /LANGUAGE[=language-name] | From old definition
> /MDB=menu-database-file | From old definition
> /MENU[=menu-path-name] | From old definition
> /PRINTFILE = print-file-spec spooled-device-name | From old definition
> /[NO]SKIPMENULANGUAGE | From old definition

## Privileges Required

> None

## Parameters

> ### old-user-name

> The OpenVMS user name in the definition you are changing. The old user name can be $ALL.

> ### new-user-name

> The OpenVMS user name for the new definition. The new user name can be $ALL.

## Qualifiers

> ### /[NO]AGENT

> The /AGENT qualifier enables an agent to submit a task that has a user name different from the user name of the agent process. You must use the /AGENT qualifier to authorize the CP and the QTI as agents. If your system has other agent programs that submit tasks of this type, you must also authorize them with the /AGENT qualifier. You must use the /AGENT qualifier for any user name that a detached task runs under. Use the /NOAGENT qualifier when an agent program no longer submits tasks for processing that run under user names other than the submitting agent program. The default is whatever is defined in the definition you are renaming.

> ### /[NO]DISPLAY_MENU

> The /DISPLAY_MENU qualifier enables the menu display identified in the user's definition and the Selection: prompt once the user signs in. A menu is identified by a menu path name and a menu database file. If a user's definition has the NODISPLAY_MENU characteristic, ACMS displays only the Selection: prompt after the user signs in, without a full default menu. The /NODISPLAY_MENU qualifier disables the menu display. The default is whatever is defined in the definition you are renaming.

> ### /[NO]FINAL=(keyword[,...])

> Specifies a task that is run when the user exits from ACMS. If you do not specify the /[NO]FINAL qualifier, the default is taken from the definition you are renaming.

> You can specify one or more of the following keywords. If you specify more than one keyword, you must enclose the keywords in parentheses.

> - APPLICATION=application-name
>   Specifies the application in which the final task is run. When you specify the APPLICATION keyword, you must also specify a task name with the TASK keyword.
> - [NO]IGNORE_ERROR
>   Specifies that errors in the final task are ignored. If an error occurs in the final task, ACMS does not display an error message or record information about the error in the audit trail log file.
> - [NO]SELECTION_STRING="string"
>   Specifies a parameter required by the final task. For example, if the final task is an editor, "string" is the file specification of the file to be edited. Enclose the string in quotation marks.
> - TASK=task-name
>   Specifies the name of the final task.

> ### /[NO]INITIAL=(keyword[,...])

> Specifies a task that is run when the user enters the ACMS environment. The default is taken from the definition you are renaming.

> You can specify one or more of the following keywords. If you specify more than one keyword, you must enclose the keywords in parentheses.

> - APPLICATION=application-name
>   Specifies the application in which the initial task is run. When you specify the APPLICATION keyword, you must also specify a task name with the TASK keyword.
> - [NO]IGNORE_ERROR
>   Specifies that errors in the initial task are ignored. By default, if an error occurs in an initial task, an error message is displayed on the user's terminal, the reason for the error is recorded in the audit trail log, and the user is signed out of ACMS.
> - [NO]SELECTION_STRING="string"
>   Specifies a parameter required by the initial task. For example, if the initial task is an editor, "string" is the file specification of the file to be edited. Enclose the string in quotation marks.
> - TASK=task-name
>   Specifies the name of the initial task.

> ### /LANGUAGE[=language-name]

> Assigns a language to a user in a UDU definition. ACMS matches the language assigned to a user with the language assigned to a DECforms form layout and displays panels in the selected language. The default is taken from the definition you are renaming.

> ### /MDB=menu-database-file

> Assigns a menu database file to a UDU definition. A menu database file is a file of run-time menu definitions created by the ADU BUILD command. The ACMS run-time system assumes ACMS$DIRECTORY as the default directory and .MDB as the default file type for menu database files in UDU definitions. The default is whatever is defined in the definition you are renaming.

> ### /MENU[=menu-path-name]

> Assigns a menu to a UDU definition. The menu path name is the location of a run-time menu definition in a menu database file. Users cannot see menus whose path names are higher in the menu tree than their default menu path names. Path names for all menus except the highest menu consist of strings of menu keywords. If you do not know the path name to include with the /MENU qualifier, you can derive the menu path name from menu keywords, as explained in the Compaq ACMS for OpenVMS ADU Reference Manual.

> You can define menu entries that contain slashes in the menu definition, however, you cannot specify menu paths containing these slashes in the UDU.

> For example, the following format is not allowed:

>     UDU> MODIFY SMITH /MENU="TOP/V32.SUBMENU"

> If you do not specify a menu path name, UDU uses the path name defined in the definition you are renaming. If there is no path name already defined, the user receives a blank path name. When a blank path name is defined, the user receives the top menu in the menu database file when signing in.

> ###
> - /PRINTFILE=print-file-spec
> - /PRINTFILE=spooled-device-name

> Use this qualifier to specify a file name or spooled device name for a user. When a form is enabled, ACMS uses the Printfile specification for a device assigned in DDU, if it is available. If it is not, ACMS uses the Printfile specification for the user.

> To use the Printfile feature, you must also include a PRINT response step in the DECforms source IDFL file that contains the specifications of the panel that you want to print.

> ### /[NO]SKIPMENULANGUAGE

> Use this qualifier with the /LANGUAGE qualifier to specify that a language is to be assigned to a user for all DECforms forms except menu forms. For example, with the /SKIPMENULANGUAGE qualifier you can specify that DECforms display all panels in French except menu panels.

## Notes

> The new user name must be unique in the user authorization file. You cannot rename the DEFAULT definition.

##

### Examples

#1
    UDU> RENAME SMITH JAMISON

> This command changes the user name from SMITH to JAMISON.

#2
    UDU> RENAME SMITH JAMES /MENU=PERSONNEL

> This command changes the user name from SMITH to JAMES and changes the default menu path name in the definition to PERSONNEL.

Previous | Next | Contents | Index