Appendix B File-System Errors

Table B-1 lists file-system errors and provides a brief description of each error. For information about correcting file-system errors, see the Guardian Procedure Errors and Messages Manual.




	NOTE: To display the message text of a file-system error, type the word error followed by the error number at the TACL prompt; for example, error 2. To display the message text and number of all file-system and SQL errors, type error -1.

Table B-1 File-System Errors 0 through 99

Decimal Number	Octal Number	Description
0	%0	The operation completed successfully.
1	%1	A read procedure reached end-of-file or a write procedure reached end of tape.
2	%2	The operation specified is not allowed on this type of file.
3	%3	An open or purge of a partition failed.
4	%4	An open operation for an alternate key file failed.
5	%5	Sequential buffering not used because no space was available in the PFS for the sequential block buffer.
6	%6	A system message was received from another process.
7	%7	This process cannot accept a CONTROL, CONTROLBUF, SETMODE, or RESETSYNC because $RECEIVE is not opened correctly.
8	%10	The operation was successful. (Examine MCW for additional status.)
9	%11	A read through a locked record was successful.
10	%12	The new record or file could not be created because a file by that name or a record with that key already exists.
11	%13	The file is not in the directory or the record is not in the file, or the specified tape file is not on a labeled tape.
12	%14	The file is in use.
13	%15	The file name was not specified in proper form.
14	%16	That device does not exist on this system.
15	%17	The volume or system specified for a file RENAME operation does not match the name of the volume or system of the file.
16	%20	No file with that file number has been opened.
17	%21	A paired-open was specified, and the file is not open by the primary process, the parameters supplied do not match the parameters supplied when the file was opened by the primary, or the primary process is not alive.
18	%22	The system specified does not exist in the network.
19	%23	No more space is available for devices in the logical device table.
20	%24	File name is too long to be opened across a network, or swap file or system name is not acceptable.
21	%25	An illegal count was specified in a file‑system call, or the operation attempted to transfer too much or too little data.
22	%26	The application parameter or buffer address is out of bounds.
23	%27	The disk address is out of bounds, or the maximum number of blocks in an alternate-key file is exceeded.
24	%30	Privileged mode is required for this operation.
25	%31	AWAITIO[X] or CANCEL was attempted on file opened for waited I/O.
26	%32	AWAITIO[X] or CANCEL or CONTROL 22 was attempted on a file with no outstanding I/O requests; or a FILE_COMPLETE_ was called with a timeout value of -1 (wait indefinitely), but no I/O had been initiated.
27	%33	An operation was attempted with outstanding nowaited I/O requests pending.
28	%34	The number of outstanding nowait operations would exceed that specified, an attempt was made to open a disk file or $RECEIVE with the maximum number of concurrent operations more than 1, or an attempt was made to add more than the configured maximum number of subdevices.
29	%35	A required parameter is missing in a procedure call, or two mutually exclusive parameters were supplied.
30	%36	Message system is unable to obtain memory.
31	%37	Unable to obtain file‑system buffer space.
32	%40	Unable to obtain storage pool space (SYSPOOL or EXTPOOL).
33	%41	I/O process is unable to obtain sufficient buffer space.
34	%42	Unable to obtain a file‑system control block.
35	%43	Unable to obtain a lock control block, or the transaction or open lock unit limit has been reached.
36	%44	Unable to lock physical memory; not enough memory is available.
37	%45	I/O process is unable to lock physical memory.
38	%46	Attempt was made to perform operation on wrong type of TNS system.
39	%47	The server process received a request with a sync ID older than the set of saved replies.
40	%50	The operation timed out. AWAITIO[X] or FILE_COMPLETE_ did not complete within the time specified by its time-limit parameter.For AWAITIIO[X], if a 0D time limit (completion check) or -1 file-number (wait for completion of an operation on any file) was specified, the operation did not finish. Otherwise, the operation timed out and was automatically canceled. It is considered completed.For FILE_COMPLETE:, this error is returned only when a time limit other than -1D (wait indefinitely) was specified and the operation did not finish.
41	%51	A checksum error occurred on a file-synchronization block.
42	%52	An attempt was made to read from unallocated extent.
43	%53	Unable to obtain disk space for file extent.
44	%54	The disk directory or DCT is full.
45	%55	The file is full, or two entries for process-name were already in the PPD.
46	%56	An invalid key was specified, key length passed to CREATE exceeds 255 bytes, or application failed to open an alternate-key file.
47	%57	The alternate key data is not consistent with primary file data.
48	%60	Security violation; an illegal operation was attempted.
49	%61	Access violation; attempt to use an unexpired labeled tape for output; or a mismatch between a DEFINE Use attribute (input or output/extend) and the current operation (read or write).
50	%62	Directory error occurred on a disk volume.
51	%63	Directory on a disk volume is marked bad.
52	%64	Error occurred in the disk free space table.
53	%65	File-system internal error or CP6100 file management interface error occurred.
54	%66	I/O error occurred in disk free space table or in DP2 undo area.
55	%67	I/O error occurred in disk directory. The file is no longer accessible.
56	%70	I/O error occurred on disk volume label. The volume is no longer accessible.
57	%71	The disk free space table is full.
58	%72	The disk free space table is marked bad.
59	%73	The disk file is bad. A mismatch exists in the internal FCB, or the file structure in a structured file is inconsistent.
60	%74	The file resides on a removed volume; the device is down or not open; or a server has failed, and a process has been replaced by a different process with the same name since the server was opened.
61	%75	No more file opens are permitted on this volume or device. The system operator issued a STOPOPENS command, or the number of open files reached the maximum allowed.
62	%76	The volume was mounted, but no mount order was given, so the file open is not permitted.
63	%77	The volume was mounted, and the mount is in progress, so a file open is not permitted.
64	%100	The volume was mounted, and the mount is in progress, so a file open is not permitted.
65	%101	Only special requests are permitted, or a special request to mirrored disk pair was attempted with only one device in special state.
66	%102	The device is down, the LIU is not yet downloaded, a hard failure occurred on the controller, the disk and controller are not compatible (DP1/DP2), or both halves of a mirrored disk are down.
70	%106	Continue the file operation.
71	%107	A duplicate record was encountered.
72	%110	An attempt was made to access an unmounted or nonexistent partition or to access a secondary partition.
73	%111	The disk file or record is locked.
74	%112	Number of READUPDATES without replies exceeds receive‑depth, or ACTIVATERECEIVETRANSID or REPLY was called with an invalid message tag.
75	%113	Requesting process has no current process transaction identifier.
76	%114	Transaction is in the process of ending.
78	%116	Transaction identifier is invalid or obsolete.
79	%117	A transaction attempted to update or delete a record that it has not previously locked.
80	%120	Invalid operation on audited file or nonaudited disk volume.
81	%121	Operation is not valid for a transaction that still has nowait I/Os outstanding on a disk or process file.
82	%122	TMF not running on this system or on the remote system.
83	%123	Attempt was made to begin more concurrent transactions than can be handled.
84	%124	TMF has not been configured on this system or on the remote system.
85	%125	A device has not been started for TMF.
86	%126	BEGINTRANSACTION is disabled either by the operator or because one or more TMF limits have been reached.
87	%127	Waiting on a READ request but did not get it.
88	%130	A CONTROL READ is pending, so a second READ is not valid.
89	%131	A remote device cannot accept text because it has no buffer available.
90	%132	The transaction was aborted by the system because its parent process died, a server using the transaction failed, or a message to a server using the transaction was cancelled.
91	%133	A TMF failure occurred during commitment of the transaction. The transaction might or might not have been committed.
92	%134	Distributed transaction aborted by system because the path to a remote system that was part of the transaction was down.
93	%135	A transaction was aborted because it spanned too many audit trail files.
94	%136	A transaction was aborted by operator command.
95	%137	A transaction was aborted because of disk process takeover by backup.
97	%141	Transaction was aborted by call to ABORTTRANSACTION.
98	%142	Allocation of a transaction control block failed because the local table is full or the table on a remote system is full.
99	%143	Process attempted to use features of a microcode option that is not installed on this system.

Table B-2 File-System Errors 100 through 199

Decimal Number	Octal Number	Description
100	%144	Device is not ready, or the controller is not operational.
101	%145	The tape is write protected.
102	%146	Printer paper out, bail open, or end of ribbon.
103	%147	Disk is not ready due to power failure.
104	%150	No response received from printer.
105	%151	Invalid printer VFU buffer.
106	%152	A buffered WRITE has failed. Data in printer buffer was lost.
110	%156	Only BREAK access is permitted.
111	%157	Operation aborted because of BREAK.
112	%160	READ or WRITEREAD preempted by operator message or too many user console messages.
113	%161	DEFINE class or attributes are not valid for the attempted function.
114	%162	X25 Network problem - RESTART FAILURE.
115	%163	X25 network problem occurred. RESET FAILURE.
119	%167	Error code value was too large to fit into an 8-bit buffer. File‑system error number is greater than 255.
120	%170	Data parity error occurred, or attempt was made to access a tape whose density is higher than the switch setting on the tape drive.
121	%171	Data overrun error, hardware problem.
122	%172	Request was aborted due to possible data loss caused by reset of circuit, CLB sequence error, or DP2 disk process takeover.
123	%173	Subdevice is busy.
124	%174	A line reset is in progress. Loss of data is possible.
130	%202	Illegal disk address was requested, or formatting error occurred.
131	%203	Write-check error from disk; internal circuitry fault.
132	%204	Seek incomplete from disk. Cylinder address was not reached after retry.
133	%205	Access not ready on disk. Cylinder address was not reached.
134	%206	Address compare error occurred on disk.
135	%207	Write-protect violation occurred with disk write.
136	%210	Disk unit ownership error occurred (dual-port disk).
137	%211	Controller buffer parity error occurred.
138	%212	Interrupt overrun. A device interrupted the processor before the software could respond.
139	%213	Controller error. Internal diagnostic failure occurred.
140	%214	Modem error occurred (communication link not yet established, modem failure, momentary loss of carrier, or disconnect), or FOX link to an Expand line handler is down.
148	%224	Attempt was made to read unwritten data or to overwrite existing data on an optical disk.
150	%226	End-of-tape marker was detected.
151	%227	Runaway tape was detected, or attempt was made to access a tape whose density is lower than the switch setting on the tape drive.
152	%230	Unusual end. Tape unit went offline, or CP6100 file was closed while requests still in progress.
153	%231	Tape drive power was restored.
154	%232	BOT was detected during backspace files or backspace records.
155	%233	Only 9-track magnetic tape is allowed on this system.
156	%234	Tape command was rejected, TIL or TLAM (D-series only) protocol violation was detected, or X25AM level-4 ITI protocol violation occurred.
157	%235	I/O process internal system error occurred.
158	%236	Invalid function code was requested for Hyper Link.
159	%237	Device mode was wrong for Hyper Link I/O request, or attempt was made to execute PUP PRIMARY command while the tape drive is waiting for a labeled tape to be mounted.
160	%240	Request is invalid for device state. Protocol error.
161	%241	Impossible event occurred for line state.
162	%242	Operation timed out.
163	%243	EOT was received, or power at autocall unit is off.
164	%244	Disconnect received, or data line is occupied.
165	%245	RVI received, or data line not occupied after setting call request.
166	%246	ENQ received, or auto call unit failed to set present-next-digit.
167	%247	EOT received on line bid, or data-set-status not set.
168	%250	NAK received on line bid, or auto-call unit failed to clear present‑next‑digit after digit‑present was set.
169	%251	WACK received on line bid, auto-call unit set abandon-call-and-retry, or station disabled or undefined.
170	%252	No ID sequence received during circuit assurance mode or invalid MCW entry number on write.
171	%253	No response was received on bid/poll/select, or reply was invalid.
172	%254	Reply was not proper for protocol. Invalid control sequence or invalid data.
173	%255	Maximum allowable NAKs received (transmission error), invalid MCW on WRITE, or invalid request ID.
174	%256	WACK received, or CLB frame aborted.
175	%257	Incorrect alternating ACK received, or command rejected.
176	%260	Poll sequence ended with no responder.
177	%261	Text overrun occurred (insufficient buffer space for data transfer).
178	%262	No address list was specified.
179	%263	Application buffer is incorrect, control request is pending, or autopoll is active.
180	%264	Unknown device status was received.
181	%265	Subdevice expected status information but received data instead.
182	%266	SNALU access method outbound RU error occurred. See SNALU error code in status area of SNAX header.
183	%267	SNA session has ended.
187	%273	Operation is returning with no useful data.
188	%274	Damage to logical flow of events.
189	%275	Response not yet available.
190	%276	Device error occurred; hardware problem.
191	%277	Device power on.
192	%300	Device is in diagnose mode. System operator is running diagnostics.
193	%301	Microcode file is invalid or missing.
194	%302	Device use or mount request was rejected by operator.
195	%303	Operation requires use of $ZSVR, but it is not running. Tape operation is not allowed.
196	%304	A tape label record is missing or incorrect.
197	%305	An SQL error occurred.
198	%306	A DEFINE of the given name could not be found.
199	%307	The disk file is Safeguard protected.

Table B-3 File-System Errors 200 through 511

Decimal Number	Octal Number	Description
200	%310	The device is owned by an alternate port.
201	%311	The current path to the device is down, an attempt was made to write to a nonexistent process, the message‑system request was incorrectly formatted, or an error was found in the message system interface.
210	%322	Device ownership changed during operation.
211	%323	The processor performing the operation failed during the operation.
213	%325	Channel data parity error occurred (path error).
214	%326	Channel timeout occurred (path error).
215	%327	I/O was attempted to absent memory page (hardware path error).
216	%330	Memory breakpoint encountered during this I/O operation.
217	%331	Memory parity error occurred during this I/O (hardware path error).
218	%332	Interrupt timeout occurred on a channel, or a controller, modem, or the line between, or lost the modem clock (path error).
219	%333	Illegal device reconnect (path error).
220	%334	Protect violation. An I/O controller attempted an illegal write.
221	%335	Controller handshake violation occurred (path error).
222	%336	Bad channel status was received from EIO instruction (path error).
223	%337	Bad channel status was received from IIO instruction (path error).
224	%340	Controller error occurred (fatal error).
225	%341	No unit was assigned, or multiple units were assigned to the same unit number (path error).
230	%346	Processor power failed and then was restored.
231	%347	Controller power failed and then was restored.
232	%350	Access is denied due to error in communication with SMON.
233	%351	Error occurred in call to SERVERCLASS_SEND_.
240	%360	Network line-handler error occurred; operation was not started. Expand performed an ownership switch.
241	%361	Network error occurred; operation was not started.
246	%366	External cluster bypass error occurred; operation was aborted.
248	%370	Network line-handler error occurred; operation was aborted.
249	%371	Network error occurred; operation was aborted.
250	%372	All paths to the system are down.
251	%373	Network protocol error occurred (path error).
252	%374	Required Expand class is not available.
255	%377	Net line handler was flooded. Too many interrupts occurred.
300-511	%454-%777	These numbers are reserved for application processes.

Table B-4 File-System Errors 541 through 899

Decimal Number	Octal Number	Description
541	%1035	A data structure version is incompatible with the requested operation.
549	%1045	Block mode is not currently allowed on this terminal.
550	%1046	File operation was attempted at illegal position.
551	%1047	Duplicate exists for insertion-ordered alternate key.
560	%1060	The function cannot be performed because one of the processes involved cannot recognize a PIN greater than 255.
561	%1061	The item code in a list is not recognized.
563	%1063	The size of an output buffer was too small.
564	%1064	The operation is not supported for this file type.
565	%1065	A malformed request was denied.
566	%1066	This reply is malformed or not appropriate.
567	%1067	The DEFINE used is incompatible for use with target system's TOS version.
573	%1075	The requested process handle cannot be returned.
578	%1102	The block size specified is too large.
579	%1103	The record size specified is too large for the given block size, file type, and format.
580	%1104	An open failed because the file was oversize and the opener did not specify use of 64-bit primary keys.
581	%1105	An operation involving 32-bit primary keys was attempted on an open that specified use of 64-bit keys.
582	%1106	Alternate key information could not be returned because it cannot be expressed in the superceded format of the parameter.
583	%1107	The extent size specified is too large, or the maxextents limit is too large.
584	%1108	The operation could not be performed because a software component does not support format 2 disk files.
590	%1116	The parameter value is invalid or inconsistent with another.
593	%1121	The request was cancelled.
594	%1122	A DSM/TC error was returned to $ZSVR. For detailed information, see the EMS log.
595	%1123	A ZSSI error was returned to $ZSVR. For detailed information, see the EMS log.
597	%1125	A required item is missing from an item list.
632	%1170	Not enough stack space is available to complete request.
633	%1171	Operation is invalid because Measure is running (D-series only).
634	%1172	A logical device number exceeded 16 bits.
635	%1173	A volume cannot be accessed because the other side is locked.
638	%1176	Process cannot be stopped until process returns to stopmode 1.
639	%1177	Process cannot be stopped until process goes to stopmode 0.
640	%1200	DEBUGNOW is required instead of DEBUG for a privileged process.
700	%1274	The sequence number of the message received by the disk process from a recovery process does not match.
701	%1275	The disk process received a message from a recovery process that requires the disk process to be in the UP state. It is currently in the DOWN state.
702	%1276	The disk process received an erroneous message from a recovery process. The message requested a physical REDO and also requested that audit be generated.
703	%1277	The disk process encountered a creation volume sequence number in an audit record sent by a recovery process that is more recent than the CRVSN of the file label.
704	%1278	The disk process encountered a previous volume sequence number in an audit record sent by a recovery process that does not match the VSN of the data block on disk.
705	%1279	Generated by the disk process when it receives a TMF Auditing Disk Process request type message and the disk process is not an ADP volume.
706	%1280	Generated by the disk process when it receives a request message that is inappropriate for an Auditing Disk Process.
707	%1281	Generated by the disk process when the Disk Process Name Stamp (DPNameTimeStamp) in the message sent by a recovery process does not match the current DPNameTimeStamp of the disk.
708	%1282	The disk process encountered a File Label that had its UndoNeeded flag set when a recovery request specified that the UndoNeeded flag must not be set.
709	%1283	The disk process encountered a File Label that had its RedoNeeded flag set when a recovery request specified that the RedoNeeded flag must not be set.
711	%1285	The disk process received a corrupt audit record in a message from a recovery process.
712	%1310	An attempt was made to register a recoverable resource manager using the TMF_REC_RM_CREATE_ procedure, but the name was already registered.
713	%1311	An attempt was made to remove a recoverable resource manager from the directory using the TM_REC_RM_REMOVE_ procedure, but the resource manager still has unresolved transactions outstanding.
714	%1312	A call to TMF_EXPORT_ or TMF_IMPORT_ specified an invalid combination of protocols and options for the transaction branch.
715	%1313	An invalid transaction handle was specified. The handle could be completely invalid, or the type of handle could be invalid for the operation specified, such as trying to do a TMF_SETTXHANDLE_ using the transaction handle returned from TMF_EXPORT_ for a branch that is not a pre-prepare branch.
716	%1314	An attempt was made to suspend a transaction (TMF_SUSPEND_), but the caller is not the beginner nor the importer nor the “resumer” of the transaction.
717	%1315	An attempt was made to resume a transaction (TMF_RESUME_), but the specified transaction is not currently suspended.
718	%1316	An invalid signal value was found. Either an invalid value was specified to TMF_WRITE_SIGNAL_ or an invalid buffer was specified to TMF_INTERPRET_SIGNAL_.
719	%1317	An attempt was made to write branch or resource manager data, but the amount of data specified would cause the allowable limits on the data to be exceeded.
721	%1321	The TMF_RESUME_ procedure was called before the BEGINTRANSACTION processing for the specified transaction is complete. This situation could occur because the BEGINTRANSACTION procedure does not wait for the processing to complete before returning to the caller and the caller could subsequently call TMF_SUSPEND_ and send the tid off to another process to resume before the processing is complete.
722	%1322	An attempt was made to open a resource manager file, but the gateway process’ local CPU has run out of available resource manager control blocks.
723	%1323	An attempt was made to export or import a transaction branch, but the limit of the number of branch control blocks per CPU has been exceeded.
724	%1324	An attempt was made to export a transaction branch with the TFILE not opened in a nowaited manner.
725	%1325	An attempt was made to call ENDTRANSACTION on an imported transaction branch.
727	%1327	An attempt was made to create a recoverable resource manager, but the maximum allowable recoverable resource managers for the system is exceeded.
728	%1328	An attempt was made to set the current transaction of a process by invoking TMF_SETTXHANDLE_ passing in the TxHandle obtained by exporting a transaction branch to a volatile resource manager with the pre-prepare option, but the exported transaction branch is prepared.
729	%1331	An attempt was made to write branch data to a prepared exported or imported transaction branch.
730	%1332	There are outstanding TMF_JOIN_s for the process. This error occurs during ENDTRANSACTION processing.
731	%1333	Transaction has already been joined by this process.
732	%1334	Transaction has already been resumed by this process.
733	%1335	The transaction branch has already failed. This error occurs when branch data is updated while the transaction is being aborted.
758	%1366	Unable to allocate space from the control block pool.
759	%1367	Unable to allocate space from the audit checkpoint pool.
760	%1370	Unable to allocate space for cache.
761	%1371	Unable to allocate space from the work pool.
762	%1372	Unable to allocate space for the free-space table.
763	%1373	Unable to allocate space from the local pool.
764	%1374	Unable to allocate space from the revive pool.
765	%1375	Unable to allocate space from the SQL data area pool (SQLMXBuffer space).
899	%1603	Attempt to switch processors with a PUP PRIMARY command failed.

Table B-5 File-System Errors 1091 through 5313

Decimal Number	Octal Number	Description
1091	%2103	The file or table cannot be purged until the NOPURGEUNTIL date.
1163	%2213	Illegal operation was attempted on a file that has a system-reserved file name.
4000 through 4999	%7640 through %11607	Open System Services (OSS) error occurred.
5001	%11611	The requester does not have sufficient knowledge of ServerWare Storage Management Foundation (SMF). Either the requester is running on an RVU earlier than D40, or the request version is not recognized by the ServerWare SMF subsystem. If the request version is not recognized, the request is being made to a remote system that is running a later product version of the ServerWare SMF subsystem that uses a different message protocol.
5002	%11612	A request to create a file on a DSM/Storage Manager logical volume was denied because a logical volume was currently being deleted.
5007	%11617	Request to create a logical file on a ServerWare SMF logical volume was denied because logical file creation is disabled.
5010	%11622	An error occurred during ServerWare SMF lock manager processing.
5011	%11623	An error occurred during access of the ServerWare SMF ANT table (which stores logical file names and their mappings).
5012	%11624	An error occurred during access of the ServerWare SMF PENDOPS (pending operations) file.
5013	%11625	The name range for a physical volume is exhausted for a new ServerWare SMF logical file.
5014	%11626	No physical volumes are available for a new ServerWare SMF logical file.
5015	%11627	The outcome for a request is unknown. The ServerWare SMF subsystem lost access to the disk process.
5017	%11631	Unable to read one of the ServerWare SMF catalog tables.
5018	%11632	An error occurred during ServerWare SMF message processing.
5028	%11644	A ServerWare SMF process was unable to read a received message.
5034	%11652	The ServerWare SMF disk process or pool process was unable to start the thread manager.
5035	%11653	A ServerWare SMF disk process or pool process was unable to start a thread while processing a request.
5043	%11663	An error occurred during a read of a ServerWare SMF catalog file.
5048	%11670	A BEGINTRANSATION error occurred when the ServerWare SMF subsystem tried to obtain a TMF transaction ID to initiate recovery processing after a create, purge, rename, or update of a ServerWare SMF logical file failed.
5049	%11671	The ServerWare SMF subsystem was unable to allocate memory.
5050	%11672	An unexpected error occurred during request processing by the ServerWare SMF.
5053	%11675	The ServerWare SMF lock manager reached its lock threshold.
5064	%11710	An error occurred while the ServerWare SMF subsystem was attempting to perform recovery processing.
5065	%11711	An error occurred within the ServerWare SMF subsystem during indeterminate outcome processing.
5072	%11720	The ServerWare SMF process was unable to initialize the PENDOPS (pending operations) file while attempting to perform recovery processing after a create, purge, rename, or update of a ServerWare SMF object failed.
5073	%11721	A PENDOPS (pending operations) semaphore failed. The process that locked a ServerWare SMF object could not be identified.
5076	%11724	An invalid operation code was found in the ServerWare SMF PENDOPS (pending operations) table. The PENDOPS entry is invalid.
5313	%12301	A virtual disk process encountered an error while trying to perform the requested operation on a ServerWare SMF logical file.