HRNKQ002W xxxx RTUQTASK HAS INITIATED A CHECKPOINT DUE TO INSUFFICIENT BUFFER ALLOCATION

HRNKQ002W xxxx RTUQTASK HAS INITIATED A CHECKPOINT DUE TO INSUFFICIENT BUFFER ALLOCATION

book

Article ID: KB0094597

calendar_today

Updated On:

Products Versions
TIBCO Object Service Broker for z/OS -
Not Applicable -

Description

Resolution:
Description:
============
The HRNKQ002W message indicates that the Data Object Broker (DOB) has run out of RESIDENTPAGES.

Environment:
============
o All Object Service Broker DOBs

Symptoms:
=========
If the HRNKQ002W message is being displayed in the DOB joblog then this means the DOB has run out of in-storage database pages and is having to steal pages from all users, including the user experiencing the problem.

Cause:
======
The RESIDENTPAGES parameter is set too low.

Resolution:
===========
Increase the RESIDENTPAGES parameter.

The DEFAULT RESIDENTPAGES value of 2 was set in the 1980s when real storage was at a premium. On current z/OS systems this is almost never the case and proper use of this real storage can greatly reduce the amount of I/O and CPU resources used by the DOB as well as greatly improving response times, sometimes, in really bad cases, by an order of magnitude.

Some useful guidelines on RESIDENTPAGES values.

1) Never set a value less than 10.
2) For test DOBs with multiple users or batch workloads a value of 50 is a good minimum.
3) For online production systems you should be looking at values in the hundreds.

As with all performance related recommendations you need to back these up with statistics from your systems however RESIDENTPAGES is one of the most critical performance settings for good DOB performance and provided you have the real storage to host these pages significant performance gains may be achieved.

References:
===========
TIBCO® Object Service Broker - Parameters
TIBCO® Object Service Broker for z/OS - Monitoring Performance

Issue/Introduction

HRNKQ002W xxxx RTUQTASK HAS INITIATED A CHECKPOINT DUE TO INSUFFICIENT BUFFER ALLOCATION