DSXchange

DataStage MVS generates nice COBOL and JCL, but the politics of getting "them" to allow it to run on their precious mainframe can be altogether too time-consuming.

When you import from the COBOL FD you must specify the column number in which the level 01 item occurs.

Run a fork-join design, using an Aggregator to count the number of each grouping key combinations. Run them all through two streams, one with a Remove Duplicates stage, the other with a filter stage on the count being >= 2.

Handle your nullability properties correctly. The stage in question is the one performing the export, not the Modify stage.

Set SHLIB_PATH in the dsenv script.

Please be more precise about "somewhere". Then review the data types mentioned in Parallel Job Developer's Guide - which include up to uint64 in the integer series, very large decimal numbers, and single- and double-precision floating point numbers (huge numbers, potentially).

You don't need to install MVS edition, though your IBM account rep would be happy for you to do so. You can get the data from the mainframe using FTP.

Join stage with full outer join would be first choice. Lookup stage if your second input is small enough to load into memory.

Problem is that these dates are all valid, being early in the so-called Christian era.
The correct approach is to use pattern matching.
before applying an IsValid() function.

Upgrade to version 8.0 and use parameter sets.

Downgrade to version 7.0 and copy/paste activities in job sequences - they preserve their parameter settings. This functionality has been removed for version 7.5 so that arbitrary expressions may be used to supply parameter values.

For user-written server routines there is not.

You can write the routine to ignore some of its arguments, but the number of arguments is fixed.

You could never have gotten those records into the hashed file, so you will never succeed in looking them up. Please post the metadata from the job that populates the hashed file. Do NOT change MAXKEYSIZE without first taking expert advice on the consequences. For example, you will not be able to us...

But these routines are probably even more better!

You could have used strings utility for that!

The ULIMIT in uvconfig is ignored if the UNIX ulimit is larger that the value specified in uvconfig.