 |
» |
|
|
|
Follow the steps below to dynamically configure DTS changes.
Refer to Chapter 5 “Configuring Serial Devices (for
Host-Based Management)” and
Chapter 6 “Configuring Serial Devices (for
PC-Based Management)” for more detailed
steps on the DTS configuration process using NMMGR for host-based
and PC-based DTC management, respectively. NMMGR can keep up to 70 changes. This means that you can change
a maximum of 70 different screens before you invoke DTCCNTRL. After
the 64th change NMMGR displays a warning that tells you the limit
is near. If more than 70 changes are made NMMGR warns that the current
change will not take effect using DTCCNTRL. Those changes made after
70 entries will not be kept and can not be made dynamically. After
DTCCNTRL is invoked and the changes were successful, NMMGR can again
keep up to 70 new changes. Those changes that were not successful
will be saved so they can be retried at a later time. When a new
DTC is added NMMGR considers this to be one change even if you save
data on many screens to configure this DTC. Run the NMMGR program and make all desired DTS configuration
changes. The network management configuration file must be NMCONFIG.PUB.SYS
for the configuration changes to become active dynamically.  |  |  |  |  | NOTE: If you are changing profile characteristics, you can
see which ldevs and DTCs will be affected by the change by pressing
the [Assoc Ldevs] function key
on the profile screen corresponding to the profile you are changing.
After pressing this key, you will see a list of all ldevs using
this profile in the DTCs configured in DTS. Refer to Chapter 7 “Terminal and Printer Profiles” for more information. |  |  |  |  |
After successful validation and cross-validation,
NMMGR will prompt you as to whether you want DTS changes to take
effect now. The following prompt will appear: Do
you want DTS changes to be become active now (Y/N)? | | Y = | all changes
made take effect now | N = | all changes
made will take effect upon next dynamic configuration or system
boot | H = | help | | > |
If you type Y,
dynamic configuration changes will take effect now. NMMGR calls
DTCCNTRL which dynamically implements the DTS changes made in NMMGR. If you type N,
dynamic configuration changes will not take effect now. Your changes
will take effect the next time dynamic configuration is invoked,
a DTS shutdown/ restart is performed, or the system is rebooted.
Dynamic configuration changes can be implemented later by calling
DTCCNTRL from the CI prompt any time thereafter. Or you can run
NMMGR again and select validate DTS/Link. See the section "DTCCNTRL
After NMMGR Exit," for steps on how to invoke the DTCCNTRL
command at the
CI prompt. If you type H,
you will see help text describing the options.  |  |  |  |  | NOTE: You can suppress the display of the question and have
DTS changes become active dynamically, without prompting, by using
capabilities within NMSTART as discussed later in this chapter. |  |  |  |  |
If you selected Y
in step 2 above and the DTS changes you have made are dynamically
configurable, no other action is required and changes will become
active automatically. You will see a message on the screen indicating
that no other actions are required. If the DTS changes you have made require additional actions
before changes become active, refer to Chapters 5 and 6, step 9,
for more information. If this is the case, you will see messages
on the screen indicating what actions are required before changes
become active. Refer to Table 4-1 “Dynamically Configurable
Tasks” for a
list of configuration changes that can be modified dynamically. After viewing the messages describing what actions
are required, if any, enter [RETURN]
when you see the prompt: (Press RETURN when finished viewing screen contents.) You will return to the Validation screen. From here you can
make further changes or exit NMMGR.
DTCCNTRL After NMMGR Exit |  |
If you choose not to invoke DTCCNTRL implicitly within NMMGR,
you can run the command from the CI prompt at any time after you
exit NMMGR. DTCCNTRL requires that you have a minimum of Network
Manager (NM) capability. The command can be entered either without specifying the desired
dynamic configuration operation or by specifying it using the syntax
outlined below: Dynamic configuration operation not
specified: :DTCCNTRL | 0 | exit | 1 | dynamically
implement DTS changes made in NMMGR | 2 | view status
of last DTS dynamic configuration | 3 | automatically
add a new DTC | 4 | shutdown
DTS subsystem | 5 | restart
DTS subsystem | 6 | manage/dynamically
configure host-based x.25 | 7 | help | | For
help on these topics, select 7 at the prompt below. | | Select
one of the numbers above corresponding to the desired operation: 1 |
Dynamic configuration operation specified: :DTCCNTRL func=dynconf
Refer to Chapter 5 “Configuring Serial Devices (for
Host-Based Management)”
and Chapter 6 “Configuring Serial Devices (for
PC-Based Management)” for more
information on actions required for changes to take effect.  |  |  |  |  | NOTE: You must have made all desired DTS changes in NMMGR
first before invoking DTCCNTRL from the CI prompt.To automatically add/configure a host-based managed
DTC to DTS without needing to specify detailed configuration information
such as DTC cards/boards and ldevs, refer to Chapter 3 “Automatic Configuration of DTCs” To manage/dynamically
configure host-based X.25 links, refer to the Configuring
and Managing Host-Based X.25 Links manual. |  |  |  |  |
Using NMSTART |  |
When NMMGR is run, one of the first actions it does is to
look for an ASCII file called NMSTART.PUB.SYS.
If this file is found, NMMGR will read the contents and attempt
to execute the commands in the file. A command can be placed in the file that will control the
display of the question "Do you want DTS changes to become active now (Y/N)?"
when validation is complete. The command has the following format: DTSDYNCONF [OFF|ON|PERMOFF] If NMMGR is run from a session and starts in maintenance mode,
and the DTSDYNCONF command
has not been called, DTCCNTRL will not be invoked and the prompt
will not appear even if there are DTS changes. If NMMGR is started
in screen mode and you switch to maintenance mode at the command
line, then the default is OFF. When DTSDYNCONF
is set to OFF,
the question and prompt will appear. NMMGR will wait for a response. When DTSDYNCONF
is set to ON,
and NMMGR is run from a session, the question will be displayed
but DTCCNTRL is invoked without waiting for a response. When DTSCYNCONF
is set to PERMOFF,
NMMGR will never display the question or invoke DTCCNTRL. When NMMGR is run from a job, NMMGR, will run in maintenance
mode and accept commands one line at a time. In this case, the "DTS
changes" question will not be displayed unless one of the
commands is "DTSDYNCONF ON". LOGDCC and LOGDCCBK Files |  |
When the system rebooted or a DTS shutdown/restart executed,
an ASCII file call LOGDCC.PUB.SYS
is purged and recreated to log DCC startup console messages, and
the results of any dynamic configuration operations. This file acts
as a log of all dynamic configuration changes since the last system
reboot or DTS restart. An example of the contents in LOGDCC.PUB.SYS
is as follows: ========== | WED, APR
16, 1996, 5:10 PM | DCC STARTUP | -
ENTER - version C0200xxx compiled 96xxxx | DCC STARTUP | -
OK | ========== | WED, APR
16, 1996, 5:16 PM | | <<
Deleting DTC02 in process... >> | | ** Deleting
DTC02 completed successfully. | | ** DTC02
changes completed successfully. | | <<
DTC01 changes in process... >> | | * Adding
TIO ldev 100 to card 0 (profile = TR10D96). | | * Adding
TIO ldev 101 to card 0 (profile = TR10D96). | | ** DTC01
changes completed successfully. | | <<
Adding DTC03 in process... >> | | ** Adding
DTC03 completed successfully. | SYSTEM
WILL COMPLETE DYNAMIC CONFIGURATION ONCE ADDITIONAL ACTIONS ABOVE
(IF ANY) ARE TAKEN. | | * New non-nailed
PAD profile TR10D96A. | | * Non-nailed
port changes completed successfully. | ACTION: | CHECK that
you have logged off any sessions or closed any jobs associated with
devices that have been changed. | | | SYSTEM
WILL COMPLETE DYNAMIC CONFIGURATION ONCE ADDITIONAL ACTIONS ABOVE
(IF ANY) ARE TAKEN. |
If the system is not rebooted or DTS restart is not done for
a long time, the file LOGDCC
may become full. If the file becomes full DTCCNTRL renames LOGDCC.PUB.SYS
to LOGDCCBK.PUB.SYS.
If LOGDCCBK already
exists it will be purged. DTCCNTRL will then recreate LOGDCC
so that this file will always contain the most current history of
dynamic configuration changes. Dynamic Configuration Status |  |
You can also use DTCCNTRL to check the status of the last
dynamic configuration.
To see the status of the last dynamic configuration, type the DTCCNTRL
command at the CI prompt either without specifying the desired operation
or by specifying it using the syntax outlined below: View status operation not specified: :DTCCNTRL | 0 | exit | 1 | dynamically
implement DTS changes made in NMMGR | 2 | view status
of last DTS dynamic configuration | 3 | automatically
add a new DTC | 4 | shutdown
DTS subsystem | 5 | restart
DTS subsystem | 6 | manage/dynamically
configure host-based x.25 | 7 | help | | For
help on these topics, select 7 at the prompt below. | | Select
one of the numbers above corresponding to the desired operation:
2 |
View status operation specified: :DTCCNTRL func=dcstatus If there were no errors from the last dynamic configuration
performed by invoking DTCCNTRL, you will see the message "No errors from last DTS dynamic configuration."
If errors occurred during the last dynamic configuration, you will
see the message "Errors occurred from the last DTS dynamic configuration. See LOGDCC.PUB.SYS for error detail."
Refer to the previous section in this chapter, "LOGDCC
and LOGDCCBK Files," for more information on the LOGDCC
file.
|