APAR status
Closed as canceled.
Error description
This APAR documents changes to the DB2 Administration Guide Volume 2 SC26488800 which did not make Version 3 GA pubs. 5740xyr00 R310 This APAR is continued in II08064. ================================================================ Version 3 Book Title: DB2 Administration Guide Pages: 4-30 - 4-31 Change Description: In Chapter 4-2, "Implementing Your Design," in the section "Creating DB2 Storage Groups," under the description of the VOLUMES clause of the CREATE STOGROUP statement, change the paragraph on the bottom of page 4-30 to read: To allow SMS to manage your storage groups, you can use asterisks (non-specific volume IDs) in the VOLUMES clause. However, do not mix specific and non-specific volume IDs, whether in a new or existing storage group. For information about using SMS to manage your storage groups, see "Managing Your DB2 Data Sets with SMS" on page 4-31. If you are using shared read-only data, see "Create DB2 Storage Groups" on page 3-56 in section 3-2 of this book for additional storage management considerations. Same section, under "Managing Your DB2 Data Sets with SMS" on page 4-31, change the paragraph starting "To allow SMS to manage your DB2 storage groups," and the example that follows it, to read as follows: To allow SMS to manage your DB2 storage groups, you can use one or more asterisks in the volume ID clause in your CREATE STOGROUP or ALTER STOGROUP statement, as shown here: For all cases except For the owner of shared read-only data shared read-only data ----------------------------------------------------------- CREATE STOGROUP G202 CREATE STOGROUP G202 VOLUMES ("*") VOLUMES ("*","*",...) VCAT DB2SMST; VCAT DB2SMST; This example causes all database data set allocations and definitions to use non-specific selection through SMS filtering services. If you are using shared read-only data, see "Create DB2 Storage Groups" on page 3-56 in section 3-2 of this book. ================================================================ Version 3 Book Title: DB2 Administration Guide Page: 4-33 Change Description: Under "Requirements for Your Own Data Sets," the following list item will be inserted as item 3 before the existing item 3: 3. You must use the DEFINE CLUSTER command to define the size of the primary and secondary extents of the VSAM cluster. If you specify zero for the secondary extent size, data set extension does not occur. 4. If you specify passwords... etc. (unchanged) ================================================================ Version 3 Book Title: DB2 Administration Guide Page: 4-40 (chapter 4-2) Change Description: In the "Creating Table Spaces" section, under "When DB2 Manages the Data Sets," replace PRIQTY and SECQTY in Figure 118 as follows: PRIQTY 3072 SECQTY 1024 =============================================================== Version 3 Book Title: DB2 Administration Guide Pages: 4-67 Change Description: In the "Creating Indexes" section of Chapter 4-2, under "Partitioned Indexes," change the first sentence of the top paragraph on the page to read: The example below shows how to create a partitioned index on the employee number column (EMPNO) of the employee table. ================================================================ Version 3 Book Title: DB2 Administration Guide Page: 4-134 Change Description: Omission correction; in "Altering Views" section under "Change the Qualifier for System Data Sets" -- Step 3, second paragraph, 2nd sentence currently reads: "You do not have to run these steps because" It now reads: You do not have to run these steps because they are unnecessary for changing the high-level qualifier. ================================================================ Version 3 Book Title: Admin Guide Volume II, Section 5, "Security and Auditing" Pages: 5-59 Change Description: Under "Required CICS Specifications", replace the four bulleted sentences with the following three: * The CICS system initialization table must specify external security. For CICS Version 4, specify SEC=YES; for earlier releases of CICS, specify EXTSEC=YES. If you are using the CICS multiple region option (MRO), you must specify SEC=YES or EXTSEC=YES for every CICS system that is connected by interregion communication (IRC). * If your version of CICS uses a sign-on table (SNT), then the CICS sign-on table must specify EXTSEC=YES for each signed on user that will use the sign-on exit. * When the user signs on to a CICS terminal-owning region (TOR), the TOR must propagate the authorization ID to the CICS application-owning region (AOR). For more information on that propagation, see the description of ATTACHSEC in the applicable version of the CICS Intercommunication Guide. =============================================================== Version 3 Book Title: Admin Guide Volume II, Section 5, "Security and Auditing" Pages: 5-60 Change Description: In Step 1, change the text following the bold-faced phrase, "For CICS sign-ons," to read as follows: FOR CICS SIGN-ONS, the intitial primary authorization ID is specified by authorization directives in the CICS resource control table (RCT). For instructions on setting up the RCT to indicate the appropriate ID, see the description of the AUTH option in the DSNCRCT macro "DSNCRCT TYPE=ENTRY" on page 2-324 and the information in "Coordinating DB2 and CICS Security" on page 2-312. You can use the following values for authorization IDs: * The VTAM application name for the CICS system; use AUTH=SIGNID. * A character string up to 8 characters long, supplied in the RCT; use AUTH=(string). * The CICS group ID (8 characters); use AUTH=GROUP. That option passes to DB2 not only the CICS user ID, but also the associated RACF connected group name. AUTH=GROUP is not a valid authorization type for transactions that do not have RACF user IDs associated with them (for example, non-terminal-driven transactions in releases of CICS before CICS Version 4). * The CICS user ID (8 characters); use AUTH=USERID. AUTH=USERID is not a valid authorization type for transactions that do not have signed-on user IDs associated with them (for example, non-terminal-driven transactions in releases of CICS before CICS Version 4). * The operator ID (3 characters padded on the right with 5 blanks); use AUTH=USER. AUTH=USER is valid only for transactions associated with a signed-on USERID or a terminal. * The terminal ID (4 characters padded with 4 blanks); use AUTH=TERM. AUTH=TERM is valid only for transactions associated with a terminal. * The transaction ID (4 characters padded with 4 blanks); use AUTH=TXID. =============================================================== Version 3 Book Title: DB2 Administration Guide, Volume 2 Pages: 5-65 Change Description: Add the following sentence to the description of the field TYPE, under "Columns Used in SYSIBM.SYSUSERNAMES": The field should contain only I or O; any other character, including blank, causes the row to be ignored. =============================================================== Version 3 Book Title: DB2 Administration Guide, Volume 2 Pages: 5-77 Change Description: Replace the second sentence of the first paragraph under "Add Entries to the RACF Router Table" ("Figure 164 on page 5-78 shows...") with the following: Figure 164 on page 5-78 shows the ICHRFRTB macros to generate entries in the RACF router table (ICHRFR01) for the DB2 subsystems DSN, DB2P, and DB2T. This table controls the action taken when DB2 invokes the RACROUTE macro. (Refer to System Programming Library: Resource Access Control Facility (RACF) for a description of how to generate the RACF router table and the RACROUTE macro). =============================================================== Version 3 Book Title: DB2 Administration Guide, Volume 2 Pages: 5-78 Change Description: Replace the entire contents of Figure 164 with the following: * * REASSEMBLE AND LINKEDIT THE INSTALLATION-PROVIDED * ROUTER TABLE ICHRFR01 TO INCLUDE DB2 SUBSYSTEMS IN THE * DSNR RESOURCE CLASS. * * PROVIDE ONE ROUTER ENTRY FOR EACH DB2 SUBSYSTEM NAME. * THE REQUESTOR-NAME MUST ALWAYS BE "IDENTIFY". ICHRFRTB CLASS=DSNR,REQSTOR=IDENTIFY,SUBSYS=DSN,ACTION=RACF ICHRFRTB CLASS=DSNR,REQSTOR=IDENTIFY,SUBSYS=DB2P,ACTION=RACF ICHRFRTB CLASS=DSNR,REQSTOR=IDENTIFY,SUBSYS=DB2T,ACTION=RACF =============================================================== Version 3 Book Title: DB2 Administration Guide, Volume 2 Pages: 5-79 Change Description: Replace the first sentence of the paragraph just before Table 134 with the following: To change the RACF started procedures table (ICHRIN03), change, reassemble, and link edit the resulting object code to MVS. Figure 165 on page 5-81 shows the sample entries for three DB2 subsystems and optional entries for CICS and IMS. (Refer to System Programming Library: Resource Access Control Facility (RACF) for a description of how to code a RACF started procedures table.) =============================================================== This APAR is continued in II08064.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
close for INTERNET viewing
APAR Information
APAR number
II07836
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-04-27
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"},"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