On Wed, 22 Feb 2006 21:34:08 +0100, R.S. wrote: > >Two questions: >1. Did you do it on Linux-based HMC 2.9 or earlier (OS/2-based) version ? >2. Is the CLIENT_IP optional ? Did you define console sessions also ? >
1. On Linux-based HMC 2.9 version. 2. According to the HELP in HMC: "The client's IP address can remain 0.0.0.0 or empty in order to allow any client to connect to a specific session". We establish the relationship between a particular 3270 terminal emulator session and a 2074 or OSA-ICC session (and, therefore, a MVS device number) through LU-NAME. The following are the session definitions we have used for a console session (index 27) and for a VTAM terminal session (index 31): Index: 27 (console session) State: Available CSS: 0 MIFID: 04 Dev. Number: A39A LU Name: LUA39A Client's IP: 0.0.0.0 Session Type: TN3270 DHD: Disabled RSP: Disabled RTO: 60 Index: 31 (VTAM terminal session) State: Available CSS: 0 MIFID: 04 Dev. Number: A39E LU Name: LUA39E Client's IP: 0.0.0.0 Session Type: TN3270 DHD: Disabled RSP: Disabled RTO: 60 Now, we can use any 3270 terminal emulator's session with the value LUA39A specified at its session's configuration on any PC attached to the OSA-ICC network as the MVS console with device number A39A. Rafa. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
