Skip to main content (Press Enter).
Skip auxiliary navigation (Press Enter).
IBM Community Home
AIOps & Management
Cloud Pak for Data
Hybrid Data Management
IBM Z & LinuxONE
Internet of Things
WebSphere & DevOps
IBM Z and LinuxONE Community
Skip main navigation (Press Enter).
Hybrid User Group
Upcoming Community Events
All Community Events
AIOps: Monitoring and Observability - Group home
IBM Z and LinuxONE - Software
Back to Blog List
MERGECAT WHILE-OPEN Enhanced in IBM Tivoli Advanced Catalog Management for z/OS
Wed September 28, 2022 09:59 AM
Normal MERGECAT WHILE-OPEN
a lot of high overhead processing, resulting in much longer run times than standard MERGECAT. WHILE-OPEN is required when there are open VSAM datasets on the level. If there are allocated datasets but no open VSAM datasets, then WHILE-OPEN(OPTIMIZE) (OPTIMIZE is now the default for WHILE-OPEN) can be used to do only the basic WHILE-OPEN alias-level activity blocking, but bypass the high-overhead full WHILE-OPEN processing. One operational difficulty with this is that MERGECAT WHILE-OPEN(OPTIMIZE) SIMULATE might run fast if there are no open VSAM data sets, but by the time the EXECUTE job is run, some VSAM data sets got open and the job will run for a lot longer because it now has to do the full WHILE-OPEN processing.
How to implement
MERGECAT WHILE-OPEN(OPTIMIZE-ONLY) can be specified. If it finds open VSAM data sets on the level, instead of continuing on using full WHILE-OPEN processing, it will wait a short time (user specifiable) and try again, for up to 5 minutes (user specifiable.) If it doesn't find a time with no open VSAM before the time limit expires, it will terminate with an appropriate message rather than falling back to doing full WHILE-OPEN processing and perhaps causing operational difficulties due to the unanticipated long run time.
For example, someone wanted to move the level containing their ZFSs. The problem is that they're always open. If they unmount them, they're closed for an instant but will probably get re-opened right away. So WHILE-OPEN(OPTIMIZE-ONLY) gives them a chance of getting it to run without the long run-time of WHILE-OPEN.
In general, this will benefit any situation where you can only tolerate the level block for as long as normal MERGECAT takes to run, but not for the extended run-time of full WHILE-OPEN, and it's difficult or risky to submit a WHILE-OPEN(OPTIMIZE) EXECUTE based on the run time of a SIMULATE because a VSAM data set could get opened unexpectedly in the interim.
This enhancement will benefit any situation where the Users of
can only tolerate the level block for as long as normal MERGECAT takes to run, but not for the extended run-time of full WHILE-OPEN, and it's difficult or risky to submit a WHILE-OPEN(OPTIMIZE) EXECUTE based on the run time of a SIMULATE because a VSAM data set could get opened unexpectedly in the interim.
Z16’s Direct-Connect for STP Feature
, 17 hours ago
IBM Open Enterprise SDK for Go 1.19 is now available!
, 22 hours ago
What's new in IBM Open Enterprise SDK for Go 1.19
Yuan Jie Song
, 23 hours ago
z/TPF DFDL parser available on linux on IBM Z (PJ46801)
, 2 days ago
November 2022 documentation refresh for Enterprise COBOL for z/OS 6.3
, 2 days ago
Copyright 2019 IBM Z and LinuxONE Community. All rights reserved.
Powered by Higher Logic
Add a tag
User Tags may not contain the following characters: @ # $ & :