z/VM: CP Commands and Utilities Reference - z/VM - IBM

ASSOCIATE MESSAGES / MSGS
Usage Notes
24 z/VM: CP Commands and Utilities Reference
Note: The order that you specify the entry points and external symbols is the
order in which CP will call them.
EPName name
is the name (or names) of the entry point or external symbol that points to the
data in CP’s system execution space where the local message repository can
be found. Each name must be a 1- to 8-character string. The first character
must be alphabetic or one of the following special characters: dollar sign ($),
number sign (#), underscore (_), or at sign (@). The rest of the string can be
alphanumeric characters, the 4 special characters ($, #, _, and @), or any
combination thereof.
Note: The order that you specify the entry points and external symbols is the
order in which CP will call them.
1. HCP is the standard component ID for z/VM messages. If you do not issue any
ASSOCIATE MESSAGES or MSGS commands (or configuration file statements)
for an entry point, HCPMES is, by default, the only message repository in the
search list for that entry point.
If you do assign one or more local message repositories to an entry point, those
repositories are added to the search list in the order that you specify (using the
REPLACE, FOLLOWING, or PRECEDING operands) and, by default, HCPMES
is the last message repository in the search list.
When the routines in that entry point issue a message, CP searches the first
message repository in the search list. If CP finds the message in that repository,
it issues the message and does not search any more repositories. If CP does
not find the message, it continues searching through each repository until it
finds the first occurrence of that message.
Using ASSOCIATE MESSAGES or MSGS commands (or configuration file
statements), you can assign local message repositories which override existing
z/VM messages in the HCPMES repository. Or, you can specify HCP as the
component ID and move the z/VM message repository to a place in the search
list other than last place.
2. Before CP can begin using your message repository, you must:
a. Generate your messages using the CMS GENMSG command. For more
information about the CMS GENMSG command, see the z/VM: CMS
Commands and Utilities Reference.
b. Load the message repository file using the CPXLOAD command (page 101).
3. If CP cannot find the message in the associated message repositories (or the
entry point can’t be found) when the message is being displayed, CP displays
message substitution data, if any.
4. To display information about the local message repositories available on your
system, use the QUERY CPLANGLIST command and specify the ASSOCIATED
operand (page 737).
5. To remove the message repository file from CP’s system execution space:
a. Use the DISASSOCIATE command (page 274) to revoke the external
symbol assignment made with the ASSOCIATE MESSAGES command or
configuration file statement
b. Use the CPXUNLOAD command (page 107) to unload the repository.
6. To have CP use the message repositories associated with a specific
component, you must specify that component ID on the COMPID keyword of