For example, VERBX VSMDATA traverses data structures which are not serialized while they are being captured by IEATDUMP/SYSMDUMP/SDUMP. As a result, sometimes the VSMDATA processing encounters problems due to inconsistent data structures in the dump. The potential for inconsistencies can be exacerbated when some register at time of error or SUMLST range causes some of the relevant VSM stuff data to be captured early during disabled or suspend summary dump, and the rest captured later. So when you see VSMDATA spewing error messages, sometimes you say, "Let me try dropping the dump and reinitializing it, replying N to BLS18160D, and then see if VSMDATA works better for this dump".
Replying N to BLS18160D is something I do only rarely, but there are times when, in order to understand what is going on in a dump, you need to know a considerable amount about how dumping works. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "IBM Mainframe Discussion List" <[email protected]> wrote on 02/27/2021 09:03:17 PM: > From: "Ed Jaffe" <[email protected]> > To: [email protected] > Date: 03/01/2021 05:04 PM > Subject: BLS18160D Response > Sent by: "IBM Mainframe Discussion List" <[email protected]> > > Regarding: > > "BLS18160D May summary dump data be used by dump access? Enter Y to > use, N to bypass." > > Under what conditions would it ever be appropriate to reply N? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
