DSXchange

Can't speak to the TX side, but XML processing comes with the base Server product, not the SOA Edition. SOA adds the ability to run Server jobs in real time by exposing them as a Web Service. You'll see comments in the Server forum about the 'speed' of XML parsing as it's not the speediest solution ...

You may want to post something (as in another thread) on the subject of "OCI doesn't work for the time being" as using ODBC is... less than ideal. How would you process 'duplicate' records outside of DataStage? It's no different here. Duplicates must, in some fashion, either update or replace the of...

Good to know, that will come handy for some of my peeps.

Wasn't sure exactly what but I know there are things specifically disabled when in the Administrator.

For what it's worth, the last time I had to do this I found that plain old Disabled is what worked for me. I don't recall exactly why, but had some strange behaviour when I tried 'Disabled, Locked for Updates'. Switching back to Disabled made it do exactly what it needed Always best, in my opinion, ...

Excellent! :D

Note that Arnd said "if you are in TCL" - this means you have to have connected via the command line and cannot do this from inside the Administrator as noted in your subject. Pretty sure stuff like that is specifically disabled when in the Adminstrator's command window.

Hello! In case you are wondering, there is a command line executable called dsjob that you will use from a shell script to run a job. And yes, parameters too. Search and yea shall find a bazillion posts on the subject. It is also, as Arnd noted, in one of the pdf manuals of all places - the Server J...

You promote a job using Version Control, which has no command line access. You can transfer a job from one environment to another at the command line by exporting and importing , but there are restrictions. You'd need to search the forum for a full list, but exports from the command line export all ...

Account = Project and it needs to be spelled correctly, case and all. Is your project really sap_sales in all lower-case?

Have you enabled the 'Enable job administration in Director' option in the Adminstrator for the project(s) in question? If you haven't, that would be the primary reason why they would always be greyed out. It is a property of each project, by the way, along with things like auto-purge of log defaults.

Try checking Output<1> instead of just Output and see if that fixes the problem. It should unless something else is going on.

What I need is a easy way to: 1) set something (variabile/status/whatever) in a transformer stage into a job server 2) read that "something" from a sequencer and use it in a Trigger or similar, to change the flow of the sequencer. - I read about UserStatus but is seems to be valid only inside the j...

This kind of question should really go in the PX forum, by the way. You haven't given us the actual compilation error, but I'm guessing it's the fact that you are using Server functions in a PX transformer. You can use all of those mentioned - IsNull, Trim, Ereplace, etc - but you have to switch to ...

It sounds like to me that you are trying to come up with some sort of 'universal solution' - some technique to handle Timestamps across all 'platforms' as you call it in exactly the same manner. Can't be done. Oracle has different requirements than DB2. Other databases throw in other wrinkles. Requi...

Pretty sure that all that option did was reindex the project and yes, it has been removed from the Administrator. You can fall back on the 'old fashioned' way and do the reindexing from DS.TOOLS or directly from a TCL prompt. An exact search on 'cleanup project' will turn up quite a number of exampl...