1 INFO-VAX	Sun, 11 Dec 2005	Volume 2005 : Issue 689       Contents:  Re: Attaching Terminals Directly  Re: Attaching Terminals Directly  Re: Attaching Terminals Directly  Re: Attaching Terminals Directly calloc() fails, no more memory Re: CMUIP Patches  Re: DFG (Defrag) - OpenVMSJ Re: mistake in/suggested enhancements for HELP LEXICALS F$GETDVI ARGUMENTS  Re: Running Image From Procedure" Re: saving recovery data with PCSI  F ----------------------------------------------------------------------  % Date: Sun, 11 Dec 2005 11:22:00 +0100 & From: "H Vlems" <nospam@what.ever.com>) Subject: Re: Attaching Terminals Directly < Message-ID: <59cfd$439bfe01$513b9a2c$27711@news.versatel.nl>  7 "Volker Englisch" <volkeren@rsli.de> schreef in bericht $ news:dnedfn$d9g$1@rrz.allgaeu.org... > Hi again!  > C > I own an Alpha Server 1000 4/200 running OpenVMS 7.3-1. The usual H > approach to attach character cell terminals to those machines seems to > be using a terminal server.  > A > But I wonder if it was possible to connect these character cell H > terminals like VT510 directly to the server. Is there something like aI > extension card that can be added to the server's hardware offering some E > additional terminal connectors? What did I have to look for, and is 3 > OpenVMS able to recognize these additional ports?  > D > Back in mainframe days, I remember we had so called "workstations"F > connected directly to the machine, and lots of "terminals" connected( > via terminal server and multiplexer... >  > TIA  > V. >  Volker,   I they way I read your question ,you're looking for a PCI equivalent of the ' DZ-11, DMF-32 serial line multiplexers. K On the back of the Alpha Server 1000 you'll find two 9 pin serial ports, #1 L and #2. The SRM variable CONSOLE determines how VMS treats these devices. OnD my Digital Server 5305 and Alpha Server 5/300 the following applies:  7     console                     #1                   #2 -     GRAPHICS           TTA0:            TTB0: 0     SERIAL                 OPA0:           TTA0:  J Connect a VTxxx terminal to either one and you're set. There are PCI cards> that support two serial lines, available from SWEEX and Q-TEC.D They use different chipsets to drive the ports so one of them may beL supported by VMS. I use these cards to connect a PC to the VAX console portsK and run Reflection as terminal emulator. I have nothing against a VT420 but   one pc replaces 10 terminals....   Hans   ------------------------------   Date: 11 Dec 2005 08:07:54 GMT( From: volkeren@rsli.de (Volker Englisch)) Subject: Re: Attaching Terminals Directly * Message-ID: <dngmoq$nv8$1@rrz.allgaeu.org>  1 Phillip Helbig---remove CLOTHES to reply schrieb: E > In article <dnedfn$d9g$1@rrz.allgaeu.org>, volkeren@rsli.de (Volker  > Englisch) writes:  > D >> I own an Alpha Server 1000 4/200 running OpenVMS 7.3-1. The usualI >> approach to attach character cell terminals to those machines seems to  >> be using a terminal server. >>  B >> But I wonder if it was possible to connect these character cellI >> terminals like VT510 directly to the server. Is there something like a J >> extension card that can be added to the server's hardware offering someF >> additional terminal connectors? What did I have to look for, and is4 >> OpenVMS able to recognize these additional ports? > F > It's certainly possible.  I prefer such a terminal as the console.  F > There should be a serial port.  One will be the console port, one a 4 > "regular" serial port (if there is more than one).  F Sure. One of both is connected to the console terminal, one otherwise.B So no one is actually left. What I'm looking for is something likeF plugging in a PCI/ISA card that offers e.g. 8 additional serial ports.D Necessarily this card should be recognized by OpenVMS. Maybe someone2 has successfully worked out that kind of approach?   V.   ------------------------------  % Date: Sun, 11 Dec 2005 10:24:34 -0500 * From: "FredK" <fred.nospam@nospam.dec.com>) Subject: Re: Attaching Terminals Directly , Message-ID: <439c44b4$1@usenet01.boi.hp.com>  @ The PBXDA-BA (which is actually made by DIGI) is a PCI card thatA will do what you want on Alpha.  For Itanium the supported method F is to use USB serial devices - in this case, DIGI also makes the rightE solution for you - in the form of a 8-port serial multiplexer (google D search for DIGI Edgeport).  The USB drivers will show up in V8.3 but; we have made them available as-needed for earlier versions.     5 "Volker Englisch" <volkeren@rsli.de> wrote in message $ news:dngmoq$nv8$1@rrz.allgaeu.org...3 > Phillip Helbig---remove CLOTHES to reply schrieb: G > > In article <dnedfn$d9g$1@rrz.allgaeu.org>, volkeren@rsli.de (Volker  > > Englisch) writes:  > > F > >> I own an Alpha Server 1000 4/200 running OpenVMS 7.3-1. The usualK > >> approach to attach character cell terminals to those machines seems to   > >> be using a terminal server. > >>D > >> But I wonder if it was possible to connect these character cellK > >> terminals like VT510 directly to the server. Is there something like a L > >> extension card that can be added to the server's hardware offering someH > >> additional terminal connectors? What did I have to look for, and is6 > >> OpenVMS able to recognize these additional ports? > > F > > It's certainly possible.  I prefer such a terminal as the console.G > > There should be a serial port.  One will be the console port, one a 6 > > "regular" serial port (if there is more than one). > H > Sure. One of both is connected to the console terminal, one otherwise.D > So no one is actually left. What I'm looking for is something likeH > plugging in a PCI/ISA card that offers e.g. 8 additional serial ports.F > Necessarily this card should be recognized by OpenVMS. Maybe someone4 > has successfully worked out that kind of approach? >  > V.   ------------------------------  % Date: Sun, 11 Dec 2005 11:33:13 -0500 * From: "d b turner" <dbturner@islandco.com>) Subject: Re: Attaching Terminals Directly 7 Message-ID: <YuYmf.1371$kP5.334@bignews5.bellsouth.net>    volker  G we stock the digi 8 port  boards with the "spider cable" with 8 x DB25  	 connector   
 Price is $800    David       6 "Volker Englisch" <volkeren@rsli.de> wrote in message $ news:dnedfn$d9g$1@rrz.allgaeu.org... > Hi again!  > C > I own an Alpha Server 1000 4/200 running OpenVMS 7.3-1. The usual H > approach to attach character cell terminals to those machines seems to > be using a terminal server.  > A > But I wonder if it was possible to connect these character cell H > terminals like VT510 directly to the server. Is there something like aI > extension card that can be added to the server's hardware offering some E > additional terminal connectors? What did I have to look for, and is 3 > OpenVMS able to recognize these additional ports?  > D > Back in mainframe days, I remember we had so called "workstations"F > connected directly to the machine, and lots of "terminals" connected( > via terminal server and multiplexer... >  > TIA  > V. >    ------------------------------  % Date: Sun, 11 Dec 2005 12:26:10 +0000 " From: Hans Blom <tocum2@yahoo.com>' Subject: calloc() fails, no more memory J Message-ID: <1134303970.bcd67978e90e81688cc82000703ebe4c@fe2.teranews.com>  
 Hello all,G I'm running OpenVMS 7.3-2 on an Alphaserver. A programmer has developed G an application that, in order to work with speed, wants to keep as much G as possible of the data in memory. At some point he does an calloc() to D get a memoryarea to keep about 400 000 pointers. He gets a null backD from the call, basically OpenVMS saying - sorry sir, no more memory!  H We have tried raising pgflquota, wsextent (in order to decrease need forG paging) and every other conceivable quota both in sysuaf and sysgen. We G can see that as long as the program works in memory everything is fine, D but as soon as wsextent is hit and it has to start paging, it fails.  / I'm stuck! Anybody got any ideas on what to do?    Regards   	 Hans Blom    ------------------------------  % Date: Sun, 11 Dec 2005 03:11:42 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>  Subject: Re: CMUIP Patches, Message-ID: <439BDF1E.E67A9D17@teksavvy.com>   David J Dachtera wrote:  > 
 > Dave wrote:  > > F > > Does anyone know where I can dowload the patches for CMUIP v6.6-5?  F This is what I have ( see below). If this is what you need, contact meV via email ( remove obvious spam counter measure) or at jfmezei domain is vaxination.ca     Listing of save set(s)    Save set:          CMUIP665K.BCK Written by:        UDAA055" UIC:               [000100,000002]* Date:              28-FEB-1996 14:49:51.96P Command:           BACKUP [CMUIP...] ANONYMOUS_ROOT:[CMU-TCPIP]CMUIP665K.BCK/INT /BLOCK=2048/LOG/SAVE+ Operating system:  OpenVMS VAX version V5.5  BACKUP version:    V5.5-2  CPU ID register:   13000202  Node name:         _BAY::  Written on:        _DSA62: Block size:        2048  Group size:        10  Buffer count:      384  > [CMUIP]IP.DIR;1                                             1  28-FEB-1996 14:48 > [CMUIP.IP]CMUTEK.DIR;1                                      1  28-FEB-1996 14:48 > [CMUIP.IP.CMUTEK]AAAREADME.DOC;5                            4  27-FEB-1996 02:08 > [CMUIP]SYS$LDR.DIR;1                                        1  28-FEB-1996 14:48 ? [CMUIP.SYS$LDR]IPDRIVER.EXE;4                               9    6-JAN-1996 05:31> [CMUIP]SYSEXE.DIR;1                                         1  28-FEB-1996 14:48 ? [CMUIP.SYSEXE]FINGER.EXE;2                                 50    6-JAN-1996 04:46? [CMUIP.SYSEXE]FINGER_SERVER.EXE;2                          51    6-JAN-1996 04:48> [CMUIP.SYSEXE]FTP.EXE;2                                   138  22-NOV-1995 14:50 > [CMUIP.SYSEXE]FTP_SERVER.EXE;2                             89  31-DEC-1995 18:17 > [CMUIP.SYSEXE]IPACP.EXE;9                                 297  25-FEB-1996 17:24 > [CMUIP.SYSEXE]IPNCP.EXE;70                                 99  25-FEB-1996 17:09 ? [CMUIP.SYSEXE]NAMRES.EXE;29                                93    6-JAN-1996 04:14? [CMUIP.SYSEXE]TALK.EXE;3                                   43    6-JAN-1996 04:30? [CMUIP.SYSEXE]TALK_SERVER.EXE;15                           30    6-JAN-1996 04:31? [CMUIP.SYSEXE]TELNET.EXE;36                               119    6-FEB-1996 15:02> [CMUIP]SYSLIB.DIR;1                                         1  28-FEB-1996 14:49 > [CMUIP.SYSLIB]CSDRV.EXE;64                                 12  16-JAN-1996 00:25 > [CMUIP]SYSMGR.DIR;1                                         1  28-FEB-1996 14:49 ? [CMUIP.SYSMGR]TELNET.CLD;37                                 6    6-FEB-1996 11:49   Total of 20 files, 1046 blocks End of save set  $    ------------------------------    Date: 11 Dec 2005 07:29:37 -0800$ From: "Ed Wilts" <ewilts@ewilts.org># Subject: Re: DFG (Defrag) - OpenVMS C Message-ID: <1134314977.085570.258540@g14g2000cwa.googlegroups.com>    Craig A. Berry wrote: H > In article <43999a19$0$28638$892e7fe2@authen.yellow.readfreenews.net>,C >  caaron@ceris.purdue-dot-edu.no-spam.invalid (Chuck Aaron) wrote:  > > > > %DFG-F-SYSSRVERR, call to system service SYS$EXPREG failed- > > -SYSTEM-F-EXQUOTA, process quota exceeded  > E > I believe with DFG this generally means you are out of file headers + > (yeah, not the most informative message).   F And you'd be wrong.  As somebody else pointed out, it simply means youD don't have enough page file quota.  And yes, the message is actually6 informative - it actually is a process quota exceeded.  F Setting the quota for DFG is documented in the Guide to Operation that you'll find in sys$Help:.   	    .../Ed    ------------------------------  + Date: Sun, 11 Dec 2005 09:32:27 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)S Subject: Re: mistake in/suggested enhancements for HELP LEXICALS F$GETDVI ARGUMENTS $ Message-ID: <dngrnb$vi7$2@online.de>  D In article <dnfik3$csi$3@online.de>, helbig@astro.multiCLOTHESvax.de3 (Phillip Helbig---remove CLOTHES to reply) writes:     > ALPHA: > E >          SHDW_CATCHUP_COPYING    SHDW_COPIER_NODE SHDW_DEVICE_COUNT C >          SHDW_GENERATION  SHDW_MASTER             SHDW_MASTER_MBR D >          SHDW_MASTER_NAME        SHDW_MBR_COPY_DONE SHDW_MBR_COUNT= >          SHDW_MBR_MERGE_DONE SHDW_MBR_READ_COST SHDW_MEMBER  >  > VAX: > K >          SHDW_CATCHUP_COPYING    SHDW_MASTER             SHDW_MASTER_NAME M >          SHDW_MEMBER             SHDW_MERGE_COPYING      SHDW_NEXT_MBR_NAME  > K > Note that, on ALPHA, some arguments (like VOLCHAR) are starred.  At the   F > bottom of the list is "* Alpha only".  Shouldn't the non-VAX shadow   > arguments be shadowed as well?  & Should be "starred as well" of course.   ------------------------------  + Date: Sun, 11 Dec 2005 09:31:35 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)) Subject: Re: Running Image From Procedure $ Message-ID: <dngrln$vi7$1@online.de>  6 In article <00A4E116.32DDD41F@SSRL.SLAC.STANFORD.EDU>,F winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing) writes:   L > >With some Fortran programs, I once found that I had to define SYS$OUTPUT G > >to SYS$COMMAND as well in order to get them to work the same from a   > >procedure as interactively. >  > Never ran into that one.   Here's the problem description:    PROGRAM TEST CHARACTER (LEN=80) DATA + WRITE (*, '(T2,A)',ADVANCE='NO') 'INPUT = '  READ  (*, '(A)') DATA  WRITE (*, *) 'WRITE' PRINT*, 'PRINT'  END PROGRAM TEST   should produce  $ INPUT = this is whatever you type in WRITE  PRINT   C as it does when RUN TEST is the command.  When the command is @TEST    $! TEST.COM $ $  DEFINE/USER SYS$INPUT SYS$COMMAND $  RUN TEST  $  EXIT  the terminal displays    this is whatever you type in
 INPUT = WRITE  PRINT   H in other words the prompt does not appear until after the data are typedH in (making it useless) and the word `WRITE' is appearing where it should not.  H I then thought `maybe this is another list directed output thing where IC shouldn't worry what happens' although I wouldn't have thought that E redefining SYS$INPUT (INput) at the DCL level should have any effect. > Just to make sure, I changed the relevant line of code to read   WRITE (*, '(T2,A)') 'WRITE'   B which runs as expected interactively but from within the .COM file produces   this is whatever you type in WRITE =  PRINT   ' which if anything is even MORE bizarre.     Explanation (from Steve Lionel):  G The WRITE doesn't have to appear at all until an ADVANCE='YES' write is G done.  We have special case code to look to see if the output device is D the same as the input device, and if so, do the partial writes.  ButE when input is redirected to the command stream, they're different and  you lose that feature.     This enlightened me:  D So I can DEFINE/USER_MODE SYS$OUTPUT SYS$COMMAND as well and get theC desired effect---I've tried it and it works.  (I assume this is the @ expected behaviour here, though I've never thought of redefining" SYS$OUTPUT to SYS$COMMAND before.)   ------------------------------    Date: 11 Dec 2005 15:28:33 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)+ Subject: Re: saving recovery data with PCSI , Message-ID: <439c45a1$1@news.langstoeger.at>  w In article <dnfhqd$csi$2@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: g >In article <439b2abb$1@news.langstoeger.at>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes:   > J >> >When I install patches, and answer the questions so that the patch is M >> >always installed, the response schemas seem to alternate back and forth.   >>  G >> I do see inconsistencies but I do not see the opposite of "logical".  > P >> 5) If you UNDO PATCH keep in mind that you can only UNDO the newest/last ECO.O >> If you need to UNDO an older one you need to undo all newer ones as well and 
 >> before. > E >OK, but when I apply a new one, I can only continue if I delete the  C >recovery data for the older ones, at least following the standard   >questions and answers.   I Then either it is no ECO or has the question bad worded or has a problem.   D >> I do not rely on the options or questions of the ECOs. No longer.C >> I did define PCSI$$SAVE_RECOVERY_DATA to "YES" in SYLOGICALS.COM L >> And yes, the ECOs seem inconsistent in if to ask for recovery data or not. >> and if to require for recovery data or not. > D >Apparently, you don't rely for a reason.  Are you sure that if you 7 >define the logicals that things then work as expected?   1 I wasn't for a long time, but am now pretty sure. @ I could be wrong of course (but so far wasn't, at least here ;-)  Q >> OpenVMS VAX V7.3 unfortunately still has no similar PCSI ECO and so is unable.  > 3 >Right, but there aren't that many patches for VAX.   . Yup. As the VMS ECOs are still VMSINSTAL ones.O But TCPIP_ECO _is_ an ECO on OpenVMS VAX, too (but w/o recovery data of course)   N >> 2) You need a patch ECO for saving (and also not deleting of already saved)K >> Recovery Data. Full kits cannot save recovery data (they also ignore the J >> qualifier and/or the corresponding PCSI logical) and do also delete all" >> previously saved recovery data. > B >Other than reading all the notes, is there a quick way to see if , >something at ITRC is a patch or a full kit?  D Anything named VMSxyz_ or ECO should be an ECO (but isn't always ;-)   --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------   End of INFO-VAX 2005.689 ************************