DSXchange

Data are moved through buffers - there is a set of buffers (= virtual data set) associated with each link in the job design. Data are moved in quantities affected by the buffer settings - by default the buffer size is 3MiB and threshold for beginning to resist input is 50%. On that basis, you would ...

Once you know the location of the user status area - I'm sure I've documented this somewhere on DSXchange - you can write a parallel routine that uses InterCall functions ic_open, ic_recordlock, ic_writev and ic_close to update that particular field (field #9 in one of the RT_STATUSnnn records). You...

It seems you have set up your state file with a block size of 1.

All of the design-time information can be had from DS_JOBOBJECTS table. Much of the information about relationships between stages is also to be found in the RT_CONFIGnnn table for the job, while the run-time status is to had from the RT_STATUSnnn table. However the structure of these tables is not ...

Sounds like you need to create your own script, then.

ArndW wrote:I'm not sure about year 0000 being valid, I think it might be.

It isn't. The day prior to 0001-01-01 is 31 December, 1BC.

You should be able to use a WebServices Transformer stage, as you suggest. But the service provider must be able to handle XML with header and body.

encrypt.bat was new in version 8.7 and ends up invoking a Java class so, even if you could get the bat file, that would not be enough.

I can't recall whether you could read the parameters from a file with the dscmdexport command - you will need to check your documentation for all options.

That's an intriguing solution, Arun. Are you able to provide a concrete example?

What Andy posted is for inbound RESTful requests. I assume your requirement is to have a DataStage job as the requestor (client)? Is this correct? The actual method you use will depend on the transport layer - for example will your request be REST over HTTP? Might you use a Java class to make the ca...

Another approach that I've seen at some sites is not to use Parameter Sets in server or parallel jobs; only to use Parameter Sets in sequences. In the Job activity the local parameter is fed its value from the parameter from the parameter set. Consistent parameter naming methodology is key to keepin...

To clarify what Andy has written, the engines (server and parallel) use different internal storage mechanisms. There's nothing to prevent you from creating parallel routines that perform Iconv() or Oconv() functionality, but that would be re-inventing the wheel - in general there are other ways to a...

Investigate the environment variable APT_DECIMAL_INTERIM_SCALE, the "type" argument of the DFloatToDecimal() function, and the Ceil() and Floor() functions.

You might also consult the FAQ post on Common Date Offsets in Parallel Jobs

The "more natural way" is to create a parallel routine and to call that from the parallel Transformer stage.

You might also consider creating a BuildOp.