DSXchange

You could always change your expectations.

Or you could address the issue of the Pivot stage's library, rather than ignoring it.

Read with a Sequential File stage, that has metadata suited to the detail lines and that has a reject output. The header, since it does not conform to the width of a detail line, will pass onto the reject link, where you can re-parse it with a Column Input stage.

What has that got to do with user-defined environment variables?!!

The message "Unable to open OUTPUT#/Inventory/BALANCESDS.20080401094424.dat: No such file or directory. " suggests that you have omitted one of the surrounding "#" characters from the job parameter reference OUTPUT.

Whoever took the backup should have labelled the media and, ideally, made an entry in a system administration record.

Yes, BIG5 is the "traditional Chinese characters" NLS map on UNIX.

NLS map can be a job parameter - you will need to be aware of how the other data are encoded in order to make intelligent choices.

You do not reclaim space through DELETE operations. Free space is preserved in hashed files against the likelihood that it will be needed again in the future.

The only command that can reclaim space (apart from deleting and re-creating the hashed file) is RESIZE.

What do you mean by "connect"? DataStage is reasonably at home with most operating system technologies, the site where I am currently working use LDAP for enterprise-wide authentication. But I am not sure what you are asking.

To clarify, you want to pivot rows into columns? Is that correct? The technique is called "vertical pivoting", and a search of the forum for that term will reveal a number of ways that it can be done with DataStage.

The data source name needs to be localuv which is pre-defined in your uvodbc.config file. User name and password will be disabled, because localuv is a pre-established connection to the DataStage project itself.

Check very carefully the Format properties, including the individual Field Width properties.

That leaves questions 2 and 3 to be answered.

There should also be a file called Template.ini (at the same level as DSEngine and Template). This file specifies the location of the template. Example: cat Template.ini [Project] Location=/app/Ascential/DataStage/Template/ FreeDiskSpace=0 Check that this file is present on your system and contains ...

You are very unclear about what has happened, what is happening and what will happen. Please answer the following questions. 1. Is the hashed file still created? If so, what is the name of that hashed file? 2. Is there a VOC pointer to it in the project (either because the hashed file was created in...

Use a UV stage with user-defined SQL containing a DELETE statement such as Provide the key value from your text file.

If the hashed file has been created in a directory you will need a VOC pointer to it. Search the forum for the SETFILE command.