Re: Downloading Print Spool files with CA/95

   Well,  I would not make any plans that assume new function in V3R2. I 
keep being told over and over and over again, that it is not going to 
happen. 

  I am not sure that device naming is going to really fix your issue 
anyway.  I would be looking at a Firewall that supports IPsec from a 
client workstation. (IBM's SNG does).  This would allow a secure 
encripted link with positive identification of the user/workstation, an 
encripted data from point to point over the net. 

 Most of the implememntations I have seen, IBM's included, are right now 
giving the client code away (See IBM's Web Page "www.isc.raleigh.ibm.com")
that will link with there Firewall.  
 
  This seems like a much more hack proof concept than and open IP server, 
with or without names on the big bad network.  Where as the named devices 
will help with things like device associated batches in mapics, and 
internal configuration and deployment management. 

   Hope I have helped here ???

        Jeff Silberberg 
        CompuDesigns, Inc. 

On Mon, 24 Nov 1997, Vern Hamberg wrote:

> Jeff
> 
> At 01:37 PM 11/22/97 -0800, you wrote:
> >
> >> 
> >> FYI, we use the device names for a physical security scheme. With these
> >> QPADEV* things, we use the new features of the QDCRDEVD API, format
> >> DEVD0600 to get the IP address, which is as unique as the SNA device name
> >> for non-TELNET sessions. Then we convert that address to an 8-char
> >> hex-equivalent with a REXX procedure. E.g., 95.96.97.98 becomes 5F606162.
> >> We use this 8-char string as the device name.
> >> 
> >Please note:  That if you are using PPP in anyway, or NAT with a Firewall 
> >product. IP means little other than a resolve route back to the location 
> >of the packet at that point in time. Unless you are a fixed internal IP 
> >user you may not be getting the security and audit trail you really want..
> 
> Right. My ISP assigns a different address every time. We really need the
> device naming feature that's coming.
> 
> At this time, at least, we don't (officially) allow access by this means—CA
> TCP/IP over the Internet. Everything we have is local and internal—so far.
> 
> In addition, we'll have v3r2 machines for awhile. Does anyone know whether
> v3r2 will have the host server changes that'll allow the new features of CA
> v3r1m3?
> 
> Cheers
> 
> Vernon Hamberg
> Systems Software Programmer
> Old Republic National Title Insurance Company
> 400 Second Avenue South
> Minneapolis, MN 55401
> (612) 371-1111 x480
> 
> 
> +---
> | 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 MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---
> 
+---
| 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 MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---