DSXchange

There are also some very special situations/techniques/approaches that require Server..... Some of this is a factor of Job design, and other methods are possible with Enterprise Edition, but here are two that only Server can easily do....(I'm sure there are others...and in the context of this discus...

Your best bet, for pure scheduling, is probably to use the JNI to ultimately issue your call via the widely used "Job Control" API, which is available for C++.

ERnie

Assuming you are using Server and Folder, and are successfully parsing your XML, take advantage of the fact that the XMLStages support "pass-through". This means that any column on the input side, that is also on the output side, with NOTHING in the Description (no Xpath that could confuse...

...if it still gives you the "plug" icon (that's just a default that appears when there is an issue with the real icon and/or it's client side program). If you still see it, there may be a problem somewhere with the registering of the client side of the xml stage. I can't remember the exac...

At that low rate, "always on" might be overkill..... if the flexibile technique you need is easier to do with straight job parameters supplied directly to a SQL statement, using a single rdbms stage going ultimately to a single WISDOutput may be fine.....especially if it is a Server Job, w...

Michael.... One key thing I don't think we talked about earlier was the frequency of calls.... how often is this service invoked? How many times per day, per hour, per minute, per second......? That will also help determine the necessity of doing this as a lookup technique vs a pure parameter based ...

Search thru some threads here for more details, but here is the summary..... when you install 8.x, you are asked at install time if you want MQ, and then, if you want Server or Client (Server means that MQ Server must be co-resident). The MQ Connector can do either....but the MQ Plugin is dependent ...

Stop and re-start the ASBAgent......that might be part of the issue.

Ernie

Stop and re-start the ASBAgent......that might be part of the issue.

Ernie

...and when you leave it as is, the "test connection" fails?

Do you have more than one DataStage engine in your Information Server domain?

Ernie

Ok....then you should be ok, but there may be some fix/patch issues to consider (again...suggest that you search thru the forum here and also call your support provider). Also --- try it in a Server Job to see if there are any differences...there were situations in the past where it worked in one jo...

JavaPack will do it nicely. You write your own class that reads your LDAP structure and integrates with the JavaPack api to write resulting data to a DataStage link.......DataStage invokes it from the one of the Java stages when the job is executed.

Ernie

"could" be a support issue..there were numerous issues with validation. Check with your support provider....and search thru here -- the subject has come up before. Someone else may have confirmed various symptoms as having patches. In the meantime, what kinds of invalid are you looking for...

Here are the basic steps.... a) create a simple job...like WISDinput to Transformer to WISDoutput. b) enable it to be a service (job properties...check box below multi-instance) c) compile it d) go into the Info Server console. e) create a new Info Services project (this is not a DS project) f) find...

Nope. Another post process is needed. I usually end up processing triggers in this way so that I can slice off individual documents for individual MQ series messages......I have seen scenarios where someone picks up my messages for other reasons and then writes them out in another application (java)...