× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. October 2006

Re: Weird sign on problems

I think I know what the problem is. It has to do with the order in which the subsystems are started. If I understand correctly, you do not have any workstation name entries in QINTER, just workstation types.
On the other hand, you have a workstation name entry in RFINTER for QPADEV* and no workstation type entries.
If you start QINTER first, it will allocate all workstations that are varied on and that match one of the workstation types. If RFINTER is started after QINTER, it will allocate workstations by name (which takes precedence over type), but only if they have not already been allocated by QINTER. Workstations that become varied on after RFINTER is started will always be allocated to RFINTER.
If this is indeed the case, you need to check your startup program to verify that subsystem RFINTER gets varied on *before* QINTER. That way none of the QPADEV* workstations will allocate to QINTER. 

Does this make sense?



Nick_Radich@xxxxxxxxxxxxxx wrote:

Wayne,
All of the Scanners use QPADEV* as a naming convention. That is why we use QPADEV* for subsystem RFINTER.
This was setup before I got here. Maybe I will change the Scanners to start with RF*, or SCAN*. It makes more sense.
Our workstations are the User's User IDs, if they are on the network with a PC. We do have a couple of dumb twinax terminals on the Plant floor that start with DSP*, though.
For myself, my UserID is NRADIC1 and all of my Sessions start with NRADIC*. These are set up through the Client Access Communication/Configure window. 

Nick

Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct  (320) 679-6683
Toll free  (800) 388-2155  ext. 6683
Fax  (320) 679-4516
nick_radich@xxxxxxxxxxxxxx
Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 
10/25/06 03:36 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Re: Weird sign on problems
But aren't your RFINTER devices named RF*? If so, that should be the only entry under workstation names. Or are you using the same QPA* devices for both the scanners and your normal workstations? 

Nick_Radich@xxxxxxxxxxxxxx wrote:

Wayne,
In my RFINTER Subsystem, the only entry for WS Names is the generic "QPADEV*" entry.
When I went down to her PC and tried some testing, I blanked out the Workstation ID in the Configure panel of her Client Access. I then started the session back up, and the correct Signon screen we use for Scanning came up, just as it normally does. It came up in Subsystem RFINTER and used the correct Workstation ID of QPADEV****. 

Is there a reason I should not use Workstation Type Entries?
All of our scanners work fine, and have been since first use, about 3 years ago. Her Workstation is the only one that tries to jump around. 


Thanx,

Nick



Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct  (320) 679-6683
Toll free  (800) 388-2155  ext. 6683
Fax  (320) 679-4516
nick_radich@xxxxxxxxxxxxxx
Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 
10/25/06 01:49 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Re: Weird sign on problems
Nick, in RFINTER there shouldn't be any workstation type entries and there shouldn't be any workstation name entries except one that corresponds to a generic entry, i.e., RF*, for the scanning devices.
Your RF subsystem is managing to allocate normal workstation devices because of an incorrect workstation name or type entry. 

Nick_Radich@xxxxxxxxxxxxxx wrote:

For RFINTER I get  "QPADEV*" for WS name entries, and the type is 5251.
For QINTER I get no WS name entries, and types of: "CONS", 3179, 3180, 


3196, 3197, 3277, 3278, 3279, 3476, 3477, 3486 and 3487.

Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct  (320) 679-6683
Toll free  (800) 388-2155  ext. 6683
Fax  (320) 679-4516
nick_radich@xxxxxxxxxxxxxx
Léo Lefebvre <leo@xxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 
10/25/06 10:30 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Weird sign on problems
Then, check the "work station name entries" and "work station type entries" in the Sub-System description(s) 


Leo




Nick_Radich@xxxxxxxxxxxxxx wrote:
Yup, I looked at that, and it was the correct Workstation ID for her, 


RWHITE1.

thanx

Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct  (320) 679-6683
Toll free  (800) 388-2155  ext. 6683
Fax  (320) 679-4516
nick_radich@xxxxxxxxxxxxxx
"Jonathan Mason" <jonathan.mason@xxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 
10/25/06 10:19 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Weird sign on problems
Have you checked the workstation name assigned in the Client Access session 
configuration?  Click on the "Communication" menu and then select
"Configuration".  There is a field where the Workstation ID can be
specified.  If you leave it blank it will try to connect to a virtual
device.

Jonathan

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Nick_Radich@xxxxxxxxxxxxxx
Sent: 25 October 2006 16:09
To: midrange-l@xxxxxxxxxxxx
Subject: Weird sign on problems

Hello everyone,
I have a User that gets the following on her SignOn screen, at least
once 
a
week. I guess it has been happening for years, but I have only been 
here
for 2 years and just found out about it. I have never seen, nor 
heard,

anything like this.

She can eventually sign on after a few tries.

We are at V4R5 of the OS, and V4.3 of Client Access Express.

It appears that her workstation is trying to sign into the RFINTER
Subsystem, and not QINTER?  We use RFINTER for our scanning guns.  The
session ID should be RWHITE1, but it looks like CA is trying to use
QPADEV0001?

Here is a screen shot of what is on her screen.
[?3l[?7h[9;12H[?3l[?7h[1;1H[2J[0m [1m[0m [1m Sign On [0m [2;80H System .: MORA1 [3;80H Subsystem: RFINTER [4;80H Display .: QPADEV0001
[8;80H
User . . [4m[0m [4m [0m [9;80H Password [0m [0m [13;1H Welcome t o MAPICS/XA [24;39H[1m[0m [1m (C) COPYRIGHT IBM CORP. 1980, 1999. [0m [9;12H[ 9;12H[9;12H[?3l[?7h[1;1H[2J [1m[0m [1m Sign On [0m [2;80H System
.: 
MORA1
[3;80H Subsystem: RFINTER [4;80H Display .: QPADEV0001 [8;80H
User 
. . [
4m[0m [4m [0m [9;80H Password [0m [0m [13;1H
Welcome 
to MAPI
CS/XA [23;80H[1m[0m [1mCPF1296 - Sign-on information required. [9;12H[9;12H[0m
Has anyone seen anything like this? Or is this from the aliens that landed 
in North Dakota?  :-)

Any help would be greatly appreciatted.


Thanx,

Nick



Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct  (320) 679-6683
Toll free  (800) 388-2155  ext. 6683
Fax  (320) 679-4516
nick_radich@xxxxxxxxxxxxxx
--
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 thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.