DSXchange

So... a couple of thoughts. Out of memory, if you reboot your PC does the problem still occur? If the answer is 'yes' then the next thought is your client has gotten itself corrupted and probably needs to be reinstalled.

Is this a problem only you have or does everyone see the same issue?

So... resolved?

Let's get you over into the dedicated QualityStage forum... there you go.

Sorry, but your subject is incomplete - is the service a re... what?

Another thought, a job parameter that can be leveraged to "turn it on" in dev and off in other environments. Basically via a filter in the link to the peek stage that either lets everything or nothing through based on the parameter.

Is your source a file with the first record containing the column names or is it something else?

Yeah, not sure what makes you think you can selectively compile only part of the job. Why don't we start with why you want to do that - is it to "disable" or otherwise not use (I assume) the peek stage target outside of dev?

Okay... so what do these jobs / transformers have in common? Are they all calling some kind of custom routine? That's what the error message you posted is implying to me when it mentions "V94S0_CALL1_XFMR_HTTP_ENCODING.so". Perhaps it's missing / wasn't migrated / needs to be recompiled?

So... some jobs with transformer stages are not compiling or all jobs with transformer stages in them do not compile?

Agreed. And dang, I remember dealing with #2 back in the day. Specifically, a client patch that corrected a sequence job compilation issue... compile without the patch, job no workie, with the patch the generated code (which I think had something to do with looping) actually worked. Had to put an an...

To add to this, the system variable @DATE gives you the date that the job started in internal format. You could then use OConv to convert it to "external" format, a string in whatever shape you need it to be after you subtract one from it.

If you are asking if you can set something in the parameter's value to automatically set itself to "sysdate-1" the answer is no. There are different ways off the top of my head to get that date and yes, the User Variables stage would probably be the most "proper" place to do it. ...

How are your launching / triggering this job? Is there a Sequence job in the mix or if not, can there be? It can set the parameter for you. If there is a script involved, it can do it as well.

So you are calling the function from a C++ routine? The docs say that: ReturnInfo is a pointer to a DSJOBINFO data structure where the requested information is stored. The DSJOBINFO data structure contains a union with an element for each of the possible return values from the call to DSGetJobInfo. ...