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

ID (so they would both be unloaded together with a
CPXUNLOAD). You have two options:
1. Ensure the file that contains the external symbol is
CPXLOADed as PERMANENT. (See the z/VM: CP
Commands and Utilities Reference and the z/VM:
CP Planning and Administration for CPXLOAD
command and statement information.)
2. Ensure the file that defines the symbol and all the
files that have an address constant for the symbol
are loaded with one CPXLOAD operation. You can
use the INCLUDE loader directive to accomplish this
task (see the z/VM: CP Exit Customization book).
You could also place all the files to be loaded in a
TXTLIB. Loading all the files under one CPXLOAD
operation allows you to load these files as
TEMPORARY and thus be able to unload them at
some point in the future.
HCP2761E Encountered duplicate member in file
fn ft fm
Explanation: A CPXLOAD command or configuration
file statement is attempting to select the members to
load from a file based on a member pattern specified on
the CPXLOAD request. An error is reported if a member
is selected, but multiple copies of that member are
contained within the file.
System Action: Processing of the requested function
stops. System operation continues.
User Response: Use CPLISTFILE to get a list of the
members contained in the file. You should not create a
file that contains multiple copies of the same member.
Correct the problem and enter the command again.
HCP2765E CP Exit nnnn [entry point name
epname] has returned unsupported
[exit control] return code xxxx
Explanation: CP exit nnnn has returned an
unsupported return code value of xxxx by way of
register 15. If the unsupported return code is a control
return code, then the entry point name is shown.
Otherwise, the unsupported return code is a mainline
return code.
System Action: System operation continues.
If an unsupported control return code was detected,
then soft abend ZXU001 is generated. No further entry
points associated with this exit are invoked. Processing
continues where the exit was invoked.
If an unsupported mainline return code was detected,
then the additional action that CP takes depends on the
exit number and how it is coded to handle unsupported
mainline return codes.
User Response: Investigate why the exit routine
returned the unsupported return code. This may require
investigation of source code for the exit routine, use of
TRSOURCE, or even a system dump. For further
information on return codes generated by exit routines,
refer to the z/VM: CP Exit Customization book.
HCP2766E Attempt to open file fn ft fm failed,
return code from open is nnnn
Explanation: A command or a configuration file
statement that allows you to specify file information (for
example, CPXLOAD) is processing. An error was
encountered while trying to get information from that file.
System Action: Processing of the requested function
stops. System operation continues.
User Response: Check the return code provided. A
complete list of possible return codes is maintained in
an internal control block (HCPDRBK COPY).
HCP2767E Nothing was loaded
HCP2761E HCP2769E
Explanation: At the conclusion of CPXLOAD
processing, there was nothing left to be loaded. This
could be because no CSECTs were in the input files,
because all CSECTs were of length 0, or because all
CSECTs were deleted by ".DEL" TEXT statement or by
CHANGE directives.
System Action: CP rejects the request; system
operation continues.
User Response: Make sure that you are actually
trying to load something. Enter the request again.
HCP2768E Missing {file name|file
type|number|entry point name|file
member name|product|product
state|I/O priority|switchname}
Explanation: The statement or command requires that
you supply the indicated datum, but you did not.
System Action: CP rejects the request; system
operation continues.
User Response: Enter the request again, making sure
that you have supplied all required data.
HCP2769E CPXUNLOAD for load ID loadid has
been rejected; the reason
Explanation: A problem occurred while trying to
unload the customer-written CP routines associated with
load identifier loadid. CP did not unload the routines for
the specified load ID because of the indicated reason:
requested load ID was not found
CP could not find the load ID to unload,
perhaps because it was never loaded in the
first place or it was already unloaded.
requested load ID was loaded as PERMANENT
When the CPXLOAD operation for the load ID
was performed, option PERMANENT was
Chapter 3. System Messages 303