RE: Named (VRTDEV) devices in PASTHR

Problem: A PC5250 session without a workstation ID sometimes uses the device name designated for the pasthr user. Then if the user tries to pasthr, she won't be able to.

Bryan Burns
iSeries Specialist
ECHO, Incorporated
Lake Zurich, Illinois

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of bvining
Sent: Friday, July 31, 2009 11:24 AM
To: Midrange Systems Technical Discussion
Subject: Re: Named (VRTDEV) devices in PASTHR

If there were earlier notes on this topic I missed them, so this may be a
repeat. But using the device name is often done to route the workstation to
a predetermined subsystem (by workstation name entry). In the case of
multi-lingual systems this is often done so that the correct (translated)
signon panel is shown (along with the correct QSYS2xxx library in the system
portion of the library list for jobs utilizing the subsystem).

What type of problem are your users experiencing? I couldn't really tell
from your note (though that may very well be in an earlier note that I
didn't see).

----- Original Message -----
From: "Burns, Bryan" <Bryan_Burns@xxxxxxxxxxxx>
To: <MIDRANGE-L@xxxxxxxxxxxx>
Sent: Friday, July 31, 2009 10:57 AM
Subject: Named (VRTDEV) devices in PASTHR

Since I began leaving the workstation ID blank on some devices, we're
having issues where these devices are using a workstation ID created
specifically for the PASTHR from our parent in Japan. These devices are
in controller QPACTL01 along with the QPAD* devices.

I thought that by recreating the PASTHR device names in the QVIRCD0001
controller our issues would disappear. But from what I could gather from
the translated Japanese, our parent was not able to PASTHR when looking
for VRT(abc) when the device was in controller QVIRCD001. Am I missing
something or would this be the expected result?

I'm wondering what named device do for pasthru anyway. Our parent uses
this command in a program:

STRPASTHR RMTLOCNAME(S1029110) VRTDEV(abc) RMTUSER(USERX) RMTPWD(xxxxxx)

What can specifying device abc accomplish? Is this a holdover from 90's
era OS? From what I understand, the OS should be able to create the
necessary device to fit the pasthru users workstation on the fly.


Bryan Burns
iSeries Specialist
ECHO, Incorporated
Lake Zurich, Illinois

--
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.