I tried it and obtained an: IGYCB7149-S An error opening "&1" was detected in "CDA" phase at &2.
So it must be a ptf level issue. Curiously, the mdeck is on the spool! El jue, 11 sept 2025, 16:05, Phil Smith III <[email protected]> escribió: > Yes, I know that. Sorry, not sure what your point is? The real question is > whether this should be considered a compiler bug or not. I don't think I > should be able to cause an "internal error" like that. > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf > Of Sri Hari Kolusu > Sent: Thursday, September 11, 2025 9:32 AM > To: [email protected] > Subject: Re: Would you consider this a compiler bug? > > > Changing that to > //SYSMDECK DD UNIT=SYSDA,SPACE=(CYL,(1,1)) made it happy. > > Phil, > > The SYSMDECK dataset need to a permanent MVS dataset which is documented > here > > > https://www.ibm.com/docs/en/cobol-zos/6.5.0?topic=output-defining-library-processing-file-sysmdeck > > As peter mentioned " You should look at the delivered sample PROC's in > <hlq>.SIGYPROC to help you configure your local compile procedure. You > would have seen the correct SYSMDECK DD specification there." > > You would have found the supplied procedures have the following > > //SYSMDECK DD UNIT=SYSALLDA,SPACE=(CYL,(1,1)),VOL=(,,,1) > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
