DSXchange

Satish,

the SDK persistent sequence calls use that hash file for storing data. Since this was the first time that any of the routines was called it created this file - you will not see this message again in this project. It is not an error, just an informational message.

Hello Raftsman, DataStage internally stores the date as an integer and the internal format for time is also an integer (number of seconds since midnight); there is no unified single timestamp format. One needs to program a small routine to take care of date addition and subtraction. It wouldn't be t...

Hello Accord,

this operation is not difficult in either Px or Server and you do not need to do any c++ or other coding to effect it.

In a transform just specify In.InDate[1,3]:'00':In.InDate[6,5] in both flavors to get the required format.

It is much safer to perform a fresh install than to try to fix problems - especially when you don't know exactly what did not get installed correctly in the first place. Since you mentioned that this was a fresh install I (perhaps mistakenly) assumed that you could quickly and easily repeat this pro...

Kumar,

it looks like you have a bad DataStage installation, the catalogue space should contain many entries and commands such as MAP need to function correctly.

Did any errors occur during your previous installation that you might have overlooked?

From the Admin or UniVerse prompt execute the command 'LIST VOC WITH @ID EQ "RELLEVEL" F2' and that will show you the DataStage detailed version for that account.

Hello Kumar, the routine *NLS.LISTMAPS should be globally cataloged within DataStage; I just checked our system and it is present. If you enter the DataStage command "MAP" from the Administrator or from the DataStage client you will get several hundred lines, and one of them should contain the strin...

Saad, so this thread in the Server forum is finished - DS outputs NLS characters as it should. Now you need to start a discussion in the QS forum asking why German characters are not being correctly read in. I haven't used QS in a long time so am not able to help you on that front. I would try to ha...

Gopskrish, you have identified the reason for the deletion failure - insufficient access rights. Now you need to revisit your user setups and group permissions and perhaps also your umask settings. Who is the owner for the files you can't delete? The subject is exhaustively described in the DataStag...

Hello VasnathRM, accessing the internal tables is not a good idea, as the structure is not officially documented and are subject to being changed in the next release. I would recommend against looking at these tables directly. If you look up information on the external program dsjob it will let you ...

Saad,

according to the standard ASCII tables the capital-O-umlaut is supposed to be 214. This means that DataStage is writing this value to your output file correctly, unless you have specified a conversion on the output stage. Is this correct?

Got it - I reread the post and had missed the multiple projects portion.

the command line program "dsjob" will return the status for a job. You can write a perl script or even a DataStage job around either this external call or by using the DSGet...() calls to write your own program.

VasanthRM, you can specify an automated reset-before-run when calling a job activity in a sequence. If you start the jobs from outside of DataStage from a command line you can use the -mode reset instead of -mode normal to reset the status before running a job. The subject of job logs has been handl...

Shiva, the built-in functions cannot handle this request directly, you would need to a short function yourself to do this. CleanIdentificationNumber(InString) {for each character in the string} {if < '0' or > 'Z' then remove} {if I, O or Q then remove} {nex...

If you want nulls in a sequential file column then set that column's definition to "nullable yes" and in the sequential file format set the "null field value" attribute to \000