OCUP minor command shows --init--

Technote (FAQ)


Why does the OCUP minor command of RGND always show me --init--?


Not enough collection cycles have occurred to gather required data


Customers sometimes ask why their 'region occupancy' continually shows as '--init--'.

OCUP is a minor command for the RGND major command designed to show you region occupancy. The REALTIME COMMANDS REFERENCE manual (SC27-4437) describes OCUP as follows:

      To calculate this number, OMEGAMON for IMS samples the message regions or DBCTL
      threads during every OMEGAMON for IMS cycle and observes the number of times it
      finds an active transaction or thread. (It does not consider a region in WFI wait active,
      which mens that WFI regions display as less than 100% occupied.) For the first 120
      samples (or about ten minutes when the interval is five seconds) the data is statistically
      insignificant, therefore OMEGAMON for IMS displays --init--.

If you issue the RGND/ocup commands within the Classic interface and receive only '--init--' in return, then pay close attention to the description of the field. The command requires 120 samples before it will produce results. In 2010's Version 420 an additional requirement was added for a minimum timeframe of 10 minutes in order to produce a metric that was 'statistically significant'. The most efficient method to collect these 120 samples is to turn on auto-update with a 5 second refresh for 10 minutes. If you simply issue the RGND/ocup command once and do NOT refresh the screen 120 times evenly over 10 minutes you'll still see '--init--'.

Rate this page:

(0 users)Average rating

Document information

More support for:

Tivoli OMEGAMON XE for IMS on z/OS

Software version:

4.2.0, 5.1.0

Operating system(s):


Reference #:


Modified date:


Translate my page

Machine Translation

Content navigation