Appendix A ERROR MESSAGES AND RECOVERY PROCEDURES

This appendix lists the error messages that may be issued as a result of errors encountered while accessing KSAM files. The messages are not limited to KSAM errors since other file system errors or language errors can occur while accessing a KSAM file.

Whenever possible, the reason the message was issued is listed under "Meaning" and any action that can be taken to correct the error is listed under "Action."

The messages are contained in the following tables:

Table A-1 “File System Error Codes” File System Error Codes
Table A-2 “COBOL Status Parameter Return Values” COBOL Status Returns
Table A-3 “BASIC Status Parameter Return Values” BASIC Status Returns
Table A-4 “KSAMUTIL Error Codes and Messages” KSAMUTIL Error Codes and Messages
Table A-5 “FCOPY Warning and Error Messages” FCOPY Warning and Error Messages

Table A-1 File System Error Codes

CODE	MEANING	ACTION
0	END OF FILE
1	ILLEGAL DB REGISTER
2	ILLEGAL CAPABILITY
3	OMITTED PARAMETER
4	INCORRECT S REGISTER
5	PARAMETER ADDRESS VIOLATION
6	PARAMETER END ADDRESS VIOLATION
7	ILLEGAL PARAMETER
8	PARAMETER VALUE INVALID
9	INCORRECT Q REGISTER
20	INVALID OPERATION
2l	DATA PARITY ERROR
22	SOFTWARE TIME-OUT
23	END OF TAPE
24	UNIT NOT READY
25	NO WRITE-RING ON TAPE
26	TRANSMISSION ERROR
27	I/O TIME-OUT
28	TIMING ERROR OR DATA OVERRUN
29	SIO FAILURE
30	UNIT FAILURE
31	END OF LINE
32	SOFTWARE ABORT
33	DATA LOST
34	UNIT NOT ON-LINE
35	DATA-SET NOT READY
36	INVALID DISC ADDRESS
37	INVALID MEMORY ADDRESS
38	TAPE PARITY ERROR
39	RECOVERED TAPE ERROR
40	OPERATION INCONSISTENT WITH ACCESS TYPE
41	OPERATION INCONSISTENT WITH RECORD TYPE
42	OPERATION INCONSISTENT WITH DEVICE TYPE
43	WRITE EXCEEDS RECORD SIZE
44	UPDATE AT RECORD ZERO
45	PRIVILEGED FILE VIOLATION
46	OUT OF DISC SPACE
47	I/O ERROR ON FILE LABEL
48	INVALID OPERATION DUE TO MULTIPLE FILE ACCESS
49	UNIMPLEMENTED FUNCTION
50	NONEXISTENT ACCOUNT
51	NONEXISTENT GROUP
52	NONEXISTENT PERMANENT FILE
53	NONEXISTENT TEMPORARY FILE
54	INVALID FILE REFERENCE
55	DEVICE UNAVAILABLE
56	INVALID DEVICE SPECIFICATION
57	OUT OF VIRTUAL MEMORY
58	NO PASSED FILE
59	STANDARD LABEL VIOLATION
60	GLOBAL RIN UNAVAILABLE
61	OUT OF GROUP DISC SPACE
62	OUT OF ACCOUNT DISC SPACE
63	USER LACKS NON-SHARABLE DEVICE CAPABILITY
64	USER LACKS MULTI-RIN CAPABILITY
71	TOO MANY FILES OPEN
72	INVALID FILE NUMBER
73	BOUNDS VIOLATION
80	SPOOFLE SIZE EXCEEDS CONFIGURATION
81	NO "SPOOL" CLASS IN SYSTEM
82	INSUFFICIENT SPACE FOR SPOOFLE
83	I/O ERROR ON SPOOFLE
84	DEVICE UNAVAILABLE FOR SPOOFLE
85	OPERATION INCONSISTENT WITH SPOOLING
86	NONEXISTENT SPOOFLE
87	BAD SPOOFLE BLOCK
89	POWER FAILURE
90	EXCLUSIVE VIOLATION: FILE BEING ACCESSED
91	EXCLUSIVE VIOLATION: FILE ACCESSED EXCLUSIVELY
92	LOCKWORD VIOLATION
93	SECURITY VIOLATION
94	USER IS NOT CREATOR
100	DUPLICATE PERMANENT FILE NAME
101	DUPLICATE TEMPORARY FILE NAME
102	I/O ERROR ON DIRECTORY
103	PERMANENT FILE DIRECTORY OVERFLOW
104	TEMPORARY FILE DIRECTORY OVERFLOW
106	EXTENT SIZE EXCEEDS MAXIMUM
107	INSUFFICIENT SPACE FOR USER LABELS
108	DEFECTIVE FILE LABEL ON DISC
110	ATTEMPT TO SAVE PERMANENT FILE AS TEMPORARY
111	USER LACKS SAVE FILE CAPABILITY
112
↓	RESERVED FOR FUTURE USE
169
170	THE RECORD IS MARKED DELETED. FPOINT POSITIONED POINTER TO A RECORD THAT WAS MARKED FOR DELETION.
171	DUPLICATE KEY VALUE WHEN DUPLICATES NOT ALLOWED.
172	KEY NOT FOUND; NO SUCH KEY VALUE.
173	`tcount` PARAMETER LARGER THAN RECORD SIZE.
174	CANNOT GET EXTRA DATA SEGMENT FOR THIS FILE.
175	KSAM INTERNAL ERROR. A KEY VALUE (NOT SEARCH KEY) FOR A RECORD TO BE DELETED IS NOT IN KEY FILE; RECORD CANNOT BE DELETED.
176	ILLEGAL EXTRA DATA SEGMENT LENGTH.
177	TOO MANY EXTRA DATA SEGMENTS FOR THIS PROCESS
178	NOT ENOUGH VIRTUAL MEMORY FOR EXTRA DATA SEGMENT	INCREASE THE SIZE OF VIRTUAL MEMORY
179	THE FILE MUST BE LOCKED BEFORE THIS INTRINSIC ISSUED	USE FLOCK TO LOCK FILE OR OPEN FILE FOR EXCLUSIVE ACCESS.
180	THE KSAM FILE MUST BE REBUILT BECAUSE THIS VERSION OF KSAM DOES NOT HANDLE THE FILE BUILT BY PREVIOUS VERSION.	USE FCOPY TO REBUILD FILE: >FROM=`oldksamfile` ;TO=(`dfile,kfile`)
181	INVALID KEY STARTING POSITION.
182	FILE IS EMPTY.
183	RECORD DOES NOT CONTAIN ALL THE KEYS.
184	INVALID RECORD NUMBER. RECORD NUMBER IS NEGATIVE, OUT OF RANGE, OR DELETED.	RECORD NUMBER MUST BE POSITIVE INTEGER.
185	SEQUENCE ERROR IN PRIMARY KEY; ATTEMPT TO WRITE RECORD WITH PRIMARY KEY LESS THAN PREVIOUS KEY WHEN ASCENDING SEQUENCE EXPECTED.
186	INVALID KEY LENGTH.
187	INVALID KEY SPECIFICATION; KEYS ILLEGAL.
188	INVALID DEVICE SPECIFICATION.
189	INVALID RECORD FORMAT.
190	INVALID KEY BLOCKING FACTOR VALUE.
191	RECORD DOES NOT CONTAIN SEARCH KEY FOR DELETION. SPECIFIED KEY VALUE POINTS TO RECORD WHICH DOES NOT CONTAIN THAT VALUE.
192	SYSTEM FAILURE OCCURRED WHILE KSAM FILE WAS OPENED	RUN KEY INFO OF KSAMUTIL TO RESET FLAG.
193	$STDIN/$STDINX CANNOT BE REDIRECTED TO KSAM FILES.
194	KSAM FILES NOT ALLOWED FOR GLOBAL AFT'S.
195	GLOBAL FILES CANNOT BE REMOTE FILES.
196	LANGUAGE NOT SUPPORTED.
197	NATIVE LANGUAGE INTERNAL ERROR.
198	INVALID VERSION NUMBER IN KSAM FILE.
193
↓	RESERVED FOR KSAM
200
201
↓	RESERVED FOR FUTURE USE
255

Table A-2 COBOL Status Parameter Return Values

STATUS VALUE	MEANING	ACTION
"00"	SUCCESSFUL COMPLETION — I/O operation was completed successfully.	None.
"02"	SUCCESSFUL COMPLETION, DUPLICATE KEY — Read or Readbykey read a record whose key value was the same as the equivalent key in the next sequential record; this is not an error since duplicate alternate keys are allowed. Write or rewrite operation was successful; a duplicate key was written for a key that is allowed duplicates.	None required, returned for information only.
"10"	AT END — End-of-file or beginning-of-file reached during sequential or random read. There is no next logical record in ascending key order.	Usually none. This result is a signal to close the file or perform another end-of-file action.
"21"	INVALID KEY, SEQUENCE ERROR — Attempt was made to write a record with a primary key that is out of sequence when the file was opened for sequential access.	Check the primary key value in the record being written. If you don't want sequence checking, re-open the file for random or dynamic access.
"22"	INVALID KEY, DUPLICATE KEY — Attempt was made to write or rewrite a record with a key value that duplicates a key value in an existing record, and duplicates are not allowed.	Check the key values. If possible change them to avoid the duplication. If duplicate keys must be written, create the file again allowing duplicates for the key and then copy the old file to the new file with FCOPY.
"23"	INVALID KEY, NO RECORD FOUND — Attempt to access record identified by a key with CKSTART or CKR EADBY KEY, but no record is found with the specified key value at the specified key location.	Check the keyvalue, keylength, an keylocation parameters in the call, Correct if necessary. If record that cannot be found should be in the file, you may want to list the data file with FCOPY.
"24"	INVALID KEY, BOUNDARY VIOLATION — An attempt was made to write beyond the externally defined end of file.
"30"	LOCK DENIED — File was locked by another process.	Wait until process locking file unlocks it — try again or lock file with lockcond = 1.
"31"	UNLOCK DENIED — File was not locked by calling process.	Before calling CKUN LOCK to unlock a shared file it must have been locked by a call to CK LOCK.
"9n"	FILE SYSTEM ERROR — Where n is a binary number between 0 and 255 corresponding to a File System Error code (Refer to Table A-1 “File System Error Codes”).	Within your program you can call CKERROR to convert the number to a displayable value and then display it. Look up the value in Table A-1 “File System Error Codes” and perform any suggested action.

Note that COBOL error messages 752 and 753 are issued for errors processing KSAM files. (Refer to Table C-2 in the COBOL manual.)

Table A-3 BASIC Status Parameter Return Values

STATUS VALUE	MEANING	ACTION
"00"	SUCCESSFUL COMPLETION — The current I/O operation was completed successfully.	None.
"02"	SUCCESSFUL COMPLETION, DUPLICATE KEY — In a call to BKREAD or BKREADBYKEY, the current key has the same value as the equivalent key in the next sequential record; duplicate keys are allowed. Or in a call to BKWRITE or BKREWRITE, the record just written created a duplicate key value for at least one key for which duplicates are allowed.	None required. Returned for information only.
"10"	AT END — A sequential read was attempted with BKREAD, but there was no next logical record in ascending sequence by key value, or random read attempted to position to record with key value less than lowest value or greater than greatest value.	Usually none. This result is a signal to close the file or perform some other end-of-file function.
"21"	INVALID KEY, SEOUENCE ERROR — BKWRITE attempted; record being written has primary key that is not in sequential order but file was opened for sequence checking. BK REWRITE attempted, but the primary key value was changed since the record being rewritten was read.	Check the primary key value in the record; if you don't want sequence checking, reopen the file with sequence = 0. Check the primary key value. Either change it back to the original value or read the record again before calling BKREWRITE.
"22"	INVALID KEY, DUPLICATE KEY ERROR — BKWRITE or BKREWRITE attempted to write record that contains a duplicate value for a key that is not allowed duplicate values.	Check the key value. If possible change it to a unique value. If duplicate keys must be written, create the file again allowing duplicate values for the key and then copy the old file to the new file.
"23"	INVALID KEY, NO RECORD FOUND — BKSTART or BKR EADBYKEY attempted to locate a record by a key value that could not be found.	Check the key value, and key location parameters. Correct if necessary. If record that cannot be found should be in file, you may want to list data file with FCOPY.
"24"	INVALID KEY, BOUNDARY VIOLATION — BKWRITE attempted to write beyond the externally defined boundaries of the file.	Re-enter command.
"71"	REQUEST DENIED, FILE ALREADY LOCKED — BK LOCK was called with conditional locking and the file was already locked by another user.	Perform some action that does not require exclusive access and then try BK LOCK again. As soon as the other user unlocks the file BKLOCK will work.
"81"	INVALID CALL, WRONG NUMBER OF PARAMETERS — A procedure call had too many or too few parameters.	Check the call syntax and correct; if not sure of error, consult manual.
"82"	INVALID CALL, INVALID PARAMETER — Specified parameter is not the correct type. For example, a string variable was specified where only numeric variables or constants are allowed.	Check the parameter and compare it to the rules specified in this manual for the parameter format.
"83"	INVALID CALL, INSUFFICIENT INTERNAL BUFFER SPACE — The data to be written to the file is too long for the configured internal buffer space.	You can ask the system manager to reconfigure the system, or you may be able to reduce the amount of data being written from parameterlist
"9xxx"	FILE SYSTEM ERROR — An MPE file system error occurred for which the value xxx specifies a 3-digit code between "0" and "255".	Within your program you can call BKER ROR to display a message with the meaning of the code; you can consult Table A-1 “File System Error Codes” for the code meaning.

Table A-4 KSAMUTIL Error Codes and Messages

CODE	MESSAGE	MEANING	ACTION
1000	COMMAND FILE READ ERROR.
1001	COMMAND FILE END OF FILE.
1002	UNKNOWN COMMAND. TYPE HELP.	Command name not recognized.	Type the correct name if you know it; else type HELP.
1003	TOO MANY PARAMETERS FOR THIS COMMAND.	More parameters specified than are allowed.	Check the command syntax and reenter correctly.
1004	COMMAND FILE DATA TRANSMISSION ERROR.
1005	COMMAND TOO LONG.
1006	FILE NAME TOO LONG OR ABSENT.	File name in BUILD command incorrect.	Enter file name of 8 or fewer alphanumeric characters starting with a letter.
1007	'REC' PARAMETER LIST EXHAUSTED.	Too many parameters specified after REC= in BUILD command.	Check syntax and reenter with correct number of parameters.
1008	'REC' RECORD SIZE VALUE INVALID.	Record size in BUILD command is not valid.	Check syntax and reenter with correct value for record size.
1009	'REC' BLOCKING FACTOR VALUE INVALID.	Block factor in BUILD command is not valid.	Check syntax and reenter with correct value for blocking factor.
1010	'REC' RECORD FORMAT VALUE INVALID.	Record format in BUILD command is not F or V.	Enter V for variable length records, F for fixed length, or omit for fixed length.
1011	'REC' RECORD TYPE VALUE INVALID.	Record code in BUILD command is not ASCII or BINARY.	Enter ASCII for ASCIIcode records; BINARY or omit for binary-coded records.
1012	'DEV' DEVICE VALUE ABSENT.	No device specification after DEV= in BUILD command.	Enter legal device name or omit if device class is DISC.
1013	'DEV' DEVICE VALUE INVALID.	Device specification in BUILD command is not valid.	Enter legal device class name or legal logical device number. Refer to System Manager/System Supervisor Manual.
1014	'DEV' DEVICE VALUE TOO LONG OR ABSENT.	DEV= missing device specification or one that is too long.	Enter device name that is 1 to 8 alphanumeric characters, begins with a letter, terminates with nonalphanumeric character; or omit DEV= for DISC; or enter logical device number.
1015	'KEY' SPECIFICATIONS EXCEED LIMIT.	Too many KEY= specifications in BUILD.	Reduce number of keys to a total of 16.
1016	'KEY' CONTAINS TOO MANY PARAMETERS.	More than 5 parameters follow KEY= in BUILD.	Parameters are: keytype, keylocation, keysize, and optionally, keyblocking, and DUP or DUPLICATE.
1017	'KEY' TYPE VALUE INVALID.	Invalid key type specified after KEY= in BUILD.	Key types may be: B, I, D R, L, N, P,*. Enter one of correct types.
1018	'KEY' POSITION VALUE ABSENT.	The key location is missing from KEY= in BUILD command.	Enter required keylocation parameter following keytype type in KEY= specification.
1019	'KEY' POSITION VALUE INVALID.	Invalid keylocation parameter specified after KEY= in BUILD.	Key location is specified as integer between 1 and number of bytes in record.
1020	'KEY' SIZE VALUE REQUIRED AND ABSENT.	The key size is missing from KEY= in BUILD command.	Enter required keysize parameter after keylocation in KEY= specification.
1021	'KEY' SIZE VALUE INVALID.	Invalid keysize parameter specified after KEY= in BUILD.	Key size is specified as the number of bytes in the key; refer to table 02-02 for legal sizes for each key type.
1022	'KEY' BLOCKING FACTOR VALUE INVALID.	Invalid key blocking parameter specified after KEY= in BUILD.	Specify keyblocking as an even number equal to or greater than 4; or omit for key blocks with four keys per block.
1023	CONFLICTING OPTIONS		Check command syntax
1024	MISSING CLOSING QUOTE		Check command syntax
1025	'KEY' 'DUPLICATE' EXPECTED.	Key word DUP or DUPLICATE expected in KEY= specification.	Enter DUP or DUPLICATE or remove terminating commas.
1026	'DISC' MUST BE FOLLOWED BY '='.	Key word DISC in BUILD command was specified without =.	Reenter DISC= followed by up to 3 parameters describing disc file, or omit for defaults.
1027	'DISC' NUMBER OF RECORDS VALUE INVALID.	Value of numrecs parameter to DISC= not a positive integer.	Enter maximum number of records as file size, or omit for default value of 1023 records.
1028	'DISC' NUMBER OF EXTENTS VALUE INVALID.	Value of numextents not in range 1-32.	Enter integer between 1 and 32, or omit for default value of 8 extents.
1029	'DISC' INITIAL ALLOCATION VALUE INVALID.	Value of initalloc not in range 1-32.	Enter integer between 1 and 32, or omit for default value of 1 extent allocated when file is opened.
1030	'LABELS' NOT FOLLOWED BY '=' OR BY TOO MANY PARAMETERS.	Key word LABELS in BUILD command was specified without = or had more than 1 parameter.	Reenter LABELS= followed by one parameter to specify number of user labels, or omit for default of 0.
1031	'LABELS' NUMBER OF LABELS VALUE INVALID.
1032	'FIRSTREC' NOT FOLLOWED BY '=' OR BY TOO MANY PARAMETERS.	Key word FIRSTREC in BUILD command was specified without = or had more than 1 parameter.	Reenter FIRSTREC= followed by starting record number, or omit to start numbering records with zero.
1033	'FIRSTREC' STARTING RECORD NUMBER MUST BE 0 OR 1.	Value other than 0 or 1 entered for first record number.	Enter correct value or omit for default of 0.
1034	'CODE' NOT FOLLOWED BY '=' OR BY TOO MANY PARAMETERS.	Key word CODE in BUILD command was specified without = or had more than one parameter.	Reenter CODE = followed by filecode, or omit for file code of zero.
1035	'CODE' FILE NUMBER VALUE INVALID.	Value not in range 0 through 1023 entered for file code.	Enter positive integer between 0 and 1023, or omit for default of 0.
1036	'KEYDEV' FOLLOWED BY TOO MANY PARAMETERS.	Key word KEYDEV= in BUILD command was specified with more than 1 parameter.	Reenter with one parameter to specify device class or logical device number of key file, or omit for DISC.
1037	'KEYDEV' MUST BE FOLLOWED BY'='.	Key word KEYDEV= not followed by =.	Reenter KEYDEV=, or omit for default device class DISC.
1038	'KEYDEV' DEVICE PARAMETER VALUE TOO LONG OR ABSENT.	Key word KEYDEV= must be followed by valid device parameter.	Reenter with device class specified as 1 to 8 alphanumeric characters beginning with letter, terminated by non-alphanumeric character, or reenter with logical device number, or omit for default DISC.
1039	'KEYFILE' NOT FOLLOWED BY '=' OR BY TOO MANY PARAMETERS.	Key word KEYFILE in BUILD command was specified without = or had more than 1 parameter.	Reenter KEYENTITY = followed by actual file designator of key file.
1040	KEY FILE NAME TOO LONG OR ABSENT.	File name specified as KEYENTITY = parameter is more than 8 characters or was omitted.	Reenter KEYENTITY = with correct file name format. (Refer to BUILD description in manual.)
1041	'KEYENTRIES' NOT FOLLOWED BY '=' OR BY TOO MANY PARAMETERS.	Keyword KEYENTR IES in BUILD command was specified without =, or had more than 1 parameter.	Reenter KEYENTRIES= followed by the maximum number of primary key entries expected in the key file, or omit for default of numrecs value from REC=parameter.
1042	'KEYENTRIES' NUMBER OF		ENTRIES VALUE INVALID.
1043	KEYWORD SPECIFICATION IN THIS COMMAND IS INVALID.	A key word specified as a KSAMUTIL command parameter is misspelled or not in syntax.	Check command syntax for correct key word and/or spelling; reenter correctly.
1044	DELIMITER AT THE END OF A SPECIFICATION IS INVALID.	A delimiter follows command specification in KSAMUTIL command.	Remove delimiter or follow with rest of command.
1045	THE NUMBER OF PARAMETERS IN THIS COMMAND IS INVALID.	Too many or too few parameters specified in a KSAMUTIL command.	Check command syntax and reenter with the correct number of parameters.
1046	A PARAMETER VALUE IS INVALID. 'TEMP' WAS EXPECTED.	The key word TEMP was expected as a parameter in PURGE or RENAME commands.	Check command syntax, reenter with correct parameter value.
1047	LOCKWORD NOT ALLOWED IN KEY FILE		Check command syntax; remove lockword from key file specification.
1048	GROUP AND/OR ACCOUNT NOT ALLOWED FOR KEYENTITY =		Check command syntax of BUILD command.
1049	BACK REFERENCE NOT ALLOWED ON formal-designator
1050	SEQ=SEQUENCE NUMBER IS INVALID	Non-numeric sequence number specified for SEQ= parameter.	Check command syntax of KEYSEQ or KEYDUMP commands.
1051	SUBSET= VALUE INVALID	Either the starting position or the number of key values to be dumped is invalid.	Check command syntax of KEYDUMP command
1052	SEQ= SYNTAX ERROR		Check command syntax of KEYSEQ or KEYINFO
1053	SEQ= PARAMETER LIST EXHAUSTED	Not enough information in parameter list; key number missing.	Enter parameter value for SEQ= in KEYSEQ or KEYDUMP commands.
1054	ENTITY = PARAMETER LIST EXHAUSTED	Not enough information in parameter list; file name missing.	Enter file name after ENTITY = in KEYDUMP command.
1055	ENTITY = SYNTAX ERROR		Check command syntax of KEYDUMP command.
1056	SUBSET= PARAMETER LIST EXHAUSTED	Not enough information in parameter list.	Check command syntax of KEYDUMP; enter correct number of parameters.
1057	SUBSET= SYNTAX ERROR		Check command syntax of KEYDUMP command.
1058	INVALID KEY SEQUENCE SPECIFICATION	Key number specified in SEQ= parameter is greater than the number of keys in file.	Key number is 1 for primary key, 2 for first alternate key, etc. Use VERIFY command to check number of keys in file.
1059	FILE SPECIFIED IN FILE- ALREADY EXISTS	File name specified in ENTITY = parameter is an existing permanent file; KEYDUMP always creates a new file.	Enter name of non-existent file, or rename permanent file.
1060	B-TREE HAS MORE THAN 20 LEVELS	KEYDUMP cannot dump more than 20 levels of the key file structure.
1061	INVALID DECIMAL DIGIT OR DIGIT COUNT >28	Packed decimal digit is not 0-9, or there are more than 28 digits. Cannot convert to ASCII for KEYDUMP.
1062	THE REFERENCED FILE IS NOT A KSAM FILE	File reference in the command is not a KSAM file.	Check file name and correct it.
1063	RECORD SIZE OF THE SPECIFIED FILE HAS BEEN CHANGED	Record size of the file specified in ENTITY = parameter of KEYDUMP has been changed by a : FILE command.	Check KEYDUMP syntax; change : FILE command so that record size is not specified.
1064	GENERIC OR APPROXIMATE SEARCH NOT ALLOWED FOR KEY TYPE	Generic or approximate keys can be specified in SUBSET= parameter of KEYDUMP only if key type is BYTE, INTEGER, or DOUBLE.	Use full key value in SUBSET= or do not use SUBSET= parameter.
1065	ILLEGAL OR TOO MANY CHARACTERS	Position value of SUBSETparameter in KEYDUMP contains non-numeric characters, or is >9 digits.	Change position value, or use quoted string for SUBSET= parameter.
1066	REMOTE FILE ACCESS NOT SUPPORTED	A :FILE command specified a remote file, but this command does not support remote access.	Change : FILE command to specify local file.
1067	SORT ON RECORD POINTERS FAILS	Sort of keydump by record pointers (SORT option of KEYDUMP) failed during sort by SORT/3000 program.	Check the reasons for failure in SORT error message.
1068	SYSTEM FAILURE OCCURRED WHILE THE KSAM FILE WAS OPEN	KSAM file was open when a system failure occurred, and file may be damaged.	Run KEYINFO command to recover file and reset flag so file can be opened, or run VERIFY with NOCHECK to examine file.
1069	UNEXPECTED CHARACTER IN FILE NAME; EXPECTED . or /	The only nonmeric characters allowed in a file name are "." or "/".	Check the file name and correct it.

Table A-5 FCOPY Warning and Error Messages

CODE	MESSAGE	MEANING	ACTION
None	<CONTROL Y>	Acknowledges receipt of a CONTROL-Y entered during a session.	None.
None	READ ERROR FROM COMMAND INPUTFILE	An error occurred while reading an FCOPY command from $STDIN.	In a job: Correct the command and resubmit the job. In a session: Re-enter the command using the correct format.
None	WRITE ERROR TO COMMAND LISTFILE	An error occurred while writing an FCOPY message to $STDLIST.	More than likely nothing serious has occurred and all FCOPY operations have been performed successfully. If you want to be sure, however, do the following: In a job: Re-submit the job. In a session: Re-enter the most recent FCOPY command.
3	SYNTAX ERROR: IN SUBSET OPTION	The subset function was not specified properly.	In a job: Correct the command and resubmit the job. In a session: Re-enter the command using the correct format.
4	SYNTAX ERROR: IN TITLE OPTION	The title option of the display function was not specified properly.
5	SYNTAX ERROR: IN IGNERR OPTION	The ignore errors function was not specified properly.
6	SYNTAX ERROR: IN VERIFY OPTION	The verify function was not specified properly.
7	SYNTAX ERROR: IN SKIPEOF OPTION	The skip end-of-file function was not specified properly
8	SYNTAX ERROR: IN COMPARE OPTION	The compare function was not specified properly.
9	SYNTAX ERROR: IN NEW OPTION	The new file function was not specified properly.
10	SYNTAX ERROR: IN HEX OPTION	The display hexadecimal function was not specified properly.
11	SYNTAX ERROR: IN EBCDICOUT OPTION	The EBCDICOUT character translate function was not specified properly.
12	SYNTAX ERROR: IN CHAR OPTION	The display character function was not specified properly
13	SYNTAX ERROR: IN OCTAL OPTION	The display octal function was not specified properly.
14	SYNTAX ERROR: IN UPSHIFT OPTION	The upshift function was not specified properly.
15	SYNTAX ERROR: IN BCDICIN OPTION	The BCDICIN character translate was not specified properly.
16	SYNTAX ERROR: IN NORECNUM OPTION	The NORECNUM option of the display function was not specified properly.
17	SYNTAX ERROR: IN EBCDICIN OPTION	The EBCDICIN character translate function was not specified properly.
18	SYNTAX ERROR: IN BCDICOUT OPTION	The BCDICOUT character translate function was not specified properly.
19	SYNTAX ERROR: INVALID FORM OF EXIT COMMAND	The EXIT command was not specified properly.	None. FCOPY terminates
51	SYNTAX ERROR: IN QUOTED STRING	The characterstring specified for the subset function is not valid.	In a job: Correct the command and resubmit the job. In a session: Re-enter the command using the correct format.
52	SYNTAX ERROR: IN BIT PATTERN	The patternlist specified for the subset function is not valid.
53	SYNTAX ERROR: INVALID INTEGER	An integer specified is outside the range allowed for the particular FCOPY function.
54	SYNTAX ERROR: UNKNOWN OPTION NAME	One of the specified functions was unrecognizable.
55	SYNTAX ERROR: IN FROMFILE SPECIFIER	The "from" file was not specified properly.
56	SYNTAX ERROR: IN TOFILE SPECIFIER	The "to" file was not specified properly.
57	SYNTAX ERROR: ILLEGAL COMBINATION OF OPTIONS	Two or more functionlist entries conflict with one another.
58	SYNTAX ERROR: FROMFILE AND TOFILE NOT BOTH SPECIFIED	FROM= and TO= were not both specified in the FCOPY command.
59	SYNTAX ERROR: ILLEGAL USE OF NEW	The context used to specify a new "to" file is not valid.
60	SYNTAX ERROR: ILLEGAL USE OF *	The context used to specify* as a "from" file or "to" file is not valid.
62	SYNTAX ERROR: FILE NAME TOO LONG	The "from" or "to" file name specified is longer than the 35 characters allowed in a fullyqualified file name with lockword.
102	CAN'T CLOSE FROMFILE	MPE can't close the "from" file. This message is followed by an MPE file information display containing (among other things) an error number.	Look up the error number in Table A-1 “File System Error Codes” and act accordingly.
103	CAN'T CLOSE TOFILE	MPE can't close the "to" file. This message is followed by an MPE file information display containing (among other things) an error number.
104	CAN'T SAVE NEW TOFILE	MPE can't close the "to" file as a permanent file. Either you do not have SF capability or there is not enough group account, or system file space.	If you don't have SF capability, you can't perform the operation. If there is not enough file space, purge some unneeded files to free some file space.
105	CAN'T OPEN FROMFILE	MPE can't open the "from" file. This message is followed by an MPE file information display containing (among other things) an error number.	Look up the error number in Table A-1 “File System Error Codes” and act accordingly.
106	CAN'T OPEN TOFILE	MPE can't open the "to" file. This message is followed by an MPE file information display containing (among other things) an error number.
107	VERIFY OR COMPARE OPTION: CAN'T GET READ ACCESS TO TO FILE	MPE can't get read access to the "to" file for a verify or 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.	Reset the particular : FILE command (using the MPE : RESET command) and retry the operation.
108	ERROR IN CALLING FGETINFO FOR FROMFILE	An error prevented MPE from obtaining information from the "from" file's label. This message is followed by an MPE file information display containing (among other things) an error number.	Look up the error number in Table A-1 “File System Error Codes” and act accordingly.
109	ERROR IN CALLING FGETINFOR FOR TOFILE	An error prevented MPE from obtaining information from the "to" file's label. This message is followed by an MPE file information display containing (among other things) an error number.
110	IGNERR OPTION: FROM FILE NOT TAPE	The "from" file's device is not a magnetic tape unit.	The ignore errors function cannot be used in this case.
111	CAN'T GET READ ACCESS TO FROMFILE	MPE can't get read access to the "from" file. The read access specified in the file label has been overridden by an MPE :FILE command containing ACC=APPEND, ACC=OUT, or ACC=OUTKEEP.	Reset the particular : FILE command (using the MPE : RESET command) and retry the operation.
112	CAN'T GET WRITE ACCESS TO TO FILE	MPE can't get write access to the "to" file. The write access specified in the file label has been overridden by an MPE :FILE command containing ACC=IN.
113	SKIPEOF OPTION: FROM FILE NOT TAPE	The skip end-of-file function was specified for the "from" file and the "from" file device is not a magnetic tape unit.	If the intended "from" or "to" file is on magnetic tape, check the associated MPE :FILE command and the back reference to it.
114	SKIPEOF OPTION: TOFILE NOT TAPE	The skip end-of-file function was specified for the "to" file and the "to" file device is not a magnetic tape unit.
115	SUBSET OPTION: STRING FALLS OUTSIDE OF FROMFILE RECSIZE	The characterstring or patternlist specified is greater than the record size of the "from" file. No such subset can exist in the specified "from" file.	Change the specified subset definition to a valid one and try the operation again.
116	CAN'T GET LARGE ENOUGH BUFFER	There is not enough data space for the buffers needed by the requested operation. FCOPY uses the DL-DB area for variable sized buffers.	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 will accommodate your record size in the maximum allowed data segment size.
117	SKIPEOF OPTION: ERROR WHILE SKIPPING IN FROMFILE	An error occurred while skipping end-of-file marks in the "from" file.	Retry the operation.
118	SKIPEOF OPTION: ERROR WHILE SKIPPING IN TOFILE	An error occurred while skipping end-of-file marks in the "to" file.
119	SUBSET OPTION: ERROR WHILE SPACING IN FROMFILE	An error occurred while spacing through the "from" file.
120	SUBSET OPTION: SUBSET STARTS OVER EOF BOUNDARY	The subset specified extends over an end-of-file mark or a tape mark boundary.	Change the specified subset definition to a valid one and try the operation again.
123	SUBSET OPTION: THIS INPUT DEVICE DOES NOT BACKSPACE	The specified subset requires backspacing in the "from" file but the device for that file is not a disc or magnetic tape.	Check the MPE :FILE command associated with the "from" file and the back reference to it.
124	READ ERROR IN FROMFILE AT RECORD recnum	An error occurred while spacing through the "from" file in search of the start of a subset.	Retry the operation.
125	SUBSET OPTION: NUMERIC SUBSET IS EMPTY	A subset specified by starting record-number, number-of records, and/or last-record number does not exist or contains no data.	Change the specified subset definition to a valid one and try the operation again.
126	VERIFY OPTION: ERROR WHILE REWINDING FROMFILE	An error occurred while spacing backward to the beginning of the "from" file at the start of a verify operation.	Retry the operation.
127	VERIFY OPTION: ERROR WHILE REWINDING TOFILE	An error occurred while spacing backward to the beginning of the "to" file at the start of a verify operation.	Retry the operation.
128	EOF FOUND WHILE SPACING IN FROMFILE	An end-of-file mark was encountered while spacing through the "from" file in search of the start of a subset. This most often occurs when the "from" file is a blocked magnetic tape. For a blocked magnetic tape, the record numbers supplied in the SUBSET= parameter are used as block numbers.	Retry the operation specifying block numbers instead of record numbers. OR Reblock the tape so each block contains one record and then retry the operation.
129	EOF FOUND WHILE SPACING IN TOFILE	An end-of-file mark was encountered while spacing through the "to" file in search of the start of a subset during a compare or verify operation	Compare operation: The "from" and "to" files are not identical. Display the "to" file to determine what it actually contains. Verify operation: The copy operation was not performed correctly. Retry the operation.
131	ERROR WHILE WRITING EOF TO TOFILE	An error occurred while writing an end-of-file mark in the "to" file.	Retry the operation
l32	VERIFY OPTION: ERROR WHILE SPACING IN THE FROMFILE	An error occurred while spacing through the "from" file during a verify operation.
133	VERIFY OPTION: ERROR WHILE SPACING IN THE TOFILE	An error occurred while spacing through the "to" file during a verify operation.
134	WARNING: FOUND EOF IN TOFILE	FCOPY has performed the specified operation but has filled the "to" file before completing the operation.	The "to" file was not large enough. Use the MPE :LISTF filename,2 command to determine the "to" file's size and then increase its size (using the MPE :PURGE and :BUILD commands) and retry the operation.
135	WRITE ERROR TO TOFILE	An error occurred while writing to the "to" file.	Retry the operation.
136	READ ERROR FROM TOFILE	An error occurred while reading from the "to" file during a compare or verify operation.	Compare operation: Retry the operation. If the error persists, you must try to recreate the "to" file. Verify operation: Retry the operation.
137	WARNING: AN UNLABELLED TAPE OPERATION ENDS ON AN ERROR	An operation involving a magnetic tape "from" file was terminated by reading beyond the end of valid data rather than by sensing an end-of-file mark.	This is not an error. You can avoid this message by reading the "from" tape one file at a time and using the keyword SUBSET.
138	TITLE OPTION: TITLE TOO LONG	The title specified for the list function is longer than the 70 characters allowed or it extended over more than one line (record).	In a job: Correct the command and resubmit the job. In a session: Re-enter the command using the correct format.
139	DUMP OPTION: TOFILE RECSIZE NOT WITHIN LEGAL LIMIT	A file display was directed to an intermediate storage device with an incorrect record size. That record size must be ≥60 bytes (30 words).	Change 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	COMPARE OR VERIFY OPTION: OPERATION FAILS; DIFFERENT FIXED RECSIZES	The compare or verify operation was not attempted because the record sizes of the "to" and "from" files are not identical.	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 "to" file (using the MPE :PURGE and :BUILD commands) so that it is the same as that of the "from" file and then retry the operation.
141	COMPARE BEGINS	The comparison phase of a verify operation has begun.	None.
143	WARNING: FROMFILE IS EMPTY	The "from" file contained no data. Nothing was copied or compared.	None. You may have accidentally specified the wrong file as the "from" file.
144	NEW OPTION: FILE ALREADY EXISTS	The "to" file named for the new file function already exists in the specified (or implied) group and account.	Change the name of the "to" file and try the operation again.
145	BACKSPACE ERROR IN FROMFILE	An error occurred while spacing backward to the beginning of the "from" file or a subset within it.	Retry the operation.
200	WARNING: FROMFILE RECSIZE IS number type, TOFILE RECSIZE IS number type	The record sizes of the "from" and "to" files are not identical.	In a job: FCOPY performs the specified operation despite the conflict. In a session: You are given the choice whether or not to continue the operation. Note that if the "from" record size is larger than the "to" record size, the "from" records would be truncated. If the "to" record size is larger than the "from" record size, the content of the excess byte positions in the "to" records is unpredictable.
201	WARNING: FROMFILE IS ASCII, TOFILE IS BINARY or WARNING: FROMFILE IS BINARY, TOFILE IS ASCII	The data formats of the "from" and "to" files are not identical.	In a job: FCOPY performs the operation despite the conflict. In a session: You are given the choice whether or not to continue the operation.
301	READ ERROR IN FROMFILE AT RECORD recnum	An error occurred while reading from the "from" file at the record number displayed (recnum).	Retry the operation. If the error persists, use the subset function to copy all of the file except the erroneous record.
302	VERIFY OPTION: RAN OUTOF VERIFY ERRORS AT FROMFILE RECORD recnum	The verify function was terminated because the specified maximum number of errors has been exceeded at the record number displayed (recnum).	Retry the operation specifying a larger number-of- errors parameter.
304	COMPARE OPTION: RAN OUT OF COMPARE ERRORS AT FROMFILE RECORD recnum	The compare function was terminated because the specified maximum number of errors has been exceeded at the record number displayed (recnum).	Retry the operation specifying a larger number-of- errors parameter
901	KSAM FROMFILE BOUNDARY (EOF OR BOF)	The beginning or end of the from file was reached during the copy operation.
902	KSAM FROMFILE POSITIONING ERROR	Could not position to desired place.	Try again.
903	ERROR; WRONG CONDITIONS FOR OPENING NEW KSAM FILE	From file is not a KSAM file, or NO KSAM was specified.	Create a KSAM file before running FCOPY and copy to that file.

Appendix A ERROR MESSAGES AND RECOVERY PROCEDURES

Technical documentation

» Table of Contents