can someone please point me to the page in the manuals where it says that 32k tablespaces in the WORK database must be segmented and cannot be UTS PBG?
In today's chapter of the WORKDB saga, I dropped/created all tablespaces in our WORKDB (in our sandbox AND in our TEST environment, which hosts some TCM databases, for example) to make them UTS PBG, and then this, that and the other stopped working with abends in object type 100 and 200 - the datasets couldn't get extents.
here is one error from one of our apps:
SELECT * FROM T9999.ISS3RESSOURCEN WHERE SYS_NAME = 'SYSCAT' ORDER by RES_ID ;
SQLERROR ON SELECT COMMAND, OPEN FUNCTION $$$
RESULT OF SQL STATEMENT: $$$
DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN
UNAVAILABLE RESOURCE. REASON 00C90084, TYPE OF RESOURCE 00000100, AND
RESOURCE NAME DB2-MANAGED SPACE WITHOUT SECONDARY ALLOCATION OR US
DSNT418I SQLSTATE = 57011 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXRSOR SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = -115 13172746 0 13231826 -959250432 0 SQL
DSNT416I SQLERRD = X'FFFFFF8D' X'00C9000A' X'00000000' X'00C9E6D2'
X'C6D30000' X'00000000' SQL DIAGNOSTIC INFORMATION
So I tried dropping the only one now defined with SECQTY -1 and recreating that one only as segmented, still no soap.
It only works if ALL the 32k tablespaces are segmented, independently of the SECQTY definition (the 4k don't seem to bother it) - so it must be documented somewhere and I have forgotten it, but I'd like to find out where... because when I look for it I find instead completely conflicting information like in here:
TIA, have a good weekend.
PS stay safe and healthy
NB black lives matter