Set Up a Native TN3270 and TN5250 Client

Create a TCP/UDP Service to invoke a local third-party application on a client to connect to a device. The target device does not have to host the client application, which must reside on the user client computer. Native TN3270 and TN5250 client support extends the access controls to any native IBM host client. These controls include session recording and automatic connection with the target account setup. Services and clients must be of the same type for session recording to work. For example, you must configure a TN5250 service to be used with a TN5250 client. 
capam32
Create a TCP/UDP Service to invoke a local third-party application on a client to connect to a device. The target device does not have to host the client application, which must reside on the user client computer. Native TN3270 and TN5250 client support extends the access controls to any native IBM host client. These controls include session recording and automatic connection with the target account setup. Services and clients must be of the same type for session recording to work. For example, you must configure a TN5250 service to be used with a TN5250 client. 
In a PCOMM client, negotiation for the function
CONTENTION-RESOLUTION
is enabled by default. When this function is enabled, session recording fails. You can disable the function by adding the following keyword to the .WS profile:
[Telnet3270] TN3270EContentionResolution=N
Follow these steps: 
  1. On the 
    Basic Info
     tab, enter values for the following fields: 
    Service Name:
     enter a name for the portal.
    Local IP:
     enter a valid local loopback address.
    Ports:
     enter 23 (for TN3270 or TN5250) and a local port mapping or asterisk. For example: 
    23:12345
    or
    23:*
    Select the 
    Enable
     checkbox.
    For the 
    Application Protoco
    l, select 
    TELNET
     from the drop-down list.
  2. Select a 
    Mainframe Protocol
     from the drop-down list.
    For the 
    Client Application
    , enter the path if you want to invoke the client automatically. The path that you specify here is launched when the enabled SSH service is accessed. Use the syntax in the sample line. Use or substitute the tags as identified here.
    Windows:
     C:path{}clientApp.exe [options] [email protected]<Local IP> 
    <
    First Port>
    <Local IP> is submitted and replaced with the IP address in the 
    Local IP
     field.
    <First Port> is replaced by the first Local port (after the colon). 
    Example for a Client Application specification: "
    C:\Downloads\QWS 3270\QWS3270.exe" <Local IP> 
    <
    First Port>
    When setting up a service for a mainframe proxy, use this execution path as an example: 
    C:\Program\putty.exe -ssh <Local IP> <First Port>
    Some clients may require this syntax: 
    C:\Program\TN5250.exe -ssl:<Local IP>:<First Port>
  3. Select 
    OK
  4. Create a Device that corresponds to the target device. 
    1. In 
      Devices
      Manage Devices
      , create a Device with the target IP address (do not use FQDN) in the 
      Address
       field. 
    2. On the 
      Services
       tab, use the controls to move the service that you created from the Available Services to the Selected Services.
    3. Select 
      OK
      .
We recommend that all mainframe connections terminate by selecting the “Disconnect” option in the terminal emulator, not by directly shutting down the terminal emulator application.
When a native TN3270 or TN5250 client service policy is configured for session recording, select the
Bidirectional
checkbox for the recording to work.