DSXchange

Why not just open the job in Designer and click the button that looks like an Internet Explorer icon? It will generate a lovely little HTML document will all that stuff in it for you... no charge.

Does not PX for Windows come with the MKS Toolkit, in essence giving you a UNIX-like environment? So the other answer should apply as well, I would think.

abc123 wrote:No, it doesn't work. I enabled RCP across the project, job and stage. I still see the Output tab as empty.

Of course it stays empty - that's why it's called Runtime Column Propagation. It happens automatically at runtime.

Wow... that's the hard way. The easy way? Slide the Columns grid over the the right and investigate the 'Incomplete Column' option. Set the last column to 'Replace' rather than 'Error' and it will automagically give you a null in that column when Excel drops it off.

If you have two client versions installed, you'll need to install it twice - once to each location.

They both have three stages, sure, but other than that they're not "the same". Those are two totally different "Xfm" stages for one thing...

From what I recall from this forum, delays like that can sometimes be attributed to multiple simultaneous compilation requests. The default license may only allow a single compile to occur at a time so subsequent requests 'queue up'.

Perhaps you should add a little detail to your post. And example or two of your problem would be helpful, too.

As I've already mentioned twice now, you'll need to use the second syntax in the previous post. Output from a command execution is returned in a dynamic array and the Field Marks are messing you up. If you check the first array element by adding <1> to the end of the variable, you'll just get the '0...

Go to Kim Duke's website and download the backup script you'll find in his Tips & Tricks section. It will export and date-stamp every Project on the server you attach to automagically - and you can schedule it.

Since you are on a Windows server, you literally put "type" as the Command and the filename (or the job parameter you are using for the filename) in the Parameters section. That's it. Then you use the Activity Variable "StageName.$CommandOutput<1>" as the LHS of a custom trigger - and compare that t...

Actually the error can be anything and not only 1. Ok, just going on the fact that you said "the sequential file is storing the output of procedure as Error num = 1 or 0". I developed a routine as follows: Would have been simpler to just "type filename" in an Execute Command stage and check the Com...

Seeing as how quotes are only for character strings, numeric values would fall into the "no quotes" camp.

So now the sequential file is storing the output of procedure as Error num = 1 or 0. But my sequence is runing irrespective of whether the procedure fails or success. Of course - it does not have a clue that a '1' to you means there was a problem. The job ran just fine so the Sequence goes on with ...

Then what?