DSXchange

As noted - yes. But you don't go from Prod to VC back to Dev. Everything is in VC, so you simply take the most recent version of the job (i.e. the one currently in production) or any previous version (technically) and promote it from VC back to development. Also as noted, make sure you clear the 'Re...

And the space isn't an issue either. It can be there or not. I'm sure it will come down to column types as mentioned earlier. Not sure why you'd want to do a query like this, one that's not tied to the current row using bind variables / parameter markers. It will be executed once for every row sent ...

Ok, I could see that. In addition to what was already asked, how exactly is the value getting 'popped' into the status area?

Roy - not sure what you mean by "select max for a column to a Xfm poping a user status and outputing to /dev/null". You might want to give more details on that.

the values changes all the time,so i cannot code it myself. Sure you can! Unless by 'changes all the time' you mean it 'changes randomly such that only a person would know what to use on any given run', you can certainly code it yourself. I'm going to take a wild guess here and say that a parameter...

Does the query run successfully outside of DataStage? If so, then it can be made to run inside it as well - provided you account for all of the fields being returned in the Columns tab and the datatypes are correct. Because of the correlated subquery, you'll need to use Custom SQL, but other than th...

Yes, you need PX in order to actually use any of the Parallel stages. You'll also find that the help will mention the PX and Mainframe stages, but unless it says 'Server' at the top it's not going to be of much use to you. Where are you seeing these stages? While the branches for Parallel stage type...

My advice is specific to Oracle and the strange way that dates have an embedded time portion in them. I know from reading the forum that DB2 is the exception to the 'external' format rule and the only stage that seems to require dates be in internal format when you send them to it - so you had that ...

True, but the MS OLEDB stage has been around for awhile and is a fairly 'generic' stage. There still isn't a native SQL Server plugin stage as far as I know.

My goal is to reduce the byte count from 38 to 10, but yet staying in DATE format, allowing date manipulation, allowing other reporting tools to understand the date (thus the reason for not using internal format). Loading 00:00:00 in for time is merely a workaround that does not truly resolve the i...

Exclusive? As in 'native', like the OCI stages for Oracle? No, not that I've seen.

It appears that the only method for loading is into a timestamp. I don't believe it's possible to load only the date. The OCI9 stage always attempts to load the DATE as TO_DATE(:4, 'YYYY-MM-DD HH24:MI:SS'), which is not a DATE field, but is really a TIMESTAMP. No, a TIMESTAMP is a completely differ...

How are you actually running the job(s) in the Sequencer? Are you doing something other than using a Job Activity stage?

Without more details and perhaps the routine code, I'm not sure how someone would know or be able to figure out what's going on.

I am changing some test jobs right now to see about the lookup file sets; I gather I do need to make sure that the column names in the lookup file set and in the main data stream are the same so that the lookup will function, but I haven't seen any other modifications that I need to make. From what...

This is just a stab in the dark as I'm in the middle of my first PX class, but - it may be looking for a pool with the reserved name of sort to know what to use for scratch space. If it can't find it, it sounds like it starts by looking for scratch space in the default pool, which it found in your c...