DSXchange

Both return an SQL date type value.

Please post in the correct forum, this is not certainly not a FAQ. All solutions involve sorting the data by both columns first. You can also add a column that contains information on group changes so you can detect a new key. I would use a simple transform stage, using a stage variable to store the...

balajisr wrote:Arnd, The jobs you sent ran fine at my end.

Thanks for testing that!

Is anyone else here on HP-UX with PX and would be willing to run my test case to see if it might be a local configuration issue and not restricted to the platform?

Kumar, is 1 row and <100 bytes total size in the test case small enough? When I use just one Lookup FileSet the size is about 400Mb and that is working like a charm. I've just took a look at the environment variables to see if there is some setting there that might affect the behaviour on this platf...

There is no way to set the initial value to anything other than 1 using the default routine. But you can create your own copy of the Manager/Routines/sdk/KeyMgt/KeyMgtGetNextValue routine and modify it appropriately to start your sequence at some other number.

That is great news - it means it isn't a general limitation but perhaps a problem with this version (7.5.1A) or on this platform (HP-UX). It would be nice if you or someone else could confirm this. I have a .dsx export file that I made for support that I could send to anyone who would like to test t...

Thanks, balajisr - it would be great if you have found a way around this. Please note that I am talking about a lookup FileSet , I have used the same DataSet multiple times in a job before with no problems. I thought maybe the access to the descriptor might be the problem, so I tried copying the .fs...

It seems that a given Lookup FileSet can only be used once in a job. When I add second copy of the same Lookup FileSet to a job it will always abort with a message Lookup2,0: Could not map table file "/path/to/file/lookuptable.20070712.mlbo12d": Not enough space This occurs even when I use a test lo...

Are you doing any repartitioning? Does the job monitor show 800 rows output or have you actually checked the data to see if it is wrong. I've noticed some discrepancies in the monitor row counts when using several nodes, sometimes it showed total row counts per node.

Is this a Job Sequence ? If so, in the Job Activity stage for that parameter click on "set to default".

Well, that means that the parent job is passing a blank (or empty) value to the job and that is overriding the default. How is that parent job getting its value for that parameter?

How are you calling the job where the default is being overridden? Are you specifiying that parameter when calling the job?

A job will always use it's default parameters unless they are explicitly set at runtime. So in your case it means that the parent job is overriding the defaults, i.e. explicitly setting a value via either the shell "dsjob -run" or a sequencer job activity or by issuing a DSSetParameter() call prior ...

Numbers cannot be stored justified. If you want a string to be stored "right justified" then you need to explicitly pad the string with spaces on the left. Note that some datatypes such as VarChar2 will strip those leading spaces out of the string! Justification is never a data value issue, just a d...

It would seem your problem is that your BASIC routine is causing an abort somewhere between your first and second log message. What sort of code do you have between these two lines, anything more than simple assign, condition and loop statements - particularly CALLs to function and other routines? T...