As I understand it:
CIERR 9030 is what you should get if you specific :PAUSE with <0 seconds.
This is a front-end error before any pausing of your job is done
CIWARN 9032 is what you should get if your job wakes up and finds that it's been asleep longer than expected
This is a back-end WARNING error AFTER the job has paused for some time.
So simply based upon seeing :PAUSE 5 followed by CIERROR 9030 my suspicion would be:
1) UDC/Command file for PAUSE
2) AIF:PE ?MPEX? command capture & possible bug there
3) NL.PUB.SYS Code corruption.
4) Possible MPE/iX bug
If someone wants to mess around in PM debug (possible system crash)
Command procedures are typically CX(command) or HX(command) suspect hxpause (or HXPAUSE?) in this case
Experimental suggestion
CI:DEBUG with PM
Debug> bp HXPAUSE
Debug> C
CI :PAUSE -5
Debug> Use "Single Step" with code "windows on"
Very likely one of the first things we'll check is the value of the pause interval.
Look for code that tests for <0
Followed by load of a value like 9030 in hex
Followed by a call (BLE) to cerror which is where all CIERRs are set-up. . .
You might get lucky if you set a BP in cerror.
If that works then you can learn about setting BPs in JOBS ( tricky w/o physical access the quiescent physical console.)
YMMV. No guarantees. No HP support implied.
Jim
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Jack Connor
Sent: Wednesday, April 02, 2014 3:43 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Always Put CONTINUE Statements Before PAUSE Statements
Ah...I missed the SUSPENDJOB portion, John...thanks!
Have to read more thoroughly in the future.
jack
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of John Clogg
Sent: Wednesday, April 02, 2014 6:24 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Always Put CONTINUE Statements Before PAUSE Statements
Although I was able to reproduce the problem, I had never seen it before, even though we run lots of jobs the PAUSE in them. I think it's pretty rare to suspend a job while it's paused, so it's not surprising that not many of us have encountered this before. This is definitely an MPE thing, not a third-party phenomenon.
John
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Jack Connor
Sent: Wednesday, April 02, 2014 2:42 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Always Put CONTINUE Statements Before PAUSE Statements
Additionally, I haven't seen it from 5.5 through 7.5 pp5.
I wonder if there's a 3rd party tool or seldom used MPE package underlying this issue?
Bizarre.
jack
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Jack Connor
Sent: Wednesday, April 02, 2014 5:14 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Always Put CONTINUE Statements Before PAUSE Statements
I've never seen this before and I use anything from pause 3 to pause 300...but it's in straight old STREAMed jcl.
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Craig Lalley
Sent: Wednesday, April 02, 2014 4:53 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Always Put CONTINUE Statements Before PAUSE Statements
I wonder if there is an OS patch that resolves this? I assume Barry's system is fully patched. Is Tracy's?
-Craig
Sent from my iPad
> On Apr 2, 2014, at 11:33 AM, Barry Lake <[log in to unmask]> wrote:
>
>> On 4/2/14 11:10 AM, Johnson, Tracy wrote:
>> Maybe you have a SYSTEM logon UDC that sets HPAUTOCONT ON?
>
> That shouldn't matter. Whether or not CONTINUE or HPAUTOCONT are enabled, one should still see this error (if the error occurs):
>
> Number of pause seconds is out of range. (CIERR 9030)
>
> But I haven't seen it in any test yet.
>
> And, to satisfy your curiosity:
>
>
> Sauron: stream
> >!job showvar,manager.sys
> >!showvar hp@
> >!eoj
> #J27
> >:
> Sauron: stj 27
>
>
> :JOB SHOWVAR,MANAGER.SYS,PUB.
> Priority = DS; Inpri = 8; Time = UNLIMITED seconds.
> Job number = #j27.
> WED, APR 2, 2014, 11:26 AM.
> HP3000 Release: C.75.00 User Version: C.75.03
> MPE/iX HP31900 C.45.05 Copyright Hewlett-Packard 1987.
> All rights reserved.
> STREAMED BY BARRY,MANAGER.SYS (#S3) ON LDEV# 4
> STREAM DATE: WED, APR 2, 2014, 11:26 AM
>
> :showvar hp@
> HPACCOUNT = SYS
> HPACCTCAP = -4259381
> HPACCTCAPF = SM,AM,AL,GL,DI,OP,CV,UV,LG,PS,NA,NM,CS,ND,SF,BA,IA,PM,MR,DS,PH
> HPAUTOCONT = FALSE
> HPCIDEPTH = 1
> HPCIERR = 0
> HPCIERRCOL = 0
> HPCIERRMSG =
> HPCMDNUM = 2
> HPCMDTRACE = FALSE
> (24/114) Continue? n
> Sauron:
>
>
> So, it's certainly a mystery. But not one worth spending too much more time on, I'd think.
>
> Barry
>
>
>
>>> -----Original Message-----
>>> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
>>> Behalf Of Barry Lake
>>> Sent: Wednesday, April 02, 2014 2:09 PM
>>> To: [log in to unmask]
>>> Subject: Re: [HP3000-L] Always Put CONTINUE Statements Before PAUSE
>>> Statements
>>>
>>> Hi Keven,
>>>
>>> I don't see how your test is any different from mine, except for the
>>> fact that the "PAUSE30" job is itself streamed, suspended and
>>> resumed by a job ("PAUSTEST"), rather than by an interactive
>>> session, as was the case in my test.
>>>
>>> I would expect to get the same result either way. And, in fact, on
>>> my system I do. I ran the job (which streams a job) exactly as you
>>> provided it. Here's the $STDLIST of the "inner" job, which was
>>> suspended during its PAUSE 30 by the "outer" job:
>>>
>>>
>>> Sauron: stj 26
>>>
>>>
>>> :JOB PAUSE30,MANAGER.SYS,PUB.
>>> Priority = DS; Inpri = 8; Time = UNLIMITED seconds.
>>> Job number = #j26.
>>> WED, APR 2, 2014, 10:55 AM.
>>> HP3000 Release: C.75.00 User Version: C.75.03
>>> MPE/iX HP31900 C.45.05 Copyright Hewlett-Packard 1987.
>>> All rights reserved.
>>> STREAMED BY PAUSTEST,MANAGER.SYS (#J25) ON LDEV# 10
>>> STREAM DATE: WED, APR 2, 2014, 10:55 AM
>>>
>>> :SETVAR PTIME 30
>>> :TELLOP !HPJOBNAME Pausing for !PTIME
>>> :SETJCW CIERROR=0
>>> :CONTINUE
>>> :PAUSE !PTIME
>>> :TELLOP !HPJOBNAME Error !HPCIERRMSG
>>> :EOJ
>>> CPU sec. = 1. elapsed min. = 1. WED, APR 2, 2014, 10:56 AM.
>>>
>>>
>>> As you can see, no errors, no warnings. So I'm still not able to
>>> duplicate the problem.
>>>
>>> Barry
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
Be sure to ask us about short term and long term rentals on servers, workstations, storage and more!
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.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
Be sure to ask us about short term and long term rentals on servers, workstations, storage and more!
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.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
Be sure to ask us about short term and long term rentals on servers, workstations, storage and more!
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.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|