SELECT dbsname, tabname, DBINFO('dbspace', partnum)
ORDER BY 1, 2;
727: Invalid or NULL TBLspace number given to dbinfo(dbspace).
Error in line 3
Near character position 12
Yep – HCL broke thousands of scripts
From XC5 you can set DBINFO_DBSPACE_RETURN_NULL_FOR_INVALID_PARTNUM to reset back to the original functionaliy
An environment variable named DBINFO_DBSPACE_RETURN_NULL_FOR_INVALID_PARTNUM was created and can be set to a non-zero value to enable the new feature. It is not active by default to continue the existing behavior.
If it is set this way dbinfo('dbspace', partnum) will return NULL instead of an error when an invalid partnum is provided. This is true for any partnum that results in an invalid (db)space number. It includes the pseudo-tables for which the (db)space number is 0. For these tables the partnum is invalid in that sense. If a partnum of NULL is provided, the error -727 will be returned in any case.
The environment variable can be set:
1) as an environment variable for the instance
2) as an environment variable for the client like dbaccess
3) as a session environment variable
In this order of increasing precedence - meaning session environment takes precedence over client environment which takes precedence over instance environment.
You can request a special build - I did