Record count warnings in CMCI

Setting up record count warnings causes a CICS® management client interface (CMCI) request to fail if a request is likely to result in the retrieval of an unacceptably large amount of data. You set up record count warnings by specifying a nonzero value for the DEFAULTWARNCNT initialization parameter during WUI server configuration when setting up CMCI.

DEFAULTWARNCNT can take an integer value in the range 0 - 99999999. The default value is 0, meaning that no warnings are issued.

If the warning mechanism determines that the number of records to be returned is greater than the value of the warning count, the request fails with an HTTP 403 response code. Users must issue a new request with different values for the SCOPE, CRITERIA and, in some cases, PARAMETER options to retrieve any results. If the returned value is less than or equal to the warning count value, the request is processed, in the usual way.

Note: In CMCI requests, the options count, index and SUMMONLY can be used to limit or prevent the display of records. However, these options do not influence the number of records requested and have no affect on the record count warning mechanism.

How to allow users to bypass record count warnings

If DEFAULTWARNCNT is set to a nonzero value, a warning count limit is in effect. Users can bypass the warning count limit by using the CMCI URI option OVERRIDEWARNINGCOUNT in their requests. For the CMCI URI option OVERRIDEWARNINGCOUNT to take effect, when setting up CMCI, you must set the RESOURCELIMIT initialization parameter to WARNING during WUI server configuration. If you want to prevent users from bypassing the warning count limit, set RESOURCELIMIT to FAIL.

When RESOURCELIMIT(WARNING) is in effect, if a request results in the retrieval of an amount of data larger than the warning count limit, a 403 HTTP response is returned and indicates that the errorInfo attribute override_warning_count_allowed is set to yes. The user can then bypass the warning count limit by using the CMCI URI option OVERRIDEWARNINGCOUNT in the request.

However, when RESOURCELIMIT(FAIL) is in effect, such requests are denied, and in the 403 HTTP response, the errorInfo attribute override_warning_count_allowed is set to no. Issuing a request with the OVERRIDEWARNINGCOUNT option will still result in the same 403 HTTP response.

Which CMCI resources are applicable

This feature does not apply to all resources. In the CMCI, record count warnings apply only to CMCI requests associated with the following resources:

CMCI Resources
AIMODEL
ATOMSERV
BRFACIL
BUNDLE
BUNDPART
CFDTPOOL
CICSDSA
CICSPAGP
CICSRGN
CICSSTOR
CLCACHE
CMDT
CONNECT
DB2CONN
DB2TRN
DB2ENTRY
DBCTLSS
DOCTEMP
DOMSPOOL
DSNAME
DSPGBL
DSPMODE
DSPPOOL
EJCOBEAN
EJCOSE
EJDJAR
EJDJBEAN
ENQUEUE
EPADAPT
EPADSET
EPAINSET
EVCSDATA
EVCSINFO
EVCSOPT
ENQMODEL
EVCSPEC
EVNTBIND
EVNTGBL
EXCI
EXITGLUE
EXITTRUE
EXTRATDQ
FEPICONN
FEPINODE
FEPIPOOL
FEPIPROP
FEPITRGT
HOST
HTASK
INDTDQ
INTRATDQ
IPCONN
IPFACIL
JRNLMODL
JRNLNAME
JVM
JVMPOOL
JVMPROF
JVMSERV
LIBDSN
LIBRARY
LOADACT
LOADER
LOCFILE
LOCTRAN
LSRPBUF
LSRPOOL
MASHIST
MODENAME
MONITOR
MQCON
MQCONN
MQINI
MVSESTG
MVSTCB
MVSTCBGL
MVSWLM
OSGIBUND
OSGISERV
PARTNER
PIPELINE
PROCTYP
PROFILE
PROGRAM
RECOVERY
REMFILE
REMTDQ
REMTRAN
REQID
RPLLIST
RQMODEL
RULE
STREAMNM
SYSDUMP
SYSPARM
TASK
TASKASSC
TASKESTG
TASKFILE
TASKRMI
TASKTSQ
TCPIPGBL
TCPIPS
TDQGBL
TERMNL
TRANCLAS
TRANDUMP
TSKSPOLS
TSKSPOOL
TSMODEL
TSPOOL
TSQGBL
TSQNAME
TSQSHR
UOW
UOWDSNF
UOWENQ
UOWLINK
URIMAP
URIMPGBL
WEBSERV
WORKREQ
XMLTRANS