DSXchange

I believe this is a limitation of Teradata's FastExport. From the DS documentation on the teraread Operator. v Single-AMP requests are not allowed. These are SELECTs satisfied by an equality term on the primary index or on a unique secondary index. Meaning use the Teradata API instead. Disclaimer: T...

This doesn't sound like either a Teradata or DataStage 7.5 problem...
This SQL within the Teradata Enterprise Stage has no issues at all.
SELECT CURRENT_DATE - 1 AS DATE1 from <table_name>
WHERE CURRENT_DATE - 1 = CURRENT_DATE -1

This works in 7.5 in the Enterprise Stage
SELECT CURRENT_DATE AS DATE1 FROM <tablename>.

You'd need a column defined as DATE1. I called it DATE1 varchar(50).

We use parameters routinely in the 7.5.1 TeradataAPI stage in both the General and Input tabs and have done so for years.

I'm happy that worked for you. The application I used it for was multiple xml schemas going to an Oracle db. The schemas described different hedged options like commodities (rice, hops, barley, the essentials for beer), as well as hedging international currency fluctuations, transportation costs, st...

I don't have access to DataStage so this is from memory and might be a little vague. It has been over a year since I talked DataStage so my accent might be rather thick. You can change it dynamically (per job run that is) using parameters. Parameters will work within the description field. Parameter...

You could use the filter option of the Sequential file read and tr -d "\"" those bad boys outta there. ALL of 'em.
You'll have to change the format definition to quotes=none
This is not optimal but kinda works. A ringing endorsement of the technique! Caveat Emptor baby.

Yes it is. Use WORKDB=<Database> as an Additional Connection Options. It is a property available within the Properties tab of the Teradata Enterprise Stage within the DB Options Mode property. Here's what we use. I know of no other options available but would love to learn of more if anyone knows of...

Jillion+1. That method too complicated and too Old School. Get Hip Daddy-O. Use a DSMacro as part of the filename in the sequential stage. <filename>#DSJobStartDate#. Use DSJobStartTimestamp if running more then once in a day. Nah, never happen.

You are using two nodes. This means you are partitioning on two nodes. This means, in general, half the data goes to one partition and half the data goes to the other partition. If you have not consciously planned for this partitioning then Datastage has done it for you. Erroneously, it would seem. ...

Sounds about right to me. Might be a 8.x difficulty. Does setting any RequestedSessions and SessionsPerPlayer values have any effect? I'm wondering if the settings are being ignored completely? If so you might try matching the case of the two exactly as above.

You canot parse the Language tag? Then your Xpath to the Language element has a typo or other fundamental problem. If you are getting a single language when you expect a row per Language then your Repeating element is probably mis-defined. Is the Repeating Element set to the Language element so that...

The classic dsxchange double play! Chulett to Wurlod to ArndW. If I am interpreting this correctly, you've got on average 3 parameters per job. What exact purpose do these parameters serve?

I'd do all that in a Excel workbook. Create the mappings and template and spit it out as a dsx framework file and import into Datastage. Give the whole process a cool sounding name like Quicktrack or something similiar.

Can you create a table using another tool in the username database with the userid?