HP 3000 Manuals HP 3000 Manuals
Creating the Configuration File
To create the configuration file perform the following steps:
1. On the primary system, log onto the group and account where the
database is located.
2. Use a supported editor to create a configuration file based on the
example shown in Figure 4-1.
3. Keep the file to a unique file name. This file name is specified
when using various Silhouette commands.
4. Note the name of the configuration file name on the Installation
Worksheet, located at the end of this chapter.
Sample Configuration File
Figure 4-1 is an example of a typical configuration file. It defines the
Silhouette environment on an HP 3000.
_________________________________________________________________________
| |
| BEGIN << Silhouette Configuration File >> |
| LOCAL = !JOB jobname,user.account/pass,group;pri=bs;hipri: |
| COMMANDS = p1.group.account: << Pipe to CP >> |
| RESPONSES = p2.group.account: << Pipe from CP >> |
| SAVEFILE = sv.group.account: << Saves environment >> |
| USE logproc WITH dbname.group.account/pass, << all three same >>|
| dbname.group.account/pass, |
| dbname.group.account/pass: |
| MODE = 4: |
| WAIT = 3000: << milli-seconds >> |
| MAXRECS = 0100: << before requesting tape >>|
| DSLINE = MPEXL950: << 1 DS Lines >> |
| REMOTE = hello session,user.account/pass,group;pri=bs;hipri: |
| LOG = logfl.group.account: |
| TAPEDEV = tape: << Tape device class >> |
| END. << of config >> |
_________________________________________________________________________
Figure 4-1. Sample Configuration File
Note the names of the databases, groups, accounts, passwords, and
communication lines on the Installation Worksheet at the end of this
chapter.
Customizing the Parameters
To create a configuration file for your system, based on the example in
Figure 4-1, customize the parameters, as follows:
LOCAL = Replace the group, and account in this jobcard to identify
where the logfile resides. Include any required passwords.
NOTE The files specified with the LOG`=, COMMANDS`=, RESPONSES`=, and
SAVEFILE`= parameters may all reside in the same group and account
as the database and configuration file. While it is recommended
that these files all reside in the same group, it is not mandatory.
This account and the user must have MAXPRI = BS and CAP = LG, OP
(User Logging and System Supervisor) capabilities. To determine
account capabilities use the LISTDIR5 >LISTACCT or >LISTUSER
command. If necessary, add the capabilities by using the MPE
:ALTACCT or :ALTUSER command. Note this information on the
Installation Worksheet at the end of this chapter.
USE...With Replace dbname with the name of your database and replace
pass with any required password. If you are duplicating
more than one database, separate each database/password
description with a comma. Use new lines if necessary, and
end the last database/password description with a colon.
Ensure that each password gives the highest access to the
database and remember that uppercase and lowercase letters
are considered different in passwords. Each dbname must be
fully qualified with its group and account name. If the
databases on your system have logging enabled, change
logproc to the name of your active logging procedure.
(cont.)
MODE = This is an optional keyword. The default is MODE = 4.
WAIT = Keep 3000 milliseconds as a starting point.
MAXRECS = Keep 100 records as a starting point unless you do not want
to go to tape, in which case, use 9999 or NEVER.
DSLINE = Replace MPEXL950 with the node name of the secondary system
as specified in your system configuration.
REMOTE = Replace the remote logon to refer to the group and account
where the logfile is located.
LOG = Replace group.account with the group and account of the
database. If necessary, move the file to the specified
group.account any change the logid. If the databases on
your system have logging enabled, change logfl to the active
logfile name. If automatic CHANGELOG is enabled on your
system, set LOG = to the first logfile in the series that
ends in 001.
NOTE Refer to Chapter 2 for additional information on the configuration
file and its parameters.
Verifying the Configuration File
After you create and customize the configuration file for your system,
verify its contents:
1. To verify the configuration file, enter:
:RUN SILMP.PUB.SYS
>VERIFY configfile
2. If the configuration file contains no errors, the following
message is displayed:
No errors found in Silhouette configuration file. (MPMSG 81)
If you have System Manager (SM) or Privileged Mode (PM) capability
a detailed report is supplied. Refer to Chapter 6 for more
information on the >VERIFY command.
3. If the configuration file contains any errors, a message is
displayed indicating what is incorrect. Use the editor to modify
the configuration file.
NOTE After you verify the configuration file using the Manager Program
(MP) >VERIFY command, alter the security of the file using the MPE
:ALTSEC command to allow EXECUTE ONLY access for all users. Enter
the command in the form :ALTSEC filename;(R,W,A,L,X:CR). This
allows only the creator of the file or the MP to access the file.