
HP NonStop Shadowbase Command Definitions
Consumer Command Descriptions
HP NonStop Shadowbase Command Reference Manual—785421-002
133
Initial Changed
Version Version Values Default Minimum Maximum Alter
4.092 OFF OFF ON No
Client Server Extended Open Target
This parameter is not yet implemented and will be available in a future
release.
This parameter is used to enable the CONS to process FUP commands
generated by a special customized NonStop FUP program feeding HP
Shadowbase as a FEP process (“front end”). Set FUPSERVER to ON to
enable FUP replication. The default is OFF.
The CONS CONTROLFILE parameter must be set, as the
CONTROLFILE is the interface file between the FEP and the CONS. Only
one CONS may be configured as a FUPSERVER for a given HP
Shadowbase environment (AUDMON environment) because all such FUP
commands must be processed sequentially after all replication threads are
quiesced at the appropriate point (see below).
Considerations related to a CONS configured as a FUPSERVER:
For an STP tcp/ip NonStop to NonStop environment, the FUPSERVER
parameter must be set the same for the client CONS and the server
CONS.
For STP tcp/ip mode, make sure that your CONS NETTIMEOUT
parameter is set large enough to handle your longest FUP operation.
In STP tcp/ip mode, the server CONS won’t recognize a client CONS
disconnect until the server CONS is finished processing a FUP
command against the target (e.g., once the FUP command starts, the
server CONS does not (cannot) check for connection status until the
FUP command completes).
For both STP and Expand NonStop to NonStop environments, the
CONS (the server CONS for STP environments) must run on the target
system (this is the usual location for the server CONS).
The FUPSERVER CONS starts a single FUP process to handle a
sequence of FUP commands from the same FUP source process. There
may be up to 20 FUP processes executing commands to be replicated
running in parallel.
HP Shadowbase starts one FUP process on the target per FUP sequence
as needed. The processes will be started in the same CPU as the CONS
process. Commands are executed single-threaded where only one FUP
process is executing a command at time, and the CONS is suspended
while the command is executing (this is required as some FUP commands
Commentaires sur ces manuels