Doing "anything" thousands of times is very likely NOT a good idea. Sounds like a serious problem with MFE 7.0 to me.
I don't know the history of DEALLOC. From SMP/E on z/OS 1.11: Entry Type: PROC Zone Name: MVST100 Entry Name: DEALLOC Zone Type: TARGET LASTUPD: HBB7760 TYPE=ADD FMID HBB7760 RMID HBB7760 DISTLIB APROCLIB SYSLIB PROCLIB Clearly IBM ships this proc to every customer, but I was able to find no documentation in the current manuals describing what this proc is for. Further, I suspect that enhancements to z/OS Allocation in the area of Vary Device processing over the last few z/OS releases have rendered this proc obsolete. Maybe someone from IBM, or perhaps someone on this list more familiar with the oddities of OS/360, could chime in to explain what DEALLOC is/was intended to accomplish. Brian On Mon, 26 Jul 2010 07:51:53 -0400, Lizette Koehler wrote: >I have a concern of the way the EMC Software - Timefinder Snap - under >Mainframe Enabler Software 7.0 works. > >EMC decided that when the SNAP function occurs on a volume, they would issue >the S DEALLOC proc (Yes IEFBR14) to get IOS to vary the volume offline >sooner. I am not sure if that is a good thing. It is issued for each vary >offline command they create. > >If I have 10 volumes and each one gets an IEFBR14 - maybe not so bad > >But if I had 1000's of volumes I am snapping, I am not sure. Each one takes >up a stc num and clutters up my spool for one thing. > >So I thought I would ask, is this the best way to get vary offline to hurry >up? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html