On Thu, 19 Apr 2012 09:16:51 -0400, Shmuel Metz (Seymour J.) <[email protected]> wrote:
>In <[email protected]>, on 04/18/2012 > at 08:36 AM, Kurt Quackenbush <[email protected]> said: > >>http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/gimusr51/3.6.3?SHELF=gim2bk90&DT=20110811181158 > >The only explanation given for "installation-wide" is "SMP/E uses this >table data set to save process status information for the SYSMOD >management dialogs." What problems occur[1] if you don't use a shared >SMPTABL? I've run into problems when it's shared. > >[1] Assuming that the unshared SMPTABL is in the > ISPTLIB concatenation. > No problems really, just none of the benefits of sharing it. IOW, if someone starts an install from the sysmod mgmt dialogs and doesn't finish it, another person can't pick up from where they left off. What problems have you run into when sharing? BTW, even when I have been at shops that have a shared SMPTABL allocated via logon clist or logon proc, I usually free it and use my own "CNTL" library instead and concatenate that into a ISPTLIB LIBDEF in my CLIST I use that invokes the SMP/E dialogs. I think I started doing that because different shops did it different ways or just had too much "junk" in their SMPTABL lib that was never cleaned up. It really doesn't matter for me these days because I haven't done an interactive sysmod install in probably 15 years. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
