DSXchange

I don't recall the exact syntax off the top of my head but a search here should turn it up if you look for 'counter' I would think. From what I recall you need to index into the list of parameters using the counter and you usually create a delmited list all at once for the StartLoop stage to iterate...

Not sure why the need to specify the start position, just the fixed field's width should be enough... it will 'stack' them appropriately from the beginning. I would think the start position only comes into play if you want to skip segments of the record.

Yup, good idea.

Sounds like your XMETA repository is out of sync with the local/legacy/'Universe' repository. You'd need to involve your official support provider for help getting that cleaned up and bakc in sync.

Ray: Please note that I put 'Universe' in quotes just for you.

Isn't there a tool in the 8.x release for this exact purpose? Or was it added as part of the 8.1 release?

Root = Project level, so if you don't see it when you click on the project name rather than a category then that's not the issue.

Keep in mind the fact that it may not actually be in any category but could be out at the 'root' level. I've 'lost' more than one job out there over the years.

You need to recognize the difference between the 'current working directory' in putty versus what it is in DataStage. What I posted previous tells you how to handle that difference.

Your trigger is fine.

You need to put the command first and then give it the full filename to check, that or cd to the directory then do the check.

Then it would seem to not be "empty" in the other environment. Is this a CHAR field? Have you compared the $APT_STRING_PADCHAR values?

In the Sequence use something (routine, script) to check the size of the reject file and conditionally send the email if the file isn't 'empty'. There are 'test' conditions you can use or perhaps 'wc -l' to do the actual check.

Sounds like Div() isn't valid for your database or the data types are wrong. Why not just use the normal "/" operator?

Apparently not. I don't believe there are many active posters on Teradata here, so you might just need to ping your official support provider instead.

Sure, should be possible, properly formatted. What have you tried? What issues have you faced?

Your "warning" is being generated by the fact that you are affecting more than a single row. Some databases send that back as extended information and anything that comes back as that triggers the warning message, even though it's just informational. Oracle doesn't do that, DB2 does from w...