DB2 QMF Reference Version 8.1 updates

Content

Update 12
Date of change: October 10, 2011
Topic: Chapter 1, "QMF commands," topic "EXPORT in TSO"
Change description: The following bullet should be added under the "Notes" topic on p. 64:

• You can export to a PDSE data set as long as the data set has been pre-allocated or your installation default specifies creation of PDSE data sets. The installation default is set in member IGDSMSxx of the SYS1.PARMLIB data set.

Update 11
Date of change: October 10, 2011
Topic: Chapter 1, "QMF commands," topic "SET GLOBAL"
Change description: In the "Notes" topic on page 151, replace the content of the entire first bullet that appears on the page with the following information:

• If the variable value that you are setting is a character string that contains quotes, you can use quotes or parentheses to delimit the value. For example, consider the following query:
  
SELECT *
FROM Q.STAFF
WHERE NAME = &STAFF_NAME

To set the STAFF_NAME variable to a value of 'JAMES' using quotes, issue the following command:

SET GLOBAL (STAFF_NAME = ’’’JAMES’’’)

To set the STAFF_NAME variable using parentheses, issue the following command:

SET GLOBAL (STAFF_NAME=(’JAMES’))

Update 10
Date of change: October 10, 2011
Topic: Chapter 4, "General topics," subtopic "Report completion and the incomplete data prompt"
Change description: Add 'query' to the list of objects documented on p. 321 in parentheses after the SAVE command, as follows:

SAVE (data, form, procedure, query, or profile)

Update 9
Date of change: October 10, 2011
Topic: Chapter 1, "QMF commands"
Change description: In the topic "SET PROFILE," the first sentence in the description of the SPACE parameter (p. 155) should be changed as follows:

Specifies the default storage space in the database to place tables created with the SAVE DATA or IMPORT TABLE command.

Update 8
Date of change: October 4, 2011
Topic: Chapter 1, "QMF commands"
Change description: In the topic "Entering commands," subtopic "On a prompt panel," which appears on page 4, add the following sentence after the sentence "A panel appears containing the parameters that are applicable to that object.":

Entries in the Name field that begin with the characters ALL must be delimited in double quotation marks. For example, if you want to list all objects whose names begin with ALL, type "ALL%" in the Name field and press the List key.

Update 7
Date of change: October 4, 2011
Topic: Chapter 1, "QMF commands"
Change description: The "CALL" topic should be moved to Chapter 2, "SQL keywords and functions used in QMF queries". The following bullet should also be added in the "Notes" topic for the CALL statement on p. 16:

• CALL statements in QMF can be directed only to DB2 for z/OS databases.

Update 6
Date of change: October 4, 2011
Topic: Chapter 1, "QMF commands"
Change description: The topic on the SWITCH command, which appears on p. 167, should be removed.

Update 5
Date of change: October 4, 2011
Topic: Chapter 1, "QMF commands"
Change description: The first paragraph in the topic on the STATE command, which appears on p. 167, should read as follows:

The STATE command saves the following set of QMF global variable values in the ISPF variable pool:

• DSQALANG
• DSQAMODL
• DSQAMODP
• DSQAPCAS
• DSQAPDEC
• DSQAPGRP
• DSQAPLEN
• DSQAPLNG
• DSQAPPFK
• DSQAPPRT
• DSQAPRMP
• DSQAPSPC
• DSQAPSYN
• DSQAPTRC
• DSQAPWID
• DSQAQMF
• DSQAREVN
• DSQAROWS
• DSQASUBI
• DSQASUBP
• DSQASYST
• DSQATRAC
• DSQAVARN
• DSQCATTN

Update 4
Date of change: October 4, 2011
Topic: Chapter 1, "QMF commands"
Change description: To clarify when QMF exports column labels versus column names, the following revisions should be made:

(1) The following bullets should be added under the "Notes" topics for both the EXPORT in CICS command (p. 56) and the EXPORT in TSO command (p. 64):

• When you issue the EXPORT DATA or EXPORT TABLE command, QMF exports either column labels or column names depending on the value of the DATAFORMAT parameter:
• When DATAFORMAT=QMF, column names are exported even for columns that have database labels defined.
  
• When DATAFORMAT=IXF, labels are exported for any columns that have labels defined. Column names are exported for all other columns.

(2) The seventh bullet under "Notes" for the IMPORT in CICS command description, as well as the fourth bullet under "Notes" for the IMPORT in TSO command description, should be replaced with the following bullet:

• When you import into an existing table, the column names and labels remain unchanged. If the table does not exist, a new table is created. QMF creates labels on the new table if the database supports the LABEL ON statement. If the database does not support the LABEL ON statement, the new table is created without column labels.

• When you issue the SAVE DATA command with the ACTION=REPLACE parameter and the data to be saved contains column label information, QMF creates labels on the new table if the database supports the LABEL ON statement. If the database does not support the LABEL ON statement, the new table is created without column labels.
  

Update 3
Date of change: October 4, 2011
Topic: Chapter 1, "QMF commands"
Change description: The description of the IDENTIFIER parameter in the topic for the DRAW command on p. 40 should read as follows:

IDENTIFIER
Specifies an identifier to uniquely designate the table in the composed query. This option is ignored when TYPE=INSERT.

When you join tables, use this option to identify which columns in the composed query come from each of the joined tables. The query will not run if the tables have common column names that are not identified.

correlationname
A user-defined name that becomes a correlation name for the table in the composed query. This name is used to qualify columns in the query to avoid ambiguity or to establish a correlated reference for subqueries. It can also be used merely as a better name for the table to improve readability of the query.

If you do not specify this option, no correlation name is added to the composed query.

• For information on how the DRAW command works in QBE, press the More Help key.

Example:
To join two tables, issue the DRAW command twice in succession, once for each table. Be sure to use the IDENTIFIER parameter to identify which columns in the composed query are associated with each table.

DRAW Q.ORG (I=ORG
DRAW Q.STAFF (I=STAFF


QMF displays the query, which joins the Q.ORG and Q.STAFF tables:

SELECT ORG.DEPTNUMB, ORG.DEPTNAME, ORG.MANAGER
, ORG.DIVISION, ORG.LOCATION

, STAFF.ID, STAFF."NAME", STAFF.DEPT, STAFF.JOB
, STAFF."YEARS", STAFF.SALARY, STAFF.COMM
FROM Q.ORG ORG

, Q.STAFF STAFF

Update 2
Date of change: October 4, 2011
Topic: Chapter 1, "QMF commands"
Change description: The topic for the DPRE command on p. 39 should read as follows:

DPRE is a command synonym that provides print-preview capabilities so that you can see how a report will look when it is printed.

When you issue the DPRE command synonym, QMF runs an application named Q.DSQAER1P, which is shared for everyone's use. The procedure completes the QMF report that is currently in temporary storage and prints it to a data set that is allocated to DSQPRINT. The ISPF browser is then called to view this data set.

If you are using an NLF, issue the translated command synonym for DPRE. For example, the German command synonym for DPRE is AGB. For the translated command synonym for DPRE in the other language environments, see the Q.COMMAND_SYNONYM_n control table, where n is the one-character language identifier for the language in which you are using QMF. These identifiers are shown in Installing and Managing QMF for TSO and CICS, which also contains information about how to configure the DPRE application.

>>-- DPre ------------------------------------------<<

Update 1
Date of change: October 4, 2011
Topic: Appendix B, “QMF global variable tables”
Change description: Descriptions for the global variables described below are missing and should be added.

In topic "DSQ global variables that control how commands and procedures are executed," add the following global variables:

• DSQEC_DISABLEADM
• DSQEC_LAST_RUN
• DSQEC_PRO_ENABLE
• DSQEC_PRO_FORM
• DSQEC_PRO_PROC
• DSQEC_PRO_PROF
• DSQEC_PRO_QUERY
• DSQEC_SP_RS_NUM

http://www.ibm.com/support/knowledgecenter/SS9UMF_10.1.0/cmn/glv/dsq_glv_cmd_proc.html

Note that, in QMF Version 8, the maximum number of variables that can be passed on CALL statements that are issued from the QMF SQL Query panel is 32. Therefore, the maximum value of the DSQEC_SP_RS_NUM variable is 32, not 63 as is documented on the web page linked above.

In topic "DSQ global variables for state information not related to the profile," add the following global variable:

• DSQAO_QMFADM

In topic "DSQ global variables that control how information is displayed on the screen," add the following global variable:

• DSQDC_SHORT_EXPT