Folks,
On a bit of a trolling mission here...
I'm documenting ETL best practices and standards at my current client. One of the managers had experience with a tool that would check 3GL code for naming conventions, code layout, commenting, etc. and wondered if such a thing exists in our world. While I have never heard of such a tool for DataStage, I thought I would ask here to see what our community's experience in this area is.
Rob
DataStage Job Standards Checking Tool
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 209
- Joined: Fri Jan 09, 2004 1:14 pm
- Location: Toronto, Canada
- Contact:
DataStage Job Standards Checking Tool
Rob Wierdsma
Toronto, Canada
bartonbishop.com
Toronto, Canada
bartonbishop.com
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I have a routine that checks for existence of default names on stages and links, but not much more than that. We have many more standards but I have not given any thought to automatically checking; we normally advocate a process of peer review, because that also involves documentation and unit testing.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 209
- Joined: Fri Jan 09, 2004 1:14 pm
- Location: Toronto, Canada
- Contact:
My approach has always been to create templates of each data flow pattern. I ensure that the pattern adheres to all the standards. Each detail design specifies a starting pattern and adherence to the pattern / standards is enforced at code review time.
IBM is suggesting much the same approach.
Some of the development team here has used various tools that do a lot more for Java development. I can't see how something like that could work for DataStage though.
Rob
IBM is suggesting much the same approach.
Some of the development team here has used various tools that do a lot more for Java development. I can't see how something like that could work for DataStage though.
Rob
Rob Wierdsma
Toronto, Canada
bartonbishop.com
Toronto, Canada
bartonbishop.com
I like the idea....it certainly is do-able, but I haven't heard of anyone building such a tool.......one could comb thru [probably by examining a .dsx] link names, job names, job parameter names and lengths, etc. etc. etc.
As reflected above, most sites enforce best practices through review, and no one's had time (or hasn't publicized the success of such a thing) to create a "helper" tool along the way. A nice as such a tool would be, there would still need to be human/community review to ensure compliance.
Ernie
As reflected above, most sites enforce best practices through review, and no one's had time (or hasn't publicized the success of such a thing) to create a "helper" tool along the way. A nice as such a tool would be, there would still need to be human/community review to ensure compliance.
Ernie
Ernie Ostic
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You don't need a .dsx, at least until IBM eschews use of the local repository for design-time information. It's all there in DS_JOBOBJECTS (and can be verified against RT_CONFIGnnn if necessary).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
A good impact analysis application should be able to accomplish this, though inconveniently requiring the user to manually set up search routines.
We use Smart Technologies TS XL. It readily parses designer code from an xml-formatted export.
We use Smart Technologies TS XL. It readily parses designer code from an xml-formatted export.
Franklin Evans
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872