VSAM initialization Error: VSAMFILE is Null

luban · Posted: Wed Apr 04, 2007 8:35 pm

Hi,

I encounter a problem of VSAM.
Here's one job,
STEP1: DEL/DEFINE a new VSAMFILE
STEP2: Use this VSAMFILE as input to run a PGM
Because this VSAMFILE is Null, the opening in PGM is error.
But after viewing this file by STARTOOL, this error can be solved.

Is there any way can solve this problem without initializing this VSAMFILE by HIGH-VALUE or LOW-VALUE, for it's impossible to open this file manually during the running of the job.

Thanks & Best regards,
Ban

William Thompson · Posted: Wed Apr 04, 2007 10:25 pm

What error do you get, exactly?

luban · Posted: Thu Apr 05, 2007 7:21 pm

Hi William,

My error is open new VSAMFILE as input file failed.
After manually open this file, this job can run successfully.
Is there anyother way can solve this problem without open vsam manually first ?

Thanks & Best regards,
Ban

expat · Posted: Thu Apr 05, 2007 7:25 pm

I really don't know why so many people are against initialising a KSDS at creation time.

Just a simple job to load a low and high value records would stop all of these problems. It was the way it used to be done when I were a lad.

superk · Posted: Thu Apr 05, 2007 7:26 pm

I agree. Isn't that a normal SOP?

luban · Posted: Thu Apr 05, 2007 7:46 pm

Hi expat,

hehe, I am not against initialising a KSDS, actually it's the business request " P

Best regards,
Ban