DSXchange

And there's really no need pad at all. The Date Format Strings fully support variable width month and day values. %m and %d instead of %mm and %dd.

Regards,

Franklin is correct in that the type of integer reflects the storage space it requires. In this case, it is based upon the number of digits in the COBOL PIC(#) COMP clause. 1-4 digits (PIC 9(1) - 9(4) COMP) is a SmallInt (2-bytes) 5-9 digits (PIC 9(5) - 9(9) COMP) is an Integer (4-bytes) 10-18 digit...

What have you tried and what level of success have you met with?

Look into the Type Conversion functions available in the transformer stage, or the Type Defaults options (or Column-level options) in the sequential file stage.

Regards,

Just to help avoid confusion for the OP: my suggestion is implemented in the target sequential file stage, where the multiple readers per node option is not available (it's active only when seqfile is used as a source).

Regards,

In the sequential file stage, use the Out_format or C_format options for the column(s) you wish to output in hex format, providing an appropriate C-style format string. Here's a list if you're not familiar with them. I would recommend either %x or %X to begin with, and you can adjust them from there...

1) Reduce the number of transformers in the jobs--each one is a separate compilation process 2) Turn down compiler optimization options so the compiler spends less time trying to optimize transformer executable code 3) Get a bigger/faster machine to compile on :) I don't recall the options to set fo...

Place the IsNull() and Trim() calls in separate if expressions:
Regards,

Did you simply disable the part/sort options in the stage (leaving no sorting/repartioning in the job), or did you replace them with a separate sort stage? Does your config file specify the correct scratch and dataset storage locations? Are the stats you just provided from AFTER the changes you made...

Two things come to my mind: 1) Your lookup outputs nearly 200 times the number of source records and more than 200 times the data volume. Is this expected and is it correct? 2) The job is sorting the data prior to writing the output dataset (shown in your OSH) Most likely, the job is "stuck&quo...

123gopal: To echo Ray's question, why? ICONV and OCONV would require the use of a BASIC transformer, potentially affecting performance if this parallel job.

Pavan, can you provide the actual derivations you have written?

Regards,

1) Yes, it can be done. From a DS perspective, it's just another project 2) Yes. 3) That will depend upon your process design...is the project name used within the jobs and other objects in the project? 4) Some Potential Issues: a - Developers editing/compiling/testing jobs will compete for resource...

You could script it so that it appears as a single command to your process

Regards,

Look into the "zoned" option of the decimal datatype...you can find it's description in the IS Information Center.

Regards,

Have you looked at the Date and Time functions available in your version of DataStage to see what might appear to be appropriate?

Regards,

You should ask the data provider for the specifics on how the date is formatted. Lacking that information, is the value in your example the only value you have encountered, or are there other values which you can examine to determine a pattern? Also, look at what the date is supposed to represent: B...