Right, of course. But the point is that that magic could just as easily be contained in the "body" of any file, as it is in a UNIX file, even if that file were a PDS member (or, for that matter, a non-PDS QSAM/BSAM dataset).
Okay, the next pointless experiment I am too lazy to do: You could make a "wrapper" PROC that would give the illusion of executing a program object from a PDS by copying it to a UNIX file first. Hmmm, I guess you can only run UNIX files from the shell, not EXEC PGM=, so the experiment is really pointless. Is there an IBM utility that is smart enough to make a UNIX executable into a program object in a PDSE? If so, then you could do it: //STEP1 EXEC OBJEXEC,EXECPGM=MYPROG //STEPLIB DD MY.BASIC.PDS,DISP=SHR Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ed Gould Sent: Saturday, October 12, 2013 10:08 AM To: [email protected] Subject: Re: PDS/E, Shared Dasd, and COBOL V5 Paul, While I am NOT a fan of PDSE's, I believe that there are entries in the PDSE "directory" (ie entries GT 9 bytes) that cannot be contained in a normal PDS directory. Or there are items that cannot be contained in a PDS directory. Such items as an entry point in c++ (or any other program) might be entry_for_my_pgm_named_gil (or some such name). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
