HP3000-L Archives

April 2014, Week 1

HP3000-L@RAVEN.UTC.EDU
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 >>]

Print Reply
Subject:
Always Put CONTINUE Statements Before PAUSE Statements
From:
"Johnson, Tracy" <[log in to unmask]>
Reply To:
Johnson, Tracy
Date:
Wed, 2 Apr 2014 14:31:36 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines) 
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 *

ATOM RSS1 RSS2