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 *