LISTSERV - HP3000-L Archives

HP3000-L Archives

April 2014, Week 1

HP3000-L@RAVEN.UTC.EDU

	LISTSERV Archives
	HP3000-L Home
	HP3000-L April 2014, Week 1

	Log In
	Register

	Subscribe or Unsubscribe

	Search Archives

Options:	Use Monospaced Font Show Text Part by Default Show All Mail Headers
Message:	[<< First] [< Prev] [Next >] [Last >>]
Topic:	[<< First] [< Prev] [Next >] [Last >>]
Author:	[<< First] [< Prev] [Next >] [Last >>]

Subject:	Re: Always Put CONTINUE Statements Before PAUSE Statements
From:	Stan Sieler <[log in to unmask]>
Reply To:	Stan Sieler <[log in to unmask]>
Date:	Fri, 4 Apr 2014 15:22:41 -0700
Content-Type:	text/plain
Parts/Attachments:	text/plain (20 lines)

Re:
> 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 :PAUSE 5
>      ^
> Number of pause seconds is out of range. (CIERR 9030)
> REMAINDER OF JOB FLUSHED.
> 


After analyzing hxpause, the executor responsible for implementing the CI PAUSE command,
I suspect there is a bug in the MPE/iX internal routine "pausey", which hxpause uses.
The bug appears to be triggerable by :BREAKJOB/:RESUMEJOB, but I have not characterized 
precisely what triggers it.  It is, however, apparently the result of the equivalent
of an uninitialized variable.

I believe Allegro could develop a patch, should a customer be interested in it.

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

ATOM RSS1 RSS2

RAVEN.UTC.EDU