- #Connect diect netmap windows how to#
- #Connect diect netmap windows license#
- #Connect diect netmap windows windows#
This is useful when running the Loopback test to check for normal operation of the Connect:Direct server.įor the Connect:Direct server's own Netmap record, set the 'Max Pnode Sess' and 'Max Snode Sess' parameter values to '1' each. This is due to the Connect:Direct server being able to specify itself as a remote node in a process. The Connect:Direct server will have its own record in the Netmap. In this case you will need to assign the values as best as you can and the remote nodes will have to compete for access to the Connect:Direct server. You may have more remote nodes then allowed sessions available. This is not a requirement.Īs a "best practice", the sum total of the 'Max Snode Sess' parameter values for all of the remote node records in the Netmap should not exceed the value set for the '' parameter in the Initparms. The 'Max Pnode Sess' and 'Max Snode Sess' parameter values can be set to '0' if desired.Īs a "best practice", the sum total of the 'Max Pnode Sess' parameter values for all of the remote node records in the Netmap should not exceed the value set for the '' parameter in the Initparms. Max Snode Sess - This is the total number of concurrent sessions that can be established with the Connect:Direct server as the Secondary node with this specific remote node. Max Pnode Sess - This is the total number of concurrent sessions the Connect:Direct server can establish as the Primary node with this specific remote node.Ģ. Set the '' and '' parameter values accordingly do not exceed the session total specified in the license.Įach remote node with which your Connect:Direct Server can communicate will have a record in the Netmap.Įach Netmap record has two parameters for controlling concurrent sessions with the remote node.ġ. If you expect your Connect:Direct server to send more files concurrently than receive, allocate more sessions to the '' parameter. If you expect your Connect:Direct server to receive more files concurrently then send, allocate a greater number of sessions to '' parameter. If your Initparms file does contain the 'sess.total' parameter, the sum of the '' and '' parameter values should not be greater than the value specified for the 'sess.total' parameter.
#Connect diect netmap windows license#
If your Initparms file does not contain the 'sess.total' parameter, the sum of the '' and '' parameter values can not be greater than the number of sessions specified in your contract license agreement. The '' and '' parameter values will need to be divided out from the total sessions allowed (in your license) according to your expectations for the workload on your Connect:Direct server.
#Connect diect netmap windows windows#
Set the 'sess.total' parameter value to the number of allowed sessions specified in your license (if your Connect:Direct for Windows version has this parameter). Set 'sess.total=510' (if your Connect:Direct for Windows version has this parameter). Setting this parameter will prevent you from exceeding your license session limits if you happen to incorrectly specify the values for the '' and '' parameters. sess.total - This is the total number of sessions specified by your contract license agreement. This is the total number of concurrent sessions that can be established to the Connect:Direct server as the Secondary node from all Primary nodes.
This is the total number of concurrent sessions the Connect:Direct server can establish as the Primary Node to all Secondary nodes.
#Connect diect netmap windows how to#
Starting with Connect:Direct for Windows v4.6.0.3 iFix020 and continuing through to the current version, the 'sess.total' parameter was introduced.įollowing are explanations of how to configure these parameters.ġ. Prior to Connect:Direct for Windows v4.6.0.3 iFix 020, in the Initparms, there are two session parameters - '' and ''. Session parameters are defined in two locations - in the Initparms and in the Netmap records. Once you have determined the total number of sessions you are allowed, you are ready to configure the session parameters for Connect:Direct for Windows. Session counts are subject to IBM audits.
You may need to contact your IBM Sales Representative to verify this information. It is your responsibility to know what type of license you have and the number of sessions you are entitled to use. If you have a "Standard" license, then the license will specify the total number of sessions you are entitled to use. If you have a "Premium" license, then you can use up to 255 sessions each for incoming and outgoing connections to remote nodes. This is determined by your contract license agreement that you signed when you acquired the Connect:Direct software. This information applies to all versions of Connect:Direct for Windows.īefore you can configure the session values in Connect:Direct, you need to determine the total number of sessions you are entitled to use.
0 kommentar(er)
