Too far gone for that.
attach 5a3 newesa4 5a3
HCPATC045E NEWESA4 not logged on
MAINT ZVMV5R10 12/19/05(00045); T=0.01/0.01 12:48:39
ind user newesa4
USERID=NEWESA4 MACH=ESA STOR=1 VIRT=V XSTORE=NONE
IPLSYS=DEV 0121 DEVNUM=00000
PAGES: RES=00000000 WS=00000001 LOCK=00000000 RESVD=00000000
NPREF=00000000 PREF=00000000 READS=00000010 WRITES=00000042
CPU 00: CTIME=02:43 VTIME=000:07 TTIME=000:10 IO=042367
RDR=000059 PRT=001079 PCH=000000
MAINT ZVMV5R10 12/19/05; T=0.01/0.01 12:49:19
And now with "track":
TRACK 1 USER : NEWESA4 **** VMD **** z64 V4.2 12:50:06 12/19/05
================================================================================
VMDBK @ 0C14A000 Class = BCDEFG Share= 50 R
Logon= 12/19/05 10:05 Virtcpu = 000:06.65 Totcpu = 000:09.63 0 Devices
Storage= -107373M Account = 161 Console= DISC
Last CP= MSGNOH Locked= 0 Resident= 0 WSS= 1
PSW= 00000000 00000000 CC = 0 Stat = EC DISABLED RUN SUPR
CPUaddr= 00 #CPUs= 01 Mach= ESA Amode= 31-bit 370accom= OFF
Sio= 42367 Pr= 1079 Pun= 0 Read = 59 Dist = DOSESA4
Rstat= CFWAIT Slist: 37 - Dispatch List
Qstat= IABIAS
Ostat= TO-LOGOFF FORCE-LOG DISC AUTO-DISC XAUTOLOG
Com = *ðíµ ©ü Exec = Mod = Tran=
Ipl = IPL 121 LOADPARM ...P
R0-7= 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
R8-F= 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
*** NO RETRIEVE BUFFER ***
================================================================================
CR=Upd CLEAR=Subset ==>
2=Auto 3=Quit 4=Prt 5=File 1=RST 9=VMD 10=VST 11=DEV 12=DBK 7=Prev 8=Next
Note that there is no storage allocated. So it seems to me that CP is the
problem.
Time to call the support center.
Tom Duerbusch
THD Consulting
>>> [EMAIL PROTECTED] 12/19/2005 12:45 PM >>>
Tom
Try attaching a tape drive at the address that was in error, and mount and
ready a tape..
eric
At 12:20 PM 12/19/2005, you wrote:
>Hopefully this won't get to any point where I have to take drastic
>action....
>
>We have an old VSE machine (VSE/ESA 2.3.2), which somehow got hung
>this
>weekend. My best guess is that it hung when one of our tape drives
>broke, but I can't be sure it was using them.
>
>I have the "forced logoff pending" stuff.
>Yep, tried:
>
>force guest
>force guest logoff
>force guest logoff immediate
>force guest immediate
>
>Tried logging on.
>There are no tape drives currently attached to the system, but someone
>may have detached them earlier.
>
>My plan was to wait an hour and see if it clears up. Well, times up.
>
>There was a method, in the old days, that you modified some bits in
>some control block and you can free up the user. Does anyone have
>that
>procedure, updated for z/VM 5.1 (RSU 501)?
>
>Any other advice would also be welcome.
>
>Tom Duerbusch
>THD Consulting
Eric Schadow
Mainframe Technical Support
www.davisvision.com
------------------------------------------------------------------------
The information contained in this communication is intended
only for the use of the recipient(s) named above. It may
contain information that is privileged or confidential, and
may be protected by State and/or Federal Regulations. If
the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,
distribution, or copying of this communication, or any of
its contents, is strictly prohibited. If you have received
this communication in error, please return it to the sender
immediately and delete the original message and any copy
of it from your computer system. If you have any questions
concerning this message, please contact the sender.
------------------------------------------------------------------------
