A VMRGRW abend, which signifies the abnormal termination of VMRGRW processing, can be caused by an internal logic error, an error processing the VMRGRW control file, or an error interfacing with another program.
VMRGRW abend codes are reported in this command error message:
VMGABN018T VMRGRW ABEND number AT address
Other messages from CMS or VMRGRW can help to clarify the problem. Correct the indicated problem and try again.
Abend Number | Meaning |
---|---|
21 | This abend is accompanied by the diagnostic message "**** LITERAL TABLE OVERFLOW ****". It indicates that the area VMRGRW uses to store constants and computed results has overflowed. An extremely large number of DEFINE, REDEFINE, or COMPUTE statements could be responsible. Using many long literals can also contribute to the problem. |
22 | The VMRGRW internal work areas cannot contain all the tasks necessary to produce your report. An extremely large number of VMRGRW statements could be responsible. |
23 | VMRGRW has attempted to begin a step that has no input. This indicates a programming error because VMRGRW attempts to detect missing input situations without abending. |
24 | While processing a CA VM:Tape TMC, VMRGRW has discovered a DSNB that is not owned by the volume it is tied to logically. This may indicate that the TMC is being updated while VMRGRW is trying to report on it. |
32 | VMRGRW cannot recognize the internalized form of one of your control statements. This is an internal error; it is not caused by any error in your control statements. If this occurs, contact your system administrator. |
47 | VMRGRW cannot locate the data definitions for the type of file specified on your FILE statement. This is an internal error; it is not caused by any error in your control statements. If this occurs, contact your system administrator. |
52 | VMRGRW found an error in opening your output file. You might have specified an invalid ddname with the TO parameter in a WRITE or SUMMARIZE statement. |
53 | VMRGRW found an error in writing to your output file. This can occur if output is written to a minidisk you have accessed as read-only, or if the output minidisk (normally your A-disk) does not have room for the output file. |
62 | VMRGRW encountered an error in opening your input file during the execution phase, although the file was verified to exist during the compile phase. This could be caused by another user ID modifying or erasing the input file while VMRGRW is trying to process it. |
63 | VMRGRW found an error reading your input file during the execution phase, although the file was verified to exist during the compile phase. This could be caused by another user ID modifying or erasing the input file while VMRGRW is trying to process it. |
71 | VMRGRW received an error indication from the called sort program. Consult any messages produced by the sort program to diagnose this problem. |
83 | VMRGRW has found an error while constructing the parameters for a call to SORT. This is an internal error; it is not caused by any error in your control statements. If this occurs, contact your system administrator. |