HP 3000 Manuals HP 3000 Manuals
Network Updates
If your system is part of an HP Desk network, it is very important that
any changes you make to your Directories are also made to the other
Directories in the network. Otherwise, NRCs won't know where to send
hierarchically addressed messages and remote users will have difficulty
sending mail to any of your local users whose details have been altered.
Network updates are performed by using one of the batch methods to apply
a batch configuration file created in one of the ways described in "Local
Updates" . In addition to the ways of creating a batch configuration
file already mentioned, you can use Mailutil to list either the local
users and nodes or the complete database to a file in batch configuration
format. This can be used to update other machines in a network. This
file cannot help update the local computer name or routes to other
computers.
Updates Using the Directory Update Facility
You can inform other computers about your Directory updates using HP Desk
itself. The updates are sent in an HP Desk message addressed to the
Directory Update facility on the remote computer you wish to update. If
the remote computer is configured to automatically apply the updates, the
HP Desk Administrator there doesn't even have to do anything because the
updates are automatically applied. If the HP Desk Administrator of the
remote machine wishes to forward the updates on to another machine, he
can do so by logging onto General Delivery, reading the updates message
and then forwarding it onto the Directory Update facility on the
appropriate computer.
Remote updates are a very good way of informing other computers in the
network of changes in user and node information.
You can send updates to remote computers in a normal HP Desk message, the
transactions being entered in the text part of the message or copied in
from a batch file. However, the updates are only applied to the remote
computer if you have System Administrator capabilities,
Updates of user names and mailnodes sent to a remote computer can only be
applied to entries which are remote to that computer (for example, local
users cannot be deleted). Otherwise, all of these commands have the same
restrictions as in the Batch Configurator.
________________________________________________________________________
| |
| How to send remote updates: |
| |
| 1. At either the Intray > or Outtray > prompt, type SEND and press|
| Return. |
| |
| 2. In the Subject field, you could type the name of the computer |
| or location you are sending the updates to, along with the date|
| of the updates. Although this is not mandatory, it will |
| make it easier to identify the replies which will be |
| sent to you when the updates are applied to the remote |
| computer. |
| |
| 3. At the To: prompt, type *ADMIN/location/sublocation and press |
| Return. |
| |
| location is the location code of the computer you wish to |
| update. |
| |
| sublocation is the code for any sublocation on that location. |
| You can give any valid sublocation code because once the |
| message is delivered, the updates are applied to the entire |
| computer. Hence, the update could be applied to a number of |
| locations. |
| |
| For example, if the HP Desk Administrator at one of the Pharaoh|
| Company's divisions wishes to send updates to the European |
| Corporate Headquarters, they would type *ADMIN/EUCORP/LE |
| . |
| |
| You can send the same update to a number of computers simply by|
| typing *ADMIN/location/sublocation for each of the computers |
| you wish to send the update to. |
| |
| 4. Press Return three times to get to the From: prompt. |
| |
| 5. At the From: prompt, type your own name and press Return. |
| |
| 6. When Text: appears, you can either: |
| |
| |
| a. Copy in an existing Batch Configuration file by typing |
| // and using the COPY FROM (filename) command, where |
| filename is the name of the Batch Configuration file you|
| want to use. |
| |
| b. Create a Batch Configuration file on the screen by |
| typing the Batch Configuration transactions you want to |
| send. You can also include comments in your message the|
| same as you can in a conventional Batch Configuration |
| file. Once you have typed in all of the updates you |
| want to send, close the message by typing // and press |
| Return. |
| |
| 7. If you want reports returned to you indicating which |
| transactions were (un)successful, you need to set an reply ACK |
| on the message. |
| |
| For example ACK 5 |
| |
| 8. At the Message > prompt, type MAIL to send the list of |
| updates. |
________________________________________________________________________
Once the message arrives at its destination:
* If the computer is configured to apply updates from your computer
automatically, the Directory Update facility strips out your
comments and performs the batch configurator transactions. It
generates two reports, and once this is done sends a reply to you,
telling whether or not it has been successful. It also sends a
message to General Delivery at its own location containing all of
the transactions successfully applied to the database.
You can configure the destinations where they are sent at the
Update Reporting Screen. See Chapter 12 for more information.
If you have set an acknowledgment on the update server, a report
is sent.
* If the computer is not configured to apply updates from your
computer automatically, a list of the updates is sent to General
Delivery at its location. The HP Desk Administrator can then
apply the file as it is or can edit it to apply only those changes
required.
The reply you receive will tell you one of four things:
* All transactions have been successfully applied to the databases.
* You do not have System Administration capabilities and so cannot
perform Directory updates.
* The receiving computer is configured so as not to accept updates
from the sending mailnode or hierarchical location. HP Desk
Administrators can specify that only update messages from
particular mailnodes should be processed.
* A list of transactions which could not be performed and the
reasons why. For example, if one of your transactions was
41 Peter Osbourne/EUCARP/LE
and EUCARP should be EUCORP, the report will read
41 Peter Osbourne/EUCARP/LE
$ Add User Peter Osbourne - Bad Location
You can edit a list of bad transactions like a normal HP Desk
message. Correct the mistakes which caused the problems and then
send it back to the computer you wish to update. You don't need
to worry about removing the comments because these will be
stripped out when the resubmitted message reaches the recipient
computer.
Use of User Configuration Templates
Configuration of local users on remote systems by the ADMIN server can be
simplified by the use of templates. User Configuration Templates can be
set up to hold standard information about users that you may want to
configure in the future. It also holds information on the default
settings for the Work Area and Filing Cabinet limits, and access and
group capabilities. The use of a named template (provided it is
configured on the remote system), allows these details to be configured
when adding the user in a single batch transaction, without needing to
use several batch transactions which would otherwise be necessary.
NOTE The User Definition 2 screen in Mailconfig takes its default values
from the default User Configuration Template.
Updates Using Mailutil
If the HP Desk Administrator at the recipient computer does not want to
use the Directory Update facility for some reason, you can send updates
in a batch configuration file stored on magnetic tape.
________________________________________________________________________
| |
| How to perform batch configuration: |
| |
| 1. Prepare a batch configuration file using one of the ways |
| described in Updates Using the Batch Configurator. |
| |
| 2. Send the tape to the HP Desk Administrator in charge of the |
| computer you wish to update. |
________________________________________________________________________