|
Vern Hamberg wrote: > So, it's not exactly the same as a printer session in old-time PCS. But I > believe this will be possible in the next release of CA. Maybe CA will > include an LPD server? > This should be available in v3r1m3 that will be out in 1998. It will support native IP printing instead of using ANYNET. Below I copied a message thread where I asked about native IP printing and TCP/IP device naming. Out of all the other features in the v3r1m3 Beta, these two will not be fully supported with the beta. This is per the Client Access v3r1m3 Beta web site. Danny Mc? <------ Start Forwarded Comments ------> Hi Danny, About your question: Any specifics on how the device naming and printer naming will work in Mod3 of Client Access? The answer is: It will work the same as it does for SNA currently. Thanks Juan L. Soto IBM Rochester, MN. cam3beta@us.ibm.com IBMUSM07(camod3beta) WMT ---------------------- Forwarded by Client Access Beta/Rochester/IBM on 10/28/97 05:59 PM --------------------------- Client Access Beta 10/28/97 04:14 PM To: dmcquestion@wmt.com@Internet cc: From: Client Access Beta/Rochester/IBM @ IBMUS Subject: Client Access/400 Questions Hi Danny, The Client Access/400 V3R1M3 release will be early 1998. I'm waiting for some information regarding your specific question on device naming and printer support. I hope to have some information to you soon. Thanks Juan L. Soto IBM Rochester, MN. cam3beta@us.ibm.com IBMUSM07(camod3beta) WMT nobody@sch-sp6.www.ibm.com 10/23/97 06:48 PM Please respond to nobody@sch-sp6.www.ibm.com @ internet To: Client Access Beta/Rochester/IBM@IBMUS cc: Subject: Via WWW-Mail gateway at Remote host: 207.50.181.162 [207.50.181.162] Mailed to: cam3beta@us.ibm.com Full name: Danny McQuestion Really from: dmcquestion@wmt.com company: Wright Medical Technology phone: (901) 867-4667 Client: Windows 95 Host: V3R2 Communications: TCP/IP (WinSock 1.1) Connection: Ethernet Comments: I have seen some of the enhancements in Client Access 95/NT and am itching for these to come out of beta. Two of the major ones are device naming under a native IP stack and printing using an IP stack. I've got a WAN project that I am working on and am setting for ANYNET to do printing with our dial-up users. I prefer not to have the overhead that is generated to encapsulate SNA in an IP stack especially over a 28.8 connection. Any specifics on how the device naming and printer naming will work in Mod3 of Client Access? About when can we start looking for Mod3 of Client Access to come out of Beta? I might hold off my WAN rollout depending on the response.. Thanks, Danny McQuestion Wright Medical Technology Operations Supervisor HTTP-Referer: http://www.as400.ibm.com/clientaccess/beta/w32comnt.htm Browser: Mozilla/4.0 (compatible; MSIE 4.0; Windows 95; Snap.home.1) -- This mail delivered courtesy of webmaster@www.ibm.com -- --- Danny Mc? E-mail: dcmcques@vantek.net or Click: mailto:dcmcques@vantek.net Web Page: http://www.vantek.net/pages/dcmcques/index.html -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzF0vwQAAAEEANHAlvrDaRFM5J3H/OZCdfIMWDDmJnfutn7nhd6RUJiGCey2 sCH0PBAFhonINuI/bm0ACk4gRuwoQfERuLUMeESvMjNbcnt1qrpjsPVB9GyUs8x5 kB4gTzjD5UXQOF+EnD5I9wgSsPlXeTfwLXTs4RXUdTKoYHkxhsDJ9mZy58+NAAUR tCZEYW5ueSBNY1F1ZXN0aW9uIDxkY21jcXVlc0B2YW50ZWsubmV0PokAlQMFEDF1 3jq89vGA2+K4WQEBa6gEAIxGmjwzJ0ezTPJdDKro+C55y9XVjoRWNcGSXDZHtDun /aGx16AQ98RjCOoJH48ze4keG+KsUrSa7xXaPQpbOnoAP6I6Yanq3lxSEZzkUj/V EL+C8LWDJli5dPyXXVnvyiZ4uoVpydQeL1lEzXm4xoCOMWe5pUkjc1+B3dtWb2Mw iQCVAwUQMXXYK8DJ9mZy58+NAQFWEQP/TRU0eIpW2LaHygMNeiISOcPr3YX7Gbga pdVi1oqi6ujSS5bWAE2qQG8OGpYjz25JpYBUMQgxfsaqhZ/P820CrcChqgu99ujM J0goQPr2SY5mezg9Z8rd7EVgTg0BMIVjGSTf3IAPGdH9gStzSeFDKtGEzYgn+9tx S7ZNYDwImUg= =cnWd -----END PGP PUBLIC KEY BLOCK----- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.