
HP NonStop Shadowbase Command Definitions
Consumer Command Descriptions
HP NonStop Shadowbase Command Reference Manual—785421-002
124
Set this parameter to the same “name” value for all CONS objects you
want to belong to the same group. The value specified must be from 1 to
16 alphanumeric or hyphen characters and must start with a letter. This
parameter can be altered at any time.
CONTROLFILE <filename>
Initial Changed
Version Version Values Default Value Specifications Alter
4.060 4.091 No
Client Server Extended Open Target
This parameter is used to define the TMF-audited control file that is used
to create a CONS “suspend update” event in the audit trail that will be
detected by a Collector in order to cut off the flow of audit trail events to a
Consumer. The file must be created on the same node where the
Collector runs (and AUDMON typically runs on that node as well). If only
the file name portion is supplied, the subvolume will default to the value
currently set for the base CMDVOL. Typically, this is the current TACL
subvolume. Use the AUDCOM SHOW command to see the value for
CMDVOL. The file must be defined on a TMF MAT (master) data volume.
Otherwise, an error will occur when you try to add the CONS. This
parameter can’t be altered. You must define a CONTROLFILE if you want
to use the SUSPENDUPD and RESUMEUPD feature. The default is
unspecified (i.e. disabled). The same file can be used for all of your
CONS objects.
Support for FUP DDL replication for Enscribe files has been added to HP
Shadowbase. The controlfile record size, associated with the CONS
CONTROLFILE parameter, has been increased. You must purge any
existing CONTROLFILEs before restarting HP Shadowbase with the 4.091
and later versions. Otherwise, you will receive user error 1390.
If the control file does not exist, AUDMON will create it. To handle the
situations where the Collector and AUDMON are not running on the same
node, the control file is created with read and write network access for all
users (‘N’). Any Safeguard policies that would prevent AUDMON from
remotely accessing the file will also have to be relaxed as well in these
cases.
Note: The CONS will start in a SUSPUPD state if a CONTROLFILE
exists from a previous environment that was shutdown with the
CONS left in SUSPUPD state. This will occur even when there is
no RESTARTFILE and the COLL starts at EOF or a specified ADT
RBA or datetime. Purge the CONTROLFILE if the environment is
to be started in a RUNNING state.
Comentários a estes Manuais