Search found 2288 matches

by roy
Sun Jul 31, 2005 6:42 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: ReadOnly Project
Replies: 2
Views: 678

Hi, IMHO, The correct way of protecting and unprotecting your project is simply performing this action via DS Administrator. You'll need a production manager privilage defined to a group that is not the developer's group. the weak side of this is that you might need to unprotect your projects in ord...
by roy
Thu Jul 28, 2005 8:39 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Jop Parametre
Replies: 3
Views: 837

Hi,
Yes it does happen some times :(
You'll need to retype your password and recompile.
This situation might also occur in schedualed jobs - reschedual them and in the schedual retype your parameters.

IHTH,
by roy
Thu Jul 28, 2005 6:39 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: User defined SQL
Replies: 8
Views: 4200

Hi and welcome aboard :),

Since such operations might need other clauses like table space and such, usually I tend to ask the DBAs to build me a SP performing the operation to their standards and invoke it as a before or after sql command or as a user defined sql.

IHTH,
by roy
Thu Jul 28, 2005 6:28 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Files bigger that 2GB form DataStage Basic using Seek
Replies: 7
Views: 3024

Hi, From the top of my mind: Try to make seek jumps in intervals lower then 2GB perhaps it will work. you can use the additional ,1 in your seek statement to signify relative to current position. I'm not sure and it is not mentioned how seek works and 2GB limits of files seeked on. By the way why wo...
by roy
Thu Jul 28, 2005 6:20 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: RESTARTING OF A CHILD SEQUENCE
Replies: 1
Views: 649

Hi,
Are you using the termination activity and using the send stop requests for running jobs inside the sequence?
by roy
Thu Jul 28, 2005 6:16 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Performance Issue using STP stage
Replies: 2
Views: 921

Hi, Your design if slow by nature, your reading a row sending it ot the stp and catching exceptions this is not a quick task. you'll be better off loading the data to a temp table, then run the STP (that will read the table and give a result set) and populate your rejects table. A better way would b...
by roy
Thu Jul 28, 2005 6:01 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Send email datastage 6
Replies: 2
Views: 682

Hi,
AFAIK, you need to have a program like blat or similar to do it.
In case the notification activity doesn't support this you can always use a routine to run a command line execution of your Email application.

I hope I remember it right it has been a while since I worked on version 6 :(

IHTH,
by roy
Thu Jul 28, 2005 2:57 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Normalize a field on Parallel EXTENDER PX
Replies: 4
Views: 1153

Hi And welcome aboard , You could read the data and in a transformer build a row foreach element (use Convert to change the comma to LF) to a seq file; So you should get something like: 1 US FR IT GR 2 GR BG After you have this simply read the file and store the number in a SV (stage Variable) build...
by roy
Thu Jul 28, 2005 2:22 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: parallel extract
Replies: 9
Views: 4028

Hi,
Did you rebuild the stages or simply added the schema prefix to the existing table name?
If you didn't rebuild the stage try it and see if the error persists.

IHTH,
by roy
Wed Jul 27, 2005 12:49 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Null handling in PX Sequential files
Replies: 23
Views: 19108

In any case reading frm seq files should be using varchar types regardles of real type since they are actually varchar (unless you have a fixed width file). using other types might cause you problems. having fields specified not null able means they can't be tested for null value sine they can't con...
by roy
Tue Jul 26, 2005 8:40 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Loop job problem
Replies: 3
Views: 833

Hi, what do you mean you see then only after the 3rd run? are you using client tools? is there a refresh interval? after the first run what happens if you run commit in the client? I've worked with MSSQL before and it worked fine. Perhaps we ovelooked something? can you give this scenario again in m...
by roy
Tue Jul 26, 2005 3:33 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: job promoted to test from dev via VC gives NLS warnings
Replies: 2
Views: 817

Update

Hi,
At this point it seems to be some issue with VC & NLS.
Trying to figure it out with support.
I'll post new info as it comes.

While when performing import/export it works fine.
by roy
Sun Jul 24, 2005 7:11 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Return code 141 from 'dsjob -jobstatus'
Replies: 8
Views: 2432

Hi Craig, AFAIK, you must wrap the dsjob command with a script in order for ctrlM to get the status. So perhaps something went wrong in the script for some reason and the 141 code your getting is not even DS related? I'm currently using a customized version of Ken's script for running jobs via comma...
by roy
Sun Jul 24, 2005 3:16 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Is there any max restriction for file size?
Replies: 9
Views: 4844

Hi,
What Unix are you using?
Usually there are file systems that can be defined to hold large files (over the 2GB limit).
So if you can do that I think your better off.

IHTH,
by roy
Thu Jul 21, 2005 4:25 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Spaces between Column names
Replies: 7
Views: 2421

Hi, Other options include building views with proper column names hence bypassing the issue. Another option would be to change hte table definition and use the original column names with aliases (i.e. column name = column_name , and the derivation would be column name column_name ) just pick the bes...