I suspect a problem with your virtual terminal assignment and this has nothing
to do with storage.
Going by the log provided, you're using VIRTPASS as your virtual terminal pool.
Out of the box, this is not the suggested pool configuration that should be
used for TSO sessions. There should be something like TSOESA (the provided
default) or perhaps your installation Admin called it something creative like
TSOPOOL. The CL/SS Configuration Guide provides detail on which pools are a
good fit.
When this problem is happening, I would suggest logging on to your Admin
console: VPSS or VPSSCUA (default names, yours may be different. They used to
be VTP/VTPOPER) and key in: VSM LIST
This will give you a listing of the status of all your virt terminal pools and
you should find VIRTPASS in the list.
VIRTUAL SESSION POOL VIRTPASS,PASS
LOGMODE: &DEFLMODE
VIRTPASS STATISTICS: ACTIVE(0) AVAIL(60) OPEN(0) DEFER(60) LIMIT(0)
1 2 3
4 5
The VSM LIST command displays statistical information about a virtual terminal
pool. This information includes
- the identifiers of all pools, or of the specified pool only
- pool parameters specified in pool definitions
- the current number of each of the following:
1 - Active sessions for virtual terminals in the pool. Because of virtual
terminal sharing, this number could be significantly higher than the number of
open sessions.
2 - Available virtual terminals. Virtual terminals are considered available
until they reach their limit of active sessions (specified with the LIMIT
parameter of the VSM DEFINE command).
3 - Open sessions (that is, ACBs opened by VTAM). If you specify DEFER and do
not specify PARALLEL in the VSM DEFINE command, the number of open sessions
provides the high-water mark for the number of active sessions with any one
application.
4 - Deferred sessions. The total number of open and deferred sessions should
equal the number of virtual terminals defined for the pool.
5 - Sessions allowed for each virtual terminal in the pool, as specified by
the LIMIT parameter of the VSM DEFINE command.
Even if you're not having issues, VSM LIST is pretty handy in keeping tabs on
your virtterm allocations. If you find that you're getting close to depleting
your pool, it may be time to increase it.
All of the above gets thrown away if you discover that the end user created
their own session and for some crazy reason decided that VIRTPASS seemed like a
good choice for their terminal pool. My assumption was that these sessions are
from the GLOBAL/GROUP profiles and not user created. If they ARE user created,
then someone owes you a big fancy coffee.
JoA
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
