FCOPY
Error, Warning, and Status Messages
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| E0701 Volume II | |
| E0300 Volume I ♥ | |
| E0300 Volume II | |
| E0300 Volume III | |
| E0394 Volume I | |
| E0796 Volume II | |
| E0494 Volume III |
 |
NOTE: In the text, * indicates a WARNING message ** indicates a STATUS message |
- MESSAGE
< CONTROL Y >
- CAUSE
Acknowledges receipt of a CTRL-Y entered during a session.
- ACTION
None
- MESSAGE
READ ERROR FROM COMMAND INPUTFILE
- CAUSE
An error occurred while reading an FCOPY command from $STDIN.
- ACTION
In a job: re-submit the job. In a session: re-enter the command.
- MESSAGE
WRITE ERROR TO COMMAND LISTFILE
- CAUSE
An error occurred while writing an FCOPY message to $STDLIST.
- ACTION
It is likely that nothing serious occurred and all FCOPY operations were performed successfully. To make sure, however, do the following: In a job: re-submit the job. In a session: re-enter the most recent FCOPY command.
- MESSAGE
SYNTAX ERROR: EOF FOUND IN COMMAND FILE, MISSING EXIT COMMAND
- CAUSE
The command input file did not contain an EXIT command.
- ACTION
Correct the input file.
- 3
- MESSAGE
SYNTAX ERROR: IN SUBSET OPTION
- CAUSE
The SUBSET function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 4
- MESSAGE
SYNTAX ERROR: IN TITLE OPTION
- CAUSE
The TITLE option of the DISPLAY function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 5
- MESSAGE
SYNTAX ERROR: IN IGNERR OPTION
- CAUSE
The "ignore errors" function is not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 6
- MESSAGE
SYNTAX ERROR: IN VERIFY OPTION
- CAUSE
The "verify" function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 7
- MESSAGE
SYNTAX ERROR: IN SKIPEOF OPTION
- CAUSE
The "skip end-of-file" function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 8
- MESSAGE
SYNTAX ERROR: IN COMPARE OPTION
- CAUSE
The "compare" function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 9
- MESSAGE
SYNTAX ERROR: IN NEW OPTION
- CAUSE
The "new file" function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 10
- MESSAGE
SYNTAX ERROR: IN HEX OPTION
- CAUSE
The hexadecimal display function was not specified.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 11
- MESSAGE
SYNTAX ERROR: IN EBCDICOUT OPTION
- CAUSE
The EBDICOUT character translation function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 12
- MESSAGE
SYNTAX ERROR: IN CHAR OPTION
- CAUSE
The "display character" function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 13
- MESSAGE
SYNTAX ERROR: IN OCTAL OPTION
- CAUSE
The "display octal" function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 14
- MESSAGE
SYNTAX ERROR: IN UPSHIFT OPTION
- CAUSE
The "upshift" function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 15
- MESSAGE
SYNTAX ERROR: IN BCDICIN OPTION
- CAUSE
The BCDICIN character translation function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 16
- MESSAGE
SYNTAX ERROR: IN NORECNUM OPTION
- CAUSE
The NORECNUM option of the display function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 17
- MESSAGE
SYNTAX ERROR: IN EBCDICIN OPTION
- CAUSE
The EBCDICIN character translation function was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 18
- MESSAGE
SYNTAX ERROR: IN BCDICOUT OPTION
- CAUSE
The BCDICOUT character translation function was not specified properly
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 19
- MESSAGE
SYNTAX ERROR: INVALID FORM OF EXIT COMMAND
- CAUSE
The EXIT command was not specified properly.
- ACTION
None. FCOPY terminates.
- 51
- MESSAGE
SYNTAX ERROR: IN QUOTED STRING
- CAUSE
The characterstring specified for the SUBSET function is not valid.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 52
- MESSAGE
SYNTAX ERROR: IN BIT PATTERN
- CAUSE
The patternlist specified for the SUBSET function is not valid.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 53
- MESSAGE
SYNTAX ERROR: INVALID INTEGER
- CAUSE
An integer specified in the command is outside the range allowed for the particular COPY function.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 54
- MESSAGE
SYNTAX ERROR; UNKNOWN OPTION
- CAUSE
One of the specified functions was unrecognizable, or the command passed with the INFO parameter of the RUN command had more than 70 characters between semicolons.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 55
- MESSAGE
SYNTAX ERROR: IN FROMFILE SPECIFIER
- CAUSE
The fromfile was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 56
- MESSAGE
SYNTAX ERROR: IN TOFILE SPECIFIER
- CAUSE
The tofile was not specified properly.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 57
- MESSAGE
SYNTAX ERROR: ILLEGAL COMBINATION OF OPTIONS
- CAUSE
Two or more "functionlist" entries conflict with one another.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 58
- MESSAGE
SYNTAX ERROR: FROMFILE AND TOFILE NOT BOTH SPECIFIED
- CAUSE
FROM=" " and TO=" " were not both specified in the FCOPY command.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 59
- MESSAGE
SYNTAX ERROR: ILLEGAL USE OF NEW
- CAUSE
The context used to specify a new tofile is not valid.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 60
- MESSAGE
SYNTAX ERROR: ILLEGAL USE OF ``*
- CAUSE
The context used to specify * as a fromfile or tofile is not valid.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 62
- MESSAGE
SYNTAX ERROR: FILE NAME TOO LONG
- CAUSE
The name specified for the fromfile or tofile is longer than the 35 characters allowed in a fully qualified file name with lockword.
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 102
- MESSAGE
CANNOT CLOSE FROMFILE
- CAUSE
MPE/iX cannot close the fromfile. This message is followed by an MPE/iX file information display containing (among other things) an error number.
- ACTION
Look up the error number in the file system error table in the MPE/iX Intrinsics Reference Manual and act accordingly.
- 103
- MESSAGE
CANNOT CLOSE TOFILE
- CAUSE
MPE/iX cannot close the tofile. This message is followed by an MPE/iX file information display containing an error number.
- ACTION
Look up the error number in the file system error table in the MPE/iX Intrinsics Reference Manual and act accordingly.
- 104
- MESSAGE
CANNOT SAVE NEW TOFILE
- CAUSE
MPE/iX cannot close the tofile as a permanent file. Either you do not have SF capability or there is not enough group, account, or system file space.
- ACTION
If you don't have SF capability, you cannot perform the operation. If there is not enough file space, purge some unneeded files to free some file space.
- 105
- MESSAGE
CANNOT OPEN FROMFILE
- CAUSE
MPE/iX cannot open the fromfile. This message is followed by an MPE/iX file information display containing an error number.
- ACTION
Look up the error number in the file system error table in the MPE/iX Intrinsics Reference Manual and act accordingly.
- 106
- MESSAGE
CANNOT OPEN TOFILE
- CAUSE
MPE/iX cannot open the tofile. This message is followed by an MPE/iX file information display containing an error number.
- ACTION
Look up the error number in the file system error table in the MPE/iX Intrinsics Reference Manual (32650-90028) and act accordingly.
- 107
- MESSAGE
VERIFY OR COMPARE OPTION: CANNOT GET READ ACCESS TO TOFILE
- CAUSE
MPE/iX cannot get READ access to the tofile for a VERIFY or COMPARE operation. The READ access specified in the file label has been overridden by an MPE/iX FILE command containing ACC=APPEND, ACC=OUT, or ACC=OUTKEEP.
- ACTION
Reset the FILE command (using the MPE/iX RESET command) and retry the operation.
- 108
- MESSAGE
ERROR IN CALLING FGETINFO FOR FROMFILE
- CAUSE
An error prevented MPE/iX from obtaining information from the fromfile's label. This message is followed by an MPE/iX file information display containing an error number.
- ACTION
Look up the error number in the file system error table in the MPE/iX Intrinsics Reference Manual and act accordingly.
- 109
- MESSAGE
ERROR IN CALLING FGETINFO FOR TOFILE
- CAUSE
An error prevented MPE/iX from obtaining information from the tofile's label. This message is followed by an MPE/iX file information display containing an error number.
- ACTION
Look up the error number in the file system error table in the MPE/iX Intrinsics Reference Manual and act accordingly.
- 110
- MESSAGE
IGNERR OPTION: FROMFILE NOT TAPE
- CAUSE
The fromfile's device is not a magnetic tape unit.
- ACTION
The "ignore errors" function cannot be used in this case.
- 111
- MESSAGE
CANNOT GET READ ACCESS TO FROMFILE
- CAUSE
MPE/iX cannot get READ access to the fromfile. The READ access specified in the file label has been overridden by an MPE/iX FILE command containing ACC=APPEND, ACC=OUT, or ACC=OUTKEEP.
- ACTION
Reset the FILE command (using the MPE/iX RESET command) and retry the operation.
- 112
- MESSAGE
CANNOT GET WRITE ACCESS TO TOFILE
- CAUSE
MPE/iX cannot get READ access to the tofile. The WRITE access specified in the file label has been overridden by an MPE/iX FILE command containing ACC=IN.
- ACTION
Reset the particular FILE command (using the MPE/iX RESET command) and retry the operation.
- 113
- MESSAGE
SKIPEOF OPTION: FROMFILE NOT AN UNLABELED TAPE
- CAUSE
The "skip end-of-file" function was specified for the fromfile, and the fromfile device is not a magnetic tape unit, serial disk, or cartridge tape unit.
- ACTION
If the intended fromfile or tofile is on magnetic tape or serial disk, check the associated MPE/iX FILE command and its backreference.
- 114
- MESSAGE
SKIPEOF OPTION: TOFILE NOT AN UNLABELED TAPE
- CAUSE
The "skip end-of-file" function was specified for the tofile, and the tofile device is not a magnetic tape unit, serial disk, or cartridge tape unit.
- ACTION
If the intended fromfile or tofile is on magnetic tape or serial disk, check the associated MPE/iX FILE command and its backreference.
- 115
- MESSAGE
SUBSET OPTION: STRING FALLS OUTSIDE OF FROMFILE RECSIZE
- CAUSE
The characterstring or patternlist specified is greater than the record size of the fromfile. No such subset can exist in the specified fromfile.
- ACTION
Change the specified subset definition to a valid one and try the operation again.
- 116
- MESSAGE
CANNOT GET LARGE ENOUGH BUFFER
- CAUSE
There is not enough data space for the buffers needed by the operation you have requested. FCOPY uses the DL-DB area for variable sized buffers.
- ACTION
Ask the system manager what size data area was specified when FCOPY was prepared, and rerun FCOPY specifying a larger MAXDATA= parameter. Also make sure that the system configuration can accommodate your record size in the maximum size allowed for data segments.
- 117
- MESSAGE
SKIPEOF OPTION: ERROR WHILE SKIPPING IN FROMFILE
- CAUSE
An error occurred while skipping end-of-file marks in the fromfile.
- ACTION
Check the syntax for the SKIPEOF function and retry the operation.
- 118
- MESSAGE
SKIPEOF OPTION: ERROR WHILE SKIPPING IN TOFILE
- CAUSE
An error occurred while skipping end-of-file marks in the tofile.
- ACTION
Check the syntax for the SKIPEOF function and retry the operation.
- 119
- MESSAGE
SUBSET OPTION: ERROR WHILE SPACING IN FROMFILE
- CAUSE
An error occurred while skipping end-of-file marks in the fromfile.
- ACTION
Check the syntax for the SKIPEOF function and retry the operation.
- 120
- MESSAGE
SUBSET OPTION: SUBSET STARTS OVER EOF BOUNDARY
- CAUSE
The specified subset extends over an end-of-file mark or a tape mark boundary.
- ACTION
Change the specified subset definition to a valid one and try the operation again.
- 123
- MESSAGE
SUBSET OPTION: THIS INPUT DEVICE DOES NOT BACKSPACE
- CAUSE
The specified subset requires backspacing in the fromfile, but the device for that file is not a disk or magnetic tape.
- ACTION
Check the MPE/iX FILE command associated with the fromfile and its backreference.
- 124
- MESSAGE
READ ERROR IN FROMFILE AT RECORD RECNUM
- CAUSE
An error occurred while spacing through the fromfile in search of the start of a subset.
- ACTION
Check the syntax of your command and retry the operation.
- 125
- MESSAGE
SUBSET OPTION: NUMERIC SUBSET IS EMPTY
- CAUSE
A subset specified by starting-record-number, number-of records and/or last-record-number does not exist, or contains no data.
- ACTION
Change the specified subset definition to a valid one and try the operation again.
- 126
- MESSAGE
VERIFY OPTION: ERROR WHILE REWINDING FROMFILE
- CAUSE
An error occurred while spacing backward to the beginning of the fromfile at the start of a "verify" operation.
- ACTION
Check the syntax of your command and retry the operation.
- 127
- MESSAGE
VERIFY OPTION: ERROR WHILE REWINDING TOFILE
- CAUSE
An error occurred while spacing backward to the beginning of the tofile at the start of a "verify" operation.
- ACTION
Check the syntax of your command and retry the operation.
- 128
- MESSAGE
EOF FOUND WHILE SPACING IN FROMFILE
- CAUSE
An end-of-file mark was encountered while spacing through the fromfile in search of the start of a subset.
- ACTION
Make sure that the starting record number for the subset does not exceed the number of records in the file.
- 129
- MESSAGE
EOF FOUND WHILE SPACING IN TOFILE
- CAUSE
An end-of-file mark was encountered while spacing through the tofile in search of the start of a subset during a "compare" or "verify" operation.
- ACTION
"Compare" operation: the fromfile and tofiles are not identical. Display the tofile to determine what it actually contains. "Verify" operation: the "copy" operation was not performed correctly. Retry the operation.
- 130
- MESSAGE
FCHECK ERROR
- CAUSE
The FCHECK intrinsic failed.
- ACTION
Notify your system manager.
- 131
- MESSAGE
ERROR WHILE WRITING EOF TOFILE
- CAUSE
An error occurred while writing an end-of-file mark in the tofile.
- ACTION
Check the syntax of your command and retry the operation.
- 132
- MESSAGE
VERIFY OPTION: ERROR WHILE SPACING IN THE FROMFILE
- CAUSE
An error occurred while writing an end-of-file mark in the fromfile during a "verify" operation.
- ACTION
Check the syntax of your command and retry the operation.
- 133
- MESSAGE
VERIFY OPTION: ERROR WHILE SPACING IN THE TOFILE
- CAUSE
An error occurred while writing an end-of-file mark in the tofile during a "verify" operation.
- ACTION
Check the syntax of your command and retry the operation.
- 134
- MESSAGE
FOUND EOF IN TOFILE
- CAUSE
FCOPY has performed the specified operation but has filled the tofile before completing the operation.
- ACTION
The tofile was not large enough. Use the MPE/iX LISTF filename,2 command to determine the tofile's size and then increase its size (using the MPE/iX PURGE and BUILD commands) and retry the operation. To copy from one file to a smaller file, use SUBSET=.
- 135
- MESSAGE
WRITE ERROR TO TOFILE
- CAUSE
An error occurred while writing to the tofile.
- ACTION
Check the syntax of your command and retry the operation.
- 136
- MESSAGE
READ ERROR FROM TOFILE
- CAUSE
An error occurred while reading from the tofile during a "compare" or "verify" operation.
- ACTION
"Compare" operation: retry the operation. If the error persists, you must try to recreate the tofile. "Verify" operation: retry the operation.
- 137 *
- MESSAGE
WARNING: AN UNLABELED TAPE OPERATION ENDS ON AN ERROR
- CAUSE
An operation involving a magnetic tape fromfile was terminated by reading beyond the end of valid data rather than by sensing an end-of-file mark.
- ACTION
This is not an error. You can avoid this message by specifying FILES=n where n is the number of files on the tape.
- 138
- MESSAGE
TITLE OPTION: TITLE TOO LONG
- CAUSE
The title specified for the "list" function is longer than the 70 characters allowed, or it extends over more than one line (record).
- ACTION
In a job: correct the command and re-submit the job. In a session: re-enter the command using the correct format.
- 139
- MESSAGE
DUMP OPTION: TOFILE RECSIZE NOT WITHIN LEGAL LIMIT
- CAUSE
A file display was directed to an intermediate storage device with an incorrect record size. That record size must be greater than 60 bytes (30 words).
- ACTION
Change the record size of the intermediate storage file (using the MPE/iX PURGE and BUILD commands) so that it is within the allowed range, and then retry the operation.
- 140
- MESSAGE
COMPARE OR VERIFY OPTION: OPERATION FAILS; DIFFERENT FIXED RECSIZES
- CAUSE
The "compare" or "verify" operation was not attempted because the record sizes of the tofile and fromfile are not identical.
- ACTION
"Compare" operation: none. The "compare" operation revealed that the fixed record sizes of the two files are not identical. "Verify" operation: change the record size of the tofile (using the MPE/iX PURGE and BUILD commands) so that it is the same as that of the fromfile and then retry the operation.
- 141 **
- MESSAGE
COMPARE BEGINS
- CAUSE
The comparison phase of a "verify" operation has begun.
- ACTION
None
- 143 *
- MESSAGE
WARNING: FROMFILE IS EMPTY
- CAUSE
The fromfile contained no data. Nothing was copied or compared.
- ACTION
None. You may inadvertently have specified the wrong file as the fromfile.
- 144
- MESSAGE
NEW OPTION: FILE ALREADY EXISTS
- CAUSE
The tofile named for the "new file" function already exists in the specified (or implied) group and account.
- ACTION
Change the name of the tofile and try the operation again.
- 145
- MESSAGE
BACKSPACE ERROR IN FROMFILE
- CAUSE
An error occurred while spacing backward to the beginning of the fromfile or a subset within it.
- ACTION
Check the syntax of your command and retry the operation.
- 146
- MESSAGE
CANNOT OPEN TEMPORARY LABEL FILE
- CAUSE
This may indicate a lack of space in your account.
- ACTION
Allocate more space in the account.
- 147
- MESSAGE
WRITE ERROR IN TEMPORARY LABEL FILE
- CAUSE
An error occurred while writing to the temporary label file.
- ACTION
Check the syntax of your command and retry the operation.
- 148
- MESSAGE
READ ERROR IN TEMPORARY LABEL FILE
- CAUSE
An error occurred while reading from the fromfile.
- ACTION
Check the syntax of your command and retry the operation.
- 149
- MESSAGE
OVERFLOW IN TEMPORARY LABEL FILE
- CAUSE
There are more labels in the fromfile than can be copied.
- ACTION
Use the NOUSERLABELS function to copy files without labels.
- 150
- MESSAGE
READ ERROR IN FROMFILE LABELS
- CAUSE
An error occurred while reading labels in the fromfile.
- ACTION
Check the syntax of your command and retry the operation.
- 151
- MESSAGE
WRITE ERROR IN TOFILE LABELS
- CAUSE
An error occurred while reading labels in the tofile.
- ACTION
Check the syntax of your command and retry the operation.
- 152
- MESSAGE
OVERFLOW IN TOFILE LABELS
- CAUSE
There are too many labels in the fromfile to be copied to the tofile.
- ACTION
If the tofile is an old file, retry the operation using the NOUSERLABELS option. If it is a new file, use the NEW option.
- 153
- MESSAGE
ATTEMPT TO BACKSPACE OVER FROMFILEBOF
- CAUSE
The negative number specified in a "skip end-of-file" function for the fromfile is too large.
- ACTION
Change the number to a smaller one to avoid skipping too many files back.
- 154
- MESSAGE
ATTEMPT TO BACKSPACE OVER TOFILEBOF
- CAUSE
The negative number specified in a "skip end-of-file" function for the tofile is too large.
- ACTION
Change the number to a smaller one to avoid skipping too many files back.
- 155
- MESSAGE
DEBLOCK OPTION: INVALID LOGICAL RECORD LENGTH
- CAUSE
Specified logical record length is greater than the physical record length of the fromfile, or it is equal to zero.
- ACTION
Correct the DEBLOCK option and retry the operation. Make sure that there is a minus sign in front of the logical record length if it is specified in bytes.
- 200 *
- MESSAGE
WARNING: FROMFILE RECSIZE IS number type, TOFILE RECSIZE IS number type
- CAUSE
The record sizes of the fromfile and tofile are not identical.
- ACTION
In a job: FCOPY performs the specified operation despite the conflict. In a session: you are given the choice of whether or not to continue the operation. If the record size of the fromfile is larger than that of the tofile, the "from" records would be truncated. If the record size of the tofile is larger than that of the fromfile, the content of the excess byte positions in the "to" records is unpredictable.
- 201 *
- MESSAGE
WARNING: FROMFILE IS ASCII, TOFILE IS BINARY OR WARNING: FROMFILE IS BINARY, TOFILE IS ASCII
- CAUSE
The data formats of the fromfile and tofile are not identical.
- ACTION
In a job: FCOPY performs the specified operation despite the conflict. In a session: you are given the choice of whether or not to continue the operation.
- 301
- MESSAGE
READ ERROR IN FROMFILE AT RECORD recnum
- CAUSE
An error occurred while reading from the fromfile at the record number displayed (recnum).
- ACTION
Retry the operation. If the error persists, use the SUBSET function to copy all of the file except the erroneous record.
- 302
- MESSAGE
VERIFY OPTION: RAN OUT OF VERIFY ERRORS AT FROMFILE RECORD recnum
- CAUSE
The "verify" function was terminated because the specified maximum number of errors has been exceeded at the record number displayed (recnum).
- ACTION
Specify a larger number-of-errors parameter and retry the operation.
- 303
- MESSAGE
RAN OUT OF IGNERRS AT FROMFILESREC
- CAUSE
More errors were found in the fromfile than are permitted by the IGNERR option.
- ACTION
Specify a larger number-of-errors parameter and retry the operation.
- 304
- MESSAGE
COMPARE OPTION: RAN OUT OF COMPARE ERRORS AT FROMFILE RECORD recnum
- CAUSE
The "compare" function was terminated because the specified maximum number of errors has been exceeded at the record number displayed (recnum).
- ACTION
Retry the operation specifying a larger number-of-errors parameter.
- 601
- MESSAGE
END OF VOLUME SET
- CAUSE
The end of the last labeled tape of the volume set has been reached.
- ACTION
None
- 800
- MESSAGE
EOF IN FROMFILE BUT NOT IN TOFILE
{ AT | AFTER | BEFORE } RECORD X
- CAUSE
The tofile is larger than the fromfile.
- ACTION
Purge the tofile and retry the operation using the NEW option if you are copying to the tofile. Alternatively, purge the tofile and rebuild it with the same attributes as the fromfile, then retry the operation.
- 801 *
- MESSAGE
EOF IN TOFILE BUT NOT IN FROMFILE
{ AT | AFTER | BEFORE } RECORD X
- Cause
The tofile is smaller than the fromfile.
- Action
Purge the tofile and retry the operation using the NEW option if you are copying to the tofile. Alternatively, purge the tofile and rebuild it with the same attributes as the fromfile, then retry the operation.
- 802 *
- MESSAGE
READ ERROR IN FROMFILE
{ AT | AFTER | BEFORE } RECORD X
- Cause
A READ error occurred while verifying or comparing.
- Action
Retry the operation and check the MPE/iX file system error.
- 803 *
- MESSAGE
READ ERROR IN TOFILE
{ AT | AFTER | BEFORE } RECORD X
- Cause
A READ error occurred while verifying or comparing,
- Action
Retry the operation and check the MPE/iX file system error.
- 901
- MESSAGE
KSAM FROMFILE BOUNDARY (EOF OR BOF)
- Cause
The beginning or end of the fromfile was reached during the FCOPY operation.
- Action
Try again.
- 902
- MESSAGE
KSAM FROMFILE POSITIONING ERROR
- CAUSE
FCOPY could not find the desired position in the fromfile.
- Action
Try again or check the length of the fromfile.
- 903
- MESSAGE
ERROR: WRONG CONDITIONS FOR OPENING NEW KSAM FILE
- Cause
The fromfile is not a KSAM file.
- Action
Create a KSAM file before running FCOPY and copy to that file.
- 904
- MESSAGE
KSAM ERROR 904
- Cause
Internal error.
- Action
Notify your system manager.
- 905
- MESSAGE
KSAM ERROR 905
- CAUSE
Internal error.
- Action
Notify your system manager.
- 906
- MESSAGE
KSAM ERROR 906
- CAUSE
Internal error.
- ACTION
Notify your system manager.
- 907
- MESSAGE
KSAM ERROR 907
- CAUSE
Internal error.
- ACTION
Notify your system manager.
- 908
- MESSAGE
NOKSAM IS NOT A VALID OPTION FOR KSAM XL FILES
- CAUSE
You have attempted to open a KSAM XL file with the NOKSAM option.
- ACTION
Correct the command syntax and try again.
- 909
- MESSAGE
VARIABLE RECORD FORMAT IS NOT SUPPORTED FOR KSAM XL FILES
- CAUSE
You are using a variable record format with a KSAM XL file.
- ACTION
Rebuild your file with a fixed-record format and try again.
- 930
- MESSAGE
WRONG ACCESS TYPE WHILE COPYING LABEL EXTENSION OF SPOOL FILES
- CAUSE
The tofile has no WRITE access or the fromfile has no READ access.
- ACTION
Use a file equation to give your file the relevant access rights.
- 931
- MESSAGE
ERROR WHILE COPYING LABEL EXTENSION OF SPOOL FILES
- CAUSE
Internal error.
- ACTION
Notify your system manager.
- 950
- MESSAGE
CTRANSLATE ERROR
- CAUSE
Internal error.
- ACTION
Notify your system manager.
- 960
- MESSAGE
LANGUAGE NOT CONFIGURED
- CAUSE
The language is not installed.
- ACTION
Run LANGID.PUB.SYS to install it.
- 961
- MESSAGE
NLS NOT CONFIGURED
- CAUSE
NLS is not installed.
- ACTION
Run LANGID.PUB.SYS to install it.
- 962
- MESSAGE
INTERNAL ERROR (NLINFO)
- CAUSE
Internal error.
- ACTION
Notify your system manager.
- 963
- MESSAGE
INTERNAL ERROR (NLREPCHAR)
- CAUSE
Internal error.
- ACTION
Notify your system manager.
- 964
- MESSAGE
INTERNAL ERROR (NLSCANMOVE)
- CAUSE
Internal error.
- ACTION
Notify your system manager.
- 965
- MESSAGE
INTERNAL ERROR (NLTRANSLATE)
- CAUSE
Internal error.
- ACTION
Notify your system manager.
- 966
- MESSAGE
WARNING: LANG OPTION NOT RELEVANT
- CAUSE
The tofile doesn't need the language.
- ACTION
Do not use the LANG option.
- 970
- MESSAGE
NO EBCDIC TABLE FOR THIS LANGUAGE
- CAUSE
Some languages do not support the EBCDIC function.
- ACTION
Do not use the EBCDIC function.
- 971
- MESSAGE
INVALID 16-BIT INPUT DATA FOR UPSHIFT
- CAUSE
16-bit character truncation.
- ACTION
Check input data and try again.
EOF FOUND IN FROMFILE AFTER RECORD X X RECORDS PROCESSED***Y ERRORS VERIFY ERROR X FOUND AT RECORD Y COMPARE ERROR X FOUND AT RECORD Y IGNORED ERROR X: READ ERROR FROM FROMFILE AT RECORD Y VERIFY ERROR X FOUND AT RECORD Y, BYTE Z COMPARE ERROR X FOUND AT RECORD Y, BYTE Z COMPARE ERROR X FOUND AT RECORD Y: DIFFERENT RECORD
|
FCOPY |
Chapter 5 Error Messages |