DSXchange

Pity the DB2 Enterprise stage doesn't actually exist in server jobs.

Are you writing to any hashed files? After all, the error is a WRITE failure.

avinayak wrote:Hi,
I am trying to write a BASIC routine which get the calling sequence name for the given job name. I am not finding any DataStage function to get the above result.
Thanks,
Vinayak

Why, if you're in a parallel job?!!

Some information is to be had in the UniVerse ODBC Guide but more detailed information is to be found in the UCI Developer's Guide from IBM.

Craig beat me to it.

Always challenge unreasonable and preposterous requirements.

Surely if you can drop indexes without a routine, that is more efficient? How good are your C++ skills? What resources do "they" have for maintaining routines?

Create an additional group for each project.
Protect each project so that it is owned by a particular administrator, its group has full control, and no other group has any access at all.
Allocate users to these groups according to their requirements for access.

There could be many possible reasons for this, starting with the fact that Windows XP is not a supported platform for DataStage. Is the user you created a member of the machine's Administrators group?

It is not. It remains on the enhancement wish list.

There is no separate login ID for DataStage; it relies upon operating system authentication. It relies upon operating system groups for implementing role-based security over use of DataStage clients to connect to projects. An operating system user who is a member of a group to which a DataStage role...

There is no separate login ID for DataStage; it relies upon operating system authentication. It relies upon operating system groups for implementing role-based security over use of DataStage clients to connect to projects. An operating system user who is a member of a group to which a DataStage role...

It is NOT possible to perform a lookup in a Transformer stage using Data Sets. The parallel Transformer stage does not support reference inputs. At all.

How did you effect the deletes? Did you COMMIT this transaction?

Not at all. You are using Field() to segregate the pipe-delimited fields. You need then, from each of these, to segreate the space-delimited fields. LoadDate: Left(Field(Load_Staus_check.$CommandOutput, '|', 4), 10) LastLoadDate: Left(Field(Load_Staus_check.$CommandOutput, '|...

Don't worry about the word "phantom" - that's just DataStage terminology for "background process" - all DataStage jobs run as background processes. When you reset the job after it aborts, do you get any additional diagnostic information "from previous run"? The mentioned routine DSD.UVOpen is the on...

They're not dates - they're timestamps. You need to strip off the date part. Use Left() function, substring or Field() function.

Or change your job parameter data type to String. Alas, there is no Timestamp job parameter data type.