Jags

John McKown assumed you were using z/OS Communications Server TN3270E 
program as your TN3270 server - and I went right along with that. However 
you may be using the OSA-ICC as your TN3270 server. Perhaps you could let 
us all know(?).

Also, I went right along with John's assumption there may be a limit in the 
definitions on the secondary side of the SNA sessions but Saurabh Khandelwal 
may have a point that it's not the "telnet" element that's at fault but the TSO 
*primary* APPLs that are insufficient. So, indeed, perhaps you should post 
some indication that there are sufficient of these - which ideally also would 
be 
minimally one model APPL statement.

Here's a sample from a project I did a little while ago:

<sample>

T1TSO    VBUILD TYPE=APPL

TTSO1    APPL  ACBNAME=TTSO1,       interpreted and uninterpreted name *
               AUTH=(TSO,PASS,NVPACE), TSO + PASS + prevent o/b pacing *
               EAS=1,                  generally one session at a time *
               FASTPASS=YES,                      efficient PASS logic *
               REGISTER=CDSERVR,            register LU with CD server *
               VPACING=0                             no inbound pacing

TTSO1??? APPL  ACBNAME=TSO0???,     interpreted and uninterpreted name *
               AUTH=(TSO,NVPACE),        TSO + prevent outbound pacing *
               EAS=1,                                      one session *
               LOSTERM=SECOND,        end session on second VARY INACT *
               MAXPVT=0,              no limit on PIUs pending RECEIVE *
               MODSRCH=FIRST,     required model search option for TSO *
               REGISTER=NO,                         do not register LU *
               VPACING=0                             no inbound pacing 

</sample>

Note that I take no responsibility whatsoever at all for the naming convention. 
It was what I found and it wasn't worth the hassle of changing!

Chris Mason

On Wed, 6 Apr 2011 12:43:33 +0530, jagadishan perumal 
<[email protected]> wrote:

>Hi,
>
>In our shop many users are not able to connect the Mainframe. While doing
>telnet they get an error saying " NO LUs available please try again later".
>we have checked the TSO region and it is very well running.
>
>Any idea to resolve.
>
>Regards,
>Jags

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to