Reflection for IBM 2014
Reflection for IBM 2011
Reflection Standard Suite 2011
Reflection for the Web 2014 (All Editions)
Reflection for the Web 2011 (All Editions)
Reflection for the Web 2008 (All Editions)
Reflection Desktop Pro 16.0
Reflection Desktop Pro 16.1
Reflection for the Web (All Editions) 12.2
Reflection for the Web (All Editions) 12.3
This technical note explains how to start the required LIPI servers on an IBM i (iSeries or AS/400) to enable file transfer over TCP/IP. Using Reflection 2014, Reflection for IBM 2014 or 2011, or Reflection for the Web, files can be transferred without starting a terminal session.
Verifying Host Services on the IBM System i
Before you can use Reflection to transfer files over TCP/IP, you must verify whether Host Servers is installed on IBM i, and then start the LIPI servers on the IBM System i.
To verify whether Host Servers is available, follow these steps:
- Open Reflection and connect to IBM i with a terminal session.
- Enter the command DSPSFWRSC.
- In the Software Resource list, look for at least one Option 12 (i5/OS - Host Servers).
If Option 12 is listed, continue with the next section. If you do not see Option 12 listed, you will need to install the host servers from the i5/OS installation media before continuing.
Starting the LIPI Servers
The LIPI servers must be started because they are not available by default.
Note: You need *ALLOBJ system administrator privileges on the IBM i to successfully complete these instructions.
On the IBM i, you can start the LIPI servers all at once or individually.
- To start all i5/OS LIPI servers, use this command:
Note: After executing the above command you may see the error, "Host server daemon jobs unable to communicate using IPX." You can ignore this error because IPX is not needed.
- To start the required LIPI servers individually, use these commands:
Determining Which LIPI Servers Are Started
To confirm which LIPI servers are started, follow these steps:
- On the IBM System i, issue this command:
- Select option 3: Work with TCP/IP connection status.
- Look for the following items under the Local Port heading to verity that the required LIPI servers are running (names may be displayed truncated):
Japanese and Other Double-byte Systems
The NETSTAT command will not display the LIPI servers in Japanese or other double-byte operating systems. Instead, look for the TCP port numbers of the LIPI servers.
The following table lists the default ports for the required LIPI servers:
||TCP Port Number
|SSL Port Numbers
||449 (must not be changed from default)
You can use non-default ports for all of the servers except the server mapper, which must be on port 449. This port allows the PC to query the host to determine where the other ports are mapped.
Verifying Prestart Jobs
Before you can make a connection and transfer files, one of the following prestart jobs must be started: QZDAINIT or QZDASOINIT. A prestart job is started when you start the corresponding host server daemon. The prestart job then waits and listens for an incoming connection before going to an active state.
- QZDAINIT is for an SNA (or 802.2) connection. QZDAINIT is the Server program.
- QZDASOINIT is for TCP/IP, specifically a TCP/IP and IPX socket connection. QZDASOINIT is the Server program, and QZDASRVSD is the Server Daemon program.
To verify whether a prestart job is running, enter the following command on the i5/OS command line:
Configuring File Transfer in Reflection for IBM
Using Reflection, you can transfer files directly to or from the IBM i host over TCP/IP without starting a terminal session. Follow these steps:
- In the Reflection Workspace, open a session document or create a new terminal session document.
- On the Ribbon, click the File Transfer Settings icon.
- The Transfer dialog box is displayed. On the Protocol tab, select AS/400.
- On the AS/400 tab, select TCP/IP from the Transport drop-down menu.
- Select LIPI from the Host TP drop-down menu.
- In the System name field, enter the name of the IBM i host, if you have not already specified this information.
- Click OK.
- In the Transfer dialog box, specify the files you wish to transfer.
- Click the appropriate Transfer button.
Configuring File Transfer in Reflection for the Web
Using Reflection for the Web, you can transfer files directly to or from the AS/400 host over TCP/IP without starting a terminal session. Follow these steps:
- Launch the Administrative WebStation and under Tools, click Session Manager.
- Click Add to create a new session.
- Select the IBM AS/400 Data Transfer option as the Web-Based Session Type and enter a Session name, such as AS/400 Transfer. Click Continue.
- Configure your session, and then click Launch to start your file transfer session.
- To configure file transfer, on the Connection menu, click Connection (or Session) Setup. In the dialog box, enter your Host, User ID, and Password.
- (Optional) To configure security, click the SSL/TLS (or Security) button.
- Click OK to connect to the AS/400.
- Click File > Save and Exit to save your file transfer session.
To change your file transfer settings, open your file transfer session and on the Options menu, click To Host or click From Host to configure the settings.
1. If you receive the error, "TCP connection dead," check the following settings on the IBM System i:
- Verify that the LIPI servers are running. (This is the most likely cause of the error.)
- Check whether the default ports are being used. See the table above for default values.
If non-default ports are being used, verify that the Use default ports check box is cleared in the advanced file transfer setup dialog box.
- Check whether any of the specified portsâdefault or notâare blocked on the host.
To verify whether files can be transferred to or from the designated host, try a different transfer protocol, such as MPTN.
2. If you receive the error, "TCP - Unable to open Connection", ensure a certificate on the IBM System i has been assigned to the:
a.) Central Server,
b.) Database Server,
c.) Signon Server, and
d.) File Server
- Symptom: Initial SSL/TLS connection to the mainframe is successful, yet LIP transfer fails very quickly with the message, "TCP - Unable to open Connection".
- Host services were verified, LIPI servers are running for SSL, appropriate prestart jobs are running, and Reflection is configured correctly for LIPI transfers.