1 INFO-VAX	Mon, 02 Apr 2001	Volume 2001 : Issue 184       Contents:. %SYSBOOT-F-PFN allocation overwrites CI ucode.2 Re: %SYSBOOT-F-PFN allocation overwrites CI ucode./ Re: Christof a bot (was: "cut" utility for VMS) / Re: Christof a bot (was: "cut" utility for VMS) / Re: Christof a bot (was: "cut" utility for VMS) / Re: Christof a bot (was: "cut" utility for VMS) < RE: FYI: NDS Authentication Services is coming to OpenVMS...< Re: FYI: NDS Authentication Services is coming to OpenVMS... Re: Mail Events.% Searching for 3.7D of HSD30s Firmware ( Re: Seeking CD-R/CD-RW SCSI INQUIRY data Re: Spice for OpenVMS Alpha? VMS-Related: Affordable  Re: VMS-Related: Affordable ) Re: When might SYS$SCHDWK not wake me up? * Re: [Q] param to increase for unsuff SPTE?  F ----------------------------------------------------------------------  # Date: Mon, 02 Apr 2001 01:08:55 GMT ! From: azog@nospam-azog.org (azog) 7 Subject: %SYSBOOT-F-PFN allocation overwrites CI ucode. 6 Message-ID: <Xns9076D7259439Dazogazogorg@199.45.45.11>  
 Greetings,  I I just tried to upgrade my VAXstation 4000/60, from 24mb to 32mb (filling I up the last two slots with 4mb). While in VMS, SHOW MEM still showed 24mb > of memory, so I checked the FAQ, which says (MGMT11) to modifyF PHYSICALPAGES (PHYSICALPAGES=-1) in MODPARAMS.DAT and then AUTOGEN...   G Now, I get "%SYSBOOT-F-PFN allocation overwrites CI ucode" on boot, and 7 can't even boot the system with a conversational boot.    C I'd like to see if I can fix this without first pulling the memory. A Pulling the memory may solve the problem, but it won't help me to > understand what the problem is and possible future avoidance.   3 I looked and found a mention in one of the manuals:   H "Reconfigure the system to require less physical memory, then reboot theC system. Reduce one or more parameters controlling the allocation of ; physical memory: NPAGEDYN, BALSETCNT, and VIRTUALPAGECNT."     ------------------------------  % Date: Sun, 01 Apr 2001 20:20:42 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> ; Subject: Re: %SYSBOOT-F-PFN allocation overwrites CI ucode. , Message-ID: <3AC7D3DC.BCC0CD0D@videotron.ca>   azog wrote: I > Now, I get "%SYSBOOT-F-PFN allocation overwrites CI ucode" on boot, and 8 > can't even boot the system with a conversational boot.  N Do you have the hardware manuals for your machine ? Perhaps there are commandsN at the >>> prompt that would allow you to diagnose a problem. (SHOW commands).   ------------------------------  % Date: Sun, 01 Apr 2001 21:37:53 +0000 ) From: Christof Brass <brass@infopuls.com> 8 Subject: Re: Christof a bot (was: "cut" utility for VMS), Message-ID: <3AC79FB1.49E51D28@infopuls.com>   John Santos wrote: > , > On Sat, 31 Mar 2001, Christof Brass wrote:   [SNIP]  ? > > I don't understand why waiting until Sunday could be of any 	 > > help.  > B > Hmm... curious lacunae* in Christof's database: Legos, Mechanos, > and now April Fools' Day...   @ Okay, thanks, if "lacunae" is the same as "lucuna" in my English; dictionary: something missing - I didn't think about 1st of  April.  D > He is a bot!  The best I ever have seen!  Congratulations, Andrew, > but we're on to you now. > . > *I've always wanted to use that in a post... >    [SNIP]  ? > Good question.  I think most such needs are the result of the = > lack of a suitable API.  For example, parsing the output of B > "$ show device/mounted" to extract the names of all the disks soB > they can be dismounted in sys$system:shutdown.com, because there? > is no wild-card support in f$getdvi, or parsing the output of @ > "$ show device" to determine the merge or copy percentage of a > shadowed disk.  = Understood and agreed. This is another argument why a general = output formatting logic should be there for every command and ' lexical function which produces output. @ In between the task has been explained by the initial poster and= it is clear now that individual extractions are necessary for 8 several commands as opposed to a general trimming of the complete output.  > > You have some program that produces the information you need? > buried in a mass of output, usually a text file.  You need to = > extract columns, perhaps with or following some tag, to get < > what you want.  If the program could provide you with just@ > the information you want, and nothing else, in a form suitable? > for manipulation (i.e. as symbols or logical names), then you  > wouldn't need this.   > Exactly. I asked about the task because I wrongly assumed that> several commands produced different output into one file which@ should have later be trimmed. I learned from this situation that= for character/line based output there should be qualifiers to 2 tell the program what to output and in what order.   > --
 > John Santos  > Evans Griffiths & Hart, Inc. > 781-861-0670 ext 539   ------------------------------  % Date: Sun, 01 Apr 2001 19:58:03 -0400 2 From: rdeininger@mindspring.com (Robert Deininger)8 Subject: Re: Christof a bot (was: "cut" utility for VMS)L Message-ID: <rdeininger-0104011958030001@user-2ive61o.dialup.mindspring.com>  B In article <1010401125010.22825A-100000@Ives.egh.com>, John Santos <JOHN@egh.com> wrote:     ? > Good question.  I think most such needs are the result of the = > lack of a suitable API.  For example, parsing the output of B > "$ show device/mounted" to extract the names of all the disks soB > they can be dismounted in sys$system:shutdown.com, because there? > is no wild-card support in f$getdvi, or parsing the output of @ > "$ show device" to determine the merge or copy percentage of a > shadowed disk.  H There's no wild card in f$getdvi, but there is f$device, which gives theG same effect.  It's pretty well hidden.  I parsed SHOW DEVICE output for  years until I discovered it.   --   Robert Deininger rdeininger@mindspring.com    ------------------------------  $ Date: Sun, 1 Apr 2001 19:51:31 -0400  From: John Santos <JOHN@egh.com>8 Subject: Re: Christof a bot (was: "cut" utility for VMS)= Message-ID: <1010401193656.56419A-100000-100000@Ives.egh.com>   + On Sun, 1 Apr 2001, Robert Deininger wrote:   D > In article <1010401125010.22825A-100000@Ives.egh.com>, John Santos > <JOHN@egh.com> wrote:  >  > A > > Good question.  I think most such needs are the result of the ? > > lack of a suitable API.  For example, parsing the output of D > > "$ show device/mounted" to extract the names of all the disks soD > > they can be dismounted in sys$system:shutdown.com, because thereA > > is no wild-card support in f$getdvi, or parsing the output of B > > "$ show device" to determine the merge or copy percentage of a > > shadowed disk. > J > There's no wild card in f$getdvi, but there is f$device, which gives theI > same effect.  It's pretty well hidden.  I parsed SHOW DEVICE output for  > years until I discovered it.  G I'd forgotten all about that.  Even used it myself (in a .com I execute C many times a day...)  OOPS.   I wonder why they haven't used it in  H sys$system:shutdown.com?  (It's still there in VMS 7.2.)  Which leads toG a story...  One former co-worker added a bunch of his favorite commands E to sylogin.com, including "open" as a synonym for "show device/file". D Took us years to discover why all the disks always needed rebuildingH after a reboot of that system.  (shutdown.com would just proceed withoutG dismounting any disks if the "open" failed.)  There must be a lesson in  there somewhere.   --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  # Date: Mon, 02 Apr 2001 00:38:55 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) 8 Subject: Re: Christof a bot (was: "cut" utility for VMS)0 Message-ID: <009F9E74.3B9AB7FD@SendSpamHere.ORG>   In article <rdeininger-0104011958030001@user-2ive61o.dialup.mindspring.com>, rdeininger@mindspring.com (Robert Deininger) writes: C >In article <1010401125010.22825A-100000@Ives.egh.com>, John Santos  ><JOHN@egh.com> wrote: >  > @ >> Good question.  I think most such needs are the result of the> >> lack of a suitable API.  For example, parsing the output ofC >> "$ show device/mounted" to extract the names of all the disks so C >> they can be dismounted in sys$system:shutdown.com, because there @ >> is no wild-card support in f$getdvi, or parsing the output ofA >> "$ show device" to determine the merge or copy percentage of a  >> shadowed disk.  > I >There's no wild card in f$getdvi, but there is f$device, which gives the H >same effect.  It's pretty well hidden.  I parsed SHOW DEVICE output for >years until I discovered it.    $ HELP LEXICAL F$DEVICE    Lexicals  
   F$DEVICE  H        Returns the device names of all devices on a system that meet the$        specified selection criteria.  ?        Note that the device names are returned in random order.   
        Format   D          F$DEVICE([search_devnam],[devclass],[devtype], [stream-id])        That's hidden? --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              O city, n., 1. a place where trees are cut down and streets are named after them.    ------------------------------  % Date: Sun, 01 Apr 2001 17:57:29 -0500 + From: "Main, Kerry" <Kerry.Main@compaq.com> E Subject: RE: FYI: NDS Authentication Services is coming to OpenVMS... R Message-ID: <DC4745D1A85CA04180C83CDC706A9D180D94C6@cthexc02.americas.cpqcorp.net>   Hello Christoff,  E While not currently available on Alpha OpenVMS, the latest Novell NDS J offerings (eDirectory 8.5) is currently available for Tru64 UNIX on Alpha.  
 Reference:L http://www.novell.com/documentation/lg/ndsedir/docui/index.html#../taoenu/da* ta/a2iii88.html (one url will likely wrap)   Quote from previous pointer:G "NDS Server is a service that currently runs on NetWareR, Windows* NT*, # Linux*, Solaris*, and Tru64 UNIX*.    J http://www.zdnet.com/eweek/stories/general/0,11011,1017124,00.html (in the press)J http://www.compaq.com/newsroom/pr/1999/0,1494,wp~85_2!ob~11690_1_1,00.html (Original Compaq press release)   H Somewhat related - as of OpenVMS v7.3, OpenVMS also now licenses a fullyC X.500 compliant directory with LDAPv3 interface as part of the OS.    
 Reference:L http://www.openvms.compaq.com/ebusiness_without_compromise/fact/OPENVMS-ENTE' RPRISE-DIR-FOR-EBUSINESS.HTML (one url)    Regards,  
 Kerry Main Senior Consultant  Compaq Canada Inc. Professional Services  Voice: 613-592-4660  Fax  :  819-772-7036 Email: Kerry.Main@Compaq.com     -----Original Message-----0 From: Christof Brass [mailto:brass@infopuls.com] Sent: March 31, 2001 3:47 AM To: Info-VAX@Mvb.Saic.Com E Subject: Re: FYI: NDS Authentication Services is coming to OpenVMS...      Thanks for your post.    Chuck Chopp wrote: >  > Bob Koehler wrote: > ; > > In article <3ABF723A.497002D8@rtfmcsi.com>, Chuck Chopp   <ChuckChopp@rtfmcsi.com> writes: > > K > > > 3)  Slightly OT here, but after attending some sessions on NetWare64,  itH > > > has become very apparent that Novell has completely redesigned theI > > > kernel [now the nano kernel] of NetWare to be hardware architecture I > > > independent.  I made some comments about why was Novell waiting for I > > > Intel to get IA64 ready for prime-time when they could have used an F > > > Alpha processor for 64-bit computing any time during the past 10 years. > > L > > Novell announced plans to port Novell to Alpha back in about '93.  Still > > waiting.  : I asked DEC people in '95 about porting Netware to Alpha -> answer: we are focused on M$. Maybe at that time porting to an= architecture owned by one company and beeing dependent on the < information supplied by that company for doing a proper port8 wouldn't have been a good idea. At least DEC should have@ communicated to Novell that porting to the Alpha platform (incl.- mainboards, chipsets, machines) were welcome.   I > That issue came up in the discussions about NetWare64 and the technical  feasibility ofL > porting to Alpha.  The assessment of NetWare 3.x/4.x that was done at that time revealed far J > too many Intel x86 dependencies & assumptions in the core NOS to make it feasible to J > convert.  It looks like Novell is at least taking some good steps in the right direction I > this time by making sure that the hardware is abstracted from the OS at  the lowest levels. > L > The reason that eDirectory on Alpha [and even NetWare64 on Alpha] would be desirable comes L > from the approach that Novell is taking with their marketing of eDirectory these days.  They I > are not necessarily catering an NOS to companies that will have at most  just a few tens ofL > thousands of objects in their directory.  Instead, they're going after the electronic B2BJ > market and the large-scale directory market where you may literally have tens or hundreds of H > millions of objects in the directory.  For example, whenever you go to CNN's web site, you ! > are issued a cookie to identify D > you.  The cookie also results in an object being created in an NDS eDirectory tree which L > gets some portal site customization information attached to it.  Later on, if you return toH > the CNN site, the cookie held by your browser is used to retrieve this
 customization F > information from your personal cookie object in the eDirectory tree. CNN's servers are C > handling something in excess of 10 to 20 million objects that get  frequently updated. L > Powering that eDirectory with Alpha-based systems should provide much more performance and > > scalability than using less capable IA32/IA64/Sparc systems. >  > --
 > Chuck Chopp  > : > ChuckChopp@rtfmcsi.com            http://www.rtfmcsi.com2 >                                   ICQ # 22321532B > RTFM Consulting Services Inc.     864 801 2795 voice & voicemail4 > 103 Autumn Hill Road              864 801 2774 fax6 > Greer, SC  29651                  800 774 0718 pager9 >                                   8007740718@skytel.com   ? Great. You mentioned the compiler technique Novell is using. Do : they use their own compiler (what language)? Do they offer? different language bindings for their Netware API - I only know @ C bindings - and compilers for different languages to write NLMs? (if this term is still correct)? Do you know what is (has been) > the base for this high performance object database? I remember? attending a Netware programming seminar back in 1994 where they = only had very low level C APIs. They did all the object stuff : manually. Very poor then. I would like to hear about major	 progress.    ------------------------------  % Date: Mon, 02 Apr 2001 01:02:37 +0000 ) From: Christof Brass <brass@infopuls.com> E Subject: Re: FYI: NDS Authentication Services is coming to OpenVMS... , Message-ID: <3AC7CFAD.7EE7D73A@infopuls.com>   "Main, Kerry" wrote: >  > Hello Christoff, > G > While not currently available on Alpha OpenVMS, the latest Novell NDS L > offerings (eDirectory 8.5) is currently available for Tru64 UNIX on Alpha. >  > Reference:N > http://www.novell.com/documentation/lg/ndsedir/docui/index.html#../taoenu/da, > ta/a2iii88.html (one url will likely wrap) >  > Quote from previous pointer:I > "NDS Server is a service that currently runs on NetWareR, Windows* NT*, $ > Linux*, Solaris*, and Tru64 UNIX*. > L > http://www.zdnet.com/eweek/stories/general/0,11011,1017124,00.html (in the > press)L > http://www.compaq.com/newsroom/pr/1999/0,1494,wp~85_2!ob~11690_1_1,00.html! > (Original Compaq press release)  > J > Somewhat related - as of OpenVMS v7.3, OpenVMS also now licenses a fullyD > X.500 compliant directory with LDAPv3 interface as part of the OS. >  > Reference:N > http://www.openvms.compaq.com/ebusiness_without_compromise/fact/OPENVMS-ENTE) > RPRISE-DIR-FOR-EBUSINESS.HTML (one url)  > 
 > Regards, >  > Kerry Main > Senior Consultant  > Compaq Canada Inc. > Professional Services  > Voice: 613-592-4660  > Fax  :  819-772-7036 > Email: Kerry.Main@Compaq.com   [SNIP]  ? Thanks. While it is a major advantage to have NDS on Tru64 this @ is only a part of Netware. It would be great if Novell ports the! complete Netware to native Alpha.    ------------------------------  % Date: Mon, 02 Apr 2001 08:49:06 +1000 < From: George Constantinides <gconstantinides@mhl.nsw.gov.au> Subject: Re: Mail Events.N, Message-ID: <3AC7B062.3CB3EF@mhl.nsw.gov.au>   Hoff Hoffman wrote:S  o > In article <3AC3BE22.7AF06B6D@mhl.nsw.gov.au>, George Constantinides <gconstantinides@mhl.nsw.gov.au> writes:( >:C > :I need to know when a particular user name receives mail. How doV! > :I capture events of this type?" >i >   What are you up to?t >aI >   I can think of a couple of potential approaches (mostly involving use L >   of existing or newly-enabled security alarms and/or audits, and possiblyH >   adding an ACL or two), but the details and background of the problemE >   here would be useful...   And SMTP, Mail-11, and/or on-node MAIL?e >A  H I have a user who will be receiving data from a remote station via SMTP.I I am thinking of a detached process (or something similar) running in the-O user's security domain (i.e.. without any special privileges) that is listening8L for mail events and on receipt of such an event, reads the VMS mail file andH processes the data. Below is an extract of an OPCOM log in OPERATOR.LOG.    8 %%%%%%%%%%%  OPCOM  30-MAR-2001 08:08:53.07  %%%%%%%%%%%$ Message from user INTERnet on MARLING INTERnet ACP SMTP Accept Request from Host: 203.0.140.141    Port: 1043      Regards,   George Constantinidesh email:  GeorgeC@mhl.nsw.gov.au URL   http://www.mhl.nsw.gov.auP   ------------------------------  $ Date: Mon, 2 Apr 2001 13:42:28 +1200+ From: "Rob Buxton" <rob.buxton@wcc.govt.nz>b. Subject: Searching for 3.7D of HSD30s Firmware& Message-ID: <986175876.202006@muldoon>  
 Hello All,  8 I'm trying to get hold of a copy of 3.7D HSD30 Firmware.J We bought a couple of HSDs second hand, one came with 3.7D, the other withI 3.4D. We're having some strange problems with Tape Drives and I'd like ton0 upgrade the Firmware of the lower rev level HSD.   Anyone have a copy?m  J we're in New Zealand so the closer the better. Though Postage costs should be pretty low!   Many Thanks,   Rob.   ------------------------------  # Date: Sun, 01 Apr 2001 19:18:03 GMT4- From: "Paul A. Jacobi" <pjacobi@mediaone.net>t1 Subject: Re: Seeking CD-R/CD-RW SCSI INQUIRY datae< Message-ID: <L9Lx6.9443$WZ4.1661075@typhoon.ne.mediaone.net>  L The reporting of LUNs is different from SCSI-1 and SCSI-2.  From the inquiryK information, the device claims to support SCSI-2, however, it still reportsoI LUNs via the SCSI-1 method.  This is a bug in the device firmware.  SincesE Windows does not normally use SCSI LUNs, this feature of the firmwareoL usually doesn't get tested.  You probably won't have any luck convincing theG manufacture to change the firmware, since it work with Windows and they " probably won't care about any O.S.  H It is my experience that you can still use LUN 0 (DKAx00) and ignore theJ rest.  If you attempt to uses the non-zero LUN, it will likely cause hangs or crashes.u  H You will also need to verify if the CD-ROM drive supports 512-byte blockK mode.  Some drives claim to implement 512-byte block mode, but implement it  incorrectly.   Paul A. Jacobi OpenVMS Systems Groupi 110 Spitbrook Rd. ZK03-4/U14 Nashua, NH 03062   ------------------------------  % Date: Sun, 01 Apr 2001 13:21:42 -0500gC From: "Craig A. Berry" <craig.berry@nospam.SignalTreeSolutions.com>w% Subject: Re: Spice for OpenVMS Alpha?SI Message-ID: <craig.berry-DDE2CB.13214201042001@newsrump.sjc.telocity.net>   - In article <3AC54567.B1A9D3A5@earthlink.net>, %  ualski <ualski@earthlink.net> wrote:o  F > I should have been more specific.  The first one I listed is FORTRAND > but the newer one, and the second listed, is purported to be C.  I* > don't have any experience with that one. > D > Anyone know what sort of new features or fixes went along with the > switch to C?  H The SPICE written in FORTRAN that I'm aware of was written in the 1970s > with portability in mind, which means the variable names were = enigmatically short and there was one very long program file aH "structured" primarily with GOTOs (few compilers supported subroutines, H much less independently compiled modules).  It was quite an achievement F for its time but was considered obsolete 15 years ago, though perhaps 8 there have been complete rewrites in FORTRAN since then.  G Berkeley SPICE 3 was written in C and came along sometime in the 80s.  hC It was highly modular and had some abstraction layers that made it mH thinkable to modify and extend it.  I was involved in getting it up and G running on VMS at Hughes Aircraft in the late 80s.  It was a challenge xH only because I was young and inexperienced and had never seen C before, F but there really weren't all that many modifications we had to make.  E There were some interesting wrinkles turned up by the VAX C compiler oH and the VMS debugger that had gone unnoticed in the Unix versions.  For D example, on the VAX, character constants were stored in a read-only D psect, which caused an accvio if you passed them to a function that E modified them; apparently the Berkeley compilers of that era allowed  , constants to be overwritten without warning.  G I haven't been involved in circuit modeling in the last 12 years and I 1= find it quite surprising that no one has posted more current 0A information.  Surely SPICE has continued to be developed, and is qD probably still in C.  If it's in ANSI C it really shouldn't be that B difficult to port to OpenVMS if it hasn't been done already.  Try C digging around on the UC Berkeley web pages and see if the code is m still being maintained there.o   ------------------------------  % Date: Sun, 01 Apr 2001 21:45:32 -0600p1 From: "David J. Dachtera" <djesys.nospam@fsi.net>   Subject: VMS-Related: Affordable' Message-ID: <3AC7F5DC.66BDBCB5@fsi.net>   
 Hi, Folks,  H I've been thinking lately whether this affordable thing is worth puttingB anymore effort into. Clearly, RM's higher-ups aren't interested inF upping their bottom line at the expense of margins, nor does RM appear1 to me interested in it or motivated to pursue it.n  : So, whaddaya think? Should I drop it? ...or hang in there?  G Feel free to chastise/support me privately if you deem this unworthy ofhF the newsgroup. Remember to demangle the Reply-to address shown in this& posting. The how-to should be obvious.   --   David J. Dachtera. dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/n  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.t   ------------------------------  % Date: Mon, 02 Apr 2001 01:14:09 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>g$ Subject: Re: VMS-Related: Affordable, Message-ID: <3AC80AA0.5DEAF5AF@videotron.ca>   "David J. Dachtera" wrote: >  > Hi, Folks, > J > I've been thinking lately whether this affordable thing is worth puttingD > anymore effort into. Clearly, RM's higher-ups aren't interested inH > upping their bottom line at the expense of margins, nor does RM appear3 > to me interested in it or motivated to pursue it.   K It is a worthy cause worth pursuing in my opinion. How to pursue it and howu" much pressure is another question.   ------------------------------  $ Date: Sun, 1 Apr 2001 23:52:13 +02004 From: "Peter Ljungberg" <peter.p.ljungberg@telia.se>2 Subject: Re: When might SYS$SCHDWK not wake me up?, Message-ID: <9a8815$5ht$1@news.han.telia.se>   Hi Tim,t        & Have you reported the problem to CPQ ?  L There seems to be some problem with a "missing AST" in current Alpha OpenVMSK 7.2-1H1, engineering is still "I think" working on it, it could be isolatedtK to the pthreads but I'm not sure... the idea is (what I understand) that antL AST "got lost" or maybe better overwritten, so the Wake was never delivered,C just a thought that come to mind when I read about your problem....2           /P.Lj0      8 "Tim Shoppa" <shoppa@trailing-edge.com> wrote in message+ news:3AC64119.4AC14D5E@trailing-edge.com...t > JF Mezei wrote:> > >  > > Tim Shoppa wrote: C > > > It's always: $SCHDWK, process, $HIBER, repeat.  The "process"  > > > step may do some I/O.  > >t >         program hibers >         integer*4 idelta(2) . >         call sys$bintim('0 00:00:05',idelta) >         sys$schdwk(,,idelta,)h >         accept * >         call sys$hiber >         type *,'I woke up!' 
 >         endn >i= > If you stall more than 5 seconds in the I/O with the acceptsC > statement, in "real VMS" wake up immediately after the sys$hiber.rB > It's only in your "hypothetical VMS" that your suggestion solves, > a problem.  Luckily I've got real VMS :-). >a > Tim.   ------------------------------  # Date: Sun, 01 Apr 2001 18:22:19 GMT.1 From: "Mark D. Jilson" <jilly@clarityconnect.com>i3 Subject: Re: [Q] param to increase for unsuff SPTE?C2 Message-ID: <3AC77243.8477D70C@clarityconnect.com>  A Sorry but I've been down this road many times.  IMHO, it is RDB'srH responsibility to make it easy to obtain the VMS system service that wasB called and what were the arguments passed to it.  SQL is not a VMSF system service!  That single SQL statement may break down into a dozen! or more VMS system service calls.p  A The bottom line is that you are attempting to map more S0 virtualOH address space than the VMS architecture allows, there is no tunable knobD for this.  There is no definitive way to examine S0 address space toB determine what is consuming how much.  Without knowing how much S0F address space this SQL statement is trying to map, no one will be ableH to tell you if you can even attempt a workaround by attempting to reduceG S0 space consumption with the SYSGEN parameters that result in S0 space:G usage for their structures.  Please contact your RDB support and advise A them of the error and ask them if RDB has ways to map the virtualkG address space to S2 space as this is an available programming techniqueaG in VMS.  If RDB does not have this ability then you'll need to considerpG moving this work to a different system.  Systems have finite limits and H you have hit the VMS limit for S0 space but nothing other than trail andF error is going to help here unless more information is provided by you or your RDB support vendor(s).   Didier Morandi wrote:I >  > Gentlemen, > P > You maybe are very familiar with "system service call" within Rdb, I am not. IR > am a poor VMS software person. The only thing I know about "system service call"O > is what I program within FORTRAN sources since 19 years. I have no clue abouteK > the way to know which "system service call" SQL could request when I do a $ > "select * from FD;" A READ, maybe? > Q > Do you want me to enable XQP debugging mode, or do you wish that I call back Mr N > Clinton to help, or should I ask Mr Bush to vote a special tax cut so that IR > will have more money to go to GKN and ask for an Rdb training they don't provideR > anymore, or should I go to the Parsec Group or Mr Burden's company, and you will* > pay for the ticket Bern Boston? Or what? >   > Thanks for your comprehension. > N > This issue is a COMPAQ issue. The error message *is* incorrect from the HELPM > facility. It gives a solution for VAX only. What is the solution for ALPHA,  > then?r > Q > (anyway, I'll increase GBLPAGES and GBLSECTIONS and I'll figure out by myself).u >  > D.K > (I don't particularily like waking up at 6 to go testing a Saturday...:-)E >  > "Mark D. Jilson" wrote:e > > I > > I know, I sing this tune very well but it seems hard to get anyone to B > > join me especially when they can't/won't provide the requestedK > > information :*(  It' be plainly obvious once we had what system servicea8 > > call returned the error and what the arguments were. > >a* > > "Brian Schenkenberger, VAXman-" wrote: > > > ( > > > Two, maybe three, days ago I said: > > >e< > > >   Sounds like you're asking too much of your S0 space.   -- bD Jilly	- Working from Home in the Chemung River Valley - Lockwood, NY0 	- jilly@clarityconnect.com			- Brett Bodine fan. 	- Mark.Jilson@Compaq.com			- since 1975 or so, 	- http://www.jilly.baka.com               -   ------------------------------   End of INFO-VAX 2001.184 ************************