• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
IMS V13 Overview - IMS UG May 2013 Boston
 

IMS V13 Overview - IMS UG May 2013 Boston

on

  • 867 views

 

Statistics

Views

Total Views
867
Views on SlideShare
867
Embed Views
0

Actions

Likes
0
Downloads
7
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    IMS V13 Overview - IMS UG May 2013 Boston IMS V13 Overview - IMS UG May 2013 Boston Presentation Transcript

    • © 2011 IBM Corporation®IMS Version 13IMS 13 OverviewBoston IMS User Group MeetingMay 14, 2013Diane Goff, IMS Advanced Technical Skillsdgoff@us.ibm.com
    • IMS Version 132IMS 13 - AgendaStatus of IMS VersionsPrerequisites, Migration, CoexistenceSystem EnhancementsTransaction Manager and Connectivity EnhancementsDatabase and DBRC Enhancements2
    • IMS Version 133Status of IMS VersionsIMS Version 9– End of service was November 7, 2010IMS Version 10– Generally available on October 26, 2007– End of service was November 5, 2012IMS Version 11– Generally available on October 30, 2009– End of service has not been announcedIMS Version 12– Generally available on October 28, 2011– End of service has not been announcedIMS Version 13– Announced on October 3, 2012– Currently in QPP program– General availability has not been announced
    • IMS Version 134Software PrerequisitesMinimum software level prerequisites– z/OS V1R13 (5694-A01)• RACF (included in separately orderable SecureWay Security Server), orequivalent, if security is used• High Level Assembler Toolkit Release 5 (5696-234)• APAR OA39392 / PTF UA66823 is required for z/OS 1.13 for IMS V13– IRLM 2.3 if the IRLM is used* subject to change
    • IMS Version 135Software Prerequisites ...Minimum software levels for optional functions– Java Dependent Regions requires JDK 6.0.1– ISC TCP/IP requires CICS 5.1– Depending on the environment, the IMS Universal Drivers require:• IBM JDK 6.0.1 or later• DB2 V9.1 or later• WAS V7 or later• CICS V4.1 or later– DB Versioning requires implementation of the IMS Catalog* subject to change
    • IMS Version 136Software Prerequisites ...Minimum software levels for optional functions ...– IMS 13 supports interactions with• DB2: Versions 9, 10• CICS: Versions 3.2, 4.1, 4.2, 5.1– CICS 5.1 (newly announced) is required for ISC TCP/IP support• Requires z/OS 1.13• MQ for z/OS: Versions V7.0.1, V7.1– Note V6 EOS was September 2012– 7.01 introduced MQ message expiry interfacing with IMS transaction expiration– 7.1 enhanced the expiry support and support for OTMA resource monitoringprotocol messages* subject to change
    • IMS Version 137Hardware PrerequisitesIMS 13 runs only on 64 bit processors running in z/Architecture mode– Processors must also support the Long-Displacement Facility of thez/Architecture– ESA mode is not supported– For a list of z/Series machines see: www.ibm.com/systems/z/hardware/z900 machines must be at GA2 level (microcode level 3G or later)
    • IMS Version 138Hardware Prerequisites ...Sysplex Data Sharing (including Data Caching and VSO Data Sharing)– Coupling Facility (CF) level 9, or laterShared Queues and Shared EMH support– Coupling Facility level 9 or later– System-managed CF Duplexing• CF level 12, or later and bidirectional CF to CF linksEAV support for non-VSAM data sets– EAVs are supported on DS8000 at microcode level R4.0 via bundle64.0.175.0 (Sept 2008) or higher
    • IMS Version 139Supported Migrations and CoexistenceIMS 12 to IMS 13– Upgrade RECONs from IMS 12 to IMS 13– Databases are compatible– Application programs are compatibleIMS 11 to IMS 13– Upgrade RECONs from IMS 11 to IMS 13– Databases are compatible– Application programs are compatibleCheck Release Planning documentation at GA for additionalprerequisites/coexistence/migration items
    • IMS Version 1310IMS 13 System EnhancementsIMS Connect EnhancementsConcurrent Application ThreadsReduced Total Cost of Ownership (TCO)IMS Command EnhancementsIMS CQS EnhancementIMS DRD EnhancementIMS User Exit EnhancementsIMS Security Enhancements/DIAG Command Enhancements
    • IMS Version 1311IMS Connect EnhancementsXML Converter EnhancementsAuto-restart of the Language Environment (LE)Expanded Recorder Trace RecordsUse of RACF Event Notification Facility (ENF) Support forcached RACF UserIDs (UID)Reporting of overall health to Workload Manager (WLM)Configurable TCP/IP backlog (queue) size
    • IMS Version 1312XML Converter EnhancementsSupport for extending the current limit of 100 up to 2000 for themaximum number of XML converters• New IMS Connect configuration parameter MAXCVRTADAPTER(…, MAXCVRT= value)• IMS 12 (PM64487 / UK79728)Capability to view converters that are currently loaded– New Type-2 Command: QUERY IMSCON TYPE(CONVERTER)• Requests detailed information about XML converters in IMS ConnectBenefits– Enhances the flexibility of converter usage• Directly impacts IMS Soap Gateway environments
    • IMS Version 1313Auto-restart of the Language Environment (LE)Automated mechanism to reinitialize the Language Environmentwhen an XML converter ABENDs– Without restarting IMS Connect– Converters will be reloaded as they are neededAutomatic refresh of the BPE User Exit for the XML Adapters(HWSXMLA0) after the ABEND limit ABLIM has been reachedBenefit– Improved efficiencies during error conditions• Eliminates IMS Connect restart and user interactions
    • IMS Version 1314Expanded Recorder Trace RecordsThe Recorder trace records have been expanded to:– Capture entire messages sent and received using:• All TCP/IP communications– Including DRDA sockets and ISC TCP/IP• SCI (OM, ODBM, MSC, and ISC communications)• Requires a Trace Level HIGH and use of the external trace data setUPDATE TRACETABLE NAME(RCTR) OWNER(HWS) LEVEL(HIGH) EXTERNAL(YES | NO)Benefits– Improved diagnostics and problem determination
    • IMS Version 1315RACF Event Notification Facility (ENF) SupportBackground– IMS Connect V12 provided the option to cache RACF UserIDs (UIDs) alongwith a command to refresh themIMS Connect V13: RACF ENF Support for Cached UserIDs (UID)– Automatically refreshes cached UIDs by listening to RACF events (ENFsignals) indicating that a change has been made to a UID– NOTE: This function applies only when RACF UID caching has beenenabled in IMS ConnectBenefit– Allows IMS Connect to listen for certain RACF events indicating that achange has been made to a specific UserID• Avoids manual intervention
    • IMS Version 1316Reporting of Overall Health to WLMWLM (Workload Manager) Health Report– New function to automatically report the overall health of IMS Connect• Allows Sysplex Distributor to use and take into account thisinformation for workload balancingBenefit– Allows WLM to know when resources are constrained or available– Minimizes the possibility of Sysplex Distributor assigning work that IMSConnect is unable to handle
    • IMS Version 1317Configurable TCP/IP backlog (Queue) sizeNew parameter TCPIPQ– Allows users to configure the length of the queue in TCP/IP forconnection requests that have not yet been assigned a socket.• Connection requests are held on this queue until IMS Connect canassign a socket– Overrides the default which is equal to the maxsoc value• Actual value used is the smaller of IMS Connect’s TCPIPQ valueand SOMAXCONN in TCP/IPBenefit– Provides a configurable option to increase the backlog queue size inTCP/IP
    • IMS Version 1318Overall Value of IMS Connect EnhancementsEnhanced usability while providing better performance anddiagnosticsIncreased resiliency to Abnormal Ends (ABENDs)Improved usability and manageability
    • IMS Version 1319Concurrent Application Threads EnhancementPartition Specification Table (PST) used for– Active dependent regions (MSG/BMP/IFP/JMP/JBP)– CICS/DBCTL threads– Open Database Access threadsCustomers continue to require more PSTs!– 31 dependent regions - 1980 (IMS 1.1.6)– 999 dependent regions - 1995 (IMS 5.1)– 4095 dependent regions - 2013 (IMS 13)Related parameters– MAXPST=– PST=– MAXTHRDS= for ODBM– MAXTHRDS=, MINTHRDS= for DBCTL
    • IMS Version 1320MAXPST= parameterUsed in DBC, DCC, and IMS procedures– Specifies the maximum number of PSTs for an online IMS controlregion– Default is 255 (no change)– Maximum value is 4095 in IMS 13 (quadrupled)Controls maximum number of– Active dependent regions (MSG/BMP/IFP/JMP/JBP)– CICS/DBCTL threads– Open Database Access threadsReducing MAXPST= requires a cold start
    • IMS Version 1321Benefits of the Concurrent Thread Enhancement(Increasing MAXPST)Customers can now have increased capacity/scalability for their IMSsystems– Larger capacity for mergers/acquisitions• Without having to add more IMS images– Increased workloads with latest zEnterprise hardware• Room for vertical growth– More regions for IMS 13 synchronous program switch function, alsosynchronous callout, distributed syncpoint/etc.• Longer region occupanciesMAXPST should no longer be a limiting factor in IMS growth
    • IMS Version 1322Reduced Total Cost of OwnershipCross-platform focus on reducing mainframe software costsMajor focus on reducing CPU usageChanges throughout IMS to improve performance, reduce storageusage and reduce CPU used to run IMS– Using more efficient storage services– Improved algorithms– Reducing pathlength– Optimizing frequently used processes– Latch / lock improvements– Storage reductions– Use of zEnterprise hardware functionsBenefits– Improved performance, lower cost per transaction, reduced cost ofownership.
    • IMS Version 1323Specific Reduced TCO EnhancementsIMS logger LOG latch contention reduction– Improves usage of log latch and log buffer management for increased loggingbandwidth and more efficient processingShared queues local first optimization now applies to program-to-program switch messages as well as ordinary input messages– Avoids false scheduling on another IMS when the local IMS can process theprogram-to-program switch messageExploitation of pageable 1M pages– Based on usage of new zEC12 processors with Flash Express storage andz/OS 1.13 (Dec. 2012)– Provides improvements in dynamic address translation and usage oftranslation lookaside buffer (TLB)DB Space Management Block Serialization Latch Improvements– Split from single to multiple latches to improve heavy BMP workloadsMEMDSENQMGMT Exploitation– More efficient memory-based data set ENQ management improves allocationof large number of data sets
    • IMS Version 1324Other Reduced TCO EnhancementsOTMA YTIB chain changed from a single linked list to a hash table, toimprove FINDDEST performance.Convert OTMA and IMS Connect STORAGE calls to CPOOLRemove unnecessary clearing of OTMA buffersDFSCPY00 improved SVC directory entry search algorithm and removalof IVSK instructions.OSAM CML Lock ReductionGeneral instruction optimization (replacing STCK with STCKF, longdisplacement facility exploitation)IMS cache manager spin loop eliminationCQS mainline modules changed to use branch-relative branchingCache efficiency improvements (DPST blocks packed into a singleIPAGE to keep cache references localized)IMS page load service algorithm optimizationIMS dispatcher optimizations
    • IMS Version 1325ESAF support in Java Dependent Regions (JDR)With IMS 13, there are two methods for accessing DB2 from JDRs– Access via the previously existing DB2 RRSAF interface– Access via the standard ESAF interfaceWith IMS 13, the ESAF interface can be used in JMP/JBP regions toaccess any ESAF defined to the IMS control region– WebSphere MQ, DB2, WOLA (WebSphere Optimized Local Adapter)Support for the SSM= parameter on the JMP/JBP dependent regionstartup JCLOnly one ESS connection method allowed per JMP/JBP– Default ESS connection method is DB2 RRSAF• No impact to existing usersBenefits– Simpler, more efficient, and more consistent interface
    • IMS Version 1326IMS Command Enhancements OverviewDBRC command enhancementsDEDB Alter command enhancements/DIAGNOSE SNAP command enhancementHALDB command enhancementsIMS Connect type-2 command enhancements– Dynamically create data store definitions (CREATE IMSCONTYPE(DATASTORE))– Dynamically create port definitions (CREATE IMSCON TYPE(PORT))– Query XML converters loaded in IMS Connect (QUERY IMSCONTYPE(CONVERTER)
    • IMS Version 1327IMS Command EnhancementsEnhancements are focused on type-2 commands for the OperationsManager (OM) environmentBenefits– Support of new IMS 13 functions– Improved manageability
    • IMS Version 1328IMS CQS EnhancementWhen IMS Common Queue Server (CQS) rejects a z/OS STOPcqsjobname command because CQS clients are still connected(CQS0300I), CQS issues a new message, CQS0301I, for eachconnected client– Enables the operator to shut down or quiesce the connected CQS clientsso that the CQS address space can be stoppedBenefits– Improved manageability for CQS
    • IMS Version 1329IMS DRD EnhancementSupport for the IMS repository (a single centralized store for resourcedefinitions in an IMSplex) enhanced to validate resource attributesbetween associated resources when a resource definition is addedto, updated in, or deleted from the IMSRSC Repository– Validates transaction, routing code, and program attributesAlso provided through the IMS 12 service process– APAR PM32805 / PTF UX75915Benefits– Simplifies management of the DRD resources
    • IMS Version 1330IMS 13 User Exit EnhancementsEnhanced user exit services extended to additional IMS controlregion user exitsUsers can now dynamically refresh more IMS user exit routines tobring in an updated version of the exit (or add/delete)– Significantly reduces downtime since IMS control region no longerrequires restartUsers can now display information about more user exits that aredefined in the USER_EXITS section of DFSDFxxx– Provides useful exit information to the userUsers can now code an exit to leverage IMS’s ability to call multipleroutines of the same type from a single point within the exit
    • IMS Version 1331BSEX (DFSBSEX0, Build Security Environment Exit)NDMX (DFSNDMX0, Non-Discardable Message Exit)RASE (DFSRAS00, Resource Access Security Exit)OTMAYPRX (DFSYPRX0, OTMA Destination Resolution Exit)OTMARTUX (DFSYRTUX, OTMA Resume TPIPE Security Exit)OTMAIOED (DFSYIOE0, OTMA Input/Output Edit Exit)LOGWRT (DFSFLGX0, Logger Exit)LOGEDIT (DFSFLGE0, Log Edit Exit)Enhanced User Exit Services Added to More ControlRegion Exit Types
    • IMS Version 1332IMS Security EnhancementsAll IMS security settings can now be defined as IMS startupparameters– Updates to SECURITY macro in system definition (SYSGEN) no longerrequired due to its removal– Previously, certain settings could only be defined in SECURITY macroMove security user exits out of the IMS nucleus into 31-bit storage– DFSCSGN0– DFSCTRN0– DFSCTSE0
    • IMS Version 1333New IMS Startup Security ParametersRCLASS parameter added to DFSPBxxx PROCLIB member– RCLASS support in DFSDCxxx PROCLIB member will remain• DFSPBxxx RCLASS parameter value will override DFSDCxxx ifspecified in bothSECCNT parameter added to DFSDCxxx PROCLIB memberRetrofit SPE APARs/PTFs available for IMS startup securityparameter enhancement activation in IMS 11 and IMS 12– PM48203/UK74050 (IMS 11)– PM48204/UK74051 (IMS 12)– If specifying RCLASS in DFSPBxxx/DFSDCxxx, can also have thefollowing APARs/PTFs applied to avoid an error message being issuedwhen it shouldn’t be• PM72199/UK82616 (IMS 11)• PM73558/UK82617 (IMS 12)
    • IMS Version 1334/DIAGNOSE Command EnhancementsProcess for capturing diagnostic data used in troubleshooting IMSissues has been simplified– SYSOUT option now available for /DIAGNOSE SNAP output• Documentation can be gathered/stored in a readable format that is easy toretrieve and send to IBM support• Time-consuming SYSLOG searches and manual data formatting prior totransmission no longer required– /DIAGNOSE SNAP command extended to include more resources + morecoverage of existing resources• SHOW() support added for LTERM, NODE and USER• BLOCK – can now specify multiple single instance blocks and more blockscan be snapped• More blocks can be snapped for DB, LINE, LINK• MSNAME support added
    • IMS Version 1335/DIAGNOSE Command EnhancementsBenefits– Cost effective, non-disruptive alternative to console dumps– /DIAGNOSE command is now more interactive• Can be used more as a tool for easing the real-time diagnosis process– Decreased time and effort required in capturing diagnostic information– Improved turn-around time in problem resolution
    • IMS Version 1336Summary of IMS 13 System TopicsIMS Connect EnhancementsConcurrent Application ThreadsReduced Total Cost of Ownership (TCO)IMS Command EnhancementsIMS CQS EnhancementIMS DRD EnhancementIMS User Exit EnhancementsIMS Security Enhancements/DIAG Command Enhancements
    • IMS Version 1337IMS 13 Transaction Manager and ConnectivityEnhancementsCallout function enhancementsISC Over TCP/IPOTMA enhancementsNon-Discardable Message Exit (DFSNDMX0) enhancements
    • IMS Version 1338Callout function enhancementsSynchronous program switchEnhancements to RECEIVE function for handling truncated messagesOTMA destination descriptors support asynchronous messages that aregoing to IBM WebSphere® MQ.
    • IMS Version 1339BackgroundDL/I ICAL support from previous IMS releases– Provided synchronous callout capability to resources outside IMSIMS SOAP GATEWAYz/OSIMSDatabaseDBServicesOTMATM/CTLServicesIMSConnectTCP/IPuser-written ClientWebSphereIMS TM resource adapterApplicationProgramICALMPP/JMP/IFP/BMP/JBPOTMADescriptorOTMADescriptor
    • IMS Version 1340Synchronous Program SwitchNew capability that enhances the DL/I ICAL support– Allows an IMS application program to synchronously call and wait for a replyfrom another IMS application program• Within the calling program’s UOWDatabaseIMS DBservicesIMS dependentregionIMS TMservicesMPP, JMPIFP, MD BMPOTMAApplicationProgramICALIMS SOAP GATEWAYIMSConnectTCP/IPuser-written ClientWebSphereIMS TM resource adapter
    • IMS Version 1341Synchronous Program Switch...Highlights– An enhancement to the DL/I ICAL to invoke another IMS application• In the same IMS• In a different IMS– In a Shared Queues back-end– Across an MSC link– And synchronously receive the response back during the same UOW– IMS internally schedules the transaction initiated by the ICAL call as an OTMAtransaction• Uses a new type of OTMA destination descriptor (TYPE=IMSTRAN) whichhas been introduced specifically for synchronous program switch support– And the target transaction can be• An IFP, MPP, MD BMP, or JMP in IMS TM or TM/DB environmentsMPP1MPP4MPP3ICALICALICALIMS1MPP2IMS XIMS2MSCSharedMsg Queues
    • IMS Version 1342Synchronous Program Switch...Usage examples– Applications can issue multiple ICALs to different destination TYPEs• Synchronous callout• Synchronous program switchICAL DEST1ICAL TRANBTRANAIMS CTL RegionIMSConnectWebSphereIMS TMRAIMS SOAPGatewayTCP/IPRYO pgmOTMAMSG-QDestinationDescriptorTYPE(IMSCON)TRANBGU IOPCBISRT IOPCBDestinationDescriptorTYPE(IMSTRAN)1234567GU, IOPCB
    • IMS Version 1343Synchronous Program Switch...Considerations– To use synchronous program switch in a shared queues environment, allof the participating IMS systems must be Version 13 or later and have aMINVERS value of 13.1– New design implications• Timeout values• Transaction Expiration• Late Responses• LTERM Override• ALTPCB destinations• Multiple ICALs• Recursive requests• Holding database locks across an ICAL request– Increased importance for performance tooling
    • IMS Version 1344Support for Truncated MessagesThe RECEIVE subfunction of the DL/I ICAL is enhanced to enableapplications to efficiently receive large messages that did not fit into apreviously specified response area.New “RECEIVE” subfunction code can be used to get truncatedmessage– IMS 13 keeps a copy of the entire response message in the control regionprivate storageBenefit– Provides the ability to complete the retrieval of a reply message• Without having to re-issue a complete ICAL “SENDRECV” and associatednetwork transmission costs
    • IMS Version 1345ISC Over TCP/IPISC Over TCP/IP value proposition– New option that supports TCP/IP network connectivity for IntersystemCommunication (ISC) connections• IMS – CICSProvides a strategic protocol alternative to SNA/VTAM• Allows an all inclusive TCP/IP solution for networks
    • IMS Version 1346ISC Over TCP/IPHighlights– Supports both static and dynamic terminals• Static terminal definitions– SYSGEN stage 1 TYPE, TERMINAL, SUBPOOL macros– DFSDCxxx PROCLIB member• Dynamic terminal specification– Logon descriptors in the DFSDSCMx or DFSDSCTy PROCLIB member– Leverages IMS Connect• Enhancements to the HWSCFGxx configuration member– No IMS Connect user message exit changes– Uses CSL to communicate between IMS and IMS Connect• Requires Structured Call Interface (SCI) and Operation Manager (OM)– Requires CICS Transaction Server for z/OS 5.1
    • IMS Version 1347OTMA Enhancements …OTMA destination descriptor enhancements– TYPE={MQSERIES}• Provides asynchronous callout and messaging support (ISRT ALTPCB)– EXIT={YES | NO}• Specifies whether or not the OTMA exits are to be calledCorresponding enhancement to IMS Type-2 OTMADESC commands– [CREATE | UPDATE | DELETE |QUERY] OTMADESC• Recovered across warm and emergency restartsBenefits– Simplifies asynchronous messaging to WMQ– Removes the need to code the OTMA exits, DFSYPRX0 and DFSYDRU0– Provides dynamic change capability with the Type-2 commands
    • IMS Version 1348OTMA EnhancementsOTMA early termination notification– Enhancement that allows OTMA to leave the XCF group earlier intermination processing• Allows OTMA clients (IMS Connect, WebSphere MQ, OTMA C/I) to benotified of the termination via their XCF Group Exit– Can route requests to other systems– Addresses issues associated with transactions messages being accepted butnot processed– Function being added to IMS 12: APAR PM73869
    • IMS Version 1349Enhancements for the Non-Discardable Messages ExitRoutineCustomer requirement for a new function to PSTOP an abendingtransaction– Stops scheduling but allows queueing to continueNew functions provided by for the DFSNDMX0, the Non-DiscardableMessages exit routine– IMS 11 APAR PM67950 / PTF UK81040– IMS 12 APAR PM45943 / PTF UK71989– Included in IMS 13
    • IMS Version 1350Summary of IMS 13 Transaction Manager andConnectivity TopicsCallout function enhancementsISC Over TCP/IPOTMA enhancementsNon-Discardable Message Exit (DFSNDMX0) enhancements
    • IMS Version 1351IMS 13 Database and DBRC EnhancementsDatabase VersioningHALDB AlterDEDB AlterDBRC Enhancements
    • IMS Version 1352Database Versioning Overview …Database Versioning provides the ability to assign user-definedversion identifiers to different versions of a database structure– Enables structural changes to a database while providing multiple views ofthe physical IMS data to application programsApplications referencing a new physical database structure can bebrought online without affecting applications that use previousdatabase structures– Applications which do not require sensitivity to the new physical structure,do not need to be modified and can continue to access the databaseBenefit– Minimizes impact and reduces cost associated with making andcoordinating coding changes to affected application programs when aphysical database structure changes
    • IMS Version 1353Database Versioning OverviewDatabase Versioning supports the following database types– DEDB– HDAM– HIDAM– PHDAM– PHIDAMCan be used in conjunction with the database alter functions to keeptrack of different versions of the structure of a database– only supports the following database structure changes• For all supported database types– Increasing the length of a segment– Adding a new field to space at the end of a segment• For Full-Function and HALDB database types– Adding new field(s) that remap existing field(s) and space at the end of asegment
    • IMS Version 1354Database Versioning must be enabled in DFSDFxxx DATABASEsectionVersioning is at the DBD level– Users define the version of a database definition on the DBD– Version numbers must be maintained in incremented valuesDatabase Versioning requires enablement of the IMS catalog– DBD definitions for versioned databases must be in the IMS catalogApplication programs can elect the desired database version– Specifying the version number on the PCB of the PSB– Specifying the version number on a DL/I INIT VERSION callDatabase Versioning Requirements
    • IMS Version 1355DFSDFxxx PROCLIB: new DATABASE section keywords– Specify whether database versioning is enabled and default version• DBVERSION=• DBLEVEL=Database and Program Generation Statements– Specify the database version number• DBD: DBVER=• PCB: DBVER=– Override the default versioning specified in DFSDFxxx• PSBGEN: DBLEVEL=“INIT VERSION” DL/I Call– Overrides the version number that is specified on the PCB statement– Must be issued before issuing a DL/I DB call to the databaseDatabase Versioning Implementation
    • IMS Version 1356HALDB Alter Overview …Structural changes can be made to HALDB databases while thedatabase remains online– Add a new field to space at the end of an existing segment– Increase the length of an existing segment– Define new fields that remap existing fields and space in an existingsegmentBenefit– Make structural changes to a database while maintaining databaseavailability
    • IMS Version 1357HALDB Alter OverviewHALDB Alter is only supported for database types:– PHDAM– PHIDAMAfter changes are made to the DBD segment definition– Type-2 INITIATE OLREORG command is used to alter a database fromthe current structure to the new structure• Type-1 command /INITIATE OLREORG does not support altering aHALDB– Online Change commands are used to bring the changed ACBLIB DBDmember online– Application programs can start using the new database structure
    • IMS Version 1358FIELD 1FIELD 1FIELD 2 SpaceFIELD 2 SpaceNewFIELD 3Add a new field to space at the end of a segmentExample 1Example 2FIELD 1FIELD 1 FIELD 2FIELD 2 SpaceNewFIELD 3Space
    • IMS Version 1359FIELD 1FIELD 1FIELD 2New SpaceFIELD 2Increase the length of an existing segmentExample 1Example 2FIELD 1FIELD 1 FIELD 2FIELD 2New SpaceSpaceSpace
    • IMS Version 1360HALDB Alter PrerequisitesSoftware requirements– CSL• SCI• OM– DBRC RECON MINVERS (‘13.1’)
    • IMS Version 1361DEDB AlterIMS 13 adds ability to dynamically change DEDB specifications– Users can dynamically change UOW, SIZE, ROOT, Randomizer while DEDB isonline– New DEDB Alter utility is used for DEDB changes– DRD is not required for DEDB Alter– Supports VSO Areas if /VUNLOAD is done before DEDB Alter is executedBenefits– Improved management of DEDB definitions• Eliminate system down time for modifications to DEDB definitions• Improve data availability since changes are done while DEDB is online
    • IMS Version 1362DEDB Alter UtilityThe new DEDB Alter utility is used to change the following itemswithout taking the area offline– The SIZE, UOW, or ROOT specifications of a DEDB area– The randomizer that is used for the DEDB areaRequirements– A two-stage randomizer must be used, which enables areas to beprocessed individually.– DEDBs to be altered must be registered to DBRC– The MINVERS value in the RECON data set for all IMS subsystems thatshare the DEDB area must be at “13.1” or later– If SDEPS present, only the randomizer name can be changed
    • IMS Version 1363DBRC EnhancementsCommand support for HALDB AlterCommand support for DEDB AlterMINVERS value of ’13.1’ must be set to use HALDB Alter, DEDB Alter,or synchronous program switch in a shared queues environmentSupported Migration and Coexistence– IMS 11 to IMS 13• Apply DBRC coexistence SPE APAR PM53134 to IMS 11– PTF UK80026• Allow IMS 11 to understand IMS 13 RECON records– IMS 12 to IMS 13• Apply DBRC coexistence SPE APAR PM53139 to IMS 12– PTF UK80027• Allow IMS 12 to understand IMS 13 RECON records
    • IMS Version 1364Summary of IMS 13 Database Manager and DBRC TopicsDatabase versioningHALDB AlterDEDB AlterDBRC enhancements
    • IMS Version 1365IMS 13 HighlightsSystem– IMS CONNECT enhancements• XML Converter Enhancements• Expanded Recorder TraceRecords• Reporting of overall health toWorkload Manager (WLM)– Concurrent application threads– Reduced Total Cost of Ownership(TCO)– Elimination of SECURITY Macro– User Exit enhancements– JDR support for ESAF– DIAG command enhancementsDatabase and DBRC– Database Versioning– HALDB Alter– DEDB Alter– DBRC support for HALDB Alter andDEDB AlterTM and Connectivity– Synchronous program switch– ISC TCP/IP Links– OTMA destination descriptorenhancements– and more!65