RE: Named (VRTDEV) devices in PASTHR

["Burns, Bryan" <Bryan_Burns@xxxxxxxxxxxx>]

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

Burns, Bryan wrote:
> 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.  
>
>   	
>
>   
QPADEV*  devices are used for Passthru and Telnet/iSeries Access. It is 
my understanding that is a  request for a session comes in without 
asking for a specific dev the system will look for a compatible already 
created and currently unused. If it doesn't find one then it will a. try 
to create a new QPADEV device or b. CHANGE a current QPADEV device. 
Maybe they are getting  changed


ISeries Access will use any compatible device in QPACTL01 not just ones that begin with QPADEV*.  Thus if device ABC is compatible, it will use it for an iSeries for Access session if it's available.