DSXchange

This is because the F1 through F9 columns are implicitly defined for hashed files, not for SQL access to hashed tables. a "LIST DS_JOBOBJECTS F3" command will work.

My first thought is that the user has insufficient access rights to the projects to write anything, thus no status change when you try to execute a job. Can you try as the administrator?

Yes, F3 and NAME are synonymous.

Ratan, don't you feel it would be helpful if you could post your routine which is returning incorrect values?

Sushil, does that mean when you start a job in the director the status of the job remains "compiled" and nothing gets written to the log file?

I suggest better go with in single project that helps you in sharing hash files between your module Thanks, --Anupam No, that is not correct. Since hashed files are best put in paths that are not in the project directory, it makes no difference how many projects you have since they can all use the ...

The ICONV() function on a date will return an integer unless it cannot parse the incoming string, in which case it gets returned. Can you write a 1-line routine in the Manager which contains "Ans = ICONV(Arg1,'D')" and test it - then post your input date that cannot be convered?

In the past some of the client apps have needed a patch from IBM/Ascential but I don't know if your issue is a client or a server one. Have you contacted your support provider about this problem?

The ICONV function has not changed in years; I suspect it is the settings of your system date defaults. What is your exact ICONV() function? It is returning the same date as was input?

Are your client/server on the same windows machine? What OS and SP level do you have on your client PC? Can you attach to projects using the other client tools or are the other problems showing up in your installation?

This is a very basic PX type question that we cannot answer for you. If the pivot can be done within the datasets in each processing node then you should be able to work in parallel. You should try it and see if it works and perhaps provide some feedback to the forum when you've finished. I looked i...

The values are for different things; @INROWNUM is for the current row number coming into a transform stage for a link and @OUTROWNUM is the current row number going out of a transform stage down a given link. They can be identical but are not necessarily so.

Wim,

Add "" to pools.

You need to read up on how the $APT_CONFIG "pools" parameter works (Chapter 58 in the Parallel Job Deverloper's Guide) and that will explain why your job has no available nodes for processing.

I missed the "from prevous one" The question is if the same job always has the same error in the same time period. This is to see if there is a way of getting a reproduceable error and/or some logical progression to your problems.

Kumar (et al), I've experimented with what you've observed and value in the NAME column of DS_JOBOBJECTS does for the ROOT record needs to be changed to correspond to the object name in DS_JOBS if the change is done manually! At first I though it would only affect the designer's displayed name since...