The following restrictions apply equally to main and subordinate procedures unless otherwise indicated.
In batch mode, QMF has no way of prompting you for the complete command.
These are commands that erase, update, or replace database objects, or that replace exported files. A confirmation panel asks you whether you want to make a change. In batch mode, QMF has no way of handling such prompts.
You can still issue commands that erase or change data objects, but you must inhibit the confirmation prompt.
To inhibit the confirmation panel, include CONFIRM=NO or issue the command:
SET PROFILE (CONFIRM=NO
QMF has no way to prompt you in batch mode.
If you are using a National Language Feature (NLF): You are writing a sequence of QMF commands that the NLF must understand. The verbs and keywords in the commands must be the translated versions of their English-language counterparts: ANZEIGEN for DISPLAY, for example, in a German batch mode procedure, and PROZEDUR for PROC.
The following main procedure illustrates some of the restrictions on batch procedures in the VM environment:
CONNECT userid (PASSWORD = mypass RUN MYQUERY (FORM = myform SAVE DATA AS MYTABLE (CONFIRM = no CMS CP SP PRT TO USERID PRINT REPORT CMS CP SP PRT CLOSE
The following main procedure illustrates some of the restrictions on batch procedures for the z/OS environment:
SET PROFILE (CONFIRM=NO RUN QUERYA (&&LICENSE='007' PRINT REPORT (PRINTER=' SAVE DATA AS TABLEA RUN PROCA (&&TABLE=TABLEA EXIT
The object names in this command are not qualified with the owner's name. Their owner is, therefore, the person for whom the procedure is being run; that is, the person whose logon ID appears as the USER parameter on the JOB card.
The SAVE command does not need to contain CONFIRM=NO because of the SET PROFILE command at the start of the procedure. If the DATA object is too large for the storage that is reserved for it, the SAVE command might end the procedure through the incomplete-data prompt condition.
The name of this table is passed to the procedure through the &TABLE parameter. This command fails if the procedure called has other substitution variables not set.