DSXchange

Hmmm... try 'Validating' the job via Director, once for each occurance of SVR_NO and use the apppropriate default values for each when you do so. I believe that will create what looks like your 10 Server Jobs with the appropriate default values. No guarantees. Be aware, however, that it is really st...

Assuming there is nothing funky in the Sequential file, a couple of questions: What does the routine do? Anything 'special' or does it use COMMON storage? Do you have Row Buffering turned on? It can be on either in this particular job or at the Project level and this job uses 'Project Level Defaults...

The answer is simple - don't convert the packed fields, simply send them as is. As you've noted, the character fields will need to be run through the EBCDIC function, but packed is packed under either encoding system so it requires no translation.

I've been pondering this and I may have been wrong about this bug still being around in 7.x. It definitely is there in 6.x but in thinking about it I can't say for certain that it has showed up again since we moved up to 7. So that might be one answer to get yourself the 'fix' - upgrade. Check with ...

I'd be interested in exploring this as well. I was disappointed to find that they were created on the Client side, meaning only useful for the person that created them. Unless, I suppose, a way could be found to redirect them to a network share for example. Is that what you meant by a "common templa...

No problem.

The stage I was trying to think of was the new "Row Splitter" stage.

The problem with writing it in it in basic is that it has to deal with three times: Australia/Victoria - including DST - > GMT, GMT+10 -> GMT and GMT+10 -> Australia/Victoria. Out of curiousity, how is this a problem? In BASIC, it too is a trivial program and I personally think adding calls out to ...

Welcome! :D On the subject of "breaking these strings" you've got a couple of choices. The tried-and-true methodology is to use a unique delimiter when concatenating fields together, typically something like a pipe. Then you can use the FIELD function to break it back up again: FIELD(YourBigStri...

You mean I can change the datatype in Datastage back to DATE and insert a value in the form of 'YYYY-MM-DD HH24:MI:SS' or let the datatye be timestamp and insert a value in the form of 'YYYY-MM-DD HH24:MI:SS'. My Rule of Thumb is to always use a Timestamp data type when dealing with DATE types in O...

It's a bug and you'll still find it happening in version 7.x as well. From what I recall, it can happen if you have Encrypted parameters and you change other parameter default values in Director without touching the Encrypted ones. Once it starts to show up, all I've been able to do is make sure you...

Ah. You've tried the OCI stage. In your version, you should have both an OCI and an OCI8 stage. You are correct that the older OCI stage is for Oracle 7.x but you really should have an OCI8 stage that is meant to be used with Oracle 8i. If it's not showing up for you in Designer, I'd guess that the ...

As you've noticed, you have to be very selective about what you change. Changing all occurances of "128" to "256" would be a Very Bad Idea.

Do the ones you are sure about.

Don't touch the ones you have listed as "not sure about".

I'm going to give you the same advise that Wolfgang gave you over on ADN - export the Project, edit the exported file (save the original!) and then reimport. About the only way other than changing the jobs one by one by hand...

The detailed list is quite long from what I remember. The simplest way to get what you need is to order the actual upgrade and then check the readme. There will be an entire section dedicated to what's new in the release. You'll also get the new and/or updated pdf documentation that you can study. A...

Well then, let us know how it goes.

Unless they are starting to distribute multi-platform releases, something for the "HP platform" - which I assume means HPUX - won't have the binaries you'd need for Sun. Be glad to be proven wrong...