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. Continued in II07864, II08602 & II09176. 5740xyr00 R310 ================================================================ Book Title: DB2 Version 3 Command and Utility Reference Page Number: 20 Change Description: A list of allowed characters for utilid was added to the description of utilid. A utility ID must begin with a letter. The remaining characters can be upper and lower case letters, numbers 0 through 9, and the following 7 characters: # $ @ ¢ ! ¬ . ================================================================ Book Title: Command and Utility Reference Page Number: 49 Change Description: In the second paragraph under the CURRENTDATA heading, remove the sentence "Data is always current for local processing" and modify the following sentence: Data might not be current for local or distributed processing if you ... =============================================================== Book Title: Command and Utility Reference Page Number: 49 Change Description: Add the following sentence at the end of the third paragraph under the CURRENTDATA heading: See "Usage Notes" on page 52 for important details. ================================================================ Book Title: Command and Utility Reference Page Number: 50 Change Description: Add the following sentence to the end of the first paragraph: See "Usage Notes" on page 54 for details on using REPLVER. =============================================================== Book Title: Command and Utility Reference Page Number: 54 Change Description: Add the following section to "Usage Notes" after "Alternative to BIND PACKAGE with REPLACE:" REPLVER: These notes describe four conditions in which REPLVER might be used. In these notes the DBRM member name is DBRM1; A and B represent two versions of the package. First Condition: Neither DBRM1 nor the package versions (A or B) exist in the DB2 catalog. If you bind version A of DBRM1 then the command BIND PACKAGE MEMBER(DBRM1) ACTION(REPLACE) REPLVER(B) produces message DSNT238I because version B does not exist in the DB2 catalog. Second Condition: DBRM1 and version B of the package exist in the DB2 catalog (but not version A). If you bind version A of DBRM1 then BIND PACKAGE MEMBER(DBRM1) ACTION(REPLACE) REPLVER(B) replaces version B with version A. As a result, version A of DBRM1 exists in the DB2 catalog but version B no longer exists in the catalog. Third Condition: DBRM1 and version A of the package exist in the DB2 catalog (but not version B). If you bind version A of DBRM1 then BIND PACKAGE MEMBER(DBRM1) ACTION(REPLACE) REPLVER(B) produces message DSNT238I because version B does not exist in the DB2 catalog. Fourth Condition: DBRM1 and both package versions (A and B) exist in the DB2 catalog. If you bind version A of DBRM1 then BIND PACKAGE MEMBER(DBRM1) ACTION(REPLACE) REPLVER(B) produces message DSNT228I because version A already exists. =============================================================== Version 3 Book Title: DB2 Command and Utility Reference Page: 54 Change Description: In Chapter 2, BIND PACKAGE (DSN), under Remote Binds, the following text should be inserted as the third paragraph: "When you perform a bind and specify the COPY option, if the local DB2 was installed with time or date format LOCAL, the LOCAL specification will be converted to ISO format for the package at the remote site." ================================================================ Version 3 Book Title:DB2 Command and Utility Reference Pages: 55 Change Description: Under AUTHORIZATION, add a footnote to the phrase, "The plan owner must have authorization to execute all SQL statements embedded in the plan...." The text of the footnote is: This excludes statements included in DBRMs that are bound to packages included in the package list of the plan. =============================================================== Book Title: Command and Utility Reference Page Number: 62 Change Description: In the second paragraph under the CURRENTDATA heading, remove the sentence "Data is always current for local processing" and modify the following sentence: Data might not be current for local or distributed processing if you ... =============================================================== Book Title: Command and Utility Reference Page Number: 62 Change Description: Add the following sentence at the end of the third paragraph under the CURRENTDATA heading: See "Usage Notes" on page 52 for important details. =============================================================== Version 3 Book Title: Command and Utility Reference Pages: 69 Change Description: The description for luwid is changed to read: luwid luwid consists of a fully qualified LU network name followed by a period and an LUW instance number. The LU network name consists of a 1 to 8 character network ID, a period, and a 1 to 8 character network LU name. The LUW instance number consists of 12 hexadecimal characters that uniquely identify the unit of work. ================================================================ Book Title: Command and Utility Reference Page Number: 80 Change Description: Change the first bullet under the "C:" heading to read: DCLGEN does not fold the arguments of the TABLE, STRUCTURE or NAMES parameters to uppercase. =============================================================== 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. ================================================================ Book Title: Command and Utility Reference Page Number: 129 Change Description: Add the following two paragraphs to the section "Protected Threads:" If you increase the active thread value using the DSNC MODIFY TRANSACTION command, the attributes of the TYPE=ENTRY macro are used. If the TYPE=ENTRY definition does not include a setting for an attribute, then the TYPE=INIT value is used. Issuing the DSNC MODIFY TRANSACTION command to increase the total threads permitted allows creation of unprotected threads. For example, assume THRDS=2, THRDA=2 and THRDM=6. If the total threads permitted is increased, the additional threads are unprotected. The DSNC MODIFY TRANSACTION command can also allow creation of protected threads. If THRDS=2, THRDA=2 and THRDM=6 and the value of THRDS is modified to 1, one of the protected threads is eliminated. If the value of THRDS is then modified back to 2, the thread which is recreated is protected. =============================================================== Version 3 Book Title: Command and Utility Reference Pages: 172 Change Description: Add the following sentence to the second paragraph under the version-id parameter description: DBRMs created in releases of DB2 prior to Version 2, Release 3 have a version-id of the empty string by default. ================================================================ Version 3 Book Title: DB2 Command and Utility Reference Pages: 184-5 Change Description: Add the following sentence after the first paragraph of the VALIDATE keyword description: "The default is the value used the last time the plan was bound or rebound." ================================================================ Version 3 Book Title: DB2 Command and Utility Reference Page: 193 Change Description: At the top of page 193, remove the sentence that says 'However, DB2 must be terminated temporarily before you issue this command.' Also remove step 1 below this paragraph. The steps should be the following: 1. Use access method services to rename or delete the failing BSDS, which DB2 has deallocated, and define a new BSDS with the same name as the failing BSDS. Control statements can be found in job DSNTIJIN. 2. Issue the DB2 command RECOVER BSDS... ================================================================ Version 3 Book Title: DB2 Command and Utility Reference Page: 202 Change Description: Add to the text under LIBRARY(library-name) a third paragraph to read as follows: Normal MVS library searching is also used for any subprograms loaded by the main program. If the subprograms reside in the same library as the main program, then library-name must also be defined for the normal MVS search pattern (STEPLIB, JOBLIB, link list). If a library defined in that way contains both the main program and any loaded subprograms, then you need not use the LIBRARY option. ================================================================ Version 3 Book Title: DB2 Command and Utility Reference Pages: 344 Change Description: Eliminate the keyword "DSN1LOGP" from the syntax diagram. =============================================================== Version 3 Book Title: DB2 Command and Utility Reference Pages: 344, 345 Change Description: The defaults shown for RBASTART and RBAEND are incorrect. Change the descriptions of the two defaults as follows: For RBASTART: The default is the RBA of the beginning of the data set. For RBAEND: The default is FFFFFFFFFFFF if RBASTART is specified. Otherwise it is the RBA of the end of the data set. =============================================================== continued in Info. APAR II07864 & II08602.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
close for INTERNET viewing
APAR Information
APAR number
II07612
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-02-11
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