Hi,
I am new to datastage and presently working on an analysis assignment involving datastage server edition. While going through one of the routines , I have come across the following 2 $include statements :
$INCLUDE DSU_BP fkey_const.h ; * Constants stored in a common area
$INCLUDE DSU_BP fkey.h ; * Common/shared fkey functionality
Is there any way by which I can view the contents of the included files to understand the functionality of the various sub programs there inside the included files.
If yes, please tell me about the process.
server routine : information regarding $include files
Moderators: chulett, rschirm, roy
Fine, if this is true , then down the lines i have the following code in the routine :
GoSub FkeyWriteError
Does this indicate that this sub routine has been declared in the included C programs as I have done a rigorous search in Manager and unable to find any transform or routine with the name "FkeyWriteError
"
Thanks in advance
GoSub FkeyWriteError
Does this indicate that this sub routine has been declared in the included C programs as I have done a rigorous search in Manager and unable to find any transform or routine with the name "FkeyWriteError
"
Thanks in advance
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
These header files are in a sub-directory called DSU_BP in the project directory on the server (engine). They are not header files supplied with DataStage but, presumably, were written in-house or by a contractor. Since they are text files you can read them with any text editor. With a product like UltraEdit you can even read them from a Windows environment.
Usually, header files of this kind include only definitions of constants - in this case definitions of the escape sequences returned by function keys would be my guess.
Usually, header files of this kind include only definitions of constants - in this case definitions of the escape sequences returned by function keys would be my guess.
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.