THE publication of the IDMS User Association The CA-IDMS Database and Applications User Association http://www.iuassn.com October 2010, Number 73 Introduction from Bill McCracken, CEO CA Technologies INSIDE THIS ISSUE I am pleased to introduce the latest issue of Introduction from Bill McCracken...1 Connections to our international community Message from International Chair ...2 of CA IDMS users. As Letter from the Editor...2 you know, the Mainframe’s resurgence has been driven Realizing the Benefits of Server CA IDMS” R17...3 by immense pressure to meet key business demands “CA World Corner”...4 while minimizing cost. The security, efficiency and IDMS User Association at CARE 2010...5 stability of the Mainframe make it the platform of choice for supporting some of the biggest and most transaction- Database Segmentation...7 intensive workloads in the industry. With its 30-year record as a mainstay of the data center, the mainframe is Remote Attendees at CMUG...10 enjoying renewed prominence as organizations seek to both manage mission-critical business information and Faulty CA Product 25 Years On:...11 support new technology approaches like cloud computing. CICS Threadsafe for IDMS Users...13 At CA Technologies, we continue to make major investments in our Mainframe 2.0 strategy and deliver IDMS Release 17 Migration Challenges...14 innovative technology to help customers leverage their investments and increase their business agility. Because ­­IDMS Release 18 Status...17 you depend on CA IDMS to manage critical data and drive business intelligence projects, we have modernized CA IDMS™ R16 – New End of Service Date!...17 it to support today’s applications, increased integration CA No Longer Distributing Some Source - with CA products for better administration, management and security, and made enhancements focused on Clarification...18 lowering total cost of ownership by capitalizing on Explaining “Deadlocks” to the Layman...18 new hardware and software technologies like IBM’s zIIP specialty processor. We will continue to support new Space Management Locks...19 releases of IBM hardware and firmware, and leverage new capabilities to help you find the most cost-effective ways Agenda of the BIUA, Thursday October 28th...19 to meet SLAs. In an ever-changing IT industry, the mainframe continues Is IDMS r17 z/IIP Exploitation Right for You?...20 to provide the power and performance that drive business Introduction to Relational Databases and SQL...21 success. On behalf of everyone at CA Technologies, I want to thank you for your support. We look forward to FAQs About CA IDMS™ Indexing...23 helping you make the most of the Mainframe. CA IDMS/DB r17 is a proven, reliable, high-performance, Web-enabled DBMS for IBM System z that provides unparalleled business value for hundreds of enterprises

1 Letter from the Editor Message from Well here we are – a month International late – but on schedule for the revised schedule – in accordance Chair with best project Management By Linda Casey principles: Set extremely low customer expectations and then try to do the very little bit that you promised!

Community…past, present and future. In retrospect we seem to have another very full issue for you – so we hope that you will Social media is all the rage these days; Facebook, find that it was worth the wait. On the news front, since MySpace, LinkedIn, Twitter, and on and on. We see it the last edition of “IDMS Connections” we have had: at home, at work, on our phones, in advertising. It’s CARE and CA World 2010, May Mainframe Madness, everywhere. But at the root of all of these tools is the announcement of CA IDMS Release 18.0 Beta cycle, idea of community and connections. As members of Release 17.0 of IDMS Server, and the launch of the new the IUA, the idea of community isn’t new to any of CA Portal – a single web presence for Support, User us. We’ve been connected in community for years. It’s Communities, and personally tailored “My CA” pages. our strength as a community that supports, promotes and influences the IDMS product line and through our The IUA has been busy trying to populate the IUA/EIUA strength as a community that we support one another. web presence at the new CA User Community portal with Long before the new social media was a blip on the screen, lots of useful content, for example: the new format User the IUA had strong community bonds. We connected Contributed Library has been uploaded, you can find the to one another through conferences, newsletters, emails last 12 “soft copy” editions of “IUA/IDMS Connections”, and through our LISTSERV list, IDMS-L. I would as well as this edition – perhaps you even downloaded this venture to say that the IUA has been in the forefront of edition from the user Community portal? community building with our strength as an organization. You can view and download this year’s CA World 2010 I’m told repeatedly that our user community is unique presentations http://caworld.ca.com/talk/presentations ! among other organizations in our commitment to our shared interest (IDMS) and each other. Talking about what to find, and where, on the web – the new CA Portal for Support and User Communities are We live in a time of a tough global economy. Many at http://support.ca.com , and of course the existing IUA cannot travel to conferences or educational offerings. web presence with links to the archives of IDMS-L and So we continue turn to one another for support and back issues of “IDMS Connections” is: http://iuassn.org ! guidance. The amount of informal learning that happens over the list is astounding. Over the past year, we’ve seen Here goes – hoping that each of you will find some requests of ranging from help for DBAs new to IDMS, to value in this issue of “IDMS Connections”. If you don’t shops expanding their access to IDMS to modernize their enjoy the experience, please feel free to provide feedback applications, and everything in between. about what we could do differently. The last piece of feedback we had was that the publication name mystified As our community expands and changes, the IUA as an some people – so we changed the name to “IDMS organization must review how we serve our community Connections”! What else can we do for you – the IDMS and what makes sense for the future; how can we User Community, whether you are part of IUA, EIUA, modernize our organization? In the coming months, we BIUA, UKIUA or OZIUA? will be looking at ways to create a cost effective, inclusive “face lift” for our community. This is not an exercise the That’s all there is – because there is no more! board can undertake alone. I call on each and every one of you to think about how the IUA can serve you and our Gary Cherlet membership into the future and give us your input. mailto:[email protected] At the CARE conference this past spring, CA has unveiled Justice Technology Services (Department of Justice - South their new community website. This site is free of charge Australia) to the IUA and its members. The IUA has begun to IUA Board Member Responsible for IDMS Connections have a presence there, thanks primarily to Gary Cherlet President Australian IDMS Database User Group (OZIUA) who has worked hard on migrating much of the archival information from our website. I invite all of you to checkout our new community there.

2 Realizing the Benefits of CA Hibernate Dialect Hibernate is an open-source product, distributed by Red IDMS™ Server r17 Hat, that simplifies Java development by taking care of Reprinted from “CA Tech Insider: CA IDMS” the details of data storage and retrieval. With Hibernate, CA IDMS works in much the same way as any other Copyright © 2010 CA. acknowledged relational DBMS and therefore allows Java programmers [Editor’s note: having mentioned IDMS Server 17.0 in to be productive without extensive CA IDMS training “Letter from the Editor” – I thought I might include this or expertise. A Java class called a dialect specifies IDMS- release from CA - Gary] unique properties and is now included as part of CA IDMS Server r17. CA IDMS Server couples standards-based Web access with proven technologies to help your organization Scrollable Result Sets achieve the objectives of secure, optimized, high- A scrollable result set allows a cursor to move both performance access to your CA IDMS mainframe forwards and backwards, or to be set to a specific row. An resources from various distributed platforms. The updateable result set can be updated using Java methods 17.0 release of CA IDMS Server contains several new instead of SQL DML statements. CA IDMS Server r17 features that will be beneficial to CA IDMS Server users supports scrollable result sets by caching rows fetched improving performance, scalability, platform support, from CA IDMS, and supports updateable result sets standards compliance and usability. Below are descriptions when used with an implementation of the CachedRowSet of the new features contained in CA IDMS Server r17: interface, such as the one provided with the Java 1.6 run- time library. ODBC Wire Protocol Similar to the JDBC Type 4 interface, CA IDMS Server's Procedure Result Sets ODBC Driver now provides direct communications from CA IDMS r17 introduced a feature in which SQL Windows to your CA IDMS CV, eliminating the need for procedures can return result sets, not just a single set CA CCI. This shortened communications path improves of output parameters. CA IDMS Server r17 makes this both responsiveness and reliability. feature available to JDBC and ODBC programs. This means that sites no longer need to code table procedures 64-bit Support in COBOL, Assembler or PL/I to return multiple rows to As more and more 64-bit products are seeing mainstream a JDBC or ODBC program. use, the demand for a 64-bit version of the CA IDMS ODBC Driver has been ever on the increase. This demand Simplified Configuration is satisfied with the r17 version of CA IDMS Server. In line with CA's efforts to simplify the management of Unlike the transition from 16 to 32-bit Windows (where its products, the CA IDMS Server ODBC Administration 32-bit applications could call 16-bit applications and vice- tool has been enhanced to simplify the creation and versa), 64-bit applications cannot make calls to functions management of your IDMS Data Sources. residing in 32-bit DLL's in Win64. These are just a few of the many features provided in CA ODBC 3.5 IDMS Server 17.0. CA IDMS Server r17 can be installed Release 17 of CA IDMS Server now supports ODBC 3.5, alongside any other prior version of CA IDMS Server, which is the current version of the ODBC specification allowing users to gently transition to the new version of from Microsoft. Most ODBC applications are now the product. To get specific detailed information on these written using one of the ODBC 3.x specifications. and other features, please see the CA IDMS Server r17 Product Brief. CA IDMS Server 17.0 is now Generally JDBC 4.0 Available (GA) and can be downloaded from CA Support CA IDMS Server r17 has implemented JDBC 4.0, the Online. latest version of the JDBC API architected by Sun Copyright © 2010 CA. All rights reserved. Microsystems (now Oracle) and the Java Community Process. This provides compatibility with newer releases of popular application servers, such as WebSphere Application Server 7.0 and Weblogic 10.3. Named Parameters The named parameter feature allows JDBC or ODBC programs to bind values to SQL CALL statement parameters using the parameter names specified in the CA IDMS CREATE PROCEDURE statement.

3 “CA World Corner” Technology Systems enlightened the audience as he consolidated 13 years of IDMS system tuning into 60 minutes. Laura Rochon from Ajilon Consulting showed how TCP/IP can be used to save money. Judy Dillman’s CA IDMS r18 Preview was a highlight of the conference. She gave a preview of what will be coming in CA IDMS 18.0 which included an overview of the new features and described the integration with CA Mainframe Software Manager. Several other CA sessions were presented including CA IDMS Server r17 Improves Performance and Scalability and Living with Very Large CA IDMS Databases. Networking Along with the great technical content in the IDMS track, there were many opportunities for networking. CA Support and Development staff were available in the CA World 2010 Technical Campground for discussion of any issue. Many CA World returned to Las Vegas this past May, and to clients took advantage of this opportunity to talk one- the beautiful Mandalay Bay Resort and Casino. The on-one with the staff. Once again we held our Birds of week full of technical sessions began with a full day free a Feather session where we filled the room with IDMS pre-conference education “CA IDMS Performance and customers and filled the hour with some great discussions Tuning” on Saturday. During a morning of keynotes on a variety of topics. New this year for the Mainframe on Monday, CA IDMS customer CAIXA received the Focus area was the MIPS lounge. This lounge, located “Impact” award as one of the three MIP awards given out next to the Technical Campground and near the session at the Mainframe Focus area opening. Then Art Cartier, rooms, offered a place to sit and network with peers and the new Vice President of Software Engineering for the take advantage of the some comfortable furniture while CA IDMS product line, presented CA IDMS Status and watching May Mainframe Madness presentations on Plans with Greg Beedy. They reinforced CA’s commitment monitors around the lounge. to CA IDMS. They discussed where CA IDMS fits into the MF 2.0 strategy, what’s available today within the product line and what’s coming next. Greg highlighted application modernization which was a big theme in our track this year. His modernization approaches session, with co-speaker Sergio Medeiros of CAIXA, laid the ground work for the rest of the modernization sessions that followed from CA and other partners, and ending with a session on moving IDMS application to SOA from Javier Sotela of Evertec, Inc.

Events CA World was full of wonderful events for attendees. Maroon 5 gave a private concert to all the attendees on the Beach at Mandalay Bay. It was a beautiful night to relax, put on your CA Technologies flip flops and mellow out to some music with your toes in the sand and a cocktail in hand. But Mainframers had an exclusive event on Wednesday night at the House of Blues that was the envy of all other focus areas. “Our Roots Run Deep” was the theme for the night featuring music by Lee Rocker of the Stray Cats. IDMS was well represented on the dance floor! May Mainframe Madness There was much more madness in May than just CA Expanding on what’s available in the product today, we World. CA May Mainframe Madness 2010 was indeed the had several customer sessions on experiences with r17. virtual event that changed everything. CA again dedicated Steve Terry from BT gave an informative session on their the entire month of May to the mainframe and to helping production experiences with IDMS r17, including use you get even more value from this amazing platform, with of the z/IIP feature and TUNE INDEX utility. Chris a calendar full of activities and new live content every Hoelscher from Humana gave a session on their improved results using the zIIP feature. Gary Cherlet from Justice (continued on page 5)

4 CA World Corner... cont’d from page 4 . There is a need for IT executives and professionals to understand the transformation weekday in May. Several of the panels at CA World were and what it means to business and government also simulcast live like the “Exploiting zIIP and zAAP” panel discussion. CA IDMS had a full slate of session . Increase IUA use of User Communities portal at available to complement its CA World offerings. Chris http://ca.com/community Hoelscher of Humana graciously volunteered to record his CA World session “Humana Adds Some z/IIP to its . Need to continue to maintain use of the List Server, CA IDMS Processing” as well as a session on CA IDMS but integrate it with Message Board and/or blogs on r17 Migration Challenges. Other CA IDMS sessions the new User Community portal available were on topics TUNE INDEX, PRINT INDEX, . Emphasis on Web 2.0 and inclusion of social CA IDMS Health Checks, CA IDMS Server r17, CA networking tools, Community Management tools IDMS DML Online and CA ADS Alive. If you missed and other new and potentially useful functionality CA World you can still hear about CA IDMS Status and Plans from Art Cartier and Greg Beedy. This session . Importance of incremental change to things and all the CA IDMS May Mainframe Madness sessions people are comfortable with can still be viewed at http://www.ca.com/us/products/ . Applies to Community Management collateral.aspx?cid=200360. . Applies to Community Management tools So as I look back on this successful CA World, I must recognize Steve Rundle from BT for all his contributions . IUA needs to be careful about member reliance to the CA World planning for the IDMS track as the on IDMS-L customer committee member. He always provides great input into the planning process and helps shape the . New User Community portal means better agenda. Thanks again to all the customers who presented membership management between RUGs and PLCs sessions at CA World. The conference would not have - easier for members - only need to sign up once been a success without you. So mark your calendars for and become registered at all levels - means members the next CA World, scheduled for November 13-17, 2011. can participate at both a Regional and International You can view and download this year’s presentations on level - means IUA Board can manage members and http://caworld.ca.com/talk/presentations. mailing (for example) at an International and/or Regional level Carla Pereira Social Media thoughts for the day CA IDMS Track Leader What’s your personal brand? What’s your professional brand? Be the best that you can be! . Use IDMS Connections to promote use of CA User Community portal and the http://iuassn.com link Let’s celebrate... . Regular communications to members is a must! another successful CA World, and to celebrate the ongoing resurgence of the Mainframe! A great buzz for me was being . Start fortnightly posts on IDMS-L a part of CARE and CA World yet again. It just seems to keep (Communications portfolio): getting better! . Encourage members to register at CA User IDMS User Association at Community portal CARE 2010 . Monthly activity updates . 130 attendees representing 116 groups and 16,530 . IDMS Connections announcements users . IUA news - now (e.g. Board elections at CA . Community 2.0 - forums, User Communities and World) etc... Regional User Groups all rolled into the . Recruitment and placement web sites should have “Community 2.0” presence on the CA Portal links to IUA web presence . Don Tapscott - the digital generation and the need . IDMS’ers to show IUA membership/participation to embrace social networking into the business on resumes model of corporations, government - and of course User Communities (continued on page 6) . 1997 “Growing Up Digital” . 2010 “Grown Up Digital” . Transformation of web from “presentation and content” to “computation and services”

5 IDMS User Association at CARE 2010... cont’d from page 6 . Excellent IDMS stream - track leader Carla Pereira - stream keynote by Art Cartier for first time - all IT thought for the day the usual suspects (John, Judy D, Dave, Cal, etc) - If 80-90% of the IT budget is required to maintain the excellent user sessions status quo - how can you innovate? . Status and Plans and Release 18 direction - some Can you afford to do the risky things? users have gone from complaining that CA was no CARE 2010 Blue Slipping Exercise longer supporting IDMS to asking CA to either slow the release/upgrade cycle or to allow for a “Blue Slipping” is a technique used by the US Congress longer sunset clause for most recent “drop support to get down to the heart of an issue in very quick order. release” The technique was applied during CARE to find out what the critical areas of concern and primary focus areas are . Ongoing resurgence of the Mainframe for each User Community. Below is the outcome of the IDMS User Community “Blue Slipping” exercise: . New mainframe business picking up in the last 2 years since Mainframe 2.0 IUA Objectives . Accelerating at 20% year on year . Meeting place for people with common interests (IDMS) . At press conference the mainframe session (Mark Combes) had the best questions and most . Collate relevant information engaged press of all CA press sessions (including . Share relevant information Cloud) CA’s Help to IUA . Special interest from European press on . Speakers rejuvenation of the mainframe . Web content OZIUA wants to try to revitalise its meeting program and membership numbers by trying to expand the CA IDMS . Cross posts (list server to CA Portal) focus - to include any and all things Mainframe. Anything in fact that resides on the same LPARs as the IDMS Partner to CA regions run in. . Help users to help themselves IDMS users should be aware of other technologies . Reduce reliance on CA beside IDMS. Non-IDMS mainframe users who need to communicate to/from mainframes that have IDMS should . Feedback on products and documentation (and be aware of the capabilities in IDMS that can facilitate training?) this communication. Product Change This may or may not be a direction that other RUGs . DARS process want to follow - but it may be something well worth Volunteers considering at both the Regional and International level of the IUA - the time has come to broaden the focus to . Whipping? the mainframe in general in order to promote, in our case, Collaborate IDMS in particular! . E-mail via list server Any all feedback from IUA members on these thoughts . Newsletter would be most welcome! Engage Gary Cherlet (Justice Technology Services) . How to engage user community User Group President IUA International Board Member . Provide useful knowledge IUA Board Member responsible for “IDMS Connections” . Provide useful content mailto:[email protected] . Facilitate meaningful exchanges . Between users . with CA My IDMS “Stream” at CA World 2010 send article . Great keynotes: Technology (Ajei Gopal), leadership and creativity (James Cameron), ongoing resurgence contributions of the Mainframe (Dayton Samerjian) to Gary Cherlet at: [email protected]

6 Database Segmentation Vertical segmentation may require some structural database changes due to restrictions enforced by multiple Today’s CA IDMS databases continue to grow. Among page group support which may in turn cause some the reasons for this growth may be the addition of new application changes. However the use of multiple page application functionality, business consolidations, or the group support allows the database to appear to the inability to archive historical data from legacy databases. application at run-time as a single entity. The restrictions Regardless of the reason for their growth this expansion currently enforced by mixed page group support are as creates concerns in two areas; space and time. The follows: concern with space is typically not related to the number of physical devices needed to contain the data but with . Sets, indexes, and referential constraints may not the number of CA IDMS pages that are available in cross page group boundaries which a given database can reside. Larger databases also . Record names must be unique mean that the time required by applications to perform routine processing also increases. This can be especially . Unqualified FIND/OBTAIN DML commands meaningful when considering batch processes or routine should not be issued within mixed page group run- maintenance operations. units. This article presents an overview of two types of database To provide a simple illustration of vertical segmentation segmentation generally referred to as vertical and consider a multi-national corporation that has an Order- horizontal segmentation. Although each segmentation Entry database that is approaching the approximate 16 implementation is unique by database, the general million page range limitation. This database is composed concepts of these two methods of segmentation provide of CA IDMS areas that break down into three functional the basis from which all segmentation strategies are areas; customer data, order data, and invoice data. All derived. areas are defined in one single CA IDMS segment that uses the default page group value of 0 for the segment. Before continuing it is important to define the terms ‘CA IDMS segment’ and ‘database segment’. The use of CA IDMS segment in this article will refer to the CA IDMS entity known as a SEGMENT which is created by the ADD SEGMENT command. Within a CA IDMS segment a user defines the files, areas, page group, and their related pages ranges that define the physical implementation of a portion of a database. A database segment will be considered to be a logical grouping of any number of CA IDMS segments and equates to the database view known by the application. A database segment is typically implemented by grouping the required CA IDMS segments within a DBNAME by using the ADD DBNAME statement when creating a DBTABLE.

Vertical Segmentation The first step to implementing vertical segmentation on Vertical segmentation is the practice of dividing a database the Order-Entry database is to identify the functional into separate functional portions and is implemented at group into which each CA IDMS database area belongs. the area level. Areas within the same functional portion Any cross-area sets between areas identified as being in of the database can then be grouped together into the different functional groups must be replaced with some same CA IDMS segment and if desired, each CA IDMS other construct which will allow the run-time processing segment defined to the database can be assigned to a using these sets to be retained. Almost always these types different page group. of changes will require some level of application changes. This highlights the fact that any form of database A standard implementation of CA IDMS limits any one segmentation is not just a Database Administrator database to a finite range of database pages which is in function but is a task requiring the commitment of a site’s the area of 16 million pages if a standard dbkey structure entire organization. is used. To remove this restriction CA IDMS provides a feature know as page groups. Areas defined in different page groups are permitted to have overlapping pages ranges. Through the use of mixed page group support a single database transaction has the ability to access areas defined in different page groups creating an almost inexhaustible number of database pages available for use by a database. For details about implementing mixed page group support refer to the Mixed Page Group Implementation article in Volume 72 of the Connections newsletter, dated March 2010. (continued on page 8) 7 Database Segmentation... cont’d from page 7 they are issued. It is best to insert the name of the desired record type into each of these commands to avoid the The following diagram is an example of a set relationship potential of improper database accesses. which crosses area boundaries where the areas are in different functional areas or ‘vertical segments’. The segment used to define the database to the physical environment should then be broken into three separate CUST-ORD CA IDMS segments. Each segment definition will SORTED NPO ORD-NUM contain only those areas participating in that segment’s CUSTOMER ORDER functional group. Assuming a standard database key CUST-NUM CALC ORD-NUM CALC structure, each vertical segment will have approximately CUSTOMER-AREA ORDER-AREA 16 million database pages available to it for a total of about 48 million pages for the entire database. Figure 2 One option would be to replace the CUST-ORD set with a system-owned index where the new index would reside in an area to be included in the ORDER vertical segment. In this case the name of the index could still be CUST- ORD to minimize the scope of the application changes.

CUST-ORD CUSTOMER ORDER I MA ASC CUST-NUM, ORD-NUM CUST-NUM CALC ORD-NUM CALC ORD CUSTOMER-AREA ORDER-AREA -INDEX-AREA

Figure 3 Horizontal Segmentation A second option would be to add a ‘dummy’ Vertical segmentation can provide a site with significant CUSTOMER record into the ORDER-AREA area. relief when approaching the maximum number of This record would only contain the calckey of the database pages available in which that database can reside. corresponding CUSTOMER from the CUSTOMER- However the applications using that database must still AREA area and would be used to connect all of the view and process it in its entirety. As databases grow ORDER records owned by each customer. or a site’s processing needs evolve, the amount of time required to perform standard application processing may CUSTOMER ORDER become too large for the available window. A horizontal CUST-NUM CALC ORD-NUM CALC segmentation strategy allows the database to be divided CUSTOMER-AREA ORDER-AREA along some site specific criteria creating multiple yet functionally equivalent databases. These smaller databases

CALC ORDER-AREA CUST-ORD can be processed independently of each other based on a SORTED NPO site’s requirements. ORD-NUM Horizontal segmentation begins with the selection of the segmentation criteria. The segmentation criteria CUST-DUM used is based on the application requirements and may CUST-NUM CALC consider divisions along geographic boundaries or ORDER-AREA company divisions. Sometimes time/date relationships are used such as a separate database segment per business Figure 4 or calendar year, while in other cases some sort of The second restriction imposed on vertical segmentation artificial segmentation key is created. For our example by mixed page group support is that all record we will continue to use the Order-Entry Database with names must be unique. Schema requirements for an the scenario of a corporation that transacts business unsegmented non-SQL database would already impose in Europe and North America. Initially they created this restriction so it is typically a non-issue when a single database structure to support their business in implementing a vertical segmentation strategy. However each geographical location. However the requirement to we will see the effect of this restriction while examining delay all batch processing until the North America online the topic of horizontal segmentation. day is completed has made it very difficult to finish that processing before the next European online day begins. Finally care should be taken to avoid all unqualified DML commands used by the associated application within The database structure must be examined to identify any mixed page group run-units. These commands would be structures that will be common to both the Europe and FIND/OBTAIN DB-KEY commands that do not include North America segments. These structures may include a record name. Although it is possible to use these records that are used as tables to control processing commands they do possess the possibility of returning or may be corporate level records that summarize the the wrong record based on run-unit currency at the time (continued on page 9) 8 Database Segmentation... cont’d from page 8 With the above segmentation of the Order-Entry Database and the defined DBNAMEs the organization high-level business of the organization. These records will now be able to start batch processing for Europe as must be removed from CA IDMS areas in which records soon as the European online window closes and while that will be unique to a given geographical segment will the North American online window is still open. In the reside and must be placed into their own areas. These same manner the North America batch processing will common areas will ultimately be defined to the physical not have to be completed before the next morning’s environment through their own CA IDMS segment European online window opens. However there are a few definitions. In addition, if any set relationships exist items that must be taken into consideration to make the between records moved to the common segment and horizontal segmentation successful. records that will be in a geographical segment they must be replaced with alternate structures as discussed under It is extremely important that no application process the topic of Vertical Segmentation. update the database areas assigned to the COMMON segment while performing update operations against The following diagram is a simple representation of the either the EUROPE or NORAMER segments. To do Order-Entry Database following the initial separation so would compromise the independence between the along the geographical lines. database segments that the horizontal segmentation strategy hoped to provide. As an example let’s say that for a given day the batch processing for Europe had been completed and North America’s batch processing was nearing completion. However both of these processing threads update records in the COMMON segment while updating their respective segmented areas. Some one then realizes that the Europe batch processing was run with incorrect input parameters requiring that processing to be rolled back and Europe’s batch jobs to be rerun. Since updates were made to the COMMON segment it is necessary to include that segment as part of the ROLLBACK operation. Rolling back the COMMON segment will also roll out any updates that the North America processes made, forcing the NORAMER segment to also be included in the ROLLBACK operation. You are now in or near the It should be noted that vertical segmentation can be used start of both online windows with no batch processing in conjunction with horizontal segmentation as space completed. requirements dictate. CA IDMS segments EUROPE, NORAMER, and COMMON could each be defined as All updating of the COMMON segment should be being in different page groups. In the same manner the isolated from update processing of the other geographical three functional portions of each geographical database segments and scheduled at a time when they will not segment (EUROPE and NOAMER) could be defined in affect the independence of the other database segments. their own CA IDMS segments which could be assigned to When the need to update the COMMON segment different page groups as long as their separation conforms concurrently with another database segment is discovered to the rules of mixed page group support. it may be necessary to remove those affected records from the COMMON segment and replicate them in each The desired end result of our horizontal segmentation is geographical segment. Sometimes there is truly a singular that a single version of the application programs will be entity that must reflect some result of both batch cycles. able to process either the Europe portion of the database In this case you could retain that information in an or the North America segment using the same schema/ intermediate file and update the COMMON area when all subschema specifications. This is accomplished by other required processing is completed. If either of these supplying the appropriate DBNAME to the programs at methods were used our scenario would have resulted in run-time. Each DBNAME indicates which segments are the Europe batch processing to be rerun and their online to be referenced during processing. The following is a window being delayed but there would have been no simplified example of the definition of the DBNAMEs. impact on the North America environment. ADD DBNAME EURDB Another concern is the CA IDMS restriction that a INCLUDE SEGMENT EUROPE transaction cannot have multiple areas with duplicate INCLUDE SEGMENT COMMON; names or records with non-unique names within a non-SQL database. This is similar to the restrictions ADD DBNAME NAMDB mentioned earlier when using mixed page group support. INCLUDE SEGMENT NORAMER As a result it is not allowed to access the areas defined to INCLUDE SEGMENT COMMON; the EUROPE and NORAMER segments in the same database transaction. If there is a requirement to report

(continued on page 10) 9 Database Segmentation... cont’d from page 10 Remote Attendees at CMUG on all occurrences of a particular record type from both From Communications of IUA Board of the separated database segments it will be necessary to extract the data using multiple database transactions. Kay Rozeboom sent the following “thank you” to those This could be done with a single program that issues who had organized a “Live Meeting” broadcast of the two BIND RUN-UNIT commands differentiated by the Chicago IUA Regional User Group (CMUG) – the guts unique DBNAMEs or could be done by two program of the message were: executions extracting data to intermediate files which are then merged to produce the desired report. “Thanks to Glen Guenther and CA staff for allowing others to attend the Chicago user group meeting Finally vertical and horizontal segmentation can reduce today via Live Meeting. The sessions were timely and the amount of time required to do standard maintenance interesting. This is an easy and inexpensive (free!) way to operations.UNLOAD/RELOADs, BACKUPs, and get additional training. I hope there will be more sessions index tuning or rebuilds can run in shorter periods of like it. Kay Rozeboom” time due to reduced volumes of data. For example, if the business in Europe grows unexpectedly the expansion of Diane Montstream, from the IUA Board, followed up areas associated with the EUROPE segment can be done with Craig McGregor (the RUG Chairman) with a without having to include the data associated with North question about numbers – by way of determining whether America. IUA should be having more meetings organized along the same lines – a “live meeting” that is “broadcast” using Summary “Live Meeting”, or similar technology. Very large CA IDMS databases can certainly pose a Below is Craig’s reply – sounds pretty positive to me! number of problems but these problems typically fall Cheers – Gary into the areas of space and processing time. CA IDMS provides the facilities to implement vertical and horizontal From: McGregor Craig - cmcgre [craig.mcgregor@ segmentation to eliminate these problems. The general acxiom.com] concepts of how to accomplish these strategies are Sent: Friday, 17 September 2010 2:09 not in themselves complex. However each database To: Diane Montstream; IUA Boardonly and application present unique conditions that often Cc: McGregor Craig - cmcgre; Bonnan Cindy - require some creative implementations of the basic cbonna; Guenther Glen - gguent concept. Unfortunately these implementations will Subject: RE: Thanks! often go beyond changes involving just a site’s Database Administrator and will include the application staff My understanding is that one point we had 17 people on and will sometimes result in visible changes to the the webcast itself. The lowest number of people on the organization’s users. As a result it is important to have webcast was 10. There was a total of 10 people in the CA the entire organization committed to these projects for Lisle office yesterday. Therefore I would say we had 20 to them to enjoy their greatest level of success. Although 27 people in attendance. I thought that was pretty good not always simple these modifications provide sites for our very first webcast!!!! with the ability for almost unlimited growth over the Craig S. Mc Gregor | Mainframe Database System foreseeable future. Programmer Global Technology Services Dick Weiland is a Senior Systems Engineer for CA IDMS 630-944-4899 office | 630-944-8948 fax Level II Support working out of the CA Lisle office. He began 3333 S Finley| Downers Grove, IL, 60515-5727 | USA | working with CA IDMS in 1977 as a DBA and joined [email protected]@Iowa.Gov Cullinet in 1981 in the Field Support organization. He moved to Level II Support in 1988 and is responsible for the DBMS engine and various utilities.

www.iuassn.org your portal to iua services and idms contacts

10 Faulty CA Product 25 Years On: CA Support “Rules” OK In years gone by CA, amongst other vendors, had received few kudos for product support. I am pleased to say that from what I can see in Australia, and from the CARE conference and the last 6 CA Worlds that this situation has seen a dramatic turn around. I thought that CA users might enjoy the following exchange of e-mails between a dissatisfied customer and CA – which serves to illustrate how seriously CA takes Customer Satisfaction!

From: Cherlet, Gary (JTS) have Barry confirm whether he has an extended support Sent: Friday, 20 August 2010 1:07 PM plan active for this? To: ‘[email protected]’; ‘greg.beedy@  ca.com’; ‘Cartier, Arthur J’; ‘Kent, Lisa’ Art Cc: Joyce, Barry (JTS); ‘DATA ENG SA IDMS’; ‘IUA Arthur Cartier Boardonly’ CA Technologies Subject: Faulty CA Product - 25 years on VP, Software Engineering Please find attached a photo of a CA product recently Tel: +1-860-627-4555 passed on to me by a work colleague. Fax: +1-860-654-1528 Mobile: +1-860-539-4401 [email protected]

Barry has used this product for years without incident until - as you can see from the picture – it has recently ceased to perform up to expectations, as per original design specifications. From: Catchlove, David [mailto:[email protected]] Are you able to help him out? Sent: Monday, August 23, 2010 9:23 AM TIA - kind regards – cheers – Gary To: Cherlet, Gary (JTS); Beedy, Gregory A; Cartier, Arthur J; Kent, Lisa Gary Cherlet Cc: Joyce, Barry (JTS); DATA ENG SA IDMS; IUA Boardonly Justice Technology Services Subject: RE: Faulty CA Product - 25 years on Department of Justice, SA Government Importance: High

“””” Telephone +61 (0)8 8226 5199 Hi Barry, @@ Facsimile +61 (0)8 8226 5311 We are sad to receive your news of poor performance of > Mobile +61 (0)41 333 1613 the CA product in question, as this is an extremely rare ~~ Mailto:[email protected] occurrence & most disappointing. Gary says: Grab them by their data - and their hearts and minds will follow! Following protracted consultation (read heated discus- sion) relating to the product in question regarding the apparent lack of warranty life (exceeds 90 days liability) and much debate regarding its obvious poor condition revolving around the apparent incorrect servicing & maintenance (especially the clear abuse that the unique From: Cartier, Arthur J [[email protected]] & highly intricate ‘Patent Pocket Positioning & Security Sent: Friday, 20 August 2010 9:57 PM Locator’ apparatus has suffered (read broken), AND the To: Cherlet, Gary (JTS); Catchlove, David; Beedy, fact that all the exquisitely applied identification expres- Gregory A; Kent, Lisa sions (painted words) have been callously maltreated, it Cc: Joyce, Barry (JTS); DATA ENG SA IDMS; IUA Boar- has been decided that no refund will be provided. donly However, in the interest of superior Customer Rela- Subject: RE: Faulty CA Product - 25 years on tions & Customer Satisfaction, PLUS in recognition of the Hmmm…I think this product has been already put outstanding loyalty & dedication you have shown toward through the End-of-Life cycle at CA. this product, we feel it only proper to replace it (see photo of the actual new authentic item attached) However there maybe an existing PTF we could send you providing you on an extended support plan. Can you

(continued on page 12)

11 Faulty CA Product... cont’d from page 11 In addition, I clearly remember issuing the care manual, which states that gloves should be worn at all times when Please note: This in no way constitutes an admission of using said product and that it is only good for 15 rulings product fault, as it behaves correctly in accordance with per week. This has obviously been ignored. the published specification. Please look after the replacement. Brenton Smith ca technologies Vice President & Area Manager Australia & NZ Tel: +61 2 8898 2860 Mobile: +61 412 892 100 twitter:brentoncatech [email protected] Please be advised that this is in recognition of your 25 year extended use is a one-off, & would ask that you keep it strictly confidential, lest there be others in the IDMS Community who would then embark on a similar program of mistreatment over the next 25 years simply to gain a similar replacement, thus provoking a run on this product which we would be unable to satisfy due to the In Conclusion fact the Numbers Painter has long since died (of old age). It goes without saying that with regard to the foregoing To optimize your long term use of this product, you will we must be careful about what we say so that we don’t benefit from exercising extreme care of use, coupled with violate the confidentiality clauses surrounding the a regular regime of weekly maintenance including wash- extended warranty for this product! CA might otherwise ing in spring water found only in the cave on the eastern be inundated with faulty pens, worn out hats, CA World side of the upper reaches at approx the 1856’ level of St back packs and heaven knows what else? Mary’s Peak in Wilpena Pound, South Australia with the However, if the measure of a vendor is in its commitment aid of a Chamois that was purchased in the Back Packers to support – then I think we can safely say that CA shop at the Base of K2 in the Himalayas will ensure that measures up – so “CA Support Rules OK”! this product will serve you for a period way past your cur- rent experience. Gary Cherlet A replacement has been dispatched to your Wakefield St Mainframe Technical Support Analyst address. Justice Technology Services Yours sincerely David Catchlove CA Technologies Channel Partner Manager Tel: +61 3 9944 6510 Mobile: +0412 438 160 [email protected]

idms-l where idms From: Smith, Brenton [[email protected]] Sent: Thursday, 2 September 2010 10:43 AM techies meet To: Catchlove, David; Cherlet, Gary (JTS); Kent, Lisa Subject: RE: Faulty CA Product - 25 years on Gary I want to go on record and say that clearly this product has been mistreated and not used in the manner intend- ed! When I sold this (because the brother of our current CA representative could not do so!) it worked!

12 CICS Threadsafe for IDMS Users Terry Schwartz IDMS System & Database Administrator Beginning with CICS Version 2, applications could execute on TCBs separate from the single threaded QR TCB. Much like multitasking in CA-IDMS this allowed CICS application programs to execute on multiple TCB’s and process concurrently. Thread-safe applications can achieve much higher throughput than single threaded applications. Until CA IDMS release 17 we in the IDMS world could not take full advantage of thread-safe applications. Before version 17 one could in theory mark the application programs as thread-safe but the IDMS interface calls would still have to switch to execute on the singled threaded QR TCB causing an unacceptable amount of TCB switching overhead. CA IDMS release 17 includes a thread-safe CICS interface that allows eligible applications and their CA IDMS calls to be dispatched on one of the multiple thread-safe TCB’s. One of our applications is a CICS based green screen application that was averaging approximately 800,000 IDMS task per day. Due to a business change in November of 2009 the number of users of the application almost doubled. Coinciding with the increase in users came large transaction backlogs in CICS during the peak morning and afternoon online periods. It seems CICS was at a processing threshold and the increase in volume had pushed CICS over the edge. With all the workload effectively limited to one processor we could not process all the work arriving at the peak times. It was decided that since CA IDMS was being upgraded to version 17 that we would take advantage of the thread-safe CICS interface No changes were made to the CA IDMS interface since we discovered that the interface takes the thread-safe mode from the application program that called the interface. Implementing a program as thread-safe requires a changes to the CEDA definition (or the auto-install setup) to change the Concurrency to “Threadsafe” There are some programming techniques that should be observed or thread switching can result;

CEDA example; Use of the CICS common work area (CWA) should OBJECT CHARACTERISTICS CICS RELEASE = 0650 be avoided if at all possible (that is, set SIT parameter CEDA View PROGram( IDMSL102 ) WRKAREA=0) PROGram : IDMSL102 All programs (including PLT programs, user exits, and user- Group : THRDSAFE replaceable modules) should not create or access shared DEscription : Language : CObol | Assembler | Le370 | C | Pli storage (that is, the EXEC CICS GETMAIN SHARED RELoad : No No | Yes command). RESident : No No | Yes Try to avoid the use of global work areas (GWAs) in user USAge : Normal Normal | Transient exits, that is, as created by the GALENGTH option of the USElpacopy : No No | Yes Status : Enabled Enabled | Disabled EXEC CICS ENABLE PROGRAM RSl : 00 0-24 | Public All programs, user exits, and URMs should use only CEdf : Yes Yes | No threadsafe EXEC CICS commands. DAtalocation : Any Below | Any EXECKey : User User | Cics Review the use of function shipping within the application. COncurrency : Threadsafe Quasirent | Threadsafe Function shipped commands will cause threadsafe EXEC Api : Cicsapi Cicsapi | Openapi CICS commands to become non threadsafe REMOTE ATTRIBUTES DYnamic : No No | Yes Thread-safe was implemented on 3-15-2010. The backups in CICS were no longer observed and the peak time CICS transaction queues which caused CICS to hit the max task of 150 were down to 4-5 concurrent task. CICS average response time for all transactions which was ranging from .3 to .55 seconds came down to .2 seconds. The number of deadlocks in IDMS was cut in half and we saw the number of daily task in IDMS go over a million per day demonstrating the latent demand we had in the system. In TMON we were able to see all the application transactions executing on R8 TCB’s which are the TCB’s CICS uses for thread-safe programs. Conclusion; Thread-safe was an overwhelming success. We did see slightly higher CPU usage in CICS (1-2 percent) but this was expected and was a perfectly acceptable trade off for More information on CICS Thread-safe programs can be the excellent throughput we saw using thread-safe programs. found here; http://www.redbooks.ibm.com/abstracts/sg246351.html

13 IDMS Release 17 Migration Challenges Chris Hoelscher; Senior DB2 and IDMS System & Database Administrator The first step to a successful implementation is to acquire the system software from CA Technologies. To do this, sign-on to https://support.ca.com, and select Download Center, and select Products. Select IDMS/DB – MVS from the dropdown menu, Select 17.0 as Release, Select SP1 as Gen Level (or the most current Service Pack if desired). You will auto-magically be routed to Product Downloads. Locate the CA IDMS/DB PRODUCT PACKAGE row, and Select FTP Path (to the right). The FTP information will appear below the CA IDMS/DB PRODUCT PACKAGE row. Figures 1a and 1b below highlight the parts of the Electronic Software Delivery Now for a step-by-step online example. First, request a (ESD) that are of interest to this discussion. new sub-directory (see Figure 4), then name the new subdirectory IDMS17 and define it as a directory, and set permissions (777) as in Figure 5.

Copy the FTP location for future reference. It should look something like /orders/site id/order#/comp/ H00904DOA00.pax.Z . Then, Locate IDMS/DB Now, go up a level and verify the subdirectory has PRODUCT AUTHORIZATION entry and select the been created (see Figure 6). Having created a place to HTTP option. When FILE DOWNLOAD pop-up opens, temporarily store the software, let’s get the software to select OPEN. When the Document opens, copy the put there. Execute FTP from the CA website to your PASSWORD for future reference. Close the Document UNIX subdirectory as shown in Figure 7. Window, and Repeat the process for IDMS SYSTEM TAPE COVER LETTER (copy, save, or print the output). Return to Download Center, select Products, From the Dropdown list, select each product (one at a time) that you plan to install. Remember, products that do not require a password may not appear on this list (check install manual A.2.1 for the entire list). For each product, as before, select HTTP , When FILE DOWNLOAD pop-up opens, select OPEN; When Document opens, copy the PASSWORD for future reference; finally, Close Document Window. After acquiring the software locations and the passwords, the next step is to acquire the software itself. This is the major departure for IDMS R17 from previous releases. The first step is to determine your root UNIX (yes, UNIX) directory. It might look like /u/userid/ autousers/myuserid. To this root directory, you must add subdirectories and permissions – this can be done either in a batch job or online – first is a batch job and the results: (continued on page 15)

14 IDMS Release 17 Migration Challenges... cont’d from page 14 be manually entered; new parameters (FROM#REL, HAD#ADS, AUTOFAST), Dictionary/Database names After running the job, verify that the software was definable, SMS values definable, and the ability to skip successfully loaded shown in Figure 8, followed by the build of EMPDEMO/SQLDEMO. “unpack the pax file” (see Figure 9). After Running CAISAG, run the jobs that CAISAG created: . JOB00 – not executed – but handy reminders . JOB01 – Allocate libraries - SMS values now definable . JOB02 – populate indirect libs – now from disk . JOB03 – populate ppoption . JOB04 – RECEIVE – now from disk . SMP/E Release V3R4 required . JOB05 – APPLY – requires CICS library . JOB06 – ACCEPT – requires CICS library . JOB07 – link macros to source modules in CSI . JOB08 – backup SMP/E – I always skip (but I am not recommending that you should) . JOB09 – create startup module and/or UCFCICS . JOB10 – execute CAIRIM – skip for now (but must run before you try to bring up a CV) . JOB11 – creates JCL “includes” . Again, verify that the operation was successful as shown JOB12 – upgrade SYSTEM/SYSDIRL – skip for now (Run when ready to update CVs) in Figure 10. . JOB13 – upgrade APPLDICT – skip for now (Run when ready to update CVs) . JOB14 – Builds EMPDEMO – skip for now . JOB15 – Builds SQLDEMO – skip for now . JOB16 – Builds system 90 – skip for now (Run when ready to update CVs) . JOB17 – backup/delete unneeded files . JOB18 – populates SAMPJCL

We can now Modify and Submit TOOLS CAISAG: Supply valid jobcard, Update password member, Update VARBLIST member (changes: New DICMIG parms, New QUEUE retention parms, New SEGMENT/ DBNAME parms).

Finally, edit the UNZIPJCL member just unpacked, (continued on page 16) and make the necessary changes: Supply a JOBCARD, CHANGE “yourHLQ” to your high level qualifier, change SMPDIR DD PATH= to the full …/GJH01B path, Uncomment SMPJHOME and SMPCPATH if needed. Submit and watch the fun. After execution of this job, you should have the “traditional” MVS datasets needed to Install IDMS release 17. don’t forget At this point, review Cover Letters and PMLs and PIBs for any additional information, and check LMP Keys to forward for any new products you might be bringing onboard at release 17. Connections We are now ready to run the more familiar IDMS install to others in your jobs, but there are changes even here. First, we modify and run CAISAG from the SAMPJCL pds. As before, organisation supply a //JOB card, update the PASSWORD member with the passwords you saved, and update the VARBLIST member. Of course there are changes: New startup parm= parms, GJCVKEY has no default; must be manually entered, new parameters (GJCVKEY has no default; must

15 IDMS Release 17 Migration Challenges... cont’d from page 15 > JOB16 – Builds system 90 (from system 99) > SGENCOPY – copies system 90 to runtime system After running CAISAG, run the jobs that CAISAG > SGENMOD – misc changes created: . Add storage pools for each storage type (HPSPO) . JOB00 – not executed – but handy reminders . STORAGE KEY 9 . JOB01 – Allocate libraries - SMS values now definable . STACKSIZE 10000 . JOB02 – populate indirect libs – now from disk > Format Journals and LOGs . JOB03 – populate ppoption > Alter/Link DMCL for journal definitions . JOB04 – Links GSISVCX to the SVC exit > Restore any customized msg mods ssc etc. . JOB05 – RECEIVE – now from disk . JOB06 – APPLY – now from disk . JOB07 – ACCEPT Next, Modify the startup JCL. RHDCPARM is no longer . JOB08 - link macros to source modules in CSI linked into the startup module, WTOEXIT is no longer . JOB09 – empty for upgrade installs linked into the startup module; specified on PARM=; . JOB10 – empty for upgrade installs global DMCL and free storage amount specified on . JOB11 – update TOOLDICT – skip for now PARM=. SYS1.CSSLIB may be required for z/IIP . JOB12 – update RHDCUXIT – skip if copied from exploitation. Authorize runtime system software library previous release (again, only for z/IIP exploitation). Remember that . JOB13 - Change SVCXLEN value for TASK or LOG IDMS release 17 requires a 64-bit OS and requires Analyzer LE runtime support. Next, let’s apply the published fixes. Beware that When starting the CV, here are new messages to be aware many – post-Service Pack 1 fixes are delivered a load of (some of these may have been introduced in Release module replacements – a MAJOR change from previous 16; but I skipped that release): releases (and even from the initial (SP0) Release 17.0 environment). This has ramifications I will discuss later. . DC200023 V75 T1 CV Change Tracking is not used Then apply in-house USERMODS 9such as additional . DC024000 V75 T0 HEALTH CHECKER: Infrastructure SVCs, SRTT modules, PMOPT modules, SYSIDMS initialized modules, INTC/CINT modules, etc). I try to do as much . DC024000 V75 T0 HEALTH CHECKER: Added check of this under SMP/E as possible. Next, apply “optional” routine IDMS_SCRATCH_IN_MEMORY@CV75 fixes – this includes RHDCOPTN and ‘zap’ fixes (such as . DC024000 V75 T0 HEALTH CHECKER: Added check GS27525). The ramifications I mentioned earlier come routine IDMS_CPU_EFFECTIVENESS@CV75 into play here: each ‘zap’ APAR *must* list as a prereq . DC024000 V75 T0 HEALTH CHECKER: Added check routine IDMS_CHANGE_TRACKING@CV75 EVERY load module-replacement PTF that replaced the . load module zapped by this optional fix. Additionally, DC024000 V75 T0 HEALTH CHECKER: Added check routine IDMS_ZIIP_USAGE@CV75 when applying subsequent load module replacement PTFs, . DC024000 V75 T0 HEALTH CHECKER: All check you must first remove the optional ‘zap” USERMOD routines registered and all un-ACCEPTED PTFS against the same load . DC074100 V75 T0 V75 ENTER NEXT TASK CODE: module, re-APPLY the (just-removed) published fixes, CA IDMS release 17.0 tape GJH00B apply the new PTF, and then re-apply the optional “zap” . DC329013 V75 T21 Startup resynchronization complete PTF (remembering to list the new PTF as a prereq. Lastly, apply any test fixes you acquired as equivalents from a previous release. (continued on page 17) CAIRIM can now be setup and run. First, copy (or have someone copy) the following modules from the R17 APFLIB to the CAIRIM lib: GJH0INIT, IDMSMSVA, RHDCSSFM, and IGCxxx). Run CAIRIM with the following: Contributed PRODUCT(CA IDMS) VERSION(GJH0) INIT(GJH0INIT) PARM(REFRESH(SVC=xxx)) PRODUCT(CA IDMS) VERSION(GJH0) INIT(GJH0INIT) PARM(REFRESH(IDMSMSVA)) PRODUCT(CA IDMS) VERSION(GJH0) INIT(GJH0INIT) PARM(REFRESH(RHDCSSFM)) Software To convert the CVs and the dictionaries, do the following: Library Copy target loadlibs to runtime loadlibs > Member CONVERT – convert catalog Save time > Save customized msg mods ssc etc and use the > IDMSDIRL – load network schema changes to SYSDIRL > JOB12 – upgrade SYSTEM/SYSDIRL experience of > JOB13 – upgrade APPLDICT > TOOLS JOB11 – upgrade TOOLDICT others to resolve > JOB14 – Builds EMPDEMO problems. > JOB15 – Builds SQLDEMO

16 IDMS Release 17 Migration Challenges... cont’d from page 16 ­­IDMS Release 18 Status Opportunities we encountered (again, we might have hit some of these had we gone to 16, but we didn’t, so we Just as you are coming to grips with Release 17.0, for didn’t): those of you who have yet to move off of 15.0 or 16.0 – here is a status update from Art Cartier about Release > Old customized code (UCFCICS) 18.0! It might be worth referring to the note in the article > CICS interface changes on CARE 2010 – about some users complaining that the . AUTOCMT, AUTONLY , TXNSHR releases are coming too fast? > 2-phase commit changes From: Cartier, Arthur J > SVC structure changes Sent: Thursday, August 19, 2010 12:13 PM > OBTAIN record name within sort name USING … To: Beedy, Gregory A; Pereira, Carla E . See RO12491, but I wouldn’t Subject: RE: Decision time ! Thanks to all who replied ! > BOOKMANAGER doc to M/F Deadline for September's issue is August 20th ! > JOURNAL changes vs. DBAN > Dashes removed on screens . Old: CA-ADS Online Dialog Compiler CA IDMS 18.0 Update and Call for Beta . New: CA IDMS Online Map Compiler Customers! > NODES change . Old – only needed node based on CV# (even if diff) A new release of the CA IDMS product family, CA IDMS . New – need node based on CV# and SYS# (if diff) 18.0 is in the final stages of development and Alpha > 2 Pool 255s – headache for external monitors testing and we are looking for additional customers to > New msgs: AREA CLOSEDOWN ????? participate in the beta test program which is currently > “zap” fixes (GS27525) vs. published fixes (RO14755 for planned for early January 2011. example) > Participants in the CA IDMS 18.0 beta testing will be able to try new features such as MSM support, auto In summary, I would recommend to reads the manuals tuning, zIIP enhancements, expanded tracing and (always the final word). Things to remember: statistics, SQL enhancements, updated installation guide . Many changes to software acquisition and much more… More details about the CA IDMS 18.0 release content and beta sign-up requirements can be . Many changes to software installation found at ca.com/betas . . Throw away SP0 install; Install w/SP1 or later Arthur Cartier . Apply all PTFs CA Technologies VP, Software Engineering . Test, Test, Test Tel: +1-860-627-4555 Fax: +1-860-654-1528 . Apply all PTFs (It’s important enough to say it Mobile: +1-860-539-4401 twice) [email protected] . But overall, R17 is GREAT!!!

IDMS Release 16 – New End of Service Date It seems a number of Users are still on Releases15.0 or 16.0 – here is a status update from Art Cartier about Release 16.0! This revised date was as a direct result of User feedback at CA World!

www.iuassn.org CA IDMS™ r16 – New End of Service Date! Based on customer feedback, January 31, 2012, is an your portal to iua update to the previously announced End of Service date for CA IDMS r16. CA is discontinuing support for CA services and idms IDMS r16 after January 31, 2012. This includes CA contacts IDMS r16.0, r16.2 and all related service packs. More information can be found on the product page when you logon to support.ca.com.

17 CA No Longer Distributing difference is that these macros will generate almost no executable code. Instead each macro will generate an Some Source - Clarification option table that will be linked with a small stub module. From IDMS-L July-August 2010 The resultant stub load module will contain only enough executable code to pass the options to a common load From: IDMS Public Discussion Forum On Behalf Of module where essentially all of the executable code will Siraco, John A reside. No source will be distributed for the common Sent: Thursday, July 22, 2010 4:55 PM module. To: [email protected] Subject: Source members no longer being shipped This will change the installation procedure somewhat with the next IDMS release - currently referred to as for release 18, but it will deliver a major benefit for release 18 subsequent updates. Because the common load module is separated from the stub load module, you will almost We are sending this email to let everyone know that in our never need to regenerate the options table nor relink your current plans for CA IDMS r18 there are several source stub load module when you apply maintenance. When members that we longer plan on shipping. We would like you apply maintenance via SMP/E or MSM, only the to hear from you if you believe this is going to cause you common module will ever be updated. The stub load any problems. Please understand that these are our plans module containing your options table and stub module currently and are subject to change. will not need to change unless you choose to implement a List of members: newly introduced feature that uses a new macro parameter. . IDMSINTL Note also that any exits that were supported in earlier releases will continue to be supported in release 18. Such . #UCFBTCH, #UCFTSO exits will be linked with your stub load module. We are . #UCFCICS, #UCFCICZ considering the possibility of introducing new exits for . #UDASCIC, #UDASBCH a few of the interfaces used with the macros below. This would be done to accommodate those sites that have With respect to IDMSINTL: We have enhanced actually modified the executable code in one of these IDMSINTL to provide a new "OPTIXIT" for dynamic macros to provide additional functionality beyond that routing of requests. provided by the CA-supplied macros. From: IDMS Public Discussion Forum on behalf of A few of you have already responded that you do modify Mickelsen, Michael G [[email protected]] executable code in these macros. We will be contacting Sent: Wednesday, 4 August 2010 3:37 AM you directly to try to determine how best to meet your To: [email protected] business needs. Subject: Update to: Source members no longer being shipped with the next IDMS release - currently If you do not hear from us in the next week and are still referred to as release 18 concerned that your site may be adversely affected, please contact John or myself directly at [email protected] or I just wanted to update this message to address some of [email protected] the questions and concerns raised by the original message above. [Editor’s note: please refer to e-mail dates of July 22nd and All of the macros listed below will be delivered in Release August 4th – Gary] 18. The macros will be invoked using the same parameters as earlier releases with minor exceptions. The main Explaining “Deadlocks” to the Layman How do you explain a ‘deadlock’ to a layman? The boss said to his secretary: ‘For a week we will go abroad for a meeting, so make arrangements.’ The secretary makes call to her husband: ‘For a week my boss and I will be going abroad, you look after yourself.’ The husband makes call to secret lover: ‘My wife is going abroad for a week, so let’s spend the week together.’ The secret lover makes call to the small boy to whom she is giving private tuition: ‘I have work for a week, so you need not come for class.’ The small boy makes call to his grandfather: ‘Grandpa, for a week I don’t have class ‘coz my teacher is busy. Let’s spend the week together.’ The grandpa (Who in fact is ‘The Boss’) makes call to his secretary: ‘This week I am spending my time with my grandson. We cannot attend that meeting.’ The secretary makes call to her husband: ‘This week my boss has some work, so we cancelled our trip.’ The husband makes call to secret lover: ‘We cannot spend this week together; my wife has cancelled her trip.’ The secret lover makes call to small boy whom she is giving private tuition: ‘This week we will have class as usual.’ The small boy makes call to his grandfather: ‘Grandpa, my teacher said this week I have to attend class. Sorry I can’t give you company.’ The grandpa makes call to his secretary: ‘Don’t worry; this week we will attend that meeting, so make arrangements.’... Source: Unattributed from the Internet

18 Space Management Locks Agenda of the BIUA event of th From IDMS-L Thursday October 28 From: IDMS Public Discussion Forum [IDMS-L@ 9.30 to 10.30 - CA IDMS Status and Plans LISTSERV.IUASSN.COM] CA IDMS is constantly evolving to meet new business Sent: Wednesday, 14 July 2010 12:51 AM challenges. Come to this session to learn about CA’s To: [email protected] ongoing commitment to CA IDMS and plans for CA Subject: SPACE MAMANGEMENT LOCKS IDMS going forward. This session provides an update I thought I'd comment on a few things based on previous on CA Technologies’ Mainframe 2.0 initiative including activity concerning SMP pages and their locking. those features supported by CA IDMS. Finally, hear how CA IDMS customers have successfully tied their First there are never any dbkey locks set on any portion of CA IDMS environments into today’s modern computing an SMP since there are no dbkeys associated with an SMP. architectures with Web applications and other technology. Also space is never allocated or freed on an SMP so the space lock is also never set. This is fine since no updates 11.00 to 12.00 - CA IDMS Modernization to the SMP are ever journaled or recovered as their data Approaches and Case Studies is never meant to always be 100% accurate relative to the Today’s IT architectures include phones that are actual space on a page. computers and computers in the clouds. Even as systems expand beyond traditional boundaries, at the heart What is maintained is a very short duration buffer lock. of many thriving environments you’ll find CA IDMS This lock is not maintained through the lock manager running on IBM System z. This session explores several but uses a simple ECB maintained within the buffer's approaches to CA IDMS modernization by looking BME. When a run-unit gets control of a buffer with the at case studies from government organizations and intent to update the page it places an exclusive lock on its enterprises around the world that depend on CA IDMS buffer when the buffer is accessed. A run-unit can only reliability for their success. hold concurrent locks on 3 buffers so they are typically cycled rather quickly. Their purpose is to make sure no 13.00 to 14.00 - CA IDMS r18 delivery is coming in two run-units are actively altering a page at the same time. 2011 In a CV environment these locks are always released at the This session provides a preview of the planned conclusion of a DML's execution. Since it is possible for enhancements for r18 and includes an overview of the contention for one of these locks between run-units it is new features and describes the integration with CA possible that time-outs or other deadlocks could occur but Mainframe Software Manager (MSM), CA’s innovative they would not be reported as dbkey deadlocks. solution for modernizing the installation, deployment Certainly the space available in an area will have an impact and configuration of mainframe software in a z/OS on the frequency of contention on these locks but unless environment. Find out how r18 will simplify the there is an application where records are being heavily management of your CA IDMS environment. stored concurrently on a small range of pages I would not 14.30 to 15.30 - Enabling your IDMS environment to expect to see that many time-outs or deadlocks related be part of a Web Services architecture to these buffer locks. I would suspect that page space In this session we will present an conceptual and technical lock contention on the actual data pages would be more overview of the fos/Web Services for IDMS product and prevalent. how this set of products, that are fully integrated within Page space locks have also been changed from their IDMS, can be used to enable your IDMS environment original implementation. We no longer use line index 255 to be part of a Web Services architecture. The fos/Web as the 'dbkey' used to lock space. With the creation of the Services Requester product enables your DC-COBOL lock manager in Release 12.0 a separate 'space' lock is now programs to call external Web Services, which can be maintained. If you see a dbkey lock conflict for line index either user or standard applications like SAP. If you have 255 of a page you are now actually seeing a conflict for a the IDMS SQL option, this capability can be extended to record which has been assigned to line index 255. batch and CICS programs as well. The fos/Web Services Provider product enables an external application to access IDMS data and applications via a Web Service. This is Dick Weiland a generic server which can call multiple services (user- CA Technologies written programs). This session will include an end-user Sr Sustaining Engineer video presentation, that will give you more information Tel: +1-630-505-6561 on the usage of the products like implementation, stability and performance. Fax: +1-630-210-9274 [email protected] 15.30 to 16.30 - Bi-directional integration and data synchronization of IDMS with Open System environments Bi-directional and transparent integration of IDMS in any Open System environment. This includes SQL based (continued on page 21)

19 Is IDMS r17 z/IIP exploitation right for your environments? Chris Hoelscher; Senior DB2 and IDMS DBA, Humana Inc.

(Note – the following represents my experiences and my “average” task would consume the same .02 seconds of experiences alone implementing , monitoring, and tuning CPU (an instruction is an instruction, be it processed on z/IIP exploitation across our IDMS enterprise. The a regular or z/IIP processor, right?), but, alas, there is opinions expressed herein do not necessarily reflect those overhead to ZIIP=Y mode processing. of any other IDMS site nor CA Technologies. Any part of this document may be reproduced, with or without the What, then, is this overhead that can so drastically affect express written consent of Major League Baseball). z/IIP exploitation results? It is the CPU instructions consumed to move an executing process from TCB mode z/IIP processor exploitation is a very powerful and to SRB mode and vice versa. The number of swaps popular feature of CA-IDMS Release 17; proper occurring can easily be seen in the DCMT D SUBT XXX exploitation can certainly create white space (diverting (where XXX is 001 in a non-multitasking site) beside the cpu cycles to z/IIP processor(s) allowing room for heading Count actual swaps. Some IDMS environments additional processing that otherwise would have nowhere (CVs), such as a CV at my site where nearly 90% of our else to immediately execute) and saving money (formerly tasks execute, is exclusively a back-end for CICS (and billable CPU cycles are diverted to z/IIP processors and other IDMS CV’s) front end transactions. In this type become non-billable). But how do we determine proper of environment, there is NO user code, and as such, exploitation? very low swapping between TCB and SRB modes (the only swapping would occur when swapping between When I moved our IDMS production environments included and excluded system code). In this environment to Release 17 in April 2009, and implemented z/IIP we averaged from 0.5 to 1.7 “swaps” per task. In other exploitation immediately upon the upgrade, we saw environments at our site, we have tasks that execute user an immediate overall 20% reduction in billable CPU and system code, but are very simple in design, and do cycles, and I was informed by our performance/billing not require many swaps. In these environments, I have monitoring group that due to the cpu reduction, we could recorded an average of 50 to 125 swaps per task. Lastly, (under the provisions of our licensing agreement) reduce we have a few online environments where the tasks our payments for IDMS by an annualized amount in 6 are ADS/O and DC-COBOL, and have very complex figures. Admittedly, I felt rather pleased with myself and user code intermixed with DB and DC calls. In these accepted the results without further examination. In other environments, I have recorded averages of over 2500 words, I rested upon my laurels with regard to z/IIP. In swaps per task! fact, I was so pleased with our results that I made a point of sharing my results with the IDMS user community. How can I determine if the overhead is defeating the Also, having other work activities to complete, I did not, benefits of z/IIP exploitation, as so clearly seemed at that point, investigate z/IIP exploitation further. the case to the sites with whom I was corresponding? Every observation will have its own sets of caveats, but Then a funny thing happened: In early 2010 DBAs this is the method I chose to investigate: in ZIIP=N at other sites emailed me privately with some concern. mode, we determined the average CPU per task (in my What was I doing that they were not? Their results were fictional example, 0.02 seconds) . In ZIIP=Y mode, any substantially different than mine. Admittedly, I was additional CPU per task is attributable to z/IIP overhead baffled, but could not let a good challenge go unanswered. (let’s say, 0.025 total CPU task, for an overhead of I began to investigate each of our online environments in 0.005 cpu seconds per task (and this overhead currently depth, and the results were very surprising (at least to me). executes in TCB mode). The next step is to determine the To explain these surprising results, let’s take a very broad average z/IIP-processed CPU per task (from summing -look at what happens during the life of an average task, the ZIIP counts (in cpu seconds) from DCMT D SUBT both in a non-z/IIP environment (ZIIP=N specified XXX (zIIP time) for each subtask. In our example, let’s on the EXEC JCL card PARM attribute), and a real or say that the average z/IIP per task is .008 cpu seconds – simulated z/IIP environment (ZIIP=Y). In non-z/IIP then we have shown that each task has a net reduction mode, the task executes whatever it needs to do, both in billable CPU of .002 seconds (.008 z/IIP transfer “user (non-DB or DC calls)” and “system (database and - .005 z/IIP overhead). In this case we are doing a good communication calls and system housekeeping)” code, thing. But what if the results showed that we are now consumes CPU cycles, and finishes (for this example, executing in ZIIP=Y mode 0.03 total CPU seconds consuming instructions equivalent to 0.02 cpu seconds). per task (with a resulting overhead of 0.01 cpu seconds/ The machine instructions, without regard to content, task, or 150% of the original CPU, but still routing that are executed in “TCB” mode, anchored off one or more same .008 cpu seconds/task to z/IIP? In this case we are TCB control blocks. In ZIIP=Y mode, the same task costing ourselves .002 billable cpu seconds/task (.008 z/ would continue to execute all “user” code and specifically- IIP transfer - .010 z/IIP overhead). In these cases, z/ excluded “system” code in TCB mode, but would execute IIP exploitation is certainly not beneficial. This appears all non-excluded “system” code in “SRB” mode, and a to be the scenario that other sites are experiencing, and portion of that “SRB” mode instructions (in our testing we reached a high water mark of 33%) would be routed to a z/IIP processor for (billing-free) execution. Were there no overhead to ZIIP=Y mode processing, this (continued on page 21)

20 R17 Z/IIP Exploitation... cont’d from page 20 Introduction to Relational (previously unbeknownst to me, at my site as well). I am Databases and SQL for IDMS in the process of extensively testing CVs with high swap Programmers rates AND DEFERRING z/IIP EXPLOITATION until release 18. What is a relational database? A Relational Database Management System (RDBMS) What did he say, you might be asking yourself, RELEASE is a way to organize and access data. You are probably 18? Release 17 has only been GA for 18 months. What already familiar with non-relational database management is up with Release 18 (announced as GA possibly in systems such as IDMS and VSAM. There are many May 2011)? *** the following is based only upon brands of relational database. Some examples are IDMS/ current plans of CA as announced at CA-WORLD 2010 SQL, DB2, Oracle, and Microsoft SQL Server. What they - nothing is guaranteed nor should be construed as a all have in common is: promise for Release 18. Having said that, the announced plans are to improve z/IIP efficiency in the newest a) The same process is employed to design the database. release, and I can only assume/hope that the improved efficiency will be in the area of swap management. CA b) The same set of terms is used to define the database. acknowledged that z/IIP exploitation, like multitasking c) The same language is used to access the data. This and shared cache exploitation before it, was introduced at language is called Structured Query Language, or SQL. one release with favorable results, and will be continually refined in subsequent results for closer to optimal results. Relational database design Are there activities you can perform to make your CVs If you are familiar with IDMS database design, you more z/IIP friendly in Release 17 RIGHT NOW ??? should have no trouble understanding relational database Surprisingly, the answer is YES. If you can identify design. The design process is very similar. You still periods of time (evening and or weekend batch cycles have to go through the same steps of normalizing data, ) where swapping is low, consider multiple CV startup etc. The visual representation of a relational database is configurations (requiring CV bouncing) to match called an entity-relationship diagram (ERD). It looks ZIIP= value to the type of processing occurring within very much like a Bachman diagram. If you can read a each time interval. I have identified 2 candidate CVS Bachman diagram, you can read an ERD. with high swapping on the weekend and low swapping What does “relational” mean? during the week which I will attempt such a startup (dare Tables “relate” to one another through the use of shared I say) swap. Additionally, while beyond the scope of key fields. what I have the time (and authority) to investigate, and not much hope of success, there is the possibility that In Figure 1, both the EMPLOYEE and the application re-engineering might have success in reducing DEPARTMENT tables contain a column called application TCB/SRB swapping. One last idea, if it is DEPTNAME. This column is the “primary key” for possible to remove any numbered user exits that your DEPARTMENT, and the “foreign key” for EMPLOYEE. task hit, you can remove a large hindrance to successful z/ To get both employee and department information for IIP exploitation. At our site, our least z/IIP-friendly CVs Jane Doe, you would first locate Jane Doe’s information execute exit 23 for every ads or cobol run unit – and this in the EMPLOYEE table, then use the value in her appears to be a very big contributor to swapping. DEPTNAME column to locate the matching information in the DEPARTMENT table. In the end, I will admit that initially I treated z/IIP exploitation with a SET IT AND FORGET IT. Obviously, a global policy toward z/IIP exploitation may be acceptable as a very first intention, but simply cannot lead to optimum results.

Agenda of BIUA event.. cont’d from page 19

access to IDMS from JAVA, .NET, WINDOWS, UNIX/ LINUX and the creation of Views between IDMS and other data-sources. Mainframe programs can also access RDBMS on Open System platforms and can directly communicate with processes and applications in these environments. Bi-directional change data capture in real-time for IDMS and Open System RDBMS with minimum impact on the mainframe. Repository based replication linkages support many to many relationships for source and target databases.. (continued on page 22)

21 Introduction to SQL... cont’d from page 21 What is different about SQL? Most DML’s such as IDMS and VSAM commands act This process is called “joining” two tables. You will see an upon one record per command. SQL can act upon example of this in the SQL section later on. many records in a single command. A single SELECT command may return hundreds or thousands of rows. Relational database terms Likewise, a single DELETE command can delete your The following table lists some relational database terms, entire database! So you need to be very careful in coding with the corresponding IDMS and VSAM terms: your selection criteria (the “WHERE clause” of the SQL statement). Sample SQL These examples use the relational database depicted in Figure 1. The following example reads the EMPLOYEE table (file). It locates all of the rows (records) that contain ‘DOE’ in the LASTNAME column (field). The contents of the LASTNAME, FIRSTNAME, and SSN columns are returned to the program that issued the command.

SELECT LASTNAME, FIRSTNAME, SSN FROM EMPLOYEE WHERE LASTNAME = ‘DOE’ ------The following example illustrates a “join”. It reads the EMPLOYEE table, locating all of the rows that contain The foreign key is not a DBkey, like the pointers we are ‘DOE’ in the LASTNAME column. It then reads the used to. It's a column (element) that is duplicated in both DEPARTMENT table, locating all of the rows that the referenced table (owner record) and the referencing contain the DEPTNAME values that match those from table (member record). It serves the function of a pointer, the ‘DOE’ employees. Values returned to the program in that it connects two tables (record types). are LASTNAME, FIRSTNAME, and SSN (from the EMPLOYEE table), and MISSION and BUDGET (from What is SQL? the DEPARTMENT table). SQL stands for “Structured Query Language”. It is the data manipulation language (DML) used to access SELECT LASTNAME, FIRSTNAME, SSN, MISSION, BUDGET relational databases. SQL commands are embedded FROM EMPLOYEE, DEPARTMENT WHERE LASTNAME = ‘DOE’ in user-written programs just as IDMS and VSAM AND EMPLOYEE.DEPTNAME = DEPARTMENT.DEPTNAME commands are. ------SQL commands The following example adds a new EMPLOYEE row. The following table lists the major SQL commands, with INSERT INTO EMPLOYEE the corresponding IDMS and VSAM commands: (LASTNAME, FIRSTNAME, SSN, SALARY, DEPTNAME) VALUES (‘DOE’, ‘JANE’, ‘999999999’, 743.28, ‘DIT’) ------The following example modifies the EMPLOYEE table. It locates all of the rows that contain ‘DDP’ in the DEPTNAME column, then changes DEPTNAME to ‘DIT’ for those rows only.

UPDATE EMPLOYEE SET DEPTNAME = ‘DIT’ WHERE DEPTNAME = ‘DDP’ ------

(continued on page 23)

22 Introduction to SQL... cont’d from page 22 An unlinked index requires less disk space in the data record's area since there is no index pointer per data The following example deletes all EMPLOYEE rows that record occurrence. have a salary over $1,200.00. The overhead of processing orphaned records in the DELETE FROM EMPLOYEE level-0 SR8's is eliminated. WHERE SALARY > 1200 However, the use of an unlinked index can cause more binary searches of the index structure since the data record Additional resources: does not have a pointer to its related SR8. This can result The “IDMS SQL Self-Training Guide” included on the in an increase in the CPU and I/O needed to process the IDMS documentation CD for Release 12 and up. index. Biographical note: It should be noted that any user-owned index must be a Kay Rozeboom is a DBA/Systems Programmer with linked index and system-owned indexes defined through the State of Iowa. She has 21 years of IDMS experience. SQL are always created as unlinked indexes. Her special interest is in integrating mainframe data and Q: I have a local batch program that issues an "OBTAIN applications with other platforms. NEXT record-name WITHIN index-name" command. IDMS will periodically return an error status of 0326. How can I get a record not found condition when I am not using a symbolic-key access? Frequently Asked Questions A: Any DML command that accesses an index structure About CA IDMS™ Indexing has the potential to return a minor code of 26. This can occur if the DBMS attempts to access an SR8 record Reprinted from “CA Tech Insider: CA IDMS” and fails to locate that record occurrence. If the run-unit involved was readied against the index area in an update Copyright © 2010 CA. acknowledged mode, the general diagnosis would be that the index Q: How many indexes can be defined in a single database structure has been corrupted and the index should be area? rebuilt using the FROM MEMBERS or ALLROWS option. A: There is no practical limit as to the number of indexes that can be defined in a database area. However, it is This certainly could be the case when encountered by a strongly recommended that each system-level index be retrieval program but few sites run with retrieval locks given its own page range whether that is a separate area or and there is no locking mechanism for local run-units. As a unique restricted page range within an area containing a result, you might be experiencing a false broken index multiple indexes. In addition, it is a bad practice to mix caused by the concurrent updating of the index by other system-level indexes in a page range with other types of run-units. When this error occurs, the recommendation data records. is to rerun the local batch job. If the error occurs consistently, you probably have a corrupt index and a These recommendations are made relative to the rebuild is in order. performance of the index. The most effective tuning option for an index is the displacement of the level-0 Copyright © 2010 CA. All rights reserved. SR8 records. Specification of this option tells IDMS how many pages to reserve for intermediate level SR8 records. If an index shares its page range with other indexes or database records, the space reserved for the intermediate records may be used by these other records/indexes and lead to excessive splitting and spawning of the index's SR8 records. This problem ultimately leads to additional I/O Contributed activity to navigate the index structure. Q: What are some things that I should take into Software consideration when deciding to define an index as linked or unlinked? ibrary A: Defining an index as being unlinked does provide a L number of benefits over using a linked index. Save time Unlinked indexes can be added and removed without and use the restructuring the database, provided the control length of the record is not changed. experience of Building or rebuilding an unlinked index is faster because others to resolve there are no index pointers in the database record that must be maintained. problems.

23 International Chair Board Member Company: Managing Member Craig McGregor Run Right, LLC Axciom Email: [email protected] [email protected]

Board Member Diane Montstream Allen Systems Group [email protected] Secretary/Treasurer Email Coordinator Bob Wiklund Board Member Company: Tiburon Technologies Jan Rabaut Address: 17101 W. Gable End Lane, [email protected] Surprise, AZ 85387 Phone: 623 594-6022 Editor Email: [email protected] Gary Cherlet Justice Technology Services South Australian Department of Justice [email protected] International Vice Chair Contributed Software Librarian Laura Rochon Desktop Publishing Company: Ajilon Professional Services Rebecca Shaw 404 377-6982 Address: 22 Jolliet, St-Bruno, [email protected] Quebec J3V 4Z1 Canada Phone: 514-943-8290 Fax: 450 441-6880 ­ Email: [email protected] IDMS Connections is a bi-annual publication of the CA-IDMS Database and Applications User Association European IUA Representative (IUA). It is designed to promote its Steve Rundle members’ objectives. IDMS Connections Company: British Telecom BT Group plc. is not responsible for the opinions Address: PP2B33 Angel Centre, expressed by its writers and editors. 403 St. John Street, London EC1V 4PL UK Phone: +44 (0)20 7777 6920 Information User Association Fax: +44 (0)20 7777 6921 401 N. Michigan Ave. Email: [email protected] Chicago, IL 60611-4267 Phone: 312/321-6827 Fax: 312/245-1081 Internet: [email protected] Board Member Web: http://iuassn.org Terry Schwartz Company: Perot Systems Address: PO Box 269005 Phone: 972 577-3722 Email: [email protected]

24