NetBase for MPE Reference Guide

NetBase Shadowing
5-31
Notes
• The command file, ADAGER.PUB.NETBASE, must be used.
• Only one database can be modified per execution of the command file.
• Online changes made with ADAGER are not shadowed.
• ADAGER.PUB.NETBASE will work when the data set is out of sync or queuing. The out of sync
or queue state will not change, but the capacity change will happen.
2) NetBase DBGENERAL Interface
NetBase also has an interface with DBGENERAL. When DBGENERAL is used to do maintenance to a
master copy of a file, then changes will automatically be sent to the shadow system and performed
there as well. This maintenance operation may be performed online or in batch. The interface
works by capturing the input to DBGENERAL on the master system and sending it over to the shadow
system. A special program NBGENRL.PUB.NETBASE is used to write the DBGENERAL changes to the
shadow transport file, NBM.IPC.NETBASE.
When the posting process NBPOST receives the DBGENERAL commands, it automatically puts the
database into a queue state. Next, NBPOST invokes DBGENERAL on the shadow system to perform
the changes. Once DBGENERAL has successfully completed on the shadow system, NBPOST does a
ROLL FORWARD automatically on the database. The STDLIST of this DBGENRAL process is created as
a SPOOL file with the name DBGENOUT.out.hpspool.
3) Manually Coordinating the Structural Changes
There are several ways that this can be accomplished. One method is to make the changes on the
master database and then restore that database to the shadow machine. This in effect produces a
“resync” of the database. Another method outlined below produces the least amount of user
downtime.