Gen 8.6 has been updated to support the use of the universal DB2 attachment stub (DSNULI) when linking CICS and batch applications. This allows sharing of some modules that may have required separate copies due to environment specific DB2 stubs.
The use of DSNULI has been implemented as optional behavior. Installing the PTFs will provide the capability, but DSNULI support must be selected and configured through Target definition within the HE or IT. The default selection is NO, which preserves existing functionality.
Implementation requires the following PTFs: RO98369 RO98370 RO98371
We have begun an internal process to resolve the status of the many "Under Review" ideas within the community. Many of these have languished for an excessive time, and it is my goal to provide answers regarding their eventual state.
Over the next 30 days or so several months (the decision process is taking a bit longer than I had anticipated), we will be changing the status of all items currently marked "Under Review" to a more definite status. The decisions will be based on merit, feasibility, votes, and resources - from a resource standpoint based on the likelihood of the idea being implemented within the current (Gen 8.6 continuous delivery) or next release of Gen.
Some Under Review" ideas will be placed in the "Currently Planned" category, and others will be wish-listed or "Not-Planned". But all will be finally given at least planned resolution. Wish-listed ideas will be reviewed again during subsequent release planning.
Where the idea has a negative outcome, I will try to explain our reasoning in a comment attached to the original idea.
There will be additional work to clean up the wish list and other categories as the year progresses.
We have certified SQL Server 2016 for use with CA Gen 8.5. There is no specific PTF required to enable this support. Note, however, that certification testing is done using the then current maintenance level of the Gen release in question.
SQL Server 2016 was previously certified for CA Gen 8.6.
The Technical Requirements and associated documents have been updated to reflect this certification.
We have certified WildFly10.1 for use with CA Gen 8.6. Technical requirements for Gen 8.6 have been updated. PTFs will be necessary to enable this support. Summary information is listed below for your convenience.
Certification efforts were initially directed towards WildFly (as opposed to EAP) due to availability at the time this was undertaken. We are currently discussing our future certification and support policy in this regard. Updated certification will follow.
All WildFly10.1 PTFs ( RTN86110, RTJ86104, RTA86104, GSN86103, BTN86111 ) are published.
* Directory CA Gen 8.6 Solutions & Patches * Sub-directory Windows * Category Runtime, GUI * Name RTN86110 / SS03640 * Platform WINDOWS * Size 4,486,199 bytes * Date 02/20/2018 * Description WildFly10.1 SUPPORT FOR CA Gen8.6. * Prerequisites IRN86100 RTN86109 * Co-requisites BTN86111 GSN86103 RTA86104 RTJ86104 * Supersedes None
* Directory CA Gen 8.6 Solutions & Patches * Sub-directory Windows * Category Runtime, Java * Name RTJ86104 / SS03646 * Platform WINDOWS * Size 386,879 bytes * Date 02/13/2018 * Description WildFly10.1 SUPPORT FOR CA Gen8.6. * Prerequisites IRN86100,RTJ86101 * Co-requisites RTN86110 RTA86104 BTN86111 GSN86103 * Supersedes None
* Directory CA Gen 8.6 Solutions & Patches * Sub-directory Windows * Category Runtime, .NET * Name RTA86104 / SS03637 * Platform WINDOWS * Size 342,124 bytes * Date 03/07/2018 * Description WildFly10.1 SUPPORT FOR CA Gen8.6. * Prerequisites IRN86100 RTA86103 * Co-requisites BTN86111 GSN86103 RTN86110 RTJ86104 * Supersedes None
* Directory CA Gen 8.6 Solutions & Patches * Sub-directory Windows * Category Gen Studio * Name GSN86103 / SS03613 * Platform WINDOWS * Size 2,720,385 bytes * Date 02/17/2018 * Description WildFly10.1 SUPPORT FOR CA Gen8.6. * Prerequisites IRN86100 * Co-requisites BTN86111 RTA86104 RTJ86104 RTN86110 * Supersedes None
* Directory CA Gen 8.6 Solutions & Patches * Sub-directory Windows * Category Other PTFs * Name BTN86111 / SS03612 * Platform WINDOWS * Size 11,143,466 bytes * Date 04/03/2018 * Description WildFly10.1 SUPPORT FOR CA Gen8.6. PROFILE TABLE IS SORTABLE WHEN DESCRIPTIONS ARE NOT. * Prerequisites IRN86100 BTN86105 BTN86108 BTN86109 * Co-requisites GSN86103 RTA86104 RTJ86104 RTN86110 * Supersedes None
It was shortly before Easter in 1998 that my wife and I packed up all our stuff, put it in her Mothers garage to be picked up by the movers. We had been married for 4 years, three of which I spent in school... and now we were off for a grand adventure.
We loaded up our 1988 VW Fox (which had no air conditioning in it at the time) and headed down to Austin TX. I was going to work on a project using "Cool:Gen" and a "Tandem", which were two terms I had never heard before. It seemed exciting, new country (I am Canadian), new climate, new opportunities. We had never been before and we really didn't know anyone down there.
That one choice, to work on a project with tools and technology that I had never heard of, has led to a career which has taken me across the US and back to Canada and who knows where I will visit in the future! I have worked in various industries, on various bits of technology and have been granted the privilege of working with very some very wonderful people. Smart people whom I have been able to learn much from.
The Gen community truly is a small world. Some days I see notes in code made by people I worked with 15 years ago. I work with people I have never met in person, and when I do finally meet them (at an Edge event or otherwise) it's not like when you first meet a stranger....rather it is like running into an old friend. People I have worked with, keep in touch with me on Facebook, Linked in and by email. We meet up sometimes and talk about old times, current problems they or I are having with our current engagement.
That's my Gen story....
So what's your Gen story? I invite you to share it here in the comments.
I also invite you to add a new chapter to your Gen story, which you can do by attending the upcoming Edge technical exchange. It's an opportunity to enhance your skillset as well as meet your peers, listening to and sharing our own Gen Stories
I look forward to hearing your Gen story, hopefully in person at the Edge event!
First of all, I would like to apologize for my absence from the community for the last 2 months. My plans for activity were overtaken by events, and I have spent much of my time dealing with a family medical issue. Between that, and just the day to day demands of the job I haven't had much time to spare. For the moment, that issue has at least stabilized. I appreciate your forbearance, and hopefully I should now be able to spend some time attending to the community.
As many of you may be aware, the issuance of interim releases (IRs) in CA Gen has had its ups and downs. Generally, the idea has been unpopular and confusing for many customers. Due to the diversity of content and platforms in Gen, IRs would often contain updates for only a small subset of our supported environments. This in turn caused confusion of what "correct" IR level was required for any given portion in Gen - a problem since these IRs were required for maintenance continuity as prerequsites for additional service.
Over the past year, we have begun releasing content as it became available in individual PTFs, or in documentation and community announcements for certifications.I feel that this reduces the complexity for both the customer and our engineering group, as well as allowing ad hoc customer testing and involvement without requiring a commitment to a complete release. It allows content to be delivered more rapidly, and permits me to adjust our schedule when pressing customer requirements present themselves in a mid-development cycle.
We have therefore made the decision to release the remaining IR2 content in this fashion. This means that the content will still be available (some of it has already been released), but it will be released as individual PTFs targeted to individual platforms rather than a combined package. Each feature will be individually announced in the community, and I will provide a summary of the items released and their information once the final items of IR2 content have been released. The remaining IR2 content should become available over the next few weeks to months.
We plan to continue this methodology following the release of this content, and items that can be delivered discretely will continue to be issued in PTF form and not as IRs.
While there is still some internal planning to be done, the general thought is to deliver a complete release of CA Gen 8.6 next, with a fully installable package that may be installed from scratch for non-CA Gen 8.6 customers. We will also deliver a full roll-up PTF in parallel that will include all previously released Gen 8.6 content (including base IR1, IR2, fixes, and additional continuous delivery content) for the convenience of those customers who have already transitioned to CA Gen 8.6.
Please feel free to ask questions about, or comment on the merits of, this change. We hope it will provide for improved delivery and reduced routine maintenance costs, as well as facilitate more responsive development for our customers.
First, I would like to thank everyone who responded to our survey. The feedback provided is very valuable in determining where we need to go with CA Gen, and the areas that are of most concern to our customers.
I'm happy to say that CA Gen is still seen as a valuable, reliable, and productive environment for most of our customers. The product itself, and the idea behind it are still strong. There are, however, legitimate concerns.
Functionally, the biggest concerns seem to be the development tools and their visual presentation, database exploitation, and general product modernization.
Operationally, ease of upgrade (along with release planning), training and availability of developers, and general documentation seem to be the most common issues.
And beyond those specific items, the general concern about the future of CA Gen comes through loud and clear.
In the new year, we will seek out your thoughts and priorities about how best to effectively address these issues - both through this forum and direct contact. I will try to initiate some discussion around the choices that we face in development, and how those choices affect your business.
For now, I can tell you that projects to address some of these items are either already in work or being planned. These things won't happen overnight, but are steadily progressing. As we move to complete our next Interim Release (IR), we will form a revised road map that will hopefully offer some relief for many of these issues and a bit more clarity in product direction.
As to CA Gen's future, nothing I could say here would alleviate those concerns. I will work with product management to ensure that our messaging clearly reflects CA's continued commitment to CA Gen.
Thank you all so much for your continued support of CA Gen. We look forward to working with you all to create a better experience and an improved product.