Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00) (30216-90269)

Chapter 10 205
Technical Articles
CI Enhancements
Footnote: this is the same value as the total number of accessors in the
LISTF format 8 summary line.
Examples
finfo('CI.PUB.SYS',"sectors") = 192
finfo('CI.PUB.SYS',"extents") = 2
finfo('CI.PUB.SYS',"createtime") = 11:08 AM
finfo('CI.PUB.SYS', -60) = 110808
finfo('CI.PUB.SYS', "accessors") = 124
PAUSE Enhancement
Syntax
PAUSE [num_seconds]
[[;JOB=]jobid]
[[;INTERVAL=]interval_secs]
[;EXIST | WAIT | NOTEXIST]
The PAUSE command allows the current task to be suspended or "sleep"
for a specified number of seconds. PAUSE now supports sleeping until
one or more jobs reach a certain state. For example, a script can pause
while selected jobs or sessions are executing (EXIST). Or, a job can sleep
while another job is suspended or waiting (WAIT), and as soon as the job
starts executing or terminates the pause completes. A session can
pause while no jobs exist (NOTEXIST) and wake up as soon as the first
job is launched.
In its simplest form, the PAUSE command sleeps for num_seconds, or less
if
Break is pressed. In this simple case no jobid is specified and all other
command arguments are ignored. If the jobid parameter is specified,
then interval_secs and the remaining command parameters have
meaning. When jobid is supplied, PAUSE typically sleeps until the jobs
or sessions matching jobid have terminated.
Options
EXIST (default) means to pause while all jobs and sessions
matching jobid exist. These jobs can be scheduled,
waiting, executing, and other states; but, as long as the
system's global job table (JMAT) contains an entry for
any of the selected jobs and sessions, the PAUSE
command will continue to sleep.
WAIT means to pause while the selected job or jobs are
waiting. As soon as all the matching jobs are no longer
waiting (meaning all the job states are no longer
"introduced," "waiting," or "scheduled") the pause ends.
The life cycle of a job is typically:
[sched or waiting->] intro-> initializing->
exec-> [susp-> exec->] terminate
Waiting jobs are considered all job states left of and
excluding "initializing." Non-waiting jobs are all jobs
right of and including "initializing."