DSXchange

Sequences and Server jobs are identical in the Enterprise edition (with the same version) and don't need any conversion. The Enterprise PX environment is an addition to the normal server environment and doesn't replace it.

The process should disappear in (at worst) 90 minutes depending upon your UNIX settings. I'm not sure what the network configuration parameter for that socket timeout is right now, though. I think that there isn't much to do between FIN_WAIT and FIN_CLOSED status; although each hardware vendor / UNI...

I was surprised to see this, thanks! I've signed up with the testing company and am awaiting my userid/password - perhaps the test is already finished, I'll see when I get to login and attempt to sign up.

Sainath, I did a transition from Server to Parallel Extender by printing out and reading the PX documentation (in the PDF files that install in to the same client directory as do the Sever ones). That isn't sufficient, but it forms the basis for further learning. Another approach which would be help...

Can you get a PX job to compile and run that doesn't use transform stages? Just to make sure that the problem truly lies only in the c++ compiler. Also, are you certain that this version of the compiler is identical to that in the install manual?

I'm not sure if it's in the PX or Orchestrate documentation (as I'm not at a PX system right now) but you might be able to find the exact compiler call and execute it from your shell, instead of trying to get the error messages post-mortem.

I recall that I once got much better compiler diagnostics when I looked at the output of the multiple-job-compile utility you can call from the manager. It might be worth giving that a try for your single job.

The error message seems to indicate that the compiler has trouble evaluating one of your expressions. If none of them show up red in the designer I would suggest you remove the more complicated ones one-by-one from a copy of your program until the compile error goes away; then you've identified the ...

Aliso,

could you read the XML file into a DataStage job and then split your incoming data into several streams in a transform stage and output each of those to a XML output file of the appropriate format?

Hello Sunshine, I think you will need to detail you question a bit more. One is a means of standardizing information exchange and the other is an ETL tool. Both deal with data. EDI file formats are complicated, but could be parsed within a DataStage job. DataStage RTI could act as a "listener" for i...

Your source data is encoded in character set that I don't know - but you need to check if the extended (non-latin) characters are mapped the same way that Windows-1252 maps them. If not you will get misconverted characters. NLS is not as complex as it seems - the difficulty lies in making sure that ...

Hello Judy,

could you explain what a "DAG" is? The CFF stage will read sequential files and allow the use of some COBOL type constructs in parsing them.

You will need to login to the IBM/Ascential developer network to download the windows patch that addresses the properties not opening correctly problem in DataStage 7.1

Your post indicates that you are using the variable "JobHandle" in your job transformation; it won't work there, only in your routine.

You can check the daemon log file to see what it has been doing, but it should clear up locks for objects that it thinks are incorrect. If a lock is present because a process has aborted or had a "kill -9" done to it then the deadlock daemon will clean that up. If you have a lock held on a job by so...