Cisco Cisco Workload Automation 6.3 User Guide

Transporting Data Objects

Transporting within the Same Database



– The Variables tab displays the variables associated with the job named in the Job Name field. These 

variables are arranged in two columns, From Master Variable and To Master Variable. At the bottom of the 
Variables tab is a Show Usage button that displays how the variables are used in the job. Unmapped variables are 
displayed as conflicts since jobs do not usually require variables.

You can use the Delete key to clear out non-required fields. This is the same as selecting <<Remove>> from the 

destination list



– The Dependencies tab displays the dependencies associated with the job named in the Job Name 

field. These dependencies are divided into three types of dependencies: job dependencies, variable dependencies 
and file/JES dependencies. Each type of dependency is arranged in two columns, From Master Dependency and 
To Master Variable. Unmapped dependencies are displayed as conflicts since jobs do not usually require 
dependencies

.

You can use the Delete key to clear out non required fields. This is the same as selecting <<Remove>> from the 

destination list

In the To Master Agent list, use the <<Remove>> option to remove the corresponding File or JES dependency. 

This option is not used to remove an Agent.



– This tab displays the job events associated with the job named in the Job Name field. These job events 

are arranged in two columns, From Master Event and To Master Event.



– This tab displays the job resources associated with the job named in the Job Name field. These 

resources are arranged in two columns, From Master Resource and To Master Resource.

You can use the Delete key to clear out non-required fields. This is the same as selecting <<Remove>> from the 

destination list.



Options – This tab allows you to set the default handling of job output.



– When an object is transported, a description of the transport operation is annotated to the Description 

field of the object, if Annotate is in effect. This option provides for a customizable annotation message to the job 
description during transport. 

The Interactive Job Definition Mapping dialog displays the following buttons:



– Accepts the changes you have made, saves the job, and displays the next job to be mapped, if any. When 

there are no more jobs to process, the dialog is closed. If a mapping error is not resolved, the Accept button is 
unavailable and you can only cancel the job and go to the next job for processing. The dialog updates with data for 
each job in process.



– Accepts all selected jobs for transport without displaying the mapping dialog for the job. Jobs with 

errors will be skipped. Jobs with only conflicts will be accepted only if Allow Conflicts is enabled. Use this option 
only if you are confident that all items were properly mapped earlier. Selecting the Accept All button displays the 
message”Only jobs without conflicts or errors will be accepted automatically. Proceed?”



– Closes the displayed job’s mapping dialog without saving any changes to that job and moves on to the next 

job, if any.



– Closes the Job Mapping dialog and cancels processing for jobs that have not yet been processed 

during the current transport operation. Jobs that were accepted earlier during the session will still be transported. 

Transporting within the Same Database

You can transport jobs and job groups within the same database, but the source and destination job cannot be the same. 
The job or job group must be mapped to a different parent if there is an existing parent or to a new parent if none exists.

Transporting within the same database only applies to Jobs; all other tabs are disabled.