DSXchange

Your approach is similar to what happens with database sequences - by changing the sequence 'cache size' you pre-allocate blocks of sequence numbers so that you don't need to get back to the database as often, with the downside that you might lose much of a cach block of sequence numbers if the job ...

I'm not at a DS system so I'm not sure is the command is "DOS" instead of "SH" but it should be in your help file.

The '$ORACLE_HOME/bin/sqlplus' is for UNIX, replace it with the appropriate command for Windows.

I prefer to use a SQL command file instead of your approach. First of all, it makes testing a lot easier until you have the format of the file correct, then it just takes a small routine to make the file contents dynamic. Take a look at the following routine which is designed to execute just a 1 lin...

Perhaps you could try a search on "stored procedure return value"; I got 50 hits on that.
Or do you wish to execut Oracle SQL from a UNIX script called from DataStage?

Try doing a simple single-key lookup to your DB2 stage. Activate the automatically generated SQL, and then click on user-defined so that ityou can edit the existing SQL. From that you will see the format and syntax and can add your own between condition easily.

This shouldn't be the case, but obviously is since you are having difficulties. Have you tried the reject link method to see what the column contents are?

You will need to stop DataStage, replace the files, and restart.

THe "S" stands for signed and add an explicit + or - sign to the data. Considering the error message you probably have an offset error somewhere and have different data. Use the reject link method to see how DataStage actually parses the data.

It would seem that you do have to change the metadata on column 128, "GL_WORKING_CAPITAL". What is the DataStage column definition with type and length, and what is the column data value in line 2? You can use a reject link from your source stage (hmm, I'm not sure if FTP allows for one, but you can...

If the file isn't corrupt (did the UVFIXFILE show no errors?) and your disk or directory still has space then the error is an odd one. The error can occur when the key contains a null or @FM but since these records are generated by DS that is highly unlikely. Can you save a copy of the job, delete t...

Does the error occur in the merge stage? What are the stage settings you've used?

jstrobel, thanks for the detailed description on how project level parameters work. I was more interested in the specific variable name and value setting you were having problems with, particularly since I thought you might have been using a name (instead of value) of $PROJDEF. But that is a moot po...

Even though compilers are usually backward compatible as well, the docs do state specific compiler versions as mandatory. When you say the jobs won't compile have you looked at the error messages to see if the errors might be due to compiler switches?

Shamshad, This is a very easy thing to do since there are no COBOL specific structures or data types in the file. Just declare the columns in your FTP stage with fixed column lengths and no column separators. You can import the COBOL copybook for that file into your column metadata and use that defi...