LOADTBL

Purpose

Use the LOADTBL command to dynamically load a new routing table. You, as a z/VM® user or an NCCF or NetView operator, can specify whether the currently assigned logical operator should be replaced by the logical operator specified in the new routing table.

Operands

filename

is the name of the routing table to be loaded. If the file name is not given, the default routing table (file name = PROP) is used.

RPL

replaces the currently assigned logical operator with the logical operator specified in the new routing table. The logical operator is replaced only after the new routing table has been successfully loaded.

If RPL is not specified, the logical operator in the new routing table simply becomes the new default logical operator, and any explicitly assigned logical operator (that is, a logical operator assigned by the LGLOPR command) remains the logical operator.

Usage Notes

1. If any action routines named in the specified routing table can not be located or loaded, an error message is issued, and the programmable operator facility drops any action routine modules associated with the specified routing table. It then tries to reload the action routine modules associated with the routing table that was active before the LOADTBL command was issued. If it cannot load these modules, the programmable operator facility terminates operation.
   Note: If any of the action routines associated with the previous routing table were modified (that is, replaced in LOADLIB) between the time the programmable operator facility dropped the specified routing table modules and reloaded the previously active routing table modules, the modified version of the action routines are used when the previous routing table is reloaded.
2. Only the file name is used to identify the routing table file to the LOADTBL command.
3. Because DMSPOL is the action routine module executing the LOADTBL command, it is not dropped and reloaded as are the other action routine modules listed in the routing table. If you want to alter or replace DMSPOL, you must stop the programmable operator facility (using the STOP command), make the desired changes or replacement, and invoke the programmable operator facility again. See Invoking the Programmable Operator Facility for information about starting the programmable operator facility and Stopping the Programmable Operator Facility for information about stopping the programmable operator facility. For information about writing a new programmable operator facility action routine, see Writing Action Routines.

   If the programmable operator virtual machine is set up so that the programmable operator is started automatically when CMS is IPLed in that virtual machine, it is sufficient to do the replacement and then IPL CMS again.

4. With the loading done by DMSPOL, it is possible for the other routines in DMSPOR to be replaced when a LOADTBL occurs. This permits changes to action routines other than DMSPOL to be made dynamically, without stopping the programmable operator. It is also possible to specify the name of a table to be loaded as a parameter to the action routine. The logical operator will be notified of the loading.
5. If the current logical operator is the default logical operator (not explicitly assigned), then the current logical operator will be replaced even if the RPL option is not specified.
6. When you issue LOADTBL and replace the logical operator, both the old and new logical operators receive the following message:

   DMSPOR758I {NCCF|VM} user userid [nodeid] is now LGLOPR
   for PROP on node nodeid

   Both operators receive this message, even if you have not specified the RPL option.

Responses

The programmable operator facility responds with:

New RTABLE not loaded

PROP terminated

PROP running with routing table fn ft fm