HDTenEightyP/NetNews huggingface dataset:
From: lionel@quark.enet.dec.com (Steve Lionel)
Newsgroups: comp.os.vms
Subject: Re: Librarian Question..............
Date: 3 Sep 92 13:31:14 GMT
Reply-To: lionel@quark.enet.dec.com (Steve Lionel)
Distribution: usa
Organization: Digital Equipment Corporation, Nashua NH


In article <1992Sep2.232729.23659@news.Hawaii.Edu>, bill@gaza.uhcc.Hawaii.Edu 
(William J. King) writes:
|>
|>Is it possible to specify a $ LIBRARY command that will search
|>for the module mame you are only interested in.
|>	eg.  *dump* 
|>
|>$ LIBRARY /MACRO sys$library:starlet.mlb  *dump*     WOULD BE NICE IF
|>							IT WORKED.

Sure.  Check out the /ONLY qualifier.  It accepts wildcards.
--

Steve Lionel                    lionel@quark.enet.dec.com
SDT Languages Group
Digital Equipment Corporation
110 Spit Brook Road
Nashua, NH 03062
From: Sanyee_Tang@mindlink.bc.ca (Sanyee Tang)
Newsgroups: comp.os.vms
Subject: RMS File Lock Questions
Date: 30 Aug 92 09:34:37 GMT
Organization: MIND LINK! - British Columbia, Canada
Distribution: world

    I am writing a utility in C to find all RMS locks on a specified file.
The scheme is:

(a) Call SYS$PARSE and SYS$SEARCH to find the 6-byte file ID (field NAM$W_FID)
    and device name (field NAM$T_DVI).  The file could be specified by a
    logical.

(b) Call SYS$GETDVI with item code DVI$_DEVLOCKNAM to find the 16-byte device
    lock name for the device name obtained in (a).

(c) Call SYS$ENQ to queue a lock on a resource whose name is concatenated as

        RMS$ + file ID + device lock name

    and receive a lock-id.

(d) Call SYS$GETLKI with item code LKI$_LOCKS, passing lock-id returned in
    (c), in hope to get a list of RMS locks associated with the resource name
    in (c).

(e) Print out PID, lock mode and queue for every lock in the list returned
    in (d).

    I have coded a test program.  My questions are:

1)  Can the above scheme work?  Is the basic idea correct?

2)  Apparently I have no access to RMS locks in normal situation.  What
    happen if I do (c) and (d) in EXEC mode (as same as RMS)?  If I queue
    a lock in EXEC mode with a valid resource name of a RMS file lock, can
    I block locks queued by RMS on the same file?  :-)

3)  If I shall change mode and call SYS$CMEXEC (or SYS$CMKRNL), what is the
    order of the argument list?  In the same order as in C or in a reversed
    order?

    I would like to have your experts' opinions before I go further, I am
a bit anxious about to shut down a busy system unwittingly.  Your help is
highly appreciated.  I thank Dan Wing, Earl D. Lakia and Martin P.J. Zinser
for their help for a previous request on lock utility.


-- Sanyee Tang
   BC Research
   Vancouver, Canada
From: davidc@montagar.com (David L. Cathey)
Newsgroups: comp.os.vms,vmsnet.sources.d
Subject: Re: PHONE port and parameters?
Date: 28 Aug 92 11:50:17 GMT
Organization: Montagar Software Concepts, Plano TX

In article <27AUG199221163604@robot.nuceng.ufl.edu>, sysop                            writes:
> In article <1992Aug25.185621.5207@iitmax.iit.edu>, bruifal@elof.iit.edu (Falke Bruinsma) writes...
>> 
>>Hello
>> 
>>Can anyone tell me what the parameters are for PHONE? Last year I wrote a 
>>program that could dump _any_ message on someone elses screen.
> 
> WARNING: It is easy for the second program (TAP) to get hung during its' read
> from the PHN$ mailbox while it waits for the Phone partner to enter something.
> PHONE's read ASTs will inevitably strip characters from the mailbox before you
> may read them, so trying to "listen in" on conversations becomes a mess of
> sporadic (about every 3rd) character.  Therefore this is program doesn't try
> to fool with listening.

	Back in college (VMS V3.0 days, when PHONE first came out!) I wrote a
program that would read and display conversations, virtually undetectable.
It would read and post-back the data, and then re-read.  Since I/O's are
queued, it tended to interleave with PHONE fairly nicely.  Every now and again
it would transpose a couple of characters, but that was generally ignored as
typo's by those you were tapping :-)

	Sorry, but I don't have the code anymore.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
David L. Cathey		                |INET: davidc@montagar.com
Montagar Software Concepts              |UUCP: ...!montagar!davidc
P. O. Box 260772, Plano TX  75026-0772  |Fone: (214)-618-2117
Newsgroups: comp.os.vms
From: k2@bl.physik.tu-muenchen.de (Klaus Steinberger)
Subject: Re: Does GhostScript support LN03
Organization: Leibniz-Rechenzentrum, Muenchen (Germany)
Date: Sat, 29 Aug 1992 11:38:03 GMT

winston@ssrl01.slac.stanford.edu writes:

>Folks --

>I've been offered a plain-vanilla LN03 printer, which is not otherwise
>currently in use.  I'd like to be able to do graphics and dtp output to
>the printer, which is not directly supported under all the programs I want
>to use.  There is basically no money available to upgrade the printer or
>buy DEC's LN03 Image software.

>So, does anybody know whether GhostScript, the GNU PostScript interpreter,
>supports the plain-vanilla LN03 as an output device?  If so,
>how good a job does it do?  How much memory does the printer need?  Where
>can I get the VMS port?

Yes, ghostscript did support the ln03.

I did not know how well the LN03 driver works, and how many memory it
needs, as I didn't have a LN03. But I'm very pleased by ghostscript.
We at the accelerator lab did use ghostscript regularly to preview
postscript files (eg. generated with tex), and to print out on
Kyocera Printers (HP compatible), and deskjets (color).

Some Postscript fonts did not look as good as with original postscript,
but with 2.5 now this isn't too bad, as the Type 1 fonts from X11R5
are used (this is since 2.4), and now since 2.5 the hints in the fonts 
are used.

You could find ghostscript on prep.ai.mit.edu, or every other mirror
site for gnu software. The ghostscript tar saveset includes the VMS
port too, there are the necessary command files included.
The only thing you need is tar and compress to unpack it.

Sincerely,
Klaus Steinberger

--
Klaus Steinberger               Beschleunigerlabor der TU und LMU Muenchen
Phone: (+49 89)3209 4287        Hochschulgelaende
FAX:   (+49 89)3209 4280        D-8046 Garching, Germany
Internet: Klaus.Steinberger@Physik.Uni-Muenchen.DE
Newsgroups: comp.os.vms
From: tihor@acfcluster.nyu.edu
Subject: Re: JMAIL tool
Organization: New York University
Date: Wed, 26 Aug 1992 21:43:14 GMT

I think SALES@JOINER.COM will work.   Or try JMAIL@JOINER.COM.  Worst come sto
worst ask POSTMASTER@JOINER.COM or CSC@JOINER.COM what the right address is.
From: winalski@adserv.enet.dec.com (Paul S. Winalski)
Newsgroups: comp.os.vms
Subject: Re: Linking C programs
Date: 28 Aug 92 16:53:58 GMT
Reply-To: winalski@adserv.enet.dec.com (Paul S. Winalski)
Organization: Digital Equipment Corporation, Nashua NH


In article <01GO244CRQ7K8WWQ8Q@MARICOPA.EDU>,
shoecraf@mc.bitnet (Steve Shoecraft) writes:

|>    A short time ago, I saw a response to one of these questions which pointed
|>out where the REAL problem is, and why we need to do this in the first place.
|>It was pointed out that since the CRTL wasn't in the sharable image library,
|>IMAGELIB.OLB, and therefore, we must provide a pointer to it implicitly. Well,
|>why not put it there?? To do this, just add it to the image library:
|> 
|>        $ SET DEF SYS$LIBRARY
|>        $ LIB/SHARE IMAGELIB SYS$SHARE:VAXCRTL.EXE
|> 
|>    Now you have to remove the logical name pointer to VAXCRTL.OLB. Do a SH
|>LOG LNK* <enter>. There will be a reference that looks something like this:
|> 
|>        LNK$LIBRARY = "SYS$LIBRARY:VAXCRTL"
|> 
|>    If you have curses and/or g_float support, it may be LNK$LIBRARY_1 or _2.
|>be sure to DEASS/SYS the logical name that points to VAXCRTL. Also, you might
|>also wish to remove/comment out the entry which defines it in the startup
|>command procedure so that if the system is rebooted, users will not go back
|>to linking against the regular library.
|>    If anyone out there might have any comments or warnings on this please let
|>me know... As yet, I have not seen/heard of any problems by doing this...

DON'T DO IT!!!  IT DOESN'T WORK PROPERLY!!

There are two problems with putting VAXCRTL.EXE into IMAGELIB.OLB:

1) VAXCRTL.EXE's global symbols don't conform to VMS naming conventions--they
   do not have a facility prefix.  If you put VAXCRTL.EXE into IMAGELIB, then
   programmers or products on your system using languages other than C may
   encounter errors when linking.  VAXCRTL.EXE defines some very popular names,
   such as "abort", "open", "close", "read", "write", as global symbols.  These
   names are not reserved words in many programming languages.

   Bottom line:  If you put VAXCRTL.EXE into IMAGELIB, other things you have
   on your system may fail to link properly.

2) The VMS Linker has traditionally had a problem resolving common block
   PSECTs (VAX C extern and global variables) that come from shareable images
   retrieved from a shareable image library.  This problem doesn't occur if
   the Linker gets the same shareable image due to its being referenced
   outside the context of a shareable image library.  This bug can cause
   multiple copies of important things like errno, stdin, stdout, and stderr
   to be in your program.  You can get incorrect and unpredictible results.

   Bottom line:  If you put VAXCRTL.EXE into IMAGELIB, the C RTL doesn't work
   properly.  It can fail in obscure ways under equally obscure circumstances.

There is a replacement C RTL, the DEC C RTL, in the works for VMS.  It will
ship with the next major VMS release.  It *is* IMAGELIB-compatible.  When the
DEC C RTL ships, all us C programmers can finally throw away our options
files.

--PSW
From: DWING@UH01.Colorado.EDU (Dan Wing)
Newsgroups: comp.os.vms
Subject: Re: Captive accounts under VMS 5.5
Date: 1 Sep 92 19:10:12 GMT
Distribution: world
Organization: The Internet

Karen Artus, artus@iowasp.physics.uiowa.edu, writes:

>We are running VMS 5.5 and are having problems with captive accounts.
>V5.5 has a new RESTRICTED flag versus CAPTIVE.  Is anyone else having
>problems with captive accounts on V5.5?  Is this a 5.5 bug and is there
>a known fix?

This is a change introduced in VMS V5.2.  The VMS V5.2 meaning of RESTRICTED
is the same as meaning of CAPTIVE in pre-V5.2 systems.  CAPTIVE in V5.2
imposes (or inflicts, depends on your point of view) a more captive 
environment.

If you could elaborate on "problems with captive accounts" it would be 
helpful.

What version of VMS were you running prior to V5.5?

-Dan Wing, DWING@UH01.Colorado.EDU or WING_D@UCOLMCC.BITNET (DGW11)
 Systems Programmer, University Hospital, Denver
From: FORT@RAMPOD-WR.AF.MIL ("TOM FORT")
Newsgroups: comp.os.vms
Subject: RE: Memory listing
Date: 2 Sep 92 13:45:00 GMT
Distribution: world
Organization: The Internet

THE NEG. VALUE COMES FROM THE FACT THAT WHEN A PROCESS IS CREATED IT ALLOCATES 
SPACE IN THE PAGEFILE IN INCREMENTS OF X.  BUT, DOESN'T ACCUALLY USES ITS 
SPACE UNTIL NEEDED.  WHEN IT HAS USED UP ALL OF ITS RESERVED SPACE, IT
RESERVESS ANOTHER CHUNK OF X (NOT NECESSARILY IN THE SAME PAGEFILE). HENCE,
SPACE FREE WILL BE GREATER THAN SPACE RESERVABLE. AND SPACE RESERVABLE IS NOT
LIMITED BY SPACE AVAILABLE. 

WHAT I'M CURIOUS ABOUT IS THE LINE : 

"Of the physical pages in use, 4294964587 pages are permanently allocated 
to VMS."

THAT PUTS YOUR MEMORY CAPACITY IN THE TERABYTE RANGE!!!

HOPE THIS HELPS.

T.

....................................
Thomas J. Fort (Tom)
Computer Systems Manager
Robins AirForce Base, GA   USA

FORT@RAMPOD-WR.AF.MIL (131.45.15.19)  

Voice : (912)926-6701; DSN 468
Fax   : (912)926-9717
From: leichter@lrw.com (Jerry Leichter)
Newsgroups: comp.os.vms
Subject: RE: LIB$SPAWN
Date: 22 Aug 92 13:58:18 GMT
Distribution: world
Organization: The Internet


	Would a kind soul explain to me why in the following code, a
	subprocess is spawned, a sort is started, but the names of the input
	and output files are not passed. Sort comes back to you and asks for
	them.

	---------------------------------------------------- 
	#include stdio
	#include descrip
	#include ssdef

	void spawn( char *DCL_command  );

	main(){ 
	   char *DCL_command;

	   DCL_command = "sort data.PCSA data.sort"; 
	   printf( "%s", DCL_command );
	   spawn( DCL_command  );
	}

	void spawn( char *DCL_command  )
	{
	   int status;

	   $DESCRIPTOR( command , DCL_command  );
	   if ((( status=LIB$SPAWN( &command )) & 1 ) != 1 )
	      LIB$STOP( status );
	}

This one is subtle, and actually quite amusing.  The problem is a misuse of
$DESCRIPTOR.  $DESCRIPTOR is intended to create COMPILE-TIME descriptors -
it's a declaration, not an executable statement.  Here's its definition:

#define $DESCRIPTOR(name,string)					\
	struct dsc$descriptor_s name =					\
	{	sizeof(string)-1,		/* String length */	\
		DSC$K_DTYPE_T,			/* Type text	 */	\
		DSC$K_CLASS_S,			/* Class string	 */	\
		string				/* -> data	 */	\
	}

(I've edited the definition for readability and added the comments.)

The intent is that the string parameter be a quoted string; then, sizeof
applied to it will produce the string's length, including the trailing NUL
(so we subtract 1 and get the length of the actual string).

In your case, string is the (char *) point DCL_command.  sizeof applied to
it produces the size of the POINTER, not of the string it points to, so the
descriptor you produce always has length 3 (and, in this example, value
"sor").  Since "SOR" is a valid abbreviation for SORT on your system, you
do indeed manage to run SORT - but without any arguments.

You need to set the string length to strlen(DCL_command).  Unfortunately,
that can't be done by this or any similar macro, since the fields of a
structure initializer must be compile-time constants, and function calls
don't qualify.  You have to write some code to do it....

							-- Jerry
From: buglady@silver.lcs.mit.edu (Aliza R. Panitz)
Newsgroups: comp.os.vms
Subject: Bug Fix Info - Where do I find it?
Summary: The release notes don't tell all...
Date: 31 Aug 92 16:58:21 GMT
Organization: MIT Laboratory for Computer Science

Looking through the release notes for our next upgrade, 
I notice a number of references to "maintenance release,
incorporating all bug fixes only."  (This is VMS 5.5, 
FORTRAN 5.7, and CDD 4.3 I'm dealing with here.)

We've been bitten before by small "bug fixes" in VMS upgrades
that had disastrous effects.  Where does one find a list of 
bug fixes incorporated in a release?

 - Aliza R. Panitz
   buglady@silver.lcs.mit.edu -or- panitz@aruba.gsfc.nasa.gov
   ARUBA::PANITZ  (SPAN)
From: LUCIUK@SKRSSC.AGR.CA (ROD LUCIUK)
Newsgroups: comp.os.vms
Subject: Re: Vax Station 3100 M38 and asynch decnet
Date: 27 Aug 92 15:40:00 GMT
Distribution: world
Organization: The Internet

Thanks to the following who replied to my query about setting up a decnet line
on a vaxstation 38 over a asynch line!

steve at spg@sunquest.com
matt at cmatt@ocvaxa.cc.oberlin.edu
charles at cts@dragon.com
Willy at
 cis.ohio-state.edu!zaphod.mps.ohio-state.edu!hobbes.physics.uiowa.edu!iowasp.physics.uiowa.edu!syswtr@ucbvax.Berkeley.EDU
AND to the UNKNOWN person(Some how the mail message got lost) whose hints were
invaluable(and encouraging to know that he was running xwindows over the link).
Thank you.

The problem was in two areas. First as a number of you suggested, I had to turn
off flow control on the modem, and let all control be handled by the two vaxes.
Secondly, the TTA2 port on the Vaxstation, when modem control is turned on, the
port will raise and drop DTR. HOWEVER as the unknown person mentioned, for
some reason the VS raises and drops DTR every 30 seconds, which can be a
diaster. As it was suggested, it works better going through TTA3. However there
is no way to drop DTR. For us this means we have to have the other end drop the
carrier to break the line, but for the moment, that is life.

Currently we have the circuit up and running on a regular basis.

Thank you to those that took the time to reply. 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
+  Rodney Luciuk                  Research Station    +
+  luciuk@skrssc.agr.ca           Agriculture Canada  + 
+  System Manager                                     +
+ 'all comments are my own, given freely, and received+
+  at your own risk                                   +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
From: viznyuk@ohstpy.mps.ohio-state.edu
Newsgroups: comp.os.vms
Subject: Command string from within VAX/VMS Pascal ???
Date: 23 Aug 92 16:30:53 EDT

Hi everybody !
Could somebody tell me how to retrieve the command string
from within VAX/VMS Pascal, including the path,program name
and on-line parameters ?
S.V.
From: tillman@swdev.si.com ("Brian Tillman, Smiths Industries, VAX Support, x8425")
Newsgroups: comp.os.vms
Subject: Re: Submitting Jobs for Last Day of Month
Date: 27 Aug 92 13:58:19 GMT
Distribution: world
Organization: The Internet

John E. Babbitt, Jr. (john@cutler.com) writes:

>f$cvtime("01-''f$cvtime("15--+60-","ABSOLUTE","MONTH")--1-","ABSOLUTE")

I like it!  However, while this is very slick, it won't handle year endings.  
Perhaps this is better (I'm writing this as more than one line so it isn't 
improperly wrapped.  It could easily be written as a single DCL statement):

$ month = f$cvtime("15--+60-","absolute","month")
$ year = f$cvtime("15--+60-","absolute","year")
$ date = f$cvtime("1-''month-''year-1-","absolute")
$ sho sym date
  DATE = "30-SEP-1992 00:00:00.00"

The advantage to this method it that it calculates the next year when 
appropriate, instead of defaulting the year to whatever the current year happens 
to be.  If the original had been used for December, the calculated date would 
have been the end of January for 1992, not 1993.

-----------------------------+--------------------------------
 Brian Tillman               | Internet: tillman@swdev.si.com
 Smiths Industries, Inc.     |
 4141 Eastern Ave., MS129    | Hey, I said this stuff myself.
 Grand Rapids, MI 49518-8727 | My company has no part in it.
-----------------------------+--------------------------------
From: LEYDON%BRUCE@VENUS.YCC.YALE.EDU ("Internet LEYDON%BRUCE.DECNET@VENUS.YCC.YALE.EDU")
Newsgroups: comp.os.vms
Subject: BAD BLOCK REPLACEMENT on opticals hangs vax?
Date: 25 Aug 92 19:30:00 GMT
Distribution: world
Organization: The Internet

Hi,
	I have an intermittent problem on my vaxstation 3200. I have a scsi
erasable optical disk subsystem that is hanging up occasionally, (i.e you
mount a disk, do some processing then say dismount and never get the $ back)
Checking monitor process shows your process in LEF state.
	The problem also occurs when backing up from the hard disk to the 
optical, you get no error messages the backup just stops, checking the log
reveals no error messages. I can sometimes get the backup to proceed by
turning the optical off/on.
	Can someone enlighten me on what is going on. I can't determine if
this is a problem with the media, (1 disk does report bad block replacement
errors), the scsi controller which controls only the optical disk, the
host controller inside the disk cabinet or the optical drive.
	Any insight into this would be greatly appreciated.

Thanks
Gary Leydon
BITNET LEYDON@YALEMED
INTERNET LEYDON%BRUCE.DECNET@VENUS.YCC.YALE.EDU
From: cdavis@BME1.IMAGE.UKY.EDU (Charles Davis VA)
Newsgroups: comp.os.vms
Subject: Re: Macterminal V3.0 printing problem
Date: 1 Sep 92 10:27:05 GMT
Organization: The Internet

After recently installing PathWorks I was also quickly disappointed
  with macterminal.
I found uaTerminal by ICE Engineering.  It supports connect and
  terminal tools and is in the public domain.  While I may
  eventually migrate to Reflection (I already own it), I'm happy
  with uaTerm and find it support of the terminal tools (Reflect
  doesn't) a plus...
From: gleason@mwk.uucp
Newsgroups: comp.os.vms
Subject: Re: q:how to add more info in sysuaf file
Date: 3 Sep 92 08:41:23 CST
Distribution: world
Organization: M. W. Kellogg, Houston TX



  If you're a real soldier, you can merely add your data at the end of
the UAF record as a counted string, making the record that much longer, 
and store the offset to your data at UAF$W_USRDATOFF, a word in the
record reserved for just that purpose.
 
 I've used this before to store extra data about accounts in the UAF
record, since that application had to read the UAF record anyway, and it
was convenient to have all the info in one place.

  I forget where I saw this documented, and it may not be documented
anymore. Previous VMS upgrades that changed the format of the UAF
did include support for user data stored in this manner, though, so it
probably is still more or less supported.

  UAF$W_USRDATOFF is define in $UAFDEF, in LIB.MAR.

Lee K. Gleason N5ZMR
Control-G Consultants
713/681-3985
gleason@mwk.uucp
From: moroney@ramblr.enet.dec.com
Newsgroups: comp.os.vms
Subject: Re: Linking C programs
Date: 28 Aug 92 19:00:44 GMT
Organization: Digital Equipment Corporation

In article <01GO244CRQ7K8WWQ8Q@MARICOPA.EDU>, shoecraf@mc.bitnet (Steve Shoecraft) writes...
>    A short time ago, I saw a response to one of these questions which pointed
>out where the REAL problem is, and why we need to do this in the first place.
>It was pointed out that since the CRTL wasn't in the sharable image library,
>IMAGELIB.OLB, and therefore, we must provide a pointer to it implicitly. Well,
>why not put it there?? To do this, just add it to the image library:
> 
>        $ SET DEF SYS$LIBRARY
>        $ LIB/SHARE IMAGELIB SYS$SHARE:VAXCRTL.EXE
...
>    If anyone out there might have any comments or warnings on this please let
>me know... As yet, I have not seen/heard of any problems by doing this...

Arrrghhh!  Good way to hose a system.

If you do this, any FORTRAN or BASIC or assembler program that has a routine
named READ, WRITE, PRINTF etc. or references a routine by these names will
not link correctly and may wind up calling the VAXC RTL instead!

The Fortran, Basic etc. RTLs all have routines name FOR$xxx or BAS$xxx, but
the C language definition requires the name to be printf etc. so DEC-reserved
names such as C$PRINTF couldn't be used.  Therefore, VAXCRTL couldn't
be put into IMAGELIB.

-Mike
Newsgroups: comp.os.vms