Chapter 14: Problem Determination

This chapter describes the steps to follow if you encounter a problem while using Remote Software Facility.

 

Basics

When you encounter a problem, always check these basic items first:

  1. Make sure you are authorized to the commands, programs, and files in library RSF.
     
  2. Insure that the RSF Server Function has been started on the server machine, and that user profile RSFSRV on the server machine is authorized to use any libraries, files or other objects that your transmission requires.

Then, if you are still having trouble connecting, check to see if you are getting past your own machine:

  1. For dial-up connections, listen to your modem to see if the other machine is answering. If not, the problem is with the setup or modem on your machine.
     
  2. For direct connections, confirm that the connection information specified in the RSF Server Directory Entry and RSF Defaults is correct. Also confirm that the appropriate lines controllers and devices are varied on and active.

Important note: If you are able to contact the server machine but the request ends in error, then the information about the cause of the error is on the server machine.

  1. Use the following command on the target machine to check for relevant messages in the system operator's message queue:

    DSPMSG MSGQ(QSYSOPR) ASTLVL(*INTERMED)
    .
  2. Use the following command on the target machine to check for relevant job logs:

    WRKSPLF SELECT(RSFSRV) ASTLVL(*INTERMED)
    .

 

Check low-level Messages

If the basic items check out, check your low level messages by following these steps:

  1. Enter the following command at any command line to display your job log:

    DSPJOBLOG
     
  2. From the Job Log display, press F10 to display low-level messages.
     
  3. Press F5 to refresh the display.
     
  4. If necessary, press F18 to display the end of the job log.
     
  5. When you have located the messages relating to the problem at hand, print the information by pressing the PRINT key.
     
  6. If you cannot determine the nature of the problem from the job log, or if you cannot correct the problem, proceed to the next section.

 

Common Problems

The following is a list of common problems that can occur with Remote Software Facility, and the likely causes of the problems. Where a problem relates to an RSF message, the message ID is shown. If you cannot find the solution to your problem in the list, proceed to the next section.

A line cannot be varied on.

There is already another line varied on that is associated with the same resource name. Either vary off the existing line, or use the Change RSF Defaults (CHGRSFDFT) command to change the resource name for the RSF line description in question.

While using one of the RSF commands that initiates a request, the display waits forever while contacting the server.

  1. There may be an inquiry message awaiting a reply on the system operator's message queue. If the server's phone is busy or does not answer, a message of the form CPAxxxx is sent to the operator's message queue. See Adding Reply List Entries for more information about adding entries to your system reply list to automatically answer these messages.
     
  2. Use the Change RSF Defaults (CHGRSFDFT) command to check the values specified for "Redial delay" and "Dial retry". If either number is too large, your system is spending an inordinate amount of time trying to redial a number that does not answer or is busy.

An attempt to retrieve an RSF package is unsuccessful.

RSF3009. The save file associated with the RSF package could not be found on the server machine at the time the request was processed. Use the CHGRSFPKG command to view or change the name of the save file associated with the RSF package. If the library list is used to locate the save file, make sure the library containing the file is in the library list of the server communications job. The initial library list of the job is determined by the job description associated with user profile RSFSRV.

This error can also result if user profile RSFSRV was not authorized to the save file on the server machine. User profile RSFSRV should have *USE authority to the file

RSF3010. The save file associated with the RSF package was found, but an error was encountered while sending the data to the requester. Check the job log that was generated for the transaction on the server machine. You can use the command WRKSPLF SELECT(RSFSRV) to help you find the job log. This problem could also result from a bad connection. Try the request again.

RSF9898. Your request was rejected by the server during pre-processing. Contact the server for more information.

RSF4006. The save file specified to receive the RSF data exists, but *NO was specified for "Replace existing save file" on the RTVRSFPKG command. Change the save file name or specify *YES for "Replace existing save file".

RSF4008. The server directory entry name you specified on the one of the RSF requester commands could not be found. Use the WRKRSFSRV command to work with RSF servers.

RSF4009. An error was encountered while trying to evoke the target APPC program on the server machine. Check the job log that was generated for the transaction on the server machine. You can use the command WRKSPLF SELECT(RSFSRV) to help you find the job log. This problem could also result from a bad connection. Try the request again.

RSF4010. The target program on the server machine was contacted successfully, but an error was encountered while trying to send the RSF request information to the server. Check the job log that was generated for the transaction on the server machine. You can use the command WRKSPLF SELECT(RSFSRV) to help you find the job log. This problem could also result from a bad connection. Try the request again.

RSF4011. The target program on the server machine was contacted successfully, but an error was encountered while receiving data for the RSF package. Check the job log that was generated for the transaction on the server machine. You can use the command WRKSPLF SELECT(RSFSRV) to help you find the job log. This problem could also result from a bad connection. Try the request again.

RSF4012. This occurs when the server's phone is busy or does not answer. If the condition persists, check to be sure the server's RSF phone number is specified correctly.

The server is unable to receive the RSF request from the requester after a communications session is successfully established.

RSF3004 Check the job log that was generated for the transaction on the server machine. You can use the command WRKSPLF SELECT(RSFSRV) to help you find the job log. There may be a communications configuration problem. Use the CHGRSFDFT command to check the values specified for installation defaults. This problem could also result from a bad connection. Try the request again

The RSF package being accessed is associated with a pre-processing program on the server machine, but the program could not be found at the time the request was received.

RSF3005 As shipped, RSF server jobs are started with job description RSF in library RSF. Check the initial library list parameter of the job description to determine the initial library list of the server communications job. Make sure the pre-processing program exists and is in a library where it can be found. Use the CHGRSFPKG command to view or change the pre-processing program associated with the RSF package.

An attempt to download the cover letter for an RSF package is unsuccessful.

RSF3006 There is no cover letter associated with the RSF package on the server machine

RSF3007 Cover letter data exists on the server machine, but an error was encountered while sending the data to the requester. Check the job log on the server machine that was generated for the transaction. You can use the command WRKSPLF SELECT(RSFSRV) to help you find the job log. This problem could also result from a bad connection. Try the request again.

An attempt to start the server function on your machine is not successful.

RSF3015 User profile RSFSRV must exist for the server function to be started. See the chapter 3, Installation for more information about how to create the user profile.

The software demonstration period has expired

RSF4001 The 30-day software demonstration period is over This error can also occur if you have recently changed CPUs. Contact Bug Busters for assistance:  support@bugbusters.net .  If your machine serial number recently changed, indicate the old and new serial numbers in your email.

Error receiving reply from server.

RSF4041 This error can occur when communicating with a previous version of RSF if the function you are trying to access was not provided in the earlier version. If you are using the RSFLINK API or the CPYFRSF command, you may have specified an invalid user id or password. Check the low-level messages on your machine and the job log on the server machine for more information.

Forwarding Problem Information To Bug Busters

If you encounter a problem while using Remote Software Facility, and you are unable to solve it by following the steps outlined in the sections above, email the following information to support@bugbusters.net:

    1. Your name, company name and phone number.
       
    2. A brief description of the problem, along with a step-by-step description of how to recreate it.
       
    3. Messages from the system operator's message queue collected in the Basics section above.
       
    4. Job logs collected in the Basics section above.