DSXchange

The Director client has a Print option on its Project menu. When you open the print dialog, there is a Print to File check box. This is by far the easiest way to get a flat file containing logged events. You can apply a filter in Director before printing if, for example, you only want warnings and e...

Your original post flagged the job type as parallel. Is this correct? It will change most of the answers you've already read.

The ulimit reported in the log suggests about 2GB as the file size limit. Have your UNIX administrator check the ulimit for this user, and change it to unlimited.

What is the data type of column myDate in your example?

The lock is held by a defunct process, which is why you're not seeing it in Cleanup Resources. You will need to login on the server, use list_readu (from UNIX) or LIST.READU (from dssh) to find out who's got the lock, and unlock that particular lock using the administrator-only command UNLOCK from t...

No, but you can gather statistics. On the Job Run Options dialog (which you get when requesting a job run in Director) there is a Tracing tab. Enable statistics gathering separately for each active stage in the job - at least those in which you are interested - before clicking the Run button. As far...

Do you have "x" permission on the libraries?

ml wrote:u r wlcm.
mat

You seem to be in a locale where there is a shortage of vowels. Do you create your system documentation thus? Please don't do it here - not everyone here has English as a first language, so these kinds of abbreviation aren't helpful.

Stored procedures used by DataStage must either consume or supply a result set, which must match the column list in the job design. Depending on the database, you may be able to use a non-ODBC stage's Before-SQL tab to issue a CALL statement. But why a stored procedure? A DataStage job can perfectly...

Welcome aboard! :D

Download Etl_Stats from Kim Duke's site (or from ADN). This will give you most of what you're after. There's no canned job that you can run. While you could write one, why re-invent the wheel?

Possibly internal corruption in the Repository database or associated files. Take a backup of the project if you don't already have one. On the server machine, attach to the project directory then execute the following commands. . $DSHOME/dsenv $DSHOME/bin/dssh This should get you to the TCL prompt ...

Is there some limiting setting for the DB2 bulk loader? DataStage has sent all the rows; one can only assume that there's something in DB2 blocking them. Ask your DBA to check.

I'm certain this has been answered before.

In a preceding Transformer stage, generate twelve Month columns as constants (the names of the months), and pivot on these also. So that Month in the Pivot stage is derived as JanName,FebName,...,DecName (you do need to fill in the remainder).

STOP statement in Routine is bad practice. Routines should always return. Prefer something like ParamName = Arg1 ParamRec = "" OpenPath "C:\users\mydir\MyParamValues" To ParamHashedFile Then Read ParamRec From ParamHashedFile, ParamName Else ParamRec = "" Call DSLogWarn...

The dslictool utility is for handling the rare occasions when licensing gets confused.