1 INFO-VAX	Tue, 13 Jun 2006	Volume 2006 : Issue 327       Contents: Re: Accounting question  Re: Accounting question  Re: Accounting question  ANN: PWAIT_SDA freeware updateP Re: Brokeback Mountain II - The IT Guys  (Was Re: So how representative is this ' RE: Cost of used alphas vs 8086+charron ' Re: Cost of used alphas vs 8086+charron ' Re: Cost of used alphas vs 8086+charron ' Re: Cost of used alphas vs 8086+charron ' Re: Cost of used alphas vs 8086+charron 1 Re: DECwindows server: why the change of username  HSG80 Serial connection  Re: HSG80 Serial connection  Re: HSG80 Serial connection ) OPEN failed when compiled with /CHECK=ALL 4 Re: Rdb, standard vs. multiversion and link problems4 Re: Rdb, standard vs. multiversion and link problems< Re: SimH 3.6-0 (problems compiling VAX using MinGW) RESOLVED VMS Compatible KVM switch  Re: VMS Compatible KVM switch ' Re: VMS, XDM, and remote connections... ' Re: VMS, XDM, and remote connections... ' Re: VMS, XDM, and remote connections...   F ----------------------------------------------------------------------  % Date: Tue, 13 Jun 2006 14:32:27 +0200 , From: "Ferry Bolhar" <bol@adv.magwien.gv.at>  Subject: Re: Accounting question5 Message-ID: <1150201948.353390@proxy.dienste.wien.at>   	 JF Mezei:   C > Could you provide just a quick description of the live capture of F > auditing messages ? Someone mentioned a mailbox. I assume one uses aG > system service to register a mailbox device to receive audit events ?   > Which system service is that ?  + I looked at the docs now, and I found this:   F x) Write a daemon which creates a mailbox and assigns a logical to it.  ; x) Use the SET AUDIT/LISTENER=<name> command to define this J mailbox as listener to the audit server (<name> is the previously assigned	 logical).   < x) In your daemon, issue a $QIO[W] IO$_READVBLK to read fromD the mailbox and trap records as they arrive. Anaylze the records and do whatever you want.   B > (from there one can more easily find te relevant documentation). > A > Also, has there ever been consideration for a more direct OPCOM E > interface for applications ? (getting them via a mailbox in a "raw" H > form, as opposed to declaring a virtual terminal and getting formatted# > messages destined for terminals).   - Yes, this would be an intersting enhancement.    Kind greetings,    Ferry    --   Ing. Ferry Bolhar % Municipality of Vienna, Department 14  A-1010 Vienna / AUSTRIA  E-mail: bol@adv.magwien.gv.at    ------------------------------    Date: 13 Jun 2006 08:03:12 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen)   Subject: Re: Accounting question3 Message-ID: <LntbE78wGgUO@eisner.encompasserve.org>   d In article <1150201948.353390@proxy.dienste.wien.at>, "Ferry Bolhar" <bol@adv.magwien.gv.at> writes: > JF Mezei:   B >> Also, has there ever been consideration for a more direct OPCOMF >> interface for applications ? (getting them via a mailbox in a "raw"I >> form, as opposed to declaring a virtual terminal and getting formatted $ >> messages destined for terminals). > / > Yes, this would be an intersting enhancement.   E It would be an interesting bit of nostalgia.  Prior to VMS V5.4 using C OPCOM output was the only way to get an audit log.  Personally I do 6 not desire to return to the unstructured bad old days.   ------------------------------  # Date: Tue, 13 Jun 2006 14:02:57 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>  Subject: Re: Accounting question2 Message-ID: <lAzjg.1811$tt7.1751@news.cpqcorp.net>  G    We've multiple parallel notification paths for security audits, for  G operator communications, for cluster events, and (albeit undocumented)  @ for system error events -- these for example.  There are others.  H    There have been considerations and discussions around resolving some @ of this parallelism, and around the ability to receive operator & communications via mailbox or similar.  I    Personally (opinion ahead), I'd toss the innards of the current OPCOM  I operator communications system (it's basically original to the operating  E system), and replace it -- whilst also obviously keeping the current  H APIs functional, of course.  The existing OPCOM operator communications F mechanisms are entirely functional -- though somewhat crufty, and (as A has been occasionally pointed out) not fully up to what was then  F available on TOPS when the OpenVMS operator communications system was A designed and implemented.  If I had my way (and enough cycles to  I complete the work), you'd be seeing XML and/or SNMP by now, for auditing  F and operator communications and process events and errors and such -- F but there is other OpenVMS work presently priority tasked in front of 
 this work.  E    If a unified communications mechanism is something that y'all are  F interested in having in a future release, that's certainly fodder for H increasing the priority of the related engineering work.  That's fodder L for direct requests into your HP rep/reseller or into the HP support center.      --   G    As for a source code example of receiving audits, here's an old one:   O http://h18000.www1.hp.com/support/asktima/appl_tools/CHAMP_SRC931102006764.html    ------------------------------  % Date: Tue, 13 Jun 2006 09:37:52 -0500 - From: Hunter Goatley <goathunter@goatley.com> ' Subject: ANN: PWAIT_SDA freeware update * Message-ID: <448ECDC0.6030100@goatley.com>  B The following package has been updated in my VMS freeware archive:  
 pwait_sda.zip A   Description:   SDA extension to help investigate hung processes 7                  on a running system or in a crash dump    Version:       V1.0 6   Author:        Ian Miller <MILLER@Encompasserve.org>   Architecture:  AXP,IA64    Size:          328 blocks    Language:      C  8 This version includes lots of improvement and bug fixes. Thanks, Ian!   http://www.process.com/openvms/   9 ftp://ftp.process.com/vms-freeware/fileserv/pwait_sda.zip > http://vms.process.com/ftp/vms-freeware/fileserv/pwait_sda.zip  5 ftp://ftp.tmk.com/vms-freeware/fileserv/pwait_sda.zip : http://www.tmk.com/ftp/vms-freeware/fileserv/pwait_sda.zip   And on the other mirrors soon. --     Hunter ------9 Hunter Goatley, Process Software, http://www.process.com/ B PreciseMail Anti-Spam Gateway for OpenVMS, Tru64, Solaris, & Linux9 goathunter@goatley.com     http://www.goatley.com/hunter/    ------------------------------  % Date: Tue, 13 Jun 2006 07:47:57 -0700 # From: "Tom Linden" <tom@kednos.com> Y Subject: Re: Brokeback Mountain II - The IT Guys  (Was Re: So how representative is this  ) Message-ID: <op.ta2917vzzgicya@hyrrokkin>   I On Tue, 13 Jun 2006 07:36:04 -0700, John Reagan <john.reagan@hp.com> wro=  te:    > Richard Maher wrote: > I >> Most COBOL sites I know of compile for /NOALIGNMENT and let the compi=  ler I >> generate the bazillion extra instructions needed to prevent an alignm=  ent 	 >> fault.  > I > I wouldn't say bazillion.  1 instruction for an aligned longword fetch=  ,  =  H > 7 instructions for an unaligned longword fetch (including two LDQ_U  =  I > instructions).  So you might cause more cache misses, more data moving=    =   C > from memory, etc.  Not pretty, certainly slower, not a bazillion.  > G >> Curious. Did Don Braffit die at his keyboard due to underfunding and I >> atrophy? Any point in asking the new-broom for a list of new features=    =    >> that I >> are coming up for COBOL (Local Storage? Recursion? Conforming to late=  st >> standards?)I >>  Don't get me wrong, I'm over the moon if you're in charge of COBOL! =   =   >> (As long ' >> as you haven't had to give up MACRO)  > I > Don took the early retirement package last fall.  He recently landed a=    =   I > teaching position at a small school in Virginia.  It was something he =   =   > wanted to do.  > I > I picked up COBOL and the sorts (SORT & Hypersort) from Don.  I still =   =  I > have Pascal and Macro-32.  I think I can juggle all of them.  I just  =   I > finished a Pascal release and I'm all done with Macro-32 with regards =  to  =   I > what will ship with 8.3.  I'm ready for my "Summer of COBOL" (sounds  =   ' > like a bad Frankie Avalon movie, eh?)  >  More like Friday the 13th :-)    ------------------------------  % Date: Mon, 12 Jun 2006 23:28:30 -0400 ' From: "Main, Kerry" <Kerry.Main@hp.com> 0 Subject: RE: Cost of used alphas vs 8086+charronT Message-ID: <FA60F2C4B72A584DBFC6091F6A2B86840155E7AD@tayexc19.americas.cpqcorp.net>   > -----Original Message-----9 > From: JF Mezei [mailto:jfmezei.spamnot@teksavvy.com]=20  > Sent: June 12, 2006 5:21 PM  > To: Info-VAX@Mvb.Saic.Com 2 > Subject: Re: Cost of used alphas vs 8086+charron >=20 > Dave Froble wrote:> > > It's really going to depend upon what CAN be used.  The=20 > itanics aren't> > > real expensive, and the licensing is a better deal than=20 > it's ever been@ > > on VAX or Alpha.  As the VMS people tell us, and others have > > experienced, it does work. >=20 >=20H > Post end-of-sales, the success of a platform depends on how many unitsF > had been sold during the platform's lifetime.  Even within the VAX's: > lifetime, you find that there are fewer "newer" VAXEs=20 > available compared? > to VAXes that date from the heydays of VMS when sales were=20  > much higher. >=20? > For the sake of discussion, should IA64 be end of saled on=20  > the same date F > as Alpha (in a couple of months), the Alpha market would continue to6 > thrive while the IA64 market would wither very fast. >=20G > This is a bit like TV programs. Once you've produced enough episodes, ? > you can go into syndication after you've stopped producing=20  > new ones andB > the program lives on in reruns.  Once enough VAXes or Alphas are1 > produced, there is an after market that exists.  >=20; > With IA64, I am not sure that there will be much of an=20  > aftermarket. TheC > platform won't have lasted long enough to really make a long term ' > survival after the product is killed.  >=20@ > Remember that there is no or little software that runs only=20 > on that IA64D > thing.  There is software that runs only on VAX, and there is some- > software that runs on Alpha but not on VAX.  >=20   JF,   6 What would you say to all these OpenVMS/IA64 vendors -9 http://h71000.www7.hp.com/openvms/integrity/partners.html F http://h71000.www7.hp.com/solutions/matrix/i64partner_A.html (click on each letter ..)    Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  4 OpenVMS - the secure, multi-site OS that just works.   ------------------------------  % Date: Tue, 13 Jun 2006 02:41:59 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 0 Subject: Re: Cost of used alphas vs 8086+charron, Message-ID: <448E5E09.4C2A9015@teksavvy.com>   "Main, Kerry" wrote:8 > What would you say to all these OpenVMS/IA64 vendors -; > http://h71000.www7.hp.com/openvms/integrity/partners.html H > http://h71000.www7.hp.com/solutions/matrix/i64partner_A.html (click on > each letter ..)   F For the used market, what counts is not how many retailers there were,, but how many units were put onto the market.  A IA64 is at the same stage now as Digital's first year into the PC N market: great growth numbers happen because you are starting with low numbers.  B Assuming IA64 is announced end-of -life in 2007, with end of salesC possibly in 2009, there won't have been that many units sold. Also, A because of the premature widthdrawal from the low end/workstation < market, there will not be that many units for hobbyists etc.  G Selling 1 machine to 100 cutsomers who each have 10 alphas is basically A just selling evaluation/test machines. Selling 100 machines to 10 D customers means you are really replacing 10 alphas at each customer.   ------------------------------  % Date: Mon, 12 Jun 2006 14:54:28 -0400 * From: "FredK" <fred.nospam@nospam.dec.com>0 Subject: Re: Cost of used alphas vs 8086+charron, Message-ID: <448db864$1@usenet01.boi.hp.com>  : "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message& news:448DB6C3.790C027E@teksavvy.com... > E > Didn't DEC engineers have one early on VAX to start developping the I > Alpha software before alphas were available ? Perhaps that could be put  > into the freeware ?  >   G Yes, but the emulator (Manniquin) had many limits - including a lack of  floating point IIRC.   ------------------------------  % Date: Tue, 13 Jun 2006 08:09:42 -0400 ' From: Dave Froble <davef@tsoft-inc.com> 0 Subject: Re: Cost of used alphas vs 8086+charron9 Message-ID: <EJKdnY7QTKNoNBPZnZ2dnUVZ_t2dnZ2d@libcom.com>    Main, Kerry wrote:   > JF,  > 8 > What would you say to all these OpenVMS/IA64 vendors -; > http://h71000.www7.hp.com/openvms/integrity/partners.html H > http://h71000.www7.hp.com/solutions/matrix/i64partner_A.html (click on > each letter ..)   H Why do you even bother?  JF lives in his own little world where reality E is whatever he says it is.  In that world the itanic is already dead.    --  4 David Froble                       Tel: 724-529-0450> Dave Froble Enterprises, Inc.      E-Mail: davef@tsoft-inc.com DFE Ultralights, Inc.  170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  # Date: Tue, 13 Jun 2006 13:28:50 GMT 1 From: Keith Parris <keithparris_NOSPAM@yahoo.com> 0 Subject: Re: Cost of used alphas vs 8086+charron2 Message-ID: <m4zjg.1810$8c7.1227@news.cpqcorp.net>   JF Mezei wrote: E > Didn't DEC engineers have one early on VAX to start developping the / > Alpha software before alphas were available ?   F I used the Mannequin emulator a few times. It took 30 minutes just to H get to the VMS startup banner. Granted, later VAX systems were somewhat G faster, but it would still run slowly. I was very glad when about that  D time we received the Application Development Units (ADUs) with EV-3 I chips, which although lacking floating-point hardware, ran at reasonable  & speeds for porting and debugging work.   ------------------------------  % Date: Mon, 12 Jun 2006 15:14:20 -0400 * From: "FredK" <fred.nospam@nospam.dec.com>: Subject: Re: DECwindows server: why the change of username, Message-ID: <448dbd0d$1@usenet01.boi.hp.com>  : "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message& news:448DBB85.5EFAB849@teksavvy.com...  9 > What VMS mechanisms are used between the client and the E > server when both run on the same node ? shared memory ? mailboxes ?  >   E Mapped Sections (shared memory) and exec mode ASTs are used for LOCAL 
 transport.  E > Also, if I start only the X server ona workstation. This gives me a G > blank "dead" screen until some application (local or remote) wants to < > display a window (and associate/register a widow manager). > E > During this "dead" time, where do the security settings come from ? G > (which file) and how can they be configured ? (since there is no menu  > available at that time). >   H Assuming the server is on VMS, there are several system files that grantK trusted access to the server by specific user/node/transports - that is - a + HOST list used until the user is logged in.   H > And out of curiosity, how does the decwidnows login software manage toG > change the UIC of a running process (the server) ? (aka: which system ? > service does it use, or is this some deep down kernel stack ?    There is a server extension.   ------------------------------    Date: 13 Jun 2006 07:29:33 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com>   Subject: HSG80 Serial connectionC Message-ID: <1150208973.481024.250480@i40g2000cwc.googlegroups.com>   F Does anybody know the pinout or a source of a cable to connect a HSG80F serial console to a 8-pin RJ45 DECserver 900TM port?  The HSG80 uses aC regular 6-pin RJ12 connector rather than the "usual" DEC MMJ style. F Unless I've missed something in the FAQ and while googling I don't see= any DECconnect type cable which has a regular RJ12 connector.    Thanks.      John H. Reinhardt    ------------------------------  % Date: Tue, 13 Jun 2006 07:46:12 -0700 # From: "Tom Linden" <tom@kednos.com> $ Subject: Re: HSG80 Serial connection) Message-ID: <op.ta29zavjzgicya@hyrrokkin>   ? On Tue, 13 Jun 2006 07:29:33 -0700, johnhreinhardt@yahoo.com  =   ! <johnhreinhardt@yahoo.com> wrote:   I > Does anybody know the pinout or a source of a cable to connect a HSG80=   I > serial console to a 8-pin RJ45 DECserver 900TM port?  The HSG80 uses a=   E > regular 6-pin RJ12 connector rather than the "usual" DEC MMJ style. I > Unless I've missed something in the FAQ and while googling I don't see=   ? > any DECconnect type cable which has a regular RJ12 connector.  > 	 > Thanks.  >  >   John H. Reinhardt  >   I I just used an MMJ console cable and trimmed off the tab.  Of course, it=    can more easily come out.    ------------------------------    Date: 13 Jun 2006 08:18:27 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com> $ Subject: Re: HSG80 Serial connectionB Message-ID: <1150211907.580949.36880@u72g2000cwu.googlegroups.com>   Tom Linden wrote: > > On Tue, 13 Jun 2006 07:29:33 -0700, johnhreinhardt@yahoo.com# > <johnhreinhardt@yahoo.com> wrote:  > J > > Does anybody know the pinout or a source of a cable to connect a HSG80J > > serial console to a 8-pin RJ45 DECserver 900TM port?  The HSG80 uses aG > > regular 6-pin RJ12 connector rather than the "usual" DEC MMJ style. J > > Unless I've missed something in the FAQ and while googling I don't seeA > > any DECconnect type cable which has a regular RJ12 connector.  > >  > > Thanks.  > >  > >   John H. Reinhardt  > >  > J > I just used an MMJ console cable and trimmed off the tab.  Of course, it > can more easily come out.   C Hmmm. Perhaps a spot of super-glue would do the trick. ;-)  Thanks!      John H. Reinhardt    ------------------------------    Date: 13 Jun 2006 09:21:36 -0700) From: "Luc" <luc.martineau.luc@gmail.com> 2 Subject: OPEN failed when compiled with /CHECK=ALLB Message-ID: <1150215696.744034.29320@u72g2000cwu.googlegroups.com>   Hi,   E We used for a long time a subroutine that reads and writes to a file.   C We had a problem and vendor tells us if we compiled with /CHECK=ALL 
 qualifier.  > Then we re-compiled programs and all subroutines and run them.  C Now we have a problem  with subroutine that reads and writes to the  file   We have a stack dump :  D %COB-F-NOT_OUTPUT, file RPT-FILE not open, or incompatible open mode/ %TRACE-F-TRACEBACK, symbolic stack dump follows G   image    module    routine             line      rel PC           abs  PC>  DEC$COBRTL                                 0 0000000000016034 0000000000926034>  DEC$COBRTL                                 0 00000000000157E8 00000000009257E8>  DEC$COBRTL                                 0 0000000000039D28 0000000000949D28>  CPYPR870  CPYPR870  CPYPR870            2967 0000000000010928 0000000000050928>  CPYPR870                                   0 000000000006D844 000000000006D844>                                             0 FFFFFFFF80273ED4 FFFFFFFF80273ED4      ! The instruction where we got it :   # OPEN I-O REPCTL-FILE  ALLOWING ALL.        The file is defined like that:    
 FILE-CONTROL. .     SELECT REPCTL-FILE ASSIGN TO "REPCTL-FILE".                        ORGANIZATION IS INDEXED-                        ACCESS MODE IS DYNAMIC ,                        RECORD KEY IS RR-KEY.    7 Then I compared the file definition with file attribute    In source code:    FD  REPCTL-FILE      FILE STATUS IS FS01 '     ALTERNATE RECORD KEY IS RR-PHY-NAME "     DATA RECORDS ARE REPORT-RECORD"                      OUTPUT-RECORD!                      DISTR-RECORD "                      COUNT-RECORD.   01  REPORT-RECORD.     05  RR-KEY. .         10  RR-KEY-ID               PIC X(01)..         10  RR-REPNO                PIC X(12).         10  RR-TIME-A..             15  RR-DATE-A           PIC 9(06)..             15  RR-HOUR-A           PIC 9(06)..         10  RR-FILLR                PIC X(12).     05  RR-DATA..         10  RR-PHY-NAME             PIC X(39)..         10  RR-DIRECTORY            PIC X(80)..         10  RR-USER-NAME            PIC X(12)..         10  RR-PROJECT-NO           PIC X(06)..         10  RR-TITLE                PIC X(30)..         10  RR-CRIT-CODE            PIC X(01)..         10  RR-DUR-RESID            PIC 9(06)..         10  RR-NBR-PAGE             PIC 9(04)..         10  RR-USER-REMARK          PIC X(30)..         10  RR-STREAM-NAME          PIC X(39)..         10  RR-SHARE-CTR            PIC 9(02).   01  OUTPUT-RECORD.     05  OR-KEY.          10  OR-1. .             15  OR-KEY-ID           PIC X(01)..             15  OR-USER-NAME        PIC X(12)..         10  OR-REPNO                PIC X(12).         10  OR-TIME-A..             15  OR-DATE-A           PIC 9(06)..             15  OR-HOUR-A           PIC 9(06)./     05  OR-DATA                     PIC X(249).    01  DISTR-RECORD.      05  DR-KEY.          10  DR-1. .             15  DR-KEY-ID           PIC X(01)..             15  DR-PROJECT-NO       PIC X(06)..             15  DR-REPNO            PIC X(12)..         10  DR-CC-NAME              PIC X(12)..         10  DR-FILLR                PIC X(06)./     05  DR-DATA                     PIC X(247).    01  COUNT-RECORD.      05  CR-KEY. .         10  CR-KEY-ID               PIC X(01)..         10  CR-FILLR                PIC X(36)./     05  CR-DATA                     PIC X(249).      With ANALYSE/FDL on file:   A IDENT   "13-JUN-2006 11:54:08   OpenVMS ANALYZE/RMS_FILE Utility"    SYSTEM'         SOURCE                  OpenVMS    FILE$         ALLOCATION              2163#         BEST_TRY_CONTIGUOUS     yes !         BUCKET_SIZE             3 #         CLUSTER_SIZE            103 "         CONTIGUOUS              no!         EXTENSION               3 "         FILE_MONITORING         no!         GLOBAL_BUFFER_COUNT     0 <         NAME                    "SDVL:[DATA]REPCTL.DAT;4863"'         ORGANIZATION            indexed (         OWNER                   [SYSTEM]E         PROTECTION              (system:RWED, owner:RWED, group:RWED, 
 world:RWE)   RECORD#         BLOCK_SPAN              yes /         CARRIAGE_CONTROL        carriage_return %         FORMAT                  fixed #         SIZE                    286    AREA 0$         ALLOCATION              1751#         BEST_TRY_CONTIGUOUS     yes !         BUCKET_SIZE             3 !         EXTENSION               3    AREA 1#         ALLOCATION              103 #         BEST_TRY_CONTIGUOUS     yes !         BUCKET_SIZE             3 !         EXTENSION               3    AREA 2#         ALLOCATION              309 #         BEST_TRY_CONTIGUOUS     yes !         BUCKET_SIZE             3 !         EXTENSION               6    KEY 0 "         CHANGES                 no#         DATA_KEY_COMPRESSION    yes #         DATA_RECORD_COMPRESSION yes !         DATA_AREA               0 #         DATA_FILL               100 "         DUPLICATES              no!         INDEX_AREA              1 #         INDEX_COMPRESSION       yes #         INDEX_FILL              100 !         LEVEL1_INDEX_AREA       1 "         NAME                    """         NULL_KEY                no!         PROLOG                  3 "         SEG0_LENGTH             37!         SEG0_POSITION           0 &         TYPE                    string   KEY 1 "         CHANGES                 no#         DATA_KEY_COMPRESSION    yes !         DATA_AREA               2 #         DATA_FILL               100 #         DUPLICATES              yes !         INDEX_AREA              2 #         INDEX_COMPRESSION       yes #         INDEX_FILL              100 !         LEVEL1_INDEX_AREA       2 "         NAME                    """         NULL_KEY                no"         SEG0_LENGTH             39"         SEG0_POSITION           37&         TYPE                    string   ANALYSIS_OF_AREA 0!         RECLAIMED_SPACE         0    ANALYSIS_OF_AREA 1!         RECLAIMED_SPACE         0    ANALYSIS_OF_AREA 2!         RECLAIMED_SPACE         0    ANALYSIS_OF_KEY 0 "         DATA_FILL               70"         DATA_KEY_COMPRESSION    64"         DATA_RECORD_COMPRESSION 79"         DATA_RECORD_COUNT       83"         DATA_SPACE_OCCUPIED     18!         DEPTH                   1 "         INDEX_COMPRESSION       44!         INDEX_FILL              9 !         INDEX_SPACE_OCCUPIED    3 !         LEVEL1_RECORD_COUNT     6 #         MEAN_DATA_LENGTH        286 "         MEAN_INDEX_LENGTH       39   ANALYSIS_OF_KEY 1 "         DATA_FILL               49"         DATA_KEY_COMPRESSION    88"         DATA_RECORD_COUNT       35!         DATA_SPACE_OCCUPIED     3 !         DEPTH                   1 !         DUPLICATES_PER_SIDR     1 "         INDEX_COMPRESSION       87!         INDEX_FILL              1 !         INDEX_SPACE_OCCUPIED    3 !         LEVEL1_RECORD_COUNT     1 "         MEAN_DATA_LENGTH        21"         MEAN_INDEX_LENGTH       41           I added   * 05  FILLER                      PIC X(02).  8 to DISTR-RECORD to get same length (286) in all records.      B I tried also to modified key RR-PHY-NAME tp PIC X(37) and added  a FILLER PIC X(02).    It always crashes.  % It never goes on declarative section.    We are using OpenVMS V7.3-2    Dis I miss something in Q http://www.helsinki.fi/atk/unix/dec_manuals/cobv27ua/cobum_018.htm#open_close_sec    ?    Do you have an idea ?    Thanks in advance.   Luc    ------------------------------  % Date: Tue, 13 Jun 2006 09:16:48 -0600 4 From: Norman Lastovica <norman.lastovica@oracle.com>= Subject: Re: Rdb, standard vs. multiversion and link problems * Message-ID: <448ED6E0.B59B68AB@oracle.com>   Rich Jordan wrote: >  > Norman Lastovica wrote: C > > sounds to me like your best and safeset bet would be to contact E > > oracle Rdb support directly and have them help get you a standard ? > > 70 kit that you can use when you build/link/install manman.  > > - >   norman lastovica / oracle rdb engineering  > 	 > Norman, G >      thanks, if there's any way for me to get that access I'll do it.   G > Can you verify that the newer kits are multiversion only?  There's no H > mention of that restriction in the release notes or install guides, at> > least that I've found, but it sure looks that way from here.  - Rdb 71 and later are multi-version kits only.    ------------------------------    Date: 13 Jun 2006 10:10:13 -0700( From: "Rich Jordan" <jordan@ccs4vms.com>= Subject: Re: Rdb, standard vs. multiversion and link problems A Message-ID: <1150218613.484265.5140@p79g2000cwp.googlegroups.com>    Norman Lastovica wrote:  > Rich Jordan wrote: > >  > > Norman Lastovica wrote: E > > > sounds to me like your best and safeset bet would be to contact G > > > oracle Rdb support directly and have them help get you a standard A > > > 70 kit that you can use when you build/link/install manman.  > > > / > >   norman lastovica / oracle rdb engineering  > >  > > Norman, I > >      thanks, if there's any way for me to get that access I'll do it.  > I > > Can you verify that the newer kits are multiversion only?  There's no J > > mention of that restriction in the release notes or install guides, at@ > > least that I've found, but it sure looks that way from here. > / > Rdb 71 and later are multi-version kits only.    Norman, D      thanks for the confirmation.  It looks like RDB 7.0 is the lastD one for MANMAN then, unless later versions have fixed things to work> nicely with the multiversion logicals (we're setting up 11.4).   Rich   ------------------------------    Date: 13 Jun 2006 00:25:50 -0700$ From: "Wilm" <w5.boerhout@planet.nl>E Subject: Re: SimH 3.6-0 (problems compiling VAX using MinGW) RESOLVED C Message-ID: <1150183550.227792.119070@f14g2000cwb.googlegroups.com>    Wilm wrote:   I > I have a problem compiling VAX and VAX780 under Windows, using the SIMH " > supplied build_mingw.bat script.  F The issue is resolved: I decided to be bold and adventurous and pulledC gcc 3.4.5 (MinGW special) from the MinGW Sourceforge download area, ) although its status there is "candidate".   D This version allowed a flawless build with the scrips as supplied by Bob.  F I only changed the optimize switch to -O3, and it then gives me a 14.2E VUP VAX780 to play with on my (hp compaq nx9010, 2.8 GHz) laptop. VAX  and PDP11 builds are fine, too.    Thanks for your help.    /Wilm    ------------------------------  % Date: Tue, 13 Jun 2006 11:38:08 -0400 C From: "David Turner, Island Computers US Corp" <dbturner@icusc.com> " Subject: VMS Compatible KVM switch: Message-ID: <VZAjg.54929$qd2.43310@bignews6.bellsouth.net>  B Anyone got any suggestions for a completely compatible KVM switch?* Manufacturer and Part number would be nice% It's for two ES45 systems running VMS    David  --     David B Turner Island Computers US Corp 2700 Gregory St, Suite 180 Savannah GA 31404  Tel: 912 447 6622 X201 Cell: 912 447 6622 X251  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    ------------------------------    Date: 13 Jun 2006 09:54:13 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com> & Subject: Re: VMS Compatible KVM switchC Message-ID: <1150217653.210312.194450@y43g2000cwc.googlegroups.com>   - David Turner, Island Computers US Corp wrote: D > Anyone got any suggestions for a completely compatible KVM switch?, > Manufacturer and Part number would be nice' > It's for two ES45 systems running VMS  >  > David   B Define "completely compatible".  Several brands will work with VMSE systems but most (if not all) will not support the full 108 keys of a C standard VMS keyboard.  If you google this group you will find much D discussion of this within the last 2 or 3 years.  You may be in luck@ since you only have 2 systems to multiplex as I think one of theD solutions that worked best was a 2-port KVM from Belkin - though I'm* not sure if that model is still available.  D Personally I have tried the following:  the Avocent 2160ES and 180ESB (actually Dell and Compaq rebrandings) and the Raritan MX416.  AllG "work" in that they switch between systems without problems, switch the B keyboard modes as required, correctly handle rebooting of machinesF without losing the use of either the keyboard or mouse.  Neither will,G however, pass through the all of the keycodes that are available on the @ LK series 108-key VMS keyboards and a couple of the keycodes are translated oddly.   G Google and read.  The other have documented the results far better than  I have listed here.    ------------------------------  # Date: Tue, 13 Jun 2006 04:14:55 GMT @ From: "Schroeder, AJ" <aaron.schroeder-no-spam@tmscomputers.com>0 Subject: Re: VMS, XDM, and remote connections...7 Message-ID: <3Zqjg.29042$GM.9361@tornado.rdc-kc.rr.com>   ; "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  & news:4481F71B.C68D1952@teksavvy.com... > "Schroeder, AJ" wrote:L >> On a hunch that it in fact was my Sun machine I installed Exceed onto an  >> XP I >> machine here and I did an XDMCP broadcast and Voila! I can login to my  >> OpenVMS system! >  > J > do a TCPTRACE of the network while the XDM communication is happening onJ > both the PC and SUN machines. I suspect you'll be seeing something like:! > (bike was the XDM server node).  > 7 > UDP Source Port = 177,   UDP Destination Port = 32785 E >   UDP Header and Datagram Length = 55 = ^x0037,   Checksum = ^xB59F  > I >   0A00000A   8EBE111E   0040FE89   4B000045    0000    E..K..@......... I >   05000100 | 9FB53700   1180B100 | 0C00000A    0010    .........7...... I >   6E697861   762E656B   69621200   00002900    0020    .)....bike.vaxin I >   6E696C6C   69571100   61632E6E   6F697461    0030    ation.ca..Willin D >                656761   6E616D20   6F742067    0040    g to manage > C > UDP Header and Datagram Length = 48 = ^x0030,   Checksum = ^xCB64  > I >   0C00000A   F87E11FF   00409AE8   44000045    0000    E..D..@...~..... I >   07000100 | 64CB3000   B1001180 | 0A00000A    0010    .........0.d.... I >   54494D12   00010000   00000000   00002200    0020    ."...........MIT I >   00312D45   494B4F4F   432D4349   47414D2D    0030    -MAGIC-COOKIE-1. = >                                    58494D03    0040    .MIX  > C > UDP Header and Datagram Length = 36 = ^x0024,   Checksum = ^xC649  > I >   0A00000A   A0FE111E   0000FF89   38000045    0000    E..8............ I >   09000100 | 49C62400   1180B100 | 0C00000A    0010    .........$.I.... I >   64646120   64696C61   76206F4E   10001600    0020    ....No valid add A >                         00000000   73736572    0030    ress....  > I > I've never gotten it to work on my network, so I don't have any packets J > that "work" to compare against. If you can trace the Exceed dialog, thenJ > this would provide some point of comparison to see what is different and > why it works.   J I'll try that next - or I will try a simple Ethereal sniff to see exactly K what is going on. I suspect that it is the Sun machine not allowing VMS to  A display. I think I pretty much proved that when Exceed connected.   J Would you be interested in seeing working packets from my Windows machine  and Exceed?    ------------------------------  % Date: Tue, 13 Jun 2006 00:18:51 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 0 Subject: Re: VMS, XDM, and remote connections..., Message-ID: <448E3C87.2FAAFFE5@teksavvy.com>   "Schroeder, AJ" wrote:K > Would you be interested in seeing working packets from my Windows machine 
 > and Exceed?   H Actually, I think it would be a great resource to have for anyone tryingF to get XDM working since it would provide a baseline of what to expectH from a working pair of XDM client and vms XDM servers.  And people couldF then compare against their own logs to try to see at what point things go sour.   ------------------------------  # Date: Tue, 13 Jun 2006 04:28:56 GMT @ From: "Schroeder, AJ" <aaron.schroeder-no-spam@tmscomputers.com>0 Subject: Re: VMS, XDM, and remote connections...8 Message-ID: <carjg.29043$GM.12203@tornado.rdc-kc.rr.com>  ; "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  & news:448E3C87.2FAAFFE5@teksavvy.com... > "Schroeder, AJ" wrote:L >> Would you be interested in seeing working packets from my Windows machine >> and Exceed? > J > Actually, I think it would be a great resource to have for anyone tryingH > to get XDM working since it would provide a baseline of what to expectJ > from a working pair of XDM client and vms XDM servers.  And people couldH > then compare against their own logs to try to see at what point things
 > go sour.  F Ok - I have never used TCPTRACE, but I can at least capture a working J conversation. I can post results from that and possibly Ethereal. I can't L promise when exactly I will get a chance to gather this information, but it  will be in the near future.   M I still want to enable *some* sort of security, but I'll take things working  ) first, then I can clamp down on security.    Thanks,    AJ Schroeder   ------------------------------   End of INFO-VAX 2006.327 ************************