Re: IBM System i Access Emulator Troubles -- MIDRANGE-L

Check in WRKSYSVAL *DEV for the particular work station that is being
attempted to connect.

We sometimes have a glitch in our communications, such that the 400-i thinks
a particular PC is connected, but the connection is broken at the PC end &
cannot re-connect using the same id as the phantom being used by self in the
lost connection. In such cases, we have to force end the phantom session to
let the real user get back on.

Once you have this resolved, you may wish to rethink *NOMAX for QAUTOVRT
with guidance here. There is a security risk. Some hacker tries to sign on
using say QPDAV009 or whatever the latest default connection is, gets their
X wrong password guesses, security disables that session, and they keep on
guessing with QPDAV010 the 011 then 012 infinity of more tries, because on
our os version the assignment of another default session is not smart
enought to recognize that the previous one was lost for security reasons.

Maybe there was some kind of upgrade on the PC over the holidays.
MOre advanced versions of Windoze may need more advanced Emulator version.

Corey Bordelon wrote

He wasn't assigned to a Workstation ID, but we tried assigning one
and it didn't work. SYSVAL QAUTOVRT is at *NOMAX.

He can connect through telnet, JWalk, and tn5250 to get an
interactive session. He can also use iSeries Navigator as normal.
But he still can't use IBM's emulator to get an interactive session.

I didn't see any error message related to this when I tried to view those
MSGQ's.

Thank you for your help.

On Tue, Jan 6, 2009 at 7:42 PM, <macwheel99@xxxxxxxxxx> wrote:

Sometimes the error message is a bit bogus to what is really happening.

Change the communication configuration ... try a different algorithm

there.

Check SYSVAL on # of virtual connections you can have ... maybe some

other

user hit the ceiling ... try increasing the ceiling.

When we lose connections, we often change workstation communication
configuration to get another session. This creates a mountain of

formerly

used sessions that maybe ought to get deleted. WRKCFGSTS *DEV then
whatever
naming associated with that work station.

You can dump device history to an *OUTFILE then query to see how recently
used ... maybe some other user has hit on same config id as problem
connection.

Do you have any relevant error messages in places like.
DSPMSG QSYSMSG or
DSPMSG QCFGMSGQ
WRKPRB

Check the physical connections ... maybe a flakey loose frayed cable.

On my company laptop, I have to have some cables going in "just so", or

don't work. On other company PC's if user accidentally kicks back of

desk,

it can cause a cable to come loose.

Depending on how the PC connects (e.g. VPN) check that the PC is

connecting

to other stuff it supposed to connect to. For example, if not talking to
Internet, then probably not talking to VPN either.

Run standard PC housekeeping, in case spyware or some such conflict.

Corey Bordelon wrote

I ran that command. For Product 5722XW1, Feature 5101, Release
V5R4M0, the Expiration Date is *NONE. I also did DSPLICKEY
PRDID(5722XW1) LICTRM(*ALL) FEATURE(5101) to tell me that Usage
Limit is *NOMAX.

We've tried uninstalling/reinstalling iSeries Access from his PC
using the CD that was shipped with the V5R4 upgrade, twice. I've
given him my *.WS connection file to use.

iSeries Navigator works fine. He is also the only person to have
this problem, everyone else using the emulator can connect just fine,
AFAIK. The last time the emulator was working for him was before
Christmas. The only change to the system in between now and then
was adding more storage to the system.

OT: I don't know what the Queen thinks about "Googling", but I know

Google

is not happy with their name being used as a verb because it "waters
down" their trademark, similar to what has happened with Kleenex and
Band-Aid.

Thank you for your help.

On Tue, Jan 6, 2009 at 3:34 PM, Jerry Adams <Jerry@xxxxxxxxxxxxxxx>

wrote:

Googling (is that a word? What will the Queen think?) the error

message

brought up several possibilities. The most common one seemed to be

expired license key on the System i (licenses are not installed on

the

PC),

and some kind of mismatch between the client-side emulator and the
server-side base product. You can check your key expirations using

CALL

PGM(QSFWINV) PARM(*PRINT). It does not, however, tell you how many

licenses

you have, only the status.

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Corey Bordelon
Sent: Tuesday, January 06, 2009 3:20 PM
To: Midrange Systems Technical Discussion
Subject: IBM System i Access Emulator Troubles

(my apologies about the earlier incomplete message, I accidentally

hit

the

hot key that sends the message in GMail.)

My coworker is having issues with the Emulator that comes with System
i/iSeries Access for Windows. He's getting the following error when
attempting to signon to our system: "CWBLM0031 - Failure, a data

conversion

error was returned by the host server rc=1 rc=2".

This point to a page that talks about running out of licenses:

http://www-

912.ibm.com/s_dir/slkbase.NSF/1ac66549a21402188625680b0002037e/d260fd933dc02b

6686256e99004cf945?

OpenDocument<http://912.ibm.com/s_dir/slkbase.NSF/1ac66549a21402188625680b000
2037e/d260fd933dc02b6686256e99004cf945?OpenDocument>

I've never had to do anything with licenses for iSeries Access when I
installed it on a PC. I updated the licenses for the product on the

system

when we upgraded to V5R4M0 (which has a Usage Limit of *NOMAX).

Has anyone encountered this problem before, or know how to fix it?

Thanks,

-- Corey Bordelon
--
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.

--
WOW! Homepage (http://www.wowway.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.

--
WOW! Homepage (http://www.wowway.com)