DSXchange

Today this is best accomplished by a) migrating your DataStage Job. Use normal means. Compile the job in the new environment. If possible, keep the Server, Project, and Folder names the same. b) export your ISD project using the export function in the Information Server console. c) Make careful note...

Well.....it depends on the context of the question and what you are trying to achieve....let's get more specific..... a) For an already deployed ISD service, are you looking to "load balance" it (the DataStage Job published as an Operation) onto other DataStage Servers in the same domain? ...

"Data Element" is the property. On the input link of the XMLStage. As Craig notes, the "&" are proper escape characters for when string content containing xml (or anytime characters such as < and > appear) is placed "inside" xml tags as "values"....... Whe...

Well... a 2058 in the formal MQ documentation says the name is incorrect. So try some alternatives... http://www-01.ibm.com/support/docview.wss?rs=856&context=SSWHKB&dc=DB520&uid=swg21166938&loc=en_US&cs=UTF-8&lang=en&rss=ct856websphere The fact that you are receiving the...

Something is wrong with the name of the Queue Manager.....check to see that you are using the right case, be sure it doesn't have any odd characters in it...probably best if it is short, single word and upper case to be safest.

Ernie

There are many... though for what you are noting here, dsjob is probably the most veratile, letting you dive deeply into job runs, link results, etc. etc. It comes in a variety of flavors, whether you prefer to do things in a shell at the OS command level, or C++, or directly from within DataStage. ...

It looks like a fairly poorly designed XML document. It would be interesting to know how the consuming application reads it. Why would you have three separate repeating nodes of "event", each with unique information? It should be perfectly fine to have the sub-nodes of event aggregated und...

Ask why those requirements are this rigid? Is it 40? or 400? Either way, somewhere you are going to have to work out the logic and map out the metadata, unless you write your own entirely dynamic parser.... How hard is it to get the metadata for all 40? ...they can exist on the same xmlInput Stage, ...

...Sort of....but now you are on a bigger topic...I can't comment on the rest of your job, and it's impact on having multiple nodes.... in general, they will all get multiples, although there are ways to control that --- but that is beyond this thread, discussed elsewhere in many topics in the forum...

....Exactly... you are now on the right track......"if" your Web service can handle it (that's a whole different discussion), you can create "additional" clients........ a) add more nodes. Each node process for that WSTransformer will be its own SOAP client, issuing calls with wh...

...it wastes space. Open the document with a tool that understands XML. Generate formatted output ought to be removed or at least not be the default.

Ernie

As Craig notes, DTDs have been pretty much replaced by XSD (XML Schema Definitions). Have the client provide an xsd, or as "complete a document as possible". Look on the web too --- there are tools that can generate reasonable xsd's from DTDs. Ditto to all that Craig said....spend time lea...

Once you recover this scenario, the preferred thing to do is to "Disable" the Operation that controls the Job..... ...in the ISD Console (Information Server Console), get yourself to the "Deployed Application Workspace" [this is after you have successfully deployed a new Applicat...

Can I assume that you are including both Xmx and Xms at the same time? One is for initial size and the other is for max....

Ernie

It's an anomaly. It's leaving out your namespace prefixes. The colon is supposed to be there, but it should also be prefixed with some letters before it. I believe that it had been fixed, as I haven't seen it in a long time, but it was definitely an early 8.x issue. Do you know if the namespaces are...