Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Mainframe\s+networking\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Mainframe\s+networking\s*$/: 3 ]

Total 3 documents matching your query.

1. Mainframe networking (score: 1): Author: Thomas Denier <Thomas.Denier AT MAIL.TJU DOT EDU>; Date: Fri, 30 Aug 2002 11:52:38 -0400; We have a TSM 4.2.1.9 server running under OS/390 Version 2 Release 9.0. We are in the process of migrating to a new network infrastructure. The old network has Ethernet connections to Unix and Windo; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-08/msg01378.html (12,383 bytes)
2. Re: Mainframe networking (score: 1): Author: Thomas Denier <Thomas.Denier AT MAIL.TJU DOT EDU>; Date: Fri, 30 Aug 2002 14:12:30 -0400; We currently have numeric addresses in the options files. In retrospect this was a mistake. My previous job left me very uncomfortable with the idea of having the success of the backups depend on th; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-08/msg01388.html (11,571 bytes)
3. Re: Mainframe networking (score: 1): Author: Bill Boyer <bill.boyer AT VERIZON DOT NET>; Date: Fri, 30 Aug 2002 12:54:28 -0400; You keep mentioning configuring the DSM.OPT file with the "addresses". Why not use a name and let DNS resolution take over. Then to move things around, just change DNS. You could try out lots of diff; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-08/msg01389.html (13,032 bytes)

Current List: 1 - 3
Page: [1]