DSXchange

My solution will also work for a variable N, provided the Column Import stage is equipped to deal with the largest possible N (number of fields) that will be in the delimited string. You could do the same with a Transformer stage. Absent columns can be populated with null or "", depending on what yo...

Given the price I'm sure that your current employer would be more than happy to have you represent them. Won't do any harm to ask anyway.

Of course you can. You can execute a pipeline through ExecDOS (for example command1 ; command2) or you can create your own after-job subroutine that invokes the batch file and tests for the empty file.

I still prefer never to abort jobs.

That's not something I've ever tried to determine.

The fact that even DSGetProjectInfo() does not let you know whether or not the project is protected suggests that the mechanism is not an obvious one.

_
Register here

Sydney 13 May 2008 (Tuesday)
Melbourne 15 May 2008 (Thursday)

Compiled date is one of the undocumented columns. It is not accessible as a column name. You need to work out which field contains it, and use an EVAL construct to access it.

Actually, I just took a look at DS_JOBOBJECTS and can't find the compilation date. I may need to get back to you on that.

By invoking the DSSetUserStatus() function within a job invoked by the Job activity. This is easy to do if the job is a server job; for a parallel job you will need to create a parallel routine as an interlude to DSSetUserStatus().

My issue is that DataStage is not where the DB2 database is. One is on UNIX, the other is on the mainframe. Are you using DB2 Connect software to access DB2 on the mainframe? If so then you can probably use the Stored Procedure stage. Obtain the year value by reading the file with a Sequential File ...

No command-line interface exists to change a project from Protected to Unprotected or vice versa.

The space is the sign character. You could specify the Numeric data type to be unsigned.

Determine in which column the level 01 item appears and fill in this value during the import. Its default value is 8. It appears that your COBOL FD has its A margin in a different column number.

Parallel routines are not compiled from within DataStage. They are totally external C++ source code, and must be compiled using the appropriate C++ compiler and linked using the appropriate linker at the operating system level.

Wherever your DataStage client is installed (for example C:\Program Files\Ascential\DataStage) there is a sub-folder called Docs. It is in the Docs folder that you will find Pivot.pdf.

As per the details in the above post i have searched for dsexport and dscmdexport in '/tools/Ascential/DataStage' , but any of the "export" commands are not present in the above path. Can anybody please tell me why this commands are not present in our environment? UNIX pathnames? These executables ...

The compiled date of a job (or job sequence) is stored in the ROOT record for that job in the DS_JOBOBJECTS table in DataStage internal format. The compiled date of a routine is stored in the DS_ROUTINES table in DataStage internal format.