DSXchange

There is no log folder. Each job log is a table in the Repository database. It can be accessed via the Director client or via the dsjob command.

I think you would be wise to consider enrolling in a DataStage Essentials class.

Use the Data Set Management utility (in the Manager's Tools menu), or use the orchadmin command from the operating system command line.

DO NOT EVEN CONTEMPLATE DOING THAT The project directory is only a part of the picture. It is also a database schema so there are system tables that refer to it. What you really need to do will depend on what's preventing the Administrator from finding the project - probably one of the system table...

mkdbfile is for either operating system. It resides in the DataStage Engine bin folder.

Read the entirety of the error message and report what you can discern from that. You might also post the entire error message so that we can also discern what might be happening. There is more information in error messages than most tyros imagine.

You need to know the output file name. Then you can search for it. Typically at least the file's directory will be a job parameter, so its location is indeterminate by inspecting the DataStage design. You need to consult the Director client (or job log via dsjob command) to determine with what param...

Don't include it (the column) anywhere in the job, other than in the user-defined SQL.

Please report the result of the following command:

You spend money with IBM Services. They will implement the dynamic configuration file and other pieces that you need for grid execution.

Thus far they have not released that particular toolkit to contractors nor, as far as I am aware, to resellers.

Dates, as you would have learned had you conducted a search, do not have any format - they are stored in binary format.

Date format strings specify how to convert between dates and string representations thereof.

YOU must create the groups. They are operating system groups. There is no such thing as a DataStage group. DataStage roles are associated with operating system groups to implement project security.

1. By using a mkdbfile command rather than a CREATE.FILE command. 2. Different files will be created in the FILE_TEST directory. 3. With any text viewer you like. Tip To execute a DOS command from the Administrator client, use the DOS command with a /C switch. For example: DOS /C "mkdbfile F:\M...

A job does not have a path. It is a set of objects stored in a database called the Repository - there is a separate Repository for each project in versions earlier than 8.0. DataStage server jobs are executed in a "virtual machine" called the DataStage Engine by a DataStage program called DSD.RUN, w...

Warning - Technical Content (again) The descriptor file for a File Set or a Lookup File Set has a name ending in ".fs". Nevertheless the descriptor file itself is a text file, and can be examined with a text editor to determine the location(s) of the data file(s) comprising the File Set. Premium me...

How do you know on which node(s) the Lookup File Set was created? The control file (xyz.fs) is possibly created on the conductor node, but how have you determined the location(s) of the data file(s)? The control file - sometimes called the descriptor file - is not the Lookup File Set itself.