About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
AVOID VMFP2P1965E ERROR FOR MONDCSS SEGMENT BUILD
APAR Identifier ...... VM65651 Last Changed ........ 15/03/12
AVOID VMFP2P1965E ERROR FOR MONDCSS SEGMENT BUILD
Symptom ...... IN INCORROUT Status ........... CLOSED PER
Severity ................... 3 Date Closed ......... 15/03/05
Component .......... 568411209 Duplicate of ........
Reported Release ......... 630 Fixed Release ............ 999
Component Name ESA VMSESS Special Notice
Current Target Date ..15/01/29 Flags
SCP ...................
Platform ............
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List:
PTF List:
Release A62 : UM34557 available 15/03/12 (1000 )
Release A63 : UM34558 available 15/03/12 (1000 )
Release 620 : UM34559 available 15/03/12 (1000 )
Release 630 : UM34560 available 15/03/12 (1000 )
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
Attempts to rebuild the MONDCSS saved segment using PUT2PROD
(whether on an individual basis, or when all segments are
rebuilt using a PUT2PROD SEGMENTS ALL command) often fail
because one or more virtual machines continue to actively use
this segment during service-related tasks. The messages that
follow are indicative of this kind of problem:
...
VMFP2P1965E The command, SEND BLDSEG EXEC VMFBLD PPF SEGBLD
ESASEGS SEGBLIST MONDCSS.SEGMENT LINK (ALL NOLOG,
failed with return code 8
VMFP2P2760I PUT2PROD processing completed unsuccessfully for
SEGMENTS
VMFP2P2760I PUT2PROD processing completed unsuccessfully
...
LOCAL FIX:
Ensure no users are actively using the MONDCSS segment when
service tasks are performed. Such users can be identified
via the command: CP QUERY NSS USERS MONDCSS
(Here, the the monitor segment name of 'MONDCSS' is presumed to
be in use).
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: All z/VM customers applying z/VM service. *
****************************************************************
* PROBLEM DESCRIPTION: *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
When the MONDCSS segment is rebuilt, the segment cannot be in
active use by any users (which, for a system that is actively
collecting monitor data would be a normal case). Currently,
when this segment is built using the PUT2PROD SEGMENTS
command, and the segment is in use, the build attempt fails
and the previously described errors are reported. These
messages, and their explanatory documentation, do not provide
sufficient information for one to take corrective actions that
will allow an ensuing segment build to complete as intended.
Better information about this type of segment build error is
needed to assist whomever is performing the segment-related
maintenance tasks.
PROBLEM CONCLUSION:
The PUT2PROD EXEC has been updated to include additional logic
to determine whether the monitor segment (defined with the
default name of MONDCSS, or otherwise) is in active use by any
user IDs. If the monitor segment is found to be in use, and
this is the -only- segment that is to be built, this condition
will be reported by a new message, VMF1241E, and no attempt will
be made to build the segment. PUT2PROD command processing will
end due to this error condition.
If the monitor segment is in use, and it is being built in
conjunction with other segments (as is done for a PUT2PROD
SEGMENTS ALL command), message VMF1241W will be reported.
Again, this segment will not be built, but processing will
continue to allow the building of other segments to continue.
PUT2PROD also has been modified with this APAR, such that its
terminating message (2760) now will have a severity that
reflects encountered conditions (W, for encountered warnings, E
for encountered errors), instead of informational (I)
status for all invocations.
Documentation updates that pertain to new messages VMF1241W and
VMF1241E are cited below.
The following changes have been made to the system reference
libraries:
***START PUBLICATION CHANGE*************************************
Publication Title: z/VM: Other Components Messages and Codes
Release: z/VM 6.3.0
Order number: GC24-6207-02
Release: z/VM 6.2.0
Order number: GC24-6207-01
----------------------------------------------------------------
Chapter 3. System Messages
Section: VMSES/E Messages
Page(s): 166 <z/VM 6.3.0>
165 <z/VM 6.2.0>
The description for messages VMF11241 is added:
--------------------------------------------------------------
VMF1241W Segment segname cannot be built because it in use by
these user IDs: userid_list
(The segment is also in use by CP system event and
sample monitoring)
Explanation: The monitor saved segment cited by the message is
actively being used by one or more user IDs, as listed by the
message. Because this segment is in active use, it cannot be
built at this time.
Use of the segment by the CP system (listed as user ID
'SYSTEM') is further noted by additional message text, when
appropriate.
System Action: RC=4. Command processing continues.
User Response: The monitor saved segment needs to be rebuilt
only when the definition for it has been altered (such as to
increase the segment size). However, when PUT2PROD is used to
build ALL segments, or the monitor segment is named along with
other segments that are to be built, an attempt will be made to
build the monitor segment. If no definition changes have been
made with respect to the monitor segment, this warning
condition can likely be dismissed.
If monitor segment definition changes have been made, then take
appropriate action for each listed user ID to discontinue its
use of the named segment. Such action might require logging
off the subject virtual machine, or instead, quiescing the
services that it provides. When necessary, CP system event or
sample monitoring can be stopped by use of the CP MONITOR STOP
command.
If the subject segment is in use by the CP system (listed as
user ID 'SYSTEM') for event or sample monitoring, this activity
also must be stopped before the segment can be built.
After the segment has been successfully built, take appropriate
action to resume its use by the listed user IDs.
For more information about the monitor segment and its use,
consult the z/VM Performance Toolkit Guide or z/VM Performance
publications.
--------------------------------------------------------------
VMF1241E Segment segname cannot be built because it in use by
these user IDs: userid_list
(The segment is also in use by CP system event and
sample monitoring)
Explanation: The monitor saved segment cited by the message is
actively being used by one or more user IDs, as listed by the
message. Because this segment is in active use, it cannot be
built at this time.
Use of the segment by the CP system (listed as user ID
'SYSTEM') is further noted by additional message text, when
appropriate.
System Action: RC=100. Command processing stops.
User Response: The monitor saved segment needs to be rebuilt
only when the definition for it has been altered (such as to
increase the segment size). Because PUT2PROD has been invoked
specifically to build just this segment, it is presumed to be
to account for changes to the segment definition.
Take appropriate action for each listed user ID to discontinue
its use of the named segment. Such action might require
logging off the subject virtual machine, or instead, quiescing
the services that it provides. When necessary, CP system event
or sample monitoring can be stopped by use of the CP MONITOR
STOP command.
If the subject segment is in use by the CP system (listed as
user ID 'SYSTEM') for event or sample monitoring, this activity
also must be stopped before the segment can be built.
After the segment has been successfully built, take appropriate
action to resume its use by the listed user IDs.
For more information about the monitor segment and its use,
consult the z/VM Performance Toolkit Guide or z/VM Performance
publications.
***END PUBLICATION CHANGE***************************************
TEMPORARY FIX:
COMMENTS:
MODULES/MACROS: PUT2PROD VMFUME VMFUMEA VMFUMEB VMF1241E
VMF1241W
SRLS: GC24620701 GC24620702
RTN CODES:
CIRCUMVENTION:
MESSAGE TO SUBMITTER:
