Solved

iSeries Auto Device Types

Posted on 2010-11-11
1
851 Views
Last Modified: 2012-06-22
We are in the process of changing our emulation screen size from Model 2 (24x80) to Model 5 (27x132).  When we switch from Model 2 to Model 5, our users are directed to a different subsystem because their device type changes from 3477 to 5251.

Does anyone know why this would be happening? We want our users coming in from a normal PC emulation screen to come in as 3477. Only our RF devices (scan guns, forklift terminals, etc) should come in as 5251, thus putting them in the correct subsystem.

I appreciate any help you can offer.
0
Comment
Question by:Matthew Roessner
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 35

Accepted Solution

by:
Gary Patterson earned 500 total points
ID: 34113366
What emulation program are you using?  Are you using named workstations, or just using default system-generated workstation names (QPADEVxxxxx)?

When using generic device names, the system system looks at the characteristics requested by the terminal, and attempts to connect to an existing generic device that provides the desired characteristics.  Apparently the 5251 device descriptions are the "best match" that is found with the new characteristics.

I connect using IBM i Access for Windows V6R1, and have a 132 column session configured.  Auto-config created a 3477 Model FC the first time I connected (I use a named workstation, so I always get the same DEVD).

You can try varying off all of the 5251 devices, and then connecting a 132-column session to see what device type is created.  May be that if there are some existing "perfect match" devices out there, they will get selected instead of the 5251.   You still run the risk of a 5251 devd getting selected if you ever run out of "perfect match" devices, so I recommend a different solution altogether:

Far and away the simplest solution is to use named devices, and to do your subsystem routing based on workstation NAME entries rather than workstation TYPE entries.  This gives you the most control, and also allows you to assign menaningful names (if desired) to each device.  That can be handy in system management and troubleshooting, for example to know where a user is located, or what department they belong to, or that a given device is an RF scanner, etc.

You can also create a custom routing program that moves the jobs to the right subsystem, assuming you can somehow figure out how to distinguish between the RF devices and a regular user.

- Gary Patterson
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There are times when I have encountered the need to decompress a response from a PHP request. This is how it's done, but you must have control of the request and you can set the Accept-Encoding header.
Part One of the two-part Q&A series with MalwareTech.
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…
Suggested Courses

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question