Um, *occasionally* something run earlier during the same logon sessions 
may have left her PF keys set differently?

What kind of dump is it that prints?  CMS doesn't usually produce dumps 
through virtual printers, instead producing VMDUMPs.  Could something be 
issuing the CP DUMP command (or a PFkey got set to it somehow)?

What does the dump show?  Is there an ABEND message of any kind?  What 
does the PSW point to in the dump?  What's in storage where the PSW 
points?  Usually register 10 or 11 is a set as a base register; what's in 
that area of the dump pointed to by R10 and R11?  What's in storage where 
R1 points?
 
Maybe you want to SPOOL her console START to some other userid so that 
when she reports another dump you can look to see what was going on 
*before* she had the problem?

Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.



"Mary Zervos" <[EMAIL PROTECTED]> 

Sent by: "VM/ESA and z/VM Discussions" <[email protected]>
11/09/2005 10:35 AM
Please respond to
"VM/ESA and z/VM Discussions" <[email protected]>



To
[email protected]
cc

Subject
CMS Dump in Xedit






A user called saying that for about 2 years, when she xedits a cms file, 
if she hits pf3 or clear, *occasionally* her account spits out a dump 
that fills half a box.  I've been poking around on her account looking 
at her mdisks, pf settings, account settings, etc.  I xedited a file on 
her account and all her settings looks fine.  Does anyone have any idea 
what would cause a dump to occur in xedit so randomly?

Thanks,

Mary Zervos
Systems Programmer
Binghamton University
607-777-6158




 
The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited.

Reply via email to