DSXchange

At some point in the future that "no support" statement may have to be rescinded. They are definitely looking at password policies for the internal registry.

DateFromDaysSince() should be the function you need. Offset is 365, or 366 if you're in a leap year.

If you're generating a command line argument from a DataStage sequence an elegant expression is This works because the internal date format (number of days since 1967-12-31) remainder after dividing by 7 is 0 for Sunday.

soumya5891 wrote:In this regard also one thing needs to be performed that the transformer must run in sequential mode.

That is never true. Learn how to get your partitioning correct.

My guess (from the error message) is that the quotes are being stripped.

UNIX drivers for MS Access do not ship with DataStage.

Not only are there no standards, even if you decree standards there is no enforcement of them in the internal user registry. An enhancement request has been opened with IBM to provide this functionality.

Sort probably is working, but the database server for your target table is storing rows in whatever order it feels like. It is a fundamental tenet of databases that storage order is under control only of the database engine.

Wrong.

The UV account is the location of the "system tables" for the DataStage engine, but you don't necessarily need to log in to that account to unlock jobs.

Option (a) would expand your horizons immensely; LIST is the principal command of a UniVerse query language called RetrieVe (called other things in other database products, such as INFORM in Prime INFORMATION and ENGLISH in Unidata). But pursuing this would not be focussing on your "core busine...

A side note. Forget about XMETA while you're on version 7.5. It simply does not exist.

And documenting queries that will work in version 7.5 is a waste of your time - everything changes radically when you move to version 8.0 or later.

Why not concentrate on becoming the best DataStage developer that you can? There's no need for detailed technical knowledge about how the engines, the services and the metadata repository work - finer minds than ours have spent vast amounts of time making these work as invisibly as possible.

Wrong. Console for IBM InfoSphere Information Server supports Information Analyzer and Information Services Director. The one you want is Web Console for IBM InfoSphere Information Server and you will require sufficient privileges to view the logs (granted through Information Server roles and DataSt...

(a) B-tree
(b) B-tree
(c) 1000 (don't you dare!)
(c) No.