DSXchange

When you look at your log file entries in the director you can go through them to find the one which lists your incoming parameters. You need to know where those extraneous quotes are coming from in order to get rid of them, be it in the job or in the program which sets & passes the parameter va...

Does the paramater value for #parmDateTime# already contain the extra double-quotes or are they added in the before-stage command?

There is always going to be a limit somewhere, but I'm not aware of any limits that you will hit when designing your job - if they fit on the canvas they'll compile and run. If you have Transformer - Transformer links in your jobs, activate interprocess buffering or put in IPC stages, and limit your...

Since the names are explicitly filtered out, you cannot use the Manager to load the column metadata using either the UniVerse Table or UniVerse hashed file tabs. You will have to manually enter the metadata. But the hashed file as well as the Table view can be read. Just remember the standard caveat...

The repository table names are filtered out from the standard ODBC and direct hashed file view. You can type in the name explicitly to access the table.

True - there have been a whole slew of installation issues as well as XML questions in recent days, but I think the FAQ forum should contain a "digested" and prepared post with both the question and the most common answers.

Ravi, the audit file is created as an audit trail of actions, so if you copy a job into project X that project sees the file as being created on the date when the job was loaded, not when it was originally created in another project. Along the same lines, any modification history would also not be v...

When you do a job reset in the director you should see a new log entry with the title "from previous run..."; this often contains additiional information about the cause of an abort. Is the job you are running a multi-instance job and does the error occur every run?

Hello and welcome to DSXchange. This error has several possible causes and it has been extensively handled before. Please go to the search facility that is shown as an option in the top of each page and enter the text "dsloadlibrary: error in dlopen" and use the "search for all terms" option to get ...

DataStage on Windows installs it's own specialized TELNET server that directs you straight into the DataStage environment. You will either need to use a "normal" telnet server or open up a DOS windows/client using another method. Once you get the normal DOS prompt you can execute the "dsjob" program...

Have you runstated (is that a verb?) the table? Could you check the speed of your CFF stage when it doesn't write to anything by putting in a transform with a "1=2" consraint? It should write many thousands of rows per second. What bulk load options have you specified for the DB/2 load? Approximatel...

Ummm - this was posted in the PX forum - does that mean this is a server job?

What rows/second speeds are you getting in the load (and just as a crosscheck how many rows/seconds does your CFF stage output if you redirect it to /dev/null?

Your image quota has been exceeded and you still haven't found out what schema values DS is using. Someone more knowledgeable than I will certainly help you. It might still behoove you to find your orchadmin command - if not for this issue then for the future.

The IBM docs state that 3107 is a warning, SQL3107W There is at least one warning message in the message file. which doesn't help much Does you log file have anything else in it? If you were to partition your table you would get some really significant speed increases on PX - but that might not be p...

Kapil, since the orchadmin program is run by PX jobs it needs to be installed. The screenshot is nice, but doesn't help in locating your problem, please refer to your original post where you showed that DS thinks a ustring length in the schema is 0... I think that the path to solution of your proble...