RE: QIBM_QTG_DEVINIT -- MIDRANGE-L

To Dan I must say I have mud on my face, I should know better than say "hat is not it".

Here is what was going on:

Client access was imitating the connection to the sign on server using a profile and password and then initiating the telnet session and the exit code was starting the job using a different profile without a password.

The non-client access TN5250 was making the connection without a user profile and the exit code was attempting to start the job with a user profile that did not have a password.

I changed the profile password from *NONE to something and it worked as expected.

End result now a given device and IP is able to start a session and initiate an initial program without the device passing a user profile or password.

Moral of the story if you ask for advice then listen to it.

Thanks to all,
Monty

-----Original Message-----
From: Monty G. James
Sent: Wednesday, August 28, 2013 2:58 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: QIBM_QTG_DEVINIT

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.

http://tools.ietf.org/html/draft-ietf-tn3270e-tn5250e-05

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monty G. James
Sent: Wednesday, August 28, 2013 11:33 AM
To: midrange-l@xxxxxxxxxxxx
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;

else;
peAllowConn = *OFF;
endif;

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.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Monty G. James
Sent: Wednesday, August 28, 2013 10:11 AM
To: midrange-l@xxxxxxxxxxxx
Subject: QIBM_QTG_DEVINIT

Using a modified example from Scott (ISOTELIR4) I have registered a
exit program with this exit point, The code validates the IP and
device name:
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
iSeries/AS400 Administrator
[cid:image001.png@01CEA3D5.1C7F9D50]
Hobby Lobby Stores, Inc.
7707 SW 44th St
Oklahoma City, OK 73179
405-745-6274
monty.james@xxxxxxxxxxxxxx<mailto:monty.james@xxxxxxxxxxxxxx>

________________________________
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

------------------------------

message: 5
date: Wed, 28 Aug 2013 15:01:10 -0400
from: rob@xxxxxxxxx
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 release.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 08/28/2013 02:35 PM
Subject: Re: PTF install questions
Sent by: midrange-l-bounces@xxxxxxxxxxxx

I ran ANOBJCVN. Vendor code was clean. Nice, because a year or two ago,
they came out with a service program but no source. We have all other
source. I have had to backtrack programs to that point, and passed that
to
"my boss". I put that in quotes for a reason. Entire structure has been
upended. Officially, he isn't my boss anymore. Used to be, though. But,
I try to get things done for him. He has authority to ask me.

I have never been in such a weird environment as this has become.

Point is, I asked boss why stop at 6.1. His response was based on his
contact with vendor. From what I have read on this list and read in the
MTU for 6.1 and 7.1, I see nothing odd going on. But, then, there is that
service program with no source.....

John McKee

On Wed, Aug 28, 2013 at 1:03 PM, <rob@xxxxxxxxx> wrote:

No problem. Often it is a mutual dilemma. The customer tries to go on
the cheap and stop paying maintenance. Now they want to upgrade from

V5R4

and find that the vendors programs will not run on 6.1 or 7.1 without
recompilation. Since they have no source they contact the vendor. The
vendor is glad to help, providing the customer does one of two things:
1 - pay all back maintenance, plus x% for not paying in a timely

fashion,

or
2 - buy their software at current list price.
Then the shoving match starts...

Then again, it could be my initial suspicion, that the vendor is

pocketing

all their support money and putting none into the product.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 08/28/2013 01:53 PM
Subject: Re: PTF install questions
Sent by: midrange-l-bounces@xxxxxxxxxxxx

Rob,

Thank you for the links, and your patience.

As to vendor level: I have no contact with the vendor. My boss >had<
contact with vendor. He is trying to get that restored. It is just

plain

weird. At times, I feel like I am rearranging deck chairs on Titanic.
System still used, minimal level, for an uncertain time. People seem to
be
jumping ship when they can.

John McKee

On Wed, Aug 28, 2013 at 12:11 PM, <rob@xxxxxxxxx> wrote:

As far as still running old versions of the OS goes, do you know that

IBM

support will only give you six months upon the announce date of SUSE

Linux

to get to that version if you still want support?

IBM i is a bit different
V5R4 has been GA for 7 and a half years.
6.1 has been GA for almost 5 and a half years.
7.1 has been GA for almost 3 and a half years.

If your vendor can't support 7.1 well after 3 years of general
availability, dump them. I don't speak lightly. I dumped vendors who
weren't ready for 6.1 within 6 months of GA date.
I don't pay vendor support so they can spend all the money on solely
paying off their last leveraged buy out. I expect product.

Hope you're not running BPCS. Support for that running on V5R4 dies
9/30/2013. I didn't see any offer of a program extension available

for

that.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.