MVT/VSE

Release 9.5
Messages and Codes

Copyright © 2001 by Software Pursuits, Inc.
All Rights Reserved.

Except as noted below, no part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise without the prior written permission of Software Pursuits, Inc.

Table of Contents


Introduction

This publication applies to the Software Pursuits, Inc. program product MVT/VSE, Release 9.5, program product number 1975-MVT.

Message Format

All messages, unless otherwise specified, are in the format:
MVTnnnt message...
Where:
MVT
Indicates an MVT/VSE message.
nnn
The MVT/VSE assigned number for a give message.
t
Indicates the type of message being issued.
A
An action message. Some type of action is required for processing to continue. The actual action(s) required will depend on the program processing and the activity being performed.

C
A cancellation message. A severe error has occurred that caused processing to be canceled.
D
A decision is required. Some type of decision is required that will require a response to the message.
I
An informational message. Action is not generally required.
E
A severe error message. Some type of action is required to complete the processing.
W
A warning message. A moderately severe error has occurred that may or may not require action.
message
The message text.

0xx Messages  [TOP]

MVT002D INVALID JOB NAME
The Job Name on a JOB statement was:
  1. Omitted
  2. Longer than eight (8) characters
  3. Rejected by the $JOBEDIT user routine.
A new JOB statement must be entered with a valid Job Name.
MVT003D ACCOUNT FIELD INVALID
The account field on the JOB statement was rejected by the $JOBEDIT user routine. A new JOB statement must be entered with a valid accounting field.
MVT004D INVALID GETVIS SPECIFICATION
The GETVIS parameter on either the EXEC, JOB, or DEFINE statement contains an illegal value. The statement must be reentered. The value must be coded as nk and is added to the region size specification for the total memory size for execution. The value is always rounded up to a multiple of 2k. If no GETVIS size is specified a default will be taken.
MVT005D INVALID PPOOL SPECIFICATION
The private page pool (PPOOL) parameter on either the EXEC, JOB, or DEFINE statement contains an illegal value. The statement must be reentered. The value must be coded as nK. The value is always rounded up to a multiple of 2K. There is no default value if the parameter is not specified.
MVT006D INVALID REGION SPECIFICATION
The REGION parameter on either the EXEC, JOB, or DEFINE statement contains an illegal value. The statement must be reentered. Please review the procedures for coding this parameter elsewhere in this manual. Remember two size parameters may be coded and each may be in the form: AUTO, xK, or AUTO+xK. For example:

REGION=(AUTO+40K,100K); REGION=AUTO+200

MVT007D INVALID TIME SPECIFICATION
The TIME field on a JOB or EXEC statement contained a non-numeric value. The statement must be reentered. The TIME field indicates minutes and seconds: TIME=(5,30) for five minutes and thirty seconds; or TIME=(,30) for thirty seconds only; or TIME=3 for three minutes; or TIME=NO to suppress timer use.
MVT008D INVALID LOAD SPECIFICATION
The LOAD operand may contain the value HI, LOW, or nK. If HI or LOW are specified, the words may be abbreviated to as few as a single character. If nK is specified, the number must be a multiple of 2K. All other values are invalid.
MVT009D TOO MANY PCIL'S DEFINED
A DEFINE command was entered trying to define a new Private Core Image Library and the maximum number of libraries which can be defined was exceeded. The define statement is ignored. To permit the DEFINE command to function, increase the operand PCIL= in your Nucleus. The command will also be permitted if other defines in other regions are removed. The maximum number of PCIL's active at any time is specified in the nucleus.
MVT010D INVALID PROGRAM NAME
The program name on an EXEC statement was longer than eight characters. The entire statement must be reentered.
MVT011D INVALID COMRG40 SPECIFICATION
The COMRG40 value coded is illegal. The operand value must be in the same form as found in a REGION operand. Enter a number or AUTO plus a number. The number may be expressed in K.
MVT012C REGION REQUESTED TOO LARGE FOR CPU
A program being executed requested more memory than is available in the CPU, excluding the nucleus. The Job is canceled since it is impossible to load the program into memory. Perhaps the region assumed is larger than desired. Review the REGION parameter on the EXEC statement, JOB statement, and the default region size. Perhaps the Job could be run if one of these values were altered.
MVT013I REGION TOO SMALL - AUTO ASSUMED
The region size which would normally be used to load the program was too small to hold the size of the program. The region specification is automatically increased to the size of the program. The REGION parameter on the EXEC or JOB statement should be altered in future runs to avoid this error message.
MVT014I nnnK REGION REQUESTED PROGRAM FOUND IN location
'location' may be:
  1. SYSRES hh.mm.ss
  2. SYSCLB=n ON cuu, CIL STARTS AT nnn hh.mm.ss
This message is issued on SYSLST for information purposes only. The size of the maximum region requested is indicated. NOTE: This may not be the actual size of the region allocated if two operands were coded; an amount less than the optimum (the number reported) may actually be allocated. The library which was used to fetch the program is also identified. If the library was a private library, the library number is shown as if a DEFINE SYSCLB=n statement was specified. 'CIL STARTS AT nnn' indicates the starting cylinder address of the private Core Image library used. The time of day that the EXEC statement was processed is also shown.
MVT015D PARM VALUE TOO LONG
The PARM field on the EXEC statement was longer than the maximum length specified at SYSGEN time. Attempt to code the PARM field with fewer characters or request a new nucleus which will allow a longer PARM value.
MVT016D INVALID FIELD NAME
The first parameter specified in an AIF or PIF statement is invalid or not defined. Check for misspelling or an improper subscript value. CANCELCD is not valid unless Job Accounting support was generated in your nucleus.
MVT017D INVALID COMPARE CONDITION
The second parameter in an AIF or PIF statement contains a compare condition which is not defined. Check for possible spelling errors or for an omitted compare condition.
MVT018D INVALID VALUE FOR COMPARE
The value specified in an AIF or PIF statement is improperly specified for the type of compare operation or contains a syntax error. Compare conditions which start with a 'B' require a one byte hex value specified by two hex digits. All values must be enclosed in single quotes.
MVT019D INVALID BRANCH NAME
The sequence symbol specified as a branch name in an AGO, PGO, AIF, or PIF statement is invalid. A sequence symbol must start with a period and have a total length of no more than eight characters.
MVT020D TOO MANY CONTROL UNITS
This message may be issued during an IPL or after a VARY command. It indicates that more control units are needed than are supported by the current nucleus. A new nucleus should be created to increase the number of control units supported. A VARY command is rejected and should be reentered to define the original configuration. At IPL, the IPL cannot be completed until control units are deleted from the system. Control units are defined as the first two digits of any physical device address, thus adding additional channel paths to a controller also counts as adding a control unit.
MVT021D DUPLICATE cuu
This message is issued during an IPL or after a VARY command. It indicates that the device in question is defined to the system more than one time. This is generally due to the use of multiple channel paths where the controllers have the same address. This message would be issued if 130 was on channels 1 and 2 and if 230 also was defined in the system. The VARY command is rejected and should be reentered to define a configuration with no conflict. IPL cannot be performed if this condition exists, devices in conflict must be deleted. Hardware truly cabled in this fashion will not function properly and must be recabled to avoid any addressing conflicts.
MVT022D INVALID HEX DATA VALUE
The hex value specified in a MVCOM, AIF, or PIF statement is invalid. Only an even number of digits 0-9, A-F may be specified.
MVT023C TOO MANY VARIABLE SYMBOLS
Too many variable symbols have been defined within a PROC. The Job is canceled. Either some variable symbols must be deleted from the PROC or the JCLSIZE= specification in the nucleus must be increased.
MVT024C SPRI IS INACTIVE
This message is issued if a // PROC statement is processed when SPRI is not active. // PROC statements are valid when SPRI is inactive only if they contain the SPOOLOUT=NO operand.
MVT025I READY 'cuu' & REPLY 'CANCEL/RETRY/IGNORE/EOB'
This message is in response to an intervention on the indicated tape drive. A reply of CANCEL, RETRY or EOB will cause the operation to be retried. A reply of CANCEL will cancel the job using this drive. Any reply other than those indicated are ignored and this message will be issued again.
MVT030D RE-ENTER CANCEL TO CANCEL 'JOB ACCT', ELSE EOB
This message is issued from the Attention Routine (AR) when a cancel command has been issued for a region where Job Accounting routines ($JOBACCT or $JOBEDIT) are active. Normally it is not desired to cancel these routines since all Job Accounting information from that point would be lost until the next IPL. This message is used to verify the desire of the operator to turn off Job Accounting in the system. The words 'JOB ACCT' in the message may be replaced with 'JOB EDIT' if the $JOBEDIT routine is active. If a second cancel command is issued immediately following this message, the cancel will take place regardless of whether $JOBEDIT or $JOBACCT are running. If it is not desired to deactivate Job Accounting, EOB the reply to the message. If it is still desired to cancel the Job in question, depress the Request Key and reenter the command. The accounting routine should have completed its processing by this time.
MVT031I NO ACTIVE TASKS
This information message is issued in response to a DISPLAY command in the Attention Routine (AR). The message indicates that no tasks are active in the entire system if a DISPLAY ALL command was used; or that the specific task requested was not active, for example, DISPLAY R5.
MVT032D DUPLICATE NAMES
A cancel command has been entered to the Attention Routine (AR) and the task/region name is not unique. Re-enter the command with a name unique to the region or task. Jobs may be canceled by Job Name or Region ID (R4, RA, etc.). Subtasks may be canceled by subtask name or Task ID (TC, T9, etc.).
MVT033C BLKSIZE TOO LARGE FOR DEVICE filename
During the OPEN of the data set indicated by 'filename', it was determined that the block size specified in the DTF or on the DLBL statement exceeds the track capacity of the disk device being used. The device independent routines cannot resolve the conflict and cancel the job.
MVT034D/W REGION SIZE LARGER THAN MAXREAL SPECIFICATION
The region size specified for the current program, which was requested to run in real memory, exceeds the MAXREAL= operand specification of the DEFINE statement. The region size may be a default or may have actually have been specified on the EXEC statement. If running in a virtual environment, the mode automatically changes to virtual and no reply is required. In a real memory system or under VM, the EXEC statement is rejected. To allow the program to run, enter a DEFINE statement specifying a MAXREAL= operand of sufficient size to allow the program to run in real memory.
MVT035W INSUFFICIENT STORAGE IN SVA TO LOAD phasename
An attempt was made to load a phase into the SVA to be used in either move mode or as a reentrant program. The SVA does not contain enough extra memory to load the new version of the phase and the request is ignored. The request may be the result of cataloging a new version of a program in the SVA or as a result of using the SET SDL JCL statement. Extra memory for SVA loading may be specified on the SVA IPL statement with the PSIZE= operand. No extra memory can be made available in the SVA until the next IPL.
MVT036W Rx HAS BEEN DE/RE-ACTIVATED
The region indicated has been deactivated or reactivated by the page load leveler routine. Regions are deactivated automatically when the paging rate becomes too high. The task selected for deactivation is the region with the largest number of active pages within the lowest priority group. Regions are reactivated in priority sequence, highest priority first. Reactivation occurs automatically when the page load is lowered. Task deactivation and reactivation can be performed manually with the attention routine (AR) STOP and START commands.
MVT037C $JOBCTLB GETVIS IN SVA FAILED CANNOT RESTART CHECKPOINT JOB.
This message is issued when attempting to restart a job with the JCL RSTRT statement. In order to perform the restart function a small amount of system GETVIS area is required. This message is issued when that memory is unavailable. The SVA GETVIS memory can be made available by terminating SDAIDS, if active, or by specifying a little more memory with the GETVIS= operand on the SVA IPL statement, then performing an IPL.
MVT038W DIOPEN FAILURE failure-type
While attempting to perform a device independent open for a disk data set an error occurred and the device independence support was not completed. The failure types are:
  1. INSUFFICIENT GETVIS
  2. AVR FAILURE. RC=xx
  3. NO LABEL INFORMATION. RC=xx
This message is normally followed by another message indicating that the open has failed. If the problem is insufficient GETVIS, rerun the program with 4K additional GETVIS area (use the GETVIS operand on the EXEC statement). RC=xx refers to return codes passed by AVR and label access macros.
MVT041W $NZAPLOG VERSION DOES NOT MATCH $NLOWC
The release level of the zap logging module $NZAPLOG loaded during IPL does not match the release level of the MVT/VSE system being IPL'd. No response is required and the IPL continues normally. The contents of the module are ignored and consequently information about zaps applied to the system is not available.
MVT051C EQU TABLE OVERFLOW
Too many EQU table entries have been submitted via EQU JCL statements. The Job is canceled. Before resubmitting the Job, review EQU usage so fewer equates might be used. The maximum number of equates per region is determined when the nucleus is compiled. Check the supervisor generation options or with your systems programming staff to determine the maximum number of device equates allowed in your installation. The EQU SHOW statement can be used to verify current EQU usage.
MVT052C JOB jobname CANCELED DUE TO PHASE LOADED OUTSIDE OF REGION
This message is issued when a phase load is attempted outside the boundaries of the region. This condition is usually caused by loading an overlay where the region size is not large enough to hold the overlay phase. The solution for this problem is to increase the region size requested on the EXEC statement.

Another cause for this cancellation would be the attempted load of a program which was link edited to a fixed address and is not a self-relocating program and was not linked with ACTION RELO. The only solution is to properly re-link the program with MVT/VSE since the location of a region is nearly impossible to predict.

MVT053C JOB jobname CANCELED DUE TO TOO MANY RCBS ENQUED
This message indicates that all the resource control blocks in the system have been used and a request was made for more. A resource control block (RCB) is required for each outstanding ENQ and STXIT IT timer interval, while two RCB's are required for each stacked fetch (a MVT/VSE special feature) and for each SETIME timer set where a TECB was specified. If more RCB's are required by your system, a new Nucleus will be required.
MVT054I PSW-psw, REGION START-ssssss, LBLTYP-type,
RELATIVE ADDR-
aaaaaa
This message appears on SYSLST after most Job cancellations. The message provides information related to the cancellation in case no memory dump is obtained. The fields are mostly self-explanatory. The Relative Address is the displacement into the region of the instruction which caused the interruption.
MVT055D INVALID DEVICE TYPE
A VARY command has been entered with the DUAL= operand and the device type is not a disk; or with the VENDOR= operand and the device type is not a disk; or with the SHARE= operand and the device type is not a disk or tape device. Re-enter the command specifying the correct device cuu.
MVT058W MVT/VSE JA NOT ACTIVE
The OPERATOR command was entered through the Attention Routine (AR) but the MVT/VSE Job Accounting Routines are not active. Job Accounting is not activated until the first program is executed after an IPL. It can be reactivated with the SET JA=ON command at any time. The OPER command is ignored.
MVT059D MOUNT ON SYSxxx=X'cuu',[PERM | TEMP],VOL=volid,DSN=dsn
This message is issued after an AVR assignment to a volume serial number or an AVR assignment for a tape data set name. The drive indicated has been selected and the assignment has been completed. If you wish to keep the assignment made, simply press EOB/END to continue or enter any JCL statement you desire. If you wish to change the assignment, a new ASSGN statement must be entered. To retry the original AVR assignment, enter the word 'RETRY'. A new mount message may result or the volume desired might be found. If the volume is found, an additional console read will be performed without any more messages; press EOB/END to continue.
MVT061D SYSxxx=cuu,VOL=volid,DSN=dsn. DUPLICATES ON cuu cuu
An AVR assignment to a volume serial number or to a tape data set name was processed and more than one volume matched the selection criteria. The assignment was made to the device indicated. If that is the desired device, no further action is required. If a different device is desired, a new assignment must be entered. Enter 'RETRY' to retry the original ASSGN statement, but it will only produce a different result if one of the duplicate devices are taken out of ready.
MVT062D VENDOR NOT SUPPORTED IN THIS NUCLEUS
A VARY command with the VENDOR operand specified a vendor which cannot be processed by the current nucleus. The command is rejected. Re-enter the command with the correct vendor name or obtain a new nucleus which supports the vendor desired.
MVT063I PATH VARIED OFFLINE
This message only follows a Device Not Operable message. If an I/O operation is attempted on a device with multiple channel paths and a channel path is found not to be functional, that channel path to the device is no longer used. This message indicates that the channel path indicated in the previous message was turned off. The channel path may only be re-activated with a system IPL.
MVT064I SHARE ATTRIBUTE REMOVED
This message will only appear after a command reject message for a device. The SHARE attribute had been specified for the device but the device was not capable of processing the device reserve CCW command. No action is necessary. The improper specification is reset. Review your SYSGEN specifications to avoid future messages.
MVT065W type INTERRUPT LOST FROM cuu
Where 'type' may be:
  1. CUE
  2. DE
  3. CE
  4. CAI

This message is issued when the missing interrupt handler detects that an I/O operation has taken too long to complete. Generally, more than 30 seconds must elapse before this message is issued. The cause of the error is generally hardware, which normally has lost the interrupt. When using the stand-alone dump facility, these messages may appear upon restart, however no error is indicated. In any event, the missing interrupt is simulated by the system in an attempt to recover from the problem and restart the system.

A missing CUE interrupt (control unit end) indicates that a control unit responded to a Start I/O (SIO) command with a control unit busy status. The system is waiting for a control unit end interrupt to signal that the control unit is again available. This missing interrupt may be caused by not having the proper number of devices defined for the control unit (i.e., the controller will support 16 devices and only 8 devices are defined).

A missing CE interrupt (channel end) is very rare an indicates that a good start I/O command was issued, but no interrupt was ever presented to the system for the device.

A data check error is simulated for missing channel end interrupts.

A missing DE interrupt (device end) is the most common and indicates that a channel end interrupt has been received, but the device end was not. This generally occurs on disk devices on a seek command where the device fails to generate an interrupt when the arm motion completes.

A missing CAI interrupt (channel available interrupt) indicates that I/O has been ready to start but has not yet been started for some reason, generally a channel busy condition.

MVT066I OPTION=SHRCUE SET
This message is produced after the first 'CUE INTERRUPT LOST' message for a control unit. The message indicates that the SHRCUE option has been automatically set for the control unit in an attempt to eliminate any more missing CUE interrupts. The SHRCUE option is needed for any control unit which can access more than 16 device addresses or where the control unit is simulated by another control unit. There is no harm in specifying SHRCUE when it is not needed, only a very slight degradation in channel scheduling performance.
MVT067W EXCESSIVE BUSY ON cuu
This message is produced after a device has remained busy and unavailable for a start I/O for more than 3 minutes. This message can also be produced if the channel end interrupt for a device takes more than 3 minutes before it is received. No action is taken for the device. This message is simply a warning that the device is either reserved to another CPU or that the device is 'hung' in some sort of busy condition. The busy condition must be cleared before I/O can be started on the device.
MVT069W task HAS BEEN WAITING nn MINUTE(S) FOR resource
This message is issued from the MVT/VSE WATCHDOG facility. It indicates that a task has been waiting for the indicated resource for the specified time interval. The resources which may be indicated are:
  1. AVR
  2. CHANNEL QUEUE
  3. COPY BLOCKS
  4. DIRECTORY FETCH
  5. FETCH
  6. IDRA
  7. LOCK
  8. LOCK MANAGER
  9. LTA
  10. PAGE FRAMES
  11. PAGE IN
  12. PAGE MANAGER
  13. PAGING IO
  14. REACTIVATION
  15. SEIZE REQUESTER
  16. SPRI SERVICE
  17. TERMINATOR
  18. VIRTUAL STORAGE
The message is an indication of a failure of the task to obtain a needed resource in a timely manner. This is an indication of possible problems with any of the item indicated. If this message occurs frequently, you should inform your system programmer of the situation so that some type of action may be taken.
MVT070D STOP OF SEIZING REGION NOT ALLOWED
This message is issued when an attempt is made to stop a region when a task within the region has seized the system. The STOP command is not allowed. The operator should reply to the message with an End-of block or another AR command.
MVT095I cuu NOT SPOOLED - SET UA
This message is issued only when the SPRI spooling system is not active. If Job Control attempts to read on a pseudo device not under the control of SPRI, cuu will be the pseudo reader address. If Job Control attempts to print on a pseudo device not under the control of SPRI, cuu will be a printer address. Either SYSRDR or SYSLST for the region will be set UA.
MVT096C NO TEST CORE-IMAGE LIBRARY DEFINED
An attempt has been made to execute LNKEDT without a Test Core Image Library present. To prevent the possibility of accidentally cataloguing a test program into production, the catalogue is rejected and the Job is canceled. Re-submit the Job when a Test Core Image Library can be properly defined for the catalogue.
MVT097C ERROR ON SOURCE STMT LIBRARY
A bad block of text was encountered in the Source Statement Library. The library had been destroyed prior to the execution of the program which issued this message. It is possible that only a few specific books in the library are unusable. Restore the library and rerun the Job. The Job is canceled.

1xx Messages  [TOP]

MVT125I nn DAYS UNTIL SYSTEM EXPIRATION
This message informs the operator how many days remain before the system expires and will no longer function. This message will only appear if thirty or fewer days remain. The message is issued after any SET DATE or SET SYSDATE command. If you have not received your expiration update, contact Software Pursuits immediately by phone. If you have received the update it should be applied as soon as possible. When the expiration date is reached, message MVT126I or MVT327A is issued.
MVT126I BEYOND SYSTEM EXPIRATION - DATE SET TO ZEROES
This message is issued after any attempt to enter a SET DATE or SET SYSDATE command beyond the system expiration date. The command should be reentered with a valid date. If dates are needed into the future, use // DATE statements in those Jobs.
MVT127I AUTOMATIC DATE UPDATE TO mm/dd/yy COMPLETED.
This message will only appear if DATEUPD=YES was specified at Nucleus assembly time. The message appears after the clock passes 2400 hours. The time of day is adjusted for a new day and the system date is incremented. The COMREG date for each region will be updated unless a //ADATE statement is present for that Job. The system date for each region is always updated to reflect the current system date. The date update routine considers year updates and leap year.

2xx Messages  [TOP]

MVT202I INVALID STATEMENT SYNTAX
The control statement contains a verb or operand which cannot be recognized. The control statement is ignored.
MVT220I s.name DELETED
The phase, relocatable module, or source book named has been successfully deleted by MAINT. The name of each item deleted is always listed since percent signs (%) may be used in the original names to automatically delete several entries.
MVT221I s.name COPIED
The phase, relocatable module, or source book named has been successfully copied by CORGZ. The name of each entry copied is always listed since percent signs (%) may be used in the original names to automatically copy several entries.
MVT222I SYSRES AND NEWRES UNLIKE DEVICE TYPES LABEL TRACKS WILL NOT BE COPIED
CORGZ is building a new SYSRES on SYS002 as requested by an ALLOC control statement but cannot copy the label tracks from the current SYSRES to the new SYSRES because they are different disk device types. Building of the new SYSRES pack will continue, however no label information will be copied to the new SYSRES label cylinder tracks.
MVT224I OPTION option OBSOLETE, STMT IGNORED.
An OPTION JCL statement contained an option other than RERUN or NORERUN. No other options are allowed. Correct the OPTION statement and rerun the job.
MVT225I MODULE MVTLBDFC NOT LOADED IN THE SVA, V1 STATEMENT CONVERSION BYPASSED.
A LIBDEF, LIBLIST or LIBLIST statement was being processed and the Version 1 Librarian conversion module (MVTLBDFC) was not present in the SVA. The statement is processed without conversion by Job Control. Module MVTLBDFC is part of the MVT/VSE 9.5 system and should be loaded in the SVA on Version 2 Librarian systems. This module should be in library IJSYSRS.SYSLIB. Move MVTLBDFC.PHASE to this library and issue a SET SDL for MVTLBDFC,SVA or IPL the system to correct the problem.
MVT226D/I SYSTEM ERROR DETECTED IN MODULE MVTLBDFC, V1 STATEMENT CONVERSION FAILED.
A Version 1 librarian LIBDEF, LIBLIST, or LIBDROP statement was being processed and the statement conversion module encountered a system error. The statement is not processed. For type code I the job is canceled, for type code D the system waits for an operator response. This error is caused by insufficient JCL GETVIS space. Increase the JCL GETVIS allocation to correct the problem.
MVT227I OPTION LINK MUST PRECEDE GO PARAMETER
The GO parameter was coded on an EXEC statement without a preceding OPTION LINK statement in the JCL. Insert the statement in the JCL and re-run the job.
MVT228I LINK OPTION NOT ALLOWED WITH LABEL INFORMATION OPTIONS, LINK OPTION RESET.
The LINK parameter in the OPTION statement cannot be included on an OPTION statement which specifies any of the label information options (i.e., PARSTD or STDLABEL). The LINK does not take effect. All other valid options are processed normally.
MVT229I VSAM NOT ALLOWED WITH REGION LABELS=YES.
Filename IJSYSLN (SYSLNK) cannot be a VSAM file when the nucleus option REGNLBL=YES is specified. VSAM catalog management does not function correctly unless the file name opened for SYSLNK is IJSYSLN. The REGNLABL option changes IJSYS file names to RnSYS file names. Change the REGNLBL parameter in the NUCOPTN3 macro to NO for VSAM work file support.
MVT230I SYS005=SYSRES, RESTORE OF SYSRES BYPASSED
An attempt was made to restore to the SYSRES currently in use. This cannot be permitted since there would be no recovery if any type of error occurred or if a fetch was attempted during the restore of SYSRES. Restore to another volume or restore in stand-alone mode.
MVT250C MVTACCT FILE NOT FORMATTED
This message is issued after an attempt to use the MVT/VSE Job Accounting file for the first time after an IPL. The routine has determined that the data set has never been formatted. Job Accounting is turned off until the next IPL or until a SET JA=ON command is entered in a region. To create the MVTACCT data set, run the program MVTACCTF. This message is only issued if you are using the MVT/VSE accounting routines.
MVT251W MVTACCT FILE IS FULL
This message is issued when no more Job Accounting records can be logged into the MVT/VSE Job Accounting disk file. The MVTACCTB program should be run immediately. Until this program is run, all accounting information will be lost.

This message is only issued if you are using the MVT/VSE accounting routines.

MVT252W MVTACCT FILE IS nn% FULL
This warning message is issued after the MVTACCT file becomes at least 80% full. The MVTACCTB program should be run as soon as can be scheduled. Once the data set becomes completely full, Accounting information will be lost. This warning will be reissued each time a new track is used on the accounting data set until the backup program is run. This message is only issued if you are using the MVT/VSE accounting routines.

3xx Messages  [TOP]

MVT302D PROCEDURE s.procname NOT FOUND
This message indicates the requested procedure could not be found. Check the name of the procedure indicated. One of the following may apply:
  1. The sub-library specified is incorrect,
  2. The name of the procedure is misspelled,
Correct the problem and resubmit the job.
MVT303W INSUFFICIENT REAL MEMORY FOR IPL
During an IPL of the MVT/VSE system, it was determined that the nucleus and IPL routines would not fit in the available real memory in the CPU. Check to be sure that some of your CPU storage is not off-line, otherwise MVT/VSE will not be able to function on this CPU. Generally, MVT/VSE should not be used on CPU's with less than 512K of real memory.
MVT303W INSUFFICIENT REAL MEMORY FOR IPL
During an IPL of the MVT/VSE system, it was determined that the nucleus and IPL routines would not fit in the available real memory in the CPU. Check to be sure that some of your CPU storage is not off-line, otherwise MVT/VSE will not be able to function on this CPU. Generally, MVT/VSE should not be used on CPU's with less than 512K of real memory.
MVT304A ENTER MVT/VSE IPL STATEMENT
The MVT/VSE system is being IPL'd manually, without the auto IPL facility and this message indicates that the IPL statements should now be entered through the console. The IPL PROC and INPUT statements can be used to obtain IPL statements from other devices.
MVT305W PHASE phasename NOT FOUND
The named phase was not found in the system Core Image library during the IPL process. If the named phase is required the IPL will be terminated. If the phase is optional, the use of the phase will be bypassed and the IPL will continue. Optional phases are generally user SVC routines.
MVT306D SYS NUMBER TOO HIGH
The SYS number specified on an IPL ASSGN statement is to high for the region specified. The ASSGN statement is ignored. If you need this SYS number you must reassemble your nucleus options phase changing the LUBS= operand.

When ALL is specified instead of a region name on an ASSGN statement, the error is ignored in those regions which do not support the SYS number and warning messages are issued later in the IPL.

MVT307C IPL ABORTED
A serious error has occurred, as explained by a prior message. It is not possible for the IPL process to continue and the system has been placed in a hard wait. Perhaps some option or IPL statement was responsible for the error and can be circumvented and would allow a reIPL. Remember that a manual IPL can be forced by using the external interrupt key during the beginning of the IPL process.
MVT308I phase LOADED FROM cuu (volid) ON CPU=cc cccccc cccc cccc
This message is issued when the nucleus options phase is loaded and indicates the name of the phase loaded, the cuu device address and volume serial number of the SYSRES device, and the CPU Id of the CPU IPL'd. The nucleus options phase name is specified on the NUCLEUS IPL statement and defaults to NUCLEUSA if not specified.
MVT309W PERM I/O ERROR ON X'cuu'
An unrecoverable I/O error has occurred on the indicated device. If the I/O was critical to the IPL process, the system will be placed in a hard wait. The error condition should be corrected before another IPL is attempted.
MVT310D PHASE phasename DOES NOT CONTAIN NUCLEUS OPTIONS.
The named phase was specified in a NUCLEUS IPL statement, but it does not contain valid nucleus options. Check to be sure the nucleus options phase has been assembled without error and is the proper (current) release level. The NUCLEUS statement has been rejected and another nucleus options phase should be specified.
MVT311A STOP. ENTER MVT/VSE IPL STATEMENT
This message is produced as a result of the STOP IPL statement which requested a stop after the statement just listed. The statement listed has already been processed and this prompting is occurring after that statement. The read from the console allows the operator to enter any desired IPL statements. An EOB/ENTER response resumes the original input stream with the next statement. The stop function is not reset until a STOP OFF statement is entered. The STOP NOW function only stops once.
MVT312A IPL STATEMENT MISSING: stmt-type
Where "stmt-type" may be:
  1. DLF
  2. DPD
  3. SET DATE
  4. SET CLOCK
The indicated IPL statement is required and has not yet been entered. The DLF statement is required whenever shared disk drives are specified. A DPD statement is required unless OPTION MODE=REAL is specified or the IPL is performed under VM. Note that MODE=REAL is ignored when IPL'd in ECPS/VSE mode and virtual is assumed. The SET DATE/CLOCK statements are only required if the TOD clock is not present or not set. Enter the needed IPL statements and any other desired IPL statements, then use EOB/ENTER to indicate that all IPL statements have been entered.
MVT313I nnn DEVICES DELETED
This message is issued in response to a DELETE IPL statement and indicates the number of devices actually deleted by the command. The DELETE statement may specify a range of devices and all devices within that range are deleted. Zero may appear in this message if no devices were deleted.
MVT314D REQUIRED OPERAND IS MISSING.
The statement rejected was missing a required operand. Please review the operands which are required for the IPL statement and reenter the corrected statement. An EOB/ENTER response will resume the original input stream of IPL statements.
MVT315D INVALID COMBINATION OF OPERANDS.
The IPL statement listed has been rejected because it contained operands which could not be used in combination with each other. Please read the description of the operands permissible for the statement and reenter the corrected statement. Use an EOB/ENTER response to resume the original input stream of IPL statements.
MVT316D MISSING PUB FOR [SYSRES | SYSLOG]
An attempt has been made to complete an IPL but the device used for SYSRES or SYSLOG has not yet been defined. A console read is issued to allow the operator to enter more IPL statements. These statements should include an ADD statement for the SYSRES or SYSLOG device as indicated in the message. An EOB/ENTER response is used to indicate that all IPL statements have been entered. Note that SYSRES is defined as the disk device address IPL'd and must have a PUB with the same name. SYSLOG is the device used for console communications during the IPL.
MVT317W DEVICE TYPE CORRECTED FOR [SYSRES | SYSLOG]
The device type code specified for SYSRES or SYSLOG does not match the true device type of the device. The system has automatically altered the device type code for the device to match its true device type.
MVT318D DUPLICATE DEVICE OR PATH
An attempt has been made to add a device during IPL which duplicates either a previously defined device name or duplicates one or more paths for a previously defined device. When defining a control unit with both single and multiple path devices, the device names must be specified in sequence. Check your nucleus options assembly and ADD statements for duplicate names and paths. The statement listed has been rejected. Enter any desired IPL statements, then use EOB/ENTER to return to the original IPL statement input stream.
MVT319D ADD REJECTED. ONLY nnn ADDITIONAL DEVICES ALLOWED.
The IPL ADD statement listed has been rejected because if it were processed it would create a total device count exceeding 253. The message indicates the number of devices which can still be added before this total is exceeded. It may be necessary to delete other devices if the current ADD statement is to be processed. Enter any desired IPL statements, then use an EOB/ENTER response to return to the original IPL statement input stream.
MVT320W ASSGN OF SYSxxx TO cuu FOR Rx IGNORED.
An IPL ASSGN statement or nucleus options NUCASSGN macro specified an assignment to be made which cannot be honored. The assignment request, as indicated in the message, has been ignored. Review your IPL statements and nucleus options assembly to determine if some necessary assignments have been omitted or specified incorrectly.
MVT321C INSUFFICIENT REAL MEMORY FOR MINIMUM PAGE POOL
An IPL has been attempted in virtual mode on a CPU with insufficient real memory for virtual operations. The CPU must have enough real memory for the nucleus and the minimum page pool. It might still be possible to IPL in real mode by specifying OPTION MODE=REAL on the next IPL. This message is followed by a hard wait.
MVT322C PUB ENTRY NOT FOUND FOR DPD COMMAND
The device to be used for the page data set was deleted after the DPD statement was processed. IPL has already progressed too far to correct the error and the system must be reipl'ed.
MVT323C DPD COMMAND GIVEN FOR NON-DASD DEVICE TYPE
The device type for one on the devices specified in a DPD statement for a page data set extent was changed to a non-DASD device type after the DPD statement was processed. The IPL has already progressed too far to recover and the system must be reIPL'd.
MVT324C DASD DEVICE NOT SUPPORTED FOR DPD COMMAND.
The device type for one on the devices specified in a DPD statement for a page data set extent was changed to a non supported device type after the DPD statement was processed. The IPL has already progressed too far to recover and the system must be reIPL'd.
MVT326D NOT VALID DASD FOR SYSxxx
The device type for the logical unit indicated is not valid and the IPL statement has been rejected. The device used in the definition must have been previously defined to the system with the correct device type. Add the device with its proper device type and reenter the IPL DEFINE to set the proper assignment.
MVT327A DATE EXCEEDS SYSTEM EXPIRATION OF yyddd.
An attempt has been made to complete an IPL with the CPU TOD clock set beyond the MVT/VSE system expiration. This may possibly be due to a bad clock value. Use the SET DATE/CLOCK statement to set the TOD clock to the proper date. If your system has expired, you may still IPL by using a back date, but you should contact Software Pursuits for an expiration update. Note that attempts to defeat the expiration mechanism may result in the loss of the SYSRES data set.
MVT328C TOO MANY ITEMS BELOW 32K ADDR
The IPL cannot proceed because a nucleus table which must be located below the address of 32K will not fit. An alternate nucleus options phase must be used in order to perform an IPL. (NUCLEUSK is distributed for such emergencies.) Once successfully IPL'd, reassemble your nucleus options phase and decrease one of the following: devices PUBS, LUBS, or regions.
MVT329C VOLID volid DOES NOT MATCH VOLID volid ON cuu
An IPL statement requested volume serial number verification, such as the DPD statement. The first volume serial number listed is the one requested. The IPL is terminated because the second volume serial number was found and it does not match the one requested.
MVT330I NUMBER OF ADDRESS SPACES IS: nn
This message is issued during the IPL process and informs you of the number of address spaces configured for your system. The number (nn) may be from 1 to 15. This is dependent on your installation.
MVT330I LOCK FILE ON cuu: FORMATTING IN PROGRESS
This message will appear whenever the Lock File is being formatted during IPL. This can occur because TYPE=FORMAT was specified on the DLF statement, or because the Lock File does not already exist on the unit specified by the DLF statement.
MVT331A REPLY "IGNORE" TO CONTINUE IPL, BUT NOT USE A LOCK FILE
This message appears during IPL after messages 0I14I, 0J27D, or 0J30I whenever the DLF statement specified a device which is not available for use or is not shared, or the file cannot be used because the NCPU value does not match that of the current file or an unrecoverable I/O error occurs on the file.

The IPL will be terminated unless the operator replies "IGNORE". If the operator chooses to continue no external locking will be available and possible system damage may occur if any shared resources rely on external locking for protection.

MVT332W REPLIED IGNORE, EXTERNAL LOCKING IGNORED
This message will appear whenever the operator replied "IGNORE" to message MVT331A. It's purpose is to warn the operator that no external locking will be available for the system being IPL'd.
MVT333I VSIZE IN K: kkkk IN MEG: mmmm
This message is issued during the IPL process. It indicates the size of your virtual storage in kilobytes and megabytes. Both numbers are rounded up to the nearest tenth, if necessary.
MVT334I MACHINE REAL STORAGE SIZE IN K: kkkk IN MEG: mmm
This message is issued during the IPL process. It display the amount of real storage available in your CPU. The size is shown in kilobytes and megabytes. Both numbers are rounded up to the nearest tenth, if required.
MVT335I MACHINE V=R SIZE IN K: kkkk IN MEG: mmm
This message is issued during the IPL process. It display the size of the V=R area for your system. The display shows the size in both kilobytes and megabytes. Both numbers are rounded up to the nearest tenth, if necessary.
MVT336I OPERATING MODE = mode
This message is issued during the IPL process. It displays the mode of operation for this IPL. The modes of operation which may be displayed are:
  1. Paging Mode
  2. VM Assisted Mode
  3. ECPS Mode
  4. Real Mode
MVT337I [VM/XRM | HPO/XRM] RMSIZE=nnMB RSSIZE=nnnMB
This message informs the operator of the beginning and ending of the extended memory which will be available to the V=R guest machine which is being IPLed. The RMSIZE and RSSIZE values in the message should correspond to those encountered on the OPTION VMXMEM statement entered during IPL.
MVT339I MVT/VSE XRM ACTIVATION IN PROGRESS
This message is issued when the MVT/VSE operating system activates the MVT/XRM service to access extended memory (above the 16Mb line).
MVT340E UNEXPECTED PROGRAM CHECK **** XRM INITIALIZATION TERMINATED
An unexpected program check has occurred during the initialization of extended memory (memory above the 16Mb line). IPL continues but extended memory will not be used. This error is generally due to an invalid specification in the OPTION VMXMEM= options. In most cases the RMSIZE of RSSIZE was specified incorrectly. If the problem persists after correction, contact Software Pursuits.
MVT341I MVT/XRM SYSTEM INITIALIZED
This message indicates that initialization of an extended memory system has been successful. The system could be a V=R guest which was IPLed with the OPTION VMXMEM IPL statement or it could be a native machine with more than 16 megabytes of memory
MVT342I MVT/XRM INIT HAS BEEN CANCELED
This message indicates that the initialization of XRM has failed. This message should be preceded by another message (i.e., MVT343) which providing additional information about the cause of the failure.
MVT343E [VM/XRM | HPO/XRM] PRODUCT HAS EXPIRED
This message indicates that the VM/XRM product has expired. Contact Software Pursuits.
MVT344I [VM/XRM | HPO/XRM] PRODUCT ACTIVATION FAILED
The VM/XRM product has failed to initialize due to an error. This message should be preceded by another message (i.e., MVT346) which provides additional information about the cause of the failure.
MVT345I MVT/XRM REQUIRES VM/XRM
This message is issued when attempting to activate MVT/XRM in a VM environment where the VM/XRM product is not installed. MVT/XRM requires VM/XRM to complete activation. Activation of MVT/XRM terminates. Contact Software Pursuits.
MVT346E CP ERROR DURING VM/XRM ACTIVATION
This message is issued if any of the CP DIAGNOSE commands, which are issued during VM/XRM activation, receive a non-zero condition code. VM/XRM activation is aborted. Contact Software Pursuits.
MVT347E [VM/XRM | HPO/XRM] PHASE 2 ACTIVATION ERROR
This message is issued if the Test Block instruction, used during phase 2 of VM/XRM activation, receives a non-zero condition code. VM/XRM activation is terminated. Contact Software Pursuits.
MVT348I [VM/XRM | HPO/XRM] ACTIVATION IN PROGRESS
This message is issued during the activation of VM/XRM to inform the operator that the activation is taking place.
MVT349II [VM/XRM | HPO/XRM] ACTIVATION COMPLETED
This informational message is issued when the VM/XRM product has completed initialization and is active.
MVT350EI [VM/XRM | HPO/XRM] RSSIZE ADJUSTMENT FAILURE
This message is issued after MVT has determined that the extended memory which is actually available is less than what was specified in the RSSIZE operand of the OPTION VMXMEM= statement. When this happens, MVT tries to inform VM/XRM of the lesser amount. This message is issued when MVT's attempt to inform VM/XRM of the lesser amount fails. Contact Software Pursuits Technical Support if you see this message.
MVT351D VM/XRM NOT INSTALLED OR GUEST NOT V=R
This message is issued in response to the IPL OPTION VMXMEM= statement. The message indicates that VM/XRM must be installed and the machine being IPLed must reside in the V=R area. The message is issued if either of these conditions is not true and the OPTION VMXMEM= statement is rejected.

4xx Messages  [TOP]

MVT400I UNLOAD OF cuu COMPLETE
The tape on the indicated address has been rewound and unloaded.
MVT401W DEVICE cuu IN USE BY Rx
The indicated tape device is already in use by the indicated region. You may select another tape device or wait until the indicated device is free.
MVT402W UNIT cuu IS NOT A TAPE DEVICE
An attempt has been made to perform a tape operation on a device that is not a tape device. Re-start the processing using a proper device.

7xx Messages  [TOP]

MVT700C JOB jobname CANCELED DUE TO JOB TIME EXCEEDED
The TIME specification on the JOB statement was exceeded and OPTION ACANCEL was in effect. If there was no TIME operand on the JOB statement, the default Job Time value was exceeded. It was assumed that a program within the Job was in a loop. If the Job must run, resubmit the Job with TIME=NO on the Job statement.
MVT701C JOB jobname CANCELED DUE TO STEP TIME EXCEEDED
The TIME specification on the EXEC statement was exceeded and OPTION ACANCEL was in effect. If TIME= was not specified on the EXEC statement, the system default step time was exceeded. It was assumed that the program was in a loop. If the program must run, resubmit the Job with TIME=NO on the EXEC statement.
MVT702W Rx HAS EXCEEDED ESTIMATED [JOB | STEP] TIME
The value specified in the TIME operand on the JOB or EXEC statement has been exceeded, or if none was specified, the system default interval was exceeded. This is a warning message. The program running may be in a loop and may need to be canceled, but the system has not taken any action. The message may be avoided in the future by proper specification of the TIME operands.
MVT703C program INSUFFICIENT GETVIS
The named program could not get sufficient GETVIS area in order to function. The task had to be canceled. Rerun your job increasing the GETVIS area. GETVIS is normally specified with the GETVIS operand on the EXEC statement.

8xx Messages  [TOP]

MVT800C ATTEMPTING TO RESTORE THE CURRENT SYSRES IS NOT PERMITTED
An attempt was made to perform a restore of the operating system SYSRES from batch. This action is not permitted. The restore is terminated. To restore the SYSRES, you must perform the restore in a Stand Alone environment. Insure that no other systems are attempting to access the SYSRES during the restore process.
MVT801C PROGRAM CANCELED DUE TO ATTEMPTING TO WRITE OUTSIDE LIBRARY FILE LIMITS
During a restore operation, the last I/O operation attempted to write outside the file limits. This is generally due to invalid input. The restore process is terminated. Check to be sure the proper tape is being used and, if in batch mode, the proper JCL specification were used.
MVT802C PROGRAM CANCELED DUE TO PROGRAM LOGIC ERROR. NEGATIVE HALFWORD DEVELOPED.
If this error is received, do the following:
  1. Take a dump of the program. Include the Region and Supervisor. If you are unable to take a Region dump, take a stand alone dump.
  2. Send the dump and the input tape to SPI.
MVT803C PROGRAM CANCELED DUE TO INCORRECT INPUT. RDWSIZE is nnnnnn ACTUAL SIZE is nnnnnn
This message is issued due to an input tape error during a restore operation. There is a difference between the actual size of the tape being read and as recorded in the Record Descriptor Word (RDW) as recorded in the first 4 bytes of the tape record. This may be due to:
  1. A tape read error, or
  2. The tape was copied incorrectly.
For a read error, perform the restore on a different tape drive. If this fails, contact the person that generated the tape and ask for another copy.
MVT804C LIBRARY NOT ALLOCATED ON A CYLINDER BOUNDARY
An attempt was made to restore a library to other than a cylinder boundary. ALL libraries must begin and end on cylinder boundaries. Correct the proper DLBL and EXTENT statements.
MVT805C LIBRARY NOT ALLOCATED IN COMPLETE CYLINDERS
An attempt was made to restore a library to other that was not allocated properly. ALL libraries must begin and end on cylinder boundaries. Correct the proper EXTENT statement.
MVT806C NO ALLOCATION INFORMATION AVAILABLE
An attempt was made to perform a restore with no allocation information. Check the JCL and add the proper DLBL and EXTENT statements.
MVT807I PROGRAM RUNNING IN QUIET MODE
The Backup/Restore program is being processed with an UPSI setting of xxx1xxxx. This setting eliminates all messages from the console. Messages are printed on SYSLST only.
MVT808C WRONG LOGICAL UNIT. EXPECTED PLU SYSxxx. FOUND PLU SYSyyy
The mandatory SYS numbers were not properly coded in an EXTENT statement when using the assignment method of Backup/Restore. Check the 'EXPECTED PLU SYSxxx' portion of the message to determine the type of library being used. The following SYS numbers apply: Correct the EXTENT statement JCL error(s) and process the job again.
MVT809C EXTENT CARD ALLOCATION MUST BE [INCREASED | DECREASED] nnnnn BLOCKS
For FBA devices only. The size of the library as defined in an EXTENT statement does not agree with the allocation for the library. Change the number of blocks allocated on the EXTENT statement, as indicated, and process the job again.

9xx Messages  [TOP]

MVT901D DUPLICATE KEYWORD SPECIFIED
The same keyword was specified twice in the same statement. Check for possible confusion on keyword abbreviations or misspelling. The statement is rejected.
MVT902D KEYWORD NOT DEFINED OR TOO MANY POSITIONAL OPERAND
A keyword was specified for a statement and the keyword is not defined for that statement, or a positional operand was specified for a statement which does not allow the number of positional operands specified. Check for misspellings and review possible operands for the statement. The statement is rejected.
MVT903D UNPAIRED PARENTHESIS
The number of left parentheses in the statement does not equal the number of right parentheses. Check for a missing parenthesis. The statement is rejected.
MVT905D UNPAIRED QUOTE
The number of single quote marks in the statement is not an even number. Check for a missing quote mark. Imbedded quotes must be doubled to be recognized. The statement is rejected.
MVT906D INVALID OPERAND SYNTAX
The statement scan routine was unable to properly determine where an operand began or ended. The statement is rejected. Check for illegal coding and missing commas.
MVT907D INVALID OPERAND VALUE
The value of an operand is not numeric or does not match one of the possible values permissible for that operand. Review the list of valid operands for each operand coded. The statement is rejected.
MVT908D TABLE SPECIFICATION ERROR
A SCANPARM table error has been detected. Possibly core has been overlaid or a verb table out of order. Obtain a dump and call SOFTWARE PURSUITS technical support.
MVT909D INVALID NAME FIELD
The name field coded for the statement contains too many characters. A name may contain a maximum of eight characters. Check if a name field was intended. Not all commands use a name field. The statement is rejected. To omit a name field, start the verb in column two.
MVT910D INVALID VERB
The name of the verb in the statement was not recognized. Check for a misspelling or improper abbreviation of the command. Some verbs cannot be abbreviated.
MVT911D INVALID KEYWORD ABBREVIATION
The abbreviation of a keyword operand was too short and could not be distinguished from other keywords. The operand must contain enough characters to be recognized from other possible operands. The statement is rejected.
MVT912D ILLEGAL CONTINUATION OF QUOTED VALUE
An attempt was made to continue a statement which contained a value in single quotes. The continuation statement did not indicate the continuation of the value with a starting quote. Check if a quote mark is missing. The statement (including the assumed continuation statement) is rejected.
MVT913C INVALID CONTINUATION
A continuation statement was requested by ending the previous statement with a comma. The continuation statement was not in the proper format. The continuation must start with "//A" followed by more blanks if desired. The operands may start in any column. If a value in quotes is being continued, a starting quote must be specified in the continuation statement. The statement and the continuation statement are rejected.
MVT920C TOO MANY CONTINUATION CARDS OR PARAMETERS
This error should never occur in normal processing. Too many continuation statements were submitted or too many operands were coded or the combined length of all operands contained too many characters. Shorten the values, code fewer operands, or use fewer continuation statements. The Job is canceled.

21xx Messages  [TOP]

MVT2106 VERSION vv.mm-mm/dd/yy
This message identifies the version of the program and is written to SYSLST.
MVT2107 ENTER REQUIRED CONTROL CARD
This message is written to SYSLOG as a prompt if the control card input is going to be read from SYSLOG.
MVT2108 TAPE FILE nnn HAS nnn BLOCKS SMALLEST IS nnn LARGEST IS nnn
This message is written to SYSLST to indicate that the file number indicated of the input master has been successfully written to disk.
MVT2109 ERROR - INVALID OR MISSING CONTROL CARD, ABEND
If control card input is from SYSIPT, this message is written to this message is written to SYSLOG and the operator is again prompted for the control card.
MVT2110 COPY ON cuu AT nnnn BPI IS nnn OF nnn AND HAS nnn FILES
This message is written to both SYSLST and SYSLOG. It indicates that the tape copy on the drive shown has been completed and may now be removed.
MVT2111 WARNING: I/O ERROR, ASSUMING EOT!
This message is written to SYSLST whenever an Un-recoverable I/O error occurs on the input tape and both of the following are true:
  1. At least one file has been read from the input tape and
  2. No blocks have been read since the last tape mark was read.
In this case the program assumes that the error indicates the end of the files to be copied. In all other cases, the program assumes that the error is fatal and cancels.
MVT2112 SCAN COMPLETE, NEED nnn TRACKS FOR DISK FILE
This message is written to SYSLST when COPIES=0 was specified to obtain required disk space information.
MVT2113 REMOVE INPUT TAPE, MOUNT OUTPUT TAPE
This message is written to SYSLOG when the input master tape has been completely copied to disk.
MVT2114 - function PROCESSING COMPLETE
This message is written to SYSLST and indicates that the requested function (SCAN or COPY) processing is complete.
MVT2115 ERROR - WRONG BLOCK SIZE READ FROM DISK, ABEND
This message is written to SYSLST if an error is encountered when reading back from the disk file. The program then cancels.
MVT2116 OPTIONS ARE: COPIES=nnn,FILES=nnn,SYSLOG=x,DRIVES=n, DSE=x,DISK=x
This message is written to SYSLST and indicates the options which have been selected. COPIES=SCAN will appear in this message whenever COPIES=0 was specified to indicate that the scanning function was chosen. Likewise, if the FILES= operand was omitted, then it will be appear in this message as FILES=EOV to indicate that copying will continue until 3 consecutive Tape-Marks are found.
MVT2117 LIBRARY FOUND-dddddd xxxxxxx yyyyyyyyyyyyyyyyyyyyyy
This message is written to SYSLST whenever a Library Info Header is read from the input tape. The library type (xxxxxx) and the 44 character library name (yyyyy...) are shown; the date created (dddddd) is also shown if available. Library Info Header records are contained only on tapes created by BACKUP.
MVT2118 SEARCH STRING FOUND IN BLK nnnnnn xxxxxxxxxxxxxxxxx
This message is written to SYSLST whenever a search string is found. The physical block number containing the search string is shown as nnnnnn and xxxxxx... is 40 bytes of data found in the physical block beginning with the string. Only the first occurrence of the sting in a block is logged
MVT2119C $$BOTSVA CANNOT DETERMINE ENTRY OFFSET
This message is written to SYSLOG if the MVT/VSE transient $$BOTSVA is unable to determine the entry offset into the required tape LIOCS module. $$BOTSVA has been called to process a VSE/SP Tape DTF and it needs to find either a BAL R14,ddd(R15) or a BAL R14 ddd(,R15) instruction in order to determine the entry offset into the Tape Liocs Module for the GET, PUT etc. function being processed.

The program is terminated with a dump. Save the dump and contact Software Pursuits Technical Support for assistance.

MVT2120C $$BOTSVA CDLOAD FOR phasename FAILED: RC=nn
This message is written to SYSLOG whenever the MVT/VSE transient $$BOTSVA get a non-zero return code from the CDLOAD request for the named Tape LIOCS module phase. The phasename should be one of the following seven names: IJFFBCWN, IJFNBZWN, IJFRBZWN, IJFSBCWN, IJFUBCWN, IJFWENZN, or IJFXBZWN.

The following return codes are some of the more common errors:

For any other return codes refer to the description of the CDLOAD macro in the appropriate 'Macro Reference' manual.

The program is terminated with a dump. Correct the condition indicated by the return code. If unable to resolve the problem, save the dump and contact Software Pursuits Technical Support for assistance.

22xx Messages  [TOP]

MVT2200E GETVIS FAILED
This message is from the MVTPRPCH utility program. It indicates that the program was unable to acquire enough region GETVIS for proper operation. Increase the GETVIS amount on the EXEC statement.
MVT2201E NO PROC RECORDS FOUND ON TAPE
This message is from the MVTPRPCH utility program. The MVTPRPCH program did not find a Procedure Library. Be sure the proper tape is mounted and/or that the tape is positioned properly.
MVT2202E LOGIC ERROR, CONTACT SOFTWARE PURSUITS
This message is from the MVTPRPCH utility program. An internal logic error occurred. Contact Software Pursuits Technical Support.

3xxx Messages  [TOP]

MVT3K06I UNEXPECTED RETURN CODE X'nn' FROM MACRO macro IN PHASE
RESTORE.
An unexpected error (X'nn') was encountered in RESTORE phase. The name of the macro encountering the error is displayed. The restore is terminated.

This error is generally due to an incorrect library type specification. All libraries restored prior to receiving this message were restored properly. If, after checking for this error, you are not able to complete the restore, contact Software Pursuits Technical Support and inform them of the return code and the macro name.

8xxx Messages  [TOP]

MVT8B05I WRONG LOGICAL UNIT. EXPECTED PLU SYSxxx
FOUND SLU/PLU SYS
yyy
The expected SYSxxx will be either 005/7/8/9 depending upon which type library is being processed. The extent card for the library DLBL must have the same SYS number as the expected SYS number printed out. This message can only occur when using the ASSGN backup method.
MVT8R000I VOLUME TO BE RESTORED TO IS dlabel. REPLY YES OR EOB TO CONTINUE
This is an informational message requesting that you indicate if the restore of the volume indicated is to continue. Reply with 'YES' or an End Of Block to continue. Any other reply will abort the restore process.
MVT8R41I TAPE ERROR, WRONG DESCRIPTOR OR BLOCK NUMBER OR SEQUENCE NUMBER
The RESTORE program does not recognize the tape being used as input. This is generally due to:
  1. Using an incorrect tape.
  2. Using a tape that was copied from another tape and the copy was not correct.
The restore is terminated. If the problem persists and you are unable to determine the cause, contact Software Pursuits Technical Support.
MVT8R50I MORE THAN 30 type LIBRARIES.
An attempt has been made to backup more than 30 libraries. This is the maximum number of libraries that can be processed. Process the backup again specifying 30 or less libraries.
MVT8R61I 'LIST' FUNCTION REQUEST REQUIRES 9.2 LEVEL BACKUP TYPE.
This error is only encountered when using the Control Card restore process. The LIST= function is being used for a tape that was created using a BACKUP program prior to that distributed with MVT/VSE Release 9.2 and using the function with a RESTORE program from MVT/VSE Release 9.2 or later. The later version of RESTORE does not support this function on the earlier tape format. The restore is terminated.
MVT8R63I ORIGINAL START ADDRESS WILL BE USED.
An End Of Block was entered for the restore extents. The extents as indicated on the backup tape will be used. The restore continues operation.
MVT8R080I EXTENT CARD ALLOCATION MUST BE [IN | DE]CREASED nnnnn BLOCKS
This message indicates on an FBA system total library blocks allocated does not equal that assigned in EXTENT statement. This message will be followed by message 8R08I ALLOCATION ERROR and program termination.
MVT8R102I RELATIVE TRACK GIVEN NOT ON CYLINDER BOUNDARY. RE-ENTER.
The relative track indicated for the library restore does not being on a cylinder boundary. Re-enter the proper cylinder to continue the restore.
MVT8R120D WAS PREVIOUS REPLY MENT TO BE DELETE? REPLY 'YES' OR 'NO'
An entry was made, in response to a reply, that may have been DELETE. RESTORE scans all entries to insure their integrity. This prompt is to insure that the user wishes to indicate that the reply is DELETE.
MVT8X09I ATTEMPTING TO RESTORE THE CURRENT OPERATING SYSTEM IS NOT PERMITTED.
An on-line (batch) mode restore is being processed. An attempt has been made to restore SYSRES data from a backup tape to the current actual operating system. This is not allowed. The restore is terminated.
MVT8X10C PROGRAM CANCELED DUE TO ATTEMPTING TO WRITE OUTSIDE LIBRARY FILE LIMITS.
An attempt has been made to restore data outside of the specified extents. The restore is terminated. This action is taken to prevent the data from being written over.
MVT8X11C PROGRAM CANCELED DUE TO PROGRAM LOGIC ERROR. NEGATIVE HALFWORD DEVELOPED.
A logic error has occurred. Contact Software Pursuits Technical Support.
MVT8X12C PROGRAM CANCELED DUE TO INCORRECT INPUT. RDW SIZE IS size. ACTUAL SIZE IS size.
The first 4 bytes of the Record Descriptor Word (RDW) does not agree with the length of the tape. The operation is terminated. This error is generally due to a backup tape being copied incorrectly and the incorrect tape used for the restore process.
MVT8X13C LIBRARY NOT ALLOCATED ON CYLINDER BOUNDARY.
The extent specification for a library was not specified as starting on a cylinder boundary. You are prompted to enter the proper extents.
MVT8X14C LIBRARY NOT ALLOCATED IN COMPLETE CYLINDERS.
The extents for a library were not specified as full cylinders. The restore terminates. Re-start the restore using the proper allocations.

  1500 Fashion Is. Blvd., Suite 205
San Mateo, CA 94404
Phone: 650-372-0900
Fax: 650-372-2912

Copyright © 2000 by Software Pursuits, Inc.
All rights reserved