Hi,
We have a problem with the subject check.
We have added three system to our sysplex in the sysplex CDS and the day
after the health check show this check. We've solved two sizes problems in
structures but we can't remove the check for the last structure.
The last structure has a problem of size and number lists (h. checker says)
but both of the checks are related between them. We've execute the cfsizer
and increase the size but the check continues.
We have increased the structure size three times and we can't remove it!!!.
And the best: we rebuild the structure to the other CF and the check
dissappears !!!.
When the structure return to it own CF the check return again.
We attach the check in the post.
Kind regards
Jorge García Juanino
Técnico de Sistemas Z/Os/Área de Producción y Tecnología
MAPFRE TECNOLOGÍAS DE LA INFORMACIÓN
Crtra. De Pozuelo nº 52
28220 Majadahonda (Madrid)
Tfno: 91 581 27 34/ 618 33 35 59
Fax: 91 581 24 01
[EMAIL PROTECTED]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
De: Cadena HZSPRINT
Enviado el: miércoles, 25 de junio de 2008 12:55
Para: zzl DGTP IT Soporte Sistemas z/OS
Asunto: CHECK(IBMXCF,XCF_SIG_STR_SIZE) en LNA4
1************************************************************************
* *
* HZSPRINT (HBB7730-06024) 2008/06/25 12:55 *
* *
* HZSU001I Check messages *
* Sysplex: SYSPLEX0 System: LNA4 *
* *
* Filter: CHECK(IBMXCF,XCF_SIG_STR_SIZE) *
* *
************************************************************************
************************************************************************
* *
* Start: CHECK(IBMXCF,XCF_SIG_STR_SIZE) *
* *
************************************************************************
CHECK(IBMXCF,XCF_SIG_STR_SIZE)
START TIME: 06/25/2008 12:55:21.679889
CHECK DATE: 20050130 CHECK SEVERITY: MEDIUM
CHECK PARM: 20
* Medium Severity Exception *
IXCH0247E Structure IXCPATH6 does not have enough lists to support full
signal connectivity.
Explanation: This check assumes that a signal structure is intended
to support full signal connectivity among all possible systems in
the sysplex. The expected number of systems in the sysplex is
determined by the number of systems supported by the primary sysplex
couple data set. The structure has 0 lists, but 140 lists are needed
to provide full signal connectivity between all 12 systems that
could be in the sysplex.
Whenever XCF allocates a signaling structure, it tries to allocate
it with enough lists to provide full signaling connectivity among
all possible systems in the sysplex. If XCF finds it needs more
lists, it will attempt to rebuild the structure to get them. When
XCF switches to a new primary sysplex couple data set that supports
more systems than the previous one, it will attempt to rebuild the
structure to get more lists in anticipation of the need to establish
signaling paths with more systems. The failure of this check
suggests that XCF was unable to allocate the structure with the
desired number of lists (an unlikely pathological case caused by
space constraints), or its attempt to rebuild the structure failed.
System Action: The system continues processing normally.
Operator Response: Report the problem to the system programmer.
System Programmer Response: Examine logs to determine why the rebuild
of the structure failed. Messages IXL013I and IXL015I are relevant.
Resolve the indicated problem(s). If XCF does not automatically
initiate a rebuild of the structure with an appropriate number of
lists as a result of the problem resolution, initiate a rebuild of
the structure. To do so, issue the command SETXCF
START,REBUILD,STRNAME=IXCxxx where "IXCxxx" is the name of the
signaling structure. Upon successful completion of the rebuild,
verify that the structure was allocated with the necessary number of
lists. XCF issues message IXC457I on the system that allocates the
structure to indicate the number of lists in the structure and the
number of systems that can establish full signaling connectivity
through those lists.
Problem Determination: N/A
Source: Parallel Sysplex (XCF)
Reference Documentation: z/OS MVS Setting Up a Sysplex
Automation: N/A
Check Reason: Avoid problems with XCF signalling in CFs.
* Medium Severity Exception *
IXCH0248E Structure IXCPATH6 is too small for full signal
connectivity.
Explanation: This check assumes that a signal structure is intended
to support full signal connectivity among all possible systems in
the sysplex. The expected number of systems in the sysplex is
determined by the number of systems supported by the primary sysplex
couple data set. When a list within the structure is used for a
signal path, the owner specification requires that there be at least
20 list entries available for each list (each such list entry
corresponds to one XCF signal). If this structure were to be used to
provide full signal connectivity between all 12 systems that could
be in the sysplex, there would fewer than 0 list entries per list.
System Action: The system continues processing normally.
Operator Response: Report the problem to the system programmer.
System Programmer Response: Run the CF sizer tool available on the
Web to determine the appropriate structure size. Modify CFRM policy
accordingly. Activate that policy. Rebuild the structure.
Problem Determination: N/A
Source: Parallel Sysplex (XCF)
Reference Documentation: z/OS MVS Setting Up a Sysplex
Automation: N/A
Check Reason: Avoid problems with XCF signalling in CFs.
END TIME: 06/25/2008 12:55:21.683553 STATUS: EXCEPTION-MED
************************************************************************
* *
* End: CHECK(IBMXCF,XCF_SIG_STR_SIZE) *
* *
************************************************************************
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
