Typically Used in Test Environment
Typically, VARY DYNAMIC PROGRAM is used in a test environment to accommodate new programs without shutting down the entire system. This allows you to execute programs that you have defined at runtime. All programs are eligible for dynamic definition, provided that they have not yet been defined to the system.
Modifying Dialogs, Edit and Code Tables, Maps, Subschemas
Dialogs, edit and code tables, maps, subschemas, and any other programs created by using a CA IDMS compiler or definition tool are automatically defined to the system when you generate them. To modify these programs, use the DCMT VARY PROGRAM command. DCMT VARY DYNAMIC PROGRAM typically is not appropriate for these entities.
Restricting Dynamic Definitions of New Program Versions
To restrict users from dynamically defining additional versions of a specific program, include the NODYNAMIC clause in the system generation PROGRAM statement that defines the program to the system.
Deleting Program Definition Elements (PDEs)
You can use the DCMT VARY DYNAMIC PROGRAM command to delete PDEs for automatically defined programs. Automatically defined programs are generated and defined to the system by DC/UCF compilers and definition tools. The number of these PDEs originally available to your system is specified by the UNDEFINED PROGRAM COUNT clause of the system generation SYSTEM statement.
Load (core-image) Libraries
If you do not identify a data dictionary by DICTNODE and/or DICTNAME as described above, DC/UCF assumes that the module resides in a load (core-image) library. If the program resides in a data dictionary, be sure to specify the dictionary and controlling DDS node (when necessary) in the DCMT VARY DYNAMIC PROGRAM command.
|
Copyright © 2014 CA.
All rights reserved.
|
|