Authorized OpenVMS users cannot sign in to ACMS until the system manager has also authorized them as ACMS users. The User Definition Utility (UDU) provides the capability to do this. Using the UDU, the system manager creates an ACMS database named ACMSUDF.DAT, located in the SYS$SYSTEM directory. When adding a user to the database, the system manager also specifies the default menu the user sees upon signing in to ACMS.

To add a new user to the ACMS database, perform the following steps:

1. Define UDU as a global symbol in your login command file. Then initialize the symbol by executing your login command file:

   $ UDU :== $ACMSUDU $ @LOGIN.COM $

2. Set the default directory to SYS$SYSTEM:

   $ SET DEFAULT SYS$SYSTEM $

3. Invoke UDU:

   $ UDU UDU>

4. Add an OpenVMS user name to the ACMS database by entering the ADD command:

   UDU> ADD uname /MDB=AVERTZ_DEFAULT:VR_MENU UDU>

   
   Include the MDB qualifier to specify the default menu displayed to this user when entering ACMS.

5. Enter the SHOW command to verify this entry in the ACMSUDF.DAT database:

   UDU> SHOW uname User name: UNAME DISPLAY MENU Default menu: Default MDB: AVERTZ_DEFAULT:VR_MENU . . . UDU>

   
   An entry under uname indicates that the uname is authorized to sign in to ACMS. The default characteristic DISPLAY MENU causes ACMS to display the top menu in uname's VR_MENU database.

6. Enter the SHOW SYSTEM command to determine if user name SYSTEM has been added to the ACMS database (it may not, if this is the first ACMS access). If you receive a "user does not exist" message, then add SYSTEM as follows:

   UDU> ADD SYSTEM /AGENT UDU>

   
   Although ACMS assigns the user name SYSTEM to the Command Process (CP) when you install ACMS, it does not automatically authorize the Command Process as an agent. Without this authorization, ACMS cannot sign in any users. The /AGENT qualifier enables an agent to submit a task that has a user name different from the user name of the agent process.

7. Exit from UDU.

Authorized ACMS users must sign in from terminals that have been authorized for access to ACMS. With the Device Definition Utility (DDU), the system manager creates a database named ACMSDDF.DAT that contains a list of authorized ACMS devices. In the simplest case, the system manager can use one DDU definition to authorize all terminals on your system, both local and remote, to use ACMS.

To use DDU to authorize terminals for users, follow these steps:

1. Define DDU as a global symbol in your login command file. Then initialize the symbol by executing your login command file:

   $ DDU :== $ACMSDDU $ @LOGIN.COM $

2. Set the default directory to SYS$SYSTEM:

   $ SET DEFAULT SYS$SYSTEM $

3. Invoke DDU:

   $ DDU DDU>

4. Use the ADD command to authorize a LAT terminal on your system for ACMS use. The device name LT authorizes all LAT terminals.

   DDU> ADD LT DDU>

   
   If the ADD LT command has been performed before, you receive the message, "device name already exists in the data base." In this case, you can exit from DDU and proceed to the next section.

5. Use the SHOW command to display information about the LT entry:

   DDU> SHOW LT Device name: LT NOT CONTROLLED No Autologin Printfile DDU>

   
   When the system manager creates a new ACMSDDF.DAT database, DDU creates a DEFAULT definition that assigns all terminals the NOT CONTROLLED characteristic. From a CONTROLLED terminal, the user signs in directly to ACMS; from a NOT CONTROLLED terminal, the user first logs in to the OpenVMS operating system and then signs in to ACMS from DCL command level.

6. Exit from DDU.

Both the ACMS system and the AVERTZ application must be started before users can sign in. You can also stop your ACMS system or AVERTZ application at any time. The next two sections describe how to:

• Start ACMS and AVERTZ
• Stop ACMS and AVERTZ

Any account from which the ACMS/START and ACMS/STOP commands are issued must have OpenVMS OPER privilege to execute these commands.

To start the ACMS system (if it is currently stopped), and to start the AVERTZ application, perform the following steps:

1. Issue the SHOW SYSTEM command to determine if another user has already started ACMS:

   $ ACMS/SHOW SYSTEM

   
   If the subsequent display states that "current system state" is STOPPED, proceed to the next step and start the ACMS system. However, if the display states that the current system state is STARTED, proceed to step 3.

2. Issue the START SYSTEM command to start the ACMS system:

   $ ACMS/START SYSTEM

   
   If the ACMS system starts successfully, the $ prompt returns with no intervening error messages.

3. Before you can invoke a command that runs the application, you need to start the application. Issue the START APPLICATION command with the name of the AVERTZ application:

   $ ACMS/START APPLICATION VR_APPL

   
   If the ACMS system starts successfully, the $ prompt returns with no intervening error messages. However, if your system logical AVERTZ_DEFAULT is not defined on this system, you receive an error message that states, in part, "Error opening TDB file AVERTZ_DEFAULT:[SYSHLP.EXAMPLES.ACMS]..." See Section 15.2.2 for information about defining your system logical.
   If you receive an "invalid login attempt" message, your system manager may not have authorized the ACMS Command Process (CP) to run as an agent (described in Section 15.3.1). Without this authorization, ACMS cannot sign in any users.

You can stop your application and the ACMS system with the ACMS/STOP command. Before you stop the system, however, issue the SHOW SYSTEM command to see if another person is using the ACMS system:

$ ACMS/SHOW SYSTEM

The system displays the names of any active applications and any active users. If no other applications or users are active, issue both ACMS/STOP commands. Otherwise, issue only the STOP APPLICATION command, specifying the name of your application:

$ ACMS/STOP APPLICATION VR_APPL $ ACMS/STOP SYSTEM $

ACMS waits until all active tasks have finished executing before it stops the application and the system.

To understand how the AVERTZ application looks to the user, imagine the conversation between a reservation clerk working for AVERTZ operations in New England and a customer who needs a rental car.

16.1 Entering AVERTZ

After his morning cup of coffee, Sparky Hartshorn, a reservation clerk at AVERTZ, enters the AVERTZ application from his OpenVMS account:

$ ACMS/ENTER VR_APPL[Return]

AVERTZ displays the AVERTZ Rental Menu shown in Figure 16-1.

Figure 16-1 AVERTZ Rental Menu

To select an option, the clerk types the option number and presses [Return]. For example, to reserve a car, the clerk types:

Selection:1[Return]

If the clerk needs online help while using AVERTZ, he can display help for any field by pressing [Help] when the cursor is on that field.

The next three sections describe a sample dialog between a customer and the clerk at AVERTZ for the following transactions:

• Reserving a car
• Checking out a car (beginning the rental)
• Checking in a car (ending the rental)

Bertram Simpson needs a car. The following telephone conversation between Bertram and the AVERTZ clerk, on April 19, shows how the reservation option is used in a real business situation. Integrated with the conversation are the steps the clerk must take to enter the car reservation in AVERTZ:

Clerk:	"Hello, AVERTZ Car Rental ... can I help you?"
Customer:	"Oh, hi. My name is Bertram Simpson and I need to rent a car for this weekend."
Clerk:	"OK, Mr. Simpson. Let me just ask you a few questions." The clerk enters the following at the AVERTZ Rental Menu: Selection: 1 [Return] AVERTZ displays the reservation panel shown in Figure 16-2.

Figure 16-2 Reservation Panel

Figure 16-3 Site Selection Panel

Figure 16-4 New Customer Panel

Figure 16-5 Reservation Completed Panel

16.3 Customer Checks Out a Car (Beginning the Rental)

Figure 16-6 Checkout Panel

Figure 16-7 Checkout Update Panel

Figure 16-8 Car Selection Panel

Figure 16-9 Checkout Completion Panel