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

HCP6271A HCP6275E
connection to *MONITOR. Probably there is an
error in the CP-to-MONWRITE communications
protocol.
X'24' MONWRITE transmitted an invalid version
code for the CONNECT parameter list. This
probably means that there is an error in the
CP-to-MONWRITE communications protocol.
X'28' The saved segment passed by MONWRITE to
*MONITOR on the connect does not match the
saved segment already established by another
connected user. Since MONWRITE has loaded
the saved segment name given on the
command line (or by default uses the name
MONDCSS segment), MONWRITE should be
invoked again, using the name of the currently
established saved segment.
X'2C' The saved segment used by MONWRITE is
not large enough to satisfy the event partition
or event block values or configuration sizes
established by previously entered MONITOR
command. Either invoke MONWRITE again
with a larger saved segment, or use the
MONITOR command to change the
PARTITION or BLOCK values or configuration
sizes. Then invoke MONWRITE again.
X'30' MONWRITE transmitted an invalid CONNECT
parameter list that did not specify any data
type(s). This probably means that there is an
error in the CP to MONWRITE communications
protocol.
X'34' MONWRITE attempted to connect to
*MONITOR in exclusive mode, when monitor
was running in shared mode.
X'38' MONWRITE attempted to connect to
*MONITOR, but there was already a user
connected in exclusive mode. Only one user
can connect to *MONITOR in exclusive mode.
HCP6271A Warning: output file does not contain
initial sample configuration records
Explanation: The monitor writer has started writing
sample data, but the configuration data is missing. If
connected to *MONITOR, the data is missing because
the writer did not reply in time to the configuration data
send.
If connected to another IUCV server, the data may be
missing because either the IUCV server was already
actively receiving notifications for sample data, or
because the writer did not reply in time to the
configuration notification sent from the IUCV server.
System Action: The monitor writer function continues
writing data to the output file. However, this output file
may not be usable.
User Response: If the program that reduces the
output from the monitor writer can tolerate the fact that
364 z/VM: System Messages and Codes — CP
|
|
|
|
|
|
|
|
|
|
|
the output file does not have the initial configuration
data, then no action is required. If in doubt, contact the
system programmer, who should examine the input
requirements for the reduction program.
If the program that reduces the output cannot tolerate
the fact that the output file does not have initial
configuration data, then enter MONWSTOP to end the
monitor writer. If it is important to collect data using the
monitor writer at this time, then also stop the IUCV
server that is connected to *MONITOR. Once all are
stopped, restart the monitor writer and the other IUCV
server, using each program’s startup procedure. Once
all are ready, enter CP MONITOR START, and the
monitor writer will see the initial configuration data.
HCP6274I The {sample|event} data messages and
corresponding records have been
purged.
Explanation: You have not replied to data messages
as required. IUCV messages and corresponding data
records have been purged.
System Action: The specified IUCV messages
previously sent to the user, or pending for the user, are
purged. The corresponding saved segment pages are
freed for reuse by monitor.
User Response: A user with the appropriate privilege
class can take the following actions to alleviate the
problem:
v Enter the MONITOR SAMPLE INTERVAL command
to make the interval length larger, which will allow the
application program more time to process the sample
data.
v Stop event monitoring, then restart it with a larger
event partition.
v Enter the SET SHARE command to increase the
access priority of the receiving virtual machine to
system resources.
Refer to z/VM: CP Commands and Utilities Reference
for more information on the SET SHARE command.
Programmer Response: Determine why the
application was unable to reply to the data notification
messages.
HCP6275E An error occurred writing to the
subchannel for device rdev, code =
code.
Explanation: A nonfatal error (specifically, error code
code) occurred while issuing a channel subsystem call.
If this is the result of attempting to attach a device, the
device is not attached.
System Action: The command is not executed;
system operation continues.
User Response: Retry the command at a later time. If
the problem persists, it is probably a hardware