Cancel this one, satisfied with CICSTS53 - XMEO filtered out. CICS UDT Datatable NOSPACE when IEF043I specified limit hit - need message in Joblog

Cancelling RFE.

RFE satisfied with TS53 message DFHFC0432 and was suppressed by our local XMEO exit.

CICS UDT DataTable gets NOSPACE returned when IEF043I specified limit hit.

No indication Dataspace storage limit hit in CICS Joblog; WUI and Explorer show zero writes rejected when backing dataspace of table full.

Diagnostic data for Dataspace limit hit, would be very useful; message in Joblog or other.

In our example the Dataspace size max was hit for CICS; not that the Max Records of table was full.

It would be good to have an IEFxxxx max hit or some other indication of why NOSPACE condition raised. Usually NOSPACE for UDT, means that the max number records hit.

Can put out an automations message that CICS is in trouble for Dataspace backing UDT's.

For regular VSAM; can run LISTCAT of file to identify NOSPACE in VSAM file.

Application will get a 103 for RESP2; but application not checking for that, to identify the issue and this could be CICS wide issue for applications using UDT.

For UDT; the error is somewhat opaque if not checked by application.

Fortunately; it was recognized that a change occurred; going from IEFUSI to SMF, that introduced this issue.

IEF043I Actions taken by SMFLIMxx parmlib policy for J8D1PRD1 IEFCICS

Step region above changed to NOLIMIT by policy - SMFLIM04 0001

Step system reserved below set to 512K by policy - SMFLIM04 0001

Step system reserved above set to 50M by policy - SMFLIM04 0001

Step MEMLIMIT set to NOLIMIT by policy - SMFLIM04 0005

Step dataspace number limit set to 4096 by policy - SMFLIM04 0003

Step dataspace size limit set to 4G by policy - SMFLIM04 0003