DSXchange

We are on AIX so not sure if patches will be the same. Here is the list of patches by ecase (in the order they were applied) from Ascential that we have applied. 75003 (The DRS plugin and the ODBC stage are incorrectly placing an unqualified tablesname in the stage when afull-qualified name is sele...

Ultramudane, Could you please advise your latest Patches number, since we have applied 2 patches in Server(Solaris) and 1 patch in Client, and would like to know if any latest patches applied to us. Could I just apply the latest patches that should cover all the old patches? Thanks for your help and...

Arnold, Can you please elaborate on how do you find out the Variables lookup in your testcase, when you have time. Just tries to learn more about that and do it ourself in case we encounter the similar problem in the future. BTW, Peter and I work on the same issue. Please accept my deeply appreciati...

pjsimon,
This is perfect case to use lookup stage. Try it and let me know how it goes!

Kumar,
you should place them in Parameter field as following:
#USERID# #PASSWORD# #ANYPARAM#

Do not try to concatenate them using :
The Parameter entry field is just an entry field. It cannot understand the syntax, and will see ":" as a character..

Let mw know how it goes!

I will try to pivot the file if it is possible, since there is no way you can speed up the compilation time if you have 1220 columns in your PX transform. PX engine literally generates C++ source codes based on transformer content and pass it to associated C++ compiler for compilation, and that sour...

Kumar, 1. When using execute command stage, ensure that you put your parameter in "Parameters" entry field. Do not place them all in one line with Shell script in "Command" entry field. 2. Upgrade to latest patch to 7.5.1.A if you still have problem on using it. I remember this p...

dsusr, This is a known bug in PX 7.5, they promised to fix it in next release. To work around it for now, you can define a job parameter RBUSER, use it in your PX transform, and place this job in a sequencer(I believe you probably need to use it). Finally, you shall be able to pass down the value of...

Hi. Pneumalin, we changed the job and it's not "freezing" more. Now, we have other problem: "APT_CombinedOperatorController(1),1: Expected identifier; got: "0001"". We don't use the job sequencer. I open a case in Ascential, but at the moment nothing... Thanks a lot! W...

This is a well-known problem in PX7.5. Try to the following: 1. Add environment variable from Reporting-->$APT_JOB_NOMON to your job parameter list. 2. Change its value from False to True. 3. Recompile the job and run You can do it from Sequencer level you are running the job from squencer, but make...

I disagree. If the dll was missing then the job would not compile and this message looks like a runtime error. The last message is "The specified module could not be found" which normally means that the function within the dll cannot be loaded. This implies that either the dll was not bui...

I will check if that DLL you just plugin works or not. Since the message shows your job finds the DLL, but fails to load it.

Kalyan, if you issue -stop while there are live client connection to the server, the dsrpcd cannot be brought up properly when -start is launched. Ensure to close any client connection before doing -stop.. To activate dsrpcd in this situation, Ray might have better idea to do it via the netstat info...

Gops,
If I were you, I will try to read all the source in as varchar and call a Routine to convert it to Numeric. For sure, you have to create a C routine using atof() yourself..

Hello, Has anyone encountered the situation like this: We run "dsjob -run -jobstatus ...." in Solaris, and get Status Code=2, sometime get status code=255 when the job "finishes with warnings".. The return status code in original dsjob C code only goes up to 99 for any other stat...