Correcting a structure error of size

During initialization, JES2 issues the following messages if the size of the coupling facility structure is too small to contain the checkpoint data set:

The $HASP536 message with the following error message:
08, STRUCTURE IS NOT LARGE ENOUGH
The $HASP542 message with the following text:
$HASP542 MEMBER member_name--STRUCTUREstrname
IS NOT LARGE ENOUGH TO CONTAIN ALL CHECKPOINT DATA.
THE CURRENT SIZE IS ccccccK. THE SIZE MUST BE INCREASED
TO HOLD AN ADDITIONAL nnnnnn 4K ELEMENTS. THIS WOULD
REQUIRE A STRUCTURE SIZE OF AT LEAST mmmmmmK.

When you receive this message sequence, you must do one of the following tasks (the first being the preferable task):

If you have a predefined structure of adequate size to contain the JES2 checkpoint data set in a CFRM policy, you can activate that structure through the STRNAME= value on the CKPTDEF initialization statement.
If you do not have a predefined structure of adequate size in any CFRM policy, run the MVS™ utility cited in Defining JES2 structures in a CFRM policy and define a structure in a CFRM policy before continuing JES2 initialization.
Then, use the SETXCF commands to specify a new active CFRM policy that contains a predefined structure with enough 4K records to contain the checkpoint.
If you cannot run the MVS utility to create a CFRM policy, invoke the initialization version of the checkpoint reconfiguration dialog and specify the checkpoint data sets on DASD.
Note: For more information about how to use the SETXCF commands in specific scenarios, see z/OS MVS System Commands.