HP 3000 Manuals HP 3000 Manuals
Controlling Devices From the Console Peripheral devices are controlled by the system operator, from the system console. Users other than the system operator can be given control of peripherals in three different ways: by use of the ALLOW command, CONSOLE command, or ASSOCIATE command. Some commands which control devices are restricted to the console. Any user can control devices from a terminal if the console is moved to that terminal. This is accomplished by using the CONSOLE command. To move the console, you must be the system operator or have SM capabilities, be issued CONSOLE command by ALLOW, or already own the console. To move the console to another terminal, enter CONSOLE with the logical device (ldev) number of the terminal. For example, to move the console to ldev 31, enter: CONSOLE 31
CAUTION If you move the console to another terminal, you will not be able to take it back unless you have been issued the CONSOLE command by ALLOW or have SM capability.
Controlling Devices with the ALLOW command The ALLOW command relaxes the "console" restriction by giving users the right to use specific console commands. The system operator issues the ALLOW command. From the console, you indicate which user, then the name of each command allowed. For example, to give the user MAC.TECH the ability to execute the ABORTIO command, you would enter the following: ALLOW MAC.TECH;COMMANDS=ABORTIO Controlling Devices with the ASSOCIATE Command The ASSOCIATE command gives users control of a device class. This means they can execute device control commands (refer to table 4-1) usually allowed only to the system operator. A device class contains a group of devices of the same type. A device can belong to more than one class (for example, logical device 6 could belong to class LPA and LPB) but it can only be associated with one user at a time. A device can only be associated with one session at a time. For example, USER1.ACCT logs onto a terminal and uses the ASSOCIATE command with device class LPA. If USER1.ACCT then logs onto another terminal, device class LPA will not be available. The ASSOCIATE command can be canceled by the DISASSOCIATE command. If the first USER1.ACCT session uses the DISASSOCIATE command for device class LPA, then the second USER1.ACCT session would be able to use the ASSOCIATE command with device class LPA. A user can be more than one person, as in @.acct. However, the one device per one user/session rule still applies. If USER1.ACCT logs on and uses the ASSOCIATE command with device class LPA, then no other user in @.ACCT can use the ASSOCIATE command with device class LPA. A user can control multiple device classes. For example, ACCTMGR.ACCT may be associated with three device classes: LPA, which contains ldevs 6, 19 and 25; LPB, which contains ldevs 25, 18 and 27; and LPC, which contains ldev 35. This means that ACCTMGR.ACCT could logon to two different sessions and use the ASSOCIATE command with LPC on one and LPA or LPB on the other. Since LPA and LPB share the ldev 25, only one session of ACCTMGR.ACCT can be associated with either LPA or LPB. Table 4-2. System Operator Commands Assigned by ASSOCIATE --------------------------------------------------------------------------------------------- | ABORTIO | OUTFENCE | | ACCEPT | REFUSE | | ALTSPOOLFILE | REPLY | | DELETESPOOLFILE | RESUMESPOOL | | DISCRPS | SHUTQ | | DOWN | STARTSPOOL | | DOWNLOAD | STOPSPOOL | | HEADOFF | SUSPENDSPOOL | | HEADON | UP | | OPENQ | | --------------------------------------------------------------------------------------------- Associating Users with Device Classes To associate a user with a device class, the system manager must first run a utility program named ASOCTBL.PUB.SYS. The program creates a table named ASOCIATE.PUB.SYS, in which users are given the right to associate to the device classes. Once this is done, the user may enter the ASSOCIATE command at logon or at any time during the session. Running the ASOCTBL Program System manager (SM) capability is required to run ASOCTBL.PUB.SYS. In addition, you should be logged on in the SYS account with write access to PUB.SYS. At the prompt (:), enter: ASOCTBL At the utility prompt (>), enter: > deviceclassname=username.accountname[,...] where: deviceclassname is a valid device class name and username.accountname is the name of the user associated with the device class. Additional user names, set off by commas (,) can be included as if they were members of the first user name specified. > LPA=USER1.ACCT,ACCTMGR.ACCT ASSOCIATE a User with a Device Class Assume that, in the ASSOCIATE table, POWER.USER is associated with the device class TAPE. To let POWER.USER exercise control over the device class TAPE, enter: ASSOCIATE TAPE ASSOCIATE Syntax ASSOCIATE devclass Table 4-3. ASSOCIATE Parameters -------------------------------------------------------------------------------------------- | | | | Parameter | Description | | | | -------------------------------------------------------------------------------------------- | | | | devclass | The name of a device class configured during SYSGEN. | | | | --------------------------------------------------------------------------------------------