DSXchange

The file is overwritten if no new SETPTR command has been executed.

There are other options with BANNER if you need to generate file names (for example BANNER UNIQUE or BANNER NEXT), otherwise execute new SETPTR command ahead of each query.

What ever happened to G.K.K. (the original poster)?

The free version is still available from Microsoft

Welcome aboard.

Draw a link from the Execute Command activity to the Notification activity. On the Triggers tab of the Execute Command activity test the exit status of your command (the test command returns 0 or 1). This is available as an activity variable.

C:\Program Files\Ascential\DataStage7.5\Docs\Pivot.pdf

Don't get hung up on control characters. Look at the message. Import (read) consumed only 27 bytes. This means either that your metadata only describes a 27-byte record, or that there is a line terminator (record delimiter) in your data.

... and I showed you one way to do that.

Premium membership is not expensive, at less than 30c (Rs12) per day.

Without a specification there ARE no details. Read the chapter in the manual about Build stages, in particular the piece about managing transfers.

DSR_JOBS it may have been; the DataStage object code (helper subroutine) that delivers a list of jobs in the Repository.

Can you post a directory listing of the project directory? It would appear that it has either not been properly created, or that it has been partially deleted.

Welcome aboard.

The SELECTs are queries to the ODBC driver to check that the metadata (column names, data types, etc.) in your job match those in the table to which you are referring in your INSERT/UPDATE query.

That's the $64 million dollar question, isn't it? Further, your quest may be hampered by use of parameterized directory/folder names and/or file names. So it becomes a very complex query indeed. Probably the easiest thing to do is to generate a job report (using dsjob -report command), and to parse ...

How would you get it if you did not have DataStage? Use that method, perhaps from an Execute Command activity in a job sequence.

Write the code to transfer conditionally from input to output. There's no particular "how" - it will depend on your particular filtering requirement.

Ennumerated SQL data types are intended for programmatic use only, and are therefore not in a table. They are in a header file, from memory ODBC.H. Your final question does not really make any sense. A hashed file is one way to implement a database table, and may therefore contain columns of any par...

Certainly. There isn't one.

The DataStage repository is a database so, in the same sense that there's no UNIX command for getting information out of, say, Oracle tables, there's no UNIX command for getting information out of the DataStage repository.