Business, regulatory, and customer privacy continue to require tighter controls over access to your critical data stored in DB2.
DB2 10 plans to continue to expand its data-centric security solutions by allowing data administrators to establish security policies or security logic on tables with restricted data, thus, enforcing security controls on all applications and tools that access the restricted data. Businesses are able to comply with new regulations without changes to existing applications since security logic is separated from application logic. The evolution of security policies also becomes easier to deploy since the security logic can be automatically deployed against all SQL access to the data. These controls can prevent the use of SQL to bypass views, application security logic, or prevent the use of SQL Injection to attack a DB2………
Join IBM experts to learn about enabling your Oracle applications for DB2 9.7.
DB2 9.7 brought the biggest infusion of SQL features since DB2 V2.1. In this presentation, learn about features that lead to a ten-fold reduction in enablement costs when Oracle-based applications are enabled for DB2. The virtual tech briefing covers the following:
Business drivers to move Oracle applications to DB2
SQL enhancements in DB2 9.7
Tooling support to enable applications from Oracle to DB2
In his latest article for Database Journal, Julian Stuhler writes about the fascinating acquisitions surrounding IBM DB2 that have been announced in the last few weeks.
xkoto & Teradata – Firstly, Teradata Corporation acquired Xkoto on 12th May 2010. Xkoto was the creator of some very interesting clustering technology dubbed GRIDSCALE, which was designed to improve database availability and scalability with minimal impact to the application. If that sounds familiar to you as an IBM DB2 person, you’ve probably been reading about IBM’s pureScale feature for the DB2 for LUW product, which is aimed pretty much at exactly the same market.
Sybase & SAP – On the same day SAP announced it’s intention to purchase Sybase. The official SAP press release majors on the enhanced mobile and in-memory computing technologies that Sybase will bring to SAP, and this is indeed very much in line with SAP’s technical vision.
Join Julian as he speculates on the facts, rumors and implications of these acquisitions. Click here to read the full article.
As an xkoto business partner we received offical notification a couple of weeks ago that they had been acquired by Teradata Corporation. The announcement has now gone public – more details here. Xkoto was the creator of the clustering technology GRIDSCALE which was designed to improve database availability and scalability with minimal impact to the application. GRIDSCALE has now been withdrawn from sale with new customers still being supported but not able to purchase new licenses.
This is an interesting turn of events, especially considering the latest product update for the DB2 LUW platform from IBM – pureScale. You may have read about Triton’s involvement with pureScale when we became the first IBM Business Partners in Europe to work with the product. With GRIDSCALE leaving the market, pureScale is currently the only solution for increasing resilience and scalability for DB2 LUW.
We are continuing to build our skills on pureScale and we’re expecting to hear some new announcements from IBM soon so watch this space.
The agenda covers the full spectrum of information management and includes keynote sessions from leading IBM, customer, and business partner speakers. There are hands-on technical labs and industry round tables.
Our very own Julian Stuhler will be speaking at the Data Management keynote session on Wednesday 19th May at 15.15 CET. He will be on stage with Martin Wildberger, Vice President, Information Management Development. During the session Julian will be discussing his own personal technical experience and the experience Triton has had with DB2 9.7 and DB2 pureScale.
Keep up to date with all the happenings here and via twitter.
In his column for Database Journal Julian Stuhler looks at how an upgrade to DB2 10 can be justified.
Under current economic conditions IT professionals are being asked to give short-term business benefit cases before any major infrastructure upgrade is agreed.
DB2 10 has a lot of interesting new functions but the more immediate benefit is the promise of significant CPU reductions for most OLTP, query and batch workloads, with initial testing showing savings of 5-10% out of the box with no application changes, when compared to Version 9. As most DB2 for z/OS csutomers are on usage-based charging, CPU reduction tranlates directly into lower monthly fees for the DB2 licence – an immediate business benefit.
Triton Director, Julian Stuhler, has begun a new blog on toolbox.com.
Golden DB2 updates will cover techie tips, news and updates from the world of DB2. As an IBM Gold Consultant, Julian is always first on the list to hear about innovations in DB2 so subscribe today and keep up to date with the latest DB2 information. Julian would love to hear your thoughts so you can contact him by leaving your comments on the blog.
As always, the answer to this is “it depends”! However, here are some basic rules of thumb that you may find useful:
• Define an application environment specifically for your Java stored procedures. This should have NUMTCB set to a relatively low value (6-8 is good) as Java stored procedures typically require a lot of storage. Java SPs also have their own JCL DD statement requirements, such as entries for JAVAENV and JSPDEBUG.
• Define another environment specifically for your REXX stored procedures. Only a single REXX SP can run in any given application environment at any one time, so you need to set NUMTCB=1 for these.
• Define an application environment specifically for stored procedures that need to run under RACF program control (some of the IBM-supplied SPs fall into this category, such as DSNACCUC). These SPs need their own environment: if you try to execute both program-controlled and non program-controlled SPs in the same environment you’ll receive message ICH420I and the controlled SPs will fail.
• Define an application environment to host all of the IBM-supplied stored procedures that don’t fall into one of the above categories.
• Define 1-n environments for your “normal” COBOL, PL/1, C or SQL stored procedures. NUMTCB for these can typically be set fairly high (40-50 isn’t uncommon).
• Finally, you may want to consider having one or more test environments for your normal procedures, but with NUMTCB=1. This forces procedures to be run individually, which can be very useful during debugging when your procedure writes messages to address space log. Failing to do this can result in several procedures interleaving their debug messages, which can get very confusing. A simple ALTER PROCEDURE statement is all that is required to change the application environment, but don’t forget to stop/start the procedure afterwards.
