HDTenEightyP/NetNews huggingface dataset:
From: kega@nobeltech.se (Kent Gabrin)
Subject: Re: DCL question.
Organization: NobelTech AB
Date: Thu, 19 Nov 1992 12:32:26 GMT

In article <a2lq0gk@lynx.unm.edu> hamjavar@hydra.unm.edu (Farid Hamjavar) writes:
   ...Deleted lines...
>
>$ DISPLAY= "WRITE SYS$OUTPUT"
>$ DISPLAY  "''p1'"
>$ DISPLAY  "''p2'"
>
>
>Now if any of the parameters starts with   /    this script will crash :
>
>$ @t.com /parameter1  /parameter2
>%DCL-W-IVQUAL, unrecognized qualifier - check validity, spelling, and placement

Yes and the reason is that VMS thinks that /parameter1 and /parameter2
is a qualifier to the command procedure (compare /OUTPUT which at the
moment is the only qualifier available). To transmit parameters
untouched you must enclosed them by quotationmark ("). In your case:

$ @t.com "/parameter1"  "/parameter2"

Note also that no upcase translations is done either.

See also  $ HELP @

-- 
Kent Gabrin   NobelTech Systems    ! My thinking is not as great as
S-175 88 Jaerfaella      Sweden    ! Oliver Berendinus Bumble /Will Try
KEGA@nobeltech.se ! System Manager (Since 1982) VAXCluster (Since 1985)
Newsgroups: comp.os.vms
Subject: Re: Problems w/ creating print queue on terminal server
From: trounson@wronz.org.nz
Date: 19 Nov 92 09:27:26 +1300

In article <BxvruC.1I8@world.std.com>, reuber@world.std.com (kent b reuber) writes:
> I'm having a problem creating a print queue on a terminal server. We have
> a VAX 8350 and 2 MicroVAX II's clustered. This isn't the first device
> configured this way--we have two other LN03's on a terminal server port.
> I'm trying to follow that COM file and the instructions in the _Maintaning
> a VMS manual, but it doesn't seem to work.
> 
> Here's a journal of the session. All input is sent to the boot node of the
> cluster. Is there something I have to do from the satellite nodes to make
> this work?
> 
> Create a port
> $ set terminal lta7738:/perm/dev=ln03/lowercase/nobroad/width=255
> 
> set protection so only the symbiont can access them
> 
> set up spooling
> 
> define a form
> 
> initialize the queue
> 
> Make sure we got a queue. Looks OK.
> 
> Try it.
> Check the queue a few seconds later. Now it's stalled
> (condensed)
> Kent Reuber                   | Schepens Eye Research Institute
> Computer Operations Manager   | 20 Staniford St.
> reuber@world.std.com          | Boston, MA 02174
> reuber@cdv.eri.harvard.edu    |


You also need the DECserver Management Guide Manual. From your description of
the way you have set up the printers, you have made no mention of setting port
characteristics for the terminal server. You will need set the port up in the
following way from the default settings

access remote
autobaud disabled
autoconnect disabled
autoprompt disabled
break disabled
dedicated none
flow control xon
inactivity logout disabled
interrupts disabled
name port_8
password disabled

we also have broadcast disabled

Hope this solves the problem

Mary Trounson                    Internet:  TROUNSON@WRONZ.ORG.NZ
Computer Systems Officer         PSI:  (05301)30000047::TROUNSON
Wool Research Organisation
Christchurch                    Telephone:  (+64) (+3) 325 2421
New Zealand                           Fax:  (+64) (+3) 325 2717
From: ACSJCE@ORION.DEPAUL.EDU ("Jobin C. Ephrem")
Newsgroups: comp.os.vms
Subject: setpql 7/9
Date: 18 Nov 92 00:39:00 GMT
Distribution: world
Organization: The Internet

Did not receive this part. Can someone please send me a copy.

*******************************************************************************
*******************************************************************************
**			|				|		     **
**      \  |  / 	|	Jobin Ephrem		|      DISCLAIMER    **
**    =*KA-BOOM*=	|  acsjce@orion.depaul.edu	|  Opinion. Yea! I   **
**	/  |  \	  	|  acsjce@hawk.depaul.edu	|  have one and its  **
**			|  acsjce@depaulo 		|  mine alone.       **
*******************************************************************************
*******************************************************************************
From: kjb@calmasd.prime.com (Ken Brucker)
Newsgroups: comp.os.vms
Subject: Re: Fixing SYSTEM-W-HEADERFULL error
Date: 23 Nov 92 19:03:10 GMT
Organization: Computervision, San Diego CA

In article <1992Nov21.120522.27@elmrd6.ineab.ikea.se>, anos@elmrd6.ineab.ikea.se writes:
>> In article <BxoMzw.Jx9@irvine.com>, adam@irvine.com (Adam Beneschan) writes:
>>> Please help us!!  We're getting this error message and we're not sure
>>> what to do.  Please email replies to abeneschan@irvine.com.  
>>> 
>>> Our situation:  We have a Vaxstation 4000 model 60, VMS version V5.5,
>>> 1 gigabyte SCSI drive.  There are 49112 files on our system, and our
>>> INDEXF.SYS file is 49190 blocks.  (Each header in INDEXF.SYS is 1
>>> block, so it's not surprising that these figures are close.)  If we
>>> say SHOW DEVICE/FULL, it says the maximum number of files is about
>>> 257000.  
>> 
> 
> I would say that the problem is that your INDEXF.SYS is too fragmented and
> can't be extended. I have had the same problem recently on a Vax 4000/100 in
> Belgium, and the way to fix it was to do an image backup, initialize the
> volume with /HEADER=n (4096 in my case) and the do the restore with the
> /NOINIT qualifier. Again, the problem is that VMS *assumes* that you will
> not have more that 16 files on your volume (do a DUMP/HEADER to check) and
> therefore allocated 16 blocks when the volume is initialized. After this,
> normal file extension is performed when needed, meaning a badly fragemented
> indexfile after a short period of time.
>  

This is indeed the problem.  To clarify the problem a little more for those
that may be wondering why the index file can't be extended; a normal VMS file
can be extended using multiple file headers (known as extents) in indexf.sys. 
As a file grows and has additional space allocated to it, eventually the table
in it's file header fills and a new extent is allocated for it in Indexf.sys to
hold a continuation table for the block allocations on the volume.

The Index file is not allowed to use multiple extents so once it's table is
filled, that's it.  No more room to grow and the header full error is the
result.

The solution presented above will mostly work.  There's a bug in backup that
causes it to ignore the /noinit qualifier and set the size of the new
indexf.sys file to be just large enough to hold the number of files that are in
the save set you are restoring.  There's a patch available from DSNlink and
from what I hear this is fixed in VMS 5.5-2.

If you really want to set the number of headers for the volume using
/header=n, then you will need to do a selective restore of the whole disk
instead of an image restore.

Ken

-- 
-------------------------------------------------------------------------------
**  Ken Brucker -- VMS/Ultrix Systems Programmer/Mangler -- Computervision
 **  kjb@calmasd.Prime.COM  
  **  Practice Random Kindness and Senseless Acts of Beauty
Newsgroups: comp.os.vms,comp.org.decus
From: murphy@burfle.dco.dec.com (Rick Murphy)
Subject: Re: Wanted: simple modem program for VMS capable of dialing
Organization: Digital Equipment Corporation
Date: Thu, 19 Nov 1992 00:44:59 GMT

In article <1992Nov18.205705.18488@cs.odu.edu> aiko@opium.cs.odu.edu (John K Hayes) writes:
>Anybody know where I can get a simple modem program for VMS (from public
>domain) that will connect to the modem, dial a number and inform of
>connection?  Some simple script capability would be nice - so that I can
>set up auto-login.

SET HOST/DTE does the dial and connect.
The current Beta-test C-Kermit kits have scripting.
There are also commercial products from DEC.
	-Rick
-- 
Rick Murphy, WA1SPT/4			Washington Open Systems Resource Center
Domain:  murphy@burfle.dco.dec.com -or- murphy@dco.dec.com
Bang:    decwrl!burfle.enet!murphy	"Somewhere between 30 and Death"
Ding:  (301) 918-5883				-bumper sticker.
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: BOUND VOLUME SETS: ARE THEY A BAD IDEA?
Date: 20 Nov 1992 03:25:21 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 <2b0bee45.8cdd59.5@BEIZ.mediatex.ch>, Programmierer@BEIZ.mediatex.ch (055485666: MEDIAtex AG) writes:
>I have two questions on volume sets. First here the qurrent config:
>
>     1 RF71      (a single-volume-volume-set)
>
>     3 RF31      (another volume-set)
>
>both of them are now at the limit of there capacity so we ordered a new
>DSSI-SCSI-Disk of 2.5 GByte capacity.
>
>Now my question. on which of these disk' s should be the root-directory?
>which is the best for performance? is it good on a RF31 or should it be on
>the new bigger disk?

It won't make a whole lot of difference.  Any time you do any directory lookup,
the first couple of reads are going to have to come from the INDEX file,
followed by a few reads from FID (4,4,0), both on the first volume in the set. 
That means that [000000]000000.DIR;1's likely to be cached.  And after that,
which is the root volume of the set doesn't make any difference.

>The other question: is it a good idea to use more than one root-directories
>of the volume set? It' s possible to do that, I've tested it, but it this a
>good Idea? (It's nowhere written of that possibility!)

If you've got files that you absolutely have to be able to read, regardless of
whether the root volume fails, then you might want to do that, I think (as well
as forcing all directories you need to find that file and the file itself to be
on the same disk).  Other than that, I can't see any reason for doing it
--------------------------------------------------------------------------------
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: karin@zach.fit.edu (Karin Nicholson)
Newsgroups: comp.os.vms
Subject: Pathworks Print Server ??problem??
Keywords: Mail, convert, migration
Date: 17 Nov 92 20:02:26 GMT
Distribution: usa
Organization: Florida Institute of Technology, Melbourne USA

Howdy fellow netters,

I recently installed Pathworks v1.1 on a VLC running VMS 5.5-1 and Motif 2.0.
This was done so that we could set up a queue for VMS users to print files on
a Apple LaserWriter, with an Ethernet card, connected to on an AppleTalk
network.  The installation was smooth, incredibly easy, and the users have
been `happily' lasering ever since.

There has been one complaint, although it's not a major one, that the printer
has to be initialized from the Macs every time after a VMS job has been sent
to it.  Pathworks seems to do this automagically whenever it senses that the
printer setup is not as expected.  The Mac users have to click on the init
icon/button/whatever in order to init the printer.  They hate it!

My question:  Is there any way around this?  Is there a driver for Pathworks
that is compatible with the Mac's driver?  The Mac folks mentioned that they'd
heard something about a patch for this problem.  Is this true?  If so, what
are the specifics on the patch?

Thanks once again for any light you can shed on this.

-- 

 .-.|     |    |     | |    /------------------\   Karin Nicholson
 |  |-..-.|/.-.|-..-.|*|/  < karin@zach.fit.edu >  VAX Sys Mgr @ Florida Tech 
 `-'| |`-'|\`-'| |`-'|||\   \------------------/   Florida Space Coast LUG Chair
From: SABRY@SHEBIN.EG
Newsgroups: comp.os.vms
Subject: HUNG SYSTEM WHEN SUBMITTING THREE JOBS ON SYS$BATCH
Date: 22 Nov 92 12:35:00 GMT
Distribution: world
Organization: The Internet

HI...
WE  WORK A MICROVAX 3400 ,12MB.
HERE ON A DEVICE USERNAME CALLED SHEBIN AND HE MAKE THREE OR 3 JOBS BY
SUBMITTING AND THIS A JOBS BY FORTRAIN ..OK.
THIS A JOBS WROKED ONCE ON SYS$BATCH AND SYS$BATCH LIMIT_JOPB=3     OK.
THEN AFTER SO SEEM THAT MICROVAX HUNG  AND CANNOT WORKINGD WITH US
AND ALSO ANY USER CONNOT LOGIN TO ACCOUNT OWN IT AND DCL  VERY SLOWER AND
NOT ANY ANSWER WITH US..OK
THEN APPEARS TO US THIS A MESSAGES:-
%SYSTEM-W-PAGEFRAD,PAGE  FILE BADLY FRAGMENTED,SYSTEM CONTINUING.
ALSO,
%SYSTEM-W-PAGECRIT,PAGE FILE SPACE CRITICAL,SYSTEM TRYING TO CONTINUE.
I SORRY ON THIS A MESSAGE BUT I WANT FROM ANYONE SOLVE THIS PROBLEM AND
GIVE ME A MAIL CONTIAN THE SOLVE  TO A ERRORS MESSAGES.
THANKS A LOT FOR NAYONE ON HELP.
E-MAIL OR  ENTERNET:SABRY@SHEBIN.EG
FROM EGYPT.
SABRY
BYE.









Newsgroups: comp.os.vms
From: michelotto@vaxfpd.pd.infn.it (Michele Michelotto)
Subject: Re: "The Man From Mars"
Reply-To: michelot@dxcern.cern.ch
Organization: CERN - European Laboratory for Particle Physics
Date: Tue, 17 Nov 1992 08:53:45 GMT


Groked
Xref: sparky comp.os.vms:18154 comp.sys.dec:6038
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms,comp.sys.dec
Subject: Re: SUMMARY : TUNING QUANTUM
Date: 18 Nov 1992 13:44:01 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 <1992Nov18.184713.493@hhcs.gov.au>, pihlab@hhcs.gov.au writes:
>  PIXSCAN
>  -------
>
>  Has a default of 1 and I'm not sure what it is used for.
>  
>  A setting of 1 was recommended.  Current settings vary on our machines as 
>  shown:
>  
>  CNB12V = 63, CNB01V = 24, CNB06V = 66, CNB08V = 66, CNB13V = 10, and CNB07V 
>  = 16.
>  
>  I'm not sure of why it should be set to 1 and if it is safe to make this 
>  change although there seems to be little correlation between CPU size, 
>  machine technology and the current set value.

$ MCR SYSGEN
SYSGEN>HELP PARAMETERS SPECIAL_PARAMS PIXSCAN

Parameters

  Special_params

    PIXSCAN


       PIXSCAN specifies the maximum number of computable or
       computable-outswapped processes that can receive a special priority
       boost each second. Only normal priority processes (0-15) are eligible
       for such a boost. The priority boost is implemented to avoid potential
       deadlocks, such as when a process executing below DEFPRI acquires a
       volume lock on a critical disk and cannot release it, because the
       process is unable to access the CPU.
--------------------------------------------------------------------------------
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: craig@halcyon.com (Craig Suhadolnik)
Subject: VMS License PAK Problems
Organization: The 23:00 News and Mail Service
Date: Tue, 17 Nov 1992 19:21:34 GMT

Greetings:

We recently did a board level upgrade of a MVII to a MV3900.  The 
new license PAK information was entered into the LMF, and we canceled
the old PAK's.  We did a "license unload vax-vms" and then a "load 
license vax-vms".

The system still utilizes the old PAK information and will only
allow 16 logins as designated by the initial PAK.

Any suggestions as to what we are doing wrong?  Could it be the start
up file?

Thank you for your time!
 
 
-- 
Craig Suhadolnik                                craig@pmi.com 
PACIFIC MICROSYSTEMS, INC                       206-455-4520    
11012 NE 3rd Place, Bellevue, WA  98004         FAX 455-4672
Newsgroups: comp.os.vms
Subject: Re: Another VMS Mail oddity
From: kcb@post.its.mcw.edu (Kent C. Brodie)
Date: 20 Nov 1992 14:34:56 -0600
Distribution: world
Organization: Medical College of Wisconsin  (Milwaukee, WI)
NNTP-Posting-Host: post.its.mcw.edu
X-Newsreader: TIN [version 1.1 PL7]

Andres Molnar - CECOM (molnar@ort.edu.uy) wrote:
(regarding the problem of lowercase VMS MAIL folder names)

: This is not an important problem; in fact, it doesn't even annoy me
: to much, but anyway, I find it interesting. Do you have any idea
: of how to fix the problem, and why it happened? Thanks for your attention.


Andres:   I was able to duplicate this problem, and the only thing
I can think of is that when you created the folder, you had to have
used quotes around the folder name.

MAIL> move/all dcl

will move mail into a folder called "DCL".   If the folder does
not exist, then it is created. no matter how to do it, it will
always create an uppercase foldername.

MAIL> move/all "dcl"

will move mail into a folder called "dcl" (yes, lowercase!).  If the
folder does not exist, it will be created.   As far as the alphabetical
thing goes, it will be sorted alphabetically, in lowercase.  (that
is, all UPPERCASE folders are listed, in order, then the LOWERCASE
ones will be listed, in order).

As far as retrieving the mail messages, you can easily access that
folder, yes, by using quotes.

MAIL> select "dcl"

2 messages selected.

If you don't believe me, try it.   (personally, the fact that mail
does this is actually quite surprising...   However, I'm not sure
you'd consider it a bug or a feature..  :-)
-- 
--------------
Kent C. Brodie - Sr. Systems/Network Manager		brodie@post.its.mcw.edu
Information Technology Systems
Medical College of Wisconsin				(414) 257-8769
From: sloane@kuhub.cc.ukans.edu (Bob Sloane)
Newsgroups: comp.os.vms
Subject: Re: ?Why does this backup go so slow?
Date: 17 Nov 92 15:42:27 GMT
Article-I.D.: kuhub.1992Nov17.094227.44871
Organization: University of Kansas Academic Computing Services

In <1992Nov12.124928.1@woods.ulowell.edu>, welchb@woods.ulowell.edu writes:
> It took us 4.5 hours to do an image backup of an RA90 (80% full of user
> data) onto an RA92?  Why does it not go faster?   [I had prepared a much 
> longer version of the question, with so many particulars, that my boss 
> said to just ask the simple question.]

This is just a guess.  An RA90 holds about 2376153 blocks. If the
device was 80% full, then you had to copy about 780,000,000 bytes.
That means your transfer rate was 780,000,000/(4.5*60*60)=48148 bytes
per second.  Our RA90s here seem to max out about 40 I/Os per second,
or 25ms access time.  If each I/O that backup does averages 1200
bytes(48,000/40), then the I/O time on the RA90 would make sense. Is
the cluster factor on the disk 3? Back may do its I/O based on the
cluster size of the disk.  If the disk is fragmented, that might also
slow down the I/O.

If both devices are connected via the same channel, then you have to
consider the bandwidth of the channel. Will it support more then 100k
bytes per second?
-- 
USmail: Bob Sloane, University of Kansas Computer Center, Lawrence, KS, 66045
E-mail: sloane@kuhub.cc.ukans.edu, sloane@ukanvax.bitnet, AT&T: (913)864-0444
From: gezelter@rlgsc.com
Newsgroups: comp.os.vms
Subject: Re: BACKUP performance - can I expect any better?
Date: 20 Nov 92 21:15:38 GMT
Organization: Robert Gezelter Software Consultant, Flushing, NY

In article <1992Nov18.195835.8983@ac.dal.ca>, ae@ac.dal.ca writes:
> ....
>   These backups do have to run while significant numbers of users are logged
> in.  The batch job that does the backup has the same base CPU priority as the
> interactive users. The disks are not badly fragmented.  The RA92 in the
> example had about 84,000 files, the RF73 about 100,000. 
> 
> Aidan Evans (AE@AC.Dal.CA), Computer Facilities & Operations, University
> Computing & Information Services, Dalhousie University, Halifax, N.S., Canada 
-- 
Aidan,
 
Important note, overall system load can significantly affect 
BACKUP performance. This can happen in two ways. First, if the 
disks being backed up are active during the backup, head movement 
will have a major impact on effective disk transfer rate. Second, 
all of today's tape drives use streaming techniques. If a 
streaming tape drive misses its decision point, it must do a 
reposition.
 
Both of the above reasons are part of the reasoning that 
traditionally has run backups during the third shift. These 
patterns can be extremely variable, depending upon the exact 
working environment.
 
If you are trying to run benchmarks, the only safe comparison is 
on an idle system. Otherwise, you will need to do some very 
extensive checking.  Just another small note before closing. The 
distribution of file lengths can also have a major impact, large 
numbers of small files will, on the average, take longer to 
backup than a small number of very large files.
 
I hope that the above is helpful. If I can be of further 
assistance, please feel free to call or send Email.
 
- 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: rao@moose.cccs.umn.edu (Rao Akella)
Newsgroups: comp.os.vms
Subject: Mapping Shift-Comma/Period keys to <> in Motif 1.1.
Date: 18 Nov 92 22:24:52 GMT
Reply-To: rao@moose.cccs.umn.edu
Organization: Colon Cancer Control Study, University of Minnesota, Minneapolis



I recently installed Motif 1.1.  I enabled the "Comma Key Sends ,<" button in
the "DECterm Keyboard Options" menu, but it didn't seem to work.  I couldn't
find any reference to this problem in the release notes, so I called the help
line, who informed me that this button no longer worked, and if I really wanted
this functionality, I would have to execute the following commands:

	$ @DECW$UTILS:DECW$DEFINE_UTILS
	$ xmodmap -e "keysym comma = comma less"
	$ xmodmap -e "keysym period = period greater"

I plugged these lines into my SYS$LOGIN:DECW$LOGIN.COM, and things seem to work
fine now.

Sorry if this is a FAQ.  Just thought you'd like to know...

-- Rao Akella    <rao@moose.cccs.umn.edu, rao%moose@umnacvx.bitnet>
From: karin@zach.fit.edu (Karin Nicholson)
Newsgroups: comp.os.vms
Subject: Re: User limit in VS4000
Date: 17 Nov 92 18:56:40 GMT
Followup-To: comp.os.vms
Organization: Florida Institute of Technology, Melbourne USA

In article <11NOV92.19244773@wums.wustl.edu> dierker@wums.wustl.edu writes:
>Check you CSLG agreement again... 
>    limits the number of simultaneous logins on a VAXStation to 8 per the
>agreement.  While the (software) licenses provided by the CSLG are unlimited.
>The paper agreement says otherwise.  If you are running unlimited logins you 
>may be in violation of the CSLG agreement.

I was aware of the 8-user limit for CSLG sites, but am not sure how that
applies to the number of DECterm windows open on a VAxstation.  Does each
DECterm session count as a user?  This would be a nutty way of counting
users, but I wouldn't put it past DEC.

Thanks much for any answers.

-- 

 .-.|     |    |     | |    /------------------\   Karin Nicholson
 |  |-..-.|/.-.|-..-.|*|/  < karin@zach.fit.edu >  VAX Sys Mgr @ Florida Tech 
 `-'| |`-'|\`-'| |`-'|||\   \------------------/   Florida Space Coast LUG Chair