DSXchange

You may need to force buffering and increase timeouts, or to re-think your design, to avoid the deadlocks if they're in DataStage. If the deadlocks are in the database, you'll need to re-think the package design; it suggests that someone is attempting to update a table on which there's an open SELEC...

No, since that - being a proper noun - would require an upper case "D".

I believe the phrase is "hoist by his own petard".

I suspect that abc123's aberration was merely a slip of the Shift key. As Dilbert once put it: shift happens.

Review your configuration file. Make sure that the conductor node is mentioned in the export node pool. That is, that the export node pool includes the node on which the conductor process runs. Be sure to check that the conductor node may be specified by an environment variable.

Signed number with trailing sign is easily converted using the "MD" (masked decimal) conversion with Iconv() and Oconv() functions. In your case is it probably sufficient to use just Iconv() with a conversion specification indicating that the sign is trailing. Invoke help on the MD conversion for mo...

You can use the -stop option in the dsjob command line interface to issue a stop request to a running job.

Note, however, that the "running" status reported in Director may be out of date, but the job was unable to update it. Search the forum for more complete description.

Technically it's an issue of SQL syntax, not a DataStage issue. Arguably it's an issue of (SQL) standards compliance.

I'm going to guess that Craig's users use Host View in Manager or other mechanism for switching between projects. That such users have touched the project to be reindexed may, indeed, cause a problem, since some of the internal code uses file variables in COMMON. Technically (and practically in my e...

Can you please post the initial command line you typed, and any error messages that appeared up to this point?

The PACK includes a number of "plug-in" stages. This is just one of them. "Plug-in" here simply means optionally installed.
Read more about this PACK and others on the IBM website - there is also a training class available.

If you use a Lookup File Set stage you won't get View Data either. Some stages just don't support it. Any stage that invokes a bulk loader does not support View Data when in bulk loader mode. End of story.

Please post the entire error message detail.

Thanks gentlemen, for your responses. ray, by "duff" data you mean some bad data, right? That is correct, this adjectival form is widely understood in the UK and most of its former colonies. Curiously, the adjective form does not appear in dictionary.com nor does the colloquial usage "up the duff" ...

It's also true that you can't view records in a table if the indexing is not up to date.

It would appear that your Repository indexing has become out of date for some reason.

Officially, server jobs do not support BLOB data type.

You may have been lucky up to now in that your BLOBs have been small enough, and now you've encountered one that's too large.

Job parameters for the start and end dates.
Populate a generically-named file, and use ExecDOS as an after-stage subroutine to execute a REN command to change the file name to one built using the job parameters.