DSXchange

HarryHome - I now see what you are looking for. The value will be in the DSParams file in your project directory, set using the administrator.

In this case the value for PrototypeJob is supposed to be the name of a job, that line reads DS_JOBS to get the job number for that job name. The default value for this parameter is stored in the job design itself.

I just took a quick look at the object code and the backslash is indeed used as a field delimiter in a couple of places, so it is probably not too far off to assume that this character cannot (currently) be used within the user status. The question is whether IBM will change to code to allow the bac...

I just tried a job as you described and it compiled just fine at 7.5.1.2

Are you certain that your link actually connects to the stage (i.e. move the bulk load stage around and see if the link follows it in the designer)

I wasn't sure about the problem until I used the Forum's useful SEARCH capability and came up with this thread.

PeterPol - good job on locating the rather obscure cause. In some of the DS code the backslash is used as a string delimiter to store and parse out multiple types of values from one string. This is probably what is happening in your case with the userstatus. I would create a minimal job that reprodu...

wow - not quite holographic but good enough for me. I want one!!

The order for SQL actions should be "update existing or insert new"

Use the Designer to actually define a default null value for that column. In the input stage, highlight the column and right-mouse-click to "edit row" and set the null attributes.

Naren6786, my only thought right now is that we still don't know the exact syntax or your ds version.

I remember reading about the advanced technology in Dick Tracy's watch and was sure that one day it would become a common accessory and I would own one. That certainly leapfrogged past a mere timepiece! What I really think might be a near-future technology is a holographic keyboard. I really want on...

Fernando, the settings are tunables for when you have the DataStage disk cacheing enabled. By setting the DISKCACHE value your system is now enabled for public hashed file cacheing. This does not necessarily mean that you are using the functionality, as a number of conditions and job settings need t...

Could you please post the code in your trigger condition; it sounds like you might have some sort of a syntax error.

Try resetting the job and looking at the details of the log entry "from previous run" to see if you get additional information on the cause. Does the job also "crash" when run manually with the same parameters? Does it crash every time or just sporadically?

I would duplicate the link to the dataset in the job to also write to a comma separated sequential file, name it with a ".csv" extension and open it from Excel. Another option is to use the UNIX "orchadmin dump" option as documented and output the contents of the dataset to a sequential file and the...