SMSGROUP command failed to return the data.on Batch job
Article ID: 260228
Updated On:
Products
Issue/Introduction
Recently we faced a issue with our batch jobs where it tried to issue SMSGROUP sysview command but it failed to return the data. But sometime later the jobs ran fine in the next run.
Below is what we could see:
The output from SMSGROUP looked like this at 0741 (system time) last night on SYSK for these pools
Name Status Type Volumes Capacity Free Large Used Used%
DB2PXXXX ENABLED POOL 16 0%
DB2PXXXX ENABLED POOL 16 0%
When it normally looks like this (like it did in the next run at 0805)
DB2PXXXX ENABLED POOL 16 25.9G 15.4G 10.7G 10.5G 41%
DB2PXXXX ENABLED POOL 16 25.9G 15.4G 10.9G 10.5G 41%
Could you please let me know what could have happened.
Environment
Release : 16.0
Cause
Some sort of problem with SMS pool availability
Resolution
The Storage pool that SYSVIEW was attempting to report on was unavailable at the time the job was run:
Scanning input for pool name "DB2PXXXX"
ERROR: Requested pool "DB2PXXXX" was not found in input.
READY
END
*** NEW BATCH FRONT-END NATURAL VERSION P912 ***
On the subsequent successful run:
Scanning input for pool name "DB2PXXXX"
Found this full record for DB2PXXXX
Name Status Type Volumes Capacity Free Large Used Used%
==> DB2PXXXX ENABLED POOL 16 25.9G 15.4G 10.7G 10.5G 41%
Processing "DB2PXXXX" FmtFree="15.4G" FmtUsedPct="41%"
Pool has 16,535,624,089 bytes or 291,818 tracks (59%) free
Output: 16 volumes matched DB2PXXXX - % Free: 59.0 - Free Tracks: 291,818
The customer will need to investigate SMS to find out why the storage pool was unavailable at the time of the batch job run.
Feedback
