DSXchange

This is also extremely useful when adding new custom attributes. You can edit swathes of terms and categories and assign values to the new custom attributes in one fell swoop. I have made much use of this capability.

Then you can mark it as resolved by clicking the green button at the top of the screen.

Why? If the port number is in use, the appropriate service is running.

The mandatory ones are

• server1
  ASBagent
  LoggingAgent
  dsrpcd

You could write your own widget - BGA itself is pure C# but is written only for Windows. Yours would have to use MacOS calls.

Q. Why do Java programmers wear spectacles?
A. Because they can't C#.

What is the actual, and complete, data type in Oracle for this field?

See my answer to your other post with this question.

Providing an illegal value as default will have this effect. For example, if the default value of a Date job parameter is "", then this will prevent a job run request from being issued successfully.

Unfortunately, every value is legal for String parameter type.

A Sequential File table definition stores wherever you specify, which can certainly be the Table Definition folder. This is specified on the first screen of the import wizard. You don't need to create anything else. And, if you didn't get that right, you can simply drag a table definition in the Rep...

It's exactly the same on the client. Run the Update Installer and provide the pathname of the package file.

serverStatus.sh for the WebSphere Application Server process server1 netstat for the ASBNode and Logging agents, specifying in a following grep the port numbers that you has ascribed to these (probably 31531 and 31533). netstat also for the dsrpcd daemon, again specifying the port number that you h...

As far as I am aware, there is no way to change this behaviour, annoying as it is. The interface remains a general text search. An enhancement request to allow this behaviour to be configurable would probably be a Good Thing.

Of course you can write your own widget - the REST API is documented.

You can not bypass using a bridge. Metadata Asset Manager just provides a cleaner way to use the bridge. The error is not a Cognos error. It's a Metabroker Interface (MBI) error code. Read the message carefully. Either your username/password is incorrect, your dispatcher URL is incorrect (unlikely) ...

It appears that English is not your first language. I am struggling to understand what you are asking. Do you have a native English speaker who can help you to formulate your question more clearly?

The options is permanently disabled for parallel jobs. When compiling in Trace mode, the option for limiting rows is given at that time, not in the Job Run Options dialog.

Yes there are, they involve deleting instance records from RT_STATUSxxx, but I don't have the details readily to hand.