HOLDDATA FOR IMS 9.1 PUT Level ** Please read all of the HOLDDATA before acting on any of it. **

Transcription

1 HOLDDATA FOR IMS 9.1 PUT Level 0706 ** Please read all of the HOLDDATA before acting on any of it. ** ************************************************************************ Please pay close attention to the holddata for the following PTFs with action items. UK26128 (UK25100) UK26154 UK26164 (UK25100) UK26372 UK26649 (UQ95312) UK26656 ********** HOLDDATA **************************************************** UK22490 TYPE = PTF DATE/TIME REC = :17:49 SOURCEID = HIPER PRP PUT0703 RSU0704 SMCCOR FMID VER(001) = JMK9902 PRE VER(001) = UQ88624 REQ VER(001) = UQ91510 UQ92496 SUPING VER(001) = DQ88676 DQ92589 UK12938 UK18197 UQ91511 UQ92497 VK17556 VK26694 VK34173 VQ88676 VQ92589 MOD = DFSCON00 SRCUPD = DFSCON00 HOLDERROR = VK HOLD(UK22490) FMID(JMK9902) REASON(VK40635) ERROR DATE(07065) (SMRTDATA(CHGDT(070306))) CLASS(PE). HOLDSYSTEM(INT) = DOC ++ HOLD(UQ92497) SYS FMID(JMK9902) REASON(DOC) DATE(07163) (DOCUMENTATION CHANGE FOR APAR PQ92589 ZES Publication Changes: Doc Change for Failure Analysis Structure Table (FAST) for Dump Analysis Version 9. Under DFSQGU00 Analysis Add label: GU695 to subcode 043). UK26047 TYPE = PTF DATE/TIME REC = :51:54 SOURCEID = PUT0706 SMCCOR FMID VER(001) = JMK9902 PRE VER(001) = UQ88624 REQ VER(001) = UK26046 UQ91510 UQ92496 SUPING VER(001) = DK42859 DQ88676 DQ92589 UK12938 UK18197 UK22490 UQ91511 UQ92497 VK17556 VK26694 VK34173 VK42859 VQ88676 VQ92589 MOD = DFSCON00 SRCUPD = DFSCON00 HOLDSYSTEM(INT) = DOC ++ HOLD(UQ92497) SYS FMID(JMK9902) REASON(DOC) DATE(07163) (DOCUMENTATION CHANGE FOR APAR PQ92589 ZES

2 Publication Changes: Doc Change for Failure Analysis Structure Table (FAST) for Dump Analysis Version 9. Under DFSQGU00 Analysis Add label: GU695 to subcode 043). UK26073 TYPE = PTF DATE/TIME REC = :51:55 SOURCEID = HIPER PUT0706 SMCCOR PRE VER(001) = UK04739 UQ91776 UQ91777 SUPING VER(001) = DK25530 DK46155 UK15073 MOD = DBFNCBS0 SRCUPD = DBFNCBS0 HOLDSYSTEM(INT) = MULTSYS ++ HOLD(UK26073) SYS FMID(HMK9900) REASON(MULTSYS) DATE(07164) (++ HOLD(DA46155) SYS FMID(HMK9900) REASON(MULTSYS) DATE(07151) ( ++ +HOLD FOR APAR PK IF NOT FAST PATH DEDB DATA SHARING IGNORE THE REST OF THIS HOLD ++ +PK46155 MAY BE INSTALLED ON EACH IMS DATA SHARING PARTNER ONE + +AT A TIME. IT WILL BECOME FULLY AFFECTIVE TO PROTECT AGAINST + +THE REPORTED PROBLEM WHEN ITS INSTALLATION HAS COMPLETED ON + +ALL IMS DATA SHARING PARTNERS IN THE SYSTEM ).). UK26128 TYPE = PTF DATE/TIME REC = :51:56 SOURCEID = HIPER PUT0706 SMCCOR FMID VER(001) = JMK9901 PRE VER(001) = UK24282 UQ86097 UQ94594 REQ VER(001) = UK25099 UK26127 SUPING VER(001) = AK24342 AK39785 AK40503 AK42400 DK24342 DK42400 UK25020 UK25100 UK25149 MOD = DFSDLR00 SRCUPD = DFSDLR00 HOLDSYSTEM(INT) = ACTION ++ HOLD(UK25100) SYS FMID(JMK9901) REASON(ACTION) DATE(07166) (********************************************************* APAR PK24342 changes the *size* and/or *content* of an IMS log record. Log record type (in hex): DFSLOG07 Macro changed: Old size: x'11f' New size: x'123' Fields deleted: Fields moved: Fields added: DLRRLSE Any user modifications or nonibm vendor software which references this block must be changed and/or reassembled to include the new size. ********************************************************* ********************************************************* APAR PK24342 changes the *size* of an IMS control block. Control Block name: DFSDACCT Macro changed: Old size: x'289'

3 New size: x'292' Any user modifications or nonibm vendor software which references this block must be changed and/or reassembled to include the new size. *********************************************************). HOLDSYSTEM(INT) = DOC ++ HOLD(UK25100) SYS FMID(JMK9901) REASON(DOC) DATE(07166) (DOCUMENTATION CHANGE FOR APAR PK24342 ================================================= * SC * Application Programming: DB * * GC * Messages and Codes Volume 1 * * SC * Utilities Reference: System * ================================================= DOCUMENTATION UPDATE FOR RLSE CALL MANUAL: Messages and Codes Volume 1 (GC ) "Appendix E. DL/I Codes" "Return and Reason Code Tables" For return code '0000', reason code '0000' add RLSE call to LIST OF DATABASE CALLS. For return code '0104', reason code '0208' add RLSE call to LIST OF DATABASE CALLS. For return code '0104', reason code '020C' add RLSE call to LIST OF DATABASE CALLS. For return code '0900', add RLSE call to LIST OF DATABASE CALLS. MANUAL: Application Programming: DB (SC ) "Writing Application Programs" "DL/I Calls" "DB Call Functions" Add: RLSE Release all locks held for unmodified data "Writing DL/I Calls for Database Management" In this Chapter Add:. "RLSE Call" in topic Then add topic for a RLSE call with the following: "Format" >>RLSEDB PCB>< AIB CALL NAME DB/DC DBCTL DB BATC For Full Function and DEDB: RLSE X X X

4 "Parameters" DB PCB Specifies the DB PCB for the call. This parameter is an input and output parameter. AIB Specifies the AIB for the call. This is an input and output parameter. These fields must be initialized in the AIB: AIBID Eye Catcher. This 8byte field must contain DFSAIB. AIBLEN AIB lengths. This field must contain the actual length of the AIB that the application program obtained. AIBRSNM1 Resource name. This 8byte, left justified, field must contain the name of a DB PCB. Restrictions The RLSE call has to be issued using a DB PCB. The PCB cannot be an I/O PCB or an MSDB PCB. "Usage" You use the RLSE call in FP to release all of the loc held for unmodified data that are owned by an applica In FF this will just be the locks held by the DB PCB is referenced in the call. If the lock is protecting resource that has been updated the lock will not be released. After the RLSE call all database position is lost. "Processing Fast Path Databases" "Fast Path Coding Considerations" Add RLSE call to the call list in the following paragraph: "You can use these calls to process a DEDB:". RLSE "Reference" "Database Management Call Summary" Add the RLSE call to the "Summary of DB calls" table Function Meaning Code and Use Options Parameters Valid For RLSE RELEASE RELEASED ALL FUNCTION, DB/DC, LOCKS LOCKS HELD DB PCB DBCTL, FOR UNMODIFIED DB BATCH, DATA ODBA "DL/I Test program (DFSDDLT0)" "DL/I Call Functions" Add RLSE to table "DL/I CALL FUNCTIONS"

5 AIB PCB DATA Call SUPPORT SUPPORT STMT DESCRIPTION RLSE yes yes N Releases all locks held by an application that are for unmodified data. "Examples of DL/I Call Functions" RLSE Call: Use a CALL FUNCTION statement to contain the RLSE function L RLSE MANUAL: Utilities Reference: System (SC ) "Interpreting //DFSSTAT Reports" "Report Descriptions" PSTAccounting Report Add to *** PST ACCOUNTING STATISTICS *** following: DB REPL CALLS 1 add: DB RLSE CALLS 0). HOLDSYSTEM(INT) = ENH ++ HOLD(UK25100) SYS FMID(JMK9901) REASON(ENH) DATE(07166) (********************************************************* APAR PK24342 adds new IMS RLSE function. Function name: RLSE See APAR closing text or PTF cover letter for complete details. *********************************************************). UK26154 TYPE = PTF DATE/TIME REC = :51:57 SOURCEID = PUT0706 SMCCOR PRE VER(001) = UK22269 SUPING VER(001) = DK45321 MOD = DSP00MVS HOLDSYSTEM(INT) = ACTION ++ HOLD(UK26154) SYS FMID(HMK9900) REASON(ACTION) DATE(07166) (* Hold for APAR PK45321 * THIS FIX CONTAINS 1 MODULE REQUIRING SPECIAL RELINKING ACTIVITY TO INSTALL INTO THE z/os SYSTEM. MODULE AFFECTED: DSP00MVS SEE IMS Installation Volume, "Installing Required IMS Links to z/os", SECTION "Binding the DBRC Type 4 SVC " for specific instructions. NOTE: the module name in SDFSRESL will be IGC00xxx as opposed to DSP00MVS where xxx is your type 4 SVC.

6 A z/os IPL WITH CLPA OPTION SPECIFIED IS REQUIRED TO ACTIVATE THE NEW VERSION OF DSP00MVS/IGC00xxx. The DBRC Type4 SVC, can also be dynamically updated using the Dynamic SVC DFSUSVC0 utility. Thus, you can apply maintenance to the DBRC type4 SVC module without having to restart z/os. See IMS System Utilities for specific instructions on using DFSUSVC0.). UK26164 TYPE = PTF DATE/TIME REC = :51:57 SOURCEID = HIPER PUT0706 SMCCOR FMID VER(001) = JMK9901 PRE VER(001) = UK24282 UQ86097 UQ94594 REQ VER(001) = UK25099 UK26127 SUPING VER(001) = AK24342 AK30649 AK39785 AK40503 AK42400 DK24342 DK42400 UK25020 UK25100 UK25149 UK26128 MOD = DFSDLR00 SRCUPD = DFSDLR00 HOLDSYSTEM(INT) = ACTION ++ HOLD(UK25100) SYS FMID(JMK9901) REASON(ACTION) DATE(07166) (********************************************************* APAR PK24342 changes the *size* and/or *content* of an IMS log record. Log record type (in hex): DFSLOG07 Macro changed: Old size: x'11f' New size: x'123' Fields deleted: Fields moved: Fields added: DLRRLSE Any user modifications or nonibm vendor software which references this block must be changed and/or reassembled to include the new size. ********************************************************* ********************************************************* APAR PK24342 changes the *size* of an IMS control block. Control Block name: DFSDACCT Macro changed: Old size: x'289' New size: x'292' Any user modifications or nonibm vendor software which references this block must be changed and/or reassembled to include the new size. *********************************************************). HOLDSYSTEM(INT) = DOC ++ HOLD(UK25100) SYS FMID(JMK9901) REASON(DOC) DATE(07166) (DOCUMENTATION CHANGE FOR APAR PK24342 ================================================= * SC * Application Programming: DB * * GC * Messages and Codes Volume 1 * * SC * Utilities Reference: System * =================================================

7 DOCUMENTATION UPDATE FOR RLSE CALL MANUAL: Messages and Codes Volume 1 (GC ) "Appendix E. DL/I Codes" "Return and Reason Code Tables" For return code '0000', reason code '0000' add RLSE call to LIST OF DATABASE CALLS. For return code '0104', reason code '0208' add RLSE call to LIST OF DATABASE CALLS. For return code '0104', reason code '020C' add RLSE call to LIST OF DATABASE CALLS. For return code '0900', add RLSE call to LIST OF DATABASE CALLS. MANUAL: Application Programming: DB (SC ) "Writing Application Programs" "DL/I Calls" "DB Call Functions" Add: RLSE Release all locks held for unmodified data "Writing DL/I Calls for Database Management" In this Chapter Add:. "RLSE Call" in topic Then add topic for a RLSE call with the following: "Format" >>RLSEDB PCB>< AIB CALL NAME DB/DC DBCTL DB BATC For Full Function and DEDB: RLSE X X X "Parameters" DB PCB Specifies the DB PCB for the call. This parameter is an input and output parameter. AIB Specifies the AIB for the call. This is an input and output parameter. These fields must be initialized in the AIB: AIBID Eye Catcher. This 8byte field must contain DFSAIB. AIBLEN AIB lengths. This field must contain the actual length of the AIB that the application program obtained.

8 AIBRSNM1 Resource name. This 8byte, left justified, field must contain the name of a DB PCB. Restrictions The RLSE call has to be issued using a DB PCB. The PCB cannot be an I/O PCB or an MSDB PCB. "Usage" You use the RLSE call in FP to release all of the loc held for unmodified data that are owned by an applica In FF this will just be the locks held by the DB PCB is referenced in the call. If the lock is protecting resource that has been updated the lock will not be released. After the RLSE call all database position is lost. "Processing Fast Path Databases" "Fast Path Coding Considerations" Add RLSE call to the call list in the following paragraph: "You can use these calls to process a DEDB:". RLSE "Reference" "Database Management Call Summary" Add the RLSE call to the "Summary of DB calls" table Function Meaning Code and Use Options Parameters Valid For RLSE RELEASE RELEASED ALL FUNCTION, DB/DC, LOCKS LOCKS HELD DB PCB DBCTL, FOR UNMODIFIED DB BATCH, DATA ODBA "DL/I Test program (DFSDDLT0)" "DL/I Call Functions" Add RLSE to table "DL/I CALL FUNCTIONS" AIB PCB DATA Call SUPPORT SUPPORT STMT DESCRIPTION RLSE yes yes N Releases all locks held by an application that are for unmodified data. "Examples of DL/I Call Functions" RLSE Call: Use a CALL FUNCTION statement to contain the RLSE function.

9 L RLSE MANUAL: Utilities Reference: System (SC ) "Interpreting //DFSSTAT Reports" "Report Descriptions" PSTAccounting Report Add to *** PST ACCOUNTING STATISTICS *** following: DB REPL CALLS 1 add: DB RLSE CALLS 0). HOLDSYSTEM(INT) = ENH ++ HOLD(UK25100) SYS FMID(JMK9901) REASON(ENH) DATE(07166) (********************************************************* APAR PK24342 adds new IMS RLSE function. Function name: RLSE See APAR closing text or PTF cover letter for complete details. *********************************************************). UK26233 TYPE = PTF DATE/TIME REC = :51:57 SOURCEID = PUT0706 SMCCOR SUPING VER(001) = DK14259 DK15134 DK17453 DK19559 DK28574 DK38715 DK44863 UK10551 UK11481 UK12337 UK12338 UK17292 UK22943 MOD = DFSKSCR0 HOLDSYSTEM(INT) = DOC ++ HOLD(UK10551) SYS FMID(HMK9900) REASON(DOC) DATE(07172) (DOCUMENTATION CHANGE FOR APAR PK14259 SC GC On the "IMS V9 Utilities Reference: System", chapter "6.4 IMS Records User Data Scrub Utility (DFSKSCR0)" The list of record considered is updated as follows: The IMS Records User Data Scrub utility (DFSKSCR0) scans all the records and eliminates those parts of the records that contain sensitive or confidential user data such as customer business informatio DFSKSCR0 specifically removes log records X'01', X'03', x'4002', X'50', X'5903', X'5950', and X'67'. The example in section " Example of DFSKSCR0" is changed CONTROL CNTL STOPAFT=EOF ************************************************** * IMSV9 INPUT LOG DATA SET NAME(S): * * IMSVS.TEST.LOG ************************************************** * * * RECORDS USER DATA SCRUB * * * **************************************************

10 OPTION COPY E=DFSKSCR0 * DFS707I END OF FILE ON INPUT #01 RECORDS PROCESSED: 33 #03 RECORDS PROCESSED: 16 #4002 RECORDS PROCESSED: 3 #50 RECORDS PROCESSED: 0 #5901 RECORDS PROCESSED: 2 #5903 RECORDS PROCESSED: 2 #5950 RECORDS PROCESSED: 0 #67 RECORDS PROCESSED: 7 DFS708I OPTION COMPLETE DFS703I END OF JOB Figure 228. Report Produced Using DFSKSCR0 Also in the "IMS V9 Release Planning Guide manual", chapter "2.8.1 Overview" add the new record to the list. IMS Records User Data Scrub Utility (DFSKSCR0) The IMS Records User Data Scrub utility (DFSKSCR0) performs a all of the IMS logs. The utility deletes those record parts th contain sensitive or confidential customer business transactio tion, in particular, X'01', X'03', x'4002', X'50', X'5901', X' X'5950', and X'67'. The deletion does not compromise the integ the content of the vital IMS system data. This scrub is useful you must send IMS log data to an outside organization for anal). UK26300 TYPE = PTF DATE/TIME REC = :51:58 SOURCEID = PUT0706 SMCCOR SUPING VER(001) = DK14259 DK15134 DK17453 DK19559 DK28574 DK38715 DK44863 DK45036 UK10551 UK11481 UK12337 UK12338 UK17292 UK22943 UK26233 MOD = DFSKSCR0 HOLDSYSTEM(INT) = DOC ++ HOLD(UK10551) SYS FMID(HMK9900) REASON(DOC) DATE(07172) (DOCUMENTATION CHANGE FOR APAR PK14259 SC GC On the "IMS V9 Utilities Reference: System", chapter "6.4 IMS Records User Data Scrub Utility (DFSKSCR0)" The list of record considered is updated as follows: The IMS Records User Data Scrub utility (DFSKSCR0) scans all the records and eliminates those parts of the records that contain sensitive or confidential user data such as customer business informatio DFSKSCR0 specifically removes log records X'01', X'03', x'4002', X'50', X'5903', X'5950', and X'67'. The example in section " Example of DFSKSCR0" is changed CONTROL CNTL STOPAFT=EOF ************************************************** * IMSV9 INPUT LOG DATA SET NAME(S): * * IMSVS.TEST.LOG ************************************************** * * * RECORDS USER DATA SCRUB * * *

11 ************************************************** OPTION COPY E=DFSKSCR0 * DFS707I END OF FILE ON INPUT #01 RECORDS PROCESSED: 33 #03 RECORDS PROCESSED: 16 #4002 RECORDS PROCESSED: 3 #50 RECORDS PROCESSED: 0 #5901 RECORDS PROCESSED: 2 #5903 RECORDS PROCESSED: 2 #5950 RECORDS PROCESSED: 0 #67 RECORDS PROCESSED: 7 DFS708I OPTION COMPLETE DFS703I END OF JOB Figure 228. Report Produced Using DFSKSCR0 Also in the "IMS V9 Release Planning Guide manual", chapter "2.8.1 Overview" add the new record to the list. IMS Records User Data Scrub Utility (DFSKSCR0) The IMS Records User Data Scrub utility (DFSKSCR0) performs a all of the IMS logs. The utility deletes those record parts th contain sensitive or confidential customer business transactio tion, in particular, X'01', X'03', x'4002', X'50', X'5901', X' X'5950', and X'67'. The deletion does not compromise the integ the content of the vital IMS system data. This scrub is useful you must send IMS log data to an outside organization for anal). UK26372 TYPE = PTF DATE/TIME REC = :51:59 SOURCEID = PUT0706 SMCCOR PRE VER(001) = UK17000 UK22157 UK23780 UK25779 SUPING VER(001) = DK27493 DK33979 DK40030 UK23782 UK25314 MAC = HWSEXPRM MOD = HWSIMSO0 HWSIMSO1 HWSSDRCV HWSSOAP1 SAMP = HWSSMPL0 HWSSMPL1 HOLDSYSTEM(INT) = ACTION ++ HOLD(UK26372) SYS FMID(HMK9900) REASON(ACTION) DATE(07172) (++ + HOLD FOR APAR PK HWSIMSO0, HWSIMSO1, HWSSMPL0, HWSSMPL1, HWSSOAP1 are + + modified. + + If your installation is currently using the HWSSMPL0 or + + HWSSMPL1 or you have written your own user message exits + + that function in a manner similar to HWSSSMP0, and HWSSMPL1 + + user message exits, then take action as necessary for + + your installation. + + EXPREA_SVT field has been changed the offset in HWSEXPRM, + + if the field was referenced by the your own user message + + exits, take action as necessary for your installation. + ++). HOLDSYSTEM(INT) = DOC ++ HOLD(UK26372) SYS FMID(HMK9900) REASON(DOC) DATE(07172) (DOCUMENTATION CHANGE FOR APAR PK40030 SC Contents of Parmlist Pointed to by Register 1

12 at READ Subroutine Table 19. will be changed as follows. From EXPREA_SVT 4 bytes Address of SVT. To EXPREA_RESV0 4 bytes Reserved space Contents of Parmlist Pointed to by Register 1 at READ Subroutine Table 20. will be changed as follows. Add the followings after EXPREA_CLID. EXPREA_SVT 4 bytes Address of SVT. EXPREA_LSTNPORT 2 bytes Binary. Specifies the listening port number.). UK26394 TYPE = PTF DATE/TIME REC = :52:00 SOURCEID = PUT0706 SMCCOR PRE VER(001) = UK00896 UK12061 UQ93745 UQ94066 SUPING VER(001) = AK37703 DK37703 MOD = DFSIDP50 DFSIQ070 SRCUPD = DFSIDP50 HOLDSYSTEM(INT) = DOC ++ HOLD(UK26394) SYS FMID(HMK9900) REASON(DOC) DATE(07172) (DOCUMENTATION CHANGE FOR APAR PK37703 SC In the IMS V9 Command Reference under "/DISPLAY DATABASE" The paragraph after Table 49 will be changed to: UK26480 TYPE = PTF DATE/TIME REC = :52:04 SOURCEID = HIPER PUT0706 SMCCOR The /DISPLAY DB OLR command displays the status of a specified partition locally. /DISPLAY DB OLR returns a list and status of all 'authorized' partitions that have HALDB Online Reorganization (OLR) in cursoractive status locally, or have cursoractive status and are not owned, to the originating terminal. A partition can be authorized by issuing a /START DB partname OPEN or UPDATE DB NAME(partname) OPTION(OPEN) command or by accessing the partition from a application. The SSYS record from a RECON listing can be used to determine if a partition is authorized and to which subsystem. Under Query DB, under the STATUS () keyword, the fourth paragraph will be changed to: The QUERY DB STATUS(OLR) command displays the status of all 'authorized' partitions with HALDB OLR in progress. Rate information is not returned. Instead, the rate information is returned on the QUERY OLREORG command output. A partition can be authorized by issuing a /START DB partname OPEN or UPDATE DB NAME(partname) OPTION(OPEN) command or by accessing the partition from a application. The SSYS record from a RECON listing can be used to determine if a partition is authorized and to which subsystem.).

13 PRE VER(001) = UK26372 SUPING VER(001) = DK39457 MOD = HWSSDRCV HOLDSYSTEM(INT) = AO ++ HOLD(UK26480) SYS FMID(HMK9900) REASON(AO) DATE(07176) (********************************************************* + Hold for APAR PK This APAR changes or affects an IMS message. IMS Message number: HWSA0360E IMS Connect will no longer issue HWSA0360E message. Any user exits or nonibm vendor software which are sensitive to this message may need to be changed. See the APAR closing text or PTF cover letter for complete details *********************************************************). HOLDSYSTEM(INT) = DOC ++ HOLD(UK26480) SYS FMID(HMK9900) REASON(DOC) DATE(07176) (DOCUMENTATION CHANGE FOR APAR PK39457 SC GC UK26607 TYPE = PTF DATE/TIME REC = :52:06 SOURCEID = PRP PUT0706 SMCCOR PRE VER(001) = UK22121 UK25099 SUPING VER(001) = DK42150 MOD = DFSCDMP0 SRCUPD = DFSCDMP0 IMS V9 Connect Guide and Reference (SC ) IMS Connect Return and Reason Codes > HWSSOAP1 IMS Connect will no longer issue RSM RSN 109 "Adapter support is not enabled." IMS V9 Messages and Codes, Volume 1 (GC ) Integrated IMS Connect Messages IMS Connect will no longer issue HWSA0360E message.). HOLDSYSTEM(INT) = DEP ++ HOLD(UK26607) SYS FMID(HMK9900) REASON(DEP) DATE(07178) (++ + Hold for APAR PK This hold is applicable to ODBA users only. + + If NOT using ODBA the rest of this hold can be ignored This Service has a software dependency Please apply one of the following, Release dependent, + + z/os Context Services PTF's for APAR OA It must be applied in conjuction with this IMS APAR FIX + + or PTF to complete the required software maintenance + + to fix said problems documented in this APAR. +

14 + + + z/os Release PTF (707) UA (708) UA (709) UA (720) UA (730) UA (740) UA ). UK26649 TYPE = PTF DATE/TIME REC = :52:06 SOURCEID = SMCCOR PRE VER(001) = UK03006 UK08766 UK08852 UK10436 UK17840 UQ87195 UQ88824 UQ95529 SUPING VER(001) = DK08909 DK19166 DK32889 DK42488 DQ82624 DQ93751 UK08563 UK16308 UK23830 UQ83592 UQ95312 MACUPD = DFSDAWE DFSMDA MOD = DFSBIND0 DFSMDA00 DFSMDA10 DFSV4200 SRCUPD = DFSBIND0 DFSMDA00 DFSMDA10 DFSV4200 HOLDSYSTEM(INT) = ACTION ++ HOLD(UQ95312) SYS FMID(HMK9900) REASON(ACTION) DATE(07179) (++ + HOLD FOR APAR PQ PLEASE READ BELOW + + Users who have created a TYPE=SLDS,DDNAME=IMSLOGR dynamic + allocation member along with a DASD Monitor dynamic allocation + member (TYPE=DFSDCMON,DDNAME=IMSMON,UNIT=DASD), in the same + assembly of DFSMDA macros, need to rebuild the IMSLOGR dynamic + allocation member after installation of this maintenance. ++). HOLDSYSTEM(INT) = AO ++ HOLD(UK26649) SYS FMID(HMK9900) REASON(AO) DATE(07179) (********************************************************* + Hold for APAR PK This APAR adds two new IMS messages. IMS Message numbers: DFS2560I and DFS2743I. Any user exits or nonibm vendor software which are sensitive to this message may need to be changed. See the APAR closing text or PTF cover letter for complete details *********************************************************). HOLDSYSTEM(INT) = DOC ++ HOLD(UK08563) SYS FMID(HMK9900) REASON(DOC) DATE(07179) (DOCUMENTATION CHANGE FOR APAR PK08909 GC DFS824I DFS824I PDS DIRECTORY READ ERROR DDN 'IMSACB ' RC=xx RSN=yy). HOLDSYSTEM(INT) = DOC ++ HOLD(UK26649) SYS FMID(HMK9900) REASON(DOC) DATE(07179) (DOCUMENTATION CHANGE FOR APAR PK42488 GC GC GC SC

15 LY Update the V91 Messages and Codes manual to add a new message code. DFS2743I READING THE OLCSTAT MDA MEMBER Explanation: The OLCSTAT DD statement is coded in the batch JCL, but the data set cannot be accessed. An attempt is being made to read the MDA member if it exists. System Action: Processing continues. Programmer Response: None. Module: DFSBIND0 DFS2560I WAITING FOR THE OLCSTAT DATA SET Explanation: The Global Online Change has the OLCSTAT data set allocated. This batch job will wait until the Global Online Change deallocates the OLCSTAT. System Action: Processing continues after the Global Online Change deallocated the OLCSTAT data set. Programmer Response: None. Module: DFSBIND0 Update the V91 Messages and Codes manual under abend 0821 to append the following under the first paragraph of the Explanation section: In order to determine which ACB library to read, IMS batch selects which OLCSTAT or MODSTAT data sets to read the online change status as follows: 1. From the OLCSTAT data set allocated via JCL if one exists. 2. From the OLCSTAT data set defined in the MDA member if one exists. 3. From the MODSTAT data set allocated via JCL if no OLCSTAT DD statement coded in JCL and no OLCSTAT MDA member defined. 4. The default is to use the ACBLIB from the IMSACB DD statement when there is no OLCSTAT and no MODSTAT DD statement coded in the JCL. An error may occur either because the data set name is incorrect or it cannot be accessed. System Action: Correct the OLCSTAT error. Update the V91 Release Planning Guide manual to add the following information: IMS batch determines which ACBLIB to read based upon the OLCSTAT, MODSTAT, or IMSACB DD statements. A long running multistep batch job results in JES allocating all the data sets up front, including the OLCSTAT data set, locking out Global Online Change. Global Onlin Change fails because it attempts to allocate the OLCSTAT data set with DISP=OLD. To prevent this usability problem for Global Online Change, when a batch job running for a long time can prevent Global Online Change from happening, apar PK42488 made changes to allow the OLCSTAT data set to be dynamically allocated. The OLCSTAT data set is only allocated while it is being used and is not allocated for the duration of the batch job. A batch job may continue to define the OLCSTAT data set with an OLCSTAT DD statement, or define a dynamic allocation member for the OLCSTAT data set. The MDA member for the OLCSTAT can be added only to the library

16 UK26656 TYPE = PTF DATE/TIME REC = :52:06 SOURCEID = HIPER SMCCOR PRE appropriate to the batch job being run or to the main library of the DFSMDA members. If you add to the main library, dynamic allocation of the OLCSTAT data set will be attempted for all batch jobs that use the main library. If you want only specific batch jobs to use the dynamic allocation of the OLCSTAT data set, add the MDA member only to the library appropriate to the batch jobs that require the OLCSTAT to be dynamically allocated. Update the V91 SYSTEM DEFINITION AND TAILORING manual to add under the OLCSTAT DD the following: The OLCSTAT data set, if defined, determines whether to use the IMSACBA or IMSACBB DD name. The OLCSTAT data set name is selected from one of two places: * The OLCSTAT DD statement coded in JCL * The dynamic allocation MDA member if either the OLCSTAT DD statement is omitted or the data set from the OLCSTAT DD cannot be accessed. The MODSTAT DD statement, if defined, determines whether to use the IMSACBA or IMSACBB DD name only when both of the following are true: * The OLCSTAT DD statement is omitted * No dynamic allocation MDA member is defined for the OLCSTAT data set. If the OLCSTAT DD statement or the MDA member exists, and the OLCSTAT data set cannot be accessed, the DBB batch job fails with an abendu0821. If both the MODSTAT and OLCSTAT DD statements are omitted, the IMSACB DD is used. Update the V91 UTILITIES: SYSTEM manual under Dynamic Allocation Macro DFSMDA about the OLCSTAT data set is as follows: TYPE=OLCSTAT statement This statement defines the dynamic allocation parameter list for the global online change OLCSTAT data set. DSNAME= Specifies the name of the OLCSTAT data set. The name can be any combination of simple and compound names valid in JCL, except that it cannot contain special characters. The format of this statement is: >>DFSMDATYPE=OLCSTAT,DSNAME=dsname>< Update the V91 FAST manual under ABENDU0821 to add the following information: Key Label Description Reg 5=A(SELACBDD) SELACBDD The OLCSTAT or MODSTAT data set could not be opened or contains invalid data or is coded as DD DUMMY. See previous error messages prior to the abendu0821 for an explanation.). VER(001) = UK07251 UK10124 UK10128 UK12016 UK17761 UK19612 UQ86866 UQ88396 UQ89992 UQ94593 UQ95706 UQ96048 UQ97159 SUPING VER(001) = DK36479 DK37560 DK40472 UK23015 UK23627 MOD = DFSDDUI0 DFSHRDB0 DFSPSEL0 DSPOLRSC

17 SRCUPD = DFSDDUI0 DFSHRDB0 HOLDSYSTEM(INT) = ACTION ++ HOLD(UK26656) SYS FMID(HMK9900) REASON(ACTION) DATE(07179) (++ + Hold for APAR PK This APAR has a requirement for special handling + + activity prior to or during installation, relating + + to the APPLY, ACCEPT, or both steps NOTE: This APAR needs to be applied on all IMS sharing + + systems, in order to address the duplicate ILK + + problem ). UK26680 TYPE = PTF DATE/TIME REC = :52:08 SOURCEID = SMCCOR FMID VER(001) = JMK9906 REQ VER(001) = UK26679 SUPING VER(001) = DK45002 JK45002 HFS = DFSICO15 DFSICO24 SHELLSCR = DFSICOS1 DFSICS24 HOLDSYSTEM(INT) = ENH ++ HOLD(UK26680) SYS FMID(JMK9906) REASON(ENH) DATE(07179) (********************************************************* APAR PK45002 adds new IMS function. Function name: Three new functions added See APAR closing text or PTF cover letter for complete details. *********************************************************). UK26759 TYPE = PTF DATE/TIME REC = :52:08 SOURCEID = SMCCOR PRE VER(001) = UK07911 UK10720 UK20095 UQ83716 UQ89967 UQ91776 UQ92678 SUPING VER(001) = DK00012 DK10754 DK34415 DQ83766 DQ88772 UK00368 UK07050 UQ86688 UQ89368 MOD = DBFMFLG0 DBFMSDP0 DBFUMDL0 DBFUMSC0 SRCUPD = DBFMFLG0 DBFMSDP0 DBFUMDL0 DBFUMSC0 HOLDSYSTEM(INT) = DOC ++ HOLD(UK26759) SYS FMID(HMK9900) REASON(DOC) DATE(07183) (DOCUMENTATION CHANGE FOR APAR PK34415 GC Document Number: GC V9 IMS Messages and Codes Reference, Volume 2: Appendix B. Fast Path Utility Status Codes > add new Status Code OB < OB The user specified STOPRBA value coincides with a preallocated SDEP CI boundary or its dummy segment which has a timestamp from a /DBR or RESTART and cannot be honored by the SDEP utility.).