DSXchange

Once you know more about it, the answer is yes. But you have to know what is required. For example, there is a post somewhere that writes an IMF file for QualityStage. Search for it. This is a metadata file rather than a data file, but will get you started.

Can you restore UV_SCHEMA from backup (remembering that it's a dynamic hashed file, so you'll need its DATA.30, OVER.30 and .Type30 as well?

If you can, you sholud be able to use VERIFY.SQL for any project whose schema is not recorded.

There are other solutions, but the Transformer stage with two outputs will be the easiest to implement, and is correct. Simply map the columns required on each output using drag and drop. You could do the same with a Copy stage with two outputs.

Processes dsapi_server and dsapi_slave have nothing whatsoever to do with running jobs; rather these are the agent processes for connected DataStage clients. Depending on version, server jobs run as uvsh or dssh , while processes in parallel jobs run as lots of osh processes - one conductor, one sec...

Getting it back will be just as much as a problem whether you use a sequence or an identity column (SID). Why do you think you need to do this?

If it's for a subsequent run, you can select them immediately prior (for example constrained by batch ID or run date).

It's a connected DataStage client (dscs = DataStage common server).

It may have child processes running as dsapi_server or dsapi_slave.

Hashed files are not available in DS EE, but you could achieve the same thing with a Lookup to a Lookup File Set or anything that can populate a virtual Data Set.

VERIFY.SQL SCHEMA /usr/ascential/datastage/sql/catalog [ FIX ] If you use a name as the argument in VERIFY.SQL it fixes the objects to conform to the catalog. If you specify a pathname it fixes the system tables to conform to what's out there. (Caveat: I've never tried this with the CATALOG schema -...

Ask for the class Programming with DataStage BASIC - it's on the books but isn't scheduled.

dsenv is a shell script. View it to understand what it does. In some cases you may need to edit it.

Oh dear. First check whether UV_SCHEMA really is corrupted. Use uvfixfile or fixtool. If it is, repair the damage. You may need to follow this with some VERIFY.SQL SCHEMA pathname commands to reinstate schema entries into the SQL Catalog. Note to Inexperienced Users Arnd is very experienced with the...

DataStage faithfully logs every warning it receives. That way you can't sue IBM for not letting you know. As Craig says, you can't suppress this; you must implement a design that does not generate the warnings in the first place. Such a job design will give you the additional benefit of running more...

Or find some options to make it less than 2GB, such as loading it only with columns and rows that are actually required in the job.

You need more disk space. Deleting anything created by dsapi_server or dsapi_slave (the agent processes for connected DataStage clients) is at your own risk entirely. The DS_TEMPnnn hashed files have been being created since your first job in which there was any dependency of one stage upon another....

That message is returned from Informix if you are connecting to a table that has no logging. I vaguely recall there is an environment variable that you can set to prevent its being generated.