1 INFO-VAX	Sun, 07 Apr 2002	Volume 2002 : Issue 192       Contents:' 2002 Government Grants For You......... 
 Anonymous ftp  Daylight savings Re: Daylight savings RE: Daylight savings Re: DCL command procedure   Re: digital MicroVAX 3100-96 Box Re: IA64 is not the VAX  Re: OpenVMS VAX V7.3 Re: OpenVMS VAX V7.3 Re: OpenVMS VAX V7.3) Re: Predictions - just for the hell of it ) Re: Predictions - just for the hell of it  Problem with Shadow Copy Re: SCSI Raid options for DS100 Re: Sue, a great promotion for "unhackable" vms!$ Vintage Computer Festival Europe 3.0# Re: Who has (ever) used DECmigrate? # Re: Who has (ever) used DECmigrate? # Re: Who has (ever) used DECmigrate? # Re: Who has (ever) used DECmigrate? ( Re: Why VMS is "unhackable" lesson 1 ...4 Re: Why VMS is "unhackable" lesson 3 ... (follow-up)  F ----------------------------------------------------------------------  % Date: Sun, 07 Apr 2002 11:58:36 -0500  From: qgrvc@topmail.com.ar0 Subject: 2002 Government Grants For You.........> Message-ID: <000045011680$00003b6c$00001ac2@plaza22.mbn.or.jp>   <html><body> <hr width =3D "100%"> K <center><font size =3D "+2" color =3D "#44C300"><b>Government Grants E-Boo=  k 2002 edition</font></b><p> <table><Tr><td> K <li>You Can Receive The <font color =3D "green"><b>Money</b></font> You Ne=  ed... K <li>Every day <b><font color =3D "green">millions of dollars</font></b> ar= ' e given away to people, just like you!! K <li>Your Government spends <b><font color =3D "green">billions</font></b> = $ of tax dollars on government grants.D <li>Do you know that private foundations, trust and corporations areH <li>required to give away a portion of theirs assets. It doesn't matter,K <li>where you live (USA ONLY), your employment status, or if you are broke= 	 , retired > <li>or living on a fixed income. There may be a grant for you! <hr width =3D "100%"> K <li><font color =3D "red"><b>ANYONE</b></font> can apply for a Grant from =  18 years old and up!K <li>We will show you HOW & WHERE to get Grants. <font color =3D "red"><b>T= I HIS BOOK IS NEWLY UPDATED WITH THE MOST CURRENT INFORMATION!!!</b></font> 3 <li>Grants from $500.00 to $50,000.00 are possible! , <li>GRANTS don't have to be paid back, EVER!K <li>Grants can be ideal for people who are or were bankrupt or just have b= 
 ad credit. </td></tr></table>: <br><font size =3D "+1">Please Visit Our Website<p></font>M And Place Your <font color =3D "red"> <b>Order TODAY!</b> </font><a href =3D= K  "http://www.software4udepo.com/GRANT/grant/"><b><font size=3D"5">CLICK HE=  RE</font></b> </a><p>&nbsp;<p> <font size=3D"1"> C We apologize for any email you may have inadvertently received.<br> K Please <a href =3D "http://www.software4udepo.com/GRANT/remove.htm">CLICK = 7 HERE</a> to be removed from future mailings.</font><br>    </BODY>  </HTML>    ------------------------------  $ Date: Sun, 7 Apr 2002 10:38:06 -0700# From: "Tom Linden" <tom@kednos.com>  Subject: Anonymous ftp9 Message-ID: <CIEJLCMNHNNDLLOOGNJIOEFNELAA.tom@kednos.com>    Running tcpip 5.1 under AXp 7.3   C When accessing the system from a command line interface works fine, = but when using browser with address ftp://freja.kednos.com it F display the ftp root directory but when you try to click on any of the@ entries. it responds "The page cannot be display"  This with IE. with Opera doesn't get that far    This waht IE displays   E 01/01/1980 12:00PM              0 Directory SYS$SYSDEVICE:[ANONYMOUS] > 01/01/1980 12:00PM              0 INPUT.DIR;1              1/48 23-AUG-2001 17:28:00  [SYSTEM]               (RWE,RWE,,)> 01/01/1980 12:00PM              0 LOGIN.COM;1              1/4: 23-AUG-2001 17:27:54  [ANONY,ANONYMOUS]      (RE,RE,RE,RE)> 01/01/1980 12:00PM              0 PUB.DIR;1                1/4< 28-AUG-2001 07:40:54  [SYSTEM]               (RWE,RWE,RE,RE)? 01/01/1980 12:00PM              0 Total of 3 files, 3/12 blocks   : I have a similar set up on Tru64 4.0d and that works fine. Is this a permission issue?    ------------------------------  $ Date: Sun, 7 Apr 2002 07:30:33 -0700# From: "Tom Linden" <tom@kednos.com>  Subject: Daylight savings 9 Message-ID: <CIEJLCMNHNNDLLOOGNJIIEFKELAA.tom@kednos.com>   @ I guess I should have paid more attention to recent postings fom@ the other side of the Atlantic.  In any event, I discovered that? one of my systems didn't have daylight svaings set, 6.2 on AXP.   @ And, UTC$TIME_SETUP.COM is not on the system, so I copied a file into SYS$MANAGER and...   . NORNS> @SYS$SYSROOT:[SYSMGR]UTC$TIME_SETUP.COME %UTC-I-UPDTIME, updating Time Zone information in SYS$COMMON:[SYSEXE] K %DCL-E-OPENIN, error opening SYS$SYSROOT:[SYSMGR]UTC$TIMEZONE_SETUP.COM; as  input  -RMS-E-FNF, file not found  J A search verifies that the first message is indeed coming from the script, so IG expect that there must be a missing logical.  Rather than trying to fix  this, @ where can i get a copy?  I have no idea why it would be missing.  B Incidentally, note that the owner is SYSTEM so shouldn't the first
 protection be System: RWED ?   7 NORNS> show sec  SYS$SYSROOT:[SYSMGR]UTC$TIME_SETUP.COM   = SYS$SYSROOT:[SYSMGR]UTC$TIME_SETUP.COM;1 object of class FILE       Owner: [SYSTEM]@      Protection: (System: RE, Owner: RWED, Group: RE, World: RE)!      Access Control List: <empty>    ------------------------------  % Date: Sun, 07 Apr 2002 17:08:43 +0200 ( From: Paul Sture <paul.sture@bluewin.ch> Subject: Re: Daylight savings * Message-ID: <3CB07D15.7A6C16F7@bluewin.ch>   Tom Linden wrote:  > B > I guess I should have paid more attention to recent postings fomB > the other side of the Atlantic.  In any event, I discovered thatA > one of my systems didn't have daylight svaings set, 6.2 on AXP.  > B > And, UTC$TIME_SETUP.COM is not on the system, so I copied a file > into SYS$MANAGER and...  >   A What version of VMS was the source system for that? This could be ' critical as there were changes in 7.3..   H Looking at my copy, UTC$TIME_SETUP.COM appears to be a new procedure for 7.3. From the abstract:   ? $!  Abstract:   This procedure is a replacement for a previous, 	 similarly ? $!              named procedure.  It includes the functionality 
 previously7 $!              provided by execution of the procedures  $!; $!                  SYS$MANAGER:UTC$TIMEZONE_SETUP.COM, and 6 $!                  SYS$MANAGER:UTC$CONFIGURE_TDF.COM, $!9 $!              and provides new functionality by calling  $!= $!                  SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COM  $! $!              Differences:> $!              By default, this new procedure always does all
 functions;E $!                  the prior procedure offered TIMEZONE/TDF options.  $   C Sorry, I don't have any previous VMS versions here to compare files ? with. I _do_ know that back when I used V6.2, we used to submit E SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM as a batch job on the Friday before  the time change.   0 > NORNS> @SYS$SYSROOT:[SYSMGR]UTC$TIME_SETUP.COMG > %UTC-I-UPDTIME, updating Time Zone information in SYS$COMMON:[SYSEXE] M > %DCL-E-OPENIN, error opening SYS$SYSROOT:[SYSMGR]UTC$TIMEZONE_SETUP.COM; as  > input  > -RMS-E-FNF, file not found > L > A search verifies that the first message is indeed coming from the script, > so II > expect that there must be a missing logical.  Rather than trying to fix  > this, B > where can i get a copy?  I have no idea why it would be missing. > D > Incidentally, note that the owner is SYSTEM so shouldn't the first > protection > be System: RWED ?  > 9 > NORNS> show sec  SYS$SYSROOT:[SYSMGR]UTC$TIME_SETUP.COM  > ? > SYS$SYSROOT:[SYSMGR]UTC$TIME_SETUP.COM;1 object of class FILE  >      Owner: [SYSTEM]B >      Protection: (System: RE, Owner: RWED, Group: RE, World: RE)# >      Access Control List: <empty>    Here's mine (7.3 remember)  . $ show security sys$manager:UTC$TIME_SETUP.COM  < SYS$COMMON:[SYSMGR]UTC$TIME_SETUP.COM;1 object of class FILE      Owner: [SYSTEM]B      Protection: (System: RWED, Owner: RWED, Group: RE, World: RE)!      Access Control List: <empty>       __
 Paul Sture Switzerland    ------------------------------  $ Date: Sun, 7 Apr 2002 09:54:02 -0700# From: "Tom Linden" <tom@kednos.com>  Subject: RE: Daylight savings 9 Message-ID: <CIEJLCMNHNNDLLOOGNJIAEFNELAA.tom@kednos.com>   D Well I think it was a 6.1 system, it was on a spare drive.  I lookedE through [000000]directory.lis but didn't see any obvious indicator of G version.  welcome.txt says 6.1, but it could be old.  I copy also from  
 a 7.3 system    . NORNS> @SYS$SYSROOT:[SYSMGR]UTC$TIME_SETUP.COM  !   Configuring the Local Time Zone     0   TIME ZONE SPECIFICATION -- MAIN Time Zone Menu  = %DCL-W-UNDSYM, undefined symbol - check validity and spelling   \ROW1\ = %DCL-W-UNDSYM, undefined symbol - check validity and spelling          0) GMT  C Select the number above that best represents the desired time zone:   + So I guess I am still missing a few things.    > -----Original Message-----1 > From: Paul Sture [mailto:paul.sture@bluewin.ch] & > Sent: Sunday, April 07, 2002 8:09 AM > To: Info-VAX@Mvb.Saic.Com  > Subject: Re: Daylight savings  >  >  > Tom Linden wrote:  > > D > > I guess I should have paid more attention to recent postings fomD > > the other side of the Atlantic.  In any event, I discovered thatC > > one of my systems didn't have daylight svaings set, 6.2 on AXP.  > > D > > And, UTC$TIME_SETUP.COM is not on the system, so I copied a file > > into SYS$MANAGER and...  > >  > C > What version of VMS was the source system for that? This could be ) > critical as there were changes in 7.3..  > J > Looking at my copy, UTC$TIME_SETUP.COM appears to be a new procedure for > 7.3. From the abstract:  > A > $!  Abstract:   This procedure is a replacement for a previous,  > similarly A > $!              named procedure.  It includes the functionality  > previously9 > $!              provided by execution of the procedures  > $!= > $!                  SYS$MANAGER:UTC$TIMEZONE_SETUP.COM, and 8 > $!                  SYS$MANAGER:UTC$CONFIGURE_TDF.COM, > $!; > $!              and provides new functionality by calling  > $!? > $!                  SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COM  > $! > $!              Differences:@ > $!              By default, this new procedure always does all > functions;G > $!                  the prior procedure offered TIMEZONE/TDF options.  > $  > E > Sorry, I don't have any previous VMS versions here to compare files A > with. I _do_ know that back when I used V6.2, we used to submit G > SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM as a batch job on the Friday before  > the time change. >   2 > > NORNS> @SYS$SYSROOT:[SYSMGR]UTC$TIME_SETUP.COMI > > %UTC-I-UPDTIME, updating Time Zone information in SYS$COMMON:[SYSEXE] ! > > %DCL-E-OPENIN, error opening  0 > SYS$SYSROOT:[SYSMGR]UTC$TIMEZONE_SETUP.COM; as	 > > input  > > -RMS-E-FNF, file not found > > C > > A search verifies that the first message is indeed coming from  
 > the script,  > > so IK > > expect that there must be a missing logical.  Rather than trying to fix 	 > > this, D > > where can i get a copy?  I have no idea why it would be missing. > > F > > Incidentally, note that the owner is SYSTEM so shouldn't the first > > protection > > be System: RWED ?  > > ; > > NORNS> show sec  SYS$SYSROOT:[SYSMGR]UTC$TIME_SETUP.COM  > > A > > SYS$SYSROOT:[SYSMGR]UTC$TIME_SETUP.COM;1 object of class FILE  > >      Owner: [SYSTEM]D > >      Protection: (System: RE, Owner: RWED, Group: RE, World: RE)% > >      Access Control List: <empty>  >  > Here's mine (7.3 remember) > 0 > $ show security sys$manager:UTC$TIME_SETUP.COM > > > SYS$COMMON:[SYSMGR]UTC$TIME_SETUP.COM;1 object of class FILE >      Owner: [SYSTEM]D >      Protection: (System: RWED, Owner: RWED, Group: RE, World: RE)# >      Access Control List: <empty>  >  >    > __ > Paul Sture
 > Switzerland  >    ------------------------------  % Date: Sun, 07 Apr 2002 13:27:30 +0200 ( From: Paul Sture <paul.sture@bluewin.ch>" Subject: Re: DCL command procedure* Message-ID: <3CB04942.1CA16770@bluewin.ch>   Didier Morandi wrote:  > 0 > I have even seen DEC programmers writing this: >  > $if i .eq. 1 then $goto OK > + Which is documented as optional in HELP IF.    _ 
 Paul Sture Switzerland    ------------------------------  % Date: Sun, 07 Apr 2002 09:53:46 -0400 2 From: rdeininger@mindspring.com (Robert Deininger)) Subject: Re: digital MicroVAX 3100-96 Box K Message-ID: <rdeininger-0704020953460001@1cust177.tnt1.nashua.nh.da.uu.net>   J In article <hrOr8.24150$2j3.1921995@news2.calgary.shaw.ca>, "Popeye Jones"  <popeyejones@hotmail.com> wrote:   >Hello all,  > L >I recently acquired a pallet of computer equipment from a company going out0 >of business.  One of the items I received is a: >  >digital MicroVAX 3100-96 Box 
 >w/ 128MB RAM  >no SCSI devices >no Power Supply Unit  > F >Anyone have a rough estimate of its value, before being submitted for	 >auction?   H Without a power supply, it's likely worth just a bit more than the valueF of the memory.  If the motherboard was known to be good, it would haveJ some value -- sometimes the motherboard dies and the power supply is stillD good.  Someone might want it for parts.  But in my experience, powerF supplies die first, so your box is missing the most-needed spare part.  I In your pallet of stuff, there might be another device from DEC that uses F the same kind of power supply.  (I don't know the part number of these supplies, sorry.)   L >PS. I believe an internal SCSI Exabyte HH CTS DAT Drive was originally partC >of this system, no other computers I received had SCSI capability.    ------------------------------   Date: 7 Apr 2002 12:34:33 GMT ( From: peter@taronga.com (Peter da Silva)  Subject: Re: IA64 is not the VAX1 Message-ID: <a8pecp$ja8$1@citadel.in.taronga.com>   @ In article <tjQr8.34764$w7.3041810@bin6.nnrp.aus1.giganews.com>,) Bill Todd <billtodd@metrocast.net> wrote: 6 >"Peter da Silva" <peter@taronga.com> wrote in message+ >news:a8oa8i$c6$1@citadel.in.taronga.com... I >> PDP-11/70 and VAX 11/780, both running comparable versions of BSD UNIX M >> (2.7, IIRC, and 4.1C). The 11/70 had 2M RAM, the 780 had more than that (I M >> don't know exactly how much). During the week before finals, quarter after F >> quarter, with both systems doing edits and compiles, using the same
 >compiler,L >> and both using a "smart" terminal driver that did command line processingI >> in the front end hardware (the Berkeley Bussiplexer) the 11/70 managed  >over 2 >> 70 users, the 11/780 croaked between 30 and 35.  L >Wow.  That kind of surprises me, but it does sound like a fair comparison -J >assuming the VAX software was using the same memory management techniquesM >(e.g., overlays) rather than virtual memory.  Certainly a hell of a lot more K >impact than the difference between 16 and 32 bit pointer-size overhead can 
 >account for.   I The -11 was using split I&D, but I don't believe any of the commonly used I programs were large enough to require overlays and I'm not sure that 2BSD K supported them at this point (2.11 did). With 70 users in 2M the system was I swapping fairly heavily, but the most commonly used programs were running : with shared text and so their code tended to stay in core.  I The VAX was using demand paged VM, but most of the programs were the same G as on the -11, so they had fairly small working sets and again the text N segments (code) tended to stay in real memory. There were a few large programsJ in use (Ingres, for example) but people tended to avoid running them under this kind of load. :->  J I do think that this was still a fair comparison, since the whole point to> using a VAX rather than an 11 *was* the demand paging support.  K ISTR that the 11 hardware could technically do demand paging, but with only L 8 pages per segment, it would have been kind of pointless. PDP-11 UNIX *did*L use this capability to trap page faults near the stack (which grew down fromI high memory in the UNIX memory model) and automatically grow the stack as J needed. The bourne shell also used this to allocate memory to the heap: itL would just use the memory and if it got a trap *then* it would call brk() to grab some more memory.  N Needless to say this caused problems on the first micro ports, since the 68000L and other micros of the day couldn't recover cleanly from memory faults... IK don't know what they did about the Bourne shell, but they used stack probessM in the subroutine preamble to make sure the stack was all there before trying 
 to use it.  6 Here's a longer discussion of the whole clever scheme:  * http://yarchive.net/comp/bourne_shell.html   --  @ Rev. Peter da Silva, ULC.	                                 WWFD?  F "Be conservative in what you generate, and liberal in what you accept" 	-- Matthew 10:16 (l.trans)i   ------------------------------  * Date: Sun, 7 Apr 2002 08:54:31 +0000 (UTC) From: david20@alpha2.mdx.ac.uk Subject: Re: OpenVMS VAX V7.3e+ Message-ID: <a8p1g7$emu$1@aquila.mdx.ac.uk>k  b In article <a8oc2e$abv$1@nntp9.atl.mindspring.net>, "Rich Jordan" <rjordan@mindspring.com> writes:J >DECwrite has a new version; we got it on the most recent SPL distribution> >(March?) specifically for VMS V7.3.  Sorry, no idea on Notes. >a  H Not used much anymore, but I've never had seen problem with Notes using  VMS 7.3 on Alpha.b  K Alpha1:sh sys/noproc                                                       bK OpenVMS V7.3  on node ALPHA1   7-APR-2002 09:49:22.08  Uptime  36 09:19:27 l    
 Alpha1: notesh   Notes>J Copyright  Digital Equipment Corporation. 1986, 1993. All Rights Reserved.L ----------------------------------------------------------------------------8                         Directory of Notebook class MAIN  E  Entry Name           Unseen  Last new note     Topics  Update statust6 >SAMPLE_CONFERENCE        85  10-OCT-2000 18:36     21  End of requested listingr     This is DEC Notes v2.5  
 David Webb VMS and Unix team leader CCSS Middlesex University   ------------------------------  % Date: Sun, 07 Apr 2002 13:22:53 +0200a( From: Paul Sture <paul.sture@bluewin.ch> Subject: Re: OpenVMS VAX V7.3>* Message-ID: <3CB0482D.520945B3@bluewin.ch>   Rich Jordan wrote: > K > DECwrite has a new version; we got it on the most recent SPL distributionn? > (March?) specifically for VMS V7.3.  Sorry, no idea on Notes.  >   4 Thanks. I'll have a look for Notes at the same time.  ? > Paul Sture wrote in message <3CAEC814.3722DCED@bluewin.ch>..., > >Mark D. Jilson wrote: > >> > >> Notes also used it. > >> > >And oh dear:b > >d
 > >$ notes= > >%SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable imagei > >$ > >>I > >So far, that's Notes and DECwrite which no longer work after upgrading=
 > >to V7.3 > >w   __
 Paul Sture Switzerland/   ------------------------------  % Date: Sun, 07 Apr 2002 13:39:29 +0200e( From: Paul Sture <paul.sture@bluewin.ch> Subject: Re: OpenVMS VAX V7.3<* Message-ID: <3CB04C11.4EDD5AE9@bluewin.ch>   david20@alpha2.mdx.ac.uk wrote:  > d > In article <a8oc2e$abv$1@nntp9.atl.mindspring.net>, "Rich Jordan" <rjordan@mindspring.com> writes:L > >DECwrite has a new version; we got it on the most recent SPL distribution@ > >(March?) specifically for VMS V7.3.  Sorry, no idea on Notes. > >F > I > Not used much anymore, but I've never had seen problem with Notes usinge > VMS 7.3 on Alpha.d >  > Alpha1:sh sys/noprocL > OpenVMS V7.3  on node ALPHA1   7-APR-2002 09:49:22.08  Uptime  36 09:19:27 >  > Alpha1: notest >  > Notes>L > Copyright  Digital Equipment Corporation. 1986, 1993. All Rights Reserved.N > ----------------------------------------------------------------------------: >                         Directory of Notebook class MAIN > G >  Entry Name           Unseen  Last new note     Topics  Update status28 > >SAMPLE_CONFERENCE        85  10-OCT-2000 18:36     21 >  End of requested listingI >  > This is DEC Notes v2.5 > - V2.5 here too. I'll try a fresh installation.R __
 Paul Sture Switzerland    ------------------------------  % Date: Sun, 07 Apr 2002 13:17:02 +0200 ( From: Paul Sture <paul.sture@bluewin.ch>2 Subject: Re: Predictions - just for the hell of it* Message-ID: <3CB046C8.25767722@bluewin.ch>   David Froble wrote:  >  > GreyCloud wrote: > J > > OT here, but in another newsgroup concerning OpenVMS, a college fellowL > > claimed that no one is developing any new products for OpenVMS.  Is this > > true???F >   > I gotta add one more question. > M > Does this 'college fellow' know what every single person and company in thec > world is doing?d > Q > Seems to reinforce something I've heard.  Those that can, do.  Those that can't, > teach.  . And those who can't teach become lecturers :-)   ducks and runs ...  E I'm just having an email discussion with someone whose website deniespH access to Netscape if running a version less than V6. He offers links toG IE, Netscape V6, Opera and Mozilla and can't understand why I shouldn'tF? merely follow his advice and get busy downloading one of those.    I sense a complete culture gap.I __
 Paul Sture Switzerland    ------------------------------   Date: 7 Apr 2002 08:56:55 -0600 - From: Kilgallen@SpamCop.net (Larry Kilgallen).2 Subject: Re: Predictions - just for the hell of it3 Message-ID: <Qt3ySauTwOjP@eisner.encompasserve.org>   W In article <3CAFB566.7010100@tsoft-inc.com>, David Froble <davef@tsoft-inc.com> writes:T > GreyCloud wrote: >  > J >> OT here, but in another newsgroup concerning OpenVMS, a college fellow L >> claimed that no one is developing any new products for OpenVMS.  Is this 
 >> true??? >   > I gotta add one more question. >  > N > Does this 'college fellow' know what every single person and company in the  > world is doing?u  H Perhaps he has total knowledge of those vendors to whom pre-announcementG is more important than product development.  Certainly that is disjointn! from my set of preferred vendors.y   ------------------------------  % Date: Sun, 07 Apr 2002 10:55:16 -0600E$ From: Lee Y T Mah <lytmah@cha.ab.ca>! Subject: Problem with Shadow Copy.) Message-ID: <3CB079F3.CA0E25AF@cha.ab.ca>e  G I am encountering a problem with Shadow Copying a particular drive back  into its regular shadow set.D The copy fails several minutes into the operation.  I have contacted" Compaq Support, but so far we have( had no success in resolving the problem.  * Manually started the Shadow Copy at 12:30.  8 %%%%%%%%%%%  OPCOM   6-APR-2002 12:35:16.69  %%%%%%%%%%% Message from user SYSTEM on K 9 %SHADOW_SERVER-I-SSRVINICPY, initiating copy operation onM?  _DSA659: at LBN: 0, I/O size: 127 blocks, ID number: 07000724.!  8 %%%%%%%%%%%  OPCOM   6-APR-2002 12:38:51.55  %%%%%%%%%%%+    (from node K at  6-APR-2002 12:38:51.89)T Message from user SYSTEM on K B %SHADOW_SERVER-E-SSRVTERMCPY, terminating copy operation on device)  _DSA659: at LBN: 0, ID number: 07000724.   8 %%%%%%%%%%%  OPCOM   6-APR-2002 12:38:51.56  %%%%%%%%%%%+    (from node K at  6-APR-2002 12:38:51.89)v Message from user SYSTEM on K C %SHADOW_SERVER-E-SSRVTRMSTS, reason for termination of operation on$ device  _DSA659: ABORT, abort   System info:,     FDDI VMScluster across two data centers.F     Six nodes in cluster - Four AS1200's at VMS 7.1-2, one ES45 at VMS$ 7.3, one VAXstation 4000 at VMS 7.3.D     Two AS1200's, two HSJ40's, two HSJ50's, one star coupler in each center..@     Four as1200's patched with VMS712_SHADOWING V5.0 22-FEB-2002 14:13:31.  One vote each.aF     ES45 patched with VMS73_SHADOWING V2.0 plus twelve latest patches. No vote.:     VAXstation 4000 patched with VAXSHAD01_073.  One vote.C     Approx. fifty-two shadow sets in cluster, with a member in eache center.o  C The problem shadow set is DSA659.  It has a shadow member DUA559 inS% center 1.  The other shadow member isS@ DUA659 in data center 2.  Each drive is dual-pathed to a pair of+ HSJ40's.  The HSJ40's are each connected to G their local star coupler.  The presence of the fast ES45 in the cluster ' has caused a CI saturation problem.  TotE overcome this problem, the AS1200's CIPCA firmware has been upgraded.:# In addition, Compaq has recommendedMF changing the parameter CI_ARBITRATION on all HSJ's from SYNCHRONOUS to ASYNCHRONOUS.  This F involves moving all drives off one HSJ to its twin, setting the HSJ to* SYNC, and then rebooting it.  On 04-Apr-02D I moved eleven 9.1GB drives off HSJM04 to HSJM05, made the change to SYNC, and rebooted the HSJ.nH I had restored six of the drives back to HSJM04 (now with CI_ARBITRATION set to SYNC) when I noticed E the constant mount verifications occurring, including those for otherh- shadow sets on drives dual-pathed to HSJ50's.oE I also noticed that during this time, drive DUA559 had dropped out ofl shadow set DSA659.  I made twoF attempts at shadow-copying DUA559 back into DSA659 but had no success.  In all this time, constant mountD verifications had degraded user response greatly, to the extent that+ some user were kicked right off the system.1F I succeeded in changing the HSJ40 back to ASYNC.  Two more attempts at shadow-copying DUA559 failed. F Eventually, user response returned to normal.  I then started a shadow% copy with a replacement drive (DUA578iG on an HSJ50) to shadow set DSA659 with no problem on the first attempt. E Suspecting DUA559 to be defective and the cause of my problems, I hadu Compaq swap out DUA559 Saturday H morning.  I initialized the new drive with no problem, filled it up, and# put it through an ANALYZE/DISK/READtG for two hours with no problems.  In fact, drive DUA559 has had an error " count of zero throughout all this.B Shadow set DSA659 was now comprised of DUA578 in data center 1 and" DUA659 in data center 2.  My plansE were to add the new DUA559 back into the shadow set as a third members  and then remove DUA578 after the shadow copy completed.G At 12:30, I initiated the shadow copy.  At 12:35, VMS acknowledged thise in OPERATOR.LOG.  At 12:38,FE the shadow copy aborted.  During this eight-minute window, continuousn" mount verifications were occurringF and users were complaining about being hung.  Subsequent investigation% revealed that the shadow copy abortedxB at LBN 0, drive DUA559 had been marked as a shadow member, but the" volume label was still the same as3 when I initialized it before doing the shadow copy.    Summary:F     Five attempts at shadow copying DUA559 into shadow set DSA659 have# failed with the same errors severalEE     minutes after starting.  Four times as a second member, once as a & third member with a replacement drive.C     I was able to create a single-member shadow set DSA959 with thee replacement drive.E     Since the problems began with DUA559, I have been able to perform  two shadow copies successfully.o+         - drive DUA578 to shadow set DSA659i,         - drive DUA678 to shadow set DSA639.  8 %%%%%%%%%%%  OPCOM   4-APR-2002 17:33:41.98  %%%%%%%%%%%1     (from node K      at  4-APR-2002 17:33:42.48)  Message from user SYSTEM on K 9 %SHADOW_SERVER-I-SSRVINICPY, initiating copy operation on,?  _DSA659: at LBN: 0, I/O size: 127 blocks, ID number: 07000724.s  8 %%%%%%%%%%%  OPCOM   4-APR-2002 17:37:16.40  %%%%%%%%%%%1     (from node K      at  4-APR-2002 17:37:16.89)n Message from user SYSTEM on KoB %SHADOW_SERVER-E-SSRVTERMCPY, terminating copy operation on device)  _DSA659: at LBN: 0, ID number: 07000724.e  8 %%%%%%%%%%%  OPCOM   4-APR-2002 17:37:16.41  %%%%%%%%%%%1     (from node K      at  4-APR-2002 17:37:16.90)o Message from user SYSTEM on KnC %SHADOW_SERVER-E-SSRVTRMSTS, reason for termination of operation onM device  _DSA659: ABORT, abort  8 %%%%%%%%%%%  OPCOM   4-APR-2002 17:43:22.64  %%%%%%%%%%%1     (from node J      at  4-APR-2002 17:43:22.61): Message from user SYSTEM on Jp9 %SHADOW_SERVER-I-SSRVINICPY, initiating copy operation on > _DSA659: at LBN: 0, I/O size: 127 blocks, ID number: 2A000721.  8 %%%%%%%%%%%  OPCOM   4-APR-2002 17:47:01.88  %%%%%%%%%%%1     (from node J      at  4-APR-2002 17:47:01.86)] Message from user SYSTEM on JWB %SHADOW_SERVER-E-SSRVTERMCPY, terminating copy operation on device)  _DSA659: at LBN: 0, ID number: 2A000721.w  8 %%%%%%%%%%%  OPCOM   4-APR-2002 17:47:01.89  %%%%%%%%%%%1     (from node J      at  4-APR-2002 17:47:01.86)a Message from user SYSTEM on JRC %SHADOW_SERVER-E-SSRVTRMSTS, reason for termination of operation on  device  _DSA659: ABORT, abort  8 %%%%%%%%%%%  OPCOM   4-APR-2002 17:53:43.06  %%%%%%%%%%%1     (from node K      at  4-APR-2002 17:53:43.56)t Message from user SYSTEM on KS9 %SHADOW_SERVER-I-SSRVINICPY, initiating copy operation one> _DSA659: at LBN: 0, I/O size: 127 blocks, ID number: 07000724.  8 %%%%%%%%%%%  OPCOM   4-APR-2002 17:56:38.13  %%%%%%%%%%%1     (from node K      at  4-APR-2002 17:56:38.63)u Message from user SYSTEM on K B %SHADOW_SERVER-E-SSRVTERMCPY, terminating copy operation on device)  _DSA659: at LBN: 0, ID number: 07000724.:  8 %%%%%%%%%%%  OPCOM   4-APR-2002 17:56:38.13  %%%%%%%%%%%1     (from node K      at  4-APR-2002 17:56:38.63)s Message from user SYSTEM on KiC %SHADOW_SERVER-E-SSRVTRMSTS, reason for termination of operation onv device  _DSA659: ABORT, abort  8 %%%%%%%%%%%  OPCOM   4-APR-2002 18:05:02.23  %%%%%%%%%%%1     (from node K      at  4-APR-2002 18:05:02.74)  Message from user SYSTEM on Kr9 %SHADOW_SERVER-I-SSRVINICPY, initiating copy operation ono> _DSA659: at LBN: 0, I/O size: 127 blocks, ID number: 07000724.  8 %%%%%%%%%%%  OPCOM   4-APR-2002 18:08:39.16  %%%%%%%%%%%1     (from node K      at  4-APR-2002 18:08:39.14)  Message from user SYSTEM on K B %SHADOW_SERVER-E-SSRVTERMCPY, terminating copy operation on device( _DSA659: at LBN: 0, ID number: 07000724.  8 %%%%%%%%%%%  OPCOM   4-APR-2002 18:08:39.16  %%%%%%%%%%%1     (from node K      at  4-APR-2002 18:08:39.14)l Message from user SYSTEM on KHC %SHADOW_SERVER-E-SSRVTRMSTS, reason for termination of operation onr device  _DSA659: ABORT, abort  5 Has anyone else encountered this shadow copy problem?1E Is there a SYSGEN parameter that disallows adding a third member to a6 shadow set?V5 If so, perhaps it got changed during recent Autogens. B The AS1200 nodes at VMS 7.1-2 have had thirteen patches since late Feb/2002, so perhaps& one of them affected volume shadowing.E There are other avenues I can try, but I want to avoid doing any moren shadow copy attemptsE unless absolute necessarily, since I don't want to put our 24x7 users. through any more discomfort.  B It seems that since including the new ES45 into the clustering and applying the thirteen patchesi> to the AS1200's, the cluster has not been as stable as before.     -- Lee   ; Lee Y T Mah                        Capital Health Authorityl? Email: lytmah@cha.ab.ca            Information Systems, RAH CSCd4 Phone:  (780) 477-4725, 477-4233   10240 Kingsway NW> Fax:      (780) 491-5119, 491-5619    Edmonton, AB, CAN T5H3V9   ------------------------------   Date: 7 Apr 2002 09:00:34 -0600n- From: Kilgallen@SpamCop.net (Larry Kilgallen)m' Subject: Re: SCSI Raid options for DS10v3 Message-ID: <ZOpY0I4MTwHX@eisner.encompasserve.org>   Z In article <3CAFCB86.3040102@qsl.network>, "John E. Malmberg" <wb8tyw@qsl.network> writes: > Rich Jordan wrote:D >  > It looks like we may finally be getting over the sales shutdownC >  > caused by compaq's alphacide last year; at least we're finallytD >  > seeing signs of interest again.  One possible needs to keep theI >  > price down in the DS10 range, but is looking for RAID capability forsG >  > fault tolerance.  It'll be a single node with either mirrorsets or.E >  > raid-5 (or striped mirrors if we can squeeze the price).  And ite$ >  > will _not_ be fiber; SCSI only. >  >E >  > It appears that the dearth of moderately priced SCSI support for D >  > RAID faster than SCSI-2 (the KZPAC) or Ultra (KZPBA to externalG >  > RA3000) with VMS is still in effect.  There are Ultra2 (KZPCA) and>G >  > Ultra3 (KZPEA?) controllers for independent disks, but none of thenG >  > faster internal RAID controllers have received VMS support, as farSD >  > as I can tell, and moderate priced externals (RA3000/HSZ22) areI >  > still limited to UltraWide and require the high-voltage differentialX
 >  > adapter.s >  >F >  > Is there by any chance any new hardware support coming out in theF >  > near future, either to allow the faster internal raid controllers@ >  > (KZPCC), or to provide > Ultrawide connectivity to externalH >  > controllers under OpenVMS? This one issue is turning into a problem5 >  > more and more frequently.  Any info appreciated.s > E > There are many storage solutions in that area being worked on.  At sA > present time most of the ones that I am aware of have not been  E > officially announced, so can not be discussed with out getting the  0 > product manager involved and a non-disclosure.  C While it was not on Rich's list of requirements, for some of us theoC ability to do SCSI clustering is important in such adapters.   HightC reliability requirements are not necessarily associated with larger  configurations, and vice versa.t   ------------------------------   Date: 7 Apr 2002 07:13:10 -0700t( From: BOB@INSTANTWHIP.COM (Bob Ceculski)9 Subject: Re: Sue, a great promotion for "unhackable" vms!@= Message-ID: <bd5b0641.0204070613.5866f300@posting.google.com>a  m bob@instantwhip.com (Bob Ceculski) wrote in message news:<d7791aa1.0204061322.2b99c1f7@posting.google.com>...s2 > remember m.c. hammer and "YOU CAN'T TOUCH THIS"?3 > why not hire him to do a vms commercial?  Instead / > of his line above, he could sing and dance toe >  > "YOU CAN'T HACK THIS"! > 4 > that would be an awesome commercial!  how about it+ > Sue, or anyone else in Q or HP marketing?   6 he and his dance team would be wearing OpenVMS tshirts6 and you could film it at defcon10, and use some of the2 defcon10 people in the clip trying to hack vms but7 failing ... if you want help directing the whole thing,R2 I would be happy to oblige for free ... I have the' whole thing laid out, and it's awesome!    ------------------------------  % Date: Sun, 07 Apr 2002 15:23:09 +0200 $ From: Gaby Chaudry <chaudry@gaby.de>- Subject: Vintage Computer Festival Europe 3.0T' Message-ID: <3CB0483D.31CC4E70@gaby.de>t   INVITATION to the $ Vintage Computer Festival Europe 3.0( April 27 and 28, 2002 in Munich, Germany  ? The third annual European Vintage Computer Festival awaits you!   
 Exhibition  B Dozens of old (but still not obsolete) computers to be viewed and 2 touched. No barrier between you and your dreams..    Speeches  G A series of speeches will be given to describe some systems in detail, tI discuss classic developments from today's perspective or other topics of   interest to collectors.   H There will also be a VCFe-Excursion to a hands on life demonstration of # a real classic big number cruncher.o   Flea Market   G No system will be ever completely debugged, so we are offering part of TA the hall to vendors to sell and trade historic gear. Anything is  D possible - as long as the item is computer related and more than 10  years old. 7  " Peoples Choice Award and Give Away  F All visitors are called to vote for their favourite piece of history. @ And unlike a constitutional poll, you may even win great stuff.    And more....  H ------------------------------------------------------------------------   Where, When and What ?   Where?  # Mehrzweckhalle des ESV Muenchen Ostr Baumkirchner Strasse 57i 81673 Munich Germany    When?o  ! 27th April 2002 from 1000 to 1830i" 28th April 2002 from 1015 to 1700   - Admission     Pre Registration    At the Door    One Person  * - One Day                         EUR 5,- ) - Both Days   EUR 5,-             EUR 8,-    Family  + - One Day     EUR 8,-             EUR 10,- 7+ - Both Days   EUR 10,-            EUR 15,-    H ------------------------------------------------------------------------   Further Informations   Contact Address:   H.Franke  mailto:hans.franke@mch20.sbs.de    VCFe Web Site: http://www.vcfe.org  http://www.vintage.org/vcfeb   ------------------------------   Date: 7 Apr 2002 06:55:00 GMT - From: djweath@attglobal.net (Dave Weatherall) , Subject: Re: Who has (ever) used DECmigrate?5 Message-ID: <DTiotGxQ0bj6-pn2-hT98iFh6p9Ux@localhost>2  0 On Sat, 6 Apr 2002 07:30:55 UTC, Didier Morandi  <Didier.Morandi@Free.fr> wrote:-  C > I'm interested to get field feedback from users of the DECmigrate D > utility, aka VEST, which, for those who do not know about it, is aI > binary image translator produced by the DEC Migration Engineering GroupeJ > when the Alpha came to life, to allow VAX executable images to be run on > Alpha systems. > J > After 20 years of VMS support, as I said in another post here, I know of > noone in Europe. > B > I personally think that the users did find their sources and did) > compile/link them on their new systems.d > 	 > Thanks.c >  > D.  D 10 years ago I went to one the Digital places here in Munich with a F tape containing the source and binaries for the Cross-Assembler/LinkerF suite I maintain. Within a few hours we had, IIRC, two elements vestedE and, for the most part, successfully running my cut-down test suite.  B The third had been both vested and compiled natively (it was 100% B Fortran, the others had a good bit of Macro-32). In addition, the F changes required for the Macro-32 had been identified. This applied toC stuff that caused problems for VEST, e.g. code in data, and things -> that would be required for the native Macro-32 compiler, e.g. @ CALL_ENTRY statements, psect organisation (the same as for Vest  really) etc.  B Within a year everything was running on one of the original Alpha  4000's (it still is :-). D  F My other area of interest, my main one now, is a test system. This hadF one component, the Analysis program, which was 98% Macro-32, a lot of F which had been MACRO-11. This stayed as a Vested program from 1993 to 0 1997/8 when the rewrite in Fortran was complete.  F We did for a long time (until 2000 when Y2K forced the change upon us)F use a VESTed version of EPOS. This was a perfect example of RW psects B containing and executing code. It had to. It only had the one. (I B exaggerate slightly because those object modules generated by Dec   compilers adhered to the rules).  > The only problem I recall, was the one Steve Lionel addresses C elsewhere. i..e. FORRTL compatibility between V5.n/V6.n of the VAX  F compiler and the RTL version on the Alpha. I did find a couple of bugs7 in Macro-32 compiler while I was doing the port though.r  E All in all, it was a very useful tool and saved us a lot of time and   effort.a  d Cheers - Dave.   ------------------------------  % Date: Sun, 07 Apr 2002 10:05:41 +0200s- From: Didier Morandi <Didier.Morandi@Free.fr> , Subject: Re: Who has (ever) used DECmigrate?' Message-ID: <3CAFFDD5.C5325AAB@Free.fr>E   Randy Park wrote:i > B > One restriction with VEST that a lot of people ignored or forgot; > was that translating images with VEST that were linked on:> > any version of the OS later than 5.5-2 was not supported and$ > could possibly not work correctly.  ? Because VESTed images require, within OpenVMS Alpha, a specificS+ Translated Images Environment (TIE) to run.%  O Actually, DECmigrate is not only a translator. It has also its own environment.2H This TIE is even a qualifier for the PASCAL compiler, to allow generated< code to be able to call VESTed images (disabled by default).  F For more on the TIE, see the Alpha Internals and Data Structures book, chapter 29.e   D.   ------------------------------  # Date: Sun, 07 Apr 2002 15:40:06 GMT " From: "Hans Vlems" <hvlems@iae.nl>, Subject: Re: Who has (ever) used DECmigrate?. Message-ID: <qLZr8.89$G3.8594@typhoon.bart.nl>  H We used a program for our library that was written in Businees Basic, an interpreter.K It ran on a VAx6310 and that was fairly slow, starting a session took up toc
 3 minutes.I There were no plans to port the interpreter to Alpha/VMS, since VMS was aa deadosI (remember the 90's). So I VESTed the interpreter and put the result on anm
 Alpha 21001 (single processor 4/200). The Alpha ran VMS V6.2.i= Getting started was reduced to somewhat less than 20 seconds.'D The users were very pleased and since I just copied there production database to runfK all the tests on (it was not that big) they flatly refused to return to thet 6310.b  H The vendor of course refused any support unless an error could be copied
 with VAX/VMS. B None was ever found until the software got replaced two years ago.   Hans8 Larry Kilgallen <Kilgallen@SpamCop.net> wrote in message- news:7v2U4kqob$Uv@eisner.encompasserve.org...r8 > In article <3CAEA430.D1B60649@Free.fr>, Didier Morandi  <Didier.Morandi@Free.fr> writes:E > > I'm interested to get field feedback from users of the DECmigratecF > > utility, aka VEST, which, for those who do not know about it, is aK > > binary image translator produced by the DEC Migration Engineering GrouptL > > when the Alpha came to life, to allow VAX executable images to be run on > > Alpha systems. > >tL > > After 20 years of VMS support, as I said in another post here, I know of > > noone in Europe. >c? > I use TECO every day, and on Alpha that is created with VEST.d >eD > > I personally think that the users did find their sources and did+ > > compile/link them on their new systems.S > = > DEC had the sources, but the Macro-32 was too squirrelly tol > just compile on Alpha. >s > =========  >mB > I have also used VEST on occasion myself, but I am not currently@ > running any VESTed programs of my own.  I would use it quicklyB > if I had any SCAN programs I needed to run on Alpha, but instead > I just run those on VAX.   ------------------------------   Date: 7 Apr 2002 12:10:45 -0600b+ From: young_r@encompasserve.org (Rob Young)L, Subject: Re: Who has (ever) used DECmigrate?3 Message-ID: <gxrL$0ceztGA@eisner.encompasserve.org>z  W In article <3CAEA430.D1B60649@Free.fr>, Didier Morandi <Didier.Morandi@Free.fr> writes:dC > I'm interested to get field feedback from users of the DECmigrate D > utility, aka VEST, which, for those who do not know about it, is aI > binary image translator produced by the DEC Migration Engineering Group5J > when the Alpha came to life, to allow VAX executable images to be run on > Alpha systems. > J > After 20 years of VMS support, as I said in another post here, I know of > noone in Europe. > B > I personally think that the users did find their sources and did) > compile/link them on their new systems.a >   : 	I used it.  It was how I convinced management a port from@ 	VAX to Alpha was not only "do-able" but we used VESTed binaries> 	initially at a client site that was starved for "horsepower."? 	Database systems didn't really run all that well on VAX 11/750e 	and attendent storage :-).s   				Robr   ------------------------------   Date: 7 Apr 2002 00:21:58 -0800t) From: P.Young@unsw.EDU.AU (Patrick Young)w1 Subject: Re: Why VMS is "unhackable" lesson 1 ...s= Message-ID: <55f85d77.0204070021.46558702@posting.google.com>p  ` "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message news:<3CAFC0AF.F51D62F9@fsi.net>...  G > It WAS angry outburst, but every word was undeniably true. No need to B > defend the truth. You can't call being pro-life sexist - the twoI > concepts are incompatible. You can't call being pro-life indefensible -S  D Valid case. I feel the same way regarding *disgusting* and *sexually9 mutated* practices such as circumcision (male or female).   eJ > As one of my mentors said, "if you don't stand for something you'll fallE > for anything". IMHO, many people stand for value that don't support J > them, with the result that they "fall for" every "feel-good", temptationC > that comes along, and the consequences be damned. That philosophy  > usually backfires, of course.S  	 Too true!E  D I'll leave this discussion at this point. Fred has already correctlyG pointed out that any discussion relating to *strong* feelings regarding E VMS, Politics, Religion, or anything else will not result in anythingY useful.p  3 Leave all topics to work their own way though life.n   ------------------------------   Date: 7 Apr 2002 07:01:57 -0700 ( From: BOB@INSTANTWHIP.COM (Bob Ceculski)= Subject: Re: Why VMS is "unhackable" lesson 3 ... (follow-up).= Message-ID: <bd5b0641.0204070601.784a2ac8@posting.google.com>C  p "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> wrote in message news:<s_Er8.1978$fL6.40803@news.cpqcorp.net>...< > "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message/ > news:Rw6jMCBN4Tx6@eisner.encompasserve.org...RI > > In article <a8kuvj$3c6$4@info.cs.uofs.edu>, bill@triangle.cs.uofs.edui >  (Bill Gunshannon) writes: > >%M > > > Does this NOWRT/NOEXE stuff have anything to do with the difficulty VMS-7 > > > seems to have implimenting the UNIX fork() call??S > >_C > > That has more to do with process structure and reference counts0F > > internal to the operating system.  This relates to a clean rundown > > etc. > F > Cloning the address space is the "easy" part, even if it may be moreL > overhead than a typical UNIX, a harder part is how to mimic the global I/ON > model of UNIX.  On VMS, the structures are mostly all process based, and notG > in a shared system space.  So the parent has an open file, and an I/O-F > channel associated with it.  Even once you go through the process ofL > "cloning" it, it doesn't become shared between the parent and the child inM > the same way UNIX would.  So.  Do we create a UNIX-like I/O mechanism for CoF > programs?  Do we try to solve the problem for programs that also useB > non-UNIX shared libraries?  It's not an "easy" problem to solve.  - not if it is going to open up security holes!0   ------------------------------   End of INFO-VAX 2002.192 ************************`i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i    `i     ai    ai    ai    ai    ai    ai    ai    ai    ai    	ai    
ai    ai    ai    
ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai     ai    !ai    "ai    #ai    $ai    %ai    &ai    'ai    (ai    )ai    *ai    +ai    ,ai    -ai    .ai    /ai    0ai    1ai    2ai    3ai    4ai    5ai    6ai    7ai    8ai    9ai    :ai    ;ai    <ai    =ai    >ai    ?ai    @ai    Aai    Bai    Cai    Dai    Eai    Fai    Gai    Hai    Iai    Jai    Kai    Lai    Mai    Nai    Oai    Pai    Qai    Rai    Sai    Tai    Uai    Vai    Wai    Xai    Yai    Zai    [ai    \ai    ]ai    ^ai    _ai    `ai    aai    bai    cai    dai    eai    fai    gai    hai    iai    jai    kai    lai    mai    nai    oai    pai    qai    rai    sai    tai    uai    vai    wai    xai    yai    zai    {ai    |ai    }ai    ~ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    ai    