WSE's & Subsystem weirdness

WSE's & Subsystem weirdness

Post by RDJ » Fri, 27 Mar 1998 04:00:00



Hello there...

I'm not sure if I 'm in the right place for help on this, but...
Can someone help me with an AS/400 subsystem that intermittently grabs remote
devices when they are varied on, instead of letting them come up where they are
supposed to? (The system is a model 310, V3R2M0)

I've got two interactive subsystems, one local and one remote. They are nearly
identical, except that one (PDINTER) has the proper WSE's (Work Station
Entries)to grab the remote devices (SDLC) that are supposed to run in it. The
other subsystem (LCLINTER) does not have any WSE's that those devices qualify
for. Yet, it grabs some of them when the line is varied on and brings them up in
LCLINTER instead of letting PDINTER have them. In fact, there are NO other WSE's
that those devices will qualify for ANYWHERE on the AS/400.

I know this is probably some stupid parameter I overlooked, but I've been
looking everywhere I know, and can't find anything. The devices are all twinaxed
to a Perle 494e controller over an analog point-to-point line. The activity
levels for the subsystems are correct, I believe. And everything else looks
good. Can someone enlighten?

                                        - RDJH

=============================================================
Altered reply address... please post to group.
=============================================================

 
 
 

WSE's & Subsystem weirdness

Post by David Fosdik » Fri, 27 Mar 1998 04:00:00


You need  workstation entries for EVERY device type/name/generic name you
want in EVERY interactive subsystem. In the subsystem you want the device
allocated to use the allocation (AT) parameter of *SIGNON in command
ADDWSE.  In every other interactive subsystem (in which you do not want the
device allocated) - you define the entry but with allocation of *ENTER.  Be
careful with the system console device.  
We have six interactive subsystems and about 30 generic device names - I
wrote CL to define the entries - much more accurate than manually.  I have
a master file with  records containing the generic name and the subsystem
to which they are defined.  My CL defines all the susbsytem details and
allocates the devices according to the file and the rules above.
Hope I was a help



Quote:> Hello there...

> I'm not sure if I 'm in the right place for help on this, but...
> Can someone help me with an AS/400 subsystem that intermittently grabs
remote
> devices when they are varied on, instead of letting them come up where
they are
> supposed to? (The system is a model 310, V3R2M0)

> I've got two interactive subsystems, one local and one remote. They are
nearly
> identical, except that one (PDINTER) has the proper WSE's (Work Station
> Entries)to grab the remote devices (SDLC) that are supposed to run in it.
The
> other subsystem (LCLINTER) does not have any WSE's that those devices
qualify
> for. Yet, it grabs some of them when the line is varied on and brings
them up in
> LCLINTER instead of letting PDINTER have them. In fact, there are NO
other WSE's
> that those devices will qualify for ANYWHERE on the AS/400.

> I know this is probably some stupid parameter I overlooked, but I've been
> looking everywhere I know, and can't find anything. The devices are all
twinaxed
> to a Perle 494e controller over an analog point-to-point line. The
activity
> levels for the subsystems are correct, I believe. And everything else
looks
> good. Can someone enlighten?

>                                         - RDJH

> =============================================================
> Altered reply address... please post to group.
> =============================================================


 
 
 

WSE's & Subsystem weirdness

Post by Rich Wal » Sat, 28 Mar 1998 04:00:00


If there are no workstation entry conflicts at all (be sure to check for
xxx* entries), then it is possible the second subsystem has a device type
entry which is grabbing the device.  Although more specific entries by
heierarchy (device name, splat name, device type) are supposed to take
precedence in subsystem selection, in practice OS/400 doesn't always
enforce the rules properly.  This would allow a device type entry or a xxx*
entry to pick a device up intermittently even if a subsystem had a specific
name entry.   Hope this helps.  - Rich    

 
 
 

WSE's & Subsystem weirdness

Post by Richard Daniel » Sat, 28 Mar 1998 04:00:00



> You need  workstation entries for EVERY device type/name/generic name you
> want in EVERY interactive subsystem.

It is NOT my experience that this is necessary OR desireable.  If
someone knows about TFRJOB, I don't necessarily want them to be able to
get into QCTL (for example).

A bigger culprit may be conflict / overlap in Workstation Name entries
vs Workstation TYPE entries.  For example, WSName = DSP* for LINTER and
WSType = *all for RINTER.

Dick Daniels
WYNTH,Inc

 
 
 

1. Client Access 'drag & drop' problem

Some of my users can 'drag and drop'  or 'copy and paste' Printer Output
from the Operations Navigator and some cannot.

They are all fresh installs of Client Access Express V4R4 at Service
Pack SF60796 (current) on PC's running Windows/95 with the most recent
Service Pack installed.  BTW, I also had this problem with Client Access
V3R2.  I don't believe security is an issue.  The same user ID is able
to drag & drop at some PC's, but not others.

I can't find differences to account for some users not having this
capability.  Any hints on how to solve this problem?

____________________________________

Jeff Gunter
  IBM Certified Specialist
  AS/400 RPG Programmer
     www.AS400Guy.com
____________________________________

2. VT220 Terminal Emulator query

3. CA Operations Navigator 'drag & drop'

4. why is 780 the limit to the length of my forms

5. RPG PA's & Sr PA's in Beautiful Colorado

6. Help in Supra Express 336i

7. 7x 3477's & 7x 5394 O1B's $2100

8. Windows 98 Update

9. X-SERIES Integrated Server 'VS' X-SERIES Adapter & the INSWNTSVR command

10. \\\\\*** Mid-Atlantic Tech'l & Mfg'g Pros ***/////

11. -'s & +'s of AFP Viewer in Client Access

12. set up wse in qctl

13. S/36: WSE (Workstation Emulation) Program v.1.0 vs. Enhanced Workstation Emulation Program