Re: Devices created automatically

[MacWheel99@xxxxxxx]

Sorry if this already answered ... I am WAY BEHIND on my e-mail.

Check your system value WRKSYSVAL QAUTOVRT for automatic creation of virtual
devices for the benefit of hackers, such as the one using the identity QUIT
... also check user profiles that start with Q.  We do not have a QUIT ... it
could be that the hacker found QUIT on some other system and is trying every
conceivable combination in hopes of breaking into your AS/400.

We set our QAUTOVRT so no unauthorized visitors, then allow automatic
creation at the time we are in fact adding another device, then reset to
block any more visitors.

We have had innocent cases of users trying to hook up some device without
consulting with IT.  In our case, something has to be done to give the device
an identity that works on BPCS.

We also have innocent cases of some device having a flaky connection,
particularly PCs, so that the 400 loses the correct identification, then the
device gets a new handshake and a new 400 identification.

Sometimes the flaky connections are not because of hardware, but because some
PC person trying to install some software that requires changes to PC that
get in conflict with 400 connection.  Truely few people have any idea what is
going on behind the scenes of software they use whether it is on PC or on
400.  Even if user does not have the technical competence for something, that
is not to say that whatever they got added to their PC is not doing something
they not know about.

I figure that sooner or later we will have a virus targeted at PCs connected
to 400s, like the banking virus targets PC software that has banking routing
information & uses the information stored on one person PC to steal from the
bank accounts of a different person.

Invariably if something is done by someone who is not the normal person to do
the work, something gets screwed up.  We had someone recently add a new item
to our item master, for a new customer part, but not being the person who
normally adds new items, they did not know how to populate fields essential
to other applications, so we went 2 days with MRP not knowing about this
manufacturing requirement.

MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)