|
wrote:
Open an individual system configuration ... Verify Connection is button on
the first page.
On Sun, Jul 22, 2018 at 8:49 AM, Jerry Adams <midrange@xxxxxxxx> wrote:
I kinda figured that. I do not, though, usually see the dialog box. But,
when I do see it, I know the log in is going to have "issues".
Jerry C. Adams
You are permitted in time of great danger to walk with the Devil until you
have crossed the bridge. -Balkan proverb
IBM i Programmer/Analyst
--
NMM&D
615-832-2730
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Jack
Woehr
Sent: Sunday, July 22, 2018 9:36 AM
To: Midrange Systems Technical Discussion
Subject: Re: iACS dropouts
iACS chats behind the scenes with the same host server threads that have
serviced the C and Java APIs since the 1990's.
That's what all that "authorization" noise is about.
If it won't "authorize", it's either not connecting to the host servers or
timing out on them.
On Sun, Jul 22, 2018 at 7:51 AM, Jerry Adams <midrange@xxxxxxxx> wrote:
I, too, have had an ACS session drop when I'm signed-on and away forhttps://archive.midrange.com/midrange-l.
"awhile". Sometimes not.
However, what I and our staff have experienced is the inability to
sign-on
-
period. I.e., after entering the user id and password to initially
access the system, we usually get the IBM i sign-on screen.
But occasionally there is a dialog box with "Sign On in Progress"
sometimes followed by a dialog box with "Checking Authorizations".
Then an error about a firewall blockage or such (sorry, don't have any
notes; I don't remember the message id). After pushing the 'OK'
button, I run the 'Connect' option again. Sometimes that works;
sometimes I have had to go through this sequence as many as seven [7]
times before I get the IBM i sign-on screen.
The service provider decided that re-IPLing the system weekly should
fix the problem. That was done for the first time this morning at
0400. I logged into the system at 0545. It did *not* solve the
problem.
Jerry C. Adams
Life isn't about waiting for the storm to pass. It's about learning
to dance in the rain.
IBM i Programmer/Analyst
--
NMM&D
615-832-2730
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Jack Kingsley
Sent: Sunday, July 22, 2018 4:58 AM
To: Midrange Systems Technical Discussion
Subject: Re: iACS dropouts
Take a look at the .HOD file you created for this user. Search on
keepalive. The default after I created a session is keepalive=false,
I would change it to true and see if it makes a difference.
On Sat, Jul 21, 2018 at 11:59 PM, Don Brown <DBrown@xxxxxxxxxx> wrote:
this.
Just hoping there is a simple resolution.
A user at a remote site recently received a replacement PC and we
installed iACS for 5250 access to IBMi running V7R3.
This is the only user at the site with iACS - five other users have
Client Access for Windows.
The user with iACS is the ONLY user experiencing drop outs.
The user will leave the 5250 session for a few minutes or more and
come back to a signon screen.
The option for keepalives has been ticked.
I opened a PMR with IBM and supplied comms traces from the IBMi and
iACS traces from the PC.
As this is a remote site we are using NAT which means all
connections from that site have the same source IP address and IBM
is saying that they can't interpret the trace because of this. I
have suggested we can get the source port from NETSTAT which will
allow the trace to be filtered to the required connection and have
not received a reply to
--
Has anyone else experienced this situation and been able to resolve ?
Thank you for any suggestions.
Don Brown
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our
affiliate
link: http://amzn.to/2dEadiD
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This communication including any and all
attachments
is for the intended recipient(s) only and may contain confidential and
privileged information. If you are not the intended recipient of this
communication, any disclosure, copying further distribution or use of this
communication is prohibited. If you received this communication in error,
please contact the sender and delete/destroy all copies of this
communication immediately.
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.