|
Device id specified? If so, is it varied on?
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: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/30/2015 02:21 PM
Subject: i Access Solutions - MSGSOCK007
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
System i 520, V7R1, fairly well up-to-date on PTFs.
The CEO uses I Access Solutions on his new Windows 10 laptop. Everyone
else is still using the Windows product.
About 30 minutes ago, when trying to connect a 5250 session, the session
opened up, asked for user ID/password, then, after trying to connect, he
got MSGSOCK007. I assume SOCK stands for socket. This was the first he
tried opening a 5250 session today, everything worked fine yesterday and
the days before that.
I also have i Access Solutions installed on my desktop (though not using
it
on a day to day basis). I tried opening a 5250 session, what looked like
a
green screen blinked at me . . . and that was it. Never asked for
userid/password or anything. Tried running acslaunch_win-64.exe. Nothing.
No one is having any issues with either the Windows product or Mochasoft.
Hesitant to ask him to reboot because the problem was happening on 2 PCs.
So I rebooted. No help.
Seems like it's more an IBM i issue? I have PTFs staged to apply, but
otherwise no changes to the IBM i. Actually, those PTFs have been staged
for several days now.
OTOH, at my PC it appears to do nothing. How would the IBM i be involved
in that?
Google doesn't return a lot for MSGSOCK007. Suggestions?
Thanks.
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
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.
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.