Well, an easy way to determine if another LISTDSI is hiding in the bushes, so to speak, is to do an "M LISTDSI", member scan, in the LISTDD function. Do not forget to turn on scanning LPA and LINKLST.
-----Original Message----- From: IBM Mainframe Discussion List [ <mailto:[EMAIL PROTECTED]> mailto:[EMAIL PROTECTED] On Behalf Of Steve Comstock Sent: Thursday, April 12, 2007 11:31 AM To: [EMAIL PROTECTED] Subject: Re: Rexx LISTDSI problem on z/OS 1.7 Nasuh KARAHALLI wrote: > Hello dear listers, > > Once I installed z/OS 1.7 I discovered something that seems to be running > improperly. > > /* REXX */ > TRACE R > DSN = '''IBMUSER.JCLLIB''' > C = LISTDSI(DSN) > SAY C > SAY SYSREASON > SAY 'THE DATASET ' DSN ' IS CREATED ON ' SYSCREATE > EXIT > > > In TSO environment, above code runs on z/OS 1.4 correctly but when I > execute it on z/OS 1.7 system my user abends with the following error : > > IEA995I SYMPTOM DUMP OUTPUT > SYSTEM COMPLETION CODE=0C1 REASON CODE=00000001 > TIME=17.18.14 SEQ=00215 CPU=0000 ASID=005D > PSW AT TIME OF ERROR 078D3000 80000002 ILC 2 INTC 01 > NO ACTIVE MODULE FOUND > NAME=UNKNOWN > DATA AT PSW 00000000 - 000A0000 000130E1 00000000 > GR 0: 00000000_00000010 1: 00000000_00069250 > 2: 00000000_000692E8 3: 00000000_0006928C > 4: 00000000_00000010 5: 00000000_00000010 > 6: 00000000_00000005 7: 00000000_00000010 > 8: 00000000_000692E8 9: 00000000_08DE8C90 > A: 00000000_000691F0 B: 00000000_88C8D2DA > C: 00000000_08C8E2D9 D: 00000000_000691F0 > E: 00000000_88C8E38C F: 00000004_80000000 > END OF SYMPTOM DUMP > IRX0250E System abend code 0C1, reason code 00000001. > IRX0253E Abend in external function LISTDSI. > IEA995I SYMPTOM DUMP OUTPUT > SYSTEM COMPLETION CODE=0C1 REASON CODE=00000001 > TIME=17.18.14 SEQ=00216 CPU=0000 ASID=005D > PSW AT TIME OF ERROR 078D3000 80000002 ILC 2 INTC 01 > NO ACTIVE MODULE FOUND > NAME=UNKNOWN > DATA AT PSW 00000000 - 000A0000 000130E1 00000000 > GR 0: 00000010 1: 00069250 > 2: 000692E8 3: 0006928C > 4: 00000010 5: 00000010 > 6: 00000005 7: 00000010 > 8: 000692E8 9: 08DE8C90 > A: 000691F0 B: 88C8D2DA > C: 08C8E2D9 D: 000691F0 > E: 88C8E38C F: 80000000 > END OF SYMPTOM DUMP > 16 > > THE DATASET 'IBMUSER.JCLLIB' IS CREATED ON > > > Actually I discovered this problem while I'm investigating our OMVS OEDIT > problem. When I type, for instance, OEDIT xxxx in OMVS Unix Shell, I get : > > $1¨ + Done(137) oedit zzz > 50331671 Killed /bin/oedit > Ö > > in OMVS Shell and 0C1 abend in syslog. Then I recognized that OEDIT is a rexx > code and the story goes on so forth.. > > So far I couldn't find any valuable clue. Anyone out there experienced such a > issue ? > > Many thanks for your assistance. > > Nasuh Karahalli Well, I just ran it on z/OS 1.7 and it worked fine. No ideas. Sorry. Looks like you're finding a LISDSI different than the one REXX normally uses; maybe someone has added a new module with that name that gets found before the expected one. Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-393-8716 <http://www.trainersfriend.com> http://www.trainersfriend.com <http://xpostmail.com/98fbd0eedbfbe4b73f6006215fb11b47worker.jpg> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
