Tracy,

What version of MPE is on the system where you see this happening?

I can't duplicate the problem on a 7.5.3 system using your instructions:


   Sauron: stream
   >!job pause60, manager.sys
   >!pause 60
   >!eoj
    #J23
   >:
   Sauron: breakjob #j23
   Sauron: showjob #j23

   JOBNUM  STATE IPRI JIN  JLIST    INTRODUCED  JOB NAME

   #J23    SUSP        10S LP       WED  9:43A  PAUSE60,MANAGER.SYS

   JOBFENCE= 7; JLIMIT= 8; SLIMIT= 16

   Sauron: pause 70
   Sauron: resumejob #j23
   Sauron: stj 23


    :JOB PAUSE60,MANAGER.SYS,PUB.
    Priority = DS; Inpri = 8; Time = UNLIMITED seconds.
    Job number = #j23.
    WED, APR  2, 2014,  9:43 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,  9:43 AM

    :pause 60
    :eoj
    CPU sec. = 1.  elapsed min. = 3.  WED, APR  2, 2014,  9:46 AM.

   Sauron:


Regards,
Barry Lake
Allegro Consultants, Inc.



On 4/2/14 7:31 AM, Johnson, Tracy wrote:
> I nearly always put a CONTINUE statement before a PAUSE in any job.  Over the years
> I have discovered that sometimes the CPU waits "longer" than the specified pause
> and fails with an error.  (Or you can duplicate this by doing a SUSPENDJOB on a job
>in the middle of a PAUSE then do a RESUMEJOB after the specified time.)
>
> :PAUSE 5
>        ^
> Number of pause seconds is out of range. (CIERR 9030)
> REMAINDER OF JOB FLUSHED.
>
> A mere CONTINUE statement would have prevented this.
>
> I brought this up for general reading because I found it in generated JCL, I had it
>recompied with embedded CONTINUE statements in the right places.
>
>
> Tracy Johnson
> Business Analyst
> Measurement Specialties, Inc.
> Office (757) 766-4318
> Cell (757) 755-6470
> [log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *