Dynamic configuration enables you to apply a select
set of DTS configuration changes made in NMMGR without rebooting
the system. Such configuration changes include adding or deleting
terminals, printers and DTCs, changing most configuration parameters
of terminals, printers and DTCs. See Table 4-1 “Dynamically Configurable
Tasks” for a complete list of configuration changes
that can be modified dynamically (this includes changes that require
additional actions, such as rebooting the DTC, before changes take
effect).
All operations that delete ldevs are non-destructive. This
means that if an ldev to be deleted is in use, then the delete is
not performed. You must take the appropriate action to free the
device. For example, you must stop the spooler on a spooled serial
printer or log off the session on a terminal ldev. If multiple ldevs
are deleted, then only free ldevs are deleted. Those ldevs that
were not free will be processed again the next time DTCCNTRL is
invoked.
Most changes will not affect current active sessions or users.
Only those changes that require a reset of the DTC or DTC card will
affect active sessions or users. A DTC reset is only required when
the change is to a DTC characteristic, such as, adding a card or
changing a DTC CPU parameter, such as, the DTC IP address or SNMP
data. Users on other DTCs are not affected.
Some changes will require additional steps to complete once
DTCCNTRL has made the desired changes. These possible additional
steps are: logoff any sessions or close any jobs that access the
changed devices, stop and restart the spooler if the device is a
printer, stop and the start X.25/PADSUP, reboot or reset the DTC.
DTCCNTRL will display a message when these steps are necessary and
tell you which DTCs are affected.
Table 4-1 Dynamically Configurable
Tasks
Task | Action
Required for Change to Become Active |
|---|
Add/configure
new terminal/printer | No action; changes take effect dynamically |
Add/delete
class name |
Change
DTC event logging class |
Host-based
X.25 configuration changes: |
-
maximum number of PAD connections |
-
X.25 link name |
-
maximum number of switched virtual circuits |
-
remote X.25 addresses and security |
-
X.25 allow access |
-
remote X.25 calling address |
-
PAD password |
Change
SNMP filter |
Change
NLIO from N to Y in terminal profile |
Increase
number of non-nailed TIO/PAD ports |
Change
terminal to printer or vice versa* | Logoff
any sessions or close any jobs associated with changed devices.
If device is a printer, stop the spooler. |
Change
device profile characteristics: |
-
change line speed | |
-
change term type file name/number | * For these changes, the device must not
be owned when dynamic configuration is invoked. The terminals must
be logged off and the printers must be not spooled. |
-
change modem type |
-
change speed/parity |
-
change hardware handshaking |
-
change reset HP terminal |
-
change allow :HELLO logon |
-
change record width |
Delete: |
-
terminal/printer* |
-
ldev* |
-
DTC* |
Decrease
number of non-nailed TIO/PAD ports* |
Change
starting ldev of non-nailed ports* |
Host-based
X.25 configuration changes: | Use DTCCNTRL
to: |
-
change PAD access | 1) Stop
X.25/PADSUP |
- change level 1,
2, or 3 configuration | 2) Start
X.25/PADSUP |
(see
Configuring and Managing Host-Based X.25 Links (36939-61004) for
more information) |
Add/configure new DTC | Reboot
or reset DTC |
or |
Perform
automatic configuration (see character 3 for more information) |
Add/configure
a TIO card | 1) Logoff
any sessions that were logged on through the changed DTC |
Change
DTC IP address | 2) Reboot
DTC (see Chapters 5/6, step 9, for more information) |
Change
AFCP/management timers | You may also use TermDSM to reset the DTC
(see Troubleshooting Terminal, Printer, and Serial Device Connections
(32022-61002) for more information) |
Change
SNMP MIB data |
Change
SNMP trap destination |
Change
from host-based TIO to host-based X.25 | 1) Use
DTCCNTRL to shutdown/restart DTS (see Chapters 5/6, step 9, for
more information) |
Change
DTC LAN address | 2) Reboot
DTC |
Change
DTC name | You may also use TermDSM to reset the DTC
(see Troubleshooting Terminal, Printer, and Serial Device Connections(32022-61002)
for more information) |
Change
DTC node name |
Change
from PC-based to host-based or vice versa |
Change
NLIO from Y to N in terminal profile |
Change
initially spooled in printer profile |
Change
HP 3000 characteristics: |
-
node name |
-
link name |
-
physical path of LANIC |
Add X.25
card to DTC when none previously existed |
NMCONFIG and NMCONFIX Files |
 |
Dynamic Configuration uses both files NMCONFIG.PUB.SYS
and NMCONFIX.PUB.SYS
to manage the devices created by the DTS subsystem. When users wish
to make any dynamic change, NMMGR will be used to modify the configuration
in NMCONFIG.PUB.SYS.
When DTCCNTRL is invoked, either within or from outside of NMMGR,
NMCONFIG will be compared to NMCONFIX and the desired changes will
be made to the system configuration. When the operation has completed
successfully, the changes will be written to NMCONFIX. The configuration
in NMCONFIX will always match the actual configuration of the DTS
subsystem.
If any errors are encountered, then information will be saved
in the NMCONFIG file that will allow DTCCNTRL to be re-invoked to
complete the changes at a later time. If an operation is partially
successful, then those changes that are successful will be written
to NMCONFIX. For example, if you delete two ldevs and the second
ldev can't be deleted because it is in use, then DTCCNTRL will save
information that will allow the second ldev to be deleted once the
device is no longer in use.
|
| |
|
 | CAUTION: If ANY other configuration file is copied to NMCONFIG.PUB.SYS
or NMCONFIX.PUB.SYS
then dynamic configuration will be disabled until a DTS shutdown
and restart is done or the system is rebooted. This includes other
files from the same system or files copied from other systems. |
|
| |
|
If there is some operation that fails, and you wish to undo
the change, you can use NMMGR to change the appropriate screens
back to what they were and then invoke DTCCNTRL.
