1 INFO-VAX	Tue, 13 Dec 2005	Volume 2005 : Issue 692       Contents:" Re: calloc() fails, no more memory" Re: calloc() fails, no more memory" Re: calloc() fails, no more memory" Re: calloc() fails, no more memory" Re: calloc() fails, no more memory, CSWS_JAVA 3.0 and JAVA-142.p2 on OpenVMS8.2?! Re: DHV11 DHQ11 in a VAX4000 QBUS ! Re: DHV11 DHQ11 in a VAX4000 QBUS ! Re: DHV11 DHQ11 in a VAX4000 QBUS 1 Re: DVNETRTG (Phase IV routing) Hobbyist license? 1 Re: DVNETRTG (Phase IV routing) Hobbyist license? 1 Re: DVNETRTG (Phase IV routing) Hobbyist license? 1 Re: DVNETRTG (Phase IV routing) Hobbyist license?  ES40 CPU Upgrade Re: ES40 CPU Upgrade+ ESC sequence for Left Margin to less then 0 / Re: ESC sequence for Left Margin to less then 0  Re: HP's 4Q FY05 results Re: illegal message cancelled ) Re: Need model number for Infoserver-1000 * Re: OpenVMS/TCPware Upgrade Results (good)* Re: OpenVMS/TCPware Upgrade Results (good)- Re: propagation of write bitmaps for minicopy A Re: Question about SPAWN/INPUT table in the DCL Dictionary manual A Re: Question about SPAWN/INPUT table in the DCL Dictionary manual " Re: saving recovery data with PCSI" Re: saving recovery data with PCSI Re: shadowing questions ! SHOW DEVICE: what should it show? % Re: SHOW DEVICE: what should it show? % Re: SHOW DEVICE: what should it show? % Re: SHOW DEVICE: what should it show? % Re: SHOW DEVICE: what should it show? % Re: SHOW DEVICE: what should it show? 0 Re: Timeout strategy: terminal vs Telnet drivers0 Re: Timeout strategy: terminal vs Telnet drivers0 RE: Timeout strategy: terminal vs Telnet drivers0 Re: Timeout strategy: terminal vs Telnet drivers0 Re: Timeout strategy: terminal vs Telnet driversC Re: USB on OpenVMS (was: Re: DS10L hardware configuration question) C Re: USB on OpenVMS (was: Re: DS10L hardware configuration question) C Re: USB on OpenVMS (was: Re: DS10L hardware configuration question) C Re: USB on OpenVMS (was: Re: DS10L hardware configuration question) C Re: USB on OpenVMS (was: Re: DS10L hardware configuration question) C Re: USB on OpenVMS (was: Re: DS10L hardware configuration question) C Re: USB on OpenVMS (was: Re: DS10L hardware configuration question)  VAX 7000 EXA0 device offline? 2 VMS/Pony Express Mail - Exchange Formatting Issues  F ----------------------------------------------------------------------  % Date: Mon, 12 Dec 2005 12:35:05 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> + Subject: Re: calloc() fails, no more memory , Message-ID: <439DB4C0.2893849E@teksavvy.com>   Richard Brodie wrote: I > Is it just me, or is everyone else on this thread wildly overestimating 0 > just how much room 400 000 longwords takes up?    G At 4 bytes each longword, it takes a whopping 1562.5 kilobytes or 3125   512-byte pages  F I have programs on my All mighty mighty Microvax II which take up more memory than that :-)  F Is it possible that the value the OP is supplying to calloc is what isB in error  ? (and you're supplying some enormous number by mistake)   ------------------------------  % Date: Mon, 12 Dec 2005 13:27:20 -0500  From: "Jilly" <jilly@hp.com>+ Subject: Re: calloc() fails, no more memory , Message-ID: <439dc108$1@usenet01.boi.hp.com>  I Please read up on C error handling in section 4.1 of the C RTL Reference  K Manual and the documentation on errno and vaxc$errno.  The VMS status from   the calloc can be retrieved.    ; "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  & news:439D9C1C.402D8DF3@teksavvy.com... > Jilly wrote: >>G >> If the process is running out PGFLQUOTA then the VMS status for the  	 >> calloc J >> should be INSVIRMEM but if the process is exceeding P0 virtual address  >> space) >> then the VMS status should be VASFULL.  > H > calloc is C function. It doesn't return a status code, it returns NULL; > when something didn't go right and the allocation failed.  >  >  > Another possible suggestion: > G > calloc a small amount of memory, and then use realloc to grow it to a  > the huge chunk you need.     ------------------------------  # Date: Mon, 12 Dec 2005 19:09:42 GMT - From: hoffman@xdelta.hp.nospam (Hoff Hoffman) + Subject: Re: calloc() fails, no more memory 0 Message-ID: <WVjnf.498$6E3.349@news.cpqcorp.net>  _ In article <dnkb5j$u6n$1@blackmamba.itd.rl.ac.uk>, "Richard Brodie" <R.Brodie@rl.ac.uk> writes:  : 2 :"Hoff Hoffman" <hoff@hp.nospam> wrote in message + :news:0vinf.483$Lv3.122@news.cpqcorp.net...  : > :>  Put another way, 400,000 longwords -- the default size forB :>  address pointers on OpenVMS -- will not fit into either P0 norE :>  into P1 space, particularly given that the image, DCL and process H :>  control structures, and other stack contents also occupy some space. : H :Is it just me, or is everyone else on this thread wildly overestimating0 :just how much room 400 000 longwords takes up?   5   It's not you.  Off by multiple orders of magnitude. $   So much for not checking the math.   $ x= 400000 * 4  $ sho sym x 3   X = 1600000   Hex = 00186A00  Octal = 00006065000  $   J   If it's really all of 1.6 megabytes (MB) total, that'll obviously easily   fit into P0 space.  J   I would look to see how much else is involved, since having all of 1.6MBI   shouldn't trigger virtual memory errors -- if the volume is that small  I   and the virtual address space is equivalently sized, then this may well I   be a run-time error (a bogus-large request) or potentially a corruption    of the heap or stack.     N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------G        Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[\0100]hp.com    ------------------------------  % Date: Mon, 12 Dec 2005 20:48:24 +0100 & From: Paul Sture <paul.sture@decus.ch>+ Subject: Re: calloc() fails, no more memory , Message-ID: <4062g9F18q6n2U1@individual.net>   Richard Brodie wrote: 3 > "Hoff Hoffman" <hoff@hp.nospam> wrote in message  , > news:0vinf.483$Lv3.122@news.cpqcorp.net... >  > = >> Put another way, 400,000 longwords -- the default size for A >> address pointers on OpenVMS -- will not fit into either P0 nor D >> into P1 space, particularly given that the image, DCL and processG >> control structures, and other stack contents also occupy some space.  >  > I > Is it just me, or is everyone else on this thread wildly overestimating 1 > just how much room 400 000 longwords takes up?   >   6  From the first post I see where Jim responds to Hans:  C "How much space do 400,000 pointers require?  Assuming 4 bytes per  F pointer, that call requires 1,600,000 bytes of free memory somewhere."   ------------------------------  + Date: Mon, 12 Dec 2005 23:37:22 +0000 (UTC) - From: klewis@OMEGA.MITRE.ORG (Keith A. Lewis) + Subject: Re: calloc() fails, no more memory . Message-ID: <dnl1ji$k46$1@newslocal.mitre.org>   Hans Blom <tocum2@yahoo.com> writes in article <1134332389.975a5b7dc6bcd3f8552d3ca4a1406370@fe2.teranews.com> dated Sun, 11 Dec 2005 20:19:49 +0000: >Jim wrote: 3 >> "Hans Blom" <tocum2@yahoo.com> wrote in message  G >> news:1134303970.bcd67978e90e81688cc82000703ebe4c@fe2.teranews.com...  >>  J >>>I'm running OpenVMS 7.3-2 on an Alphaserver. A programmer has developedJ >>>an application that, in order to work with speed, wants to keep as muchJ >>>as possible of the data in memory. At some point he does an calloc() toG >>>get a memoryarea to keep about 400 000 pointers. He gets a null back G >>>from the call, basically OpenVMS saying - sorry sir, no more memory!  >>> 2 >>>I'm stuck! Anybody got any ideas on what to do?  D >I agree with you. But shouldn't we get the infamous "PAGEFILE full,D >system will try to continue" or at least something in OPERATOR.LOG?G >And shouldn't accounting show that the process used an enormous amount  >of the paging file?   Sanity check time:   $ show proc /quota $ show mem /phys /file@ printf("data structure is %d bytes.\n", sizeof(printer_struct));  L As someone else pointed out, you can/should check ERRNO if you get NULL fromI calloc().  And if you're allocating all the memory in one fell swoop, try * malloc() and then zero what needs to be 0.  0 --Keith Lewis              klewis {at} mitre.org> The above may not (yet) represent the opinions of my employer.   ------------------------------  # Date: Tue, 13 Dec 2005 04:50:50 GMT 5 From: "Schroeder, AJ" <ajschroeder@no-spam.gmail.com> 5 Subject: CSWS_JAVA 3.0 and JAVA-142.p2 on OpenVMS8.2? 6 Message-ID: <Kqsnf.9770$Dk.2774@tornado.rdc-kc.rr.com>   Hello group,  I I have been looking around, but I cannot find any hard and fast evidence  G that CSWS_JAVA and the JAVA-142.p2 kits are supported on VMS 8.2 - all  ? relevant documentation that I find just says "7.3-2 and higher"   I I ask because everytime I start my tomcat server, it logs a crash, since  H I am not a VMS guru yet, I'll post the logfile for the group to look at.  , Any help on this is, as always, appreciated,   AJ Schroeder   Here is the logfile:  
 $ Set NoOn/ $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY")) <    Using CATALINA_BASE  : /sys$common/apache/jakarta/tomcat/<    Using CATALINA_HOME  : /sys$common/apache/jakarta/tomcat/@    Using CATALINA_TMPDIR: /sys$common/apache/jakarta/tomcat/temp Using Java 1.4.2 setup Running Tomcat.....  Created MBeanServer with ID:  : -ce4831:108226b8921:-8000:destro.butler.tmscomputers.com:1E Dec 12, 2005 10:40:59 PM org.apache.coyote.http11.Http11Protocol init / INFO: Initializing Coyote HTTP/1.1 on http-8080 B Dec 12, 2005 10:40:59 PM org.apache.catalina.startup.Catalina load* INFO: Initialization processed in 16763 ms SIGBUS    10*  bus error  9 Full thread dump Classic VM (1.4.2-4.p2, native threads): C      "Finalizer" (TID:0x10fe4e8, sys_thread_t:0x484dd00, state:CW,   native ID:0x48d7340) prio=8 0          at java.lang.Object.wait(Native Method)H          at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)H          at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)K          at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159) A      "Reference Handler" (TID:0x10fe548, sys_thread_t:0x4849d58,  & state:CW, native ID:0x4885340) prio=100          at java.lang.Object.wait(Native Method)2          at java.lang.Object.wait(Object.java:429)L          at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)A      "Signal dispatcher" (TID:0x10fe580, sys_thread_t:0x48472c8,  $ state:CW, native ID:0x3d7340) prio=5C      "main" (TID:0x10fe360, sys_thread_t:0x43b9e8, state:R, native   ID:0x7bba6d48) prio=5 C          at java.lang.ClassLoader$NativeLibrary.load(Native Method) E          at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1582) I          at java.lang.ClassLoader.loadLibrary(ClassLoader.java, Compiled   Code) <          at java.lang.Runtime.loadLibrary0(Runtime.java:780)9          at java.lang.System.loadLibrary(System.java:834) C          at java.lang.ClassLoader$NativeLibrary.load(Native Method) E          at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1582) I          at java.lang.ClassLoader.loadLibrary(ClassLoader.java, Compiled   Code) <          at java.lang.Runtime.loadLibrary0(Runtime.java:780)9          at java.lang.System.loadLibrary(System.java:834)           at D sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)F          at java.security.AccessController.doPrivileged(Native Method)J          at sun.awt.NativeLibLoader.loadLibraries(NativeLibLoader.java:38)=          at sun.awt.DebugHelper.<clinit>(DebugHelper.java:46) ;          at java.awt.Component.<clinit>(Component.java:393)           at W com.sun.naming.internal.ResourceManager.getInitialEnvironment(ResourceManager.java:125) E          at javax.naming.InitialContext.init(InitialContext.java:215) G          at javax.naming.InitialContext.<init>(InitialContext.java:174)           at r org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBeans(GlobalResourcesLifecycleListener.java:98)          at t org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.lifecycleEvent(GlobalResourcesLifecycleListener.java:78)          at W org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:113)           at F org.apache.catalina.core.StandardServer.start(StandardServer.java:668)I          at org.apache.catalina.startup.Catalina.start(Catalina.java:528) G          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)           at M sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:27)           at U sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) <          at java.lang.reflect.Method.invoke(Method.java:309)K          at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:268) J          at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:372) Monitor Cache Dump: H      java.util.Vector@10FE090/11322B8: owner "main" (0x43b9e8) 2 entriesH      java.util.Vector@10FE0A0/1132268: owner "main" (0x43b9e8) 2 entriesI      java.lang.Runtime@1100530/1147448: owner "main" (0x43b9e8) 2 entries A      java.lang.ref.ReferenceQueue$Lock@10FE500/11353D0: <unowned>            Waiting to be notified:$              "Finalizer" (0x484dd00)<      java.lang.ref.Reference$Lock@10FE558/1134F50: <unowned>           Waiting to be notified:,              "Reference Handler" (0x4849d58) Registered Monitor Dump:      utf8 hash table: <unowned>        JNI pinning lock: <unowned>)      JNI global reference lock: <unowned>       BinClass lock: <unowned> "      Class linking lock: <unowned>(      System class loader lock: <unowned>!      Code rewrite lock: <unowned>       Heap lock: <unowned> 8      Monitor cache lock: owner "main" (0x43b9e8) 1 entry7      Thread queue lock: owner "main" (0x43b9e8) 1 entry 6      Monitor registry: owner "main" (0x43b9e8) 1 entry  7 %SYSTEM-F-OPCCUS, opcode reserved to customer fault at    PC=FFFFFFFF80B6E074, PS=0000001B/ %TRACE-F-TRACEBACK, symbolic stack dump follows K    image    module    routine             line      rel PC           abs PC @   DECC$SHR_EV56                              0 00000000000FE074  FFFFFFFF80B6E074@   JAVA$JVM_SHR  INTERPRETER  Abort       38420 0000000000003F98  00000000000AEFD8(   JAVA$JVM_SHR  SIGNALS_MD  panicHandler@                                          35279 00000000000001B8  000000000010ACC8,   JAVA$HPI_SHR  INTERRUPT_MD  intrDispatchMD@                                          23817 0000000000000248  00000000001666E8@   DECC$SHR_EV56                              0 00000000001C2FA4  FFFFFFFF80C32FA4@   DECC$SHR_EV56                              0 00000000001C2C6C  FFFFFFFF80C32C6C@   DECC$SHR_EV56                              0 000000000002D6DC  FFFFFFFF80A9D6DC= ----- above condition handler called with exception 0000000C: < %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual : address=0000000000000004, PC=00000000001BA214, PS=0000001B ----- end of exception message@                                              0 FFFFFFFF800B293C  FFFFFFFF800B293C,   JAVA$JAVA_VMS_SHR  DL_JACKET  Java$dlclose@                                          32015 0000000000000224  00000000001BA214+   JAVA$JAVA_VMS_SHR  DL_JACKET  Java$dlopen @                                          32141 0000000000000778  00000000001BA768)   JAVA$HPI_SHR  LINKER_MD  sysLoadLibrary @                                          25721 0000000000000264  000000000016AD54@   JAVA$JVM_SHR  JVM  JVM_LoadLibrary     45873 000000000000DC58  00000000000EAB68   JAVA$JAVA_SHR  CLASSLOADER  2 Java_java_lang_ClassLoader_00024NativeLibrary_load@                                          17257 0000000000000728  00000000045DB1D8@   JAVA$JVM_SHR  INVOKERS  invoke_O_V     36463 0000000000000988  00000000000AFCA8@                                              0 0000000004A265B8  0000000004A265B8@                                              0 0000000004A23668  0000000004A23668@                                              0 00000000049EFFF4  00000000049EFFF4@                                              0 0000000004A13328  0000000004A13328(   JAVA$JVM_SHR  EXECUTEJAVA  ExecuteJava@                                          38859 000000000000C50C  00000000000BCFAC@   JAVA$JVM_SHR  JNI  jni_Invoke          39549 00000000000016C4  00000000000C18F4.   JAVA$JVM_SHR  JNI  jni_CallStaticVoidMethodV@                                          40798 000000000000535C  00000000000C558C5   JAVA$JAVA_SHR  JNI_UTIL  JNU_CallStaticMethodByName @                                          11586 0000000000000574  00000000045E39A4+   JAVA$AWT_SHR  AWT_LOADLIBRARY  JNI_OnLoad @                                          21050 0000000000000264  0000000005960264   JAVA$JAVA_SHR  CLASSLOADER  2 Java_java_lang_ClassLoader_00024NativeLibrary_load@                                          17272 00000000000007B4  00000000045DB264@   JAVA$JVM_SHR  INVOKERS  invoke_O_V     36463 0000000000000988  00000000000AFCA8@                                              0 0000000004A265B8  0000000004A265B8@                                              0 0000000004A23668  0000000004A23668@                                              0 00000000049EFFF4  00000000049EFFF4@                                              0 0000000004A13328  0000000004A13328@                                              0 0000000004A1E450  0000000004A1E450(   JAVA$JVM_SHR  EXECUTEJAVA  ExecuteJava@                                          38859 000000000000C50C  00000000000BCFAC:   JAVA$JVM_SHR  INTERPRETER  do_execute_java_method_vararg@                                          37447 00000000000012D4  00000000000AC314@   JAVA$JVM_SHR  JVM  JVM_DoPrivileged    41374 0000000000000E78  00000000000DDD88@   JAVA$JVM_SHR  INVOKERS  invoke_O_O     36727 00000000000012A4  00000000000B05C4@                                              0 000000000592473C  000000000592473C>   JAVA$JIT_142_SHR  SUNINTERFACE_  AlphaInvokeUncompiledMethod@                                          33946 00000000000002BC  00000000049B0DCC/   JAVA$JIT_142_SHR  SUNGENERATOR_  InvokeStatic @                                          34477 000000000000DD18  00000000049ABFF8@                                              0 000000000591BF34  000000000591BF34>   JAVA$JIT_142_SHR  SUNINTERFACE_  AlphaInvokeUncompiledMethod@                                          33946 00000000000002BC  00000000049B0DCC(   JAVA$JVM_SHR  EXECUTEJAVA  ExecuteJava@                                          38859 000000000000C50C  00000000000BCFAC:   JAVA$JVM_SHR  INTERPRETER  do_execute_java_method_vararg@                                          37447 00000000000012D4  00000000000AC3143   JAVA$JVM_SHR  INTERPRETER  do_execute_java_method @                                          37290 0000000000000B40  00000000000ABB803   JAVA$JVM_SHR  CLASSRUNTIME  RunStaticInitializers @                                          37468 000000000000202C  00000000000A0ACC@   JAVA$JVM_SHR  CLASSRUNTIME  InitClass  37543 0000000000002318  00000000000A0DB87   JAVA$JVM_SHR  CLASSINITIALIZE  InitClassConstantClass @                                          36143 000000000000012C  000000000009332C<   JAVA$JVM_SHR  CLASSINITIALIZE  ResolveClassConstantAndInit@                                          36162 0000000000000000  0000000000000000=   JAVA$JIT_142_SHR  SUNGENERATOR_  ResolveClassConstantJacket @                                          34303 000000000000D6A4  00000000049AB984/   JAVA$JIT_142_SHR  SUNGENERATOR_  InvokeStatic @                                          34445 000000000000DC20  00000000049ABF00@                                              0 00000000057DE754  00000000057DE754>   JAVA$JIT_142_SHR  SUNINTERFACE_  AlphaInvokeUncompiledMethod@                                          33946 00000000000002BC  00000000049B0DCC(   JAVA$JVM_SHR  EXECUTEJAVA  ExecuteJava@                                          38859 000000000000C50C  00000000000BCFAC:   JAVA$JVM_SHR  INTERPRETER  do_execute_java_method_vararg@                                          37447 00000000000012D4  00000000000AC3143   JAVA$JVM_SHR  INTERPRETER  do_execute_java_method @                                          37290 0000000000000B40  00000000000ABB803   JAVA$JVM_SHR  CLASSRUNTIME  RunStaticInitializers @                                          37468 000000000000202C  00000000000A0ACC@   JAVA$JVM_SHR  CLASSRUNTIME  InitClass  37543 0000000000002318  00000000000A0DB83   JAVA$JVM_SHR  CLASSRUNTIME  RunStaticInitializers @                                          37443 0000000000001F68  00000000000A0A08@   JAVA$JVM_SHR  CLASSRUNTIME  InitClass  37543 0000000000002318  00000000000A0DB83   JAVA$JVM_SHR  CLASSRUNTIME  RunStaticInitializers @                                          37443 0000000000001F68  00000000000A0A08@   JAVA$JVM_SHR  CLASSRUNTIME  InitClass  37543 0000000000002318  00000000000A0DB83   JAVA$JVM_SHR  CLASSRUNTIME  RunStaticInitializers @                                          37443 0000000000001F68  00000000000A0A08@   JAVA$JVM_SHR  CLASSRUNTIME  InitClass  37543 0000000000002318  00000000000A0DB87   JAVA$JVM_SHR  CLASSINITIALIZE  InitClassConstantClass @                                          36143 000000000000012C  000000000009332C<   JAVA$JVM_SHR  CLASSINITIALIZE  ResolveClassConstantAndInit@                                          36162 0000000000000000  0000000000000000,   JAVA$JIT_142_SHR  SUNGENERATOR_  CheckCast@                                          35035 000000000000F784  00000000049ADA64@                                              0 00000000058E4518  00000000058E4518>   JAVA$JIT_142_SHR  SUNINTERFACE_  AlphaInvokeUncompiledMethod@                                          33946 00000000000002BC  00000000049B0DCC@                                              0 00000000058EABB8  00000000058EABB8>   JAVA$JIT_142_SHR  SUNINTERFACE_  AlphaInvokeUncompiledMethod@                                          33946 00000000000002BC  00000000049B0DCC0   JAVA$JIT_142_SHR  SUNGENERATOR_  InvokeVirtual@                                          34363 000000000000D8D8  00000000049ABBB8@                                              0 00000000058CB884  00000000058CB884>   JAVA$JIT_142_SHR  SUNINTERFACE_  AlphaInvokeUncompiledMethod@                                          33946 00000000000002BC  00000000049B0DCC0   JAVA$JIT_142_SHR  SUNGENERATOR_  InvokeSpecial@                                          34428 000000000000DB68  00000000049ABE48@                                              0 00000000058EA43C  00000000058EA43C>   JAVA$JIT_142_SHR  SUNINTERFACE_  AlphaInvokeUncompiledMethod@                                          33946 00000000000002BC  00000000049B0DCC0   JAVA$JIT_142_SHR  SUNGENERATOR_  InvokeVirtual@                                          34363 000000000000D8D8  00000000049ABBB8@                                              0 00000000058A6744  00000000058A67442   JAVA$JIT_142_SHR  SUNGENERATOR_  InvokeInterface@                                          34538 000000000000DF68  00000000049AC248@                                              0 00000000058941D4  00000000058941D40   JAVA$JIT_142_SHR  SUNGENERATOR_  InvokeVirtual@                                          34363 000000000000D8D8  00000000049ABBB8@                                              0 00000000058997AC  00000000058997AC>   JAVA$JIT_142_SHR  SUNINTERFACE_  AlphaInvokeUncompiledMethod@                                          33946 00000000000002BC  00000000049B0DCC2   JAVA$JIT_142_SHR  SUNGENERATOR_  InvokeInterface@                                          34538 000000000000DF68  00000000049AC248@                                              0 00000000058A3A5C  00000000058A3A5C>   JAVA$JIT_142_SHR  SUNINTERFACE_  AlphaInvokeUncompiledMethod@                                          33946 00000000000002BC  00000000049B0DCC(   JAVA$JVM_SHR  EXECUTEJAVA  ExecuteJava@                                          38859 000000000000C50C  00000000000BCFAC@   JAVA$JVM_SHR  JVM  pop_result          45113 000000000000BF08  00000000000E8E18@   JAVA$JVM_SHR  JVM  invoke              45117 0000000000000000  0000000000000000@   JAVA$JVM_SHR  JVM  JVM_InvokeMethod    45212 000000000000C6B0  00000000000E95C03   JAVA$JVM_SHR  JAVA$INVOKE_NATIVE  sysInvokeNative @                                           2479 00000000000002A0  000000000010C1603   JAVA$JVM_SHR  CLASSRUNTIME  invokeJNINativeMethod @                                          36909 0000000000000AF4  000000000009F594@                                              0 0000000004B6C08C  0000000004B6C08C0   JAVA$JIT_142_SHR  SUNGENERATOR_  InvokeVirtual@                                          34363 000000000000D8D8  00000000049ABBB8@                                              0 0000000004B6BC2C  0000000004B6BC2C2   JAVA$JIT_142_SHR  SUNGENERATOR_  InvokeInterface@                                          34538 000000000000DF68  00000000049AC248@                                              0 0000000004B5D994  0000000004B5D9940   JAVA$JIT_142_SHR  SUNGENERATOR_  InvokeVirtual@                                          34363 000000000000D8D8  00000000049ABBB8@                                              0 00000000058A091C  00000000058A091C>   JAVA$JIT_142_SHR  SUNINTERFACE_  AlphaInvokeUncompiledMethod@                                          33946 00000000000002BC  00000000049B0DCC0   JAVA$JIT_142_SHR  SUNGENERATOR_  InvokeVirtual@                                          34363 000000000000D8D8  00000000049ABBB8@                                              0 0000000004BE2774  0000000004BE2774>   JAVA$JIT_142_SHR  SUNINTERFACE_  AlphaInvokeUncompiledMethod@                                          33946 00000000000002BC  00000000049B0DCC(   JAVA$JVM_SHR  EXECUTEJAVA  ExecuteJava@                                          38859 000000000000C50C  00000000000BCFAC@   JAVA$JVM_SHR  JNI  jni_Invoke          39549 00000000000016C4  00000000000C18F4-   JAVA$JVM_SHR  JNI  jni_CallStaticVoidMethod @                                          40788 0000000000005310  00000000000C5540@   JAVA$JAVA  JAVA  Java$main_Jacket       9429 0000000000000FC4  0000000000030FC4@   JAVA$JAVA  MAIN_JACKET  main           33170 0000000000000204  000000000003C694@   JAVA$JAVA  MAIN_JACKET  __main             0 0000000000000084  000000000003C514@   PTHREAD$RTL                                0 00000000000572E8  FFFFFFFF80A512E8@   PTHREAD$RTL                                0 0000000000030444  FFFFFFFF80A2A444@                                              0 FFFFFFFF8033DF94  FFFFFFFF8033DF94* Tomcat Logicals and Classpaths are cleared9    APACHE$WWW   job terminated at 12-DEC-2005 23:41:01.57       Accounting information:F    Buffered I/O count:               5422      Peak working set size: 	     60880 B    Direct I/O count:                 1502      Peak virtual size: 	    356672 @    Page faults:                     12263      Mounted volumes: 	         0 E    Charged CPU time:        0 00:00:20.16      Elapsed time:       0   00:00:27.17    ------------------------------  % Date: Mon, 12 Dec 2005 17:47:29 -0500 - From: William Webb <william.w.webb@gmail.com> * Subject: Re: DHV11 DHQ11 in a VAX4000 QBUSH Message-ID: <8660a3a10512121447q6495b42q74bd67d7e2b30772@mail.gmail.com>  L On 12/12/05, David Turner, Island Computers US Corp <dbturner@icusc.com> wr= ote:K > If I remember correctly there was a type of Microvax III that went into a  > BA23 or BA123 ; > If that is so, I don't see why you can't go the other way  > K > As for the DHV11, I remember a long time ago when we sold to ticketmaster C > they were using DHV11 with the KA650  Microvax III in a BA23 form  >  > DT >  > -- >  > David B Turner > Island Computers US Corp > 2700 Gregory St, Suite 180 > Savannah GA 31404  > Tel: 912 447 6622 X201 > Cell: 912 447 6622 X252  > Fax: 912 201 0402  > Email: dbturner@icusc.com  > Web: http://www.islandco.comK > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= ' =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > All orders are subject to the following terms and conditions0 > of sale. These should be read before ordering.' > http://www.islandco.com/warranty.html  > < > "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message( > news:439DA0A7.8A281BCC@teksavvy.com...K > > The documentation for the various flavours of the VAX 4000 mention only 6 > > the CXS16 CXB16 and CXY08 serial line controllers. > > K > > Would good old DHV11 and DHQ11 (the DHQ is a half width module, the DHV K > > is the older one that takes up A B C and D of the Q bus slot) work in a  > > VAX 4000 ? > > J > > I realise that there are mechanical considerations for the actual DB25I > > connector assemblies. Assuming I have good quality duct tape to affix B > > the DB25 connector assembly, would the board have any problems* > > interfacing with the CPU and with VMS? > > F > > Similarly, on my all mighty Microvax II, I have a DILOG SQ739 SCSII > > controller. I have a set of console mode commands that start the SCSI I > > controller configuration menu. (deposit a few bytes here and there to H > > initialise the IO subsystem and then  START at a specific address toD > > branch to the controller program (all done from the >>> prompt). > > K > > If I were to plug this one into a VAX 4000-200 or -600, would it work ? I > > And more importantly, would the same commands function ? (I know that # > > the CSR adresses would change).  > > D > > The doc seems to indicate that it works for Microvax II and III. > > + > > D/P/L 20008004 80000001  ; setup IO map - > > D/P/W 20001F40 20        ; enable mapping  > > = > > D/P/W 200000DC 0         ; write IP to reset host adapter < > > D/P/W 200000DE 3FFF      ; write keyword to initiate DMA > > G > > S 200                    ; start virtual terminal driver (the SQ739  > > config menus)  > >  > > E > > The middle 2 instructions have memory adresses that depend on the K > > board's "position" on the QBUS in terms of CSR vectors etc. The first 2   > > and last one seem "generic". > > L > > Are the generic instructions' memory adresses  part of the QBUS standar= d . > > on all VAX models equipped with the QBUS ? > >  > > ------------ > >  > > K > > On a realted note, I have seem somewhat conflicting info on whether the K > > motherboard and memory from a VAX4000-200 can be inserted into the QBUS I > > of an all mighty Microvax II. Were there special boards made for such L > > upgrades, or can any generic 4000-200 motherboard and memory be inserte= d L > > into the cabinet of a Microvax II (I have the big H9642 with the 2 BA21= 3s.  >  >  >   F MicroVAX 3400 or 3500?  I know where one is sitting in storage and the5 guy who owns it (not me) would LOVE to get rid of it.   E He's also got an AlphaServer 1000 with HSZ40s? and some BA35x shelves  that are gathering dust.   Located in Raleigh, NC.    WWWebb --C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  # Date: Tue, 13 Dec 2005 00:10:43 GMT # From: hoff@hp.nospam (Hoff Hoffman) * Subject: Re: DHV11 DHQ11 in a VAX4000 QBUS0 Message-ID: <7konf.532$YQ3.346@news.cpqcorp.net>     Have a look at:   0     http://decdoc.itsx.net/dec94mds/396abtm2.txt0     http://decdoc.itsx.net/dec94mds/437abts2.pdf  F   I don't know that they'll help here, but they are sources of details    on the KA660 series processor.  E   MicroVAX III (KA650), MicroVAX III+ (KA655) and MicroVAX IV (KA660) B   processors were the upgrades for the BA23 and BA123 enclosures.   F   I know the bulkheads for the MicroVAX II, MicroVAX III and MicroVAX E   III+ are compatible.  (See the FAQ.)  Off-hand, I don't know if the E   MicroVAX IV (the VAX 4000 model 200, KA660) was compatible with the H   older bulkheads and thus with the older enclosures -- the old MicroVAXG   IV upgrade part number was 2T-KA660-*.  AFAIK, no MicroVAX 3300/3400  G   KA640 was compatible with the older boxes -- the console I/O bulkhead G   was attached to the processor module, as is the norm for many modules     destined for S-box enclosures.  G   I do not know if the memory map is the same across all the processors F   here, nor if the Dilog SCSI controller would be compatible with the I   newer processors.  If it works with the II and the III, it likely also  H   works with the III+ and there is a reasonable chance it works with theF   IV.  That said, faster Q-bus VAX processors have derailed at least a!   few of the older Q-bus modules.   B   The MicroVAX processors with detached handles could be installed@   into the BA23 and BA123, but those processors with fixed S-box   handles can not.    D   All the KA640 processors I've seen have had a fixed S-box handle. F   I'm not certain if all the KA660 processors had fixed S-box handles.G   Modules with the S-box handle (or bulkhead) won't fit in the BA23 nor G   BA123 enclosure, and there is no particular way to mount the I/O into D   the enclosure -- well, from experience, you won't be able to closeE   the box nor secure the bulkheads without resorting to a Dremel tool    and some field engineering.   D   You need to be careful with the CD slots here, too, as a processorC   or memory that expects to be in a Q22/CD slot should be installed F   in one.  Different enclosures had different configurations of Q22/CDD   slots, and older boxes had numbers of Q22/Q22 slots.  You can haveD   exactly as many processor and memory modules as you have CD slots.  E   The usual rack-mount MicroVAX II enclosure -- often called the "Q5" H   configuration -- was comprised of two or rarely even three BA23 9-slotF   boxes.  (I'm aware of one product that shipped with three BA23 boxes7   in one combined system.  There may have been others.)     N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------G        Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[\0100]hp.com    ------------------------------  % Date: Mon, 12 Dec 2005 20:22:40 -0600 / From: Chris Scheers <chris@applied-synergy.com> * Subject: Re: DHV11 DHQ11 in a VAX4000 QBUS2 Message-ID: <439E3070.1030301@applied-synergy.com>  - David Turner, Island Computers US Corp wrote: K > If I remember correctly there was a type of Microvax III that went into a  > BA23 or BA123 ; > If that is so, I don't see why you can't go the other way   B They weren't normal DEC products, but through CSS you could get a D MicroVAX 3 (not III!) which was a KA650, a MicroVAX 3+ (KA655) or a  MicroVAX 4 (KA660).    These were BA23/BA123 upgrades.   G The MicroVAX 4 upgrade had a KA660 without S handles.  I think it used   it's own cabinet kit.   I The MicroVAX 3 and 3+ used the same cabinet kit as a MicroVAX II. (KA630)   D I think that these systems used the standard MicroVAX II backplanes.   --  G ----------------------------------------------------------------------- $ Chris Scheers, Applied Synergy, Inc.  B Voice: 817-237-3360            Internet: chris@applied-synergy.com    Fax: 817-237-3074   ------------------------------  # Date: Mon, 12 Dec 2005 19:04:32 GMT # From: hoff@hp.nospam (Hoff Hoffman) : Subject: Re: DVNETRTG (Phase IV routing) Hobbyist license?0 Message-ID: <4Rjnf.497$6E3.239@news.cpqcorp.net>  c In article <4Ohnf.464$Kw.226@news.cpqcorp.net>, Keith Parris <keithparris_NOSPAM@yahoo.com> writes:  :Bob Armstrong wrote: I :>   Is there a reason that DVNETRTG is not included (among the 100 or so ( :> other PAKs!) in the hobbyist program? : 2 :If you're on Alpha, try the DVNETEXT PAK instead.  A   For the longest time, there was no DECnet routing available on  ?   OpenVMS Alpha, so there was no routing PAK -- there was a way 9   to use a cluster alias, but not full-on DECnet routing.   @   What we should have in the OpenVMS Alpha bundle is one of the ?   NET-APP-SUPP license PAKs.  (Whether or not that license can  "   be added is another discussion.)      I'll poke around and ask.   N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------G        Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[\0100]hp.com    ------------------------------    Date: 12 Dec 2005 16:27:24 -0800$ From: "Bob Armstrong" <bob@jfcl.com>: Subject: Re: DVNETRTG (Phase IV routing) Hobbyist license?C Message-ID: <1134433644.347159.115830@g49g2000cwa.googlegroups.com>   @ > For the longest time, there was no DECnet routing available on@ >  OpenVMS Alpha, so there was no routing PAK -- there was a way: >  to use a cluster alias, but not full-on DECnet routing.  G   I'm confused - is there actually Phase IV routing capability on Alpha F now?  I didn't think there was.  Can it do level 2 (area) routing too?  > >What we should have in the OpenVMS Alpha bundle is one of the >  NET-APP-SUPP license PAKs.   B   Alpha or VAX?  I didn't say, but I'm actually interested in VAX.D However, if Alpha is the only option for a router (that'd be ironic,F considering that they couldn't even do it not that long ago) then I'll dig one up somewhere :-)   >I'll poke around and ask.       Thank you!   Bob    ------------------------------  # Date: Tue, 13 Dec 2005 01:53:15 GMT # From: hoff@hp.nospam (Hoff Hoffman) : Subject: Re: DVNETRTG (Phase IV routing) Hobbyist license?0 Message-ID: <fQpnf.534$wR3.148@news.cpqcorp.net>  j In article <1134433644.347159.115830@g49g2000cwa.googlegroups.com>, "Bob Armstrong" <bob@jfcl.com> writes:B :>  For the longest time, there was no DECnet routing available onA :>  OpenVMS Alpha, so there was no routing PAK -- there was a way ; :>  to use a cluster alias, but not full-on DECnet routing.  : H :  I'm confused - is there actually Phase IV routing capability on AlphaG :now?  I didn't think there was.  Can it do level 2 (area) routing too?   E   OpenVMS Alpha has host-based DECnet routing as part of DECnet-Plus.   E   As an alternative, if all the nodes are connected on the same or to E   a bridged LAN and you have just one circuit and one line configured D   (and it's the LAN), you don't need a DECnet router -- DECnet will C   operate on a LAN without a DECnet router.  (DECnet end nodes will B   try to contact to other end nodes -- in the absence of a DECnet D   router -- by simply tossing out the network packets onto the LAN.)  C :  Alpha or VAX?  I didn't say, but I'm actually interested in VAX. E :However, if Alpha is the only option for a router (that'd be ironic, G :considering that they couldn't even do it not that long ago) then I'll  :dig one up somewhere :-)   C   You need either the DECnet routing license or the appropriate NAS B   license to enable it, or (if you lack the licenses) an external *   router with DECnet routing capabilities.   :>I'll poke around and ask.   C   I posted out the DECnet question (actually, the request for a PAK C   to be added into the hobbyist set) about an hour ago.  If/when I     hear back...    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------G        Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[\0100]hp.com    ------------------------------    Date: 12 Dec 2005 20:41:35 -0800$ From: "Bob Armstrong" <bob@jfcl.com>: Subject: Re: DVNETRTG (Phase IV routing) Hobbyist license?C Message-ID: <1134448895.544898.295330@g44g2000cwa.googlegroups.com>   D >As an alternative, if all the nodes are connected on the same or toK >  a bridged LAN and you have just one circuit and one line configured ....   F   Thanks, but that doesn't help in this case.  Bridging geographicallyG separated LANs over Internet requires specialized routers (e.g. a Cisco : - not exactly rare, but not something every hobbyist has).  D >  You need either the DECnet routing license or the appropriate NAS >  license to enable it,  D   You had mentioned the possibility of adding the NAS license to theE Alpha hobbyist PAKs, but we'd actually want to add it to both VAX and  Alpha.  
 Thanks again,  Bob    ------------------------------  # Date: Mon, 12 Dec 2005 19:26:52 GMT  From: dittman@dittman.net  Subject: ES40 CPU Upgrade * Message-ID: <0aknf.37070$Y7.6921@trnddc02>  B I have an ES40 with two 667MHz CPUs.  The CPU part number for bothB CPUs is 54-30362-01.A03.  These are EV67 pass 2.3.3.  If I add two@ more 667MHz CPUs do I need to match the CPU part number and EV67@ pass?  I know this was an issue with the 500MHz CPUs but I can't& find any warnings for the 667MHz CPUs.  ? This is a hobbyist system so asking HP support isn't an option.  --   Eric Dittman dittman@dittman.net    ------------------------------  % Date: Mon, 12 Dec 2005 15:07:57 -0500 C From: "David Turner, Island Computers US Corp" <dbturner@icusc.com>  Subject: Re: ES40 CPU Upgrade 9 Message-ID: <EEknf.51842$i7.29221@bignews2.bellsouth.net>     Yes - they need to be identical?   DT   --     David B Turner Island Computers US Corp 2700 Gregory St, Suite 180 Savannah GA 31404  Tel: 912 447 6622 X201 Cell: 912 447 6622 X252  Fax: 912 201 0402  Email: dbturner@icusc.com  Web: http://www.islandco.com% ===================================== < All orders are subject to the following terms and conditions. of sale. These should be read before ordering.% http://www.islandco.com/warranty.html   K <dittman@dittman.net> wrote in message news:0aknf.37070$Y7.6921@trnddc02... D > I have an ES40 with two 667MHz CPUs.  The CPU part number for bothD > CPUs is 54-30362-01.A03.  These are EV67 pass 2.3.3.  If I add twoB > more 667MHz CPUs do I need to match the CPU part number and EV67B > pass?  I know this was an issue with the 500MHz CPUs but I can't( > find any warnings for the 667MHz CPUs. > A > This is a hobbyist system so asking HP support isn't an option.  > --   > Eric Dittman > dittman@dittman.net    ------------------------------    Date: 12 Dec 2005 20:42:25 -0800 From: timf@ptd.net4 Subject: ESC sequence for Left Margin to less then 0B Message-ID: <1134448945.360114.46340@g49g2000cwa.googlegroups.com>  G Does anyone know how the PCL for setting left margin to be less than 0. E I tried negative number and the result was the same as 0. The printer 
 is a LEXMARK.    Tried:  1 <ESC>&a9                     ! Resets left margin  <ESC>&a9, <ESC>&a0L  <ESC>&a9, <ESC>&a-2L  G The desired output is for the first character of each line is to start:     here.  -     not here. Which seems  to be the default.     5 The customer does not allow for any form definitions.   ! Any input is greatly appreciated.    ------------------------------    Date: 12 Dec 2005 21:26:44 -0800 From: dooleys@snowy.net.au8 Subject: Re: ESC sequence for Left Margin to less then 0C Message-ID: <1134451604.294238.202900@g49g2000cwa.googlegroups.com>   1 shouldn't you have <ESC>9 to clear margins first? C then <ESC>&a0L to set left margin to leftmost position in printable  area Phil   ------------------------------  % Date: Mon, 12 Dec 2005 20:14:03 -0800 # From: "Tom Linden" <tom@kednos.com> ! Subject: Re: HP's 4Q FY05 results ( Message-ID: <ops1pfdpqrzgicya@hyrrokkin>  0 On Mon, 12 Dec 2005 17:31:40 GMT, Keith Parris  % <keithparris_NOSPAM@yahoo.com> wrote:    > Tom Linden wrote: 8 >> I meant to what amount. I know it was yoy comparison. > F > http://h71028.www7.hp.com/ERC/cache/251028-0-0-0-121.html?ERL=true  J > indicates HP Integrity Server revenues topped $1 Billion in FY2004. So  H > one could conclude that FY2005 HP Integrity Server revenue must have  & > been getting up close to $2 Billion.  F Keith, you don't seriously think anybody will believe that do you?  In fact the URL you cite says:     K Fact 1: HP Integrity solutions revenue surpassed $1B for fiscal year 2004    [1]  	  	   K HP Integrity servers have strong market momentum which is demonstrated by   B the significant revenue by generated by Integrity server-related  C solutions. These solutions -- which include HP Integrity servers,   E software, HP StorageWorks systems and hardware services -- span key   K industries such as financial services, manufacturing, network and service   ! providers, and the public sector.    ------------------------------  % Date: Mon, 12 Dec 2005 18:21:39 +0000 " From: Darrell <cota348@rogers.com>& Subject: Re: illegal message cancelled8 Message-ID: <1gfk4bjf83asb$.juq84wr1d47n.dlg@40tude.net>  = On Sat, 10 Dec 2005 15:58:36 +0000 (UTC), Nomen Nescio wrote:    > illegal message cancelled   + awww, is someone cmsg cancel Nomen's posts?    ------------------------------  % Date: Mon, 12 Dec 2005 20:03:30 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>2 Subject: Re: Need model number for Infoserver-1000+ Message-ID: <439E2BF2.A7EAB4E2@comcast.net>    Hoff Hoffman wrote:  > s > In article <gxYg+juJRoyy@eisner.encompasserve.org>, koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes:  > : H > :   I'm trying to get a hardware maintenance contract from HP.  One ofG > :   my systems, an Infoserver-1000, has the following model number on  > :   its tag: > :  > :      70-30343-03. A02  > : > > :   HP claims that "703034303A" is not a valid model number. > 6 >   The 2-5-2 format is a classic DIGITAL part number. > = >   The serial number will begin with two characters (tied to ? >   a DIGITAL site code, such as WM, ZK or NI, followed by some : >   number of letters and (usually mostly or all) numbers. > D > :   Is this a punctuation problem, or is HP looking for some other
 > :   number?  >  >   The latter.  > H >   The serial number sticker is located on the bottom of the InfoServerG >   1000 itself, and clearly labeled with the model number and with the C >   classic "SN" prefix indicating the serial number of the device. F >   Pull the cables off the back, slide the release lever to the left,5 >   and pull the device out of the shelf for a look.)  > G >   We now have InfoServer support built directly into current versions H >   of OpenVMS, as another alternative to the older InfoServer hardware.F >   You can use an AlphaServer, for instance, for InfoServer services.E >   (Not including the CD recording that was once provided by the old E >   and optional InfoServer Scribe package, though that capability is 4 >   also available within OpenVMS V7.3-1 and later.)  G Indeed. I like the idea of COPY/RECORD that I saw you mention somewhere E else, assuming the equivalent of DVDWRITE can be made CLI$ compliant.  That'd be excellent!   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Mon, 12 Dec 2005 19:14:16 -0500 ) From: "Neil Rieck" <n.rieck@sympatico.ca> 3 Subject: Re: OpenVMS/TCPware Upgrade Results (good) 9 Message-ID: <knonf.1189$PQ3.284149@news20.bellglobal.com>   A Ok so I went into work this morning with the following intention:   G Use both "SYSGEN" and "$SET CACHE/RESET" to disable the XFC while I use G "$MON CLU/INT=1/AVE" and "$MON CLU/INT=1/MAX" to watch the system for 5 L minutes. Then I was going to reenable the cache and monitor again for 5 moreK minutes. I was hoping that I could use the lock count as a rough measure of H time-compressed work. (if system work can be related to lock operations,G then twice as many lock operations in the same amount of time means the & system is approximately twice as fast)  K The only thing wrong with my plan was disabling the cache. As soon as I did L this the system slowed down and my phone starting ringing within 60 seconds.F So I've got nothing else to tell the world other than the XFC is doing? something really cool for me (I've ordered another 1 GB of RAM)   
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.8 http://www3.sympatico.ca/n.rieck/links/cool_openvms.html   ------------------------------    Date: 12 Dec 2005 18:51:24 -0800 From: bob@instantwhip.com 3 Subject: Re: OpenVMS/TCPware Upgrade Results (good) B Message-ID: <1134442284.058296.58600@o13g2000cwo.googlegroups.com>  C I am telling you perfectcache from Raxco would make your system hum 
 even more ...    ------------------------------  + Date: Mon, 12 Dec 2005 22:05:32 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)6 Subject: Re: propagation of write bitmaps for minicopy$ Message-ID: <dnks7b$gnj$2@online.de>  9 In article <dnipf4$rdb$1@news01.intel.com>, Ken Fairfield ! <my.full.name@intel.com> writes:    D >     The first thing you have to know is that MINICOPY maintains anB > in-memory bitmap of clusters of blocks for the whole shadow set.? > Secondly, since shadow sets are cluster-wide entities, when a D > shadow member is dismounted, all nodes with the shadow set mounted@ > have to communicate to all other nodes which blocks they write > to.    OK.   C >     I find the inline HELP for MOUNT/POLICY=MINICOPY and DISMOUNT # > /POLICY=MINICOPY confusing! :-(      Indeed!   " > The entry for DISMOUNT says thatD > a write bitmap will be created when a single member is dismounted.D > It doesn't say whether other bitmap-capable nodes will also create > bitmaps (likely not)    ! This is what is not clear for me.   . > and neither this entry nor the one for MOUNTB > say that the subsequent mini-copy of the dismounted member needsE > to be executed from the node that dismounted it...but that may very  > well be the case.      Right---that's my question.   0 > The entry for MOUNT implies that the _initial_C > mount in cluster of a shadow set must specify /POLICY=MINICOPY to F > allow subsequent minicopies (and creates the write bitmap), but that > seems too restrictive, etc.   = Definitely not true.  I think what it means is that if you do H MOUNT/POLICY=MINICOPY, then the DISMOUNT defaults to /POLICY=MINICOPY.  E I think this is true of some other MOUNT|DISMOUNT qualifiers as well.   E I would like to see MOUNT/POLICY=MINICOPY=NOW which would initiate a  I write bitmap right away.  Thus, one could have a minicopy in the case of  D an UNPLANNED split of a shadow set.  Of course, if the disk is very H active, this wouldn't make much sense, but would on a disk which is not  very active.  M > > In particular, if I dismount a physical member of a shadow set on a node  K > > which is to be shut down and rebooted, and the shadow set gets mounted  J > > during the startup sequence, what do I need to do to make sure that a  > > MINICOPY occurs? > G >     You need to make sure there's an active write bitmap on some node E > in the cluster that has the shadow set mounted, and that you're NOT C > shutting down.  The bitmap is memory-resident and won't survive a  > reboot (obviously).   F Of course.  However, I was thinking that it might get propagated to a @ rebooting node before this node is capable of initiating a copy.   ------------------------------    Date: 12 Dec 2005 13:31:11 -0800$ From: "AEF" <spamsink2001@yahoo.com>J Subject: Re: Question about SPAWN/INPUT table in the DCL Dictionary manualC Message-ID: <1134423071.479544.144610@o13g2000cwo.googlegroups.com>    briggs@encompasserve.org wrote: l > In article <1134403065.283312.274140@z14g2000cwz.googlegroups.com>, "AEF" <spamsink2001@yahoo.com> writes:G > > Apparently the confusion is coming from the NRO term. I thought all H > > these examples you show use record-oriented devices. So what's going; > > on? I think this term, NRO, is the crux of the problem.  > @ > Disk devices are not record oriented.  They are file oriented. > K > Disk EISNER$DRA3:, device type 7 Member RAID 5, is online, mounted, file- Q >     oriented device, shareable, available to cluster, error logging is enabled.  > O > Device MBA8964:, device type local memory mailbox, is online, record-oriented ( >     device, shareable, mailbox device. > Q > Terminal VTA2621:, device type VT200 Series, is online, record-oriented device,  >     carriage control.  > H > Again, as I wrote in my first response, the issue is file positioning.F > If you are trying to pass an open file complete with record positionG > to the subprocess, that's more difficult than simply passing a device G > name.  And if you are trying to reposition the parent record position F > to reflect records consumed by the child, that's more difficult thanL > simply reading the next record from the mailbox/card reader/user keyboard. > M > The important distinction is that record-oriented devices are non-seekable.   3 I goofed. I meant record-oriented files. Anyway,...   @ The manual says NON-record-oriented process-permanent FILES. TheF mailbox and terminal are record-oriented, so the table shouldn't applyG to them. The disk is a device, not a file, so the table shouldn't apply  to it.   ------------------------------    Date: 12 Dec 2005 15:45:59 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) J Subject: Re: Question about SPAWN/INPUT table in the DCL Dictionary manual3 Message-ID: <ycyoQ1w5bc+m@eisner.encompasserve.org>   T In article <xlHiO2ZuCRsS@eisner.encompasserve.org>, briggs@encompasserve.org writes: > ' > Now, what's a "record-oriented" file?  > D > A record-oriented file is a mailbox, or a card reader.  What otherI > platforms might call a "unit record" device.  It is a sequential device " > that returns a record at a time.  G    Or a file on disk or tape, with attributes that make it a collection F    of records.  And of course, if it isn't a collection of records butB    your accessing it through RMS, it can look like a collection of    records anyhow.   > 0 > I don't know whether serial terminals qualify.      Yes, they do.   ------------------------------  + Date: Mon, 12 Dec 2005 22:11:55 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)+ Subject: Re: saving recovery data with PCSI $ Message-ID: <dnksjb$gnj$3@online.de>  / In article <gvhnf.459$fA3.52@news.cpqcorp.net>, 6 hammond@not@peek.ssr.hp.com (Charlie Hammond) writes:   : > You can save recovery data ONLY when installing PATCHES.   OK.   C > You can save recovery data for any number of patch installations, E > provided that ALL the patch installation save recovery data, and NO + > other install/remove operations intevene.  > D > If you install patches A, B and C, saving recovery data, that data > will be lost if you then > 8 >     - Install patch D without saving recovery data, or, >     - Install or remove a layered product. > K > PCSI will warn you if you perform an operation that will require removing ! > previously saved recovery data.   N > PRODUCT UNDO PATCH can rollback one or more patches for which there is savedM > recovery data.  The rollback happens in reverse chronological order -- i.e. M > the reverse of the order in which the patches were installed.  If there is  I > recoverdy data for more than one patch, you "undo" only the most recent N > patch(es), or all of them.  However, you cannot "skip" on or more patches --$ > the removal must be reverse order. > " > If this doesn't help, ask again.  @ If I apply several patches one after the other, no PCSI logicalsE defined, and answer the questions so that I can continue, it appears  F that if I save data for patch A, then it is deleted by patch B, whose   data are deleted by patch C etc.   ------------------------------  # Date: Tue, 13 Dec 2005 04:53:31 GMT   From: John Santos <john@egh.com>+ Subject: Re: saving recovery data with PCSI , Message-ID: <ftsnf.23915$Wo2.23830@trnddc04>  / Phillip Helbig---remove CLOTHES to reply wrote: 1 > In article <gvhnf.459$fA3.52@news.cpqcorp.net>, 8 > hammond@not@peek.ssr.hp.com (Charlie Hammond) writes:  >  > : >>You can save recovery data ONLY when installing PATCHES. >  >  > OK.  >  > C >>You can save recovery data for any number of patch installations, E >>provided that ALL the patch installation save recovery data, and NO + >>other install/remove operations intevene.  >>D >>If you install patches A, B and C, saving recovery data, that data >>will be lost if you then >>8 >>    - Install patch D without saving recovery data, or, >>    - Install or remove a layered product. >>K >>PCSI will warn you if you perform an operation that will require removing ! >>previously saved recovery data.  >  > N >>PRODUCT UNDO PATCH can rollback one or more patches for which there is savedM >>recovery data.  The rollback happens in reverse chronological order -- i.e. M >>the reverse of the order in which the patches were installed.  If there is  I >>recoverdy data for more than one patch, you "undo" only the most recent N >>patch(es), or all of them.  However, you cannot "skip" on or more patches --$ >>the removal must be reverse order. >>" >>If this doesn't help, ask again. >  > B > If I apply several patches one after the other, no PCSI logicalsG > defined, and answer the questions so that I can continue, it appears  H > that if I save data for patch A, then it is deleted by patch B, whose " > data are deleted by patch C etc.  ? This is *WRONG*.  However, I think that not all patches ask the A questions anymore.  You should always use the /SAVE_RECOVERY_DATA C qualifier (or use the logical name).  This also greatly reduces the ) amount of boilerplate PCSI prints at you.   < (You aren't deleting the [PCSI$UNDO*] directories, are you?)     --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Mon, 12 Dec 2005 19:58:28 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>  Subject: Re: shadowing questions+ Message-ID: <439E2AC4.A99C9687@comcast.net>    Keith Parris wrote:  >  > Ken Fairfield wrote:H > >> Is there some way to allow a MINICOPY in the case of unplanned node > >> crashes?  ... > >  > >     No.  End of story. > K > If the Shadowing developer has his way, the story will not end like this.    Interesting thought.  H I should think there ought to be a way to recover the bitmap data from a" crash dump and write it to a file.  C For that matter, there ought to be a qualifier for DISMOUNT, to the 
 effect of:  ' /SHADOW_SET/SAVE_BITMAP/OUTPUT=filespec    For example:  = $ DISMOUNT DSA1/SHAD/SAVE/OUT=SYS$SYSDEVICE:[WBM]DSA1_WBM.DAT   - ...or some such, and a counterpart for MOUNT:   , $ MOUNT/SYSTEM DSA1/SHAD=($1$DGA1,$1$DGA10)-' 	/WBM=SYS$SYSDEVICE:[WBM]DSA1_WBM.DAT -  	SHAD01 SHAD01  C (If /WBM was specified on the MOUNT, DISMOUNT should default to the 0 write-bitmap save file specified at MOUNT time.)   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  + Date: Mon, 12 Dec 2005 21:59:04 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)* Subject: SHOW DEVICE: what should it show?$ Message-ID: <dnkrr8$gnj$1@online.de>  I SHOW DEVICE shows a lot of devices, but not all.  For example, not NET*.  F Yes, with SHOW DEVICE NET you can see them, but not with no arguments.   Bug or feature?   ) Is there an easy way to show ALL devices?    ------------------------------    Date: 12 Dec 2005 14:10:58 -0800- From: "Allosaur" <ALLOSAUR@ATHENA.SITECH.COM> . Subject: Re: SHOW DEVICE: what should it show?C Message-ID: <1134425458.095982.235660@g44g2000cwa.googlegroups.com>   F I note BG (TCP/IP) devices also do not appear, nor do MB mailboxes. ItA must be that these virtual devices with no real hardware were not 3 considered important for the "SHOW DEVICE" command.    ------------------------------  # Date: Mon, 12 Dec 2005 22:55:43 GMT # From: hoff@hp.nospam (Hoff Hoffman) . Subject: Re: SHOW DEVICE: what should it show?0 Message-ID: <Pdnnf.523$0P3.403@news.cpqcorp.net>  s In article <1134425458.095982.235660@g44g2000cwa.googlegroups.com>, "Allosaur" <ALLOSAUR@ATHENA.SITECH.COM> writes: G :I note BG (TCP/IP) devices also do not appear, nor do MB mailboxes. It B :must be that these virtual devices with no real hardware were not4 :considered important for the "SHOW DEVICE" command.  I   It was considered that there are usually a gazillion of these devices,  G   and the display of these wasn't something that (most) users wanted to E   see.  (SHOW DEVICE also uses direct access into kernel mode, and it G   passes a buffer back down to user mode for display, so there is also  F   a preference to fit the data within this buffer -- likely due to itsE   sheer age, SHOW DEVICE does not work the way you might expect; it's E   not a loop of $device_scan[w] and $getdvi[w] system service calls.)   G   Devices with the MBX bit set within the UCB are among those filtered  G   by the kernel-mode code, and this accounts for most of (all of?) the     devices cited.  F   Adding /SELECT, maybe, with a default of the current behaviour, and B   some set of keywords to allow different selection criteria to beD   requested, might well be a reasonable enhancement suggestion, for H   those that wanted to see a list of every device name.  (Folks writing G   DCL command procedures seeking devices should be using the available  G   DCL lexical functions of course, and these can and do allow access to ,   the names of all of the devices present.)   H   (I thought about SHOW DEVICE/ALL here, but that would tend to collide *   with the existing /ALLOCATED qualifier.)    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------G        Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[\0100]hp.com    ------------------------------  + Date: Mon, 12 Dec 2005 23:43:44 +0000 (UTC) - From: klewis@OMEGA.MITRE.ORG (Keith A. Lewis) . Subject: Re: SHOW DEVICE: what should it show?. Message-ID: <dnl1vg$k46$2@newslocal.mitre.org>   helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes in article <dnkrr8$gnj$1@online.de> dated Mon, 12 Dec 2005 21:59:04 +0000 (UTC):J >SHOW DEVICE shows a lot of devices, but not all.  For example, not NET*. G >Yes, with SHOW DEVICE NET you can see them, but not with no arguments.  >  >Bug or feature?  ( Feature.  A relatively new one, I think.  * >Is there an easy way to show ALL devices?   $ show dev a $ show dev b $ show dev c $ show dev d $ show dev e ..  0 --Keith Lewis              klewis {at} mitre.org> The above may not (yet) represent the opinions of my employer.   ------------------------------    Date: 12 Dec 2005 16:05:32 -0800$ From: "AEF" <spamsink2001@yahoo.com>. Subject: Re: SHOW DEVICE: what should it show?B Message-ID: <1134432332.393178.83970@z14g2000cwz.googlegroups.com>   Hoff Hoffman wrote:  [...] G >   Adding /SELECT, maybe, with a default of the current behaviour, and D >   some set of keywords to allow different selection criteria to beE >   requested, might well be a reasonable enhancement suggestion, for I >   those that wanted to see a list of every device name.  (Folks writing H >   DCL command procedures seeking devices should be using the availableI >   DCL lexical functions of course, and these can and do allow access to - >   the names of all of the devices present.)  > I >   (I thought about SHOW DEVICE/ALL here, but that would tend to collide , >   with the existing /ALLOCATED qualifier.)    $ Well, how about SHOW DEVICE/EVERY !?  1 Or make it like DIR/SIZE=ALL vs. DIR/SIZE=ALLO !.    ------------------------------    Date: 12 Dec 2005 16:09:12 -0800$ From: "AEF" <spamsink2001@yahoo.com>. Subject: Re: SHOW DEVICE: what should it show?C Message-ID: <1134432552.839909.100110@o13g2000cwo.googlegroups.com>    Keith A. Lewis wrote:  > helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes in article <dnkrr8$gnj$1@online.de> dated Mon, 12 Dec 2005 21:59:04 +0000 (UTC):K > >SHOW DEVICE shows a lot of devices, but not all.  For example, not NET*. I > >Yes, with SHOW DEVICE NET you can see them, but not with no arguments.  > >  > >Bug or feature? > * > Feature.  A relatively new one, I think.   Same as on VAX/VMS V6.1:   $ FILT UPTIME SH SYS- %FILTER-I, SEARCHing for UPTIME from $ SH SYS B VAX/VMS V6.1  on node NODEX  13-DEC-2005 00:02:04.15   Uptime  100 00:04:14 $ SHOW DEV NET  . Device                  Device           Error.  Name                   Status           Count. NET0:                   Mounted              0. NET1:                   Mounted              0. NET4:                   Mounted              0. NET5:                   Mounted              0. NET6:                   Mounted              0. NET8:                   Mounted              0. NET10:                  Mounted              0. NET7326:                Mounted              0 $    > , > >Is there an easy way to show ALL devices? >  > $ show dev a > $ show dev b > $ show dev c > $ show dev d > $ show dev e > ..    That's simple, but not easy! :-)   ------------------------------    Date: 12 Dec 2005 15:42:36 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 9 Subject: Re: Timeout strategy: terminal vs Telnet drivers 3 Message-ID: <Cz0xcID7JEdJ@eisner.encompasserve.org>   \ In article <439D9BB8.2403BE03@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: > Bob Koehler wrote:M >>    Post a _hughe_ read, and process according to the actual size read when  >>    the read completes.  > . > What causes a read to complete  for TCPIP ?  > I > If I request a read of 500 characters and the system at the other sends 0 > only 400, what/how/why does my read complete ?  H    The read completes when the block is received, no matter what size itI    is.  If you are working on a single LAN segment this will probably be  G    the same size as the write at the sending end.  If there is a router !    in between it can be any size.   H    A network protocol is not a stream of bytes, even if C tends to treat    it that way sometimes.    ------------------------------  % Date: Mon, 12 Dec 2005 19:34:17 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 9 Subject: Re: Timeout strategy: terminal vs Telnet drivers , Message-ID: <439E16E7.75DDA58A@teksavvy.com>   Bob Koehler wrote:J >    The read completes when the block is received, no matter what size it >    is.    By "block" you mean "packet" ???  D From what I had read some time ago, it was written that one couldn'tA make any assumption about the contents of a read.But if it can be G confirmed that a read works at the TCPIP packet level, then in a telnet C type of interactive connectiuon, the server could count on a packet 2 being sent when the user presses RETURN, correct ?   ------------------------------  % Date: Mon, 12 Dec 2005 21:13:02 -0500 # From: "Dan Allen" <dallen@nist.gov> 9 Subject: RE: Timeout strategy: terminal vs Telnet drivers : Message-ID: <JFEPKAPBPMDFDBOIANGDMEIHHBAA.dallen@nist.gov>   > -----Original Message-----6 > From: JF Mezei [mailto:jfmezei.spamnot@teksavvy.com]) > Sent: Monday, December 12, 2005 7:34 PM  > To: Info-VAX@Mvb.Saic.Com ; > Subject: Re: Timeout strategy: terminal vs Telnet drivers  >  >  > Bob Koehler wrote:L > >    The read completes when the block is received, no matter what size it
 > >    is. > " > By "block" you mean "packet" ??? > F > From what I had read some time ago, it was written that one couldn'tC > make any assumption about the contents of a read.But if it can be I > confirmed that a read works at the TCPIP packet level, then in a telnet E > type of interactive connectiuon, the server could count on a packet 4 > being sent when the user presses RETURN, correct ? >   P Well I missed some intermediate message in theis thread packets are invisible toL the application. You have no way or need to know where TCP packet boundariesM are. You're making this way to complicated. A TCP socket is a byte stream and P Telnet runs over a TCP socket. Bytes are sent as they are typed by the user withN only a VERY small inter-character delay to allow for the possibility of savingM network overhead by sending multiple data bytes in a single TCP packet. CR is  just another data byte.   N Now WRT reading a Telnet (TCP) stream. If you issue a read requesting one byteM it doesn't return until one byte is received. If you ask for two it waits for O two, etc. If you ask for n and fewer than n have been received it waits until n P are available UNLESS you set the socket "non-blocking". When a read is issued toO a non-blocking TCP socket the read returns IMMEDIATELY with what ever number of P bytes if any that have been received (up to a max of the number you requested)atJ that instant. YOU have to check the return value to determine how many youJ actually received. If you need to know where an end of line (CR) is in theM stream YOU have to check each byte as you receive it. If you need to time out N the process sending the data YOU have to keep a timer in your read loop. THERE) IS NO INHERENT BLOCK OR RECORD STRUCTURE.    Dan    ------------------------------  + Date: Tue, 13 Dec 2005 03:46:31 +0000 (UTC) 7 From: moroney@world.std.spaamtrap.com (Michael Moroney) 9 Subject: Re: Timeout strategy: terminal vs Telnet drivers ( Message-ID: <dnlg6n$5eo$1@pcls4.std.com>  % "Dan Allen" <dallen@nist.gov> writes:   Q >Well I missed some intermediate message in theis thread packets are invisible to M >the application. You have no way or need to know where TCP packet boundaries N >are. You're making this way to complicated. A TCP socket is a byte stream andQ >Telnet runs over a TCP socket. Bytes are sent as they are typed by the user with O >only a VERY small inter-character delay to allow for the possibility of saving N >network overhead by sending multiple data bytes in a single TCP packet. CR is >just another data byte.  O >Now WRT reading a Telnet (TCP) stream. If you issue a read requesting one byte N >it doesn't return until one byte is received. If you ask for two it waits forP >two, etc. If you ask for n and fewer than n have been received it waits until nQ >are available UNLESS you set the socket "non-blocking". When a read is issued to P >a non-blocking TCP socket the read returns IMMEDIATELY with what ever number ofQ >bytes if any that have been received (up to a max of the number you requested)at  >that instant.  H A VMS QIO READVBLK with IO$M_TIMED specified, and time (P3 parameter, I F think) equal to 0 will give you whatever is in the typahead buffer (upF to the smaller of the buffer size/the typeahead size SYSGEN parameter)B and not wait at all for anything further.  This is how to get the " nonblocking behavior through $QIO.   ------------------------------    Date: 12 Dec 2005 22:17:57 -0800 From: dooleys@snowy.net.au9 Subject: Re: Timeout strategy: terminal vs Telnet drivers C Message-ID: <1134454677.069668.171280@o13g2000cwo.googlegroups.com>   6 a telnet packet is sent for every keystroke (and echo) Phil   ------------------------------  % Date: Mon, 12 Dec 2005 14:01:09 -0500 , From: Forrest Kenney <Forrest.Kenney@hp.com>L Subject: Re: USB on OpenVMS (was: Re: DS10L hardware configuration question)& Message-ID: <439DC8F5.166CFCB4@hp.com>   > H > So I guess it was like the ISDN port on the old Flamingos (or did that) > work but there was never a VMS driver?)  > F > If it didn't work and support never offered, I'm surprised it wasn't" > quickly "value engineered" away. >   ? 	It was not like the ISDN port there was an OpenVMS driver for  E it.  There were some issues with it but nothing killer just annoying. D The hardware group was looking to remove users of DMA bandwidth and E the USB was an easy on to turn off.  There was nothing that required  4 it so they went and hid the controller from the O.S.   > >  The PCIO > >  USB card is the approach, if you want to add and use USB in an unsupported B > >  fashion on those AlphaServer systems that lack supported USB. > N > >  The USB PCI cards are variously offered for US$10 or so, and usually wellM > >  under US$30, based on various prices I've seen.  (I am not counting what O > >  I saw offered at Singapore's Sim Lim City -- PCI USB cards were absolutely O > >  everywhere, as was pretty much any other electronic device you might want.  > H > Which ones work with the OpenVMS USB driver?  Do they all work or onlyL > ones with certain chips, or only certain cards or whatever?  I see severalK > kinds of those cards in places like CompUSA/Best Buy/Circuit City as well  > as PC shows. > 6 > I have another Alpha I could plug a USB PCI card in.  @ 	What cards work is a bit tricky partly because they change all H the time and partly because we have picked up cards over time.  So there6 are more that will work with V8.2 than will with V7.3.   	Symbios		60800 
 	CMD		6730 	Acer	 	Phlips*		ISP 1561 	NEC*	 	Lucent/agere*	USS344   A 	I have tested all of these at one time or another the ones with  H "*" all work with V8.2 of OpenVMS without any user intervention.  Other H require that an entry be created for them in sys$user_config.dat.  Also H this is not an all inclusive list folks have stopped by with cards that G we tried briefly that appeared to work well but I did not have time to  H really test.  The key is all of them are base on the OHCI UCB controller model.  = 	When V8.3 ships there will be three new USB drivers two for  C USB to RS232 device and one to allow folks to add support to custom E USB devices.  I presently have two example programs that use the USB  D Generic driver and a thrid one that I hope to get ready in time for  V8.3.      Forrest    ------------------------------  + Date: Mon, 12 Dec 2005 14:17:36 -0600 (CST) * From: sms@antinode.org (Steven M. Schweda)L Subject: Re: USB on OpenVMS (was: Re: DS10L hardware configuration question)2 Message-ID: <05121214173666_2024716B@antinode.org>  7 From: moroney@world.std.spaamtrap.com (Michael Moroney)   I > Which ones work with the OpenVMS USB driver?  Do they all work or only  L > ones with certain chips, or only certain cards or whatever?  I see severalK > kinds of those cards in places like CompUSA/Best Buy/Circuit City as well  > as PC shows.  E    All this recent discussion led me to run the experiment with a $10 F (including S&H) 5-port card from an Ebay seller, and it seemed to workC about as well as I could expect, as I have almost no USB stuff with H which to do any serious testing.  (Things appeared in the configuration,D and the USB log showed events with appropriare device identifiers.) : That was on my spare/experimental XP1000 running VMS V8.2.  G    My guess is that any of the cheap Chinese cards which say "NEC chip" E on them will be fine.  The (NEC) <mu>PD720101 seems to be the popular E chip on all the cheap cards, and that's one of the approved chips, as  reported in this forum.   H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode-org     Saint Paul  MN  55105-2547    ------------------------------  # Date: Mon, 12 Dec 2005 19:48:00 GMT # From: hoff@hp.nospam (Hoff Hoffman) L Subject: Re: USB on OpenVMS (was: Re: DS10L hardware configuration question)0 Message-ID: <Qtknf.502$6E3.380@news.cpqcorp.net>  !   The USB hardware does not work.   *   This is not a device driver restriction.  G   This non-functional USB hardware was never an official nor documented F   part of the particular products, as was stated in my earlier reply, G   and this is again included here to avoid being quoted out of context.   G   On those Alpha and Integrity servers where USB was sold as being part F   of the product, it is enabled and it does work, or -- as is the caseD   for supported devices that do not work -- we can and will make the9   device functional, or will otherwise address the issue.   F   Put in other words, I have no personal interest in attempting nor inF   using the USB on these particular systems.  I do use USB on OpenVMS,F   and -- for use on one of the Alpha systems where USB was disabled --I   I specifically purchased one of the aforementioned USB PCI controllers.   N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------G        Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[\0100]hp.com    ------------------------------  % Date: Mon, 12 Dec 2005 15:22:46 -0500 * From: "FredK" <fred.nospam@nospam.dec.com>L Subject: Re: USB on OpenVMS (was: Re: DS10L hardware configuration question), Message-ID: <439ddc17$1@usenet01.boi.hp.com>  6 The easiest to find in the US - Belkin F5U220.  $29.62    < http://www.walmart.com/catalog/product.do?product_id=2470580    9 "Forrest Kenney" <Forrest.Kenney@hp.com> wrote in message   news:439DC8F5.166CFCB4@hp.com... > > J > > So I guess it was like the ISDN port on the old Flamingos (or did that+ > > work but there was never a VMS driver?)  > > H > > If it didn't work and support never offered, I'm surprised it wasn't$ > > quickly "value engineered" away. > >  > ? > It was not like the ISDN port there was an OpenVMS driver for G > it.  There were some issues with it but nothing killer just annoying. E > The hardware group was looking to remove users of DMA bandwidth and F > the USB was an easy on to turn off.  There was nothing that required6 > it so they went and hid the controller from the O.S. >  > > >  The PCIE > > >  USB card is the approach, if you want to add and use USB in an  unsupported D > > >  fashion on those AlphaServer systems that lack supported USB. > > K > > >  The USB PCI cards are variously offered for US$10 or so, and usually  wellJ > > >  under US$30, based on various prices I've seen.  (I am not counting whatF > > >  I saw offered at Singapore's Sim Lim City -- PCI USB cards were
 absolutelyK > > >  everywhere, as was pretty much any other electronic device you might  want.  > > J > > Which ones work with the OpenVMS USB driver?  Do they all work or onlyF > > ones with certain chips, or only certain cards or whatever?  I see several H > > kinds of those cards in places like CompUSA/Best Buy/Circuit City as well > > as PC shows. > > 8 > > I have another Alpha I could plug a USB PCI card in. > @ > What cards work is a bit tricky partly because they change allJ > the time and partly because we have picked up cards over time.  So there8 > are more that will work with V8.2 than will with V7.3. >  > Symbios 60800 
 > CMD 6730 > Acer > Phlips* ISP 1561 > NEC* > Lucent/agere* USS344 > A > I have tested all of these at one time or another the ones with I > "*" all work with V8.2 of OpenVMS without any user intervention.  Other I > require that an entry be created for them in sys$user_config.dat.  Also I > this is not an all inclusive list folks have stopped by with cards that H > we tried briefly that appeared to work well but I did not have time toJ > really test.  The key is all of them are base on the OHCI UCB controller > model. > = > When V8.3 ships there will be three new USB drivers two for E > USB to RS232 device and one to allow folks to add support to custom F > USB devices.  I presently have two example programs that use the USBE > Generic driver and a thrid one that I hope to get ready in time for  > V8.3.  >  > 	 > Forrest    ------------------------------  % Date: Mon, 12 Dec 2005 15:57:10 -0500 * From: "FredK" <fred.nospam@nospam.dec.com>L Subject: Re: USB on OpenVMS (was: Re: DS10L hardware configuration question), Message-ID: <439de427$1@usenet01.boi.hp.com>  H Well, when V8.3 comes out - there will be a Joystick driver to play withF (complements of Paul, Forrest and I) and I also wrote a little libraryK interface for it (included in source form) that will handle (via some ASCII J data files) normalization of various joysticks, as well as specific deviceH range and zero offset correction.  I also have a modified OpenGLUT imageI that supports it and a SKYFLY OpenGL/GLUT example that has been hacked to  work pretty well with it.   F For more serious efforts, Forrest has created a generic driver that isL sort-of a "GK" equivalent (lets you read/write directly to the device) along with some examples.   I If we get some time, we are also hacking around with a fingerprint reader K using the generic driver as an example.  There are all kinds of strange and G wacky USB devices - like a scale from Radio Shack.  The biggest problem I generally is a lack of any documentation from the device makers - so from L scratch you tend to need a PC and a USB analyzer to snoop the traffic of theJ device in-use on a PC to figure out how to program it - and then guess how to decode the data it sends.  K I'm also looking at at least supporting tablets as mouse equivalents... and H "thinking" about doing a XInput extension to support them in "digitizer" mode.   G But out-of-the-box, many disks and pen devices will work.  As will most $ asynch serial terminal dongle/muxes.    7 "Steven M. Schweda" <sms@antinode.org> wrote in message , news:05121214173666_2024716B@antinode.org...9 > From: moroney@world.std.spaamtrap.com (Michael Moroney)  > J > > Which ones work with the OpenVMS USB driver?  Do they all work or onlyF > > ones with certain chips, or only certain cards or whatever?  I see several H > > kinds of those cards in places like CompUSA/Best Buy/Circuit City as well > > as PC shows. > G >    All this recent discussion led me to run the experiment with a $10 H > (including S&H) 5-port card from an Ebay seller, and it seemed to workE > about as well as I could expect, as I have almost no USB stuff with J > which to do any serious testing.  (Things appeared in the configuration,E > and the USB log showed events with appropriare device identifiers.) < > That was on my spare/experimental XP1000 running VMS V8.2. > I >    My guess is that any of the cheap Chinese cards which say "NEC chip" G > on them will be fine.  The (NEC) <mu>PD720101 seems to be the popular G > chip on all the cheap cards, and that's one of the approved chips, as  > reported in this forum.  > J > ------------------------------------------------------------------------ > 6 >    Steven M. Schweda               (+1) 651-699-98185 >    382 South Warwick Street        sms@antinode-org  >    Saint Paul  MN  55105-2547    ------------------------------  % Date: Mon, 12 Dec 2005 16:24:23 -0500 , From: Forrest Kenney <Forrest.Kenney@hp.com>L Subject: Re: USB on OpenVMS (was: Re: DS10L hardware configuration question)& Message-ID: <439DEA87.8842EE7C@hp.com>  8 	No clustering or DECnet over USB.  We did get a USB to ? ethernet device working a long time ago.  The problem with most A of the USB to wireless or ethernet is they use a vendor specific  A protocol.  So you need help from the vendor or lots of time with  @ a USB bus analyzer to make them work.  Then the next model that + comes out you need to do it all over again.   : 	I admit to having given some thought to USB to bluetooth A but it is more work than I can easily fit in right now.  The next C midnight hack is a USB fingerprint reader.  But it all depends upon * how busy I am on the weekends this winter.   Forrest    Bill Gunshannon wrote: > > > Not that I have the hardware to do it or anything, but...... > E > Does VMS support things like Clustering or running DECNET over USB? D > Just curious as I know that Linux/BSD both support networking overD > USB or Firewire (not that I have ever seen it work successfully!!) >  > bill >  > --L > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesF > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > University of Scranton   |@ > Scranton, Pennsylvania   |         #include <std.disclaimer.h>   ------------------------------  % Date: Tue, 13 Dec 2005 08:01:31 +0800 3 From: "Richard Maher" <maher_rj@hotspamnotmail.com> L Subject: Re: USB on OpenVMS (was: Re: DS10L hardware configuration question)1 Message-ID: <dnl32b$jje$1@news-02.connect.com.au>   	 Hi Steve,    >   (I am not counting what C >   I saw offered at Singapore's Sim Lim City -- PCI USB cards were 
 absolutelyH >   everywhere, as was pretty much any other electronic device you might want. I >   Singapore was part of the Asia Pacific portion of this year's OpenVMS L >   Technical Update Days (TUD), and Sim Lim City is certainly computer geek >   heaven.  But I digress.)  I Not up to Sue's standard, (but not bad for a first timer :-) Feel free to 8 digress. I'm sure I'm not the only one who's interested.   Regards Richard Maher   0 "Hoff Hoffman" <hoff@hp.nospam> wrote in message* news:J_hnf.469$Lv3.375@news.cpqcorp.net...J > In article <dn84tr$i9v$1@pcls4.std.com>, moroney@world.std.spaamtrap.com (Michael Moroney) writes:  > F > :I'm kinda peeved that the USB on the DS10L seems to be deliberately8 > :disabled so I can't even play with unsupported stuff. > G >   I was discouraged, as well.  Unfortunately, the latent USB hardware  (whichK >   was never supported, and was never part of the advertised product, BTW) E >   didn't work, and a decision was made to disable it rather than to  receive F >   and to process the problem reports that were to be expected if the hardwareL >   was left visble and potentially enabled -- even if unsupported.  The PCIB >   USB card is the approach, if you want to add and use USB in an unsupported A >   fashion on those AlphaServer systems that lack supported USB.  > H >   The USB PCI cards are variously offered for US$10 or so, and usually wellL >   under US$30, based on various prices I've seen.  (I am not counting whatC >   I saw offered at Singapore's Sim Lim City -- PCI USB cards were 
 absolutelyH >   everywhere, as was pretty much any other electronic device you might want. I >   Singapore was part of the Asia Pacific portion of this year's OpenVMS L >   Technical Update Days (TUD), and Sim Lim City is certainly computer geek >   heaven.  But I digress.) > K >   The USB on the Integrity servers and on specific AlphaServer systems is @ >   supported, does work, and is part of the advertized product. >  > ( >  ---------------------------- #include' <rtfaq.h> ----------------------------- 4 >     For additional, please see the OpenVMS FAQ --  www.hp.com/go/openvms/faq , >  --------------------------- pure personal# opinion --------------------------- I >        Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[\0100]hp.com  >    ------------------------------  % Date: Mon, 12 Dec 2005 17:05:39 +0000 ! From: Baldrick <none@[127.0.0.1]> & Subject: VAX 7000 EXA0 device offline?' Message-ID: <dnkal9$1pq$1@lore.csc.com>   B To cut a long story short, I've got a VAX 7000 which is presently : connected using the FDDI (FXA, FXB) and it's working fine.  I We've not had the 10 MB AUI connected for a long time, and I now need to  F use it, however the device EXA0 is showing as OFFLINE. I've plugged a H working cable in, and a little block with a green light on, it supplies  power but just reports OFFLINE.   3 There is nothing in LANCP database to disable this.   E This is VAX/VMS 7.1 with the most recent patches applied, it's a VAX   7860 (SMP).   B We also need this to work for FlexLM licensed software (duh), the I LM_HOSTID program returns the VMS error code saying "device offline, not  # in configuration or not available".   E What may or may not be related was the DWLMA board was replaced some  B months ago. We also have installed a couple of the Nemonix 100 MB . Ethernet cards and they are working just fine.   Any suggestions? --  E Regards, Nic Clews a.k.a. Mr. Car Park Charges, CSC Computer Sciences  nclews at csc dot com    ------------------------------    Date: 12 Dec 2005 13:31:13 -0800 From: andrew@floatingbear.ca; Subject: VMS/Pony Express Mail - Exchange Formatting Issues B Message-ID: <1134423073.302694.93140@g44g2000cwa.googlegroups.com>  C We recently connected our VMS box running Pony Express for the mail D transport between VMS mail and the rest of the world directly to our Exchange server.  D Everything is working just wonderfully except that the CRLF pairs inE reports are being treated as two lines.  Does anyone know of a way to , correct this?  My users are getting annoyed.   Andrew Butchart  andrew@floatingbear.ca   ------------------------------   End of INFO-VAX 2005.692 ************************