The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Once Transporter is connected to the selected source and destination, you may want to configure the way the application works. You can modify how Transporter operates on initial startup and the way it works when copying data objects. The configuration options that are selected are saved for future sessions.
Clicking Continue on the Transporter toolbar or selecting the Configure option from the File main menu displays the Configuration Options dialog.
Use this dialog to configure Transporter to work according to your personal preference.
Some options can be locked down so that no one without Superuser authorization can modify the settings. These options have a Restricted check box beside them.
Note Users without Superuser security will not see the Restricted check boxes.
If a configuration option has been restricted, that option is unavailable to other users. These configuration restrictions apply only to the selected destination. If another source is selected for the destination, then the same restrictions do not apply.
Transporter options are saved in the user's Transporter Home Directory to a file called user.props . For example, a file called user.props will be created in the following directory:
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>
This section describes the options in the Configuration Options dialog.
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.
By Default, session logs are created with .sess extension and saved to the user's Transporter Home directory under a subdirectory called sessions. This default location may be changed given this option.
– 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>
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.
– 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 option.
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.
– Allow Conflicts – 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.
– Effective Date – 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.
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 Output tab of the Job Detail dialog. You can choose from the following options:
– Summary Only – 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 Discard option is selected.
– Allow unscheduled – 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 Operator Instructions field ( Description tab) can inform the operator of any external requirements that need to be met before the job is released.
– Disable carryover – 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 Active or a Launched 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).
To override the global setting during interactive job transport, supply a new value in the Annotation 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 xx at the end.
Also, a description of the transport operation is annotated at the end of the custom annotation.
These compiling options are used to control compilation of production schedules at the destination, during job transport. When a job is transported, the job update will affect the destination production schedule given the options selected.