DSXchange

chulett wrote:There's no way for them to revert back to a state before your change unless you didn't actually save them.

...unless you are on version 8.5...

JR39833: COLUMN ORDER IN TRANSFORMER NOT MAINTAINED AFTER SAVING THE JOB

See Also: Superceded by patch JR39983.

We had to apply a Designer patch addressing WSDL import problems. I do not recall if it is the problem you describe. If it is, and you don't want to apply Fix Packs to all server and client tiers at once, you can apply the specific patch. I just found a link: http://www-01.ibm.com/support/docview.ws...

I am not sure if the case matters, but often it does... The extra space after the = sign most likely does make it not work. I have this line in my dsenv file on AIX:

export NLS_LANG=AMERICAN_AMERICA.UTF8

Double check the data type of your target column to make sure it is a string, like varchar, then it should suppress the zeros. If it is still set as a decimal type then it would explain the zeros you're still seeing.

It may also help to remove comment lines. Here is a technote about it.

http://www-01.ibm.com/support/docview.w ... wg1JR41137

There are some special characters that are not handled well and can lead to errors.

Try a different user name and password. Also try temporarily changing the password to something simple. Test it again, then change it back. Then you will know if it's a special character problem or not.

I should clarify that PKZIP on z/OS does not corrupt files every time. We have run into corruption multiple times however, on large files. It could be that our PKZIP version is older or has a defect. If you plan use it, test it first on a variety of file sizes. I don't know if they compress anything...

Caution: We avoid using PKZip on the mainframe because we have seen it corrupt too many ZIP files.

Think about this too: If your DataStage server has access to the mainframe file, such as on a shared drive (not sure that's possible), then your job could just go ahead and read the file.

chulett wrote:I'd also be curious if this was working and then stopped or are you are trying to get it to work for the first time? ...

If it used to be working, then the error should say "Connection Died."

What I see with two links coming into the Oracle Connector stage: 1. The Transaction property section disappears from the link properties and can be found on the stage properties (click the stage icon picture in the top-left corner). 2. The Record Count property is not "disabled" in the se...

I hit the "Connection Dead" error last year via DataDirect ODBC drivers. In our case it was because we had enabled Oracle Advanced Security on the database server and forced it to required encrypted client connections. If that is your situation too, then you have to upgrade the DataDirect ...

James is correct. By default, without the env var set, it will expand any wildcards into the matching filenames and cat those files together (sequential). With the env var set, if there are multiple files, then it will process the files in parallel. Either way, it will expand the wildcard and read t...

Andy, Glad to be of help where possible. I don't know the answer to your original questions about the message numbers or line numbers. I searched UniVerse manuals and came up empty. The line numbers are higher than the 9 line program mentioned. I am having the memory compression activated on our 8.7...

Actually, a real question - I remember P and T but what's R again? Replace? And with no parameters seems to empty the line? The editor can tell you too. ----: HELP R R - Do the last 'REPLACE' (R any) command again. R any - REPLACE this line with 'any'. R/// - CHANGE one or more lines (same as C/// ...

Trying to help... Are you able to take advantage of additional memory? I posted a link in this topic that describes Active Memory Expansion in detail. The claim is that it will allow higher throughput and increased utilization. It sounds like this could help your situation. http://www.dsxchange.com/...