DSXchange

Exactly... the desired goal is to have 'one line'. No wasted bytes...less space on the wire, on disk, etc.

Ernie

Follow Craig's note.

....the formal solution is to "uncheck" 'generate formatted output'.......it's just a check box. The point that Ray and Craig are making is that we should never check that box......

....uncheck it and the crlf's will just "go away"...

Ernie

Are you looking for the "value" that might have been passed to a parameter, without knowing the parameter or the job name? A Metadata Workbench query can do that, "if" you were collecting Operational Metadata for the particular Jobs in question....

Ernie

Metadata Workbench is not performing "value" based lineage analysis...however, it will certainly show you the flow that data can take thru it's various paths (down to the column level), and from there, review things like contstraints that might force "some" data in one direction ...

Your sales team has access to a sizing tool, but like anything, it produces a "swag" --- a 'guestimate' of what you might need..... it take a lot of things into account, as you should, such as the expected number of developers, the number of "concurrent" jobs you might want to ru...

Beats me....it definitely throws an error when you don't supply any repetition element, but I haven't tried providing many in a very long time...I suspect it finds the first one and is happy. Only one is needed.... provided that it's the correct one... ...quite clearly, one of the ones that was sele...

I haven't tested this much..... are the sessions all of the same credentials, or unique credentials?

hard to say, but perhaps your payload grew....and went past the length of the column on the link and got truncated.

If you are not yet using DTS, and you can't afford to lose messages, then you probably should avoid using a destructive read. Browse the messages in the source, and only remove them afterwards....via audit check on your target, and then cleaning them out via message id.... ....another technique you ...

Even if you could control it, I wouldn't want to rely on a process like this......what if the entire DataStage machine were to fail? Then what does it mean that the database did not get written? You can ensure that the original message will not be lost, using the DTS........but doing subtle message ...

It's really a web server issue. ISD uses IBM's IHS (a subset of which is inside of WAS).....load balancers and firewalls in front of that can do even more creative things. Like WS-Security, keep this type of logging at the network level.

Ernie

It certainly isn't available to ISD, as the http stuff is already stripped away by then.....you "might" be able to get it at WAS, at its HTTP server component that receives the incoming HTTP packets containing SOAP.....otherwise, another thought would be to see if you can intercept it with...

We need a lot more detail...what stage types, what kinds of settings...did it ever work before...etc.

I don't think we can really help you until you outline why and what you are trying to accomplish. There may be 100 ways to accomplish whatever it is that you are trying to do...and perhaps even access to xmeta might be one of them...but before you spin your wheels deciphering the underlying model, p...