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 Info. APAR II07612, II07864 and II09176. 5740xyr00 R310 DB2 ================================================================ Version 3 Book Title: DB2 Command and Utility Reference Pages: 97 Change Description: Change the description of status code UTRO to: UTRO A utility is in process, on the table space, table space partition, index space, or index space partition, that allows only RO access. If the utility was canceled before the object was drained, the object can allow SQL access because the object was not altered by the utility. ============================================================ Version 3 Book Title: DB2 Command and Utility Reference Pages: 97 Change Description: Change the description of status code UTUT to: UTUT A utility is in process, on the table space, table space partition, index space, or index space partition, that allows only UT access. If the utility was cancelled before the object was drained, the object can allow SQL access because the object was not altered by the utility. ============================================================== Version 3 Book Title: DB2 Command and Utility Reference Pages: 193 Change Description: In the Usage Note "RECOVER BSDS Following BSDS I/O Error", change the pointer to the Administration Guide from "Section 5" to "Section 6". =============================================================== Version 3 Book Title: DB2 Command and Utility Reference Pages: 209 (START DATABASE) and 231 (STOP DATABASE) Change Description: Change the last two paragraphs of the "Authorization" section for START DATABASE to: When data definition control is active, installation SYSOPR or installation SYSADM authority is required to start the database, a table space, or an index space containing a registration table or index. Database DSNDB06 contains the table spaces and index spaces required to check the authorization for using START DATABASE. If a table or index space required for this authorization check is stopped and unavailable, then installation SYSADM authority is required to start any data base, table space, or index space, including the ones required for the authorization check. Change the last paragraph of the "Authorization" section of STOP DATABASE and add an additional paragraph to warn users about stopping DSNDB06: When data definition control is active, installation SYSOPR or installation SYSADM authority is required to stop the database, a table space, or an index space containing a registration table or index. Database DSNDB06 contains the table spaces and index spaces required to check authorization. If you stop any table space or index space required for the START DATABASE authorization check, then installation SYSADM authority is required to restart it. ========================================================== Version 3 Book Title: DB2 Command and Utility Reference Pages: 221, 227 Change Description: 1). On page 221, the IFCID option in the syntax will be footnoted with the following: Allows you to specify trace events in addition to the IFCIDs activated by the CLASS option. For details see the description of IFCID(ifcid,...) on page 227. 2). On page 227 under the description for the IFCID option, the first 4 paragraphs will be reworded into the following 3 paragraphs: Specifies what other IFCIDs (trace events), in addition to those IFCIDs contained in the classes specified in the CLASS option, are to be started. To start only those IFCIDs specified in the IFCID option, use trace classes 30-32. These classes have no predefined IFCIDs and are available for a location to use. See "Example 1" on page 229 for an example of activating only those trace events specified in the IFCID option.) If you do not specify the IFCID option, only those IFCIDs contained in the activated trace classes are started. The maximum number of IFCIDs is 156. The range of values that can be specified in the IFCID option is 1 through 350, with the exception of: 4, 5, 185, 187, 217, 232, 234, 240, and 241. These exceptions are invalid values for the IFCID option. IFCIDs 4 and 5 are always automatically active. Some of the other invalid IFCIDs can be activated only by certain trace classes. The invalid values for the IFCID option that can be started only by trace classes are listed below. ================================================================ Version 3 Book Title: DB2 Command and Utility Reference Pages: 232 Change Description: change the description of the option AT(COMMIT) to: AT(COMMIT) ---------- Marks the specified object as being in STOPP status to prevent access from new requesters. Currently running applications are allowed to continue access until their next commit. After commit, further access by the committing application is prohibited. The object is actually stopped when all jobs release their claims on it and all utilities release their drain locks on it. ================================================================ Version 3 Book Title: DB2 Command and Utility Reference Pages: 233 Change Description: This usage note is now added: AFTER A DASD FAILURE: Issuing the STOP DATABASE command before interrupting the I/O interface between the failed device and DB2 can result in incomplete I/O requests. To prevent this hang situation, create an interruption either by forcing the device offline using the MVS command VARY with the FORCE option, or by setting the I/O timing interval for the device before any failures. You can set the I/O timing interval through the IECIOSxx MVS parmlib member or by issuing the MVS command: SETIOS MIH,DEV=dddd,IOTIMING=mm:ss ================================================================ Version 3 Book Title: DB2 Command and Utility Reference Pages: 278 Change Description: The description of the EXCEPTIONS option will change from Specifies the maximum number of exceptions reported. CHECK DATA teminates when it reached the number of exceptions specified. If you specify zero, all exceptions are reported. ... integer is the maximum number of exceptions reported. to Specifies the maximum number of exceptions reported to the job output only. CHECK DATA terminates in the CHECKDAT phase when it reaches the number of exceptions specified. If termination occurs, the error rows are not written to the EXCEPTION table. If you specify zero, all exceptions are reported. ... integer is the maximum number of exceptions. =============================================================== Version 3 Book Title: DB2 Command and Utility Reference Pages: 342 Change Description: The sample JCL for running DSN1COPY contains two errors: 1) Figure 20 shows table space SYSUTIL instead of SYSUTILX 2) Figure 21 shows the wrong values for the SYSXLAT DD card The sample JCL for DSN1COPY will be modified as follows: In figure 20, line 4 will be changed to read: //SYSUT1 DD DSN=DSNCAT.DSNDBC.DSNDB01.SYSUTILX.I0001.A001, DISP=OLD In figure 21, the example will be changed to read: //EXECUTE EXEC PGM=DSN1COPY,PARM='OBIDXLAT' //STEPLIB DD DSN=PDS CONTAINING DSN1COPY //SYSPRINT DD SYSOUT=A //SYSUT1 DD DSN=DSNC310.DSNDBC.DSN8D41P.DSN8S41C.I0001.A001 // DISP=OLD //SYSUT2 DD DSN=DSNC318.DSNDBC.DSNDD41P.DSN8S41C.I0001.A001, // DISP=OLD //SYSXLAT DD * 260,280 2,10 3,55 6,56 7,57 /* ============================================================ Version 3 Book Title: Command and Utility Reference Pages: 348 Change Description: The description of the SUMMARY option for DSN1LOGP will change from: Scans the recovery log to determine what work is incomplete when DB2 restarts. To: The report summarizes all recovery information within the RBASTART and RBAEND specifications. Summary information can also be used to determine what work is incomplete when DB2 starts. You cannot limit the output of the summary report with any of the other options, except by using the FILTER option with a URID or LUWID specification. =============================================================== Version 3 Book Title: Command and Utility Reference Pages: 360 Change Description: Add as the second sentence in the description under NUMPARTS: NUMPARTS is required if the input data set is partitioned. ================================================================ Version 3 Book Title: Command and Utility Reference Pages: 403 Change Description: Under the heading "Output," the discussion of MODIFY that currently reads: The MODIFY utility does not delete SYSLGRNG records if a partition of data set is specified using DSNUM. will be changed to: The MODIFY utility does not delete SYSLGRNG records at the table space level if a partition or data set is specified using DSNUM. However, it does delete SYSLGRNG records for a specific partition if you run MODIFY on that partition. =============================================================== Version 3 Book Title: DB2 Command and Utility Reference Pages: 472-473 Change Description: The description under NEAROFFPOS, paragraph 3, will change from For segmented table spaces, a page is considered near-off the present page if the difference between the two page numbers is greater than or equal to 2, and less than SEGSIZE / 2. to For segmented table spaces, a page is considered near-off the present page if the difference between the two page numbers is greater than or equal to 2, and less than SEGSIZE * 2. The description for FAROFFPOS, paragraph 3, will change from For segmented table spaces, a page is considered far-off the present page if the two page numbers differ by SEGSIZE / 2 or more. To: For segmented table spaces, a page is considered far-off the present page if the two page numbers differ by SEGSIZE * 2 or more. ===============================================================
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
close for INTERNET viewing
APAR Information
APAR number
II08602
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
1995-04-04
Closed date
1997-10-31
Last modified date
1997-10-31
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"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"001"}]
Document Information
Modified date:
09 September 2020