Archive-Date: Mon, 2 May 2005 09:39:07 -0400 Resent-Date: Mon, 02 May 2005 09:37:30 -0400 Date: Mon, 02 May 2005 14:11:30 +0100 Resent-From: Geoff Bryant From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: Off-the-wall TCPware/Multinet Question Resent-To: info-tcpware@process.com To: info-tcpware@process.com Reply-To: Info-TCPware@process.com Resent-Message-ID: <01LNS0QOIUOMBESCQC@PROCESS.COM> Message-ID: <42763512$1@news.langstoeger.at> In article , Hans Bachner writes: >David J Dachtera wrote: > >> In both UCX and TCPware, TELNET processes are created by the Job >> Controller. Thus, TELNET users cannot log in at VMS startup until STDRV >> has done the initial SET LOGINS/INTERACTIVE command. By contrast, in >> Multinet, TELNET processes are created by the MUTLINET_SERVER, and >> logins become possible immediately after Multinet is started, even >> before the startup process has finished (applications may not be ready >> for logins, user disks may not be MOUNTed yet, ...). > > >There may be a solution for this one. After UCX startup, you could add >$ SET LOGIN /INTERACTIVE=1 >$ SET LOGIN /INTERACTIVE=0 >This will at least allow users with OPER privilege to login from this >point on, while keeping standard users away from the system until the >startup driver allows logins as usual. And I thought DJD meant it the other way. No login for Multinet TELNET until SET LOGIN is done (eg. in SYSTARTUP_VMS) and not as early as now (when maybe even disks are still unmounted)... -- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist ================================================================================ Archive-Date: Tue, 3 May 2005 06:35:53 -0400 Resent-Date: Tue, 03 May 2005 06:34:20 -0400 Date: Mon, 02 May 2005 21:31:58 -0500 Resent-From: Geoff Bryant From: David J Dachtera Subject: Re: Off-the-wall TCPware/Multinet Question Resent-To: info-tcpware@process.com To: info-tcpware@process.com Reply-To: Info-TCPware@process.com Resent-Message-ID: <01LNT8MX2NRYBESCQC@PROCESS.COM> Message-ID: <4276E29E.CAE1A230@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Peter 'EPLAN' LANGSTOEGER wrote: > > In article , Hans Bachner writes: > >David J Dachtera wrote: > > > >> In both UCX and TCPware, TELNET processes are created by the Job > >> Controller. Thus, TELNET users cannot log in at VMS startup until STDRV > >> has done the initial SET LOGINS/INTERACTIVE command. By contrast, in > >> Multinet, TELNET processes are created by the MUTLINET_SERVER, and > >> logins become possible immediately after Multinet is started, even > >> before the startup process has finished (applications may not be ready > >> for logins, user disks may not be MOUNTed yet, ...). > > > > > >There may be a solution for this one. After UCX startup, you could add > >$ SET LOGIN /INTERACTIVE=1 > >$ SET LOGIN /INTERACTIVE=0 > >This will at least allow users with OPER privilege to login from this > >point on, while keeping standard users away from the system until the > >startup driver allows logins as usual. > > And I thought DJD meant it the other way. > No login for Multinet TELNET until SET LOGIN is done (eg. in SYSTARTUP_VMS) > and not as early as now (when maybe even disks are still unmounted)... Quite. Little known stuff: Until a SET LOGINS/INTER=n is done, the Job Controller will not create interactive processes. So doing as he suggests gives UCX the "Multinet Blues". What I need is for Multinet to acquire the TCPware/UCX talent of handing that off to JBC instead of MULTINET_SERVER doing the $CREPRCs. -- David J Dachtera dba DJE Systems http://www.djesys.com/ Unofficial OpenVMS Hobbyist Support Page: http://www.djesys.com/vms/support/ Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/ Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/ Coming soon: Unofficial OpenVMS Marketing Home Page ================================================================================ Archive-Date: Tue, 3 May 2005 06:36:50 -0400 Resent-Date: Tue, 03 May 2005 06:35:13 -0400 Date: Mon, 02 May 2005 21:42:13 -0500 Resent-From: Geoff Bryant From: David J Dachtera Subject: Re: Off-the-wall TCPware/Multinet Question Resent-To: info-tcpware@process.com To: info-tcpware@process.com Reply-To: Info-TCPware@process.com Resent-Message-ID: <01LNT8O2WMLEBESCQC@PROCESS.COM> Message-ID: <4276E505.AB5B110@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Jim Mehlhop wrote: > > At 09:08 PM 4/29/2005, you wrote: > >Bob Blum wrote: > > > >Hi, Bob, > > > >Can I ask two favors? > > > > 1. Please don't top-post. > > 2. Please turn off MIME. I had to begin the reply just read your > >message. It showed up in my newsreader (Netscape V4.77) in such a small > >font, I couldn't read it even with my glasses on. > > > > > > snip > > > > > > As was stated in the original posting, though, UCX/TCPIP does have > > > some advantages. And since they ported the Tru64 IP kernel over to > > > VMS when they went to TCPIP v5, it seems a lot more stable. > > > >Well, the key feature I seem to need at work is for network I/O to be > >done via buffered I/O rather than Direct I/O. We have one real > >abomination of an application that not only floods the network, it peaks > >out the CPUs with interrupt service as a result (we run Multinet - V5.0 > >died a miserable death and took the cluster with it; V4.4A is livable, > >but ...). > > Was that WITH the latest UCXDRIVER and Kernel Updates???? I'll check the latest READMEs and get with my partner at work about it. First guess time: we'll likely wait until V5.1 has been out in the field for a bit and has seen its first few rounds of ECOs - just to see what "shakes loose" outta that one. -- David J Dachtera dba DJE Systems http://www.djesys.com/ Unofficial OpenVMS Hobbyist Support Page: http://www.djesys.com/vms/support/ Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/ Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/ Coming soon: Unofficial OpenVMS Marketing Home Page ================================================================================ Archive-Date: Tue, 17 May 2005 04:22:04 -0400 Date: Tue, 17 May 2005 10:19:42 +0200 From: Godfrey Pillay Reply-To: Info-TCPware@process.com Subject: Using COPY/FTP To: info-tcpware@process.com Message-ID: MIME-Version: 1.0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi

When using Decnet copy from one node to another, the date attributes come across with the file. In other words the creation date is the same as when the file was created on the source node. I am trying to change this using COPY/FTP and the creation date chang= es to when the file is created on the destination node. Is there a way that I can preserve the dates from the source file.

Thanks in advance....

Regards

Godfrey Pillay
IDC – VMS/UNIX Syste= m Administrator
Location: IBM Park S= andton, IE1G
Tel: (011) 302-6310 &= nbsp; Fax: (011) 302-8158
Cell: 083 571 7861 Email: mailto:gpillay@za.ibm.com
================================================================================ Archive-Date: Tue, 17 May 2005 09:15:31 -0400 Date: Tue, 17 May 2005 09:14:38 -0400 From: Richard Whalen Reply-To: Info-TCPware@process.com Subject: RE: Using COPY/FTP To: info-tcpware@process.com Message-ID: <3EF96AF20489A34296050FBD5C36ECB905A445@beacon.PSC.process.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable The date is preserved when copying between two VMS systems using = TCPware, MultiNet or HGFTP as these implementations have an additional = transfer mode which transfers many of the VMS file characteristics along = with the file. If the transfer is to a non-VMS system, then there is no = way to preserve the date. -----Original Message----- From: Godfrey Pillay [mailto:gpillay@za.ibm.com] Sent: Tuesday, May 17, 2005 4:20 AM To: info-tcpware@process.com Subject: Using COPY/FTP Hi=20 When using Decnet copy from one node to another, the date attributes = come across with the file. In other words the creation date is the same = as when the file was created on the source node. I am trying to change = this using COPY/FTP and the creation date changes to when the file is = created on the destination node. Is there a way that I can preserve the = dates from the source file.=20 Thanks in advance....=20 Regards=20 =20 Godfrey Pillay=20 IDC - VMS/UNIX System Administrator=20 Location: IBM Park Sandton, IE1G=20 Tel: (011) 302-6310 Fax: (011) 302-8158=20 Cell: 083 571 7861 Email: = mailto:gpillay@za.ibm.com=20 =20 ================================================================================ Archive-Date: Tue, 17 May 2005 09:46:34 -0400 Date: Tue, 17 May 2005 15:44:04 +0200 From: Godfrey Pillay Reply-To: Info-TCPware@process.com Subject: RE: Using COPY/FTP In-Reply-To: <3EF96AF20489A34296050FBD5C36ECB905A445@beacon.PSC.process.com> To: info-tcpware@process.com Message-ID: MIME-Version: 1.0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi

The copy is between two OpenVMS/VAX systems using OpenVMS 7.2 and TCPware v5.3-2 and the date is definitely not carried over....

Regards

Godfrey Pillay
IDC – VMS/UNIX Syste= m Administrator
Location: IBM Park S= andton, IE1G
Tel: (011) 302-6310 &= nbsp; Fax: (011) 302-8158
Cell: 083 571 7861 Email: mailto:gpillay@za.ibm.com

Richard Whalen <wh= alenr@process.com>

2005/05/17 03:14 PM

Please respond to
Info-TCPware

To	info-tcpware@process.co= m
cc
Subject	RE: Using COPY/FTP

The date is preserved when copying between two VMS systems using TCPware, MultiNet or HGFTP as these implementations have an additional transfer mode which transfers many of the VMS file characteri= stics along with the file. If the transfer is to a non-VMS system, then there is no way to preserve the date. -----Original Message----- From: Godfrey Pillay [mailto:gpillay@za.ibm.com] Sent: Tuesday, May 17, 2005 4:20 AM To: info-tcpware@process.com Subject: Using COPY/FTP Hi When using Decnet copy from one node to another, the date attributes come across with the file. In other words the creation date is the same as when the file was created on the source node. I am trying to change this using COPY/FTP and the creation date changes to when the file is created on the destination node. Is there a way that I can preserve the dates from the source file. Thanks in advance.... Regards Godfrey Pillay IDC - VMS/UNIX System Administrator Location: IBM Park Sandton, IE1G Tel: (011) 302-6310 Fax: (011) 302-8158 Cell: 083 571 7861 Email: <mailto:gpillay@za.ibm.com> mailto:gp= illay@za.ibm.com
================================================================================ Archive-Date: Tue, 17 May 2005 10:05:18 -0400 Date: Tue, 17 May 2005 10:04:14 -0400 From: Richard Whalen Reply-To: Info-TCPware@process.com Subject: RE: Using COPY/FTP To: info-tcpware@process.com Message-ID: <3EF96AF20489A34296050FBD5C36ECB905A447@beacon.PSC.process.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I'd have to see a TCPDUMP of port 21 and the data port to figure out = what is going on. You should contact Process Software Technical support = and open a case. =20 =20 -----Original Message----- From: Godfrey Pillay [mailto:gpillay@za.ibm.com] Sent: Tuesday, May 17, 2005 9:44 AM To: info-tcpware@process.com Subject: RE: Using COPY/FTP Hi=20 The copy is between two OpenVMS/VAX systems using OpenVMS 7.2 and = TCPware v5.3-2 and the date is definitely not carried over....=20 Regards=20 =20 Godfrey Pillay=20 IDC - VMS/UNIX System Administrator=20 Location: IBM Park Sandton, IE1G=20 Tel: (011) 302-6310 Fax: (011) 302-8158=20 Cell: 083 571 7861 Email: = mailto:gpillay@za.ibm.com=20 =20 Richard Whalen =20 2005/05/17 03:14 PM=20 Please respond to Info-TCPware To info-tcpware@process.com=20 cc Subject RE: Using COPY/FTP =09 The date is preserved when copying between two VMS systems using = TCPware, MultiNet or HGFTP as these implementations have an additional = transfer mode which transfers many of the VMS file characteristics along = with the file. If the transfer is to a non-VMS system, then there is no = way to preserve the date. -----Original Message----- From: Godfrey Pillay [mailto:gpillay@za.ibm.com] Sent: Tuesday, May 17, 2005 4:20 AM To: info-tcpware@process.com Subject: Using COPY/FTP Hi=20 When using Decnet copy from one node to another, the date attributes = come across with the file. In other words the creation date is the same = as when the file was created on the source node. I am trying to change = this using COPY/FTP and the creation date changes to when the file is = created on the destination node. Is there a way that I can preserve the = dates from the source file.=20 Thanks in advance....=20 Regards=20 =20 Godfrey Pillay=20 IDC - VMS/UNIX System Administrator=20 Location: IBM Park Sandton, IE1G=20 Tel: (011) 302-6310 Fax: (011) 302-8158=20 Cell: 083 571 7861 Email: = mailto:gpillay@za.ibm.com=20 =20 ================================================================================ Archive-Date: Tue, 17 May 2005 10:33:55 -0400 Date: Tue, 17 May 2005 10:32:53 -0400 From: Michael Corbett Reply-To: Info-TCPware@process.com Subject: Re: Using COPY/FTP In-Reply-To: To: info-tcpware@process.com Message-ID: <428A0095.40306@process.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: Godfrey Pillay wrote: > > Hi > > When using Decnet copy from one node to another, the date attributes > come across with the file. In other words the creation date is the same > as when the file was created on the source node. I am trying to change > this using COPY/FTP and the creation date changes to when the file is > created on the destination node. Is there a way that I can preserve the > dates from the source file. > > Thanks in advance.... > Copy/ftp and ftp put or get commands will not preserve the creation date of the original file. I don't see them preserved when I do DECnet copy either - ALCOR> copy login.com alcor"corbett mycleverpassword"::login.decnet ALCOR> dir/date=all login.com,login.decnet Directory DISK$SYS_LOGIN:[LOGIN.CORBETT] LOGIN.COM;12 12-JAN-2004 08:38:19.50 30-NOV-2004 15:13:15.86 14-MAY-2005 06:00:38.20 LOGIN.DECNET;2 17-MAY-2005 10:29:22.47 17-MAY-2005 10:29:22.55 regards Mike -- +-------------------------------------------------------------------------+ Michael Corbett Email: Corbett@process.com Process Software Phone: 800 722-7770 x369 959 Concord St. 508 879-6994 x369 Framingham MA 01701-4682 FAX: 508 879-0042 ================================================================================ Archive-Date: Tue, 17 May 2005 10:50:40 -0400 Date: Tue, 17 May 2005 09:47:40 -0500 (CDT) From: Hunter Goatley Reply-To: Info-TCPware@process.com Subject: RE: Using COPY/FTP In-Reply-To: "Your message dated Tue, 17 May 2005 09:14:38 -0400" <3EF96AF20489A34296050FBD5C36ECB905A445@beacon.PSC.process.com> To: info-tcpware@process.com Message-ID: <01LOCZHMJGQE8WVYOV@goatley.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 > The date is preserved when copying between two VMS systems using > TCPware, MultiNet or HGFTP as these implementations have an additional > transfer mode which transfers many of the VMS file characteristics > along with the file. Just to clarify, STRU O VMS mode does not preserve the date. The dates are the only things that aren't preserved by that mode. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.goatley.com/hunter/ ================================================================================ Archive-Date: Tue, 17 May 2005 11:07:18 -0400 Date: Tue, 17 May 2005 11:06:23 -0400 From: Richard Whalen Reply-To: Info-TCPware@process.com Subject: RE: Using COPY/FTP To: info-tcpware@process.com Message-ID: <3EF96AF20489A34296050FBD5C36ECB905A448@beacon.PSC.process.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable >> The date is preserved when copying between two VMS systems using >> TCPware, MultiNet or HGFTP as these implementations have an = additional >> transfer mode which transfers many of the VMS file characteristics >> along with the file. > > Just to clarify, STRU O VMS mode does not preserve the date. The > dates are the only things that aren't preserved by that mode. > > Hunter > ------ > Hunter Goatley, Process Software, http://www.process.com/ > http://www.goatley.com/hunter/ I guess I've been doing mostly SFTP lately - SFTP does preserve the = dates. Rich ================================================================================ Archive-Date: Tue, 17 May 2005 12:54:31 -0400 Date: Tue, 17 May 2005 12:53:36 -0400 From: Michael Corbett Reply-To: Info-TCPware@process.com Subject: Re: Using COPY/FTP In-Reply-To: <428A0095.40306@process.com> To: info-tcpware@process.com Message-ID: <428A2190.3050100@process.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <428A0095.40306@process.com> Michael Corbett wrote: > > Copy/ftp and ftp put or get commands will not preserve the > creation date of the original file. I don't see them preserved when I do > DECnet copy either - > > ALCOR> copy login.com alcor"corbett mycleverpassword"::login.decnet > ALCOR> dir/date=all login.com,login.decnet > > Directory DISK$SYS_LOGIN:[LOGIN.CORBETT] > > LOGIN.COM;12 12-JAN-2004 08:38:19.50 30-NOV-2004 15:13:15.86 > ecified> 14-MAY-2005 06:00:38.20 > LOGIN.DECNET;2 17-MAY-2005 10:29:22.47 17-MAY-2005 10:29:22.55 > ecified> > Someone pointed out to me that if the DECnet copy command does not specify the filename in the remote file specification the creation date is preserved. FTP does not do this either when doing copy/ftp or ftp put or get commands. regards Mike -- +-------------------------------------------------------------------------+ Michael Corbett Email: Corbett@process.com Process Software Phone: 800 722-7770 x369 959 Concord St. 508 879-6994 x369 Framingham MA 01701-4682 FAX: 508 879-0042 ================================================================================ Archive-Date: Tue, 17 May 2005 16:48:58 -0400 Return-Path: Date: Tue, 17 May 2005 09:08:34 -0500 From: Sabu Zacharias Reply-To: Info-TCPware@process.com Subject: RE: RE: Using COPY/FTP To: info-tcpware@process.com Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable I would like to know the final outcome, since I also have the same issue, but was ignoring it for years!!!. Sabu Zacharias Reuters, 744 Office Parkway Drive, St. Louis, MO 63141. Phone : 314 468 3746 -----Original Message----- From: Richard Whalen [mailto:whalenr@process.com]=20 Sent: Tuesday, May 17, 2005 9:04 AM To: info-tcpware@process.com Subject: RE: Using COPY/FTP I'd have to see a TCPDUMP of port 21 and the data port to figure out what is going on. You should contact Process Software Technical support and open a case. =20 =20 -----Original Message----- From: Godfrey Pillay [mailto:gpillay@za.ibm.com] Sent: Tuesday, May 17, 2005 9:44 AM To: info-tcpware@process.com Subject: RE: Using COPY/FTP Hi=20 The copy is between two OpenVMS/VAX systems using OpenVMS 7.2 and TCPware v5.3-2 and the date is definitely not carried over....=20 Regards=20 =20 Godfrey Pillay IDC - VMS/UNIX System Administrator Location: IBM Park Sandton, IE1G=20 Tel: (011) 302-6310 Fax: (011) 302-8158=20 Cell: 083 571 7861 Email: mailto:gpillay@za.ibm.com=20 =20 Richard Whalen =20 2005/05/17 03:14 PM=20 Please respond to Info-TCPware To info-tcpware@process.com=20 cc Subject RE: Using COPY/FTP =09 The date is preserved when copying between two VMS systems using TCPware, MultiNet or HGFTP as these implementations have an additional transfer mode which transfers many of the VMS file characteristics along with the file. If the transfer is to a non-VMS system, then there is no way to preserve the date. -----Original Message----- From: Godfrey Pillay [mailto:gpillay@za.ibm.com] Sent: Tuesday, May 17, 2005 4:20 AM To: info-tcpware@process.com Subject: Using COPY/FTP Hi=20 When using Decnet copy from one node to another, the date attributes come across with the file. In other words the creation date is the same as when the file was created on the source node. I am trying to change this using COPY/FTP and the creation date changes to when the file is created on the destination node. Is there a way that I can preserve the dates from the source file.=20 Thanks in advance....=20 Regards=20 =20 Godfrey Pillay IDC - VMS/UNIX System Administrator Location: IBM Park Sandton, IE1G=20 Tel: (011) 302-6310 Fax: (011) 302-8158=20 Cell: 083 571 7861 Email: mailto:gpillay@za.ibm.com=20 =20 ----------------------------------------------------------------- Visit our Internet site at http://www.reuters.com To find out more about Reuters Products and Services visit http://www.reute= rs.com/productinfo=20 Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd. ================================================================================ Archive-Date: Wed, 18 May 2005 02:22:20 -0400 Date: Wed, 18 May 2005 08:19:54 +0200 From: Godfrey Pillay Reply-To: Info-TCPware@process.com Subject: Re: Using COPY/FTP In-Reply-To: <428A0095.40306@process.com> To: info-tcpware@process.com Message-ID: MIME-Version: 1.0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Michael

Quite true. As can be seen from the examples below. When you do not specify a filename then the attributes get copied as well...

IOSV01> copy oasis.txt iosv01"system passsword&q= uot;::oasis.tst = ;
IOSV01> dir/date=3Dall oasis.txt,oasis.tst &nb= sp;

Directory SYS$SYSROOT:[SYSMGR] &nbs= p;

OASIS.TXT;1 15-MAR-2005 10:25:53.66 15-MAR-2005 10:31:59.75 <None sp
ecified> 11-MAY-2005 17:20:47.95 <None specified> <None specified>
OASIS.TST;1 18-MAY-2005 08:15:09.68 18-MAY-2005 08:15:09.90 <None sp
ecified> <No backup recorded> <= ;None specified> <None specified>

Total of 2 files. &nb= sp;

IOSV01> copy oasis.txt iosv01"system password&qu= ot;::*
IOSV01> dir/date=3Dall oasis.txt;1,oasis.txt;2

Directory SYS$SYSROOT:[SYSMGR] &nbs= p;

OASIS.TXT;1 15-MAR-2005 10:25:53.66 15-MAR-2005 10:31:59.75 <None sp
ecified> 11-MAY-2005 17:20:47.95 <None specified> <None specified>
OASIS.TXT;2 15-MAR-= 2005 10:25:53.66 18-MAY-2005 08:16:19.62 <None sp
ecified> <No backup recorded> <= ;None specified> <None specified>

Total of 2 files. &nb= sp;
Regards

Godfrey Pillay
IDC – VMS/UNIX Syste= m Administrator
Location: IBM Park S= andton, IE1G
Tel: (011) 302-6310 &= nbsp; Fax: (011) 302-8158
Cell: 083 571 7861 Email: mailto:gpillay@za.ibm.com

Michael Corbett <c= orbett@process.com>

2005/05/17 04:32 PM

Please respond to
Info-TCPware

To	info-tcpware@process.co= m
cc
Subject	Re: Using COPY/FTP

Godfrey Pillay wrote: > > Hi > > When using Decnet copy from one node to another, the date attributes > come across with the file. In other words the creation date is the same > as when the file was created on the source node. I am trying to change > this using COPY/FTP and the creation date changes to when the file is > created on the destination node. Is there a way that I can preserve the > dates from the source file. > > Thanks in advance.... > Copy/ftp and ftp put or get commands will not preserve the creation date of the original file. I don't see them preserved when I do DECnet copy either - ALCOR> copy login.com alcor"corbett mycleverpassword"::login.d= ecnet ALCOR> dir/date=3Dall login.com,login.decnet Directory DISK$SYS=5FLOGIN:[LOGIN.CORBETT] LOGIN.COM;12 12-JAN-2004 08:38:19.50 30-N= OV-2004 15:13:15.86 <None sp ecified> 14-MAY-2005 06:00:38.20 <None specified> <None specified> LOGIN.DECNET;2 17-MAY-2005 10:29:22.47 17-MAY-20= 05 10:29:22.55 <None sp ecified> <No backup recorded> <None specified> <None specified> regards Mike -- +-------------------------------------------------------------------------+= Michael Corbett Email: Corbett@process.com Process Software Phone: 800 722-7770 x369 959 Concord St. 508 879-6994 x369 Framingham MA 01701-4682 FAX: 508 879-0042
================================================================================ Archive-Date: Fri, 20 May 2005 02:54:49 -0400 Date: Fri, 20 May 2005 08:52:06 +0200 From: =?iso-8859-15?Q?Vorl=E4nder=2C_Martin?= Reply-To: Info-TCPware@process.com Subject: US-CERT Vulnerability Note VU#637934 To: info-multinet@process.com, info-tcpware@process.com Message-ID: <4af01a21f821a5134b1d9d72f92ee0cc428d8921@pdv-systeme.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable Hi, are TCPware / MultiNet vulnerable to this? http://www.kb.cert.org/vuls/id/637934 See also http://www.kb.cert.org/vuls/id/JGEI-6ABPLK ; TCPware isn't even listed... According to http://www.kb.cert.org/vuls/id/JGEI-6ABPEF, "HP's operating system products are not vulnerable". cu, Martin --=20 | Martin Vorlaender | OpenVMS rules! OpenVMS: Where do you | work: mv@pdv-systeme.de want to BE today? | http://www.pdv-systeme.de/users/martinv/ | home: martin@radiogaga.harz.de ================================================================================ Archive-Date: Fri, 20 May 2005 09:55:32 -0400 Date: Fri, 20 May 2005 09:54:17 -0400 From: Richard Whalen Reply-To: Info-TCPware@process.com Subject: RE: US-CERT Vulnerability Note VU#637934 To: info-multinet@process.com, info-tcpware@process.com CC: cert@cert.org Message-ID: <3EF96AF20489A34296050FBD5C36ECB9188209@beacon.PSC.process.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable MultiNet 4.4 and 5.0 validate the sequence numbers before recording the = timestamp, hence MultiNet is not vulnerable. TCPware does not do timestamp processing, hence TCPware is not = vulnerable. ---------------------- Richard Whalen Process Software 508-879-6994