DSXchange

Always specify a maximum string length (VarChar(255) for example) or always specify unbounded VarChar.

There are pros and cons to both approaches, discussed elsewhere.

Check.

In particular double check that Payment_Date is nullable on the output link of the Lookup stage.

The scope of a stage variable is the stage in which it is declared.

Therefore the same stage variable name may be used in more than one Transformer stage in the same job.

Demonstrate that the SQL in the second lookup matches the metadata in the job design. Or, if it's a hashed file lookup, demonstrate that the location field in the table definition is correct for all three columns.

No, because we don't have access to your system. You need to do your own diagnostics. Start with looking in the job log for any problems, and in Monitor (or Designer) for link row counts. Is there a constraint expression in the Transformer stage? Did you run the job with a 100 row limit?

Premium membership is the main way that DSXchange's hosting and bandwidth costs are met. Why not sign up? It's not expensive, at less than 30c (approximately Rs11 on current rates) per day.
Follow the membership link from the home page.

When you get to version 8.5 there are new ways for getting at DB2 on mainframe from parallel jobs that would make your life easier. But you will still definitely need to analyse the logic of the COBOL program's procedure division and replicate that logic in DataStage.

You can do this, but you have to design it in to your own jobs - there is no automatic mechanism for keeping track of successfully committed transactions.

This is a vertical pivot. Search DSXchange for many posts on how to achieve.

Recover it from the export you took at close of business yesterday.

Otherwise it's gone forever.

Use the rtype argument to manage your rounding, and Trim() to remove leading and trailing zeroes. It's slightly more complex with signed decimal numbers.

All that information is stored in the common metadata repository (a database we usually call XMETA, since this is its default name). You are correct to assume that the format is proprietary, though it can be discovered.

A sequencer doesn't have that option either. The only option available to a sequencer is Any/All. It may be that you are meaning to use the term "sequence". A Search of DSXchange will tell you much about the "automatically handle activities that fail" and any gaps then remaining ...

svYear Left(InLink.TheDate, 4) svIsLeapYear Mod(svYear,4) = 0 And (Mod(svYear,100) <> 0 Or Mod(svYear,400) = 0) svFebDays If svIsLeapYear Then 29 Else 28 svMonthDays "31|" : svFebDays : "|31|30|31|30|31|31|30|31|30|31" svMonthNo InLink.TheDate[5,2] svLastDay Field(svMonthDays, &...

Maybe a Head stage, then, with the Period and Number of Rows properties used.