APAR status
Closed as canceled.
Error description
This Info. APAR documents changes to the DB2 Command & Utility Reference SC26489100 which did not make Version 3 GA pubs. Continuation of II07612, II08602 & II09176. 5740xyr00 R310 ================================================================ Version 3 Book Title: DB2 Command and Utility Reference Page: 121 Change Description: Add the following paragraph as an additional Usage Note to the DSN command: DSN RETURN CODE PROCESSING: At the end of a DSN session, register 15 contains the highest value placed there by any DSN subcommand used in the session or by any program run by the RUN subcommand. Your run-time environment might format that value as a return code. The value DOES NOT, however, originate in DSN. ================================================================ Version 3 Book Title: Command and Utility Reference Pages: 224 Change Description: Add the following sentence to the AUTHID keyword description for the -START TRACE command: "The authorization IDs specified must be the primary authorization IDs." ================================================================ Book Title: Command and Utility Reference Page Number: 241 Change Description: Replace the first, second and third new paragraphs on the page with the following: You must specify a trace type or an asterisk. For example, the command -STOP TRACE (*) stops all active traces. When stopping trace classes, a special circumstance occurs if monitor trace class 6 is active. Monitor trace class 6 enables and disables data propagation in V3R1. To avoid accidentally stopping this trace class, the -STOP TRACE(*) or -STOP TRACE(MON) CLASS(*) commands fail if monitor trace class 6 is active. To stop monitor trace class 6, all 32 trace classes within the monitor trace type must be explicitly specified as arguments of the CLASS option of the -STOP TRACE command. For example, issuing the command -STOP TRACE(MON) CLASS(1,2,3,4, ... 32) is required to stop monitor trace classes started with the command -START TRACE(MON) CLASS(*) or monitor trace class 6. However, if monitor trace class 6 is not active the -STOP TRACE(*) command will stop all active traces. ================================================================ Version 3 Book Title: Command and Utility Reference Pages: 304 & 307 Change Description: 1) On pg. 304, under "PASSWORD=password", the statement that begins with "In the SYSTEMDB statement," should be corrected: In the SYSTEMDB statement, 'password' assigns a password to the directory(DSNDB01) and the catalog(DSNDB06). 2) The first sentence on pg. 307 (under TBLSPACE= table-space-name) should read as follows: Use the SYSTEMDB statement only if the database name (dbname) is DSNDB01 or DSNDB06. =============================================================== Book Title: DB2 Version 3 Command and Utility Reference Page Number: 330 Change Description: The maximum value for the ROWLIMIT option of DSN1COMP was corrected to 99,000,000. =============================================================== Version 3 Book Title: DB2 Command and Utility Reference Pages: 339 Change Description: After the sentence stating "DSN1COPY allocates all target data sets." The following sentence will be added: However, all A002, A003,...A00n datasets must be previously defined using IDCAMS. ================================================================ Version 3 Book Title: Command and Utility Reference Page: 345 Change Description: Add the following sentence to the RBAEND keyword description: If the specified RBA is in the middle of a log record, DSN1LOGP continues reading until the end of that log record. =============================================================== Version 3 Book Title: Command and Utility Reference Pages: 363 Change Description: The syntax diagram for DSN1SDMP is incorrect. The SELECT keyword can only be used once. The arrow should point after the SELECT keyword, as in the following syntax diagram: >--------------------------------------------------------> ¦ <-------------------------------- ¦ ----SELECT----function,offset,data-specification---- ================================================================ Version 3 Book Title: Command and Utility Reference Pages: 365 Change Description: Change the description of the offset parameter: | 'A decimal value that specifies the number of bytes into the trace record where the comparison with the data-specification field begins. The offset starts...' ================================================================ Book Title: DB2 Version 3 Command and Utility Reference Page Number: 371 Change Description: A warning was added to the description of the RESUME option of LOAD that says serializing at the table space level rather than the partition level can inhibit concurrent processing of multiple partitions. =============================================================== Version 3 Book Title: Command and Utility Reference Pages: 392 Change Description: Add to the Usage Note 'Recovering a Failed LOAD Job' that the SYSCOPY record is inserted only when LOG YES has been specified. =============================================================== Book Title: DB2 Version 3 Command and Utility Reference Page Number: 401 Change Description: The following sentence was added to the MODIFY RECOVERY description: There are no SYSCOPY records for DSNDB06.SYSCOPY, DSNDB01.SYSUTIL, or DSNDB01.DBD01. You can run MODIFY RECOVERY on these table spaces, but you receive message DSNU573, indicating that no SYSCOPY records could be found. The utility stops without deleting any records from SYSCOPY or SYSLGRNG. =============================================================== Version 3 Book Title: Command and Utility Reference Page: 407 Change Description: The second sentence of the table-space-name description is incorrect. Replace it with the following: You cannot include DSNDB01.SYSUTILX in a list of table spaces to quiesce. =============================================================== Version 3 Book Title: DB2 Command and Utility Reference Pages: 422 Change Description: The paragraph reading: To run on DSNDB01.SYSUTILX, RECOVER TABLESPACE must be the only utility in the job step and the only utility running in the DB2 subsystem. will be changed to: To run on DSNDB01.DBD01 or DSNDB01.SYSUTILX, RECOVER TABLESPACE must be the only utility in the job step and the only utility running in the DB2 subsystem. ================================================================ Version 3 Book Title: Command and Utility Reference Pages: 434 Change Description: In Table 48. 'Reorg Summary', the REORG TABLESPACE PART n row should be changed to the following: Specification Results ----------------------------------------------------------- REORG Data for part n + part n of the partitioned TABLESPACE index + index entries for part n in all PART n non-partitioned indexes =============================================================== Book Title: DB2 Version 3 Command and Utility Reference Page Number: 439 Change Description: The REORG usage note, 'Effects of Specifying SORTDATA', was clarified so that the first bullet now says: If an explicit clustering index exists on any table in the table space being reorganized, rows of the table space are unloaded in physical sequence. (If the object being reorganized is a partition, rows of that partition are unloaded in physical sequence.) DFSORT then uses the clustering index key to sort the rows. If any other table in the table space has no explicit clustering index, the key of the implicit clustering index (if one exists) is used for the sort. =============================================================== Book Title: DB2 Version 3 Command and Utility Reference Page Number: 423 Change Description: The RECOVER TABLESPACE usage note, 'Avoiding Damaged Media', was split into two notes. The resulting usage note, shown below, was clarified as well. RETAINING TAPE MOUNTS If the image copy data sets from which you want to recover reside on the same tape, you do not need to remove the tape. For noncataloged image copies, specify the following parameters on the DD cards (in this example, the DD cards are COPY1 and COPY2): //COPY1 DD UNIT=3480,DSN=COPY1,DISP=(OLD,PASS),LABEL=1, // VOL=(,RETAIN,SER=USRDMP) //COPY2 DD UNIT=3480,DSN=COPY2,DISP=(OLD,PASS),LABEL=2, // VOL=(,REF=*.COPY1) The above example only works for multiple image copies on a single volume. To use multiple image copies on multiple volumes, the image copy data sets must be cataloged. WARNING: You might lose data during RECOVER if an image copy data set spans two or more volumes and the data set is not cataloged. For cataloged image copies on one or more tape volumes, specify the following parameters on the DD cards (in this example, the DD cards are COPY1, COPY2 and COPY3); //COPY1 DD DSN=IC1,UNIT=3480,DISP=(OLD,PASS), // VOL=(,RETAIN),LABEL=(1,SL) //COPY2 DD DSN=IC2,UNIT=3480,DISP=(OLD,PASS), // VOL=(,RETAIN),LABEL=(2,SL) //COPY3 DD DSN=IC3,UNIT=3480,DISP=(OLD,PASS), // VOL=(,RETAIN),LABEL=(3,SL) =============================================================== Version 3 Book Title: DB2 Command and Utility Ref. Pages: 469 Change Description: The following corrections apply to table 57, "Catalog Tables Updated by RUNSTATS": Remove SYSCOLDIST and SYSCOLDISTSTATS from the TABLE - UPDATE ACCESSPATH row. These catalog tables are not updated by running RUNSTATS TABLESPACE TABLE. Add the SYSCOLSTATS table to the following rows: INDEX - UPDATE ALL INDEX - UPDATE ACCESSPATH =============================================================== Version 3 Book Title: Command and Utility Reference Page Number: 67 Change Description: Add the following sentence in the Usage notes: " Binding a Plan with DEGREE(ANY): Binding will cause the average size of the Plan to increase. " =============================================================== Continued in II08602.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
close for INTERNET viewing
APAR Information
APAR number
II07864
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1994-05-06
Closed date
1997-11-01
Last modified date
1997-11-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
14 December 2020