3.4.3 Cautionary notes on backing up and recovering the execution registration status
The following are cautionary notes regarding the functions for exporting and importing the registered execution-schedule information for jobnets.
-
When the information is exported while generations are being created or deleted
The export function exports the registration status existing when the export command (ajsrgexport) is executed. Therefore, if the export command is executed during the creation or deletion of generations (while registering period-based fixed execution, temporarily changing an execution plan, or canceling registration), the generation being created or deleted is exported as is.
The following example shows how export is performed during the creation of generations.
Figure 3‒5: Example of export performed during the creation of generations (for fixed execution registration) ![[Figure]](GRAPHICS/ZJ040020.GIF)
For example, Figure 3-5 shows that fixed generations are to be created from April 1 to April 6. If the registered execution-schedule information for jobnets is exported when only the generations up to April 2 have been created, only those generations will be output. The generations for April 3 and after are not exported.
Do not export the registered execution-schedule information for jobnets while generations are being created, such as during processing that registers execution, cancels registration, or temporarily changes execution plans.
-
For a jobnet with a start condition defined
If a start condition is defined and a valid range is set in the jobnet's schedule rule, the following information up to the time of export is not output: the number of times an event defined as the start condition occurred, and the monitoring time. For example, if the valid range for the event count is set to 5 for the start condition and two events have already occurred when the export is performed, the monitoring continues after the import until the event has occurred five times.