Specifies prompts that must be answered affirmatively before a job or job stream is launched.


prompt [folder/]promptname [,...]

prompt "[: | !]text" [,...]


Specifies the name of a prompt in the database. You can specify more than one promptname separated by commas but you cannot mix under the same prompt keyword prompts defined in the database with literal prompts.
Specifies a literal prompt as a text string enclosed in quotes ("). Multiple strings separated by backlash n (\n) can be used for long messages. If the string begins with a colon (:), the message is displayed but no reply is necessary. If the string begins with an exclamation mark (!), the message is displayed, but it is not recorded in the log file. You can include backslash n (\n) within the text for new lines.
You can use one or more parameters as part or all of the text string. To use a parameter, place its name between carets (^). Refer to Variable and parameter definition for additional information and examples.
Note: Within a local prompt, when not specifying a parameter, carets (^) must be preceded by a backslash (\) or they cause errors in the prompt. Within global prompts, carets do not have to be preceded by a backslash.


The following example shows both literal and named prompts. The first prompt is a literal prompt that uses a parameter named sys1. When a single affirmative reply is received for the prompt named apmsg, the dependencies for both job1 and job2 are satisfied.
schedule sked3 on tu,th
  prompt "All ap users logged out of ^sys1^? (y/n)"
  job1 prompt apmsg
  job2 prompt apmsg
The following example defines a literal prompt that appears on more than one line. It is defined with backlash n (\n) at the end of each line:
schedule sked5 on fr
  prompt  "The jobs in this job stream consume \n
an enormous amount of cpu time.\n
Do you want to launch it now? (y/n)"
  j2 follows j1