DSXchange

It's easy if you documented it at the time.

I always do, and document jobs that read the Data Set that the Data Set was created in job name XYZ. Usually I also include job XYZ as a dependency in the job that reads the Data Set for that reason.

Try reading it as NVarChar.

Was this a "run now" or a scheduled job? There is also a transient Java "connection refused" error in the application log - perhaps if you try again a little later?

I understood that the limit was 99. It now appears that 99 is too many. Does it work with 98?

Note that DataStage regards # as a reserved character, which must be mapped (to "__035__" if I recall correctly when used in queries to DB2 to access table/column names containing that character.

Closely enough for most purposes.

It's called the category, and CATEGORY is a field in the DS_JOBS table.

I've had a bit of a look around in 8.1 and can't find any IADB management capabilities in the Information Analyzer tool. Next week I hope to be on an 8.5 site, and can check there. The Repository Management tab in Web Console for Information Server only works with XMETA, though it does have the usef...

Which part of "Because no-one has imported the table definition" is not clear?

Because no-one has imported the table definition!

See information here.

I have no idea whether U (one of our posters) minds or not.

Why not get yourself a premium membership? It's not expensive, at less than 30c (Rs12) per day, and definitely worth it. It also helps to keep DSXchange alive and running.

The message has been returned from SQL Server. You have sent it a value that it has not been able to convert to a GUID. Don't send it anything for this column.

Think of it as an alert.