Jack,
Thanks for that. I have been able to stop the second (good) MONITOR job
with the STOP command but unfortunately all attempts to stop the rouge
job have failed (ie STOP and a simple abortjob).
Simon
-----Original Message-----
From: Jack Connor [mailto:[log in to unmask]]
Sent: Monday, 29 November 2010 11:24 AM
To: Buckingham, Simon; [log in to unmask]
Subject: RE: MM3000 problem
The MONITOR for MM3000 uses a command message file for commands.
I would assume that the second version has the control file hung up.
You may try bring down both of the monitor jobs with the STOP job...for
the Maintenance version of MM it's MNTSTOP.JOBS...I can't remember what
it is for MM3000 proper.
From the stack markers, it looks like it's trying to process a log on
for a user. I suspect there is interaction between the two mon jobs.
It shouldn't take long to stream the stop job and get the terminals
freed up.
jack
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Buckingham, Simon
Sent: Sunday, November 28, 2010 7:03 PM
To: [log in to unmask]
Subject: [HP3000-L] FW: MM3000 problem
Below is further correspondence on the topic. If anyone else has any
ideas they would be gratefully received if it means I can avoid a
re-boot.
Regards
Simon
-----Original Message-----
From: Craig Lalley [mailto:[log in to unmask]]
Sent: Monday, 29 November 2010 10:45 AM
To: Buckingham, Simon
Subject: RE: MM3000
Simon,
I would post this to the list. I don't want to be responsible for
crashing your system ;-)
You could set a break point, but clearly it is waiting for a port
(probably network port). I assume it is a listener of some sort.
You could break the process, but then that may crash the system.
It looks like the dispatcher has it blocked, maybe you could jump queues
to give priority?
I would see if anyone else has any suggestions. I know Stan probably
knows a way to do it.
Good Luck,
-Craig
--- On Sun, 11/28/10, Buckingham, Simon <[log in to unmask]>
wrote:
> From: Buckingham, Simon <[log in to unmask]>
> Subject: RE: MM3000
> To: "Craig Lalley" <[log in to unmask]>
> Date: Sunday, November 28, 2010, 3:39 PM
> Craig,
>
> Option 2 couldn't find anything to abort.
>
> The results of option 1 are:
>
> $3 ($2a3) nmdebug > pin 276
> $4 ($276) nmdebug > tr,d,i
> PC=a.0018899c
> enable_int+$2c
> NM* 0) SP=4184a750 RP=a.0077856c
> notify_dispatcher.block_current_process+$338
> NM 1) SP=4184a750 RP=a.0077a3ac
> notify_dispatcher+$268
> NM 2) SP=4184a6d0 RP=a.00241c54
> wait_for_active_port+$e8
> NM 3) SP=4184a5d0 RP=a.002428b8
> receive_from_port+$544
> NM 4) SP=4184a550 RP=a.007499c8
> ipc_awake_process+$5bc
> NM 5) SP=4184a350 RP=a.003143c4 ACTIVATE+$c78
> NM 6) SP=4184a0d0 RP=a.00313738 ?ACTIVATE+$8
> export stub:
> a.013b6f4c arg_regs+$28
> NM 7) SP=41849dd0 RP=a.013a4e40 nm_switch_code+$900
> NM 8) SP=41849ca0 RP=a.0132242c SWT_RETURN
> (switch marker frame)
> CM
> SYS % 226.404
> SWITCH'TO'NM'+%4 (MitroC
> CCG) SUSER1
> CM * 0) SYS % 226.404
> SWITCH'TO'NM'+%4
> (MitroC CCG) SUSER1
> CM 1) SYS %
> 164.152 ACTIVATE+%61
> (MitroC CCG) CMSWITCH
> CM 2) SYS %
> 157.31071 CXPREPRUN+%4635
> (Mitroc CCG) CISEG1
> CM 3) SYS %
> 161.1207 EXEC_CMD+%773
> (MitroC CCG) CISEG3
> CM 4) SYS %
> 161.161
> RECEIVE'CX'SWIT+%106 (MitroC CCG)
> CISEG3
> CM 5) switch marker
>
> (Mitroc CCG)
> NM 9) SP=41849960 RP=a.013a3b54 switch_to_cm+$7e8
> NM a) SP=41849770 RP=a.00d655b4 do_cx_switch+$d0
> NM b) SP=41849430 RP=a.00d654b0 ?do_cx_switch+$8
> export stub:
> a.0118bf14 try_exec_cmd+$f4
> NM c) SP=418491b0 RP=a.011890a8
> command_interpret+$318
> NM d) SP=41848d30 RP=a.01188d5c
> ?command_interpret+$8
> export stub:
> a.0118c954 xeqcommand+$b8
> NM e) SP=41848730 RP=a.00d81368 exec_usercmd+$2cc
> NM f) SP=418486b0 RP=a.00d81068 ?exec_usercmd+$8
> export stub:
> a.01189074 command_interpret+$2e4
> NM 10) SP=41847470 RP=a.01188d5c ?command_interpret+$8
> export stub:
> a.0118c954 xeqcommand+$b8
> NM 11) SP=41846e70 RP=a.00d81368 exec_usercmd+$2cc
> NM 12) SP=41846df0 RP=a.00d81068 ?exec_usercmd+$8
> export stub:
> a.01189074 command_interpret+$2e4
> NM 13) SP=41845bb0 RP=a.01188d5c ?command_interpret+$8
> export stub:
> a.0118c954 xeqcommand+$b8
> NM 14) SP=418455b0 RP=a.00d81368 exec_usercmd+$2cc
> NM 15) SP=41845530 RP=a.00d81068 ?exec_usercmd+$8
> export stub:
> 1b6.00006400 handle_logon_cmds+$ec
> NM 16) SP=418442f0 RP=1b6.00007418 PROGRAM+$23c
> NM 17) SP=41844230 RP=1b6.00000000
> (end of NM stack)
> $5 ($276) nmdebug >
>
> Simon
>
>
>
> -----Original Message-----
> From: Craig Lalley [mailto:[log in to unmask]]
>
> Sent: Monday, 29 November 2010 10:30 AM
> To: Buckingham, Simon
> Subject: RE: MM3000
>
> Simon,
>
> Since you know the pin #, there are two choices.
>
> 1) is probably you best hope of success, and also a really
> good chance of crashing the system... so...
>
> debug
>
> pin #(pin number) the # is required
> tr,d,i
>
>
> and post the results
>
> Option 2) ABORTPROC PIN#
>
> Of course if option 2 fails, then you are again looking at
> a reboot.
>
> -Craig
>
> Personally, I think you have a corrupt JMAT table, but if
> your goal is to just release the file, there could be a
> chance.
>
> --- On Sun, 11/28/10, Buckingham, Simon
<[log in to unmask]>
> wrote:
>
> > From: Buckingham, Simon <[log in to unmask]>
> > Subject: RE: MM3000
> > To: "Craig Lalley" <[log in to unmask]>
> > Date: Sunday, November 28, 2010, 3:24 PM
> >
> > Craig,
> >
> > The showproc command produced the message:
> >
> > No processes matched any specification. (CIERR 11504)
> >
> > However, I do know that the rogue job has a pin#
> associated
> > with it as it has hold of a file in the MMSWORK
> group.
> >
> > Is there anything I can try to abort this pin#? (my
> use is
> > a little rusty)
> >
> > Regards
> >
> > Simon
> >
> > -----Original Message-----
> > From: Craig Lalley [mailto:[log in to unmask]]
> >
> > Sent: Monday, 29 November 2010 10:18 AM
> > To: [log in to unmask];
> > Buckingham, Simon
> > Subject: Re: MM3000
> >
> > Simon,
> >
> > If you do a
> >
> > SHOWPROC JOB=#J###;TREE
> >
> > and see pin numbers, you may have a chance of getting
> rid
> > of the job.
> >
> > If the response is along the lines of "no such
> pins/job",
> > they you have a "ghost" job and the only option is a
> > reboot.
> >
> > Sorry,
> >
> > -Craig
> >
> >
> > --- On Sun, 11/28/10, Buckingham, Simon
<[log in to unmask]>
> > wrote:
> >
> > > From: Buckingham, Simon <[log in to unmask]>
> > > Subject: MM3000
> > > To: [log in to unmask]
> > > Date: Sunday, November 28, 2010, 3:14 PM
> > > We are still running MM3000 here and
> > > for those who remember the package
> > > I have 2 MONITOR jobs running where there should
> only
> > be
> > > one.
> > >
> > > I have tried aborting the 'rogue' job which has
> been
> > > running before the
> > > weekend but without success. The 'good' job is
> still
> > > providing MM3000
> > > processing for our users.
> > >
> > > Any ideas as to how to get rid of the 'rogue'
> version
> > > without re-booting
> > > my HP3000?
> > >
> > > Regards
> > >
> > > Simon Buckingham
> > >
> > > Gilbarco Australia
> > >
> > > Please be advised that this email may contain
> > confidential
> > > information. If you are not the intended
> recipient,
> > > please notify us
> > > by email by replying to the sender and delete
> this
> > > message. The
> > > sender disclaims that the content of this email
> > constitutes
> > > an offer
> > > to enter into, or the acceptance of, any
> agreement;
> > > provided that the
> > > foregoing does not invalidate the binding effect
> of
> > any
> > > digital or
> > > other electronic reproduction of a manual
> signature
> > that is
> > > included
> > > in any attachment.
> > >
> > > * To join/leave the list, search archives,
> change
> > list
> > > settings, *
> > > * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> > >
> >
> >
> > Please be advised that this email may contain
> confidential
> > information. If you are not the intended recipient,
> > please notify us
> > by email by replying to the sender and delete this
> > message. The
> > sender disclaims that the content of this email
> constitutes
> > an offer
> > to enter into, or the acceptance of, any agreement;
> > provided that the
> > foregoing does not invalidate the binding effect of
> any
> > digital or
> > other electronic reproduction of a manual signature
> that is
> > included
> > in any attachment.
> >
>
>
> Please be advised that this email may contain confidential
> information. If you are not the intended recipient,
> please notify us
> by email by replying to the sender and delete this
> message. The
> sender disclaims that the content of this email constitutes
> an offer
> to enter into, or the acceptance of, any agreement;
> provided that the
> foregoing does not invalidate the binding effect of any
> digital or
> other electronic reproduction of a manual signature that is
> included
> in any attachment.
>
Please be advised that this email may contain confidential
information. If you are not the intended recipient, please notify us
by email by replying to the sender and delete this message. The
sender disclaims that the content of this email constitutes an offer
to enter into, or the acceptance of, any agreement; provided that the
foregoing does not invalidate the binding effect of any digital or
other electronic reproduction of a manual signature that is included
in any attachment.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
Call us today about our Windows consulting for monthly support services,
plus configurations and migrations.
CONFIDENTIALITY NOTICE: This communication with its contents may contain
confidential information. It is solely for the use of the intended
recipient(s). Unauthorized interception, review, use or disclosure is
prohibited and may violate applicable laws including the Electronic
Communications Privacy Act. If you are not the intended recipient,
please contact the sender and destroy all copies of the communication.
Please be advised that this email may contain confidential
information. If you are not the intended recipient, please notify us
by email by replying to the sender and delete this message. The
sender disclaims that the content of this email constitutes an offer
to enter into, or the acceptance of, any agreement; provided that the
foregoing does not invalidate the binding effect of any digital or
other electronic reproduction of a manual signature that is included
in any attachment.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
