| 
|  | » |  | 
 |  | These are the messages you are likely to encounter when you use
the FCOPY subsystem. Message< CONTROL Y >
CauseAcknowledges receipt of a CTRL Y entered during a
session.ActionNone.
MessageREAD ERROR FROM COMMAND INPUTFILE
CauseAn error occurred while reading an FCOPY command from
$STDIN.
ActionIn a job, resubmit the job. 
 In a session, reenter the command.
MessageWRITE ERROR TO COMMAND LISTFILE
CauseAn error occurred while writing an FCOPY message to
$STDLIST.
ActionIt is likely that nothing serious occurred and
all FCOPY operations were performed successfully. To make sure,
however, do the following: In a job, resubmit the job. 
In a session, reenter the most recent FCOPY command.
MessageSYNTAX ERROR:  EOF FOUND IN COMMAND FILE, MISSING
EXIT COMMAND
CauseThe command input file did not contain an EXIT
command.
ActionCorrect the input file.
3
 MessageSYNTAX ERROR: IN SUBSET OPTION
CauseThe SUBSET function was not specified properly.
ActionIn a job, correct the command and resubmit the
job. 
In a session, reenter the command using the correct format.
4
 MessageSYNTAX ERROR: IN TITLE OPTION
CauseThe "title" option of the DISPLAY function was
not specified properly.
ActionIn a job, correct the command and resubmit the
job. 
 In a session, reenter the command using the correct format.
5
 MessageSYNTAX ERROR: IN IGNERR OPTION
CauseThe "ignore errors" function is not specified
properly.
ActionIn a job, correct the command and
resubmit the job.  In a session, reenter the command 
using the correct format.
6
 MessageSYNTAX ERROR: IN VERIFY OPTION
CauseThe "verify" function was not specified properly.
ActionIn a job, correct the command and resubmit the
job.  
In a session, reenter the command using the correct format.
7
 MessageSYNTAX ERROR: IN SKIPEOF OPTION
CauseThe "skip end-of-file" function was not specified
properly.
ActionIn a job, correct the command and
resubmit the job.   In a session, reenter the command
using the correct format.
8
 MessageSYNTAX ERROR: IN COMPARE OPTION
CauseThe "compare" function was not specified properly.
ActionIn a job, correct the command and
resubmit the job. 
In a session, reenter the command using
the correct format.
9
 MessageSYNTAX ERROR: IN NEW OPTION
CauseThe "new file" function was not specified properly.
ActionIn a job, correct the command and
resubmit the job.  In a session, reenter the command
using
the correct format.
10
 MessageSYNTAX ERROR: IN HEX OPTION
CauseThe hexadecimal display function was not specified.
ActionIn a job, correct the command and
resubmit the job.  In a session, reenter the command
using the correct format.
11
 MessageSYNTAX ERROR: IN EBCDICOUT OPTION
CauseThe EBDICOUT character translation function was
not
specified properly.
ActionIn a job, correct the command and resubmit
the job.  In a session, reenter the command using
the correct format.
12
 MessageSYNTAX ERROR: IN CHAR OPTION
CauseThe "display character" function was not specified
properly.
ActionIn a job, correct the command and resubmit
the job.  In a session, reenter the command using
the correct format.
13
 MessageSYNTAX ERROR: IN OCTAL OPTION
CauseThe "display octal" function was not specified
properly.
ActionIn a job, correct the command and resubmit
the job.  In a session, reenter the command using
the correct format.
14
 MessageSYNTAX ERROR: IN UPSHIFT OPTION
CauseThe "upshift" function was not specified properly.
ActionIn a job, correct the command and resubmit
the job.  In a session, reenter the command using
the correct format.
15
 MessageSYNTAX ERROR: IN BCDICIN OPTION
CauseThe BCDICIN character translation function was not
specified properly.
ActionIn a job, correct the command and resubmit
the job.   In a session, reenter the command using
the correct format.
16
 MessageSYNTAX ERROR: IN NORECNUM OPTION
CauseThe NORECNUM option of the display function was
not
specified properly.
ActionIn a job, correct the command and resubmit
the job.  In a session, reenter the command using
the correct format.
17
 MessageSYNTAX ERROR: IN EBCDICIN OPTION 
CauseThe EBCDICIN character translation function was
not
specified properly.
ActionIn a job, correct the command and resubmit
the job.   In a session, reenter the command using
the correct format.
18
 MessageSYNTAX ERROR: IN BCDICOUT OPTION 
CauseThe BCDICOUT character translation function was
not
specified properly 
ActionIn a job, correct the command and resubmit
the job.  In a session, reenter the command using
the correct format.
19
 MessageSYNTAX ERROR: INVALID FORM OF EXIT COMMAND 
CauseThe EXIT command was not specified properly.
 
ActionNone. FCOPY terminates.
51
 MessageSYNTAX ERROR: IN QUOTED STRING 
CauseThe characterstring specified for the SUBSET
function is not valid. 
ActionIn a job, correct the command and resubmit
the job.  In a session, reenter the command using
the correct format.
52
 MessageSYNTAX ERROR: IN BIT PATTERN 
CauseThe patternlist specified for the SUBSET
function
is not valid. 
ActionIn a job, correct the command and resubmit
the job.  In a session, reenter the command using
the correct format.
53
 MessageSYNTAX ERROR: INVALID INTEGER 
CauseAn integer specified in the command is outside the
range allowed
for the particular COPY function. 
ActionIn a job, correct the command and resubmit
the job.  In a session, reenter the command using
the correct format.
54
 MessageSYNTAX ERROR; UNKNOWN OPTION
CauseOne 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. 
ActionIn a job, correct the command and resubmit
the job.  In a session, reenter the command using
the correct format.
55
 MessageSYNTAX ERROR: IN FROMFILE SPECIFIER 
CauseThe fromfile was not specified properly.
 
ActionIn a job, correct the command and resubmit the
job.  In a session, reenter the command using the
correct format.
56
 MessageSYNTAX ERROR:  IN TOFILE SPECIFIER 
CauseThe tofile was not specified properly.
ActionIn a job, correct the command and resubmit the
job.  In a session, reenter the command using the
correct format.
57
 MessageSYNTAX ERROR: ILLEGAL COMBINATION OF OPTIONS
CauseTwo or more "functionlist" entries conflict with one
another. 
ActionIn a job, correct the command and resubmit the
job.  In a session, reenter the command using the
correct format.
58
 MessageSYNTAX ERROR: FROMFILE AND TOFILE NOT BOTH
SPECIFIED
CauseFROM= and TO= were not both specified in
the FCOPY
command. 
ActionIn a job, correct the command and resubmit the
job.   In a session, reenter the command using the
correct format.
59
 MessageSYNTAX ERROR: ILLEGAL USE OF NEW 
CauseThe context used to specify a new tofile is not
valid. 
ActionIn a job, correct the command and resubmit the
job.  In a session, reenter the command using the
correct format.
60
 MessageSYNTAX ERROR: ILLEGAL USE OF *
CauseThe context used to specify * as a fromfile or
tofile is not valid. 
ActionIn a job, correct the command and resubmit the
job.  In a session, reenter the command using the
correct format.
62
 MessageSYNTAX ERROR: FILE NAME TOO LONG 
CauseThe name specified for the fromfile or tofile
is
longer than the 35 characters allowed in a fully qualified file
name with lockword.
ActionIn a job, correct the command and resubmit the
job.  In a session, reenter the command using the
correct format.
102
 MessageCANNOT CLOSE FROMFILE 
CauseMPE cannot close the fromfile. This message is
followed by an MPE file information display containing (among
other things) an error number. 
ActionLook up the error number in the file system error
table in the  MPE V Intrinsics Reference Manual
(30000-90010) or the MPE XL Error Message Manual Volumes 1 and 2 (32650-90066 and 32650-90152) and act accordingly.
103
 MessageCANNOT CLOSE TOFILE 
CauseMPE cannot close the tofile. This message is
followed by an MPE file information display containing an error
number.  Usually, this occurs when the file being created already exists.  (It was created after the NEW file checking code determined that the file did not exist.)
ActionLook up the error number in the file system error
table in the  MPE V Intrinsics Reference Manual
(30000-90010) or the MPE XL Error Message Manual Volumes 1 and 2 (32650-90066 and 32650-90152) and act accordingly.
104
 MessageCANNOT SAVE NEW TOFILE 
CauseMPE 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. 
ActionIf 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
 MessageCANNOT OPEN FROMFILE 
CauseMPE cannot open the fromfile. This message is
followed by an MPE file information display containing an error
number. 
ActionLook up the error number in the file system error
table in the  MPE V Intrinsics Reference Manual
(30000-90010) or the MPE XL Error Message Manual Volumes 1 and 2 (32650-90066 and 32650-90152) and act accordingly.
106
 MessageCANNOT OPEN TOFILE 
CauseMPE cannot open the tofile. This message is
followed by an MPE file information display containing an error
number.
ActionLook up the error number in the file system error
table in the MPE V Intrinsics Reference Manual
(30000-90010) or the MPE XL Error Message Manual Volumes 1 and 2 (32650-90066 and 32650-90152) and act accordingly.
107
 MessageVERIFY OR COMPARE OPTION: CANNOT GET READ ACCESS
TO TOFILE
CauseMPE cannot get read access to the tofile for a
verify or a compare operation. The read access
specified in the file label has been overridden by an MPE
FILE command
containing ACC=APPEND, ACC=OUT, or ACC=OUTKEEP.
ActionReset the FILE command (using the MPE
RESET command) and retry the operation.
108
 MessageERROR IN CALLING FGETINFO FOR FROMFILE 
CauseAn error prevented MPE from obtaining information from
the fromfile's label. This message is followed by an MPE file
information display containing an error number. 
ActionLook up the error number in the file system error
table in the   MPE V Intrinsics Reference Manual
(30000-90010) or the MPE XL Error Message Manual Volumes 1 and 2 (32650-90066 and 32650-90152) and act accordingly.
109
 MessageERROR IN CALLING FGETINFO FOR TOFILE 
CauseAn error prevented MPE from obtaining information from
the tofile's label. This message is followed by an MPE file
information display containing an error number. 
ActionLook up the error number in the file system error
table in the   MPE V Intrinsics Reference Manual
(30000-90010) or the MPE XL Error Message Manual Volumes 1 and 2 (32650-90066 and 32650-90152) and act accordingly.
110
 MessageIGNERR OPTION: FROMFILE NOT TAPE 
CauseThe fromfile's device is not a magnetic tape unit.
 
ActionThe "ignore errors" function cannot be used in this
case.
111
 MessageCANNOT GET READ ACCESS TO FROMFILE 
CauseMPE cannot get read access to the fromfile.
The
read access specified by FCOPY has been overridden
by an
MPE FILE command containing ACC=APPEND, ACC=OUT, or
ACC=OUTKEEP.
ActionReset the FILE command (using the MPE
RESET command) and retry the operation.
112
 MessageCANNOT GET WRITE ACCESS TO TOFILE 
CauseMPE cannot get read access to the tofile. The
write access specified by FCOPY has been overridden
by
an MPE FILE command containing ACC=IN. 
ActionReset the particular FILE command (using the MPE
RESET command) and retry the operation.
113
 MessageSKIPEOF OPTION: FROMFILE NOT AN UNLABELED TAPE 
CauseThe "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 containing unlabeled media. 
ActionIf the intended fromfile or tofile is on
magnetic tape or serial disk, check the associated MPE FILE
command and its backreference.
114
 MessageSKIPEOF OPTION: TOFILE NOT AN UNLABELED TAPE
CauseThe "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 containing unlabeled media. 
ActionIf the intended fromfile or tofile is on
magnetic tape or serial disk, check the associated MPE FILE
command and its backreference.
115
 MessageSUBSET OPTION: STRING FALLS OUTSIDE OF FROMFILE RECSIZE
CauseThe characterstring or patternlist specified
extends beyond the record size of the fromfile. No such
subset can exist in the specified fromfile. 
ActionChange the specified subset definition to a valid one
and try the operation again.
116
 MessageCANNOT GET LARGE ENOUGH BUFFER 
CauseThere 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. 
ActionAsk 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
 MessageSKIPEOF OPTION: ERROR WHILE SKIPPING IN FROMFILE
CauseAn error occurred while skipping end-of-file marks in
the fromfile. 
ActionCheck the syntax for the SKIPEOF function and
retry the
operation.
118
 MessageSKIPEOF OPTION: ERROR WHILE SKIPPING IN TOFILE 
CauseAn error occurred while skipping end-of-file marks in
the tofile.
ActionCheck the syntax for the SKIPEOF function and
retry the
operation.
119
 MessageSUBSET OPTION: ERROR WHILE SPACING IN FROMFILE
CauseAn error occurred while skipping end-of-file marks in
the fromfile. 
ActionCheck the syntax for the SKIPEOF function and
retry the
operation.
120
 MessageSUBSET OPTION: SUBSET STARTS OVER EOF BOUNDARY 
CauseThe specified subset extends over an end-of-file mark
or a tape mark boundary. 
ActionChange the specified subset definition to a valid one
and try the operation again.
123
 MessageSUBSET OPTION: THIS INPUT DEVICE DOES NOT
BACKSPACE
CauseThe specified subset requires backspacing in the
fromfile, but the device for that file is not a disk or
magnetic tape.
ActionCheck the MPE FILE command associated with the
fromfile and its backreference.
124
 MessageREAD ERROR IN FROMFILE AT RECORD RECNUM 
CauseAn error occurred while spacing through the
fromfile in search of the start of a subset. 
ActionCheck the syntax of your command and retry the
operation.
125
 MessageSUBSET OPTION: NUMERIC SUBSET IS EMPTY 
CauseA subset specified by starting-record-number,
number-of records and/or last-record-number does not exist,
or contains no data.
ActionChange the specified subset definition to a valid one
and try the operation again.
126
 MessageVERIFY OPTION: ERROR WHILE REWINDING FROMFILE
CauseAn error occurred while spacing backward to the
beginning of the fromfile at the start of a "verify"
operation.
ActionCheck the syntax of your command and retry the
operation.
127
 MessageVERIFY OPTION: ERROR WHILE REWINDING TOFILE
CauseAn error occurred while spacing backward to the
beginning of the tofile at the start of a "verify" operation.
ActionCheck the syntax of your command and retry the
operation.
128
 MessageEOF FOUND WHILE SPACING IN FROMFILE 
CauseAn end-of-file mark was encountered while spacing
through the fromfile in search of the start of a subset. 
ActionMake sure that the starting record number for the
subset does not exceed the number of records in the file.
129
 MessageEOF FOUND WHILE SPACING IN TOFILE 
CauseAn 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.
ActionIn a compare operation, the fromfile and tofiles
are not identical. Display the tofile to determine what it
actually contains.  
In a verify operation, the copy operation was not
performed correctly. Retry the operation.
130
 MessageFCHECK ERROR 
CauseThe FCHECK intrinsic failed. 
ActionNotify your system manager.
131
 MessageERROR WHILE WRITING EOF TOFILE 
CauseAn error occurred while writing an end-of-file mark in
the tofile.
ActionCheck the syntax of your command and retry the
operation.
132
 MessageVERIFY OPTION: ERROR WHILE SPACING IN THE
FROMFILE
CauseAn error occurred while writing an end-of-file mark in
the fromfile during a "verify" operation. 
ActionCheck the syntax of your command and retry the
operation.
133
 MessageVERIFY OPTION: ERROR WHILE SPACING IN THE TOFILE
CauseAn error occurred while writing an end-of-file mark in
the tofile during a "verify" operation. 
ActionCheck the syntax of your command and retry the
operation.
134
 MessageFOUND EOF IN TOFILE 
CauseFCOPY has performed the specified operation but has
filled the tofile before completing the operation. 
ActionThe tofile was not large enough. Use the MPE
LISTF filename,2 command to determine the tofile's
size and then increase its size (using the MPE PURGE and
BUILD
commands) and retry the operation. To copy from one file to a
smaller file, use SUBSET=.
135
 MessageWRITE ERROR TO TOFILE 
CauseAn error occurred while writing to the tofile.
ActionCheck the syntax of your command and retry the
operation.
136
 MessageREAD ERROR FROM TOFILE 
CauseAn error occurred while reading from the tofile
during a "compare" or "verify" operation. 
ActionIn a compare operation, retry the operation. If the
error persists, you must try to recreate the tofile. 
In a verify operation, retry the operation.
137 *
 MessageWARNING: AN UNLABELED TAPE OPERATION ENDS ON AN
ERROR 
CauseAn 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. 
ActionThis is not an error. You can avoid this message by
specifying FILES=n where n is the number of files on
the tape.
138
 MessageTITLE OPTION: TITLE TOO LONG 
CauseThe title specified for the "list" function is longer
than the 70 characters allowed, or it extends over more than one
line (record).
ActionIn a job, correct the command and resubmit the
job.  In a session, reenter the command using the
correct format.
139
 MessageDUMP OPTION: TOFILE RECSIZE NOT WITHIN LEGAL
LIMIT
CauseA 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). 
ActionChange the record size of the intermediate
storage file (using the MPE PURGE and BUILD commands) so
that it is within the allowed range, and then retry the
operation.
140
 MessageCOMPARE OR VERIFY OPTION: OPERATION FAILS; DIFFERENT FIXED RECSIZESCauseThe "compare" or "verify" operation was not attempted
because the record sizes of the tofile and fromfile are not identical. 
ActionIn a compare operation, none. The compare operation
revealed that the fixed record sizes of the two files are not
identical. 
In a verify operation, change the record size of the tofile
(using the MPE PURGE and BUILD commands) so that it is
the same
as that of the fromfile and then retry the operation.
141 **
 MessageCOMPARE BEGINS 
CauseThe comparison phase of a "verify" operation has
begun.
ActionNone.
143 *
 MessageWARNING: FROMFILE IS EMPTY 
CauseThe fromfile contained no data. Nothing was copied
or compared. 
ActionNone. You may inadvertently have specified the wrong
file as the fromfile.
144
 MessageNEW OPTION: FILE ALREADY EXISTS
CauseThe tofile named for the "new file" function
already
exists in the specified (or implied) group and account. 
ActionChange the name of the tofile and try the
operation again.
145
 MessageBACKSPACE ERROR IN FROMFILE 
CauseAn error occurred while spacing backward to the
beginning of the fromfile or a subset within it. 
ActionCheck the syntax of your command and retry the
operation.
146
 MessageCANNOT OPEN TEMPORARY LABEL FILE 
CauseThis may indicate a lack of space in your account. 
ActionAllocate more space in the account.
147
 MessageWRITE ERROR IN TEMPORARY LABEL FILE 
CauseAn error occurred while writing to the temporary label
file. 
ActionCheck the syntax of your command and retry the
operation.
148
 MessageREAD ERROR IN TEMPORARY LABEL FILE 
CauseAn error occurred while reading from the fromfile.
ActionCheck the syntax of your command and retry the
operation.
149
 MessageOVERFLOW IN TEMPORARY LABEL FILE 
CauseThere are more labels in the fromfile than can be
copied. 
ActionUse the NOUSERLABELS function to copy files
without labels.
150
 MessageREAD ERROR IN FROMFILE LABELS 
CauseAn error occurred while reading labels in the
fromfile.
ActionCheck the syntax of your command and retry the
operation.
151
 MessageWRITE ERROR IN TOFILE LABELS 
CauseAn error occurred while reading labels in the
tofile.
ActionCheck the syntax of your command and retry the
operation.
152
 MessageOVERFLOW IN TOFILE LABELS 
CauseThere are too many labels in the fromfile to be
copied to the tofile. 
ActionIf the tofile is an old file, retry the operation
using the NOUSERLABELS option. If it is a new file, use the
NEW option.
153
 MessageATTEMPT TO BACKSPACE OVER FROMFILEBOF 
CauseThe negative number specified in a "skip end-of-file"
function for the fromfile is too large. 
ActionChange the number to a smaller one to avoid skipping
too many files back.
154
 MessageATTEMPT TO BACKSPACE OVER TOFILEBOF
CauseThe negative number specified in a "skip end-of-file"
function for the tofile is too large. 
ActionChange the number to a smaller one to avoid skipping
too many files back.
155
 MessageDEBLOCK OPTION: INVALID LOGICAL RECORD LENGTH 
CauseSpecified logical record length is greater than
the physical record length of the fromfile, or it is equal to
zero. 
ActionCorrect 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 *
 MessageWARNING: FROMFILE RECSIZE IS number
type, TOFILE RECSIZE IS number type
CauseThe record sizes of the fromfile and tofile
are not identical. 
ActionIn 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 will be blanks if the tofile is ASCII, and zeros otherwise.
201 *
 MessageWARNING: FROMFILE IS ASCII, TOFILE IS BINARY or WARNING: FROMFILE IS BINARY, TOFILE IS ASCIICauseThe data formats of the fromfile and tofile
are not identical. 
ActionIn 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
 MessageREAD ERROR IN FROMFILE AT RECORD recnum
CauseAn error occurred while reading from the fromfile
at the record number displayed (recnum). 
ActionRetry the operation. If the error persists, use the
SUBSET function to copy all of the file except the erroneous
record.
302
 MessageVERIFY OPTION: RAN OUT OF VERIFY ERRORS AT
FROMFILE
RECORD recnum
CauseThe "verify" function was terminated because the
specified maximum number of errors has been exceeded at the
record number displayed (recnum). 
ActionSpecify a larger number-of-errors parameter and
retry the
operation.
303
 MessageRAN OUT OF IGNERRS AT FROMFILESREC 
CauseMore errors were found in the fromfile than are
permitted by the IGNERR option. 
ActionSpecify a larger number-of-errors parameter and
retry the operation.
304
 MessageCOMPARE OPTION: RAN OUT OF COMPARE ERRORS AT FROMFILE RECORD recnum
CauseThe "compare" function was terminated because the
specified maximum number of errors has been exceeded at the
record number displayed (recnum). 
ActionRetry the operation specifying a larger
number-of-errors parameter.
601
 MessageEND OF VOLUME SET 
CauseThe end of the last labeled tape of the volume set has
been reached. 
ActionNone.
800
 MessageEOF IN FROMFILE BUT NOT IN TOFILE
 | 
             { AT
               AFTER
               BEFORE } RECORD X
 | 
CauseThe tofile is larger than the fromfile to which it is being compared. 
ActionNone.
801 *
 MessageEOF IN TOFILE BUT NOT IN FROMFILE
 | 
             { AT
               AFTER
               BEFORE } RECORD X
 | 
CauseThe tofile is smaller than the fromfile to which it is being compared. 
ActionNone.
802 *
 MessageREAD ERROR IN FROMFILE
 | 
             { AT
               AFTER
               BEFORE } RECORD X
 | 
CauseA read error occurred while verifying or
comparing. 
ActionRetry the operation and check the MPE file system
error.
803 *
 MessageREAD ERROR IN TOFILE
 | 
             { AT
               AFTER
               BEFORE } RECORD X
 | 
CauseA read error occurred while verifying or
comparing, 
ActionRetry the operation and check the MPE file system
error.
901
 MessageKSAM FROMFILE BOUNDARY (EOF OR BOF) 
CauseThe beginning or end of the fromfile was reached
during the FCOPY operation. 
ActionTry again.
902
 MessageKSAM FROMFILE POSITIONING ERROR 
CauseFCOPY could not find the desired position in the
fromfile. 
ActionTry again or check the length of the fromfile.
903
 MessageERROR: WRONG CONDITIONS FOR OPENING NEW KSAM
FILE
CauseThe fromfile is not a KSAM file. 
ActionCreate a KSAM file before running FCOPY and copy to
that file.
904
 MessageKSAM ERROR 904 
CauseInternal error. 
ActionNotify your system manager.
905
 MessageKSAM ERROR 905 
CauseInternal error. 
ActionNotify your system manager.
906
 MessageKSAM ERROR 906 
CauseInternal error. 
ActionNotify your system manager.
907
 MessageKSAM ERROR 907 
CauseInternal error. 
ActionNotify your system manager.
908
 MessageNOKSAM IS NOT A VALID OPTION FOR KSAM XL FILES
CauseYou have attempted to open a KSAM XL file with the NOKSAM option.
ActionCorrect the command syntax and try again.
909
 MessageVARIABLE RECORD FORMAT IS NOT SUPPORTED FOR KSAM XL FILES
CauseYou are using a variable record format with a KSAM XL file.
ActionRebuild your file with a fixed-record format and try again.
910
 MessageERROR DELETING TO FILE ACD 
CauseInternal error. 
ActionNotify your system manager.
911
 MessageERROR DELETING TO FILE  ACD 
CauseInternal error. 
ActionNotify your system manager.
912
 MessageUSER CAN'T ACCESS FROMFILE ACD 
CauseCOPYACD was specified for a file to which you have insufficient access rights.
ActionRetry without specifying COPYACD.
913
 MessageUSER CAN'T ACCESS FROMFILE ACD 
CauseCOPYACD was specified for a file to which you have insufficient access rights.
ActionRetry without specifying COPYACD.
914
 MessageERROR COPYING ACD TO NEW TOFILE 
CauseInternal error. 
ActionNotify your system manager.
915 *
 MessageWARNING: NO SOURCE ACD 
CauseCOPYACD option specified but the fromfile
doesn't have an ACD.  Note that on MPE XL release 3.0 or later, this message is not displayed if the COPYACD option is not used and the file does not contain an ACD.
ActionQuit or continue to copy only the data from the
fromfile.
916 *
 MessageWARNING: COPYACD NOT RELEVANT 
CauseCOPYACD option should be specified only if the
tofile is a local disk file.  Note that on MPE XL release 3.0 or later, this message is not displayed if the COPYACD option is not used and the file does not contain an ACD.
ActionQuit or continue to copy only the data from the
fromfile.
930
 MessageWRONG ACCESS TYPE WHILE COPYING LABEL EXTENSION OF SPOOL FILES 
CauseThe tofile has no write access, or the fromfile has no
read access.
ActionUse a file equation to give your file the relevant access rights.
931
 MessageERROR WHILE COPYING LABEL EXTENSION OF SPOOL FILES
CauseInternal error. 
ActionNotify your system manager.
950
 MessageCTRANSLATE ERROR 
CauseInternal error. 
ActionNotify your system manager.
960
 MessageLANGUAGE NOT CONFIGURED 
CauseThe language is not installed. 
ActionRun LANGID.PUB.SYS to install it.
961
 MessageNLS NOT CONFIGURED 
CauseNLS is not installed. 
ActionRun LANGID.PUB.SYS to install it.
962
 MessageINTERNAL ERROR (NLINFO) 
CauseInternal error. 
ActionNotify your system manager.
963
 MessageINTERNAL ERROR (NLREPCHAR) 
CauseInternal error. 
ActionNotify your system manager.
964
 MessageINTERNAL ERROR (NLSCANMOVE) 
 
CauseInternal error. 
ActionNotify your system manager.
965
 MessageINTERNAL ERROR (NLTRANSLATE) 
CauseInternal error. 
ActionNotify your system manager.
966
 MessageWARNING: LANG OPTION NOT RELEVANT 
CauseThe tofile doesn't need the language. 
ActionDo not use the LANG option.
970
 MessageNO EBCDIC TABLE FOR THIS LANGUAGE 
CauseSome languages do not support the EBCDIC function.
ActionDo not use the EBCDIC function.
971
 MessageINVALID 16-BIT INPUT DATA FOR UPSHIFT 
Cause16-bit character truncation. 
ActionCheck input data and try again.
The following status messages, without assigned numbers, may also
be given.  They are self-explanatory. | 
   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
 | 
 |