Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  15. Appendix B: PowerExchange Glossary

LISTENER Statement

LISTENER Statement

The LISTENER statement defines the TCP/IP port on which a named PowerExchange Listener process listens for work requests.
You can define up to 10 LISTENER statements in a DBMOVER configuration file.
For netport jobs on z/OS, define a LISTENER statement with a unique port and define a NETPORT statement that references that port.
Optionally, you can specify SSL authentication and additional parameters that control TCP/IP buffer sizes and wait times.
All
NETPORT for netport jobs and SSL for SSL authentication
No
LISTENER=({
listener_node
|
node1
}    ,TCPIP    ,{
port
|
2480
}    [,{
send_bufsize
|
65536
}]    [,{
receive_bufsize
|
65536
}]    [,{
send_size
|
4096
}]   [,{
receive_size
|
4096
}]   [,
receive_timeout
]   [,
ip_address
]   [,SSL] [,
message_queue
] )
{
listener_node
|
node1
}
Required. Node name of the TCP/IP port on which the PowerExchange Listener process listens.
Use this node name to select a LISTENER statement when you start the PowerExchange Listener process, as follows:
  • On Linux, UNIX, and Windows, specify the listener node name on the dtllst command.
  • On i5/OS, specify the listener node name in the SBMJOB command that runs the DTLLST program. For more information, see the
    PowerExchange Command Reference
    .
  • On z/OS, specify the listener node name in the PARM field of the EXEC card in the JCL.
Default is node1.
TCPIP
Required. Communications protocol. TCPIP is the only valid option.
{
port
|
2480
}
Required. TCP/IP port used to listen for work requests. Valid values are from 1 through 65535. Default is 2480.
{
send_bufsize
|
65536
}
Optional. Size, in bytes, of the data portion of the TCP/IP send buffer. Valid values are from 1024 through 1048576. Default is 65536.
{
receive_bufsize
|
65536
}
Optional. Size, in bytes, of the data portion of the TCP/IP receive buffer. Valid values are from 1024 through 1048576. Default is 65536.
{
send_size
|
4096
}
Optional. Maximum size, in bytes, of the block of data that PowerExchange sends to TCP/IP at one time. If the data exceeds this size, PowerExchange splits data into multiple blocks until all of the data is sent. Valid values are from 512 through 1048576. Default is 4096.
Enter a value that is less than or equal to the TCP/IP send buffer size.
{
receive_size
|
4096
}
Optional. Maximum size, in bytes, of the block of data that PowerExchange processes from TCP/IP in one operation. If the data exceeds this size, PowerExchange splits data into multiple blocks until all of the data is received. Valid values are from 512 through 1048576. Default is 4096.
Enter a value that is greater than or equal to the TCP/IP receive buffer size.
receive_timeout
Optional. Number of seconds that PowerExchange uses as the receive timeout value when a long wait is required. PowerExchange uses this value for this request only. Valid values are from 1 through 14400.
ip_address
Optional. IP address that PowerExchange uses on the bind operation for the socket.
If you do not specify an IP address, PowerExchange uses INADDR_ANY on the bind operation, which causes TCP/IP to bind to all network interfaces on the host. Use this parameter if you have multiple network interfaces and want to restrict the port on which the PowerExchange Listener listens to a specific interface.
SSL
Optional. Specifies that PowerExchange uses SSL authentication. Specify this parameter on a Linux, UNIX, or Windows Listener machine that serves as the SSL server during SSL communications.
To use TLS networking for IBM i, you can specify SSL in tenth comma position. When you use TLS networking, the send and receive sizes in the sixth and seventh comma positions of the LISTENER statement must be set to a value that does not exceed 16384.
message_queue
Optional. Add a message queue to the LISTENER statement for IBM i. IBM i can run multiple listeners from the same PowerExchange environment by specifying a different message queue for each PowerExchange Listener. For example:
/* Listener using default message queue (LISTENER) LISTENER=(node1,TCPIP,2480,262144,262144,262144,262144) /* Listener using user defined message queue (LISTENER2) LISTENER=(node2,TCPIP,12480,262144,262144,262144,262144,,,,LISTENER2)
If no value is specified the existing default message queue LISTENER is assumed.
For information about creating message queues, see the
PowerExchange Installation and Upgrade Guide
.
  • If you create a PowerExchange Listener Service, use the node name that you define in the LISTENER statement as follows:
    • If you create the Listener Service through Informatica Administrator, the node name value that you specify in the
      Start Parameters
      property must match the node name that you define in the LISTENER statement.
    • If you create the Listener Service through the infacmd pwx CreateListenerService command, the node name value that you specify for the -StartParameters option on the command must match the node name that you define in the LISTENER statement.
    When you create the Listener Service, the Service Manager associates it with the PowerExchange Listener process on the node. For more information about configuring and creating a Listener Service, see the
    Informatica Application Service Guide
    .
  • If you issue pwxcmd commands or infacmd pwx commands to the PowerExchange Listener process, the node name that you define in the LISTENER statement must match the node name that you define in the SVCNODE statement in the DBMOVER configuration file. In this case, enter a string of up to 12 characters in length for the
    listener_node
    parameter of the LISTENER statement. This is the maximum length of the service name that you can specify in the SVCNODE statement.