Re: Why isn't a QPADEV* name used? -- MIDRANGE-L

Subject: Re: Why isn't a QPADEV* name used?
From: Pete Helgren <Pete@xxxxxxxxxx>
Date: Thu, 07 Dec 2006 08:20:00 -0700
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Seems to me that that is part of the subsystem configuration. What atrethe entries for "Work station name entries" "Work station type entries"in the subsystem running the interactive jobs (probably QINTER).


Pete Helgren

Burns, Bryan wrote:

I have some type 3477 device descriptions that are hard coded names for java based emulators. When I connect a CLI thin client and leave the device name blank, the system uses one on the hard coded names for the java based emulators instead of using a QPADEV* name. How can I get the thin clients to use a QPADEV* name?
Bryan Burns
M.I.S. Department
ECHO, Incorporated

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Why isn't a QPADEV* name used? , Burns, Bryan

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.