HDTenEightyP/NetNews huggingface dataset:
From: dragon@NSCVAX.PRINCETON.EDU (Mighty Firebreather)
Newsgroups: comp.os.vms
Subject: RE: SUBMIT help please.
Date: 11 Jan 93 14:53:52 GMT
Organization: The Internet


	Steven B. Brant sbrant@npal.rn.com writes:
>
>
>		I know I have seen this here before, and I can not seem to
>		find the info wherever I have placed it, so I could find it
>		when I needed it.  ( you know how it goes!)
>
>		Anyway,  I have an EXE program that runs with no problem.
>		The program does not require any input from a user. It is simply
>		a special file processing program.
>
>		When I start the .com file with the following commands, all works
>		well.
>
>		$ define/exec sys$input sys$command
>		$ run/error=nla0:/output=nla0: dua1:[data.sweep]scanit
>
>		Now the problem arises.  I want to SUBMIT this com procedure
>		so we can schedule the execution of the .exe program.
>
>		Submitting the com program causes a failure. Nothing works.
>
>		If I remember correctly, I think I need to use the loginout
>		program to do this, but as I said, I can not find the info
>		on how to do this.
>

	The RUN command you are using creates a detached process!  Is that 
what you meant to do?

	Why are you using a /EXECUTIVE_MODE in your define?  I don't think
it hurts but neither do I see how it can possibly help.  For that matter,
why are you defining it at all?  Since "The program does not require any
input from a user" this seems unnecessary. For a batch job, SYS$INPUT and
SYS$COMMAND would be identical anyway. 

	Why are you directing SYS$ERROR and SYS$OUTPUT to NLA0:?  Why are
you surprised when nothing happens and you get no error messages? 

	Try:

$! DEFINE /USER	NLA0:		SYS$OUTPUT
$! DEFINE /USER	NLA0:		SYS$ERROR
$ RUN DUA1:[DATA.SWEEP]SCANIT

	If you *really* want to suppress output and/or error messages, you
can uncomment the DEFINES for SYS$OUTPUT and/or SYS$ERROR.

*************************************************************************
*                                                                       *
*                        Here, there be dragons!                        *
*                      dragon@nscvax.princeton.edu                      *
*                                                                       *
*                                                Richard B. Gilbert     *
*************************************************************************
From: ecf_stbo@jhuvms.hcf.jhu.edu (UNIX of course, now what was the question?)
Newsgroups: comp.os.vms
Subject: Re: Running old executables on later VMS versions
Date: 8 Jan 1993 09:18 EST
Organization: The Johns Hopkins University - HCF
Distribution: world
NNTP-Posting-Host: jhuvms.hcf.jhu.edu
News-Software: VAX/VMS VNEWS 1.41    

In article <01GT8UWPTG3K9BWII0@SPOCK.FHCRC.ORG>, JOE@SPOCK.FHCRC.ORG (Joe Meadows) writes...
>Anyone care to dredge up some old memories? It's gotta be a lot funner than
>the flame-fest we've been having lately (not to they they haven't been
>somewhat humorous, but even [name-your-comedian-here] gets boring after a
>while).

Up until version 4, DMO was an undocumented (at least not doc. in version
3 manuals) synonym for the DISMOUNT command. This was removed, so I guess you
could say it broke DCL code that used DMO. Obviously this was a holdover from
RSX.


Tom O'Toole - ecf_stbo@jhuvms.hcf.jhu.edu - JHUVMS system programmer 
Homewood Computing Facilities, Johns Hopkins University, Balto. Md. 21218 
>Here comes a jet ski.
>weuh weeuhh weeuhh weeuhh WEEUHH WEEUHH WEEUHH WEEUHH weeuhh weeuhh weeuhh weuh
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: SET TERM/INQ (Was Re: TT_AccPorNam field remains null)
Date: 9 Jan 1993 13:16:05 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 <29834@ursa.bear.com>, RABINOWITZ@VAX5.BEAR.COM (Ari) writes:
=My current attempt at avoiding the problem of SET TERM/INQ shrinking
=DECterms is to not do a SET TERM/INQ at all.  In our shop we don't have
=any VT52's so a VT100 is the lowest common denominator of terminal type
=that we use (even xterm on a Un*x workstation and most PC terminal
=emulators do VT100 reasonably well).
=
=What I do is to set the terminal to VT100 if we don't already know what
=type of terminal it is.  DEC recommended in the release notes for
=DECWindows (in VMS 5.2, VMS 5.3, and VMS 5.4 release notes) that SET
=TERM/INQUIRE not be executed for WT, TW, FT and RT type devices.  I have
=extended that to set the terminal type to VT100 if the terminal type is
=unknown.  I use the following code in LOGIN.COM for my users who need
=it:
=
=$ If F$Getdvi("TT:","DEVTYPE") .Eq. 0 Then $Set Term TT/Device=VT100
=
=I'm sure someone will come up with a case where this may cause problems,
=but I haven't seen it yet.

For the Heath/Zenith H19 terminal, in VT52 mode, the "set baud rate" escape
sequence is the same as the VT100 "set scrolling region" sequence.  Tell the
VAX you've got a VT100 when you've really got an H19, and you'll soon find
yourself trying to talk at the wrong baud rate.
--------------------------------------------------------------------------------
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.
From: tihor@acf3.NYU.EDU (Stephen Tihor)
Newsgroups: comp.os.vms
Subject: Re: Stingray - experiences
Date: 4 Jan 93 06:07:00 GMT
Organization: New York University

Pricing can be an advantage.  The cable system is nicer tho I expect that to 
change.  I prefer the DEC disk modules.
Newsgroups: comp.os.vms,de.comp.os.vms
From: wb@arb-phys.uni-dortmund.de (Wilhelm B. Kloke)
Subject: Re: Does anybody know about Excelan interfaces?
Organization: Institut f. Arbeitsphysiologie a.d. Uni Dortmund
Date: Thu, 7 Jan 93 15:26:39 GMT

In article <1993Jan6.073759.27243@arb-phys.uni-dortmund.de> I wrote:
>interface EXCELAN EXOS 203. I could not find any information about this
Thank all, who replied by mail to this questions. Now I know:
It is an Ethernet interface.
This interface is now worthless in a uVAX on VMS and Ultrix, as it is not
supported any more. The last supported VMS-Version seems to be 5.4.

Perhaps it can be used in a PDP11 under RT11 or RSX11M. Does anybody
know about such software?
-- 
Dipl.-Math. Wilhelm Bernhard Kloke,
Institut fuer Arbeitsphysiologie an der Universitaet Dortmund
Ardeystrasse 67, D-4600 Dortmund 1, Tel. 0231-1084-257
From: RIC@RML2.SRI.COM (Ric Steinberger)
Newsgroups: comp.os.vms
Subject: Turning off DCL WARNING messages: Can it be done?
Date: 8 Jan 93 17:02:27 GMT
Distribution: world
Organization: The Internet


If a rusty DCL programmer may be permitted a question, here's mine:

Can DCL Warning messages be turned off during execution of a command
file?  It seems that SET MESSAGE can turn off everything, but not just
WARNINGS.  

Thanks in advance for any suggestions.

ric steinberger
ric@rml2.sri.com
From: tihor@acf3.NYU.EDU (Stephen Tihor)
Newsgroups: comp.os.vms
Subject: Re: Question about RMS and MSCP-pair
Date: 5 Jan 93 04:35:00 GMT
Organization: New York University

DAHMS@ifk20.mach.uni-karlsruhe.de writes:

	Use ANALYZE/RMS
	: Another interesting varation on that tool would be something to run on
	: a privately mounted disk to read or double read and compare, overwrite
	: with test patterns, and then rewrite each block on a disk.
	Use BACKUP/VERIFY often enough and either restore or delete the file.
	Hack on the file only if it is of great importance.
	Hint: Use DUMP in block mode to read after the error,
	possibly after copying with backup to clear the error, to recover as
	much as possible.

Thanksw that was useful.  For example I never know ANAL/RMS would prompt me 
to fix forced errors in case I liked the bits there.  

I am not sure show a standalong disk scrubber and test tool that hits all the
blocks is replaced by BACKUP/VERIFY unless you meant BACKUP/VERIFY/PHYSICAL
to tape then a BACKUP/VERIFY/PHYSICAL restore of a set of tapes I had
previously made by a program about as messy as the one I suggested containing
all ones, all zeros, and the other test patterns and then the original 
datatapes.

I get the impression that you have had worse forced errors than I have.
IN the 12 forced error events I have had to resolve all but one case the data 
in the file was sufficiently valid to be used in the situation where it occured.
From: mgrthh@rosevc.rose-hulman.edu (Thomas H. Hopson)
Newsgroups: comp.os.vms
Subject: RE: SYSDUMP.DMP File Question...
Date: 8 Jan 1993 18:23:22 GMT
Organization: Rose-Hulman Institute of Technology
Distribution: world
Reply-To: mgrthh@rosevc.rose-hulman.edu
NNTP-Posting-Host: hydra.rose-hulman.edu


In article <009664BF.0BC52900.27241@swdev.si.com>, tillman@swdev.si.com 
("Brian Tillman, Smiths Industries, VAX Support, x8425") writes:

>The concept of primary/secondary 
>page files was eliminated when VMS was altered to allow up to four page files 
>(none of which need to be on the system disk).

This is not entirely true.  If there exists a file named SYS$SYSTEM:PAGEFILE.SYS
then it will be mapped as a "primary" pagefile *before* SYS$SYSTEM:STARTUP.COM
gets control (actually, before the dumpfile gets mapped, even).  If there is 
no such file, no error is issued.  Any pagefile installed by the SYSGEN INSTALL
command is a "secondary" pagefile.

The differences between the types of pagefiles are minor, but in particular,
one characteristic that I commented on a while back is that primary pagefiles
do not have to be set to W:R to have their names appear in a SHOW MEMORY
listing (to unprivileged users), whereas secondary pagefiles *DO*.  Also,
as you mentioned, you can only crash dump into a primary pagefile.

Also, I believe that it is possible to have more than four pagefiles, the
limit being controlled by the SYSGEN parameter PAGFILCNT (which has a maximum
value of 63--63 pagefiles?!).  There's also a SWPFILCNT for swapfiles.

							- Tom

--
Thomas H. Hopson                      work: mgrthh@rosevc.rose-hulman.edu
VMS Manager / CS geek                       mgrthh@rhit
Rose-Hulman Institute of Technology   play: hopsonth@cs.rose-hulman.edu
Terre Haute, Indiana
Newsgroups: comp.os.vms
Subject: Re: Date incorrect after reboot
From: tp@mccall.com (Terry Poot)
Date: Thu,  7 Jan 1993 09:02:47 CST
Reply-To: tp@mccall.com (Terry Poot)
Organization: The McCall Pattern Co., Manhattan, KS, USA
Nntp-Posting-User: tp


In article <1993Jan7.090347.14794@fys.ruu.nl>, hooft@fys.ruu.nl (Rob Hooft)
writes:
>Just make sure you have a cluster: good LAVC practice is to
>synchronize the clocks every once in a while: I think SET TIME/CLUSTER
>will also take care of the problem?

I don't think so. SET TIME with no arguments copies the system time into the TOY
clock. SET TIME/CLUSTER synchronizes the cluster, but does NOT copy it into the
TOY clock on any system. 

Once, one node of a remote cluster I look after was off by an hour, because I
didn't realize it was down when I adjusted the time after a DST change. I fixed
it by doing SET TIME/CLUSTER from a node that was right. A few days later we
lost power, and when the cluster came back up, that same node was again off by
an hour. I always try to remember now to use sysman to do a SET TIME on each
system after synchonizing the cluster time. One of these days, I'll even look up
the SYSMAN command to do that so I can do all from within SYSMAN. :-)
--
Terry Poot <tp@mccall.com>                   The McCall Pattern Company
(uucp: ...!rutgers!depot!mccall!tp)          615 McCall Road
(800)255-2762, in KS (913)776-4041           Manhattan, KS 66502, USA
From: ARNE@KOPC.HHS.DK (Arne Vajhxj)
Newsgroups: comp.os.vms
Subject: Re: Where is the putenv()???
Date: 12 Jan 93 18:14:23 GMT
Distribution: world
Organization: The Internet

> Hi, I am porting a make to VMS.

That has been done before !

> and it needs putenv(). while the getenv()
> is in the stdlib.h but I can find nowhere
> the putenv().

There is no putenv in VAXCRTL !

The some alternatives f.ex.: LIB$SET_LOGICAL and LIB$SET_SYMBOL which sets
defines logicals and symbols. Theese logical/symbols can be retrieved
again with getenv.

Example with LIB$SET_LOGICAL:

#include <descrip.h>

int lib$set_logical();

main()
{
   $DESCRIPTOR(namdes,"TEST");
   $DESCRIPTOR(valdes,"This is a logical");
   lib$set_logical(&namdes,&valdes);
};

Example with LIB$SET_SYMBOL:

#include <descrip.h>

int lib$set_symbol();

main()
{
   $DESCRIPTOR(namdes,"TEST");
   $DESCRIPTOR(valdes,"This is a symbol");
   lib$set_symbol(&namdes,&valdes);
};

PS: If both a logical and a symbol exist for a getenv call, then getenv
    will return the logical.

PPS: Both the above examples will create a "permanent" [may the VMS gods
     forgive me that way of putting it] logical/symbol, while the putenv
     in your code may assume it to be temporary.

Hope it helps !

                                                          Arne

Arne Vajhxj                             local DECNET:  KO::ARNE
Computer Department                     PSI:           PSI%23831001304030::ARNE
Business School of Southern Denmark     Internet:      ARNE@KO.HHS.DK
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Question of anal/disk/repair...
Date: 4 Jan 1993 08:58: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 <9F313A9EF1FF000913@EGFRCUVX>, SABRY@SHEBIN.EG (Sabry Kotob El-Ganzory) writes
>Please, when I issue this a commands:-
>$ anal/disk/repair dia0:
>%VERIFY-W-LOSTHEADER,file(1464,47,1) MAIL.MAI;
>          not found in a directory
>%VERIFY-W-INCQUOTA, QUOTA.SYS indicates 53 blocks used,actual use 57 blocks
>for [300,24]
>-------------------------------------------------------------------------------
>Of coruse, for the first message I go [SYSLOST] then there are file MAIL.MAI
>And the following reading and delete.... IS it a right??
>For the second message, I want from anyone explain this a message ..
>Also, How access with these a message??
>Many Thanks..............

Thank you Sabry.  At last you've asked a question and (though probably by
accident) included all the information needed to answer it.

The first message said that the file wasn't found in a directory.  That usually
means that it was created as a temporary file [though those are usually also
marked for delete] or that someone did a SET FILE/REMOVE on it.  ANAL/DISK will
move it to [SYSLOST].  What you do with it after that is up to you.  You can
check the ownership of the file (DIR/OWNER) to figure out who it once belonged
to, in case that's important to the disposition.

The second message meant that the disk quotas had been corrupted (not very
unusual, unfortunately).  You want to let VERIFY fix this.
--------------------------------------------------------------------------------
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.
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Boot VAX3800 problem, help please!
Date: 9 Jan 1993 13:45:37 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 <5JAN199321194117@spades.aces.com>, gavron@spades.aces.com (Ehud Gavron 602-570-2000 x. 2546) writes:
=In article <1993Jan5.175824.4035@proton.llumc.edu>, lin@primus.llumc.edu (P. James Lin) writes...
=# 
=#When I boot VAX3800 VMS5.3-1 which recovered for power supply failured,
=#message
=#	Error opening primary input file SYS$INPUT
=#	Error in device name or inappropriate device type for operation
=# 
=#What is it? How Should I take care of it?
=
=	I suspect that somewhere in your startup procedures you
=	are using SYS$INPUT.  Instead of SYS$INPUT which may point
=	to the startup database, use SYS$OUTPUT which points to the
=	console output.  
=
=	Normal .COM file: $ define sys$command "''f$trnlnm("sys$input")'"
=	Startup .COM file:$ define sys$command "''f$trnlnm("sys$output")'"

Sorry, Ehud, but your explanation seems very unlikely.  Something's complaining
it can't open its "primary input file."  That's an error message associated
usually with process creation, not with other uses of SYS$INPUT.  I don't want
to bring down any of the systems I manage, but I'd guess the <Startup> process
can't find the startup file given by the SHOW/STARTUP command in SYSBOOT.
--------------------------------------------------------------------------------
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.
Newsgroups: comp.os.vms
From: hays@TECHNET.NM.ORG (Larry 'Purple' Hays)
Subject: glogin.mar
Date: Thu, 07 Jan 93 21:15:07 GMT
Organization: New Mexico Technet   Albuquerque, NM
Reply-To: hays@TECHNET.NM.ORG

Hello all:

I ftp'd glogin.mar and played with it some and it seems like a very handy
utility, and I'd like to thank Anthony McCracken and Northern Arizona
University for making it available.  However, I know just barely enough
Macro-32 to follow the code, so although it looks straightforward and
well written to me, there are lots of things that I'm likely to miss.

I'd like to ask anybody who is using it how it has worked for them.  Are
there any difficulties I need to avoid?  Are there any incompatibilities
with other software that are known?  Are there releases later than 1.1?

Again, thanks to Anthony McCracken and Northern Arizona University - my
questions are intended to make up for my lack of Macro-32 expertise, not
to imply that it's not a well-written package.  Please e-mail and I'll
summarize to the net.

(For those readers unfamiliar with glogin.mar, it allows the user to
login as another user and run under their environment.  No password
is required.  The user (or the image) must have SYSPRV and CMKRNL.)

--------------------------------------------------------------------------
Larry 'Purple' Hays                                    hays@technet.nm.org
--------------------------------------------------------------------------
From: rankin@EQL.CALTECH.EDU (Pat Rankin)
Newsgroups: comp.os.vms
Subject: Re: need ANSI C compiler for VMS (GCC?)
Date: 9 Jan 93 10:46:00 GMT
Organization: The Internet

> I need to find a decent ANSI C compliant compiler for VMS (VAX for now).
> I've tried to get ahold of GCC 2.x.x, but its been taken off the net
> and noone seems to have it available for anon ftp. Can anyone who either
> has it put it out for anon ftp or can someone recommend a better
> alternative compiler?

     You can always get the 2.x (2.3.3 is current) sources and the
1.x (1.42 is current) VMS binaries and rebuild the latest version.
That's the primary purpose for distributing the VMS binaries in the
first place.  The gcc-vms distribution does include some VMS-specific
stuff that is not included in the gcc sources distribution though.
It includes an executable for bison (needed to compile the gcc sources)
and for gas (the assembler back end needed by the compiler, but not
distributed with it), as well as the GCC driver (including DCL command
definition, main program, and support command procedure), and lastly a
set of header files.  The ones with the 1.x binaries aren't very good.

     Calling gcc-vms an ANSI compliant compiler is stretching things
quite a bit, because any code you compile with it will need to be
linked with VAXCRTL.  The run-time library would definitely not pass
as a conforming implmentation.  Bugs aside, it has many global names
in place (mainly the Unix emulation routines) which are not specified
by ANSI and hence potentially conflict with user selected names.

		Pat Rankin, rankin@eql.caltech.edu
From: flowers@memstvx1.memst.edu (Harry Flowers)
Newsgroups: comp.os.vms
Subject: Re: DECwindows and the Starship Enterprise
Date: 8 Jan 93 12:23:05 -0600
Organization: Memphis State University

In article <1993Jan8.115456.13425@bsu-ucs>, 00mjstum@leo.bsuvc.bsu.edu
 (Matthew J. Stum) writes:
> ritley@uimrl7.mrl.uiuc.edu writes:
>> In Kevin Barkes' "DCL Dialogue" column in this month's
>> DECprofessional magazine, he indicates that by changing the
>> value of sm.pointer_shape to -142, in the file
>> DECW$SM_GENERAL.DAT, the DECwindows pointer
>> will be changed to an outline of the "starship Enterprise".
>> 
>> This seems to work.
>> 
>> Is there somewhere a list of accepted pointer types??????
>> Possibly other arrow styles????
> 
> I saw a similar reference quite awhile ago (months) but had _just_ switched
> to Motif and, alas, the table of values given didn't work.  I assume this is
> a DECwindows thing only, not Motif.  Or is it?  Any way I can access this
> alternate list of pointer shapes from Motif?

Yes.  With Motif, sm.pointer_shape is in DECW$SMB_POINTER_COLOR.DAT instead.
For a list of values, see DECW$INCLUDE:CURSORFONT.H (give the negative of the
value shown).  I use -104, the sailboat.
--
Harry Flowers                           Internet: FLOWERS@MEMSTVX1.MEMST.EDU
Memphis State University                & Bitnet: FLOWERS@MEMSTVX1
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: re: Re: Passing parameters to detached processes.
Date: 4 Jan 1993 07:48:06 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 <31DEC199209423681@author.gsfc.nasa.gov>, rkoehler@author.gsfc.nasa.gov (Bob Koehler) writes:
>In article <9212301623.AA19674@uu3.psi.com>, leichter@lrw.com (Jerry Leichter) writes...
>> 
>> 
>>Note that running LOGINOUT to map the CLI in this way is itself undocumented
>>and unsupported....

Where?  And could you please specify things explicitly enough that we'd have
a chance of knowing what you're talking about?  The post to which I'm replying
is the sort of thing that those who object to my flames should *REALLY* be
complaining about.
--------------------------------------------------------------------------------
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.