Validating hash file

vinodhraj · Post by **vinodhraj** » Sat Dec 03, 2005 8:43 am

Hi DS Gurus,

I need a routine to validate a hash file.

Thanks

Vinod

kcbland · Post by **kcbland** » Sat Dec 03, 2005 9:10 am

What do you mean by validate? Check that it exists? It's populated? It's structurally correct?

chulett · Post by **chulett** » Sat Dec 03, 2005 9:24 am

And why do you "need" it?

ray.wurlod · Post by **ray.wurlod** » Sat Dec 03, 2005 9:18 pm

Code: Select all

FUNCTION ValidateHashFile(HashFile)
* Ignore input argument
Message = "There is no such thing as a hash file."
Message<-1> = "It's a HASHED file."
Call DSTransformError(Message, "ValidateHashFile")
Ans = @FALSE
RETURN(Ans)

(It has been brought to my attention that a hash file is a tool that can be used to re-shape a block of hash. This fact is not really within the scope of the present universe of discourse.)

kduke · Post by **kduke** » Sun Dec 04, 2005 7:39 am

chulett · Post by **chulett** » Sun Dec 04, 2005 9:15 am

In other words, we've got an answer now but have no idea what the original question was. :D

ArndW · Post by **ArndW** » Sun Dec 04, 2005 10:09 am

No problem with the question; just tell me what the budget is for solving it and I'll get an answer for you.

To the original question

I need a routine to validate a hash file.

The "hash" has been addressed, the "need" has been touched upon so I think I should ask if it's really a "routine" or if a function, transform or sequence might not be sufficient.

vinodhraj · Post by **vinodhraj** » Mon Dec 05, 2005 1:36 am

Thanks all,

I am doing migration 71. to 7.5.
I have 5 hash files collected by a link collector and populated into a seq file. When running on 7.5 it shows abnormal termination.

Then I had made a fix, by inserting seq files after hash files followed by link collector.

My question is why it is not working before...

Thanks

Vinod

ray.wurlod · Post by **ray.wurlod** » Mon Dec 05, 2005 2:07 am

You must provide the error messages and any "from previous run..." messages logged after resetting the job. Otherwise we have no diagnostic information on which to base any judgment.

vinodhraj · Post by **vinodhraj** » Mon Dec 05, 2005 8:28 am

Hi ray,

This is the warning I got, no information about the hash file and only just abnormal termination of job name alone give in the log.

"Abnormal termination of stage LOADIPXIPStagingRecon.SCI_D_UK_ORG_MAP_18264.LC_IPXIP_Recon detected"

Thanks

vinod

ray.wurlod · Post by **ray.wurlod** » Mon Dec 05, 2005 1:25 pm

After the job aborts, you must RESET the job in Director. Tell us of any "from previous run..." message that appears in the job log.