HP 3000 Manuals HP 3000 Manuals
Configuration Files The environment for a Silhouette system is specified in a file referred to as the configuration file. The configuration file contains all the parameters necessary for Silhouette to operate. It is an ASCII file, created using any supported Editor. Since it is a stand-alone text editor file, the configuration file can be created prior to the actual installation of Silhouette. Parameters can be supplied in any order and can be specified in uppercase or lowercase. Parameter specifications must be separated by a colon (:). File records can be up to 132 bytes wide. The BEGIN keyword denotes the start of specifications within the file. Any text found prior to the BEGIN keyword is treated as a comment. The END. keyword (the period is required) denotes the end of specifications. Any text found after the END. keyword is treated as a comment. All the keywords shown in Figure 2-1 must be specified somewhere in the file. Comments can be inserted within the file anywhere space allows. The start of a comment is defined with a << sequence and the end of a comment with a >> sequence. You can create more than one configuration file for Silhouette. However, if you have more than one configuration file, you need to specify a configuration file name when using certain commands.
NOTE After you verify the configuration file, using the Silhouette Manager Program >VERIFY command, alter the security of the file by 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 Silhouette Manager Program to access the file.
Sample Configuration File Figure 2-1 is an example of a typical configuration file created to define the Silhouette environment on your system. _________________________________________________________________________ | | | 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 dbtst1.group.account/pass, << all three same >>| | dbtst2.group.account/pass, | | dbtst3.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 2-1. Configuration File Configuration File Parameters The configuration file keywords, shown in Figure 2-1 are defined below: BEGIN The BEGIN keyword defines the beginning of the parameters within the configuration file.
NOTE It is recommended, but not mandatory, that the files specified with the COMMANDS =, RESPONSES=, and LOG = parameters all reside in the same group.
LOCAL = The LOCAL = keyword specifies the logon to the primary system for the batch job to run the Communication Process (CP). This process acts as the controller process on the primary system. This logon is also used for the batch job to run the Recovery Process (RP) as a stand-alone recovery job. COMMANDS = On the primary system, the COMMANDS = parameter specifies the name of the message file that the Manager Program (MP) uses to send instructions to the Communication Process (CP). On the secondary message file that the Secondary Communication Process (SP) uses to send commands to the Recovery Process (RP). In both cases, Silhouette manages the building and maintenance of this file. This file name may not begin with the letters X, Y, or Z. RESPONSES = On the primary system, the RESPONSES = parameter specifies the name of the message file that the Communication Process (CP) uses to return responses to the Manager Program (MP). On the secondary system, this is the name of the message file that the Recovery Process (RP) uses to return responses back to the Secondary Communication Process (SP). In both cases, Silhouette manages the building and maintenance of this file. This file name may not begin with the letters X, Y, or Z. SAVEFILE = The SAVEFILE = parameter specifies the name of the file Silhouette builds, maintains, and uses to store the current environment information for the system. This file name may not begin with the letters X, Y, or Z. USE...WITH The USE...WITH parameter specifies the name of the logging process to be monitored. In addition, it specifies the databases to be duplicated using that log process and a password that is used to get creator capabilities for each of the databases. MODE = The MODE = parameter specifies whether the secondary databases are to be opened with locking (mode is 1) or without locking (mode is 4). If the keyword is omitted, the default is mode = 4. It is recommended that MODE = 4 be used or this line omitted. Using MODE = 1 can cause the databases to become nonduplicating due to the possibility of additional writers on the secondary system. WAIT = The WAIT = parameter specifies the maximum time (in milli-seconds) that Silhouette waits before examining the logfile on the primary system. This is used when Silhouette finds no more log records to process and pauses. By specifying a short period of time, you minimize the data that might be lost during a failure of the system. However, this may cause Silhouette overhead to be higher than necessary. This parameter also controls the maximum period of time data sits in a memory log buffer before going to disc since Silhouette does a FLUSHLOG to force the data to disc whenever it examines the logfile. (cont.) MAXRECS = The MAXRECS = parameter is the high water mark that specifies how far Silhouette is allowed to get behind in the logfile before the Operator is requested to provide a tape for storing the records. If the duplicating begins to run more slowly than the primary system processing, there will be a dangerous number of records in the logfile that have not been transmitted to the secondary system. At some point, the logfile records must be output to tape so they can be loaded onto the secondary system in case a primary system failure occurs. Specifying a low number can generate frequent tape requests which can be annoying from an operations standpoint. When the duplicating catches up and the outstanding logfile record count falls below this point again, the tape is released. The maximum allowable number for MAXRECS is 9999. Two reserved words may be used with the MAXRECS = parameter. If MAXRECS = NEVER, Silhouette will never write records to tape. If MAXRECS = ALWAYS, all transactions are sent to tape as well as across the data communication line to the secondary system. DSLINE = The DSLINE = parameter specifies which data communication lines are available for Silhouette to use. These can be specified as either logical device numbers or device class names. REMOTE = The REMOTE = parameter specifies the logon command used by Silhouette to log onto the secondary system. LOG = The LOG = parameter specifies the name of the disc file to which the logging process on the primary system will write. It is also used to access a copy of this logfile on the secondary system. This file name may not begin with the letters X, Y, or Z. When using the MPE automatic CHANGELOG feature, the first file in the series should end in 001. TAPEDEV = The TAPEDEV = parameter supplies the device class name to be used by Silhouette on the primary system when it finds that the transmission process is running behind and must copy the outstanding data to tape. END. The END. keyword defines the end of the configuration parameters within a configuration file. The period is part of the keyword and must be supplied.
NOTE The specified group and account must be identical for the LOCAL = and REMOTE = parameters of the configuration file. The specified account for COMMANDS =, RESPONSES =, and LOG = must be the same as LOCAL = and REMOTE =.