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.
Start of change

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.

End of change

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


clientapi_defaultwarncnt.html | Timestamp icon Last updated: Sunday, 4 June 2017