z/OS JES2 Messages
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


$HASP542

z/OS JES2 Messages
SA32-0989-01

$HASP542

Explanation

Read syntax diagramSkip visual syntax diagram
>>-MEMBER--member_name –  – --STRUCTURE--strname---------------->

>--IS NOT LARGE ENOUGH TO CONTAIN ALL CHECKPOINT DATA.---------->

>--THE CURRENT SIZE IS ccccccK. THE SIZE MUST BE INCREASED------>

>--TO HOLD AN ADDITIONAL aaaaaa 4K ELEMENTS. THIS WOULD--------->

>--REQUIRE A STRUCTURE SIZE OF AT LEAST nnnnnnK.---------------><

JES2 attempted to use the coupling facility structure strname, but the structure is not large enough to contain the checkpoint data set. In the message text:
member_name
The name of the JES2 member.
strname
The name of the coupling facility structure.
ccccccK
The current size of the structure
aaaaaa
The number of 4K elements that would not fit in the current structure.
nnnnnnK
The minimum structure size needed to hold all the checkpoint data. JES2 determined this size by adding 4 times aaaaaa to the current structure size; however, this dies not account for any control data associated with the 4K elements. If aaaaaa is larger than 50, then a structure of this size might not be large enough to hold the checkpoint.

System action

JES2 stops processing.

Operator response

Notify the system programmer.

System programmer response

Specify a new, larger coupling facility structure that has been defined in the active CFRM administrative policy. To determine the exact size required, calculate the total storage required to hold aaaaaa 4K elements on the coupling facility on which the structure is to be placed and then add that value to cccccc. If a large enough structure does not exist, move the checkpoint to DASD and restart JES2. See z/OS MVS Setting Up a Sysplex for more information about CFRM policies.

Module

HASPCKDS

Routing Code: 2,10

Descriptor Code: 4

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014