Guardian Procedure Errors and Messages 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.
© Copyright 2014 Hewlett-Packard Company. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents What’s New in This Manual...........................................................................8 Manual Information..................................................................................................................8 New and Changed Information..................................................................................................8 About This Manual......................................................................................10 Purpose of This Manual...........
17: ZFIL-VAL-READUPDATELOCK.........................................................................................102 18: ZFIL-VAL-REPLY............................................................................................................103 19: ZFIL-VAL-SETMODE.....................................................................................................104 20: ZFIL-VAL-SETMODENOWAIT.......................................................................................105 21: ZFIL-VAL-WRITE..
Effect.........................................................................................................................157 Recovery....................................................................................................................157 6 Process Creation Errors...........................................................................158 Error Codes.........................................................................................................................158 Error Lists.
13 SEGMENT_USE_Errors..........................................................................211 Error Lists.............................................................................................................................211 23: ZGRD-VAL-SEGMENT-USE...........................................................................................211 Unconditional Tokens...................................................................................................211 Conditional Tokens.............
21 Traps and Signals.................................................................................273 Trap Handling......................................................................................................................273 Signal Handling...................................................................................................................274 Signals and Trap Numbers....................................................................................................
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. Product Version N/A Supported Release Version Updates (RVUs) This publication supports J06.
Changes to the H06.26/J06.15 manual: • Added a new error 757 (page 78). Changes to the H06.24/J06.13 manual: • Modified system message 102 (page 264). • Modified system message 109 (page 268). • Added system message 654 (page 72). • Added system message 149 (page 272). Changes to the H06.22/J06.11 manual: • Added error detail 19 for error 77 (page 178). • Updated the format of remote password (page 246). • Added error code description for error 1092 (page 81). Changes to the H06.21/J06.
About This Manual Purpose of This Manual This manual describes the Guardian messages for HP systems that use the HP NonStop operating system.
• “SEGMENT_ALLOCATE_ and SEGMENT_ALLOCATE64_ Errors” (page 204), describes the error codes and error lists produced by the SEGMENT_ALLOCATE_ procedure. • “USESEGMENT Errors” (page 209), describes the error list associated with the USESEGMENT procedure. • “SEGMENT_USE_Errors” (page 211), describes the error list associated with the SEGMENT_USE_ procedure.
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. For example: myfile.c italic computer type.
$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 ]...
of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE). The CRE has many new message types and some new message type codes for old message types. 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.
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.
Procedure Errors Procedure errors are values returned to your program after your program calls procedures such as file-system procedures. Your application program must test for possible errors and take appropriate action when necessary. Your program detects procedure errors in two ways, depending on the procedure being called. Errors returned by D-series procedures are not in the same format as those returned by C-series procedures.
errors relating to operations involving open files; the last error associated with the file number is returned. A typical method of testing for an error and calling FILEINFO to get the error value might appear as follows: IF <> THEN ! If CCL or CCG occurred, then CALL FILEINFO ! call this procedure to get the error value. Interprocess Messages Interprocess messages are data structures that are exchanged between processes or between the operating system and a process.
The value of the return token, ZSPI-TKN-RETCODE, indicates the content of the error list: • If zero and no error list follows, no error occurred. • If zero but one or more error lists follow, the error lists contain only warning messages: unusual conditions that might be of interest to the requester but do not prevent the server from completing the command. • If nonzero, the error list must contain at least one token with an error number that matches the value of the return token.
2 File-System Errors Error Codes The file system of the NonStop operating system returns a code to the calling procedure to indicate errors and other special conditions. 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. For example: WARNING - $VOLUME.SUBVOL.
On D-series releases, file-system error information is also available using one of the procedures described in Table 3. 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). FILE_GETINFOBYNAME_ To obtain information about a file using the file name (file-name).
Table 4 Guardian File-System Errors Mapped to C Errors (continued) File-System Error C errno Symbolic Name 43-44 ENOSPC 45 EFBIG 46 EIO 48 EACCES 49 EINVAL 50-51 EIO 53 EFSERR 54 EINVAL 55 EIO 59 EFILEBAD 60 EWRONGID 61 EIO 73 EGUARDIANLOCKED 103 EIO 232 EIO 549, 560, 564, 590 EINVAL Error Code Descriptions 0 (%0) The operation completed successfully. Cause The file-system procedure successfully completed the requested operation.
• 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. • The address of a parameter is extended, but is an absolute address. • The file system cannot use the user's segment when needed.
Cause The process received a system message from the operating system. Effect Data is returned in the application process buffer. Recovery Informative message only. The process receiving the system message must read it (from $RECEIVE) to determine what action is needed. 7 (%7) This process cannot accept a CONTROL, CONTROLBUF, SETMODE, or RESETSYNC because $RECEIVE is not opened correctly.
Effect The procedure sets the error code and returns without performing the requested operation. Recovery Corrective action is application dependent; for record not in file, it depends on the positioning mode. 12 (%14) The file is in use. (device type: any) Cause The specified file was in use, with exclusive or protected access, by another process.
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. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Corrective action is application dependent.
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. • A FILE_CREATE_ or CREATE procedure call for a disk file requested a size larger than the system limit. • A file access specifies an inconsistent key length or compare length.
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. 25 (%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.
Recovery Corrective action is application dependent. 29 (%35) A required parameter is missing in a procedure call, or two mutually exclusive parameters were supplied. (device type: any) Cause A file-system procedure call was missing a required parameter or supplied two mutually exclusive parameters. The string:maxlen and actual-length parameters must both be present if either one is present. If one of these two parameters is present but the other is missing, this error is returned.
If the problem persists, contact your HP representative. Configuration information for the current system image must be saved for your HP representative. 33 (%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. Effect The procedure sets the error code and returns without performing the requested operation.
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; run MEASURE to help determine which processes are locking memory. 37 (%45) I/O process is unable to lock physical memory.
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. 41 (%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. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Correct the coding error.
For a PROCESS_CREATE_, NEWPROCESS, or NEWPROCESSNOWAIT call, use another process name. 46 (%56) An invalid key was specified; key length passed to a file creation API exceeds its maximum allowable length; 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 a file creation API exceeds its maximum allowable length.
• 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. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Corrective action is application dependent. 50 (%62) Directory error on a disk volume.
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. 55 (%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. The file associated with the error is no longer accessible. Effect The procedure sets the error code and returns without performing the requested operation.
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. Recovery Wait until the utility operation finished before attempting to open the file. If the file is not currently open, then the utility abended before finishing; purge the file or table.
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. 63 (%77) The volume was mounted and the mount is in progress, so a file open is not permitted. (device type: 3) Cause The specified disk volume was physically mounted and the mount command has been given, but the mount has not finished.
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. Recovery If there is a DP2-DP1 consistency problem, correct the problem.
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. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Corrective action is application dependent.
Recovery For more information, see the NonStop TM/MP Operations and Recovery Guide. 81 (%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. Error 81 is received by ENDTRANSACTION or REPLY. Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Ensure that devices are enabled for the TMF subsystem. For example, use the command ENABLE VOLUMES through TMFCOM. 86 (%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.
Recovery For more information, see the NonStop TM/MP Application Programmer's Guide. 91 (%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. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Contact your service provider.
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. Effect The procedure sets the error code and returns without performing the requested operation.
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. For more information, see the DSM/Tape Catalog User's Guide. 100 (%144) Device is not ready or the controller is not operational.
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. 105 (%151) Invalid printer VFU buffer. (device type: 5.4) Cause The printer direct-access vertical-format unit buffer was invalid. This error can occur for the following reasons: • More than one stop was defined for channel 0 (top of form).
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 110 until normal access is permitted. If this process enabled break, check $RECEIVE for the system break message and take appropriate action.
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. For more information, see the DSM/Tape Catalog User's Guide. 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.
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.
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. 130 (%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. Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Reset the write-protect switch to allow writes. 136 (%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. Effect The disk process automatically retries. Recovery If the automatic retry is not successful, retry the operation yourself.
• 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 For additional information, see the appropriate subsystem manual. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Corrective action is device dependent.
Recovery Take corrective action appropriate to the device. If this error occurs with several tapes, contact your service provider regarding a possible hardware problem. 153 (%231) Tape drive power restored. (device type: 4) Cause The tape-drive power failed and was restored. Effect The tape unit automatically returns to the ready state and to the beginning of the tape. Recovery If two units are set to the same unit number when the power is restored, the wrong unit can be placed online.
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. 158 (%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. Recovery Contact your system operator or supply the correct function code.
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. 163 (%243) EOT received (device type: 7.0, 7.1, 7.2, 7.3, or 7.8) or power at autocall unit is off (device type: 7.56 or 11).
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. 168 (%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).
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.
Recovery Corrective action usually involves increasing the read count. For more information, see the manual for the specific device. If this problem persists and a data communications process is involved, obtain a trace and submit it to your service provider. 178 (%262) No address list specified. (device type: 7.2, 7.3, 7.8, 7.9, 11.40, or 61) Cause An address list was required for this operation, but none was specified.
Recovery Corrective action is application dependent. 183 (%267) SNA session has ended. (device type: 14.2) Cause The file-system procedure call issued by the primary or secondary logical unit was not performed because the logical-unit-to-logical-unit session associated with the specified device (filenum) no longer exists. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Close, then reopen the process.
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. 192 (%300) Device in diagnose mode; system operator running diagnostics. (device type: 3, 4, 5, or 6) Cause The system operator was running diagnostic programs on the specified device.
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. Correct the label accordingly. For additional information, see the appropriate system operator's guide. 197 (%305) An SQL error has occurred.
• 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 replied. • 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.
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. 215 (%327) I/O attempted to absent memory page (hardware path error). (device type: any except 2) Cause A hardware failure occurred (path error). Effect The file operation stopped at some indeterminate point. Recovery Corrective action is device dependent and application dependent.
Cause An I/O controller tried to write to memory when it did not have permission. Effect The file operation stopped at some indeterminate point. Recovery Corrective action is device dependent and application dependent. 221 (%335) Controller handshake violation (path error). (device type: any except 2) 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.
Recovery Corrective action is device dependent and application dependent. 231 (%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. Recovery Corrective action is device dependent and application dependent.
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. • The Expand process received a request from a system for which it is not the current path. • An Expand process received a request to forward a message, but all its lines are down.
• The line normally exhibits error 248 on the operator console when the line is initially brought up. The message must 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. The FCS error count indicates that garbled data was received.
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. 252 (%374) Required EXPAND class is not available.
Recovery If a block mode application needs to use the device, direct the console to another terminal. The operator process stops using the device and allows it to be used in block mode. 550 (%1046) File operation attempted at illegal position. Cause The current setting of the file's positioning information is not valid for the attempted operation.
Cause The size of an output buffer was too small to hold the data. Error 563 is an operating system error and must not be confused with error 177, which is a data communications error. Effect The operation failed. Recovery Increase the size of the buffer. 564 (%1064) The operation is not supported for this file type. Cause The operation specified is not permitted on this file type. Effect The operation failed. Error 564 is returned rather than error 2 when an unqualified failure occurs.
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 and other file types, the largest allowed value is 4096 bytes. However, for format 2 key-sequenced files, the largest allowed value is 32,768 bytes. 579 (%1103) The record size specified is too large for the given block size, file type and format.
this error will be returned if the alternate key information is requested using the FILEINQUIRE procedure because the format from this procedure allows only 12 bits for an offset. Effect The requested operation is not performed. Recovery Update the application to use an interface supporting the full range of alternate key information, for instance by using FILE_GETINFOLIST_ item 106 583 (%1107) The extent size specified is too large or the maxextents limit is too large.
Cause DSM/TC returned a fatal error to $ZSVR. Effect The tape request failed. Recovery For details about the DSM/TC error, see the EMS log. For recovery actions, see the DSM/Tape Catalog Messages Manual. 595 (%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. Recovery For details about the ZSSI error, see the EMS log. For recovery actions, see the DSM/Tape Catalog Messages Manual.
Recovery Retry the locking operation after seeing that both optical disk drives are up and both volumes are unlocked, or retry the access operation after unlocking the volume on the other side of the cartridge. 638 (%1176) Process cannot be stopped until process returns to stopmode 1. Cause A stop request passes the security checks but the process is running at stopmode 2. Effect The stop request is queued until the process to be stopped reduces its stopmode.
Cause Volume is in the DOWN state. Effect The operation fails. TMF generates an EMS event that provides information regarding the error. Recovery The system administrator must change the volume to the UP state. 702 (%1276) FEUNSUPPORTEDOP - The disk process received an erroneous message from a recovery process. The message requested a physical 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.
Recovery Contact your HP service provider. 707 (%1281) FEINVALIDDPNAMETIMESTAMP - Generated by the disk process when the Disk Process Name Stamp(DPNameTimeStamp)in the message sent by a recovery process does not match the current DPNameTimeStamp of the disk. 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.
Cause An attempt was made to register a recoverable resource manager using the TMF_REC_RM_CREATE_ procedure, but the name was already registered. Effect No change is made to the resource manager directory. Recovery Change the name to be registered and try again if needed. 713 (%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.
Recovery Determine if the transaction must be suspended and why it is not and repair the application as appropriate. 718 (%1316) FEINVALIDSIGNAL 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.
Another possible recovery is to add more resource managers to the directory and distribute the load of transaction branches across them. 724 (%1324) FENOTNOWAITTFILE Cause An attempt is made to export a transaction branch with the TFILE not opened in a nowaited manner. Effect The Export fails. Recovery Open the TFILE in nowaited manner and then export the transaction branch. 725 (%1325) FEIMPORTINVALOP Cause An attempt is made to call ENDTRANSACTION on an imported transaction branch.
Recovery Call TMF_SUSPEND_ for each outstanding join before calling ENDTRANSACTION. 731 (%1333) FEALREADYJOINED Cause Transaction has already been joined by this process. Effect The operation fails. Recovery A process can only have one join outstanding at any time. 732 (%1334) FEALREADYRESUMED Cause Transaction has already been resumed by this process. Effect The operation fails. Recovery A process can only have one join outstanding at any time.
Recovery Commit the read-only transaction before attempting to start a read-write transaction. You must also check your auto commit settings. 758 (%1366) Unable to allocate space from the control block pool or trying to open too many files or partitions on a volume. (device type: 3) 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.
Cause No space is available in the local pool to allocate a new buffer. Effect The procedure sets the error code and returns without performing the requested operation. Recovery This is a Data Access Manager internal error. Contact your service provider. 764 (%1374) Unable to allocate space from the revive pool. (device type: 3) 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.
Cause • A process attempted to create a file with attributes that exceed the maximum size of a file label. • A process called a non-file creation API with a filename, such as FILE_OPEN_, and the disk process does not recognize the contents of that file’s file label. Typical causes for file creation APIs are: • Files with up to 16 partitions: too many alternate key files, alternate keys, extents, or secondary partitions specified, or secondary partitions with long partition partial keys specified.
Cause An attempt was made to refer to a file that has either a reserved name or cannot be used in the current context. For example, this error is returned when a Guardian internal name for an OSS file is given as the program file in the PROCESS_CREATE_ procedure. Effect The operation failed. Recovery Correct the error in the call and try again.
Recovery Use PUP or SMFIXUP to operate on SMF catalog files. 5010 (%11622) An error occurred during SMF lock manager processing. (device type: 3.36, 25.0, or 52.0) Cause The NonStop Storage Management Foundation (SMF) internal lock manager encountered an error (for example, a lock was not obtained because of a problem with a particular file). Effect The requested operation is not performed. Recovery Appropriate recovery varies according to the specific cause of the error.
Recovery If you specified a physical volume, retry the request either without specifying a physical volume or specifying a different physical volume. If you did not specify a physical volume, start the pool process (if it's not running), wait, and retry the request. 5014 (%11626) No physical volumes are available. (device type: 3.
Recovery See the event log for additional information and take action as appropriate. Retry the request. If the problem persists, contact your service provider. 5028 (%11644) Unable to read a received message. (device type: 3.36, 25.0, or 52.0) Cause A NonStop Storage Management Foundation (SMF) process received an invalid message from any process. Effect The message is ignored and the requested operation is not performed.
Recovery Appropriate recovery varies according to the specific error returned by the BEGINTRANSACTION procedure. See the event log and take action as appropriate. The recovery might be to just retry the request. In some cases, no user action is required. 5049 (%11671) A memory allocation failed. (device type: 3.36, 25.0, or 52.0) Cause The NonStop Storage Management Foundation (SMF) subsystem was unable to allocate memory due to a shortage of resources. Effect The requested operation is not performed.
Recovery See the event log for additional information and take action as appropriate. Bring the SMF process to the DOWN state and then to the UP state. Retry the request. If the problem persists, contact your service provider. 5072 (%11720) Recovery processing was unable to initialize PENDOPS processing. (device type: 3.36, 25.0, or 52.
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. The contents of the error list depend on which procedure was called.
Table 5 Conditional Tokens That Can Appear in Any File-System Error List (continued) Token Name Token Type Description ZFIL-TKN-ERRORPARTITION ZSPI-TYP-INT is the partition in error. ZFIL-TKN-EXTENTSIZE ZSPI-TYP-INT is the file extent size. ZFIL-TKN-FILE- OPEN-ACCESS ZFIL-TYP-INT is the file-open-access mode. ZFIL-TKN-FILEOPEN-EXCLUSION ZFIL-TYP-INT is the file-open-exclusion mode. ZFIL-TKN-FILEOPEN-NOWAIT ZFIL-TYP-INT is the file-open-nowait depth.
1 ZFIL-VAL-AWAITIO A call to the file-system procedure AWAITIO resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZSPI-TKN-ENDLIST Conditional Tokens ZFIL-TKN-BUFFERADDR ZFIL-TKN-COUNTTRANSFERRED ZFIL-TKN-FILENAME ZFIL-TKN-TAG ZFIL-TKN-TIMEOUT token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-SSCTL.
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 zero because CHECKCLOSE does not return an error code. ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-CHECKCLOSE (2).
Value Meaning 2 Primary's processor failed 3 Primary called CHECKSWITCH Conditional Tokens ZFIL-TKN-OLDPRIMARY is the old primary process ID. Effect Normal processing continues in the new primary. Recovery Informative message only; no corrective action is needed. 4: ZFIL-VAL-CHECKOPEN A call to the procedure CHECKOPEN returned a nonzero file-system error code.
5: ZFIL-VAL-CHECKPOINT A call to the procedure CHECKPOINT returned a nonzero file-system error code. Either an error was detected, or a backup takeover occurred. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-CHECKPOINTSTATUS ZSPI-TKN-ENDLIST Conditional Tokens ZFIL-TKN-STACKBASE ZFIL-TKN-SREGISTER ZFIL-MAP-CHECKPOINTCELL token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
Recovery Check ZFIL-TKN-CHECKPOINTSTATUS for information about CHECKPOINT. If the backup process took over, this is an informative message only; no corrective action is necessary. 6: ZFIL-VAL-CHECKPOINTMANY A call to the procedure CHECKPOINTMANY returned a nonzero file-system error code. Either an error was detected or a backup takeover occurred.
Conditional Tokens ZFIL-TKN-STACKBASE is the checkpoint base-of-stack. ZFIL-TKN-SREGISTER is the current S register. ZFIL-MAP-CHECKPOINTLIST is the CHECKPOINT list passed to CHECKPOINTMANY. ZFIL-TKN-OLDPRIMARY is the old primary process ID. Effect The operation fails. If the backup process took over, the system continues normally. Recovery If an error occurred, check ZFIL-VAL-CHECKPOINTSTATUS for information about CHECKPOINTMANY.
Value Meaning <8:15>=2 primary's processor failed <8:15>=3 primary called CHECKSWITCH Conditional Tokens ZFIL-TKN-OLDPRIMARY is the old primary process ID. Effect If an error occurred, the operation fails. If the backup process took over, the system continues normally. Recovery Check ZFIL-VAL-CHECKPOINTSTATUS for information about CHECKSWITCH. If the backup process took over, this is an informative message only; no corrective action is necessary.
Effect The attempted CONTROL operation fails. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 9: ZFIL-VAL-CREATE A call to the procedure CREATE resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-FILENAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type Conditional Tokens ZFIL-TKN-OPENDEFAULTS token-type ZSPI-TYP-UINT. ZSPI-TYP-LIST. ZSPI-TYP-ERROR.
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-KEYPOSITION (10). ZFIL-TKN-XFILENAME is the completely qualified file name (including node name) in external format.
Conditional Tokens ZFIL-TKN-CONDITION is the condition code returned by OPEN (-1, 0, or 1). ZFIL-TKN-PRIMARYFILE is the primary file number. ZFIL-TKN-PRIMARYPROCESS is the primary process ID of the process for which the backup process reports the error. ZFIL-TKN-BLOCKBUFFERLENGTH is the length of the requested sequential block buffer. Effect The attempted OPEN operation fails. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section.
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-POSITION (13). ZFIL-TKN-XFILENAME is the completely qualified file name (including node name) in external format.
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). Effect The attempted read operation fails. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section.
Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 16: ZFIL-VAL-READUPDATE A call to the READUPDATE procedure resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-SSCTL.
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 ZFIL-TKN-COUNTTRANSFERRED ZFIL-TKN-FILENAME ZFIL-TKN-TAG ZFIL-TKN-TRANSFERCOUNT token-type token-type token-type token-type token-type ZSPI-TYP-UINT. ZSPI-TYP-INT. ZSPI-TYP-FNAME. ZSPI-TYP-INT2. 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.
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-REPLY (18). ZFIL-TKN-FILENAME is the file name (blank-filled if unknown). Conditional Tokens ZFIL-TKN-BUFFERADDR is the base address of the REPLY buffer.
Conditional Tokens 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-PARAM1 is the first function parameter. ZFIL-TKN-PARAM2 is the second function parameter. ZFIL-TKN-LASTPARAMS contains the previous parameter settings. Effect The attempted SETMODE operation fails.
ZFIL-TKN-TAG is the AWAITIO tag value. Effect The attempted SETMODENOWAIT operation fails. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 21: ZFIL-VAL-WRITE A call to the WRITE procedure resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM.
22: ZFIL-VAL-WRITEREAD A call to the WRITEREAD procedure resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-SSCTL.
Conditional Tokens ZFIL-TKN-BUFFERADDR ZFIL-TKN-COUNTTRANSFERRED ZFIL-TKN-FILENAME ZFIL-TKN-TAG ZFIL-TKN-TRANSFERCOUNT token-type token-type token-type token-type token-type ZSPI-TYP-UINT. ZSPI-TYP-INT. ZSPI-TYP-FNAME. ZSPI-TYP-INT2. 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. Z-SSID is the subsystem identifier ZFIL-VAL-SSID. Z-ERROR is the file-system error code returned in the error parameter of FILEINFO.
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-WRITEUPDATEUNLOCK (24). ZFIL-TKN-XFILENAME is the completely qualified file name (including node name) in external format.
Conditional Tokens ZFIL-TKN-BUFFERADDRX is the base address of the I/O buffer. ZFIL-TKN-COUNTTRANSFERRED is the length of the transferred data (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. ZFIL-TKN-TAG is the AWAITIOX tag value. ZFIL-TKN-TIMEOUT is the timeout value. Effect The AWAITIOX operation fails.
Value Meaning <0:7>=2 Takeover from the primary; then <0:7>=3 <8:15>=0 primary stopped <8:15>=1 primary abnormally ended <8:15>=2 primary's processor failed <8:15>=3 primary called CHECKSWITCH Invalid parameter; then <8:15>=1 error in stack-base parameter <8:15>=n, n > 1 error in word[n-2]; For more information, see the Guardian Procedure Calls Reference Manual. Conditional Tokens ZFIL-TKN-STACKBASE is the checkpoint base-of-stack. ZFIL-TKN-SREGISTER is the current S register.
returned in the error parameter of FILEINFO; it is always zero because CHECKPOINTX does not return an error code. ZSPI-TKN-PROC-ERR is the procedure in which the error occurred. Its value is ZFIL-VAL-CHECKPOINTX (27). ZFIL-TKN-CHECKPOINTSTATUS indicates the status of the call to CHECKPOINTX.
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-KEYPOSITIONX (28). ZFIL-TKN-XFILENAME is the completely qualified file name (including node name) in external format.
Conditional Tokens ZFIL-TKN-BUFFERADDRX is the base address of the READLOCKX 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. ZFIL-TKN-TAG is the AWAITIO tag value. ZFIL-TKN-TRANSFERCOUNT is the request length (in bytes).
Effect The attempted READUPDATELOCKX operation fails. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 31: ZFIL-VAL-READUPDATEX A call to the READUPDATEX procedure resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-SSCTL.
32: ZFIL-VAL-READX A call to the READX procedure resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-SSCTL.
ZFIL-TKN-COUNTTRANSFERRED ZFIL-TKN-RECEIVETAG ZFIL-TKN-REPLYCODE token-type ZSPI-TYP-INT. token-type ZSPI-TYP-INT2. 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. 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-REPLYX (33).
Conditional Tokens ZFIL-TKN-BUFFERADDRX is the base address of the WRITEREADX 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. ZFIL-TKN-READCOUNT is the read length (in bytes). ZFIL-TKN-TAG is the AWAITIO tag value.
Effect The attempted WRITEUPDATEUNLOCKX operation fails. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 36: ZFIL-VAL-WRITEUPDATEX A call to the WRITEUPDATEX procedure resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING.
37: ZFIL-VAL-WRITEX A call to the WRITEX procedure resulted in an unexpected error. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-SSCTL.
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-CLOSE (38). ZFIL-TKN-XFILENAME is the completely qualified file name (including node name) in external format.
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 ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZFIL-TKN-STATUS ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. Unconditional Tokens ZSPI-TKN-ERROR is the standard SPI error token, whose value consists of the fields Z-SSID and Z-ERROR.
Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 67: ZFIL-VAL-FILE-OPEN A call to FILE_OPEN_ returned a nonzero error as the function value. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZFIL-TKN-STATUS ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
Effect The operation failed. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 69: ZFIL-VAL-FILE-CLOSE A call to FILE_PURGE_ returned a nonzero error as the function value. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-SSCTL.
Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 71: ZFIL-VAL-FILE-GETRECEIVEINFO A call to FILE_GETRECEIVEINFO_ returned a nonzero error as the function value. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZSPI-TKN-ENDLIST token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL.
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-TKN-ERROR token-type ZSPI-TKN-PROC-ERR token-type ZFIL-TKN-XFILENAME token-type ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING.
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 ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type Conditional Tokens ZFIL-TKN-XFILENAME token-type ZSPI-TYP-STRING. ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING.
Effect The operation failed. Recovery Follow the recovery procedure for the returned file-system error code as described earlier in this section. 77: ZFIL-VAL-FILENAME-FINDNEXT A call to FILENAME_FINDNEXT[64]_ returned a nonzero error as the function value. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-SSCTL.
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 ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZFIL-TKN-XFILENAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-SSCTL.
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. Except for errors 521, 532, and 533, all the error codes in this section indicate fatal coding errors.
Recovery Do not attempt the SIO operations listed above. 516 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. Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Correct the record length. 521 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 For corrective action, see “EDITREAD and EDITREADINIT Errors” (page 222).
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. 527 SIOERR^BLOCKINGREQD: The temporary buffer required for a nowait WRITE^FILE operation was not provided.
Recovery Contact your service provider. 534 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. Effect The procedure sets the error code and returns without performing the requested operation and the process abends. The FCB might be damaged.
Recovery Do not attempt the SIO operation listed above. 539 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. Recovery Use multiple edit files instead of a single edit file to write data or use a structured file, for example, Entry-sequenced.
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. 0 (%000000) Successful completion. Cause The call completed successfully. Effect The operation is successful. Recovery Informative message only; no corrective action is needed.
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. Cause A bounds error occurred in a parameter of the procedure call. Effect The procedure returns the error code and does not perform the requested operation. Recovery This is a coding error; corrective action is application-dependent.
If the consistency check failed for a TAPE DEFINE, the consistency check number returned indicates the cause: Code Meaning 001 Use RETENTION or EXPIRATION, not both. 002 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. 003 VOLUME is required with LABELS ANSI, LABELS IBM, or LABELS IBMBACKUP. 004 The EBCDIC attribute cannot be used with LABELS ANSI.
Code Meaning 117 GEN cannot be specified as a relative generation when USE OUT is used. 118 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. Recovery Correct the inconsistency, then retry the operation. 2059 (%004013) The working set for DEFINEs is invalid. Cause The working set is invalid.
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. 2067 (%004023) An invalid value was supplied for an attribute. Cause An illegal value was supplied for an attribute.
Cause DEFINERESTORE option.<0:13>must be 0 or DEFINESAVE option.<0:14>must be 0. Effect The option not selected must be set to 0 even though it is not used. Until it is set to 0, other options cannot be selected. Recovery Set the unused option to 0. 2076 (%004034) The buffer is too small for the saved DEFINE. Cause The buffer was too small to contain the DEFINE. Effect The DEFINE is not saved. The buffer size required to save the DEFINE is returned in the length parameter.
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. In many cases, the error message must be decoded.
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. 2 (%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. Effect No process is created.
Table 6 NEWPROCESS Error 6 Error Subcodes (continued) Decimal Octal Meaning 7 %007 The library file does not have the correct file structure. 8 %010 The program file requires a later version of the operating system. 9 %011 The library file requires a later version of the operating system. 10 %012 The program file does not have a main procedure. 13 %015 The library file has a main procedure. 14 %016 Program file has a stack definition of zero pages.
Table 6 NEWPROCESS Error 6 Error Subcodes (continued) Decimal Octal Meaning 47 %057 Library file has entry in TNS/R fixup list with invalid external entry-point (XEP) index value or invalid code address value. 48 %060 Accelerated program file has external procedure identifier list (EPIL), internal procedure identifier list (IPIL), or external entry-point (XEP) table with incorrect format.
Table 6 NEWPROCESS Error 6 Error Subcodes (continued) 146 Decimal Octal Meaning 84 %124 The code area of the program file is too large. 85 %125 The code area of the library file is too large. 86 %126 The program file has a gateway (GW) table but no callable procedures. 87 %127 The library file has a gateway (GW) table but no callable procedures. 89 %131 The file codes of the program file and library file do not match.
Table 6 NEWPROCESS Error 6 Error Subcodes (continued) Decimal Octal Meaning 112 %160 The program file specifies too many shared run-time libraries (SRLs). 113 %161 The library file specifies too many shared run-time libraries (SRLs). 114 %162 The program file specifies duplicate shared run-time libraries (SRLs). 115 %163 The library file specifies duplicate shared run-time libraries (SRLs). 117 %165 The shared run-time library (SRL) does not export any procedures.
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 For corrective action for error number %nnn, see “File-System Errors” (page 19). 12 (%006000) PROGRAM FILE AND LIBRARY FILE ARE THE SAME Cause The program file and library file are the same file. Effect No process is created. Recovery Select a different library file for the program.
Bits <8:15> contain a subcode that indicates the cause of the error, as follows: Subcode Meaning 0 Unable to convert a DEFINE name to network form. 2 Internal error. 3 Illegal DEFMODE supplied. Effect No process is created. Recovery Retry the call to NEWPROCESS. If errors recur, contact your service provider. 18 (%011000) OBJECT FILE WITH AN ILLEGAL DEVICE SUBTYPE Cause An attempt was made to run an object file with an invalid device subtype.
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. 24 (%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. Effect The call returns the PROCESS_CREATE_ error number %nnn, or 119 if the actual error number is too large, in errinfo.<8:15>. No process is created.
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 For corrective action for the file-system error returned in errinfo.<8:15>, see “File-System Errors” (page 19). If the file-system error indicates an invalid operation or an invalid parameter, the problem might be caused by a version mismatch between the NonStop operating system and Standard Security.
Recovery Use the original object files and the nld utility to re-create the program file. If the error recurs, contact your service provider. 36 (%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. %nnn in error.<8:15> contains the SRL number of the SRL that was not found. Recovery Use the original object files and the nld utility to re-create the program file.
Cause A security violation occurred. The program file is not licensed but a shared run-time library (SRL) is licensed and has instance data. 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. 42 (%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. Effect %nnn in error.
Effect No process is created. Recovery Use the original object files and the nld utility to re-create the program file. 51 (%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.
Recovery Either correct the coding error, use nld utility to add the data to the data area or user library, or refer the call to the data that is already present in the application program. 119 (%073400) ERROR NUMBER RETURNED IS TOO LARGE Cause The error returned in error.<0:7> is too large to fit into one byte. Effect No process is created. Recovery Instead of the error parameter, specify the errinfo parameter, which is a two-word parameter, to obtain complete error information.
3: ZGRD-VAL-NEWPROCESS There was an error during a call to NEWPROCESS. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZSPI-TKN-ENDLIST token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL.
4: ZGRD-VAL-NEWPROCESSNOWAIT There was an error during a call to NEWPROCESSNOWAIT. Unconditional Tokens ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZSPI-TKN-ENDLIST token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL.
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. For more information on error codes and error lists produced by PROCESS_SPAWN_, see “PROCESS_SPAWN_ Open System Services (OSS) Errors” (page 194). You can create a process with a number of different procedures.
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 For corrective action for the file-system error returned in the error-detail information, see “File-System Errors” (page 19). 2 PARAMETER ERROR Cause The call contained an invalid combination of options.
Table 7 Error Subcodes for PROCESS_LAUNCH_ and PROCESS_SPAWN_ Errors 2 and 3 (continued) error- detail PROCESS_LAUNCH_ Structure Field or Parameter in Error PROCESS_SPAWN_ Structure Field or Parameter in Error 21 The program image file is in error. This error subcode is returned if PROCESS_LAUNCH_ is called from COUP; it applies only to some privileged callers on D-series releases. The program image file is in error.
Recovery For corrective action for the file-system error returned in the error-detail information, see “File-System Errors” (page 19). 7 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.
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 162). Effect No process is created. Recovery Take corrective action as indicated by the subcode. For example, if subcode 1 or 2 is returned, use the FUP INFO command to check the file code. In many cases, the object file was built improperly or corrupted. It must be relinked and perhaps recompiled.
Table 8 Error Subcodes for Process Creation Errors 12, 13, 70, 76, 84, and 3xx (continued) Subcode Meaning 23 File has entry in TNS/R fixup list with invalid external entry-point (XEP) index value or invalid code address value. 24 Accelerated file has external procedure identifier list (EPIL), internal procedure identifier list (IPIL), or external entry-point (XEP) table with incorrect format.
Table 8 Error Subcodes for Process Creation Errors 12, 13, 70, 76, 84, and 3xx (continued) Subcode Meaning 51 The program or library file does not have a valid ELF header for execution on this NonStop operating system. The file either is not targeted for this system, is not an ELF file, or has been corrupted. 52 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.
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.
Cause The program file and library file are the same file. Effect No process is created. Recovery Select a different library file for the program. 20 PROGRAM FILE WITH AN ILLEGAL DEVICE SUBTYPE Cause An attempt was made to run a program file with an invalid device subtype. The device subtype is an attribute stored in each program file. The process created from a program file is assigned the device subtype stored in that program file. Only named processes are allowed nonzero device subtypes.
Recovery Retry the call. If errors recur, contact your service provider. 26 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. Effect No process is created. Recovery Run software that is properly configured for your system. 27 ILLEGAL PFS SIZE Cause The size specified for the process file segment (PFS) is invalid.
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 For corrective action for the file-system error returned in the error-detail information, see “File-System Errors” (page 19).
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. 41 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. Effect No process is created.
Recovery Use the original object files and the nld utility to re-create the program file. If the error recurs, contact your service provider. 46 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); the error-detail information contains the maximum number of SRLs that can be specified. Effect No process is created.
Recovery Either remove the licensing of the program, if possible, or use the nld utility to specify another SRL. 51 THE PROGRAM FILE REQUIRES A SYMBOL FROM A SHARED RUNTIME 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; the error-detail information contains the SRL number of the SRL that does not export the required symbol. Effect No process is created.
Recovery Retry the call. If this error recurs, contact your service provider. 57 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. Recovery Check that the SRL versions match and obtain matching versions if they do not; otherwise, contact your service provider.
Recovery Use the original object files and the nld utility to recreate the program file. 63 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. For example: PID: \SAT.1,284 \SAT.$DATA.SRLVOL.NULCLIE2 (ELF) External References Not Resolved to Any User/System Library: Prg: \SAT.$DATA.SRLVOL.
Cause The system did not recognise 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-subcodes are listed in Table 10. Table 10 Error Subcodes for Process Creation Error 66 Subcode Meaning 2 Unrecognized floating-point specification in file. 4 This library specified Tandem floating-point, which mismatches the program.
Table 13 Corrective Action for Process Creation Error 67 Subcode Corrective Action 2 The DLL file specified to create the process contains incorrect or corrupt information about the floattype. Recompile the object file(s) using a valid floattype. 4 Recompile and relink the object file(s) using the same floating-point type for all, or if the DLL does not operate on floating-point data, force its floattype attribute to neutral_float.
Table 15 Error Subcodes for Process Creation Error 71 Subcode Meaning 9 The process abended while rld was running. 10 The process stopped while rld was running. 11 RLD is licensed. 12 rld returned an out-of-range error value to the operating system. 16 The export digest of the file does not match the export digest of the impImp file in memory. 19 The user attempted to use RLD as a user library. This is not supported. 22 RLD began processing, but did not complete the update of a loadfile.
Recovery For corrective action for the file-system error returned in the error-detail information, see “File-System Errors” (page 19). 76 INVALID FILE FORMAT IN A DLL Cause An error was detected in the file format of a DLL. The error-detail information contains an error subcode that indicates the invalid file format error. These errors are listed in Table 8 (page 162). Effect No process is created. The name of the DLL for which the error occurred is reported to the home terminal.
Table 17 Error Subcodes for Process Creation Error 77 (continued) Subcode Meaning 18 The loadfile was built to use an Application Binary Interface version that is not supported. 19 A process with OSS file privileges attempted to load an ordinary DLL with lesser OSS file privileges. Effect No process is created. The name of the file involved might be reported on the home terminal. Recovery This depends on the error detail.
Table 18 Corrective Action for Process Creation Error 77 (continued) Subcode Corrective Action 17 Relink the file if the environment changes, or do not 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. 18 Recompile the source code with current compilers and relink the loadfile with the current linker. Contact your service provider.
Cause The error-detail information contains an error subcode that indicates the nature of the error. The error-subcodes are listed in Table 21. Table 21 Error Subcodes for Process Creation Error 79 Subcode Meaning 1 The RLD heap attempted to exceed available KMSF space. 2 The RLD heap attempted to exceed its allocated address range. 3 RLD limit of handles was exhausted. This error is reported for dynamic loading, not at process creation. 4 The process limit for keys is exhausted.
Recovery Take corrective action as indicated by the error subcode. 83 A FILE SYSTEM ERROR WAS ENCOUNTERED ON THE TNS EMULATOR Cause A file system error occurred on the TNS Emulator while attempting process creation. The error detail contains a file system error number. Effect No process is created. Recovery For corrective action for the file-system error returned in the error-detail information, see “File-System Errors” (page 19).
Cause (This error is returned only by PROCESS_SPAWN_.) An OSS process cannot be created because there are insufficient resources. Effect No process is created. Recovery The recovery method depends on the error-detail code received: 1. Request TNS floating point in your creation request, or upgrade to a release and processors that support IEEE floating point. 2. Change your process create request to one of the supported floating point types. 3.
corrective action for the file-system error returned in the error-detail information, see “File-System Errors” (page 19). 111 OSS FILE DESCRIPTOR DUP ERROR Cause (This error is returned only by PROCESS_SPAWN_.) One of the file descriptors specified to be duplicated with the OSS dup() function that was passed in the fdinfo parameter was not duplicated. The ZSYS-DDL-PROCESSRESULTS.Z-TPCDETAIL field of the process-results parameter contains the index into the ZSYS-DDL-FDINFO.
Cause (This error is returned only by PROCESS_SPAWN_ .) The system was unable to allocate global data or heap for the process. Effect No process is created. Recovery Run on another processor or try later. 116 UNABLE TO PROPAGATE SHARED RUN-TIME LIBRARY (SRL) DATA (PROCESS_SPAWN_ ONLY). Cause (This error is returned only by PROCESS_SPAWN_ .) The system was unable to propagate shared run-time library (SRL) data. Effect No process is created. Recovery Run on another processor or try later.
Each error list always includes the unconditional tokens listed under its description in this subsection. In addition, each error list can include any of the conditional tokens listed under its description. If you are designing a subsystem that uses SPI, follow these guidelines when constructing a PROCESS_LAUNCH_ or PROCESS_CREATE_ error list: • Include all unconditional tokens listed in the error-list description.
ZGRD-TKN-ERRORDETAIL is the error-detail information returned by PROCESS_CREATE_ for some classes of errors. ZGRD-TKN-NAMEOPTION is the specified process name option. ZGRD-TKN-XPROCESSNAME is the new process name. ZGRD-TKN-PROCESSDESCR is the process descriptor returned by PROCESS_CREATE_. If its length is 0, no process was created. ZGRD-TKN-XHOMETERM is the name of the home terminal for the new process. ZGRD-TKN-JOBID is the job ID to be assigned to the new process.
returned in the error parameter of PROCESS_LAUNCH_. This error code indicates the outcome of the process-creation attempt. ZSPI-TKN-PROC-ERR is the procedure code. Its value is ZGRD-VAL-PROCESS-LAUNCH (25). ZSPI-TKN-ERRORDETAIL is the error-detail information returned by PROCESS_LAUNCH_. Conditional Tokens ZGRD-TKN-XOBJECTFILE is the file name of the program file to be run. ZGRD-TKN-XLIBRARYFILE is the name of the user library file to be used by the process, if one was explicitly named.
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. The PROCESS_GETINFO_ procedure muist be used when the caller requires only selected information about a particular process.
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_. 4 SPECIFIED PROCESS DOES NOT EXIST Cause The specified process does not exist or does not meet the search criteria.
Recovery Correct the attribute value, then try again. 11 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. Effect The return is not done. Recovery Correct the return attribute code, then try again. 12 INVALID SEARCH OPTION Cause The search option was not valid.
Recovery Do not specify this attribute code in et-attr-list when the srch-option is 1 or 2. 17 Attribute restricted to privileged callers. Cause The error-detail parameter contains 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 privileged mode.
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 must be used when the caller requires only selected information about a particular process. Error Codes This subsection lists each PROCESS_GETPAIRINFO_ procedure error code and provides a description of each code.
Effect Information is successfully returned. Recovery None required. 7 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. 8 SEARCH IS COMPLETE Cause The search has finished. Effect No information is returned. The search finished and no more information was found.
9 PROCESS_SPAWN_ Open System Services (OSS) Errors The following error codes and error lists are produced by PROCESS_SPAWN_, the process-control procedure that creates an Open System Services (OSS) process. The process-results parameter of PROCESS_SPAWN_ returns the ZSYS-DDL-PROCESSRESULTS structure, which contains errors detected by the OSS environment and errors detected by the Guardian environment. You must examine all error fields to determine the source of the error.
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. 4007 ARGUMENT LIST TOO LONG Cause The number of bytes available for the new process's combined argument (argv) and environment (envp) lists has exceeded the system-imposed limit.
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. The corresponding OSS errno value is ENOMEM. Effect No process is created.
Cause The specified pathname or a component of the pathname is longer than PATH_MAX characters. (PATH_MAX is a symbolic constant that is defined in the OSS limits.h header file.) The corresponding OSS errno value is ENAMETOOLONG. Effect No process is created. Recovery Correct the parameter containing the erroneous pathname. 4203 OSS NOT RUNNING OR NOT INSTALLED Cause Open System Services is not running. To create an OSS process, Open System Services must be running.
ZGRD-TKN-SWAP-PATH ZGRD-TKN-EXTSWAP-PATH ZGRD-TKN-TERM-PATH ZGRD-TKN-CWD-PATH ZGRD-TKN-FD-PATH ZGRD-TKN-FDINFO ZGRD-TKN-ARG ZGRD-TKN-ENV ZGRD-TKN-PROCESS-EXTENSION ZGRD-TKN-PATH token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-BYTESTRING. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-BYTESTRING. ZSPI-TYP-STRING.
Recovery Follow the recovery procedure for the returned PROCESS_SPAWN_ errors as described earlier in this section.
10 ALLOCATESEGMENT Errors This section contains the error codes returned by the ALLOCATESEGMENT procedure and the error lists associated with the ALLOCATESEGMENT procedure. Error codes and error lists associated with the SEGMENT_ALLOCATE_ procedure are described in “SEGMENT_ALLOCATE_ and SEGMENT_ALLOCATE64_ Errors” (page 204). The error list for USESEGMENT is described in “USESEGMENT Errors” (page 209). The error list for SEGMENT_USE_ is described in “SEGMENT_USE_Errors” (page 211).
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. -5 UNABLE TO ALLOCATE SEGMENT SPACE Cause ALLOCATESEGMENT did not allocate extended data segment space. Effect The procedure sets the error code and returns without allocating the extended data segment. Recovery Retry the operation, or run the application on another processor.
Recovery Make sure the PIN specified in pin-and-flags is not the PIN of the calling process. -11 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. Effect The procedure sets the error code and returns without accessing the extended data segment.
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 PINANDFLAGS.<0:7> Flag options PINANDFLAGS.
11 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 200).
Recovery Correct the call to SEGMENT_ALLOCATE_ so that the options are correct and in the proper order. 3 BOUNDS VIOLATION Cause A bounds violation occurred on a reference parameter. The reference parameter address is checked for length and location. The error-detail parameter contains the ordinal number of the first (leftmost) parameter encountered whose option is in error. Effect The procedure sets the error code and returns without any further action.
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. • The group manager for the access ID of the other process • The super ID (255,255) 9 PIN DOES NOT EXIST Cause The SEGMENT_ALLOCATE_ call specified an invalid PIN.
Effect The procedure sets the error code and returns without accessing the extended data segment. Recovery Wait until more process file segment (PFS) space is available, or run the application on another processor. For corrective action for the file-system error returned in the error-detail information, see “File-System Errors” (page 19). 15 REQUESTED ADDRESS RANGE ALREADY ALLOCATED Cause Part or all of the specified address range has already been allocated.
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). Conditional Tokens ZGRD-TKN-XOBJECTFILE is the name of the object file that contains the SEGMENT_ALLOCATE_ procedure call in internal format.
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 can typically use the SEGMENT_USE_ procedure on D-series and later releases, while you used the USESEGMENT procedure on C-series releases.
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. Effect The extended data segment requested is not enabled for use by the caller.
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 can typically use the SEGMENT_USE_ procedure on D-series and later releases, while you used the USESEGMENT procedure on C-series releases.
Conditional Tokens ZGRD-TKN-XOBJECTFILE is the name of the object file that contains the SEGMENT_USE_ procedure call in internal format. ZGRD-TKN-SEGMENTID is the extended data segment ID requested. ZGRD-TKN-OLDSEGMENT is the previous extended data segment ID in use. ZGRD-TKN-ERRORDETAIL is the detailed information associated with some classes of errors. Effect The extended data segment requested is not enabled for use by the caller.
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. When any of these errors (except error 0 or error -1) occurs, the header token ZSPI-TKN-LASTERR is set to the error number.
• 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. Recovery Correct the parameter in error.
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. -6 ZSPI-ERR-XSUMERR Invalid checksum Cause The current buffer checksum does not match the checksum computed on return from the last SPI call. This error suggests that the buffer has been modified or damaged.
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. • The token length was not a multiple of the basic length associated with the token data type. • The token map contained an invalid null-value specification.
Cause A file-system error occurred. Effect The requested operation is not completed. Recovery Corrective action depends on the error. Check Table 25 for an explanation of the status-1 and status-2 parameters. Table 25 Supplementary Status Values Error status-1 status-2 Explanation -13 2 x File-system error x received during an open of the nonresident template file. -13 1 x File-system error x received during a read of the nonresident template file.
Recovery No recovery is possible. Report this error to your service provider. -27 ZSPI-ERR-NO-FORMATID No format ID available Cause Currently, no more than one format ID can be active at one time. Effect The requested operation is not completed. 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.
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.
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. Effect The call to SSMOVE or SSMOVETKN fails. Recovery Follow the recovery procedure for the returned SPI error code as described earlier in this section.
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). ZSPI-TKN-PARM-ERR contains fields ZTOKENCODE, ZINDEX, and ZOFFSET.
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. For EDITREAD, a positive value represents the number of characters that the procedure read in the text line. Effect None.
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. Effect The procedure sets the error code and returns without performing the requested function.
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.
Recovery Correct the request. 10 (%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. IOEdit has no procedure corresponding to WRITEUPDATE; you can rewrite a record only by first deleting it (by calling DELETEEDIT). Effect No action is taken.
Recovery Call EXTENDEDIT to increase the file's capacity, then try the call to WRITEEDIT again. 46 (%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. Recovery Specify a valid EDIT line number.
Recovery Proceed as described at the beginning of this subsection. -4 (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. -5 (duplicate block numbers in the directory) Cause A directory error occurred in an EDIT file. Effect Processing stops. Recovery Proceed as described at the beginning of this subsection.
Recovery The file is bad but possibly most of the file's contents can be recovered by copying the entire file and ignoring only the records having this error. -10 (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. Effect The procedure stops.
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 must 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. Effect The calling process is terminated abnormally. Recovery Recovery is not possible.
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, see the Guardian Programmer's Guide. Error Codes This subsection lists each FORMATDATA[X] procedure error code and provides a description of each code.
Recovery Correct the format or the data list. 273 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. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Correct the format. 274 NUMERIC OVERFLOW Cause A data element's numeric value was so small or so large that FORMATDATA[X] did not place it in its corresponding data element.
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, see 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. The error message is passed along in the ABEND procedure call to the process's creator.
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. Effect INITIALIZER prepares the error message and calls ABEND.
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. Recovery Make sure $RECEIVE is not open when you call INITIALIZER. Error message: "INITIALIZER: Unexpected error" Cause This is an internal error.
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. If a user-written command interpreter is in use, read command interpreter instead of TACL in the following messages.
Table 26 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 Sent to $CMON in deluser^msg -56 Alter Priority Sent to $CMON by TACL process -57 Password Sent to $CMON in password^msg -58 Remote Password Sent to $CMON in remotepassword^msg -59 Prelogon Sent to
END; STRING param [0:n-1]; ! ! ! ! ! ! ! ! ! ! END; [33] parameter string of the RUN command (if any) that was entered by the operator.
INT recordsize; INT blocksize; ! [52] record-size ! [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. -3 PARAM Cause A new process receives a PARAM message if any parameters are in effect when the new process is created. The PARAM messages immediately follow the ASSIGN messages if the process does one of the following: • Replies to the startup message with an error return value of 70.
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. Format The format of the display message follows. The message length is 2 bytes plus the display-text length (in bytes).
INT cioutfile [0:11]; ! command file ! [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.
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. END; The $CMON process can reply in one of two ways: • With a run-the-process reply • With a disallow-process-creation reply A run-the-process reply contains the process priority and the name of the processor where the process runs.
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. -53 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. No byte count is returned.
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; ! ! ! ! STRING replytext [0:n]; ! ! ! END; [0] 0 = allow addition of user 1 = disallow addition of user [1] optional message to be printed; maximum length of 132 bytes The length of the message is 2 bytes plus the reply-text length in bytes.
change the priority of any process. However, if the $CMON process is not running, then no $CMON alter-priority restrictions are in effect.
INT replycode; ! ! ! ! STRING replytext [0:n]; ! ! ! END; [0] 0 = allow password to be changed 1 = disallow password to be changed [1] optional message to be printed; maximum length of 132 bytes 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. If reply-count=2, no text is displayed. -58 REMOTE PASSWORD Cause The user tried to change his or her remote password.
INT INT INT INT cipri; ciinfile [0:11]; cioutfile [0:11]; loggedon; INT username [0:7]; ! ! ! ! ! ! ! ! ! ! ! ! 0 if the user is logged off or is logged on as NULL.NULL (0,0) [2] current priority of TACL [3] TACL IN file [15] TACL OUT file [27] 0 if TACL is currently logged off, non-zero if TACL is already logged on [28] internal username through which the user wants to log on END; The $CMON reply indicates whether the user can log on and contains an optional display message.
INT autologoffdelay; INT logoffscreenclear; INT remotesuperid; INT blindlogon; INT namelogon; INT cmontimeout; INT cmonrequired; INT remotecmontimeout; INT remotecmonrequired; INT nochangeuser; INT stoponfemodemerr; INT requestcmonuserconfig; END; ! ! ! ! ! ! ! ! ! ! ! ! [2] see #GETCONFIGURATION [3] description in the [4] TACL Reference [5] Manual for more [6] information on these [7] parameters.
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 must not be used for new development.
Table 27 D-Series-Format System Messages (continued) -22 Elapsed Time Timeout -23 Memory Lock Completion -24 Memory Lock Failure -26 Process Time Timeout -32 Process CONTROL -33 Process SETMODE -34 Process RESETSYNC -35 Process CONTROLBUF -37 Process SETPARAM -38 Queued Message Cancellation -41 Nowait DEVICEINFO2 Completion -100 Remote Processor Down -101 Process Deletion: ABEND, STOP, or Processor Down -102 Nowait PROCESS_LAUNCH_ or PROCESS_CREATE_ Completion -103 Process Open
Table 28 C-Series and D-Series System Messages Compared (continued) -5 Process Deletion: STOP -5 Process Deletion: STOP Process Deletion: ABEND -101 Process Deletion: ABEND Change in Status of Network Node -100 Remote Processor Down -110 Remote Processor Down Loss of Communication With Network Node Establishment of Communication With -111 Network Node Remote Processor Up -113 -9 Job Process Creation -112 Job Process Creation -10 SETTIME -10 SETTIME -11 Power On -11 Power On -12 NE
Message Descriptions This subsection lists the system messages and provides a description of each message. -2 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.
sysmsg[11] sysmsg[12] sysmsg[13] sysmsg[17] sysmsg[18] sysmsg[19] sysmsg[20] • = The completion code = Termination information; 0 if the user did not supply information FOR 4 = The subsystem organization name; for HP products,this is HP = The subsystem number = The subsystem version = The length of text in bytes FOR n = Up to 80 bytes of text If the call to the STOP procedure deletes the process name from the process-pair directory, the operating system sends this message: sysmsg[0] sysmsg[1] FOR 3 sysm
sysmsg[17] sysmsg[18] sysmsg[19] sysmsg[20] FOR n • for HP products, this is HP The subsystem number The subsystem version The length of text in bytes Up to 80 bytes of text = = = = If the operating system deletes the process name from the process-pair directory, it sends the following message. This message indicates that neither member of the process pair exists.
Response The response, if any, is application dependent. -9 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.
sysmsg[9] error = NEWPROCESS suberror or file-system For more information on the NEWPROCESS error, see “NEWPROCESS AND NEWPROCESSNOWAIT Errors” (page 142) TPSEC05.fm NEWPROCESS AND NEWPROCESSNOWAIT Errors. NOTE: If 119 is returned in sysmsg[1].<8:15>, the file-system error number is greater than 255. The actual error is in sysmsg[9]. Response The response, if any, is application dependent.
Response The response, if any, is application dependent. -22 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] sysmsg[1] = -22 = parameter1 supplied to SIGNALTIMEOUT (0 if none) sysmsg[2] FOR 2 = parameter2 supplied to SIGNALTIMEOUT (0D if none) Response The response, if any, is application dependent.
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> to 0 or the OPEN procedure parameter flags.
Response Obtain the process ID of the caller to CONTROL by a call to LASTRECEIVE or RECEIVEINFO. The response, if any, is application dependent. -33 PROCESS SETMODE Cause Another process referred to the receiving process in a call to the SETMODE or SETMODENOWAIT procedure. 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.
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.
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; in these cases, the cancellation message does not appear. Do not use the cancellation notice to determine the delivery status of replies.
Response The response, if any, is application dependent. -100 REMOTE PROCESSOR DOWN Cause The remote operating system has declared a processor to be down, and the process had called MONITORNET to monitor remote status changes.
sysmsg[34] sysmsg[35] sysmsg[36] sysmsg[37].<0:13> sysmsg[37].<14> sysmsg[37].
Table 29 Completion Codes (continued) Completion Code Definition 5 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. 6 PROCESS_STOP_, STOP, or ABEND was called to delete a process by an external, but authorized, process. The system includes this completion code in the process deletion message.
Table 29 Completion Codes (continued) Completion Code Definition -12 One of the OSS exec or tdm_exec set of functions executed successfully. The OSS process ID continues to exist as it migrates to another process handle, but the original process handle is deleted. Call PROCESS_GETINFOLIST_ to obtain the new process handle of the OSS process. -13 The OSS open() or dup() function performed by the PROCESS_SPAWN_ procedure failed.
FILE_OPEN_ procedure parameter options.<15>to 0 or the OPEN procedure parameter flags.
repmsg[0] = -103 repmsg[1] = OpenLabel value -104 PROCESS CLOSE Cause The receiving process was closed by another process. 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.
repmsg[3] FOR 3 repmsg[6] -107 = Reserved, must be filled with -1 = Physical record length SUBORDINATE NAME INQUIRY 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] sysmsg[1] FOR 2 sysmsg[3] sysmsg[4] FOR 5 sysmsg[9] sysmsg[10] = -108 = The tag value from the timeout-or-tag parameter to FILE_GETINFOBYNAME_ = The file-system error code giving the resultant status of the request = The type information (device type, and so on) having the same layout as described for the typeinfo parameter of FILE_GETINFOBYNAME_ = The physical record length value = The flag value from the flag
sysmsg[8] = Length in bytes of the returned name (zero if none present because of an error) = The tag parameter from FILENAME_FINDNEXT64_ = Reserved, subject to change = The returned name, in external form with a length given in sysmsg[8] sysmsg[9] FOR 4 sysmsg[11] sysmsg[14] FOR * Response The process can use the information returned (if sysmsg(2) indicates no error occurred).
sysmsg[4] sysmsg[5] FOR 3 sysmsg[8] FOR * = Length of node name, in bytes = Reserved = Node name (including the \) 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.
Cause The receiving process (which must have subtype 30 to receive this message) was the subject of a call to CONFIG_GETINFO_BYLDEV_, CONFIG_GETINFO_BYNAME_, or a similar procedure requesting physical device information. This message is used only on G-series releases.
NOTE: When evaluating the size of the data structure that contains everything preceding the device-specific information (as declared in the Guardian Application Conversion Guide 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 is $len(data)-1; the correct length in C is sizeof(data)-2.
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.
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 must 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. The actions of a signal handler typically include either terminating the process or, in certain cases, resuming execution.
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. For further information, see “Trap Handling” (page 273). For the signal SIGILL, the default or specified signal handling occurs. For further information, see “Signal Handling” (page 274). Recovery Check your application program.
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. ◦ There was not enough remaining virtual data space for an operating-system procedure to execute.
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. For further information, see “Trap Handling” (page 273). For the signal SIGTIMEOUT, the default or specified signal handling occurs. For further information, see “Signal Handling” (page 274).
Cause This error occurs for one of the following reasons: • A page fault occurred, but no physical memory page is available for overlay. • Disk space cannot be allocated when the program is referencing an extensible segment. Effect For trap 12, 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. For more information, see “Trap Handling” (page 273).
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 ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZSPI-TKN-ENDLIST token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL.
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.
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.
Index A ALLOCATESEGMENT procedure error codes, 200 error list, 202 guidelines for using, 202 C C language error numbers for file-system errors, 20 C-series procedure errors, 16 Command interpreter messages, 17, 236, 247 description of, 235 Completion codes, 264 D DEFINE procedure error codes, 136 DSM/Storage Manager errors, 19 E EDITREAD procedure error codes, 222 EDITREADINIT procedure error codes, 222 errno values for file-system errors, 20 Error codes ALLOCATESEGMENT procedure, 200 DEFINE procedure, 1
PROCESS_LAUNCH_ procedure, 186 guidelines for using, 185 PROCESS_SPAWN_ procedure, 197 guidelines for using, 197 SEGMENT_ALLOCATE_ procedure, 207 guidelines for using, 207 SEGMENT_USE_ procedure, 211 guidelines for using, 211 signal error list, 279 guidelines for using, 278 SSGET procedure, 218 SSGETTKN procedure, 218 SSINIT procedure, 219 SSMOVE procedure, 219 SSMOVETKN procedure, 219 SSNULL procedure, 220 SSPUT procedure, 220 SSPUTTKN procedure, 220 Subsystem Programmatic Interface (SPI) general descripti
Interprocess command interpreter messages, 17, 236, 247 description of, 235 Interprocess messages, general description of, 17 IOEdit procedures catastrophic error messages, 228, 229 file-system error codes used by, 224, 226 unique error codes used by, 226, 228 M Messages command interpreter, 236, 247 interprocess, general description of, 17 N NEWPROCESS procedure error codes, 142, 155 error list, 156 guidelines for using, 155 NEWPROCESSNOWAIT procedure error codes, 142, 155 error list, 157 guidelines for
SIGNOMEM, 277 SIGSEGV, 274 SIGSTK, 275 SIGTIMEOUT, 276 SIGNOMEM signal, 277 SIGSEGV signal, 274 SIGSTK signal, 275 SIGTIMEOUT signal, 276 SSGET procedure error list, 218 SSGETTKN procedure error list, 218 SSINIT procedure error list, 219 SSMOVE procedure error list, 219 SSMOVETKN procedure error list, 219 SSNULL procedure error list, 220 SSPUT procedure error list, 220 SSPUTTKN procedure error list, 220 Subsystem Programmatic Interface (SPI) error codes, 213, 218 error lists, 218, 221 general description of
