DSXchange

Is the other number just as large, or might the conversion be limited to int and not bigint numbers?

lstsaur,

yes, the price difference (whatever it may be) is definately worth it to many organizations.

I have a job which puts together a Varchar(32) string variable that contains a timestamp in the form "2005-01-01 12:13:14.567891". When I move this to a TimeStamp defined column (extended is switched on) using the StringToTimestamp(StageVar,"%yyyy-%mm-%dd %hh:%nn:%ss.6") it converts correctly but st...

You might use the following in a routine: OPENPATH '\imsv14\SAILDEV\hashfiles\Hash_BEngTaxonomyTermGroupKey' TO FileToClearPtr ELSE CALL DSLogFatal('Unable to open file','') CLEARFILE FileToClearPtr ON ERROR CALL DSLogFatal('Uanble to clear file, status is "':STATUS():'"...

Mayer, as you have noticed, the CLEAR.FILE command does not accept file paths, it expects to have the filename you use declared as some type of a file in the local VOC and is not meant for remote files. Instead of using a UNIX command I think it advisable to use a DataStage job to clear the file usi...

The site I am at is using CITRIX for DataStage clients, both 7.1 and 7.5, with no problems.

hhh, it doesn't matter what you do in the transform, if the incoming column has nullable=no then it is dropped before it gets to your transform logic. Your error message "Format_NV_Tfm,0: Field 'P_MKTPRC_BAM' from input dataset '0' is NULL. Record dropped. point to this. In the INPUT definition for ...

The basic rule in PX jobs is that if a column might contain null values then the nullable attribute MUST be set; so in your source table you need to set those columns potentially containing nulls so that they are nullable=yes. You can specify attributes on input to change nulls to some other charact...

Meorz, does your director log show any additional information on the abnormal termination? Sometimes when you RESET a job you will get additional information on the cause for an abort. Does this job do anything in a transform stage? One option you have is to clear out the contents of your project's ...

Radidwh, if you are only upgrading from one DS version to another, there is no reason to modify UNIX level items such as scripts. If the two versions are on different machines with different OS levels then that question is best asked in a UNIX support forum. If you search on "upgrade" and "7" in thi...

Balaid, I would recommend printing them out and typing them in by hand Seriously - please tell us which database you are loading and which method you are using. Whenever records get rejected some description of the error is written, either to the log file or to another file. You can also activate th...

hman,

but you are getting your error BEFORE you handle the nulls in your transform. The error looks like you have declared the incoming columns to be non-nullable even though they do contain null values. PX is quite picky about this, you can get away with it in a server job but not in PX.

MartinD, I am assuming that you mean training apart from that offered by Ascential/IBM? Ray will certainly get back to you on this one, as that part of the globe is in his bailiwick. Depending on number of pupils (and payment), there are consultants in this forum who would hold such a course as well.

All of your old project work will import into version 7.x You might have to change some jobs because of the new parameter handling (in older versions you could change job parameters within the job, that is no longer allowed and causes jobs to fail). Since Server jobs are compiled within the engine t...

Is your rule to convert any input date into the last day of the next month? If so: 1. Use ICONV with DM code to get the month number of the date 2. USE ICONV with DY code to get the year from the date 3. Add 2 to the month, checking for year overflow 4. Build a new date from {year}:'-':{month}:'-01'...