3.4.2 Precautions on backing up and recovering the execution registration status

To use the functions for exporting and importing registered execution-schedule information for jobnets, you must make sure that the importing environment matches the exporting environment so that jobs can be executed at the importing location.

If necessary, before you perform the import, use the procedure in 2.3 Restoring the setup information for a system that uses JP1/AJS3 to set up the environment in which jobs can be executed.

You can use the functions for exporting and importing registered execution-schedule information for jobnets if the host or scheduler service is not the same at the exporting and importing locations. Note, however, that you must adjust the character encoding and the linefeed codes in the file of registered execution-schedule information for jobnets, to match the importing environment.

The following describes the prerequisites for exporting or importing on different hosts or scheduler services, and the effects if the prerequisites are not met.

• Prerequisites related to the host

  Prerequisites	Effects when not met
  The name and setting of the time zone used when a jobnet was registered for execution must be the same for the exporting and importing locations.	A schedule with a different scheduled start time from that of the exporting location might be created.
  The agent host must be able to communicate with the exporting and importing locations.	If communication with the agent host is disabled, jobs cannot be executed during import.
  The host specified in a QUEUE job must be able to communicate with the exporting and importing locations.	If communication with the agent host is disabled, the QUEUE job cannot be executed during import.
  The language (Japanese, English, or Chinese) must be the same for both the exporting and importing locations.	If a multi-byte character is included in a macro variable that was specified when a unit was defined or when a jobnet was registered for execution, the variable will not be able to be imported, because the characters will become garbled.

• Prerequisites in the JP1/Base settings

  Prerequisites	Effects when not met
  The JP1 user who registered a jobnet for execution must be set in the user mapping at the importing location.	If the JP1 user who registered a jobnet for execution has not been set in the user mapping at the importing location, an error occurs during import.
  If the exporting authentication server and the importing authentication server are different, the same JP1 user access permission must be registered on both authentication servers.	If the same JP1 user access permission is not registered on the exporting and importing authentication servers, an error might occur during import or job execution.

• Prerequisites for a scheduler service

  Prerequisites	Effects when not met
  The local time of the importing JP1/AJS3 must not be later than the local time of the exporting location.	If the local time of the importing location is later than the local time of the exporting location, a schedule that has already been executed at the exporting location might be created again.
  When queueless jobs are used, the ajsqlsetup command, which sets up a queueless job execution environment, must also be executed at the importing location.	If the queueless job execution environment has not been set up, queueless jobs cannot be executed after the import.

• Prerequisites for the job execution environment

  Prerequisites	Effects when not met
  There must be transfer files for job operations at both the exporting and importing locations.	If there are no transfer files, an error occurs during job execution after the import.
  The agent and queues used for executing jobs at the exporting location must be defined at the importing location.	If the agent and queues used for executing jobs have not been defined, an error occurs during job execution after the import.

• Prerequisites for environment setting parameters

  The values of the following environment setting parameters must be the same for the exporting and importing locations.

  • Environment setting parameters related to scheduler services

    Environment setting parameter#	Effects when not met
    AJSCHARCODE (Character encoding for a scheduler service)	Any multi-byte characters contained in the unit definition or in a macro variable specified when a jobnet was registered for execution are represented in the character encoding specified in AJSCHARCODE. Therefore, if the character encoding specified in AJSCHARCODE is different at the exporting and importing locations, import cannot be performed because the characters after the import will be garbled.
    ROOTJOBNETSCHEDULERANGE (Time format of a root jobnet)	If a 48-hour schedule is set for the exporting location and a 24-hour schedule is set for the importing location, an execution date in a two-day schedule will be treated as the next day. Accordingly, when, for example, a jobnet is to be executed on an open day that is treated as the next day in a two-day schedule, no schedule is created if the next day is a close day.

    #

    The definition key is [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name].

    The following table shows the settings for the character encodings for each OS.

    Value of AJSCHARCODE	Value of the environment variable LANG when the ajsrgexport command is executed
    	HP-UX	Solaris	AIX	Linux
    SJIS	ja_JP.SJIS japanese	ja_JP.PCK	Ja_JP Ja_JP.IBM-932	--
    EUC	ja_JP.eucJP japanese.euc	ja ja_JP.eucJP	ja_JP ja_JP.IBM-eucJP	--
    C	C	C	C	C
    UTF-8	ja_JP.utf8	ja_JP.UTF-8	JA_JP JA_JP.UTF-8	ja_JP.UTF-8 ja_JP.utf8

    Legend:

    --: Cannot be used

  • Environment setting parameters related to the job execution environment

    Definition key	Environment setting parameter	Definition
    [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Queue]	MaximumQueue#1	Maximum number of defined queues
    [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Job]	MaximumContentJob#2	Maximum number of jobs in the system
    	AlterContentJob#2	Number of warning jobs in the system
    [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Agent]	MaximumAgent#1	Maximum number of defined agents
    	LeastRecentlyUsed#2	Definition of method used to determine the agent host that distributes jobs
    [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Resource]	MaximumResource#1	Maximum number of defined execution-locked resources
    [{JP1_DEFAULT|logical-host-name}\JP1NBQCLIENT\PathEnv]	All Users#2	Search path for the files to be transferred
    	JP1-user-name#2	Search path for the files to be transferred
    [{JP1_DEFAULT|logical-host-name}\JP1NBQCLIENT\Process]	MacroOptionReplaceMode#2	Replacement method used when the information passed by a macro variable is a NULL character string

    #1

    If the value is not the same, defining agents or queues might no longer be possible.

    #2

    If the value is not the same, job execution might be affected.

• Prerequisites for units to be imported or exported

  Prerequisites	Effects when not met
  A job must not be running on the exporting manager.	If the exporting manager goes down or a different host is specified for job execution, an error might occur during the execution of a job after the import.
  Neither a physical host nor a logical host at the exporting location must be specified for the host name of a QUEUE job.	If the exporting manager goes down or a different host is specified for job execution, an error might occur during the execution of a job after the import.
  If the unit being exported has been registered for planned execution, the unit full path to the root jobnet at the exporting location must be the same as that at the importing location.	An error occurs during import.
  If the unit being exported has been registered for fixed execution, the unit full path to the root jobnet at the exporting location must be the same as that at the importing location. The unit configuration in the root jobnet must also be the same at both locations.	An error occurs during import.
  When a jobnet specified to reference the calendar of another job group is imported, the job group to be referenced must have the same path as that at the exporting location, and must also exist at the importing location.	An attempt to register the jobnet for execution fails during import.
  When a jobnet with an exclusive schedule specified is imported, an exclusive jobnet that has same path as that at the exporting location must also exist at the importing location.	An attempt to register the jobnet for execution fails during import.
  When a root jobnet containing a jobnet connector is imported, the connection-destination jobnet must have the same path as that at the exporting location, and must exist at the importing location.	After the import, the status of the jobnet connector remains Running + Abend status during job execution.
  When a connection-destination jobnet is imported, a jobnet connector that has the same path as the job connector at the exporting location must also exist at the importing location.	During job execution after the import, the connection-destination jobnet operates as follows: When Synchro is selected for Exec. order method: The job is executed after the scheduled start time is reached. When Aynchro is selected for Exec. order method: The job is executed at the scheduled start time.

To Page Top