I suspect this is a problem (phenomenon? -- some think it's a feature) that has been discussed here at some length in the past few weeks. DFSMS is creating the dataset in the same location as before, and the same data is still there. Don't know enough about ISPF edit internals to know why it (alone) does not read the data. Perhaps other programs have a default RECFM, but ISPF edit will not read a dataset for which the DSCB does not already have a RECFM (shows it as empty).
For SMS-managed datasets, this phenomenon goes away as SMS writes an EOF on the first track on the new dataset. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Paul Jodlowski Sent: Tuesday, February 13, 2007 7:28 PM To: IBM-MAIN@BAMA.UA.EDU Subject: ps dataset I have a wierd problem, a programmer runs a job that creates a dsn (tst.report) then he ftp's it down to a server and then uncat/deletes it. Later on he runs the job again expecting the dsn (tst.report) to be empty. AND IT SHOULD BE. Well it's not in fact it has the same data as the first run. I go to 3.4 screen an try to browse the dataset but it says it is empty. I even ran a IEBGENER and i showed the data???? (of cource we DID NOT run the uncat/delete step) This is all done on the same volume (userb4) and it is NOT sms-managed. In fact We don't HAVE any SMS-managed data sets. We are running of z/os v1r7. ---------------------------------------------------------------------- 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
