Simple Question about an *ERROR-NR Value => Why 24?

, ,
1

Hello

Natural environment: Nat 9.2.1 z/OS 3.1

I’m puzzled about a specific *ERROR-NR value. Maybe someone can explain “why”.

When I run a batchprogramm which tries to open a PDS-Member which doesnot exists, I get *ERROR-NR 1500. I expect this value, all fine.

Now the “magic”:

I use as Input the concatination of DD * and a PDS-Member (the PDS is defined with LRECL=133).

//CMWKF01 DD *,SYMBOLS=EXECSYS
“some data”
// DD DISP=SHR,DSN=“non existing pds member”

When I try to access this “non existing pds member”, I get *ERROR-NR 24.

Can someone explain me, why I get 24?

Thx Christian

2

Hi Christian,
Well, I tried to reproduce your problem in a very similar environment: Z/OS 2.4, Nat 9.2.2.2.
However, in my case the result was a bit different:
From Natural:
Open for WORK file 1 failed S013.

which perfectly make sense (OPEN = SVC 13), and the message also confirmed that:

From OS:
IEC141I 013-18,IGG0191B,DRP588D1,NATBDEV,CMWKF01,BB28,DEV014,

My program also tried to read a non-existing PDS member.

Regards,
knv09

3

Hello Nikolay
Thx for your test.
Maybe the difference between your and my results is based on different natural installion on your and my side.
Nevertheless: I can live with my ERROR-NR values.
My naive guess why I get ERROR-NR 24 was:
Input from JCL => LREC = 80
Input from a PDS-Member which doesn’t exists, but the PDS was created with LRECL=133
If these are concatinated, then a non existing PDS-Member will cause ERROR-NR 24.

Whatever, we can stop further investigations on this topics.

Best regards Christian

4

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.