Appendix A. MESSAGES
This appendix contains the description for messages produced
by the VM Data Transfer Program. These messages have a
slightly different format, depending on whether the messages
are produced in CMS or MVS.
CMS MESSAGES
Messages produced by the VM Data Transfer Program code, which
operates only in CMS, are in the standard VM message format
and can be affected by the CP SET MSG command. The message
format is:
cccmmmnnnl message text
where:
ccc - is the component prefix of VMT.
Some IBM values for ccc are:
DMS - a CMS message
HCP - a VM/ESA CP message
DMT - an RSCS message
mmm - is the name of the function issuing the
message
nnn - is the message number
l - is the message level indicator. The values
for this are:
I - informational message
W - warning message
E - error message
S - severe error
T - error causing immediate termination
R - input request
Different modules may issue the same message. Messages are
listed by number to help locate the explanations.
Example: Message VMTGEN109I is listed as message 109.
MVS MESSAGES
Messages produced by the VM Data Transfer Program code that
operates only in MVS are in the standard MICSLOG message
format:
ccc00nnnl message text
where:
ccc - is the component prefix of VMT
nnn - is the message number
l - is the message level indicator. The values
for this are:
I - informational message
W - warning message
E - error message
+---------+
| 001 |
+---------+
TEXT: Help completed
TYPE: Information
REASON: A function providing information was exited.
ACTION: None required.
+---------+
| 002 |
+---------+
TEXT: Data type misspelled or omitted: ........
TYPE: Error
REASON: A function that requires a datatype as a parameter
was invoked in error with this parameter.
ACTION: Correct the error and reissue the command.
+---------+
| 003 |
+---------+
TEXT: Unknown parameter(s): <value>
TYPE: Error
REASON: A function was called with parameters that were not
recognized.
ACTION: Correct the parameter(s) and restart the command or
function.
+---------+
| 004 |
+---------+
TEXT: Keyword parameter missing before parenthesis
TYPE: Error
REASON: A command was issued without the correct keyword
parameter specifications.
ACTION: Reissue the command with the correct parameter(s).
+---------+
| 005 |
+---------+
TEXT: Parameter specified is not recognized or not
supported
TYPE: Error
REASON: A command was issued with an invalid parameter.
ACTION: Reissue the command with the correct parameter(s).
+---------+
| 006 |
+---------+
TEXT: Return code: <rc> received from VMTFDEF(type,dd)
TYPE: Error
REASON: VMTXMIT received a non-zero return code from
VMTFDEF. Other messages may be associated with this
one.
ACTION: Correct the problem and restart VMTXMIT.
+---------+
| 007 |
+---------+
TEXT: <option> requires Y or N as a parameter, <value> was
entered
TYPE: Error
REASON: The indicated option was given an incorrect
parameter value.
ACTION: Correct the parameter.
+---------+
| 008 |
+---------+
TEXT: Return code <rc> from STATE [set the File Name variable]
TYPE: Error
REASON: An error occurred while attempting to locate the
named file.
ACTION: Determine the reason the error occurred, and correct
the condition. Refer to the CMS Command and Macro
Reference for STATE return code definitions.
+---------+
| 009 |
+---------+
TEXT: <i/o> medium incorrectly specified as <value> -
should be <medium>
TYPE: Error
REASON: The transmission mode or data source was incorrectly
specified.
ACTION: Correct the parameter.
+---------+
| 011 |
+---------+
TEXT: INTERNAL ERROR - field at: <location> has no
matching variable.
TYPE: Error
REASON: A screen field has been incompletely defined. This
is a consistency check.
ACTION: Correct the code error and retry the display.
+---------+
| 012 |
+---------+
TEXT: Invalid characters in [set the File Name variable]
TYPE: Error
REASON: A file name was entered, but it contained characters
that were not valid for the CMS file system.
ACTION: Specify an acceptable filename.
+---------+
| 013 |
+---------+
TEXT: RC=<rc> attempting to validate RSCS userid <id>
TYPE: Error
REASON: A userid was specified that does not exist on your
system.
ACTION: Provide the correct userid.
+---------+
| 014 |
+---------+
TEXT: Unrecognized PF key
TYPE: Warning
REASON: A program function key was pressed for which no
action has been defined.
ACTION: Press another PF key.
+---------+
| 015 |
+---------+
TEXT: VMTXMIT parameters have been set for <datatype>, set
enter 'VMTXMIT PARMS' and restart the transmission
process.
TYPE: Error
REASON: The parameters for VMTXMIT were not set prior to the
first attempt to transmit data.
ACTION: Set the parameters and retry the transmission
process.
+---------+
| 016 |
+---------+
TEXT: Bad parameter(s) passed to VMTFDEF: <values>
TYPE: Error
REASON: VMTFDEF did not recognize the parameters passed to
it by VMTXMIT. This is probably due to changes made
to VMTXMIT that have not also been made to VMTFDEF.
ACTION: Regenerate VMTFDEF and restart VMTXMIT. If the error
persists, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 017 |
+---------+
TEXT: Device at address <cuu> is <type> not <type>
TYPE: Error
REASON: An attempt to validate a device type failed.
ACTION: Correct the condition by placing a virtual device of
the correct type at the address indicated and retry
the command.
+---------+
| 018 |
+---------+
TEXT: Return code <rc> from command <name>
TYPE: Informational
REASON: A command issued a permissible return code.
ACTION: None required.
+---------+
| 019 |
+---------+
TEXT: Return code <rc> from command <name>
TYPE: Warning
REASON: A command issued an error return code.
ACTION: Correct the condition and retry the command.
+---------+
| 020 |
+---------+
TEXT: Generation procedure completed successfully
TYPE: Information
REASON: The requested code generation was performed.
ACTION: None required.
+---------+
| 021 |
+---------+
TEXT: Required input file(s) could not be located.
Terminating.
TYPE: Error
REASON: The command issued required one or more files for
operation, but these were not available.
ACTION: Correct the condition based on the command issued.
+---------+
| 022 |
+---------+
TEXT: INTERNAL ERROR: <err> - line: <num> - unexpected
value in <variable>. Variable contains <value>
TYPE: Error
REASON: An internal consistency check failed.
ACTION: Correct the code and retry the command.
+---------+
| 023 |
+---------+
TEXT: File <name> does not exist. FILEDEF <dd> DUMMY
used
TYPE: Warning
REASON: VMTXMIT determined that an optional file could not
be located.
ACTION: If the default settings or conditions are
satisfactory, none required. Otherwise, create the
named file.
+---------+
| 024 |
+---------+
TEXT: Generation procedure completed successfully
TYPE: Information
REASON: The requested code generation was performed.
ACTION: None required.
+---------+
| 025 |
+---------+
TEXT: <command> may not be run in CMS SUBSET
TYPE: Error
REASON: An attempt to run a command that must be loaded
into the CMS user area was made while that area was
in use.
ACTION: Do not issue the command.
+---------+
| 026 |
+---------+
TEXT: Help file <name> has been generated
TYPE: Information
REASON: The requested file generation was performed.
ACTION: None required.
+---------+
| 027 |
+---------+
TEXT: Required parameter has not been specified <parm>
TYPE: Error
REASON: A command was issued without the named parameter.
ACTION: Reissue the command with the named parameter.
+---------+
| 028 |
+---------+
TEXT: Expected parameters <parm> not found in [set the File Name variable]
TYPE: Error
REASON: VMTMNT encountered an invalid FIXINFO File.
ACTION: For assistance, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 029 |
+---------+
TEXT: Maintenance item <fixnum> has been loaded to disk
TYPE: Information
REASON: The named maintenance has been loaded to the product
installation minidisk.
ACTION: None required.
+---------+
| 030 |
+---------+
TEXT: Installation of maintenance item <fixnum> is now
<status>
TYPE: Information
REASON: The named product change is in the process of being
applied, and is in the indicated status.
ACTION: None required.
+---------+
| 036 |
+---------+
TEXT: The operating system type/level for this generation
is not recognized. Contact the CA MICS Product
Support Group for assistance. System level data:
<name>
TYPE: Error
REASON: The operating system is not z/VM or VM/ESA.
ACTION: For assistance, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 037 |
+---------+
TEXT: <name> Group/type combination unrecognized: <name>
TYPE: Error causing immediate termination
REASON: The internal screen code contains an error.
ACTION: If you are making screen modifications, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 038 |
+---------+
TEXT: New file initialized from distribution sample
TYPE: Information
REASON: No existing SELECT or JCL file was found. A new
file was initialized that contains the default
parameters from the distributed CA MICS VM Data
Transfer Program tape.
ACTION: Use the default parameters or edit the file to
tailor the parameters to your installation.
+---------+
| 039 |
+---------+
TEXT: Line <n> Unrecognized opcode <n>
TYPE: Error
REASON: The SELECT File contains an unknown parameter.
ACTION: Edit the file to use only SELECT, EXCLUDE, or
UNKNOWN statements.
+---------+
| 040 |
+---------+
TEXT: An error has occurred in < >. Please report this to
the CA MICS Product Support Group. The error
occurred on line <n> with error code <n>. The REXX
error is <text>. The line in error is <n>. REXX
debug mode is now being entered.
TYPE: Error
REASON: This is an internal error.
ACTION: For assistance, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 041 |
+---------+
TEXT: Line <n> Unrecognized parameter for UNKNOWN: < >
Correct values are SELECT or EXCLUDE.
TYPE: Error
REASON: SELECT File does not specify the records to select
or exclude from the raw input data.
ACTION: Review the SELECT File and use the SELECT or EXCLUDE
parameter to specify the desired data.
+---------+
| 042 |
+---------+
TEXT: Line <n> Unrecognized <Domain/Class>: <n>
<Record/Code>: <n>
TYPE: Error
REASON: The SELECT File contains a VM input record
specification combination that the program does not
recognize as valid.
ACTION: Review the SELECT File and correct the error.
+---------+
| 043 |
+---------+
TEXT: Return from OpCodeCheck = <n>
TYPE: Error
REASON: This is an internal screen definition error.
ACTION: If you are making screen modifications, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 044 |
+---------+
TEXT: Syntax check completed without errors.
TYPE: Information
REASON: The requested syntax check was successful.
ACTION: None
+---------+
| 060 |
+---------+
TEXT: An unsupported XEDIT tag has been generated. This
is an unexpected condition and has been ignored.
Tag <n> Data <text>
TYPE: Warning
REASON: The internal screen code is generating an erroneous
edit tag.
ACTION: If you are making screen modifications, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 061 |
+---------+
TEXT: Unrecognized function request: <name>
TYPE: Error
REASON: The internal screen code contains an error.
ACTION: If you are making screen modifications, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 062 |
+---------+
TEXT: Undefined key: PFK<n>
TYPE: Error
REASON: You have used a function key that the program does
not recognize.
ACTION: Choose a function that is defined on the screen.
+---------+
| 063 |
+---------+
TEXT: Menu item <n> is not defined for screen <name>
TYPE: Error
REASON: You have pressed an invalid key for this screen.
ACTION: Choose a menu item that is defined on the screen.
+---------+
| 064 |
+---------+
TEXT: Screen name <name> is not defined.
TYPE: Error
REASON: The internal screen code contains an error.
ACTION: If you are making screen modifications, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 065 |
+---------+
TEXT: Input screen definition file <name> and error screen
file <name> are missing.
TYPE: Error
REASON: The requested screen is not defined and the error
screen is missing. This is a product installation
(VMTDSP screen) error.
ACTION: If you are installing a modified screen, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 066 |
+---------+
TEXT: Unrecognized screen build code: <n> in file <name>
at line <n>.
TYPE: Error
REASON: The internal screen definition code contains an
error.
ACTION: If you are making screen modifications, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 067 |
+---------+
TEXT: Field <name> has not been previously defined for
screen <name>. Cursor will be positioned at <line>
<column>.
TYPE: Warning
REASON: The internal screen definition code contains an
error. The cursor has been placed at an undefined
field.
ACTION: If you are making screen modifications, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 068 |
+---------+
TEXT: Menu item of "0" is not allowed. Screen <name>
TYPE: Error
REASON: The internal screen definition code contains an
error. "0" is not permitted for use as a menu
selection.
ACTION: If you are making screen modifications, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 069 |
+---------+
TEXT: Field defined already (<line> <column>): <name>
TYPE: Error
REASON: The internal screen definition code contains an
error. The field name noted has been defined
previously.
ACTION: If you are making screen modifications, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 070 |
+---------+
TEXT: Line number specification: <n> is invalid. The line
number must be a non-zero integer or screen midpoint
reference.
TYPE: Error
REASON: The internal screen definition code contains an
error. The specified line number is invalid.
ACTION: If you are making screen modifications, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 071 |
+---------+
TEXT: Attribute definition <name> is not recognized.
TYPE: Error
REASON: The internal screen definition code contains an
error.
ACTION: If you are making screen modifications, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 072 |
+---------+
TEXT: The screen support function <name> defined for
screen <name> was not found.
TYPE: Error
REASON: The internal screen definition code contains an
error. The screen field edit/action exec was not
found.
ACTION: If you are making screen modifications, correct the
error in your code. If this is an unmodified
screen, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 073 |
+---------+
TEXT: SYNTAX trap variable @TRAP=<n> which is not
recognized. Error originates in line <n>.
TYPE: Error causing immediate termination
REASON: This is an internal error.
ACTION: For assistance, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
+---------+
| 074 |
+---------+
TEXT: New password. Please re-enter the password for
verification.
TYPE: Information
REASON: The read password for the data disk is updated.
ACTION: Enter the password one more time.
+---------+
| 075 |
+---------+
TEXT: Invalid mode <x>.
TYPE: Error
REASON: The specified file mode is invalid.
ACTION: Provide a correct file mode.
+---------+
| 076 |
+---------+
TEXT: Invalid virtual address <cuu>.
TYPE: Error
REASON: The specified virtual address is invalid.
ACTION: Provide a correct virtual address.
+---------+
| 077 |
+---------+
TEXT: Error! RC=<rc> when attempting to link <userid>
<cuu> disk
TYPE: Error
REASON: A link attempt for the specified disk is failed.
ACTION: Review and correct the provided userid, disk
address, and read access password then retry the
command with the correct information.
+---------+
| 078 |
+---------+
TEXT: Invalid command <command>
TYPE: Error
REASON: The specified command is not recognized.
ACTION: Provide a correct command.
+---------+
| 079 |
+---------+
TEXT: Unauthorized user <userid>
TYPE: Error
REASON: The specified userid is not authorized to issue any
operational command to the VM Data Transfer Program.
ACTION: If <userid> is eligible to issue an operational
command to the VM Data Transfer Program, use PF key
4 to authorize <userid> from the Common Transfer
Parameters panel and reissue the command.
+---------+
| 080 |
+---------+
TEXT: Error! RC=<rc> when attempting to access disk <cuu>
TYPE: Error
REASON: The access attempt to the specified disk <cuu> is
failed.
ACTION: Correct the provided disk information and retry the
command.
+---------+
| 081 |
+---------+
TEXT: Invalid specification (<x>) for <var>. Must be
numeric.
TYPE: Error
REASON: The specified value <x> for <var> is incorrect.
ACTION: Provide a numeric value for <var>
+---------+
| 082 |
+---------+
TEXT: FILEDEF for xxxxxxxx ddname failed with RC=<rc>
(File: <id>)
TYPE: Error
REASON: FILEDEF command for the file <id> with the ddname
xxxxxxxx failed with return code <rc>
ACTION: Correct the error and retry the command.
+---------+
| 083 |
+---------+
TEXT: File <id> not found or incorrectly specified
Transmission of <datatype> data is skipped.
TYPE: Error
REASON: Invalid or missing file Id <id>.
ACTION: Correct the error and retry the command.
+---------+
| 101 |
+---------+
TEXT: The parameter <parm> was entered as <value>. The
correct values are: <list>
TYPE: Error
REASON: VMTGEN determined that a parameter was incorrectly
specified.
ACTION: Reissue the command with the correct parameter
value.
+---------+
| 102 |
+---------+
TEXT: The options list (source: <src>) contains too many
words: <list>
The correct form is OPTION (value)
TYPE: Error
REASON: VMTGEN determined that the option parameters were
incorrectly specified.
ACTION: Reissue the command with the correct parameter
value.
+---------+
| 103 |
+---------+
TEXT: File <name> was not found. RC=<rc>
TYPE: Error
REASON: The named file was not located.
ACTION: Determine why the named file does not exist, and
correct the condition. Reference CMS Command and
Macro Guide for STATE return codes.
+---------+
| 104 |
+---------+
TEXT: Assembling <name> ....
TYPE: Information
REASON: VMTASM is assembling the named file.
ACTION: None required.
+---------+
| 105 |
+---------+
TEXT: Error(s) updating library members. MACLIB <name>
not created/replaced
TYPE: Error
REASON: VMTMAC detected errors during macro library
maintenance.
ACTION: Resolve the errors indicated by the associated
messages and retry the command.
+---------+
| 106 |
+---------+
TEXT: ----> <name> has been <operated>.
TYPE: Information
REASON: The action to <name> completed successfully.
ACTION: None required.
+---------+
| 107 |
+---------+
TEXT: Member name not specified
TYPE: Error
REASON: The name of the macro or copybook was not specified
on the VMTMAC command when a single member operation
was requested.
ACTION: Reissue the command with the correct parameter
specification.
+---------+
| 108 |
+---------+
TEXT: ----> <member> not added to <name> MACLIB due to
error(s). RC=<rc>
TYPE: Error
REASON: An error was encountered while attempting to update
a member to be added/replaced in the named library.
ACTION: Correct the error and retry the command.
+---------+
| 109 |
+---------+
TEXT: Generation procedure completed successfully
TYPE: Information
REASON: The requested code generation was performed.
ACTION: None required.
+---------+
| 110 |
+---------+
TEXT: Generation procedure encountered errors, RESTART
required after error correction
TYPE: Error
REASON: The requested code generation failed due to errors.
ACTION: Correct the errors listed and restart the generation
process. See VMTGEN in Chapter 10 for restart
instructions.
+---------+
| 111 |
+---------+
TEXT: Unable to obtain the R/W filemode to generate <name>
TYPE: Error
REASON: The destination disk to store generated <name> is
accessed as read-only.
ACTION: Access the disk in R/W mode and then restart the
generation process.
+---------+
| 112 |
+---------+
TEXT: Library <name> is not on a write accessed minidisk.
TYPE: Error
REASON: The destination disk to store library <name> is not
accessed in R/W mode.
ACTION: Access the disk in R/W mode and then restart the
generation process.
+---------+
| 113 |
+---------+
TEXT: The free assembler was used during this assembly.
TYPE: Information
REASON: The IBM-provided free assembler was used to assemble
the CA MICS VM Data Transfer Program because the
high level assemble is not available.
ACTION: None
+---------+
| 114 |
+---------+
TEXT: Unable to access the following IBM macro libraries.
==> <name> ...
Contact your VM systems programmer for assistance.
TYPE: Error
REASON: The CA MICS VM Data Transfer Program generation
process requires access to the macro libraries
mentioned in the message text.
ACTION: Contact the VM systems programmer for the minidisk
where the macro libraries reside. Then access the
disk in R/O mode and then restart the generation
process.
+---------+
| 200 |
+---------+
TEXT: DUPLICATE PARAMETER: .........
TYPE: Error
REASON: A parameter was coded more than once on the VMTRDR
command.
ACTION: Reissue or recode the command with only one
occurrence of the parameter.
PROGRAM: VMTRDR
+---------+
| 201 |
+---------+
TEXT: UNRECOGNIZED PARAMETER: .........
TYPE: Error
REASON: A parameter was coded that is not valid for the
VMTRDR command.
ACTION: Reissue or recode the command with the correct
parameter.
PROGRAM: VMTRDR
+--------+
| 202 |
+--------+
TEXT: WRONG FILE SELECTED (....) EXPECTING (....)
TYPE: Terminal
REASON: An internal error occurred during the selection of a
spool file.
ACTION: For assistance, contact Technical Support at
http://ca.com/support, and provide the text of this
message.
PROGRAM: VMTRDR
+---------+
| 203 |
+---------+
TEXT: * nnnn fff
TYPE: Information
REASON: A reader file was selected by VMTRDR. The 'nnnn'
value is the spool file number and the 'fff' value
is either MON for a Monitor file or ACT for an
Account file.
ACTION: None required.
PROGRAM: VMTRDR
+---------+
| 204 |
+---------+
TEXT: UNRECOGNIZED OPERAND: ........
TYPE: Error
REASON: A parameter was coded with an invalid or
unrecognized operand.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTSEL
+---------+
| 205 |
+---------+
TEXT: MISSING DELIMITER: ........
TYPE: Error
REASON: A delimiter of "/" was expected but not found.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTSEL
+---------+
| 206 |
+---------+
TEXT: NON-NUMERIC FOUND: ........
TYPE: Error
REASON: A parameter was coded with a character value when a
numeric was expected.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTSEL
+--------+
| 207 |
+--------+
TEXT: INVALID DELIMITER FOUND: .....
TYPE: Error
REASON: A parameter was coded with an invalid or
unrecognized delimiter when a '/' was expected.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTSEL
+--------+
| 208 |
+--------+
TEXT: NON-MODIFIABLE TABLE ENTRY: ......
TYPE: Warning
REASON: An attempt was made to override a record selection
value for a prohibited record type.
ACTION: The program continues without honoring the request.
PROGRAM: VMTSEL
+--------+
| 209 |
+--------+
TEXT: NO INTERNAL TABLE ENTRY FOR: .....
TYPE: Warning
REASON: A record type was encountered for which the internal
record table contains no matching entry.
ACTION: The record type is ignored and processing continues.
Any records of this type encountered in the input
data are handled as UNKNOWN records. For
assistance, contact Technical Support at
http://ca.com/support, and provide the text of this
message and the accompanying record selection
report.
PROGRAM: VMTSEL
+--------+
| 210 |
+--------+
TEXT: ACCOUNT RECORD IDENTIFIER: ..... MUST BE ONE OR TWO
CHARACTERS LONG
TYPE: Error
REASON: A parameter was coded with an invalid or
unrecognized operand.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTSEL
+--------+
| 211 |
+--------+
TEXT: UNRECOGNIZED PARAMETER FOR "UNKNOWN": ........
TYPE: Error
REASON: The expected value of SELECT or EXCLUDE was not
found on the UNKNOWN parameter.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTSEL
+--------+
| 212 |
+--------+
TEXT: MISSING MONITOR DOMAIN OR CODE: ....
TYPE: Error
REASON: The Monitor record domain was not coded in the
record type.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTSEL
+--------+
| 213 |
+--------+
TEXT: UNRECOGNIZED RECORD: ........
TYPE: Warning
REASON: An input record of a type not in the internal record
types table was encountered.
ACTION: Processing continues; the record is handled as an
UNKNOWN record type. For assistance, contact
Technical Support at http://ca.com/support, and
provide the text of this message.
PROGRAM: VMTSEL, VMTXEL, VMTNSL
+--------+
| 214 |
+--------+
TEXT: CC(.) FROM DIAGNOSE 14 RX(...) RY(...) RY+1(...),
READER FILE(....) HELD
TYPE: Error
REASON: An error was encountered while attempting to access
a spool file.
ACTION: The spool file is held and error termination is
initiated. Contact Technical Support at
http://ca.com/support, and provide the text of this
message.
PROGRAM: VMTRDM, VMTRDA
+--------+
| 215 |
+--------+
TEXT: RDR1 (...) IS NOT DEFINED
TYPE: Error
REASON: A reader for CMS does not exist.
ACTION: Program error termination is initiated. Define a
reader at the address in the message text, or
contact your VM System Administrator for more
assistance. Restart VMTXMIT.
PROGRAM: VMTRDM, VMTRDA
+---------+
| 216 |
+---------+
TEXT: UNRECOGNIZED CCW: .................., TERMINATING
TYPE: Error
REASON: An unrecognized or unexpected CCW was encountered
while decoding a SPLINK.
ACTION: The spool file is held and error termination is
initiated. For assistance, contact Technical
Support at http://ca.com/support, and provide the
text of this message.
PROGRAM: VMTRDA
+---------+
| 217 |
+---------+
TEXT: <<<- THIS LINE (TEXT LENGTH + DISPLACEMENT) EXCEEDS
LINE LENGTH
TYPE: Warning
REASON: A formatted line was passed to VMTPRT, but the text
would not fit in the line.
ACTION: Processing continues. For assistance, contact
Technical Support at http://ca.com/support, and
provide the text of this message.
PROGRAM: VMTPRT
+---------+
| 218 |
+---------+
TEXT: NETSPY SUBTYPE TOO LONG: ......
TYPE: Error
REASON: The length of NETSPY record subtype given in the
network data select file was longer than expected.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTNSL
+---------+
| 219 |
+---------+
TEXT: MISSING SMF RECORD TYPE OR SUBTYPE: ........
TYPE: Error
REASON: An invalid parameter was coded in the network data
select file without specifying record type or
subtype.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTNSL
+---------+
| 220 |
+---------+
TEXT: UNDEFINED RECORD TYPE: ........
TYPE: Error
REASON: A parameter was coded with an unrecognized record
type in the network data select file.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTNSL
+---------+
| 221 |
+---------+
TEXT: INVALID SMF RECORD TYPE: ........
TYPE: Error
REASON: A record type was coded in the network select file
with a value larger than 255.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTNSL
+---------+
| 222 |
+---------+
TEXT: SYSID TOO LONG: ........ TRUNCATE TO 4 CHARACTERS
TYPE: Warning
REASON: System identification must be 1-4 characters. The
parameter coded at SYSID statement was too long.
ACTION: System identification is truncated. Processing
continues.
PROGRAM: VMTNSL
+---------+
| 223 |
+---------+
TEXT: NON-HEXADECIMAL NPM SUBTYPE: ........
TYPE: Error
REASON: A record subtype coded for NPM data selection or
exclusion had a nonhexadecimal value.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTNSL
+---------+
| 224 |
+---------+
TEXT: NON-ALPHANUMERIC NETSPY SUBTYPE: ........
TYPE: Error
REASON: A record subtype was coded for NETSPY data selection
or the exclusion was not alphanumeric.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTNSL
+---------+
| 225 |
+---------+
TEXT: NPM SUBTYPE TOO LONG: ........
TYPE: Error
REASON: A record subtype parameter for NPM data selection or
exclusion was specified longer than 2 bytes.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTNSL
+---------+
| 226 |
+---------+
TEXT: SYSTEM ID HAS BEEN DEFINED PREVIOUSLY
TYPE: Error
REASON: System identification parameter was defined more
than once.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTNSL
+---------+
| 227 |
+---------+
TEXT: INVALID OPTION SPECIFIED: ........
TYPE: Error
REASON: An invalid or unrecognized option was coded.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTNSL
+---------+
| 228 |
+---------+
TEXT: EXTRANEOUS PARAMETER(S) SPECIFIED: ........
TYPE: Error
REASON: Extraneous parameter(s) was coded in the data select
file.
ACTION: Correct the parameter and restart VMTXMIT.
PROGRAM: VMTNSL
+---------+
| 229 |
+---------+
TEXT: INPUT RECORD FORMAT IS NOT V.
TYPE: Error
REASON: The input file defined by the FILEDEF INPUT
statement in the NETDATA.INPUT routine of VMTFDEF
EXEC is not RECFM=V. All supported network data
records are variable length records.
ACTION: Correct VMTFDEF and restart VMTXMIT.
PROGRAM: VMTNSL
+---------+
| 231 |
+---------+
TEXT: ERROR ... ON FILE .................?
TYPE: Error
REASON: An FSREAD error was encountered on an input file.
ACTION: Correct the problem and restart VMTXMIT.
PROGRAM: VMTCNI
+---------+
| 232 |
+---------+
TEXT: NON-DISK FILES MAY NOT BE CONCATENATED
TYPE: Error
REASON: The concatenated files were not disk residents.
Nondisk files cannot be processed all together.
ACTION: Correct the problem and restart VMTXMIT.
PROGRAM: VMTCNI
+---------+
| 233 |
+---------+
TEXT: NO FILEDEF ISSUED FOR ......
TYPE: Error
REASON: CMS FILEDEF for a ddname was not found.
ACTION: Define the ddname in VMTFDEF and restart VMTXMIT.
PROGRAM: VMTCNI
+---------+
| 234 |
+---------+
TEXT: INCONSISTENT RECORD FORMATS FOR CONCATENATED FILES
TYPE: Error
REASON: The concatenated files were with a different record
format.
ACTION: Check the record formats of those files and ensure
that they are the same. Then restart VMTXMIT.
PROGRAM: VMTCNI
+---------+
| 235 |
+---------+
TEXT: INCONSISTENT RECORD LENGTHS FOR FIXED FORMAT FILES
TYPE: Error
REASON: The concatenated files were in fixed format but with
different record length.
ACTION: Check the record format and record length of the
concatenated files.
PROGRAM: VMTCNI
+---------+
| 236 |
+---------+
TEXT: FIRST RECORD IS NOT CONFIGURATION RECORD: ......
TYPE: Warning
REASON: The VM monitor data violates IBM standards and does
not have configuration records in the beginning.
ACTION: Check with your VM Systems Programmer. Although the
process continues, the CA MICS VM and CMS Analyzer
may abend with U997 if the first set of monitor data
processed for the system does not start with
configuration records.
PROGRAM: VMTXEL
+---------+
| 301 |
+---------+
TEXT: RECORD nnnnnnnn: INVALID DATA PAGE
TYPE: Warning
REASON: A 4k block of binary zeros was encountered while
reading VM monitor data pages.
ACTION: The record is discarded. Processing continues.
PROGRAM: VMTMWI
+---------+
| 302 |
+---------+
TEXT: RECORD nnnnnnnn: UNEXPECTED NON-CONTROL RECORD
TYPE: Warning
REASON: A non-control record was encountered while a control
record is expected.
ACTION: The record is discarded. Processing continues.
PROGRAM: VMTMWI
+---------+
| 303 |
+---------+
TEXT: RECORD nnnnnnnn: UNEXPECTED CONTROL RECORD
ENCOUNTERED (SHORT DATA)
TYPE: Warning
REASON: An unexpected control record was encountered while
reading data pages.
ACTION: Processing continues. Users should check the reason
why the data pages were short.
PROGRAM: VMTMWI
+---------+
| 304 |
+---------+
TEXT: RECORD nnnnnnnn: INVALID CONTROL AREA ENTRY (TRGCLS
= xx)
TYPE: Warning
REASON: The control area at the control record (record
nnnnnnnn) contains an invalid entry. Possibly, in
the control area entry, the end address for the
monitor records is not higher than the start
address.
ACTION: Discard the control record and the associated data
pages. Processing continues.
PROGRAM: VMTMWI
+---------+
| 305 |
+---------+
TEXT: RECORD nnnnnnnn: COL cccc -- INVALID RDW xxxxx
DETECTED
TYPE: Error
REASON: The record nnnnnnnn consists of an invalid record
descriptor word at the column cccc.
ACTION: Program abends with code 997. For assistance,
contact Technical Support at http://ca.com/support,
and provide the text of this message.
PROGRAM: VMTMWI
+---------+
| 500 |
+---------+
TEXT: VM DATA TRANSFER PROGRAM
SOURCE CODE TRANSMISSION
TYPE: Information
REASON: The source code transmission to a VM system from
MVS was initiated.
ACTION: None required.
REFERENCE: VMTXRDR
+---------+
| 501 |
+---------+
TEXT: PROCESSING DDNAME xxxxxxxx
TYPE: Information
REASON: Source code transfer from the named DD was started
or continued.
ACTION: None required.
REFERENCE: VMTXRDR
+---------+
| 502 |
+---------+
TEXT: FILETYPE: xxxxxxxx
TYPE: Information
REASON: The source code transmission process is assigning
the indicated CMS file type to the transmitted
source files.
ACTION: None required.
REFERENCE: VMTXRDR
+---------+
| 503 |
+---------+
TEXT: MEMBER : xxxxxxxx RECORDS: nnnn
TYPE: Information
REASON: The source code transmission process is sending
the named member that has the indicated number of
records to CMS. The member has the CMS file
identifier of <member> <filetype>.
ACTION: None required.
REFERENCE: VMTXRDR
+---------+
| 504 |
+---------+
TEXT: MEMBER : xxxxxxxx =ERR=> NOT FOUND
TYPE: Error
REASON: The named member was not found. The library that
was searched for this member is indicated on the
preceding VMT00501I message.
ACTION: For assistance, contact Technical Support at
http://ca.com/support, and provide the text of
this message.
REFERENCE: VMTXRDR
+---------+
| 505 |
+---------+
TEXT: MEMBER : xxxxxxxx =***=> SUPPRESSED DUE TO
PREVIOUS ERROR
TYPE: Information
REASON: The named member was found by VMTXRDR but
transmission to CMS was inhibited by previous
error(s).
ACTION: None required.
REFERENCE: VMTXRDR
+---------+
| 506 |
+---------+
TEXT: PROCESS xxxxxxxx HAS COMPLETED WITH A HIGH
CONDITION CODE OF nnn.
TYPE: Information
REASON: The named process has finished with a maximum
return code indicated in the message.
ACTION: None required.
REFERENCE: VMTXRDR
+---------+
| 507 |
+---------+
TEXT: TRANSMISSION OF SOURCE HAS BEEN SUPPRESSED DUE TO
ERRORS.
TYPE: Information
REASON: The source code transmission process encountered
errors during the member collection process. See
the preceding VMT00504E message(s) for more
information.
ACTION: None required.
REFERENCE: VMTXRDR
+---------+
| 508 |
+---------+
TEXT: nnn MEMBERS (mmmmm LINES) HAVE BEEN PREPARED FOR
TRANSMISSION.
TYPE: Information
REASON: The source code transmission member collection
process completed successfully and the indicated
number of members and lines will subsequently be
written to the CMSRDR ddname. The number of lines
in this message equals the sum of the records in
the preceding VMT00503I messages and the number of
members being sent.
ACTION: None required.
REFERENCE: VMTXRDR
