Some API commands format information or write information to minidisks. These processes can take some time to complete. You can write your program or EXEC to either wait for the API command to finish before other work can be done from the issuing terminal, or to complete the work in a servant, allowing the issuing user ID to continue with other work.
Because a process running on a servant has no communication path to the issuing user ID’s virtual machine, CA VM:Director sends all messages generated by the process to the servant. When an API command in the servant completes, CA VM:Director sends the console file of the servant’s activity to the issuing user’s reader queue.
One option is available on most API commands that can run the process on a servant:
Waits (WAIT) for the API command to finish processing before allowing the issuing user ID to continue or does not wait (NOWAIT) but runs the process on a servant so the issuing user ID can continue.
The Servant Facility must be active for the NOWAIT option to work.
The WAIT | NOWAIT option on an API command is ignored if you specify the NOFORMAT option on that API command, since NOFORMAT implies that there is no time‑consuming command processing. The option is also ignored if you create a directory profile or a minidisk on T‑DISK or V‑DISK, since no time‑consuming activity involving a minidisk actually occurs.
The NOWAIT option cannot be used with the FILE or STACK option.
|
Copyright © 2014 CA.
All rights reserved.
|
|