*** Please read all of the HOLDDATA before acting on any of it. *** ************************************************************************

Transcription

1 HOLDDATA FOR IMS 7.1 PUT Level 0302 *** Please read all of the HOLDDATA before acting on any of it. *** ************************************************************************ Please pay close attention to the holddata for the following PTF's with action items. UQ73806 UQ73925 UQ74013 UQ74204 UQ74628 (IOGEN) ************************************************************************ ++ HOLD(UQ73806) SYS FMID(HMK7700) REASON(ACTION) DATE(03034) (AFTER THIS MAINTENANCE IS IMPLEMENTED ALL USERS USING ONLINE CHANGE THAT HAVE DATABASES WITH LOGICAL RELATIONSHIPS AND/OR A SECONDARY/PRIMARY INDEX WILL NEED TO DO AN ACBGEN FOR THOSE DATABASES.). ++ HOLD(UQ73853) SYS FMID(HMK7700) REASON(DOC) DATE(03038) (DOCUMENTATION CHANGE FOR APAR PQ68493 GC IMS Version 7 Messages and Codes Volume 2 Documentation change: IMS Version 7 Messages and Codes Volume 2 DFS0488I Message An additional reason for stopping an area is added. Code (Dec) Meaning 21 During /STA AREA command processing, an IXLFORCE command is issued to delete any failed persistent connections from a prior failed system. The IXLFORCE was not able to delete the failed persistent connection. In this case, the following messages are generated: DFS2783A UNABLE TO DELETE FAILEDPERSISTENT CONNECTION TO STR: SSSSSSSSSSSSSSSS REASON=RRRR DFS0488I STA COMMAND COMPLETED. AREA= XXXXXXXX RC=21). ++ HOLD(UQ73855) SYS FMID(JMK7701) REASON(DOC) DATE(03038) (DOCUMENTATION CHANGE FOR APAR PQ68493 GC IMS Version 7 Messages and Codes Volume 2 Documentation change: IMS Version 7 Messages and Codes Volume 2 DFS0488I Message An additional reason for stopping an area is added. Code (Dec) Meaning 21 During /STA AREA command processing, an IXLFORCE

2 command is issued to delete any failed persistent connections from a prior failed system. The IXLFORCE was not able to delete the failed persistent connection. In this case, the following messages are generated: DFS2783A UNABLE TO DELETE FAILEDPERSISTENT CONNECTION TO STR: SSSSSSSSSSSSSSSS REASON=RRRR DFS0488I STA COMMAND COMPLETED. AREA= XXXXXXXX RC=21). ++ HOLD(UQ46286) SYS FMID(HMK7700) REASON(ACTION) DATE(03037) (********************************************************* + Hold for APAR PQ This APAR changes or affects an IMS message. IMS Message number: DFS3721I 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 *********************************************************). ++ HOLD(UQ46286) SYS FMID(HMK7700) REASON(DOC) DATE(03037) (============================================================= DOCUMENTATION CHANGE FOR APAR PQ40547 GC : IMS V7 Messages and Codes Message DFS3721I was modified to keep it under 80 characters: DFS3721I STOP ADS REJECTED DUE TO ONLY 1 AVAIL ADS. AREA=xxxxxxxx DD=xxxxxxxx). ++ HOLD(UQ73925) SYS FMID(HMK7700) REASON(DOC) DATE(03037) (DOCUMENTATION CHANGE FOR APAR PQ51998 GC Document Number: GC IMS Version 7 Volume 2: Messages and Codes DFS3065I UTILITY ACTIVE IN AREA=areaname, COMMAND PENDING UTILITY TERMINATION Explanation: Fast PATH utility active for area. At utility I/O, status FH or AO will be issued and the command will be processe Utility terminates before completion. System Action: The /DBR or /STO command is processed but utility cleanup and disconnect occur before command execution. Programmer Response: None. Module: DBFARDA0). ++ HOLD(UQ73926) SYS FMID(JMK7701) REASON(DOC) DATE(03037) (DOCUMENTATION CHANGE FOR APAR PQ51998 GC

3 Document Number: GC IMS Version 7 Volume 2: Messages and Codes DFS3065I UTILITY ACTIVE IN AREA=areaname, COMMAND PENDING UTILITY TERMINATION Explanation: Fast PATH utility active for area. At utility I/O, status FH or AO will be issued and the command will be processe Utility terminates before completion. System Action: The /DBR or /STO command is processed but utility cleanup and disconnect occur before command execution. Programmer Response: None. Module: DBFARDA0). ++ HOLD(UQ73934) SYS FMID(HMK7700) REASON(DOC) DATE(03037) (DOCUMENTATION CHANGE FOR APAR PQ68317 GC The IMS Version 7 Volume 2 Messages and Codes manual, GC , is changed to update the Explanation for the Reason NO IC TAKEN AFTER A PITR for message DFS4266I. The Explanation is: Recovery for the database data set or area failed because a POINTINTIME (PITR) recovery was performed earlier and no image copy was taken afterwards. Because backout information may have been deleted from the RECON due to the prior PITR recovery, a new recovery may result in a corrupted database.). ++ HOLD(UQ73951) SYS FMID(HMK7700) REASON(DOC) DATE(03038) (DOCUMENTATION CHANGE FOR APAR PQ55998 GC GC Document Number: GC IMS Version 7 Install Volume 2: System Definition and Tailoring 4.23 Parameter Descriptions DMHVF = specifies how much storage of the FP VSO ERE DATASPACE is to be pagefixed. The value is in megabytes. The acceptable values are 099. This startup PARM is valid only on an XRF tracking system. The ERE DATASPACE is deleted at the end of the XRF TAKEOVER. At that time, the storage is also page freed. Document Number: GC IMS Version 7 Volume 2: Messages and Codes DFS2449I In the message text: cccccc Is one of the following values: PAGEFIX The request to pagefix storage in the VSO ERE DATASPACE

4 received a DSPSERV failure. xxxx The hex reason code displays if the CREATE or PAGEFIX command receives a DSPSERV macro error. These codes are defined by the DSPSERV macro. For additional information, see the OS/390: Programming: Authorized Assembler Services Reference, Volume 1 (ALESERVDYNALLOC) manual.). ++ HOLD(UQ73951) SYS FMID(HMK7700) REASON(EXRF) DATE(03038) (***************************************************** + Hold for APAR PQ WARNING: IF THIS IS AN ''XRF'' ENVIRONMENT, THIS MAINTENANCE MUST BE APPLIED TO THE ALTERNATE. INSTALLATION ON THE ACTIVE IS NOT REQUIRED AT THE SAME TIME. HOWEVER, IT IS RECOMMENDED THAT THE INSTALLATION OF THE MAINTENANCE ON BOTH SYSTEMS BE DONE IN A TIMELY MANNER, TO ASSURE THAT IN SITUATIONS WHERE THE ACTIVE BECOMES THE ALTERNATE, THIS FIX IS NOT LACKING. *****************************************************). ++ HOLD(UQ73952) SYS FMID(JMK7701) REASON(DOC) DATE(03038) (DOCUMENTATION CHANGE FOR APAR PQ55998 GC GC Document Number: GC IMS Version 7 Install Volume 2: System Definition and Tailoring 4.23 Parameter Descriptions DMHVF = specifies how much storage of the FP VSO ERE DATASPACE is to be pagefixed. The value is in megabytes. The acceptable values are 099. This startup PARM is valid only on an XRF tracking system. The ERE DATASPACE is deleted at the end of the XRF TAKEOVER. At that time, the storage is also page freed. Document Number: GC IMS Version 7 Volume 2: Messages and Codes DFS2449I In the message text: cccccc Is one of the following values: PAGEFIX The request to pagefix storage in the VSO ERE DATASPACE received a DSPSERV failure. xxxx The hex reason code displays if the CREATE or PAGEFIX command receives a DSPSERV macro error. These codes are defined by the DSPSERV macro. For additional information, see the OS/390: Programming: Authorized Assembler Services Reference, Volume 1 (ALESERVDYNALLOC) manual.). ++ HOLD(UQ73952) SYS FMID(JMK7701) REASON(EXRF) DATE(03038) (*****************************************************

5 + Hold for APAR PQ WARNING: IF THIS IS AN ''XRF'' ENVIRONMENT, THIS MAINTENANCE MUST BE APPLIED TO THE ALTERNATE. INSTALLATION ON THE ACTIVE IS NOT REQUIRED AT THE SAME TIME. HOWEVER, IT IS RECOMMENDED THAT THE INSTALLATION OF THE MAINTENANCE ON BOTH SYSTEMS BE DONE IN A TIMELY MANNER, TO ASSURE THAT IN SITUATIONS WHERE THE ACTIVE BECOMES THE ALTERNATE, THIS FIX IS NOT LACKING. *****************************************************). ++ HOLD(UQ73959) SYS FMID(HMK7700) REASON(DOC) DATE(03059) (DOCUMENTATION CHANGE FOR APAR PQ67428 GC IMS Version 7 Installation Volume 2: System Definition and Tailoring GC IMS Version 7 Messages and Codes Volume 2 Documentation change: IMS Version 7 Messages and Codes Volume 2 1 New message DFS2853A DFS2853A A NEW STRUCTURE WAS CREATED FOR AREA AAAAAAAA. REPLY 'C' TO CONTINUE OR 'R' TO RECOVER. Explanation: This message is generated because the user specified the SVSODR startup option of 'WTOR'. This option is used at a remote site to provide the user with an option as to whether an SVSO area needs to be marked as recovery needed or not. The user is given an option whenever a new structure is created for an SVSO area at emergency restart and SVSODR=WTOR is specified. System Action: If the user selects option 'C', IMS will open the area specified, connect to a new structure and normal processing will resume for that area. If the user selects option 'R', the specified area will be stopped and marked as recovery needed. Programmer Response: Reply 'C' to continue with normal processing for the area. Reply 'R' if the area is to be marked as recovery needed. Module: DBFVXCS0 2 New reason code 14 for message DFS2574I DFS2574I AREA=AAAAAAAA STOPPED, RECOVERY NEEDED, RSN=14 Explanation: Reason 14 indicates that an area has been stopped and marked as recovery needed due to one of the SVSODR options. These options take effect at emergency restart processing for SVSO areas. IMS Version 7 Installation Volume 2: System Definition and Tailoring Chapter 4 IMS Procedure New Fast Path parameter SVSODR added for IMS procedure. Parameter Descriptions: SVSODR = This parameter is optional. It specifies options for processing SVSO areas at a remote site. The options take

6 effect at an emergency restart when IMS connects to and creates a new structure for a SVSO area. NONE; This is the default option. In this case, processing is unchanged from existing SVSO ERE processing. AUTO: This option specifies that during ERE if IMS connects to a new structure for a SVSO area, that area is automatically marked as recovery needed. If the connection is made to a failed persistent structure, processing continues as normal. DRRS: This option is specified for a system that will be restarted at the disaster recovery remote site. When this is specified, IMS will recognize that this is an ERE at a remote site and process accordingly. At area open processing for a SVSO area, IMS will not attempt to connect to SVSO structures. The areas are marked as recovery needed in DBRC. Since the ERE is at the remote site, the connection would create a new structure and the areas would have to be marked as recovery needed. This saves the overhead of doing a connect and then a disconnect for each SVSO area. WTOR: This option allows the user to mark shared VSO areas as recovery needed. At an ERE process, during area open, IMS will connect to a SVSO structure. If the connection created a new structure, a WTOR will be generated. The prompt will give the user the option of continuing to process with the new structure or marking the area as recovery needed. Based on the reply to the WTOR, IMS will process accordingly. A WTOR will be issued for each SVSO area that is opened during an ERE process and the connection creates a new structure. The WTOR message is as follows: DFS2853A A NEW STRUCTURE WAS CREATED FOR AREA AAAAAAAA. REPLY 'C' TO CONTINUE OR 'R' TO RECOVER. Note: These options can also be specified at a local site.). ++ HOLD(UQ73960) SYS FMID(JMK7701) REASON(DOC) DATE(03065) (DOCUMENTATION CHANGE FOR APAR PQ67428 GC IMS Version 7 Installation Volume 2: System Definition and Tailoring GC IMS Version 7 Messages and Codes Volume 2 Documentation change: IMS Version 7 Messages and Codes Volume 2 1 New message DFS2853A DFS2853A A NEW STRUCTURE WAS CREATED FOR AREA AAAAAAAA. REPLY 'C' TO CONTINUE OR 'R' TO RECOVER. Explanation: This message is generated because the user specified the SVSODR startup option of 'WTOR'. This option is used at a remote site to provide the user with an option as to whether an SVSO area needs to be marked as recovery needed or not. The user is given an option whenever a new structure is created for an SVSO area at emergency restart and SVSODR=WTOR is specified. System Action: If the user selects option 'C', IMS will open the area specified, connect to a new structure and

7 normal processing will resume for that area. If the user selects option 'R', the specified area will be stopped and marked as recovery needed. Programmer Response: Reply 'C' to continue with normal processing for the area. Reply 'R' if the area is to be marked as recovery needed. Module: DBFVXCS0 2 New reason code 14 for message DFS2574I DFS2574I AREA=AAAAAAAA STOPPED, RECOVERY NEEDED, RSN=14 Explanation: Reason 14 indicates that an area has been stopped and marked as recovery needed due to one of the SVSODR options. These options take effect at emergency restart processing for SVSO areas. IMS Version 7 Installation Volume 2: System Definition and Tailoring Chapter 4 IMS Procedure New Fast Path parameter SVSODR added for IMS procedure. Parameter Descriptions: SVSODR = This parameter is optional. It specifies options for processing SVSO areas at a remote site. The options take effect at an emergency restart when IMS connects to and creates a new structure for a SVSO area. NONE This is the default option. In this case, processing is unchanged from existing SVSO ERE processing. AUTO This option specifies that during ERE if IMS connects to a new structure for a SVSO area, that area is automatically marked as recovery needed. If the connection is made to a failed persistent structure, processing continues as normal. DRRS This option is specified for a system that will be restarted at the disaster recovery remote site. When this is specified, IMS will recognize that this is an ERE at a remote site and process accordingly. At area open processing for a SVSO area, IMS will not attempt to connect to SVSO structures. The areas are marked as recovery needed in DBRC. Since the ERE is at the remote site, the connection would create a new structure and the areas would have to be marked as recovery needed. This saves the overhead of doing a connect and then a disconnect for each SVSO area. WTOR This option allows the user to mark shared VSO areas as recovery needed. At an ERE process, during area open, IMS will connect to a SVSO structure. If the connection created a new structure, a WTOR will be generated. The prompt will give the user the option of continuing to process with the new structure or marking the area as recovery needed. Based on the reply to the WTOR, IMS will process accordingly. A WTOR will be issued for each SVSO area that is opened during an ERE process and the connection creates a new structure. The WTOR message is as follows: DFS2853A A NEW STRUCTURE WAS CREATED FOR AREA AAAAAAAA. REPLY 'C' TO CONTINUE OR 'R' TO RECOVER. Note: These options can also be specified at a local site.). ++ HOLD(UQ74013) SYS FMID(HMK7700) REASON(ACTION) DATE(03041) (++

8 + HOLD FOR APAR PQ In OS/390 R6 and above, OW38840 added a new function to suppress notification to other participants in the SYSPLEX environment. This apar added a new keyword(suppressevents) to the IXLCONN macro. IMS is now taking advantage of this new function so OW38840 must be applied before applying this apar.). **** OW38840 > UQ74018 for IMS810 on PUT0302 **** ++ HOLD(UQ53831) SYS FMID(JMK7702) REASON(ACTION) DATE(03048) (++ + HOLD FOR APAR PQ Depending on how your zones are configured, SMP/E APPLY of this service may relink USER EXITS into your existing SDFSRESL. Please consider the following: This service updates or changes IMS USER EXITS. To install the latest version of these exits in IMS.SDFSRESL, it may require you to reassemble (with these changes) and relink into SDFSRESL your own customized versions of these USER EXITS. DFSNPRT0 and DFSMSCE0 have been modified to correct the comment lines in the prolog to indicate that the exit is called when the APPC conversation is allocated and after the data is received.). ++ HOLD(UQ74204) SYS FMID(JMK7702) REASON(ACTION) DATE(03048) (++ + HOLD FOR APAR PQ This maintenance is changing the sample + + user exit DFSNPRT0 provided by IMS. If + + this part is known to your target zone, + + it may overlay your customized version + + in the target library. Users that have + + their own DFSNPRT0 exit should take the + + appropriate actions to ensure that this + + maintenance will not affect their exit. + ++). ++ HOLD(UQ74204) SYS FMID(JMK7702) REASON(DOC) DATE(03048) (DOCUMENTATION CHANGE FOR APAR PQ68164 SC The IMS Version 7 Customization Guide SC has been update as follows: 4.11 INPUT MESSAGE ROUTING EXIT ROUTINE DFSNPRT Contents of Registers at Entry +20 = ADDRESS OF A 4 BYTE FIELD WITH THE LENGTH OF THE DESTINATION NAME. IF THE DESTINATION NAME POINTED TO BY PARMLIST+16 IS CHANGED, THIS LENGTH SHOULD BE CHANGED TO REFLECT THE LENGTH OF THE NEW DESTINATION NAME. FOR OTMA MESSAGES, THE LENGTH CAN BE ZERO IF THE DESTINATION, OR THE FIRST CHARACTER OF THE DESTINATION, IS BLANK.).

9 ++ HOLD(UQ74250) SYS FMID(JMK7701) REASON(DOC) DATE(03058) (DOCUMENTATION CHANGE FOR APAR PQ63878 SC IMS/ESA V7 Utilities Reference: Database Manager SC Chapter 13. DEDB Sequential Dependent Scan Utility (DBFUMSC0) DD Statements QUITCI In a shared SDEP environment: specifies that all IMS partners except for the owner of the HWM give up their current SDEP CI and any preallocated CI RBAs immediately. The IMS that owns the HWM will keep available for use the set of preallocated CI RBAs to which the high water mark (HWM) belongs along with it's current SDEP CI. This option is useful it there is an IMS partner that processes a low volume of transactions and therefore takes an extended period of time to fill its preallocated CIs. QUITCI forces inuse but only partiallyfilled CIs belonging to any preallocated set of CI RBAs except for the set from the IMS partner that owns the HWM to be written to the ADS and then released. In turn, this enables the delete utility to process the entire CI and advance the logical beginning (DMACXVAL) as far as possible, ensuring that sufficient space is available when the SDEPs cycle around. Using the QUITCI parameter guarantees that no new SDEPs will be inserted into the QUITCIs of the IMS partners that DO NOT own the HWM. However, the IMS partner that DOES own the HWM (highest DMACNXTS minus one CI) DOES allow new SDEPs to be inserted into the set of preallocated CI RBAs that include HWM when using QUITCI. In a nonshared SDEP environment: specification only effective if used in combination with V5COMP and STOPRBA where the CI RBA that STOPRBA references is the value of DMACNXTS. This value can be acquired from an unqualified POS call. In such a case, the IMS on which the SDEP utility is run, forces the inuse but only partiallyfilled current CI as well as the rest of the preallocated set of CI RBAs to be written to the ADS and then released. This enables the delete utility to move LB as far as possible. Using QUITCI with V5COMP and STOPRBA=DMACNXTS guarantees that no new SDEPs will be inserted into the QUITCIs of the IMS on which the SDEP utility is run. This combination of keywords must ONLY be used in a nonshared SDEP environment. If QUITCI is specified with any other set of parameters it will not take effect in a nonshared SDEP environment and the current and preallocated SDEP CIs will be retained for further SDEP inserts. Chapter 14. DEDB Sequential Dependent Delete utility (DBFUMDL0) DD Statements QUITCI

10 It is recommended that this parameter be used on the SCAN utility rather than DELETE. Do NOT specify it on a SCAN and then a DELETE for the same range of SDEP CI RBAs as this will result in too many unused preallocated CI RBA sets to be written out. Another set must then be created at the next SDEP insert. In a shared SDEP environment: specifies that all IMS partners except for the owner of the HWM give up their current SDEP CI and any preallocated CI RBAs immediately. The IMS that owns the HWM will keep available for use the set of preallocated CI RBAs to which the high water mark (HWM) belongs along with it's current SDEP CI. This option is useful it there is an IMS partner that processes a low volume of transactions and therefore takes an extended period of time to fill its preallocated CIs. QUITCI forces inuse but only partiallyfilled CIs belonging to any preallocated set of CI RBAs except for the set from the IMS partner that owns the HWM to be written to the ADS and then released. In turn, this enables the delete utility to process the entire CI and advance the logical beginning (DMACXVAL) as far as possible, ensuring that sufficient space is available when the SDEPs cycle around. Using the QUITCI parameter guarantees that no new SDEPs will be inserted into the QUITCIs of the IMS partners that DO NOT own the HWM. However, the IMS partner that DOES own the HWM (highest DMACNXTS minus one CI) DOES allow new SDEPs to be inserted into the set of preallocated CI RBAs that include HWM when using QUITCI. In a nonshared SDEP environment: specification only effective if used in combination with V5COMP and STOPRBA where the CI RBA that STOPRBA references is the value of DMACNXTS. This value can be acquired from an unqualified POS call. In such a case, the IMS on which the SDEP utility is run, forces the inuse but only partiallyfilled current CI as well as the rest of the preallocated set of CI RBAs to be written to the ADS and then released. This enables the delete utility to move LB as far as possible. Using QUITCI with V5COMP and STOPRBA=DMACNXTS guarantees that no new SDEPs will be inserted into the QUITCIs of the IMS on which the SDEP utility is run. This combination of keywords must ONLY be used in a nonshared SDEP environment. If QUITCI is specified with any other set of parameters it will not take effect in a nonshared SDEP environment and the current and preallocated SDEP CIs will be retained for further SDEP inserts. Appendix A: Command Descriptions QUITCI In a shared SDEP environment: specifies that all IMS partners except for the owner of the HWM give up their current SDEP CI and any preallocated CI RBAs immediately. The IMS that owns the HWM will keep available for use the set of preallocated CI RBAs to which the high water mark (HWM) belongs along with it's current SDEP CI. This option is useful it there is an IMS partner that processes a low volume of transactions and therefore takes an extended period of time to fill its preallocated CIs. QUITCI forces inuse but only partiallyfilled CIs belonging to any preallocated set of CI RBAs except for the set from the IMS partner that owns the HWM to be

11 written to the ADS and then released. In turn, this enables the delete utility to process the entire CI and advance the logical beginning (DMACXVAL) as far as possible, ensuring that sufficient space is available when the SDEPs cycle around. Using the QUITCI parameter guarantees that no new SDEPs will be inserted into the QUITCIs of the IMS partners that DO NOT own the HWM. However, the IMS partner that DOES own the HWM (highest DMACNXTS minus one CI) DOES allow new SDEPs to be inserted into the set of preallocated CI RBAs that include HWM when using QUITCI. In a nonshared SDEP environment: specification only effective if used in combination with V5COMP and STOPRBA where the CI RBA that STOPRBA references is the value of DMACNXTS. This value can be acquired from an unqualified POS call. In such a case, the IMS on which the SDEP utility is run, forces the inuse but only partiallyfilled current CI as well as the rest of the preallocated set of CI RBAs to be written to the ADS and then released. This enables the delete utility to move LB as far as possible. Using QUITCI with V5COMP and STOPRBA=DMACNXTS guarantees that no new SDEPs will be inserted into the QUITCIs of the IMS on which the SDEP utility is run. This combination of keywords must ONLY be used in a nonshared SDEP environment. If QUITCI is specified with any other set of parameters it will not take effect in a nonshared SDEP environment and the current and preallocated SDEP CIs will be retained for further SDEP inserts.). ++ HOLD(UQ74539) SYS FMID(JMK7701) REASON(DOC) DATE(03057) (DOCUMENTATION CHANGE FOR APAR PQ70368 LY Document Number: LY IMS Version 7: Failure Analysis Structure Tables ABENDU1027 DBFMGXC0 Key Label Description Reg15=X'10' SDEP CI lock request duplicate). ++ HOLD(UQ74580) SYS FMID(HMK7700) REASON(DOC) DATE(03058) (DOCUMENTATION CHANGE FOR APAR PQ70096 GC : Installation Volume 2: System Definition and Tailoring Specifying the FDBR Options: Add optional parameter SVSOOPEN=SERIAL to the ACTIVEIMSID control statement diagram. SVSOOPEN=SERIAL Specifies that all areas requiring redo processing in an FDBR system will be serially processed. This option is ignored for /ERE and XRF TKO processing. It is used to reduce the number of structures being allocated by FDBR for redo processing.).

12 ++ HOLD(UQ74580) SYS FMID(HMK7700) REASON(ENH) DATE(03058) (********************************************************* APAR PQ70096 ADDS NEW IMS FUNCTION. FUNCTION NAME: FDBR SERIALIZED PROCESSING FOR SHARED VSO AREAS. SEE APAR CLOSING TEXT OR PTF COVER LETTER FOR COMPLETE DETAILS. *********************************************************). **** APAR PQ70096 COPIED INLINE *************************** THIS APAR PROVIDES AN ENHANCEMENT TO FDBR PROCESSING WITH SHARED VSO AREAS. WHEN SHARED VSO AREAS ARE USED WITH DUPLEXING, THE TOTAL NUMBER OF STRUCTURES IN AN MVS IMAGE CAN GET CLOSE TO THE MAXIMUM ALLOWED. THIS MAXIMUM IS 256. IF THERE IS AN FDBR SYSTEM TRACKING AN IMS SYSTEM USING A LARGE NUMBER OF AREAS, ADDITIONAL STRUCTURES WILL BE ALLOCATED FOR THOSE AREAS REQUIRING REDO PROCESSING. THESE ADDITIONAL STRUCTURES MAY EXCEED THE MVS LIMIT RESULTING IN SHARED VSO AREAS FAILING TO COMPLETE OPEN PROCESSING. THIS WILL RESULT IN THESE AREAS BEING MARKED RECOVERY NEEDED. THIS ENHANCEMENT WILL PROVIDE AN OPTION FOR FDBR SYSTEMS TO OPEN AND PROCESS AREAS THAT REQUIRE REDO PROCESSING SERIALLY. THE OPTION, SPECIFIED IN THE DFSFDRXX MEMBER, IS AS FOLLOWS: 'SVSOOPEN=SERIAL'. THIS OPTION WILL CREATE 1 ITASK FOR REDO PROCESSING. ALL AREAS WILL BE PROCESSED BY THIS ITASK. THIS OPTION IS IGNORED FOR /ERE AND XRF TAKEOVER PROCESSING. WHEN THIS OPTION IS SPECIFIED ON AN FDBR SYSTEM, AREAS THAT WILL REQUIRE REDO PROCESSING ARE NOT OPENED WHEN THE PRIMARY DMAC CHAIN IS BUILT. DBFERS10 WILL SKIP THIS PROCESSING. THE OPEN AND CONNECT PROCESSING WILL BE DELAYED UNTIL THE AREA IS READY TO BE PROCESSED IN DBFERS20. AFTER THE AREA HAS COMPLETED ITS REDO PROCESSING, THE AREA IS CLOSED. THIS WILL ALSO RESULT IN THE STRUCTURE BEING DISCONNECTED. THE NET RESULT IS THAT THE TOTAL NUMBER OF STRUCTURES ALLOCATED DOES NOT INCREASE PAST THE MAX. ++ HOLD(UQ73960) SYS FMID(JMK7701) REASON(DOC) DATE(03065) (DOCUMENTATION CHANGE FOR APAR PQ67428 GC IMS Version 7 Installation Volume 2: System Definition and Tailoring GC IMS Version 7 Messages and Codes Volume 2 Documentation change: IMS Version 7 Messages and Codes Volume 2 1 New message DFS2853A DFS2853A A NEW STRUCTURE WAS CREATED FOR AREA AAAAAAAA. REPLY 'C' TO CONTINUE OR 'R' TO RECOVER. Explanation: This message is generated because the user specified the SVSODR startup option of 'WTOR'. This option is used at a remote site to provide the user with an option as to whether an SVSO area needs to be marked as recovery needed or not. The user is given an option whenever a new structure is created for an SVSO area at emergency restart and SVSODR=WTOR is specified. System Action: If the user selects option 'C', IMS will open the

13 area specified, connect to a new structure and normal processing will resume for that area. If the user selects option 'R', the specified area will be stopped and marked as recovery needed. Programmer Response: Reply 'C' to continue with normal processing for the area. Reply 'R' if the area is to be marked as recovery needed. Module: DBFVXCS0 2 New reason code 14 for message DFS2574I DFS2574I AREA=AAAAAAAA STOPPED, RECOVERY NEEDED, RSN=14 Explanation: Reason 14 indicates that an area has been stopped and marked as recovery needed due to one of the SVSODR options. These options take effect at emergency restart processing for SVSO areas. IMS Version 7 Installation Volume 2: System Definition and Tailoring Chapter 4 IMS Procedure New Fast Path parameter SVSODR added for IMS procedure. Parameter Descriptions: SVSODR = This parameter is optional. It specifies options for processing SVSO areas at a remote site. The options take effect at an emergency restart when IMS connects to and creates a new structure for a SVSO area. NONE This is the default option. In this case, processing is unchanged from existing SVSO ERE processing. AUTO This option specifies that during ERE if IMS connects to a new structure for a SVSO area, that area is automatically marked as recovery needed. If the connection is made to a failed persistent structure, processing continues as normal. DRRS This option is specified for a system that will be restarted at the disaster recovery remote site. When this is specified, IMS will recognize that this is an ERE at a remote site and process accordingly. At area open processing for a SVSO area, IMS will not attempt to connect to SVSO structures. The areas are marked as recovery needed in DBRC. Since the ERE is at the remote site, the connection would create a new structure and the areas would have to be marked as recovery needed. This saves the overhead of doing a connect and then a disconnect for each SVSO area. WTOR This option allows the user to mark shared VSO areas as recovery needed. At an ERE process, during area open, IMS will connect to a SVSO structure. If the connection created a new structure, a WTOR will be generated. The prompt will give the user the option of continuing to process with the new structure or marking the area as recovery needed. Based on the reply to the WTOR, IMS will process accordingly. A WTOR will be issued for each SVSO area that is opened during an ERE process and the connection creates a new structure. The WTOR message is as follows: DFS2853A A NEW STRUCTURE WAS CREATED FOR AREA AAAAAAAA. REPLY 'C' TO CONTINUE OR 'R' TO RECOVER. Note: These options can also be specified at a local site.). ++ HOLD(UQ74581) SYS FMID(JMK7701) REASON(DOC) DATE(03065)

14 (DOCUMENTATION CHANGE FOR APAR PQ70096 GC : Installation Volume 2: System Definition and Tailoring Specifying the FDBR Options: Add optional parameter SVSOOPEN=SERIAL to the ACTIVEIMSID control statement diagram. SVSOOPEN=SERIAL Specifies that all areas requiring redo processing in an FDBR system will be serially processed. This option is ignored for /ERE and XRF TKO processing. It is used to reduce the number of structures being allocated by FDBR for redo processing.). ++ HOLD(UQ74581) SYS FMID(JMK7701) REASON(ENH) DATE(03065) (********************************************************* APAR PQ70096 ADDS NEW IMS FUNCTION. FUNCTION NAME: FDBR SERIALIZED PROCESSING FOR SHARED VSO AREAS. SEE APAR CLOSING TEXT OR PTF COVER LETTER FOR COMPLETE DETAILS. *********************************************************). ++ HOLD(UQ74250) SYS FMID(JMK7701) REASON(DOC) DATE(03058) (DOCUMENTATION CHANGE FOR APAR PQ63878 SC IMS/ESA V7 Utilities Reference: Database Manager SC Chapter 13. DEDB Sequential Dependent Scan Utility (DBFUMSC0) DD Statements QUITCI In a shared SDEP environment: specifies that all IMS partners except for the owner of the HWM give up their current SDEP CI and any preallocated CI RBAs immediately. The IMS that owns the HWM will keep available for use the set of preallocated CI RBAs to which the high water mark (HWM) belongs along with it's current SDEP CI. This option is useful it there is an IMS partner that processes a low volume of transactions and therefore takes an extended period of time to fill its preallocated CIs. QUITCI forces inuse but only partiallyfilled CIs belonging to any preallocated set of CI RBAs except for the set from the IMS partner that owns the HWM to be written to the ADS and then released. In turn, this enables the delete utility to process the entire CI and advance the logical beginning (DMACXVAL) as far as possible, ensuring that sufficient space is available when the SDEPs cycle around. Using the QUITCI parameter guarantees

15 that no new SDEPs will be inserted into the QUITCIs of the IMS partners that DO NOT own the HWM. However, the IMS partner that DOES own the HWM (highest DMACNXTS minus one CI) DOES allow new SDEPs to be inserted into the set of preallocated CI RBAs that include HWM when using QUITCI. In a nonshared SDEP environment: specification only effective if used in combination with V5COMP and STOPRBA where the CI RBA that STOPRBA references is the value of DMACNXTS. This value can be acquired from an unqualified POS call. In such a case, the IMS on which the SDEP utility is run, forces the inuse but only partiallyfilled current CI as well as the rest of the preallocated set of CI RBAs to be written to the ADS and then released. This enables the delete utility to move LB as far as possible. Using QUITCI with V5COMP and STOPRBA=DMACNXTS guarantees that no new SDEPs will be inserted into the QUITCIs of the IMS on which the SDEP utility is run. This combination of keywords must ONLY be used in a nonshared SDEP environment. If QUITCI is specified with any other set of parameters it will not take effect in a nonshared SDEP environment and the current and preallocated SDEP CIs will be retained for further SDEP inserts. Chapter 14. DEDB Sequential Dependent Delete utility (DBFUMDL0) DD Statements QUITCI It is recommended that this parameter be used on the SCAN utility rather than DELETE. Do NOT specify it on a SCAN and then a DELETE for the same range of SDEP CI RBAs as this will result in too many unused preallocated CI RBA sets to be written out. Another set must then be created at the next SDEP insert. In a shared SDEP environment: specifies that all IMS partners except for the owner of the HWM give up their current SDEP CI and any preallocated CI RBAs immediately. The IMS that owns the HWM will keep available for use the set of preallocated CI RBAs to which the high water mark (HWM) belongs along with it's current SDEP CI. This option is useful it there is an IMS partner that processes a low volume of transactions and therefore takes an extended period of time to fill its preallocated CIs. QUITCI forces inuse but only partiallyfilled CIs belonging to any preallocated set of CI RBAs except for the set from the IMS partner that owns the HWM to be written to the ADS and then released. In turn, this enables the delete utility to process the entire CI and advance the logical beginning (DMACXVAL) as far as possible, ensuring that sufficient space is available when the SDEPs cycle around. Using the QUITCI parameter guarantees that no new SDEPs will be inserted into the QUITCIs of the IMS partners that DO NOT own the HWM. However, the IMS partner that DOES own the HWM (highest DMACNXTS minus one CI) DOES allow new SDEPs to be inserted into the set of preallocated CI RBAs that include HWM when using QUITCI. In a nonshared SDEP environment: specification only effective if used in combination with V5COMP and STOPRBA where the CI RBA that STOPRBA references is the value of DMACNXTS. This value can be acquired from an unqualified POS call. In such a case, the IMS on which the SDEP

16 utility is run, forces the inuse but only partiallyfilled current CI as well as the rest of the preallocated set of CI RBAs to be written to the ADS and then released. This enables the delete utility to move LB as far as possible. Using QUITCI with V5COMP and STOPRBA=DMACNXTS guarantees that no new SDEPs will be inserted into the QUITCIs of the IMS on which the SDEP utility is run. This combination of keywords must ONLY be used in a nonshared SDEP environment. If QUITCI is specified with any other set of parameters it will not take effect in a nonshared SDEP environment and the current and preallocated SDEP CIs will be retained for further SDEP inserts. Appendix A: Command Descriptions QUITCI In a shared SDEP environment: specifies that all IMS partners except for the owner of the HWM give up their current SDEP CI and any preallocated CI RBAs immediately. The IMS that owns the HWM will keep available for use the set of preallocated CI RBAs to which the high water mark (HWM) belongs along with it's current SDEP CI. This option is useful it there is an IMS partner that processes a low volume of transactions and therefore takes an extended period of time to fill its preallocated CIs. QUITCI forces inuse but only partiallyfilled CIs belonging to any preallocated set of CI RBAs except for the set from the IMS partner that owns the HWM to be written to the ADS and then released. In turn, this enables the delete utility to process the entire CI and advance the logical beginning (DMACXVAL) as far as possible, ensuring that sufficient space is available when the SDEPs cycle around. Using the QUITCI parameter guarantees that no new SDEPs will be inserted into the QUITCIs of the IMS partners that DO NOT own the HWM. However, the IMS partner that DOES own the HWM (highest DMACNXTS minus one CI) DOES allow new SDEPs to be inserted into the set of preallocated CI RBAs that include HWM when using QUITCI. In a nonshared SDEP environment: specification only effective if used in combination with V5COMP and STOPRBA where the CI RBA that STOPRBA references is the value of DMACNXTS. This value can be acquired from an unqualified POS call. In such a case, the IMS on which the SDEP utility is run, forces the inuse but only partiallyfilled current CI as well as the rest of the preallocated set of CI RBAs to be written to the ADS and then released. This enables the delete utility to move LB as far as possible. Using QUITCI with V5COMP and STOPRBA=DMACNXTS guarantees that no new SDEPs will be inserted into the QUITCIs of the IMS on which the SDEP utility is run. This combination of keywords must ONLY be used in a nonshared SDEP environment. If QUITCI is specified with any other set of parameters it will not take effect in a nonshared SDEP environment and the current and preallocated SDEP CIs will be retained for further SDEP inserts.). ++ HOLD(UQ74628) SYS FMID(HMK7700) REASON(IOGEN) DATE(03059) (AFTER THIS MAINTENANCE IS ACCEPTED AN IMS "CTLBLKS" LGEN IS REQUIRED. ===>*Please Note*<=== A SYSGEN is *NOT* required if you use standard sysgen. A SYSGEN is *NOT* required if you use LGEN but do not have

17 Fast Path Exclusive transactions. A SYSGEN is *NOT* required if you use LGEN and do not have Fast Path Exclusive Transactions and RTCODE duplicate names. *NO LGEN or SYSGEN IS REQUIRED*. Apply and Accept this service and it will be picked up the next time an LGEN is done. Please see the cover letter for this service for further details.). ****** The details from PQ69628 copied inline. ****** In this case the STAGE 1 input had Fast Path Exclusive Trans that had duplicate RTCODE names. Since Fast Path Exclusive generates its' own route codes dynamically duplicates are not allowed and should be caught in LGEN. Standard sysgen detects this type of duplication but LGEN does not. The FPEXCLSV flag in IMS module DFSPRE10 is being reset after the FPATH= keyword is detected. When the duplicate check is then made for Resource Name Tables (RNT) containing the RTCODE and TRANSACTION names, no duplicates are found because the Fast Path Exclusive RNT is empty. IMS module DFSPERE10 is changed to correct the timing of the FPEXCLSV bit setting. ++ HOLD(UQ39601) SYS FMID(HMK7700) REASON(DOC) DATE(03062) (DOCUMENTATION CHANGE FOR APAR PQ34640 ZES THE IMS/ESA V7 SYSTEM UTILITIES REFERENCE, ZES , WILL BE UPDATED TO EMPHASIZE THE PROPER USE OF THE ST PARAMETER. C PARAMETER:(WITHOUT DOC CHANGE) SPECIFIES THE NUMBER OF CHECKPOINTS TO BE PROCESSED BEFORE SELECTION OF TRANSACTIONS STOPS. C IS A NUMBER FROM 0 TO 9. C PARAMETER:(WITH DOC CHANGE) SPECIFIES THE NUMBER OF CHECKPOINTS TO BE PROCESSED BEFORE SELECTION OF TRANSACTIONS STOPS. C IS A NUMBER FROM 1 TO 9.).