1 INFO-VAX	Mon, 20 Jun 2005	Volume 2005 : Issue 343       Contents: 3rd party scsi controllers Re: 3rd party scsi controllers- Re: Another (simpler) DCL enhancement request - Re: Another (simpler) DCL enhancement request - Re: Another (simpler) DCL enhancement request ! Re: Another DCL CHallenge for Guy ! Re: Another DCL CHallenge for Guy  Re: Backup question  CHARON-VAX demo available : Competence Center for VAX/VMS migration: what do YOU want?1 Re: Hackers and Microsoft Engineers, very amusing 1 Re: Hackers and Microsoft Engineers, very amusing 1 Re: Hackers and Microsoft Engineers, very amusing 3 Re: Intel neuters Montvale, Itanic screams in alarm 3 Re: Intel neuters Montvale, Itanic screams in alarm 3 Re: Intel neuters Montvale, Itanic screams in alarm   LDAP API for OpenVMS v7.2 Alpha?+ Re: Need to export All-In-One files to a PC + Re: Need to export All-In-One files to a PC  Old DEC mailing list: Desperado # Re: Old DEC mailing list: Desperado  OpenVMS and XML questions  Re: OpenVMS and XML questions  Re: OpenVMS and XML questions 4 Re: OpenVMS BootCamp (anonymous) pixes - Day 5/5 :-(4 Re: OpenVMS BootCamp (anonymous) pixes - Day 5/5 :-( Re: OT: vms keyboard9 Restarting SMB service with the SWAT kill my DECW session = Re: Restarting SMB service with the SWAT kill my DECW session " Re: several new 7.3-2 patches!!!!!  Re: SURVEY: Best Handheld for...  Re: UCX connect function timeout  Re: UCX connect function timeout  Re: VAX/VMS Consulting in Europe  Re: VAX/VMS Consulting in Europe  Re: VAX/VMS Consulting in Europe  Re: VAX/VMS Consulting in Europe  F ----------------------------------------------------------------------    Date: 20 Jun 2005 03:22:38 -0700; From: "tomarsin2015@comcast.net" <tomarsin2015@comcast.net> # Subject: 3rd party scsi controllers C Message-ID: <1119262958.452837.187910@z14g2000cwz.googlegroups.com>    Hello F I was wondering what 3rd party scsi controllers will work in the older? Alphastation 200/4-233 models??? I have some older Adaptec 2940 D controllers and was wondering if theres anyway to get the 200 to seeG them. The 200 sees the controller, but shows the controller as a unkown 3 device.  I'm just trying to find the cheap way out.    phillip    ------------------------------  % Date: Mon, 20 Jun 2005 10:40:40 -0400 - From: William Webb <william.w.webb@gmail.com> ' Subject: Re: 3rd party scsi controllers 7 Message-ID: <8660a3a1050620074020d07ba3@mail.gmail.com>   7 On 20 Jun 2005 03:22:38 -0700, tomarsin2015@comcast.net ! <tomarsin2015@comcast.net> wrote:  > Hello H > I was wondering what 3rd party scsi controllers will work in the olderA > Alphastation 200/4-233 models??? I have some older Adaptec 2940 F > controllers and was wondering if theres anyway to get the 200 to seeI > them. The 200 sees the controller, but shows the controller as a unkown 5 > device.  I'm just trying to find the cheap way out.  >=20	 > phillip  >=20 >=20  D It'll stop hurting when you quit banging your head against the wall.  > As a general rule, the older you go in terms of VMS system/VMSD version, the less likely it is that 3rd party SCSI host bus adapters
 will work.  = For systems of the vintage of which you speak, it has been my E experience that they won't work with Adaptec at all; at least for the  non-DEC/Compaq/HP branded ones.   $ Ditto for the Personal Workstations.    Try something Qlogic 10x0 based.  D And as for cheap, you can get KZPBAs rather inexpensively on auction sites from time to time.   WWWebb   --=20 C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  % Date: Mon, 20 Jun 2005 08:21:27 +0200 ( From: "Rudolf Wingert" <win@fom.fgan.de>6 Subject: Re: Another (simpler) DCL enhancement request3 Message-ID: <003a01c57560$4b382c90$994614ac@wat153>    Hello,  H If I understand this thread right, there is bug within DIFF. DCL ignoresG the ! as comment start character if one of the previous character is an C ". This is right, so you can use ! as parameter or so. DIFF make no C difference between this to cases. It sees the ! and interpret it as D start of comment. HP have to change DIFF, so that this work correct.   Best regards R. Wingert    ------------------------------    Date: 20 Jun 2005 08:05:00 -0700$ From: "AEF" <spamsink2001@yahoo.com>6 Subject: Re: Another (simpler) DCL enhancement requestC Message-ID: <1119279900.752661.129910@f14g2000cwb.googlegroups.com>    Rudolf Wingert wrote:  > Hello, > J > If I understand this thread right, there is bug within DIFF. DCL ignoresI > the ! as comment start character if one of the previous character is an E > ". This is right, so you can use ! as parameter or so. DIFF make no E > difference between this to cases. It sees the ! and interpret it as F > start of comment. HP have to change DIFF, so that this work correct. >  > Best regards R. Wingert     A Perhaps this could be mixed with my previous request for ignoring  leading dollar signs:    http://groups-beta.google.com/group/comp.os.vms/browse_frm/thread/576b0f9532ace53a/1f516d550e9af14b?q=dollar+signs&rnum=2&hl=en#1f516d550e9af14b    ; So I think what it would be great if the default action for D /IGNORE=COMMENTS with .COM files would be to simply process comments, exactly the same way DCL does. So lines like  
 $! comment $  ! comment:    $  ! comment   (not sure if this style is really legit) (etc.)  F would be ignored as comments. (Actually, this is not quite the same asD what I requested in the quoted thread. I think what I wrote above is3 actually a better way to achieve the desired goal.)     
 In lines like   % $ EXCITING COMMAND ! exciting comment   & "! exciting comment" would be ignored.    F When "!" appears inside quotation marks, no comment would be inferred.    F Additionally, it would also be nice to have and ignore option that canF tell if two .COM files are DCL-functionally equivalent, but that mightF be too ambitious. One would have to ignore spaces exactly as DCL does.G I don't think you can do that with the present DIFF command. Also, case E would have to be ignored except inside quotation marks. And so on. It > may well not be worth the trouble. But I think the DCL comment processing request is!   ------------------------------  % Date: Mon, 20 Jun 2005 11:55:09 -0400  From: norm.raphael@metso.com6 Subject: Re: Another (simpler) DCL enhancement requestQ Message-ID: <OFEAC2DC58.1E459BDC-ON85257026.005597A3-85257026.005794FF@metso.com>   ? "AEF" <spamsink2001@yahoo.com> wrote on 06/20/2005 11:05:00 AM:    > Rudolf Wingert wrote: 
 > > Hello, > > D > > If I understand this thread right, there is bug within DIFF. DCL ignores K > > the ! as comment start character if one of the previous character is an G > > ". This is right, so you can use ! as parameter or so. DIFF make no G > > difference between this to cases. It sees the ! and interpret it as H > > start of comment. HP have to change DIFF, so that this work correct. > >  > > Best regards R. Wingert  >  > C > Perhaps this could be mixed with my previous request for ignoring  > leading dollar signs:  > . > http://groups-beta.google.com/group/comp.os.: > vms/browse_frm/thread/576b0f9532ace53a/1f516d550e9af14b?. > q=dollar+signs&rnum=2&hl=en#1f516d550e9af14b >  > = > So I think what it would be great if the default action for F > /IGNORE=COMMENTS with .COM files would be to simply process comments. > exactly the same way DCL does. So lines like >  > $! comment > $  ! comment< >    $  ! comment   (not sure if this style is really legit) > (etc.) > H > would be ignored as comments. (Actually, this is not quite the same asF > what I requested in the quoted thread. I think what I wrote above is5 > actually a better way to achieve the desired goal.)  >  >  > In lines like  > ' > $ EXCITING COMMAND ! exciting comment  > ( > "! exciting comment" would be ignored. >  > H > When "!" appears inside quotation marks, no comment would be inferred. >  > H > Additionally, it would also be nice to have and ignore option that canH > tell if two .COM files are DCL-functionally equivalent, but that mightH > be too ambitious. One would have to ignore spaces exactly as DCL does.I > I don't think you can do that with the present DIFF command. Also, case G > would have to be ignored except inside quotation marks. And so on. It @ > may well not be worth the trouble. But I think the DCL comment > processing request is! > 6 Well, we now have three (at least) different requests.  C   I.)  Properly do not treat a "!" as a comment in F$FAO() lexicals '     A.)  Extend to any and all lexicals B  II.)  Properly do not treat a "!" as a comment when surrounded by        double-quote marks C     A.)  Handle the case where DCL does not care when the line ends 4          without a closing double-quote mark (oopsy)2     B.) Extend to any designated comment_dilimeterH       1.)  Extend to any "default" comment dilimiters where appropriate.@ III.) Treat the character pair "$!" at the start of a line as if=       it were the single character "!" at the start of a line ;     A.)  Extend to ignoring any white-space between the two           characters of the pair >       1.)  Extend to any white-space preceeding the pair after6            parsing out any white-space between the two         characters of the pairE     B.) Extend to any designated comment_dilimeter paired after a "$"   G I and II look to me like bug-fixes that ought to be done, especially I. I III is clearly not a but-fix, and one man's meat is another man's poison. I I think the discussions around /IGNORE=white_space should be enough. This E one is really at odds with properly-written DCL having every line not F between $DECK/$EOD pairs start with a "$" character, and unresolvable.   ------------------------------  # Date: Mon, 20 Jun 2005 14:46:47 GMT & From: John Reagan <john.reagan@hp.com>* Subject: Re: Another DCL CHallenge for Guy0 Message-ID: <rFAte.7338$MK4.85@news.cpqcorp.net>   David J Dachtera wrote:    >  > 5 > O.k., Guy, how hard would it be to add this to DCL:  >  > DEFINE VERB SAMPLE >     image sample >     qualifier privved_sample5 >         value (list,privs=(oper),rights=(np_allow))  > J > Then, if a user invokes the verb SAMPLE with the /PRIVVED_SAMPLE[=value]D > qualifier, but lacks OPER privilege, or does not hold the NP_ALLOWI > identifier, then DCL itself refuses the command with a message such as:  > = > %DCL-E-PRVQUAL, /PRVVED_SAMPLE qualifier requires privilege 7 > ("%DCL-E-PRVQUAL, /!AS qualifier requires privilege")  >  > Anything useful here?  >   B What aboue images installed with privs?  Or images linked against E user-written system services that might grant the privilege based on  $ some scheme Guy doensn't know about?  C Having DCL "guess" at what the program needs feels like half a job.    --   John Reagan / HP Pascal/{A|I}MACRO for OpenVMS Project Leader  Hewlett-Packard Company    ------------------------------  + Date: Mon, 20 Jun 2005 15:21:13 +0000 (UTC) . From: klewis@LUMINA.MITRE.ORG (Keith A. Lewis)* Subject: Re: Another DCL CHallenge for Guy. Message-ID: <d96mt9$ett$1@newslocal.mitre.org>  | John Reagan <john.reagan@hp.com> writes in article <rFAte.7338$MK4.85@news.cpqcorp.net> dated Mon, 20 Jun 2005 14:46:47 GMT: >David J Dachtera wrote: >>  6 >> O.k., Guy, how hard would it be to add this to DCL: >>   >> DEFINE VERB SAMPLE  >>     image sample  >>     qualifier privved_sample 6 >>         value (list,privs=(oper),rights=(np_allow)) >>  K >> Then, if a user invokes the verb SAMPLE with the /PRIVVED_SAMPLE[=value] E >> qualifier, but lacks OPER privilege, or does not hold the NP_ALLOW J >> identifier, then DCL itself refuses the command with a message such as: >>  > >> %DCL-E-PRVQUAL, /PRVVED_SAMPLE qualifier requires privilege8 >> ("%DCL-E-PRVQUAL, /!AS qualifier requires privilege") >>   >> Anything useful here? >>   > C >What aboue images installed with privs?  Or images linked against  F >user-written system services that might grant the privilege based on % >some scheme Guy doensn't know about?  > D >Having DCL "guess" at what the program needs feels like half a job.  E I agree.  I don't see a drawback with the current scheme of the image J optionally checking its privs.  I didn't read the whole backup thread, butL it still produces a good backup even if it can't /RECORD, right?  No harm no foul.   0 --Keith Lewis              klewis {at} mitre.org> The above may not (yet) represent the opinions of my employer.   ------------------------------    Date: 20 Jun 2005 10:37:06 -0700$ From: "AEF" <spamsink2001@yahoo.com> Subject: Re: Backup questionC Message-ID: <1119289026.056321.182130@g44g2000cwa.googlegroups.com>    Dave Weatherall wrote:H > On Thu, 16 Jun 2005 17:35:26 UTC, "Syltrem" <syltremzulu@videotron.ca> > wrote: > = > > "AEF" <spamsink2001@yahoo.com> a ,crit dans le message de A > > news:1118941830.129843.298400@g43g2000cwa.googlegroups.com...   G [>-depth got screwed up here. What's quoted below, up to the [...], was  written by me, AEF]    > > G > > Here's an example of how renaming a file clears its backup date and  > > foils the tape2 backup.  > >  > > $ DIR/DATE=(M,B) A.A > > ! > > Directory _DSA1:[SCRATCH.AAA]  > > A > > A.A;1                      0/0        16-JUN-2005 13:04:51.98  > > 16-JUN-2005 13:05:14.63  > >   > > Total of 1 file, 0/0 blocks. > > $ REN A.A C.C : > > %RENAME-I-RENAMED, _DSA1:[SCRATCH.AAA]A.A;1 renamed to > > _DSA1:[SCRATCH.AAA]C.C;1 > > $ DIR/DATE=(M,B) C.C > > ! > > Directory _DSA1:[SCRATCH.AAA]  > > G > > C.C;1                      0/0        16-JUN-2005 13:05:27.75   <No  > > backup recorded> > >   > > Total of 1 file, 0/0 blocks. > > $ > > > $ BACK/LOG */BACK/SINC=16-JUN-2005 NL:A.B/SAVE  ! to tape2F > > %BACKUP-W-NOFILES, no files selected from _DSA1:[SCRATCH.AAA]*.*;* > > $  > >  [...] H > Does the same apply if you rename the file back to ;1. A practice I doA > not indulge in for many reasons but it's good to have one more.  >  > -- > Cheers - Dave W.    8 Is there some reason you can test this with a test file?  6 Anyway, renaming a file to ;1 *does* clear the backup.   ------------------------------  % Date: Mon, 20 Jun 2005 14:09:54 +0200 - From: Didier Morandi <prenom.nom@freesurf.fr> " Subject: CHARON-VAX demo available4 Message-ID: <42b6b216$0$17377$636a15ce@news.free.fr>  9 The Charon-VAX demo is back on the Net for demo purposes: < http://www.softresint.com/charon-vax/Tools_and_tips.htm#demo   D. --  1 Didier MORANDI - Expert informaticien - VMS / SAP 0   13 chemin du Gu, 1213 Petit-Lancy (GE) Suisse0 Tl. : +33(0)6 7983 6418 ~ www.didiermorandi.com   ------------------------------  % Date: Mon, 20 Jun 2005 19:21:56 +0200 - From: Didier Morandi <prenom.nom@freesurf.fr> C Subject: Competence Center for VAX/VMS migration: what do YOU want? 4 Message-ID: <42b6fb3b$0$17378$636a15ce@news.free.fr>   THIS MESSAGE FOR VAX/VMS USERS  N I'm working these days as a consultant on the setup of an European Competence 7 Center to help VAX/VMS Users to migrate to OpenVMS/I64.   6 What resources do you expect to find in such activity?  J  From previous analysis, I already decided to propose the following items:  O a) advisory, or better say Change Management i.e. psychological help to assist  O users in the process of taking such decision. The "ostrich behaviour" is not a   professional one.   P b) numerous platforms to port software on and perform actual migration of code, Q locally in a lab or remotely via the Internet (Telnet, DECNet over IP, VPN, etc.)   L c) software engineers availability for technical discussions and/or on site 
 consulting  K d) marketing/sales people availability for discussions on licenses and such   J e) CHARON-VAX, CHARON-Alpha booth for those who would prefer that solution   f) coffee/tea/red wine corner   
 What else? Thanks,    D.   --  1 Didier MORANDI - Expert informaticien - VMS / SAP 0   13 chemin du Gu, 1213 Petit-Lancy (GE) Suisse0 Tl. : +33(0)6 7983 6418 ~ www.didiermorandi.com   ------------------------------  + Date: Mon, 20 Jun 2005 16:51:47 +0000 (UTC)  From: david20@alpha2.mdx.ac.uk: Subject: Re: Hackers and Microsoft Engineers, very amusing) Message-ID: <d96s72$msd$1@news.mdx.ac.uk>   @ In article <XOote.3931$mD6.2635@fe07.lga>, Z <Z@no.spam> writes: >Dave Froble wrote: & >> This link has a very amusing story., >> http://www.theinquirer.net/?article=24013J >> Apparently Microsoft got together their software people and hackers to H >> show how much more secure their products are.  It only took about 10 J >> minutes for the hackers to get the Microsoft programmers rather upset. J >> Microsoft managers were quite happy.  They said that they kept talking L >> at the programmers about security, to no avail.  The Hackers finally got # >> the programmer's attantion.  :-)  > G >If you bother to follow the ZDNet link on the Inquirer's web page and  < >read _that_ story, you'll get a much more accurate account. > 9 >And here is another, more factual, account of the event: W >http://news.com.com/Microsoft+meets+the+hackers/2009-1002_3-5747813.html?tag=nefd.lede  > D >And, fwiw, the "exploit" wasn't a flaw in Windows but was luring a 8 >laptop user to connect to a malicious wireless network.  O Unfortunately in the name of user friendliness Windows default is to add every  > Wireless network you have ever connected to into it's list of G preferred networks and then send out probes for each of these networks  ? and finally to connect to the first one it finds automatically. K Hence if you have ever connected to a non-encrypted network, ie your local  L internet cafe hotspot, then it is trivial for a hacker to fool your wirelessH laptop into connecting to an access-point configured to impersonate that network on his laptop.  + Personally I'd call that a flaw in windows.       
 David Webb Security team leader CCSS Middlesex University   ------------------------------  % Date: Mon, 20 Jun 2005 10:04:38 -0700  From: Z <Z@no.spam> : Subject: Re: Hackers and Microsoft Engineers, very amusing+ Message-ID: <GGCte.11847$wm2.8135@fe05.lga>    david20@alpha2.mdx.ac.uk wrote: Q > Unfortunately in the name of user friendliness Windows default is to add every  @ > Wireless network you have ever connected to into it's list of I > preferred networks and then send out probes for each of these networks  A > and finally to connect to the first one it finds automatically.   = That's odd, my Windows XP Pro system doesn't behave that way.    I'm prompted to connect.  , Maybe I have a defective version of Windows?   ------------------------------  % Date: Mon, 20 Jun 2005 13:39:04 -0400 - From: William Webb <william.w.webb@gmail.com> : Subject: Re: Hackers and Microsoft Engineers, very amusing7 Message-ID: <8660a3a105062010392e8b8aef@mail.gmail.com>     On 6/20/05, Z <Z@no.spam> wrote:! > david20@alpha2.mdx.ac.uk wrote: L > > Unfortunately in the name of user friendliness Windows default is to ad= d every A > > Wireless network you have ever connected to into it's list of J > > preferred networks and then send out probes for each of these networksC > > and finally to connect to the first one it finds automatically.  >=20? > That's odd, my Windows XP Pro system doesn't behave that way.  >=20 > I'm prompted to connect. >=20. > Maybe I have a defective version of Windows? >=20   We all do, brother, we all do.   WWWebb   --=20 C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------    Date: 20 Jun 2005 07:13:51 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) < Subject: Re: Intel neuters Montvale, Itanic screams in alarm3 Message-ID: <9xa3Xn9XnFTn@eisner.encompasserve.org>   _ In article <1119187773.467177.136730@g43g2000cwa.googlegroups.com>, bob@instantwhip.com writes: = > sorry Billy ... you and your self proclaimed genius liberal < > buddies are in the minority ... this is a Christian nation      What planet are you from?   ------------------------------  % Date: Mon, 20 Jun 2005 15:18:56 +0200  From: S <soterroatyahoodotcom>< Subject: Re: Intel neuters Montvale, Itanic screams in alarm& Message-ID: <42b6c235$1@news1.ethz.ch>   Bob Koehler wrote:a > In article <1119187773.467177.136730@g43g2000cwa.googlegroups.com>, bob@instantwhip.com writes:  > = >>sorry Billy ... you and your self proclaimed genius liberal < >>buddies are in the minority ... this is a Christian nation >  >  >    What planet are you from?  - Wait, there are quite a few from that planet:    http://www.reandev.com/taliban/  o_O    S    ------------------------------  % Date: Mon, 20 Jun 2005 12:40:28 -0400 ' From: Dave Froble <davef@tsoft-inc.com> < Subject: Re: Intel neuters Montvale, Itanic screams in alarm0 Message-ID: <11bds91sq9fvs52@corp.supernews.com>   Bob Koehler wrote:a > In article <1119187773.467177.136730@g43g2000cwa.googlegroups.com>, bob@instantwhip.com writes:  > = >>sorry Billy ... you and your self proclaimed genius liberal < >>buddies are in the minority ... this is a Christian nation >  >  >    What planet are you from? > C He's from this planet, and specifically the USA.  He's part of the  K reason Bush won the last election.  Now you can be afraid.  Be very afraid!    --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  + Date: Mon, 20 Jun 2005 15:03:48 +0000 (UTC) = From: jlw@psulias.psu.edu (j.lance wilkinson, (814) 865-1818) ) Subject: LDAP API for OpenVMS v7.2 Alpha? . Message-ID: <d96lsk$182u$1@f04n12.cac.psu.edu>  J I have OVMS v7.2-1H1, not likely to be able to convince the powers that beF to upgrade it, and have a need to use a C-callable API for LDAP.  Any H successful ports of an LDAP API library out there?  When I look for thisN online, about all I find is an LGI callout module allowing VMS to authenticateN against an LDAP database.  I need to be able to bind and then send queries and! get the results of those queries.   P +----"Never Underestimate the bandwidth of a station wagon full of mag tapes"--+B | J.Lance Wilkinson ("Lance")		InterNet:  Lance.Wilkinson@psu.edu < | Systems Design Specialist - Lead	AT&T:      (814) 865-18189 | Digital Library Technologies		FAX:       (814) 863-3560 2 | 3 Paterno Library				"I'd rather be dancing..." B | Penn State University		    A host is a host from coast to coast,K | University Park, PA 16802	    And no one will talk to a host that's close C | <postmaster@psulias.psu.edu>	    Unless the host that isn't close : | EMail Professional since 1978	    Is busy, hung or dead.P +---------"He's dead, Jim. I'll get his tricorder. You take his wallet."-------+9                 [apologies to DeForest Kelley, 1920-1999] 3 <A Href="http://perdita.lcs.psu.edu">home page</a>  J <a Href="http://perdita.lcs.psu.edu/junkdec.htm">junk mail declaration</a> --	/"\ 	\ /	ASCII RIBBON CAMPAIGN 	 X	AGAINST HTML MAIL  	/ \   ------------------------------    Date: 20 Jun 2005 06:25:23 -0700 From: jtpryan@gmail.com 4 Subject: Re: Need to export All-In-One files to a PCC Message-ID: <1119273923.635046.213400@g14g2000cwa.googlegroups.com>   D It looks like the only chance I have of converting these files is toF find the converter for teamlinks.  Is this simply a plugin or file(s)?5 Would it be possible for somebody to send/sell me it?    -Jim   ------------------------------  % Date: Mon, 20 Jun 2005 13:21:33 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 4 Subject: Re: Need to export All-In-One files to a PC, Message-ID: <42B6FB18.D60726FF@teksavvy.com>   jtpryan@gmail.com wrote: > F > It looks like the only chance I have of converting these files is toH > find the converter for teamlinks.  Is this simply a plugin or file(s)?7 > Would it be possible for somebody to send/sell me it?   J What is the best way to send about 10 diskettes ? (I have an old version).   ------------------------------    Date: 20 Jun 2005 08:37:51 -0700- From: "Tim Shoppa" <shoppa@trailing-edge.com> ( Subject: Old DEC mailing list: DesperadoC Message-ID: <1119281871.901148.263850@g43g2000cwa.googlegroups.com>   G Sometime in the late 70's an electronic mailing list called "Desperado" G was set up inside DEC.  Its moderator at one point (or maybe only ever) B was Tom Parmenter.  I know of it because bits and pieces have beenF copied to Usenet and DECUSserve over the years, and from what I see itB seems to be part RISKS digest and part alt.humor.best-of-usenet inF theme.  (I am probably oversimplifying greatly).  Ex-DECcies have also mentioned it to me.   C Does anyone know if archives of this mailing list are on the web or 
 elsewhere?   Tim.   ------------------------------    Date: 20 Jun 2005 09:09:01 -0700- From: "Tim Shoppa" <shoppa@trailing-edge.com> , Subject: Re: Old DEC mailing list: DesperadoC Message-ID: <1119283741.059076.187500@f14g2000cwb.googlegroups.com>    Hein writes:  % > http://desperado-list.blogspot.com/ < >  http://www.wired.com/wired/6.04/es_lists.html?pg=4&topic=  G But neither of the above lead me to an archive of the 1970's Desperado. $  Believe me, I tried Google already.  G I also found an E-mail address for Tom at world.std.com, but E-mails to D that address have not returned anything yet.  (Maybe I'm not patient enough).  B I suppose I could try commenting in his blog to get his attention.   Tim.   ------------------------------    Date: 20 Jun 2005 09:55:39 -0700' From: "tadamsmar" <tadamsmar@yahoo.com> " Subject: OpenVMS and XML questionsC Message-ID: <1119286539.558160.164080@g14g2000cwa.googlegroups.com>   G I am researching how to read/write data points from/to an environmental ? control system using XML over an intranet to/from an VMS legacy % application written in FORTRAN and C.   C The application currently uses a serial interface to read/write the B data points, but we are exploring using the XML interface that the& environmental control system provides.  G Any ideas on how to approach this?  I don't know very little about XML. E  I am not sure what kind of XML support VMS provides.  We have TCP/IP  for our VMS Systems.  C I figure I could read/writh the XML via Java and transfer it to the E legacy application via files.  That would probably work for us, but I ! would like to explore my options.    ------------------------------    Date: 20 Jun 2005 12:26:31 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) & Subject: Re: OpenVMS and XML questions3 Message-ID: <B6qsXAlXe5O3@eisner.encompasserve.org>   m In article <1119286539.558160.164080@g14g2000cwa.googlegroups.com>, "tadamsmar" <tadamsmar@yahoo.com> writes:   E > The application currently uses a serial interface to read/write the D > data points, but we are exploring using the XML interface that the( > environmental control system provides.  2 Why ?  What is broken about the serial interface ?   ------------------------------  % Date: Mon, 20 Jun 2005 13:26:48 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> & Subject: Re: OpenVMS and XML questions, Message-ID: <42B6FC53.EB221213@teksavvy.com>   tadamsmar wrote: > I > I am researching how to read/write data points from/to an environmental A > control system using XML over an intranet to/from an VMS legacy ' > application written in FORTRAN and C.   9 There is a library of XML support functions available at: C http://h71000.www7.hp.com/openvms/products/ips/XML/cplus_files.html   E It does require C++ to compile, and I have never looked into it , but 2 you should be able to interface with any language.   ------------------------------  % Date: Mon, 20 Jun 2005 15:47:23 +0930 % From: Jeremy Begg <nospam@vsm.com.au> = Subject: Re: OpenVMS BootCamp (anonymous) pixes - Day 5/5 :-( / Message-ID: <42b65f74$1@duster.adelaide.on.net>    Didier Morandi wrote: # > http://didier.morandi.free.fr/d5/  >  > D. > G > PS: The Longest Trip Contest (which did not occur) was won by Jeremy  F > Begg (HP CSC Australia): 26 hours, followed by a young lady from HP = > Japan: 22 hours. You may easily recognize her on a picture.   3 I left home at 9am and arrived in Boston at 9pm :-)   K FWIW it's taken longer in the past.  For CETS in 2000 I went via Hong Kong  J and was travelling for about 30 hours (including stops) just to get to LA.  - BTW I do not work for HP let alone in HP CSC.    Regards,   	Jeremy Begg   ------------------------------  % Date: Mon, 20 Jun 2005 14:11:04 +0200 - From: Didier Morandi <prenom.nom@freesurf.fr> = Subject: Re: OpenVMS BootCamp (anonymous) pixes - Day 5/5 :-( 4 Message-ID: <42b6b25c$0$17377$636a15ce@news.free.fr>   Jeremy Begg wrote:  1   > BTW I do not work for HP let alone in HP CSC.   ; Yep. I have been (many times) noticed. Fixed in the report. ! Please buy a beer to Mark for me.    D.   ------------------------------  % Date: Mon, 20 Jun 2005 13:40:12 -0400 - From: William Webb <william.w.webb@gmail.com>  Subject: Re: OT: vms keyboard 7 Message-ID: <8660a3a105062010402b149774@mail.gmail.com>   5 On 19 Jun 2005 20:53:38 -0700, skearney@accessbee.com  <skearney@accessbee.com> wrote: F > The subject of the Dvorak keyboard has come up half a dozen times inG > this group.  While Keytweak may be irrelevant, the transposition dfjk G > with etni will increase the amount of text typed from these four home  > keys by almost 500%. >=20 >=20 > Aset keyboard G > It has been said that the most common letters were taken off the home B > row of the first typewriter keyboard to slow down the typist and > prevent jamming.I > On a Dvorak keyboard almost sixty percent of average text is typed from G > the home keys.  Transposing the letters 'etni' with 'dfjk'  would put H > more than 55% of text on the home keys, up from only 26% on the qwertyI > layout.  Thats more than twice the text typed without lifting a finger.  >=20G > The change is quite pleasant and easy to learn.  I hope you will pass 
 > this on. >=20B > To put e, t, n and i back where they belong, there is a keyboardG > remapping program that is free, downloads quickly and is very easy to B > use.  I am typing this post on a keyboard remapped to the 'etni'I > transposition layout.  The program is called 'Keytweak 2.11' and can be I > googled up by that name.  It is available from several sites, including  > PC magazine. >=204 > 1)  After you have loaded the program click start.H > 2)  Click the "KeyTweak" icon and a graphic of a keyboard will appear.> > 3)  Click the "Full Teach Mode" at the bottom of the screen.3 > 4)  A box will appear.  Click "Begin Teach Mode". B > 5)  Press the key you want to reassign, then the key you want it% > reassigned to, in this case D to E. " > 6)  Click "Remap Key#1 to Key#2"I > 7)  The box will disappear and the scancodes of the keys will appear in 3 > the "Pending Changes" window at the bottom right. F > 8)  Follow the same procedure (from 3) for E to D, and the remaining
 > six remaps. E > 9)  Click "Apply" and you will be asked if you want to turn off the   > computer to apply the changes.E >     At the top there is also a clickable "Restore Defaults" to give  > you back your qwerty layout.F >     I was able to remap in under three minutes and restore qwerty in, > thirty seconds, not including the restart. >=20F > You can try out the sample lines of text below to discover that your, > fingers already know where etni should go. >=20. > nineteen lean little saints settle in a nest. > jkjdfddj ldaj lkffld sakjfs sdffld kj a jdsf >=20) > an alien eats an ant antenna in atlanta ) > aj alkdj dafs aj ajf ajfdjja kj aflajfa  >=20. > elite sense entails a siesta in a satin seat. > dlkfd sdjsd djfakls a skdsfa kj a safkj sdaf >=20! > a stain is seen at a linen sale ! > a sfakj ks sddj af a lkjdj sald  >=20- > a latent latin talent tast tests in seattle - > a lafdjf lafkj faldjf fasf fdsfs kj sdaffld  >=20  > insane santa sails in sea salt  > kjsajd sajfa sakls kj sda salf >=20
 > Many thanks  >=20 >=20   Looks like ROT-13 to me.   WWWebb   --=20 C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  % Date: Mon, 20 Jun 2005 15:42:26 +0200 ) From: "Usenet" <bruno.seghers@banksys.be> B Subject: Restarting SMB service with the SWAT kill my DECW session6 Message-ID: <42b6c80f$0$24263$ba620e4c@news.skynet.be>   Hi,   L On the Freeware 7.0 cd's, they is a version of SAMBA for VMS (2.2.8). I have? insalled it on an alphastation running VMS7.3-2 with Motif 1.3.   G Each time I want to restart the smbd service via the SWAT (under STATUS ) option), my DECWindows session is killed. I The "Stop smbd" button seems to have no effect. There is no problems with ' "Stop nmbd" and "Restart nmbd" buttons.   L Is somebody has had the same problem and did he find a workaround or is this7 simply a bug and I can thus no more use those buttons ?    Thanks for your help  
 Seghers Bruno  Banksys  Belgium    ------------------------------  % Date: Mon, 20 Jun 2005 10:18:24 -0400 6 From: Brad Hamilton <brMadAhaPmiSlton@coMmcAasPt.Snet>F Subject: Re: Restarting SMB service with the SWAT kill my DECW session0 Message-ID: <2tudnZnY5JisTSvfRVn-1A@comcast.com>  
 Usenet wrote:  > Hi,  > N > On the Freeware 7.0 cd's, they is a version of SAMBA for VMS (2.2.8). I haveA > insalled it on an alphastation running VMS7.3-2 with Motif 1.3.  > I > Each time I want to restart the smbd service via the SWAT (under STATUS + > option), my DECWindows session is killed. K > The "Stop smbd" button seems to have no effect. There is no problems with ) > "Stop nmbd" and "Restart nmbd" buttons.  > N > Is somebody has had the same problem and did he find a workaround or is this9 > simply a bug and I can thus no more use those buttons ?  >   D I've never tried to stop/restart the smbd service in this way; I've E usually used the native CLI tools available for this task.  There is  F also a SAMBA_SHUTDOWN procedure distributed with the latest SAMBA for B VMS releases; I've simply executed the procedure (followed by the ) SAMBA_STARTUP procedure) to restart SMBD.   D I've seen no "stop smbd" button in the STATUS option, only an "auto  refresh" button.  = You might also want to ask your question on the mailing list:    samba-vms@lists.samba.org    > Thanks for your help <snip>   ------------------------------    Date: 20 Jun 2005 15:16:40 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)+ Subject: Re: several new 7.3-2 patches!!!!! , Message-ID: <42b6ddd8$1@news.langstoeger.at>  w In article <d90cle$fl4$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: J >I notice that several new patches for 7.3-2 have arrived in the last few  >days.  > Yup. TCPIP V5.4 ECO5, MOTIF V1.3-1 ECO2 as well as VMS732 ECOsM (AMATHRTL V1, JOBCTL V1,) IOGEN V1, SHADOWING V4, MANAGE V3 and FIBRE_SCSI V6   D >Why wasn't I notified via the announcement list I signed up for at J >OpenVMS.org?  Until recently I have gotten notifications even before the  >patches showed up at ITRC.   5 Because OPENVMS.ORG announcements are not automatic ? ; And even if they were (like with HPQ) errors are possible ?   J >Why is the new Fibre-SCSI patch preceeded by a dot in the list?  This is E >normally done for superseded patches, but in this case it's the NEW  , >patch.  Is there perhaps a problem with it?  H Yes, there is a problem with it. V6 is the replacement, but not yet out.   --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  + Date: Mon, 20 Jun 2005 07:16:08 +0000 (UTC) < From: gartmann@non.immunbio.mpg.de.sens (Christoph Gartmann)) Subject: Re: SURVEY: Best Handheld for... ) Message-ID: <d95qfo$3sc$1@news.BelWue.DE>   c In article <42b630ac$0$1342$636a15ce@news.free.fr>, Didier Morandi <prenom.nom@freesurf.fr> writes: I >I had my Palm Pilot 505 aged 5 stolen in my car yesterday (no, I had no   >passwords lists inside...)  > ' >So it is time for me to get a new one.   J My PalmV is even older and is now decrepit. So I thought about the same. IK prefer the Palm approach over Windows CE (small, efficient, ...). I thought N about some smartphone but decided that this is too early. So I ended up with a3 Tungsten T5. It is about the same size as my PalmV.   
 >read my mail   L The T5 has a card slot and I added a WLAN card. So web browsing is possible.  
 >telephone  F It has IR and Bluetooth, my mobile phone has only IR. IR is less power
 consuming.   >log into my Alpha   MochaTelnet.   Regards,    Christoph Gartmann    --  E  Max-Planck-Institut fuer      Phone   : +49-761-5108-464   Fax: -452   ImmunbiologieI  Postfach 1169                 Internet: gartmann@immunbio dot mpg dot de   D-79011  Freiburg, Germany 9                http://www.immunbio.mpg.de/home/menue.html    ------------------------------  + Date: Mon, 20 Jun 2005 05:39:38 +0000 (UTC) 3 From: "Richard Maher" <maher_rj@hotspamnotmail.com> ) Subject: Re: UCX connect function timeout ? Message-ID: <d95kqm$4fg$1@nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com>    Hi,   F > The timeout on a connect function appears to be about 90 seconds. Is% > there a way to change that timeout?   I You use the ucx$tcpopt option of probe_idle. (FYI if you're using TCPWARE 1 for this then you need privs to do it. IIRC OPER)   K The following example is taken from t3$examples:demo_client_tcp_ip.cob Look " at the socket_and_connect section.   Regards Richard Maher   L **************************************************************************** ******** *  * F *            COPYRIGHT (c) BY TIER3 SOFTWARE LTD. ALL RIGHTS RESERVED. *  *  * J *    THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED	 ONLY    * K *    IN ACCORDANCE  WITH THE TERMS AND CONDITIONS OF SUCH LICENSE AND  WITH  THE    *I *    THE INCLUSION  OF THE ABOVE COPYRIGHT NOTICE.  THIS SOFTWARE  OR ANY 
 OTHER    *J *    COPIES  THEREOF MAY NOT  BE PROVIDED  OR OTHERWISE MADE AVAILABLE  TO ANY    *G *    OTHER  PERSON.  NO  TITLE TO  AND OWNERSHIP  OF  THE  SOFTWARE  IS  HEREBY    *  *    TRANSFERRED.  *  *  * K *    THE INFORMATION  IN THIS SOFTWARE  IS SUBJECT TO CHANGE WITHOUT NOTICE  AND    *C *    SHOULD NOT BE CONSTRUED AS A COMMITMENT BY TIER3 SOFTWARE LTD.  *  *  * L **************************************************************************** ******** *+! * Facilility:  DEMO_CLIENT_TCP_IP  * L * Abstract:    This is an example of a VMS client program communicating with
 a remote task L *              via TIER3. This program accepts a queue entry number from the user and sendsC *              it to the remote Tier3 communication server for this  application (T3_DEMO).K *              After Tier3 has allocated an execution server to perform the 
 operation the D *              USER_RECV routine is called to retrieve the job entry information and return) *              the results to the client.  * H * Overview:    Due to the fact that client programs can communicate with Tier3 servers using J *              standard TCP/IP Socket Level programming, no Tier3 specific software need beL *              installed on the client node. In this example the client will
 execute under H *              the VMS operating system so VMS system services have been used for client task *              development.  *  * Build example:- *              $COBOL/LIST DEMO_CLIENT_TCP_IP * *              $MACRO/LIST DEMO_TCP_IP_DEF8 *              $LINK DEMO_CLIENT_TCP_IP, DEMO_TCP_IP_DEF$ *              $SET TERM/WIDTH = 132& *              $RUN DEMO_CLIENT_TCP_IP *- identification division." program-id.    demo_client_tcp_ip. data division. working-storage section.L 01  io$_setmode                     pic s9(9)       comp    value   external io$_setmode.L 01  io$_writevblk                   pic s9(9)       comp    value   external io$_writevblk.L 01  io$_readvblk                    pic s9(9)       comp    value   external
 io$_readvblk. L 01  io$_access                      pic s9(9)       comp    value   external io$_access. L 01  lib$_normal                     pic s9(9)       comp    value   external lib$_normal.L 01  ss$_linkdiscon                  pic s9(9)       comp    value   external ss$_linkdiscon. L 01  ss$_bufferovf                   pic s9(9)       comp    value   external ss$_bufferovf.L 01  ss$_abort                       pic s9(9)       comp    value   external
 ss$_abort.L 01  ss$_reject                      pic s9(9)       comp    value   external ss$_reject. L 01  ss$_nopriv                      pic s9(9)       comp    value   external ss$_nopriv. L 01  ss$_normal                      pic s9(9)       comp    value   external ss$_normal. 9 01  sys_status                      pic s9(9)       comp.  * 9 01  net_chan                        pic s9(4)       comp. 	 01  iosb. 9     03  cond_val                    pic s9(4)       comp. 9     03  byte_count                  pic s9(4)       comp. 9     03                              pic s9(9)       comp.  *  01  create_socket.L     03                              pic s9(4)       comp    value   external
 ucx$c_tcp.L     03                              pic s9(4)       comp    value   external inet_protyp$c_stream.  *  01  local_sock_desc.G     03                              pic s9(9)       comp    value   16. A     03                                              pointer value  reference       local_addr.  01  local_addr. L     03                              pic s9(4)       comp    value   external ucx$c_af_inet.     03  local_port_number.A         05  low_byte                pic x                   value  low-values. A         05  high_byte               pic x                   value  low-values. L     03                              pic s9(9)       comp    value   external ucx$c_inaddr_any. -     03                              pic x(8).  *  01  rem_sock_desc.G     03                              pic s9(9)       comp    value   16. A     03                                              pointer value  reference       rem_addr.  *+F * In this example the T3_DEMO server is listening on port 1024 at node address 1.2.3.4 9 * NB: The port number is specified in network byte order.  *-
 01  rem_addr. L     03                              pic s9(4)       comp    value   external ucx$c_af_inet.     03  rem_port_number.J         05  low_byte                pic x                   value   x"04".J         05  high_byte               pic x                   value   x"00".     03  rem_node_addr.J         05                          pic x                   value   x"01".J         05                          pic x                   value   x"02".J         05                          pic x                   value   x"03".J         05                          pic x                   value   x"04".-     03                              pic x(8).  *  01  sock_opt_desc.G     03  sock_opt_len                pic s9(4)       comp    value   24. L     03                              pic s9(4)       comp    value   external ucx$c_sockopt.A     03                                              pointer value  reference       sock_opt. 
 01  sock_opt. F     03                              pic s9(4)       comp    value   4.L     03                              pic s9(4)       comp    value   external ucx$c_reuseaddr.A     03                                              pointer value  reference       opt_on. F     03                              pic s9(4)       comp    value   4.L     03                              pic s9(4)       comp    value   external ucx$c_full_duplex_close.A     03                                              pointer value  reference       opt_on. F     03                              pic s9(4)       comp    value   4.L     03                              pic s9(4)       comp    value   external ucx$c_keepalive.A     03                                              pointer value  reference       opt_on.  *  01  tcp_opt_desc. F     03                              pic s9(4)       comp    value   8.L     03                              pic s9(4)       comp    value   external
 ucx$c_tcpopt. A     03                                              pointer value  reference       tcp_opt. 01  tcp_opt.F     03                              pic s9(4)       comp    value   4.L     03                              pic s9(4)       comp    value   external ucx$c_tcp_probe_idle. A     03                                              pointer value   reference       connect_timeout. * F 01  opt_on                          pic s9(9)       comp    value   1.F 01  opt_off                         pic s9(9)       comp    value   0.G 01  connect_timeout                 pic s9(9)       comp    value   10.  *+L * The Access Control Information buffer must be the first buffer transmitted toJ * the communication server. This buffer will not be passed to an execution serverF * and is the only data message buffer whose format and content will be scrutinized  * by Tier3.  * H * Each field must contain ascii coded text and may be null terminated or space 	 * filled.  *- 01  aci_buffer. .     03  aci_username                pic x(40)..     03  aci_password                pic x(40). *+L * The Tier3 Identification buffer is returned to the client, once access has beenG * authorized. The first three bytes will contain "T3$" and the next two 
 bytes willC * contain the major and minor version numbers of the Tier3 software  installed at * the target node. *- 01  t3_id_buffer. ,     03  t3_id                       pic xxx.*     03  maj_vers                    pic x.*     03  min_vers                    pic x.-     03  scsnode                     pic x(6). -     03  logfails                    pic 9(5).      03  last_login_i. -         05  yyyy                    pic 9(4). -         05  mt                      pic 9(2). -         05  dd                      pic 9(2). -         05  hh                      pic 9(2). -         05  mn                      pic 9(2). -         05  ss                      pic 9(2). -         05  cc                      pic 9(2).      03  last_login_n. -         05  yyyy                    pic 9(4). -         05  mt                      pic 9(2). -         05  dd                      pic 9(2). -         05  hh                      pic 9(2). -         05  mn                      pic 9(2). -         05  ss                      pic 9(2). -         05  cc                      pic 9(2).  *  01  time_vector_binary. 9     03  yyyy                        pic s9(4)       comp. 9     03  mt                          pic s9(4)       comp. 9     03  dd                          pic s9(4)       comp. 9     03  hh                          pic s9(4)       comp. 9     03  mn                          pic s9(4)       comp. 9     03  ss                          pic s9(4)       comp. 9     03  cc                          pic s9(4)       comp. 9 01  vms_binary_time                 pic s9(18)      comp. . 01  vms_ascii_date                  pic x(17). 01  day_names_table.A     03                              pic x(9)                value 	 "Monday". F     03                              pic 9(4)        comp    value   6.A     03                              pic x(9)                value 
 "Tuesday".F     03                              pic 9(4)        comp    value   7.A     03                              pic x(9)                value  "Wednesday".F     03                              pic 9(4)        comp    value   9.A     03                              pic x(9)                value  "Thursday". F     03                              pic 9(4)        comp    value   8.A     03                              pic x(9)                value 	 "Friday". F     03                              pic 9(4)        comp    value   6.A     03                              pic x(9)                value  "Saturday". F     03                              pic 9(4)        comp    value   8.A     03                              pic x(9)                value 	 "Sunday". F     03                              pic 9(4)        comp    value   6.= 01  day_names_array                                 redefines  day_names_table.=     03  day_of_week                                 occurs 7. -         05  day_name                pic x(9). 9         05  day_name_len            pic 9(4)        comp. 9 01  day_number                      pic 9(9)        comp. . 01  welcome_string                  pic x(65).9 01  welcome_string_len              pic 9(4)        comp. . 01  last_login_msg                  pic x(62). 01  logfails_msg. .     03  out_logfails                pic z(8)9.E     03                              pic x(37)               value   " & failures since last successful login". *+H * The following buffers are application specific. In this DEMO example a maximum H * buffer size of 510 bytes has been selected, and the first two bytes of every J * message have been reserved for message identification. Note that this is purelyK * an application convention that needs to be observed by the programmers of  the I * client and server components of DEMO and is not a requirement of Tier3.  *- 01  reply_buffer. +     03  msg_type                    pic xx. I         88  valid_reply                                     values  "00",  "11", "99". I         88  error_msg                                       value   "00". I         88  entry_data                                      value   "11". I         88  end_of_file                                     value   "99". /     03  reply_body                  pic x(508).  * = 01  error_buffer                                    redefines 
 reply_buffer. +     03                              pic xx. ,     03  error_msg_len               pic 999./     03  error_msg_text              pic x(505).  * = 01  entry_info_buffer                               redefines 
 reply_buffer. +     03                              pic xx. -     03  entry_number                pic 9(4). .     03  job_name                    pic x(39)..     03  job_status                  pic x(15)..     03  que_name                    pic x(31)..     03  que_type                    pic x(10)..     03  que_status                  pic x(10). *  01  get_entry_buffer. I     03                              pic xx                  value   "10". -     03  user_entry                  pic 9(4). G     03  max_entries                 pic 9(4)                value   12.  * 9 01  reply_body_len                  pic 9(4)        comp.  *+' * Application specific working-storage.  *- 01  screen_line_table.>     03  screen_line                                 occurs 12.-         05  entry_number            pic 9(4). .         05  job_name                pic x(39)..         05  job_status              pic x(15)..         05  que_name                pic x(31)..         05  que_type                pic x(10)..         05  que_status              pic x(10). 01  screen_header.E     03                              pic x(9)                value   "  Entry#".H     03                              pic x(40)               value   "Job Name".H     03                              pic x(16)               value   "Job Status".J     03                              pic x(32)               value   "Queue Name".J     03                              pic x(13)               value   "Queue Type".J     03                              pic x(22)               value   "Queue Status". 01  out_entry.+     03                              pic xx. -     03  entry_number                pic zzz9. ,     03                              pic xxx..     03  job_name                    pic x(39).*     03                              pic x..     03  job_status                  pic x(15).*     03                              pic x..     03  que_name                    pic x(31).*     03                              pic x..     03  que_type                    pic x(10).,     03                              pic xxx..     03  que_status                  pic x(10). * H 01  user_exit                       pic x                   value   "N".9 01  line_count                      pic 9(9)        comp. 9 01  screen_index                    pic 9(9)        comp. - 01  end_key                         pic x(4).  *  procedure division.  kick_off section.  00.      perform socket_and_connect. .     if sys_status not = ss$_normal go to fini.       perform application_logon.     if t3_id not = "T3$"$         move ss$_abort to sys_status         go to fini.        perform display_welcome.  D     perform get_entry_info until user_exit = "Y" or sys_status not = ss$_normal. .     if sys_status not = ss$_normal go to fini.       perform socket_close.  *  fini. .     call "sys$exit" using by value sys_status. *  get_entry_info section.  00. C     display "Enter job entry number (zero = wild, ctrl/z = exit): " 6             line 1 column 1 erase screen no advancing.&     accept user_entry with  conversion$                             reversed                              bold%                             protected +                             default is zero 1             at end          move "Y" to user_exit '                             go to fini.  *+ * Call my USER_RECV routine. *-     call    "sys$qiow">             using   by value        0, net_chan, io$_writevblk(                     by reference    iosb(                     by value        0, 04                     by reference    get_entry_buffer2                     by value        10, 0, 0, 0, 0             giving  sys_status. ;     if sys_status = ss$_normal move cond_val to sys_status. .     if sys_status not = ss$_normal go to fini.       move zeros to line_count. (     perform load_entries with test after@             until not entry_data or sys_status not = ss$_normal..     if sys_status not = ss$_normal go to fini.       if error_msg=             display "Error retrieving job entry information," 3             display error_msg_text(1:error_msg_len) J     else    display screen_header at line 1 column 1 reversed erase screenI             perform varying screen_index from 1 by 1 until screen_index > 
 line_countE                     move corr screen_line (screen_index) to out_entry %                     display out_entry              end-perform.  5     display "Press RETURN to continue." no advancing. *     accept key in end_key at end continue. *  fini.  *  socket_and_connect section.  00.      call "sys$assign" $         using   by descriptor "_BG:"&                 by reference  net_chan%                 by value      0, 0, 0          giving  sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.  *      call    "sys$qiow"<             using   by value        0, net_chan, io$_setmode(                     by reference    iosb(                     by value        0, 0K                     by reference    create_socket, omitted, local_sock_desc %                     by value        0 1                     by reference    sock_opt_desc %                     by value        0              giving  sys_status. ;     if sys_status = ss$_normal move cond_val to sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.  *+L * Set the connect timeout to 10 secs. TCPWARE requires privilege to do this. *-     call    "sys$qiow"<             using   by value        0, net_chan, io$_setmode(                     by reference    iosb4                     by value        0, 0, 0, 0, 0, 00                     by reference    tcp_opt_desc%                     by value        0              giving  sys_status. ;     if sys_status = ss$_normal move cond_val to sys_status. 1     if sys_status not = ss$_normal and ss$_nopriv 2         call "lib$stop" using by value sys_status. *+I * Request a logical link connection to the Tier3 communication server for  this application.  *-     call    "sys$qiow";             using   by value        0, net_chan, io$_access (                     by reference    iosb.                     by value        0, 0, 0, 01                     by reference    rem_sock_desc +                     by value        0, 0, 0              giving  sys_status. ;     if sys_status = ss$_normal move cond_val to sys_status.      if sys_status = ss$_rejectH         display "Access denied or the DEMO application is not running on
 remote node."      else&         if sys_status not = ss$_normal6             call "lib$stop" using by value sys_status. *  fini.  *  application_logon section. 00.  *+L * Once a logical link has been established, the communication server will beF * expecting access control information so that it can authorize client access * to the application.  * F * The aci_buffer allocates 40 bytes each for the username and password
 fields butF * as VMS is currently the only supported server platform for Tier3 you should limit, * usernames to 12 bytes and passwords to 32. *-3     display "Username: " erase screen no advancing. D     accept aci_username protected size 12 editing at end go to fini.&     display "Password: " no advancing.L     accept aci_password protected size 32 editing no echo at end go to fini.       call    "sys$qiow">             using   by value        0, net_chan, io$_writevblk(                     by reference    iosb(                     by value        0, 0.                     by reference    aci_buffer2                     by value        80, 0, 0, 0, 0             giving  sys_status. ;     if sys_status = ss$_normal move cond_val to sys_status. .     if sys_status not = ss$_normal go to fini. *+K * To complete the hand-shaking sequence the communication server will reply G * to a successfull access attempt with the Tier3 identification buffer.  * H * If the access control information was invalid the communication server> * will break the connection and the following read will return ss$_linkdiscon. G * Before retrying a failed access attempt you must therefore re-connect G * (io$_access) the communication server. The communication server's log E * file will contain detailed information describing any authorization  * failures.  * C * The Tier3 Identification buffer for handshake 1 is 48 bytes long.  *-     call    "sys$qiow"=             using   by value        0, net_chan, io$_readvblk (                     by reference    iosb(                     by value        0, 00                     by reference    t3_id_buffer2                     by value        48, 0, 0, 0, 0             giving  sys_status. ;     if sys_status = ss$_normal move cond_val to sys_status. "     if sys_status = ss$_linkdiscon0             display "User authorization failure"*             move ss$_normal to sys_status. *  fini.  *  load_entries section.  00.  *+I * As terminal i/o can take an indefinite amount of time to complete, once G * entry information is retrieved from the remote node it is deferred to E * working-storage rather than being sent directly to the screen. This @ * strategy removes a potential cause of buffer starvation in the
 communication J * server. If it is impractical to set a limit on the amount of information toJ * be returned from the execution server then the developer should considerI * deferring output to a temporary file, or expanding available memory via  * a routine such as LIB$GET_VM.  * B * Furthermore, if it is a requirement of your application that the association K * between client and execution server persist during terminal i/o it may be E * necessary to modify the application's parameter record in the Tier3 F * configuration file so that the "maximum servers" and "maximum links"L * parameters are set to the same value. This configuration would effectivelyI * dedicate a seperate execution server to each client and avoid potential - * delays in the servicing of client requests.  *-     call    "sys$qiow"=             using   by value        0, net_chan, io$_readvblk (                     by reference    iosb(                     by value        0, 0,                     by reference    msg_type1                     by value        2, 0, 0, 0, 0              giving  sys_status. ;     if sys_status = ss$_normal move cond_val to sys_status. .     if sys_status not = ss$_normal go to fini. *+C * TCP/IP is a stream oriented protocol and has no concept of record 
 boundries,K * therefore if you wish to exchange variable length records/messages (as is  the L * case with the DEMO example) then you have to read the first two bytes (ie: the J * record header) of each message first, as this will tell us how many more bytes ; * we need to receive to complete a SINGLE message transfer.  * G * If this convention was not observed then a single network read of 510 
 bytes (theJ * maximum buffer size for the demo example) could return multiple messages in a> * single buffer, resulting in trailing messages being ignored. *-     evaluate    true:         when    entry_data      move 109 to reply_body_len:         when    end_of_file     move   3 to reply_body_len:         when    error_msg       move 508 to reply_body_len     end-evaluate.        call    "sys$qiow"=             using   by value        0, net_chan, io$_readvblk (                     by reference    iosb(                     by value        0, 0.                     by reference    reply_body>                     by value        reply_body_len, 0, 0, 0, 0             giving  sys_status. ;     if sys_status = ss$_normal move cond_val to sys_status. -     if entry_data and sys_status = ss$_normal              add 1 to line_count D             move corr entry_info_buffer to screen_line (line_count). *  fini.  *  socket_close section.  00.  *+; * Break logical connection and dassign the network channel.  * F * The communication server will automatically deallocate any resourcesE * maintained on behalf of the client and will call, at AST level, the D * interrupt routine specified in the Tier3 configuration file if the: * client is currently associated with an execution server. *-@     call "sys$dassgn" using by value net_chan giving sys_status. *  display_welcome section. 00.      call "sys$fao"J         using   by descriptor   "Welcome to the DEMO application via TIER3 V!@UB.!@UB on node !AS" 2                 by reference    welcome_string_len.                 by descriptor   welcome_string2                 by reference    maj_vers, min_vers'                 by descriptor   scsnode          giving  sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status. 2     display welcome_string (1:welcome_string_len).  1     move corr last_login_i to time_vector_binary.      perform cvt_lastlogin.1     string      "    Last interactive login on ", C                 day_name (day_number) (1:day_name_len(day_number)), #                 " ", vms_ascii_date !                 delimited by size      into        last_login_msg.      display last_login_msg.   1     move corr last_login_n to time_vector_binary.      perform cvt_lastlogin.5     string      "    Last non-interactive login on ", C                 day_name (day_number) (1:day_name_len(day_number)), #                 " ", vms_ascii_date !                 delimited by size      into        last_login_msg.      display last_login_msg.        if logfails > zeros          if logfails = 1 C             display "        1 failure since last successful login"          else)             move logfails to out_logfails !             display logfails_msg.   5     display "Press RETURN to continue." no advancing. *     accept key in end_key at end continue.       go to fini.  *  cvt_lastlogin. * J     call "lib$cvt_vectim" using time_vector_binary, vms_binary_time giving sys_status. B     if sys_status not = lib$_normal call "lib$stop" using by value sys_status.        call "sys$asctim" !         using   by value        0 .                 by descriptor   vms_ascii_date/                 by reference    vms_binary_time !                 by value        0          giving  sys_status. D     if sys_status not = ss$_bufferovf call "lib$stop" using by value sys_status.   C     call "lib$day_of_week" using vms_binary_time, day_number giving  sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.  *  fini.  *  end program demo_client_tcp_ip.   0 "BC Berry" <nobody@spamcop.net> wrote in message2 news:9rkbb1hl1blmg4ms9qu48730p317gdavb4@4ax.com...F > The timeout on a connect function appears to be about 90 seconds. IsF > there a way to change that timeout? Being blocked for a minute and aG > half every time I try to access an offline logging machine is killing  > me.  >  > --F > E-mail address is invalid due to spam overflow - Please reply in the
 newsgroup. > --   ------------------------------  % Date: Mon, 20 Jun 2005 14:14:03 +0200 - From: Didier Morandi <prenom.nom@freesurf.fr> ) Subject: Re: UCX connect function timeout 4 Message-ID: <42b6b310$0$17377$636a15ce@news.free.fr>   Richard Maher wrote:   > Hi,  >  > F >>The timeout on a connect function appears to be about 90 seconds. Is% >>there a way to change that timeout?  >  > K > You use the ucx$tcpopt option of probe_idle. (FYI if you're using TCPWARE 3 > for this then you need privs to do it. IIRC OPER)  > M > The following example is taken from t3$examples:demo_client_tcp_ip.cob Look $ > at the socket_and_connect section.  K Richard, when you post code, pls change your prefs to 80 chars width... :-)    D.   ------------------------------   Date: 20 Jun 2005 12:26:27 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)) Subject: Re: VAX/VMS Consulting in Europe + Message-ID: <3hnqvjFhpdmtU2@individual.net>   3 In article <EnUI5cN11NtI@eisner.encompasserve.org>, > 	koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes:\ > In article <11bbb25ri2v5779@corp.supernews.com>, Dave Froble <davef@tsoft-inc.com> writes: >>  J >> If all we end up with is x86, then everything is a PC.  A PC running a K >> VAX emulator would then allow you to run a decent operating system.  If  L >> the alternative is a PC running windows, then maybe the conclusion needs 
 >> to change.  > F >    Will you be happier when your PC is running MacOS?  I'm sure simh! >    will run just find that way.  >   C SIMH will run just fine n a PC now under FreeBSD.  Why would anyone  want to run MacOS on a PC?   bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------    Date: 20 Jun 2005 07:24:10 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) ) Subject: Re: VAX/VMS Consulting in Europe 3 Message-ID: <EnUI5cN11NtI@eisner.encompasserve.org>   Z In article <11bbb25ri2v5779@corp.supernews.com>, Dave Froble <davef@tsoft-inc.com> writes: > I > If all we end up with is x86, then everything is a PC.  A PC running a  J > VAX emulator would then allow you to run a decent operating system.  If K > the alternative is a PC running windows, then maybe the conclusion needs   > to change.  D    Will you be happier when your PC is running MacOS?  I'm sure simh    will run just find that way.    ------------------------------   Date: 20 Jun 2005 17:06:43 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)) Subject: Re: VAX/VMS Consulting in Europe + Message-ID: <3hobd3Fi1hfpU1@individual.net>   4 In article <42b6f600$0$19049$636a15ce@news.free.fr>,0 	Didier Morandi <prenom.nom@freesurf.fr> writes: > Bill Gunshannon wrote: > F >> SIMH will run just fine n a PC now under FreeBSD.  Why would anyone >> want to run MacOS on a PC?  > P > Because Steve told us during his keynote last week that it was possible since  > version 10.0-0 of MAC OS X...   A That doesn't answer the question "Why?".  If the desire is to run B SIMH in order to run VMS on a PC, this has been possible since the> very first version of SIMH to simulate a VAX.  MAC OSX was not@ needed then and it certainly isn't now.  Having targeted the x86? architecture from it's earliest point I would expect FreeBSD to ? do the job better and more efficiently than MAC OSX which only  * decided to include x86 as an afterthought.   bill     --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  % Date: Mon, 20 Jun 2005 18:59:40 +0200 - From: Didier Morandi <prenom.nom@freesurf.fr> ) Subject: Re: VAX/VMS Consulting in Europe 4 Message-ID: <42b6f600$0$19049$636a15ce@news.free.fr>   Bill Gunshannon wrote:  E > SIMH will run just fine n a PC now under FreeBSD.  Why would anyone  > want to run MacOS on a PC?  N Because Steve told us during his keynote last week that it was possible since  version 10.0-0 of MAC OS X...    D.   ------------------------------   End of INFO-VAX 2005.343 ************************