Chapter 4: Making Connections

This chapter describes how to connect your machine to other iSeries machines with RSF.  Before you can use RSF functions between machines, you must define an RSF connection.

Two RSF concepts are important for connections:  the server directory and the requester directory.  Each machine has both directories.

The server directory is used for outbound connections.  This is where you store information and options that tell RSF how you want to connect to other machines or partitions.  You give each entry in the server directory a ten-character name or server ID which can then be used with various RSF functions to indicate who you want to connect to.

The requester directory is used for inbound connections.  It lets you control the rights and options that apply to other machines when they contact you.

The term requester machine is used to refer to the machine that initiates a transaction.  The server machine is the one that responds to the request.  A given physical machine can act as both a requester and a server.

Referring to machines as source and target can be confusing in some contexts, particularly when a requester machine is retrieving objects from a server machine.  In this case, the server machine is the target of the request but the requester machine is the target for the objects. 

The following sections explain how to create the most common connections. 

TCP/IP Over a LAN

To connect to another machine with TCP/IP over a LAN or WAN:

Add Server Directory Entries

                     Add Server Directory Entry (ADDRSFSDE)

 Type choices, press Enter.           

 Server ID  . . . . . . . . . . . > TEST          Name     
 Connection method  . . . . . . . > *TCPIP        *SDLCDIAL, *TCPIP...
 Remote system  . . . . . . . . . > '10.3.4.5'

 RSF data port  . . . . . . . . .   602           Number
 Local tunnel access port . . . .   *NONE         1-65534, *JOB, *NONE
 Encryption . . . . . . . . . . .   *BASIC        *NONE, *BASIC, *SSL
 Encryption key data area . . . .   *NONE         Name, *NONE
   Library  . . . . . . . . . . .                 Name, *LIBL
 Run-time compression . . . . . .   *NONE         *NONE, *BASIC, *MAX
 Text 'description' . . . . . . .   My test machine

1. Access the Work With RSF Servers display by running the WRKRSFSRV command or by selecting option 1 from the RSF menu.
    
2. Key F6 to define a new connection.  At the command prompt, specify any name you like for "Server ID". Specify *TCPIP for "Connection Method".  Press Enter.
    
3. Further command prompts will be displayed.  Specify the IP address or TCP/IP network name of the other system for "Remote System".  Press Enter. More prompts will be displayed.  Accept all the defaults and press Enter again. Specify a value for "Text", accept the other defaults and press Enter one last time to complete the entry.
    
4. Repeat steps 1 through 3 above on the other machine if you want to be able to initiate the connection from either machine.
    

Start the Server Function

On the server machine--or on both machines if two way communication is desired--start the RSF server function by prompting the command STRRSFSRV or by selecting option 21 from the RSF menu.  Be sure to specify *YES for "Start RSF TCP/IP support".  Specify *NO for Dialup SDLC, Dialup PPP and Broadcast support if machines will not be connecting to this one using those protocols.  You can specify *YES for "Save as new defaults" if you would like the values specified to become the new command defaults.

                Start RSF Server Function (STRRSFSRV)

Type choices, press Enter.

Start dialup SDLC support . . .  *NO       *YES, *NO
Start dialup PPP support . . . . *NO       *YES, *NO
Start RSF TCP/IP support . . . . *YES      *YES, *NO
Start broadcast support . . . .  *NO       *YES, *NO
Save as new defaults . . . . . . *YES      *YES, *NO

When you press Enter, additional prompts will be displayed.  Accept the defaults and press Enter again as necessary.  You should see a message indicating that the RSF TCP/IP server started normally.

Test the Connection

From the Work With RSF Servers display, key a "T" for test in the option field beside the connection you want to test.  A successful completion message indicates that the connection is working.

Add Requester Directory Entries (Optional)

Requester directory entries control such things as:

• Where received save files go and how they are named.
• Whether pass-through, remote program calls, generic object retrieval, etc. are allowed.
• The minimum level of encryption required for you to accept the connection.

You can add requester entries which are tied to the requesting machine's serial number, system name, or both.  If you do not add requester directory entries to handle incoming requests from a specific machine, RSF will use the entry named ANY to determine the options that apply.

See the on-line help text for the Add Requester Directory Entry (ADDRSFRDE) command for more details.

TCP/IP Over the Internet

Note that RSF transmissions are encrypted by default.  See Appendix G: Configuring Encrypted Connections for more information.

To connect to another machine with TCP/IP over the Internet:

On the Target (Server) Machine.

1. Determine the public IP address of your network or firewall.  If you need help, you can access the following web site from a PC attached to the same network as your iSeries
   
       http://www.whatsmyip.org/
   
   You will need to give this IP address to anyone who will be contacting your iSeries over the Internet.
    
2. Open port 602 in your firewall and forward incoming traffic to your iSeries.  Even better, ask for the public IP address of those allowed to contact your iSeries and open port 602 only for traffic from those specific IP addresses.  There is no need to open the FTP or Telnet ports;  all RSF traffic passes through port 602.
    
3. Start the server function as described above.  Note that no one can use RSF to connect to your machine unless the RSF server function is started.  Ending the RSF server function is an effective way to block incoming connections.
    
4. Optionally, add requester directory entries as described above.

On the Source (Requester) Machine.

1. Obtain the public IP address for the machine you wish  to contact.  Specify the IP address for "Remote System" and create an RSF server entry as described above.
   
   Important:  For Internet connections, be sure to press F10 when adding the server entry and specify *JOB (recommended) or some value other than *NONE for "Local Tunnel Access Port."  This will ensure that RSF telnet and other traffic is routed over port 602.
    
2. Provide your public IP address to the target location so that they can use this to restrict access to their firewall.
    
3. Confirm that the RSF TCP/IP server function has been started at the target location.  Then test the connection as described above.

TCP/IP Dial-Up (PPP)

PPP is a switched (dial-up) protocol used with TCP/IP networks.  All RSF functions can be used over PPP connections with the following limitations:

• RSF release 6.2 or later should be installed on the machines at both ends of the connection.
   
• PPP requires an asynchronous modem.  This is in contrast to the old ECS modems which were configured for synchronous SDLC communications.  Internal modems shipped with newer iSeries machines can be used without change.  Older, synchronous modems must be reconfigured for asynchronous communications.
   
• RSF creates all of the necessary line, controller and device descriptions, as well as the PPP profiles.  You just need to tell RSF how to establish contact between the machines.

On the server (answering) machine:

                          Change RSF Defaults (CHGRSFDFT)
                                                                               
 Type choices, press Enter.
            
 PPP server info:                                                              
   Line description . . . . . . .   RSFSRP          Name, *NONE, *SAME
   Resource name  . . . . . . . .   CMN05           Name
   Interface type . . . . . . . .   *INTMODEM       *RS232V24, *V35, *X21...
   Modem type . . . . . . . . . .   '2793 Internal Modem'      
                     + for more values
 PPP server IP address  . . . . .   '10.24.23.22'                     

1. Select option 31 from the RSF menu to change the product defaults.  Page down to PPP Server Info.  Enter the following:

Line description:  RSFSRP

Resource name:  The name of the resource that corresponds to your internal modem or an async external modem.  (For internal modems, this is typically the first resource listed with type 2771, 2772, 2793, or 2805 on the WRKHDWRSC *CMN display.  The text should say “Comm port”.)

Interface type:  *INTMODEM for an internal modem.  Otherwise *RS232V24.

Modem type:  Enter a modem description that exactly matches one of the entries in the PPP modem list (CFGTCP then option 22, then option 11 to see the list.)  Tip:  If you page down and then page back up, RSF will fill in “2771 Internal Modem” for the modem type.  Just type over the “2771” with the actual type of your adapter, if different.

PPP server IP address:  This is the IP address that the remote machine uses to contact your machine via PPP.  It should be different than your network address.  A default value should have been filled in for you.  If *CALC shows for this parameter, retype *CALC, press Enter and then prompt the command again to see the default IP address chosen by RSF.

2. Run the Display Network Attributes (DSPNETA) command.  Page all the way to the end.  Make sure that the correct country ID is specified for “Modem country or region ID”.  If not, use the CHGNETA command to change it.

3. Select option 21 from the RSF menu to start the server function.  Specify *NO for SDLC and *YES for both “Start dialup PPP support” and “Start RSF TCP/IP support”.  You may type *YES for “Save as new defaults” if this parameter is shown.  When you press Enter, additional parameters are displayed.  Accept the defaults and press Enter again.

              Start RSF Server Function (STRRSFSRV)

Type choices, press Enter.

Start dialup SDLC support . . .  *NO      *YES, *NO
Start dialup PPP support . . . . *YES     *YES, *NO
Start RSF TCP/IP support . . . . *YES     *YES, *NO
Start broadcast support . . . .  *NO      *YES, *NO
Save as new defaults . . . . . . *YES     *YES, *NO

4. If you like, you can also enter PPP Requester Info.  Assuming you have only one modem, the information you enter hear should be nearly the same as what was entered for PPP Server Info.  The only difference is that you should specify RSFRQP for Line Description.

5. The following information should then be provided to someone at the remote location so that they can configure the connection to your machine:

Connection type:  Tell them you are configured for a PPP (*TCPDIAL) connection.

Phone number:  The phone number to use to reach your modem.  You can confirm that you have the correct number by dialing from a regular phone and listening for the modem to answer.  (Make sure to start the RSF server function first.)

IP address:  The IP address shown for “PPP server IP address” in the RSF defaults.  (See above.)

Call-back:  If the remote location will be connecting using RSF’s call-back feature, they will need to know if an initial 9 or other sequence should precede an outgoing phone number when dialing from your modem, and whether any access code must follow the phone number when dialing long distance.

On the requester (calling) machine:

1. Select option 31 from the RSF menu to change the product defaults.  Page down to PPP Requester Info.  Enter one block of information for each available outgoing PPP line.  Call the first line RSFRQP, the second RSFRQP2, and so on.  Be sure to enter a default call-back phone number if call-back is to be used.  Key a plus sign in the blank after “+ for more values” and press Enter to define up to 8 lines.  To define more than 8 lines, use DFU to edit file RSF/RSPF018

                         Change RSF Defaults (CHGRSFDFT)
                                                                               
 Type choices, press Enter.
                                                                               
 PPP requester info:                                                           
   Line description . . . . . . .   RSFRQP           Name, *NONE, *SAME
   Resource name  . . . . . . . .   CMN05            Name
   Interface type . . . . . . . .   *INTMODEM        *RS232V24, *V35, *X21...
   Modem type . . . . . . . . . .   '2793 Internal Modem'              
   Call-back phone number . . . .   '12066330512'  
   Switched connection group  . .   *NONE            Name, *NONE
                + for more values     
 PPP dial attempts  . . . . . . .   1                1-10, *SAME
 PPP redial delay (sec.)  . . . .   15               1-60, *SAME

2. Select option 1 from the RSF menu to Work With Servers.  Press Enter at the initial prompt.  Either key a 2 beside an entry in the list to change it, or press F6 to create a new entry.  For each location to be contacted by PPP.  Specify:

Server ID:  A server ID

Connection method:  *TCPDIAL

RSF phone number:  The number to reach the server via PPP

Remote system:  The IP address specified on the server machine for “PPP server IP address” in the RSF defaults

3. 3. Run the Display Network Attributes (DSPNETA) command. Page all the way to the end. Make sure that the correct country ID is specified for “Modem country or region ID”. If not, use the CHGNETA command to change it.

SDLC Dial-Up

SDLC  requires a synchronous external modem.   Internal modems shipped with newer iSeries machines can not be used for SDLC connections.

RSF creates all of the necessary line, controller and device descriptions.  You just need to tell RSF how to establish contact between the machines.

On the server (answering) machine:

                         Change RSF Defaults (CHGRSFDFT)

 Type choices, press Enter.

 SDLC server info:
   Line description . . . . . . .   RSFSRV      Name, *SAME
   Resource name  . . . . . . . .   CMN06       Name
   Interface type . . . . . . . .   *RS232V24   *RS232V24, *V35, *X21...
   Line speed . . . . . . . . . .   19200       Number, 600, 1200...
   Modem type . . . . . . . . . .   *V54        *NORMAL, *V54, *IBMWRAP.
   Auto dial  . . . . . . . . . .   *YES        *YES, *NO
   Duplex . . . . . . . . . . . .   *HALF       *HALF, *FULL
                + for more values
 Server vary on wait (sec.)   . .   30          15-180, *SAME, *NOWAIT
 Delay dropping inactive line   .   1800        0-65535, *NOMAX, *SAME

1. Select option 31 from the RSF menu to change the product defaults.  Page down to SDLC Server Info.  Enter the following:

Line description:  RSFSRV

Resource name:  The name of the resource that corresponds to your external modem.  Not sure what resource name to use?  See Appendix D:  SDLC Configuration Tips for more information.

Accept the defaults for the other parameters.

2. Select option 21 from the RSF menu to start the server function.  Specify *YES for SDLC and *NO for other protocol options unless you plan to use them as well.  You may type *YES for “Save as new defaults” if this parameter is shown.  When you press Enter, additional parameters are displayed.  Accept the defaults and press Enter again.

              Start RSF Server Function (STRRSFSRV)

Type choices, press Enter.

Start dialup SDLC support . . .  *YES     *YES, *NO
Start dialup PPP support . . . . *NO      *YES, *NO
Start RSF TCP/IP support . . . . *NO      *YES, *NO
Start broadcast support . . . .  *NO      *YES, *NO
Save as new defaults . . . . . . *YES     *YES, *NO

4. If you like, you can also enter SDLC Requester Info.  Assuming you have only one modem, the information you enter hear should be nearly the same as what was entered for SDLC Server Info.  The only difference is that you should specify RSFRQS for Line Description.

5. The following information should then be provided to someone at the remote location so that they can configure the connection to your machine:

Connection type:  Tell them you are configured for a SDLC (*SDLCDIAL) connection.

Phone number:  The phone number to use to reach your modem.  You can confirm that you have the correct number by dialing from a regular phone and listening for the modem to answer.  (Make sure to start the RSF server function first.)

Call-back:  If the remote location will be connecting using RSF’s call-back feature, they will need to know if an initial 9 or other sequence should precede an outgoing phone number when dialing from your modem, and whether any access code must follow the phone number when dialing long distance.

On the requester (calling) machine:

1. Select option 31 from the RSF menu to change the product defaults.  Page down to SDLC Requester Info.  Enter one block of information for each available outgoing SDLC line.  Call the first line RSFRQS, the second RSFRQS2, and so on.  Be sure to enter a default call-back phone number if call-back is to be used.  Key a plus sign in the blank after “+ for more values” and press Enter to define up to 8 lines.  To define more than 8 lines, use DFU to edit file RSF/RSPF012

                         Change RSF Defaults (CHGRSFDFT)

 Type choices, press Enter.

 SDLC requester info:
   Line description . . . . . . .   RSFRQS      Name, *SAME
   Resource name  . . . . . . . .   CMN06       Name
   Interface type . . . . . . . .   *RS232V24   *RS232V24, *V35, *X21...
   Line speed . . . . . . . . . .   19200       Number, 600, 1200...
   Modem type . . . . . . . . . .   *V54        *NORMAL, *V54, *IBMWRAP.
   Auto dial  . . . . . . . . . .   *YES        *YES, *NO
   Duplex . . . . . . . . . . . .   *HALF       *HALF, *FULL
   Call-back phone number . . . .   '1 206 633 0512'
   Switched connection group  . .   *NONE       Name, *NONE
                + for more values
 Requester vary on wait (sec.)  .   15          15-180, *SAME, *NOWAIT
 Redial delay (0.5 sec.)  . . . .   10          0-254, *SAME
 Dial retry . . . . . . . . . . .   0           0-254, *SAME

2. Select option 1 from the RSF menu to Work With Servers.  Press Enter at the initial prompt.  Either key a 2 beside an entry in the list to change it, or press F6 to create a new entry.  For each location to be contacted by dialup SDLC.  Specify:

Server ID:  A server ID

Connection method:  *SDLCDIAL

RSF phone number:  The number to reach the server

Text:  A useful description of the remote location.

SDLC LAN and WAN

On both the requester and server machines:

1. Create a line, controller and device description if suitable ones do not already exist..  The type for the device and controller controller should be *APPC.   The line type must be compatible with Advanced Program To Program Communications (APPC).  Possible line types include SDLC, X.25, Token Ring and Ethernet and TCP/IP.  This step only needs to be performed once, before the first time you attempt to connect to the other  machine.

2. Be sure that the line, controller and device are varied on for both the server and the requester machines.

3. Use the Display Device Description (DSPDEVD) command to display the device description you will be using. Note the following values from the device description:
   
   …Remote location name
   …Device name
   …Local location name

4. Add an entry to the server directory on your machine that refers to the other  machine (option 1 on the RSF menu).
   
   Specify *SDLC for "Connection Method", and press Enter. Fill in the Remote location name, Device name, and Local location name on the server directory entry from the information obtained in step 3 above.

                    Add Server Directory Entry (ADDRSFSDE)

Type choices, press Enter.

Server ID  . . . . . . . . . . . > TEST       Name
Connection method  . . . . . . . > *SDLC      *SDLCDIAL, *SDLC, *TCPIP..
Use existing connection:
  Remote location name . . . . . > THEM       Name, *NONE
  Device . . . . . . . . . . . . > MY_DEV     Name, *LOC
  Local location name  . . . . . > US         Name, *LOC, *NETATR
  Mode . . . . . . . . . . . . .   BLANK      Name, *NETATR
  Remote network identifier  . .   *LOC       Name, *LOC, *NETATR, *NONE
Vary existing controller . . . .   *NONE      Name, *NONE
Vary existing line . . . . . . .   *NONE      Name, *NONE
Text 'description' . . . . . . . > 'My SDLC connection to TEST'