DSXchange

Andrew?

Assuming these are the only two possibilities, use substring operators to extract all except the prefix, then trim leading and trailing tilde characters from the result. Trim(If Left(InLink.TheString,5) = "~LFA" Then InLink.TheString[6,Len(InLink.TheString)-5] Else InLink.TheString[8,Len(I...

1) No idea. You have not provided the configuration file nor any information about the use of node pools. But at least four. 2) Yes, and no. You must have at least one node in the default node pool, and the first-named of these (by default) will be where the conductor process executes. 3) Yes. The s...

Once, that is, they provide a command line interface that allows MAM to perform the initial tasks - define server, create import area, perform initial import. These are sadly lacking, and prevent one from totally automating the process.

We ended up using a packet sniffer (WireShark) to see what was actually being transmitted/received.

Unless you specify expressions in FastTrack the generated job only has a container containing the text of your mapping specification as an annotation. You still need DataStage skills to achieve much more than filter, lookup and join.

Tony (IBM InfoSphere Data Integration Project Manager) will be at the Information Server user group meeting in Melbourne on Wednesday, August 29, 2012. Details at http://www.meetup.com/ISUG-Melbourne.

Please RSVP for catering purposes.

Tony (IBM InfoSphere Data Integration Project Manager) will be at the Information Server user group meeting in Sydney on Thursday, August 30, 2012. Details at http://www.meetup.com/ISUG-Sydney.

Please RSVP for catering purposes.

Tony (IBM InfoSphere Data Integration Project Manager) will be at the Information Server user group meeting in Canberra on Tuesday, August 28, 2012. Details at http://www.meetup.com/ISUG-Canberra.

Please RSVP for catering purposes.

DSGetLinkInfo() has to be called with a job handle as its first argument. You are trying to call it with a job name as the first argument. Try DSJ.ME.

You don't exit from your routine in the event that you cannot attach the job - you blithely sail on into the DSGetLinkInfo() code.

The structures in XMETA are deliberately undocumented by the vendor, and may change at any time. Using exports is probably safer as a long-term strategy.

If you have an explicit Failure trigger it should pre-empt anything the Exception Handler might be set up to do. A Failure trigger should fire if the exit status is any non-zero value.

Welcome aboard.

This information can be found in the DS_AUDIT table, MODS association.

Search DSXchange for examples.

Wrap them in your own after-job subroutine (using CALL statements). You can use DSExecute rather than ExecSH within your own routine.