HP 3000 Manuals HP 3000 Manuals
File Transmission Review
File transfers can occur in two directions:
* Customer system to the HP Response Center.
* HP Response Center to the customer system, after the customer
system establishes contact with the HP Response Center. The HP
Response Center system never initiates file transfer activity with
the customer system.
Most Common Causes of Problems
The most common causes of file transfer problems are:
* A modem that is improperly cabled to the system
* An incorrectly configured modem port
* An incorrect HP Response Center phone number in psconfig
* A heavily input/output (I/O) bound system
* Problems with the telephone line
* A network problem
Why File Transfers Are Initiated
File transfer connections originate from the customer system either
automatically by HP Predictive Support or through psconfig by the user:
* Automatically by HP Predictive Support:
* To transfer event information (in the PSDCFILE file) from a
current HP Predictive Support run or a previous run.
* To transmit a code word request (PSCODERD file), HP
Predictive Support then waits (for up to 5 minutes) for the
HP Response Center to download a code word update (PSCODEWD
file).
* To process downloads again because during its last file
transfer connection to the HP Response Center, downloads
could not be processed correctly. This would happen if the
RC Predictive database was unavailable, or RC Predictive
attempted to download files but one of the downloads
failed.
[REV BEG]
* By the user, through psconfig:
* To transmit a currently existing data file (transfer
normal).
* To connect to the HP Response Center to receive an awaiting
ruleset download (transfer force).
* To request a code word (transfer request).
* To perform a file transfer test (transfer test).[REV END]
__________________________________________________________
NOTE HP Response Center downloads are possible under all
of the above conditions except with file transfer
tests.
__________________________________________________________
File Transfer Programs
The file transfer process is carried out by two programs: PSUXFDMP and
PSUXFRDP.
* PSUXFDMP gets the modem LDEV number, the HP Response Center phone
number, and the system serial and model numbers from the Onsite
Predictive Support Database (OPSDB) and launches PSUXFRDP (see
below). OPSDB values are stored via psconfig.
PSUXFDMP is also called the "retry monitor" because it controls
the number of attempts and the timing between attempts to transfer
data in the event the initial attempt is unsuccessful. The number
of attempts and timing between attempts are based on the values
stored in the OPSDB, via psconfig.
* PSUXFRDP is the modem transfer program. It is responsible for
identifying the modem, dialing the modem, and transferring the
data file, PSDCFILE, to the HP Response Center. It is also
responsible for receiving ruleset and code word downloads from the
HP Response Center.
* PSUXFRNP is the network transfer program. It is responsible for
initiating the connection to the HP Response Center and
transferring the data file (PSDCFILE) to the HP Response Center.
It is also responsible for receiving ruleset and codeword
downloads from the HP Response Center.
After an event file (PSDCFILE) or a code word request file
(PSCODERD) is successfully transmitted, PSUXFRDP purges the file.
PSUXFRDP does not, however, purge the test file, PSDCTSTD.
NOTE Although PSUXFRDP purges the event file after successful
transmission, event information is still available through the
"Action Summary Report."
If file transmission is unsuccessful when the "maximum number of retries"
has been attempted, HP Predictive Support stops further attempts to
transfer for the current run. Any files that were not successfully
transmitted are transmitted with the next HP Predictive Support run or if
the user initiates file transfer activity through psconfig.
PSRNLOGD
Whenever a file transfer problem is encountered, HP Predictive Support
sends messages to the system console and to its run log, PSRNLOGD. Figure
E-1 illustrates and explains run log messages depicting a successful file
transfer as consisting of a series of stages, A through H. If a file
transfer attempt is unsuccessful, the run log shows an error message at
the point that the transfer terminated.
![[]](../../pic3k/M011844/FFN463c50.gif)
Figure E-1. Sample PSRNLOGD Messages: Successful File Transfer
NOTE The information in the run log is also available in the "Trace
Report." However, the "Trace Report" reflects this information in
reverse chronological order.
----------------------------------------------------------------------------------------
| | | |
| Step | Successful Activity | Probable Cause if Transfer |
| | At This Step | Fails At This Step |
| | | |
| A | PSUXFDMP successfully obtained the | Invalid/incorrect data in psconfig, |
| | modem LDEV, the HP Response Center | an internal error, or a file error. |
| | phone number, and the system's | (Go to the "File Transfer Errors" |
| | serial and model numbers stored by | section in Appendix F.) |
| | psconfig. | |
| | | |
- - - -
| B | PSUXFDMP has successfully launched | An internal error or a file error. |
| | PSUXFRDP. | (Go to the "File Transfer Errors" |
| | | section in Appendix F.) |
| | | |
- - - -
| C | PSUXFRDP, the file transfer program, | Failure to open the port, or the |
| | identified the modem. | modem did not respond. (Go to |
| | | Datacomm Troubleshooting Procedure |
| | | No. 1 in this appendix; also, see |
| | | "FSERR Messages" in Appendix F if an |
| | | FSERR appears in the message.) |
| | | |
- - - -
| D | Predictive dialed the number stored | Problem with dialing phone number. |
| | by psconfig and connection to the | (See Datacomm Troubleshooting |
| | remote modem was made. | Procedure No. 2.) |
| | | |
- - - -
| E | The program successfully logged on | Incorrect RC phone number, or RC |
| | to the HP Response Center's system. | system is temporarily unavailable. |
| | | (See Datacomm Troubleshooting |
| | | Procedure No. 3.) |
| | | |
- - - -
| F | The program transferred the | Failure to transmit data or an |
| | referenced number of records to the | interruption in data transmission. |
| | HP Response Center. (NOTE that the | Find the error message in the "File |
| | file name is PSDCFILE.PRED.SYS.) | Transfer Errors" section in Appendix |
| | | F to determine whether you should go |
| | | to Datacomm Troubleshooting |
| | | Procedure #4; #5; #6; or #7. |
| | | |
- - - -
| G | This step ONLY occurs when there is | HP Response Center has encountered a |
| | a download (such as, RC Predictive | problem with file transmission. |
| | downloads files to HP Predictive | Find the error message in the "File |
| | Support after any transmission has | Transfer Errors" section in Appendix |
| | been completed). RC Predictive | F to determine whether you should go |
| | files identified as follows: | to Datacomm Troubleshooting |
| | | Procedure #4; #5; #6; or #7. |
| | | |
| | * Xvvvrrrr is the format of the | |
| | file name for a ruleset | |
| | (X000DS35 is an example) | |
| | | |
| | * PSCODEWD identifies a code | |
| | word file. | |
| | | |
- - - -
| H | These messages appear when a file | An error message can occur at this |
| | transfer has successfully completed. | point. If so, all retries have been |
| | | exhausted, and the message begins |
| | | with "TRANSFER." Go to the "TRANSFER |
| | | Errors" in the "File Transfer |
| | | Errors" section in Appendix F. |
| | | |
----------------------------------------------------------------------------------------