DSXchange

Seems to me that Ray is not mentioning something that will solve your current problem but rather something you may need to look into once you do.

(but then The Mind Of The Ray can be an inscrutable thing at times)

Support.

The option to Add to Favorites is on the far right-hand side of the page, both at the very top and bottom of the page/screen. Clicking it will put a link to the topic in your Favorites so you can get back to it easily.

You can always save it as a Favorite.

I wondered about that. Seems to me the original transfer by 'the business user' to the mainframe is the one that would be doing the ASCII to EBCDIC conversion. And it sounds like the 'corruption' is happening on that initial step. From what I recall, a simple FTP script to get the file onto the UNIX...

Yes, it can have a reject link as a source or a target.

Let's assume Parallel and get your post into the correct forum. Starting off life in the FAQ Discussion forum wasn't it.

Cutty Mark, can you go back and edit your post to include the details the original forum didn't force you to include - O/S, Job Type, Version? Thanks.

You don't have a DataStage problem, at least not yet, so technically not something that should have been posted here.

Fix the "some code page issue" in Step 1 so your data remains intact. Perhaps the Business User will need to use a binary transfer.

I'd start with your Teradata DBA... that and your official support provider.

Doesn't really matter what user you log in with, the jobs run under whatever user ('engine credentials') has been setup for running jobs. Guessing that's your issue here.

Details on how you are "unpacking" the fields would help, specifically settings in the Sequential File stage for those fields. Unless you are doing something for that in the Transformer?

What kind of advice are you looking for, exactly? You launch one after the other, using unique Invocation IDs for each one. From the command line, you include the Invocation ID after the job name with a dot "." separator: JobName.InvocationID From the command line you use the dsjob utility...

A little confused. Which data "looks good when you view data from the Designer"? Are we talking about the EBCDIC file or the file your job created from it? Both? Are you trying to "unpack" the fields into the target file? It's not really clear in your post and just wanted to poin...

qt_ky wrote:will only show you the most recent person to save it

So, literally just "saved", regardless of whether or not an actual change was made?