IBM Mainframe Forum

HI,
We have a variable length VSAM file (12000 120004) that I have defined as follows:


etc (more detail fields follow)

Read is coded:


*****************************************************************************************
What am I missing? I thought this would work??

Thank you for your help,

Steve

Code'd and Aligned

Hello and welcome to the forum,

Which line raised the error?

In the JES sysouts is there any other info?

We have many Easytrieve processes that do this - almost exactly the same way. Ours are:
READ ORDMSTR KEY(ORDMSTR-KEY) STATUS

Is there a DD statement for this file?

These users thanked the author dick scherrer for the post:

SteveM001 (Fri Aug 24, 2012 3:23 pm)

We need to know which line the message points to.

I'd code



rather than what you have, but that is not the problem.

At a blind guess, I'd say you have accidently defined PARM-ALPHA PARM-REFNO as part of the VSAM file, but I prefer not to guess blindly.

Hello Dick,

The brackets/parenthesis are optional there - I like to use them as well, but not the problem.

These users thanked the author BillyBoyo for the post:

SteveM001 (Fri Aug 24, 2012 3:23 pm)

Gentlemen, thanks to your responses I fixed it. Problem had to do with the lookup key on the VSAM file being in the File Section. Once I used Working Storage to load a key and used the key for the reads it seemed golden. I had thought my syntax was hokey; but thanks to your affirmations, I was able to look elsewhere.

In answer to the question of what line was the error pointing to.. it was the loading of the keys just before the read. I was passing the parmfile values to the keyfield and then doing my read. As I said, once I built a working storage key structure and loaded to it, instead, the read (which now pointed to the WS-key) worked fine.

Thank you again for your help.

STeve

You're welcome - thank you for the follow up

d

These users thanked the author dick scherrer for the post:

SteveM001 (Fri Aug 24, 2012 3:22 pm)