Archive-Date: Fri, 5 Nov 1999 11:38:26 -0400 From: "Eddy Crompton" Reply-To: Info-TCPware@process.com Subject: Printing to DeskJet printers from VMS 5.5 via TCPWARE 5.0 Date: Fri, 5 Nov 1999 16:28:51 -0000 Message-ID: <7vv0f2$si4$1@news5.svr.pol.co.uk> To: Info-TCPware@PROCESS.COM We have a VAX/VMS Ver. 5.5 system connected to NT Servers and printers on a LAN using TCPWARE 5.0-4. I have used the @TCPWARE:CNFNET LPS utility to configure HP Laserjet printers (configured to use VMS formatting option rather than LPD). I am now trying to do the same with HP Deskjet 895Cxi printers, connected via a JetDirect box. When configured with the VMS formatting option, the print job hanges at the printer (the Resume button can be used to release it) - the print then comes out correctly - it also comes out if you wait for 10 minutes! Another interesting(?) feature is that if you print 2 files, they are concatenated and appear as if one print job. It would seem that some control character is not being sent with the print job (FF ?) to indicate the end of job. If you append a FF to the print job it does work, but we really want to avoid having to modify the hysical print files programatically. I have tried sending PCL commands with the print job to try modifying the behaviour (adding them to the file, and via the DEFINE/FORM mechanism with VMS queue libraries) but they don't achieve the desired results. If you have any experience of similar problems, or have actually got this to work with any printers other than HP Laserjets, I would appreciate your comments. Regards, Eddy Crompton ================================================================================ Archive-Date: Fri, 5 Nov 1999 11:48:40 -0400 From: "Carl G. Cioffi" Reply-To: Info-TCPware@process.com To: Subject: RE: Printing to DeskJet printers from VMS 5.5 via TCPWARE 5.0 Date: Fri, 5 Nov 1999 11:46:35 -0500 Message-ID: <000601bf27ad$527136c0$13faff0a@test.splusnet> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit In-Reply-To: <7vv0f2$si4$1@news5.svr.pol.co.uk> Eddy, Although I have not had experience with the JetDirect card in this scenario I would assume that you need to have the /DEFAULT=(FEED) switch set on you VMS queue. I believe this will send a form feed at the end of the job. Regards, Carl Cioffi Carl@canvaslink.com ================================================================================ Archive-Date: Fri, 5 Nov 1999 11:56:32 -0400 From: Tim_Geldard@kerry-ingredients.co.uk Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com CC: eddy@visionit.freeserve.co.uk Message-ID: <80256820.005CFCF0.00@mailhost.kerry-ingredients.co.uk> Date: Fri, 5 Nov 1999 16:55:47 +0000 Subject: Re: Printing to DeskJet printers from VMS 5.5 via TCPWARE 5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Try using the additional qualifier /SEPARATE=(RESET=(RESET)) I think this forces a form feed.... Certainly can work with our non Laserjet 4 printers Cheers, Tim "Eddy Crompton" on 05/11/99 16:28:51 Please respond to Info-TCPware@process.com To: Info-TCPware@PROCESS.COM cc: (bcc: Tim Geldard/Aylesbury/Ingredients/Kerry) Subject: Printing to DeskJet printers from VMS 5.5 via TCPWARE 5.0 We have a VAX/VMS Ver. 5.5 system connected to NT Servers and printers on a LAN using TCPWARE 5.0-4. I have used the @TCPWARE:CNFNET LPS utility to configure HP Laserjet printers (configured to use VMS formatting option rather than LPD). I am now trying to do the same with HP Deskjet 895Cxi printers, connected via a JetDirect box. When configured with the VMS formatting option, the print job hanges at the printer (the Resume button can be used to release it) - the print then comes out correctly - it also comes out if you wait for 10 minutes! Another interesting(?) feature is that if you print 2 files, they are concatenated and appear as if one print job. It would seem that some control character is not being sent with the print job (FF ?) to indicate the end of job. If you append a FF to the print job it does work, but we really want to avoid having to modify the hysical print files programatically. I have tried sending PCL commands with the print job to try modifying the behaviour (adding them to the file, and via the DEFINE/FORM mechanism with VMS queue libraries) but they don't achieve the desired results. If you have any experience of similar problems, or have actually got this to work with any printers other than HP Laserjets, I would appreciate your comments. Regards, Eddy Crompton ********************************************************************** This message, including any attachments, is confidential, privileged and for the sole benefit of the person(s) to whom it was intended to be addressed. If you receive it in error, please delete it from your system, make no copies of it, do not disclose its contents to any third party or use it for your own or any other person's benefit. Please advise "postmaster@kerry-ingredients.co.uk" of its receipt as soon as possible. This footnote also confirms that this email message has been swept by for the presence of computer viruses. ********************************************************************** ================================================================================ Archive-Date: Fri, 5 Nov 1999 16:30:07 -0400 Message-ID: <0994250321A0D2118A5D00062B001CCBFB5C3D@GALAXY> From: Jim Hunter Reply-To: Info-TCPware@process.com To: Info-TCPware@PROCESS.COM Subject: Configuring an LPS queue to match the LPR "-l" option Date: Fri, 5 Nov 1999 15:29:37 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" I'm printing a VFC file with print file carriage control to an LPD server. Using the LPR command from the VMS command prompt with the "-l" option (do not convert to Stream-LF), the output looks great. What I want to do now is to configure an LPS queue on the VMS system to pass the "-l" option so all the user enters is: $PRINT/QUE=LPS1 file-name I thought the way to go was to use the /PARAMETER qualifier. So I configured the LPS queue with the additional qualifier of: /PARAMETERS=("","l") But it did not work. Is my syntax wrong, or what? I'm using the LPD symbiont. James A. Hunter Network Manager American Agrisurance email: jhunter@amag.com voice: (712) 325-5381 ================================================================================ Archive-Date: Mon, 8 Nov 1999 02:12:20 -0400 Message-ID: <003001bf29ba$2691f9e0$4b28010a@pcn584.thomassen-int.nl> Reply-To: Info-TCPware@process.com From: "Eddie Vercauteren" To: Subject: Re: Printing to DeskJet printers from VMS 5.5 via TCPWARE 5.0 Date: Mon, 8 Nov 1999 08:23:27 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hello eddie I think we have had the same problem. we fixed this problem with seperate=(reset=(reset)) the reset module has the syntax : ]VMS;2\PE\ try this , i hope this will help you -----Original Message----- From: Eddy Crompton To: Info-TCPware@PROCESS.COM Date: vrijdag 5 november 1999 17:48 Subject: Printing to DeskJet printers from VMS 5.5 via TCPWARE 5.0 >We have a VAX/VMS Ver. 5.5 system connected to NT Servers and printers on a >LAN using TCPWARE 5.0-4. >I have used the @TCPWARE:CNFNET LPS utility to configure HP Laserjet >printers (configured to use VMS formatting option rather than LPD). I am now >trying to do the same with HP Deskjet 895Cxi printers, connected via a >JetDirect box. > >When configured with the VMS formatting option, the print job hanges at the >printer (the Resume button can be used to release it) - the print then comes >out correctly - it also comes out if you wait for 10 minutes! Another >interesting(?) feature is that if you print 2 files, they are concatenated >and appear as if one print job. >It would seem that some control character is not being sent with the print >job (FF ?) to indicate the end of job. > >If you append a FF to the print job it does work, but we really want to >avoid having to modify the hysical print files programatically. > >I have tried sending PCL commands with the print job to try modifying the >behaviour (adding them to the file, and via the DEFINE/FORM mechanism with >VMS queue libraries) but they don't achieve the desired results. > >If you have any experience of similar problems, or have actually got this to >work with any printers other than HP Laserjets, I would appreciate your >comments. > >Regards, >Eddy Crompton > > > > ================================================================================ Archive-Date: Mon, 8 Nov 1999 15:20:37 -0400 From: "Eddy Crompton" Reply-To: Info-TCPware@process.com Subject: Re: Printing to DeskJet printers from VMS 5.5 via TCPWARE 5.0 Date: Mon, 8 Nov 1999 20:06:17 -0000 Message-ID: <807ai4$h9f$1@news6.svr.pol.co.uk> To: Info-TCPware@PROCESS.COM Thanks to all concerned for your help, I have used the /SEPARATOR=(RESET=module) qualifier on the INIT/QUEUE command, where the module just contains the reset PCL code (E) and that does print the job, and I have tested that you can queue requests from VAX and Windows clients to the printer without problems. However, after sending a job from the VAX, the Resume button (on the Deskjet 895cxi) still flashes - but this does not have any adverse affect on the operation of the printing (you don't need to press it to print). On the HP 2500C, the corresponding situation means theat the displayed message is "PROCESSING JOB". In both cases, there is a timeout which causes the printer to reset OK. I would regard this as a (successful) workaround. Ideally I would like to avoid having the printer displaying the flashing Resmue button, so if there are any other special PCL codes that anyone could suggest then I would be grateful. Regards, Eddy Crompton Eddy Crompton wrote in message <7vv0f2$si4$1@news5.svr.pol.co.uk>... >We have a VAX/VMS Ver. 5.5 system connected to NT Servers and printers on a >LAN using TCPWARE 5.0-4. >I have used the @TCPWARE:CNFNET LPS utility to configure HP Laserjet >printers (configured to use VMS formatting option rather than LPD). I am now >trying to do the same with HP Deskjet 895Cxi printers, connected via a >JetDirect box. > >When configured with the VMS formatting option, the print job hanges at the >printer (the Resume button can be used to release it) - the print then comes >out correctly - it also comes out if you wait for 10 minutes! Another >interesting(?) feature is that if you print 2 files, they are concatenated >and appear as if one print job. >It would seem that some control character is not being sent with the print >job (FF ?) to indicate the end of job. > >If you append a FF to the print job it does work, but we really want to >avoid having to modify the hysical print files programatically. > >I have tried sending PCL commands with the print job to try modifying the >behaviour (adding them to the file, and via the DEFINE/FORM mechanism with >VMS queue libraries) but they don't achieve the desired results. > >If you have any experience of similar problems, or have actually got this to >work with any printers other than HP Laserjets, I would appreciate your >comments. > >Regards, >Eddy Crompton > > > ================================================================================ Archive-Date: Mon, 8 Nov 1999 18:49:08 -0400 From: Chris Townley Subject: DECEDI V 3.2 Date: Mon, 8 Nov 1999 23:37:38 +0000 Message-ID: Reply-To: Info-TCPware@process.com MIME-Version: 1.0 To: Info-TCPware@PROCESS.COM I have just been asked to step into an overrunning project to upgrade our antique DECEDI 1.3 to the current version 3.2 for Y2K compliance. We seem to have a conflict DECEDI and our standard TCP stack - TCPWare from Process software. I know the SPD states quite clearly that DECEDI 3.2 needs UCX, but I understand that TCPWare can cope with that at an application level. However there are problems with a command file that issues UCX commands directly. Our contact with a UK sales outlet wants to charge consultancy rates to sort this out. I cannot believe that this has not come out before - is there anybody out there running DECEDI with a TCPWare stack ? If there are, I would be interested to find out what problems there are, and what the workarounds are. Any comments would be appreciated, either here or by e-mail. TIA -- Chris Townley chris@townleyc.demon.co.uk townleyc@spicers.ltd.uk ================================================================================ Archive-Date: Tue, 9 Nov 1999 11:00:50 -0400 Message-ID: <382844EF.AE76E132@PROCESS.COM> Date: Tue, 09 Nov 1999 10:59:43 -0500 From: Michael Corbett Reply-To: Info-TCPware@process.com MIME-Version: 1.0 To: info-tcpware@process.com Subject: RE: DECEDI V 3.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > I have just been asked to step into an overrunning project to upgrade > our antique DECEDI 1.3 to the current version 3.2 for Y2K compliance. > > We seem to have a conflict DECEDI and our standard TCP stack - TCPWare > from Process software. I know the SPD states quite clearly that DECEDI > 3.2 needs UCX, but I understand that TCPWare can cope with that at an > application level. However there are problems with a command file that > issues UCX commands directly. Our contact with a UK sales outlet wants > to charge consultancy rates to sort this out. > > I cannot believe that this has not come out before - is there anybody > out there running DECEDI with a TCPWare stack ? > > If there are, I would be interested to find out what problems there are, > and what the workarounds are. > > Any comments would be appreciated, either here or by e-mail. > I haven't come across DECEDI myself but if you post the UCX commands that it uses and I can give you the proper TCPware commands to replace them with. Regards Mike -- +-------------------------------------------------------------------------+ Michael Corbett Email: Corbett@process.com Process Software Corporation Phone: 800 722-7770 x369 959 Concord St. 508 879-6994 x369 Framingham MA 01701-4682 FAX: 508 879-0042 ================================================================================ Archive-Date: Tue, 9 Nov 1999 11:13:26 -0400 Message-ID: <01BE9872614BD311BB8000805F9F4A85BC9BBB@norma.mfs.com> From: "Robert, Andrew" Reply-To: Info-TCPware@process.com To: Subject: RE: DECEDI V 3.2 Date: Tue, 9 Nov 1999 11:12:49 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit It sounds like you need to load the UCX driver to emulate the DEC TCP/IP services for VMS $QIO interface. I am not sure what the equivalent command would be for TCPWARE but in Multinet, it would be: NET-CONFIG> set load-ucx-driver true Regards, Andrew Robert Senior Systems Analyst Massachusetts Financial Services Phone: 617-954-5882 -----Original Message----- From: Michael Corbett [mailto:corbett@PROCESS.COM] Sent: Tuesday, November 09, 1999 11:00 AM To: info-tcpware@process.com Subject: RE: DECEDI V 3.2 > I have just been asked to step into an overrunning project to upgrade > our antique DECEDI 1.3 to the current version 3.2 for Y2K compliance. > > We seem to have a conflict DECEDI and our standard TCP stack - TCPWare > from Process software. I know the SPD states quite clearly that DECEDI > 3.2 needs UCX, but I understand that TCPWare can cope with that at an > application level. However there are problems with a command file that > issues UCX commands directly. Our contact with a UK sales outlet wants > to charge consultancy rates to sort this out. > > I cannot believe that this has not come out before - is there anybody > out there running DECEDI with a TCPWare stack ? > > If there are, I would be interested to find out what problems there are, > and what the workarounds are. > > Any comments would be appreciated, either here or by e-mail. > I haven't come across DECEDI myself but if you post the UCX commands that it uses and I can give you the proper TCPware commands to replace them with. Regards Mike -- +-------------------------------------------------------------------------+ Michael Corbett Email: Corbett@process.com Process Software Corporation Phone: 800 722-7770 x369 959 Concord St. 508 879-6994 x369 Framingham MA 01701-4682 FAX: 508 879-0042 ================================================================================ Archive-Date: Tue, 9 Nov 1999 11:59:08 -0400 Message-ID: <38285295.78852F19@PROCESS.COM> Date: Tue, 09 Nov 1999 11:57:57 -0500 From: Michael Corbett Reply-To: Info-TCPware@process.com MIME-Version: 1.0 To: info-tcpware@process.com Subject: RE: DECEDI V 3.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > It sounds like you need to load the UCX driver to emulate the DEC TCP/IP > services for VMS $QIO interface. > I am not sure what the equivalent command would be for TCPWARE but in > Multinet, it would be: > > NET-CONFIG> set load-ucx-driver true > The UCX driver is loaded by default in TCPware. If you have a BG0 device then all that has been done. regards Mike -- +-------------------------------------------------------------------------+ Michael Corbett Email: Corbett@process.com Process Software Corporation Phone: 800 722-7770 x369 959 Concord St. 508 879-6994 x369 Framingham MA 01701-4682 FAX: 508 879-0042 ================================================================================ Archive-Date: Tue, 9 Nov 1999 19:27:41 -0400 From: Chris Townley Subject: Re: DECEDI V 3.2 Date: Wed, 10 Nov 1999 00:21:21 +0000 Message-ID: Reply-To: Info-TCPware@process.com MIME-Version: 1.0 To: Info-TCPware@PROCESS.COM In article <382844EF.AE76E132@PROCESS.COM>, Michael Corbett wrote: > >> I have just been asked to step into an overrunning project to upgrade >> our antique DECEDI 1.3 to the current version 3.2 for Y2K compliance. >> >> We seem to have a conflict DECEDI and our standard TCP stack - TCPWare >> from Process software. I know the SPD states quite clearly that DECEDI >> 3.2 needs UCX, but I understand that TCPWare can cope with that at an >> application level. However there are problems with a command file that >> issues UCX commands directly. Our contact with a UK sales outlet wants >> to charge consultancy rates to sort this out. >> >> I cannot believe that this has not come out before - is there anybody >> out there running DECEDI with a TCPWare stack ? >> >> If there are, I would be interested to find out what problems there are, >> and what the workarounds are. >> >> Any comments would be appreciated, either here or by e-mail. >> > >I haven't come across DECEDI myself but if you post the UCX commands that it >uses and I can give you the proper TCPware commands to replace them with. > Sounds good to me - I was intending to sit down with the manual... The only command I need to sort is as follows: $ ucx set service 'this_service' /port='this_service_port' - /protocol=tcp /user=DECEDI /process='this_process_name' - /file=dummy_startup_file Where this_service = decedi_csf (for example) this_service_port = 5150 this_process_name = decedi$csf There are 3 of them. Doesnt look that difficult, but I would otherwise need to RTFM to sort out the details. TIA -- Chris Townley chris@townleyc.demon.co.uk townleyc@spicers.ltd.uk ================================================================================ Archive-Date: Wed, 10 Nov 1999 02:05:48 -0400 From: "Martin Vorlaender" Reply-To: Info-TCPware@process.com To: CC: Subject: RE: DECEDI V 3.2 Date: Wed, 10 Nov 1999 08:03:34 +0100 Message-ID: <000001bf2b49$b56d0110$0d0110ac@pcmv2.pdv.intern> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit In-Reply-To: > Michael Corbett wrote: > > application level. However there are problems with a command file that > > issues UCX commands directly. > > >I haven't come across DECEDI myself but if you post the UCX commands that it > >uses and I can give you the proper TCPware commands to replace them with. > > Sounds good to me - I was intending to sit down with the manual... > > The only command I need to sort is as follows: > > $ ucx set service 'this_service' /port='this_service_port' - > /protocol=tcp /user=DECEDI /process='this_process_name' - > /file=dummy_startup_file You need to add a line 'this_service_port' 'this_service'/tcp to TCPWARE:SERVICES. (this replaces the /port part). The service can then be set up by $ NETCU ADD SERVICE 'this_service' BG_TCP /USERNAME=DECEDI - /PROCESS_NAME='this_process-name' /INPUT=dummy_startup_file (Hope I didn't forget anything - I don't setup services every day) cu, Martin -- | Martin Vorlaender VMS & WNT programmer OpenVMS is today | work: mv@pdv-systeme.de what Microsoft wants | http://www.pdv-systeme.de/users/martinv/ Windows NT 8.0 to be! | home: martin@radiogaga.harz.de ================================================================================ Archive-Date: Sat, 13 Nov 1999 14:32:38 -0400 From: martin@RADIOGAGA.HARZ.DE (Martin Vorlaender) Subject: named OPCOM messages Message-ID: <382d9275.524144494f47414741@radiogaga.harz.de> Date: Sat, 13 Nov 1999 17:31:49 +0100 Reply-To: Info-TCPware@process.com To: Info-TCPware@PROCESS.COM Hi! We're running TCPware 5.3-3 on OpenVMS/Alpha 7.1. Now and then I see the following in NETCP.LOG %%%%%%%%%%%% NAMED 11-NOV-1999 23:25:34.59 %%%%%%%%%%%% %TCPWARE_NAMED-I-ns_resp: query(www.xxx.de) contains our address (ns2.pdv-systeme.de:194.163.127.179) learnt (A=pdv-systeme.de:NS=193.141.40.42) %%%%%%%%%%%% NAMED 12-NOV-1999 02:09:15.84 %%%%%%%%%%%% %TCPWARE_NAMED-I-UNEXPSRC, Response from unexpected source ([127.0.0.1].14022) www.xxx.de was formerly domain name served by us, but has been retired some time ago. What's going on here? Does someone try to fake a DNS record? If so, what can be done against it? cu, Martin -- | Martin Vorlaender | VMS & WNT programmer OpenVMS: When you | work: mv@pdv-systeme.de KNOW where you want | http://www.pdv-systeme.de/users/martinv/ to go today. | home: martin@radiogaga.harz.de ================================================================================ Archive-Date: Wed, 17 Nov 1999 10:51:43 -0400 From: "Wim" Reply-To: Info-TCPware@process.com Subject: print problem Date: Wed, 17 Nov 1999 16:33:42 +0100 Sender: bull@diode.rdc.nl Message-ID: <80uht0$kj1$1@news1.xs4all.nl> To: Info-TCPware@PROCESS.COM Please help me on the folowing I set up a new printer queue. We have done this many times. But now I cant print the job says it is processing for a long time and then I see this error %TCPWARE_TSSYM-W-CONNERR, error connecting to 192.168.1.57,9100 for queue PR208 -TCPWARE-W-ETIMEDOUT, connection timed out I can ping to the ip adress. What can I do to solve this problem? Many thanks in advance -- Wim Knoll, RDC Datacentrum B.V. De Klencke 12, P.O. Box 74707 1070 BS Amsterdam, The Netherlands Phone 31 - 205497171 Fax 31-206611526 ================================================================================ Archive-Date: Wed, 17 Nov 1999 11:03:47 -0400 Subject: Re: print problem From: eplan@kapsch.net (Peter LANGSTOEGER) Reply-To: Info-TCPware@process.com Message-ID: <3832ce1a@news.kapsch.co.at> Date: 17 Nov 1999 16:47:38 +0100 To: Info-TCPware@PROCESS.COM In article <80uht0$kj1$1@news1.xs4all.nl>, "Wim" writes: >I set up a new printer queue. We have done this many times. >But now I cant print the job says it is processing for a long time and then >I see this error > >%TCPWARE_TSSYM-W-CONNERR, error connecting to 192.168.1.57,9100 for queue >PR208 >-TCPWARE-W-ETIMEDOUT, connection timed out > >I can ping to the ip adress. Can you TELNET to the (TCP) port 9100 of this ip address ? Or is the HPJD (is it a HPJD ?) rejecting the connection, because the printer is busy/offline/disconnected/out-of-paper/out-of-toner ? -- Peter "EPLAN" LANGSTOEGER Tel. +43 1 81111-2651 Network and OpenVMS system manager Fax. +43 1 81111-888 FBFV/Information Services E-mail eplan@kapsch.net <<< KAPSCH AG Wagenseilgasse 1 PSImail PSI%(0232)281001141::EPLAN A-1121 VIENNA AUSTRIA "I'm not a pessimist, I'm a realist" "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998 ================================================================================ Archive-Date: Wed, 17 Nov 1999 11:30:13 -0400 Message-ID: <45C82258A1B2D111892500805FCC9B0D022E945D@nt05.wstf.nasa.gov> From: "Peebles, Darwin" Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com Subject: RE: print problem Date: Wed, 17 Nov 1999 09:30:27 -0700 MIME-Version: 1.0 Content-Type: text/plain Hello, I'm using TCPWARE V5.3-3 on OpenVMS Alpha V7.2-1. This is how I establish my TCP/IP print queues. I also make sure that the printer name (in my example PEPE) is either DNS resolved or in my local host table. I have ran into troubles if it can't figure out what the name is (it won't print to it). <<...>> I define the form "NOWIDTH" by the following command: DEFINE/FORM/WIDTH=132/LENGTH=66/NOTRUNCATE/NOWRAP/STOCK=DEFAULT NOWIDTH 3 I have never had this problem with TCPWARE, but I did have it with Digital TCP/IP (UCX). There were some logicals that you could define, that would rearrange the time-out and allow things to work. Hope this somehow helps. Darwin "Peebs" Peebles Sr. Scientific Programmer/Analyst AlliedSignal Technical Services Corporation NASA, JSC, White Sands Test Facility Mail Stop 101P P.O. Box 20 Las Cruces, NM 88004 Phone: 505-524-5619 Fax: 505-524-5544 E-mail: dpeebles@wstf.nasa.gov > ---------- > From: Wim[SMTP:wim@wanadoo.nl] > Reply To: Info-TCPware@process.com > Sent: Wednesday, November 17, 1999 8:33 AM > To: Info-TCPware@PROCESS.COM > Subject: print problem > > Please help me on the folowing > > > I set up a new printer queue. We have done this many times. > But now I cant print the job says it is processing for a long time and > then > I see this error > > %TCPWARE_TSSYM-W-CONNERR, error connecting to 192.168.1.57,9100 for queue > PR208 > -TCPWARE-W-ETIMEDOUT, connection timed out > > I can ping to the ip adress. > > What can I do to solve this problem? > > Many thanks in advance > > > -- > Wim Knoll, RDC Datacentrum B.V. > De Klencke 12, P.O. Box 74707 > 1070 BS Amsterdam, The Netherlands > Phone 31 - 205497171 Fax 31-206611526 > > > ================================================================================ Archive-Date: Wed, 17 Nov 1999 11:47:46 -0400 Message-ID: From: "Garrido, Ramon, Mr, HQAFCEE" Reply-To: Info-TCPware@process.com To: "'Info-TCPware@process.com'" Subject: RE: print problem Date: Wed, 17 Nov 1999 10:46:41 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF311B.55A965CA" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF311B.55A965CA Content-Type: text/plain; charset="iso-8859-1" Try to telnet to that printer. TELNET 192.168.1.57 9100 Then type away and do ^z to exit. It should print the message you just typed-in. If that works then try to look at the status of the process, device, etc.. for that printer. -----Original Message----- From: Wim [mailto:wim@wanadoo.nl] Sent: Wednesday, November 17, 1999 9:34 AM To: Info-TCPware@process.com Subject: print problem Please help me on the folowing I set up a new printer queue. We have done this many times. But now I cant print the job says it is processing for a long time and then I see this error %TCPWARE_TSSYM-W-CONNERR, error connecting to 192.168.1.57,9100 for queue PR208 -TCPWARE-W-ETIMEDOUT, connection timed out I can ping to the ip adress. What can I do to solve this problem? Many thanks in advance -- Wim Knoll, RDC Datacentrum B.V. De Klencke 12, P.O. Box 74707 1070 BS Amsterdam, The Netherlands Phone 31 - 205497171 Fax 31-206611526 ------_=_NextPart_001_01BF311B.55A965CA Content-Type: text/html; charset="iso-8859-1" RE: print problem

Try to telnet to that printer. TELNET  192.168.1.57 9100
Then type away and do ^z to exit. It should print the message you just typed-in.
If that works then try to look at the status of the process, device, etc.. for that printer.

-----Original Message-----
From: Wim [mailto:wim@wanadoo.nl]
Sent: Wednesday, November 17, 1999 9:34 AM
To: Info-TCPware@process.com
Subject: print problem


Please help me on the folowing


I set up a new printer queue. We have done this many times.
But now I cant print the job says it is processing for a long time and then
I see this error

%TCPWARE_TSSYM-W-CONNERR, error connecting to 192.168.1.57,9100 for queue
PR208
-TCPWARE-W-ETIMEDOUT, connection timed out

I can ping to the ip adress.

What can I do to solve this problem?

Many thanks in advance


--
Wim Knoll, RDC Datacentrum B.V.
De Klencke 12, P.O. Box 74707
1070 BS Amsterdam, The Netherlands
Phone 31 - 205497171   Fax 31-206611526


------_=_NextPart_001_01BF311B.55A965CA-- ================================================================================ Archive-Date: Wed, 17 Nov 1999 13:08:33 -0400 Message-ID: <42E8EAD18405D311B9D90050047A71701D05AB@RANTXCHG01> From: "Mah, Lee" Reply-To: Info-TCPware@process.com To: "'Info-TCPware@process.com'" Subject: RE: print problem Date: Wed, 17 Nov 1999 11:07:25 -0700 MIME-Version: 1.0 Content-Type: text/plain We use HP network cards in our printers. Telnet into your printer. Enter the command to show the current settings. Look for "Idle Timeout" (or an equivalent to it if you are not using HP cards). I have had to increase the parameter "Idle Timeout" to 1200 seconds on some cards which process large print jobs (45K block report files). --- Lee Lee Y T Mah Capital Health, RAH Site Email: lytmah@cha.ab.ca Information Systems, CSC 417 Phone: (780) 477-4725, 477-4233 10240 Kingsway NW Fax: (780) 491-5119, 491-5619 Edmonton, AB, CAN T5H 3V9 > ---------- > From: Garrido, Ramon, Mr, > HQAFCEE[SMTP:Ramon.Garrido@hqafcee.brooks.af.mil] > Reply To: Info-TCPware@process.com > Sent: Wednesday, November 17, 1999 9:46 AM > To: 'Info-TCPware@process.com' > Subject: RE: print problem > > Try to telnet to that printer. TELNET 192.168.1.57 9100 > Then type away and do ^z to exit. It should print the message you just > typed-in. > If that works then try to look at the status of the process, device, etc.. > for that printer. > > -----Original Message----- > From: Wim [ mailto:wim@wanadoo.nl] > Sent: Wednesday, November 17, 1999 9:34 AM > To: Info-TCPware@process.com > Subject: print problem > > > Please help me on the folowing > > > I set up a new printer queue. We have done this many times. > But now I cant print the job says it is processing for a long time and > then > I see this error > > %TCPWARE_TSSYM-W-CONNERR, error connecting to 192.168.1.57,9100 for queue > PR208 > -TCPWARE-W-ETIMEDOUT, connection timed out > > I can ping to the ip adress. > > What can I do to solve this problem? > > Many thanks in advance > > > -- > Wim Knoll, RDC Datacentrum B.V. > De Klencke 12, P.O. Box 74707 > 1070 BS Amsterdam, The Netherlands > Phone 31 - 205497171 Fax 31-206611526 > > > ================================================================================ Archive-Date: Wed, 17 Nov 1999 15:37:02 -0400 Message-ID: <383307F9.D73641A3@SMTP.DeltaTel.RU> Date: Wed, 17 Nov 1999 22:54:33 +0300 From: "Ruslan R. Laishev" Reply-To: Info-TCPware@process.com MIME-Version: 1.0 Subject: Re: print problem Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit To: Info-TCPware@PROCESS.COM This problem can caused by limited "back log queue" of HP JD card, also in some case this problem is appeared if you use Novel Netware queue to the same printer, or you have other VMS queues to this printer. ... http://www.openvms.digital.com:8000/72final/6526/6526profile_029.html#pri_charac_sec_ 19.4.5 Releasing a TELNETSYM Link By default, TELNETSYM releases an open link at the end of a print job. This behavior is useful when multiple systems contend for the same printer. Configuring TELNETSYM to release the link at the end of a job allows other systems to print quickly. However, this behavior can be a disadvantage because of the overhead involved with link creation for each print job. When there is little or no contention for a printer, it is useful to configure TELNETSYM to release the link only after a certain period of idle time has passed. With this approach, TELNETSYM waits for the configured idle time to elapse and then closes the link. This option works well within batch printing applications. Use the logical name TCPIP$TELNETSYM_IDLE_TIMEOUT to define the length of time to wait before terminating an inactive link. Specify a value that is an OpenVMS delta time. For example, to define a link-idle-timeout of 10 minutes, enter: $ DEFINE /SYSTEM UCX$TELNETSYM_IDLE_TIMEOUT "0 00:10:00.00" ... Wim wrote: > > Please help me on the folowing > > I set up a new printer queue. We have done this many times. > But now I cant print the job says it is processing for a long time and then > I see this error > > %TCPWARE_TSSYM-W-CONNERR, error connecting to 192.168.1.57,9100 for queue > PR208 > -TCPWARE-W-ETIMEDOUT, connection timed out > > I can ping to the ip adress. > > What can I do to solve this problem? > > Many thanks in advance > > -- > Wim Knoll, RDC Datacentrum B.V. > De Klencke 12, P.O. Box 74707 > 1070 BS Amsterdam, The Netherlands > Phone 31 - 205497171 Fax 31-206611526 -- Regards. +.....................pure personal opinion..........................+ Free & commercial software for ISP -> HTTP://WWW.RadiusVMS.COM +.....................Kick ass VMS solution!.........................+ ================================================================================ Archive-Date: Fri, 19 Nov 1999 04:03:46 -0400 From: "Wim" Reply-To: Info-TCPware@process.com Subject: upgrade question Date: Fri, 19 Nov 1999 09:48:53 +0100 Sender: bull@diode.rdc.nl Message-ID: <8132tv$n59$1@news1.xs4all.nl> To: Info-TCPware@PROCESS.COM Hello thanks to all of them who helped me out on the print problem. Now I would like to get some advice on the following. Currently we have TCPWARE for OpenVMS V5.3-2, I would like to upgrade this to OpenVMS V5.4. Can I just install it over the old version?? I would like to get some pointers. Regards -- Wim ================================================================================ Archive-Date: Fri, 19 Nov 1999 08:06:28 -0400 Sender: bryant@process.com Date: Fri, 19 Nov 1999 08:05:32 -0400 From: Geoff Bryant Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com CC: bryant@process.com Message-ID: <009E15ED.50C16EB0.95@process.com> Subject: RE: upgrade question "Wim" writes: > >Hello thanks to all of them who helped me out on the print problem. > >Now I would like to get some advice on the following. > >Currently we have TCPWARE for OpenVMS V5.3-2, I would like to upgrade this >to OpenVMS V5.4. >Can I just install it over the old version?? Do you mean upgrading TCPware from 5.3-2 to TCPware version 5.4-2? If so, then by all means go ahead and upgrade. Or do you mean you are upgrading VMS versions? >I would like to get some pointers. > >Regards > >-- >Wim ------------------------------------------------------------- Geoff Bryant bryant@process.com TCPware/Multinet Engineering Process Software Corporation http://www.process.com/ 959 Concord St. Framingham, MA 01701 USA ================================================================================ Archive-Date: Fri, 19 Nov 1999 08:50:19 -0400 Message-ID: <45C82258A1B2D111892500805FCC9B0D022E9B01@nt05.wstf.nasa.gov> From: "Peebles, Darwin" Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com Subject: RE: upgrade question Date: Fri, 19 Nov 1999 06:49:43 -0700 MIME-Version: 1.0 Content-Type: text/plain And I thought we were out of date. VMS V5.4 is highly likely to have Y2K problems. You should go to V5.5 (or higher, we are at V7.1 on our VAXs and V7.2 on our Alphas) and get the Y2K patches ASAP!!! Yes you can "UPGRADE" from one minor VMS version to another (V5.n to V5.n+m) with very little problem, but you will probably need to reinstall TCPWare when you are done with the VMS upgrade. The "VMS Upgrade and Installation Manual" will give you the instructions for upgrading, but be sure to read the "VMS Release Notes" pertaining to the upgrade for any gotas. Good luck! Darwin "Peebs" Peebles Sr. Scientific Programmer/Analyst AlliedSignal Technical Services Corporation NASA, JSC, White Sands Test Facility Mail Stop 101P P.O. Box 20 Las Cruces, NM 88004 Phone: 505-524-5619 Fax: 505-524-5544 E-mail: dpeebles@wstf.nasa.gov > ---------- > From: Wim[SMTP:wim@wanadoo.nl] > Reply To: Info-TCPware@process.com > Sent: Friday, November 19, 1999 1:48 AM > To: Info-TCPware@PROCESS.COM > Subject: upgrade question > > Hello thanks to all of them who helped me out on the print problem. > > Now I would like to get some advice on the following. > > Currently we have TCPWARE for OpenVMS V5.3-2, I would like to upgrade this > to OpenVMS V5.4. > Can I just install it over the old version?? > > I would like to get some pointers. > > > Regards > > > -- > Wim > > > ================================================================================ Archive-Date: Fri, 19 Nov 1999 11:49:43 -0400 Message-ID: <4.1.19991119091431.00b5beb0@mehlhop.org> Date: Fri, 19 Nov 1999 09:15:25 -0700 To: Info-TCPware@process.com From: Jim Mehlhop Reply-To: Info-TCPware@process.com Subject: RE: upgrade question In-Reply-To: <45C82258A1B2D111892500805FCC9B0D022E9B01@nt05.wstf.nasa.go v> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" As long as you stay within V5 IE V5.5-2 you will not need to re-install TCPware. If you go to V6 or V7 then yes you will Jim At 06:49 AM 11/19/99 -0700, you wrote: >And I thought we were out of date. VMS V5.4 is highly likely to have Y2K >problems. You should go to V5.5 (or higher, we are at V7.1 on our VAXs and >V7.2 on our Alphas) and get the Y2K patches ASAP!!! > >Yes you can "UPGRADE" from one minor VMS version to another (V5.n to V5.n+m) >with very little problem, but you will probably need to reinstall TCPWare >when you are done with the VMS upgrade. The "VMS Upgrade and Installation >Manual" will give you the instructions for upgrading, but be sure to read >the "VMS Release Notes" pertaining to the upgrade for any gotas. > >Good luck! > >Darwin "Peebs" Peebles >Sr. Scientific Programmer/Analyst >AlliedSignal Technical Services Corporation >NASA, JSC, White Sands Test Facility >Mail Stop 101P >P.O. Box 20 >Las Cruces, NM 88004 >Phone: 505-524-5619 >Fax: 505-524-5544 >E-mail: dpeebles@wstf.nasa.gov > >> ---------- >> From: Wim[SMTP:wim@wanadoo.nl] >> Reply To: Info-TCPware@process.com >> Sent: Friday, November 19, 1999 1:48 AM >> To: Info-TCPware@PROCESS.COM >> Subject: upgrade question >> >> Hello thanks to all of them who helped me out on the print problem. >> >> Now I would like to get some advice on the following. >> >> Currently we have TCPWARE for OpenVMS V5.3-2, I would like to upgrade this >> to OpenVMS V5.4. >> Can I just install it over the old version?? >> >> I would like to get some pointers. >> >> >> Regards >> >> >> -- >> Wim >> >> >> _________________________________________________________________________ Jim Mehlhop, Support Engineer Process Software Mehlhop@process.com Phone 719-638-8448 Join Cauce to outlaw spam http://www.cauce.org/ _________________________________________________________________________ ================================================================================ Archive-Date: Fri, 19 Nov 1999 11:50:44 -0400 Message-ID: <4.1.19991119091629.00b64e30@mehlhop.org> Date: Fri, 19 Nov 1999 09:17:41 -0700 To: Info-TCPware@process.com From: Jim Mehlhop Reply-To: Info-TCPware@process.com Subject: RE: upgrade question In-Reply-To: <45C82258A1B2D111892500805FCC9B0D022E9B01@nt05.wstf.nasa.go v> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" If on the other hand you are asking about going from TCPware 5.3-2 to 5.4 then yes simply install 5.4 over the old version and it should take care of everything. At 06:49 AM 11/19/99 -0700, you wrote: >And I thought we were out of date. VMS V5.4 is highly likely to have Y2K >problems. You should go to V5.5 (or higher, we are at V7.1 on our VAXs and >V7.2 on our Alphas) and get the Y2K patches ASAP!!! > >Yes you can "UPGRADE" from one minor VMS version to another (V5.n to V5.n+m) >with very little problem, but you will probably need to reinstall TCPWare >when you are done with the VMS upgrade. The "VMS Upgrade and Installation >Manual" will give you the instructions for upgrading, but be sure to read >the "VMS Release Notes" pertaining to the upgrade for any gotas. > >Good luck! > >Darwin "Peebs" Peebles >Sr. Scientific Programmer/Analyst >AlliedSignal Technical Services Corporation >NASA, JSC, White Sands Test Facility >Mail Stop 101P >P.O. Box 20 >Las Cruces, NM 88004 >Phone: 505-524-5619 >Fax: 505-524-5544 >E-mail: dpeebles@wstf.nasa.gov > >> ---------- >> From: Wim[SMTP:wim@wanadoo.nl] >> Reply To: Info-TCPware@process.com >> Sent: Friday, November 19, 1999 1:48 AM >> To: Info-TCPware@PROCESS.COM >> Subject: upgrade question >> >> Hello thanks to all of them who helped me out on the print problem. >> >> Now I would like to get some advice on the following. >> >> Currently we have TCPWARE for OpenVMS V5.3-2, I would like to upgrade this >> to OpenVMS V5.4. >> Can I just install it over the old version?? >> >> I would like to get some pointers. >> >> >> Regards >> >> >> -- >> Wim >> >> >> _________________________________________________________________________ Jim Mehlhop, Support Engineer Process Software Mehlhop@process.com Phone 719-638-8448 Join Cauce to outlaw spam http://www.cauce.org/ _________________________________________________________________________ ================================================================================ Archive-Date: Fri, 19 Nov 1999 13:21:50 -0400 Message-ID: From: "Garrido, Ramon, Mr, HQAFCEE" Reply-To: Info-TCPware@process.com To: "'Info-TCPware@process.com'" Subject: RE: upgrade question Date: Fri, 19 Nov 1999 12:20:47 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF32BA.CC937F2C" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF32BA.CC937F2C Content-Type: text/plain; charset="iso-8859-1" LOWEST VERSION OF VMS YOU SHOULD BE AT IS VMS 6.2 with its proper patches (Y2K KIT for VAX VMS 6.2) -----Original Message----- From: Jim Mehlhop [mailto:mehlhop@process.com] Sent: Friday, November 19, 1999 10:18 AM To: Info-TCPware@process.com Subject: RE: upgrade question If on the other hand you are asking about going from TCPware 5.3-2 to 5.4 then yes simply install 5.4 over the old version and it should take care of everything. At 06:49 AM 11/19/99 -0700, you wrote: >And I thought we were out of date. VMS V5.4 is highly likely to have Y2K >problems. You should go to V5.5 (or higher, we are at V7.1 on our VAXs and >V7.2 on our Alphas) and get the Y2K patches ASAP!!! > >Yes you can "UPGRADE" from one minor VMS version to another (V5.n to V5.n+m) >with very little problem, but you will probably need to reinstall TCPWare >when you are done with the VMS upgrade. The "VMS Upgrade and Installation >Manual" will give you the instructions for upgrading, but be sure to read >the "VMS Release Notes" pertaining to the upgrade for any gotas. > >Good luck! > >Darwin "Peebs" Peebles >Sr. Scientific Programmer/Analyst >AlliedSignal Technical Services Corporation >NASA, JSC, White Sands Test Facility >Mail Stop 101P >P.O. Box 20 >Las Cruces, NM 88004 >Phone: 505-524-5619 >Fax: 505-524-5544 >E-mail: dpeebles@wstf.nasa.gov > >> ---------- >> From: Wim[SMTP:wim@wanadoo.nl] >> Reply To: Info-TCPware@process.com >> Sent: Friday, November 19, 1999 1:48 AM >> To: Info-TCPware@PROCESS.COM >> Subject: upgrade question >> >> Hello thanks to all of them who helped me out on the print problem. >> >> Now I would like to get some advice on the following. >> >> Currently we have TCPWARE for OpenVMS V5.3-2, I would like to upgrade this >> to OpenVMS V5.4. >> Can I just install it over the old version?? >> >> I would like to get some pointers. >> >> >> Regards >> >> >> -- >> Wim >> >> >> _________________________________________________________________________ Jim Mehlhop, Support Engineer Process Software Mehlhop@process.com Phone 719-638-8448 Join Cauce to outlaw spam http://www.cauce.org/ _________________________________________________________________________ ------_=_NextPart_001_01BF32BA.CC937F2C Content-Type: text/html; charset="iso-8859-1" RE: upgrade question

LOWEST VERSION OF VMS YOU SHOULD BE AT IS VMS 6.2 with its proper patches (Y2K KIT for
VAX VMS 6.2)

-----Original Message-----
From: Jim Mehlhop [mailto:mehlhop@process.com]
Sent: Friday, November 19, 1999 10:18 AM
To: Info-TCPware@process.com
Subject: RE: upgrade question


If on the other hand you are asking about going from TCPware 5.3-2 to 5.4
then yes simply install 5.4 over the old version and it should take care of
everything.


At 06:49 AM 11/19/99 -0700, you wrote:
>And I thought we were out of date.  VMS V5.4 is highly likely to have Y2K
>problems.  You should go to V5.5 (or higher, we are at V7.1 on our VAXs and
>V7.2 on our Alphas) and get the Y2K patches ASAP!!!
>
>Yes you can "UPGRADE" from one minor VMS version to another (V5.n to V5.n+m)
>with very little problem, but you will probably need to reinstall TCPWare
>when you are done with the VMS upgrade.  The "VMS Upgrade and Installation
>Manual" will give you the instructions for upgrading, but be sure to read
>the "VMS Release Notes" pertaining to the upgrade for any gotas.
>
>Good luck!
>
>Darwin "Peebs" Peebles
>Sr. Scientific Programmer/Analyst
>AlliedSignal Technical Services Corporation
>NASA, JSC, White Sands Test Facility
>Mail Stop 101P
>P.O. Box 20
>Las Cruces, NM 88004
>Phone: 505-524-5619
>Fax: 505-524-5544
>E-mail: dpeebles@wstf.nasa.gov
>
>> ----------
>> From:        Wim[SMTP:wim@wanadoo.nl]
>> Reply To:    Info-TCPware@process.com
>> Sent:        Friday, November 19, 1999 1:48 AM
>> To:  Info-TCPware@PROCESS.COM
>> Subject:     upgrade question
>>
>> Hello thanks to all of them who helped me out on the print problem.
>>
>> Now I would like to get some advice on the following.
>>
>> Currently we have TCPWARE for OpenVMS V5.3-2, I would like to upgrade this
>> to OpenVMS V5.4.
>> Can I just install it over the old version??
>>
>> I would like to get some pointers.
>>
>>
>> Regards
>>
>>
>> --
>> Wim
>>
>>
>>

    _________________________________________________________________________
    Jim Mehlhop, Support Engineer              
    Process Software
    Mehlhop@process.com
    Phone 719-638-8448
    Join Cauce to outlaw spam
    http://www.cauce.org/
    _________________________________________________________________________

------_=_NextPart_001_01BF32BA.CC937F2C-- ================================================================================ Archive-Date: Fri, 19 Nov 1999 14:07:47 -0400 Message-ID: <01BE9872614BD311BB8000805F9F4A850168B1CC@norma.mfs.com> From: "Robert, Andrew" Reply-To: Info-TCPware@process.com To: "'Info-TCPware@process.com'" Subject: RE: upgrade question Date: Fri, 19 Nov 1999 14:06:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Please reference this list of patches required after a base installation of VAX or Alpha 6.2 VAX: Subject: VVMS 6.2 ============================================================================ ============================================================================ This Proactive Patch report is being provided to PROPATCH as part of your Business Critical Support Services. The purpose of this report is to assist in managing your system by identifying patches and allowing you to proactively decide the applicability to your environment and business needs. Data within this report was collected from the system disk of node PPV062 and will pertain to all nodes within the cluster that share the same system disk. If the cluster has multiple system disks then a separate Proactive Patch report will need to be generated for each system disk. NOTES: 1. Some patches in this report are identified as being --CRITICAL--. This indicates that the problem(s) addressed by the patch have the potential to cause system outages (i.e. hang or crash). 2. Some patches require the prior installation of other patches. For patches that have this prerequisite, please read the patch release notes for additional information. 3. If you plan to install multiple patches simultaneously it is recommended you install them in a test environment to test with your applications before implementing in a production environment. ============================================================================ ============================================================================ LIFE Analysis Report For: PPV062 Date: Tue Sep 14 14:21:04 1999 Report Type: BRIEF Rules Database Version Number: VAX RMR-AUG-1999 ProPatch executable Version Number: V4.30 ============================================================================ ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:BACKUP.EXE image file id: VAX V61R_62-000 link date/time: 15-JUN-1895 00:32:51.93 Service action: VAXY2K02_062 Patch reference name: VAXY2K02_062 --CRITICAL-- Year 2000 Enhancements ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:ECDRIVER.EXE image file id: X-4 link date/time: 03-DEC-1896 10:00:39.30 Service action: VAXPHV03_062 Patch reference name: VAXPHV03_062 --CRITICAL-- Network Driver Crash Fixes ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:F11CACP.EXE image file id: X-8 link date/time: 09-AUG-1895 13:17:41.69 Service action: VAXF11C01_062 Patch reference name: VAXF11C01_062 --CRITICAL-- ISO 9660 CD-ROM Problem Corrections OPENVMS VAX ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:AUTHORIZE.EXE image file id: X-20 link date/time: 20-MAY-1896 19:17:31.67 Service action: VAXUAF01_070 Patch reference name: VAXUAF01_070 Login Hang/Slow Proxy Command Processing Fix ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:SMBSRVSHR.EXE image file id: A-1 link date/time: 15-OCT-1896 14:35:31.42 Service action: VAXPRTS02_070 Patch reference name: VAXPRTS02_070 Print Symbiont and SMBSRVSHR Fixes ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:SYS$CLUSTER.EXE image file id: X-6 link date/time: 16-AUG-1896 19:59:00.08 Service action: VAXSYSL01_070 Patch reference name: VAXSYSL01_070 --CRITICAL-- Multiple Cluster Fixes ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:INSTALL.EXE image file id: X-16 link date/time: 10-AUG-1895 02:29:12.81 Service action: VAXINST01_062 Patch reference name: VAXINST01_062 Dangling Lock Fix For INSTALL Utility ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:MTAAACP.EXE image file id: X-7 link date/time: 27-JUL-1895 02:04:29.01 Service action: VAXMTAA03_062 Patch reference name: VAXMTAA03_062 --CRITICAL-- Mailbox Read Sync Corrections. Requires prior installation of VAXY2K02_062. Also requires installation of VAXBACK03_062, VAXDISM02_062, VAXINIT01_062, VAXSYSA02_062, and VAXMOUN03_062 or supersedent kits. ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:CMA$OPEN_RTL.EXE image file id: CMA V2.11-440B link date/time: 18-APR-1896 19:02:54.65 Service action: VAXCMAR04_062 Patch reference name: VAXCMAR04_062 DECthreads and VAX C Macro Fixes, On multi CPU systems please review the release notes for applicability ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:DECC$SHR.EXE image file id: V06.1R-2 link date/time: 02-JUL-1897 10:21:45.96 Service action: VAXCRTL11_062 Patch reference name: VAXCRTL11_062 Multiple Corrections for DEC C RTL ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:SYSLOA440.EXE image file id: X-36 link date/time: 12-JAN-1896 10:44:02.58 Service action: VAXSYSL02_062 Patch reference name: VAXSYSL02_062 Console Hang on VAX 3100 Model 80 ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:BASRTL.EXE image file id: V05-000 link date/time: 09-MAR-1894 01:34:16.85 Service action: VAXBASR01_070 Patch reference name: VAXBASR01_070 Corrections to Basic Run-Time Library ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:SMGSHR.EXE image file id: V06-001 link date/time: 09-MAR-1894 01:34:17.24 Service action: VAXSMGR02_070 Patch reference name: VAXSMGR02_070 Corrections for Screen Management Routines ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:CONVERT.EXE image file id: X-3 link date/time: 29-AUG-1895 16:57:33.20 Service action: VAXRMS03_062 Patch reference name: VAXRMS03_062 --CRITICAL-- Miscellaneous Fixes for RMS ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:SETP0.EXE image file id: X-3 link date/time: 27-JUL-1896 09:15:12.53 Service action: VAXCLIU03_062 Patch reference name: VAXCLIU03_062 Set Password Allowed in Command Procedure Fix ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:BADBLOCK.EXE image file id: X-1 link date/time: 16-AUG-1896 19:59:42.80 Service action: VAXBADB02_070 Patch reference name: VAXBADB02_070 BADBLOCK Correction ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:CXXL$011_SHR.EXE image file id: CXXL V1.3-3 link date/time: 16-MAR-1895 18:43:00.35 Service action: VAXCXXL01_062 Patch reference name: VAXCXXL01_062 Multiple Fixes for DEC C++ Class Libraries ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:DISMNTSHR.EXE image file id: X-2 link date/time: 10-AUG-1895 01:48:09.50 Service action: VAXCLUSIO01_062 Patch reference name: VAXCLUSIO01_062 --CRITICAL-- VMScluster Enhancements and Fixes. CAUTION! Prior installation of additional patches are required. Please Read Release Notes. ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:DUDRIVER.EXE image file id: X-57A2A4A9 link date/time: 18-SEP-1897 23:27:52.90 Service action: VAXDRIV07_062 Patch reference name: VAXDRIV07_062 --CRITICAL-- Fixes for TUDRIVER/DUDRIVER. Requires prior installation of VAXCLUSIO01_062. ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:PADRIVER.EXE image file id: X-29 link date/time: 06-MAY-1897 01:17:43.64 Service action: VAXDRIV03_062 Patch reference name: VAXDRIV03_062 --CRITICAL-- PADRIVER And PEDRIVER Fixes ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:MSCP.EXE image file id: X-55A2 link date/time: 09-APR-1896 11:41:19.25 Service action: VAXMSCP03_062 Patch reference name: VAXMSCP03_062 --CRITICAL-- Various TMSC/MSCP Server Fixes ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:SET.EXE image file id: X-2 link date/time: 14-MAY-1897 01:56:29.86 Service action: VAXCLIU08_062 Patch reference name: VAXCLIU08_062 --CRITICAL-- SHOW.EXE and SET.EXE Image Corrections ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:CIA.EXE image file id: X-8A1 link date/time: 03-SEP-1896 13:56:51.79 Service action: VAXLOAD03_062 Patch reference name: VAXLOAD03_062 LOGINOUT/Audit and Security Server/Proxy Fixes ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:SHWCLSTR.EXE image file id: X-34 link date/time: 09-MAR-1894 02:13:33.72 Service action: VAXCLIU09_062 Patch reference name: VAXCLIU09_062 --CRITICAL-- SHWCLSTR.EXE Image Corrections ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:SHADOW_SERVER.EXE image file id: X-21A3 link date/time: 06-NOV-1896 07:30:54.86 Service action: VAXSHAD08_062 Patch reference name: VAXSHAD08_062 --CRITICAL-- SHADOWING Misc Fixes. Requires prior installation of VAXCLUSIO01_062 ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:LMF.EXE image file id: X-4 link date/time: 09-MAR-1894 02:10:03.58 Service action: VMSLMF01_Y2000 Patch reference name: VMSLMF01_Y2000 For Systems Running Special Marketing date limited Software PAKS ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:MAIL.EXE image file id: X-4 link date/time: 27-MAR-1895 18:37:00.32 Service action: VAXMAIL02_062 Patch reference name: VAXMAIL02_062 --CRITICAL-- Fixes for VAXmail ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:DEBUG.EXE image file id: V6.1-05R link date/time: 04-OCT-1896 10:02:16.41 Service action: VAXDEBU01_062 Patch reference name: VAXDEBU01_062 Multiple DEBUG Corrections ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:LATACP.EXE image file id: V1.0-147F link date/time: 15-AUG-1897 13:28:15.25 Service action: VAXLAT02_062 Patch reference name: VAXLAT02_062 --CRITICAL-- Fixes for LTDRIVER, LATACP and LATCP ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:DKDRIVER.EXE image file id: X-40A3 link date/time: 12-APR-1895 17:57:34.88 Service action: VAXSCSI01_062 Patch reference name: VAXSCSI01_062 --CRITICAL-- VARIOUS SCSI DRIVER CORRECTIONS ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:MOUNTSHR.EXE image file id: X-1 link date/time: 20-FEB-1896 10:11:15.29 Service action: VAXMOUN04_062 Patch reference name: VAXMOUN04_062 --CRITICAL-- MOUNT corrections and enhancements. Prior installation of VAXCLUSIO01_062 is required. Also requires VAXSYSA02_062, VAXINIT01_062, VAXBACK03_062, VAXMTAA03_062, and VAXDISM02_062 ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:JBC$JOB_CONTROL.EXE image file id: X-20 link date/time: 27-JUL-1896 09:16:24.12 Service action: VAXQMAN05_062 Patch reference name: VAXQMAN05_062 --CRITICAL-- Queue Manager and Job Controller Fixes ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:AUDIT_SERVER.EXE image file id: X-8 link date/time: 16-JAN-1897 11:13:57.05 Service action: VAXAUDS01_062 Patch reference name: VAXAUDS01_062 Audit Server Log File Fix ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:SETAUDIT.EXE image file id: X-9 link date/time: 09-MAR-1894 02:07:43.28 Service action: VAXCLIU07_062 Patch reference name: VAXCLIU07_062 SET AUDIT hang fix ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:ESS$DADDRIVER.EXE image file id: X-12 link date/time: 09-MAR-1894 02:09:43.22 Service action: VAXLAD01_062 Patch reference name: VAXLAD01_062 Various Fixes for DAD, LAD, LAST, MAD Drivers. ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:SYSLOA1202.EXE image file id: X-36 link date/time: 09-MAR-1894 02:23:37.83 Service action: VAXSYSL04_062 Patch reference name: VAXSYSL04_062 --CRITICAL-- SET TIME and System Crash Fixes ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:EVENT_FLAGS_AND_ASTS.EXE image file id: X-24 link date/time: 09-MAR-1894 02:13:27.69 Service action: VAXSYSB02_062 Patch reference name: VAXSYSB02_062 --CRITICAL-- Multiple SYSTEM Components Corrections ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:ERRORLOG.EXE image file id: X-24 link date/time: 09-MAR-1894 02:24:22.71 Service action: VAXSYSA02_062 Patch reference name: VAXSYSA02_062 --CRITICAL-- Multiple SYSTEM ROUTINES Corrections. Requires prior installation of VAXCLUSIO01_062, and VAXY2K02_062. If VAXDOSD08_062 is to be installed it must be installed before VAXSYSA02_062 ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:SYS$TRANSACTION_SERVICES.EXE image file id: DDTM V1.2-K link date/time: 27-FEB-1896 09:52:21.03 Service action: VAXDDTM02_062 Patch reference name: VAXDDTM02_062 DECdtm fixes ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:LIBRTL.EXE image file id: V06-001 link date/time: 27-JUL-1896 08:26:55.05 Service action: VAXLIBR03_062 Patch reference name: VAXLIBR03_062 Misc Run-Time Library Fixes Requires prior installation of VAXY2K02_062. ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:BACKUP.EXE image file id: VAX V61R_62-000 link date/time: 15-JUN-1895 00:32:51.93 Service action: VAX_TH_Y2K01_062 Patch reference name: VAX_TH_Y2K01_062 --CRITICAL-- This Kit is **ONLY** for OpenVMS/Thai VAX. Do not install this kit unless your system is running OpenVMS/Thai VAX. Y2K Fixes for OpenVMS/Thai VAX. Requires prior installation of VAXCLUSIO01_062. ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:BACKUP.EXE image file id: VAX V61R_62-000 link date/time: 15-JUN-1895 00:32:51.93 Service action: VAXBACK03_062 Patch reference name: VAXBACK03_062 Multiple BACKUP Corrections. If using SLS please reference DSNlink article regarding this article. Also requires installation of VAXDISM02_062, VAXINIT01_062, VAXMTAA03_062, VAXSYSA02_062, and VAXMOUN03_062 or supersedent kits. ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:LBRSHR.EXE image file id: X-1 link date/time: 27-JUL-1894 00:26:52.75 Service action: VAXLBR01_062 Patch reference name: VAXLBR01_062 Corrections to LBRSHR.EXE, requires prior installation of VAXY2K02_062. ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:DISMNTSHR.EXE image file id: X-2 link date/time: 10-AUG-1895 01:48:09.50 Service action: VAXDISM02_062 Patch reference name: VAXDISM02_062 --CRITICAL-- Mailbox Read Sync Corrections. Requires prior installation of VAXCLUSIO01_062. Also requires installation of VAXBACK03_062, VAXINIT01_062, VAXMTAA03_062, VAXSYSA02_062, and VAXMOUN03_062 or supersedent kits. ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:INIT$SHR.EXE image file id: X-2 link date/time: 18-JUN-1896 18:59:03.18 Service action: VAXINIT01_062 Patch reference name: VAXINIT01_062 --CRITICAL-- Mailbox Read Sync Corrections. Also requires installation of VAXBACK03_062, VAXDISM02_062, VAXMTAA03_062, VAXSYSA02_062, and VAXMOUN03_062 or supersedent kits. ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:PCSI$MAIN.EXE image file id: X1.1 link date/time: 09-MAR-1894 02:17:33.58 Service action: DEC-VAXVMS-VMS62TO71_PCSI-V0100--4 Patch reference name: DEC-VAXVMS-VMS62TO71_PCSI-V0100--4 PCSI Update for OpenVAX V6.2 and V7.1 ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:OPCOM.EXE image file id: X-6A1A1 link date/time: 31-JUL-1895 17:52:43.22 Service action: VAXOPCO02_062 Patch reference name: VAXOPCO02_062 --CRITICAL-- OPCOM/REPLY/REQUEST Fixes ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SYSTEM:MONITOR.EXE image file id: X-6 link date/time: 27-JUL-1895 02:03:08.17 Service action: VAXMONT01_062 Patch reference name: VAXMONT01_062 MONITOR/NODE Update to V7.2 Functionality ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:BASRTL.EXE image file id: V05-000 link date/time: 09-MAR-1894 01:34:16.85 Service action: VAXBASR01_062 Patch reference name: VAXBASR01_062 --CRITICAL-- Corrections for BASIC Run-Time Library ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:SYS$IPC_SERVICES.EXE image file id: IPC V1.2-K link date/time: 27-FEB-1896 09:52:12.96 Service action: VAXIPC01_062 Patch reference name: VAXIPC01_062 --CRITICAL-- IPC BLOCK RETRY Access Violation Fix. ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$SHARE:SMI$OBJSHR.EXE image file id: 0 link date/time: 15-MAY-1896 04:57:56.82 Service action: VAXMANA02_062 Patch reference name: VAXMANA02_062 Various SYSMAN and SMISERVER Fixes. Require prior installation of VAXCLUSIO01_062. ============================================================================ Image on your system: VMS version: OPENVMS VAX V6.2 image name: DSA0:SYS$LOADABLE_IMAGES:FTDRIVER.EXE image file id: X-8A1 link date/time: 12-FEB-1896 13:38:06.47 Service action: VAXPTD01_070 Patch reference name: VAXPTD01_070 --CRITICAL-- FTDRIVER Fix for System Crash ============================================================================ For Alpha: - Please see the release notes for each of these patches to determine order of installation. ALPACRT13_062 ALPAMAC02_062 ALPAUDS01_062 ALPBACK02_062 ALPBASR03_062 ALPBOOT13_062 ALPCLIU01_062 ALPCLIU03_062 ALPCLIU04_062 ALPCLIU05_062 ALPCLUS01_062 ALPCLUSIO01_062 ALPCMAR04_062 ALPCPU0907_062 ALPCPU0C09_062 ALPCPU1501_062 ALPCPU1603_062 ALPCPU1A02_062 ALPCPU1B03_062 ALPCXXL01_062 ALPDCL01_062 ALPDDTM04_062 ALPDEBU03_062 ALPDISM02_062 ALPDRIV05_062 ALPDRIV06_062 ALPDRIV09_062 ALPDRIV10_062 ALPDRIV13_062 ALPDRIV18_062 ALPDRIV20_062 ALPDUP01_062 ALPDWXT01_070 ALPF11C03_062 ALPF11X03_062 ALPINIT01_062 ALPINST01_062 ALPLAD03_062 ALPLAN05_062 ALPLAT03_062 ALPLBR01_062 ALPLIBR07_062 ALPLINK01_062 ALPLMF01_062 ALPLOAD02_062 ALPMAIL03_062 ALPMANA02_070 ALPMONT01_062 ALPMOUN04_062 ALPMSGF02_062 ALPMTAA02_062 ALPOPCO01_062 ALPOPCO01_070 ALPOPDR04_062 ALPPORTS01_062 ALPPRTS02_070 ALPPTD01_070 ALPQMAN03_062 ALPRMS03_062 ALPRTPA01_062 ALPSCSI07_062 ALPSDA03_062 ALPSHAD08_062 ALPSMGR02_070 ALPSYSB03_062 ALPSYSI01_062 ALPSYSL02_070 ALPTRAC02_062 ALPTTDR02_062 ALPY2K02_062 -----Original Message----- From: Garrido, Ramon, Mr, HQAFCEE [mailto:Ramon.Garrido@hqafcee.brooks.af.mil] Sent: Friday, November 19, 1999 1:21 PM To: 'Info-TCPware@process.com' Subject: RE: upgrade question LOWEST VERSION OF VMS YOU SHOULD BE AT IS VMS 6.2 with its proper patches (Y2K KIT for VAX VMS 6.2) -----Original Message----- From: Jim Mehlhop [ mailto:mehlhop@process.com ] Sent: Friday, November 19, 1999 10:18 AM To: Info-TCPware@process.com Subject: RE: upgrade question If on the other hand you are asking about going from TCPware 5.3-2 to 5.4 then yes simply install 5.4 over the old version and it should take care of everything. At 06:49 AM 11/19/99 -0700, you wrote: >And I thought we were out of date. VMS V5.4 is highly likely to have Y2K >problems. You should go to V5.5 (or higher, we are at V7.1 on our VAXs and >V7.2 on our Alphas) and get the Y2K patches ASAP!!! > >Yes you can "UPGRADE" from one minor VMS version to another (V5.n to V5.n+m) >with very little problem, but you will probably need to reinstall TCPWare >when you are done with the VMS upgrade. The "VMS Upgrade and Installation >Manual" will give you the instructions for upgrading, but be sure to read >the "VMS Release Notes" pertaining to the upgrade for any gotas. > >Good luck! > >Darwin "Peebs" Peebles >Sr. Scientific Programmer/Analyst >AlliedSignal Technical Services Corporation >NASA, JSC, White Sands Test Facility >Mail Stop 101P >P.O. Box 20 >Las Cruces, NM 88004 >Phone: 505-524-5619 >Fax: 505-524-5544 >E-mail: dpeebles@wstf.nasa.gov > >> ---------- >> From: Wim[SMTP:wim@wanadoo.nl] >> Reply To: Info-TCPware@process.com >> Sent: Friday, November 19, 1999 1:48 AM >> To: Info-TCPware@PROCESS.COM >> Subject: upgrade question >> >> Hello thanks to all of them who helped me out on the print problem. >> >> Now I would like to get some advice on the following. >> >> Currently we have TCPWARE for OpenVMS V5.3-2, I would like to upgrade this >> to OpenVMS V5.4. >> Can I just install it over the old version?? >> >> I would like to get some pointers. >> >> >> Regards >> >> >> -- >> Wim >> >> >> _________________________________________________________________________ Jim Mehlhop, Support Engineer Process Software Mehlhop@process.com Phone 719-638-8448 Join Cauce to outlaw spam http://www.cauce.org/ _________________________________________________________________________ ================================================================================ Archive-Date: Fri, 19 Nov 1999 22:27:08 -0400 Message-ID: <383605C4.56B47438@email.sps.mot.com> Date: Sat, 20 Nov 1999 10:21:56 +0800 From: "Kumar Prem" Reply-To: Info-TCPware@process.com MIME-Version: 1.0 To: Info-TCPware@process.com Subject: Re: upgrade question References: <45C82258A1B2D111892500805FCC9B0D022E9B01@nt05.wstf.nasa.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I also have few vax servers but I dont really make use of this tcpware. I am using something else called multinet. Could anyone explain what is this tcpware about and what is the difference compared to multinet. Thanks. Prem. "Peebles, Darwin" wrote: > > And I thought we were out of date. VMS V5.4 is highly likely to have Y2K > problems. You should go to V5.5 (or higher, we are at V7.1 on our VAXs and > V7.2 on our Alphas) and get the Y2K patches ASAP!!! > > Yes you can "UPGRADE" from one minor VMS version to another (V5.n to V5.n+m) > with very little problem, but you will probably need to reinstall TCPWare > when you are done with the VMS upgrade. The "VMS Upgrade and Installation > Manual" will give you the instructions for upgrading, but be sure to read > the "VMS Release Notes" pertaining to the upgrade for any gotas. > > Good luck! > > Darwin "Peebs" Peebles > Sr. Scientific Programmer/Analyst > AlliedSignal Technical Services Corporation > NASA, JSC, White Sands Test Facility > Mail Stop 101P > P.O. Box 20 > Las Cruces, NM 88004 > Phone: 505-524-5619 > Fax: 505-524-5544 > E-mail: dpeebles@wstf.nasa.gov > > > ---------- > > From: Wim[SMTP:wim@wanadoo.nl] > > Reply To: Info-TCPware@process.com > > Sent: Friday, November 19, 1999 1:48 AM > > To: Info-TCPware@PROCESS.COM > > Subject: upgrade question > > > > Hello thanks to all of them who helped me out on the print problem. > > > > Now I would like to get some advice on the following. > > > > Currently we have TCPWARE for OpenVMS V5.3-2, I would like to upgrade this > > to OpenVMS V5.4. > > Can I just install it over the old version?? > > > > I would like to get some pointers. > > > > > > Regards > > > > > > -- > > Wim > > > > > > ================================================================================ Archive-Date: Mon, 22 Nov 1999 14:34:50 -0400 Message-ID: From: "Garrido, Ramon, Mr, HQAFCEE" Reply-To: Info-TCPware@process.com To: "'Info-TCPware@process.com'" Subject: RE: upgrade question Date: Mon, 22 Nov 1999 13:33:29 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF3520.7462014E" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF3520.7462014E Content-Type: text/plain; charset="iso-8859-1" go to their Website and order an eval (free). That's the only way to really see the difference, then it's a matter of which one you're mostly comfortable with. -----Original Message----- From: Kumar Prem [mailto:r34124@email.sps.mot.com] Sent: Friday, November 19, 1999 8:22 PM To: Info-TCPware@process.com Subject: Re: upgrade question Hi, I also have few vax servers but I dont really make use of this tcpware. I am using something else called multinet. Could anyone explain what is this tcpware about and what is the difference compared to multinet. Thanks. Prem. "Peebles, Darwin" wrote: > > And I thought we were out of date. VMS V5.4 is highly likely to have Y2K > problems. You should go to V5.5 (or higher, we are at V7.1 on our VAXs and > V7.2 on our Alphas) and get the Y2K patches ASAP!!! > > Yes you can "UPGRADE" from one minor VMS version to another (V5.n to V5.n+m) > with very little problem, but you will probably need to reinstall TCPWare > when you are done with the VMS upgrade. The "VMS Upgrade and Installation > Manual" will give you the instructions for upgrading, but be sure to read > the "VMS Release Notes" pertaining to the upgrade for any gotas. > > Good luck! > > Darwin "Peebs" Peebles > Sr. Scientific Programmer/Analyst > AlliedSignal Technical Services Corporation > NASA, JSC, White Sands Test Facility > Mail Stop 101P > P.O. Box 20 > Las Cruces, NM 88004 > Phone: 505-524-5619 > Fax: 505-524-5544 > E-mail: dpeebles@wstf.nasa.gov > > > ---------- > > From: Wim[SMTP:wim@wanadoo.nl] > > Reply To: Info-TCPware@process.com > > Sent: Friday, November 19, 1999 1:48 AM > > To: Info-TCPware@PROCESS.COM > > Subject: upgrade question > > > > Hello thanks to all of them who helped me out on the print problem. > > > > Now I would like to get some advice on the following. > > > > Currently we have TCPWARE for OpenVMS V5.3-2, I would like to upgrade this > > to OpenVMS V5.4. > > Can I just install it over the old version?? > > > > I would like to get some pointers. > > > > > > Regards > > > > > > -- > > Wim > > > > > > ------_=_NextPart_001_01BF3520.7462014E Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: upgrade question

go to their Website and order an eval (free). That's = the only way to really see the difference, then it's a matter of which = one you're mostly comfortable with.

-----Original Message-----
From: Kumar Prem [mailto:r34124@email.sps.mot.com= ]
Sent: Friday, November 19, 1999 8:22 PM
To: Info-TCPware@process.com
Subject: Re: upgrade question


Hi,

I also have few vax servers but I dont really make = use of this tcpware.
I am using something else called multinet. Could = anyone explain what is
this tcpware about and what is the difference = compared to multinet.

Thanks.

Prem.

"Peebles, Darwin" wrote:
>
> And I thought we were out of date.  VMS = V5.4 is highly likely to have Y2K
> problems.  You should go to V5.5 (or = higher, we are at V7.1 on our VAXs and
> V7.2 on our Alphas) and get the Y2K patches = ASAP!!!
>
> Yes you can "UPGRADE" from one minor = VMS version to another (V5.n to V5.n+m)
> with very little problem, but you will probably = need to reinstall TCPWare
> when you are done with the VMS upgrade.  = The "VMS Upgrade and Installation
> Manual" will give you the instructions for = upgrading, but be sure to read
> the "VMS Release Notes" pertaining to = the upgrade for any gotas.
>
> Good luck!
>
> Darwin "Peebs" Peebles
> Sr. Scientific Programmer/Analyst
> AlliedSignal Technical Services = Corporation
> NASA, JSC, White Sands Test Facility
> Mail Stop 101P
> P.O. Box 20
> Las Cruces, NM 88004
> Phone: 505-524-5619
> Fax: 505-524-5544
> E-mail: dpeebles@wstf.nasa.gov
>
> > ----------
> > = From:         = Wim[SMTP:wim@wanadoo.nl]
> > Reply To:     = Info-TCPware@process.com
> > = Sent:         Friday, November = 19, 1999 1:48 AM
> > To:   = Info-TCPware@PROCESS.COM
> > Subject:      = upgrade question
> >
> > Hello thanks to all of them who helped me = out on the print problem.
> >
> > Now I would like to get some advice on the = following.
> >
> > Currently we have TCPWARE for OpenVMS = V5.3-2, I would like to upgrade this
> > to OpenVMS V5.4.
> > Can I just install it over the old = version??
> >
> > I would like to get some pointers.
> >
> >
> > Regards
> >
> >
> > --
> > Wim
> >
> >
> >

------_=_NextPart_001_01BF3520.7462014E-- ================================================================================ Archive-Date: Tue, 23 Nov 1999 06:13:13 -0400 Subject: Re: upgrade question From: eplan@kapsch.net (Peter LANGSTOEGER) Reply-To: Info-TCPware@process.com Message-ID: <383a71b7$1@news.kapsch.co.at> Date: 23 Nov 1999 11:51:35 +0100 To: Info-TCPware@PROCESS.COM In article <383605C4.56B47438@email.sps.mot.com>, "Kumar Prem" writes: >I also have few vax servers but I dont really make use of this tcpware. Then reconsider this. >I am using something else called multinet. Could anyone explain what is >this tcpware about and what is the difference compared to multinet. TCPware and Multinet are both 3rd party TCP/IP stacks for OpenVMS. Because DEC did a bad job in building a good enough TCP/IP stack (once called ULTRIX CONNECTION, later called UCX - means abbreviation - only, now called TCPIP Services for OpenVMS), some guys at TGV (Two Guys and a Vax) built their own stack MULTINET, some other guys at Process Software Corp. built TCPware, Wollongong did their own (later called PATHWAY, now dead) and the Carnegie Mellon University did their own freeware (once called CMU TEK now called CMUIP and almost dead). DEC did (very late) many development for UCX and finally ported the dUNIX stack to OpenVMS and renamed the product from UCX to TCPIP. And you know, when the 1st party product is "good enough", the 3rd party market is almost gone (look how M$ ruined many companies). CISCO did buy TGV some years ago, took some of their know-how (eg. TN3270 in the CISCO routers) and sold Multinet to Process Software. Wollongong became Attachmate some years ago, and some time after then ended PATHWAY. DEC sold it self (instead of its products) in slices (to EDI, TTI, QUANTUM, ORACLE, CABLETRON) and the rest to COMPAQ. So, what's left is COMPAQ (http://www.openvms.digital.com) with the product TCPIP (news:vmsnet.networks.tcp-ip.ucx) and Process Software Corporation (http://www.process.com) with Multinet (news:vmsnet.networks.tcp-ip.multinet) and TCPware (news:vmsnet.networks.tcp-ip.tcpware) as commercial ware. And the CMUIP (news:vmsnet.networks.tcp-ip.cmuip) freeware, still not fully ported to OpenVMS Alpha. (http://www.openvms.digital.com/freeware/cmuip/) I suggest UCX^WTCP/IP because it's license is included with every new OpenVMS system (or you don't need a license at all, if you are only using TCP/IP as a DECwindows X11 transport). But if you need special features now (eg. GATED, DHCP server, BIND V8, ...) and can't wait till TCPIP V5 is free of the most annoying bugs (>= V5.1) or if you have to buy a new license to get a TCPIP stack, then buy TCPware !!! -- Peter "EPLAN" LANGSTOEGER Tel. +43 1 81111-2651 Network and OpenVMS system manager Fax. +43 1 81111-888 FBFV/Information Services E-mail eplan@kapsch.net <<< KAPSCH AG Wagenseilgasse 1 PSImail PSI%(0232)281001141::EPLAN A-1121 VIENNA AUSTRIA "I'm not a pessimist, I'm a realist" "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998 ================================================================================ Archive-Date: Tue, 23 Nov 1999 11:47:16 -0400 Message-ID: <383AC4F4.DE288604@mmaz.com> Date: Tue, 23 Nov 1999 09:46:44 -0700 From: Barry Treahy Reply-To: Info-TCPware@process.com MIME-Version: 1.0 To: TCPware User List Subject: Slow FTP transfers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have 5.3 running on VMS 5.5-2, I haven't had the time to upgrade to 5.4, and I'm moving a big file over a 56k FR circuit. The estimated transfer time is 16 hours, but I'm seeing that the transfer rate is half of the circuit speed. I know its not a problem with my hardware or circuit on either end because I move data between the Unix & Linux systems on each end and they move at the max transfer rate of the circuit. Is there a know problem with this in TCPware that is choking me? Barry ================================================================================ Archive-Date: Tue, 23 Nov 1999 11:53:29 -0400 Message-ID: <383AC66A.2B77C96F@mmaz.com> Date: Tue, 23 Nov 1999 09:52:58 -0700 From: Barry Treahy Reply-To: Info-TCPware@process.com MIME-Version: 1.0 To: TCPware User List Subject: Slow FTP Tranfers - Continued Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Also, I had expected this transfer to complete two hours ago... Other Unix FTP's allow for a reget to restart an interrupted transfer. I don't see that in TCPware and I've got to reboot my systems to install additional power equipment. Please don't tell me that what has transferred is for not? Barry ================================================================================ Archive-Date: Tue, 23 Nov 1999 13:05:50 -0400 From: cajunmikemike@netscape.net (CajunMikeMike) Subject: TCPWARE-W-EPIPE, pipe is broken Date: Tue, 23 Nov 1999 17:17:31 GMT Message-ID: <383ac985.74344832@enews.newsguy.com> Reply-To: Info-TCPware@process.com To: Info-TCPware@PROCESS.COM Hello: On an OpenVMS 7.1, TCPware 5.3 system, I have a terminal server symbiont print queue which points to an HP Color LaserJet with an HP JetDirect card. Periodically over the last few weeks, I've gotten the following message: %%%%%%%%%%% OPCOM 23-NOV-1999 09:30:42.59 %%%%%%%%%%% (from node VAX1 at 23-NOV-1999 09:30:54.59) Message from user SYSTEM on VAX1 %TCPWARE_TSSYM-W-CONNERR, error connecting to 172.25.80.55,9100 for queue SENCLJ17 -TCPWARE-W-EPIPE, pipe is broken %%%%%%%%%%% OPCOM 23-NOV-1999 09:30:57.66 %%%%%%%%%%% (from node VAX1 at 23-NOV-1999 09:31:09.66) Message from user SYSTEM on VAX1 %TCPWARE_TSSYM-I-CONNECTED, connected to 172.25.80.55,9100 for queue SENCLJ17 It seems that it tries to connect, fails, tries again and succeeds. I've seen similar messages when a printer's network card begins to go goofy, but I've never gotten the PIPE message. I can't find it in the manuals, online help, or a DejaNews search. Anyone ever seen this, or have any idea what it might mean? I've taken the cover off of both my VAX and the printer, but I can't find anything that looks like a pipe! ; ) ================================================================================ Archive-Date: Wed, 24 Nov 1999 05:36:39 -0400 From: Adrian.Parker@rb.cwplc.com Reply-To: Info-TCPware@process.com Subject: smtp & dns Date: Wed, 24 Nov 1999 10:21:35 GMT Message-ID: <81ge7d$h30$1@nnrp1.deja.com> To: Info-TCPware@PROCESS.COM Hello, TCPWARE V5.3-3 & V5.3-2 DNS resolver is enabled. I have hosts defined in tcpware:hosts. I want to send a vmsmail using smtp%"user@host", the host is in hosts., not DNS. The message doesn't reach it's destination - it remains in the SMTP outgoing queue with the following status; Delivery has failed and will retry Name server not responding user@host If I disable the DNS resolver then it works. Is there a way around this? We want to be able to mail hosts without adding them to DNS. Thanks, Adrian Parker Sent via Deja.com http://www.deja.com/ Before you buy. ================================================================================ Archive-Date: Wed, 24 Nov 1999 08:14:20 -0400 Message-ID: <5BF932D2CD05D211B54800805FE60FEB029E04FD@serv-hermes.systeme.cpr.fr> From: CLAIREMBAULT Pierre Reply-To: Info-TCPware@process.com To: "'Info-TCPware@process.com'" Subject: RE: smtp & dns Date: Wed, 24 Nov 1999 13:44:56 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF3679.B616B370" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF3679.B616B370 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello,=20 I must work. Do you use host or full name dns? If it is just host, you must = configure the resolver on the server with a domain search list. Can you ping host with dns enabled? You must configure smtp. Here is an example with my system milou.systeme.cpr.fr SYS_MILOU> netcu sho conf smtp TCPware(R) for OpenVMS SMTP Parameters Parameter Value --------- ----- POSTMASTER SYSTEM CHECK_INTERVAL 0 00:30:00 RETRY_INTERVAL 0 02:00:00 MSG_LIFE 5 00:00:00 FROM_DOMAIN milou.systeme.cpr.fr VRFY_ENABLE 1 MAILING_LIST_DIRECTORY TCPWARE_COMMON:[TCPWARE.MAILING_LIST] LOCALHOSTS cpr.fr. RETURN_MSG SMTP_RETURN_MSG.TXT RELAY NONE MAX_ADDR 8 MAXHOP 32 CONNECT_TIMEOUT 0 00:02:00 RETURN_RECEIPT_TO_HEADER_ENABLE 1 Cpr.fr. is my mx record : SYS_MILOU> nslookup -type=3Dmx cpr.fr. Server: localhost.0.0.127.in-addr.arpa Address: 127.0.0.1 cpr.fr preference =3D 10, mail exchanger =3D uhura.cpr.fr cpr.fr preference =3D 7, mail exchanger =3D scotty.cpr.fr cpr.fr preference =3D 5, mail exchanger =3D serv-hermes.systeme.cpr.fr cpr.fr nameserver =3D ns.reseau.cpr.fr cpr.fr nameserver =3D origan.systeme.cpr.fr uhura.cpr.fr internet address =3D 193.57.80.1 scotty.cpr.fr internet address =3D 193.57.80.2 serv-hermes.systeme.cpr.fr internet address =3D 10.2.13.94 ns.reseau.cpr.fr internet address =3D 10.2.126.1 Regards, Pierre Clairembault ----------------------------- Banque CPR Architecture/r=E9seau mailto:pclairembault@cpr.fr -----Message d'origine----- De: Adrian.Parker@rb.cwplc.com [mailto:Adrian.Parker@rb.cwplc.com] Date: mercredi 24 novembre 1999 11:22 =C0: Info-TCPware@PROCESS.COM Objet: smtp & dns Hello, TCPWARE V5.3-3 & V5.3-2 DNS resolver is enabled. I have hosts defined in tcpware:hosts. I want to send a vmsmail using smtp%"user@host", the host is in hosts., not DNS. The message doesn't reach it's destination - it remains in the SMTP outgoing queue with the following status; Delivery has failed and will retry Name server not responding user@host If I disable the DNS resolver then it works. Is there a way around this? We want to be able to mail hosts without adding them to DNS. Thanks, Adrian Parker Sent via Deja.com http://www.deja.com/ Before you buy. ------_=_NextPart_001_01BF3679.B616B370 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: smtp & dns

Hello,

I must work.

Do you use host or full name dns? If it is just host, = you must configure the resolver on the server with a domain search = list.

Can you ping host with dns enabled?

You must configure smtp. Here is an example with my = system milou.systeme.cpr.fr


SYS_MILOU> netcu sho conf smtp
TCPware(R) for OpenVMS SMTP Parameters

Parameter         =             =             = Value
---------         =             =             = -----
POSTMASTER         = ;            = ;           = SYSTEM
CHECK_INTERVAL        &= nbsp;           &= nbsp;       0 00:30:00
RETRY_INTERVAL        &= nbsp;           &= nbsp;       0 02:00:00
MSG_LIFE         &= nbsp;           &= nbsp;            = 5 00:00:00
FROM_DOMAIN        &nbs= p;           &nbs= p;          = milou.systeme.cpr.fr
VRFY_ENABLE        &nbs= p;           &nbs= p;          1
MAILING_LIST_DIRECTORY       = ;            = ; TCPWARE_COMMON:[TCPWARE.MAILING_LIST]
LOCALHOSTS         = ;            = ;           = cpr.fr.
RETURN_MSG         = ;            = ;           = SMTP_RETURN_MSG.TXT
RELAY         &nbs= p;           &nbs= p;           &nbs= p;   NONE
MAX_ADDR         &= nbsp;           &= nbsp;            = 8
MAXHOP         &nb= sp;           &nb= sp;           &nb= sp;  32
CONNECT_TIMEOUT        =             =        0 00:02:00
RETURN_RECEIPT_TO_HEADER_ENABLE     &n= bsp;     1

Cpr.fr. is my mx record :

SYS_MILOU> nslookup -type=3Dmx cpr.fr.
Server:  localhost.0.0.127.in-addr.arpa
Address:  127.0.0.1

cpr.fr  preference =3D 10, mail exchanger =3D = uhura.cpr.fr
cpr.fr  preference =3D 7, mail exchanger =3D = scotty.cpr.fr
cpr.fr  preference =3D 5, mail exchanger =3D = serv-hermes.systeme.cpr.fr
cpr.fr  nameserver =3D ns.reseau.cpr.fr
cpr.fr  nameserver =3D = origan.systeme.cpr.fr
uhura.cpr.fr    internet address =3D = 193.57.80.1
scotty.cpr.fr   internet address =3D = 193.57.80.2
serv-hermes.systeme.cpr.fr      = internet address =3D 10.2.13.94
ns.reseau.cpr.fr        = internet address =3D 10.2.126.1

Regards,

Pierre Clairembault
-----------------------------
Banque CPR
Architecture/r=E9seau
mailto:pclairembault@cpr.fr

-----Message d'origine-----
De: Adrian.Parker@rb.cwplc.com [mailto:Adrian.Parker@rb.cwplc= .com]
Date: mercredi 24 novembre 1999 11:22
=C0: Info-TCPware@PROCESS.COM
Objet: smtp & dns


Hello,

TCPWARE V5.3-3 & V5.3-2

DNS resolver is enabled. I have hosts defined in = tcpware:hosts.

I want to send a vmsmail using = smtp%"user@host", the host is in hosts.,
not DNS.

The message doesn't reach it's destination - it = remains in the SMTP
outgoing queue with the following status;

Delivery has failed and will retry
  Name server not responding user@host

If I disable the DNS resolver then it works. Is there = a way around
this? We want to be able to mail hosts without = adding them to DNS.

Thanks,
Adrian Parker


Sent via Deja.com http://www.deja.com/
Before you buy.

------_=_NextPart_001_01BF3679.B616B370-- ================================================================================ Archive-Date: Sat, 27 Nov 1999 12:03:30 -0400 From: "Internet & Intranet Orders" Reply-To: Info-TCPware@process.com Subject: Order Logitech Cordless Mouse for 20 US $ . Date: Sat, 27 Nov 1999 21:45:39 +0100 Message-ID: <81mrnc$36j$3@as102.tel.hr> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit To: Info-TCPware@PROCESS.COM Order Logitech Cordless Mouse for 20 US $ . ---------------------------------------------------------------------------- ------------------------------------------ No Credit Card needed,No Checks needed you can order simply by sending 20 US $ -------------------------------------------------------------- We work with all the people across the world! -------------------------------------------------------------- The picture is attached in this post!!! --------------------------------------- Our postal adress: -------------------------------------- "Internet & Intranet Orders" Vojmila Rabadana 9 10090 Zagreb HR Croatia -------------------------------------- Speciall Small Millenium Price! "ULTIMATE LOGITECH CORDLESS MOUSE SPECIAL EDITION" FOR 20 US $ We send over the post and We accept payments over the Air Mail post! So the fastest way to order is to send via mail in a letter, but remember put the money between 2 pieces of paper so nobody is able to see the money! Send via Air Mail and the money will arrive within 3 days but remember to enter your exact postal adress so we can send the cordless mouse to this adress (the cordless mouse will arrive within 3-4 days) Logitech Cordless Mouse Special Edition box contains a CD with the utilitty needed to install the drivers. The Installation is easy as surfing on the internet! If you have any questions or problems with installing the drivers just e-mail us! Thanks! "Internet & Intranet Orders" E-mail: internet_intranet@europe.com begin 666 log-cord-wh.gif M1TE&.#EAI@'T`-4``/____?W]_?O[^[O[^CF[^;FYN3?Y=W?YM[>WM7?X-?6 MW=;6UL[/U*NL)G,S+:[P[6UM;2UO*^OQZVO MM:VMK:6GKJ6COZ6EI62_O9RCJ,21E)N=IIF9F8N/E(J+J]YL;(R,C'B,I86* MCH2&C"ZKJ8.#A'V"AWE[AGI[?'-W>W-U<]A"0@"9F69F9M B(E-45#195L\1 M$4A)1$%"/\P``#,S,R$A(1$1$0```````"'Y! 04`/\`+ ````"F`?0```;_ M0(!P2"P:C\BD$PNF\_HM'K-;KO?\+A\ M3J_;[_B\?L_O^_^ @8*#A(6&AXB)BHN,C8Z/D)&2DY25EI>8F9J;G)V>GZ"A MHJ.DI::GJ*FJJZRD`0`#`;&SL@$$K;BYB[(#" @+#0L+O\+%`[K(R7\#!03% M#04(T=/2" 8(RMG:=@/!OP4%QZ_;Y.5S`[W!Z..Z/E\20CQ8\D_N1# [7?1* M\.9P`;\"LDMFKXN]8U<*-E$(@&$6A$H<^DLS`)B!<.3L\9BQPT0\CAX;S, Q MHP& &AH`:( !P$2.'2QA^, APEV#? !V=,.!HY^0_QKP9LQ0Z=%'C1TB`(C$ MD<-D`Y[]%,K$H71D20`]>'@4LA2'29XLJ$B=C; M^[2A"9^38;V="8&YJ6^)9,`743!YN=[:Z@77DX-;"5;<^$[Z0SQQ+#P#!CN$[3!>I@=S$C*V#[9"6$/EI5L1F[+G'D(!$R!?>768Q M6 2$K(GG!4 -Z!>;>APN=?\5`!+X8!H^COVT@P8%D<0565L-84(/2OF0UF - MU,!42"Q"EYF')L%(1(T\>40B/3B$99.-.6Q59&,G6BA&10L4<)Z35%:9!0(- M&&#EEEQ:41$"4W8IYIA&!" ,F6BF202&8:KI9I7=:/BF@;,I5@4]/MG)A$]6 MT#=G&!C.M44`LL "2Z&MR"8H%0C9%D6%4/CYYQ<%,%# A> ,4XPP;4ZRUEGN M916252;1MU%'L/!7XA! `2 446:UU=!12?'(H:QBD776<*+:JEQ#(_7W$DM8 M::66KI,Z8:8!G4XABS#?5 /.'C'<0(,0U5X+0+;86MNMMMQJ9EI/T7T&`&=4 MT9?_U[E1$<'828]%!IUD3@TGJ6I"D%MN>_5R.%M[I-5EKHC)/G'-HE4,<%$P MX;S2;!TZ1"Q$Q#I,+#$`%%M<,<87#Z$==]&%3)BZ(XLL1''')2?=8([^RM#' MX?GK\KS720=SP4L$8.D66"K@R\-YT+"Q%Q#J&]Y>[TY*!TLD.(,@ $+("Q%7 @(8+8?'7.QI%(VEN7C65>1;!:0 M,S#T8HPSFI@2C:0*8<)&]!R54KYA`5D65EP%_BL/<0\PI!!SORTV$F8N\) P M:P,2P]!](#3 W)=W\MJE5[RF0.=5CL73!J5_HD #0"]1_P"GL>=N246H5_$: MF(P(K?OP1=Q>>Q)0LB[(#: 3GWOF5@0P>^^+?.X\\0%D: 4!T%SO?2.\5P'] M]^0GTHWR2;R&_B#"_U-^*>I38::%: 0D0]1;@_4N- `"1$,!`80`!"*PP0Y&( (B&('F`(#!\O@" M' 0@U $I\0M&"5"!1T#;`JXAC?6%SG_ $" $&K!#`?*0ASO4( 0VD (7I,0` M$:A !2[ Q PX,0-,C$ P#A"+%3("`0IP(?VBP QUJ!"&=[!%`3#HPS*:\8P^ MA, '5C #% R `1^4P!*9:($G.O]1`QO0@!,OL$,$K,.*@'" ($FXQ28PD%$" MN4/;5AD64B`!:%XN8R@RH-*,;#8%4/Y !"/@QI&5P@#HI!@(85D2>0[A=(>G@@!C$X `\K6E-;;K6 MMOI"K3:=J5QC*M<(K(!$CSQC43=(0 )"E)06F*@=O?E-J'9@JE(5P0A7B%8@L$NM(T4UP%MPAG,#(3BL5!,K@@Y \:J/W4()F$>Q$D1) M"EBB0CSQ$(!HI%.=)?#9-?ZW7020UA>D)6UWO6M:T1Y `RS@_\@(;J=)- +Q MFGSM*U(E&EBF6M2WXOS <$,@`OZ*X+_]M0#PXA <8RU!3X\J`I^0@ \`X"D) M"':P$18;HTQJ8 >+WZ@FUK\`#O KW7 05"D!K >* M\A(.HJ,)(<$A86M#66,@!%] =P$P- #MSN$_\JIX`EN-V 02L&)KJ/C-TGAQ M-%9\`/_-6<;4B'$!UB@4FPZTD@QU;T/C6]L+C/*V="1R885+7 "/((0A#($$ MH)R%@C1 'D_)03\^91=5T6,C. #/4__(A8"X264F(O"56&82*U0/052S&8"G M@56DI. J#Z]1(-G ^@M*=X$9UG#Q/:,Q8LF>N,7@,@#D-"M%+8NJR M&G;YJVCS9IJ4T27EKWD&'IMIUT'\/0=Z`B!['U;"[>2I,RVYP8(&B#BSG8V MZS;W(N#(N,;O2><4#_LB=;Z(R"\BC3%*LP8H<.!,GPGH''+[O4:-HWPENM14 MKA*/&M5OH]7-[G6+0 -C+D-!-""/ZGR'.RUSE-%;)C*F;TW*OYI.T_'0-MP] MH2*W@,(ATR#_QABWV<[A0,=F+^P`0IG=[$*P'SI(#O:29QSCPVZV!3SY`@+0 MT!<^(ZBV`QAH0<^6T."68U)-64?"KC($44WR?WMN`G:+X-UC:+)'"F2UVM@[ MZNZ@_.6IDZ\$];O*+=-WTJD.NFYD75G#B,*9X!+W:6#\CV9'!P$F0'N-B_SC M8%\'.L !=SNSG??#7@"U7U -U?;SS\O<]LO?R]? "S[13P2G1H?KZ!"RVP0H MR+X)1""!A&MA)J'>RE-JH"0CP8TD*^,+^<^_*E:=2-7^,MRK188WRV=&_GN8 M7Q2B^P2$HZ&Z+A9Q-51%!\<,*E=G&V=!&[> X ! 4@(+O3=L#'A/_QHP31!P M3S)F4Z"5;2S7MZW!< 6#@KX8N*5<4@8=F&G-M%0 M1I1T0DJ(0AFW`!VP`MA A1H'`2D``Q:@,!177@#5A5X(:-P61,T71[957S;W M38E7?>R6?6ZX`G#8`1PV!.&2B]ZR+;MX.?\&-P188D[!J"P^\R2]UW$,6$%A MIX3,``$9$ (DP (M,(TMP */%@+D)"4&F'$6A&-@HHG@$ (SX (9)PTD=PUW MIX$SE0`$E4P[9DD@F$;P-8;:5(:M:&["!8LCT(*S2(MN.&E%D#$(P)R(2+R(Q8U `5P $DL)$G< (M< (O\ (S()(B MV0(C<&W,X(3-X +(L8T+: `7\ (K$"7 UWH9:%,TE'?'5TP#I4D\AD:SA4VB M-'@UYT2%I7/ZB +8]X8KT)0I, +=EUQ)P#TS6":!R 0*^1 1.)$5B81*J#82 MD $9R0%D20(:R9'_'GD"(UD#+5 #(AD"NZ=QW; #*" `5'@!+& "S0!\$:=Q MR79G&8)W-S5,!<5,8 B4125SI&2/]X5S1^9HZR:+L\@"3;D"(V !KP!,7!!O M#)8/%!9A3)!EEH E@V@$7M8$PY@%4UB33D@`7CF)KSD`JW62&( !9'F;9KF1 M))"6,] "-C!-)FF7"]@`.2 "J[EQ"V ",#!I$[@`)5 "#4@-,P`#*J>!CQ00 M>->3AQF"01E']5B4%I4!&,5HD+EN+Y@"M$B9E)D"J::96\"91T!PHAF?F/"+ M:P(,^9,_%6$>5Z",X!"7K\F(LA>@`W `(? "&? `M;F@M+N51_C8:-:WCVV(GD!*F2C0`084,+&F%^TB,I=! M#_*9&:2Z+OJ&+Y,@I >715\0*(SBGP1ZA&6JA/]VB@X-\ ([T (/L*8*^@`5 MH*!N6I8E\8A92+9WW]JIX1 MLYZ/UP1>@["OFAF:Q[#__A*V2W.J8&,EB-)AZV!!MC +S!B@CHB$`C "/, # M&#"R#+!/!W `!/"W:/4`;(J;NFD`&]L+%RBFO="B'="KX-@-+S$#.< #%_@: M-BL7#2@-, "7`< 8O?0+I*A)T"2IM"5XI52U3O5;FLIN;Y@"E"DT+5"9(Z"G M2S Y"@"_TJ9*R " M_Q?P/;+*# @`'L:#C>1`S/0OC"1`87X>PAPH#400AT@F#K9@9/47J9+ MJ01D:- GGJK4`?FX>.O6J0&K`^;:`@SL`O_H/1-,!U^I,+&@L1H%`#C5CMH&2?-Z36.81/1UC^9VP++8M5D,L #+GEPJE5RG MA,];QF6\C 40:609`K?YRF2)`1&POW&*4?U94JK&TX[6L4H M(+O2Z +DK,7KF0&DS :G+,>HW,ZFK##]E$&81+1DK#:R,,?NK $M<+.YJ@+ M+ ,48(@+X (S( *K<\.$V@$I8 +U0E6)2KJU%3K+4H M`*1;3,X`2XL:,(=;TH=ZX,XHS;C,.,.\K)\L7_,+ "(A"]X2 `'J#3.]W' M#]#''I#7`?UV%M `H@R%T"" -\F%.(5,+-=>`>QC,S='NR6>.DI]B\<\+K@" M#0S2(.V/#8DS")D'L:!"4.#91W!V7[2$*GE[NEK6Z `!#YPV&BS7=/W:=$T! MPMD+UE=ZEA3`36ZT 2UBNU\HG1*X8E1YJ9?`"8TLMB4'YW535F[ M!9O.@+*$N(?;MP=Q>_EV>ZF2(;IQ9'K3*9T];L@L92P`.0W;Z"W;F>("(:"< M>8Q[TK*B1NRTE+1\BGVO2W1;9GB4^[J/GNH"6FS9_[H"*! "CB7=3 `0BBC4 M8ZTV_PY^/P\>X1(.X2[]X&$,WBG]4RN@QZA<`/Z,WG2M`@@X`"80`@<7`3-0 M`U@8G3*6CM$\BLCWDV%(:-F$6Q9 49CJS8D5,;&(`I3]KY9-SDV)`B.-X! 9 MX>SX4@>UA;NX$^>Y&(-WAANR@W@XV#FSKX,XO^L`A1 11BA`3.PAB<) M`Y>KW44HBH(I4.\8P#K4G>&F5'?DV.$T7!&S>(WGJ>8:Y Q,BR)0E4;.14@^ MY4ONY(4^Z$U>Z(2^Z#>-X0`A`BX``>N,RG.-WBK@`0E0MPL@`@HL`A9PQY^( MR.:8YL874_'JA0#\U$3E0?;Z5Z.$HU!\M2%PYXNWM:#,Y_]^GMF!GC")WNN* MWM)-[NO _M+X;.%?N>DIH*>H/0`)D-?.[@%]#.'_V0`_EP%-V44O:9,NOM3' MUY.E"]PU&GA.C-%T#ES([6A+R=Q 'N2T6+N[C@52+NR,'N^_3M;%ON1DG>^F MO,HN``_++L=0;L.W7$$"@ (6( 020)W9K=VY?6?;'A ZU8&2!,"5[$'BGFAU MM %6VP',@V36UX:4#>"X/N1<_0GD$<7%3'$Q7.3N>?D_ *7;9D%5 K_O@$BJ"(!+7)E*(6P5N,&N@>]."_EBG[S M]?[V2@[>TH/'F/G2_RZ@28A%^".;T<2$20]\$]?B*ZIWI%O-,S[UXDZU.;H! M0H.UFSK9ZX[K"[V'HI TVT<5G^$KL.8.?G$LB\,7]4$PZ:(6KN8#(P&E&@$2 M1$"D8!#&O, +2D[O=1_W+"(F,R8^-&9R.D(R1$Q'-DQ"0E987%Y=3E!95E M)<5$(P! =I:VUO86-U=WE[<7MT8"!P"X!L!G]M@8N0=!5H1'A!9&I*:AYE4Y M6_LXN9M6HP8FV9=<2FK@/#WI?+U="0F)7J(ZEX@H$ DI0/]2CXM`PDN MD=+ 3)D"!-0T="/'`(*($>O,N;. #Y\_?P`5\G@(T2)&CB!%HJ3ATH8.F3IY M$@$*Q:A2J%2IN!CZ4[NX]`\<,I6*1%2V&8P>,6CV( MUBB6K<8.#=NR@94%8T<-'KEMM1LRCXHZO][3AE?"KNZ4MP(6B$"AH5[;]8#I M8R&L\##B-F?DQ*%(L0X])/.CLLHZPHP0"!I(A$%&'K'@`DHVJ&0#E391;03W MQ"AEA=A0>0T%$R3@CL0233P1Q=OD<0O_('74DFM%=_["@IVVJHAG``U2&*$` M\,:[T<;ZJ$B(2(;,T&^_A_QC+$ [(!NP0,L0- 0DD3ISI ((3;I$@PI70@U# MF$@QQ9'$*\( \8@$-1NA@@;[BVU/( M^HC,#\DUW# @HC@JLLB.!?(@<*,#$01)$448\:PD2;BD4"5.7'H)%)E,(1,5 M%V@S8801VWP5UEC;?''..5N\%2T7\Y0OKO'L"<" E_[Q,3YZ["HT"\'*6/9( M1-5P0[$X''W4R8LBV\C !0BY+#/-).#,LPHJ"(V&&S;0H$L+1?T$%#%(Z3#5 M55K1:SA9[;T7_]^?]FG'G._0@9.MMW+%<2ZY"/Y+GR8\68!8(P1]6#UD"[.B MV3.,3'0Q::F%S(X$H(RRLBD'47"S324`+;1)TCU--791B&FF>&=;@541FLD7 MYYQUGF6?'@%&Q]9^S;$5Z%OC&MC?\O1IH),-#(!X/D$+GAI9P:Q>"&-H^Y/C M43T0D$RC2D/F%K,J(>CL9)),4CG=E2X<%2846($W55-:84T$`G;.>;MX0$RXLLSUSRP+09@R-E$X7AC M6FJMS8A2`QL@F\HJ/?/LD0MTT$$2#2KIL@,PX79/% Y=:"'5#N?]<_^GO>^= M*I>R=%$>5N0)C^/P`(9F/.B@_\75WY_U]"Z !C00`5 ]DWXQZD$%*O0^SX]$ MDHW]()*H:R?!)M R2R\M.=R39=>!D@Q6[F 3'X!;J=[%BMFH2E5W,\$_C `5%V<#,`B$,8#0".<*ZR0:5@,!JRZ $/6).#Y,A"*SB !@`&X!SM M=! '.:A7=:X#P6RD<(4M=,[@>$8`.$@/8 '0AQ"G)SW%:4][C&N1]= !@ 5L M`CYZJA'DBD47B6GA4(;)&G\TMC$]9 1UDU&=R#2SFO,(F/3Z)$"&]8H\ M./)5%=]!$&4IBUFAT\_H- 8@QSPIC),)Q)0PE2DKH6QM_FO;!S:QNU# [#4& MM-NJ4" "Y^DQ3<^(1C),,!:DR)"&7'F*5[H"#G%XA1O%\4$,<9#(30) F^'\ M2G%J`T?;9SR("S)2)FU,#`&@!`[#E:.7A517/=\7/J4\A%WM6 M&MH'/U\VR5H#LHR!6/<139D,!#2(008BI+(*;8"9J8$C*%CSKM>\-($*M"8V MUQ1)/^[ !,K!)%*4_\(4GBZE*8I,AC>MTTFN[&"&]!R'3=$I27+.8@",*F*M MJ$>]J2K1G]BKE0(TL!++"?%PD9-1G!C*JQEU[J&?6Q_[N+B&K9E.?A_CB+;( MJ!F11 `$,2B-2$'0OV4V#0U$7*4([W_]/ MQL&(^0R `TJPUQ+45K=7]6=L=VM;!%0B`P4`0-"22#3PT"IS,U)N06[Y4(PI MAG3ONR@=\B"@U D"Q)7/8,9JQ!<0ZM MN;086S'<2[A&)FQ1ZDA'-5-&18"@R+,#P09J!ZI,`!:.(F"5*&"<7@6BH .) MM?&>WPM*?0)M`J4Q,0T`#,3\VG9HB=;GT IP`=M%X3OZU:^44SG6LF*Y(/>I MV(6EE>$-6V2ZF=,U"2X= .$'1W M"2UD(2]:U_X^M+$UP# D#[B4L%UVXLX3$/-)C N$:6ZB2)=AN$KJ8_4C]QD $D3"W_T[*XA:/:LXM=7=Z#\O >IOH&#R\1>!V(7->, ]%95A Y(@H M`"*;^,@)-^(0B2[P_ [1>QMX\FZ'KMO<3GI.#(_E?" ^;2)Q>6M+VG!&O3VV M<#<(!&&_0)9&3G++WS/OE9O'C+G!NB[KCXNXETOEK@\Q? M_Q::Z;L-LN![;F@!-,!_#0BXD DLZ3\;6I\,WQXM,5V8:3.7TUISJZ,NZK7Y M<>2ZQ"S99T #FC7ZCT*Y`R"^'$UH/LM"%VT&D+*2BKP)HB^?ZT,<$8A #H1>> M\-I?O!$17W!=BW_PZ?,;\=>HD M4D_=T@[E7LT5WJTU0B3/:N_F1,21!LF3!JDWW"D;*HF%M@,': XL_(B2)I K M#O_)D#P)`)!J]X B`'RH`0@C\)J.!<-/X(I.>@# `-A(\5RP!0-N\/ZMV1 * M3]*C\I)E,)A+E]" EQC%4;8-4C".4H:)_T+B=4@"-$1#0LYN$UAOI60/UE;N M;D+$!!2/`9='%LRIJ%)KI]8IQX2A+#90G)2*.L8)GF8`&_1E`!"@`Z"IX;SN28;* [[*D0[2(XK.>0PV5(1^;C_GJD;6N0Z=,L `4H %> MR="*T>CV,/ $\2 TX *F$0)W[ K+HV M;F2<\$HN`&4Z\5S4!1U%$0MAK17N3!08)A5[DH6HPKX`0!_ED XE0##4[PXS M4BFEIP`DP (D`".-;BD93P_7S_&(QAKA(=HNC]JL+3&BY:U^Z?,X@B5=!W8V M$4)&@^3.4:72+D-23N5(48'._\L$#, G4[''=FPIGL,V=$Y!S&,BP6\JA0P" M-, ">D0JT8\%H7$C#ZWI^.EGX,3*[B%(!J+"YD\_-,_^'",!*E&,6+(EK21< MM.3<3"I=0#$478TUN)#.5N[%>FQS1?=S.*-Q,+&*K*2F M.:E _K!FB]PG(@Z@:Q1@4L*&,K[NH\21$]425%2OO H0+EN3%%LS)DQ@/4?4 M2GOA/1<@`@YSBJR*(JFR`#RC&:72&?OS!<]4*2$3*Z6&,BG,.FN9L!1KI2A-U%PJG`3K#8!*-/X]S M`!9$&&64-\F4*OW3&7,+<6"I32MS)",.3C,3+-_@T[YH"8W49& R+55F29D4 M/#-T%$6!0^\,9JI447.5%J3@^B#@W H`-P,BX6(4Z18A*K__5",QU=\$43&A M;GJ4LWRV\DVIC4>1Y"0YSXN^QDXQ\4A!@^S44M50ZD*:-#SA M`U%UU5UEX02+T@(:X!*R8 6/<0`4P>"J4EG[M3$#,T9'B0?)IU J[.HBL7V4 MA$%1]3._;B20J4+'JR9%4;#.Y `'RSS=;@6L"1[?540%X/H:-0/R\*P2C49] M4T$0,T7]E667U4SW, <9A\H(5B2G-8LPAI>TS8LRSCJOTT'49FVZI$O(BUQE M]37)$V/9;A17@ P\UEUY55O8" *F\;AD5M];,K(0D1H.- MW*@M`3507\QB<]+=6-,U>.1O`5:N7Z7C0P[9-QR31&!;/ M%$XN9LD1RT `XD^+Z$_KI$LC^$!S-_=L.(43^^>D4HIR4E/.`C5$.)1698UT M7:!263=7018!9L>WA)$(]DD+V (C!O%D<3=W=5=]65!-?Q=SRI;:(M%]=/;+ M,C?T6H=S8^Y)79\(;$0` MOH8CHY%KV_\W4R_5$)TN:2CS4R_/8!$T0;D(?J;S:SZSH_ G7)+T?\6U$XJ6 MI2KV>M6U0U> "_.61ZZI@4<4:AO5M[AT&.V#"^#S\9(29D\663GX99WN(Z]L MN:RN)/<#PR@""3/J$MU64]!&;5QU;@,84,TK1 CX`.^&-FCFQ6AFYQCXA[\P MB)VR`R:X?+.O,!0C>M!T@YVX@W8 M99$5!K'*<<2GEFS)ZIC%*Z\-NK"5#ABV4NZG01QY-(16AHN6W$])RA/]]#N=R7I=[XQ?;PO/RQ_PS9E'M#1XE0Y]M:LL@"\. MYO'@E5?1H(B3E96].6#[19Q'N&RO!F'QMTG&4DK<=E6?=Q)F,E0$:(Q9JHS) M\Y)S4KU&V@3:N)^O%* 'MZN8D3*[=&AX9@M0V;8H"T$<0M )X@,48F].5,;3WZS$JBSD:W>_PI(=UE;EY#,/NJ%'UG%$PFQFK4Q$W>68?X%.(7SH09]GA\B0&9==BHBQ9R]1?"_&5 M(9I@J:Y !V/+N"R=`\1C)&.C6KB+(P`F\7HM49.>YRSV2OH\#8NJKW<%.H"? M#_LN+Z&>HDI;MK2KJ#FRB85@3/8<4/F#N1FS^W5K(6_9M!)4.^?J*,[++AIU MCII*& 28.SKUP*1)9563#] U6.ZEH'1C[(T/LFUO 5WF-$`@N1.0/)8 MP0JY!=9EE[N#>].4B(ORA.1FT;:+.J^T>UFC'S9E3O-M6B9#X^B&2QJ3TQBJ M-W8!<#6]112@M?]%E*MPYZSHRNS$JL8:$=-Z?;T6;!U3.3L;P.L79S1OV M(Q;DH\:%H^?6N]V25&""5GL'GY,YMEVAP@W[PEOW!$-6H(.;CH$7+NY$-_%C M';X/IQ?W&0,N\@1TH3Y[6)[R!%;!W2AI1L;@$1 `A2 $7<%EMIBMZ#,IF^K/Q=-(J%1LZ/Q\2*Z M9G5TNM]Z2;A->>\TNYM7M5.&0C[@Q@-+I&$FS0.;O"]97>NPB>*\]F9G49-@ MJ\]FFC6!F0/9PVM$8&(!B!R.JB2M\%14N8U.9EU]T8$PM)VKTU!RE[W_C0E; MTJ[?N:,KI*G3\:GU6N/5'/80X&8<.K$"JK]JNI1HID'=UQ1>@`BE]7%N'\VZS:FMYS MV70*O-CY=Q'$!:_C&=/7K5W"VZ1[/*;2]9*K?8$17E%YE;$;.[@+C@L0)CX& MQCR>'*$%0]WK^S__==@X7J(MDUJW7-@;5)A06[LK':^578S9Y:G].KT(GA6V MOD-E8OCTO)-IG@'WB=N]99HIAYK3!V'8].=K_VDGA B/\:E67-DQ>Q-:L)OC&L3DQ]Q+3J[!$Q#KHPDVHOTFR!MCJ?G@Q;[F,]SL@UL$ M"BX+)G-0T**XX/4PQ JLKM)JI_R?'NS]L+S1$R,LJR6C,GID1DQ3QB4*DUV& MP2 ,M_THY[[*;;WHDMC*HQL(L_&6*^[1Y=H;K=,L@3:O0Q<4-.2\ M7&-,7J,%%O\F[E_Q20$%YM7:;^."(P`(,I@(D0AY* X$PH!0*! ,3 "U:KUB ML]HMM^O]@L-B<6 P,/\@%HV(Q*+I=$2:AMDLJ-\']WM9[Z_W]0T$! `0/CV5 M!0@H#CHV$@X2,D8N0C[:_>75<7;6%0R (HXB&A0@H"&HJBJT+B@P+,0R--36 M0N!"$$E47%QD_&X(?WR$B!B/B(PLHXRDI*Q K[!,K[BP7+M8KU2S0*>,2#0@ M$!2.904PA'!P9&R8S,S4U.#,QZ.(7#0H-1D<( PXA\6'""HX!'+Q<44"PBH, MK_#X\A! Q(9ARCA1H":"!3=P1$A8P"D/23^;,@7*!(A*'X!F(/$9Q(C2(T66 M,#4J:=*3)U%F1)$:90K!*33_5BE(L.#5+%JV&N"*H(M(+U\9W&D0%F*KB*[_ MR[X^>\:-6HMLULIFHT8MV@J0XP99I** 1 @,'5S,J#=#6U<1)E; D&?/108$ MEHR60[B#1\"#<:\HM!*YX>0J`;U,KOR82Z0!JFI)D*#A31P-#'ANVK-39TG5 MY@"$`A73)DZ:E6PRTI-R)\^>GV(')37TU"FD"%IIE,5@^5,(4(M$J/KKZK . M7)5]=196[8H6W;69=>']&K?R'<09N&SQ0@H,&F#,@P%R06(KBPHLD"!B13P7 M&Q@PXH\"`)V#@PDF`.!8`WG-T$ 5"^*0`P`0-DA%#SR8@ `]-50&@P\XB$"A M@Y;-4T-$$.;0@(<@2D8%#S/L@. 5*Q;D0PT[%(3B_X@3'H2 #P@D"( ).>P` M`P`U,/3>%I$4@$8M;(SVD06@X*&2'JJQE@F6?K 4&R8X@4D(;9=4F65O/Z$) M5%"F-%G4*L<=IQ0LLBCW%%11L5%!55=ED-4&Q1CC%3,H/+,6"]@@ZH*B:"G* M77D:1+ `*'%M0,(")LQC@@0%C%& ?O#!D($!A!@`BP%BX## #@@XAH.##3B6 MX$2N\DB%#YKF\)!FD=$*JQ4XZ)H@D -$I!D`D2DT@+''5H&LL+!5Y.(`F&8X M`VP`^ B !C4`4"%G932IQAH=P0&'!:=UHMIJ,?VAB1U\B.FE;F$^PD=N\>:D MB;IG_A:*E\&Q.10JQB%'Y_]R3MF2"U6\6$7=,-=E1V@*:AT*'EJ,EE46=]Y8 MT !]KPE4J8HUN "!>@(%H$ '@:U@@0$""* `J@"(D)>MS>*<,[,[9P;9S3\# MK="'.>!PD+'.[NSSST)'6+05\M700 TF:*!M#1ZZR"H83!H@;FA1QF&!2"-9 MV9J65[J[ASGROA13;GFD= F[6_+;B4]JKDF4WF\>MT :L\ABYW-321"!5=,) M\R?$V*% Z#389'.QHI,O>LU:X;P%\A@96"J/"*=N1@4"*\\P`@.:=]%J#P8Y M*(&$!LW:^NN\!MMB@K+_&NP..R:=,])*\PS [EE(S>V+%@84V9 R;@UNUZ"Y M09K_"!"X5.5JUV^9O6Y4A)*>'XU\Z?9+\Z9MY9E4WAW<$\,A\,]1<2XU)W-V MXAF=G@V[\W"@7S4^L5J19X-RE3/+HP52SD8PFXAE2+(PZ<;E[%/`/XSEW/$ M!C(H ,-\)[USG;)G3A@`A,P M)UQBPP1'9"DUE#S?2=>I/KVY*8S)F07]%):G/3GL3X"BI<18T (YZO(%>=5I MY;S#`F!&*H_G"$$+BL2II2(VL8K=3%,I:M$W8%0"&K6>6+,W@1+00 3*_Z[2= L3$" MGQY0"X+_X,17[<,)[S8WP0I.['.A\E@X;$"R9RKI'2:06>UJ=@(PL^IGGP"0 MCH[5I&@R:TJ)(K WH5(CK#W82XM0N#W-] /6,<9M!W73LNA5IP`5#X]70%!A M"A8=3!CRD$4)!1(_X:L(7C"3F[S,!D?7(W&0*I4F_(<)8%B[#E#)EC[;M0*\ MS7RD'>4=TM=%+PYEO7!RQ5H#UQS81N<"%; `XMS!1F38=V*^M*M.<9SCO*)% M#C^MCQ;\]54CB]()2X""HJ$0%#,X.=*2MJ89T !=Z9:F`57>J!TLG&4::+@U MK8F$*EX&2BN.64UG`-@7U6H:II?>\ NADO@4;498@!J M&"XH16Q>4K(:K:=,0*SK-<PCA_6EG<&W7[N+OZFI>2DT/'AMD%8R,;T5M, M)Z-#T6CT.N$`Q"'TM!L^[3Y8&BH=D=X1M3V RV9VLZ$F:;L*(0`#>&S#X^07 ME9RPSC.7PL-I?1\J52EK>L*V%W"E[;RW@MMZWQ??>.5K/TT0;/00>TGI!'BB M#2V*1C/;V8T^P#^@[?"G.[DECX02:0B:[=Y4. 8Q$.\>L'15`> GY.0=\RA1 M7LJAO \!"8B3B@WFWOK5>CKRGBL)W/\(QT/Q&<>2$X^/@QN+X1KRT,_&XWRC>M@Z.*=.:;@3O3^ 1@*91=8Q_0'+-@!!T`,%&("YLCUT%I+4'A%=[ *9ZC MH9>CF0+QM8(R+=\#*E7S/0FYS-(&T$$GW,#UE0W'99\>$ `$3,F D579A9\7 M-8G>J%DKH%__>]'35.A)&O&)O&V%S?&/,^!=[.&2+OV5N0A3>OA?T2&;.@U= MP0D?P@%?DSA!P!0?%%3 1$#@$T:@\W@-])7&-F56$FF?OI2/'TA !XR*296< MV;':/QB%6K$6ZMU"/<$77,F;XAA#W>G:#6:,?OE26Q#43P7=OYE

L',HBE!FPQ7!+1 `T'A(B85UTPAV%@=]542%IK-J2F !4A >:4)DBU> MFQS?2L632[68ZE4`,,25&R+#H-Q7'.$8WT45@"F TQ7;T#5!D1%B MV2DT'?FI`KN)45/,&JW)5XS9%EVM(G[U$U_L7[^!@O]QC\D-GK(UFB\6(-(1 M``!X@ U0``"4P)817Y,,P &\0 X(9H3T&P /8@ H`P 4TGL*U20`<0 L0Y$$:94,YXD*^0092&=:=6KEA M7@%@5#5JDB9Q$3NQ"1FJ`LNQ5$O-4R[4$PS.E/[@%G;07][57U3=X3@`GAC4 M(A :W3K=9/ Y`0"H@ Q0P [,P OLD5":0O\Y#"4.%.11$F8A)65%=0138IM$ M6E%E\42P4655FE8"GAT8(9_YG>'+W0FMM9\[U-8,FF.AZ&#]F< KBD,LYN$7 M&%P\(MJ1^9XN^AX"XJ,->, *Y, !`$ A+J!0M@`.9$!A`N>3)6-%70!#%I%/ M319JE,D&?@)&\<2AE=SOI1=J#0S+O4*;J5\K+0Q)KA%HBD"NU5L*9 S>K4!I M[I\X2$IJJJ8MOF7!V:/BX60`R( ,%$(%% 02*AQO"F9P\J=A#N?72,]Y1"06 M@5BZ2&4'>%YTAAY6$H?[K);+O=Q[I9' M)P2 `415E6U:"998`13?*AP%N[6;:TFH6-*<&WXGX_C2Q.R3>0:7,+VDB&;D M'I(@;()ID@& !2B !J"!"6Q 0(R @_PE;^: !=1HG#)6&62@0N;HM85 QXB8 M:'4"`HB !0R83PBA&*9<:KT:9J9?ZK&?K M>R+"*3, MZDNL3 -LPMW(Y9&B@:M]I-NQD@N*I0QF1\0T#J'@`Z4Z!SE$JT7@XCP&HA^. M0J.E!Q5 :Q6(21(.UU 69;IR;*N"RRG00I1575>$A.#=J@`L" R8K&D1ZK.A M(%(43**VX$C*US!\Q3$,;#-,3#)@E+/VWV.,*.@I6HEF:RYJJ_=@+&JA5@`0 MP##":<=";1=DE\6NZR-%F7'&P9^RY;R:00280 1LXMU0IG"H5 K*26:^75CV MPF<>@P@`R@B<9#/DGX>>9\)"JSOJWBW&YA8=G/\10FP4H*@"M@D3!*:J1NWA M4L'4V@?$.=;$%5%7S($I<&UQR&1*C0)')D J_ .38F?:HI$[T)B%UMP;+D.N M-4Y?P(&P^(N!F+M*IP4!&EOGBN3`0ML^,!#Q(H6)%)< M.*$7A! @3<3Q+I;B8DȀF96T'!!8\VBKUH8_EFJ"A>F3;D1',Z8F=6:@I MYD\(V-;-O1'JKB-Z?A@@!>TH^>UV#?801=0Q*E=V('9[9&=\[H2 :%,<_F)Z;X0G#W(]T M[,D:E>-MD4!IHF]'.$?_>BYLZ! @`A9>\ 5%`B*<%-0O$CY;.@VCX3:7!!Q$ M:>ZP.)00`%P(@BA$S>10/;R0BVS(CM#(!J$0[SP3MR@$#"#(JE3!BQ1)7N ( M$WN+%2/($MM(%AQSJ611'1+ F:I 3'OP`'#*,4L++"-]H"PD07&TB% M+N#"9KK5ZD7IG7WG,O2%6@:7^K9C(:VFH-(EQ%[K'])N[2IMC*:JI"D$MZP. MM_2*8]P*0Q"$M1P+D!SQSDA "$W&)4N&)R?+B]10LD2&LMQ.K3 +*R<-TOQ( M8C%O%W2&4]U"&TA9UN9IPF+O+V_D4;2"QRP%=#&%K.%Q;%'H,,Q5,@0R' SR M_PEO*]Z&0:?"Y@M'K-\V6\ @J?RV21-$+``\4Q#G' MLNV\*22B+J0PP,"8M/$]FP4C MZ<"LUP%\)/I)-,S!VYY@0/YP0#$$,MVF+R&_1#-Y5?_@PN\B)S(WE[4GCDKA M2EH#^,"K'+86=Q#.8$J"%(D5F,"+5(0/Y$74Q- .5 T&50$./+9"S !#8#90 MJ] /(XT,_0QG_S06:%?B*NYJ`X!KPW9KR[8.-%)3X3)H/-89M]$ZXMZ :&5U M\LV2)@6BRFP:)K/]K"TP)$X;8?0&#+)&QR)'Z[6CM?#?)MT!CC2SU:_Q#2XX MXT#^RND`(RXAW7+$.5@;],G(/O/M>0SR=>.:P1.BRD^$*HPK(;=L/4Q=J^7^ M90`FGC JM",U(X27N'%(1ZQVD_3\CO02%I\I,&TXK^KPCC=2YL$)BLOS3ES5 MH?%!WYYSQ((*JI)7=N]$1T?_3+%M79?+:&"B.+0W%"U90^WUB1KX7QMB#5_K M$FXK`?01#D]XC\?%)/R$I8G+U1;TX^IW!SCW!4A%`Y"1:T'%`]3/VEZH?O<% M1D%S7)"#5Q6D5=;^F"Q>A4(RT%" I$G+D_1* [OIXFRM29\3&0-L" M&^CR:%0=1E'Y,2"Y<]-6#%Z%GUPH<^NWE>^?BH>&<[2WY*JG0SD`9FD69]FC MF)_6\*W/F3_;[2KN]?N1AYGJ-Z71,Z-*_CBB.Z MWVSYBR,5MVE7"<3NHOFUI-MXP"1A#3^X;T)=121O%@S[%RAO%HAW[R [\&C! M1!2O_Q8<^^/!.1PO12Z'1D=80'I#HJE;.49UNW68.I+;.9:O..[5`JQ#D7I: MWVM/;6;%```\Y+O'.[O3MKO#^PW(.[ZS]@T`@ -U2^C\J M7!-L^M-=A@$#3[);QAX=8[S\Q FFP84[&)UC^[C;>:$7NLB3 M^XI+0'39PE(`."#\40;2>\RO]LQ/+,\$#KB<&O=*R MR:_O[H(A2;=8BP8(<0Y]2(W<2#L[/8M0-F?G2(04KT*\" ZP,Q,/=?!H2#V, M=H0X2-AS"&14MH,,R6/3"(WHB(5@"+/ 2JY0P1-#H)C8=O]Q='RU)TQH^#TF M`C[@MX'?%PZ+GSO+JT*Z*T(79!9$Q<"_9U? %RW9`G:E7_HOE@)W>S>/+U<$ M'4E$S "0\'/O&# KXP`3'*\^^ZZL?+)"]&Y0#TM$O/ZNV+2$!$2VQ#,.Q+ZM M`%-0F\%D>S(C`GGHK5 M%\QFXH$@%!Z&[8+;X!X07#B+5;__YU-KM0:3&9,FGT(G0X#$0T9%@!T$*<-% M0QR)I\1,`,O#G88G3D?,)HD<@)X!4+;@0EF,[!G,3*B,[3J-H.UH;@WL[H6'(UD<3Z3'H >_1FIUP M32=V=\1SG!K"T=6&FGI&$YX9'N?VU0BH#P<.0@8)0N$Q,!6,'0L!Q)O8SF". M>^8.-:AW#\<.&.-$CDPVS.1)DD]N($MI90`U`C&AS81YQ@`;;7+@R.'F#5Q+ MH$&%#B5:U.A1H5J02GD9#1JU,&B(8-/)3>=-,P$(?,NSU.M7L&'%CB4+5,2( M# M2-7E)__.IS3C7L!Y@4[>GG9]E]>[EV]?O7UP,6LRH,6/&" 9LWSZ=^^;: M&[IQ;T;V&0[P9L]YG7)@0,/(I"8T2*#``!UAL24M@WK33AU)\\94GGS M;=RY=8];Z148KP`"`C (\6(#$Z=HLCV^FE,;; ,^,^RF7MVZ=:5+G1&H`X;) M@1"(`3A3CE..&[IS9L.F2V=KWNOQY<^G?^N9S&=(`!P0D4$KU6R>DTTG`M>S MK3X$$U20ONV*<(J )3+80#5JF)M,LCC22^\FZ1;T\$,0^^ALJ3+N^Z*.Z,[I MP(@VEI/,K@W5D_' $&NT,<3>M-N.M?N>`4"!#% 4$"?)-)01-/\A:+QQ22;G MRPZI.'ATD$?6`%C@`A3MDFV;&&6`=A @@@R$,$&`P"X;X #&* 5LMD0 M4$]71-,;U51@@\WM#.\.N$""#Y*U`85,90J@@2\NG"M.)$.ELX40FFCY6P!@\ $'FY_X&5P` M=NXYZ'HX8F4MH8G^&>91`/@'!QYLAH&?J$50.B15GNB!AX2^O>1HG\T^I(9P M-(#A9QP^&?L>6P+T#H!7<; A$C%F/4"!0^<\@-AR1A2U- M&@@H%002"65=)W"(9(#)`:B\D$@>:0"!&JIFW.EY1'G'SN$@`+K_'N^L\1[$SNVQ;]\0$=(7Q7S8JU;D6QS*#J5M%:M[!PO9A#Q9-P-T. M&6$80J@0<[4P@QJ*H( %,." #5 ``AS(FC@$``&&@XZ10-.>DI7L9.S+8)BZ ME;.I?4)[F?C#)R B$84T@1TNT(C/]H&1H$7D7!\!&PS !@^+N(QJ-)P''=78 MCC.>2WNG< )'["$0?M#CD**0`.L0B1!"%B-*8C!"$I)@!/P$J@"$LKS&A38T M!,+1:079ZF(I];<'TA5CC\(R7G]20L# M;+ >?R!G..Y!`G:$@0OJ:4=[WO.>]LPG/_?I@A?P MTP4#)6A!![H"$T @G@ME:"R"T0M>^ *B$:5H,"SZ"X@6H*$;Y6A'/?I1D(94 &I*4,`@`[ ` end ================================================================================ Archive-Date: Mon, 29 Nov 1999 08:33:19 -0400 Date: Mon, 29 Nov 1999 14:31:42 +0100 (MET) From: jsa@aua.auc.dk Reply-To: Info-TCPware@process.com Subject: Multinet printer problem To: Info-TCPware@PROCESS.COM Message-ID: <01JIWVPPWZ7S90PO67@aua.auc.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hi Process Software MultiNet V4.2 Rev A-X lpdsmb-011_a I can't get my konica 7040 to work properly width my Multinet LPD symbiont. I'm using setup modules with my forms. If I encapsulate the escape's between P and \ -as is standard with other print symbionts- the P's and \ are printed. Isn't the symbiont supposed to strip these P\? or should the printer ignore them? If I omit them, an extra LF/FF is ejected before the actual print begins. I've defined MULTINET_PRINTER_Q_FILTER "f". (Otherwise the printer ignores all input. The spooler on the printer is a FIERY-spooler). Is there a way around? Jens S Andersen Email: jsa@aua.auc.dk Aalborg University Telf: 9635 9464 Fredrik Bajers Vej 5 Fax: 9815 6970 9220 Aalborg Denmark ================================================================================ Archive-Date: Mon, 29 Nov 1999 19:02:10 -0400 Message-ID: <3843103C.2406839A@mail.dls.net> From: "Ruslan R. Laishev" Reply-To: Info-TCPware@process.com MIME-Version: 1.0 Subject: TCPWAre TCP 5.3-3 & VMS 7.2-1 & PING Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Date: Mon, 29 Nov 1999 17:46:04 -0600 To: Info-TCPware@PROCESS.COM Hi All! I have some problem with ping&traceroute command after of VMS 7.1/AXP -> 7.2-1/AXP upgrade: $ set proc /priv=(all) $ install remove tcpware:ping $ instal add tcpware:ping.exe/priv=sysprv $ INSTALL LIST/FULL tcpware:ping DISK$ENERGY01:.EXE PING;2 Prv Entry access count = 0 Privileges = SYSPRV Authorized = SYSPRV $ set proc /priv=(noall,tmpmbx,netmbx) $ ping 127.0.0.1 ping: socket: permission denied $ $ ping www.process.com ping: socket: permission denied TIA. -- Cheers, SysMan at DLS. www.dls.net --- Conection with care www.radiusvms.com --- Free & Commercial software for ISP under OpenVMS ================================================================================ Archive-Date: Tue, 30 Nov 1999 14:32:47 -0400 From: "AG" Reply-To: Info-TCPware@process.com Subject: Printing from VMS to a NT4 (LPR) queue Message-ID: Date: Tue, 30 Nov 1999 19:17:39 GMT To: Info-TCPware@PROCESS.COM Hi folks, I have a serious problem: a) I don't know VMS at all b) a customer of mine wants to send his print flow from VMS to a Windows NT queue using TCP/IP (LPR protocol) c) whatever tests have been done up to now resulted in missing CRs, missing CRs and LF's and/or Page feeds (h'0C') where not needed. Can anybody help me with the right settings? Thanks a lot Andreas ================================================================================ Archive-Date: Tue, 30 Nov 1999 16:26:23 -0400 Sender: goatley@triton.process.com Return-Path: Message-ID: <01BF3B2C.30822AA0.CSHIPMAN@EARTHLINK.NET> From: "Charles P. Shipman" Reply-To: Info-TCPware@process.com To: "'Info-TCPware@process.com'" Subject: RE: Printing from VMS to a NT4 (LPR) queue Date: Tue, 30 Nov 1999 11:58:57 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Andreas, Are you trying to queue THROUGH the NT server, or just reach a printer that also is USED by the NT server? If the latter, it s no big issue. Let me know. Chuck Shipman Southwest Systems Integrators, LP (310) 962-7912 cshipman@earthlink.net ================================================================================ Archive-Date: Tue, 30 Nov 1999 16:33:45 -0400 From: cajunmikemike@netscape.net (Mike M.) Subject: Re: TCPWARE-W-EPIPE, pipe is broken Date: Tue, 30 Nov 1999 20:45:05 GMT Message-ID: <3844346f.81605031@enews.newsguy.com> Reply-To: Info-TCPware@process.com To: Info-TCPware@PROCESS.COM On Tue, 23 Nov 1999 17:17:31 GMT, cajunmikemike@netscape.net (CajunMikeMike) wrote: Answering my own question, here. When I checked the printer, printing a self-test config page revealed that a duplicate IP address was the root of the problem. Odd that TCPware was able to connect at all, unless whoever had the dup address was nice enough to shut their machine down regularly. Jeez, if I just had a directory-centric IP address management tool! ;) >Hello: >On an OpenVMS 7.1, TCPware 5.3 system, I have a terminal server >symbiont print queue which points to an HP Color LaserJet with an HP >JetDirect card. > >Periodically over the last few weeks, I've gotten the following >message: > >%%%%%%%%%%% OPCOM 23-NOV-1999 09:30:42.59 %%%%%%%%%%% (from node >VAX1 at 23-NOV-1999 09:30:54.59) >Message from user SYSTEM on VAX1 >%TCPWARE_TSSYM-W-CONNERR, error connecting to 172.25.80.55,9100 for >queue SENCLJ17 >-TCPWARE-W-EPIPE, pipe is broken > >%%%%%%%%%%% OPCOM 23-NOV-1999 09:30:57.66 %%%%%%%%%%% (from node >VAX1 at 23-NOV-1999 09:31:09.66) >Message from user SYSTEM on VAX1 >%TCPWARE_TSSYM-I-CONNECTED, connected to 172.25.80.55,9100 for queue >SENCLJ17 > >It seems that it tries to connect, fails, tries again and succeeds. >I've seen similar messages when a printer's network card begins to go >goofy, but I've never gotten the PIPE message. I can't find it in the >manuals, online help, or a DejaNews search. > >Anyone ever seen this, or have any idea what it might mean? I've >taken the cover off of both my VAX and the printer, but I can't find >anything that looks like a pipe! ; ) ================================================================================ Archive-Date: Tue, 30 Nov 1999 16:54:14 -0400 Message-ID: <4.2.2.19991130144852.00bcfab0@mehlhop.org> Date: Tue, 30 Nov 1999 14:49:35 -0700 To: Info-TCPware@process.com From: Jim Mehlhop Reply-To: Info-TCPware@process.com Subject: Re: TCPWARE-W-EPIPE, pipe is broken In-Reply-To: <3844346f.81605031@enews.newsguy.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed At 08:45 PM 11/30/99 +0000, you wrote: >On Tue, 23 Nov 1999 17:17:31 GMT, cajunmikemike@netscape.net >(CajunMikeMike) wrote: > >Answering my own question, here. > >When I checked the printer, printing a self-test config page revealed >that a duplicate IP address was the root of the problem. Odd that >TCPware was able to connect at all, unless whoever had the dup address >was nice enough to shut their machine down regularly. > >Jeez, if I just had a directory-centric IP address management tool! ;) Yah mean like IPWorks. :-) > >Hello: > >On an OpenVMS 7.1, TCPware 5.3 system, I have a terminal server > >symbiont print queue which points to an HP Color LaserJet with an HP > >JetDirect card. > > > >Periodically over the last few weeks, I've gotten the following > >message: > > > >%%%%%%%%%%% OPCOM 23-NOV-1999 09:30:42.59 %%%%%%%%%%% (from node > >VAX1 at 23-NOV-1999 09:30:54.59) > >Message from user SYSTEM on VAX1 > >%TCPWARE_TSSYM-W-CONNERR, error connecting to 172.25.80.55,9100 for > >queue SENCLJ17 > >-TCPWARE-W-EPIPE, pipe is broken > > > >%%%%%%%%%%% OPCOM 23-NOV-1999 09:30:57.66 %%%%%%%%%%% (from node > >VAX1 at 23-NOV-1999 09:31:09.66) > >Message from user SYSTEM on VAX1 > >%TCPWARE_TSSYM-I-CONNECTED, connected to 172.25.80.55,9100 for queue > >SENCLJ17 > > > >It seems that it tries to connect, fails, tries again and succeeds. > >I've seen similar messages when a printer's network card begins to go > >goofy, but I've never gotten the PIPE message. I can't find it in the > >manuals, online help, or a DejaNews search. > > > >Anyone ever seen this, or have any idea what it might mean? I've > >taken the cover off of both my VAX and the printer, but I can't find > >anything that looks like a pipe! ; ) _________________________________________________________________________ Jim Mehlhop, Support Engineer Process Software Mehlhop@process.com Phone 719-638-8448 Join Cauce to outlaw spam http://www.cauce.org/ _________________________________________________________________________ ================================================================================ Archive-Date: Tue, 30 Nov 1999 17:08:38 -0400 Message-ID: From: "Garrido, Ramon, Mr, HQAFCEE" Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com Subject: tcpware 5.4 ftplogfile/outgoingAcess Date: Tue, 30 Nov 1999 16:07:26 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF3B7F.493FD54E" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF3B7F.493FD54E Content-Type: text/plain; charset="iso-8859-1" I upgraded my tcpware from 5.3 to 5.4 and two things that worked do not work now. 1) TCPWARE_FTP_LOGFILE logical does not work, meaning nothing gets written to the specified logfile. Do I need to restart the whole network after defining the logical? 2) TCPWARE_OUTGOING_RESTRICTIONS.DAT file loads, but does not deny access. _________________________________ deny * 0 0 eq telnet permit * _________________________________ $netcu show outgoing DENY * 0.0.0.0 0.0.0.0 EQ 23 ________________________________ But anyone can still telnet out. Help, Thanks..Ramon ------_=_NextPart_001_01BF3B7F.493FD54E Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable tcpware 5.4 ftplogfile/outgoingAcess

I upgraded my tcpware from 5.3 to 5.4 = and two things that worked do not work now. 1) TCPWARE_FTP_LOGFILE = logical does not work, meaning nothing gets written to the specified = logfile. Do I need to restart the whole network after defining the = logical?

 2) = TCPWARE_OUTGOING_RESTRICTIONS.DAT file loads, but does not deny = access.
_________________________________
deny * 0 0 eq telnet
permit *
_________________________________
$netcu show outgoing

DENY * 0.0.0.0   = 0.0.0.0    EQ   23
________________________________

But anyone can still telnet = out.

Help, Thanks..Ramon

------_=_NextPart_001_01BF3B7F.493FD54E-- ================================================================================ Archive-Date: Tue, 30 Nov 1999 17:12:01 -0400 Message-ID: <63D30D6E10CFD11190A90000F805FE8601E753A9@lespaul.process.com> From: Richard Whalen Reply-To: Info-TCPware@process.com To: "'Info-TCPware@process.com'" Subject: RE: tcpware 5.4 ftplogfile/outgoingAcess Date: Tue, 30 Nov 1999 17:10:36 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" For problem 1 you must restart FTP after defining TCPWARE_FTP_LOGFILE (@tcpware:restart ftp) I'm sorry, but I don't know the answer to your second problem. -----Original Message----- From: Garrido, Ramon, Mr, HQAFCEE [mailto:Ramon.Garrido@hqafcee.brooks.af.mil] Sent: Tuesday, November 30, 1999 5:07 PM To: Info-TCPware@process.com Subject: tcpware 5.4 ftplogfile/outgoingAcess I upgraded my tcpware from 5.3 to 5.4 and two things that worked do not work now. 1) TCPWARE_FTP_LOGFILE logical does not work, meaning nothing gets written to the specified logfile. Do I need to restart the whole network after defining the logical? 2) TCPWARE_OUTGOING_RESTRICTIONS.DAT file loads, but does not deny access. _________________________________ deny * 0 0 eq telnet permit * _________________________________ $netcu show outgoing DENY * 0.0.0.0 0.0.0.0 EQ 23 ________________________________ But anyone can still telnet out. Help, Thanks..Ramon