RE: SBS not ending

Try ending the jobs running within the subsystem. ENDMQM I believe is the
right command

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces+nelsonp=speakeasy.net@xxxxxxxxxxxx
[mailto:midrange-l-bounces+nelsonp=speakeasy.net@xxxxxxxxxxxx] On Behalf Of
Michael Ryan
Sent: Saturday, October 06, 2007 12:57 PM
To: Midrange Systems Technical Discussion
Subject: Re: SBS not ending

Did you so an ENDMQM prior to ending the subsystem? Are there active
jobs in the subsystem. I do this by first ending any communication
processing jobs that are talking to/from any queues, end any
listeners, then end the channels. You should be able to bring down
QMQM then.

On 10/6/07, James.Hawkins@xxxxxxxxxx <James.Hawkins@xxxxxxxxxx> wrote:

We have a subsystem (qmqm) that was issued an end *immed command at 8:45
this morning (via a scheduled job), at 1:15 the subsystem and associated
job are in a status of ending. Unfortunately this was configured by my
predecessor so I haven't looked into the how/why of the configuration. It
is set up with minimal job logging.

Why would this job and subsystem not end?

How can I get the subsystem and job to end? (ENDSBS *IMMED or *CNTRLD
and ENJOB *IMMED or *CNTRLD have been unsuccessful)


Any thoughts out there? (or is everyone doing what I wish I were doing
and watching college football? lol)

Thanks in Advance
- Jim
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.