HDTenEightyP/NetNews huggingface dataset:
From: jeh@cmkrnl.com
Newsgroups: comp.os.vms
Subject: Re: Detecting directory of invoked .com
Date: 24 Dec 92 04:30:28 GMT
Organization: Kernel Mode Consulting, San Diego, CA

In article <1992Dec23.160636.27010@tigger.jvnc.net>,
 fogelinc@nmr1.Cyanamid.COM (Carl Fogelin) writes:
> At the risk of being flamed by the "active" participants of this Sig, I have
> a problem which I hope has a reasonable answer.

	Oxidizer and napalm tanks full		check!
	Pressure tank charged			check!
	Igniter charged				check!
	Safety off				che

... oops, sorry, got carried away there.

> 
> In a DCL program, I would like to be able to determine what directory the
> invoked .com file is located in.  I seem to remember a similar thread about
> 6 - 8 months ago, so I hope someone remembers the solution.

General rule of DCL command procedures:  If you want information about 
something -- almost anything -- look at lexical functions.  HELP LEXICALS
gives you a complete list.  Unfortunately this is one of those cases where
you have to know the name by which VMS refers to something before you can
go looking for it. 

	f$environment("PROCEDURE")

will return the complete file specification of the command procedure from
which it is invoked.  To get just the device and directory name, you can
parse this out yourself with just a few quick strokes of f$element, but
f$parse will do it for you:

	$ comfile = f$environment("PROCEDURE")
	$ comfile_dev = f$parse(comfile,,,"DEVICE")
	$ comfile_dir = f$parse(comfile,,,"DIRECTORY")

For more information, see HELP LEXICALS F$ENVIRONMENT or ... F$PARSE.

	--- Jamie Hanrahan, Kernel Mode Consulting, San Diego CA
drivers, internals, networks, applications, and training for VMS and Windows-NT
uucp 'g' protocol guru and release coordinator, VMSnet (DECUS uucp) W.G., and 
Chair, Programming and Internals Working Group, U.S. DECUS VMS Systems SIG 
Internet:  jeh@cmkrnl.com, hanrahan@eisner.decus.org, or jeh@crash.cts.com
Uucp:  ...{crash,eisner,uunet}!cmkrnl!jeh
From: leichter@lrw.com (Jerry Leichter)
Newsgroups: comp.os.vms
Subject: re: How Open is Open VMS?
Date: 1 Jan 93 12:27:15 GMT
Organization: The Internet


	Could someone tell me how "open" Open VMS really is. Is it so open
	that someone can obtain the source codes, or is it another proprietary
	operating system with the word "Open" attached to it? Thanks.

This is bound to start a whole bunch of flame wars, as it does when the issue
of "openness" comes up in any newsgroup or mailing list.

"Openness" is the latest bit of market-speak, replacing such phrases as "user-
friendly" and competing with "object-oriented".  The term was, if not invented
by Sun, certainly heavily pushed by them as the centerpiece of their marketing
strategy.  If you believe that "Open" means "sources are available", I suggest
you ask Sun about the availability of sources for SunOS or Solaris.  Or ask
ANY of your favorite commercial Unix vendors about the availability of sources
for their offerings.

FWIW, source LISTINGS of almost all of VMS are available on CD-ROM quite
cheaply.  (Some fairly small pieces that DEC considers proprietary are left
out.  Generally they are extremely hardware-specific.)  Source KITS have
traditionally been available, but hard to get and quite expensive; I don't
know the current state of things.  DEC has announced that they intend to
make complete source kits available, along with licenses to port VMS to other
architectures.  I don't believe anyone has taken them up on it, so I doubt
they've ever worked out all the details.

There are several DEC-sponsored books that describe the inner workings of VMS.
I know of no analogous documentation for any commercial version of Unix - and
even the classic books (Leffler et al on 4.3BSD, Bach on System V) are much
less complete, and of course by now well out of date, and in any case don't
describe any particular implementation that you can buy.

							-- Jerry
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Question about DECnet of Network..
Date: 22 Dec 1992 05:27:55 GMT
Organization: HST Wide Field/Planetary Camera
Distribution: world
Reply-To: carl@SOL1.GPS.CALTECH.EDU
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <A94717D1F99F00101A@EGFRCUVX>, SABRY@SHEBIN.EG (Sabry Kotob El-Ganzory) writes:
>Hello all.............
>I am Sabry from EGYPT, Our system MV 3400 by 12.00MB with VMS V5.2-1 and
>Couple with DECnet with all univetiries egyptain....ok.
>Of course, I am sending to you needing a help.
>I'm a novice in system managment.....
>My question is:-
>When I boot to device appear to me these a messages it is:-
>Message from user DEcnet
>DECnet starting
>%NCP-I-NOINFO,no information database
>%NCP-W-INVIDE, invalid indentification,line=tx-0-12
>%SYSTEM-F-INDEVMAN,invalid device name
>%NCP-W-UNRCMP,unrecongized component,circurit
>Circuit=tx-0-12
>Please, how I avoid this a messages to appears me????
>As a matter of fact, I'm a novice in system management.....

No shit, Sherlock?  I'll spell out your best strategy:  READ THE FUCKING
MANUAL!  The NOINFO message simply means that one of the categories that NCP
works with has no definitions in it (LOGGING comes to mind as a likely culprit).
The INVIDE message would, of course, be obvious to anyone who understands
English:  You're trying to start circuit TX-0-12.  That corresponds to device
TXA12.  Buy a bigger terminal driver board, or LEARN TO  SPEAK ENGLISH, or hire
someone to do it for you!
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.
Xref: sparky comp.os.vms:19642 comp.sys.dec:6573
From: lee@hsh.com (Lee Havemann)
Newsgroups: comp.os.vms,comp.sys.dec
Subject: Re: Help with PATHWORKS and Novell work on my PC
Date: 21 Dec 92 15:13:26 GMT
Organization: HSH Associates

In article <AAD6TChyM6@nienschanz.spb.su>, valera@nienschanz.spb.su (Valera Bulgakov) writes:
> Hi everybody!
> 
>         I have some problems when using ODINSUP with DEC PathWorks.
> I have D-Link DE-200 card with irq=5 and IO=300. When I use PathWorks
> with the following PROTOCOL.INI file and original NDIS driver for
> DE-200 all works fine.
>         My PROTCOL.INI file in this case looks like this:
> ;NI_IRQ       = 5
> 
Deleted stuff...
> 
>         But when I try to use PathWorks with original ODI
> driver and ODINSUP I always recive an error.
>         My PROTCOL.INI file in that case looks like this:
> [protocol manager]
>     drivername = PROTMAN$
> 
> [DATALINK]
> DRIVERNAME   = DLL$MAC
> BINDINGS     = DE-200
> ;NI_IRQ       = 5
> 
More deleted stuff...
> 
>         The error message that I recieve is generated by scheduler module
> (schk) and looks like this:
> Error:    Wrong Hardware Vector.  Set NI_IRQ in PROTOCOL.INI to
>           Interrupt Vector For Network Adapter.
> 
>         I think that I shouldn't set the NI_IRQ to value 5
> according to description of ODINSUP
>         But I've tried to set NI_IRQ to 5, the general result was
> approximately the same, also on my VAX 3600 console I recieved message:
> "DECnet event 4.15 adjacency up". But niether PathWorks file service
> nor sethost (through LAT or CTERM) didn't work.
> 
>         Could anybody tell me what wrong I've done?
> 

In both examples cited, you still have the  ;NI_IRQ       = 5 remmed out.
Remove the semicolon and it should work. (emphasis on should :-)

-- 

 Lee Havemann, Comp Ops Dir.    HSH Associates      (201) 838-3330 
 Internet: lee@hsh.com    Compuserve: 70410,3507    AOL: HSH Assoc
 "Any opinions expressed are not necessarily those of anyone else, 
  including myself."                     
Newsgroups: comp.os.vms
From: larry@eco.twg.com (Lawrence B. Henry III)
Subject: Re: How Open is Open VMS?
Reply-To: larry@eco.twg.com
Organization: The Wollongong Group (East Coast Operations)
Date: Thu, 31 Dec 92 20:32:20 GMT


In article <1992Dec31.190236.29454@zooid.guild.org>, Mark Kovarski <kovarski@zooid.guild.org> writes:
|>Newsgroups: comp.os.vms
|>Path: eco.twg.com!uunet!utcsri!geac!zooid!kovarski
|>From: Mark Kovarski <kovarski@zooid.guild.org>
|>Subject: How Open is Open VMS?
|>Organization: ZOOiD BBS
|>Date: Thu, 31 Dec 1992 19:02:36 GMT
|>Message-ID: <1992Dec31.190236.29454@zooid.guild.org>
|>Lines: 7
|>
|>
|>Could someone tell me how "open" Open VMS really is. Is it so open that
|>someone can obtain the source codes, or is it another proprietary operating
|>system with the word "Open" attached to it? Thanks.
|>
|>Mark K.
|>E-Mail: kovarski@zooid.guild.org
|>
From what I understand source code for VMS is obtainable.. but one must pay
money.. I would'nt touch the "open" word debate for anything.... especially when
talking about operating systems.

-Larry.
From: gezelter@rlgsc.com
Newsgroups: comp.os.vms
Subject: Re: Detecting directory of invoked .com 
Date: 24 Dec 92 00:51:49 EST
Organization: Robert Gezelter Software Consultant, Flushing, NY

In article <1992Dec23.160636.27010@tigger.jvnc.net>, fogelinc@nmr1.Cyanamid.COM (Carl Fogelin) writes:
> At the risk of being flamed by the "active" participants of this Sig, I have
> a problem which I hope has a reasonable answer.
> 
> In a DCL program, I would like to be able to determine what directory the
> invoked .com file is located in.  I seem to remember a similar thread about
> 6 - 8 months ago, so I hope someone remembers the solution.
> 
Use the lexical function F$ENVIRONMENT with the item code of 
"PROCEDURE". Example:
 
             F$ENVIRONMENT("PROCEDURE")
 
> Reason:  I have a production command procedure that every once in awhile
> must be moved to a test area for modification.  Currently, when I copy the
> com file to the test area, I comment out the assigns associated with the
> production version and uncomment the assigns associated with the test
> version.  Unfortunately, sometimes when this command procedure is moved
> back into production, the assigns are NOT switched back.
> 
There are some better ways to do this. For example, you could 
define a series of logical names which exist in both the test and 
production environments (they just happen to point to different 
places). This has the added side effect of being completely 
consistent for program testing.
 
> What I would like is to some code to this command procedure which would:
> 
>      if command file in production area then
>         assign production logicals
>      else
>         assign test logicals
>      endif
> 
See my comments above.
 
> Does anyone know a method for doing this?
> 
> - Carl
> ---------------------------------------------------------------------------
>  Carl Fogelin (fogelincc@cyanamid.com)     "All opinions are strictly mine" 
>    "Sushi!   That's what my ex-wife called me.  Cold fish." -- Blade Runner
-- 
Carl,
 
Please see my comments above.
 
I hope that the above information is helpful. If I have been 
unclear, or if I can be of further assistance, please feel free 
to contact me via Email or phone.
 
- Bob
+--------------------------------------------------------------------------+
| Robert "Bob" Gezelter                       E-Mail:  gezelter@rlgsc.com  |
| Robert Gezelter Software Consultant         Voice:   +1 718 463 1079     |
| 35-20 167th Street, Suite 215               Fax:       (on Request)      |
| Flushing, New York  11358-1731                                           |
| United States of America                                                 |
+--------------------------------------------------------------------------+
From: mandach@decus.ch (mandach)
Newsgroups: comp.os.vms
Subject: SUBSCRIBE
Date: 2 Jan 93 11:55:09 GMT
Distribution: world
Organization: The Internet
X-Unparsable-Date: Sat, 2 Jan 93 11:45:04 CET


Please SUBSCRIBE Hans v. Mandach - Thansk !@
From: vance@lpl.arizona.edu (Vance Haemmerle x4021)
Newsgroups: comp.os.vms
Subject: Re: What is XPDRIVER for?
Date: 30 Dec 92 03:27:14 GMT
Distribution: world,local
Organization: Lunar & Planetary Laboratory, Tucson AZ.

In article <1992Dec29.143542.4184@arizona.edu> CHD@HERMES.ECE.ARIZONA.EDU (Chris De Young) writes:
>
>    Booting a 4000/300 VMS 5.4-2, I get the following error early in the boot
>process:
>    
>    %SYSGEN%W-NOMSG, Message number 00000910
>    [SYSEXE]XPDRIVER.EXE
>    %SYSGEN%W-NOMSG, Message number 00000910
>    [SYSEXE]XPDRIVER.EXE
>    
>This occurs after loading the MSCP disk server but before mounting the disks.
>The 4000 being booted is the disk server for a cluster of 6 VS 3100's.
>
>There is no XPDRIVER.EXE anywhere on the system that I can find, but there
>also is not on another VMS 5.4-2 system which does not exhibit this message.
>

  XPDRIVER.EXE is the driver for a PCL11 device (don't ask me what a PCL11
  is... It says so in the SYSGEN manual :-) ), and it doesn't come with
  VMS so unless you have one, you can ignore it.

>What is the source of this message, and is it something I need to worry
>about?
>

  Your error message sounds like something we get after a system crash.
  A MicroVAX II I manage has a Peritek VCX-Q video board.  It's a very
  picky device in that it must be re-initialized during shutdown, otherwise
  bad things happen on the next warm reboot.  Namely error messages
  similar to yours.  SYSGEN will want some driver it doesn't need, the
  terminal lines will timeout or the system will just crash during
  startup... the error is different for each new version of VMS :-).
  It even changed on the same VMS version when our VAX changed from a
  stand-alone to a boot node.  My theory is that the Q-bus is set in a
  weird state that confuses SYSGEN into thinking something's there.
  The only thing that clears it is a cold restart... i.e. power down
  and then back up.  Try it and see if the error goes away.

>Thanks much,
>
>-Chris

  Hi Chris! ;-)

--
  Vance Haemmerle                              vance@vips.lpl.arizona.edu
  Support Systems Analyst, Senior              vance%toyvax@arizona.edu
  Lunar & Planetary Lab
  University of Arizona
Newsgroups: comp.os.vms
From: winalski@adserv.enet.dec.com (Paul S. Winalski)
Subject: Re: ballooning EXE size
Reply-To: winalski@adserv.enet.dec.com (Paul S. Winalski)
Organization: Digital Equipment Corporation, Nashua NH
Date: Wed, 30 Dec 1992 22:10:28 GMT


In article <1992Dec29.111631.1@slacvx.slac.stanford.edu>,
fairfield@slacvx.slac.stanford.edu writes:

[regarding the problem of a FORTRAN program that suddenly needed 70 times
 as many disk blocks for the .EXE after minor changes and a relink]
|>
|>    You haven't told us what you're doing  in "my code".  If your code was
|>    Fortran  (which  I  take  it, it is not), and if  you  declared  local
|>    arrays, and if  you  initialized  _any_portion_  of  those  arrays  to
|>    non-zero  values,  then  you would get the behaviour you've described.
|>    If you're writing in C, and the  arrays are static, and you initialize
|>    any  portion  of  them  to non-zero values, I would  expect  the  same
|>    situation.
|>
|>    Reason: the VMS linker normally  will  not allocate blocks in the disk
|>    file  (.EXE file) for uninitialized memory.  These are referred to  as
|>    "demand zero pages".  Only when the  image  is  activated  is  virtual
|>    memory  allocated  for  such  memory.   However,  if  you initialize a
|>    portion of an array, the  linker  is  prevented from using demand-zero
|>    pages and the whole, initialized array is expanded in the .EXE file.

Not true.  Initialization of a portion of an array doesn't cause the whole
array to be written to blocks in the disk file.  The Linker lays out memory for
all program sections in the image, then it fills in the initial values for
the code and initialized data, and then it scans the image looking for
uninitialized pages.  Where it finds a run of uninitialized pages, it creates
a new image section with the demand-zero attribute.  Demand-zero pages don't
have to appear in the .EXE file, since by definition the system knows that they
are all zeros.  This phase of the link is called "demand-zero compression".

Image sections do not come for free.  Your process can only have a certain
number of them, given by the PROCSECTCNT SYSGEN parameter value.  To avoid
creating too many image sections, the Linker stops doing demand-zero compression
when the total number of image sections reaches the value set by the ISD_MAX
linker option, the default value of which is 96.  This is what happened to the
original poster.  His program has lots of little runs of uninitialized pages
in it.  Something that he changed pushed the Linker over the ISD_MAX limit and
it stopped creating demand-zero image sections.  One or more large,
uninitialized arrays that occur in the image after that point thus weren't
dzero-compressed and ended up on disk.

Steve Lionel's posting gave the solutions to this problem.

--PSW
From: lionel@quark.enet.dec.com (Steve Lionel)
Newsgroups: comp.os.vms
Subject: Re: Question about utility Mail....
Date: 21 Dec 92 21:33:56 GMT
Reply-To: lionel@quark.enet.dec.com (Steve Lionel)
Organization: Digital Equipment Corporation, Nashua NH


In article <A94A99B5E63F000FCD@EGFRCUVX>, SABRY@SHEBIN.EG 
(Sabry Kotob El-Ganzory) writes:
||>
|>Hello All...............
|>I am Sabry Kotob. Do your remeber me????
|>Our system MV 3400 by 12.00Mb VMS V5.2-1....
|>Does anyone know what the mail$xxxxx.mai files are that are created by mail.
|>They don't seem to be related to the number of messages in various mail folders.
|>Just wondering....

MAIL stores the text of messages longer than 3 blocks in these separate files.
The header information (From, To, Subject, etc.) is kept in the file MAIL.MAI.
If you prefer, you can ask that MAIL keep all these files in a subdirectory
by means of the MAIL command SET MAIL_DIRECTORY.   The MAIL$xxx.MAI files
are explained in the VMS Mail Utility User Manual in the section titled 
"Creating a MAIL Subdirectory for Large Messages".  This section also explains
the use of the SET MAIL_DIRECTORY command.
--

Steve Lionel                    lionel@quark.enet.dec.com
SDT Languages Group
Digital Equipment Corporation
110 Spit Brook Road
Nashua, NH 03062
Newsgroups: comp.os.vms
From: michael@chpc.utexas.edu (Michael Lemke)
Subject: Re: Flaming and Such
Keywords: flaming
Organization: The University of Texas System - CHPC
Date: Sun, 3 Jan 93 04:25:19 GMT

In article <C08qB5.CoA@micrognosis.co.uk> nreadwin@micrognosis.co.uk (Neil Readwin) writes:
>In article <74@colornet.com>, dfilip@colornet.com writes:
>|> Has anyone done any stats in this newsgroup as to : [ flames ]
>
[...]
>In a nutshell, 6.5% of the articles were discussions about flames (and I
>guess quite a few more were the flames themselves :-). Hope this helps. Neil.
>
>[%]
>Calculated using:
>	#!/bin/sh
>	trap 's=$?; rm -f /tmp/gak.$$; exit $s' 0
>
>	grep \^Subject: * | tr '[A-Z]' '[a-z]' | \
>	sed -e 's/[0-9]*:subject:[      ]*//' -e 's/^re:[     ]*//' \
>		-e 's/^re:[     ]*//' | sort > /tmp/gak.$$
>
>	awk -f - /tmp/gak.$$ <<"Grok!This" | sort -n
>	BEGIN {f=1;c=0} {if (f) {f=0;c=1;l=$0} else {if ($0 == l) {c++;} else {
>	printf "%3d %s\n",c,l;c=1;l=$0}}} END {if (c) {printf "%3d %s\n",c,l;}}
>	Grok!This
>

How dare you to post such disgusting gobbledygook in a VMS news group?  :-)
And then without translation to VMS/english!   :-) :-) :-)

Michael
-- 
Michael Lemke
Astronomy, UT Austin, Texas
(michael@io.as.utexas.edu or UTSPAN::UTADNX::IO::MICHAEL [SPAN])
From: gezelter@rlgsc.com
Newsgroups: comp.os.vms
Subject: Re: PLEASE, I wanr know addess DECUS....
Date: 21 Dec 92 15:27:25 GMT
Organization: Robert Gezelter Software Consultant, Flushing, NY

In article <AA0C4A0A27FF000513@EGFRCUVX>, SABRY@SHEBIN.EG (Sabry Kotob El-Ganzory) writes:
> Hello All....
> PLease, how to contact with DECUS or I want  her address to contact it??
> Thanks to any help...
> Sabry
> E-mail:sabry@shebin.eg
> 
> 
-- 
Sabry,
 
I believe that Egypt is considered as part of the At-Large DECUS 
Chapter. The Chapter Administrator for the At-Large DECUS Chapter 
is:
 
                      Mr. Dale Brandt
                      DECUS At-Large
                      Box 176
                      12, avenue des Morgines
                      1213 Petit-Lancy 1
                      Geneva, Switzerland
 
                      E-mail: dale.brandt@geo.mts.dec.com
                      Tel:    41 (22) 709 4258
                      Fax:    41 (22) 709 4099
                      Telex:  422593
 
(The above is abstracted from the "At-Large Chronicle", Number 7, 
June 1992.
 
I hope that the above information is helpful.
 
- Bob
+--------------------------------------------------------------------------+
| Robert "Bob" Gezelter                       E-Mail:  gezelter@rlgsc.com  |
| Robert Gezelter Software Consultant         Voice:   +1 718 463 1079     |
| 35-20 167th Street, Suite 215               Fax:       (on Request)      |
| Flushing, New York  11358-1731                                           |
| United States of America                                                 |
+--------------------------------------------------------------------------+
From: dragon@NSCVAX.PRINCETON.EDU (Mighty Firebreather)
Newsgroups: comp.os.vms
Subject: RE: Pagefile size and distribution guidelines desired
Date: 22 Dec 92 15:13:01 GMT
Organization: The Internet


	Don Roberts <dsroberts@beckman.com> writes:
>
>We managed to work out getting a pair of two two gigabyte disks to replace two
>ra92's for our set of "system" packs.  By system packs, in this case, I mean
>where we put the layered products, page files, etc.  As opposed to user data
>:-).  So, for the first time in a while, we can make our page files bigger.
>And contiguous.  WHat guidelines do others use for determining the proper size
>for pagefiles?  

	Take the figure that AUTOGEN with FEEDBACK gives you and add blocks
"to taste".  How much you need depends so strongly on your system 
configuration and your workload that I wouldn't even attempt to tell you 
how much is enough.

	I have a VAXStation 3100 with 32Mb of memory and two 126,000 block 
page files, one on each disk drive.  This may seem a little extreme until I
tell you that the poor thing is driving three VT1200 and two VT1300 
X-terminals!

>As we don't have a defragmentor the problem we've run into in
>the past is that if we make them too small we are not later able to make them
>contiguous until we can do an image backup and restore (almost never
>unfortunately).  Currently we have two 100,000 block page files each for our
>6420 and 6520, and this is a tad small.  Another thing I've never seen
>guidelines on is number of page files.  Does it do any good to put multiple
>page files for one system on one disk?

	In general, no.  A single, bigger, page file should work better.  
If you are having problems with "page file fragmentation", it might help.

>If we have multiple page files per
>system on several disks, but those pagefiles are on the same disks as the
>pagefiles for other systems, isn't that just as bad?

	Not quite.  But putting them on disks that have *no* other page 
files should provide better performance.  Take those two RA92s that you 
freed up and use them for secondary paging files.  The more spindles that
share the load, the better the performance (up to a point).

>
>We're on 5.5 on our cluster.


*************************************************************************
*                                                                       *
*                        Here, there be dragons!                        *
*                      dragon@nscvax.princeton.edu                      *
*                                                                       *
*                                                Richard B. Gilbert     *
*************************************************************************