MVSFORUMS.com

[Bee_bop]

Hi Gurus,

Would like to consult error we're encountering using CLIST in accessing a certain member in a PDS. For other members in the PDS it was able to read except for 1 specific PDS member.

This is the line from our CLIST :

OPEN PDS_MEMBER INPUT SYSTEM
IF NOT $OPEN(PDS_MEMBER) THEN DO
.... we put the WTO error message here ...
End

The member is existing but it doesn't return any useful messages for us to know the cause why the member wasn't process. I tested in Test environment it was able to process it even my ID is in EDIT mode for the dataset member. Just wondering if it has something to do with the SETTINGS of the MEMBER but when I issue PROF command in TSO it has the same values on those that are currently processed.

Hope you could help me on this.

Thanks in advance.
-Bee_bop

[Bill Dennis]

Are there any return codes you can display to help diagnose the error?

Are you trying to OPEN multiple members at the same time?
_________________
Regards,
Bill Dennis

Disclaimer: My comments on this foorum are my own and do not represent the opinions or suggestions of any other person or business entity.

[Bee_bop]

Hi Bill Dennis,

I tried executing the script accessing the same PDS with different members it still worked. If the PDS is not opened successfully, no error message is displayed. Only the WTO that we sent which is incorrect, because the default is if the file wasn't opened we assume that the member is not existing.

For this case, the member name exist on the PDS.

Thanks,
-Bee_bop

[Bee_bop]

I just noticed when I got the AFOPER log, it shows " . " when I access the AF/OPER log on BROWSE mode. For EDIT and VIEW mode it doesn't show the log. Application program is sending the message to us, this is what they send in SYSLOG, and the value on AFOPER LOG :

BROWSE :

+AFXXX ABCDEF.

EDIT/VIEW :

+AFXXX ABCDEF


I think their program didn't initialized before sending message.