HP 3000 Manuals HP 3000 Manuals
File Transfer Errors
File transfer errors are presented in the following order:
1. CTL errors
2. RTY errors
3. TRANSFER errors
4. XFR errors
5. FSERR errors (that may occur during the file transfer process)
6. DATACOMM errors
CTL Errors
Table F-3. File Transfer CTL Errors
------------------------------------------------------------------------------------
| | |
| Error | Message/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(7) | Terminating transfer attempt |
| | |
| | * Action: None. Informational message only |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(8) | Remote modem busy/failed to answer/no carrier |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #2, #3, and #1, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(9) | Operator has failed to dial modem |
| | |
| | * Action: None. Informational message only |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(10) | Logon string failed |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #3. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(14) | FCLOSE failure on LDEV! |
| | |
| | * Action: None. This is an informational message only. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(15) | Failed to receive expected response from modem |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #2, #1, and #4 (in that order). |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(16) | LDEV ! is not configured as a modem port |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #1. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(17) | Cannot FOPEN port on LDEV ## (FSERR ##) |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #1. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(18) | Modem detected a voice. Phone number = ####### |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #2. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(19) | No dial tone detected by modem on LDEV ! |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #2. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(20) | Maximum allotted time to logon exceeded |
| | |
| | * Action: None. Informational message only |
| | |
------------------------------------------------------------------------------------
Table F-3. File Transfer CTL Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(21) | Remote modem failed to send carrier |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #2 and #3, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(22) | Maximum attempts to logon exceeded |
| | |
| | * Action: None. Informational message only |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(23) | Speed sensing failed on remote system |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #3. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(24) | Modem failed to go ON LINE after receiving carrier |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #2, #3, and #4 (in that order). |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(25) | Remote modem failed to answer |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #2 and #3, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(28) | Phone number ####### is busy |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #2 and #3, in that order. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(29) | Invalid command line sent to modem |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #2. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(53) | Unable to set up modem to proper state |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #1. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(55) | File System Error on from file `!' |
| | |
| | * Action: See "FSERR File Messages" later in this appendix. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(56) | File System Error on to file `!' |
| | |
| | * Action: See "FSERR File Messages" later in this appendix. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(57) | Program Error occurred on Remote System |
| | |
| | * Action: Use the messages that accompany this message to |
| | resolve the condition. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(72) | No modem detected on the LDEV specified |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #1. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(73) | Error dialing on modem. Phone number = ! |
| | |
| | |
| | * Action: Go to Appendix E, "Datacomm Troubleshooting Guide," |
| | Procedure #2, #3, and #1 (in that order). |
| | |
------------------------------------------------------------------------------------
Table F-3. File Transfer CTL Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(90) | XFERDIAL: ERROR at proc: xxx location: 1 status: ! |
| | |
| | |
| | * Meaning: This is an error message indicating an error within |
| | Sherlock. The specific type of error depends on the proc: |
| | (procedure) number displayed in the message when it occurs. |
| | |
| | |
| | * If proc: 200, then Sherlock initialization failed. |
| | |
| | * If proc: 210, then a Sherlock error occurred while |
| | retrieving the Predictive Monitor (PSMON) port number. |
| | |
| | |
| | * If proc: 220, then a Sherlock error occurred while |
| | receiving commands from the Retry Monitor, PSUXFDMP. |
| | |
| | * If proc: 230, then a Sherlock error occurred receiving |
| | options from the Retry Monitor, PSUXFDMP. |
| | |
| | * If proc: 240, then a Sherlock error occurred while |
| | sending a final status to the Retry Monitor, PSUXFDMP. |
| | |
| | * Action: If subsequent runs are successful, ignore this error. |
| | If it continues, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(91) | Unable to open Action Summary log PSASFILE.PRED.SYS |
| | * Meaning: The Action Summary log could not be opened. |
| | * Action: Go to PSRNLOGD and examine the messages that follow |
| | this message. (Refer to "File Access Error" at the end of |
| | this appendix for error descriptions.) |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(97) | Timeout receiving commands from Retry Monitor. Unable to continue. |
| | |
| | * Meaning: A Sherlock error occurred while retrieving commands. |
| | |
| | * Action: If subsequent runs are successful, ignore this error. |
| | If it continues, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(120) | Error sending console start to PSMON. ipc_status = xxx |
| | |
| | * Meaning: This is an internal error. |
| | * Action: If the error persists, contact the HP Response |
| | Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(121) | Error sending console stop to PSMON. ipc_status=xxx |
| | * Meaning: This is an internal error. |
| | * Action: If the error persists, contact the HP Response |
| | Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(130) | Could not open run log : status = xxx |
| | |
| | * Meaning: Unable to open run log and print banner. (This |
| | message is only printed to the console.) |
| | |
| | * Action: Ensure no users are reading from PSRNLOGD.PRED.SYS. |
| | |
| | Do a LISTF,2 on PSRNLOGD.PRED.SYS and ensure that TYP is FAO |
| | and SIZE is 80B; if not, purge PSRNLOGD and Predictive will |
| | rebuild it correctly. |
| | |
| | Repeat transfer attempt. |
| | |
| | If the error persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
Table F-3. File Transfer CTL Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(131) | Open failed on catalog file PSUXFRDM.PRED.SYS |
| | |
| | * Meaning: The program could not open the message catalog. |
| | |
| | * Action: If the error persists, restore the message catalog |
| | from a backup or the installation tape. If this does not |
| | solve the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(132) | Could not access catalog file PSUXFRDM.PRED.SYS |
| | |
| | * Meaning: The program could not open the message catalog. |
| | |
| | * Action: If the error persists, restore the message catalog |
| | from a backup or the installation tape. If this does not |
| | solve the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(133) | PSUXFRDM.PRED.SYS is not a GENCAT formatted catalog. |
| | |
| | |
| | * Meaning: PSUXFRDM.PRED.SYS is not a valid catalog file. |
| | |
| | * Action: Restore the message catalog from a backup or |
| | installation tape. If this does not solve the problem, |
| | contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(134) | Internal CATOPEN error on PSUXFRDM.PRED.SYS |
| | |
| | * Meaning: The program could not open the message catalog. |
| | |
| | * Action: If the error persists, restore the message catalog |
| | from a backup or the installation tape. If this does not |
| | solve the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(135) | Fatal error opening message catalog. |
| | |
| | * Meaning: The program could not open the message catalog. |
| | |
| | * Action: If the error persists, restore the message catalog |
| | from a backup or installation tape. If this does not solve |
| | the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(140) | CATREAD Error : invalid catindex. |
| | |
| | * Meaning: An error occurred while retrieving a message from |
| | message catalog. |
| | |
| | * Action: If the error persists, restore message catalog and |
| | PSUXFRDP from a backup or the installation tape. If this does |
| | not solve the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(141) | Read failed on catalog file. |
| | |
| | * Meaning: An error occurred while retrieving a message from |
| | the message catalog. |
| | |
| | * Action: If the error persists, restore the message catalog |
| | from a backup or installation tape. If this does not solve |
| | the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(142) | Message set xxx not found. |
| | |
| | * Meaning: An error occurred while retrieving a message from |
| | the message catalog. |
| | |
| | * Action: If the error persists, restore the message catalog |
| | from a backup or installation tape. If this does not solve |
| | the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
Table F-3. File Transfer CTL Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(143) | Missing Msg: Set = xxx Num = yyy |
| | |
| | * Meaning: An error occurred while retrieving a message from |
| | the message catalog. |
| | |
| | * Action: If the error persists, restore the message catalog |
| | from a backup or installation tape. If this does not solve |
| | the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(144) | CATREAD Error : User buffer overflow. |
| | |
| | * Meaning: An error occurred while retrieving a message from |
| | the message catalog. |
| | |
| | * Action: If the error persists, restore message catalog and |
| | PSUXFRDP from a backup or the installation tape. If this does |
| | not solve the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(145) | Invalid msg set: xxx |
| | |
| | * Meaning: An error occurred while retrieving a message from |
| | the message catalog. |
| | |
| | * Action: If the error persists, restore the message catalog |
| | and PSUXFRDP from a backup or the installation tape. If this |
| | does not solve the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(146) | Invalid msg num : xxx |
| | |
| | * Meaning: An error occurred while retrieving a message from |
| | the message catalog. |
| | |
| | * Action: If the error persists, restore message catalog and |
| | PSUXFRDP from a backup or the installation tape. If this does |
| | not solve the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(147) | CATREAD Error : invalid buffer size : xxx |
| | |
| | * Meaning: An error occurred while retrieving a message from |
| | the message catalog. |
| | |
| | * Action: If the error persists, restore message catalog and |
| | PSUXFRDP from a backup or the installation tape. If this does |
| | not solve the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(148) | Internal CATREAD error. |
| | |
| | * Meaning: An error occurred while retrieving a message from |
| | the message catalog. |
| | |
| | * Action: If the error persists, restore message catalog and |
| | PSUXFRDP from a backup or the installation tape. If this does |
| | not solve the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| CTL(149) | Unrecognized status on CATREAD : xxx |
| | |
| | * Meaning: An error occurred while retrieving a message from |
| | the message catalog. |
| | |
| | * Action: If the error persists, restore the message catalog |
| | from a backup or the installation tape. If this does not |
| | solve the problem, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
[REV BEG]
DATACOMM Errors
Table F-4. File Transfer DATACOMM Errors
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| DATACOMM(100) | Failure to download code word. Will try again later. |
| | |
| | |
| | * Meaning: A transfer attempt to download a new code |
| | word was unsuccessful. |
| | |
| | * Action: HP Predictive Support will automatically |
| | attempt to retrieve a code word on a subsequent run |
| | unless the psconfig Configure Code Word screen shows |
| | a status: Expired or Disabled. In that case, |
| | perform a transfer request. In a case where you |
| | have received a code word manually from the HP |
| | Response Center and you have disabled your datacomm, |
| | and you still get the error message, purge the file |
| | pscodered.pred.sys. |
| | |
------------------------------------------------------------------------------------
| | |
| DATACOMM(200) | HP Response Center database unavailable. Downloads may |
| | have been missed. |
| | |
| | * Meaning: HP Predictive Support transfer connected |
| | to the HP Response Center at a time when downloads |
| | were not available. This does not necessarily mean |
| | that any code word or ruleset downloads were |
| | scheduled, but if any were scheduled, they were |
| | missed on this connection. |
| | |
| | * Action: If transfers are infrequent on this system, |
| | perform a transfer force in psconfig to receive any |
| | pending downloads. |
| | |
| | If this message occurs more than once, change the |
| | nightly schedule for Predictive to one or two hours |
| | earlier or later, so that transfers will occur at a |
| | time when any pending downloads can be received. |
| | |
------------------------------------------------------------------------------------
[REV END]
RTY Errors
Table F-5. File Transfer RTY Errors
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(90) | RETRYMON: ERROR at proc: xxx loc: yyy stat: zzzz |
| | |
| | * Meaning: This is an internal error. |
| | |
| | * Action: If the error persists, contact the HP Response |
| | Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(91) | RETRYMON: ERROR at proc: xxx loc: yyy file:zzz stat=aaa |
| | |
| | |
| | * Meaning: This is an internal error. |
| | |
| | * Action: If the error persists, contact the HP Response |
| | Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(92) | Error retrieving hardware ID status: ! Will use 0 |
| | |
| | * Meaning: This is a warning message, only, indicating that an |
| | error occurred while retrieving the hardware ID for the |
| | machine. |
| | |
| | * Action: None. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(93) | Error retrieving baud rate: xxxx Will use default: 0. |
| | |
| | |
| | * Meaning: This is a warning message. The value for the modem |
| | baud rate found in the OPSDB is not valid. The default value, |
| | 0, will be used. (0 is the same as Autoselect.) |
| | |
| | * Action: Run psconfig. Go to the "Configure Transfer |
| | Information" Menu and enter a valid value for the baud rate. |
| | If the error persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(94) | Error retrieving max retries: ! Will use default: 5 |
| | |
| | * Meaning: This is a warning message. The value for the |
| | maximum number of retries found in the OPSDB is not valid. |
| | The default value, 5, will be used. |
| | |
| | * Action: Run psconfig. Go to the "Configure Transfer |
| | Information" Menu and enter a valid value for the number of |
| | retries. If the error persists, contact the HP Response |
| | Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(95) | Error retrieving retry wait: ! Will use default: 5 |
| | |
| | * Meaning: This is a warning message. The retry wait found in |
| | the OPSDB is not valid. The default value of 5 minutes will |
| | be used. |
| | |
| | * Action: Run psconfig. Go to the "Configure Transfer |
| | Information" Menu and set the Retry Wait to a valid value. If |
| | the error persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(96) | Invalid options mask from PSMON: xxx. Will use defaults. |
| | |
| | |
| | * Meaning: This is a warning message. Invalid options were |
| | received from the Predictive Monitor (PSMON). There may be |
| | incompatible versions of PSMON.PRED.SYS and PSUXFDMP.PRED.SYS. |
| | The following defaults will be used: no test, no code word |
| | connect, transfer PSDCFILE. |
| | |
| | * Action: If the error continues, restore PSUXFDMP from the |
| | last Predictive installation tape. (PSMON cannot be restored |
| | from tape because it is always active.) If the error |
| | persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
Table F-5. File Transfer RTY Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(97) | Timeout receiving options from PSMON. Will use defaults. |
| | |
| | |
| | * Meaning: This is a warning message indicating that a Sherlock |
| | error occurred while retrieving options from the Predictive |
| | Monitor. The following defaults will be used: no test, no |
| | code word connect, transfer PSDCFILE. |
| | |
| | * Action: If the error persists, contact the HP Response |
| | Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(98) | Error retrieving trace level: xxx Will use default. |
| | |
| | |
| | * Meaning: This is a warning message indicating that the value |
| | for the trace level retrieved from the OPSDB is not valid. |
| | The default production trace level will be used. |
| | |
| | * Action: Inform the customer that the trace level should be |
| | reset. (The default level is "1.") |
| | |
| | To change the trace level, do the following at MPE: |
| | |
| | :hello manager.sys,pred |
| | :query |
| | >b=opsdb |
| | {password = ';' mode=1} |
| | >f m-module-field.module-field-key="DATACOMM TRACELEVEL" |
| | |
| | If |
| | |
| | 1 ENTRIES QUALIFIED |
| | |
| | then |
| | |
| | >replace,field-value-buf=``n'';end (where ``n'' is 5) |
| | |
| | However, if |
| | |
| | 0 ENTRIES QUALIFIED |
| | |
| | then |
| | |
| | >add m-module-field |
| | MODULE-FIELD-KEY=>>DATACOMM TRACELEVEL |
| | FIELD-VALUE-BUF=>>``n'' (where ``n'' is 5) |
| | MODULE-FIELD-KEY=>>// |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(99) | Unrecognized msg received at proc: xxx loc: x queue: xxx msg: yyy |
| | |
| | |
| | * Meaning: This is a warning message indicating that an |
| | unrecognized message was received during specific activity |
| | phases of one of the two file transfer programs. The specific |
| | point during which the unrecognized message was received is |
| | indicated by the "proc:" (procedure) number: |
| | |
| | |
| | * If proc: 144, then the unrecognized message was |
| | received during the retry wait (the retry wait period |
| | may have been shorter than expected). |
| | |
| | * If proc: 146, then the unrecognized message occurred |
| | while waiting for PSUXFRDP to terminate. PSUXFDMP will |
| | continue to wait for PSUXFRDP to terminate. |
| | |
------------------------------------------------------------------------------------
Table F-5. File Transfer RTY Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(99) | Continued. |
| | |
| | * Meaning: |
| | |
| | * If proc: 220, then the unexpected message was received |
| | while retrieving commands from PSUXFDMP. |
| | |
| | * If proc: 230, then the unexpected message was received |
| | while retrieving options from PSUXFDMP. |
| | |
| | * Action: If any of these messages persists, contact the HP |
| | Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(100) | RC phone number not configured |
| | |
| | * Meaning: The RC phone number, as stored in the OPSDB, is |
| | blank. |
| | |
| | * Action: Run psconfig (you will be placed in required fields |
| | mode). Provide a value for the RC phone number when prompted. |
| | |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(101) | Modem LDEV not configured |
| | |
| | * Meaning: The modem LDEV, as stored in the OPSDB, is blank. |
| | |
| | * Action: Run psconfig (you will be placed in required fields |
| | mode). Provide a value for the modem LDEV when prompted. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(102) | System serial number not configured |
| | |
| | * Meaning: The system serial number, as stored in the OPSDB, is |
| | blank. |
| | |
| | * Action: Run psconfig (you will be placed in required fields |
| | mode). Provide a value for the system serial number when |
| | prompted. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(103) | System model number not configured |
| | |
| | * Meaning: The system model number, as stored in the OPSDB, is |
| | blank. |
| | |
| | * Action: Run psconfig (you will be placed in required fields |
| | mode). Provide a value for the system model number when |
| | prompted. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(104) | HP Response Center database unavailable. |
| | |
| | |
| | * Meaning: This message is printed when a code word connection |
| | fails because the HP Response Center database is unavailable. |
| | |
| | |
| | * Action: If a code word is needed, try a code word request |
| | (that is, a TRANSFER REQUEST in psconfig) again at a later |
| | time. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(105) | Unable to open database : [IMAGE] status = xxx |
| | |
| | * Meaning: OPSDB.PRED.SYS could not be opened. |
| | |
| | * Action: The specific action depends on whether or not an |
| | IMAGE condition word from the database open is in the message. |
| | |
| | |
| | * If IMAGE status = xxx, use the IMAGE condition word to |
| | resolve the condition. |
| | |
| | * If status = xxx (that is, no IMAGE condition word), an |
| | internal error has occurred. Contact the HP Response |
| | Center. |
| | |
------------------------------------------------------------------------------------
Table F-5. File Transfer RTY Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(106) | Unable to close message catalog : status = ! |
| | |
| | |
| | * Meaning: The message catalog could not be closed. |
| | |
| | * Action: |
| | |
| | * If the status reads, FILE NOT OPENED, ignore the error. |
| | |
| | |
| | * If the status persistently reads any other condition, |
| | contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(107) | Insufficient system resources to launch PSUXFRDP.PRED.SYS |
| | |
| | |
| | * Meaning: There is not enough system resources to run |
| | PSUXFRDP. |
| | |
| | * Action: Try again when the system is less busy. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(108) | Program PSUXFRDP.PRED.SYS does not exist |
| | |
| | * Meaning: The program, PSUXFRDP.PRED.SYS, does not exist. |
| | |
| | * Action: Restore PSUXFRDP.PRED.SYS from a backup or the |
| | installation tape. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(109) | Unable to load and run program PSUXFRDP.PRED.SYS |
| | |
| | * Meaning: Unable to load and run PSUXFRDP.PRED.SYS. |
| | |
| | * Action: If the error persists, restore PSUXFRDP from a backup |
| | tape or the installation tape. If the error continues to |
| | persist, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(110) | Unable to load and run program PSUXFRDP.PRED.SYS : status = xxx |
| | |
| | |
| | * Meaning: Unable to load and run PSUXFRDP.PRED.SYS. |
| | |
| | * Action: If the error persists, restore PSUXFRDP from a backup |
| | tape or the installation tape. If the error continues to |
| | persist, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(111) | Unable to retrieve datacomm configuration from OPSDB : [IMAGE] status |
| | = xxx |
| | |
| | * Meaning: Unable to retrieve datacomm configuration from |
| | OPSDB. |
| | |
| | * Action: Run psconfig. Go to the "Configure Transfer |
| | Information" Menu and provide the missing values. |
| | |
| | If an IMAGE condition word is in the message (that is, IMAGE |
| | status = xxx), use the condition word to resolve the error. |
| | |
| | If the error persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(112) | Unable to retrieve customer configuration from OPSDB : [IMAGE] status |
| | = xxx |
| | |
| | * Meaning: Unable to retrieve customer information from OPSDB. |
| | |
| | * Action: Run psconfig. Go to the "Configure Customer |
| | Information" Menu and provide the missing values. |
| | |
| | If an IMAGE condition word is in the message (that is, IMAGE |
| | status = xxx), use the condition word to resolve the error. |
| | |
| | If the error persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
Table F-5. File Transfer RTY Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(113) | Unable to retrieve download configuration from OPSDB : [IMAGE] status |
| | = xxx |
| | |
| | * Meaning: Unable to retrieve utilities configuration from |
| | OPSDB to determine whether or not downloads are enabled. |
| | |
| | * Action: Run psconfig. Go to the appropriate "Configure |
| | Utilities" Menu and provide the missing value. |
| | |
| | If an IMAGE condition word is in the message (that is, IMAGE |
| | status = xxx), use the condition word to resolve the error. |
| | |
| | If the error persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(114) | Database error retrieving trace level : [IMAGE] status = xxx |
| | |
| | |
| | * Meaning: An error occurred while retrieving the datacomm |
| | trace level from the database. |
| | |
| | * Action: Unless the customer wants the trace level set at |
| | other than the default, ignore this warning. |
| | |
| | If an IMAGE condition word is in the message (that is, IMAGE |
| | status = xxx), use the condition word to resolve the error. |
| | |
| | If the error persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(115) | Error closing database: [IMAGE] status = xxx |
| | |
| | * Meaning: Unable to close the database. |
| | |
| | * Action: If an IMAGE condition word is in the message (that |
| | it, IMAGE status = xxx), use the condition word to resolve the |
| | error. |
| | |
| | If the error persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(117) | Unable to update transfer status in database : [IMAGE] status = xxx |
| | |
| | |
| | * Meaning: An error occurred while updating the OPSDB with the |
| | status of the last download. This status value causes |
| | Predictive to connect to RC Predictive at the end of a run if |
| | the last connection resulted in a download error. |
| | |
| | * Action: If an IMAGE condition word is in the message (that |
| | is, IMAGE status = xxx), use the condition word to resolve the |
| | error. |
| | |
| | If the error persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(120) | WARNING : Error locking database module fields : [IMAGE] status = xxx |
| | |
| | |
| | * Meaning: An error occurred while locking the M-MODULE-FIELDS |
| | set of the OPSDB, while trying to update status of last |
| | download. |
| | |
| | * Action: If an IMAGE condition word is in the message (that |
| | is, IMAGE status = xxx), use the condition word to resolve the |
| | error. |
| | |
| | If the error persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
Table F-5. File Transfer RTY Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(121) | WARNING : Error unlocking database : [IMAGE] status = xxx |
| | |
| | |
| | * Meaning: An error occurred unlocking the OPSDB. |
| | |
| | * Action: Ignore this warning unless followed by other database |
| | errors. |
| | |
| | If an IMAGE condition word is in the message (that is, IMAGE |
| | status = xxx), use the condition word to resolve the error. |
| | |
| | If the error persists, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(122) | Dropping back speed to 1200 for modem <modem type> |
| | |
| | * Meaning: A 2400 baud modem - HP 37212B or HP 50759A - was |
| | dialed at 2400 baud, but had a speed sensing or timeout |
| | failure, perhaps from a noisy phone line. After the retry |
| | wait, it will be dialed at 1200 baud to decrease the effects |
| | of noise on the line. |
| | |
| | * Action: None. Informational message only. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(123) | Attempt tone dialing on <modem type> modem, phone xxx |
| | |
| | * Meaning: A dialing error occurred on an HP 37212A or HP |
| | 37212B modem, and the phone number was prefaced with neither a |
| | T (tone dialing) nor a P (pulse dialing). After the retry |
| | wait, it will be dialed using tone dialing. |
| | |
| | * Action: None. Informational message only. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(130) | Error printing banner to run log |
| | |
| | * Meaning: An error occurred while trying to print the banner |
| | to the run log. This error accompanies errors RTY(131) |
| | through RTY(134). |
| | |
| | * Action: See the action specified for the error message that |
| | appears with this message. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(131) | PSRNLOGD.PRED.SYS being read. |
| | |
| | * Meaning: This message appears with message RTY(130). The |
| | program was unable to open the run log and print the banner |
| | because another process was reading from the run log. Because |
| | PSRNLOGD.PRED.SYS is an MPE circular file, it cannot be opened |
| | for writing while it is open for reading. (This message is |
| | only printed to the console.) |
| | |
| | * Action: Determine which process is reading from |
| | PSRNLOGD.PRED.SYS. This may be a user printing the Trace |
| | Report from psconfig, or simply using the MPE PRINT command on |
| | PSRNLOGD.PRED.SYS. Close the file and attempt the transfer |
| | again. |
| | |
------------------------------------------------------------------------------------
Table F-5. File Transfer RTY Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(132) | PSRNLOGD.PRED.SYS not a circular file. |
| | |
| | |
| | * Meaning: This message accompanies message RTY(130) and |
| | indicates that PSRNLOGD.PRED.SYS is not an MPE circular file. |
| | (This message is only printed to the console.) |
| | |
| | * Action: To verify this, do a LISTF PSRNLOGD.PRED.SYS,2. The |
| | file type (TYP) should be FAO - fixed ASCII circular. If it |
| | is not, it was not built by HP Predictive Support. Purge it. |
| | HP Predictive Support will rebuild it automatically the next |
| | time it attempts to open it. |
| | |
| | If the user or CE wishes to build the run log rather than let |
| | HP Predictive Support build it - for example, to make it |
| | larger or smaller - it must be built as a circular file using |
| | the ;CIR option on the build command. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY | PSRNLOGD.PRED.SYS record size incorrect. |
| (133) | |
| | |
| | * Meaning: This message appears with message RTY(130), |
| | indicating that PSRNLOGD.PRED.SYS is built with an incorrect |
| | record size. |
| | |
| | * Action: Purge PSRNLOGD.PRED.SYS. HP Predictive Support will |
| | rebuild it automatically the next time it attempts to open it. |
| | |
| | |
| | If you wish to build the run log rather than let HP Predictive |
| | Support build it (for example, to make it larger or smaller), |
| | you must build it using the same record size that HP |
| | Predictive Support uses. Use the following command: |
| | BUILD PSRNLOG.PRED.SYS;REC=-80,100,F,ASCII;DISC=n;CDIR |
| | The number of records = n. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(134) | Status = xxx |
| | |
| | * Meaning: This message accompanies message RTY(130), |
| | indicating that the program was unable to the open run log and |
| | print the banner. |
| | |
| | * Action: Purge PSRNLOGD.PRED.SYS. Predictive will rebuild it |
| | automatically the next time it attempts to open it. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(135) | Error opening message catalog PSUXFRDM.PRED.SYS : ! |
| | |
| | |
| | * Meaning: An error occurred while opening PSUXFRDM.PRED.SYS. |
| | |
| | * Action: If the status condition is: |
| | |
| | |
| | * file being accessed. PSUXFRDM.PRED.SYS is being |
| | accessed, probably exclusively. Release other access |
| | to PSUXFRDM.PRED.SYS. |
| | |
| | * nonexistent file. PSUXFRDM.PRED.SYS does not exist. |
| | Restore the message catalog from a backup or the |
| | installation tape. |
| | |
| | * not a GENCAT catalog. PSUXFRDM.PRED.SYS is not a valid |
| | GENCAT message catalog. Restore the message catalog |
| | from a backup or the installation tape. |
| | |
| | * security violation. Security violation accessing |
| | PSUXFRDM.PRED.SYS. |
| | |
| | * status = <other>. PSUXFRDM.PRED.SYS could not be |
| | opened. Restore the message catalog from a backup or |
| | the installation tape. |
| | |
| | If the error persists, contact the HP Response Center. |
| | |
| | |
------------------------------------------------------------------------------------
Table F-5. File Transfer RTY Errors (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(136) | Message catalog read error. Set xxx Msg # yyy : status = zzz |
| | |
| | |
| | * Meaning: Message does not exist. The action to take depends |
| | on the status conditions. |
| | |
| | * Action: If the status condition is: |
| | |
| | |
| | * NONEXISTENT MESSAGE : Restore message catalog and |
| | PSUXFDMP from a backup or the installation tape. |
| | |
| | * INVALID SET NUM : Restore the message catalog and |
| | PSUXFDMP from a backup or the installation tape. |
| | |
| | * BAD FILE # : Ignore this message if preceded by |
| | message catalog open errors. |
| | |
| | * Other : Restore the message catalog and PSUXFDMP from |
| | a backup or the installation tape. |
| | |
| | If the error persists, contact the HP Response Center. |
| | |
| | |
------------------------------------------------------------------------------------
| | |
| RTY | Predictive Support datacomm hang |
| (144) | |
| | * Meaning: The remote console is enabled or the modem was in |
| | use when HP Predictive Support attempted to dial out. |
| | |
| | * Action: Disable the remote console if it was enabled. Verify |
| | that the port is available by performing a showdev command for |
| | the correct port. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(146) | Unable to kill PSUXFRDP process |
| | |
| | * Meaning: This message accompanies message RTY(147), and |
| | shares its explanation and action. |
| | |
------------------------------------------------------------------------------------
| | |
| RTY(147) | Perform ABORTIO on Device! |
| | |
| | * Meaning: PSUXFRDP hung because the remote console was |
| | enabled, or because the modem was in use when HP Predictive |
| | Support tried to dial out. |
| | |
| | * Action: Disable the remote console if it was enabled. If a |
| | dial in session is not currently active on the port, perform |
| | an abortio on it. |
| | |
| | If the error persists, contact the HP Response Center. |
| | |
| | * Meaning: A device class was specified for the LAN console |
| | port. |
| | |
| | * Action: Specify the LAN console port in psconfig, using the |
| | LDEV number. |
| | |
------------------------------------------------------------------------------------