DSXchange

Anyone gonna ask for the 'why' behind the question?

i have 2 instances of the same job but i m unable to run them simultaniously. I'm lost... why the heck not? That's the whole point of these kind of jobs - so you can run the same job multiple times at the same time. Highlight the main job in the Director, click 'Run', supply a unique Invocation ID ...

Are you passing in a full pathname to the routine? What was wrong with using 'test' - as noted, you need to check the exit status of the command, not the output of it as it doesn't have any. Are you sure it will be empty empty? If the file includes a first row of headers it will never be zero bytes.

That tr must come with MKS because it ain't no DOS command.

Sorry, just took it as a complaint that your problem wasn't getting solved fast enough. Been a long day.

Hope you figure it out... or someone running a Windows server throws us all a bone.

Name is hshCustomer and also i forgot to mention..the job name is also hshCustomer..Do you think thats throwing error...

Ans.No, that would not be a problem.

I have spent an amount of time on this problem and would like to be able to solve it so I can move on. Do you think you are the only one? Food for thought: C:\DOCUME~1\Craig>type fred.txt -param FRED=fred -param BOB=bob C:\DOCUME~1\Craig>echo fred.txt fred.txt C:\DOCUME~1\Craig>echo 'type fred.txt'...

How about sharing with us the actual File name you've been using in the hashed file stage? I'm wondering if there's something... funky... about it. Also, when you changed the stage to 'Use account Name' instead of a directory path - did you put something in the Account Name field? If so, what? If yo...

What exactly is in your file? You've never said and people are just assuming they know what's there. If you don't have that correct then no amount of proper echo'ing or type'ing is going to get you proper command line syntax.

Nothing, just clarifying how to trigger the default value on a required field. If the incoming timestamp is high 9s, i cannot pass 9999-12-31 23:59:59.999999 as that is the default value and the database will not accept that. What makes you say this? Why would the database care? (hint: it won't)

You're right in that you can't send NULL to a required field. However, you can trigger the default value in the required field by not including the field in your DML.

Perhaps two different links are in order?

As previously noted, after the job aborts you need to Reset the job (note, not recompile but reset). Look to see if the reset brings new information into the job's log labelled as 'From previous run...'.

Let us know if they show up and if they do double-click on them and paste the details here.

Ken Bland posted these routines back in 2003 to do ranged lookups in hashed files. Only 'problem' is they are considered Premium Content now, but I'm sure you could contact Ken directly as all of his stuff is 'open source' I do believe.

Cute. Nothing like a little revisionist history.

Yah, noticed that after I posted here. However, I didn't notice the '4' in the output... and what the OP is looking for is specifically a 'range lookup' rather than a 'non-equaljoint' one. Ken Bland posted a way to do this in hashed files which I've leveraged in the past. Not for the faint of heart,...