Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Transmuter ‘Recipes’ are files which define an ordered combination of Transmuter Functions which work together to deliver a useful transformation for your DataStage assets.

Name

Config File

Description

Change prefetch memory

recipes/change_prefetchmemory.yaml

Change the prefetch memory setting for an ORAOCI9 stage to 102,400,000
Demonstrates use of the InsertAttribute transform.

Add unit test parameter

recipes/add_unittest_parameter.yaml

Add the $DM_ENABLE_UNIT_TESTING parameter to all jobs in the target folder structure
Demonstrates use of the InsertJobParameter transform.

Remove unit test parameter

recipes/remove_unittest_parameter.yaml

Remove the $DM_ENABLE_UNIT_TESTING parameter from jobs in the target folder structure that have it
Demonstrates use of the RemoveJobParameter transform.

Change library path and file type

recipes/changeStaticLibToDynamicLibFilename.yaml

Search the modulePath attribute (of parallel routine definitions, typically) for a given pattern, and replace it with a different directory path, keeping the base name of the file but changing the extension from .o to .so. This changes a statically linked routine to dynamic, helping ensure coherence of routine definitions and routine implementations.
Demonstrates use of the SearchAndReplace transform.

Fix ODBC SQL placeholder issue

recipes/fix_odbc_sql_parameter_issue.yaml

This recipe fixes an issue where the following warning is displayed when migrating an ODBC stage using CCMT:

[WARN] WARNING: The number of placeholders in the UPDATE statement does not match the number of key flow variables so placeholder substitution will not occur.

Demonstrates use of the RemoveElement transform.

NOTE: This warning can occur due to a genuine bug in the job in which case this recipe will not fix it. This is a fix for a specific, unusual scenario (described in the YAML file).

Example YAML file

This file essentially defines an ordered set of transform THINGS, each describing the name of a transform function and other properties required by that transform. e.g:

 - transform: AppendToAttribute
   xpath: //contains_JobObject[@stageType]/@name
   appendString: _I_AM_STAGE

 - transform: PrependToAttribute
   xpath: //contains_JobObject[@stageType]/@name
   prependString: MY_NAME_IS_

Note that this file has more than one transform. Each transform is performed sequentially, so for any given isx the first one will be applied to each DataSstage object within that isx before the second one is applied.

  • No labels