IKTLOGR ERROR 026

2011-12-01 Thread Richards, Robert B.
IKJ608I TSOLOGON TERMINATED. IKTLOGR ERROR 026,USER xx,PROC x

Anyone know what might cause these to show up all of the sudden?

We are at z/OS 1.12 and have been for months.

-
Robert B. Richards(Bob)
US Office of Personnel Management
1900 E Street NW Room: BH04L
Washington, D.C.  20415
Phone: (202) 606-1195
Email: robert.richa...@opm.gov<mailto:robert.richa...@opm.gov>
-

--
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


Re: IKTLOGR ERROR 026

2011-12-01 Thread Walt Farrell
On Thu, 1 Dec 2011 12:33:27 -0500, Richards, Robert B. 
 wrote:

>IKJ608I TSOLOGON TERMINATED. IKTLOGR ERROR 026,USER xx,PROC x
>
>Anyone know what might cause these to show up all of the sudden?
>
>We are at z/OS 1.12 and have been for months.

It's explained in the Messages book if you lookup that message. See 
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2M9C0/SPTM012768

When the program is IKTLOGR and the return code is 26, it means reconnect 
failed because a previous reconnect attempt was already in progress. 


-- 
Walt Farrell
IBM STSM, z/OS Security Design

--
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


Re: IKTLOGR ERROR 026

2011-12-01 Thread Ulrich Krueger
According to the manual, System Messages, Vol. 9:

IKJ608I TSOLOGON TERMINATED. {srname|mac} ERROR return-code. USER
{userid|UNKNOWN} PROC {ppp|UNKNOW}
| |Explanation:
(some text omitted)
||When the program is IKTLOGR and the return code is 26, it means reconnect
failed because a previous reconnect attempt was already in progress.|

Does that help shed any light on the situation?

Regards,
Ulrich Krueger


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf
Of Richards, Robert B.
Sent: Thursday, December 01, 2011 9:33 AM
To: IBM-MAIN@bama.ua.edu
Subject: IKTLOGR ERROR 026

IKJ608I TSOLOGON TERMINATED. IKTLOGR ERROR 026,USER xx,PROC x

Anyone know what might cause these to show up all of the sudden?

We are at z/OS 1.12 and have been for months.

-
Robert B. Richards(Bob)
US Office of Personnel Management
1900 E Street NW Room: BH04L
Washington, D.C.  20415
Phone: (202) 606-1195
Email: robert.richa...@opm.gov<mailto:robert.richa...@opm.gov>
-

--
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


Re: IKTLOGR ERROR 026

2011-12-01 Thread Richards, Robert B.
Walt,

Thank you, but I was not asking what it was... I was asking what would cause it 
to show up all of the sudden (about a dozen times recently for different users 
on different systems in one sysplex).

I am suspecting a bug, but thought I'd canvass the list for their experience 
with this (or lack thereof). 

Bob


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Walt Farrell
Sent: Thursday, December 01, 2011 12:49 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: IKTLOGR ERROR 026

On Thu, 1 Dec 2011 12:33:27 -0500, Richards, Robert B. 
 wrote:

>IKJ608I TSOLOGON TERMINATED. IKTLOGR ERROR 026,USER xx,PROC x
>
>Anyone know what might cause these to show up all of the sudden?
>
>We are at z/OS 1.12 and have been for months.

It's explained in the Messages book if you lookup that message. See 
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2M9C0/SPTM012768

When the program is IKTLOGR and the return code is 26, it means reconnect 
failed because a previous reconnect attempt was already in progress. 


-- 
Walt Farrell
IBM STSM, z/OS Security Design

--
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


Re: IKTLOGR ERROR 026

2011-12-01 Thread Chris Mason
Bob

We may need a description of the configuration of your users in order better to 
appreciate what might cause this phenomenon.

It could be something like the following, which unless and until I hear 
otherwise, I am going to assume:

TSO--VTAM--VTAM--SERVER--EMULATOR

Where "SERVER" is the SNA-oriented Communications Server TELNET server program 
(TN3270E) and "EMULATOR" is some sort of 3270 emulator taking on the role of 
the TELNET client probably with TN3270E capability, for example PCOMM.

Have there been, in a recent "change slot", changes to parameters relating to 
the "SERVER"?

Have there been, in a recent "PC software download" - or whatever you might 
call it, changes to parameters relating to the "EMULATOR"?

Have the users of your "EMULATOR" been given instructions on how to "improve" 
the operation of their workstation affecting setting up, or more likely, 
closing down their TN3270(E) connections?

What does you local specialist in charge of the "SERVER" say about this 
phenomenon? There may be some associated messages only he or she could get his 
or her head around.

You may like to check on this function, new in V1R11 - which you may have 
skipped and so encountered first in V1R12, which is one of those very, very 
naughty cases where the developers have put out - and *implemented* - an 
"enhancement" without asking, as it were.

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2e2a0/60.5

Pending full analysis of what is going wrong, you might like to see if 
LOGONHERE(OFF) prevents the problem reoccurring.

This is all based on the word "reconnect" being associated with "return code" 
26.

Chris Mason

On Thu, 1 Dec 2011 12:33:27 -0500, Richards, Robert B. 
 wrote:

>IKJ608I TSOLOGON TERMINATED. IKTLOGR ERROR 026,USER xx,PROC x
>
>Anyone know what might cause these to show up all of the sudden?
>
>We are at z/OS 1.12 and have been for months.
>
>-
>Robert B. Richards(Bob)

--
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


Re: IKTLOGR ERROR 026

2011-12-01 Thread Walt Farrell
On Thu, 1 Dec 2011 13:05:07 -0500, Richards, Robert B. 
 wrote:

>Walt,
>
>Thank you, but I was not asking what it was... I was asking what would cause 
>it to show up all of the sudden (about a dozen times recently for different 
>users on different systems in one sysplex).
>
>I am suspecting a bug, but thought I'd canvass the list for their experience 
>with this (or lack thereof).

I would suspect you're having a number of users who are starting to do a LOGON 
RECONNECT and for some reason are initiating another one before the first one 
finishes. It's hard to say whether that would represent a change in user 
behavior, an issue with connectivity such that the first reconnect isn't 
completing for them and they start another one, an issue with the user's PCs, 
or what.

-- 
Walt

--
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


Re: IKTLOGR ERROR 026

2011-12-02 Thread Elardus Engelbrecht
Richards, Robert B. wrote:

>Thank you, but I was not asking what it was... I was asking what would cause 
>it to show up all of the sudden (about a dozen times recently for different 
>users on different systems in one sysplex).

>I am suspecting a bug, but thought I'd canvass the list for their experience 
>with this (or lack thereof).

After reading all those replies... Perhaps could you try out these suggestions?


Check if all those terminals are covered/shared by a bad logmode entry. 

Or if they connected to a bad control unit, try VARY them offline and online. 
And perhaps the major network node too.

That is of course if you can locate something common between all these problem 
terminals.

Last question: Are they not perhaps sharing a bad emulator software (perhaps 
bad due to recent upgrade)?

HTH!

Groete / Greetings
Elardus Engelbrecht

--
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