INFO-VAX Tue, 22 Apr 2008 Volume 2008 : Issue 225 Contents: Re: comp.os.vms charter Re: HSD52 dead reduced raidset Re: HSD52 dead reduced raidset Re: HSD52 dead reduced raidset RE: Intel Itanium RAS Comparison with X86 Re: Intel Itanium RAS Comparison with X86 Re: Intel Itanium RAS Comparison with X86 RE: Intel Itanium RAS Comparison with X86 Re: Intel Itanium RAS Comparison with X86 OpenVMS Encryption Re: OT: IBM looking at Macintosh Re: OT: IBM looking at Macintosh ---------------------------------------------------------------------- Date: Tue, 22 Apr 2008 02:40:16 -0400 From: JF Mezei Subject: Re: comp.os.vms charter Message-ID: <480d8877$0$7220$c3e8da3@news.astraweb.com> moderator@comp.os.vms wrote: > true; > } > } > // ]]> Yes, very. ------------------------------ Date: 22 Apr 2008 08:59:37 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: HSD52 dead reduced raidset Message-ID: In article , "Richard B. Gilbert" writes: > > Yes, there are. But I have heard stories about $1,000 US/megabyte > recovered. True, or not, it's a poor position to be in!! And regular > backups are almost certainly cheaper. I know of a group that lost a critical hard drive. The backups also failed. I don't know how much they paid but they went from a several million dollar loss to a fairly cheap bill. Most likely the electronics failed but the platters still held the data. ------------------------------ Date: Tue, 22 Apr 2008 09:21:51 -0400 From: "Richard B. Gilbert" Subject: Re: HSD52 dead reduced raidset Message-ID: Bob Koehler wrote: > In article , "Richard B. Gilbert" writes: >> Yes, there are. But I have heard stories about $1,000 US/megabyte >> recovered. True, or not, it's a poor position to be in!! And regular >> backups are almost certainly cheaper. > > I know of a group that lost a critical hard drive. The backups also > failed. I don't know how much they paid but they went from a > several million dollar loss to a fairly cheap bill. > > Most likely the electronics failed but the platters still held the > data. > I suppose it happens that way occasionally. I'm not convinced, however, that it is a common failure mode. Given a decent environment to work in, the electronics can be expected to outlast the moving parts by a substantial margin. Do you ever test your ability to read and restore your backups? It's a very good idea! ------------------------------ Date: Tue, 22 Apr 2008 16:07:45 GMT From: Tad Winters Subject: Re: HSD52 dead reduced raidset Message-ID: "Richard B. Gilbert" wrote in news:Ke6dndwelttbbZHVnZ2dnUVZ_jKdnZ2d@comcast.com: [..snip..] > Yes, there are. But I have heard stories about $1,000 US/megabyte > recovered. True, or not, it's a poor position to be in!! And > regular backups are almost certainly cheaper. > Backups are definitely cheaper. My father spent about $600 to have data recovered from a 3.6 GB IDE drive, put on two DVDs and returned to him, after the drive failed. (CDs were an option, but a little more money and time.) The recovery company was clear about how they did things: They recover every file possible, and the customer must pay based on the total size of the data recovered. (I suspect it was per megabyte or portion thereof.) ------------------------------ Date: Tue, 22 Apr 2008 18:26:48 +1000 From: "O'Brien Paddy" Subject: RE: Intel Itanium RAS Comparison with X86 Message-ID: <0A7046B0A95F2B41B3712F0C5FD1CDC303BCD2@ex-tg2-pr.corporate.transgrid.local> This is a multi-part message in MIME format. ------_=_NextPart_001_01C8A452.9BB8AF7E Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -----Original Message----- From: Tad Winters [mailto:stafford.no.spam.winters2@verizon.net] Sent: Tue 4/22/2008 3:41 PM To: Info-VAX@Mvb.Saic.Com Subject: Re: Intel Itanium RAS Comparison with X86 =20 This all reminds me of Microsoft's end-user license agreement. Here=20 are a couple paragraphs: 22. DISCLAIMER OF WARRANTIES. The Limited=20 Warranty that appears above is the only=20 express warranty made to you and is provided=20 in lieu of any other express warranties or=20 similar obligations (if any) created by any=20 advertising, documentation, packaging, or=20 other communications. Except for the Limited=20 Warranty and to the maximum extent permitted=20 by applicable law, Manufacturer and its=20 suppliers (including MS, Microsoft=20 Corporation (including its subsidiaries) and=20 their respective suppliers) provide the=20 SOFTWARE and support services (if any) AS IS=20 AND WITH ALL FAULTS, and hereby disclaim all=20 other warranties and conditions, whether=20 express, implied or statutory, including, but=20 not limited to, any (if any) implied=20 warranties, duties or conditions of=20 merchantability, of fitness for a particular=20 purpose, of reliability or availability, of=20 accuracy or completeness of responses, of=20 results, of workmanlike effort, of lack of=20 viruses, and of lack of negligence, all with=20 regard to the SOFTWARE, and the provision of=20 or failure to provide support or other=20 services, information, software, and related=20 content through the SOFTWARE or otherwise=20 arising out of the use of the SOFTWARE. ALSO,=20 THERE IS NO WARRANTY OR CONDITION OF TITLE,=20 QUIET ENJOYMENT, QUIET POSSESSION,=20 CORRESPONDENCE TO DESCRIPTION OR NON- INFRINGEMENT WITH REGARD TO THE SOFTWARE. =20 23. EXCLUSION OF INCIDENTAL, CONSEQUENTIAL=20 AND CERTAIN OTHER DAMAGES. TO THE MAXIMUM=20 EXTENT PERMITTED BY APPLICABLE LAW, IN NO=20 EVENT SHALL MANUFACTURER OR ITS SUPPLIERS=20 (INCLUDING MS, MICROSOFT CORPORATION,=20 (INCLUDING ITS SUBSIDIARIES) AND THEIR=20 RESPECTIVE SUPPLIERS) BE LIABLE FOR ANY=20 SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT, OR=20 CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING,=20 BUT NOT LIMITED TO, DAMAGES FOR LOSS OF=20 PROFITS OR CONFIDENTIAL OR OTHER INFORMATION,=20 FOR BUSINESS INTERRUPTION, FOR PERSONAL=20 INJURY, FOR LOSS OF PRIVACY, FOR FAILURE TO=20 MEET ANY DUTY OF GOOD FAITH OR OF REASONABLE=20 CARE, FOR NEGLIGENCE, AND FOR ANY OTHER=20 PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING=20 OUT OF OR IN ANY WAY RELATED TO THE USE OF OR=20 INABILITY TO USE THE SOFTWARE, THE PROVISION=20 OF OR FAILURE TO PROVIDE SUPPORT OR OTHER=20 SERVICES, INFORMATION, SOFTWARE, AND RELATED=20 CONTENT THROUGH THE SOFTWARE, OR OTHERWISE=20 ARISING OUT OF THE USE OF THE SOFTWARE, OR=20 OTHERWISE UNDER OR IN CONNECTION WITH ANY=20 PROVISION OF THIS EULA, EVEN IN THE EVENT OF=20 THE FAULT, TORT (INCLUDING NEGLIGENCE),=20 MISREPRESENTATION, STRICT LIABILITY, BREACH=20 OF CONTRACT OR BREACH OF WARRANTY OF=20 MANUFACTURER OR ANY SUPPLIER (INCLUDING MS,=20 MICROSOFT CORPORATION (INCLUDING ITS=20 SUBSIDIARIES) AND THEIR RESPECTIVE SUPPLIERS), AND EVEN IF MANUFACTURER OR ANY SUPPLIER=20 (INCLUDING MS, MICROSOFT CORPORATION=20 (INCLUDING ITS SUBSIDIARIES) AND THEIR=20 RESPECTIVE SUPPLIERS) HAS BEEN ADVISED OF THE=20 POSSIBILITY OF SUCH DAMAGES. I hope this comes over correctly --- I am forced onto this stupid microshaf= t stuff. If not, I apologise, and is why I do not now write here much. An= d I cannot use internal Outlook mail, I only have access from my VMS (genuf= lection) box to the very frustrating Outlook Web Access. In reply to Tad: -- since I never have and never will buy anything from mic= roshaft, I have never read Herr (a quick goose-step) Ballmer's licence. Th= anks for the enlightenment. With this sort of licence agreement, why are large companies and government= s agreeing to such restrictions or exceptions? Thankfully I have seen repo= rts that several governments are dishing this most "crapfull" (not a word, = I do know) OS. O.K., the home user is probably not too worried as he/she i= s not usually doing too much other than reading email, playing solitaire an= d letting themselves become a zombie. But companies and organisations ... = ?? Yes, Bill, I know, but how many of them do tie down their (not "there" -- a= nd I haven't used "you're", so not "your" -- this is general, not specifica= lly to you Mr. Gunshannon) systems? I know of several organisations that d= o not. Regards, Paddy *********************************************************************** Please consider the environment before printing this email. "This electronic message and any attachments may contain privileged and confidential information intended only for the use of the=20 addressees named above. If you are not the intended recipient of=20 this email, please delete the message and any attachment and advise the sender. You are hereby notified that any use, dissemination,=20 distribution, reproduction of this email is prohibited. If you have received the email in error, please notify TransGrid=20 immediately. Any views expressed in this email are those of the=20 individual sender except where the sender expressly and with=20 authority states them to be the views of TransGrid. TransGrid uses virus-scanning software but excludes any liability for viruses contained in any attachment." *********************************************************************** ------_=_NextPart_001_01C8A452.9BB8AF7E Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Intel Itanium RAS Comparison with X86

-----Original Message-----
From: Tad Winters [mailto:stafford.no.spam.winters2@verizon.net]
Sent: Tue 4/22/2008 3:41 PM
To: Info-VAX@Mvb.Saic.Com
Subject: Re: Intel Itanium RAS Comparison with X86

This all reminds me of Microsoft's end-user license agreement.  Here are a couple paragraphs:

22. DISCLAIMER OF WARRANTIES. The Limited
    Warranty that appears above is the only
    express warranty made to you and is provided
    in lieu of any other express warranties or
    similar obligations (if any) created by any
    advertising, documentation, packaging, or
    other communications. Except for the Limited
    Warranty and to the maximum extent permitted
    by applicable law, Manufacturer and its
    suppliers (including MS, Microsoft
    Corporation (including its subsidiaries) and
    their respective suppliers) provide the
    SOFTWARE and support services (if any) AS IS
    AND WITH ALL FAULTS, and hereby disclaim all
    other warranties and conditions, whether
    express, implied or statutory, including, but
    not limited to, any (if any) implied
    warranties, duties or conditions of
    merchantability, of fitness for a particular
    purpose, of reliability or availability, of
    accuracy or completeness of responses, of
    results, of workmanlike effort, of lack of
    viruses, and of lack of negligence, all with
    regard to the SOFTWARE, and the provision of
    or failure to provide support or other
    services, information, software, and related
    content through the SOFTWARE or otherwise
    arising out of the use of the SOFTWARE. ALSO,
    THERE IS NO WARRANTY OR CONDITION OF TITLE,
    QUIET ENJOYMENT, QUIET POSSESSION,
    CORRESPONDENCE TO DESCRIPTION OR NON-
    INFRINGEMENT WITH REGARD TO THE SOFTWARE.
   
23. EXCLUSION OF INCIDENTAL, CONSEQUENTIAL
    AND CERTAIN OTHER DAMAGES. TO THE MAXIMUM
    EXTENT PERMITTED BY APPLICABLE LAW, IN NO
    EVENT SHALL MANUFACTURER OR ITS SUPPLIERS
    (INCLUDING MS, MICROSOFT CORPORATION,
    (INCLUDING ITS SUBSIDIARIES) AND THEIR
    RESPECTIVE SUPPLIERS) BE LIABLE FOR ANY
    SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT, OR
    CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING,
    BUT NOT LIMITED TO, DAMAGES FOR LOSS OF
    PROFITS OR CONFIDENTIAL OR OTHER INFORMATION,
    FOR BUSINESS INTERRUPTION, FOR PERSONAL
    INJURY, FOR LOSS OF PRIVACY, FOR FAILURE TO
    MEET ANY DUTY OF GOOD FAITH OR OF REASONABLE
    CARE, FOR NEGLIGENCE, AND FOR ANY OTHER
    PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING
    OUT OF OR IN ANY WAY RELATED TO THE USE OF OR
    INABILITY TO USE THE SOFTWARE, THE PROVISION
    OF OR FAILURE TO PROVIDE SUPPORT OR OTHER
    SERVICES, INFORMATION, SOFTWARE, AND RELATED
    CONTENT THROUGH THE SOFTWARE, OR OTHERWISE
    ARISING OUT OF THE USE OF THE SOFTWARE, OR
    OTHERWISE UNDER OR IN CONNECTION WITH ANY
    PROVISION OF THIS EULA, EVEN IN THE EVENT OF
    THE FAULT, TORT (INCLUDING NEGLIGENCE),
    MISREPRESENTATION, STRICT LIABILITY, BREACH
    OF CONTRACT OR BREACH OF WARRANTY OF
    MANUFACTURER OR ANY SUPPLIER (INCLUDING MS,
    MICROSOFT CORPORATION (INCLUDING ITS
    SUBSIDIARIES) AND THEIR RESPECTIVE SUPPLIERS),
    AND EVEN IF MANUFACTURER OR ANY SUPPLIER
    (INCLUDING MS, MICROSOFT CORPORATION
    (INCLUDING ITS SUBSIDIARIES) AND THEIR
    RESPECTIVE SUPPLIERS) HAS BEEN ADVISED OF THE
    POSSIBILITY OF SUCH DAMAGES.


I hope this comes over correctly --- I am forced onto this stupid microshaf= t stuff.  If not, I apologise, and is why I do not now write here much=   And I cannot use internal Outlook mail, I only have access from my = VMS (genuflection) box to the very frustrating Outlook Web Access.

In reply to Tad: -- since I never have and never will buy anything from mic= roshaft, I have never read Herr (a quick goose-step) Ballmer's licence.&nbs= p; Thanks for the enlightenment.

With this sort of licence agreement, why are large companies and government= s agreeing to such restrictions or exceptions?  Thankfully I have seen= reports that several governments are dishing this most "crapfull"= ; (not a word, I do know) OS.  O.K., the home user is probably not too= worried as he/she is not usually doing too much other than reading email, = playing solitaire and letting themselves become a zombie.  But compani= es and organisations ... ??

Yes, Bill, I know, but how many of them do tie down their (not "there&= quot; -- and I haven't used "you're", so not "your" -- = this is general, not specifically to you Mr. Gunshannon) systems?  I k= now of several organisations that do not.

Regards, Paddy

*******= ****************************************************************

Plea= se consider the environment before printing this email.

=

 <= /span>

"T= his electronic message and any attachments may contain privileged

and con= fidential information intended only for the use of the

address= ees named above. If you are not the intended recipient of

this em= ail, please delete the message and any attachment and advise

the sen= der. You are hereby notified that any use, dissemination,

distrib= ution, reproduction of this email is prohibited.

=

 <= /span>

If you = have received the email in error, please notify TransGrid

immedia= tely. Any views expressed in this email are those of the

individ= ual sender except where the sender expressly and with

authori= ty states them to be the views of TransGrid. TransGrid uses

virus-s= canning software but excludes any liability for viruses

contain= ed in any attachment."

=

 <= /span>

*******= ****************************************************************

 <= /span>

------_=_NextPart_001_01C8A452.9BB8AF7E-- ------------------------------ Date: 22 Apr 2008 08:50:24 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: Intel Itanium RAS Comparison with X86 Message-ID: In article <674l9gF2n0ghcU1@mid.individual.net>, billg999@cs.uofs.edu (Bill Gunshannon) writes: > > The group I am with now makes up somewhere in the area of 600 man years > of Army IT experience covering more than 30 calendar years of time and > pretty much every theater of operations and out of all of this, one man > has seen VMS in use by DA and that was years ago. If the cream of Army > IT never work with these VMS systems, just who do you think does? > I should be really honest, however. I, too, have seen VMS in use in DA. > Of course, that was at the Military Academy in the Computing Science > Department which is probably more academia than government and anyway, > that was over 20 years ago and has probably been gone for more than 18 > years. DoD != Army Take out your ego, pat it on the back, and put it away. Nobody in DoD knows everything, although I hope the Joint Chiefs have a good overview. ------------------------------ Date: 22 Apr 2008 08:55:56 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: Intel Itanium RAS Comparison with X86 Message-ID: In article <674nahF2me5j8U1@mid.individual.net>, billg999@cs.uofs.edu (Bill Gunshannon) writes: > Bob, this is just getting funnier all the time. "Need to know" > applies to classified information. Hey, I work on a governemnt contract. I can't tell you lots of things which aren't classified. I have passed training in UNIX system admin because it was either that or Windows system admin in order to be on record as a VMS and MacOS system admin. UNIX and Windows are the only two available for the required course. There are things which aren't classified which I can't tell you simply because you obviously don't have a need to know. There are things I can't say here because this is a public forum. Military secrets are not the only things our government controls. You have not convinced me that your position requires you to know everything about IT in DoD. ------------------------------ Date: 22 Apr 2008 13:07:03 GMT From: VAXman- @SendSpamHere.ORG Subject: RE: Intel Itanium RAS Comparison with X86 Message-ID: <480de2f7$0$11639$607ed4bc@cv.net> In article <0A7046B0A95F2B41B3712F0C5FD1CDC303BCD2@ex-tg2-pr.corporate.transgrid.local>, "O'Brien Paddy" writes: >{...snip...} >I hope this comes over correctly --- I am forced onto this stupid microshaf= >t stuff. If not, I apologise, and is why I do not now write here much. An= >d I cannot use internal Outlook mail, I only have access from my VMS (genuf= >lection) box to the very frustrating Outlook Web Access. Too bad too. I'd like to see you back here participating. >In reply to Tad: -- since I never have and never will buy anything from mic= >roshaft, I have never read Herr (a quick goose-step) Ballmer's licence. Th= >anks for the enlightenment. Nice to know that I'm not the only one in this battle against total world domination by SPECTRE^H^H^H^H^H^H^HMicro$hit. >With this sort of licence agreement, why are large companies and government= >s agreeing to such restrictions or exceptions? Thankfully I have seen repo= >rts that several governments are dishing this most "crapfull" (not a word, = >I do know) OS. O.K., the home user is probably not too worried as he/she i= >s not usually doing too much other than reading email, playing solitaire an= >d letting themselves become a zombie. But companies and organisations ... = >?? In the past 2 weeks I've made several PeeCees useful by installing Linux on them. One was one neighbor's dual CPU system with a motherboard that provided both IDE and SCSI. It was running Weendoze XP and was infected by a virus and the owner asked me if I wanted it. He was tossing it for a Mac because he'd had it with viruses! Last virus infected (destroyed) the BIOS firmware! I located a site that would reprogram any BIOS to a flash for a few bucks so that the box would recognize devices instead of just printing up the virus message. Save for a minor glitch in loading Ubuntu (due to the system being SCSI and, AFAICT, the x86 Ubuntu expects IDE), it loaded quite easily. It looks _much_ nicer than Weendoze too! I do not know why people continue to send their dollars, pounds, euros, krones, roubles, rupees, rands, yen, etc., off to that scumbag and his cult's compound in Redmond. I have also installed Ubuntu on an old d|i|g|i|t|a|l HiNote VP 700 I was given. It had Weendoze virus '98 on it and was a dog. I put Ubuntu on it as well after replacing the old 4GB drive with a 60GB drive. I had a few SIMMs laying about which fit so it also has 277MB now as well. This works remarkably well on this old 266MHz Pentium II. The only difficult part was making the sound card function. I finally fould the clue I was needing by reading some .INI file on the d|i|g|i|t|a|l restore CD that I found in the box with the HiNote. The control port address for the card is at 0x0ff0 if anyone is interested. I've also installed Linux (another Ubuntu distro) on a Compaq Evo N610c. A 2.4GHz Evo and it's very nice. The only problem with his unit is that its button battery cell holder is broken off the board. Thus, the unit complains about the clock when booted but once linux is running, I have it get the time from an NTP server. OpenOffice, Envision Mail, FireFox (FF 3 actually passes ACID2 as well), Opera, Pidgin Chat, numerous sound and video (I installed XMMS, Icecast2, Ices2, and numerous plugins easily too after the basic Ubuntu install), and I was even able to get an EVDO card functioning with this write up on Sprint's site: http://www4.sprint.com/pcsbusiness/downloads/Sprint_Mobile_Broadband_Setup_Guide.pdf and $ sudo lsusb to get the actual vendor and product IDs for the EVDO card I used. Thus, when it comes to Micro$hit and Weendoze... Just say, No! >Yes, Bill, I know, but how many of them do tie down their (not "there" -- a= >nd I haven't used "you're", so not "your" -- this is general, not specifica= >lly to you Mr. Gunshannon) systems? I know of several organisations that d= >o not. I hear the grammar police sirens wailing. :) -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Tue, 22 Apr 2008 10:36:27 -0400 From: John Reagan Subject: Re: Intel Itanium RAS Comparison with X86 Message-ID: Bill Gunshannon wrote: > A few years ago is right. Fielded in 1991, approved for production in 1996, > last system delivered in 2005. A total of 8 systems. > There is much more information about the airframe than anything else and > no mention of VMS at all. I wonder if it has been ported to Windows yet? > > A NG employee gave a keynote address at last year's OpenVMS Technical Bootcamp on JSTARS. The non-disclosure prevents me from giving details from the talk (which itself was very high level) plus I'd probably remember incorrectly anyway. -- John Reagan OpenVMS Pascal/Macro-32/COBOL Project Leader Hewlett-Packard Company ------------------------------ Date: Tue, 22 Apr 2008 11:33:43 -0400 From: "Paul" Subject: OpenVMS Encryption Message-ID: Hi, There have been some recent postings regarding Encryption for OpenVMS. I provide the following to set the facts straight. The former VAX Encryption for OpenVMS (single DES) was updated with the AES encryption algorithm, (Encrypt-AES V2.0) and introduced into (integrated with) the OpenVMS version V8.3 operating system. The standard NIST AES 16 byte block, 128, 192, or 256 bit keys with ECB and CBC block modes, and CFB and OFB byte stream modes are optionally avaliable, 128 bit AES CBC (/key_alg=AESCBC128 /data_alg=AESCBC128) is the default for AES, DES CBC if not specified. The encryption library utilized is from SSL (which is also shipped with OpenVMS). Although its single block I/O file encryption design hasn't been changed from the original design during the late 70's and early 80's was very slow. Since that time, we have improved Encrypt's I/O performance by a factor of 35 to 40x faster (using multiple buffer, aggregated writes, pre-allocation and larger read-ahead). This was part of Encrypt version V2.1 that was released with OpenVMS version V8.3-1H1 and later. We also made this latest version work with 2 terabyte file sizes, and fixed a few bugs. 1 GB File using V8.3 Image without Fix -------------------------------------- $ encrypt $80$DKB400:[TEST]Z. des /out=$80$DKB400:[TEST]z.enc $ exit SYSTEM job terminated at 4-APR-2007 18:02:18.42 Accounting information: Buffered I/O count: 25082 Peak working set size: 4304 Direct I/O count: 2225059 Peak virtual size: 176144 Page faults: 306 Mounted volumes: 0 Charged CPU time: 0 00:10:47.17 Elapsed time: 0 03:30:53.53 1 GB File with ENCRYPSHR Fix ---------------------------- $ encrypt $80$DKB400:[TEST]Z. des /out=$80$DKB400:[TEST]z.enc $ exit SYSTEM job terminated at 9-APR-2007 11:30:53.06 Accounting information: Buffered I/O count: 83 Peak working set size: 5600 Direct I/O count: 47432 Peak virtual size: 177776 Page faults: 387 Mounted volumes: 0 Charged CPU time: 0 00:05:30.26 Elapsed time: 0 00:05:42.28 I would say that's an improvement. Encryption for OpenVMS is backward compatible with DES encryption, so conversion from single DES (56 bit keys) to the stronger AES encryption is simple. Encryption (DES or AES) works with BACKUP, $ BACKUP/ENCRYPT, to encrypt save-sets of files or image save-sets. Encryption for OpenVMS also has file integrity checking with its MAC message authentication code qualifier and database. Encryption works with ODS-2 and ODS-5 volumes on Alpha and Integrity systems and has a set of API's to support those applications. We have not updated VAX Encryption. So that separately licensed product supports encryption with only DES encryption, also MAC and BACKUP/ENCRYPT (DES) support. Regards, Paul Mosteika, CISSP OpenVMS Engineering - Security ------------------------------ Date: Tue, 22 Apr 2008 06:22:10 -0700 (PDT) From: AEF Subject: Re: OT: IBM looking at Macintosh Message-ID: <231eda99-f328-475d-9e73-7f9cac8e832c@24g2000hsh.googlegroups.com> On Apr 21, 6:57 pm, billg...@cs.uofs.edu (Bill Gunshannon) wrote: > In article , > AEF writes: > > > On Apr 21, 12:50 am, JF Mezei wrote: > >> AEF wrote: > >> >> > AEF UPPERCASE AND PROUD OF IT! > > >> Warning: see a doctor immediatly if you stay in uppercase for more than > >> 4 hours at a time. > > > AEF UPPERCASE AND PROUD OF IT! > > Repeating yourself like that is a bad sign!!! > > bill > > -- > Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves > billg...@cs.scranton.edu | and a sheep voting on what's for dinner. > University of Scranton | > Scranton, Pennsylvania | #include I can downshift when needed. :-) AEF UPPERCASE AND PROUD OF IT ------------------------------ Date: Tue, 22 Apr 2008 06:24:07 -0700 (PDT) From: AEF Subject: Re: OT: IBM looking at Macintosh Message-ID: <0f91c846-633b-4b5e-b47d-e04887d657b5@e67g2000hsa.googlegroups.com> On Apr 21, 12:50 am, JF Mezei wrote: > AEF wrote: > >> > AEF UPPERCASE AND PROUD OF IT! > > Warning: see a doctor immediatly if you stay in uppercase for more than > 4 hours at a time. JF, What's the matter? Are you having trouble SHIFTing into uppercase? Speaking of which, 4 hours is a problem, but 3 hours is okay? This reminds me of a Saturday Night Live parody: If you are stuck in uppercase for more than 24 hours, get on the phone (or something) and brag about it! Hey, I can downshift when needed. :-) AEF UPPERCASE AND PROUD OF IT! ------------------------------ End of INFO-VAX 2008.225 ************************