I assume you are using the CI pause command and you are *not* specifying
a job number, but rather some form of: @J, @J:user.acct,
@J:jobname,user.acct... for the jobID parm.

CIWARN 9032 is reported when one or more matching jobs still exist but
the pause time given to PAUSE (1st parm) has been exceeded.

The easiest solution is to know the job numbers of the job you wish to
pause for.  This is simple to capture, via the HPLASTJOB variable, if
your job/session has streamed the job(s) in question.

You could also capture these job numbers from another job/session if
that job/session placed the job number for each job they streamed in a
variable "array/list". Then you could capture this list via  :SHOWVAR
list;job=#j|Snnn >foo   and read foo to create you own local list.

You might also be able to be more selective in your JobID parm for
PAUSE.  Remember you can select based on job vs. session, user.acct, and
jobname, all with full wildcarding support.

HTH,
 Jeff

> Our daily processing shuts down various jobs before the 
> backup, and then aborts those that do not shut down. I had 
> noticed that some jobs took longer to shut down than this 
> process allowed, so I added times pauses for these jobs to 
> shutdown. Later, I noticed that one pause always gave an 
> error that the time for pause had been exceeded. Then I 
> noticed that this job was being rescheduled to start before 
> the backup. So of course, it existed, and pause waited on it. 
> Is there a simple way around this, to pause for the executing 
> job while it is shut down, but not for the scheduled job?

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