Filling in the prompt panel

A user can get help filling out the prompt panel by pressing function key 1, which results in the display of the first of three help panels.

Figure 256. The QMF batch prompt panel

 QMF BATCH              QUERY/PROC BATCH PROMPT
 OBJECT NAME    ===>                 Name of query or procedure
 Current OBJECT ===>  NO             Use object in temporary storage?
 QUERY or PROC  ===>  QUERY
 FORM  NAME     ===>                 Form to be used with query
 Current FORM   ===>  NO             Use form in temporary storage?
 BATCH NAME     ===>                 Name of QMF batch execution proc
 PROC arguments ===> ARGS
 CONNECT PASSWORD    ===>            Database password
 DISK PASSWORD       ===>            User 'A' disk read pasword      
 LOGGING             ===>  YES       Log messages and commands?
 BATCH MACHINE       ===>            CMS ID of batch machine
 SAVE DATA           ===>            Name of data to be saved
 REVIEW OUTPUT       ===>  YES       Send report to your reader?
 DISTRIBUTION        Userids and notes to send report
       USERID        ===>                   NODE  ===>
                     ===>                         ===>
 PRINT OUTPUT:       Printer ID and node for printed output.
           ID        ===>                  NODE     ===>
PF1=Help PF3=End  Enter=Process batch request

Required entry fields

Certain fields on the batch prompt panel are mandatory. Messages are displayed prompting the user to enter values for these required fields if the Enter key is pressed before values are provided. The cursor is then positioned on the field requiring input. Table 87 describes the required fields.

Table 87. BATCH application required entry fields
Field	Description
OBJECT NAME	A value is required for the name of the query or procedure to be run in batch mode. If the query or procedure is currently in temporary storage, it is saved in the database using this name. If the name is that of an existing object, the new object replaces the old one. (The name must be unqualified.) If the object is in the database, enter the name under which it was saved. (The name must be qualified if the object is owned by someone else and shared.) Save this object using CONFIRM = NO as a profile setting.
QUERY or PROC	The object type to be run in batch; must be either QUERY or PROC.
BATCH NAME	A value is required for the name of the QMF procedure to be run in batch mode. (The name is not qualified.) If you are submitting multiple queries, you need to modify the BATCH NAME field for each query or the new batch job replaces the old job. This procedure contains the appropriate QMF commands depending upon the user's input. The user's query or procedure, specified in the QUERY or PROC field, is run from this procedure. The procedure is saved using the SHARE = YES keyword option. It must be able to be run by the batch machine. Save this procedure using CONFIRM = NO as a profile setting.
PROC arguments	Through this field, you can pass arguments to the REXX procedure specified in the OBJECT NAME field.
CONNECT PASSWORD	Users are required to enter the DB2 for VM password. Assign this to a user in the SYSTEM.SYSUSERAUTH table. This password is used in a CONNECT command in the batch machine. The user is then operating with the authority granted to the DB2 for VM user ID. The batch procedure is run with this authority.
DISK PASSWORD	Users are required to enter their 191 A-disk read password. (If the user has no read password, 'ALL' must be entered instead.) This is used in the batch job sent to the CMS batch machine. The batch machine then links to the user's 191 disk.
BATCH MACHINE	Users are required to enter the CMS user ID of a batch machine on which the job is to be run. The job is punched to this machine. This value is saved across sessions for users. The batch machine must exist on the same processor as that of the user.

Table 87. BATCH application required entry fields

Field

Description

OBJECT NAME

A value is required for the name of the query or procedure to be run in batch mode. If the query or procedure is currently in temporary storage, it is saved in the database using this name. If the name is that of an existing object, the new object replaces the old one. (The name must be unqualified.) If the object is in the database, enter the name under which it was saved. (The name must be qualified if the object is owned by someone else and shared.) Save this object using CONFIRM = NO as a profile setting.

QUERY or PROC

The object type to be run in batch; must be either QUERY or PROC.

BATCH NAME

A value is required for the name of the QMF procedure to be run in batch mode. (The name is not qualified.) If you are submitting multiple queries, you need to modify the BATCH NAME field for each query or the new batch job replaces the old job. This procedure contains the appropriate QMF commands depending upon the user's input. The user's query or procedure, specified in the QUERY or PROC field, is run from this procedure. The procedure is saved using the SHARE = YES keyword option. It must be able to be run by the batch machine. Save this procedure using CONFIRM = NO as a profile setting.

PROC arguments

Through this field, you can pass arguments to the REXX procedure specified in the OBJECT NAME field.

CONNECT PASSWORD

Users are required to enter the DB2 for VM password. Assign this to a user in the SYSTEM.SYSUSERAUTH table. This password is used in a CONNECT command in the batch machine. The user is then operating with the authority granted to the DB2 for VM user ID. The batch procedure is run with this authority.

DISK PASSWORD

Users are required to enter their 191 A-disk read password. (If the user has no read password, 'ALL' must be entered instead.) This is used in the batch job sent to the CMS batch machine. The batch machine then links to the user's 191 disk.

BATCH MACHINE

Users are required to enter the CMS user ID of a batch machine on which the job is to be run. The job is punched to this machine. This value is saved across sessions for users. The batch machine must exist on the same processor as that of the user.

Optional entry fields

Table 88 describes the remaining (optional) entry fields on the panel. Where a value of YES or NO is expected, a default YES or NO normally appears on the screen. If a user blanks out a value in a YES/NO field, the user is prompted for an entry.

Table 88. BATCH application optional entry fields
Field	Description
Current OBJECT	If the batch query or procedure is currently in temporary storage, the user enters YES in this field. The query or procedure is then saved to be run later in batch. If the query or procedure is in the database, enter NO. The default value for this field is NO.
FORM NAME	To run the batch query using a form, the user must specify the name of a form in this field. If the form to be used: Is the default form, leave the field empty. Is in the database, the form is saved using this name. The name must be qualified if the form is owned by someone else and shared. Is the current form, enter a name under which it can be saved. The name must be unqualified, because the form is saved under your own authorization ID. This form is saved using CONFIRM = NO as a profile setting. If you enter the name of an existing form, the new form replaces the old.
Current FORM	If the batch form is the current form, the user enters YES in this field. The form is then saved for use later in batch. If the form is in the database, enter NO. The default value for this field is NO.
LOGGING	The default value for this field is YES. This means that the default trace level in batch mode is L2, which traces messages and commands. If the user doesn't want tracing at the L2 level, NO should be specified. Tracing does not continue in the batch procedure beyond the SET PROFILE (TRACE=NONE command, which is then in the generated user procedure.
SAVE DATA	If the user wants the data resulting from running a query or procedure to be saved, a value must be given for this field. The DATA is saved as a new table using this name and the CONFIRM=NO keyword option.
REVIEW OUTPUT	If the user wants to view the report from running the batch query or procedure, YES (the default value) should be specified as the value for this field. The report is sent to the user's reader using SENDFILE. If the query or procedure to be sent to batch does not generate a report, such as an INSERT or UPDATE query, this field should be set to NO.
DISTRIBUTION USERID and NODE	If the user wants the resulting report to be sent to other users, the user must enter their user IDs and nodes in these fields. The report is sent using SENDFILE, which makes use of the NAMES file. Because of this fact, the NODE need only be supplied if the recipient of the report is on a different system and there is no entry for that user in the NAMES file. The USERID can also be a list defined in the NAMES file. If the query or procedure to be sent to batch does not generate a report, such as an INSERT or UPDATE query, no values should be supplied for these fields.
PRINT OUTPUT	If the user wants the resulting report to be sent to a printer, the printer ID and the NODE should be entered here. If the printer ID is SYSTEM, the output is sent to the system printer. The appropriate CP SPOOL and TAG commands are executed before the report is printed.

Table 88. BATCH application optional entry fields

Field

Description

Current OBJECT

If the batch query or procedure is currently in temporary storage, the user enters YES in this field. The query or procedure is then saved to be run later in batch. If the query or procedure is in the database, enter NO. The default value for this field is NO.

FORM NAME

To run the batch query using a form, the user must specify the name of a form in this field. If the form to be used:

Is the default form, leave the field empty.
Is in the database, the form is saved using this name. The name must be qualified if the form is owned by someone else and shared.
Is the current form, enter a name under which it can be saved. The name must be unqualified, because the form is saved under your own authorization ID.

This form is saved using CONFIRM = NO as a profile setting.

If you enter the name of an existing form, the new form replaces the old.

Current FORM

If the batch form is the current form, the user enters YES in this field. The form is then saved for use later in batch. If the form is in the database, enter NO. The default value for this field is NO.

LOGGING

The default value for this field is YES. This means that the default trace level in batch mode is L2, which traces messages and commands. If the user doesn't want tracing at the L2 level, NO should be specified. Tracing does not continue in the batch procedure beyond the SET PROFILE (TRACE=NONE command, which is then in the generated user procedure.

SAVE DATA

If the user wants the data resulting from running a query or procedure to be saved, a value must be given for this field. The DATA is saved as a new table using this name and the CONFIRM=NO keyword option.

REVIEW OUTPUT

If the user wants to view the report from running the batch query or procedure, YES (the default value) should be specified as the value for this field. The report is sent to the user's reader using SENDFILE. If the query or procedure to be sent to batch does not generate a report, such as an INSERT or UPDATE query, this field should be set to NO.

DISTRIBUTION USERID and NODE

If the user wants the resulting report to be sent to other users, the user must enter their user IDs and nodes in these fields. The report is sent using SENDFILE, which makes use of the NAMES file. Because of this fact, the NODE need only be supplied if the recipient of the report is on a different system and there is no entry for that user in the NAMES file. The USERID can also be a list defined in the NAMES file. If the query or procedure to be sent to batch does not generate a report, such as an INSERT or UPDATE query, no values should be supplied for these fields.

PRINT OUTPUT

If the user wants the resulting report to be sent to a printer, the printer ID and the NODE should be entered here. If the printer ID is SYSTEM, the output is sent to the system printer. The appropriate CP SPOOL and TAG commands are executed before the report is printed.