|
I had an ex-mainframe developer ask me today if the 400 has an equivalent of the DUMMY parameter. My only thought was to use QTEMP, but that may not solve the problem. According to the developer, there was a JCL statement that read: //DDNAME1 DD DUMMY where DUMMY meant for the system to ignore writes to whatever was assigned to DUMMY. The need is to save DASD during testing without corrupting the original code. My suggestion of QTEMP may fall short, because (I suspect) a write to a QTEMP file, while destroyed at the end of the job/session, still uses the DASD while the job runs. The site I am at is a little short on DASD and knocking on the 90% threshhold. Is there a way to ignore all writes to a file via a CL command (probably some type of OVRDBF) ??? Dan Rasch - because if the human species concentrated on the really important things in life, there would be a shortage of fishing poles! +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.