DSXchange

Ah, ok... I only had an Annotation on the canvas when I had all of the "code" the job ran in the Job Control tab and possibly something before job. If literally all you have is something 'Before Job' then you could either move it from there to Job Control (easily done) and add the Annotati...

It also required me to add some dummy stages to my new script as system would not compile DS jobs with empty bodies. FYI - All you needed was an Annotation on the canvas to fulfill that requirement. Mine would typically note what it does and that all of the code was either in Job Control or Before ...

Sheesh... we know the answer Ray, it was meant to be answered by the OP.

And what is in this "VOC folder"?

I was wondering how it allowed that job design but having the last link as yet another reject link is the only thing that makes sense. PX is not like Server in that it does not allow input and output links from the same target stage. If you want to 'process' that reject file, you'll need to use anot...

Nope. You'll need to use a client that matches the server version to do anything, including any monitoring.

Unless something has changed in 8.x I seem to recall that you'll need at least one input parameter for the proc. Even if the proc doesn't use it, there needs to be something it can bind to the input link.

:!: Please don't bump posts like that, at least ask another question - even something like "Can anyone help me with this?" is better than just "bump" or "UP". That being said, if no-one has posted a reply then perhaps no-one has the experience or expertise to help with ...

Permissions. Have you checked what they are in the Project's directory for that folder?

From the linked instructions: Changing the VOC file from a static file to a dynamic file speeds up the updating of the VOC. You don't have an issue, keep on going. In all honesty, if you don't understand why I don't think you should be in there doing something of this nature. ps. Your 'folder' came ...

Suggest you search the forums here for your error message.

Posting in all caps on the Internet is considered SHOUTING... please don't shout.

One stage = one connection / session that all of the links would leverage. I've done that in the past for multiple simultaneous sources but never checked to see exactly how 'simultaneous' they really truly were.

One option - try using a single source stage with multiple output links. Another - one query to stage the entire source table locally, then you can take your time pulling out what you need.

How are you partitioning for the target? Do an exact search here for "deadlock" to find discussions of the cause and solution for this issue.