Re: GO SAVE Problem

It means that either you're signed on to another session or you have
another job running that has allocated your message queue. Apparently
this job or session is preventing a subsystem from ending. Do a
WRKACTJOB and see what job is still active. Alternative do a WRKOBJLCK
DDUNN *MSGQ and see what job has your message queue allocated.

--

"David Dunn" <dont@xxxxxxxxxx> schreef in bericht
news:42785e61$0$21894$9a6e19ea@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ok, it's late but here's an update on my problem :

I actually caught the exact wording of the error I'm getting sometimes
when
doing a go save (option 21)


========================================================================
============
JOB 236346/DDUNN/DSP01 started on 05/03/05 at 20:35:48 in subsystem
QCTL in
message queue DDUNN is allocated to another job. Not all subsystems
ended
(C G)

========================================================================
============

I have no idea what this is telling me.

Any thoughts ?

Thanks,

DLD




"Robert Comer" <bobcomer_removeme_@xxxxxxxxxxxxxx> wrote in message
news:d3jhlk$dfvs$1@xxxxxxxxxxxxxxxxxxxx
It's probably hard to find in the log, but when this happens, just
doing a
WRKACTJOB and pressing F14, then look for any jobs there that have a
Status of 'End', but hat don't go away.

--
Bob Comer


"unlimited.newshosting.com" <dont@xxxxxxxxxx> wrote in message
news:425d3c10$0$16461$9a6e19ea@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Yeah that sounds right, but how do you find out which one it is ?
Logged
somewhere ?

Thanks !


DLD


"Robert Comer" <bobcomer_removeme_@xxxxxxxxxxxxxx> wrote in message
news:d3jd18$ddue$1@xxxxxxxxxxxxxxxxxxxx
Some job you have on the system is not ending, you'll have to find
out
what it is...

--
Bob Comer


"unlimited.newshosting.com" <dont@xxxxxxxxxx> wrote in message
news:425d26e2$0$15897$4dd03c44@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
I start a GO SAVE nightly and just leave; the next morning when we
come
in the system is up and ready to go.

Sometimes, however (maybe once every 2 weeks) we are getting "NOT
ALL
SUBSYSTEMS ENDED" and the only way to clear this is to CANCEL,
then
restart the system.

Anybody know why it would only show this problem every now and
then ?
We recently upgraded to V5R3 from V5R2 and I'd never seen this
problem
before we did that.

Thanks !


DLD











.