No, iSeries Access does not have the Bypass Sign on box selected it using tn5250 and not tn5250e.
In this case the exit code is not dependent upon what is in the telnet string provided by the client with the exception of the device name.
I can actually configure the client access session with the Bypass Sign on box selected and disallow the auto sign on from the exit code.
For what I am attempting to do the client is not passing any log in credentials at all, just a device name.
date: Wed, 28 Aug 2013 18:52:13 +0000
from: "Monnier, Gary" <Gary.Monnier@xxxxxxxxx>
subject: RE: QIBM_QTG_DEVINIT
Auto-signon does not work with TN5250. In iSeries Access I suspect you have the Bypass Signon box selected. This tells iSeries Access to use the TN5250E protocol.
In iSeries Access try deselecting Bypass Signon then try connecting. This will tell iSeries Access to use the TN5250 protocol. You may have to restart your client to have the change take effect.
Here's a link to the TN5250E RFC. The " Enhanced Display Auto-Signon and Password" section should answer most of your questions.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monty G. James
Sent: Wednesday, August 28, 2013 11:33 AM
Subject: RE: QIBM_QTG_DEVINIT
*NONE for the password is not the issue, in this cause it is not a display file issue.
Since the sign on is bypassed and a program is called and not a display file.
iSeries Access 5250 functions as expected but when using TN5250 the auto sign on fails.
Here is the relevant code snippet:
if ( IP.Addr>=wkLowRF and IP.Addr<=wkHighRF )
or ( IP.Addr>=wkLowHD and IP.Addr<=wkHighHD );
peUser.Profile = 'SSLTST1';
peUser.Curlib = 'UTILLIB ';
peUser.Program = 'RFTELNET ';
peAutoSignOn = *ON;
peAllowConn = *OFF;
I would have expected the connection to have been dropped but what I am seeing is the sign screen displayed with the user profile, current lib and program fields populated.
Again iSeries Access 5250 works just fine TN5250 does not.
date: Wed, 28 Aug 2013 17:00:00 +0000
from: Dan Kimmel <dkimmel@xxxxxxxxxxxxxxx>
subject: RE: QIBM_QTG_DEVINIT
CPF1118 indicates that the user profile whose name you're putting into the structure in your exit has password set to *NONE. *NONE isn't allowed ever for a display file.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Monty G. James
Sent: Wednesday, August 28, 2013 10:11 AM
Using a modified example from Scott (ISOTELIR4) I have registered a
exit program with this exit point, The code validates the IP and
If the validating passes sets the user profile, curlib initial program
and turn auto signon On.
All work as expected with iSeries Access.
If using TN5250 it failes by filling in the sign on screen with the
user profile, initial program and current lib and through a CPF1118 No
password associated with the user.
The target for me is to bypass the sign on screen and run the initial
program if the connection is from a predefined IP range and device.
Any help would be appreciated.
Monty G. James
Hobby Lobby Stores, Inc.
7707 SW 44th St
Oklahoma City, OK 73179
This email message, including any attachment(s) is for the sole use of
the intended recipient(s) and may contain confidential information.
Any unauthorized review, use, disclosure or distribution is strictly
prohibited. If you are not the intended recipient, please immediately
contact the sender by email.
This email message, including any attachment(s) is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you are not the intended recipient, please immediately contact the sender by email.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l
date: Wed, 28 Aug 2013 15:01:10 -0400
subject: Re: PTF install questions
I'd dearly love to know why the vendor wishes to stop at 6.1.
Is it because they've not tested it on 7.1?
Is it because of some other issue? Like my favorite pet peeve is how IBM
always changes CPYTOIMPF with every release.
If it's because they like to stay one release behind for "stability"
reasons, smack them upside the head. Three years plus of service, eight
cumes, six technology refreshes; that's enough of a shakedown cruise.
I'm having a tough enough of a time getting IBM to patch security
breaches, now, in 7.1 with them attempting to postpone it to some future