Starting Multiple Named Sessions

[J.Panzenhagen]

I am running CA version V3R2. We have been running through Netsoft router, but now we are moving to TCP. Under Netsoft we were able to name the session. The 400 would then create a device name for each new session that was opened, i.e. PAYROLS1, PAYROLS2, etc. Under TCP the only device that gets created is PAYROLL and there is no way to start another CA session. Question: Does anyone know how to get multiple named CA sessions using CA under TCP/IP? Thanks, John Panzenhagen

[Guest.Visitor]

Leave the device name blank in the CA session configuration. Then the AS/400 will autoconfig a QPADEV000x for each session you care to open.

[J.Panzenhagen]

Is there any way to do this with named sessions? John

[Guest.Visitor]

You can put a name where the device name is. If you still want to continue the same thing as your netsoft, è name PAYROLS= that way, the first session will be name PAYROLS1 2nd = PAYROLS2 etc... Gilbert

[J.Panzenhagen]

Gilbert, I tried putting an id of JOHNP= but when I start the session it comes up with the generic QPADEV000C. Am I doing something wrong? John P

[B.Myrick]

John, When you change the name of your session, are you saving it? If not, the original setting of QPADEV000xxx will remain the session name. If you are saving it, make sure you are starting the proper *.WS session. When you attempt to connect, do you have QAUTOCFG turned on? If not, the device will just stay at a blank screen and attempt to attach itself every few seconds. -bret

[S.Mildenberger]

John, I believe that naming scheme only works for Client Access Express. If you can't move to Express then you will have to create a different session for each named device individually (MYNAMES1 and MYNAMES2 would be different icons) if you want named devices. Scott Mildenberger

[Guest.Visitor]

If you are able to use CA Express, there is a good Information APAR that explains how the naming options work. Take a look at APAR II12112.