Binding the CA CSM Application Server to a TCP/IP Stack in a Multi-TCP/IP Stack Environment
search cancel

Binding the CA CSM Application Server to a TCP/IP Stack in a Multi-TCP/IP Stack Environment

book

Article ID: 28438

calendar_today

Updated On:

Products

Mainframe Software Manager (Chorus Software Manager)

Issue/Introduction

When your LPAR with CA CSM has multiple TCP/IP stacks, establish a TCP/IP stack affinity to a desired stack. Establishing a stack affinity binds all socket communications to that stack.

To establish a stack affinity, select one of the following methods:

 

§     Add a DD statement SYSTCPD DD to the CA CSM startup JCL (RunTimeMVSHLQPrefix.JCL(MSMTCSRV)) pointing to a

   specific TCPIP.DATA data set.

For example:

//SYSTCPD DD DSN=TCPIP.SEZAINST(TCPDATA),DISP=SHR

 

 

§     Add the environment variable _BPXK_SETIBMOPT_TRANSPORT to the RunTimeMVSHLQPrefix.SAMPLIB(MSMLIB) member

   that is associated to the STDENV DD of the CA CSM application server.

For example: 

export _BPXK_SETIBMOPT_TRANSPORT=stackname

 

 

§     Add an extra step, AFFINITY, in the CA CSM startup JCL (RunTimeMVSHLQPrefix.JCL(MSMTCSRV)) before the MSMSRV step:

For example: 

//AFFINITY EXEC PGM=BPXTCAFF,PARM=stackname

 

 

Environment

Release:
Component: MSM