On Thu, 21 Dec 2006 15:07:21 -0800, Edward Jaffe <[EMAIL PROTECTED]> wrote:
>If you collect SMF Type 19 records, beware that an >SMF-initialization-time LSPACE request is issued for every volume >connected to the system. If SYSVTOC.volid is held by another system for >any significant period of time, an IPLing system will appear to be >"stuck". This happened to us and we had to wait over half an hour for a >full-volume dump (occurring on another system) of a 60K cylinder DASD to >finish before SMF would initialize and the IPL could continue. The >contention looked like this: > >ISG343I 08.05.18 GRS STATUS FRAME LAST F E SYS=MVS70 >S=SYSTEMS SYSVTOC TIVSM4 >SYSNAME JOBNAME ASID TCBADDR EXC/SHR STATUS >MVS70 DFHSM70 0026 00BA2E88 EXCLUSIVE OWN >MVS60 SMF 0018 00BFD0C0 EXCLUSIVE WAIT > >IBM's suggestion for a fix/workaround/solution? Don't collect SMF Type >19 records. :-( > I wonder what happens if your SMFPRMxx used at IPL time excludes type 19 records, then after everything is up you issue SETSMF (or SET SMF) to include type 19 records. Yeah, I know, it's kind of a kluge, but I wonder how the system behaves. -- Tom Marchant ---------------------------------------------------------------------- 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
