|
Nick_Radich@xxxxxxxxxxxxxx wrote:
Hi Albert, I have *SIGNON in the AT Parm in my SUBSD for RFINTER.But, why would I put my my WS Device names (QPADEV*) into the QINTER subsystem also, with *ENTER in the AT parm? What would this do?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"Albert York" <albertyork@xxxxxxxxx> Sent by: midrange-l-bounces+nick_radich=epcmolding.com@xxxxxxxxxxxx10/25/06 02:05 PM 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 This is what has worked for me. On the ADDWSE command specify *SIGNON for the AT (allocation) parameter for the RF* device in the RFINTER subsystem. Then add the same device name (RF*) in the QINTER subsystem bit specify *ENTER for allocation. Albert ----- Original Message ----- From: "Wayne McAlpine" To: midrange-l@xxxxxxxxxxxx Subject: Re: Weird sign on problems Date: Wed, 25 Oct 2006 13:49:47 -0500 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 Sent by: midrange-l-bounces@xxxxxxxxxxxx > 10/25/06 10:30 AM > Please respond to > Midrange Systems Technical Discussion > > > To > Midrange Systems Technical Discussion > 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" Sent by: >> midrange-l-bounces@xxxxxxxxxxxx >> 10/25/06 10:19 AM >> Please respond to >> Midrange Systems Technical Discussion >> >> >> To >> "'Midrange Systems Technical Discussion'" >> 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. >> >> >> >> >> >> >> > -- 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.