HP 3000 Manuals HP 3000 Manuals
File Transfer Errors (cont.)
TRANSFER Errors
File Transfer TRANSFER Errors
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(200) | Dialing error on <type of modem> modem |
| | |
| | * Meaning: Error dialing modem. The type of modem is |
| | indicated; if this is unrecognized, the modem could not |
| | be identified. |
| | |
| | * Action: Following this message in the run log or Action |
| | Summary should be textual description of the error with |
| | an error number (such as CTL, (xxx)). Refer to Appendix |
| | E, "Datacomm Troubleshooting Guide," and use the dialing |
| | error and error description to resolve the problem. |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(200) | Failure on upload/download of <file name>; PGERR xxx FSERR yyy |
| | |
| | |
| | * Meaning: Transfer failure. Upload is from customer to |
| | HP Response Center; download the other direction. The |
| | file name, program error (PGERR), and file system error |
| | (FSERR) are provided. |
| | |
| | * Action: A textual description of the error (that is, |
| | XFR(XXX)) should follow this message in the run log or |
| | Action Summary. Refer to Appendix E, "Datacomm |
| | Troubleshooting Guide," and use the error number and |
| | description to resolve the problem. |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(200) | Failure on connection; PGERR xxx FSERR yyy |
| | |
| | * Meaning: Failure after connection with HP Response |
| | Center was made but before any file transfer was |
| | initiated. The program error (PGERR) and file system |
| | error (FSERR) are provided. |
| | |
| | * Action: Should follow this message in the run log or |
| | Action Summary. A textual description of the error. |
| | Refer to Appendix E, "Datacomm Troubleshooting Guide," |
| | and use the error number and description to resolve the |
| | problem. |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(200) | PSUXFRDP error |
| | |
| | * Meaning: Internal error in PSUXFRDP prevented transfer. |
| | |
| | |
| | * Action: See run log for error messages from PSUXFRDP. |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(300) | Received shutdown request from Predictive Monitor |
| | |
| | |
| | * Meaning: Either the user issued a stop, or a HP |
| | Predictive Support run was started before PSUXFRDP could |
| | complete any attempts to transfer. |
| | |
| | * Action: Request transfer from psconfig as necessary, |
| | and allow to complete. |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(400) | Operator has denied approval for Predictive transfer |
| | |
| | |
| | * Meaning: Operator replied 'N' to console request for |
| | Predictive to use modem. |
| | |
| | * Action: If the user wishes transfer to proceed, run |
| | again from psconfig and reply `Y' to request. |
| | |
------------------------------------------------------------------------------------
Table F-5. File Transfer TRANSFER Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(500) | PSUXFDMP internal error xxx. |
| | |
| | * Meaning: PSUXFDMP experienced an error, the nature of |
| | which is explained by the value of xxx when this message |
| | appears. |
| | |
| | * Action: The action to take depends on the value of xxx. |
| | |
| | |
| | If xxx is replaced by: |
| | |
| | * -4 : A console request failed. If the error |
| | persists, contact the HP Response Center. |
| | |
| | * -2 or other error: PSUXFDMP experienced a fatal |
| | Sherlock error. Refer to the run log (PSRNLOGD) |
| | and examine the messages accompanying this |
| | message for more information. |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(510) | PSUXFDMP run log open failure. No transfer. |
| | |
| | |
| | * Meaning: PSUXFDMP could not open run log, |
| | PSRNLOGD.PRED.SYS. |
| | |
| | * Action: See the console messages to the determine cause |
| | of the error. Make sure no other process or user is |
| | reading from the file, and a store is not in progress. |
| | If the error persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(520) | PSUXFDMP Action Summary open failure. No transfer. |
| | |
| | |
| | * Meaning: PSUXFDMP was unable to open the Action Summary |
| | file. |
| | |
| | * Action: See previous error messages in the run log to |
| | determine the nature of the error. Make sure no other |
| | process or user is reading from PSASFILE.PRED.SYS, and a |
| | store is not in progress. |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(530) | PSUXFDMP database open failure. No transfer. |
| | |
| | |
| | * Meaning: PSUXFDMP could not open OPSDB. |
| | |
| | * Action: See previous error messages in the run log to |
| | determine the nature of the error. |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(540) | PSUXFDMP file open failure. No transfer. |
| | |
| | |
| | * Meaning: PSUXFDMP could not open a file. |
| | |
| | * Action: See previous error messages in the run log to |
| | determine which file PSUXFDMP was unable to open. |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(550) | PSUXFDMP configuration failure. No transfer. |
| | |
| | |
| | * Meaning: PSUXFDMP was unable to retrieve valid |
| | configuration values. |
| | |
| | * Action: See previous error messages in the run log to |
| | determine the nature of the error. Run psconfig and |
| | provide any missing values. |
| | |
------------------------------------------------------------------------------------
Table F-5. File Transfer TRANSFER Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(560) | PSUXFDMP message catalog open failure. No transfer. |
| | |
| | |
| | * Meaning: PSUXFDMP was unable to open the message |
| | catalog. |
| | |
| | * Action: If the error persists, restore |
| | PSUXFRDM.PRED.SYS from a backup or the installation |
| | tape. Make sure no other user or process is accessing |
| | PSUXFRDM.PRED.SYS exclusively. |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(600) | PSUXFDMP did not receive status from PSUXFRDP. |
| | |
| | * Meaning: PSUXFDMP received termination notification |
| | from PSUXFRDP but did not receive final status. |
| | |
| | * Action: If the error persists, contact the HP Response |
| | Center. |
| | |
------------------------------------------------------------------------------------
| | |
| Transfer(700) | Checking for downloads. No action necessary. |
| | |
| | |
| | * Meaning: No files were transferred on this connection. |
| | This was probably the result of a transfer force, in |
| | which there were no downloads scheduled. |
| | |
| | * Action: No action is necessary. |
| | |
------------------------------------------------------------------------------------
XFR Errors
Table F-6. File Transfer XFR Errors
------------------------------------------------------------------------------------
| | |
| Error | Message/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(299) | Character scan failed to see a dc1 |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6 and #4 (in that order). |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(300) | Error while writing to port |
| | |
| | * Meaning: The phone line may have inadvertently been |
| | disconnected, or the modem or modem port configuration is in |
| | error. |
| | |
| | * Action: |
| | * Repeat the transfer attempt. |
| | * If the error continues, check the modem option settings |
| | (see Appendix C) and the datacomm port configuration |
| | (see Appendix D). |
| | * If the modem options settings are correct as well as |
| | the datacomm port configuration, and an FSERR # |
| | accompanies the message, look up the FSERR number in |
| | the subsection, "FSERR Port Errors" (located at the end |
| | of this appendix) for additional instructions. |
| | * Finally, if correcting the FSERR condition does not |
| | work, go to Appendix E, "Datacomm Troubleshooting |
| | Guide," Procedure #5 and reset the port. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(301) | Error setting up port |
| | |
| | * Action: See the information provided for XFR(300). |
| | |
------------------------------------------------------------------------------------
Table F-6. File Transfer XFR Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(302) | Error while resetting port |
| | |
| | * Action: See the information provided for XFR(300). |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(303) | Timeout (Host transfer program not responding) |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6 and #4, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(304) | Timeout (Receiver tried to send ABORT but did not complete) |
| | |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6 and #4, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(305) | Timeout (Sender sent EOD but did not complete protocol) |
| | |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6 and #4, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(306) | Timeout (Sender did not respond to Receivers Abort turn char) |
| | |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6 and #4, in that order. |
| | [REV BEG] |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(307) | Error while opening $STDIN |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #4. |
| | [REV END] |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(308) | Error while opening $STLIST |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #4. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(309) | Incorrect revision level of program |
| | |
| | * Meaning: The file transfer mechanism is outdated. |
| | |
| | * Action: |
| | |
| | * Restore the latest version of PSUXFRDP.PRED.SYS (the |
| | file transfer mechanism) from a backup or the |
| | installation tape. |
| | |
| | * Initiate a transfer normal file transfer. |
| | |
| | * If problems persist, or you are unable to restore |
| | PSUXFRDP, contact the HP Response Center. |
| | [REV BEG] |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(310) | Error opening write file |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #7. |
| | [REV END] |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(311) | Error opening read file |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #7. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(313) | Error writing to write file |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #7 |
| | |
------------------------------------------------------------------------------------
Table F-6. File Transfer XFR Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(314) | Error writing user label |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #7. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(315) | Error closing file |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #7. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(316) | Error reading from read file |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #7. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(317) | Error reading user label |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #7. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(318) | Error closing read file |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #7. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(319) | Error closing write file |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #7. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(320) | Noisy line (Sender did not receive acknowledgment to packet sent) |
| | |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6 and #4, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(321) | Too many timeouts (No acknowledgment to packet transmitted) |
| | |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6 and #4, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(322) | Read error (Sender could not read acknowledgment to packet sent) |
| | |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6 and #4, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(323) | Noisy line (Receiver has not been able to receive packet) |
| | |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6 and #4, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(324) | Read error (Receiver could not read packet) |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6 and #4, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(325) | Packet received contained incorrect block number |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(326) | Packet received contained an unexpected packet type |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6. |
| | |
------------------------------------------------------------------------------------
Table F-6. File Transfer XFR Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(327) | Error closing files after receiving an ABORT packet |
| | |
| | * Action: None. This is not a serious error. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(328) | The file already exists on receiving system |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #7. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(329) | Error closing file when file exists on receiving system |
| | |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #7. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(330) | Noisy line (too many bad packets have been received or sent) |
| | |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #6 and #4, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(331) | Unable to set time out on port |
| | |
| | * Action: See the information provided for XFR(300). |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(332) | File system error |
| | |
| | * Action: See "FSERR File Errors" later in this appendix. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(500) | Error sending logon string to the HP Response Center |
| | |
| | * Action: Contact the HP Response Center because this indicates |
| | a problem there. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(501) | Error establishing connection to the HP Response Center |
| | |
| | |
| | * Action: Attempt a DSLINE to the HP Response Center machine, |
| | then a remote. If the remote is unsuccessful, then the |
| | network connection is not set up properly, or the network |
| | could be down somewhere between the HP Predictive Support hub |
| | and the HP Response Center. Contact your network specialist. |
| | |
| | |
| | If the remote is unsuccessful, the dispatcher program at the |
| | HP Response Center may not be running. Contact the HP |
| | Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(502) | Network error while sending data to the HP Response Center |
| | |
| | |
| | * Action: You will get an accompanying NS error. Refer to your |
| | NS 3000 MPE/iX Network Services manual for the correct action. |
| | |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(503) | Network error while receiving RUN/BYE command |
| | |
| | * Action: Same as XFR (502). |
| | |
------------------------------------------------------------------------------------
| | |
| XFR(504) | Network error while receiving data from HP Response Center |
| | |
| | |
| | * Action: Same as XFR(502). |
| | |
------------------------------------------------------------------------------------
FSERR Messages
The following are FSERR messages that occur when an error is encountered
during the file transfer process. Each is identified as a File error or
a Port error.
Table F-7. File Transfer FSERR Messages
---------------------------------------------------------------------------------------
| | | |
| Error | File | Message/Meaning/Action |
| Number | or | |
| | Port? | |
| | | |
---------------------------------------------------------------------------------------
| | | |
| FSERR 2 | File | Illegal Capability |
| | | |
| | | * Meaning: HP Predictive Support cannot run because of |
| | | missing capabilities. |
| | | |
| | | * Action: |
| | | |
| | | * Verify the capabilities of PRED.SYS, by typing |
| | | LISTGROUP PRED.SYS at MPE. The required |
| | | capabilities are: |
| | | |
| | | IA, BA, PH, DS, PM, MR |
| | | |
| | | * Add any missing capabilities through ALTGROUP. |
| | | |
---------------------------------------------------------------------------------------
| | | |
| FSERR 24 | Port | UNIT NOT READY |
| | | * Meaning: The phone line may have disconnected during |
| | | the transfer. |
| | | * Action: Repeat the transfer attempt. If the error |
| | | recurs, check the datacomm port configuration (Appendix |
| | | D) and the modem switch settings (Appendix C). If |
| | | problems persist, contact the HP Response Center. |
| | | |
---------------------------------------------------------------------------------------
| | | |
| FSERR 32 | Port | SOFTWARE ABORT |
| | | |
| | | * Meaning: The port may be misconfigured, or the system |
| | | may have lost communication with the DTC, especially if |
| | | the DTC is PC-based. |
| | | |
| | | * Action: Recheck the port configuration in NMMGR, and if |
| | | appropriate, in OPENVIEW. The system or the DTC may need |
| | | to be restarted. |
| | | |
---------------------------------------------------------------------------------------
| | | |
| FSERR 42 | Port | OPERATION INCONSISTENT WITH DEVICE TYPE |
| | | * Meaning: Same as for FSERR 24. |
| | | * Action: Same as for FSERR 24. |
| | | |
---------------------------------------------------------------------------------------
| | | |
| FSERR 46 | File | Out of disc space |
| | | * Meaning: There is not enough system space to perform |
| | | this HP Predictive Support function.[REV BEG] |
| | | * Action: Contact the system manager to have some space |
| | | in system volumes released.[REV END] If problems |
| | | persist, contact the HP Response Center. |
| | | |
---------------------------------------------------------------------------------------
| | | |
| FSERR 52 | File | Nonexistent permanent file. |
| | | * Meaning: An HP Predictive Support function could not |
| | | find a file that it expected to find. |
| | | * Action: Repeat transfer attempt. If the error recurs, |
| | | contact the HP Response Center. |
| | | |
---------------------------------------------------------------------------------------
Table F-7. File Transfer FSERR Messages (cont.)
---------------------------------------------------------------------------------------
| | | |
| Error | File | Message/Meaning/Action |
| Number | or | |
| | Port? | |
| | | |
---------------------------------------------------------------------------------------
| | | |
| FSERR 56 | Port | Invalid Device Specification |
| | | |
| | | * Meaning: The LDEV or device class for the modem port is |
| | | invalid. |
| | | |
| | | * Action: |
| | | * Check the modem LDEV number in psconfig. |
| | | * Perform a showdev on the Port (that is, showdev |
| | | nnn, where nnn is the port LDEV, or showdev |
| | | xxxxxxxx, where xxxxxxxx is the modem device |
| | | class). |
| | | * If showdev shows AVAIL or UNAVAIL, the |
| | | LDEV/device class is valid. |
| | | |
| | | * Repeat transfer. |
| | | [REV BEG] |
| | | * If showdev results in either of the |
| | | following errors, the LDEV/device class is |
| | | invalid: |
| | | CIERR 1581 or CIERR 1583 |
| | | * Options: |
| | | * Use psconfig to change LDEV or device |
| | | class to a valid LDEV; attach modem to |
| | | that port. |
| | | * With the system manager, review NMMGR and, |
| | | if appropriate, OPENVIEW. Remember to |
| | | validate any change in NMMGR and |
| | | cross-validate in SYSGEN. The system and |
| | | DTC may need to be restarted. |
| | | * Attempt another file transfer. |
| | | * If errors persist, contact the HP Response |
| | | Center.[REV END] |
| | | |
---------------------------------------------------------------------------------------
| | | |
| FSERR 64 | File | MR capability required. |
| | | |
| | | * Meaning: This is a missing capabilities message. |
| | | |
| | | * Action: |
| | | * Ensure that capabilities for PRED.SYS are: IA, |
| | | BA, PS, DS, PM, MR.[REV BEG] |
| | | * Add capabilities using ALTGROUP. |
| | | * Repeat transfer attempt. |
| | | |
| | | If problems persist, contact the HP Response Center. |
| | | |
---------------------------------------------------------------------------------------
| | | |
| FSERR 68 | Port | Insufficient system resources |
| | | |
| | | * Meaning: Unable to open the modem port. This error |
| | | occurs if the modem signals DSR/CD are not high on a |
| | | modem port. |
| | | |
| | | * Action: Go to Appendix E, "Datacomm Troubleshooting |
| | | Guide," Procedure #1, particularly regarding the port |
| | | configuration and modem option setting information. |
| | | Check the modem LDEV in psconfig and the modem |
| | | cabling.[REV END] |
| | | |
---------------------------------------------------------------------------------------
| | | |
| FSERR 90 | File | EXCLUSIVE VIOLATION: FILE BEING ACCESSED |
| | | |
| | | * Meaning: The file that HP Predictive Support is |
| | | attempting to transfer is open or locked by another |
| | | process. |
| | | |
| | | * Action: Repeat the transfer attempt. If the error |
| | | recurs, make sure that no other user or process is |
| | | reading from or writing to the file. Also, make sure a |
| | | store is not in progress. |
| | | |
| | | If the error persists, contact the HP Response Center. |
| | | |
---------------------------------------------------------------------------------------
File Access Errors
These errors can occur in any program. They generally take either of the
following forms:
error : <type of error> source is : <source>
source error is : <source error>
<file name>
OR
error : <type of error> source is : <source>
HPFOPEN error : <error #> HPFOPEN subsys: <subsys #>
<file name>
For example,
error : FILE_BEING_ACCESSED source is : HPFOPEN_INTR
HPFOPEN error : -456 HPFOPEN subsys: 143
PSASFILE.PRED.SYS
This is an HPFOPEN error -456, which indicates an exclusive access
violation.
In general, the <type of error> will be sufficient to determine what
action to take. The possible values are:
Type of Error Possible Action
FILE_ALREADY_OPEN Internal program error. If error persists,
contact the HP Response Center.
SECURITY_VIOLATION If psconfig, check user, group and account
capabilities. Otherwise, contact the HP
Response Center.
NONEXISTENT_FILE File does not exist. Restore from tape.
FILE_BEING_ACCESSED PSRNLOGD and PSASFILE cannot be opened for
writing while they are open for reading. Close
these files while HP Predictive Support
attempts to access them. For other files,
ensure they are not accessed exclusively, for
example, by FCOPY.
INVALID_FILE_NAME Internal program error. If error persists,
contact the HP Response Center.
HPFOPEN_ERROR See HPFOPEN error for cause.
FCHECK_ERROR See file system error for cause.
PRINTOP_FAILED Internal program error. If error persists,
contact the HP Response Center.
EOF_FOUND File is full. If this occurs on PSDCFILE, it
should be transferred to the HP Response Center
using transfer normal.
NOT_CIRCULAR_FILE If this occurs on PSRNLOGD, PSASFILE, or
PSUILOGD, do a listf,2 on the file. If it is
not of TYP FAO (fixed ASCII circular), purge
it. It will be rebuilt. If this occurs on any
other file, contact the HP Response Center.
FFILEINFO_FAILED If this error recurs, contact the HP Response
Center.
INCORRECT_RECORD_SIZE If this error recurs, purge the file; it should
be rebuilt. If this error persists, contact
the HP Response Center.
Sometimes, the source error may be useful in fixing the problem. Here is
a list of possible sources.
Source Errors Documented
HPFOPEN MPE/iX Intrinsics Reference Manual, HPFOPEN
Intrinsic.
FWRITE, FREAD, Any listing of MPE file system errors, for example,
FREADDIR, FPOINT, MPE/iX Intrinsics. FCHECK intrinsic; see this
FCLOSE appendix for some common file system errors (FSERR
File Errors and What To Do).
FCLOSE_NM Same as FCLOSE.
internal_err Source error # should be 0.