In this session we will explore relevant industry trends and considerations, and a comprehensive solution that can start and grow with you and your DevOps journey.ĭan Luksetich is a Db2 DBA consultant. For Db2 to be a first-class participant in an organization’s competitive innovation delivery, requires a forward-thinking culture that can adapt Db2 processes and tooling to meet today’s demands to outperform competition. It will not just be an extended use of existing tools. This next frontier will not just be a new or enhanced feature within Db2. Addressing data friction in modern DevOps processes by offering Db2 Database as a Service, may be the biggest challenge to date.
![db2 administration tool for z os db2 administration tool for z os](https://slideplayer.com/12863764/78/images/slide_7.jpg)
Session abstract: Db2 has kept pace with technological and business challenges for over 3 decades.
![db2 administration tool for z os db2 administration tool for z os](https://docplayer.fr/docs-images/41/1341647/images/page_10.jpg)
Session title: Db2 for z/OS, the Next Frontier Subject: Db2 z/OS 12 - I'm having a HOLDDATA nightmareWatch recording (logged in Tridex members only) You can confirm this for yourself.the output from your APPLY CHECK should show UI74139 as superseded and UI77711 as APPLIED.
#DB2 ADMINISTRATION TOOL FOR Z OS CODE#
So my guess is that your APPLY is bringing in both PTFs, and 77711 is superseding 74139.but the effect to the enclave management code is the same, so 77711 is set up to dig up the 74139 HOLD ACTION and display it to you, so you know about it. It did NOT show the HOLDDATA for UI74139. So 77711 has to post the same warning as 74139.įor giggles, I tried an APPLY CHECK for UI77711 on my own system, where 74139 is already on. Not sure SMP/E would know about it since it's in a different SREL. The WLM code that interfaces with UI77711 may or may not be available yet. UI77711 is the PTF that "fixes" that issue, combined with a new WLM function. We actually ran into this problem with our DDF enclaves due to high performance DBATs. Those jobs will now fail with the updated Mutually exclusive to TARGET_TYPE = 'AUTO' and were previously ++ HOLD(UI77516) SYSTEM DATE(21281) FMID(H0IHC10) REASON(ACTION)Įxisting CM batch JCL should be checked for options that are PTF UI77516 already installed/superseded in platform xxxxxxx In any of the job_card_line parameters and make * FMID H0IHC10 - IBM DB2 Administration Tool for z/OS To return to the previous panel, enter END. R1xx CSI QUERY - SYSMOD ENTRY Row 1 to 4 of 10 Just to give you an example, I have included a few of the "duplicate" PTFs below:
![db2 administration tool for z os db2 administration tool for z os](https://higherlogicdownload.s3.amazonaws.com/IMWUC/UploadedImages/d09b827f-45d4-4ec5-aead-46628e62751c/mo7_.png)
I mean I thought ENHANCED HOLDDATA just gave you the blasted details of whether the PTF was already there, and a list of pre- and co-requisites and dependencies, but I have never in my working life seen such a jumble, with the PTF ACTION text nested under the other one. Imagine my shock-horror when I saw that out ++HOLD REASON(ACTION) list was about 6,000 lines!Īnd then I noticed that for some unknown reason have included all the HOLD text for each PRE and SUP PTF, in the ++HOLD ACTION body of each PTF – I don't know if this is the case for the other products as well, but it certainly means >6,000 lines of HOLD data for our product, and a lot of replication to be sorted through. I am REALLY having a HOLDDATA nightmare - due to one reason or another, we last applied maintenance to our Db2s about 6 months ago, and so have a huge number of PTFs to apply now.