RMTIMSCON statement
Use this statement to define a TCP/IP connection to a remote IMS Connect instance.
You can define multiple connections to one or more remote IMS Connect instances by specifying a separate RMTIMSCON statement for each connection.
A connection defined by an RMTIMSCON statement can be used for either OTMA messages or MSC messages, but not both.
For OTMA connections, an RMTIMSCON statement is required by the sending IMS Connect instance only.
For Multiple Systems Coupling (MSC) connections, a corresponding RMTIMSCON statement must also be specified in the HWSCFGxx member of the IMS PROCLIB data set of the remote IMS Connect instance.
RMTIMSCON statement syntax
RMTIMSCON statement parameters
- APPL=
- Specifies the 1- to 8-character alphanumeric application name
to use in a RACF® PassTicket
that is sent to the remote IMS
Connect instance.
If it is configured to use RACF,
the remote IMS
Connect instance
passes the PassTicket to RACF to
authenticate the user.
You must specify both the APPL and USERID parameters to secure a connection to a remote IMS Connect instance by using RACF. If only one of the two parameters is specified, IMS Connect abends at startup.
You can specify no more than 50 RMTIMSCON statements.
Recommendation: If RACF is not enabled in the remote IMS Connect instance, do not specify either the USERID or the APPL parameters, to avoid unnecessarily generating a PassTicket that is not used. - AUTOCONN=
- For OTMA connections, determines whether this IMS
Connect instance
connects to the remote IMS
Connect instance
during startup.
To connect during startup, a persistent connection is required. You can define an OTMA connection as persistent by specifying PERSISTENT=Y in this RMTIMSCON statement. If both PERSISTENT=N and AUTOCONN=Y are specified, IMS Connect uses AUTOCONN=N and issues the message HWX0920W.
AUTOCONN is an optional parameter.
AUTOCONN= accepts the following values:
- N
- During startup, this IMS
Connect instance
does not establish socket connections to the remote IMS
Connect instance.
The socket connections are made only when messages are sent to the
remote IMS
Connect instance.
AUTOCONN=N is the default.
- Y
- During startup, for OTMA connections defined as persistent, this IMS
Connect instance
establishes one or more socket connections with the remote IMS
Connect instance.
You can specify the number of socket connections that IMS
Connect makes
at startup on the RESVSOC parameter in this RMTIMSCON statement.Restriction: MSC links do not support AUTOCONN=Y. If AUTOCONN=Y is specified in an RMTIMSCON statement that is referenced by an MSC statement, IMS Connect uses AUTOCONN=N and issues message HWSX0920W during startup.
- HOSTNAME=
- The host name of the remote IMS
Connect instance
that you are connecting to.
Your host name can be up to 60 characters in length.
An example of a host name is www.example.com.
You must specify either the HOSTNAME or the IPADDR parameter, but not both.
- ID=
- The 1- to 8-character alphanumeric name that identifies this definition
of a connection to a remote IMS
Connect instance.
If this connection is used for MSC messages, the value specified here must also be specified on the RMTIMSCON parameter of a corresponding MSC configuration statement in the HWSCFGxx member of the IMS PROCLIB data set.
If this connection is used for OTMA messages, the value specified here must also be specified in either the RMTIMSCON parameter of a corresponding OTMA destination descriptor or in an OTMA User Data Formatting exit routine (DFSYDRU0).
This parameter is required.
- IDLETO=
- Specifies the amount of time open socket connections can remain
idle before they are terminated due to inactivity. The timeout interval
is in hundredths of seconds. Timeout values can be from 0 to 2 147 483 647
(X'7FFFFFFF'). A value of 0 prevents inactive connections from timing
out.
This parameter is optional and applies only to persistent socket connections. The default value is 0.
Restriction: MSC links do not support the timeout function. If a timeout value is specified in an RMTIMSCON statement that is referenced by an MSC statement, IMS Connect resets the value 0 and issues message HWSX0920W. - IPADDR=
- The IP address of the remote IMS
Connect instance
you are connecting to.
You can specify the IP address as either an IPv4 32-bit address or an IPv6 128-bit address.
An example of an IPv4 32-bit address is:
127.0.0.1An example of an IPv6 128-bit address is:
2001:DB8:0:0:0:0:0:0You must specify either the IPADDR or the HOSTNAME parameter, but not both.
- PERSISTENT=
- Defines the sockets used for this connection as persistent. This
parameter is optional.Recommendation: For OTMA connections, to reduce storage usage at the remote IMS installation, specify PERSISTENT=Y. When persistent socket connections are used, less storage is used because the remote OTMA creates fewer tpipes.
PERSISTENT=N requires more tpipes because IMS Connect generates a unique client ID for each new socket connection, and for every unique client ID, the remote OTMA instance creates a tpipe. Moreover, until the timeout for idle tpipes cleans them up, the tpipes persist at the remote installation after the socket connection is closed by the local IMS Connect.
For MSC connections, if PERSISTENT=N is specified or accepted as the default, IMS Connect changes the value to PERSISTENT=Y and issues message HWSX0920W, because MSC links require a persistent connection. Specifying PERSISTENT=Y for MSC connections avoids the HWSX0920W message.
- N
- Socket connections from this instance of IMS
Connect to
the remote IMS
Connect instance
are not persistent. After a message is sent through this connection,
the connection is closed.
This value is the default.
- Y
- Socket connections from this instance of IMS Connect to the remote IMS Connect instance are persistent.
- PORT=
- The 1- to 5-character decimal port number of the remote IMS
Connect instance
that you are connecting to. This port number must match a port number
defined on either the PORT or PORTID parameter of the TCPIP configuration
statement of the remote IMS
Connect instance.
This parameter is required.
- RESVSOC=
- The number of send sockets that IMS
Connect reserves
for use by this connection. IMS
Connect reserves
this number of sockets from the maximum number of sockets allowed
for this instance of IMS
Connect,
as specified in the MAXSOC parameter in the TCPIP statement.
RESVSOC is an optional parameter. The default value is 0.
For OTMA connections, when both the AUTOCONN=Y and PERSISTENT=Y parameters are specified, IMS Connect opens the number of sockets specified on the RESVSOC parameter during startup.
For MSC connections, use a RESVSOC value that is equal to or greater than the number of MSC logical links that are using this remote IMS Connect connection. If additional send sockets are required above the number specified on the RESVSOC parameter, IMS Connect opens them only if doing so does not increase the total number of open sockets past the number specified on the MAXSOC parameter.
Each MSC logical link requires two sockets: one send socket and one receive socket. RESVSOC reserves only the send sockets. The receive sockets required by MSC are not reserved. When calculating the total number of sockets required by IMS Connect for the MAXSOC keyword on the TCP/IP configuration statement, account for the additional receive sockets used by MSC by doubling the total number sockets specified on the RESVSOC keyword of all RMTIMSCON statements used by MSC.
Restrictions: The sockets reserved by the RESVSOC parameter are subject to the following restrictions related to the value specified on the MAXSOC parameter of the TCPIP statement:- In the local IMS Connect configuration member, the sum of all the RESVSOC values on all RMTIMSCON statements cannot exceed the total value of the MAXSOC parameter of the TCPIP configuration statement.
- In the remote IMS
Connect configuration
member, the value of the MAXSOC parameter must be large enough to
account for the sum of all RESVSOC parameters on all RMTIMSCON statements
that connect to the remote IMS
Connect instance,
plus the number of connections from any other clients that the remote IMS
Connect instance
might support.
In the local IMS Connect configuration member, the sum of all RESVSOC parameters on RMTIMSCON statements that connect to the same remote IMS Connect instance cannot exceed the value of the MAXSOC parameter of the remote IMS Connect instance.
- USERID=
- Specifies the 1- to 8-character, alphanumeric user ID to use in
a RACF PassTicket that is sent
to the remote IMS
Connect instance.
RACF=Y must be specified in the configuration member of the remote IMS
Connect instance
to complete the security implementation. If the remote IMS
Connect instance
is not configured to support RACF,
the remote IMS
Connect instance
ignores the PassTicket and the connection is not secured.Recommendation: If RACF is not enabled in the remote IMS Connect instance, do not specify either the USERID or the APPL parameters, to avoid unnecessarily generating a PassTicket that is not used.
You must specify both the USERID and APPL parameters for RACF security support. If only one of the two parameters is specified, IMS Connect abends at startup.
