I have been looking for a way to get the current DataStage version from a DataStage routine but haven't found anything in the API or documentation. Does anyone know of a documented way to get this information?
I am aware that I can use an entry in the UV.ACCOUNT file to get a project's version number and can also get some information through the VOC's "RELLEVEL" or the project home directory file ".dsrel"; but I wanted to write something that will withstand the test of time, especially with the upcoming changes to the underlying structures in DataStage.
Reading the current DataStage Version string in a routine
Moderators: chulett, rschirm, roy
</a>-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I am not aware of any function call in the API.
However, in DSVERSION.H (in DSINCLUDE) there is the declaration
that's fairly reliable. Lots of other version stuff in there too.
The following you might also find interesting. It's from DSR_ESRPROPS.H (again DSINCLUDE). They left out 40 (version 7.1).
However, in DSVERSION.H (in DSINCLUDE) there is the declaration
Code: Select all
EQU DSFullVersionStr TO "7.5.1.35"that's fairly reliable. Lots of other version stuff in there too.
The following you might also find interesting. It's from DSR_ESRPROPS.H (again DSINCLUDE). They left out 40 (version 7.1).
Code: Select all
3003: * Current job version string - must be an integer.
3004: * The numbers that have been used correspond to these releases:
3005: * 0 = SCT1 ; 1 = SCT2; 2 = FCS (1.0)
3006: * 3 = 1.1
3007: * 4 = 2.0
3008: * 5 = 3.0 (early builds)
3009: * 6 = 3.0 (FCS)
3010: * 7 = 3.1
3011: * 8 = 3.5
3012: * 9 = 3.6 development
3013: * 10= 3.6 (QA and FCS)
3014: * 11= 3.7 (Jakarta)
3015: * 12= 4.0.1 (4.0 NLS)
3016: * 13= 4.1
3017: * 14= 4.0.3
3018: * 15= 4.1.2
3019: * 20= 5.0 (Kobe)
3020: * 22= 5.2.1
3021: * 25= 6.0 (Viper)
3022: * 30= 6.1 (Rattler)
3023: * 35= 7.0 (Twister Alpha)
3024: * 36= 7.0 (Twister)
3025: * 50= 7.5 (Trinity)
3026:
3027: * Note that for major releases, we now increment the version number by
3028: * five, rather than one, to allow some leeway in case a new version
3029: * appears that needs to be slipped in before the major release.
3030:
3031: EQU DSC.CURRENT.JOBVERSION TO "50"
3032:
3033: * Values for version stamping
3034:
3035: EQU DSC.INITIAL.VERSION TO "0.0.0"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.