1 INFO-VAX	Sun, 15 Dec 2002	Volume 2002 : Issue 692       Contents:) Re: Bookreader, .PS and Acrobat Distiller ! DECwindows/Motif sessions over IP % Re: DECwindows/Motif sessions over IP % Re: DECwindows/Motif sessions over IP  Re: Help with Datatrieve. % Re: How do you invalidate a dumpfile. % Re: How do you invalidate a dumpfile. % Re: How do you invalidate a dumpfile. % Re: How do you invalidate a dumpfile. G Re: Migration minute of the day:  Pascal VAX/VMS 5.5-2H4 to OpenVMS 8.2 G Re: Migration minute of the day:  Pascal VAX/VMS 5.5-2H4 to OpenVMS 8.2 1 Re: misc HW maintenance end of life dates, where? 3 Oracle Rdb V7.1.0.4 and V7.1.0.5 have been released @ PSECT GBL,OVR 1 User shareable 1 Exec UWSS - Alpha OK, VAX fails$ Re: tcp/ip services sys$qio problems Test( Re: VMS still a bastard child under DPSS@ Your Multi-volume Tape Backups may be bad on all versions of VMSD Re: Your Multi-volume Tape Backups may be bad on all versions of VMS  F ----------------------------------------------------------------------  % Date: Sun, 15 Dec 2002 11:30:23 -0600 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> 2 Subject: Re: Bookreader, .PS and Acrobat Distiller' Message-ID: <3DFCBC2F.7B47DD81@fsi.net>    Larry Kilgallen wrote: > ] > In article <3DFC0998.EBA7E5F2@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes: L > > I'm wondering if anyone has successfully used DECW$BOOKREADER to produceE > > .PS output can then convert that to .PDF using Acrobat distiller.  > E > This is trivial with the .sdml source files, but I think it is nigh  > onto impossible without. > L > > I'll need to put up a product soon where the doc is Bookreader only, butL > > the ODL (beta) Bookereader for WhineBloze won't print, and the .PS I getH > > from Bookreader comes out kind scrambled when read back with AcrobatI > > Reader - several pages overlayed on one page every five or six pages,  > > starting with the first. > 9 > Is there any chance of influencing the product vendor ?   H The vendor is, of course, DEC/Q/HP who, as evidenced by multiple threads! here, are not easily influenced.    F The product is DCSC. If anyone in the associated group is reading thisG forum, could you please influence someone to make the source text files D available (.SDML, or whatever) so these can be converted to a formatG that can be used by a ubiquitous reader where the print option actually ( works - like Acrobat Reader and its ilk?   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Sun, 15 Dec 2002 16:44:59 +0100 " From: "Hans Vlems" <hvlems@iae.nl>* Subject: DECwindows/Motif sessions over IP6 Message-ID: <ati82h$13nbrr$1@ID-143435.news.dfncis.de>  E My VAX systems have always used DECnet as the preferred transport for H DECterm sessions. Yesterday I tried to establish an xterm session from aH RedHat Linux 7.2 host. The command that worked towards a W2k box running+ Reflection: xterm -display 192.168.44.7:0.0 F I tried that same command, directed at a VMS host. The command failed,G "unable to create session". Assuming this was a linux problem I tried a  VAX-to-VAX session over IP:   6 $ set display/create/transport=tcpip/node=192.168.44.6
 $ sho disp"       Device:     WSA10:   [super]       Node:       192.168.44.6       Transport:  TCPIP        Server:       0        Screen:       0  $ mc decw$clock # X Toolkit Error: Can't Open display % %DWT-F-NOMSG, Message number 03Ab8204 0 $ set display/create/transport=decnet/node=argon $ mc decw$clock   " .. which shows the familiar clock.    What did I forget to configure ?   Hans   ------------------------------  # Date: Sun, 15 Dec 2002 16:05:33 GMT " From:   VAXman-  @SendSpamHere.ORG. Subject: Re: DECwindows/Motif sessions over IP0 Message-ID: <00A187B2.5AC471FF@SendSpamHere.ORG>  [ In article <ati82h$13nbrr$1@ID-143435.news.dfncis.de>, "Hans Vlems" <hvlems@iae.nl> writes: F >My VAX systems have always used DECnet as the preferred transport forI >DECterm sessions. Yesterday I tried to establish an xterm session from a I >RedHat Linux 7.2 host. The command that worked towards a W2k box running , >Reflection: xterm -display 192.168.44.7:0.0G >I tried that same command, directed at a VMS host. The command failed, H >"unable to create session". Assuming this was a linux problem I tried a >VAX-to-VAX session over IP: > 7 >$ set display/create/transport=tcpip/node=192.168.44.6  >$ sho disp # >      Device:     WSA10:   [super]  >      Node:       192.168.44.6  >      Transport:  TCPIP >      Server:       0 >      Screen:       0 >$ mc decw$clock$ >X Toolkit Error: Can't Open display& >%DWT-F-NOMSG, Message number 03Ab82041 >$ set display/create/transport=decnet/node=argon  >$ mc decw$clock > $ >... which shows the familiar clock. > ! >What did I forget to configure ?  >  >Hans  >   	 Security!    --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------  % Date: Sun, 15 Dec 2002 18:39:04 +0100 " From: "Hans Vlems" <hvlems@iae.nl>. Subject: Re: DECwindows/Motif sessions over IP6 Message-ID: <atieo4$1468dg$1@ID-143435.news.dfncis.de>   > > # > >What did I forget to configure ?  > >  > >Hans  > >  >  > Security!  >  > --9 The session manager on the target VAX was set as follows:    protocol    node    username DECnet      *             *  TCPIP        *             * LAT            *             *   Hans   ------------------------------  % Date: Sun, 15 Dec 2002 10:29:05 -0500 / From: "Joe H. Gallagher" <dtrwiz@ix.netcom.com> " Subject: Re: Help with Datatrieve.- Message-ID: <3DFC9FBC.BEA3FE75@ix.netcom.com>    Rohit Prasad wrote:  > N > I have written a datatrieve procedure that creates a report for the clients.G > I am thinking of calling this Datatrieve procedure from a DCL command 3 > procedure. Can somebody please help me with this.  > H > My guess is that when I create a Datatrieve procedure a .DTR file getsK > created at someplace. We then have to assign this .DTR file with its full & > path to the logical name DTR$STARTUP >  > Thanks >  > Rohit Prasad >   C You didn't mention what version of DATATRIEVE you are using, but ..   C If DTR will invoke DATATRIEVE at DCL, and if your procedure name is  YOUR-PROCEDURE, then try   	$ dtr execute YOUR-PROCEDURE   D You can muck around with logical names if you want to, but it should not be necessary.    Joe H. Gallagher, Ph. D.$ Former SIG Chair & Newsletter Editor DATATRIEVE/4GL SIG of DECUS  dtrwiz at ix dot netcom dot com " See "The DATATRIEVE Programmer" at http://dtrwiz.home.netcom.com/   ------------------------------  # Date: Sun, 15 Dec 2002 12:55:05 GMT , From: matt@drumheights.removethis.com (Matt). Subject: Re: How do you invalidate a dumpfile.0 Message-ID: <3dfc7b3c.77292911@news.demon.co.uk>  B On Sat, 14 Dec 2002 15:44:51 -0500, Mike Duffy <Duffy@process.com> wrote:   >> -----Original Message----- ( >> From: matt@drumheights.removethis.com+ >> [mailto:matt@drumheights.removethis.com] - >> Sent: Saturday, December 14, 2002 11:24 AM  >> To: Info-VAX@Mvb.Saic.Com- >> Subject: How do you invalidate a dumpfile.  >>   >>   >> Hi, >>  H >> Is there any way to invaidate a dump file, so that VMS thinks it does >> not contain a vaild dump? >>   >> Many thanks in advance. >>   >> 	Matt >>   > = >I assume rebooting the system is not an option in this case,  >because that'll do it. E I don't want to reintruduce the node to the cluster until I know what  caused the crash.  > C >Someone else might have a elegant, simple answer, but I'll provide ; >an ugly, brute-force one.  You might get your hands on the ? >instructions for re-validating an invalidated dump, and deduce = >what locations should be given what values to invalidate it. F I haven't been able to find these instructions, but have found info onF the byte & values that mean invalid/valid analyzed/valid not analyzed. > : >You can use PATCH (assuming that's possible in this case): >to modify the file, just as if you were re-validating it.9 >The particulars depend on architecture, VMS version, and ! >in some cases, dump flags, IIRC. F Sounds promising, I am unfamiliar with PATCH, is it possible to run itE on AXP V7.3? (I was under the [misguided?] impression that it was VAX ! only).  If so how do I use it....    Matt   ------------------------------  % Date: Sun, 15 Dec 2002 14:47:53 +0100 1 From: John McLean <mcleanj@swissonline.delete.ch> . Subject: Re: How do you invalidate a dumpfile.5 Message-ID: <3DFC8809.92C8D57D@swissonline.delete.ch>    Mike Duffy wrote:  >  > > -----Original Message-----) > > From: matt@drumheights.removethis.com , > > [mailto:matt@drumheights.removethis.com]. > > Sent: Saturday, December 14, 2002 11:24 AM > > To: Info-VAX@Mvb.Saic.Com . > > Subject: How do you invalidate a dumpfile. > >  > >  > > Hi,  > > I > > Is there any way to invaidate a dump file, so that VMS thinks it does  > > not contain a vaild dump?  > >  > > Many thanks in advance.  > >  > >       Matt > >  > > > I assume rebooting the system is not an option in this case, > because that'll do it.    C It won't do it if you keep the same filename.  The system will just E reboot and as it does so, record the FID of the dumpfile.  This means D that you can't even rename it on an active system because the systemC already knows where to find it.  You can however rename it and then ( reboot the system pretty soon aferwards.  H Matt, why do you want to invalidate the dump file ?  What do you want to7 gain ?  What are the contraints on how it can be done ?   G Answers to these might help someone here to identify the best way to do 7 it, or perhaps we can give you an alternative solution.      cheers     John McLean    ------------------------------  % Date: Sun, 15 Dec 2002 16:19:56 +0100 1 From: John McLean <mcleanj@swissonline.delete.ch> . Subject: Re: How do you invalidate a dumpfile.5 Message-ID: <3DFC9D9C.29B02AE6@swissonline.delete.ch>    Matt wrote:  > D > On Sat, 14 Dec 2002 15:44:51 -0500, Mike Duffy <Duffy@process.com> > wrote: >  > >> -----Original Message----- * > >> From: matt@drumheights.removethis.com- > >> [mailto:matt@drumheights.removethis.com] / > >> Sent: Saturday, December 14, 2002 11:24 AM  > >> To: Info-VAX@Mvb.Saic.Com/ > >> Subject: How do you invalidate a dumpfile.  > >> > >> > >> Hi, > >>J > >> Is there any way to invaidate a dump file, so that VMS thinks it does > >> not contain a vaild dump? > >> > >> Many thanks in advance. > >> > >>      Matt > >> > > ? > >I assume rebooting the system is not an option in this case,  > >because that'll do it. G > I don't want to reintruduce the node to the cluster until I know what  > caused the crash.   H You should copy the contents of the dump file to another file an perform! any analysis on that second file.   F The commands are easy but I forget exactly what they are.  The doc setG should be able to tell you how to do it, perhaps in the section talking E about a common dump file for cluster nodes.  (I can't remember if you D need a normal DCL COPY or whether within SDA there is a Copy command that you should use.)   E Doing things this way means you don't have to worry about renames and  thing like that.     John   ------------------------------  % Date: Sun, 15 Dec 2002 11:24:10 -0600 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> . Subject: Re: How do you invalidate a dumpfile.' Message-ID: <3DFCBABA.B31B29AF@fsi.net>    Mike Duffy wrote:  >  > > -----Original Message-----) > > From: matt@drumheights.removethis.com , > > [mailto:matt@drumheights.removethis.com]. > > Sent: Saturday, December 14, 2002 11:24 AM > > To: Info-VAX@Mvb.Saic.Com . > > Subject: How do you invalidate a dumpfile. > >  > >  > > Hi,  > > I > > Is there any way to invaidate a dump file, so that VMS thinks it does  > > not contain a vaild dump?  > >  > > Many thanks in advance.  > >  > >       Matt > >  > > > I assume rebooting the system is not an option in this case, > because that'll do it.  F To clarify, I belive that occurs during the shutdown sequence. Whether< you choose to boot after that is, of course, another matter.   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Sun, 15 Dec 2002 11:11:44 +0100 $ From: Michael Unger <unger@decus.de>P Subject: Re: Migration minute of the day:  Pascal VAX/VMS 5.5-2H4 to OpenVMS 8.2* Message-ID: <00A187B3.377517A0.5@decus.de>  7 "Didier Morandi" <Didier.Morandi.nospam@Free.fr> wrote:    > [...]  > E > Frankly speaking, when you hear press news in France about VMS only H > thanks to John The Ripper, you may wonder what you should do with yourH > VMS systems, right? (I'm note sure my translation is understandable. I. > mean HP France does not communicate on VMS).   That's not only HP France ...    Michael    ------------------------------  # Date: Sun, 15 Dec 2002 10:19:55 GMT 0 From: HARANGOZO CSABA   <spameater@spam.invalid>P Subject: Re: Migration minute of the day:  Pascal VAX/VMS 5.5-2H4 to OpenVMS 8.24 Message-ID: <fHYK9.133$N5.6430@nasal.pacific.net.au>  5 Didier Morandi <Didier.Morandi.nospam@free.fr> wrote:  > The question is:  Q > Is it obvious to consider recompiling/linking in two years or so a few million  Q > lines of Pascal VAX/VMS 5.5-2H4 on an Itanium Server running OpenVMS 8.2? (the  - > Pascal compiler is in the roadmap for 8.2).   I > Or is it safer to consider upgrading the VAX from 5.5-2H4 to 8.2 first?   C 	It seems your customer stays on VMS V5.5-2H4 ( a hardware release, ? 	if I'm correct ) for some very good reason, else they would've @ 	upgraded to a more recent version of VMS. So please make *VERY*E 	sure that the future V8.2 version *WILL* support that configuration.   @ 	As for recompiling/relinking that many lines, it will take time/ 	( and money, etc. ), and don't forget testing.   F 	It is not an easy decision, in my opinion they should start exploring? 	the option of getting a fairly current Alpha, with current VMS 8 	version, and start some work of porting all those code.   	Just my 2 cents...  						Cheers,  Csaba  J  -------------------------------------------------------------------------H   CSABA I. HARANGOZO  |d|i|g|i|t|a|l|  csabah(at)zipworld(dot)com(dot)auJ  -------------------------------------------------------------------------;    EARTH::AUSTRALIA:[SYDNEY]HARANGOZO.CSABA;1, delete? [N]:    ------------------------------  % Date: Sun, 15 Dec 2002 09:25:05 +0100 4 From: Didier Morandi <Didier.Morandi.nospam@Free.fr>: Subject: Re: misc HW maintenance end of life dates, where?$ Message-ID: <3DFC3C61.40401@Free.fr>  ! Michael Unger (and others) wrote:  >>FE?  >  >  > Field Engineer ? >  > Just a guess of course ...   Unknown.8 I know of Field Service Engineer, but they deal with HW.   D.   ------------------------------  % Date: Sat, 14 Dec 2002 10:27:13 -0500 2 From: norm lastovica <norman.lastovica@oracle.com>< Subject: Oracle Rdb V7.1.0.4 and V7.1.0.5 have been released) Message-ID: <3DFB4DD1.8030009@oracle.com>   I      Oracle is pleased to announce the release of Oracle Rdb V7.1.0.4 and K      Oracle Rdb V7.1.0.5 (aka V7.1-04 and V7.1-05).  The kits are available       on Metalink.   F          Software Errors Fixed in Oracle Rdb Release 7.1.0.4 & 7.1.0.5F          -------------------------------------------------------------  ;          Software Errors Fixed That Apply to All Interfaces F            - Deadlocks From SET TRANSACTION RESERVING When Fast Commit              Enabled:            - Bugcheck at RDMS$$ALPHA$CONVERT_SORT+00000778C            - RDMS$CREATE_LAREA_NOLOGGING Partly Ignored for Objects               with Row Caches2            - Exception in RDMS$$KOD_ISCAN_GET_NEXTA            - Records Incorrectly Applied to a Key Entry in Sorted               Ranked Index C            - LRS Uses Too Much CPU in 7.1.0.1, 7.1.0.2, and 7.1.0.3 E            - Persona Nopriv Error Using SQLplus and Other OCI Clients E            - Query With OR and Repeated AND Predicates Looped Forever G            - %SYSTEM-F-ILLEGAL_SHADOW, Illegal Formed Trap Shadow Error <            - AIJBL_START_FLG Not Always Set Correctly in AIJH            - Left Outer Join Query With UNION Legs Returns Wrong ResultsF            - Query With EXISTS Clause Using Hashed Index Returns Wrong              ResultsD            - Performance of Self-Referencing Foreign Key ConstraintsB            - Online Change of Storage Area Access Mode Now Allowed+            - RCS Exits with COSI-F-SUBLOCKS H            - TRUNCATE TABLE Results in RMU-E-BADABMPAG & RMU-W-ABMBITERR%              Messages from RMU/VERIFY >            - Execution Trace For Dynamic Estimation Inaccurate<            - Dynamic Optimizer Index Estimation May Be WrongG            - DBR Does Not Write Valid TSN for Commit of 2PC Transaction G            - Various Problems With Dynamic Estimation of Ranked Indices :            - Count Scan Optimization Returns Wrong Results=            - Insert Statement Fails With Constraint Violation D            - Followup on Bug 2529598 From Oracle Rdb Release 7.0.6.5C            - Ranked Index Node Corruption After Insert of Duplicate               Record B            - Unexpected Bugcheck When Using RDMS$SET_FLAGS LogicalD            - NOT NULL Test in OJ Query With UNION Legs Returns Wrong              Results,            - Bugchecks at PSII2SCANRESETSCANE            - Stack Overflow Exception Replaced by %RDMS-E-NOSOL_FOUND               Signal E            - Another OR With Constant Predicate Returns Wrong Results E            - Ranked Index Node Corruption After Deletion of Duplicate               Record           SQL Errors Fixed ?            - Incorrect Handling of FOR Loop Select List Columns D            - Unexpected Error on FOR Loop With Dialect ORACLE LEVEL1F            - Unexpected Truncation of Data Assigned in Precompiled SQL3            - CREATE SEQUENCE Not Defaulting to WAIT %            - Input Line Limit Too Low 0            - CASE Expression Causes SQL Bugcheck*              @SQL$$BLR_MSG_FIELD_REF + 1E8A            - %SQL-F-INVFUNREF on Subquery of SELECT with GROUP BY 9            - Bugcheck on DDL Command With a Host Variable :            - VALUE Keyword Not Recognized in DDL Statement4            - ALTER TABLE May Result in a Bugcheck at#              RDMS$$COMPILE_RTN_EXPR <            - DROP VIEW Corrupts Base Table AUTOMATIC Columns4            - RDB-E-BAD_REQ_HANDLE in Stored Function<            - Unexpected SEQNONEXT Error When Using SequencesD            - Sequence Does Not Increase When Used in SELECT ... INTO>            - AUTOMATIC Columns Can Now Reference Other Columns@            - SET NO EXECUTE Permits More SHOW and SET StatementsC            - CAST Function Enhanced for Single Field INTERVAL Types >            - Unexpected INVALID_BLR Error During CREATE MODULE?            - Unexpected DEFVALINC Error When Using ALTER DOMAIN K            - Unexpected UNRES_REL Error When DEFAULT Value References Table E            - Restricted Range Index Not Detecting Out-of-Range Values J            - Unexpected NODBKDRVTBL Error When Fetching DBKEY From a Table0            - Function Reference Causes Exception/            - SQL Precompiler Bugchecks on ALTER C            - Bugcheck at RDMS$$COMPILE_FOR_IF for Aggregate Queries D            - Unexpected INVALID_BLR When Using Variable CHECK ClauseH            - Unexpected OBSOLETE_METADA When Accessing Older Rdb VersionC            - IMPORT Did Not Create Objects with Function References >            - Unexpected Table References From FOR Cursor Query:            - Additional Warnings Generated for ALTER INDEXF            - ALTER INDEX Would Report Unexpected OBSOLETE_METADA Error@            - SELECT DISTINCT Returns Incorrect Value for NEXTVAL>            - Unexpected Trailing Character in SMALLINT DisplayA            - DEFAULT Value With Subselect Not Evaluated Correctly ;            - DROP SEQUENCE Bugchecks in Routine AIJ$JOURNAL 3            - DECLARE TRANSACTION Causes Memory Leak =            - Restrictions Lifted for DROP and ALTER TABLE for               Temporary Tables C            - Object Dependencies Not Tracked for Domains or Complex               DEFAULT Clauses0            - SET LINE LENGTH Changed Upper Limit?            - DROP SEQUENCE Not Synchronized With Other Sessions =            - Compiled Applications May Fail With SQLCODE -304 "          RDO and RDML Errors FixedD            - RDO SHOW FIELD Would Bugcheck on SQL Created Definition=            - RDML/PASCAL Shareable Link/DEBUG SHRSYMFND Error            Oracle RMU Errors Fixed2            - RMU/CONVERT Writes Incorrect MetadataG            - RMU/BACKUP to Tape Can Hang on a Quit Response to a Prompt I            - RMU/BACKUP to Tape Can Hang When Terminating on Fatal Errors 9            - Unexpected COSI-F-TRU Error From RMU/EXTRACT L            - RMU/LOAD Returned Error When Interchange File Contained No RowsM            - RMU/RECOVER Exit Status Does Not Indicate That a Recovery Failed =            - New Multithreaded Backup to Disk, Size Algorithm L            - Bugcheck at AIJUTL$FORMAT_ARBS When Performing RMU/BACKUP/AFTERL            - Thread Assignment and Storage Area Statistics Messages Were Not,          Being Displayed With RMU/BACKUP/LOG=            - Cannot Resolve 2PC Transaction After RMU/RECOVER D            - RMU/RESTORE /CDD Failed to Integrate Root File into CDD:            - RMU/BACKUP Verifies Area File Belongs to Root9            - RMU Extract Not Processing DEFAULT Correctly ;            - Unexpected BLRINV Error When Using RMU/EXTRACT 4            - RMU/BACKUP/AFTER/NOQUIET Could BugcheckG            - RMU/RECOVER/AREA Increments the Active AIJ Sequence Number 4            - RMU/LOAD/FIELDS With Empty Options File9            - BTRLEACAR Warning Raised by RMU/VERIFY/INDEX ?            - RMU UNLOAD Incorrectly Using DBKEY SCOPE IS ATTACH ;            - RMU Extract of Trigger Fails With BLRINV Error H            - RMU Extract Could Generate a Bugcheck When Extracting Views          LogMiner Errors FixedH            - RMU/UNLOAD AFTER_JOURNAL AIJ Backup and Restart Information?              STATISTICS Modified to Display Transaction Summary G            - RMU Show Statistics Does Not Update Counters With /Time=-n 7            - Commit Queue Algorithms are no Longer Used F            - RMU Show Statistics/Cluster Not Generating OPCOM Messages              Consistently 4            - Stall Message Descriptions InconsistentH            - Ability to Invoke a Procedure From RMU/SHOW STATISTICS When*              a Stall Exceeds ALARM SecondsC            - RMU SHOW STATISTICS Device Information Screen Enhanced !          Hot Standby Errors Fixed ;            - LRS Bugchecks at KUTREC$DO_C_AIJBUF + 00001128   2          Enhancements that Apply to all Interfaces<            - RMU /UNLOAD /AFTER_JOURNAL Wildcard Table Names(            - Enhancements to RMU Extract.            - RMU /SET ROW_CACHE /ALTER CommandD            - New Keyword SCREEN_NAME for RMU/SHOW STATISTICS/OPTIONS5            - New RMU /SET SHARED_MEMORY /TYPE Command B            - Zoom Option for "Process Analysis" Screen in RMU/SHOW              STATISTICS J            - Statistics Collection Performance Improvement for AlphaServer              GS Systems ?            - New PRAGMA Clause Added to SQL Compound Statements *            - New DECLARE Routine Statement6            - New AUTO_INDEX Option Added for SET FLAGS  O      Oracle Rdb V7.1.0.5 Optimized for Alpha EV56 Processor and Later Platforms   ;        For improved performance on current generation Alpha <        processors, Oracle Rdb Release 7.1.0.5 (also known as=        V7.1-05) is compiled explicitly for the Alpha EV56 and ;        later systems. This version of Oracle Rdb requires a =        system with a minimum Alpha processor chip of EV56 and ;        a maximum processor chip of Alpha EV68 (known as the         Alpha 21264B) family.  8        Oracle Rdb V7.1.0.5 is functionally equivalent to5        Oracle Rdb release 7.1.0.4. It shares the same 7        source code, uses the same data structures, call ;        interfaces, and so on as Oracle Rdb Release 7.1.0.4. 8        The difference is a potentially improved level of=        performance due to Release 7.1.0.5 being compiled with /        optimizations for newer alpha processors   :        Oracle Rdb V7.1.0.5 is explicitly compiled for EV569        and later Alpha processors such that the generated =        instruction stream can utilize the byte/word extension ;        (BWX) of the Alpha architecture first available with 7        the Alpha EV56 (21164A) processor. Additionally, :        this kit is compiled with instruction tuning biased:        for performance of Alpha EV6 and later systems that1        support quad-issue instruction scheduling.   :        Note, that you should not attempt to install or run7        this version of Oracle Rdb on Alpha EV4, EV45 or 8        EV5 systems. These processor types do not support:        the required byte/word extension (BWX) of the Alpha=        architecture. An install-time check that verifies that =        the installation node is using an Alpha EV56 processor 8        or higher. Attempts to install on Alpha EV4, EV459        or EV5 systems results in a fatal error during the :        installation procedure. You should also ensure that<        systems in a cluster sharing the system disk are also0        using the Alpha EV56 or higher processor.   ------------------------------  + Date: Sun, 15 Dec 2002 13:04:38 +0000 (UTC) , From: "Richard Maher" <maher_rj@hotmail.c0m>I Subject: PSECT GBL,OVR 1 User shareable 1 Exec UWSS - Alpha OK, VAX fails 1 Message-ID: <athul5$s6q$1@knossos.btinternet.com>    Hi,   K There's a good chance that I'm doing something wrong here but as it appears J to work perfectly well on Alpha yet fails on VAX I was hoping that someoneJ maybe able to shed light on the subject. For the most part, I subscribe toK what Stephen Hoffman and others have had to say about these COMMON areas of = memory but if we can leave that to one side for a moment. . .   I I have a stock standard user mode shareable image (Written in COBOL as it D happens) that overlays an EXTERNAL PSECT with an EXECutive mode UWSSF shareable image. The attributes have been set to NOSHR but are GBL andL WRTable. The theory/design is that when the User/application image (that wasK linked against my w:re RTL) is activated, my lib$initialize code (just gets K better doesn't it :-) will call the EXEC mode initialization routine to set I up the contents of the EXTERNAL Psect. Subsequent user mode USER mode RTL E calls will be able to take full advantage of access to this privilege L initialized memory safe in the knowledge that it is protected from USER mode corruption.   G As I said previously, on Alpha everything is just peachy but on VAX I'm L getting everything from ACCVIO when the image tries to initialize to "OPCODEF reserved to DEC" and "Reserved addressing mode" when the code tries toK access the PSECT. The code appears to behave a little more predictably when    PROTECT=NO,   COLLECT=T3$$SAFE,T3$TIP_URL_DATA  , but that's sort of defeating the purpose :-(  L Obviously there's a fair bit of change in the build procedure for this stuffI between VAX and ALPHA so plently of room for something to get lost in the L translation, but if someone could just confirm that this is supposed to work0 on VAX (or not) then that would be a great help!   Cheers Richard.   G PS. I appreciate the risk of evasion of my lib$initialize code (but the L psect will at least be in my compile time state) but if you know of a way toH specify an EXEC MODE initialization routine for UWSSs then please let me6 know. My PLV documentation doesn't seem to declare it.   ------------------------------  # Date: Sun, 15 Dec 2002 08:36:34 GMT * From: Edward Brocklesby <ejb@lythe.org.uk>- Subject: Re: tcp/ip services sys$qio problems 9 Message-ID: <slrnavofoi.4lh.ejb@deliverance.lythe.org.uk>   : In article <3DFC1D93.CB71AD3A@eps.zk.dec.com>, Hein wrote:/ >  Didn't you simply accidently doubly declare:   ? Ugh -- now I feel stupid.  I was looking too closely for errors ; in the VMS specific code that I missed something so simple.   > Now I have SS$_NOPRIV (hey, it's not even listed as a possibleA error), but I'm sure I'll find that's caused by something equally  stupid.   
 Thanks a lot.    Regards, Edward.    ------------------------------  % Date: Sun, 15 Dec 2002 17:14:21 +0300 ! From: Dron Link <dl@CyberPunk.ru> 
 Subject: Test 0 Message-ID: <ati2nt$2fo0$1@alpha2.radio-msu.net>   Test   ------------------------------  # Date: Sun, 15 Dec 2002 14:43:11 GMT ( From: "Jay E. Morris" <jem@epsilon3.com>1 Subject: Re: VMS still a bastard child under DPSS < Message-ID: <3y0L9.209582$Kj1.6635862@twister.austin.rr.com>  8 In message <3DF968D0.C6B45054@vl.videotron.ca>, JF Mezei( <jfmezei.spamnot@vl.videotron.ca> wrote: > Larry Kilgallen wrote:F > > It is in the interest of web "designers" to make things as complexF > > as possible to justify the need for web "designers".  This has not: > > a whole lot to do with actually conveying information. > M > Are these overly complex web pages the result of weenies wanting to impress K > their bosses with all sorts of fancy features that work well on their 25" I > monitor and 2ghz windows with a particular version, or could it be that  someL > "graphic artist" is just using some automated web design software that hasM > pre-packaged routines to do those fancy tricks instead of using simple HTML  to > achieve the same ?   Yes. --  
 Jay E. Morris @ Posted with Ink Spot (for Windows CE) from DejaVu Software, Inc.8 Usenet wherever you are - http://www.dejavusoftware.com/   ------------------------------  # Date: Sun, 15 Dec 2002 15:03:55 GMT + From: Jeff Cameron <JCam90502@jcameron.com> I Subject: Your Multi-volume Tape Backups may be bad on all versions of VMS 2 Message-ID: <BA21D9DA.2470%JCam90502@jcameron.com>  L Attention : Your Multi-volume Tape Backups may be bad on all versions of VMS through VMS 7.3-1.   OVERVIEW  K A serious bug in Compaq/HPs BACKUP utility which causes backup savesets on L multiple tape volumes to be improperly written causing restore operations to fail with one of two errors :   J %BACKUP-W-NOT1STVOL, <tape-device>:[000000]*.*; is not the start of a save set  or  J %BACKUP-I-WRONGVOL, <tape-device>:[000000].; is not the next volume in the set      PROBLEM DESCRIPTION     F The VMS BACKUP image improperly writes/rewrites/initializes the volumeG headers for multi-volume backups when a saveset spans to any other tape L volume after the first volume, only when the Native OpenVMS Media ManagementL Environment (MME) is enabled. MME is used by Compaq/HP, and sometimes, otherI third party tape management products, to handle multi-volume ANSI labeled  tapes.    G MME is enabled by various layered products that involve writing of ANSI G formatted tape volumes. Layered products that support multi-volume tape ) replication are examples of users of MME.   J If MME is not enabled on your system, you will not experience the problem,I and your backups are secure. If MME is active by any VMS layered or other H third party product, then you will not be able to restore, from savesetsF which span tape volumes, those files that are written after the volume transition.    PROBLEM DETERMINATION     G This problem affects all versions of VMS BACKUP from 7.3-1 and earlier. K Also, depending on firmware of various types and models of DLT tape drives, L this problem may or may not occur. No research by Compaq/HP has been done toL determine which tape drives are or are not effected. If you use some sort ofG layered product for performing backups, tape replication, or tape media J management, you must contact the manufacturer of the software to determineG if the product uses the native OpenVMS MME environment. If you just use C native VMS backup commands to do your backups, you have no problem.   G Known third party software products that use MME are Software Partners' E TapeSys, and MTI's TAPEControl. Some of Compaq/HP's integrated backup I solutions also use MME. Contact the support for your software product for  absolute determination.      IMMEDIATE WORKAROUND    J MME is enabled and disabled by calls to the MME system routines and can beK turned on and off by whatever utility is using it. In some cases a softwareiL product that uses MME only enables it as it is needed. In other cases it mayH be enabled at system boot and remains enabled until system shutdown. YouI must determine which is the case for your site, and if possible make sure ; MME is disabled while generating multi-volume tape backups.S    	 SOLUTION n    K Compaq/HP has identified the problem and will have a patch/update available K soon. The Compaq/HP patch website for VMS can be found at the following web 
 address :   * http://ftp1.support.compaq.com/public/vms/  I At this time (December 15, 2002) Compaq/HP has not yet released the patch J for this problem for any versions of VMS. If you would like to be notifiedK when this patch is available, please send an email to MMEPatch@jcameron.com G with the subject line "MME/BACKUP multi-volume patch notification". The-I sender of the email will be automatically notified when the patch becomesvI available. As soon as it is available from Compaq/HP, you will be sent anA+ eMail on how and where to obtain the patch.D  H Compaq/HP highly recommends that all BACKUP users apply the patch/update< mentioned above, when available, even if you do not use MME.  B Questions about this problem may be sent to JCam90502@jcameron.com   Jeff Cameron www.jcameron.com/vms/    ------------------------------    Date: 15 Dec 2002 08:57:06 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) M Subject: Re: Your Multi-volume Tape Backups may be bad on all versions of VMSd3 Message-ID: <bIEWtBBoQv3D@eisner.encompasserve.org>e  ` In article <BA21D9DA.2470%JCam90502@jcameron.com>, Jeff Cameron <JCam90502@jcameron.com> writes:N > Attention : Your Multi-volume Tape Backups may be bad on all versions of VMS > through VMS 7.3-1. > 
 > OVERVIEW > M > A serious bug in Compaq/HPs BACKUP utility which causes backup savesets on N > multiple tape volumes to be improperly written causing restore operations to > fail with one of two errors :r >  L > %BACKUP-W-NOT1STVOL, <tape-device>:[000000]*.*; is not the start of a save > set  > or  L > %BACKUP-I-WRONGVOL, <tape-device>:[000000].; is not the next volume in the > set   . Even when the backup was create with /VERIFY ?   	As everybody should do.  2 Presumably not when it was followed with /COMPARE.  < 	As the more paranoid will do, using a different tape drive.  F Although years ago on another operating system I used a tape drive forF backups followed by compare.  The tape drive hardware was defective in6 a manner that erased the tape on a successful read :-)   ------------------------------   End of INFO-VAX 2002.692 ************************