4.4.1 Overview of backing up and recovering the execution registration status

(1) Exporting the registered execution-schedule information for jobnets (ajsrgexport command)

The ajsrgexport command exports the execution registration status of jobnets (including the macro variables and time zones specified when the jobnets were registered for execution) to a text file. The information that includes the execution registration status of jobnets and the conditions specified when the jobnets were registered is called the registered execution-schedule information for jobnets. A file to which the registered execution-schedule information for jobnets is exported is called a file of registered execution-schedule information for jobnets. For details about the ajsrgexport command, see ajsrgexport in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1. For details about the file of registered execution-schedule information for jobnets, see 4.6 File of registered execution-schedule information for jobnets in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

When exporting information, you can specify the root jobnets listed below that have been registered for execution with planned execution or fixed execution selected. If you specify a jobnet registered for execution with immediate execution selected, the registered execution-schedule information for jobnets will not be registered.

• Root jobnet

• Root remote jobnet

• Root jobnet in a planning group

For a jobnet registered for planned execution, the nearest execution schedule is exported. For a jobnet registered for fixed execution, the nearest execution schedule and subsequent schedules are exported. In either case, execution results or dummy schedules are not exported. For details about the dummy schedule, see 4.4.2(1) Schedule simulation in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

Figure 4‒3: Execution schedules to be exported

For a jobnet registered for fixed execution, changes in the schedule made by temporarily changing the plan are also exported. Note, however, that these changes cannot be canceled at the importing location. For a jobnet registered for planned execution, changes in the schedule made by temporarily changing the plan are not exported. Therefore, you need to change the schedule again after the import.

To Page Top

(2) Importing the registered execution-schedule information for jobnets (ajsrgimport command)

The ajsrgimport command imports a file of registered execution-schedule information for jobnets (that was exported by the ajsrgexport command), and sets the same registration execution status set for the exported jobnets. For details about the ajsrgimport command, see ajsrgimport in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

For a jobnet registered for planned execution, the schedules are recalculated after the import based on the jobnet schedule rule. For a jobnet registered for fixed execution, the execution schedules after the date that the ajsrgimport command was executed are exported based on the contents of the file of registered execution-schedule information for jobnets.

Figure 4‒4: Execution schedules to be imported

The unit configuration in the root job group to be imported must be the same at the exporting and importing locations.

Import cannot be performed in the following cases:

• The JP1 user specified when the exported unit was registered for execution and the JP1 user who performs import are different.

• The specified unit is not found in the exported file of registered execution-schedule information for jobnets.

• The file of registered execution-schedule information for jobnets cannot be accessed.

• The file of registered execution-schedule information for jobnets contains a unit that does not exist at the importing location.

• The name of the file of registered execution-schedule information for jobnets contains more than 255 bytes.

• The file of registered execution-schedule information for jobnets contains an invalid definition.

• The specified unit does not exist at the importing location.

• The jobnet to be imported has already been registered for execution at the importing location.

• The import date exceeds the valid term for schedule rules of jobnets.

• The processing cycle or substitute schedule method is not specified in the schedule rule for jobnets.

• The jobnet specified in an exclusive schedule is not the same at the exporting and importing locations.

• There is no job group that references a calendar.

To Page Top