S322 is not timeout, nor is S622 limited to I/O error. In this case, it's 3. 
below. The terminal in question is the TN3270 server.

622
Explanation
A task entered from a Time Sharing Option (TSO) terminal ended for one of the 
following reasons:

    1. The system encountered one of the following errors while constructing 
control blocks for TSO:
        a. The system encountered a multiple-step procedure.
        b. The prompting task ended abnormally.
    2. The terminal user signaled ATTN during LOGON scheduling.
    3. The user submitting the job disconnected his or her terminal from the 
system.
    4. The terminal malfunctioned.




--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of 
Jesse 1 Robinson [[email protected]]
Sent: Monday, December 28, 2020 12:34 PM
To: [email protected]
Subject: Re: TSO timeout S622

I don't actually see evidence of timeout, which should generate at least one 
S322 abend message. 622 is I/O error, which can result from any number of 
'unconditional logoff' events. Consider CANCEL from an unexpected source.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
[email protected]

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Nai, Dean
Sent: Monday, December 28, 2020 8:55 AM
To: [email protected]
Subject: (External):Re: TSO timeout S622

*** EXTERNAL EMAIL - Use caution when opening links or attachments ***

Thanks everyone for your suggestions. I am looking into all of them.

________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of 
Steely.Mark <[email protected]>
Sent: Monday, December 28, 2020 11:25 AM
To: [email protected] <[email protected]>
Subject: Re: TSO timeout S622

EXTERNAL: Do not open attachments or click on links unless you recognize and 
trust the sender.
________________________________

Also check your JES PARM JOBCLASS(TSU). That has a TIME option.

Thanks

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Michael Brennan
Sent: Monday, December 28, 2020 10:21 AM
To: [email protected]
Subject: Re: TSO timeout S622

ATTENTION: This e-mail came from an external source. Do not open attachments or 
click on links from unknown or unexpected emails.


Also suggest you check your security system.  ACF2 has a setting that can 
influence S622 time outs at both a global level and an individual id level.  
Not sure if RACF and Top Secret have the same ability.

Michael

________________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of 
Lizette Koehler <[email protected]>
Sent: Monday, December 28, 2020 10:04 AM
To: [email protected]
Subject: Re: TSO timeout S622

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don't click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

I would start with D SMF,O in SDSF LOG function on the system getting the
S622

What you think is in SMF may be something else when displayed.

Next I would work with an ID (Hopefully yours) that is getting S622.

Then logon the ID and start a stop watch.  Make sure you can repeat the error

Next - are you using a Session Manager?  Can it control length of time of 
inactivity and cause a S622

Lastly - any changes since the last time it worked and when it first started to 
get S622?

Lizette


-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Nai, Dean
Sent: Monday, December 28, 2020 5:49 AM
To: [email protected]
Subject: TSO timeout S622

Morning,

     Our TSO sessions are timing out in less than 15 minutes even though we has 
SMFPRM00 set to JWT(0030). Any thoughts on what else could be causing this?

0090  IKT100I USERID SYSxxx    CANCELED DUE TO UNCONDITIONAL LOGOFF
0090  EZZ6034I TN3270 CONN 0010269E LU TCP00059 CONN DROP  INACT-S 894
0090    IP..PORT: 
https://urldefense.com/v3/__http://10.250.214.220__;!!Oai6dtTQULp8Sw!HyCQtMV1DQ-qAgtZnYvr4QdA7aGi68vAKoIGyJLpUfFkrZ65TULZq-k3USSewcUkMa2-$
 ..19745
0281  IKT122I IPADDR..PORT 
https://urldefense.com/v3/__http://10.250.214.220__;!!Oai6dtTQULp8Sw!HyCQtMV1DQ-qAgtZnYvr4QdA7aGi68vAKoIGyJLpUfFkrZ65TULZq-k3USSewcUkMa2-$
 ..19745
0285  IEA989I SLIP TRAP ID=X622 MATCHED.  JOBNAME=SYSxxx  , ASID=00DD.
0285  IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=SYSxxx  , ASID=00DD.
0285  IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=SYSxxx  , ASID=00DD.
0090  EZZ6034I TN3270 CONN 00101B55 LU MULTIPLE CONN DROP  INACT-S 900
0090    IP..PORT: 
https://urldefense.com/v3/__http://10.250.214.209__;!!Oai6dtTQULp8Sw!HyCQtMV1DQ-qAgtZnYvr4QdA7aGi68vAKoIGyJLpUfFkrZ65TULZq-k3USSewTHhWsU8$
 ..60713
0090  IEF450I SYSxxx IKJACCNT IKJSYS - ABEND=S622 U0000 REASON=00000000 901
0090          TIME=07.19.08
0090  $HASP395 SYSxxx  ENDED - ABEND=S622


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to