1.7.3 Notes on operation
-
If both of the following conditions are satisfied, the processing results of import might be invalid. Do not perform import if these conditions are satisfied.
-
A character string unit= or eun= is defined in a second or subsequent line in one of the following items:
• Command statement for a UNIX job
• List of message texts for an email reception monitoring job
• Explanation in Windows event-log monitoring job
• Message text for an email sending job
• Command statement for a custom UNIX job
-
A unit that is not immediately under the root job group and that is on the same level as a unit containing a job that satisfies the above condition is imported.
-
-
If a huge amount of definition information is output to a cell, the color of the record changes and the KAVZ0310-W message might be appended. Note that if the record with the message is exported by selecting either Batch or Individual, either an error occurs or definition information is lost. When exporting, delete or correct the content of the cell with the problem, and execute export.
-
Do not press the ESC key while import or export or the ajsdaconvert command is being performed, since this may cause the results of inherited or terminated processing to become invalid.
-
The default display of the results of importing or exporting may differ between JP1/AJS3 - Definition Assistant and JP1/AJS3 - View.
-
Exporting unit definition information that is not supported by the destination manager host causes an error. You must delete the unsupported unit definition information before exporting.
Before you attempt to export the unit definition information imported from a higher version to a lower version, delete the items that are supported in versions later than that of the destination manager host.
-
JP1/AJS3 - Definition Assistant does not run properly if a character set that differs from the character set used in JP1/AJS3 - Definition Assistant is used to define any definition information on the destination manager host.
-
JP1/AJS3 - Definition Assistant internally executes JP1/AJS commands for performing importing and exporting. For details about the specification of command operations and about errors, see the appropriate JP1/AJS manuals. The following lists the commands used for importing and exporting:
Importing
-
ajsprint, ajsname#
#
If you specify Y for the IMPORT-UNIT-NUM-CHECK environment settings parameter
Exporting
-
ajsprint
-
Batch: ajsdefine
-
Individual: ajsdefine, ajschgnet
-
Modification: ajschange, ajschgnet, ajschgjob, ajscalendar
-
Deletion: ajsdelete
-
-
If you import a unit containing a tab character in its unit definition information, the import processing result might be invalid. Do not import a unit containing a tab character in its unit definition information.
However, if a tab character is used in Command statement in the Basic job definition information section or in the definition items in the Other definition information section of the unit definition information, the result will not be invalid. For details about the display during import when a tab character is used in Command statement in the Basic job definition information section or in the Other definition information section, see 5.1 List of definition items.
-
If you try to change a definition item for which multiple definitions can be specified by using a line feed (Alt + Enter keys), all the definitions in the cell, including blank lines, will be changed.
-
The Last updated time section is used for confirming the last date and time that a unit was updated at the time of import. Accordingly, the value in the Last updated time section cannot be changed and is not exported.
-
If a unit with the same name already exists, the batch definition or individual definition function deletes the unit and then re-creates it. For this reason, if an error occurs during the re-creation processing, the unit might be deleted.
-
With JP1/AJS3, characters that you cannot use differ depending on the type of character encoding. For information on characters that cannot be used in JP1/AJS3, see the part that Language type and character encoding of the system in the manual JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
-
When the machines used for import and export are different, JP1/AJS3 - Definition Assistant with the same version and the same number of bits must be used on both machines.
-
When you want to use the definition information management template created by JP1/AJS3 - Definition Assistant with a different number of bits, use the ajsdaconvert command to convert the file format. Note that a file can be converted from xlsm format to xls format only if the number of definitions is 65,000 units or less.
-
For units in a suspended state to learn how to recalculate a schedule according to whether the unit was created in a batch or an individual export, see the part describes how to change job and jobnet definitions without unregistering the jobnet in the manual JP1/Automatic Job Management System 3 Overview.
-
If a jobnet is referenced that is scheduled to be registered for execution, or a jobnet that is registered for execution specifies a future generation number, when an overwrite update by a batch or individual export is performed, the jobnets that reference the following units will change to shutdown status, because the operation schedule was not recalculated. As a result, some of the jobnets scheduled to be executed might not be executed.
-
Job groups that reference calendar information according to Refer to a calendar of another job group
-
Jobnets that reference a schedule according to Exclusive schedule
For this reason, if you perform an overwrite update on the above units by batch or individual export, after unregistering a jobnet that is scheduled to be registered for execution registration or a jobnet that is registered for execution, export the jobnet or change the unit definition by performing a change export.
-
-
Do not export a root jobnet that has a release entry. If you do so, the release information in the target root jobnet is initialized, and the release entry is removed. If a jobnet has a release entry, cancel the release, perform the export, and then re-execute the release entry.
-
Execution file name in the Basic job definition information section of an R3 job is the path to the execution program that is linked to the custom job. It is important to note that if this definition is changed, the custom job might not work. Execution file name in the Basic job definition information section of an R3 job cannot be changed or exported. To change the file name, perform a batch export or separate export.
-
CP specified with the environment settings parameter RESTRICT-CHAR-RANGE is valid only within the scope of application of the JP1/AJS3 - Definition Assistant functionality. Thus, when you attempt to start JP1/AJS3 - Definition Assistant as a tool from JP1/AJS3 - View, if any unit name contains any of the characters listed below, your attempt to open JP1/AJS3 - Definition Assistant could fail regardless of the setting specified for RESTRICT-CHAR-RANGE. In this case, you have to perform import after starting the definition information management template.
" & ' * < > ? [ \ ] ^ ` { | } ~
-
If you perform import or export for a unit whose name contains any of the characters listed below, the message KAVS0183-E Unit name is too long could be output even when the complete name of the unit is no longer than 930 bytes. In this case, either remove the following characters from the unit name or change the target unit from the unit in question to the upper unit, and then perform import or export.
" & ' * < > ? [ \ ] ^ ` { | } ~