You're right! In never occurred to me that the TSO USERMAX might be set higher 
than the number of TSO LUs defined to VTAM. 

Also, thanks for the explanation on my initial reply. I knew what I needed to 
do to get something that worked, or at least was fairly sure. But I'm not the 
best in really deep understanding and explaining. I do know that some of the 
strangeness of the 3270 LU definitions is due to copying from the past when we 
used physical DFT mode 3278 terminals for some multisession  capability, but 
mainly TPX for most of the multisession capability to logon to TSO and multiple 
CICS regions from a single physical 3278 terminal. We have eliminated TPX and 
now use multiple TN3270 sessions per user. Curiously, the ex-TPX users really 
hate this. But then I never liked using TPX. "Each to his own." I like having 
multiple TN3270 sessions visible at the same time, which is impossible with TPX.

--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

 

> -----Original Message-----
> From: IBM Mainframe Discussion List 
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chris Mason
> Sent: Wednesday, April 06, 2011 11:27 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: No LUs available
> 
> 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 
> <jagadish...@gmail.com> 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
> 
> 

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

Reply via email to