z/VM: System Messages and Codes Š CP - z/VM - IBM

HCP6209I INVOKING ICKDSF.
Explanation: CPFMTXA uses ICKDSF to accomplish
the function designated from the command input. The
messages following this one will be issued by ICKDSF.
System Action: None.
User Response: None.
HCP6210I DEVICE SUPPORT FACILITIES
(5684-042) IS NECESSARY FOR CP
VOLUME MAINTENANCE. FILE ICKDSF
MODULE CANNOT BE FOUND ON ANY
ACCESSED DISK; CPFMTXA
PROCESSING ENDED.
Explanation: The CPFMTXA utility uses ICKDSF to
accomplish the function requested in the command line
input. The ICKDSF MODULE is placed on the CMS
system disk at installation.
System Action: None.
User Response: The CMS system disk may have
been released. Reaccess it.
Operator Response: Check if ICKDSF MODULE is on
your CMS system disk. If it is not, notify your system
support personnel.
HCP6224I {Sample|Event} recording is pending
because there are no users connected
to *MONITOR for this type of data.
Explanation: No user is currently connected to
*MONITOR for the specified data type because one of
following conditions has occurred:
For exclusive or shared mode:
v MONITOR EVENT START, MONITOR SAMPLE
START, or MONITOR START command has been
entered, but no user is connected to *MONITOR for
the type of data being started
For shared mode:
v The last (only) user has severed his path to
*MONITOR
v The last (only) user’s connection has been severed
by *MONITOR because the application purged the
monitor saved segment or logged off.
System Action: The specified monitor recording will
begin when a user connects to *MONITOR for that type
of data. If the high frequency sampling is enabled, the
high frequency counters are maintained. The count of
lost event records is not maintained.
Operator Response: If an application connects to
*MONITOR for the specified data type, monitoring is
activated for that data type.
HCP6227E Monitor {event|sample} collection is
not active.
Explanation: Monitor EVENT or SAMPLE monitoring
was inactive at the time the specified MONITOR STOP
command was entered.
System Action: None.
User Response: None.
HCP6228E Monitor sample collection cannot start
because DCSS dcssname is completely
partitioned for event data.
Explanation: A MONITOR SAMPLE START or
MONITOR START command was entered when the
saved segment was completely partitioned for event
monitoring. Because event monitoring is using the
whole saved segment, sample monitoring cannot be
started.
System Action: The command is rejected.
Operator Response: To run both sample and event
monitoring, enter a MONITOR EVENT STOP command
followed by a MONITOR START command specifying a
partition size that is less than the size of the saved
segment.
HCP6229E Monitor {event|sample} collection is
already active.
Explanation: A MONITOR START command was
entered, but the type of monitoring specified (event or
sample) is already active.
System Action: None.
User Response: None.
HCP6209I HCP6230E
HCP6230E Monitor event collection cannot start
because the block size is greater than
half the event data area
Explanation: A MONITOR EVENT START or
MONITOR START command was entered with the
specified BLOCK size was too large as compared with
the number of pages in the event data area of the
saved segment. If no BLOCK option was used on the
start command, a MONITOR EVENT BLOCK command
was entered before starting event monitoring. The
BLOCK size must be equal to or less than half the
number of pages in the event area of the saved
segment defined for MONITOR. (The number of pages
in the event area is equal to the number of pages in the
event partition, minus the number of pages reserved for
event configuration records by the MONITOR EVENT
CONFIG command.)
System Action: The command is rejected.
User Response: To display the number of pages
currently being reserved for event configuration records,
Chapter 3. System Messages 355