TSO/e
Time Sharing Option/Extensions
 Please! Verify all
details or suggestions with the appropriate vendor and / or vendor's
manuals.
The TSO/E element of z/OS originated from the former TSO/E
component of previous MVS/ESA and OS/390 systems. It originally
contained a set of commands and a set of system services that end users
and programmers could use when writing their own commands. During its
life it was continually enhanced and became the primary user interface
to the OS/390 system and now to the z/OS system.
TSO/E (Time Sharing Option/Extensions) provides an interactive
terminal interface. As in prior releases of TSO/E, this element
includes CLISTs and REXX, but does not include a REXX compiler.
Example logon proc
//********************************************************************
//* NAME = IKJOPER
//* LAST UPDATED BY MS - 01/18/08 //*
//* THIS PROC INVOKES CLIST OPRPROF WHICH RESIDES IN SYS3.TSO.CLIST9
//********************************************************************
//IKJOPER PROC
//IKJOPER EXEC PGM=IKJEFT01,DYNAMNBR=256,PARM=OPRPROF,TIME=1440 //SYSPROC DD DISP=SHR,DSN=SYS3.TSO.CLIST9
//SYSPRINT DD TERM=TS,SYSOUT=*
//SYSTERM DD TERM=TS,SYSOUT=*
//SYSIN DD TERM=TS
Example of Clist OPRPROF called from the above PROC
TSO/E Manuals
SA22-7780-00 Administration PDF
SA22-7781-06 CLISTs PDF
SA22-7782-13 Command Reference PDF
SA22-7783-11 Customization PDF
SA22-7784-04 General Information PDF
SA22-7785-01 Guide to SRPI PDF
SA22-7786-10 Messages PDF
SA22-7787-02 Primer PDF
SA22-7788-04 Programming Guide PDF
SA22-7789-08 Programming Services PDF
SA22-7790-09 REXX Reference PDF
SA22-7791-01 REXX User's Guide PDF
GA22-7792-06 System Diagnosis Data Areas PDF
SA22-7793-04 System Programming Command Reference PDF
SA22-7794-05 User's Guide PDF
Website
TSO ABEND622, FOLLOWED BY ABEND13E or ABEND33E
Technote (troubleshooting)
Problem(Abstract)
TSO users connecting via TCPIP are receiving ABEND622, followed by ABEND13E or ABEND33E.
Cause
Prior to the ABEND622, there are no messages issued. However, the
operator will notice that if the TSO user stays active with sends and
receives, then there is no problem. The ABEND622 occurs if the user has
not pressed the enter key for a period of time.
The Telnet profile contains an INACTIVE parameter statement, which
controls an inactivity timer. This timer controls how long a terminal
connection can be idle with no SNA data traffic before the connection
is dropped.
For example, if you code the timer as INACTIVE 600, a Telnet client
which does not generate any I/O for 10 minutes will be terminated. When
this occurs, the NSEXIT exit for the TSO user is driven with an
unconditional logoff code. This exit generates the ABEND622 to
terminate the TSO user's address space, which is normal. The subsequent
ABEND13E or ABEND33E is also expected when ATTACHED TCBs for this TSO
user are DETACHED.
Resolving the problem
This timeout is normal. If it is occurring too often, you should increase the value coded for the INACTIVE timer.
Website
|
Software Diversified Services, Minneapolis, MN USA