Can any one please send
Best Practices for coding in Datastage.
For example.
1)Null handling must be done.
2)Parameters shud not be hard coded.
Best Practices for coding in Datastage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 94
- Joined: Sun Jul 18, 2010 11:35 pm
Re: Best Practices for coding in Datastage
Best Practices are rarely as simple as the examples you mention, quite often are dependent upon the situation.
1) Null handling must be done to examine and manipulate nullable columns within a transformer stage.
2) Parameters which are likely to change value from run to run, or over time, should not be hardcoded.
IBM has two redbooks which provide job design best/standard practices for DataStage development and are available as PDF files from the Redbooks website www.redbooks.ibm.com
"IBM InfoSphere DataStage Data Flow and Job Design" #SG247576
"InfoSphere DataStage Parallel Framework Standard Practices" #SG247830
Both are aimed at the parallel framework and not DS Server.
Regards,
1) Null handling must be done to examine and manipulate nullable columns within a transformer stage.
2) Parameters which are likely to change value from run to run, or over time, should not be hardcoded.
IBM has two redbooks which provide job design best/standard practices for DataStage development and are available as PDF files from the Redbooks website www.redbooks.ibm.com
"IBM InfoSphere DataStage Data Flow and Job Design" #SG247576
"InfoSphere DataStage Parallel Framework Standard Practices" #SG247830
Both are aimed at the parallel framework and not DS Server.
Regards,
- james wiles
All generalizations are false, including this one - Mark Twain.
All generalizations are false, including this one - Mark Twain.
-
- Participant
- Posts: 94
- Joined: Sun Jul 18, 2010 11:35 pm