When you specify the /PRINTFILE qualifier, you can specify only a spooled device name or a file name. The default for this qualifier is whatever sign-in characteristics are currently defined in the definition you are modifying.

The DDU MODIFY command does not invoke an editor.

Notes

Changes to definitions go into effect after you use one of the following commands:

• ACMS/RESET TERMINALS
• ACMS/START TERMINALS
• ACMS/START SYSTEM

The DDU MODIFY command does not invoke an editor.

Examples

DDU> MODIFY TTE3 /NOCONTROLLED
      

This command removes the Controlled characteristic from terminal TTE3. Users log in directly to OpenVMS at terminal TTE3.

DDU> MODIFY TTE4 /AUTOLOGIN=EVARD /CONTROLLED
      

This command assigns the Autologin and Controlled characteristics to terminal TTE4. User EVARD signs in directly to ACMS at terminal TTE4 by pressing the [Return] and typing a password.

DDU> MODIFY TTE5 /PRINTFILE=SPOOLDEV::TXA0:
      

This command assigns the Printfile characteristic to terminal TTE5 and specifies spooled device SPOOLDEV::TXA0: as the device for any DECforms panel screens to be printed when the user presses the Print key.

Removes a DDU definition from the device authorization file.

Format

REMOVE device-name

Parameters

device-name

The name of the device. Do not include a colon (:) when you specify a device name. The device name can be a logical name, a physical device name, or a group device name. See Table 2-1 for a list of the DDU group device names.

Privileges Required

None

Notes

To restrict a terminal to OpenVMS use only, delete the definition for the $ALL group device name (if the device authorization file contains one), and then delete the definition for the terminal.

You cannot remove the DEFAULT definition from the DDU device authorization file.

Changes to definitions go into effect after you use one of the following commands:

• ACMS/RESET TERMINALS
• ACMS/START TERMINALS
• ACMS/START SYSTEM

Examples

DDU> REMOVE TTE5
Device TTE5         has been removed from the database
 
      

This command deletes the device definition for TTE5. If the device authorization file does not contain a $ALL definition, this command removes terminal TTE5 for use with ACMS.

DDU> REMOVE $ALL
Device $ALL         has been removed from the database
 
      

This command deletes the $ALL definition. The command deauthorizes all terminals that do not have individual device definitions.

Changes the device name in a DDU definition.

Format

RENAME old-device-name new-device-name

Command Qualifiers	Default
/[NO]AUTOLOGIN=user-name	From old definition
/[NO]CONTROLLED	From old definition
/PRINTFILE = print-file-spec spooled-device-name	From old definition

Privileges Required

None

Parameters

old-device-name

The device name in the definition you are changing. The device name can be a logical name, a physical device name, or a group device name. Do not include a colon (:) when you specify a device name. See Table 2-1 for a list of the DDU group device names.

new-device-name

The new name for the device. The new device name cannot already exist in the device authorization file. See the description of old-device-name for syntax rules.

Qualifiers

/[NO]AUTOLOGIN=user-name

The /AUTOLOGIN qualifier enables automatic sign-ins for ACMS-controlled terminals. With automatic sign-in enabled, the user does not need to enter a user name to sign in to ACMS. If a password is required, the user receives the password prompt after pressing [Return]. If a password is not required, the user is signed in to ACMS as soon as [Return] is pressed on the terminal's keyboard.

ACMS places the user name you specify with the /AUTOLOGIN qualifier in the device authorization file and uses that user name each time a user presses [Return] at that terminal. The user name can contain 1 through 12 characters.

The /AUTOLOGIN qualifier has no effect unless the terminal has the Controlled sign-in characteristic. Assign a Controlled sign-in characteristic by specifying the /CONTROLLED qualifier. Disable automatic sign-ins with the /NOAUTOLOGIN qualifier. The default for this qualifier is whatever sign-in characteristics are defined in the original definition.

/[NO]CONTROLLED

The /CONTROLLED qualifier assigns the Controlled sign-in characteristic to a device. Users at application port terminals with the Controlled sign-in characteristic sign in directly to ACMS. Users at dedicated service port terminals sign in either directly to ACMS or not, depending on the node they connect to at the "Local>" prompt. See Section 2.11 for a description of application ports and dedicated service ports.

The /NOCONTROLLED qualifier assigns the Not Controlled sign-in characteristic to a device. Users at terminals with the Not Controlled characteristic log in directly to OpenVMS. For access to ACMS, a user must enter the ACMS/ENTER command.

When you specify the /CONTROLLED qualifier, you can specify only a physical device name or the group device names TT and LT. See Table 2-1 for a description of the DDU group device names. The default for this qualifier is whatever sign-in characteristics are defined in the original definition.

Note The ACMS Terminal Subsystem Controller (TSC) does not support dialup lines as ACMS-controlled terminals. Because the TSC keeps a channel to ACMS-controlled terminals even when the user signs out, the modem does not receive any hangup notification. If you operate a terminal using ACMS over dialup lines, you must first log in to OpenVMS, and then issue the ACMS/ENTER/NORETURN command. The /NORETURN qualifier deletes the OpenVMS process after you enter ACMS.

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

The /PRINTFILE qualifier assigns the Printfile characteristic to a device. The PRINT response must appear in the form source IFDL file, and a print key must also be defined there. When the user presses the print key, the DECforms panel screens automatically are sent to the print file or spooled device specified after the /PRINTFILE qualifier.

When you specify the /PRINTFILE qualifier, you can specify only a spooled device name or a file name. The default for this qualifier is whatever sign-in characteristics are currently defined in the original definition.

Notes

You cannot rename the DEFAULT definition.

Changes to definitions go into effect after you use one of the following commands:

• ACMS/RESET TERMINALS
• ACMS/START TERMINALS
• ACMS/START SYSTEM

Examples

DDU> RENAME TTE7 TTE6 /CONTROLLED
      

This command changes the device name of terminal TTE7 to TTE6 and assigns the Controlled sign-in characteristic. Terminal TTE7 is no longer authorized.

DDU> RENAME TTE6 TTE7 /NOCONTROLLED
      

This command changes the device name of terminal TTE6 to TTE7 and removes the Controlled characteristic from the definition. Users log in to OpenVMS from terminal TTE7 and enter ACMS using the ACMS/ENTER command. Terminal TTE6 is no longer authorized.

Displays DDU definitions.

Format

SHOW device-name

Command Qualifier	Default
/BRIEF	Full definition

Privileges Required

None

Parameters

device-name

The name of the device. Do not include a colon (:) when you specify a device name. The device name can be a logical name, a physical device name, a group device name, or the wildcard character (*). See Table 2-1 for a list of the DDU group device names. You can use the wildcard character as a prefix, a suffix, or both to specify a partial device name, for example, TT*, *TT, or *TT*.

Qualifiers

/BRIEF

Displays only device names. DDU displays complete definitions by default.

Notes

To display all definitions, use the wildcard character (*) as the parameter.

Examples

DDU> SHOW  *
Device Name:            DEFAULT         NOT CONTROLLED
No Autologin
 
Printfile:
 
Device Name:            LT              NOT CONTROLLED
No Autologin
 
Printfile:
 
Device Name:            LTA902          CONTROLLED
Autologin Username:     TURKLES
 
Printfile:
 
Device Name:            TT              NOT CONTROLLED
No Autologin
 
Printfile:
 
Device Name:            TTB5            NOT CONTROLLED
No Autologin
 
Printfile:
 
Device Name:            VTA65           NOT CONTROLLED
No Autologin
 
Printfile:
 
      

This command displays the full device definitions for all devices authorized in the device authorization file.

DDU> SHOW * /BRIEF
Device Name:    DEFAULT     
Device Name:    LT
Device Name:    LTA901      
Device Name:    LTA902      
Device Name:    LTA903      
Device Name:    LTA904      
Device Name:    PT          
Device Name:    RT          
Device Name:    TT          
Device Name:    TTA9        
Device Name:    TTB5        
Device Name:    TTE5        
Device Name:    VT          
Device Name:    VTA65       
      

This command displays just the device names for all devices authorized in the device authorization file.

DDU> SHOW TTE4
Device Name:          TTE4             CONTROLLED
Autologin Username:   MILLER
      

This command displays the full device definition for terminal TTE4.

DDU> SHOW VT
Device Name:           VT               NOT CONTROLLED
No Autologin
      

This command displays the device definition that authorizes virtual terminals to have access to your ACMS system.

DDU> SHOW *E* 
Device Name:           DEFAULT          NOT CONTROLLED 
No Autologin
 
Printfile:
Device Name:           TTE5             NOT CONTROLLED
No Autologin
Printfile:     SPOOLDEV::TXA0:
 
 
Device Name:           TTE6             NOT CONTROLLED
No Autologin
      

This command displays all device definitions for terminals containing the letter E.

This chapter contains reference information and examples for the ACMS User Definition Utility (UDU) commands. See Chapter 3 for more information on the UDU commands and their functions.

Authorizes and assigns sign-in characteristics to ACMS users by adding UDU definitions to the user authorization file (ACMSUDF.DAT). You can use qualifiers to assign sign-in characteristics or let new definitions receive information from the UDU DEFAULT definition.

Format

ADD user-name

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

Privileges Required

None

Parameters

user-name

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

Qualifiers

/[NO]AGENT

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 Command Process (CP) and the Queued Task Initiator (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 DEFAULT definition.

/[NO]DISPLAY_MENU

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 DEFAULT definition.

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

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

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. When you specify the TASK keyword, you must also specify an application name with the APPLICATION keyword.

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

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

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. When you specify the TASK keyword, you must also specify an application name with the APPLICATION keyword.

/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 DEFAULT 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. If you do not specify the /MDB qualifier, the name of the menu database file is taken from the DEFAULT 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 DEFAULT definition. If there is no path name defined in the DEFAULT 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

Create a user definition for the CP using the /AGENT qualifier. This action authorizes the CP as an agent.

Specifying the $ALL user name authorizes and assigns sign-in characteristics to users who do not have separate definitions. If the user authorization file, ACMSUDF.DAT, does not contain a $ALL definition, each ACMS user needs a separate definition.

The menu database file, menu path names, and OpenVMS account must be created before a user can sign in. However, you can add a menu database file specification or default menu path name to a UDU definition before the menu database file or menu path name exists. You can create a definition for a user before the user has an OpenVMS account.

Examples

UDU> ADD CONNOR 
      

This command creates a new definition for the user name CONNOR. Because the command has no qualifiers, the new definition receives information from the DEFAULT definition.

UDU> ADD CMDPRCSS /AGENT
      

This command authorizes the CP as an agent. ACMS requires you to create a user definition for the CP and also for any other task submitting agent that processes tasks running under user names different from that of the Command Process. The user name of the Command Process (CMDPRCSS) is defined with the ACMSGEN Utility.

UDU> ADD $ALL /MENU=PERSONNEL
      

This command creates a $ALL definition authorizing all OpenVMS users to sign in to ACMS. The /MENU qualifier assigns the default menu path name PERSONNEL to the $ALL definition. The $ALL definition receives the remaining information from the DEFAULT definition. ACMS uses the $ALL definition for users who do not have separate user definitions.

UDU> ADD CONNOR /MDB=WORKDISK$:[CONNOR]ACMS.MDB /MENU=PERSONNEL
      

This command creates a new definition for CONNOR. The /MDB and /MENU qualifiers assign to CONNOR the menu path name PERSONNEL and the menu database file WORKDISK$:[CONNOR]ACMS.MDB.

UDU> ADD BELLOW /INITIAL=(APPLICATION=ACCOUNTING, -
_UDU> TASK=LOGGING_PROG,SELECTION_STRING="LOG.DAT")
      

This command creates a new definition for BELLOW. The /INITIAL qualifier specifies that the task LOGGING_PROG in application ACCOUNTING is run when BELLOW signs in. Task LOGGING_PROG displays the file LOG.DAT, which verifies BELLOW's booking information.

Adds a user proxy to the ACMS proxy file (ACMSPROXY.DAT). Before you can use the ADD /PROXY command, you must have already created a proxy file using the CREATE /PROXY command.

Format

ADD /PROXY remote-node::remote-user local-user

Parameters

remote-node

Specifies a remote node name (1 to 6 alphanumeric characters). If you substitute an asterisk, the specified <remote-user> on all nodes is authorized to submit tasks under the user name specified by the <local-user> parameter.

remote-user

Specifies the user name of a user at a remote node. A valid user name is a string of 1 to 12 alphanumeric characters and can contain underscores and dollar signs. If you use an asterisk, all users on the specified <remote-node> are authorized to submit tasks under the user name specified by the <local-user> parameter.

local-user

Specifies the user name of the user on the local application node. If you specify an asterisk, the local user name is the same as the remote user name. You can specify only one <local-user> for each <remote-node>::<remote-user> combination.

Notes

UDU does not check that the <local-user> name you enter is unique. Use the SHOW /PROXY *::* command to obtain a list of <local-user> names.

When you add a proxy, UDU interprets the <remote-node>::<remote-user> and <local-user> parameters as text strings, and each parameter is stored as specified, including any asterisks. However, at run time, ACMS interprets the asterisk as a wildcard.

You cannot partially wildcard any parameters with the ADD /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."

Before you create a proxy file, set default to the appropriate directory, such as SYS$SYSTEM, or define a logical for the proper directory location for the proxy file.