Marc's Place

1  SYNCHRONIZE
   Holds the process issuing the command until the specified job
   completes execution.

   Requires delete (D) access to the specified job.

   Format

     SYNCHRONIZE  [job-name]
 

2  Parameter
 

job-name

   Specifies the name of the job as defined when the job was
   submitted. You can specify only job names that are associated
   with your user name. (A job is associated with the user name of
   the process that submits it.)

   To specify a job that does not have a unique name, use the
   /ENTRY qualifier to specify the entry number. If you specify both
   the job-name parameter and the /ENTRY qualifier, the job-name
   parameter is ignored.

   If you specify the job-name parameter, the command searches for a
   job with the specified name in the queue SYS$BATCH. To specify a
   job in a different queue, you must specify the name of the queue
   using the /QUEUE qualifier.
 

2  Qualifiers
 

/ENTRY

      /ENTRY=entry-number

   Identifies the job by the system-assigned entry number.

   The system assigns a unique entry number to each queued print
   or batch job in the system. By default, the PRINT and SUBMIT
   commands display the entry number when they successfully queue
   a job for processing. These commands also create or update the
   local symbol $ENTRY to reflect the entry number of the most
   recently queued job. To find a job's entry number, enter the SHOW
   ENTRY or SHOW QUEUE command. If you specify both the job-name
   parameter and the /ENTRY qualifier, the job name is ignored.
 

/QUEUE

      /QUEUE=queue-name[:]

   Names the queue containing the job. If you use the /QUEUE
   qualifier, you must specify either the job-name parameter or
   the /ENTRY qualifier. If you specify the job-name parameter, the
   default queue is SYS$BATCH. If you specify the /ENTRY qualifier,
   there is no default queue. If you specify a generic queue, the
   command looks for the job in the generic queue and in the qeneric
   queue's target execution queues.
 

2  Examples

   1.$ SUBMIT/NAME=PREP FORMAT/PARAMETERS=(SORT,PURGE)
       Job PREP (queue SYS$BATCH, entry 219) started on queue SYS$BATCH
     $ SUBMIT PHASER
       Job PHASER (queue SYS$BATCH, entry 223) started on queue SYS$BATCH

     In this example, the first SUBMIT command submits the command
     procedure FORMAT.COM for execution and names the job PREP.
     The second SUBMIT command queues the procedure PHASER.COM. The
     procedure PHASER.COM contains the following line:

       $ SYNCHRONIZE PREP

     When this line is processed, the system verifies whether the
     job named PREP exists in the default queue SYS$BATCH. The
     procedure PHASER is forced to wait until the job PREP completes
     execution.

   2.$ SUBMIT/NAME=TIMER       COMP.COM
       Job TIMER (queue SYS$BATCH, entry 214) started on queue SYS$BATCH
     $ SYNCHRONIZE /ENTRY=214

     In this example, a batch job named TIMER is submitted. Then
     the SYNCHRONIZE command is entered interactively. This command
     places the interactive process in a wait state until entry
     number 214 (TIMER) completes. You cannot enter subsequent
     commands from your terminal session until the SYNCHRONIZE
     command completes and your process is released from the wait
     state.

   3.$ SUBMIT/NAME=TIMER COMP.COM/QUEUE=BUILD_QUEUE
     $ SYNCHRONIZE/QUEUE=BUILD_QUEUE TIMER

     The batch job name TIMER is submitted to the queue BUILD_QUEUE
     in this example. Then the SYNCHRONIZE command is entered
     interactively. Because the job named TIMER is not in the
     default queue SYS$BATCH, the SYNCHRONIZE command includes
     the /QUEUE qualifier to specify the queue in which the job
     is located.

---

© 1997- Marc Vos (and others)   -   Privacy Statement   -    Contact Me

On this website, Google Analytics is used to track visitor statistics. These are anonymised data about the number of visitors, which pages they visit on this site, from which regions they visit, which web browsers they use, etc.. You will also see non-personalised ads via Google AdSense. Cookies from Paddle or Paypal are placed when you click on a 'Buy now!' or 'Donate!' button, and possible cookies from Disqus when you use that system to comment on one or more blogposts.
Privacy Statement

Dismiss