3.1.2 Precautions for backup and restoration

• If 2-byte codes are used in a unit name, make sure that the values of the LANG environment variables at the source and the destination are the same. For example, if a backed-up unit defined using 2-byte Shift-JIS codes is restored to a host that supports only EUC encoding, the restored unit can no longer be used.

• Before you restore a jobnet, cancel the registration of the jobnet.

• Do not back up or restore any units that are being referenced or updated. Before you perform backup or restoration, make sure that the jobnet work element is not being used.

• You must be authorized to update the units for which you back up units that you want to use for restoration. You cannot restore units, if you were not authorized to update them when you backed them up. A user with administrator privileges or superuser privileges can restore units that were backed up by a user without deletion authorization.

  Note that if the ADMACLIMIT environment setting parameter is set to yes, a JP1 user who has the following authorizations can back up or restore units:

  • Backup

    Authorization to reference all units to be backed up

  • Restoration

    Authorization to update all units to be restored

  For details about the ADMACLIMIT environment setting parameter, see 20.11.2(4) ADMACLIMIT in the JP1/Automatic Job Management System 3 Configuration Guide.

• When jobnets registered for release (release target jobnets) are backed up, only those definitions in Being applied status are backed up while those definitions in Release wait status are not backed up. Therefore, if you restore the backed-up jobnets, the definitions in Release wait status are not restored. If you want to back up and restore the definitions in Release wait status, you must also back up the release-source jobnets (the jobnets from which the definitions in Release wait status were registered for release). After restoring the definitions, re-register these definitions for release.

• A backup box contains backup information management files (.ajsbkup). When you change the attributes of the backup box, you must also change the attributes of the backup information management files.

• When you use the ajsprint or ajsbackup command or JP1/AJS3 - View to back up units, only the unit definition information is backed up. Execution results are not backed up.

• If you back up units by using the ajsprint or ajsbackup command or JP1/AJS3 - View to back up a jobnet registered for execution, the registration is canceled when you restore the jobnet by using the ajsdefine or ajsrestore command or JP1/AJS3 - View.

• You can use the ajsbackup and ajsrestore commands or JP1/AJS3 - View to manage several units collectively for each backup box. If you do not need to manage units collectively, you can use the ajsprint and ajsdefine commands to back up and restore jobnets.

• When you restore unit definition information backed up by JP1/AJS3, schedule definitions for nested jobnets might be different at the source and the destination.

  The following illustrates this problem.

  Cause:

  This problem occurs when all of the following three conditions exist:

  1. You copy a root jobnet that has a schedule rule, and define the copy as a nested jobnet.

  2. You use one of the following to back up units that include the nested jobnet described above:

     - ajsbackup command

     - ajsexport command

     - ajsprint command

     - JP1/AJS3 - View backup functionality

  3. You use one of the following to restore the units you backed up in 2 above:

     - ajsrestore command

     - ajsimport command

     - ajsdefine command

     - JP1/AJS3 - View restore functionality

  Result:

  The result is as follows.

  • For the schedule definition for the nested jobnet at the source, Depends on upper-level jobnet takes effect.

  • For the schedule definition for the nested jobnet at the destination, the schedule rule set for the nested jobnet takes effect.

  Action:

  If you set the AJSPRINTNETSCHPRF environment setting parameter to no for the scheduler service before you back up or restore the units, the unit definition information will be consistent at both the source and the destination. This setting is specified by default in a new installation of JP1/AJS3 or JP1/AJS2 version 08-00 or later. If you upgrade a version of JP1/AJS2 earlier than 08-00 and this setting has not been specified yet, you will need to specify it. For details about how to set the AJSPRINTNETSCHPRF environment setting parameter, see 4.2 Environment setting parameter settings in the JP1/Automatic Job Management System 3 Configuration Guide.

• When you specify a file name for a command argument, make sure that the file contents match the character encoding specified in the AJSCHARCODE environment setting parameter.

• If a unit definition file specified in an ajsdefine command is large, the command might abnormally terminate due to insufficient memory. If this happens, split the file so that each part is less than 200 MB.

To Page Top