DSXchange

Benny, the COBOL redefines shows that you don't need to do any conversion at all - in the job input file column definition tell DataStage PX that you are getting a CHAR(1) column and also specify that no conversion is to be done on that column and -presto- you have done the same thing as your REDEFI...

snassimr,

All of the guides can be downloaded here

Nima,

nanosleep is used in Unix as the sleep/wait/do-nothing command, but I think you might need to post some more information on what the job does - i.e. do you issue a SLEEP call in there somewhere? If not, what does this job do (i.e. which stages does it call)? Is the error reproduceable?

Vinod,

I hope you can now answer those 3 interview questions

Vinod,

who said you need to use a load stage? If you read the documentation it will describe the reasons for not being able to use the bulk loader stage, in which case you would revert to a normal load stage.

Christina, the information you are looking for is not available by looking at files from the operating system, the information is contained within the DataStage files. You can write a DataStage job / function which will loop through all the jobs in a project and use the DSGetJobInfo() function with ...

Lali_swam, it might be that your job is still running as a process, check a "ps -ef | grep ds" to see if you find it, or go into the Cleanup Resources tab in the director to do so. Once that is gone you need to ensure that the locks that this job might have are also cleared, this should be done with...

Since the Pre/Post commands are Uv/BASIC calls you will only be able to do this from the BASIC transformer (as you've discovered) as well as at the Pre/Post JOB level. Wouldn't it be nice to get the best of both worlds - the ease of Uv/Basic coding plus the speed of PX.

Garthmac,

I just remember doing this once and it wasn't the correct formula (it was in Germany and I recall looking up a DIN norm for the calendar week; something to do with the number of days in the first week of the year changing the start date...)

You can go into the DataStage command line environment and do a HELP ANALYZE.FILE or you can do something really brave - download the .PDF file UniVerse Administering UniVerse, Version 9.6 and read the documentation

Garthmac, I think that there are a number of different methods of computing the calendar week. I would start off with the following: INT(OCONV({InternalDate},"DJ")/7)+1 This would be CW 1 for days 1 through 6 of the year, 2 for 7 through 13 and so on. Modify to yo...

snassimr, you stated that you have a static hash file. Normally the only way to do this without going into the DataStage command line is by specifying the create options in the job's hash file stage. The file is not created until you run the job for the first time. Unless you specifically set the st...

Hmm... I think I am using the same method that they are in order to find out who the parent process is; but it still involves iterating through the instances until you get a match.

I'll post the causes and (hopefully) the solution when I get it.

snassimr,

if you used all the defaults in the hash file stage, it will be in the project directory.... After you run the job the first time...

Ray - I actually created a common DSDetachJob interlude so that I could play around with debugging information and even commented out the statement, the error is then evinced elsewhere! It seems that somehow the internal common variables that hold the open and used JobHandles are getting very mixed ...