Discussion:
oh my jes2 Resources.
Ron Hudson
2010-05-05 19:14:13 UTC
Permalink
Story of an inexperienced operator / programmer

I wrote a small program to try and find the range of the random number
generator and it was
acting strangely - supposedly the random number was never lower than 999.. ?

So in a fit of stupids I added a line to the program to print out the
number returned from the random number generator and a number
counting the number of calls to IRND i had made...

Submitted the job, then though "hmm this is lilely to generate a ton of dead
tree"

About that time the console started complaining of "job has exceeded line
limit by x"

oh not good.

so I try to purge/stop the jobe with: P jobnumber at console a (dev 011)

console says no job named jobnumber

so I try

p jobname (from job card)

console says no job named that either

$p? (no)
oh now the console is saying "spool space is 80% used" or something like
that

errh! try many other $P P c jobname c jobnumber nothing stops the job.

Ok try a normal shutdown.
No dice, the job is using the computer right now and you cant tell it
anything...
spool space is 99% used

hmm can't shutdown, can't stop the job. Spool space is completely filled
now.


Ok, here's the stupid... go to the blinky light panel and "remove power",
turn the thing off.

In a real shop I probably just got fired with extreme prejudice. That's not
only fired,
but probably fired out of a cannon!


Ipl again. seems normal until just after the r 00,clpa then it prints the
normal few lines
and is just sitting there - I guess it's finishing up it's thinking from
when it was so rudely
interrupted.

hope it gets done soon.

How *do* you stop a job that has gone off the rails?

p.s. Now all it's good for is saying

$HASP050 JES2 RESOURCE SHORTAGE. CODE = CMBS

which Google leads me to belive I am out of console message blocks
but nothing tells me what to do about it right now (increase the number
of message blocks?)

What I need is empty out the filled message blocks since I don't think
I have any message waiting. The consoles are both in Roll Delete
so there are no built up messages.

?

Ron
Gerhard Postpischil
2010-05-05 19:48:49 UTC
Permalink
Post by Ron Hudson
so I try to purge/stop the jobe with: P jobnumber at console a (dev 011)
To stop MVS from executing a job, you need to cancel it:
C jobname

to remove JES2 output for the job, you need $PJnnn

The error responses you are getting are misleading, because MVS
doesn't know about JES2 job numbers Jnnnn, and while JES2 knows
about job names, commands to use them don't exist in the tk
version of JES2 .
Post by Ron Hudson
Ipl again. seems normal until just after the r 00,clpa then it prints
the normal few lines
and is just sitting there - I guess it's finishing up it's thinking from
when it was so rudely
interrupted.
No. It's not starting any work because there is no spool space,
and won't be until you free up some:

$PJ1-9999 (not usually safe - deletes all your jobs)
$PT1-9999 (removes TSO session output)
$PS1-9999 (removes output for started jobs)
Post by Ron Hudson
How *do* you stop a job that has gone off the rails?
All of this information is covered in Volker's cookbook that
came with the turnkey. However, frequently you need a bad
experience and a reread before it starts making sense <G>


Gerhard Postpischil
Bradford, VT


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/turnkey-mvs/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/turnkey-mvs/join
(Yahoo! ID required)

<*> To change settings via email:
turnkey-mvs-digest-***@public.gmane.org
turnkey-mvs-fullfeatured-***@public.gmane.org

<*> To unsubscribe from this group, send an email to:
turnkey-mvs-unsubscribe-***@public.gmane.org

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
Ron Hudson
2010-05-05 20:05:54 UTC
Permalink
The commands below that purge various queues $PS1-9999 for example
all of them say "Not Executed"



On Wed, May 5, 2010 at 12:48 PM, Gerhard Postpischil
Post by Gerhard Postpischil
$PJ1-9999 (not usually safe - deletes all your jobs)
$PT1-9999 (removes TSO session output)
$PS1-9999 (removes output for started jobs)
Gerhard Postpischil
2010-05-05 20:22:48 UTC
Permalink
Post by Ron Hudson
The commands below that purge various queues $PS1-9999 for example
all of them say "Not Executed"
I'm not aware of any such response. All MVS messages have a
letter/number prefix, and the JES2 messages have a
$/letter/number prefix.

Did the IPL complete, i.e., did JES2 initialize. How far did the
IPL get? You mentioned a CMB shortage - does this message
persist, or did it clear up (the message and clearing up is
normal at IPL time).




Gerhard Postpischil
Bradford, VT
Ron Hudson
2010-05-05 20:46:13 UTC
Permalink
Post by Gerhard Postpischil
Post by Ron Hudson
The commands below that purge various queues $PS1-9999 for example
all of them say "Not Executed"
I'm not aware of any such response. All MVS messages have a
letter/number prefix, and the JES2 messages have a
$/letter/number prefix.
JES2 did not initialize, I think it was trying to start.
Post by Gerhard Postpischil
Did the IPL complete, i.e., did JES2 initialize. How far did the
IPL get? You mentioned a CMB shortage - does this message
The message persisted most of the morning - JES2 was the
only thing listed in the D a,l command that and some "Starting"
Post by Gerhard Postpischil
persist, or did it clear up (the message and clearing up is
normal at IPL time).
Gerhard Postpischil
Bradford, VT
I IPL'ed a second time and JES2 got into a more useful state where
it would accept the $Px1-9999 commands. I still have a

$HASP093 100% SPOOL UTILIZATION

And I think I need to restart JES2 with PARM='FORMAT,NOREQ' to resolve that.

(you may have mentioned something else earlier in this thread - I have to go
back and
look)

Ron.
Rick Fochtman
2010-05-05 21:32:38 UTC
Permalink
Try "$PJ1-9999 command before you format...........

Rick
-------------------------------------------------------
On Wed, May 5, 2010 at 1:22 PM, Gerhard Postpischil
Post by Ron Hudson
The commands below that purge various queues $PS1-9999 for example
all of them say "Not Executed"
I'm not aware of any such response. All MVS messages have a
letter/number prefix, and the JES2 messages have a
$/letter/number prefix.
JES2 did not initialize, I think it was trying to start.
Did the IPL complete, i.e., did JES2 initialize. How far did the
IPL get? You mentioned a CMB shortage - does this message
The message persisted most of the morning - JES2 was the
only thing listed in the D a,l command that and some "Starting"
persist, or did it clear up (the message and clearing up is
normal at IPL time).
Gerhard Postpischil
Bradford, VT
I IPL'ed a second time and JES2 got into a more useful state where
it would accept the $Px1-9999 commands. I still have a
$HASP093 100% SPOOL UTILIZATION
And I think I need to restart JES2 with PARM='FORMAT,NOREQ' to resolve that.
(you may have mentioned something else earlier in this thread - I have
to go back and
look)
Ron.
Ron Hudson
2010-05-05 21:37:47 UTC
Permalink
That command reminded me of the original job and said it was waiting to
purge it for some reason.

A number of IPLs finally cleared everything up.

Thanks.
Post by Rick Fochtman
Try "$PJ1-9999 command before you format...........
Rick
-------------------------------------------------------
Post by Gerhard Postpischil
Post by Ron Hudson
The commands below that purge various queues $PS1-9999 for example
all of them say "Not Executed"
I'm not aware of any such response. All MVS messages have a
letter/number prefix, and the JES2 messages have a
$/letter/number prefix.
JES2 did not initialize, I think it was trying to start.
Post by Gerhard Postpischil
Did the IPL complete, i.e., did JES2 initialize. How far did the
IPL get? You mentioned a CMB shortage - does this message
The message persisted most of the morning - JES2 was the
only thing listed in the D a,l command that and some "Starting"
Post by Gerhard Postpischil
persist, or did it clear up (the message and clearing up is
normal at IPL time).
Gerhard Postpischil
Bradford, VT
I IPL'ed a second time and JES2 got into a more useful state where
it would accept the $Px1-9999 commands. I still have a
$HASP093 100% SPOOL UTILIZATION
And I think I need to restart JES2 with PARM='FORMAT,NOREQ' to resolve that.
(you may have mentioned something else earlier in this thread - I have to
go back and
look)
Ron.
Tony Harminc
2010-05-05 20:59:34 UTC
Permalink
Post by Gerhard Postpischil
Post by Ron Hudson
The commands below that purge various queues $PS1-9999 for example
all of them say "Not Executed"
I'm not aware of any such response. All MVS messages have a
letter/number prefix, and the JES2 messages have a
$/letter/number prefix.
IIRC there is an IEE message with that text if the subsystem command
character is defined, but the subsystem is inactive.

Tony H.
Ron Hudson
2010-05-05 21:35:32 UTC
Permalink
Ok, I ipl'ed it one more time - and now everything seems ok.

All three $Px1-9999 commands report "Job(s) not found"
and specifically the $PJ1-9999 does not report the one spool filling job
that
caused the original problem.

So I guess all is well now.
Kevin Leonard
2010-05-06 00:20:42 UTC
Permalink
Post by Tony Harminc
Post by Gerhard Postpischil
Post by Ron Hudson
The commands below that purge various queues $PS1-9999 for example
all of them say "Not Executed"
I'm not aware of any such response. All MVS messages have a
letter/number prefix, and the JES2 messages have a
$/letter/number prefix.
IIRC there is an IEE message with that text if the subsystem command
character is defined, but the subsystem is inactive.
MVS issues msgIEE707I cm NOT EXECUTED when a subsystem
command exit returns an SSOB return code of 8. JES2's
subsystem interface command exit (HOSCMND in JES2 4.1)
recognized the command as one that it should process,
but because of some constraint (no free CMBs) it couldn't.

--

Loading...