RE: 170 Box and virtual devices

["Paul Nelson" <nelsonp@xxxxxxxxxxxxx>]

M36 is like a separate partition, except one needs to be entirely inside
that partition to do much of anything configuration-wise. I'm glad I'm done
with the client who is still stumbling along with that system 2 years after
I told them to get off of it ASAP.

Paul Nelson
Cell 708-670-6978
Office 708-425-4198
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Carl Galgano
Sent: Monday, July 02, 2007 9:12 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: 170 Box and virtual devices

Perhaps I don't understand the difference.
cjg 


Carl J. Galgano
EDI Consulting Services, Inc.
770-422-2995
www.ediconsulting.com
 
600 Kennesaw Avenue
Suite 400 
Marietta, GA  30060

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Saturday, June 30, 2007 11:07 PM
To: Midrange Systems Technical Discussion
Subject: RE: 170 Box and virtual devices

I recall he was talking about M36

Paul Nelson
Cell 708-670-6978
Office 708-425-4198
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Carl Galgano
Sent: Saturday, June 30, 2007 6:10 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: 170 Box and virtual devices

I don't think you need another controller.
I just logged onto a client's box that has S36 running on a 170.   They have
virtual devices mapped to S36 device names.

                            Change S/36 Display IDs  
                                                     
 S/36 environment . . . . . . . . . . :   #LIBRARY   
                                                     
 Type new/changed values, press Enter.               
                                                     
 AS/400            S/36        S/36 Default          
 Display        Display ID      Printer ID           
 J1                 J1                               
 J2                 J2                               
 J3                 J3                               
 L1                 L1                               
 L2                 L2                               
 L3                 L3                               
 VC                 VC                               
 QCONSOLE           W@              P1               
 QPADEV000A         WM                               
 QPADEV000E         WQ                               
 QPADEV000F         WR                               
 QPADEV000G         WS                               

CHGS36
S36 Display IDs.

cjg 


Carl J. Galgano
EDI Consulting Services, Inc.
770-422-2995
www.ediconsulting.com
 
600 Kennesaw Avenue
Suite 400
Marietta, GA  30060

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Crooks
Sent: Thursday, June 28, 2007 5:56 PM
To: Midrange Systems Technical Discussion
Subject: 170 Box and virtual devices

Have a 170 box with 1 workstation controller on V4R4. This controller just
controls 2 consoles and a twinax printer. All the other access is done thru
TCP/IP. We need to transfer to a S/36 machine using tfrm36. If we need more
devices on the 36 side than the controller supports, do we need to get
another workstation controller even though nothing will be physically
plugged into it? I tried mapping a virtual port (ie QPADEV0099) to a port on
the 36 side and the system didn't like it. Any tricks I need to know?

 

Brian


No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.9.10/875 - Release Date: 6/27/2007
9:08 PM
 
--
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.



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