Page 1 Manual Abstract This manual describes the Guardian messages for HP systems that use the HP NonStopTM operating system. The manual covers the following types of messages: error codes and error lists associated with Guardian procedure calls, the interprocess messages sent to application programs by the operating system and the command interpreter, traps, and signals.
Page 2 The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Page 3: Table Of Contents
Related Reading........................11 Notation Conventions......................11 General Syntax Notation....................11 Notation for Messages.......................13 Notation for Management Programming Interfaces..............13 Change Bar Notation......................13 HP Encourages Your Comments....................14 1 Introduction.....................15 Procedure Errors........................15 G-Series and Later Procedure Errors..................15 C-Series Procedure Errors....................16 Interprocess Messages......................16 Interprocess Command Interpreter Messages.................16 System Messages.......................16...
Page 4 18: ZFIL-VAL-REPLY......................103 19: ZFIL-VAL-SETMODE.....................103 20: ZFIL-VAL-SETMODENOWAIT..................104 21: ZFIL-VAL-WRITE......................105 22: ZFIL-VAL-WRITEREAD....................106 23: ZFIL-VAL-WRITEUPDATE....................107 24: ZFIL-VAL-WRITEUPDATEUNLOCK..................107 25: ZFIL-VAL-AWAITIOX....................108 26: ZFIL-VAL-CHECKPOINTMANYX..................109 27: ZFIL-VAL-CHECKPOINTX....................110 28: ZFIL-VAL-KEYPOSITIONX....................111 29: ZFIL-VAL-READLOCKX....................112 30: ZFIL-VAL-READUPDATELOCKX..................113 31: ZFIL-VAL-READUPDATEX....................114 32: ZFIL-VAL-READX......................115 33: ZFIL-VAL-REPLYX......................116 34: ZFIL-VAL-WRITEREADX....................116 35: ZFIL-VAL-WRITEUPDATEUNLOCKX................117 36: ZFIL-VAL-WRITEUPDATEX.....................118 37: ZFIL-VAL-WRITEX......................119 38: ZFIL-VAL-CLOSE......................120 39: ZFIL-VAL-DEVICEINFO2....................120 65: ZFIL-VAL-FILE-OPEN-CHKPT..................121...
Page 5 Recovery........................156 6 Process Creation Errors................157 Error Codes.........................157 Error Lists..........................182 22: ZGRD-VAL-PROCESS-CREATE..................182 Unconditional Tokens....................183 Conditional Tokens......................183 Effect.........................183 Recovery........................183 25: ZGRD-VAL-PROCESS-LAUNCH..................184 Unconditional Tokens....................184 Conditional Tokens......................184 Effect.........................185 Recovery........................185 7 PROCESS_GETINFOLIST_ Errors...............186 Error Codes.........................186 8 PROCESS_GETPAIRINFO_ Errors..............190 Error Codes.........................190 9 PROCESS_SPAWN_ Open System Services (OSS) Errors......192 Guardian Error Codes......................192 OSS Error Codes........................192 Error Lists..........................195...
Page 6 13 SEGMENT_USE_Errors................209 Error Lists..........................209 23: ZGRD-VAL-SEGMENT-USE...................209 Unconditional Tokens....................209 Conditional Tokens......................210 Effect.........................210 Recovery........................210 14 Subsystem Programmatic Interface (SPI) Errors...........211 Error Codes.........................211 Error Lists..........................216 Error From SSGET or SSGETTKN..................216 Unconditional Tokens....................216 Conditional Tokens......................217 Effect.........................217 Recovery........................217 Error From SSINIT......................217 Unconditional Tokens....................217 Effect.........................217 Recovery........................217 Error From SSMOVE or SSMOVETKN.................217 Unconditional Tokens....................217 Conditional Tokens......................218...
Page 7 21 Traps and Signals.................271 Trap Handling........................271 Signal Handling........................272 Signals and Trap Numbers....................272 Error Lists..........................276 5: ZGRD-VAL-TRAPOUT....................277 Unconditional Tokens....................277 Conditional Tokens......................277 Effect.........................278 Recovery........................278 22 OSS Error Information................279 Brief OSS Error Information....................279 Detailed OSS Error Information....................279 Example.........................279 Index.......................280 Contents...
Page 8: What's New In This Manual
Manual Information Abstract This manual describes the Guardian messages for HP systems that use the HP NonStopTM operating system. The manual covers the following types of messages: error codes and error lists associated with Guardian procedure calls, the interprocess messages sent to application programs by the operating system and the command interpreter, traps, and signals.
Page 9 Changes to the H06.21/J06.10 Manual Added a description for error 35 on (page 29). Added file-system errors 758 through 766 on (page 78). Updated Note under Signals and Trap Numbers on (page 272). Updated the description of error code 72 on “Error Codes”...
Page 10: About This Manual
About This Manual Purpose of This Manual This manual describes the Guardian messages for HP systems that use the HP NonStop operating system. It covers the following types of messages: The error codes and error lists associated with Guardian procedure calls...
Page 11: Related Reading
279), describes how to find information on Open System Services (OSS) errors. Related Reading This manual assumes that you are familiar with the HP system architecture and the NonStop operating system. The following manuals provide information about the hardware architecture and the operating system:...
Page 12 lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required.
Page 13: Notation For Messages
$process-name.#su-name Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] CONTROLLER [ , attribute-spec ]...
Page 14: Hp Encourages Your Comments
In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to docsfeedback@hp.com.
Page 15: Introduction
1 Introduction This manual describes the Guardian messages associated with the NonStop operating system. This manual is dual-threaded, covering both G-series and H-series releases. For each message, the description provides an explanation of the cause, a discussion of the effect on the system, and suggestions for corrective action or response.
Page 16: C-Series Procedure Errors
An interprocess command interpreter message is an interprocess message that is exchanged between the command interpreter and an application process. The Tandem Advanced Command Language (TACL) command interpreter is supplied by HP for use on the operating system. Use of interprocess command interpreter messages is documented in the Guardian Programmer's Guide.
Page 17: Error Lists
Each subsystem defines its own set of error numbers. Error Lists and Non-SPI Subsystems Some HP software facilities do not have a programmatic command interface based on SPI but do define standard error lists. If a HP subsystem that has an SPI-based command interface calls one of these facilities and receives an error, the subsystem usually tries to recover from the error.
Page 18 Each description of a trap or signal condition contains the following information: The signal name or trap number The cause of the trap or signal The effect of the error on the system The recovery actions you can take You can use the ARMTRAP procedure to specify a location in your application program where execution should begin if a trap occurs.
Page 19: File-System Errors
Because most programs use the file system, these conditions can occur during execution of almost any user-written application or any program supplied by HP. Many programs display file-system error codes on the user's terminal. These messages typically contain the code number and a short message.
Page 20: Error Mapping To C Language Errno Values
On D-series releases, file-system error information is also available using one of the procedures described in Table Table 3 D-Series Error Information Procedures Procedure When to Use FILE_GETINFO To obtain information about a file using the file number (filenum). FILE_GETINFOLIST_ To obtain information about a file using the file number (filenum).
Page 21: Error Code Descriptions
Table 4 Guardian File-System Errors Mapped to C Errors (continued) File-System Error C errno Symbolic Name 43-44 ENOSPC EFBIG EACCES EINVAL 50-51 EFSERR EINVAL EFILEBAD EWRONGID EGUARDIANLOCKED 549, 560, 564, 590 EINVAL Error Code Descriptions (%0) The operation completed successfully. Cause The file-system procedure successfully completed the requested operation.
Page 22 Invalid SETMODE operation ACTIVATERECEIVETRANSID, READUPDATE, or REPLY attempted on $RECEIVE opened with a receive-depth of zero. This error is also returned from REPLYX in any of the three following cases: The address of a parameter is extended, but no segment is in use at the time of the call or the segment in use is invalid.
Page 23 Recovery Informative message only. The process receiving the system message should read it (from $RECEIVE) to determine what action is needed. (%7) This process cannot accept a CONTROL, CONTROLBUF, SETMODE, or RESETSYNC because $RECEIVE is not opened correctly. (device type: 0) Cause The process receiving the error message called CONTROL, SETMODE, RESETSYNC, or CONTROLBUF for a server process file, but the server process did not open its $RECEIVE file to enable receipt of these messages either with the procedure OPEN parameter flags.<1>set to 1 or...
Page 24 Recovery Corrective action is application dependent; for "record not in file," it depends on the positioning mode. (%14) The file is in use. (device type: any) Cause The specified file was in use, with exclusive or protected access, by another process. If a backup open is being performed and the file number is currently opened by the backup process, the open operation returns this file-system error number though the file was not in use.
Page 25 Cause A backup process attempted an OPEN or FILE_OPEN_ operation, or the primary process attempted a CHECKOPEN or FILE_OPEN_CHKPT_ operation, but either the file was not opened by the primary process, the parameters supplied did not match the parameters supplied when the file was opened by the primary, or the primary process was not alive.
Page 26 Cause A process specified an invalid count parameter in a file-system call, or the operation tried to transfer too much or too little data. Typical causes are: A FILE_CREATE_ or CREATE procedure call for a structured disk file contains an invalid record length or alternate-key length.
Page 27 If a call to OPEN returned this error, check the flags parameter. If a call to FILE_OPEN_ returned this error, check the options parameter. (%31) AWAITIO[X] or CANCEL attempted on file opened for waited I/O. (device type: any) Cause A process called AWAITIO[X] or CANCEL for a file opened for waited I/O. Effect The procedure sets the error code and returns without performing the requested operation.
Page 28 (A process can change its limits by using the CONTROLMESSAGESYSTEM procedure call.) Retry the operation. Try to determine what system process or application process is causing the fault. If the problem persists, contact your HP representative.
Page 29 If the problem persists, contact your HP representative. Configuration information for the current system image should be saved for your HP representative. (%41) I/O process is unable to obtain sufficient buffer space. (device type: any except 2) Cause Insufficient buffer space was available for the I/O process. This message is returned for a privileged operating system call.
Page 30 Cause Insufficient physical memory was available to perform the specified operation. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Wait, then try again. If the problem persists, check the system for processes that use too much locked memory;...
Page 31 Recovery Corrective action is application dependent and depends on whether a read or a write was involved or a PROCESS_DEBUG_ or DEBUGPROCESS operation was being used. (%51) A checksum error occurred on a file synchronization block. (device type: 3) Cause A file synchronization block was in error, probably because a user program modified the file-system sync buffer area.
Page 32 For a PROCESS_CREATE_, NEWPROCESS, or NEWPROCESSNOWAIT call, use another process name. (%56) An invalid key was specified; key length passed to CREATE exceeds 255 bytes; or application failed to open an alternate-key file. (device type: 3) Cause An operation on a structured file specified an invalid key, or the key length passed to CREATE exceeds 255 bytes.
Page 33 There was an attempt to use a labeled tape for output that had not expired. There was a mismatch between the DEFINE USE attribute and the current operation on a CLASS tape DEFINE. The DEFINE USE attribute specifies how the tape is to be used: for example, input, output, or extend.
Page 34 Effect The procedure sets the error code and returns without performing the requested operation. Recovery Your system operator might be able to recover the file. (%67) I/O error in disk directory; the file is no longer accessible. (device type: 3) Cause A severe problem occurred on a disk volume used by the file system.
Page 35: Error Occurs During File Open
Error Occurs During File Open Cause The file you attempted to open is marked as corrupt. A utility command such as FUP DUP, FUP LOAD, SQLCI DUP, SQLCI LOAD, or RESTORE has not finished. Effect The procedure sets the error code and returns without performing the requested operation. The file or table cannot be opened.
Page 36 Cause The specified disk volume was physically mounted, but the system has not received a mount request. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Retry the operation after issuing a mount command. (%77) The volume was mounted and the mount is in progress, so a file open is not...
Page 37 If there is a DP2-DP1 label consistency problem, the disk goes down, but the system does not freeze. If the problem occurs just after a cold load, $SYSTEM goes down, and then the monitor process cannot open the OSIMAGE file and the operator process cannot open the log file. Console messages to this effect are issued and, a minute later, the system freezes with code %002002.
Page 38 Cause This error can occur for two reasons: A process called READUPDATE to read a message from $RECEIVE, but the number of outstanding messages read but not replied to equals the receive depth. A process called ACTIVATERECEIVETRANSID or REPLY either with an invalid message tag or when no outstanding message exists.
Page 39 Recovery See the NonStop TM/MP Operations and Recovery Guide (%121) Operation is not valid for a transaction which still has nowait I/Os outstanding on a disk or process file. (device type: 3 or none) Cause The operation was invalid because the transaction had one or more outstanding nowait I/O operations on a disk or process file.
Page 40 Recovery Ensure that devices are enabled for the TMF subsystem. For example, use the command ENABLE VOLUMES through TMFCOM. (%126) BEGINTRANSACTION is disabled either by the operator or because one or more TMF limits have been reached. (device type: not applicable) Cause BEGINTRANSACTION failed due to explicit action by an operator or because one or more audit trails have reached maxfiles, the maximum number of audit files permitted.
Page 41 Recovery See the NonStop TM/MP Application Programmer's Guide (%133) A TMF crash occurred during commitment of the transaction; the transaction may or may not have been committed. (device type: 3) Cause A serious internal error occurred on a system that runs the Transaction Management Facility (TMF) subsystem.
Page 42 Cause The system aborted the transaction because of a processor failure that caused loss of access to a disk. This can be caused by: The disk volume itself down while there is a transaction outstanding against it. A volume cannot access its audit trail. The primary process of a participating disk process fails and the backup takes over.
Page 43 If the cause of the error is that the operation tried to use a CLASS TAPECATALOG DEFINE, the tape request fails. Recovery Ensure that the system has the required microcode. If the cause of the error is that the operation tried to use a CLASS TAPECATALOG DEFINE, you must either use a CLASS TAPE DEFINE in the operation or enable TAPECATALOG DEFINEs.
Page 44 Cause The printer did not return the requested status; either the printer power was off or a hardware problem occurred. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Power up the device or repair it. (%151) Invalid printer VFU buffer.
Page 45 If this process did not enable break and the error occurred during a read operation, recovery is application dependent. NOTE: If more than one process is accessing a terminal when break is used, only break access is allowed after break is entered; subsequent retries are rejected with error 1 10 until normal access is permitted.
Page 46 If the cause of the error is that the operation tried to use a CLASS TAPE DEFINE when this DEFINE class was not supported, you must either use a CLASS TAPECATALOG DEFINE in the operation or enable TAPE DEFINEs. See the DSM/Tape Catalog User's Guide for more information. If the error is due to an incompatibility among the DENSITY, TAPEMODE, and DEVICE attributes of a TAPE DEFINE or TAPECATALOG DEFINE, you must change the DEFINE in accordance with the following rules.
Page 47 Cause This error can occur for the following reasons: A hardware data-parity error occurred and persisted through several retries of the operation. The tape density is higher than the tape drive allows. Effect On a disk or tape READ or READUPDATE, the procedure returns as much (invalid) data as possible.
Page 48 Recovery Corrective action is device dependent and application dependent. If a data-communication process is involved, obtain a trace and save it for your service provider. (%202) Illegal disk address requested, or formatting error occurred. (device type: 3) Cause The requested address was too large for the disk space, or an error occurred during formatting.
Page 49 Recovery Reset the write-protect switch to allow writes. (%210) Disk unit ownership error (dual-port disk). (device type: 3) Cause This error can occur for the following reasons: The driver tried to take ownership of the drive through the controller, and the attempt failed. An incorrect controller address was passed to the disk process.
Page 50 The interprocessor bus monitor process ($IPB or for TorusNet configurations, $IPBn, where n is a number in the range of 1 through 4) reported that the FOX link or TorusNet vertical link to an Expand process is down A subunit or logical unit is not in the started condition Refer to the appropriate subsystem manual for additional information.
Page 51 (device type: 4) Cause A seven-track tape device was specified for an operation requiring a nine-track tape (most HP subsystems require a nine-track tape). Effect The procedure sets the error code and returns without performing the requested operation.
Page 52 Cause An internal system error occurred. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Contact your system operator. (%236) Invalid function code requested for Hyper Link. (device type: 26) Cause An operation specified an invalid Hyper Link function code. Effect The procedure sets the error code and returns without performing the requested operation.
Page 53 Effect The procedure sets the error code and returns without performing the requested operation. Recovery Corrective action is device dependent. If this problem persists and a data communications process is involved, obtain a trace and submit it to your service provider. (%243) EOT received (device type: 7.0, 7.1, 7.2, 7.3, or 7.8) or power at autocall unit is...
Page 54 Recovery Corrective action is device dependent. If this problem persists and a data communications process is involved, obtain a trace and submit it to your service provider. (%250) NAK received on line bid (device type: 7.0, 7.1, 7.3, or 7.8), or auto-call unit failed to clear present-next-digit after digit-present was set (device type: 7.56 or 11).
Page 55 Cause The selected device responded with an invalid control sequence or invalid data. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Corrective action is device dependent. If this problem persists and a data communications process is involved, obtain a trace and submit it to your service provider.
Page 56 Recovery Corrective action usually involves increasing the read count; refer to the manual for the specific device for more information. If this problem persists and a data communications process is involved, obtain a trace and submit it to your service provider. (%262) No address list specified.
Page 57 Recovery Corrective action is application dependent. (%267) SNA session has ended. (device type: 14.2) Cause The file-system procedure call issued by the primary or secondary logical unit could not be performed because the logical-unit-to-logical-unit session associated with the specified device (filenum) no longer exists.
Page 58 Cause The device power was switched off, perhaps due to power failure, then was switched back on during this operation. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Corrective action is device dependent. (%300) Device in diagnose mode;...
Page 59 Recovery Check that the correct tape was mounted. If a mismatch of DEFINE attribute values occurred, modify the DEFINE attribute that did not match the tape label. Use the MEDIACOM INFO TAPELABEL command (on G-series systems) to dump the beginning of the volume group labels on the tape.
Page 60 For a process file, either an attempt was made to write to a nonexistent process or a pending WRITE or WRITEREAD was aborted because the server process read the request using READUPDATE but died before it could reply. For a device, the current path to the device was down. Effect Either the operation never starts, the operation finishes but the path fails before a reply can be made, or the processor fails.
Page 61 Cause A controller or channel failure occurred (path error). Effect The file operation stopped at some indeterminate point. Recovery Corrective action is device dependent and application dependent. (%327) I/O attempted to absent memory page (hardware path error). (device type: any except 2) Cause A hardware failure occurred (path error).
Page 62 Cause An I/O controller tried to write to memory when it should not have done so. Effect The file operation stopped at some indeterminate point. Recovery Corrective action is device dependent and application dependent. (%335) Controller handshake violation (path error). (device type: any except 2) Cause A controller or channel failure occurred (path error).
Page 63 Recovery Corrective action is device dependent and application dependent. (%347) Controller power failed, then restored. (device type: any except 2) Cause The controller power failed and then was restored during this operation (path error). At least one path, and possibly both paths, is operable. Effect The file operation stops at some indeterminate point.
Page 64 Or, the Expand process encountered one of the following situations: The Layer 4 protocol detected a protocol error. An I/O power on occurred but all lines used by the Expand process were attached to the controller for which the IOPON occurred. A processor power on occurred.
Page 65 The line normally exhibits error 248 on the operator console when the line is initially brought up. The message should be followed by another message announcing that the line is up. By performing successive SCF STATS commands (at one minute intervals) and observing the U-FRAME counts, you can determine whether data is being transmitted and received.
Page 66 Cause A network protocol error occurred (path error). Effect The procedure sets the error code and returns without performing the requested operation. Recovery Corrective action is application dependent. If sync depth is greater than 0, keep trying until successful or until a different error is returned. If this problem persists, your service provider needs to run traces or perform other corrective action.
Page 67 Recovery If a block mode application needs to use the device, direct the console to another terminal; the operator process will stop using the device and allow it to be used in block mode. (%1046) File operation attempted at illegal position.
Page 68 Cause The size of an output buffer was too small to hold the data. Error 563 is an operating system error and should not be confused with error 177, which is a data communications error. Effect The operation failed. Recovery Increase the size of the buffer. (%1064) The operation is not supported for this file type.
Page 69 Cause The specified block size is too large. Effect The requested operation is not performed. Recovery Reduce the block size specified in the file creation request to an acceptable value. For format 1 files, the largest allowed value is 4096 bytes. (%1103) The record size specified is too large for the given block size, file type and format.
Page 70 Recovery Update the application to use an interface supporting the full range of alternate key information, for instance by using FILE_GETINFOLIST_ item 106 (%1107) The extent size specified is too large or the maxextents limit is too large. Cause The specified extent size is too large or a maxextents value bigger than 16 is specified for a non-key sequenced partitioned file.
Page 71 Recovery See the EMS log for details about the DSM/TC error. Then see the DSM/Tape Catalog Messages Manual for recovery actions. (%1123) A ZSSI error was returned to $ZSVR. Refer to the EMS log for detailed information. Cause ZSSI returned a fatal error to $ZSVR. Effect The tape request failed.
Page 72 Cause DP2 received an incorrect message sequence number. Effect The operation fails. Recovery Contact your HP service provider. (%1275) FEDEVICEDOWNFORTRANSACTIONS - The disk process received a message from a recovery process that requires that the disk process be in the UP state;...
Page 73 REDO and also requested that audit be generated. Cause The request is not understood by DP2. Effect The operation fails. Recovery Contact your HP service provider. (%1277) FEAUDITTOONEW - 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.
Page 74 DPNameTimeStamp of the disk. Cause When the DPNameTimeStamp of the request does not match the DPNameTimeStamp of the disk process. Effect The operation fails. Recovery Contact your HP service provider. (%1282) FEFILEUNDONEEDED - The disk process encountered a File Label that had its...
Page 75 Effect No change is made to the resource manager directory. Recovery Change the name to be registered and try again if needed. (%1311) FERMOUTSTANDINGTRANS Cause 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.
Page 76 Cause 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_. Effect The operation is not performed. Recovery Determine why the invalid signal value was used or why the TMF sub-system thinks the buffer is invalid.
Page 77 Cause An attempt is made to export a transaction branch with the TFILE not opened in a nowaited manner. Effect The Export will fail. Recovery Open the TFILE in nowaited manner and then export the transaction branch. (%1325) FEIMPORTINVALOP Cause An attempt is made to call ENDTRANSACTION on an imported transaction branch. Effect The ENDTRANSACTION call fails.
Page 78 Cause File recovery cannot be applied to this file because the SQL/MX software version and object version do not match. Effect The file recovery operation fails. Recovery Contact your HP service provider. (%1337) [FEZLTCOMMITHOLD] DP2 cannot guarantee zero lost transactions and has activated commit hold.
Page 79 Cause No space is available in the control block pool to allocate a new control block, or a file or partition open request exceeds the maximum number of opens per volume. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Wait for a few minutes, and then retry.
Page 80 Cause No space is available in the revive pool to allocate a new buffer. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Wait for a few minutes, and then retry. If the problem persists, contact your service provider.
Page 81 Effect The procedure sets the error code and returns without performing the requested operation. Recovery Wait till the server finishes processing other activities and retry the operation. Contact HP support in case of repeated failure. 4000 (%7640...
Page 82 Recovery The requestor's system must be upgraded before the request can be processed. 5002 (%11612) Creation of logical file rejected pending deletion of volume from storage pool. (device type: 3.36, 25.0, or 52.0) Cause A request to create a logical file was rejected because the target physical volume was being deleted from a storage pool.
Page 83 Recovery Appropriate recovery varies according to the file-system error that occurred during access of the PENDOPS file. Refer to the event log to determine the file-system error and take appropriate action. 5013 (%11625) The name range for a physical volume is exhausted.
Page 84 Cause A file-system request (create, purge, or alter) was made against a NonStop Storage Management Foundation (SMF) object, and the reply from the disk process contained an error. This often indicates a HP internal error. Effect The requested operation is not performed.
Page 85 An unexpected error occurred during request processing. (device type: 3.36, 25.0, or 52.0) Cause This error message indicates a HP internal error. Effect The requested operation is not performed. Recovery Refer to the event log for additional information and take action as appropriate. Retry the request.
Page 86 Recovery Wait and retry the request. If the problem persists, bring the SMF process to the DOWN state and then to the UP state before retrying the request again. If the problem still persists, contact your service provider. 5064 (%11710) An error occurred during recovery processing.
Page 87: Error Lists
If you are using the Subsystem Programmatic Interface (SPI) to send commands to a subsystem, you might receive a file-system error list in a response. HP subsystems return such an error list when, in performing your request, they call a file-system procedure directly or indirectly and an error occurs on the call.
Page 88 This subsection does not discuss the mechanics of error-list construction. For information about creating error lists, and for additional information about tokens and token types, and for definitions of tokens whose names begin with ZSPI-, refer to the SPI Programming Manual. Table 5 Conditional Tokens That Can Appear in Any File-System Error List Token Name Token Type...
Page 89: Zfil-Val-Awaitio
Table 5 Conditional Tokens That Can Appear in Any File-System Error List (continued) Token Name Token Type Description ZFIL-TKN-OPENFLAGS ZSPI-TYP-UINT is the number of open flags. ZFIL-TKN-OWNER ZSPI-TYP-BYTE-PAIR is the file owner ID or the CRAID (process ID). ZFIL-TKN- PARTITIONPARAMS ZSPI-TYP-BYTESTRING is the partition parameters.
Page 90: 2: Zfil-Val-Checkclose
ZFIL-TKN-TIMEOUT is the timeout value. Effect The AWAITIO operation fails. 2: ZFIL-VAL-CHECKCLOSE A call to the procedure FILE_CLOSE_CHKPT_ or CHECKCLOSE resulted in a condition code less (CCL). Either the file number supplied in the call is invalid, or the caller's backup no longer exists. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST.
Page 91: 4: Zfil-Val-Checkopen
ZFIL-TKN-CHECKPOINTSTATUS token-type ZSPI-TYP-INT. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. Conditional Tokens ZFIL-TKN-OLDPRIMARY token-type ZSPI-TYP-CRTPID. Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR. Z-SSID is the subsystem identifier ZFIL-VAL-SSID. Z-ERROR is the file-system error code returned in the error parameter of FILEINFO;...
Page 92: 5: Zfil-Val-Checkpoint
ZFIL-TKN-FILENAME is the file name (blank-filled if unknown). Conditional Tokens ZFIL-TKN-FILENUMBER is the number of the file opened in the primary process. ZFIL-TKN-OPENFLAGS is the open flags used by the primary process. ZFIL-TKN-SYNCRECEIVEDEPTH is the sync or receive depth used by the primary process. ZFIL-TKN-BLOCKBUFFER is the address of the sequential block buffer.
Page 93: 6: Zfil-Val-Checkpointmany
ZFIL-TKN-CHECKPOINTSTATUS indicates the status of the call to CHECKPOINT. This token returns a status word in the following form: Value Meaning <0:7>=0 No error <0:7>=1 There is no backup or the primary process cannot communicate with the backup; then <8:15>=file-system error number <0:7>=2 Takeover from the primary;...
Page 94: 7: Zfil-Val-Checkswitch
returned in the error parameter of FILEINFO; it is always zero, since CHECKPOINTMANY does not return an error code. ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-CHECKPOINTMANY (6). ZFIL-TKN-CHECKPOINTSTATUS indicates the status of the call to CHECKPOINTMANY. This token returns a status word in the following form: Value Meaning...
Page 95: 8: Zfil-Val-Control
Conditional Tokens ZFIL-TKN-OLDPRIMARY token-type ZSPI-TYP-CRTPID. Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR. Z-SSID is the subsystem identifier ZFIL-VAL-SSID. Z-ERROR is the file-system error code returned in the error parameter of FILEINFO; it is always is zero, since CHECKPOINT does not return an error code.
Page 96: 9: Zfil-Val-Create
Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR. Z-SSID is the subsystem identifier ZFIL-VAL-SSID. Z-ERROR is the file-system error code returned in the error parameter of FILEINFO. ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-CONTROL (8).
Page 97: 10: Zfil-Val-Keyposition
Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 10: ZFIL-VAL-KEYPOSITION A call to the procedure KEYPOSITION resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZSPI-TKN-PROC-ERR token-type ZSPI-TYP-ENUM. ZFIL-TKN-XFILENAME token-type ZSPI-TYP-STRING.
Page 98: 1: Zfil-Val-Open
1 1: ZFIL-VAL-OPEN A call to the OPEN procedure resulted in a condition code less (CCL) or a condition code greater (CCG). If CCL (ZFIL-TKN-CONDITION=- 1 ), the file is not opened. If CCG (ZFIL-TKN-CONDITION=1), the file is open, but the file system detected an exceptional condition during the OPEN operation. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST.
Page 99: 13: Zfil-Val-Position
ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-PURGE (12). ZFIL-TKN-FILENAME is the file name (blank-filled if unknown). Effect The attempted PURGE operation fails. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section.
Page 100: 15: Zfil-Val-Readlock
ZSPI-TKN-PROC-ERR token-type ZSPI-TYP-ENUM. ZFIL-TKN-XFILENAME token-type ZSPI-TYP-STRING. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. Conditional Tokens ZFIL-TKN-BUFFERADDR token-type ZSPI-TYP-UINT. ZFIL-TKN-COUNTTRANSFERRED token-type ZSPI-TYP-INT. ZFIL-TKN-FILENAME token-type ZSPI-TYP-FNAME. ZFIL-TKN-TAG token-type ZSPI-TYP-INT2. ZFIL-TKN-TRANSFERCOUNT token-type ZSPI-TYP-INT. Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR.
Page 101: 16: Zfil-Val-Readupdate
ZFIL-TKN-COUNTTRANSFERRED is the length of the data read (in bytes). ZFIL-TKN-FILENAME is the name of the file in internal network format. If the file name cannot be represented in this format or if the file name is not known (file-system error 16 occurred), this token will not appear.
Page 102: 17: Zfil-Val-Readupdatelock
ZFIL-TKN-COUNTTRANSFERRED is the length of the data read (in bytes). ZFIL-TKN-FILENAME is the name of the file in internal network format. If the file name cannot be represented in this format or if the file name is not known (file-system error 16 occurred), this token will not appear.
Page 103: 18: Zfil-Val-Reply
Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 18: ZFIL-VAL-REPLY A call to the REPLY procedure resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZSPI-TKN-PROC-ERR token-type ZSPI-TYP-ENUM. ZFIL-TKN-FILENAME token-type ZSPI-TYP-FNAME.
Page 104: 20: Zfil-Val-Setmodenowait
ZFIL-TKN-PARAM1 token-type ZSPI-TYP-INT. ZFIL-TKN-PARAM2 token-type ZSPI-TYP-INT. ZFIL-TKN-LASTPARAMS token-type ZSPI-TYP-INT2. Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR. Z-SSID is the subsystem identifier ZFIL-VAL-SSID. Z-ERROR is the file-system error code returned in the error parameter of FILEINFO. ZSPI-TKN-PROC-ERR is the procedure in which the error occurred.
Page 105: 21: Zfil-Val-Write
ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-SETMODENOWAIT (20). ZFIL-TKN-XFILENAME is the completely qualified file name (including node name) in external format. The token ZFIL-TKN-XFILENAME can be null if certain errors occur. For example, if file-system error 16 (file not opened) occurs, the token will be null.
Page 106: 22: Zfil-Val-Writeread
ZFIL-TKN-FILENAME is the name of the file in internal network format. If the file name cannot be represented in this format or if the file name is not known (file-system error 16 occurred), this token will not appear. ZFIL-TKN-TAG is the AWAITIO tag value. ZFIL-TKN-TRANSFERCOUNT is the request length (in bytes).
Page 107: 23: Zfil-Val-Writeupdate
Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 23: ZFIL-VAL-WRITEUPDATE A call to the WRITEUPDATE procedure resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZSPI-TKN-PROC-ERR token-type ZSPI-TYP-ENUM. ZFIL-TKN-XFILENAME token-type ZSPI-TYP-STRING.
Page 108: 25: Zfil-Val-Awaitiox
ZSPI-TKN-PROC-ERR token-type ZSPI-TYP-ENUM. ZFIL-TKN-XFILENAME token-type ZSPI-TYP-STRING. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. Conditional Tokens ZFIL-TKN-BUFFERADDR token-type ZSPI-TYP-UINT. ZFIL-TKN-COUNTTRANSFERRED token-type ZSPI-TYP-INT. ZFIL-TKN-FILENAME token-type ZSPI-TYP-FNAME. ZFIL-TKN-TAG token-type ZSPI-TYP-INT2. ZFIL-TKN-TRANSFERCOUNT token-type ZSPI-TYP-INT. Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR.
Page 109: 26: Zfil-Val-Checkpointmanyx
Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR. Z-SSID is the subsystem identifier ZFIL-VAL-SSID. Z-ERROR is the file-system error code returned in the error parameter of FILEINFO. ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-AWAITIOX (25).
Page 110: 27: Zfil-Val-Checkpointx
ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-CHECKPOINTMANYX (26). ZFIL-TKN-CHECKPOINTSTATUS indicates the status of the call to CHECKPOINTMANYX. This token returns a status word in the following form: Value Meaning <0:7>=0 No error <0:7>=1 There is no backup or the primary process cannot communicate with the backup; then <8:15>= file-system error number <0:7>=2...
Page 111: 28: Zfil-Val-Keypositionx
def ZFIL-DDL-CHECKPOINTCELL version C00 FOR z-file-sync THROUGH z-file-number end. ZFIL-TKN-OLDPRIMARY token-type ZSPI-TYP-CRTPID. Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR. Z-SSID is the subsystem identifier ZFIL-VAL-SSID. Z-ERROR is the file-system error code returned in the error parameter of FILEINFO;...
Page 112: 29: Zfil-Val-Readlockx
Conditional Tokens ZFIL-TKN-COMPAREKEYLENGTH token-type ZSPI-TYP-BYTE-PAIR. ZFIL-TKN-FILENAME token-type ZSPI-TYP-FNAME. ZFIL-TKN-KEYVALUE token-type ZSPI-TYP-BYTESTRING. ZFIL-TKN-KEYSPEC token-type ZSPI-TYP-INT. ZFIL-TKN-POSITIONMODE token-type ZSPI-TYP-ENUM. Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR. Z-SSID is the subsystem identifier ZFIL-VAL-SSID. Z-ERROR is the file-system error code returned in the error parameter of FILEINFO.
Page 113: 30: Zfil-Val-Readupdatelockx
Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR. Z-SSID is the subsystem identifier ZFIL-VAL-SSID. Z-ERROR is the file-system error code returned in the error parameter of FILEINFO. ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-READLOCKX (29).
Page 114: 31: Zfil-Val-Readupdatex
Conditional Tokens ZFIL-TKN-BUFFERADDRX is the base address of the READUPDATELOCKX buffer. ZFIL-TKN-COUNTTRANSFERRED is the length of the data read (in bytes). ZFIL-TKN-FILENAME is the name of the file in internal network format. If the file name cannot be represented in this format or if the file name is not known (file-system error 16 occurred), this token will not appear.
Page 115: 32: Zfil-Val-Readx
Effect The attempted READUPDATEX operation fails. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 32: ZFIL-VAL-READX A call to the READX procedure resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR.
Page 116: 33: Zfil-Val-Replyx
33: ZFIL-VAL-REPLYX A call to the REPLYX procedure resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZSPI-TKN-PROC-ERR token-type ZSPI-TYP-ENUM. ZFIL-TKN-FILENAME token-type ZSPI-TYP-FNAME. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. Conditional Tokens ZFIL-TKN-BUFFERADDRX token-type ZSPI-TYP-UINT. ZFIL-TKN-TRANSFERCOUNT token-type ZSPI-TYP-INT. ZFIL-TKN-COUNTTRANSFERRED token-type ZSPI-TYP-INT. ZFIL-TKN-RECEIVETAG token-type ZSPI-TYP-INT2.
Page 117: 35: Zfil-Val-Writeupdateunlockx
Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR. Z-SSID is the subsystem identifier ZFIL-VAL-SSID. Z-ERROR is the file-system error code returned in the error parameter of FILEINFO. ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-WRITEREADX (34).
Page 118: 36: Zfil-Val-Writeupdatex
ZFIL-TKN-XFILENAME is the completely qualified file name (including node name) in external format. The token ZFIL-TKN-XFILENAME can be null if certain errors occur. For example, if file-system error 16 (file not opened) occurs, the token will be null. Conditional Tokens ZFIL-TKN-BUFFERADDRX is the base address of the WRITEUPDATEUNLOCKX buffer.
Page 119: 37: Zfil-Val-Writex
ZFIL-TKN-TAG is the AWAITIO tag value. ZFIL-TKN-TRANSFERCOUNT is the request length (in bytes). Effect The attempted WRITEUPDATEX operation fails. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 37: ZFIL-VAL-WRITEX A call to the WRITEX procedure resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST.
Page 120: 38: Zfil-Val-Close
38: ZFIL-VAL-CLOSE A call to the file-system procedure FILE_CLOSE_ or CLOSE resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZSPI-TKN-PROC-ERR token-type ZSPI-TYP-ENUM. ZFIL-TKN-XFILENAME token-type ZSPI-TYP-STRING. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. Conditional Tokens ZSPI-TKN-FILENAME token-type ZSPI-TYP-FNAME. Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR.
Page 121: 65: Zfil-Val-File-Open-Chkpt
Effect The DEVICEINFO2 operation fails. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 65: ZFIL-VAL-FILE-OPEN-CHKPT A call to FILE_OPEN_CHKPT_ returned a nonzero error as the function value. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR.
Page 122: 67: Zfil-Val-File-Open
ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-FILE-CREATELIST (66). ZFIL-TKN-XFILENAME is the completely qualified file name (including node name) in external format. Effect The operation failed. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section.
Page 123: 69: Zfil-Val-File-Close
ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-FILE-CLOSE (69). ZFIL-TKN-XFILENAME is the completely qualified file name (including node name) in external format. The token ZFIL-TKN-XFILENAME can be null if certain errors occur. For example, if file-system error 16 (file not opened) occurs, the token will be null.
Page 124: 71: Zfil-Val-File-Getreceiveinfo
ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-FILE-GETINFOBYNAME (70). ZFIL-TKN-XFILENAME is the completely qualified file name (including node name) in external format. Effect The operation failed. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section.
Page 125: 73: Zfil-Val-File-Getopeninfo
ZFIL-TKN-XFILENAME (second occurrence) is the name of the second file. Effect The operation failed. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 73: ZFIL-VAL-FILE-GETOPENINFO A call to FILE_GETOPENINFO_ returned a nonzero error as the function value. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST.
Page 126: 75: Zfil-Val-File-Rename
Effect The operation failed. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 75: ZFIL-VAL-FILE-RENAME A call to FILE_RENAME_ returned a nonzero error as the function value. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR.
Page 127: 77: Zfil-Val-Filename-Findnext
ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-FILENAME-FINDSTART (76). ZFIL-TKN-XFILENAME is the completely qualified file name (including node name) in external format. Effect The operation failed. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section.
Page 128: 80: Zfil-Val-File-Create
ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-FILENAME-FINDFINISH (78). Effect The operation failed. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 80: ZFIL-VAL-FILE-CREATE A call to FILE_CREATE_ returned a nonzero error as the function value. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST.
Page 129: Sequential I/O Errors
3 Sequential I/O Errors The following error codes are produced by the sequential I/O (SIO) procedures. An application process can use the following SIO procedures to sequentially access files: CHECK^BREAK, CHECK^FILE, CLOSE^FILE, GIVE^BREAK, NO^ERROR, OPEN^FILE, READ^FILE, SET^FILE, TAKE^BREAK, WAIT^FILE, and WRITE^FILE. The error number is returned as the function result from the procedure call.
Page 130 Recovery Do not attempt the SIO operations listed above. SIOERR^INVALIDBUFADDR: The specified buffer address is invalid. A valid address is within 'G' Cause The buffer was not within 'G'[0:32767] of the user data area. This error is returned by OPEN^FILE if the block buffer fails the test, or by READ^FILE and WRITE^FILE if the data buffer fails the test.
Page 131 Recovery Correct the record length. SIOERR^INVALIDEDITFILE: The specified file is not a valid EDIT file. Cause The directory indicates that the EDIT file is damaged. This error is returned only by OPEN^FILE. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Refer to “EDITREAD and EDITREADINIT Errors”...
Page 132 buffer, or the next physical transfer began at an odd byte. However, the attempt failed. This error is returned only by WRITE^FILE. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Increase the run-time memory size if it is less than 32K bytes; otherwise, move one or more nonstring arrays to upper memory.
Page 133 Recovery Contact your service provider. SIOERR^CHECKSUMCOMM: A discrepancy was detected between the common FCB checksum and the previous checksum. Cause While performing a checksum on the common file control block (FCB), the system encountered a discrepancy between this checksum and the previous checksum. This error is returned by all procedures.
Page 134 Recovery Do not attempt the SIO operation listed above. SIOERR^PAGEWRITE^OVERFLOW: The highest possible page in EDIT file has been written. Cause While writing the data to the edit file, the SIO procedure call attempted to write a page above the edit file limit, where the page limit is 64,000 pages. Effect Data cannot be written further in the edit file.
Page 135: Define Errors
4 DEFINE Errors This section contains errors that relate specifically to DEFINE attribute sets. DEFINE errors can occur when you create, save, restore, delete, or otherwise manipulate DEFINEs of any class using the DEFINE procedures. Error Codes This subsection lists each DEFINE error code and provides a description of each code. (%000000) Successful completion.
Page 136 Effect The procedure returns the error code and does not perform the requested operation. Recovery Wait, then try again. If the problem persists, check the system for processes that use too much memory. 2054 (%004006) There was a bounds error in a parameter.
Page 137 If the consistency check failed for a TAPE DEFINE, the consistency check number returned indicates the cause: Code Meaning Use RETENTION or EXPIRATION, not both. USE IN and USE EXTEND require LABELS ANSI, LABELS IBM, or LABELS IBMBACKUP. In addition, if REELS is specified, the value must equal the number of volumes listed for VOLUME.
Page 138 Code Meaning 1 17 GEN cannot be specified as a relative generation when USE OUT is used. 1 18 GEN cannot be +1 when USE IN is used. Effect If the operation is DEFINESAVE, the working set is saved. If the operation is DEFINERESTORE, the saved DEFINE is restored to the working attribute set.
Page 139 Effect The procedure returns the error code and does not perform the requested operation. Recovery You cannot reset a required DEFINE attribute. 2066 (%004022) A required parameter is missing. Cause A required parameter was not supplied. Effect The procedure returns the error code and does not perform the requested operation. Recovery Add the missing parameter, then reissue the request.
Page 140 DEFINE because the =_DEFAULTS DEFINE is always present. 2081 (%004041) Bad internal format. Cause Some internal error occurs during DEFINE propagation. Effect Process creation fails. Recovery Retry the operation. Contact HP support in case of repeated failure. 140 DEFINE Errors...
Page 141: Newprocess And Newprocessnowait Errors
5 NEWPROCESS AND NEWPROCESSNOWAIT Errors The following error codes and error lists are produced by the process-control procedures NEWPROCESS and NEWPROCESSNOWAIT. These procedures can only create processes with process identification numbers (PINs) in the low range of 0 through 254. The NEWPROCESS and NEWPROCESSNOWAIT procedures return errors in a format that is different from other procedures.
Page 142 Recovery Either correct the coding error, use linker (Binder or nld utility) to add the procedure to the code area or user library, or refer the call to a procedure that is already present in the application program. (%001000) NO PCB AVAILABLE Cause All entries in the configured process control block (PCB) table for the processor were in use or the process required a low PIN but none were available.
Page 143 Table 6 NEWPROCESS Error 6 Error Subcodes (continued) Decimal Octal Meaning %007 The library file does not have the correct file structure. %010 The program file requires a later version of the operating system. %01 1 The library file requires a later version of the operating system. %012 The program file does not have a main procedure.
Page 144 Table 6 NEWPROCESS Error 6 Error Subcodes (continued) Decimal Octal Meaning %057 Library file has entry in TNS/R fixup list with invalid external entry-point (XEP) index value or invalid code address value. %060 Accelerated program file has external procedure identifier list (EPIL), internal procedure identifier list (IPIL), or external entry-point (XEP) table with incorrect format.
Page 145 Table 6 NEWPROCESS Error 6 Error Subcodes (continued) Decimal Octal Meaning %124 The code area of the program file is too large. %125 The code area of the library file is too large. %126 The program file has a gateway (GW) table but no callable procedures. %127 The library file has a gateway (GW) table but no callable procedures.
Page 146 Table 6 NEWPROCESS Error 6 Error Subcodes (continued) Decimal Octal Meaning 1 12 %160 The program file specifies too many shared run-time libraries (SRLs). 1 13 %161 The library file specifies too many shared run-time libraries (SRLs). 1 14 %162 The program file specifies duplicate shared run-time libraries (SRLs).
Page 147 Cause The system monitor encountered a file-system error while accessing library file during process creation. Effect File-system error number %nnn is returned in error.<8:15>. No process is created. Recovery Refer to “File-System Errors” (page 19) for corrective action for error number %nnn. (%006000) PROGRAM FILE AND LIBRARY FILE ARE THE SAME Cause The program file and library file are the same file.
Page 148 Bits <8:15> contain a subcode that indicates the cause of the error, as follows: Subcode Meaning Unable to convert a DEFINE name to network form. Internal error. Illegal DEFMODE supplied. Effect No process is created. Recovery Retry the call to NEWPROCESS. If errors recur, contact your service provider. (%011000) OBJECT FILE WITH AN ILLEGAL DEVICE SUBTYPE...
Page 149 Recovery If insufficient PFS space was the cause of this error, either try to free up more PFS space or wait for more PFS space to become available. (%014000 + %nnn) UNKNOWN ERROR Cause An error was received when an attempt was made to start a process on a remote system. Your system does not know how to interpret the error.
Page 150 Cause An error occurred during an attempt to obtain or propagate security identity information. Effect The call returns the file-system error number % nnn in errinfo.<8:15>. No process is created. Recovery Refer to “File-System Errors” (page 19) for corrective action for the file-system error returned in errinfo.<8:15>.
Page 151 Recovery Use the original object files and the nld utility to re-create the program file. If the error recurs, contact your service provider. (%022000 + %nnn) UNKNOWN SRL SPECIFIED BY PROGRAM Cause The system was unable to find a shared run-time library (SRL) specified by the program file. Effect No process is created.
Page 152 Effect %nnn in error.<8:15> contains the SRL number of the licensed SRL. No process is created. Recovery License the program file, if possible. (%025000 + %nnn) SRL SECURITY VIOLATION Cause A security violation occurred. Either the program file or a shared run-time library (SRL) is licensed, but another SRL is not licensed.
Page 153 Recovery Use the original object files and the nld utility to re-create the program file. (%031400) INCORRECT NUMBER OF SRLS IN LIBRARY Cause The number of shared run-time libraries (SRLs) specified for the library file is incorrect. Effect No process is created, and a message is printed on the home terminal. For example: PID: \SAT.0,36 \SAT.$DATA.MDTUNRES.TC03 (ELF) SRL-Client References Symbols Not Found In Nominated SRL: Prg: \SAT.$DATA.MDTUNRES.TC03E ->...
Page 154: Error Lists
If you are using the Subsystem Programmatic Interface (SPI) to send commands to a subsystem, you might receive a NEWPROCESS or NEWPROCESSNOWAIT error list in a response. HP subsystems return such an error list when, in performing your request, they call the NEWPROCESS or NEWPROCESSNOWAIT procedure directly or indirectly and an error occurs on the call.
Page 155: 3: Zgrd-Val-Newprocess
3: ZGRD-VAL-NEWPROCESS There was an error during a call to NEWPROCESS. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZSPI-TKN-PROC-ERR token-type ZSPI-TYP-ENUM. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. Conditional Tokens ZGRD-TKN-OBJECTFILE token-type ZSPI-TYP-FNAME. ZGRD-TKN-LIBRARYFILE token-type ZSPI-TYP-FNAME. ZGRD-TKN-SWAPFILE token-type ZSPI-TYP-FNAME. ZGRD-TKN-PRIORITY token-type ZSPI-TYP-UINT. ZGRD-TKN-MEMORYPAGES token-type ZSPI-TYP-BYTE.
Page 156: 4: Zgrd-Val-Newprocessnowait
4: ZGRD-VAL-NEWPROCESSNOWAIT There was an error during a call to NEWPROCESSNOWAIT. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZSPI-TKN-PROC-ERR token-type ZSPI-TYP-ENUM. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. Conditional Tokens ZGRD-TKN-OBJECTFILE token-type ZSPI-TYP-FNAME. ZGRD-TKN-LIBRARYFILE token-type ZSPI-TYP-FNAME. ZGRD-TKN-SWAPFILE token-type ZSPI-TYP-FNAME. ZGRD-TKN-PRIORITY token-type ZSPI-TYP-UINT. ZGRD-TKN-MEMORYPAGES token-type ZSPI-TYP-BYTE.
Page 157: Process Creation Errors
6 Process Creation Errors The following error codes and error lists are produced by the PROCESS_LAUNCH_ and PROCESS_CREATE_ procedures, which create a Guardian process. Most of the error codes are also returned by the PROCESS_SPAWN_ procedure, which creates an Open System Services (OSS) process.
Page 158 Cause A file-system error occurred on the program file during process creation. The error-detail contains a file-system error number. Effect No process is created. Recovery Refer to “File-System Errors” (page 19), for corrective action for the file-system error returned in the error-detail information. PARAMETER ERROR Cause The call contained an invalid combination of options.
Page 159 Table 7 Error Subcodes for PROCESS_LAUNCH_ and PROCESS_SPAWN_ Errors 2 and 3 (continued) error- detail PROCESS_LAUNCH_ Structure Field or PROCESS_SPAWN_ Structure Field or Parameter in Error Parameter in Error The program image file is in error. This The program image file is in error. This error subcode error subcode is returned if is returned if PROCESS_SPAWN_ is called from COUP;...
Page 160 Recovery Refer to “File-System Errors” (page 19), for corrective action for the file-system error returned in the error-detail information. FILE SYSTEM ERROR ON PFS Cause An error occurred during the creation of the process file segment (PFS). The error-detail information contains the error number of the file-system error that occurred. Effect The procedure sets the error code and returns without performing the requested operation.
Page 161 Cause An error was detected in the file format of the Program file. The error-detail information contains an error subcode that indicates the invalid file format error. These errors are listed in Table 8 (page 161). Effect No process is created. Recovery Take corrective action as indicated by the subcode.
Page 162 Table 8 Error Subcodes for Process Creation Errors 12, 13, 70, 76, 84, and 3xx (continued) Subcode Meaning File has entry in TNS/R fixup list with invalid external entry-point (XEP) index value or invalid code address value. Accelerated file has external procedure identifier list (EPIL), internal procedure identifier list (IPIL), or external entry-point (XEP) table with incorrect format.
Page 163 The file either is not targeted for this system, is not an ELF file, or has been corrupted. The file is not executable because it has more than one instance of a header structure unique to HP NonStop Server systems. An error occurred during the linking of the file.
Page 164 PID: \SYS10.4,94 \SYS10.$XL.SVOL.TEST (TNS) External References Not Resolved to Any User/System Library: Prg: \SYS10.$XL.SVOL.TEST -> MY_PROC (PROC) Undefined externals where MY_PROC is the name of the undefined external procedure in the program file \SYS10.$XL.SVOL.TEST. When the operating system finds a call to an undefined external procedure, it replaces the original call with a call to the PROCESS_DEBUG_ procedure.
Page 165 Created from licensed program files Created from program files owned and provided by the super ID Subtypes 1 through 47 are reserved for HP use. Effect No process is created. Recovery Verify either that the call specifies a process name or that the program file is marked as "must run named"...
Page 166 Recovery Retry the call. If errors recur, contact your service provider. DYNAMIC IOP ERROR Cause This error is returned only to privileged callers, or unprivileged callers attempting to use certain privileged features. On G series, it can be returned by an attempt to create a D-series I/O Process.
Page 167 Cause An error occurred during an attempt to obtain or propagate security identity information. The error-detail information contains the number of the file-system error that occurred. Effect No process is created. Recovery Refer to “File-System Errors” (page 19), for corrective action for the file-system error returned in the error-detail information.
Page 168 Cause The main stack maximum value is too large. Effect No process is created. Recovery Either change the procedure call (if applicable) or use the nld utility to change the object file to specify a new value that is within the valid range. THE HEAP MAXIMUM VALUE, SPECIFIED EITHER BY THE PROCEDURE CALL OR BY THE OBJECT FILE, IS TOO LARGE Cause The heap maximum value is too large.
Page 169 Recovery Use the original object files and the nld utility to re-create the program file. If the error recurs, contact your service provider. PROGRAM FILE REQUIRES FIXUPS TO A SHARED RUN-TIME LIBRARY (SRL) BUT THE PROGRAM FILE IS CURRENTLY RUNNING Cause The process creation request specifies too many shared run-time libraries (SRLs);...
Page 170 Recovery Either remove the licensing of the program, if possible, or use the nld utility to specify another SRL. THE PROGRAM FILE REQUIRES A SYMBOL FROM A SHARED RUN- TIME LIBRARY (SRL) BUT THE SRL IS NOT EXPORTING IT Cause The program file requires a symbol from a shared run-time library (SRL) but the SRL is not exporting it;...
Page 171 Recovery Retry the call. If this error recurs, contact your service provider. A SHARED RUN-TIME LIBRARY (SRL) HAS UNDEFINED EXTERNALS Cause A shared run-time library (SRL) has undefined externals; the error-detail information contains the SRL number of the SRL that has undefined externals. Effect No process is created.
Page 172 Recovery Use the original object files and the nld utility to recreate the program file. EXTERNAL DATA REFERENCES NOT RESOLVED TO ANY USER/SYSTEM LIBRARY Cause An anonymous data symbol reference was not located in a UL, Native UL, or system library. Effect No process is created, and a message is printed on the home terminal.
Page 173 Cause The system couldn't honor the floattype attribute for the user library requested by a process-creation request. The error-detail information contains an error subcode that indicates the nature of the error. The error-detail indicates: 2: Unrecognized floating-point specification in file. 4: This library specified Tandem floating-point, which mismatches the program.
Page 174 Cause A file system error occurred on the runtime loader library while attempting the process creation. The error-detail contains a file-system error number. Effect No process is created. Recovery Refer to Section 2, File-System Errors, for corrective action for the file-system error returned in the error-detail information.
Page 175 Recovery Use the information reported on the home terminal, and attempt to fix the problem. (Either fix the code in the caller or the callee, or get a version of code that does not make the faulty call.) A FILE SYSTEM ERROR WAS ENCOUNTERED ON A DLL Cause A file system error occurred on a DLL while attempting the process creation.
Page 176 16- RLD failed to pass to the operating system a function pointer necessary to process the initialization functions, constructor callers, destructor callers, or termination functions specified to the linker. 17- The specified loadfile was built with linker option -no_runtime_fixup, but it is not preset to load with the symbol bindings available on this system or in this process.
Page 177 16- Contact your service provider. Report the error code and the error detail. 17-Relink the file if the environment changes, or don't set the option if the same file must be used simultaneously in different environments. Contact your service provider. Report the file name, error code, and the error detail.
Page 178 Recovery For detail 3: Each call on dlopen() generates a new handle; avoid a large number of calls specifying the same path argument. For the others: Contact your service provider, and report the error and the error detail. ERROR LOADING A DROP-IN PROGRAM Cause A failure occurred while loading or running a program that must be "dropped in"...
Page 179 Recovery Take corrective action as indicated by the error subcode. In many cases, the object file was improperly built or corrupted. Consider relinking and recompiling the file. ERROR IN PRELOADING A PUBLIC DLL Cause A failure occurred while attempting to preload a public DLL specified in the zreg file. Error details are: 1- The export digest of the public DLL is not a match to the export digest found in the specified zreg file.
Page 180 Cause (This error is returned only by PROCESS_SPAWN_.) An error occurred during the allocation of user data space for static variables used by the system library. The error-detail information contains the error number of the file-system error that occurred. Effect No process is created. Recovery Refer to “File-System Errors”...
Page 181 Recovery Determine corrective action by referring to the Open System Services System Calls Reference Manualfor a description of the OSS open() function errno values. OSS FILE DESCRIPTOR OPEN TIMEOUT ERROR Cause (This error is returned only by PROCESS_SPAWN_.) The timeout value in the ZSYS-DDL-FDINFO.Z-TIMEOUT field of the fdinfo parameter was reached before the file descriptors specified in the fdinfo parameter could be opened.
Page 182: Error Lists
If you are using the Subsystem Programmatic Interface (SPI) to send commands to a subsystem, you might receive an error list in a response. HP subsystems return such an error list when, in performing your request, they call the PROCESS_LAUNCH_ or PROCESS_CREATE_ procedure directly or indirectly and an error occurs on the call.
Page 183: Unconditional Tokens
ZGRD-TKN-PROCESSDESCR token-type ZSPI-TYP-STRING. ZGRD-TKN-XHOMETERM token-type ZSPI-TYP-STRING. ZGRD-TKN-JOBID token-type ZSPI-TYP-INT. ZGRD-TKN-XMEMORYPAGES token-type ZSPI-TYP-INT. ZGRD-TKN-CREATEOPTIONS token-type ZSPI-TYP-UINT. ZGRD-TKN-DEBUGOPTIONS token-type ZSPI-TYP-UINT. ZGRD-TKN-PFS-SIZE token-type ZSPI-TYP-INT2. Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR. Z-SSID is the subsystem identifier ZGRD-VAL-SSID. Z-ERROR is the 16-bit error code returned in the error parameter of PROCESS_CREATE_.
Page 184: 25: Zgrd-Val-Process-Launch
25: ZGRD-VAL-PROCESS-LAUNCH A call to PROCESS_LAUNCH_ failed due to an error. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZSPI-TKN-PROC-ERR token-type ZSPI-TYP-ENUM. ZSPI-TKN-ERRORDETAIL token-type ZSPI-TYP-INT. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. Conditional Tokens ZGRD-TKN-XOBJECTFILE token-type ZSPI-TYP-STRING. ZGRD-TKN-XLIBRARYFILE token-type ZSPI-TYP-STRING. ZGRD-TKN-XSWAPFILE token-type ZSPI-TYP-STRING. ZGRD-TKN-EXTSWAPFILE token-type ZSPI-TYP-STRING.
Page 185: Effect
ZGRD-TKN-HEAP-MAX is the maximum size, in bytes, of the process heap, if a nondefault value was specified. This token is applicable only to TNS/R native processes. ZGRD-TKN-SPACE-GUARANTEE is the maximum size, in bytes, of the amount of space to be reserved with the Kernel-Managed Swap Facility (KMSF), if a nondefault value was specified.
Page 186: Process_Getinfolist_ Errors
7 PROCESS_GETINFOLIST_ Errors The PROCESS_GETINFOLIST_ procedure is used to obtain detailed information about a particular process or about processes within a processor that meet a specified list of search criteria. The process of interest can be specified either by process handle or by node name, processor number, and PIN.
Page 187 Effect The procedure sets the error code; the error-detail parameter contains the number of the parameter in error. Recovery Pass a correct reference address to PROCESS_GETINFOLIST_. SPECIFIED PROCESS DOES NOT EXIST Cause The specified process does not exist or does not meet the search criteria. Effect The information returned is for higher-numbered processes;...
Page 188 Recovery Correct the attribute value, then try again. INVALID RETURN ATTRIBUTE CODE Cause The return attribute code was not valid; the error-detail parameter contains the invalid code. This error can occur if the attribute index is unrecognized, or if a non-zero auxiliary data size is specified for an attribute that does not require auxiliary data.
Page 189 Recovery Do not specify this attribute code in et-attr-list when the srch-option is 1 or 2. Attribute restricted to privileged callers. Causeerror-detailcontains the attribute code. Effect The procedure sets the error code and puts the attribute code in error-detail. Recovery Avoid using this attribute, or use it in a call from a function running in priviliged mode. Error Codes 189...
Page 190: Process_Getpairinfo_ Errors
8 PROCESS_GETPAIRINFO_ Errors The PROCESS_GETPAIRINFO_ procedure retrieves basic information about a process pair. The caller can specify a process handle or process descriptor, or can search through the named processes in a given system. The PROCESS_GETINFO_ procedure should be used when the caller requires only selected information about a particular process.
Page 191 Effect Information is successfully returned. Recovery None required. PROCESS IS UNNAMED Cause The process is not a named process. Effect No information is returned because the process is unnamed. The process can be the caller. Recovery No recovery action is required. Call PROCESS_GETINFO_ or PROCESS_GETINFOLIST_ to obtain the process descriptor.
Page 192: Process_Spawn_ Open System Services (Oss) Errors
The PROCESS_SPAWN_ Guardian error codes are the values returned to the calling process in the ZSYS-DDL-PROCESSRESULTS.Z-TPCERROR field of the process-results parameter. For many classes of Guardian errors, additional information is returned in the ZSYS-DDL-PROCESSRESULTS.Z-TPCDETAIL field of the process-results parameter. Guardian process creation error codes returned by PROCESS_SPAWN_ are also returned by PROCESS_CREATE_.
Page 193 Recovery Create a file with the specified pathname or specify a pathname that exists. 4005 I/O ERROR Cause A physical input or output error occurred during an attempt to create or access a file. The corresponding OSS errno value is EIO. Recovery Corrective action is application dependent.
Page 194 the size with the Binder. If the process name selected is already in use, then choose another process name and call PROCESS_SPAWN_ again. 4012 INSUFFICIENT USER MEMORY Cause There is insufficient user memory to create the OSS process. The new process image requires more memory than is allowed by the hardware or system-imposed memory management constraints.
Page 195: Error Lists
If you are using the Subsystem Programmatic Interface (SPI) to send commands to a subsystem, you might receive a PROCESS_SPAWN_ error list in a response. HP subsystems return such an error list when, in performing your request, they call the PROCESS_SPAWN_ procedure directly or indirectly and an error occurs on the call.
Page 196: Unconditional Tokens
ZGRD-TKN-SWAP-PATH token-type ZSPI-TYP-STRING. ZGRD-TKN-EXTSWAP-PATH token-type ZSPI-TYP-STRING. ZGRD-TKN-TERM-PATH token-type ZSPI-TYP-STRING. ZGRD-TKN-CWD-PATH token-type ZSPI-TYP-STRING. ZGRD-TKN-FD-PATH token-type ZSPI-TYP-STRING. ZGRD-TKN-FDINFO token-type ZSPI-TYP-BYTESTRING. ZGRD-TKN-ARG token-type ZSPI-TYP-STRING. ZGRD-TKN-ENV token-type ZSPI-TYP-STRING. ZGRD-TKN-PROCESS-EXTENSION token-type ZSPI-TYP-BYTESTRING. ZGRD-TKN-PATH token-type ZSPI-TYP-STRING. Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR.
Page 197: Recovery
Recovery Follow the recovery procedure for the returned PROCESS_SPAWN_ errors as described earlier in this section. Error Lists 197...
Page 198: Allocatesegment Errors
Recovery Specify a valid extended data segment ID, then retry the operation. User processes can specify an extended data segment ID equal to 1023 or less; only processes supplied by HP can specify an extended data segment ID greater than 1023.
Page 199 Effect The procedure sets the error code and returns without allocating the extended data segment. Recovery Correct the call to ALLOCATESEGMENT so that the options are correct and in the proper order. UNABLE TO ALLOCATE SEGMENT SPACE Cause ALLOCATESEGMENT could not allocate extended data segment space. Effect The procedure sets the error code and returns without allocating the extended data segment.
Page 200: Error Lists
Recovery Make sure the PIN specified in pin-and-flags is not the PIN of the calling process. REQUESTED SEGMENT IS CURRENTLY BEING RESIZED Cause Either the requested segment cannot be accessed by SEGMENT_ALLOCATE_ until the current resizing operation is complete or the requested segment is a shared selectable segment but the allocated segment is a flat segment.
Page 201: Conditional Tokens
Conditional Tokens ZGRD-TKN-OBJECTFILE is the name of the object file containing the ALLOCATESEGMENT procedure call in internal format. ZGRD-TKN-SEGMENTID is the extended data segment ID requested. ZGRD-TKN-SEGMENTSIZE is the extended data segment size in bytes. ZGRD-TKN-FILENAME is the swap file name. ZGRD-TKN-PINANDFLAGS contains the value of the pin-and-flags parameter: Value Meaning...
Page 202: 1 Segment_Allocate_ And Segment_Allocate64_ Errors
1 1 SEGMENT_ALLOCATE_ and SEGMENT_ALLOCATE64_ Errors This section lists and describes the error codes and error lists associated with the SEGMENT_ALLOCATE_ and SEGMENT_ALLOCATE64_ procedure. The SEGMENT_ALLOCATE_ and SEGMENT_ALLOCATE64_ error codes are the values returned in the error parameter to SEGMENT_ALLOCATE_. The same error codes are returned by SEGMENT_ALLOCATE_CHKPT_. Error codes and error lists associated with the ALLOCATESEGMENT procedure are described in “ALLOCATESEGMENT Errors”...
Page 203 Effect The procedure sets the error code and returns without allocating the extended data segment. Recovery Specify a valid segment ID, then retry the operation. User processes can specify a segment ID equal to 1023 or less; only processes supplied by HP can specify a segment ID greater than 1023.
Page 204 Effect The procedure sets the error code and returns without allocating the extended data segment. Recovery Make sure the calling process access ID is one of the following: The same as the process whose process identification number (PIN) is specified in the SEGMENT_ALLOCATE_ call.
Page 205: Error Lists
If you are using the Subsystem Programmatic Interface (SPI) to send commands to a subsystem, you might receive a SEGMENT_ALLOCATE_ error list in a response. HP subsystems return such an error list when, in performing your request, they call the SEGMENT_ALLOCATE_ procedure directly or indirectly and an error occurs on the call.
Page 206: Unconditional Tokens
Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR. Z-SSID is the subsystem identifier ZGRD-VAL-SSID. Z-ERROR is the error code returned in the error parameter of SEGMENT_ALLOCATE_. ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZGRD-VAL-SEGMENT-ALLOCATE (21).
Page 207: Usesegment Errors
12 USESEGMENT Errors This section contains the error list associated with the USESEGMENT procedure. There are no error codes associated with USESEGMENT; USESEGMENT does not return error codes. Note that the USESEGMENT procedure is similar to the SEGMENT_USE_ procedure. You would typically use the SEGMENT_USE_ procedure on D-series and later releases, while you used the USESEGMENT procedure on C-series releases.
Page 208: Conditional Tokens
ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZGRD-VAL-USESEGMENT (2). Conditional Tokens ZGRD-TKN-OBJECTFILE is the name of the object file that contains the USESEGMENT procedure call in internal format. ZGRD-TKN-SEGMENTID is the extended data segment ID requested. ZGRD-TKN-OLDSEGMENT is the extended data segment ID returned.
Page 209: Segment_Use_Errors
13 SEGMENT_USE_Errors This section contains the error list associated with the SEGMENT_USE_ procedure. This procedure selects a particular extended data segment to be currently addressable by the calling process. Note that the SEGMENT_USE_ procedure is similar to the USESEGMENT procedure. You would typically use the SEGMENT_USE_ procedure on D-series and later releases, while you used the USESEGMENT procedure on C-series releases.
Page 210: Conditional Tokens
User processes can specify a segment ID equal to 2047 or less. Only processes supplied by HP can specify a segment ID greater than 2047. If the error code is 5 (segment ID not found), the SEGMENT_USE_ call specified a segment ID (in the new-segid parameter) that has not been allocated.
Page 211: Subsystem Programmatic Interface (Spi) Errors
14 Subsystem Programmatic Interface (SPI) Errors This section lists and describes the error numbers issued by the Subsystem Programmatic Interface (SPI) procedures and the error lists associated with those procedures. Error Codes The following pages describe the SPI error numbers. These numbers are the values returned in the status parameter on calls to the SPI procedures.
Page 212 The program supplied an SPI-defined token code that was invalid for this procedure call. For example, ZSPI-TKN-DELETE was specified in a call to SSGET, or ZSPI-TKN-COMMAND was specified in a call to SSPUT. An invalid position descriptor was supplied with ZSPI-TKN-POSITION. Effect The header token ZSPI-TKN-LASTERR is set to this error number, and the requested operation is not completed.
Page 213 Effect The header token ZSPI-TKN-LASTERR is set to this error number, and the requested operation is not completed. Recovery For the first cause, use a larger buffer. For the second cause, recovery is application-dependent. ZSPI-ERR-XSUMERR Invalid checksum Cause The current buffer checksum does not match the checksum computed on return from the last SPI call.
Page 214 Cause An illegal token code or token map was supplied in the procedure call. Possible causes for this error include: The token data type was not recognized. For example, a program used a token data type not included in the standard SPI definitions. The only token data types permitted by SPI are those defined by SPI.
Page 215 Cause A file-system error occurred. Effect The requested operation is not completed. Recovery Corrective action depends on the error. Check Table 1 1 for an explanation of the status- 1 and status-2 parameters. Table 1 1 Supplementary Status Values Error status- 1 status-2 Explanation...
Page 216: Error Lists
Recovery Recode your program to format only one buffer at a time. Error Lists If a HP subsystem calls an SPI procedure and an SPI error occurs—that is, the call returns a nonzero value in status—the subsystem normally attempts to recover from the error. If it can't recover (for example, when the application program buffer is corrupted), the subsystem returns information to the application in an error list.
Page 217: Conditional Tokens
Conditional Tokens ZSPI-TKN-SSID-ERR is the ssid parameter passed in the call that failed. This token appears only if ssid was omitted in the call that failed. Effect The call to SSGET or SSGETTKN fails. Recovery Follow the recovery procedure for the returned SPI error code as described earlier in this section. Error From SSINIT A call to SSINIT returned an error.
Page 218: Conditional Tokens
ZINDEX is the source-index parameter passed in the call that failed; ZINDEX is 0 if source-index was omitted in the call that failed. ZOFFSET is 0. Conditional Tokens ZSPI-TKN-SSID-ERR is the ssid parameter passed in the call that failed. This token appears only if ssid was omitted in the call that failed.
Page 219: Unconditional Tokens
Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR. Z-SSID is the SPI subsystem identifier ZSPI-VAL-SSID. Z-ERROR is the status value from the SPI procedure SSPUT or SSPUTTKN. ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZSPI-VAL-SSPUT (7) or ZSPI-VAL-SSPUTTKN (8).
Page 220: Editread And Editreadinit Errors
15 EDITREAD and EDITREADINIT Errors This section lists and describes the errors returned in the status parameter of EDITREAD and EDITREADINIT procedure calls. Error Codes This subsection lists each EDITREAD and EDITREADINIT procedure error code and provides a description of each code. 0 or greater NO ERROR Cause The call was completed successfully.
Page 221 Cause EDITREAD returns this error if the sequence number of the line about to be read is one of the following: Less than that of its predecessor. Greater than 99999.999. Greater than the largest sequence number in the directory entry for the file page containing the line about to be read.
Page 222: Ioedit Errors
16 IOEdit Errors IOEdit allows the run-time libraries of the compilers supported on the operating system to read and write EDIT format files. An application process can use the following IOEdit procedures to access files IOEdit Errors. BACKSPACEEDIT INITIALIZEEDIT CLOSEALLEDIT NUMBEREDIT CLOSEEDIT OPENEDIT...
Page 223 Recovery Correct the request. (%12) FILE/RECORD ALREADY EXISTS Cause This error is returned when the same file has already been processed by a previous call. IOEdit does not support multiple concurrent opens of the same file. IOEdit returns this error when trying to write a record having the same EDIT line number as a record already in the file.
Page 224: Error Codes Unique To Ioedit
Recovery Call EXTENDEDIT to increase the file's capacity, then try the call to WRITEEDIT again. (%56) INVALID KEY SPECIFIED Cause Several IOEdit procedures return this error when the EDIT line number specified in the call is less than -3 or greater than 99999999. Effect The request is ignored.
Page 225 Recovery Proceed as described at the beginning of this subsection. (a block number in the directory is outside the file) Cause A directory error occurred in an EDIT file. Effect Processing stops. Recovery Proceed as described at the beginning of this subsection. (duplicate block numbers in the directory) Cause A directory error occurred in an EDIT file.
Page 226: Catastrophic Error Messages
Recovery The file is bad but possibly most of the file's contents could be recovered by copying the entire file and ignoring only the records having this error. (cannot do renumbering) Cause NUMBEREDIT returns this error when the parameters represent disallowed renumbering: the first new record number is not greater than that of the record preceding the first record to be renumbered, the new record number increment is zero or negative, or no records are affected.
Page 227 much larger than was apparent when the program was compiled and bound. When the stack is about to overflow due to such an action, IOEdit issues this message rather than allowing a mysterious trap to occur. The user should rearrange global primary, global secondary, and the stack space use of the calling procedures leading to the call to IOEdit to increase the space available for the stack within IOEdit.
Page 228: Formatter Errors
17 Formatter Errors The following errors are returned by the FORMATDATA and FORMATDATAX procedures. The error code is returned as the resulting value from the procedure call. For additional information about the FORMATDATA[X] procedures, refer to the Guardian Programmer's Guide. Error Codes This subsection lists each FORMATDATA[X] procedure error code and provides a description of each code.
Page 229 Effect The procedure sets the error code and returns without performing the requested operation. Recovery Correct the format or the data list. BAD FORMAT Cause The format contains an edit descriptor that is valid for output but not for input. For example, I5.5 is invalid for input.
Page 230: Initializer Errors
18 INITIALIZER Errors The following error messages are returned by the INITIALIZER procedure. No error numbers are returned from this procedure call. For additional information about the INITIALIZER procedure, refer to the Guardian Programmer's Guide and the Guardian Procedure Calls Reference Manual. The following messages indicate fatal coding or internal errors and are issued only when the program calls the ABEND procedure.
Page 231 Cause The cause of this error can be one of the following: The INITIALIZER procedure was called by a TNS/R native process that did not specify the required num^fcbs parameter. A negative number of file control blocks (FCBs) was specified in the num^fcbs parameter. A positive number of file control blocks (FCBs) was specified in the num^fcbs parameter but the fcb^array parameter was not specified.
Page 232 Recovery Either correct the problem that caused the primary process to terminate, make sure the primary process does stack checkpointing, or set bit 12 of the flags parameter to 1. Error message: "INITIALIZER: Unable to open $RECEIVE" Cause $RECEIVE is probably already open. Effect INITIALIZER prepares the error message calls ABEND.
Page 233: Interprocess Command Interpreter Messages
19 Interprocess Command Interpreter Messages Application processes use Tandem Advanced Command Language (TACL) to send or receive the messages described in this section. The TACL product is the command interpreter supplied by HP for use on the operating system. Though user-written command interpreters can be used, in this section the TACL product is assumed to be the only command interpreter.
Page 234: Message Descriptions
Table 12 Command Interpreter Messages (continued) CI Message Source -50 Logon Sent to $CMON by TACL process -51 Logoff Sent to $CMON by TACL process -52 Run Sent to $CMON by TACL process -53 Illegal Logon Sent to $CMON by TACL process -54 Add User Sent to $CMON in adduser^msg -55 Delete User...
Page 235 INT dname [0:3]; END; STRING param [0:n-1]; ! [33] parameter string of the RUN ! command (if any) that was ! entered by the operator. ! This is in either of the ! following forms: ! parameter-string null [null] ! or ! null null ! n = ( count-read - 66 ) END;...
Page 236 INT accessspec ![51] %0000 if I/O } of ! %2000 if INPUT } OPEN ! %4000 if OUTPUT } INT recordsize; ! [52] record-size INT blocksize; ! [53] block-size END; The application need not respond to the ASSIGN message. When all of the ASSIGN and PARAM messages have been received, the process is ready for use.
Page 237 The TACL process can store 8 undisplayed, 132-byte messages. If 8 messages are stored, subsequent messages are rejected with an error 12 indication (file in use). If the TACL process receives a user message followed by a zero-length message, the TACL process clears its $RECEIVE buffer and checks the message length.
Page 238 ! command file INT cioutfile [0:11]; ! [15] name of the TACL ! list file END; The $CMON reply contains an optional display message. If the $CMON process is not running, the TACL process does not try to write the logoff message. The format of the reply to the logoff message is: STRUCT logoff^reply;...
Page 239 STRING param [0:527] ! [90] parameter string of the RUN ! command, which is up to 528 ! bytes in length including 2 null ! bytes at the end of the string. ! This is defined for D42 and ! later releases of the ! operating system.
Page 240 The length of the message is 2 bytes plus the replytext length in bytes. The length of the replytext is implied in the reply count used when making a reply. If reply-count=2, no text is displayed. ILLEGAL LOGON Cause A user tried to log on three times in a row and failed each time. Format The format of the illegal logon message follows.
Page 241 INT user^id; ! [36] the user number of the ! user being added END; The $CMON reply indicates whether the user can be added and contains an optional display message. The format of the reply message is: STRUCT adduser^reply; BEGIN INT replycode;...
Page 242 change the priority of any process. However, if the $CMON process is not running, then no $CMON alter-priority restrictions are in effect. Format The format of the alter-priority message is: STRUCT altpri^msg; BEGIN INT msgcode; ! [0] -56 INT userid; ! [1] user ID of user altering ! the priority INT cipri;...
Page 243 INT replycode; ! [0] 0 = allow password to be ! changed ! 1 = disallow password to ! be changed STRING replytext [0:n]; ! [1] optional message to be ! printed; maximum length of ! 132 bytes END; The length of the message is 2 bytes plus the reply-text length in bytes. The length of the reply text is implied in the reply count used when making a reply.
Page 244 ! 0 if the user is logged off ! or is logged on as ! NULL.NULL (0,0) INT cipri; ! [2] current priority of TACL INT ciinfile [0:11]; ! [3] TACL IN file INT cioutfile [0:11]; ! [15] TACL OUT file INT loggedon;...
Page 245 ! follow (currently12); INT autologoffdelay; ! [2] see #GETCONFIGURATION INT logoffscreenclear; ! [3] description in the INT remotesuperid; ! [4] TACL Reference INT blindlogon; ! [5] Manual for more INT namelogon; ! [6] information on these INT cmontimeout; ! [7] parameters. INT cmonrequired;...
Page 246: System Messages
20 System Messages A system message is an interprocess message that is sent from the operating system to an application process. System messages are received by an application process through its $RECEIVE file. There are two procedures you can use to open $RECEIVE: FILE_OPEN_ and OPEN. The OPEN procedure, which is superseded by the FILE_OPEN_ procedure, is supported for compatibility with previous software and should not be used for new development.
Page 247 Table 13 D-Series-Format System Messages (continued) Elapsed Time Timeout Memory Lock Completion Memory Lock Failure Process Time Timeout Process CONTROL Process SETMODE Process RESETSYNC Process CONTROLBUF Process SETPARAM Queued Message Cancellation Nowait DEVICEINFO2 Completion - 1 00 Remote Processor Down - 1 01 Process Deletion: ABEND, STOP, or Processor Down - 1 02...
Page 248 Table 14 C-Series and D-Series System Messages Compared (continued) Process Deletion: STOP Process Deletion: STOP Process Deletion: ABEND - 1 01 Process Deletion: ABEND Change in Status of Network Node - 1 00 Remote Processor Down - 1 10 Remote Processor Down Loss of Communication With Network Node Establishment of Communication With - 1 1 1...
Page 249: Message Descriptions
Message Descriptions This subsection lists the system messages and provides a description of each message. PROCESSOR DOWN Cause The operating system did not receive an "I'm alive" message from the specified processor which was being monitored with the MONITORCPUS procedure. Compare the named process deletion form of message -2, which is listed separately.
Page 250 = The completion code sysmsg[12] = Termination information, 0 if the user did not supply information sysmsg[13] FOR 4 = Subsystem organization (8 bytes); for HP products, this is HP sysmsg[17] = Subsystem number sysmsg[18] = Subsystem version sysmsg[19]...
Page 251 HP products, this is HP sysmsg[17] = The subsystem number sysmsg[18] = The subsystem version sysmsg[19] = The length of text in bytes sysmsg[20] FOR n = Up to 80 bytes of text If the operating system deletes the process name from the process-pair directory, it sends the following message.
Page 252 Response The response, if any, is application dependent. JOB PROCESS CREATION Cause (C-series-format system message only) The receiving process is the supervisor of a job and a process running under the supervisor's GMOM job ID created a third process. Format The layout of the received message described in terms of an array of words is: sysmsg[0]=-9 sysmsg[1] FOR 4=Job ID sysmsg[5]=Process ID of the newly created process Response The response, if any, is application dependent.
Page 253 sysmsg[9] = NEWPROCESS suberror or file-system error For more information on the NEWPROCESS error, refer to “NEWPROCESS AND NEWPROCESSNOWAIT Errors” (page 141) TPSEC05.fm NEWPROCESS AND NEWPROCESSNOWAIT Errors. NOTE: If 1 19 is returned in sysmsg[1].<8:15>, the file-system error number is greater than 255. The actual error is in sysmsg[9].
Page 254 Response The response, if any, is application dependent. ELAPSED TIME TIMEOUT Cause A timer set by a call to SIGNALTIMEOUT timed out. Format The layout of the received message described in terms of an array of words is: sysmsg[0] = -22 sysmsg[1] = parameter1 supplied to SIGNALTIMEOUT (0 if none)
Page 255 Cause (C-series-format system message only) Either the process was opened by another process or the backup process of a process pair opened a process (a process receives two process open messages when opened by a process pair). Format The operating system sends the process the following message, provided the process has opened its $RECEIVE file to receive file management system messages either by setting the FILE_OPEN_ procedure parameter options.<15>...
Page 256 Response Obtain the process ID of the caller to CONTROL by a call to LASTRECEIVE or RECEIVEINFO. The response, if any, is application dependent. PROCESS SETMODE Cause Another process referred to the receiving process in a call to the SETMODE or SETMODENOWAIT procedure.
Page 257 Cause Another process called the CONTROLBUF procedure while referring to the receiver process file. Format The operating system sends the process the following message, provided the process has opened its $RECEIVE file to receive file management system messages either by setting the FILE_OPEN_ procedure parameter options.<15>to 0 or the OPEN procedure parameter flags.<1>to sysmsg[0] = -35...
Page 258 and the close message is sent. The receiving process cannot assume that the cancellation message appears on $RECEIVE before the close message (or vice versa). The absence of a cancellation message does not mean that the sending process received a reply. A cancellation can occur at any time, including just before a reply or while the reply data is awaiting delivery;...
Page 259 = Termination information (0 if none supplied) The next three items contain the SPI subsystem ID: sysmsg[18] FOR 4 = Subsystem organization: "HP" for HP supplied subsystems; blank if not supplied sysmsg[22] = Subsystem number: zero if not supplied...
Page 260 \node.$name:seqno Table 15 shows HP completion codes; we recommend that you use positive completion codes in the same way. You can specify a completion code with any positive value in a PROCESS_STOP_, STOP, or ABEND procedure call. Negative completion codes are reserved for HP use.
Page 261 Table 15 Completion Codes (continued) Completion Code Definition Process calls PROCESS_STOP_ (with abnormal termination specified) or ABEND on itself. This code is the default completion code for the PROCESS_STOP_ procedure (when abnormal termination is specified) and the ABEND procedure. PROCESS_STOP_, STOP, or ABEND was called to delete a process by an external, but authorized, process.
Page 262 Table 15 Completion Codes (continued) Completion Code Definition subsystem ID in sysmsg[18]contains the null value. The termination text in sysmsg[41] can contain additional information. Response The response, if any, is application dependent. -102 NOWAIT PROCESS_LAUNCH_ OR PROCESS_CREATE_ COMPLETION CauseA nowait call to the PROCESS_LAUNCH_ OR PROCESS_CREATE_ procedure finished. Format The layout of the received message described in terms of an array of words is: sysmsg[0] = -102...
Page 263 FILE_OPEN_ parameter) sysmsg[3] = Nowait depth (from the nowait FILE_OPEN_ parameter) sysmsg[4] = Sync depth (from the sync-or-receive-depth FILE_OPEN_ parameter) sysmsg[5] = Open options (from the options FILE_OPEN_ parameter) sysmsg[6] = User ID of opener (process access ID) sysmsg[7] = Miscellaneous: .<0:12>...
Page 264 Format The operating system sends the process the following message, provided the process has opened its $RECEIVE file to receive file management system messages either by setting the FILE_OPEN_ procedure parameter options.<15>to 0 or the OPEN procedure parameter flags.<1>to sysmsg[0] = -104 sysmsg[1] = tapedisposition parameter to FILE_CLOSE_ Response If the application is tracking openers, the receiver should call FILE_GETRECEIVEINFO_ to obtain the sender's process handle, which can then be used to search the application's tables...
Page 265 Cause The receiving process (which must have requested these messages by an explicit call to PROCESS_SETINFO_) is being queried for subordinate names by another process calling FILENAME_FINDNEXT[64]_. Format The layout of the received message described in terms of an array of words is: sysmsg[0] = -107 sysmsg[1]...
Page 266 sysmsg[4] FOR 5 = The type information (device type, and so on) having the same layout as described for the typeinfo parameter of FILE_GETINFOBYNAME_ sysmsg[9] = The physical record length value sysmsg[10] = The flag value from the flags parameter to FILE_GETINFOBYNAME_ .<0:14>...
Page 267 sysmsg[11] = Reserved, subject to change sysmsg[14] FOR * = The returned name, in external form with a length given in sysmsg[8] Response The process can use the information returned (if sysmsg[2]indicates no error occurred). -110 LOSS OF COMMUNICATION WITH NETWORK NODE Cause The remote node has either gone down or become partitioned from this node, and the process had called MONITORNET to enable reception of remote status change messages.
Page 268 Response The response, if any, is application-dependent. -121 PATHSEND DIALOG ABORT Cause A Pathsend dialog has been aborted for one of the following reasons: The requester aborted the dialog explicitly by calling the SERVERCLASS_DIALOG_ABORT_ procedure. The requester process abended. The requester canceled the last server-class send operation in the dialog. Format The operating system sends the server process the following message, provided the server has opened its $RECEIVE file to receive file-management system messages either by setting the FILE_OPEN_ procedure parameter options.<15>...
Page 269 Format The layout of the received message described in terms of an array of words is: sysmsg[0] = -147 sysmsg[1] = Message version (must be equal to ZSYS-VAL-SMSG-CONFIGINFO-VERS) sysmsg[2] FOR 4 = Device name for which configuration info is needed; blank-filled (can be all blanks) sysmsg[6] FOR 4 = Subdevice name;...
Page 270 NOTE: When evaluating the size of the data structure that contains everything preceding the device-specific information (as declar Guardian Application Conversion Guideed in ZSYS* files), TAL and pTAL give a different result from C. For example, if this data is declared as a structure called data, the correct length in TAL and pTAL would be $len(data)- 1 ;...
Page 271: Traps And Signals
21 Traps and Signals Certain critical problems can cause a process to be unable to continue executing. These are typically the result of coding errors, but other conditions, such as the lack of a system resource (for example, memory), can also prevent normal process execution. Such conditions are reported as traps to TNS processes and as signals to TNS/R native processes.A trap is a software mechanism that stops process execution.A signal is a software interrupt that can notify a process of other events, such as timer expiration, as well as of critical error conditions.
Page 272: Signal Handling
Signal Handling When a process receives a TNS/R native signal, the default action is for the process to abend. Alternatively, the program can call the SIGACTION_INIT_ procedure to specify that another action should result, such as the execution of a signal handler. If a signal handler has been specified, it is executed when the process receives a signal.
Page 273 Effect For trap 1, process control passes to the Debug or Inspect debugger or to the trap handler designated by a call to the ARMTRAP procedure, or else the process is abended. See “Trap Handling” (page 271) for further information. For the signal SIGILL, the default or specified signal handling occurs.
Page 274 Cause The cause of the stack overflow varies with the type of process. In TNS or accelerated mode, a stack overflow results when one of the following problems occurs: ◦ The value in the TNS stack register, S, exceeds 32767. Typically, an attempt was made to execute a procedure or subprocedure whose stack marker, sublocal data area, or local data area extends into the upper 32K of the user data segment.
Page 275 Effect For trap 4, process control passes to the Debug or Inspect debugger or to the trap handler designated by a call to the ARMTRAP procedure, or else the process is abended. See “Trap Handling” (page 271) for further information. For the signal SIGTIMEOUT, the default or specified signal handling occurs.
Page 276: Error Lists
If you are using the Subsystem Programmatic Interface (SPI) to send commands to a subsystem, you might receive a trap-out error list in a response. HP subsystems return such an error list when, in performing your request, they encounter either a trap condition or an exception condition that causes a signal to be generated.
Page 277: 5: Zgrd-Val-Trapout
5: ZGRD-VAL-TRAPOUT A user-enabled trap or signal handler started execution following the detection of a trap or exception condition while a process was executing. Unconditional Tokens ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZSPI-TKN-PROC-ERR token-type ZSPI-TYP-ENUM. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. Conditional Tokens ZGRD-TKN-XOBJECTFILE token-type ZSPI-TYP-STRING.
Page 278: Effect
Effect The process might not be able to continue executing. Recovery Take corrective action as indicated by the returned trap or signal number. Traps and signals are described earlier in this section. 278 Traps and Signals...
Page 279: Oss Error Information
22 OSS Error Information This section describes how to find more information on Open System Services (OSS) errors. Brief OSS Error Information Guardian procedures that make use of OSS functions can return OSS errno values in addition to Guardian file-system error codes. You can obtain a short explanation of any OSS errno value or Guardian file-system error code at the TACL prompt by entering: ERROR number...
Page 280: Index
Index ZFIL-VAL-CHECKOPEN, ZFIL-VAL-CHECKPOINT, ALLOCATESEGMENT procedure ZFIL-VAL-CHECKPOINTMANY, error codes, ZFIL-VAL-CHECKPOINTMANYX, error list, ZFIL-VAL-CHECKPOINTX, 1 10 guidelines for using, ZFIL-VAL-CHECKSWITCH, ZFIL-VAL-CLOSE, ZFIL-VAL-CONTROL, C language error numbers for file-system errors, ZFIL-VAL-CREATE, C-series procedure errors, ZFIL-VAL-DEVICEINFO2, Command interpreter messages, 16, 234, ZFIL-VAL-DISK-REFRESH, description of, ZFIL-VAL-FILE-CLOSE, Completion codes, ZFIL-VAL-FILE-CREATE,...
Page 281 PROCESS_LAUNCH_ procedure, ZFIL-VAL-CHECKPOINT, guidelines for using, ZFIL-VAL-CHECKPOINTMANY, PROCESS_SPAWN_ procedure, ZFIL-VAL-CHECKPOINTMANYX, guidelines for using, ZFIL-VAL-CHECKPOINTX, 1 10 SEGMENT_ALLOCATE_ procedure, ZFIL-VAL-CHECKSWITCH, guidelines for using, ZFIL-VAL-CLOSE, SEGMENT_USE_ procedure, ZFIL-VAL-CONTROL, guidelines for using, ZFIL-VAL-CREATE, signal error list, ZFIL-VAL-DEVICEINFO2, guidelines for using, ZFIL-VAL-DISK-REFRESH, SSGET procedure, ZFIL-VAL-FILE-CLOSE, SSGETTKN procedure, ZFIL-VAL-FILE-CREATE,...
Page 282 Interprocess command interpreter messages, 16, 234, PROCESS_SPAWN_ error codes, 157, description of, error list, Interprocess messages, general description of, Guardian error codes, 157, IOEdit procedures OSS error codes, 192, catastrophic error messages, 226, SEGMENT_ALLOCATE_ file-system error codes used by, 222, error codes, unique error codes used by, 224, error list,...
Page 283 SIGNOMEM, CONTROL, SIGSEGV, CREATE, SIGSTK, DEVICEINFO2, SIGTIMEOUT, DISK-REFRESH, SIGNOMEM signal, FILE-CLOSE, SIGSEGV signal, FILE-CREATE, SIGSTK signal, FILE-CREATELIST, SIGTIMEOUT signal, FILE-GETINFOBYNAME, SSGET procedure error list, FILE-GETOPENINFO, SSGETTKN procedure error list, FILE-GETRECEIVEINFO, SSINIT procedure error list, FILE-OPEN, SSMOVE procedure error list, FILE-OPEN-CHKPT, SSMOVETKN procedure error list, FILE-PURGE, SSNULL procedure error list,...

This manual is also suitable for:

Guardian

HP Guardian Errors Manual

What's New in this Manual

About this Manual

Introduction

File-System Errors

Sequential I/O Errors

DEFINE Errors

NEWPROCESS and NEWPROCESSNOWAIT Errors

Process Creation Errors

PROCESS_GETINFOLIST_ Errors

PROCESS_GETPAIRINFO_ Errors

PROCESS_SPAWN_ Open System Services (OSS) Errors

ALLOCATESEGMENT Errors

1 SEGMENT_ALLOCATE_ and SEGMENT_ALLOCATE64_ Errors

USESEGMENT Errors

Segment_Use_Errors

Subsystem Programmatic Interface (SPI) Errors

EDITREAD and EDITREADINIT Errors

Ioedit Errors

Formatter Errors

INITIALIZER Errors

Interprocess Command Interpreter Messages

System Messages

Traps and Signals

OSS Error Information

Index

Quick Links

Related Manuals for HP Guardian Errors

Summary of Contents for HP Guardian Errors

This manual is also suitable for:

Table of Contents