APAR status
Closed as program error.
Error description
Transformer expressions that use macros eg DSJobName in Stage var variable perform significanlty worse that if hte equivalent expression is placed on the output link. There is an optimistaion used for the output link expression that is not used for the Stage Variable.
Local fix
As the macros are constant values, they can be set as initial values in the stage variable properties. Whilst they will not be optimiesed they will be evaluated only once and not every row.
Problem summary
**************************************************************** USERS AFFECTED: Server **************************************************************** PROBLEM DESCRIPTION: Non optimal code laid down for server jobs making use of stage variables which contain macros **************************************************************** RECOMMENDATION: In provided job a simple change to the job can achieve the performance improvement. No need to reevaluate stage variable for every row. ****************************************************************
Problem conclusion
Improved the handling of stage variables.
Temporary fix
Comments
APAR Information
APAR number
JR35896
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-18
Closed date
2011-08-26
Last modified date
2011-08-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
R850 PSY
UP
R810 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
26 August 2011