1 INFO-VAX	Sun, 30 Oct 2005	Volume 2005 : Issue 606       Contents:N Re: Alphaserver 4100 and Mylex DAC960 RAID controller documentation/utilities?N Re: Alphaserver 4100 and Mylex DAC960 RAID controller documentation/utilities?N Re: Alphaserver 4100 and Mylex DAC960 RAID controller documentation/utilities? Re: Disk Optimizer 2.4 Re: Getting into VMS( NTPDATE buglet (unable to resolve CNAME), Re: NTPDATE buglet (unable to resolve CNAME) RF/RZ26 disk question  RF/RZ26 disk question I Stupid newbie's error: Howto reset system's password from user's account? M Re: Stupid newbie's error: Howto reset system's password from user's account? M Re: Stupid newbie's error: Howto reset system's password from user's account? M Re: Stupid newbie's error: Howto reset system's password from user's account? M Re: Stupid newbie's error: Howto reset system's password from user's account?  Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP  F ----------------------------------------------------------------------  % Date: Sun, 30 Oct 2005 13:42:30 +0000 $ From: Sampsa Laine <news@sampsa.com>W Subject: Re: Alphaserver 4100 and Mylex DAC960 RAID controller documentation/utilities? 0 Message-ID: <2005103013423050073%news@sampsacom>  D Your wisdom always arrives late unfortunately, I already managed to B build the array, and alas, this being my first ever RAID5 setup I H misconfigured it - I didn't set any drives as spares, just set up three E drive groups and initialized them. So my current setup is as follows:   7 (the letter after the drive size is the drive group ID)    Channel 0	Channel 1  18.2G A		18.2G B 18.2G A		18.2G B 18.2G A		18.2G B 18.2G B		18.2G A 18.2G B		18.2G A 9.1G C		9.1G C 9.1G C		9.1G C   Some questions: F -	If I lose a drive in a group, the group will still function, right?  Just at reduced speed?B -	Does it make sense to split the groups over the two channels? I  assumed that I would get more thruput this way?B -	The initialization took AGES. Like 6 or 7 hours. Is this normal?G -	Where's the actual physical connector to the third channel? I've got  F an extra BA365 kicking about that I'm just using as a shelf for a few H spare drives, but I could actually plug it in and add some 9 gig drives 
 as hot spare.   B Anyway, since I haven't installed anything on these drives (still C waiting for my OpenVMS hobbyist media pack, argh), I thought about   updating my setup as follows:    Channel 0	Channel 1  18.2G A		18.2G B 18.2G A		18.2G B 18.2G A		18.2G B 18.2G B		18.2G A 18.2G B spare	18.2G A spare  9.1G C		9.1G C 9.1G C		9.1G C spare  & Is this a good setup for these drives?   Regards,   Sampsa Laine    J On 2005-10-30 02:48:10 +0000, "Richard Tomkins" <tomkinsr@istop.com> said:  G > From my now failing memory, firmware updates to the Mylex fixed small K > things, like performance issues, larger drive handling, small glitches in $ > the SCSI protocols,  and the like. > I > Do not use Write Back operation unless you have a Ni-Cad battery on the I > module. If not, you will get data corruption, even on a clean shutdown.  > N > Ensure you power up drives first and power down drives last. The Mylex cache+ > is a lazy write for performance purposes.  > N > There was something I just remembered about block sizes and unfortunately do- > not remember what was optimal on the 4100..  > N > There was a maximum of number of drives allowed on the 3 channel controller,H > and 7 sticks in my memory. If you make a RAID 5, which is Striped withN > Parity (Spread across all drives), right? you should set aside one drive forL > a spare so that it can be automatically introduced as a replacement when a > failure occurs.  > L > I had a 4100 that had a failed drive that ran that way for months before I
 > noticed. >  >  >  > Q > ----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==---- B > http://www.newsfeeds.com The #1 Newsgroup Service in the World!  > 120,000+ Newsgroups M > ----= East and West-Coast Server Farms - Total Privacy via Encryption =----    ------------------------------  % Date: Sun, 30 Oct 2005 12:32:53 -0500 , From: "Richard Tomkins" <tomkinsr@istop.com>W Subject: Re: Alphaserver 4100 and Mylex DAC960 RAID controller documentation/utilities? 6 Message-ID: <1130693733_203@spool6-east.superfeed.net>   Found a Manual at,Q http://manuals.fujitsu-siemens.com/serverbooks/navigation/en/manuals/adapter.htm,   J Channel 2 is the most rear connector and was brought out to the back by anD extension cable and small SCSI connector mounted on a metal bracket.  D For best performance, yes, spread the drives evenly across all threeI channels. In RAID 5, loose a drive and performance is reduced as the unit = must now calculate what the missing data was. Big disks, long K initialization. We used to have the tech's set it up for 17:00 and check in  on the completion the next day.   K If you could find a connector for the third channel, then you could do some  good stuff.   A Take a gander through the manual I found, it has some good ideas.    Consider RAID 1 as well as 5.   9 Maybe even RAID 1+5 and 5+1, for the truly data paranoid.   J If you are just monkeying around, go for performance first in your design.    C http://www.pcguide.com/ref/hdd/perf/raid/levels/singleLevel0-c.html       1 "Sampsa Laine" <news@sampsa.com> wrote in message * news:2005103013423050073%news@sampsacom...E > Your wisdom always arrives late unfortunately, I already managed to C > build the array, and alas, this being my first ever RAID5 setup I I > misconfigured it - I didn't set any drives as spares, just set up three G > drive groups and initialized them. So my current setup is as follows:  > 9 > (the letter after the drive size is the drive group ID)  >  > Channel 0 Channel 1  > 18.2G A 18.2G B  > 18.2G A 18.2G B  > 18.2G A 18.2G B  > 18.2G B 18.2G A  > 18.2G B 18.2G A  > 9.1G C 9.1G C  > 9.1G C 9.1G C  >  > Some questions: G > - If I lose a drive in a group, the group will still function, right?  > Just at reduced speed?C > - Does it make sense to split the groups over the two channels? I  > assumed that I would > get more thruput this way?D > - The initialization took AGES. Like 6 or 7 hours. Is this normal?H > - Where's the actual physical connector to the third channel? I've gotG > an extra BA365 kicking about that I'm just using as a shelf for a few I > spare drives, but I could actually plug it in and add some 9 gig drives  > as hot spare.  > C > Anyway, since I haven't installed anything on these drives (still D > waiting for my OpenVMS hobbyist media pack, argh), I thought about > updating my setup as follows:  >  > Channel 0 Channel 1  > 18.2G A 18.2G B  > 18.2G A 18.2G B  > 18.2G A 18.2G B  > 18.2G B 18.2G A  > 18.2G B spare 18.2G A spare  > 9.1G C 9.1G C  > 9.1G C 9.1G C spare  > ( > Is this a good setup for these drives? > 
 > Regards, >  > Sampsa Laine >  > L > On 2005-10-30 02:48:10 +0000, "Richard Tomkins" <tomkinsr@istop.com> said: > I > > From my now failing memory, firmware updates to the Mylex fixed small J > > things, like performance issues, larger drive handling, small glitches in& > > the SCSI protocols,  and the like. > > K > > Do not use Write Back operation unless you have a Ni-Cad battery on the K > > module. If not, you will get data corruption, even on a clean shutdown.  > > J > > Ensure you power up drives first and power down drives last. The Mylex cache - > > is a lazy write for performance purposes.  > > ? > > There was something I just remembered about block sizes and  unfortunately do/ > > not remember what was optimal on the 4100..  > > D > > There was a maximum of number of drives allowed on the 3 channel controller, J > > and 7 sticks in my memory. If you make a RAID 5, which is Striped withL > > Parity (Spread across all drives), right? you should set aside one drive for L > > a spare so that it can be automatically introduced as a replacement when a  > > failure occurs.  > > L > > I had a 4100 that had a failed drive that ran that way for months before I  > > noticed. > >  > >  > >  > > H > > ----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet
 News==----C > > http://www.newsfeeds.com The #1 Newsgroup Service in the World!  > > 120,000+ Newsgroups I > > ----= East and West-Coast Server Farms - Total Privacy via Encryption  =----  >  >  >       O ----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==---- S http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups K ----= East and West-Coast Server Farms - Total Privacy via Encryption =----    ------------------------------    Date: 30 Oct 2005 09:47:38 -0800) From: "Rok Vidmar" <Rok.Vidmar@gmail.com> W Subject: Re: Alphaserver 4100 and Mylex DAC960 RAID controller documentation/utilities? C Message-ID: <1130694458.567694.222630@g43g2000cwa.googlegroups.com>   N >  -       If I lose a drive in a group, the group will still function, right? > Just at reduced speed?    Yes.   I > -       Does it make sense to split the groups over the two channels? I 1 > assumed that I would get more thruput this way?    Absolutely!   J > -       The initialization took AGES. Like 6 or 7 hours. Is this normal?  F  I don't think so. Check geometry and version of the drives (IRC thereG is an option for that in the SW).  18.2G should be identical, so should F the 9.1G. Mismatching geometry slows down cosiderably both buildup and  later the speed of virtual disk.G  By the way, it pays off to enlarge the cache. I've tried it up to 32MB 8 with ECC memory (hidden by the battery if you have one).  N > -       Where's the actual physical connector to the third channel? I've gotG > an extra BA365 kicking about that I'm just using as a shelf for a few I > spare drives, but I could actually plug it in and add some 9 gig drives  > as hot spare.   "  If it were there you wold see it.  C > Anyway, since I haven't installed anything on these drives (still D > waiting for my OpenVMS hobbyist media pack, argh), I thought about > updating my setup as follows:  >  > Channel 0       Channel 1  > 18.2G A         18.2G B  > 18.2G A         18.2G B  > 18.2G A         18.2G B  > 18.2G B         18.2G A  > 18.2G B spare   18.2G A spare  > 9.1G C          9.1G C > 9.1G C          9.1G C spare > ( > Is this a good setup for these drives?  )  I would use only one spare of each size.  -- Regards, Rok   ------------------------------  # Date: Sun, 30 Oct 2005 14:33:00 GMT # From: Beach Runner <bob@nospam.com>  Subject: Re: Disk Optimizer 2.4 7 Message-ID: <wQ49f.9172$kd.548@tornado.tampabay.rr.com>    andyg wrote:J > After trying to defrag a volume (inex of 90!) I can start the script andD > then try and monitor this script, after about 10 seconds a warningB > window appears "DFG-W-MONNOVOL ***** disk is not being currently > defragmented"  > A > Ive tried different settings but this is just playing ball why? H > The disk is currently in a mirrored Raid 5 and im running VMS 7.2-1 on > a 3 node cluster.  > Any ideas?
 > Cheers Andy  >  > E Just a comment. DFO is up to 2.9.  A lot of stuff has been fixed and  & improved.  Especially for large disks.   ------------------------------    Date: 30 Oct 2005 04:04:07 -0800 From: "Zach" <netrek@gmail.com>  Subject: Re: Getting into VMS A Message-ID: <1130673847.890166.6890@g43g2000cwa.googlegroups.com>    Colin Butcher wrote: [...]    Thanks for all the info Colin!   Zach   ------------------------------  % Date: Sun, 30 Oct 2005 02:41:15 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 1 Subject: NTPDATE buglet (unable to resolve CNAME) , Message-ID: <43645CD2.FFA85F98@teksavvy.com>    For VAX, TCPIP Services 5.3-2...  G The utility TCPIP$NTPDATE.EXE   (used to manually sychronise the clock)  has a problem.   ntpdate -d ntp1.cmc.ec.gc.ca     Fails. "Server not found".   NSLOOKUP ntp1.cmc.ec.gc.ca Name: wxo-srv1.cmc.ec.gc.ca  Address: 199.212.17.15 Aliases: ntp1.cmc.ec.gc.ca  - ntpdate -d wxo-srv1.cmc.ec.gc.ca 			Succeeds.       ; So it appears that the utility is unable to resolve CNAMES.    ------------------------------  # Date: Sun, 30 Oct 2005 16:13:18 GMT ( From: Alan Greig <greigaln@netscape.net>5 Subject: Re: NTPDATE buglet (unable to resolve CNAME) < Message-ID: <yi69f.94407$Ih5.5086@fe1.news.blueyonder.co.uk>   JF Mezei wrote:    > = > So it appears that the utility is unable to resolve CNAMES.    Works in TCPIP 5.3 (no patches)    $ ntpdate -q ntp1.cmc.ec.gc.ca3 Server ntp1.cmc.ec.gc.ca (199.212.17.15), stratum 2 # offset -0.2180220, delay +0.1456226 F Selected server is ntp1.cmc.ec.gc.ca (199.212.17.15) offset -0.2180220
 $ UCX SHO VER   6    Compaq TCP/IP Services for OpenVMS VAX Version V5.32    on a VAXserver 3900 Series running OpenVMS V7.3       --  
 Alan Greig   ------------------------------  % Date: Sun, 30 Oct 2005 16:30:12 +0100 & From: "H Vlems" <nospam@what.ever.com> Subject: RF/RZ26 disk question< Message-ID: <ecd07$4364e7ee$513b9a2c$30301@news.versatel.nl>  C Last week I was given an Alpha and a VAXstation (if you're curious: : home.zonnet.nl/hvlems) with a lot of spare parts and CD's.. Among the spare parts was a hard disk labeled:        |d|i|g|i|t|a|l|     Model RF/RZ26    P/N RZ26-E   K Perhaps the RF indication has always been part of the RZ26-E but now that I 2 have DSSI capable machines the RF part is suddenlyH interesting. RF35 drives are bulky and low capacity. This disk, at 1 GB, would be quite an improvement. The questions are:  ) (1) can this disk be used as a DSSI disk? % (2) if so, what jumpers must be set ?   
 Hans Vlems   ------------------------------  + Date: Sun, 30 Oct 2005 12:26:17 -0600 (CST) * From: sms@antinode.org (Steven M. Schweda) Subject: RF/RZ26 disk question2 Message-ID: <05103012261755_202AAB19@antinode.org>  & From: "H Vlems" <nospam@what.ever.com>   >      |d|i|g|i|t|a|l|! >     Model RF/RZ26    P/N RZ26-E  > [...] + > (1) can this disk be used as a DSSI disk? ' > (2) if so, what jumpers must be set ?   H    I assume that they used the same head-disk assembly for the DSSI RF26F and the SCSI RX26.  I also assume that the electronics assemblies wereG quite different, and thus that there's no simple way to change one into 
 the other.  H    Being able to see one of each would make my opinion more trustworthy.  H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode-org     Saint Paul  MN  55105-2547    ------------------------------  % Date: Sun, 30 Oct 2005 23:17:37 +1300 1 From: Tux Wonder-Dog <wes.parish@paradise.net.nz> R Subject: Stupid newbie's error: Howto reset system's password from user's account?# Message-ID: <43649ca8@clear.net.nz>   ; Howto reset system's password when the old one has expired?   L How do I do that?  VMS won't let me log in as system, and I'm able to log inK as wep, but though vax-simh tells me that "set proc/priv=all" is equivalent D to Unix's "su root", I'm still in wep's directory on dua1 instead ofF system's directory on dua0, and I don't know if I could reset system's6 password even if I were to "set def dua0:[sys$system]"  	 If anyone  --  O "Good, late in to more rewarding well."  "Well, you tonight.  And I was U lookintelligent woman of Ming home.  I trust you with a tender silence."  I C get a word into my hands, a different and unbelike, probably - 'she D fortunate fat woman', wrong word.  I think to me, I justupid.G Let not emacs meta-X dissociate-press write your romantic dialogs...!!!    ------------------------------  # Date: Sun, 30 Oct 2005 10:34:51 GMT L From: winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing)V Subject: Re: Stupid newbie's error: Howto reset system's password from user's account?6 Message-ID: <00A4C082.F7D99FEA@SSRL.SLAC.STANFORD.EDU>  W In article <43649ca8@clear.net.nz>, Tux Wonder-Dog <wes.parish@paradise.net.nz> writes: < >Howto reset system's password when the old one has expired? > M >How do I do that?  VMS won't let me log in as system, and I'm able to log in L >as wep, but though vax-simh tells me that "set proc/priv=all" is equivalentE >to Unix's "su root", I'm still in wep's directory on dua1 instead of G >system's directory on dua0, and I don't know if I could reset system's 7 >password even if I were to "set def dua0:[sys$system]"    $ SET PROC/PRIV=ALL   P turns on all those privileges but doesn't change your username, so it's not the J equivalent of "su root", it's just how you acquire all the privileges your account is allowed to have.    Do:   L $ SHOW LOG SYSUAF  ! Because this definition overrides the default location;G                    ! if it's not defined, you need to go to the default                     !location $ SET PROC/PRIV=ALL K $ SET DEF SYS$SYSTEM  ! which is SET DEF DUA0:[sys.sysexe] where the SYSUAF  lives  $ MCR AUTHORIZE , UAF> MOD SYSTEM/PASSWORD=newpassword /NOPWDE UAF> ^Z  $   M (Now you should be able to log in as system.  The /NOPWDE means that your new I SYSTEM password isn't preexpired, so you won't have to change it on first O login.  Not necessarily good practice in all cases, but on your virtual machine 6 you'll know what you made system change it to anyway.)   -- Alan        (this would leave    > 
 >If anyone >-- P >"Good, late in to more rewarding well."  "Well, you tonight.  And I wasV >lookintelligent woman of Ming home.  I trust you with a tender silence."  ID >get a word into my hands, a different and unbelike, probably - 'sheE >fortunate fat woman', wrong word.  I think to me, I justupid. H >Let not emacs meta-X dissociate-press write your romantic dialogs...!!!   ------------------------------  # Date: Sun, 30 Oct 2005 11:52:39 GMT A From: "Colin Butcher" <colin_DOT.butcher_AT@xdelta_DOT.co_DOT.uk> V Subject: Re: Stupid newbie's error: Howto reset system's password from user's account?= Message-ID: <bu29f.140511$G8.6874@text.news.blueyonder.co.uk>   J If it's an Alpha or Integrity then boot from the CD / DVD and get to a DCLH prompt, mount the target disc, point logicals at the UAF and RIGHTSLIST,C then use AUTHORIZE. I usually make a similar bootable CD for VAXes.   7 However, this seems to be an emulated (VAX) system, so:   3 If you have the appropriate privileges then simply:    $ SET DEFAULT SYS$SYSTEM:  $ MCR AUTHORIZE D UAF>MODIFY SYSTEM/PASS=<new_password>  with the optional /NOPWDL and /NOPWDEXP qualifiers
 UAF> <ctrl-Z>  $   L If you don't have the appropriate privileges then you're going to have to goI though a 'conversational boot'. There are a variety of techniques. Search K the web looking for "VMS CONVERSATIONAL BOOT" and you'll see quite a few of : them. This is what I tend to do under these circumstances:  
 >>> B/R5:1 SYSBOOT> SET /STARTUP OPA0:  SYSBOOT> CONTINUE   L First thing is to protect against typos in the command line which will cause you to have to start again.   
 $ SET NOON   $ SET DEFAULT SYS$SYSTEM:  $ MCR AUTHORIZE   F This will fail and complain that some shared image (whose name I can'tH remember) is not installed. Note the full filename specification for theG image, taking careful note of the odd-looking directory syntax. because J you'll need to repeat it exactly - this is a very primitive system at this< point with only just enough stuff in place to get it to run.   $ INSTALL := $INSTALL/COMMAND 4 $ INSTALL ADD <full_image_name>/OPEN/HEAD/SHARE/PROT  1 Now modify the password with AUTHORIZE (as above)   . Put the proper startup file back in place with   $ MCR SYSGEN SYSGEN> USE CURRENT + SYSGEN> SET /STARTUP SYS$SYSTEM:STARTUP.COM  SYSGEN> WRITE CURRENT  SYSGEN> <ctrl-Z> $   J Reboot the machine (halt button or equivalent in an emulator), or continue* with startup using @SYS$SYSTEM:STARTUP.COM   Have fun...    --     Hope this helps, Colin. ) colin DOT butcher AT xdelta DOT co DOT uk E It's not mine, but I like this definition: Legacy = stuff that works.    ------------------------------  % Date: Sun, 30 Oct 2005 14:15:20 +0200 4 From: Mike Rechtman <michael.rechtman.nospam@hp.com>V Subject: Re: Stupid newbie's error: Howto reset system's password from user's account?% Message-ID: <4364D578.36590EB@hp.com>    Tux Wonder-Dog wrote:  > = > Howto reset system's password when the old one has expired?  > N > How do I do that?  VMS won't let me log in as system, and I'm able to log inM > as wep, but though vax-simh tells me that "set proc/priv=all" is equivalent F > to Unix's "su root", I'm still in wep's directory on dua1 instead ofH > system's directory on dua0, and I don't know if I could reset system's8 > password even if I were to "set def dua0:[sys$system]" >  > If anyone  > --Q > "Good, late in to more rewarding well."  "Well, you tonight.  And I was W > lookintelligent woman of Ming home.  I trust you with a tender silence."  I E > get a word into my hands, a different and unbelike, probably - 'she F > fortunate fat woman', wrong word.  I think to me, I justupid.I > Let not emacs meta-X dissociate-press write your romantic dialogs...!!!   8 Look for a copy of the OpenVMS FAQ, go to section 5.6.1:& "Ive forgotten the SYSTEM password..."   a possible ULR would be 2 http://eisner.decus.org/vms/vmsfaq_007.html#mgmt5a  @ from there you will have to read section 5.6 for more details...   MikeR    --  E --------------------------------------------------------------------- E Usual disclaimer: All opinions are mine alone, perhaps not even that. ? Mike Rechtman                            *rechtman@tzora.co.il* F Kibbutz Tzor'a.                          Voice (home): 972-2-9908337  B   "20% of a job takes 80% of the time, the rest takes another 80%"E ---------------------------------------------------------------------  -----BEGIN GEEK CODE BLOCK-----  Version: 3.1: GCM/CS d(-)pu s:+>:- a++ C++ U-- L-- W++ N++ K? w--- V+++$6 PS+ PE-- t 5? X- tv-- b+ DI+ D-- G e++ h--- r+++ y+++@ ------END GEEK CODE BLOCK------    ------------------------------  % Date: Sun, 30 Oct 2005 18:58:01 +0100 & From: "H Vlems" <nospam@what.ever.com>V Subject: Re: Stupid newbie's error: Howto reset system's password from user's account?; Message-ID: <ce368$436509a8$513b9a2c$3582@news.versatel.nl>   % Alternatively, boot into SYSBOOT and:      SET UAFALTERNATE 1     SET STARTUP_P1 "MIN"3 and enter Continue in SYSBOOT to get the system up. G Note that this won't work if the previous owner did have an alternative  authorization file installed. L Most aren't that paranoid so thiw is very likely to work. Do note that there are a few things to remember with this method: K (1) you'll have to enter two passwords, not necessarily the same, to get in J (2) the SYSTEM account is not privileged by default (enable the privileges that you need)& (3) you're not in SYSMGR but in SYSEXEI (4) def/sys/exec sysuaf sys$system:sysuaf.dat , beforem making changes to * the characteristics of the SYSTEM account.   Hans  F "Colin Butcher" <colin_DOT.butcher_AT@xdelta_DOT.co_DOT.uk> schreef in? bericht news:bu29f.140511$G8.6874@text.news.blueyonder.co.uk... L > If it's an Alpha or Integrity then boot from the CD / DVD and get to a DCLJ > prompt, mount the target disc, point logicals at the UAF and RIGHTSLIST,E > then use AUTHORIZE. I usually make a similar bootable CD for VAXes.  > 9 > However, this seems to be an emulated (VAX) system, so:  > 5 > If you have the appropriate privileges then simply:  >  > $ SET DEFAULT SYS$SYSTEM:  > $ MCR AUTHORIZE F > UAF>MODIFY SYSTEM/PASS=<new_password>  with the optional /NOPWDL and > /NOPWDEXP qualifiers > UAF> <ctrl-Z>  > $  > K > If you don't have the appropriate privileges then you're going to have to  goK > though a 'conversational boot'. There are a variety of techniques. Search J > the web looking for "VMS CONVERSATIONAL BOOT" and you'll see quite a few of< > them. This is what I tend to do under these circumstances: >  > >>> B/R5:1 > SYSBOOT> SET /STARTUP OPA0:  > SYSBOOT> CONTINUE  > H > First thing is to protect against typos in the command line which will cause  > you to have to start again.  >  > $ SET NOON >  > $ SET DEFAULT SYS$SYSTEM:  > $ MCR AUTHORIZE  > H > This will fail and complain that some shared image (whose name I can'tJ > remember) is not installed. Note the full filename specification for theI > image, taking careful note of the odd-looking directory syntax. because L > you'll need to repeat it exactly - this is a very primitive system at this> > point with only just enough stuff in place to get it to run. >  > $ INSTALL := $INSTALL/COMMAND 6 > $ INSTALL ADD <full_image_name>/OPEN/HEAD/SHARE/PROT > 3 > Now modify the password with AUTHORIZE (as above)  > 0 > Put the proper startup file back in place with >  > $ MCR SYSGEN > SYSGEN> USE CURRENT - > SYSGEN> SET /STARTUP SYS$SYSTEM:STARTUP.COM  > SYSGEN> WRITE CURRENT  > SYSGEN> <ctrl-Z> > $  > L > Reboot the machine (halt button or equivalent in an emulator), or continue, > with startup using @SYS$SYSTEM:STARTUP.COM > 
 > Have fun...  >  > --   >  > Hope this helps, Colin. + > colin DOT butcher AT xdelta DOT co DOT uk G > It's not mine, but I like this definition: Legacy = stuff that works.  >  >    ------------------------------  % Date: Sun, 30 Oct 2005 14:15:13 +0800 3 From: "Richard Maher" <maher_rj@hotspamnotmail.com> # Subject: Re: Writing an OpenVMS ACP 1 Message-ID: <dk1og6$e0v$1@news-02.connect.com.au>    Hi JF,  H > -the equivalent of setting up a object name requires system manager to6 > include the definition in the ICC startup procedure,  K Can you show me an example of that? (Reserved Memory Registry yes but ICC?)    Regards Richard Maher   L PS. Below is a brief COBOL example of useing $ICC. As I said before COBOL isL crap with receiving BY VALUE :-( I also asked previously for a new interfaceL more tightly coupled to the performance features of I64 (and not so paranoidL about 6 register optimization) and everyone else said the $icc interface was3 both optimal and perfect for I64 so here we are -->    $ ty ICC.COB;1 identification division. program-id.    icc_server. data division. working-storage section.C 01  ast_receive            pic 9(9)        comp    value   external  ast_receive.C 01  ast_handshake          pic 9(9)        comp    value   external  ast_handshake.K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. * 0 01  assoc_handle           pic 9(9)        comp.= 01  buffer_count           pic 9(9)        comp    value   5. E 01  prot_sysprv                    pic 9(9)        comp    value   2.  *  procedure division.  kick_off section.  00.      perform server_init.%     display "Hibernating. . .zzzzzz".   '     call "sys$hiber" giving sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.  *  fini. A     call "sys$icc_close_assoc" using by value assoc_handle giving  sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.   
     stop run.  *  server_init section. 00.      call "sys$icc_open_assoc" '    using  by reference     assoc_handle *           by descriptor    "T3$TIP_SERVER"           by value 0, 0,!                    ast_handshake, !                    ast_handshake,                     ast_receive, ,                    buffer_count, prot_sysprv    giving sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.  *  fini.  *  end program icc_server.  identification division. program-id.    ast_handshake.  data division. working-storage section.K 01  ast_discon                     pic 9(9)        comp    value   external  ast_discon. K 01  ss$_reject                     pic 9(9)        comp    value   external  ss$_reject. K 01  ss$_abort                      pic 9(9)        comp    value   external 
 ss$_abort.K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. * + 01  rem_pid                        pointer. @ 01  buff_init_size         pic 9(9)        comp    value   1024.+ 01  event_type                     pointer. C     88  icc$c_ev_connect                           value   external  icc$c_ev_connect. K     88  icc$c_ev_disconnect                                value   external  icc$c_ev_disconnect.; 01  cxn_handle                                     pointer. 3 01  cxn_data_len                           pointer.  01  cxn_p5. 3     03  cxn_p5_lw                          pointer. =     66  cxn_reply_buff_len                 renames cxn_p5_lw. =     66  cxn_discon_status                  renames cxn_p5_lw.  01  user_context. 
     03  iosb. 0    05  cond_val            pic 9(4)        comp.    05              pic x(6).0     03  input_buff         pic 9(9)        comp.8     03  input_buff_size            pic 9(9)        comp.     03  ios_icc.0    05  icc_status          pic 9(4)        comp.    05              pic xx.0    05  recv_len            pic 9(9)        comp.0    05  req_handle          pic 9(9)        comp.0    05  reply_len           pic 9(9)        comp. *  linkage section.8 01  by_val_event_type              pic 9(9)        comp.8 01  by_val_cxn_handle              pic 9(9)        comp.8 01  by_val_cxn_data_len            pic 9(9)        comp.' 01  cxn_data_buff          pic x(1000). 0 01  by_val_cxn_p5          pic 9(9)        comp.- 01  discon_user_context            pic x(32). % 01  rem_username           pic x(12).  *  procedure division    using  by_val_event_type,           by_val_cxn_handle,           by_val_cxn_data_len,           cxn_data_buff,           by_val_cxn_p5,           discon_user_context,           rem_username.  kick_off section.  00. 2     set cxn_handle to reference by_val_cxn_handle.<     set cxn_data_len       to reference by_val_cxn_data_len..     set cxn_p5_lw  to reference by_val_cxn_p5.2     set event_type to reference by_val_event_type.       evaluate       true 4    when   icc$c_ev_connect perform accept_reject_cxn5    when   icc$c_ev_disconnect      perform remove_cxn K    when   other                    call "lib$stop" using by value ss$_abort      end-evaluate.  *  fini.      exit program.  *  accept_reject_cxn section. 00. 1     set rem_pid to reference discon_user_context. .     display "pid = ", rem_pid with conversion.(     display "username = ", rem_username.=     display "connect data = ", cxn_data_buff(1:cxn_data_len). =     display "cxn_data_len is ", cxn_data_len with conversion. D     display "reply_buff_len = ", cxn_reply_buff_len with conversion.  1     if cxn_data_buff(1:cxn_data_len) = "*Hello!*"     call "sys$icc_accept"-           using    by value        cxn_handle '            by reference    "*accepted*"             by value        10 '            by reference    user_context             by value        0           giving   sys_status      else    call "sys$icc_reject"-           using    by value        cxn_handle '            by reference    "*rejected*" )            by value        10, ss$_reject            giving   sys_status.A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.   I     call "lib$get_vm" using buff_init_size, input_buff giving sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status. +     move buff_init_size to input_buff_size.  *  fini.  *  remove_cxn section.  00. -     move discon_user_context to user_context. B     display "Exit Status was ", cxn_discon_status with conversion.       call "sys$icc_disconnect"     using  by value cxn_handle            by reference     iosb            by value ast_discon '           by reference     user_context            by value 0,0    giving sys_status. B      if sys_status not = ss$_normal call "lib$stop" using by value sys_status.  *  fini.  *  end program ast_handshake. identification division. program-id.    ast_receive.  data division. working-storage section.C 01  ast_read_comp          pic 9(9)        comp    value   external  ast_read_comp.K 01  ss$_abort                      pic 9(9)        comp    value   external 
 ss$_abort.K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. * ; 01  cxn_handle                                     pointer. 3 01  message_size                           pointer.  *  linkage section.8 01  by_val_msg_size                pic 9(9)        comp.8 01  by_val_cxn_handle              pic 9(9)        comp. 01  user_context. 
     03  iosb. 0    05  cond_val            pic 9(4)        comp.    05              pic x(6).0     03  input_buff         pic 9(9)        comp.8     03  input_buff_size            pic 9(9)        comp.     03  ios_icc.0    05  icc_status          pic 9(4)        comp.    05              pic xx.0    05  recv_len            pic 9(9)        comp.0    05  req_handle          pic 9(9)        comp.0    05  reply_len           pic 9(9)        comp. *  procedure division    using  by_val_msg_size,           by_val_cxn_handle,           user_context.  00. 2     set message_size to reference by_val_msg_size.2     set cxn_handle to reference by_val_cxn_handle.8     display "MSG Size = ", message_size with conversion.%     if message_size > input_buff_size I    call "lib$free_vm" using input_buff_size, input_buff giving sys_status K    if sys_status not = ss$_normal call "lib$stop" using by value sys_status  end-ifE    call "lib$get_vm" using message_size, input_buff giving sys_status K    if sys_status not = ss$_normal call "lib$stop" using by value sys_status  end-if(    move message_size to input_buff_size.       call "sys$icc_receive"    using  by value cxn_handle "           by reference     ios_icc            by value ast_read_comp'           by reference     user_context .           by value input_buff, input_buff_size    giving sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.  *  fini.      exit program.  *  end program ast_receive. identification division. program-id.    ast_read_comp.  data division. working-storage section.K 01  ss$_abort                      pic 9(9)        comp    value   external 
 ss$_abort.K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. *  linkage section. *  01  user_context. 
     03  iosb. 0    05  cond_val            pic 9(4)        comp.    05              pic x(6).0     03  input_buff         pic 9(9)        comp.8     03  input_buff_size            pic 9(9)        comp.     03  ios_icc.0    05  icc_status          pic 9(4)        comp.    05              pic xx.0    05  recv_len            pic 9(9)        comp.0    05  req_handle          pic 9(9)        comp.0    05  reply_len           pic 9(9)        comp. * & procedure division using user_context. 00.      if req_handle not = zeros %    display "Can't handle transceives" ,    call "lib$stop" using by value ss$_abort.       display "in read ast".       call "output_msg"     using  by value input_buff $           by reference     recv_len. *  fini.      exit program.  *  end program ast_read_comp. identification division. program-id.    ast_discon. data division. working-storage section.K 01  ss$_abort                      pic 9(9)        comp    value   external 
 ss$_abort.C 01  ss$_linkdiscon         pic 9(9)        comp    value   external  ss$_linkdiscon. K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. *  linkage section. *  01  user_context. 
     03  iosb. 0    05  cond_val            pic 9(4)        comp.    05              pic x(6).0     03  input_buff         pic 9(9)        comp.8     03  input_buff_size            pic 9(9)        comp.     03  ios_icc.0    05  icc_status          pic 9(4)        comp.    05              pic xx.0    05  recv_len            pic 9(9)        comp.0    05  req_handle          pic 9(9)        comp.0    05  reply_len           pic 9(9)        comp. * & procedure division using user_context. 00.      display "in discon ast".3     if cond_val not = ss$_normal and ss$_linkdiscon +    call "lib$stop" using by value cond_val.  *  fini.      exit program.  *  end program ast_discon.  identification division. program-id.    output_msg. data division. working-storage section.K 01  ss$_abort                      pic 9(9)        comp    value   external 
 ss$_abort.C 01  ss$_linkdiscon         pic 9(9)        comp    value   external  ss$_linkdiscon. K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. *  linkage section. * 0 01  out_buff                       pic x(65535).8 01  out_len                        pic 9(9)        comp. * + procedure division using out_buff, out_len.  00. .     display "message = ", out_buff(1:out_len). *  fini.      exit program.  *  end program output_msg.    $ ty icc_def.mar    .title icc_def !    .library "sys$library:lib.mlb"       $iccdef GLOBAL       .end    $ ty icc_client.cob  identification division. program-id.    icc_client. data division. working-storage section.C 01  ast_receive            pic 9(9)        comp    value   external  ast_receive.C 01  ast_disconnect         pic 9(9)        comp    value   external  ast_disconnect. C 01  ast_cxn_comp           pic 9(9)        comp    value   external 
 ast_cxn_comp. K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. * 0 01  assoc_handle           pic 9(9)        comp.= 01  buffer_count           pic 9(9)        comp    value   5. E 01  prot_sysprv                    pic 9(9)        comp    value   2.  01  user_context. 
     03  iosb. 0    05  cond_val            pic 9(4)        comp.    05              pic x(6).0     03  input_buff         pic 9(9)        comp.8     03  input_buff_size            pic 9(9)        comp.0     03  cxn_handle         pic 9(9)        comp..     03  return_buff                pic x(512).8     03  return_buff_len            pic 9(4)        comp. *  procedure division.  kick_off section.  00.      perform client_init.       call "sys$icc_connect"    using  by reference     iosb            by value ast_cxn_comp '           by reference     user_context            by value assoc_handle %           by reference     cxn_handle 3           by descriptor    "T3$TIP_SERVER", "TIER3" 3           by reference     user_context, "*Hello!*"            by value 8&           by reference     return_buff           by value 512*           by reference     return_buff_len           by value 0    giving sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.   &     display "Hibernating. . .zzzzzzz".     call "sys$hiber".      display "Trying again.".       call "sys$icc_connect"    using  by reference     iosb            by value ast_cxn_comp '           by reference     user_context            by value assoc_handle %           by reference     cxn_handle 3           by descriptor    "T3$TIP_SERVER", "TIER3" 2           by reference     user_context, "1234567"           by value 7&           by reference     return_buff           by value 512*           by reference     return_buff_len           by value 0    giving sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.   &     display "Hibernating. . .zzzzzzz".     call "sys$hiber".      display "Exiting.".  *  fini. A     call "sys$icc_close_assoc" using by value assoc_handle giving  sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.   
     stop run.  *  client_init section. 00.      call "sys$icc_open_assoc" '    using  by reference     assoc_handle *           by descriptor    "T3$TIP_CLIENT"           by value 0, 0, 0, "                    ast_disconnect,                    ast_receive,                      buffer_count,                    prot_sysprv    giving sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.  *  fini.  *  end program icc_client.  identification division. program-id.    ast_disconnect. data division. working-storage section.K 01  ast_discon                     pic 9(9)        comp    value   external  ast_discon. K 01  ss$_abort                      pic 9(9)        comp    value   external 
 ss$_abort.K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. * + 01  rem_pid                        pointer. @ 01  buff_init_size         pic 9(9)        comp    value   1024. *  linkage section.8 01  event_type                     pic 9(9)        comp.C     88  icc$c_ev_connect                           value   external  icc$c_ev_connect. K     88  icc$c_ev_disconnect                                value   external  icc$c_ev_disconnect.8 01  cxn_handle                     pic 9(9)        comp.0 01  cxn_data_len           pic 9(9)        comp.' 01  cxn_data_buff          pic x(1000).  01  cxn_p5. 0     03  cxn_p5_lw          pic 9(9)        comp.=     66  cxn_reply_buff_len                 renames cxn_p5_lw. =     66  cxn_discon_status                  renames cxn_p5_lw.  01  user_context. 
     03  iosb. 0    05  cond_val            pic 9(4)        comp.    05              pic x(6).0     03  input_buff         pic 9(9)        comp.8     03  input_buff_size            pic 9(9)        comp.8     03  a_cxn_handle               pic 9(9)        comp..     03  return_buff                pic x(512).8     03  return_buff_len            pic 9(4)        comp.% 01  rem_username           pic x(12).  *  procedure division    using  event_type,            cxn_handle,            cxn_data_len,            cxn_data_buff,           cxn_p5,            user_context,            rem_username.  kick_off section.  00.      if icc$c_ev_disconnect    perform remove_cxn      else,    call "lib$stop" using by value ss$_abort. *  fini.      exit program.  *  remove_cxn section.  00. B     display "exit Status was ", cxn_discon_status with conversion.     call "sys$icc_disconnect"     using  by value cxn_handle            by reference     iosb            by value ast_discon '           by reference     user_context            by value 0,0    giving sys_status. B      if sys_status not = ss$_normal call "lib$stop" using by value sys_status.  *  fini.  *  end program ast_disconnect.  identification division. program-id.    ast_receive.  data division. working-storage section.C 01  ast_read_comp          pic 9(9)        comp    value   external  ast_read_comp.K 01  ss$_abort                      pic 9(9)        comp    value   external 
 ss$_abort.K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. *  01  ast_param.     03  ios_icc.0    05  icc_status          pic 9(4)        comp.    05              pic xx.0    05  recv_len            pic 9(9)        comp.0    05  req_handle          pic 9(9)        comp.0    05  reply_len           pic 9(9)        comp. *  linkage section.0 01  message_size           pic 9(9)        comp.8 01  cxn_handle                     pic 9(9)        comp. 01  user_context. 
     03  iosb. 0    05  cond_val            pic 9(4)        comp.    05              pic x(6).0     03  input_buff         pic 9(9)        comp.8     03  input_buff_size            pic 9(9)        comp.8     03  a_cxn_handle               pic 9(9)        comp..     03  return_buff                pic x(512).8     03  return_buff_len            pic 9(4)        comp. *  procedure division    using  message_size,            cxn_handle,            user_context.  00. 8     display "MSG Size = ", message_size with conversion.%     if message_size > input_buff_size I    call "lib$free_vm" using input_buff_size, input_buff giving sys_status K    if sys_status not = ss$_normal call "lib$stop" using by value sys_status  end-ifE    call "lib$get_vm" using message_size, input_buff giving sys_status K    if sys_status not = ss$_normal call "lib$stop" using by value sys_status  end-if(    move message_size to input_buff_size.       call "sys$icc_receive"    using  by value cxn_handle "           by reference     ios_icc            by value ast_read_comp$           by reference     ast_param.           by value input_buff, input_buff_size    giving sys_status. A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.  *  fini.      exit program.  *  end program ast_receive. identification division. program-id.    ast_read_comp.  data division. working-storage section.K 01  ss$_abort                      pic 9(9)        comp    value   external 
 ss$_abort.K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. *  linkage section. *  01  ast_param.     03  ios_icc.0    05  icc_status          pic 9(4)        comp.    05              pic xx.0    05  recv_len            pic 9(9)        comp.0    05  req_handle          pic 9(9)        comp.0    05  reply_len           pic 9(9)        comp. * # procedure division using ast_param.  00.      if req_handle not = zeros %    display "Can't handle transceives" ,    call "lib$stop" using by value ss$_abort.       display "in read ast". *  fini.      exit program.  *  end program ast_read_comp. identification division. program-id.    ast_discon. data division. working-storage section.K 01  ss$_abort                      pic 9(9)        comp    value   external 
 ss$_abort.K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. *  linkage section. *  01  user_context. 
     03  iosb. 0    05  cond_val            pic 9(4)        comp.    05              pic x(6).0     03  input_buff         pic 9(9)        comp.8     03  input_buff_size            pic 9(9)        comp.8     03  a_cxn_handle               pic 9(9)        comp..     03  return_buff                pic x(512).8     03  return_buff_len            pic 9(4)        comp. * & procedure division using user_context. 00. 6     display "in discon ast", cond_val with conversion.I     if cond_val not = ss$_normal call "lib$stop" using by value cond_val.   :     call "sys$wake" using by value 0, 0 giving sys_status.A     if sys_status not = ss$_normal call "lib$stop" using by value  sys_status.  *  fini.      exit program.  *  end program ast_discon.  identification division. program-id.    ast_cxn_comp. data division. working-storage section.K 01  ast_xmit                       pic 9(9)        comp    value   external 	 ast_xmit. K 01  ss$_reject                     pic 9(9)        comp    value   external  ss$_reject. K 01  ss$_abort                      pic 9(9)        comp    value   external 
 ss$_abort.K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. *  linkage section. *  01  user_context. 
     03  iosb. 0    05  cond_val            pic 9(4)        comp.    05              pic x(6).0     03  input_buff         pic 9(9)        comp.8     03  input_buff_size            pic 9(9)        comp.8     03  a_cxn_handle               pic 9(9)        comp..     03  return_buff                pic x(512).8     03  return_buff_len            pic 9(4)        comp. * & procedure division using user_context. 00.      display "in cxn_comp ast".     if cond_val = ss$_reject    display "CXN rejected!"8    call "sys$wake" using by value 0, 0 giving sys_statusK    if sys_status not = ss$_normal call "lib$stop" using by value sys_status  end-if    go to fini.  I     if cond_val not = ss$_normal call "lib$stop" using by value cond_val.   "     if return_buff_len not = zeros=    display "Return buff = ", return_buff (1:return_buff_len).        call "sys$icc_transmit"     using  by value a_cxn_handle            by reference     iosb            by value ast_xmit C           by reference     user_context, "This is the message. . ."            by value 24     giving sys_status. B      if sys_status not = ss$_normal call "lib$stop" using by value sys_status.  *  fini.      exit program.  *  end program ast_cxn_comp.  identification division. program-id.    ast_xmit. data division. working-storage section.K 01  ast_discon                     pic 9(9)        comp    value   external  ast_discon. C 01  ss$_linkdiscon         pic 9(9)        comp    value   external  ss$_linkdiscon. K 01  ss$_abort                      pic 9(9)        comp    value   external 
 ss$_abort.K 01  ss$_normal                     pic 9(9)        comp    value   external  ss$_normal. 8 01  sys_status                     pic 9(9)        comp. *  linkage section. *  01  user_context. 
     03  iosb. 0    05  cond_val            pic 9(4)        comp.    05              pic x(6).0     03  input_buff         pic 9(9)        comp.8     03  input_buff_size            pic 9(9)        comp.8     03  a_cxn_handle               pic 9(9)        comp..     03  return_buff                pic x(512).8     03  return_buff_len            pic 9(4)        comp. * & procedure division using user_context. 00. 4     display "in xmit ast", cond_val with conversion.  ,     if cond_val = ss$_linkdiscon go to fini.I     if cond_val not = ss$_normal call "lib$stop" using by value cond_val.        call "sys$icc_disconnect"     using  by value a_cxn_handle            by reference     iosb            by value ast_discon '           by reference     user_context            by value 0,0    giving sys_status. B      if sys_status not = ss$_normal call "lib$stop" using by value sys_status.  *  fini.      exit program.  *  end program ast_xmit.     : "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message& news:436458C9.4137E3A4@teksavvy.com... > danco@ns2.pebble.org wrote: I > > I'm interested in knowing why you think ICC isn't as clean as DECnet.  > F > -totally different interface (not $QIO). Requires additional work if> > converting from DECNET or serial/LAT/mailbox communications. > H > -the equivalent of setting up a object name requires system manager toJ > include the definition in the ICC startup procedure, whereas for DECNET,I > the application can dynamically define the object name (assuming as has  privileges). > D > A decnet application is therefore more self contained. (although ID > realise that from a security point of view, ICC is more powerful).   ------------------------------  % Date: Sun, 30 Oct 2005 14:25:20 +0800 3 From: "Richard Maher" <maher_rj@hotspamnotmail.com> # Subject: Re: Writing an OpenVMS ACP 1 Message-ID: <dk1p37$f3g$1@news-02.connect.com.au>    Hi Dan,   A > Unless one has a large investment in _existing_ MACRO32 code to B > perpetuate, then I don't think it would be a good idea to create > more.   2 Oh Really, why not? 'Cos Hoff (et al) told you so?  : > As you say, MACRO32 is not native assembler on Alpha and9 > Itanium, but rather is just another low level language.   I Ahhh, ye olde heinous crime of being a low level language. Damn its eyes!    Regards Richard Maher   L PS. So the COBOL porridge is too cold, and the Macro-32 porridge is too hot?) But this little JAVA, C# is juuust right!   ' <danco@ns2.pebble.org> wrote in message + news:slrndm8hq0.5mj.danco@ns2.pebble.org... I > In article <436394E7.7759.27CF1887@localhost>, Stanley F. Quayle wrote:  > H > > True, but VAX Macro is supported on all 3 platforms.  On a VAX, it'sI > > directly converted to machine code.  On Alpha and Integrity, Macro is I > > processed by an optimizing compiler, just like any other language (C, , > > Fortran, etc.), to produce machine code. > > B > > And VAX Macro is the only language that comes "free" with VMS. > A > Unless one has a large investment in _existing_ MACRO32 code to B > perpetuate, then I don't think it would be a good idea to createA > more.  As you say, MACRO32 is not native assembler on Alpha and A > Itanium, but rather is just another low level language.  If you @ > need _real_ assembler on Alpha, then you need MACRO64.  And if: > you need _real_ assembler on Itanium, then you need IAS. >  > - Dan    ------------------------------  % Date: Sun, 30 Oct 2005 02:14:39 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> # Subject: Re: Writing an OpenVMS ACP , Message-ID: <43645699.4ACC79EB@teksavvy.com>   danco@ns2.pebble.org wrote: B > > And VAX Macro is the only language that comes "free" with VMS. > A > Unless one has a large investment in _existing_ MACRO32 code to B > perpetuate, then I don't think it would be a good idea to create > more.     C Then the owners of VMS must provide an alternative language that is G garanteed to be available on all systems, including those still running  on VAx 5.5-2 etc.     B Consider some application written in some strange lnaguage with anB obscure compiler. Vendor supplies object code. But a customisation= executable needs to be built locally to include site specific F information. The only way to do this is with MACRO because that is theH only assured utility available to create an object module which can then8 be linked with the rest of the pre-compiled application.  G And in the early days of communications, a simple file transfer program D was supplied as text in MACRO which was then compiled and provided a) primitive means to download the product.    ? It isn't a question of making a C or BLISS license available to D everyone. It is a question of having a command which is garanteed to6 work on any machine when you distribute your software.   ------------------------------  # Date: Sun, 30 Oct 2005 09:17:53 GMT ! From: Nigel Barker <nigel@hp.com> # Subject: Re: Writing an OpenVMS ACP 8 Message-ID: <cb19m1ledicofj64kac6eo7o8qjt7l6lfl@4ax.com>  P On Sat, 29 Oct 2005 15:27:35 -0400, "Stanley F. Quayle" <squayle@insight.rr.com> wrote:  $ >On 29 Oct 2005 at 10:48, Max wrote:G >> it's in assembler, which is unhelpful since the machine I'm using at D >> the moment is an Alpha but the eventual target machine will be an6 >> Integrity, presumably with different machine code.  > F >True, but VAX Macro is supported on all 3 platforms.  On a VAX, it's G >directly converted to machine code.  On Alpha and Integrity, Macro is  G >processed by an optimizing compiler, just like any other language (C,  ) >Fortran, etc.), to produce machine code.  > ? >And VAX Macro is the only language that comes "free" with VMS.   < Java, PERL & PHP are all "free" with VMS on Alpha & Itanium.   -- Nigel Barker Live from the sunny Cote d'Azur    ------------------------------  % Date: Sun, 30 Oct 2005 06:09:22 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> # Subject: Re: Writing an OpenVMS ACP , Message-ID: <43648D8D.1C6EEB6A@teksavvy.com>   Nigel Barker wrote: > > Java, PERL & PHP are all "free" with VMS on Alpha & Itanium.    9 "free" != garanteed to be installed and available after a K $DELETE/SYMBOL/GLOBAL * whcih is often done during installation procedures.   N And none come by default on VAX systems. (JAVA isn't available at all on VAX).  5 MACRO is the lowest common denominator. It is a fact.    ------------------------------    Date: 30 Oct 2005 07:10:38 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) # Subject: Re: Writing an OpenVMS ACP 3 Message-ID: <46iSd$M2WG+v@eisner.encompasserve.org>   \ In article <43645699.4ACC79EB@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes:  E > Then the owners of VMS must provide an alternative language that is I > garanteed to be available on all systems, including those still running  > on VAx 5.5-2 etc.   ! "Must" is pretty strong language.   D > Consider some application written in some strange lnaguage with anD > obscure compiler. Vendor supplies object code. But a customisation? > executable needs to be built locally to include site specific H > information. The only way to do this is with MACRO because that is theJ > only assured utility available to create an object module which can then: > be linked with the rest of the pre-compiled application.  H That is a relatively unreliable manner for a vendor to supply a product.F It is much more sound to have behavior of the product depend upon some parameter file or the like.   D Consider the issue of providing full testing of all code paths.  HowD could a vendor possibly test code paths that have not been written ?   ------------------------------    Date: 30 Oct 2005 07:12:34 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) # Subject: Re: Writing an OpenVMS ACP 3 Message-ID: <WiFFm7mY4ORn@eisner.encompasserve.org>   \ In article <cb19m1ledicofj64kac6eo7o8qjt7l6lfl@4ax.com>, Nigel Barker <nigel@hp.com> writes:R > On Sat, 29 Oct 2005 15:27:35 -0400, "Stanley F. Quayle" <squayle@insight.rr.com> > wrote: > % >>On 29 Oct 2005 at 10:48, Max wrote: H >>> it's in assembler, which is unhelpful since the machine I'm using atE >>> the moment is an Alpha but the eventual target machine will be an 7 >>> Integrity, presumably with different machine code.   >>G >>True, but VAX Macro is supported on all 3 platforms.  On a VAX, it's  H >>directly converted to machine code.  On Alpha and Integrity, Macro is H >>processed by an optimizing compiler, just like any other language (C, * >>Fortran, etc.), to produce machine code. >>@ >>And VAX Macro is the only language that comes "free" with VMS. > > > Java, PERL & PHP are all "free" with VMS on Alpha & Itanium.  F I do not think so.  I looked into PERL and found that one must install( something else to put it onto a machine.  F And it is certainly unavailable to organizations that will not install unsupported software.    ------------------------------  # Date: Sun, 30 Oct 2005 14:27:43 GMT ! From: Nigel Barker <nigel@hp.com> # Subject: Re: Writing an OpenVMS ACP 8 Message-ID: <gfj9m1td5e45prg9gorid84gdiskgnpcfu@4ax.com>  K On Sun, 30 Oct 2005 06:09:22 -0400, JF Mezei <jfmezei.spamnot@teksavvy.com>  wrote:   >Nigel Barker wrote:? >> Java, PERL & PHP are all "free" with VMS on Alpha & Itanium.  >  > : >"free" != garanteed to be installed and available after aL >$DELETE/SYMBOL/GLOBAL * whcih is often done during installation procedures.  P However they are "free" in the sense that as in no additional fee to be paid forP a license to use like COBOL or BASIC. They are also supported as part of OpenVMS, so no additional fee for a support contract.   -- Nigel Barker Live from the sunny Cote d'Azur    ------------------------------  # Date: Sun, 30 Oct 2005 14:25:57 GMT ! From: Nigel Barker <nigel@hp.com> # Subject: Re: Writing an OpenVMS ACP 8 Message-ID: <c6j9m15ka9sdri904dhve834dsetf97j0m@4ax.com>  M On 30 Oct 2005 07:12:34 -0600, Kilgallen@SpamCop.net (Larry Kilgallen) wrote:   ] >In article <cb19m1ledicofj64kac6eo7o8qjt7l6lfl@4ax.com>, Nigel Barker <nigel@hp.com> writes: S >> On Sat, 29 Oct 2005 15:27:35 -0400, "Stanley F. Quayle" <squayle@insight.rr.com> 	 >> wrote:  >>  & >>>On 29 Oct 2005 at 10:48, Max wrote:I >>>> it's in assembler, which is unhelpful since the machine I'm using at F >>>> the moment is an Alpha but the eventual target machine will be an8 >>>> Integrity, presumably with different machine code.  >>> H >>>True, but VAX Macro is supported on all 3 platforms.  On a VAX, it's I >>>directly converted to machine code.  On Alpha and Integrity, Macro is  I >>>processed by an optimizing compiler, just like any other language (C,  + >>>Fortran, etc.), to produce machine code.  >>> A >>>And VAX Macro is the only language that comes "free" with VMS.  >>  ? >> Java, PERL & PHP are all "free" with VMS on Alpha & Itanium.  > G >I do not think so.  I looked into PERL and found that one must install ) >something else to put it onto a machine.  > G >And it is certainly unavailable to organizations that will not install  >unsupported software.  L PERL is supported on OpenVMS. It is supplied by HP & is supported as part ofO base OpenVMS support along with all the other so-called eBusiness products like M Secure Web Server. If you have a support contract for OpenVMS then you have a M support contract for PERL. It is free as in 'no additional license or support L cost' unlike say C or BASIC. It does need to be installed from the PCSI kit.   -- Nigel Barker Live from the sunny Cote d'Azur    ------------------------------  % Date: Sun, 30 Oct 2005 15:32:36 +0100 & From: Paul Sture <paul.sture@decus.ch># Subject: Re: Writing an OpenVMS ACP + Message-ID: <3sk3s5Fopct3U1@individual.net>    Larry Kilgallen wrote:^ > In article <cb19m1ledicofj64kac6eo7o8qjt7l6lfl@4ax.com>, Nigel Barker <nigel@hp.com> writes: > R >>On Sat, 29 Oct 2005 15:27:35 -0400, "Stanley F. Quayle" <squayle@insight.rr.com> >>wrote: >> >>& >>>On 29 Oct 2005 at 10:48, Max wrote: >>> H >>>>it's in assembler, which is unhelpful since the machine I'm using atE >>>>the moment is an Alpha but the eventual target machine will be an 7 >>>>Integrity, presumably with different machine code.   >>> H >>>True, but VAX Macro is supported on all 3 platforms.  On a VAX, it's I >>>directly converted to machine code.  On Alpha and Integrity, Macro is  I >>>processed by an optimizing compiler, just like any other language (C,  + >>>Fortran, etc.), to produce machine code.  >>> A >>>And VAX Macro is the only language that comes "free" with VMS.  >>> >>Java, PERL & PHP are all "free" with VMS on Alpha & Itanium. >  > H > I do not think so.  I looked into PERL and found that one must install* > something else to put it onto a machine. >   D I don't see any software prerequisites with the HP supplied version:  W http://h71000.www7.hp.com/openvms/products/ips/apache/csws_perl_relnotes_20.html#prereq    ** start quote **       Software Prerequisites   D Perl for OpenVMS Version 5.6.1 ECO 3 requires OpenVMS Alpha Version  7.2-2 or higher.G Perl for OpenVMS Version 5.6.1 requires OpenVMS Alpha Version 7.2-1 or   higher.   H Perl runs with the Secure Web Server for OpenVMS via CSWS_PERL. You can < also use Perl in a standalone mode through the command line.  A You do not need to install the Secure Web Server for OpenVMS nor  " CSWS_PERL to use Perl for OpenVMS.   ** end quote **   H > And it is certainly unavailable to organizations that will not install > unsupported software.    See Nigel's response.    ------------------------------    Date: 30 Oct 2005 10:14:39 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) # Subject: Re: Writing an OpenVMS ACP 3 Message-ID: <HSDzKnY+iWQP@eisner.encompasserve.org>   T In article <3sk3s5Fopct3U1@individual.net>, Paul Sture <paul.sture@decus.ch> writes: > Larry Kilgallen wrote:  I >> I do not think so.  I looked into PERL and found that one must install + >> something else to put it onto a machine.  >>   > F > I don't see any software prerequisites with the HP supplied version: > Y > http://h71000.www7.hp.com/openvms/products/ips/apache/csws_perl_relnotes_20.html#prereq   C You need to install a PERL kit, which is not likely to be installed B at most sites.  The original discussion started with discussion of9 what people could depend on existing on all VMS systems.,    > ** start quote **  >  >    Software Prerequisites  > F > Perl for OpenVMS Version 5.6.1 ECO 3 requires OpenVMS Alpha Version  > 7.2-2 or higher.I > Perl for OpenVMS Version 5.6.1 requires OpenVMS Alpha Version 7.2-1 or  	 > higher.   E What about the VAX versions ?  J.F. was interested in doing something G on VAX, Alpha and Itanium, and claimed that Macro32 was the only common  supported language.    ------------------------------  % Date: Sun, 30 Oct 2005 17:54:02 +0100 & From: Paul Sture <paul.sture@decus.ch># Subject: Re: Writing an OpenVMS ACP + Message-ID: <3skc5bFoj25eU1@individual.net>    Larry Kilgallen wrote:V > In article <3sk3s5Fopct3U1@individual.net>, Paul Sture <paul.sture@decus.ch> writes: >  >>Larry Kilgallen wrote: >  > I >>>I do not think so.  I looked into PERL and found that one must install + >>>something else to put it onto a machine.  >>>  >>F >>I don't see any software prerequisites with the HP supplied version: >>Y >>http://h71000.www7.hp.com/openvms/products/ips/apache/csws_perl_relnotes_20.html#prereq  >  > E > You need to install a PERL kit, which is not likely to be installed D > at most sites.  The original discussion started with discussion of; > what people could depend on existing on all VMS systems.,  >   K Ah, I took your phrasing to imply prerequisites in addition to Perl itself.    >  >>** start quote **  >> >>   Software Prerequisites  >>F >>Perl for OpenVMS Version 5.6.1 ECO 3 requires OpenVMS Alpha Version  >>7.2-2 or higher.I >>Perl for OpenVMS Version 5.6.1 requires OpenVMS Alpha Version 7.2-1 or  	 >>higher.  >  > G > What about the VAX versions ?  J.F. was interested in doing something I > on VAX, Alpha and Itanium, and claimed that Macro32 was the only common  > supported language.   F Understood, although if anyone is interested in Perl on VAX/VMS, Perl F 5.8.7 (Not the supported HP version) is available on VAX, although it G requires DEC C rather than VAX C to build, and to build, also requires  
 MMS or MMK...   Q http://search.cpan.org/~nwclark/perl-5.8.7/README.vms#Introduction_to_Perl_on_VMS    ------------------------------   End of INFO-VAX 2005.606 ************************