What is XREF table?
What does it mean increasing it and how to calculate the new size?
Is it required to recycle Top Secret or a Refresh command is enough?
Is the XREF table allocated in the TSS region or in the STC specified in the message (J(jobname))?
-)At startup of a multi user region, the MAXUSER XREF table is built to hold the userid and key. This table is 12 bytes times the MAXUSER value, plus 16 bytes for table header. There is one 12 bytes entry for each user that signs on. The table is built in private storage above the line.
-) When the TSS0962E message is issued, the user is still allowed to signon, but there is no entry added to the XREF table for this user, so if the region abends, the storage for the user(s) is not freed. This could lead to orphaned storage.
The entry for a user is cleared and available to be reused after that user signs off.
Increasing MAXUSER will only affect the size of the MAXUSER XREF table built at startup of the region.
Changing MAXUSER requires a recycle of the region because the XREF table is built at startup.
The impact of increasing MAXUSER value is that the next time the region is started, the XREF table will be bigger (by 12 bytes * the difference between the old MAXUSER value and the new MAXUSER value) in CICS storage area, but this will not degrade CICS performance.
The table is built in private storage above the line.
The only impact is the amount of private storage available above the line.
The default value was set to 3000 because most multi user address spaces at majority client sites have 3000 or less users on at any one time.
The control option can be changed. If you are sure you have enough private storage available above the line to set MAXUSER with an higher value.
This does not effect your TSS secfile, this is an internal CICS region space.
-)The XREF table is allocated above the region STC started in the message:
STC60960 * TSS0962E MAXUSER EXCEEDED - XREF TABLE FULL - F (facility) J (jobname)
-)The parameter MAXUSER may be modified at any time for a FACILITY, but for the address space jobname must be recycled for the new parameter to take effect.