Work with distributed relational database users

Investigating a problem usually begins with the user. Users might not be getting the results they expect when running a program or they might get a message indicating a problem. Sometimes the best way to diagnose and solve a problem is to go through the procedure with a user.

The Copy screen function allows you to do this either in real time with the user or in examining a file of the displays the user saw previously.

You can also gather more information from Messages than just the line of text that appears at the bottom of a display. This topic collection discusses how you can copy displays being viewed by another user and how you can obtain more information about messages you or a user receives when doing distributed relational database work.

In addition to programming problems, you might have problems with starting the program or connecting to the server when using Advanced Program-to-Program Communication (APPC) or TCP/IP.

• Copy screen
  The Start Copy Screen (STRCPYSCN) command allows you to be signed on to your workstation and see the same displays being viewed by someone else at another workstation.
• Messages
  The iSeries™ server sends a variety of system messages that indicate conditions ranging from simple typing errors to problems with server devices or programs.
• Handle program start request failures for APPC
  When a program start request is received by an i5/OS™ subsystem on the application server (AS), the server attempts to start a job based on the information sent with the program start request. The application requester (AR) user's authority to the application server (AS), existence of the requested database, and many other items are checked.
• Handle connection request failures for TCP/IP
  The main causes for failed connection requests at a Distributed Relational Database Architecture™ (DRDA^®) server configured for TCP/IP use is that the DDM TCP/IP server is not started, an authorization error occurred, or the machine is not running.