Global variable

ray.wurlod · Post by **ray.wurlod** » Sat Jun 21, 2003 5:43 pm

Depending on the platform on which you're executing, you should be able to get a CPU millisecond count using SYSTEM(9) and the current system time in milliseconds using SYSTEM(12); in the latter case you may (probably will) need to enable collection of milliseconds using compiler directive $OPTIONS TIME.MILLISECOND

Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518

trobinson · Post by **trobinson** » Sun Jun 22, 2003 8:19 am

How do I format the oconv for milliseconds? The Help examples are only to the second. I'm told by Ascential that DataStage 5.2.1 on HP-UX 11.11, which is our system, cannot support milliseconds without a patch. This illustrates Ascential's overall shortcoming with designing a realtime architecture. They can come out with functional Realtime Bells and Whistles (7.0) and call it a silk purse but until they upgrade their core architecture to support real-time, its' still a sow's ear. How's that for mixing metaphors?

ray.wurlod · Post by **ray.wurlod** » Sun Jun 22, 2003 9:31 pm

Well, if HP-UX can't deliver milliseconds, it is surely unreasonable to expect DataStage Engine to retrieve milliseconds from the operating system environment? DataStage Engine acquires system time by making calls to system functions.

Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518

trobinson · Post by **trobinson** » Mon Jun 23, 2003 6:15 am

Yeah, that would be unreasonable. However, it is a DataStage patch not a UNIX patch.

battaliou · Post by **battaliou** » Mon Jun 23, 2003 10:35 am

I've been playing with named pipes for temporary unix variables. You will need to create a named pipe using the mkfifo command, then you can echo to it and extract from it eg:
$ mkfifo martin
$ echo 88 > martin &
$ head martin

This remains fairly persistent, although it requires re initialisation after extract.