Sometimes it is possible to find in CA OPSMVS OPSLOG some messages related to an Abend S0C3 in module OPCOSB, even if the product functionality is apparently not affected by these abends.
Below a sample situation :
... OPM3092H ABEND X'000C3000' in GET POOL STORAGE OPCOSB+X'0000336C' detected at OPUNFU+X'F95EF6FA' OPM3092H CA OPS/MVS ABEND 0C3000 detected at OPCOSB+0000336C OPM3092H PSW at ABEND 078C1000ABAC736C - data at 2BAC7366 ===> 00044420C1F855307018A7D4 OPM3092H Last PRB PSW 078D0000B23300C2 - data at 323300BC ===> 40404040E39981838540F140 OPM3092H ABEND - caused by tag check failure OPM3092H Home:0397 Prime:0134 Sec:0397 ABEND Interrupt Code:000 OPM3092H R0=00000001 PSA +0001 0A000000 0130E100 00000000 000 ...
Why this abend and how to correct it?
Z/OS CA OPSMVS
It has been verified that one of the main cause of this abend is the value defined in GENERICPOOLSIZE initial parameter. In CA OPSMVS Reference Guide there is the following explanation about this parm:
Determines the size of the storage pool used by a number of basic and optional CA OPS/MVS facilities (for example, ADDRESS USS and ADDRESS NETMAN).
* Default value 1024 KB
* Other possible values Any amount of storage between 524288 bytes (512 KB) and 67108864 (64 MB) bytes
* Set or modify this parameter… At initialization
So, increasing GENERICPOOLSIZE to 2465K the abend will be bypassed. This change can be done as follows:
T = OPSPRM_SET("GENERICPOOLSIZE","2465K")
Please note this parameter is only allowed at startup, so the product will have to be recycled after the OPSSPA00 (or your parm member) has been updated.
If this change doesn't address the problem , Please open a case with Broadcom Support and provide the archived OPSLOG with also the System Dump collected for this Abend.