DSXchange

Oops, here's a server variation on the same theme. I would normally just stick with string date representations stage variable svFieldDate = ICONV(In.Field[1,10],"D4YMD") svFieldTime = ICONV(In.Field[12,8],"MTS") Derivation IF In.Field[10,2]='12' THEN OCONV(svFieldDate-1,'D4YMD')...

You can write a job sequence which only executes job 2 if job 1 finishes successfully. In your example, Job 1 would abort and thus Job 2 will not run; so you don't need to know the value of any columns.

It sounds like you have a data inconsistency of some sort in your xmeta repository. The details of those structures are not publicly documented so your best bet will be to approach your support provider to see if IBM has seen this problem before and can fix it (without having to do a re-install, whi...

Could you specify the problem a bit more, since generally a job processes more than one record, and thus each column can have many values. Generally you could make a constraint in a transform stage which either creates a text file with the value you want, or could set the user status to that value, ...

Is the error on the view user credentials just for your userid or also when you try to view other users? Also, are you entering the IBM web console using your id or another one?

I don't have access rights on my current machine to check if this is reproduceable since it sounds too strange. Are the numeric contents that come across as NULL all of a similar tpye, i.e. with leading zeroes or negative values? Do values such as "123" not get transferred correctly?

Date and Timestamp columns have no format. Only when converting or displaying these data types is a format needed.

Internally these data types are stored so that comparisons on greater or lesser or equality are easily done.

What is the data type of your input columns?

Edit your job and add a before-job subroutine call to "ExecSH" with the parameter "ulimit -a" and see what the actual runtime value is. I am willing to be that the value you get is "16" and not unlimited. Note that you ulimit value is often set or modified in the dsenv ...

I will assume that your incoming field is type VarChar() or Char(19). In that case stage variable svField = StringToTimeStamp(In.Field,'YYYYMMDD HH:NN:SS') Derivation IF In.Field[10,2]='12' THEN TimestampFromSecondsSince((-1*(60*60)+(60*60*24)),svField) ELSE TimestampFromSecondsSince((-60*60),svFiel...

Does this error affect just your userid or others as well - is it a new installation or one that has worked correctly before?

What is wrong with using the "monitor" in the director in order to display this information?

I would start with your ulimit settings at both the user and the system limits level, see

...Need to be able to open at least 16 files; please check your ulimit setting for number of file descriptors...

You are confusing me. At first it was a decimal value, then string and now you are asking about date data types. Comparing date type against each other will correctly handle < and > values regardless of the display format.

That sounds really strange. If you select all cells and remove formatting in the document, does the error persist?

There is indeed a limit on the reference data size of a lookup stage in PX. If you are on AIX then this thread might help solve the problem, but only within certain limits.