...
Server Job Name | Generated Assets | Description | Example |
|---|---|---|---|
| Job Sequence: | Top-level Job sequence |   |
Parallel Job: Parallel Job: Parallel Job: | Component Parallel Jobs |
...
To support the co-residence of generated Parallel Jobs with their Server ancestors either the original Server Job or its Parallel derivate will have a suffix appended to the Job name. This option is specified in the transfer section of the S2PX config file. The section allows you to specify how the S2PX conversion process names handles the potential conflict between Server assets and their Parallel equivalents. The decision on whether to rename Server Jobs or not will have implications for your Job scheduling/orchestration mechanisms. Valid options are:
BACKUP_SERVER_JOB | RENAME_PARALLEL_JOB | |
|---|---|---|
Transfer Strategy |
|
|
Suffix |
|
|
Original Server Job |
|
|
S2PX Output Server Job |
|
|
S2PX Output Parallel Job |
Notes
BACKUP_SERVER_JOB
MyOriginalJob
MyOriginalJob_S2PX
MyOriginalJob
|
| |
S2PX Hashed File Migration Output Server Job |
|
|
|---|---|---|
Notes | Rename Server Job with a suffix and reuse its original name for the new Parallel Job. Existing job orchestration/scheduling mechanisms(DataStager Job Sequences, Control-M schedules, Shell scripts, etc.) will now work with the new Parallel Jobs. |
RENAME_PARALLEL_JOB
MyOriginalJob
MyOriginalJob
MyOriginalJob_S2PXRetain Server Job’s original name and use its name with a suffix for the new Parallel Job. Existing job orchestration/scheduling mechanisms(DataStager Job Sequences, Control-M schedules, Shell scripts, etc.) will continue to work with the existing Server Jobs as normal. |