General Options Section
Connect on Startup
– Connections started to the most recently selected source and destination are made whenever Transporter is started.
Read on Connect/New Data Type
– Once a connection is established between the source and destination, the data type used in the last Transporter session is read and displayed. If the data type is changed during the session, it is also read.
Include Duplicates (Replace Allowed)
– Displays any duplicate data objects on the
side in blue. If this option is not selected, then objects already existing on the
side are not displayed on the
side (since there may be no need to copy them again).
Note A job group will be displayed if at least one child job within that job group is not a duplicate even if the job group is duplicated.
– Specifies where the session log file(s) are written to.
By Default, session logs are created with
extension and saved to the user's Transporter Home directory under a subdirectory called sessions. This default location may be changed given this option.
Default location examples:
– For Windows:
C:\Documents and Settings\<user>\.transporter\session\transporter-20100506025113898.sess
Note A user's home directory is different on different platforms. The examples provided are specific to internal Windows XP systems and intended for demonstration only. Your configuration will be different.
Following are examples of user home locations by platform:
Microsoft Windows NT: <root>\WINNT\Profiles\<user> %UserProfile%
Microsoft Windows 2000, XP and 2003: <root>\Documents and Settings\<user>
Microsoft Windows Vista and 7: <root>\Users\<user>
– Displays a warning message each time a non-critical issue is encountered as data is copied. The operator has to acknowledge each warning message as it is displayed to continue the copying operation.
– Updates either the
(for Jobs) field with the names of the source, the user, and the date and time of the transfer of data objects.
Note If you are copying data objects, Transporter may not be able to annotate these objects. The Description text fields of data objects are limited to 4000 characters and there may not be any room available in the Description field to add annotations. Deleting text in the object’s Description field will provide room for annotations. If Transporter cannot annotate the data objects it is transferring, this is noted in the session log. This issue does not apply to jobs that are copied when using the Annotate option.
– Disables each job, event, or resource as it is copied into the destination. This option ensures that the object cannot be used in the schedule until the operator manually enables it. This option only applies to jobs, events, and resources; other objects do not have this attribute.
Job Transport Options Tab
Auto Select Dependencies
– If a job selected for copying has any predecessors, all of its predecessors are also automatically selected for copying. This option works in conjunction with the
Replace Existing Dependencies
Note The Auto Select option may affect system performance when used.
Replace Existing Dependencies
– Selects only a dependency if it does not already exist in the destination.
Auto Select Parent Group
– If a job selected for copying is a child job, then all of the parent job groups it belongs to are also automatically selected for copying.
Auto Select Children
– If a job selected for copying is a parent job, then all of its child jobs are also automatically selected for copying.
Auto Add (no errors, no conflict)
– Performs the Job transport operation automatically if no conflicts or errors are detected. If a mapping error or conflict occurs, the
Job Definition Mapping
dialog is displayed to resolve the problem interactively.
– Allows a Job transport as long as there are no errors during the copying operation, even if mapping conflicts occur. If a conflict between the source and destination is not resolved, that job may still run correctly but may be missing dependencies, variables, or events, etc.
– Enter a date in the text field or click on the down arrow to display a calendar where a date can be selected to indicate the earliest date that the copied job can be compiled into the schedule.
Warning Changing the default Effective Date (current date) from the current date while transferring job groups cause severe disruptions in the production schedule. Do not modify the Effective Date option to resolve this issue. Instead use one of two methods to transfer a job group with a future effective date. Either disable the job group and then transfer it with the default Effective Date (current date) or select the Disable Copy and No Compile options in this dialog before transferring job groups. After the job group transfer is complete, enable the job group and schedule it as needed.
Override Options Tab
– Sets the default handling of job output.
Figure 4-1 Configuration Options, Override Options Tab
Save Output Option
– Specifies what will happen to the job's output. If job output is saved, you can view it from the
tab of the
dialog. You can choose from the following options:
– Does not save the job output. (Default)
– Saves the complete output from each job instance, adding the output to the previous job instance’s output.
– Saves the complete output from each job instance, overwriting the previous job instance’s output.
– Selecting this option saves the job output in a summary form. This option is useful when jobs have long job output and you do not want the entire output file. Not available if the
option is selected.
– Enables the job to be inserted into the production schedule on an as-needed basis. The default is that unscheduled instances are allowed. If you do not want the job to run on an ad hoc basis, you can clear this option to prevent non-scheduled submissions.
Allow operator rerun
– Allows the operator to rerun a job. The default is allow operator reruns (options selected).
For UNIX, source user’s profile
– Allows you to execute Unix user profiles. This option provides for the execution of all variables in a Unix user’s profile. Without this option, Unix user profile variables that are referenced by scripts are not being executed, causing errors in TES.
Require operator release
– Holds the job until an operator releases it. The job will not run until it is released. When all the job’s dependencies are met, and it is ready to run, its status is
Waiting On Operator
. The information in the
tab) can inform the operator of any external requirements that need to be met before the job is released.
– Disables the job carry forward feature that appends the jobs that did not run in the current production schedule to the next day's production schedule. Any job from the current production schedule that is not in an
status when the next production day starts, will not be carried over to the next production day. The default is to enable job carry forward (cleared).
Job Transport Annotation Tab
– When an object is transported, a description of the transport operation is annotated to the description field of the object, if
is selected. This option provides for a customizable annotation message to the job description during transport. Use the
dialog to supply a global annotation message which will apply to all jobs during transport.
To override the global setting during interactive job transport, supply a new value in the
tab of the job transport.
The job is transported with the customized annotation included in the job's notes field. In the following example, the annotation has been overwritten by appending with
at the end.
Also, a description of the transport operation is annotated at the end of the custom annotation.