root@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa11533; 30 Dec 89 5:00 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa08523; 30 Dec 89 4:52 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0867; Sat, 30
Dec 89 04:56:58 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8415; Sat, 30 Dec 89 04:56:57 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
4502; Fri, 29 Dec 89 22:55:33 C
Date: Sat, 30 Dec 89 04:51:14 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 88 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa16705; 23 Dec 89 4:30 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa14346; 23 Dec 89 4:25 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0985; Sat, 23
Dec 89 03:54:48 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
7862; Sat, 23 Dec 89 03:54:48 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
7608; Fri, 22 Dec 89 21:53:46 C
Date: Fri, 22 Dec 89 17:12:43 GMT
Reply-To: Daniel Berglund <foperator@se.chalmers.tekno>
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: Daniel Berglund <foperator@se.chalmers.tekno>
Subject: Re: Troubles adding batches with 5.9B
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912190723.AA14204@uunet.uu.net>,
munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) writes:
>>Suggestions: 1. Add an interpretation of the error status return from
>>file open attempts. These messages would be a lot more helpful if
>>accompanied by "no privilege for attempted operation" or "no such device"
>>or whatever.
> its just another of the integration problems - vaxc is not quite VMS - at this
> point the NEWS code sees a -1 value from a file operation and says "oh well -
> nice try" - to get past this to the RMS return status is what you are asking
> for... could be interesting!
Maybe I'm overlooking something obvious, but the rms STS value can be
found in vaxc$errno (but I don't know how to access the STV value). Example:
#include errno
#include perror
main()
E
fopen("sahdjgf$$$","r");
perror("Blurp");
printf("%d %d\n",errno,vaxc$errno);
fopen("sdf:asjklhdf$$$","r");
perror("Blurp");
printf("%d %d\n",errno,vaxc$errno);
fopen("gdgd%gsgs","r");
perror("Blurp");
printf("%d %d\n",errno,vaxc$errno);
L
yields:
$ r apa
Blurp: no such file or directory
2 98962
Blurp: no such device or address
6 99524
Blurp: non-translatable vms error code: 0x18744, vms message:
%rms-f-wld, invalid wildcard operation
65535 100164
--
Daniel Berglund (foperator@tekno.chalmers.se, BITNET: FOP@SECTHF51)
Chalmers University of Technology, G|teborg, Swedenroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac07103; 29 Dec 89 1:41 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09384; 29 Dec 89 1:33 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0226; Fri, 29
Dec 89 01:37:25 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
9329; Fri, 29 Dec 89 01:37:25 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8517; Thu, 28 Dec 89 19:27:20 C
Date: Thu, 28 Dec 89 17:41:25 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: Arbitron is coming in 2 parts
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
I'm about to post arbitron V1.0 as a 2 part vms_share set. Extract the parts,
concatenate them, and run the resulting file as a DCL command procedure.
Send any comments or questions to me or post them to this newsgroup.
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa03350; 28 Dec 89 17:56 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa03918; 28 Dec 89 16:21 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7383; Thu, 28
Dec 89 16:25:42 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
6750; Thu, 28 Dec 89 16:25:42 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
4843; Thu, 28 Dec 89 08:20:57 C
Date: Wed, 27 Dec 89 17:03:14 GMT
Reply-To: Jim Gerland <gerland@edu.buffalo.acsu>
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
Comments: Warning -- original Sender: tag was nobody@ACSU.BUFFALO.EDU
From: Jim Gerland <gerland@edu.buffalo.acsu>
Subject: Help with ANU News V5.9
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
I am trying to install V5.9 and have a few questions.
The person who installed V5.8 is no longer here so please bear with me.
We would like to use the NNTP with V5.9 and WIN/TCP V5.1
I decided to just install V5.9 from scratch and have followed the instructions
in the doc (although it is V5.8 - is there a newer doc?).
I get to the point in section 10.9 First Time Execution of NEWS and things
begin to fall apart. It does not do what paragraph 2 says it should (create
files in news_root: and news_manager:).
So then I invoke NEWS and first do a SET NEWSGROUP DEFAULT /SERVER=NEWS
/PROTOCAL=WINTCP /FILEHOLD=0, where NEWS is the name of my Unix newsserver,
eerie.cs.buffalo.edu
Next, I CREATE CONTROL /LOCAL and CREATE JUNK /LOCAL as per the last paragraph
in section 10.9 and then go into rn on my Unix machine and get the latest
version of checkgroups. from the news.admin newsgroup, copy it to my
VAXcluster, edit it appropriately and do an ADD FILE CHECKGROUPS. but this
only adds an entry into the CONTROL newsgroup. Am I doing something wrong?
Any help would be greatly appreciated. Thanks.
Jim Gerland UUCP: ...Eallegra,decvax,watmathL!sunybcs!gerland
CSNET: gerland@buffalo
UCS BITNET: gerland@ubvms (VAX/VMS)
SUNY at Buffalo gerland@ubvm (VM/CMS)root@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa10706; 31 Dec 89 4:55 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa07284; 31 Dec 89 4:44 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4504; Sun, 31
Dec 89 04:49:29 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1864; Sun, 31 Dec 89 04:49:29 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
4058; Sat, 30 Dec 89 22:49:03 C
Date: Sat, 30 Dec 89 15:54:21 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: Arbitron
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
Nice job, Lenny!
I've put the following in my NEWSSKIM.COM to automatically run ARBITRON
near the end of the month. Location is not critical (I have it just after
the SKIM operation). Note that it is not necessary to run this code once
per day, ie it need not be "under" the first-run-of-new-day test, but it
won't hurt if it is, either.
I didn't know if decwrl needed some precise format for the mail subject
line, so I just fudged something.
$ ! ---------------------
$ ! If it's close to the end of the month, run the arbitron program and
$ ! mail the results to decwrl.
$
$ test_mo = f$element(1, "-", f$cvtime("''f$time()'+2-0:0:0", "ABSOLUTE"))
$
$ ! In the preceding line, the "2-0:0:0" means that this code will trigger
$ ! if it's 2 days (ie 48 hours -- or closer) to the end of the last day of
$ ! the month. Modify this (ie make it bigger) if you are far away from
$ ! decwrl (in terms of number of days for delivery). To be included in the
$ ! monthly arbitron stats, the mail message should get there before 00:00
$ ! preceding the first of the new month (or 23:59.59.99 ending the last
$ ! day of the current month, if you prefer).
$
$ this_mo = f$element(1, "-", f$time()) ! note: we use this_mo later.
$ day_of_month_ok = this_mo .nes. test_mo
$
$ ! Have we done it this month already?
$
$ if (f$search("news_log:arbitron.out").eqs."")
$ then
$ ! ok if haven't done it before, at all.
$ month_ok = 1
$ else
$ ! ok if last month run is different from current month.
$ last_arb = f$file("news_log:arbitron.out","CDT")
$ month_ok = f$element(1, "-", last_arb) .nes. this_mo
$ endif
$
$ if (day_of_month_ok .and. month_ok)
$ then
$ write sys$output "Arbitron Beginning at ''f$time()'"
$ run uucp_bin:arbitron
$ rename arbitron.out news_log:
$ purge news_log:arbitron.out
$ host = f$logi("uucp_host_name")
$ mmm_yyyy = f$elem(0, " ", f$time()) - f$elem(0, "-", f$time()) - "-"
$ mail news_log:arbitron.out -
/subj="Arbitron stats from uucp host ''host' for ''mmm_yyyy'" -
uucp%"""netsurvey@decwrl.dec.com""",usenet
$ write sys$output "Arbitron Completed at ''f$time()'"
$ endif
$
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac12347; 30 Dec 89 6:08 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09015; 30 Dec 89 6:02 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0975; Sat, 30
Dec 89 06:07:38 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8513; Sat, 30 Dec 89 06:07:38 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5421; Sat, 30 Dec 89 00:06:40 C
Date: Sat, 30 Dec 89 05:56:06 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 91 attempts over 172 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ad14251; 23 Dec 89 0:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa13513; 23 Dec 89 0:49 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7997; Sat, 23
Dec 89 00:50:31 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
4992; Sat, 23 Dec 89 00:50:31 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8819; Fri, 22 Dec 89 11:52:22 C
Date: Thu, 21 Dec 89 19:55:39 GMT
Reply-To: brodie@edu.mcw.fps
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: brodie@edu.mcw.fps
Subject: Re: RE: rot13 utility in DCL. (and TPU suggestion)
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912200842.AA22375@uunet.uu.net>, munnari!csc.anu.oz.au!gih900@UUNET
.UU.NET (Geoff Huston) writes:
[stuff deleted about my dcl rot13 utility)
> I'm impressed!!!
thanks, geoff!!
>>READ/ROT13, so it shouldn't be TOO tough....)
>
> Wouldn't it be better to have a TPU edit procedure called rot13 to allow you
> to rot the necessary bits??
> (said he trying to avoid having to add the code)
>
> Geoff
hey, now THERE's a neat idea. The tricky part is to tell TPU to do the
ROT13 stuff when WRITING the file upon exit. Sounds neat, and I'm sure
it's pretty easy to do. Unfortunately, I don't know tpu programming
at ALL... never had time do learn it (I really should... maybe this would
be a good project?)
unless someone ELSE wants to do it.....
-------------------------------------------------------------------------------
Kent C. Brodie - Systems Manager brodie@mcw.edu
Medical College of Wisconsin +1 414 778 4500
"Gee, I hope these are the right coordinates..." -Chief O'Brian; STTNGroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa05244; 29 Dec 89 19:07 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa04822; 29 Dec 89 18:56 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7074; Fri, 29
Dec 89 19:01:09 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
5479; Fri, 29 Dec 89 19:01:08 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
9654; Fri, 29 Dec 89 13:00:44 C
Date: Fri, 29 Dec 89 18:49:31 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 107 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab08434; 22 Dec 89 17:57 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09712; 22 Dec 89 17:53 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4931; Fri, 22
Dec 89 17:53:48 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
2225; Fri, 22 Dec 89 17:53:47 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8790; Fri, 22 Dec 89 11:52:08 C
Date: Thu, 21 Dec 89 22:00:50 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: arbitron is coming
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
I've made some progress on writing arbitron. It should be ready in a couple of
days. I'm trying to do approximately the same thing that the unix script does.
I'm writing it in C, using lot's of calls to NEWS functions, there was no
practical way to write it in DCL. I'll send more details soon.
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00625; 30 Dec 89 7:57 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00540; 30 Dec 89 7:50 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 1160; Sat, 30
Dec 89 07:55:29 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8682; Sat, 30 Dec 89 07:55:29 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6670; Sat, 30 Dec 89 01:53:12 C
Date: Sat, 30 Dec 89 07:48:42 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 77 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00313; 23 Dec 89 7:11 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00343; 23 Dec 89 7:05 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3573; Sat, 23
Dec 89 07:07:18 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0514; Sat, 23 Dec 89 07:07:17 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8488; Fri, 22 Dec 89 22:52:21 C
Date: Fri, 22 Dec 89 14:07:42 GMT
Reply-To: brodie@edu.mcw.fps
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: brodie@edu.mcw.fps
Subject: TPU procedure for rot13. My examples. (enjoy)
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
Well, here it is, my first attempt at TPU programming. I have to
thanks Geoff for forcing me to do this (well, not forcing, but I
needed a good excuse to learn how to do junk inside of TPU for a
change.... up to this point, I'd never used my own SECTION file.
Damned neat, once you take the time to learn it......)
First off, I would like to show you my "first" attempt at a rot-13
procedure. works pretty damned good, for a first try....
(no flames, please. I'm a good programmer, but TPU is totally new to
me. It doesn;t help when you don't know all of the neat stuff available..)
!
! TPU procedure to ROT13 a text file.
! Copyright (C) 1989 Kent C. Brodie / Medical College of Wisconsin
! This software is available to all VAX users, and can be distributed
! freely as long as the above copyright is included. So there.
!
procedure eve_rot13
message ("Beginning ROT13 procedure...");
letterpat := ANY("ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
position(beginning_of(current_buffer)); ! Go to the star
t of the current buffer
loop; ! For each character in buffer
exitif (mark(none) = end_of(current_buffer)); ! exit if EOF found
match_pos := search_quietly (letterpat, FORWARD); ! find the next (A-Z|a-z
)
exitif (match_pos = 0);
position (match_pos); ! go there
letterval := ASCII(current_character);
newletter := "";
if (letterval >= 65) and (letterval <= 90)
then
if (letterval > 77)
then
letterval := letterval - 13;
else
letterval := letterval + 13;
endif;
newletter := ASCII(letterval);
else
if (letterval >= 97) and (letterval <= 122)
then
if (letterval > 109)
then
letterval := letterval - 13;
else
letterval := letterval + 13;
endif;
newletter := ASCII(letterval);
endif;
endif;
if (newletter <> "")
then
deleted_char := erase_character(1);
copy_text(newletter);
endif;
endloop;
endprocedure;
that was my first try. Then I realized that was pretty gross, so I
bettered it. I removed all of those multiple if statements, and
used a long alphabet string. Locate the letter, move 13 right,
grab the new letter, done. My first example used too many of the
old "fortran" or "pascal" methods of doing it. The second pass
made use of the TPU string handling junk. much nicer.
!
! TPU procedure to ROT13 a text file.
! Copyright (C) 1989 Kent C. Brodie / Medical College of Wisconsin
! This software is available to all VAX users, and can be distributed
! freely as long as the above copyright is included. So there.
!
! This procedure works by utilizing the string handling capabilities
! of TPU. The string "letters" is used for the rot-ting process, which
! is why there are TWO sets of upper and lower case. In this fashion,
! the "rot" factor (see variable rotfactor) can be changed to create a
! new rot program (such as rot17, etc.).
!
procedure eve_rot13
!declare program constants to be used. Change "rotfactor" to do the
!rot-ting of your choice. Due to popularity, the default is 13.
!
rotfactor := 13;
letterpat := ANY("ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
letters := "ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmno
pqrstuvwxyzabcdefghijklmnopqrstuvwxyz";
message ("Beginning ROT13 procedure...");
position(beginning_of(current_buffer)); ! Go to the top...
loop; ! For each character in buffer
exitif (mark(none) = end_of(current_buffer)); ! exit if EOF found
match_pos := search_quietly (letterpat, FORWARD); ! find the next (A-Z|a-z
)
exitif (match_pos = 0); ! exit if no more letters found
position (match_pos); ! go there
letterpos := index (letters,current_character); ! Look in "letters" for index
letterpos := letterpos + rotfactor; ! ad the "rot factor" to the ind
ex
newletter := substr (letters,letterpos,1); ! create the new letter
deleted_char := erase_character(1); ! delete the old character
copy_text(newletter); ! replace it with the new one.
endloop;
endprocedure;
Now I thought I was done. Nice, clean, compact code. Then I saw it.
(gee, you mean it helps to RTFM?) heh. God bless it, it was right
in the (^!%^(&! book. Seems there's this neat little TPU built-in
called TRANSLATE that does all the work for you, and is quite flexible.
I basically ended up stealing this from the book, but hey, that's what
us computer folk do best, make use of someone ELSE's work..
!
! TPU procedure to ROT13 a text file.
! 12/20/1989 Kent C. Brodie / Medical College of Wisconsin
!
! This procedure example was taken from page 4-352 of the VAXTPU reference
! manual. Seems that TPU has a REAL easy way to do this, using the TRANSLATE
! built-in.
!
procedure eve_rot13
translate (current_buffer,
"NOPQRSTUVWXYZABCDEFGHIJKLMnopqrstuvwxyzabcdefghijklm",
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
message ("ROT13 complete.")
endprocedure;
cute, eh?
(and about 10 times faster than my code. *sigh*...)
-------------------------------------------------------------------------------
Kent C. Brodie - Systems Manager brodie@mcw.edu
Medical College of Wisconsin +1 414 778 4500
"Gee, I hope these are the right coordinates..." -Chief O'Brian; STTNGroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ae07103; 29 Dec 89 1:41 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09401; 29 Dec 89 1:35 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0242; Fri, 29
Dec 89 01:38:58 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
9333; Fri, 29 Dec 89 01:38:57 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8597; Thu, 28 Dec 89 19:30:01 C
Date: Thu, 28 Dec 89 17:43:00 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: arbitron part 2/2
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
+-+-+-+ Beginning of part 2 +-+-+-+
X short cmp;
X
X prev = NULL;
X userp = top_user;
X while (userp && !past)
X`009`123
X`009cmp = strcmp (userp->devdir, devdir);
X`009if (cmp == 0)
X`009 `123
X`009 printf ("duplicated by %s\n", userp->name);
X`009 return (TRUE);
X`009 `125
X`009if (cmp > 0)
X`009 past = TRUE;
X`009else
X`009 `123
X`009 prev = userp;
X`009 userp = userp->next;
X`009 `125
X`009`125
X
X new = malloc (sizeof (USER_STRUCT));
X new->devdir = malloc (strlen (devdir) + 1);
X strcpy (new->devdir, devdir);
X
X new->name = malloc (strlen (name) + 1);
X strcpy (new->name, name);
X
X if (top_user == NULL)
X`009`123
X`009new->next = NULL;
X`009top_user = new;
X`009`125
X else if (prev == NULL)
X`009`123
X`009new->next = top_user;
X`009top_user = new;
X`009`125
X else
X`009`123
X`009new->next = prev->next;
X`009prev->next = new;
X`009`125
X
X return (FALSE);
X`125
X
X
Xopen_uaf ()
X`123
Xint sts;
Xstatic char filename[] = "sysuaf";
Xstatic char dfltname[] = "sys$system:.dat";
X
X uaffab = cc$rms_fab;
X uafrab = cc$rms_rab;
X uaffab.fab$b_fns = sizeof(filename) - 1;
X uaffab.fab$l_fna = filename;
X uaffab.fab$b_dns = sizeof(dfltname) - 1;
X uaffab.fab$l_dna = dfltname;
X uaffab.fab$b_fac = FAB$M_GET;
V uaffab.fab$b_shr = FAB$M_SHRGET `124 FAB$M_SHRPUT `124 FAB$M_SHRDEL `124 FA
XB$M_SHRUPD;
X uafrab.rab$l_rop = RAB$M_NLK;
X uafrab.rab$w_usz = sizeof(record);
X uafrab.rab$l_ubf = (char *) &record;
X uafrab.rab$l_fab = &uaffab;
X
X sts = SYS$OPEN(&uaffab);
X if (!(sts & 1)) lib$stop (sts, uaffab.fab$l_stv);
X
X sts = SYS$CONNECT(&uafrab);
X if (!(sts & 1)) lib$stop (sts, uafrab.rab$l_stv);
X`125
X
X
Xopen_outfiles ()
X`123
X if ((outfile = fopen ("arbitron.out", "w")) == NULL)
X`009`123
X`009printf ("arbitron: unable to open arbitron.out\n");
X`009exit (0);
X`009`125
X`125
$ GOSUB UNPACK_FILE
$ FILE_IS = "ARBITRON.COM"
$ CHECKSUM_IS = 523836491
$ COPY SYS$INPUT VMS_SHARE_DUMMY.DUMMY
V$! run the arbitron program and send the output to netsurvey@decwrl.dec.com,`
X032
X$! with a copy to the local news manager. This should be run in time to
X$! get to decwrl by the first day of the month.
X$!
X$ run arbitron
X$ mail arbitron.out uucp%"""netsurvey@decwrl.dec.com""",usenet
X$ purge arbitron.out
$ GOSUB UNPACK_FILE
$ FILE_IS = "NEWSRC.PATCH"
$ CHECKSUM_IS = 956767850
$ COPY SYS$INPUT VMS_SHARE_DUMMY.DUMMY
X/* This function clears the profile_flags variable. It is used by arbitron
X in between reading NEWSRC files of different users. It must be included
X in newsrc.c because profile_flags is static to that module.
X*/
X
Xclear_profile_flags ()
X`123
X profile_flags = 0;
X`125
$ GOSUB UNPACK_FILE
$ FILE_IS = "UAF.H"
$ CHECKSUM_IS = 558394689
$ COPY SYS$INPUT VMS_SHARE_DUMMY.DUMMY
X/* add the following for the second longword */
X#define PRV$M_UPGRADE 0x00000001
X#define PRV$M_DOWNGRADE 0x00000002
X#define PRV$M_GRPPRV 0x00000004
X#define PRV$M_READALL 0x00000008
X#define PRV$M_SECURITY 0x00000040
X
X
X/* *** MODULE $UAFDEF *** */
X/* ++ */
X/* User authorization file format */
X/* Note: With the exception of the username and account name, */
X/* all strings are blank padded counted strings. Username and */
X/* account name are uncounted, blank padded. */
X/* -- */
X#define UAF$C_USER_ID 1 /* main user ID record */
X#define UAF$C_VERSION1 1 /* this version */
X#define UAF$C_KEYED_PART 52 /* ISAM keys come this far */
X#define UAF$C_AD_II 0 /* AUTODIN-II 32 bit crc code */
X#define UAF$C_PURDY 1 /* Purdy polynomial over salted input */
X#define UAF$C_PURDY_V 2 /* Purdy polynomial + variable length username */
X#define UAF$K_FIXED 644 /* length of fixed portion */
X#define UAF$C_FIXED 644 /* length of fixed portion */
X#define UAF$K_LENGTH 1412
X#define UAF$C_LENGTH 1412
X#define UAF$S_UAFDEF 1412
X
X#define UAF$S_USERNAME 32
X#define UAF$S_PARENT_ID 8
X#define UAF$S_ACCOUNT 32
X#define UAF$S_OWNER 32
X#define UAF$S_DEFDEV 32
X#define UAF$S_DEFDIR 64
X#define UAF$S_LGICMD 64
X#define UAF$S_DEFCLI 32
X#define UAF$S_CLITABLES 32
X#define UAF$S_PWD 8
X#define UAF$S_PWD2 8
X#define UAF$S_EXPIRATION 8
X#define UAF$S_PWD_LIFETIME 8
X#define UAF$S_PWD_DATE 8
X#define UAF$S_PWD2_DATE 8
X#define UAF$S_LASTLOGIN_I 8
X#define UAF$S_LASTLOGIN_N 8
X#define UAF$S_PRIV 8
X#define UAF$S_DEF_PRIV 8
X#define UAF$S_MIN_CLASS 20
X#define UAF$S_MAX_CLASS 20
X#define UAF$S_NETWORK_ACCESS_P 3
X#define UAF$S_NETWORK_ACCESS_S 3
X#define UAF$S_BATCH_ACCESS_P 3
X#define UAF$S_BATCH_ACCESS_S 3
X#define UAF$S_LOCAL_ACCESS_P 3
X#define UAF$S_LOCAL_ACCESS_S 3
X#define UAF$S_DIALUP_ACCESS_P 3
X#define UAF$S_DIALUP_ACCESS_S 3
X#define UAF$S_REMOTE_ACCESS_P 3
X#define UAF$S_REMOTE_ACCESS_S 3
X
Xstruct uaf$r_flags_bits `123
X unsigned uaf$v_disctly:1; /* no user control-y */
X unsigned uaf$v_defcli:1; /* only allow user default CLI */
X unsigned uaf$v_lockpwd:1; /* disable SET PASSWORD command */
X unsigned uaf$v_captive:1; /* captive account (no overrides) */
X unsigned uaf$v_disacnt:1; /* no interactive login */
X unsigned uaf$v_diswelcom:1; /* skip welcome message */
X unsigned uaf$v_dismail:1; /* skip new mail message */
X unsigned uaf$v_nomail:1; /* disable mail delivery */
X unsigned uaf$v_genpwd:1; /* passwords must be generated */
X unsigned uaf$v_pwd_expired:1; /* password has expired */
X unsigned uaf$v_pwd2_expired:1; /* 2nd password has expired */
X unsigned uaf$v_audit:1; /* audit all actions */
X unsigned uaf$v_disreport:1; /* skip last login messages */
X unsigned uaf$v_disreconnect:1; /* inhibit reconnections */
X unsigned uaf$v_autologin:1; /* auto-login only */
X unsigned uaf$v_disforce_pwd_change:1; /* disable forced password change */
X`125;
X
Xstruct uaf$r_primedays_bits `123
X unsigned uaf$v_monday:1; /* bit clear means this is a primary day */
X unsigned uaf$v_tuesday:1; /* bit set means this is an off day */
X unsigned uaf$v_wednesday:1;`032
X unsigned uaf$v_thursday:1;`032
X unsigned uaf$v_friday:1;`032
X unsigned uaf$v_saturday:1;`032
X unsigned uaf$v_sunday:1;`032
X`125;
X
Xstruct UAFDEF
X`123
X char uaf$b_rtype; /* UAF record type */
X char uaf$b_version; /* UAF format version */
X short int uaf$w_usrdatoff; /* offset of counted string of user data */
X char uaf$t_username[UAF$S_USERNAME]; /* username */
X union `123
X long int uaf$l_uic; /* user ID code */
X struct `123
X short int uaf$w_mem; /* member subfield */
X short int uaf$w_grp; /* group subfield */
X `125 uaf$r_uic_fields;
X `125 uaf$r_uic_overlay;
X long int uaf$l_sub_id; /* user sub-identifier */
X long int uaf$q_parent_id[2]; /* identifier of owner of this account */
X char uaf$t_account[UAF$S_ACCOUNT]; /* account name */
X char uaf$t_owner[UAF$S_OWNER]; /* owner's name */
X char uaf$t_defdev[UAF$S_DEFDEV]; /* default device */
X char uaf$t_defdir[UAF$S_DEFDIR]; /* default directory */
X char uaf$t_lgicmd[UAF$S_LGICMD]; /* login command file */
X char uaf$t_defcli[UAF$S_DEFCLI]; /* default command interpreter */
X char uaf$t_clitables[UAF$S_CLITABLES]; /* user CLI tables */
X union `123
X long int uaf$q_pwd[2]; /* hashed password */
X long int uaf$l_pwd; /* 32 bit subfield */
X `125 uaf$r_pwd_overlay;
X long int uaf$q_pwd2[2]; /* second password */
X short int uaf$w_logfails; /* count of login failures */
X short int uaf$w_salt; /* random password salt */
X char uaf$b_encrypt; /* encryption algorithm */
X/* encryption codes */
X char uaf$b_encrypt2; /* encryption algorithm for 2nd pwd */
X char uaf$b_pwd_length; /* minimum password length */
X char uaf$fill_1;
X long int uaf$q_expiration[2]; /* expiration date for account */
X long int uaf$q_pwd_lifetime[2]; /* password lifetime */
X long int uaf$q_pwd_date[2]; /* date of password change */
X long int uaf$q_pwd2_date[2]; /* date of 2nd password change */
X long int uaf$q_lastlogin_i[2]; /* date of last interactive login */
X long int uaf$q_lastlogin_n[2]; /* date of last non-interactive login */
X union `123
X long int uaf$q_priv[2]; /* process privilege vector */
X union prvdef uaf$r_priv;
X `125 uaf$r_priv_overlay;
X union `123
X long int uaf$q_def_priv[2]; /* default process privileges */
X union prvdef uaf$r_def_priv;
X `125 uaf$r_def_priv_overlay;
X char uaf$r_min_class[UAF$S_MIN_CLASS]; /* minimum security class */
X char uaf$r_max_class[UAF$S_MAX_CLASS]; /* maximum security class */
X union `123
X long int uaf$l_flags; /* user flags longword */
X struct uaf$r_flags_bits uaf$r_flags_bits;
X `125 uaf$r_flags_overlay;
V char uaf$b_network_access_p[UAF$S_NETWORK_ACCESS_P]; /* hourly network acce
Xss, primary */
V char uaf$b_network_access_s[UAF$S_NETWORK_ACCESS_S]; /* hourly network acce
Xss, secondary */
V char uaf$b_batch_access_p[UAF$S_BATCH_ACCESS_P]; /* hourly batch access, pr
Ximary */
V char uaf$b_batch_access_s[UAF$S_BATCH_ACCESS_S]; /* hourly batch access, se
Xcondary */
V char uaf$b_local_access_p[UAF$S_LOCAL_ACCESS_P]; /* hourly local access, pr
Ximary */
V char uaf$b_local_access_s[UAF$S_LOCAL_ACCESS_S]; /* hourly local access, se
Xcondary */
V char uaf$b_dialup_access_p[UAF$S_DIALUP_ACCESS_P]; /* hourly dialup access,
X primary */
V char uaf$b_dialup_access_s[UAF$S_DIALUP_ACCESS_S]; /* hourly dialup access,
X secondary */
V char uaf$b_remote_access_p[UAF$S_REMOTE_ACCESS_P]; /* hourly remote access,
X primary */
V char uaf$b_remote_access_s[UAF$S_REMOTE_ACCESS_S]; /* hourly remote access,
X secondary */
X char uaf$fill_2[514 - 502];
X union `123
X char uaf$b_primedays; /* bits representing primary days */
X struct uaf$r_primedays_bits uaf$r_primedays_bits;
X `125 uaf$r_primedays_overlay;
X char uaf$fill_3[516 - 515];
X char uaf$b_pri; /* base process priority */
X char uaf$b_quepri; /* maximum job queuing priority */
X short int uaf$w_maxjobs; /* maximum jobs for UIC allowed */
X/* 0 means no limit */
X short int uaf$w_maxacctjobs; /* maximum jobs for account allowed */
X/* 0 means no limit */
X short int uaf$w_maxdetach; /* maximum detached processes for UIC */
X/* 0 means no limit */
X short int uaf$w_prccnt; /* subprocess creation limit */
X short int uaf$w_biolm; /* buffered I/O limit */
X short int uaf$w_diolm; /* direct I/O limit */
X short int uaf$w_tqcnt; /* timer queue entry limit */
X short int uaf$w_astlm; /* AST queue limit */
X short int uaf$w_enqlm; /* enqueue limit */
X short int uaf$w_fillm; /* open file limit */
X short int uaf$w_shrfillm; /* shared file limit */
X long int uaf$l_wsquota; /* working set size quota */
X long int uaf$l_dfwscnt; /* default working set size */
X long int uaf$l_wsextent; /* working set size limit */
X long int uaf$l_pgflquota; /* page file quota */
X long int uaf$l_cputim; /* CPU time quota */
X long int uaf$l_bytlm; /* buffered I/O byte count limit */
X long int uaf$l_pbytlm; /* paged buffer I/O byte count limit */
X long int uaf$l_jtquota; /* job-wide logical name table creation quota */
X short int uaf$w_proxy_lim; /* number of proxies user can grant */
X short int uaf$w_proxies; /* number of proxies granted */
X short int uaf$w_account_lim; /* number of sub-accounts allowed */
X short int uaf$w_accounts; /* number of sub-accounts in use */
X char uaf$fill_4[UAF$K_LENGTH - 580];
X`125;
X `032
$ GOSUB UNPACK_FILE
$ EXIT
-+-+-+-+-+ End of part 2 +-+-+-+-+-
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa09032; 31 Dec 89 1:41 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa06681; 31 Dec 89 1:33 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3801; Sun, 31
Dec 89 01:38:15 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1159; Sun, 31 Dec 89 01:38:15 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
2567; Sat, 30 Dec 89 19:36:26 C
Date: Fri, 29 Dec 89 23:47:16 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: RE: Troubles adding batches with 5.9B
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912190737.AA16720@uunet.uu.net>,
munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) writes:
>>We are running NEWS 5.9B.
>>
>>Last night a large number of articles that arrived in "rnews" format were
>>rejected by the add/network command, with messages of the form
>>
>> Add <id> news.group: JUNK (Cannot open output file (write access))
>>or
>> Add <id> junk: REJECT (Cannot open output file (write access))
>>
> .......
>
> check which account owns the itm files, and then check the diskquota entry - i
t
> looks like you are out of quota (or out of free space on the disk).
>
Accounts and file ownership and directory protections and all were all as they
used to be and as they are now -- ie I didn't change anything and things just
suddenly started to work again. We don't use diskquotas here, and it's quite
unlikely that the disk was full, since (a) there was 75 Mbytes of free space
the next morning and (b) some batches had some items that were received
correctly.
> its just another of the integration problems - vaxc is not quite VMS - at this
> point the NEWS code sees a -1 value from a file operation and says "oh well -
> nice try" - to get past this to the RMS return status is what you are asking
> for... could be interesting!
imho this is one of the things that really needs to be worked on. It's a
real pain to track down the cause of problems when the only diagnostic is
equivalent to "there's a problem".
Another nicety in the "problem tracking" area would be some trace capability.
Folks are always having troubles getting their news.sys and news.distribution
files right; it'd be nice to turn on a "forwarding trace" feature and get
output like
neighbor system crash: Item not forwarded (news.sys filter)
neighbor system pnet01: Item not forwarded (news.distribution filter)
where each decision is made.
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab09032; 31 Dec 89 1:42 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa06684; 31 Dec 89 1:33 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3806; Sun, 31
Dec 89 01:38:41 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1165; Sun, 31 Dec 89 01:38:41 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
2606; Sat, 30 Dec 89 19:36:37 C
Date: Fri, 29 Dec 89 23:55:41 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: Giving NEWS an internal news command at startup
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <ANU-NEWS%89122011084646@NDSUVM1.BITNET>,
JHWELCH@AMHERST.BITNET (Jonathan_Welch) writes:
> I've been modifying my copy of news.c when new releases come out to enable
> one to supply an internal news command to be executed after news has
> started up [by specifying the command as command-line parameters to NEWS, eg
>
> $ news select ecs.announce
>
> Geoff - if you think this feature is a good idea perhaps you could put
> it into forthcoming releases.
This is nice, but I would like to repeat my earlier request that the
NEWS_INI file be allowed to contain generalized commands and not just
DEFINE/KEY . For instance I (and all users at my shop) would like to
specify SET LINE_EDITING automatically upon NEWS startup; I should be
able to put this command in the NEWS_INI file.
A NEWS command found on the DCL command line, as in the example supplied
by Mr. Welch, should of course be executed after any commands found in
NEWS_INI.
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa09034; 31 Dec 89 1:42 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa06686; 31 Dec 89 1:34 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3811; Sun, 31
Dec 89 01:39:56 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1169; Sun, 31 Dec 89 01:39:56 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
2643; Sat, 30 Dec 89 19:36:49 C
Date: Sat, 30 Dec 89 00:05:06 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: Help with ANU News V5.9
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <15300@eerie.acsu.Buffalo.EDU>,
gerland@acsu.buffalo.edu (Jim Gerland) writes:
> I am trying to install V5.9 and have a few questions....
You're working too hard. If 5.8 is already set up and running, you need
only to place the executable for 5.9 in the same directory where 5.8 has
always been, and do an INSTALL> REPLACE on it. No need to do any of the
"first time execution" stuff. Maybe do an INSTALL> LIST/FULL to make sure
it's installed with SYSPRV. Repeat as necessary for the NNTP-related
images.
Btw, my personal number one favorite mistake when bringing up a new version
of NEWS is to forget to INSTALL the new image file. Without SYSPRV, NEWS
can't do much. Of course my account has SYSPRV so when I test it all works
well, but when others try it... hoo boy.
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa07126; 29 Dec 89 1:46 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09418; 29 Dec 89 1:36 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0249; Fri, 29
Dec 89 01:40:08 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
9337; Fri, 29 Dec 89 01:40:07 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8552; Thu, 28 Dec 89 19:29:43 C
Date: Thu, 28 Dec 89 17:42:15 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: arbitron part 1/2
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
$! ................... Cut between dotted lines and save. ...................
$!...........................................................................
$! VAX/VMS archive file created by VMS_SHARE V06.10 7-FEB-1989.
$!
$! VMS_SHARE was written by James Gray (Gray:OSBUSouth@Xerox.COM) from
$! VMS_SHAR by Michael Bednarek (U3369429@ucsvc.dn.mu.oz.au).
$!
$! To unpack, simply save, concatinate all parts into one file and
$! execute (@) that file.
$!
$! This archive was created by user GLASSMANN
$! on 28-DEC-1989 12:36:14.35.
$!
$! ATTENTION: To keep each article below 31 blocks (15872 bytes), this
$! program has been transmitted in 2 parts. You should
$! concatenate ALL parts to ONE file and execute (@) that file.
$!
$! It contains the following 6 files:
$! AAAREADME.TXT
$! ARBBUILD.COM
$! ARBITRON.C
$! ARBITRON.COM
$! NEWSRC.PATCH
$! UAF.H
$!
$!============================================================================
$ SET SYMBOL/SCOPE=( NOLOCAL, NOGLOBAL )
$ VERSION = F$GETSYI( "VERSION" )
$ IF VERSION .GES "V4.4" THEN GOTO VERSION_OK
$ WRITE SYS$OUTPUT "You are running VMS ''VERSION'; ", -
"VMS_SHARE V06.10 7-FEB-1989 requires VMS V4.4 or higher."
$ EXIT 44 ! SS$_ABORT
$VERSION_OK:
$ GOTO START
$!
$UNPACK_FILE:
$ WRITE SYS$OUTPUT "Creating ''FILE_IS'"
$ DEFINE/USER_MODE SYS$OUTPUT NL:
$ EDIT/TPU/COMMAND=SYS$INPUT/NODISPLAY/OUTPUT='FILE_IS'/NOSECTION -
VMS_SHARE_DUMMY.DUMMY
b_part := CREATE_BUFFER( "EPartL", GET_INFO( COMMAND_LINE, "file_name" ) )
; s_file_spec := GET_INFO( COMMAND_LINE, "output_file" ); SET( OUTPUT_FILE
, b_part, s_file_spec ); b_errors := CREATE_BUFFER( "EErrorsL" ); i_errors
:= 0; pat_beg_1 := ANCHOR & "-+-+-+ Beginning"; pat_beg_2 := LINE_BEGIN
& "+-+-+-+ Beginning"; pat_end := ANCHOR & "+-+-+-+-+ End"; POSITION
( BEGINNING_OF( b_part ) ); LOOP EXITIF SEARCH( SPAN( ' ' )@r_trail
& LINE_END, FORWARD) = 0; POSITION( r_trail ); ERASE( r_trail ); ENDLOOP
; POSITION( BEGINNING_OF( b_part ) ); i_append_line := 0; LOOP EXITIF MARK
( NONE ) = END_OF( b_part ); s_x := ERASE_CHARACTER( 1 )
; IF s_x = '+' THEN r_skip := SEARCH( pat_beg_1, FORWARD, EXACT ); IF r_skip
<> 0 THEN s_x := ''; MOVE_HORIZONTAL( -CURRENT_OFFSET ); ERASE_LINE; ENDIF
; ENDIF; IF s_x = '-' THEN r_skip := SEARCH( pat_end, FORWARD, EXACT )
; IF r_skip <> 0 THEN s_x := ''; MOVE_HORIZONTAL( -CURRENT_OFFSET ); m_skip
:= MARK( NONE ); r_skip := SEARCH( pat_beg_2, FORWARD, EXACT ); IF r_skip
<> 0 THEN POSITION( END_OF( r_skip ) ); MOVE_HORIZONTAL( -CURRENT_OFFSET )
; MOVE_VERTICAL( 1 ); MOVE_HORIZONTAL( -1 ); ELSE POSITION( END_OF( b_part )
); ENDIF; ERASE( CREATE_RANGE( m_skip, MARK( NONE ), NONE ) ); ENDIF; ENDIF
; IF s_x = 'V' THEN s_x := ''; IF i_append_line <> 0 THEN APPEND_LINE
; MOVE_HORIZONTAL( -CURRENT_OFFSET ); ENDIF; i_append_line := 1
; MOVE_VERTICAL( 1 ); ENDIF; IF s_x = 'X' THEN s_x := ''; IF i_append_line
<> 0 THEN APPEND_LINE; MOVE_HORIZONTAL( -CURRENT_OFFSET ); ENDIF
; i_append_line := 0; MOVE_VERTICAL( 1 ); ENDIF; IF s_x <> '' THEN i_errors
:= i_errors + 1; s_text := CURRENT_LINE; POSITION( b_errors ); COPY_TEXT
( "The following line could not be unpacked properly:" ); SPLIT_LINE
; COPY_TEXT( s_x ); COPY_TEXT( s_text ); POSITION( b_part ); MOVE_VERTICAL
( 1 ); ENDIF; ENDLOOP; POSITION( BEGINNING_OF( b_part ) ); LOOP r_x := SEARCH
( "`", FORWARD, EXACT ); EXITIF r_x = 0; POSITION( r_x ); ERASE_CHARACTER( 1
); COPY_TEXT( ASCII( INT( ERASE_CHARACTER( 3 ) ) ) ); ENDLOOP
; IF i_errors = 0 THEN SET( NO_WRITE, b_errors, ON ); ELSE POSITION
( BEGINNING_OF( b_errors ) ); COPY_TEXT( FAO
( "The following !UL errors were detected while unpacking !AS", i_errors
, s_file_spec ) ); SPLIT_LINE; SET( OUTPUT_FILE, b_errors, "SYS$COMMAND" )
; ENDIF; EXIT;
$ DELETE VMS_SHARE_DUMMY.DUMMY;*
$ CHECKSUM 'FILE_IS
$ WRITE SYS$OUTPUT " CHECKSUM ", -
F$ELEMENT( CHECKSUM_IS .EQ. CHECKSUM$CHECKSUM, ",", "failed!!,passed." )
$ RETURN
$!
$START:
$ FILE_IS = "AAAREADME.TXT"
$ CHECKSUM_IS = 1716919986
$ COPY SYS$INPUT VMS_SHARE_DUMMY.DUMMY
XARBITRON - Create statistics to be sent monthly to netsurvey@decwrl.
X
XThis makes heavy use of subroutines that are part of NEWS. Because of
Xthe intertwining of these subroutines, the EXE winds up being over 600
Xblocks. This means that I can't reasonably post the EXE to the net.
XUnfortunately, this means that arbitron is only available to sites with
XC compilers.
X
XTo build arbitron, you first have to include the file NEWSRC.PATCH into
XNEWSRC.C, and recompile it. Then compile and link arbitron. ARBBUILD.COM
Xis included for this purpose, but you'll probably have to modify it for
Xyour site.
X
XARBITRON.COM should be run monthly. This will also have to be modified
Xfor your site.
X
XLenny Glassmann
Xlenny@ccavax.camb.com
Xuunet!ccavax!lenny
$ GOSUB UNPACK_FILE
$ FILE_IS = "ARBBUILD.COM"
$ CHECKSUM_IS = 1027810274
$ COPY SYS$INPUT VMS_SHARE_DUMMY.DUMMY
X$ cc/include=news_src arbitron
X$ link arbitron,[.news_build]news_library/lib,news_src:options_c_link/opt
$ GOSUB UNPACK_FILE
$ FILE_IS = "ARBITRON.C"
$ CHECKSUM_IS = 1140914158
$ COPY SYS$INPUT VMS_SHARE_DUMMY.DUMMY
X/* ARBITRON.C - Calculate number of readers of each newsgroup for ANU NEWS.
X`009This is meant to be run once per month, with results mailed to
X`009netsurvey@decwrl.dec.com on about the 20th of every month.
X`009The results are placed in the file ARBITRON.OUT.
X
X`009The NEWS database is read to determine what is the oldest and newest
X`009item number still on the system for each newsgroup. Then each
X`009user's NEWSRC file is read to determine what the last item was
X`009that the user read. If the last item read is later than the oldest
X`009one still on the system, then the user is counted as a reader of
X`009the newsgroup.
X
X`009This program makes heavy use of subroutines that are part of NEWS to
X`009read the files. This is not the most efficient way to read these
X`009files because work is done by those subroutines which is not needed
X`009by this program. However, it made this easy to write and maintain,
X`009and since it only runs once a month, we don't care how long it takes.
X
X`009Just about all of the numbers generated by this program are estimates
X`009of some kind. Number of users on the system is the number of
X`009accounts that have logged on interactively in the past 30 days. Number
X`009of news readers is the number of users who are readers of at least
X`009one newsgroup. A reader of a newsgroup is someone who has read an
X`009article that has an item number between the lowest and highest
X`009currently stored in the newsgroup.
X
X`009This has only been tested with ANU NEWS V5.9C, VAX C V3.0, VMS V5.2.
X`009If you have another configuration, you'll probably have to at least
X`009recompile this module.
X
X`009This must run from a place that has read access to every NEWSRC
X`009file on the system. The NEWSRC files must be in the user's
X`009default directory to be counted.
X
X`009Lenny Glassmann
X`009Cambridge Computer Associates
X`00956 Beaver St.
X`009New York, NY 10004
X`009(212) 425-5830
X`009lenny@ccavax.camb.com
X
XThanks to:
X`009Geoff Houston (gih900@csc.anu.oz.au) for ANU NEWS.
X`009Joe Meadows (joe@fhcrcvax.bitnet) for the UAF reading code.
X`009Brian Reid (reid@decwrl.dec.com) for the original UNIX arbitron.
X
XHistory:
X`009Dec 27 1989 - Initial release.
X*/
X
X#include "newsinclude"
X#include lnmdef
X#include libdef
X#include "uaf"
X#include "newsdefine"
X
X#define extrnl
X#define iev(v)`009= v
X#define iv(v)`009v
X#include "newsvariables"
X
Xtypedef struct
X `123
X char name[SUBJLEN];
X unsigned int low_item;
X unsigned int high_item;
X unsigned short readers;
X `125 GRP_INFO;
X
Xtypedef struct u_struct
X `123
X char *devdir;
X char *name;
X struct u_struct *next;
X `125 USER_STRUCT;
X
Xtypedef unsigned long SYSTIME[2];
X
Xstatic struct FAB uaffab;
Xstatic struct RAB uafrab;
Xstatic struct UAFDEF record;
Xstatic FILE *outfile;
Xstatic GRP_INFO *grparray;
Xstatic SYSTIME curtime;
Xstatic char version[] = "vms-arbitron-1.0";
Xstatic int news_readers = 0;
Xstatic int num_users = 0;
X
X
Xarbitron ()
Xmain_program
X`123
Xchar reg_filename[] = "newsrc";
X$DESCRIPTOR (delta_d, "30 0");`009`009/* Thirty days */
Xregister int grp_num;
XITM_PTR itmptr;
Xregister GRP_PTR group;
Xchar *cp;
Xchar *cp2;
Xint lastread;
Xchar user_reads_news;
Xint devlen;
Xint dirlen;
Xshort namelen;
Xchar username[UAF$S_USERNAME + 1];
XSYSTIME delta_t;
XSYSTIME month_ago;
X
X /* figure out the date that was 30 days ago */
X sys$gettim (&curtime);
X sys$bintim (&delta_d, &delta_t);
X lib$sub_times (&curtime, &delta_t, &month_ago);
X
X openfiles ();`009/* open and read NEWS.GROUPS */
X open_uaf ();`009/* open SYSUAF.DAT */
X open_outfiles ();
X
X grparray = malloc (sizeof (GRP_INFO) * ga_size);
X
X /* inspect each group (group 0 is not used) */
X for (grp_num=1; grp_num <= ga_size; grp_num++)
X`009`123
X`009map_items (grp_num);`009`009/* read NEWS.ITEMS */
X`009group = ga[grp_num];
X`009strcpy (grparray[grp_num].name, group->grp_name);
X`009itmptr = group->grp_ia;
X`009if (group->grp_count > 0)
X`009 `123
X`009 /* get high and low item numbers (itmptr[0] is not used) */
X`009 grparray[grp_num].low_item = itmptr[1].itm_num;
X`009 grparray[grp_num].high_item = itmptr[group->grp_count].itm_num;
X`009 `125
X`009else
X`009 `123
X`009 grparray[grp_num].low_item = 0;
X`009 grparray[grp_num].high_item = 0;
X`009 `125
X`009grparray[grp_num].readers = 0;
X`009free (group->grp_ia);`009`009/* no longer need item list */
X`009`125
X
X while (SYS$GET (&uafrab) & 1)`009/* read every record in the UAF */
X`009`123
X`009cp = username;
X`009cp2 = record.uaf$t_username;
X`009namelen = 0;
X`009while ((*cp2 != ' ') && (namelen++ < UAF$S_USERNAME))
X`009 *cp++ = *cp2++;
X`009*cp = '\0';
X
X`009printf ("%s ", username);
X
X`009if (lib$sub_times (&record.uaf$q_lastlogin_i, &month_ago,
X`009`009`009`009`009`009&delta_t) == LIB$_NEGTIM)
X`009 `123
X`009 printf ("hasn't logged in this month\n");
X`009 continue;`009`009`009`009/* skip this user */
X`009 `125
X
X`009num_users++;
X
X`009devlen = *record.uaf$t_defdev;
X`009dirlen = *record.uaf$t_defdir;
X`009if (devlen + dirlen + strlen (reg_filename) + 1 > sizeof(news_register))
X`009 `123
X`009 printf ("register file name is too long\n");
X`009 exit (0);
X`009 `125
X`009memcpy (news_register, &record.uaf$t_defdev[1], devlen);
X`009memcpy (news_register + devlen, &record.uaf$t_defdir[1], dirlen);
X`009*(news_register + devlen + dirlen) = '\0';
X
X`009/* if more than one user has the same default directory, and therfore
X`009 the same NEWSRC file, we only want to count it once.`009`009 */
X`009if (duplicate_user (news_register, username))
X`009 continue;
X
X`009strcat (news_register, reg_filename);
X
X`009if (access (news_register, 0) != 0)
X`009 `123
X`009 printf ("no NEWSRC file found\n");
X`009 continue;`009`009`009/* skip this user */
X`009 `125
X
X`009clear_profile_flags ();`009/* get rid of profile info from other users */
X`009read_reg_file ();`009/* read the NEWSRC file */
X`009user_reads_news = FALSE;
X
X`009for (grp_num=1; grp_num <= ga_size; grp_num++)
X`009 `123
X`009 group = ga[grp_num];
X`009 if (group->grp_reg_text)
X`009`009`123
X`009`009cp = group->grp_reg_text +
X`009`009`009strlen (group->grp_reg_text) - 1;
X`009`009while (isdigit (*cp)) /* find last non-digit */
X`009`009 --cp;
X`009`009lastread = atoi (++cp);
X`009`009free (group->grp_reg_text);
X`009`009group->grp_reg_text = NULL;
X`009`009if ((grparray[grp_num].low_item !=
X`009`009`009`009`009grparray[grp_num].high_item) &&
X`009`009 (lastread >= grparray[grp_num].low_item) &&
X`009`009 (lastread <= grparray[grp_num].high_item))
X`009`009 `123
X`009`009 grparray[grp_num].readers++;
X`009`009 user_reads_news = TRUE;
X`009`009 `125
X`009`009`125
X`009 `125
X`009if (user_reads_news)
X`009 `123
X`009 news_readers++;
X`009 printf ("reads news\n");
X`009 `125
X`009else
X`009 `123
X`009 printf ("doesn't read news\n");
X`009 `125
X`009`125
X
X sort_output ();
X write_header ();
X write_data ();
X`125
X
Xwrite_header ()
X`123
Xchar *cp;
Xunsigned int ret;
Xchar timbuf[13];
X$DESCRIPTOR (timbuf_d, timbuf);
X$DESCRIPTOR (systbl, "LNM$SYSTEM_TABLE");
X$DESCRIPTOR (addr_log_d, "NEWS_ADDRESS");
Xunsigned short hostlen;
Xchar hostnam[80];
Xstruct
X `123
X unsigned short buflen;
X unsigned short itmcode;
X char *buf_addr;
X int *retlen;
X `125 hostitm[] =
X`009`123`123sizeof (hostnam) - 1, LNM$_STRING, &hostnam, &hostlen`125,
X`009`1230, 0, 0, 0`125`125;
X
V if ((ret = sys$trnlnm (0, &systbl, &addr_log_d, 0, &hostitm)) != SS$_NORM
XAL)
X`009lib$stop (ret);
X hostnam[hostlen] = '\0';
X
X for (cp = hostnam; *cp; cp++)
X`009*cp = _tolower (*cp);
X fprintf (outfile, "Host %s\n", hostnam);
X fprintf (outfile, "Users %d\n", num_users);
X fprintf (outfile, "NetReaders %d\n", news_readers);
X sys$asctim (0, &timbuf_d, &curtime, 0);
X fprintf (outfile, "ReportDate %c%c%c%.4s\n",
X`009timbuf[3], _tolower(timbuf[4]), _tolower(timbuf[5]), &timbuf[7]);
X fprintf (outfile, "SystemType %s\n", version);
X`125
X
Xwrite_data ()
X`123
X GRP_INFO group_rec;
X struct dsc$descriptor rec_d;
X unsigned int ret;
X
X rec_d.dsc$w_length = sizeof (group_rec);
X rec_d.dsc$b_dtype = DSC$K_DTYPE_T;
X rec_d.dsc$b_class = DSC$K_CLASS_S;
X rec_d.dsc$a_pointer = &group_rec;
X
X while ((ret = sor$return_rec (&rec_d)) == SS$_NORMAL)
X`009fprintf (outfile, "%d %s\n", group_rec.readers, group_rec.name);
X
X if (ret != SS$_ENDOFFILE)
X`009lib$stop (ret);
X`125
X
X/* sort the newsgroup lines in descending order by number of readers */
Xsort_output ()
X`123
X unsigned int ret;
X unsigned short sort_buf[] =
X`009`1231, DSC$K_DTYPE_WU, 1,
X`009(char *)&grparray[0].readers - (char *)&grparray[0],
X`009sizeof (grparray[0].readers)`125;
X unsigned short reclen = sizeof (grparray[0]);
X struct dsc$descriptor rec_d;
X unsigned int grp_num;
X
X if ((ret = sor$begin_sort (&sort_buf, &reclen, 0, 0, 0, 0, 0, 0, 0)) !=
X`009`009`009`009`009`009`009`009 SS$_NORMAL)
X`009lib$stop (ret);
X rec_d.dsc$w_length = sizeof (grparray[0]);
X rec_d.dsc$b_dtype = DSC$K_DTYPE_T;
X rec_d.dsc$b_class = DSC$K_CLASS_S;
X
X for (grp_num=1; grp_num <= ga_size; grp_num++)
X`009`123
X`009rec_d.dsc$a_pointer = &grparray[grp_num];
X`009if ((ret = sor$release_rec (&rec_d)) != SS$_NORMAL)
X`009 lib$stop (ret);
X`009`125
X
X if ((ret = sor$sort_merge (0)) != SS$_NORMAL)
X`009lib$stop (ret);
X`125
X
X
X/* check for users who have the same default directory */
Xduplicate_user (devdir, name)
Xchar *devdir;
Xchar *name;
X`123
X static USER_STRUCT *top_user = NULL;
X register USER_STRUCT *userp;
X register USER_STRUCT *new;
X USER_STRUCT *prev;
X char past = FALSE;
-+-+-+-+-+ End of part 1 +-+-+-+-+-
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa10873; 30 Dec 89 3:58 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa08206; 30 Dec 89 3:48 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0662; Sat, 30
Dec 89 03:53:01 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8242; Sat, 30 Dec 89 03:53:00 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
3222; Fri, 29 Dec 89 21:51:58 C
Date: Sat, 30 Dec 89 03:50:07 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 85 attempts over 170 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac14832; 23 Dec 89 1:39 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa13714; 23 Dec 89 1:38 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 8765; Sat, 23
Dec 89 01:38:41 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
5760; Sat, 23 Dec 89 01:38:41 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
3719; Fri, 22 Dec 89 18:00:04 C
Date: Fri, 22 Dec 89 04:49:58 GMT
Reply-To: tlimonce@uucp.drunivac
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: tlimonce@uucp.drunivac
Subject: Re: How do YOU accept a newsfeed?
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912190551.AA27490@uunet.uu.net>,
munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) writes:
> This has me beat - in newsutility do_newg calls sys_accept (or some similar
> name) which should reject newsgroup ba.forsale and NOT create it - what versio
n
> are you running????
We're running version 5.9B (Or is it 5.9A? I'm not sure. I did at
least one set of patches but it's the set that didn't include a
change to the VERSION command. I guess that's 5.9A, eh?)
Guess what? The problem magically fixed itself. How often does NEWS
re-read the NEWS.SYS file? Only when the first person enters news?
The problem went away after a few days, which is about how often
there is a time when everyone exits news.
I don't think we rebooted, we're pretty 24hrs around here (library
automation mostly, students reading news and mail is the other
reason) so if we crashed & rebooted I would have heard about it.
-Tom
(replying to this addres won't work yet... try tlimonce@drew.bitnet,
tlimonce@drew.uucp, rutgers!drew!tlimonce or limonce@pilot.njin.net)root@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa01224; 30 Dec 89 9:04 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00905; 30 Dec 89 8:53 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 1252; Sat, 30
Dec 89 08:58:52 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8751; Sat, 30 Dec 89 08:58:51 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
7305; Sat, 30 Dec 89 02:57:36 C
Date: Sat, 30 Dec 89 08:50:23 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 119 attempts over 170 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab17809; 23 Dec 89 6:13 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa14845; 23 Dec 89 6:12 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 2520; Sat, 23
Dec 89 06:13:24 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
9405; Sat, 23 Dec 89 06:13:24 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8506; Fri, 22 Dec 89 22:52:34 C
Date: Fri, 22 Dec 89 20:58:52 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: RE: Troubles adding batches with 5.9B
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912190723.AA14204@uunet.uu.net>, munnari!csc.anu.oz.au!gih900@UUNET
.UU.NET (Geoff Huston) writes:
> its just another of the integration problems - vaxc is not quite VMS - at this
> point the NEWS code sees a -1 value from a file operation and says "oh well -
> nice try" - to get past this to the RMS return status is what you are asking
> for... could be interesting!
>
I thought this info could be gotten from the global variable vaxc$errno.
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00266; 2 Jan 90 7:17 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00371; 2 Jan 90 7:07 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3733; Tue, 02
Jan 90 06:59:10 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0096; Tue, 02 Jan 90 06:59:10 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5153; Tue, 02 Jan 90 00:56:08 C
Date: Tue, 2 Jan 90 06:35:33 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa05244; 29 Dec 89 19:07 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa04822; 29 Dec 89 18:56 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7074; Fri, 29
Dec 89 19:01:09 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
5479; Fri, 29 Dec 89 19:01:08 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
9654; Fri, 29 Dec 89 13:00:44 C
Date: Fri, 29 Dec 89 18:49:31 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 107 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab08434; 22 Dec 89 17:57 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09712; 22 Dec 89 17:53 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4931; Fri, 22
Dec 89 17:53:48 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
2225; Fri, 22 Dec 89 17:53:47 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8790; Fri, 22 Dec 89 11:52:08 C
Date: Thu, 21 Dec 89 22:00:50 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: arbitron is coming
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
I've made some progress on writing arbitron. It should be ready in a couple of
days. I'm trying to do approximately the same thing that the unix script does.
I'm writing it in C, using lot's of calls to NEWS functions, there was no
practical way to write it in DCL. I'll send more details soon.
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa01223; 30 Dec 89 9:04 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00908; 30 Dec 89 8:54 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 1257; Sat, 30
Dec 89 08:59:55 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8753; Sat, 30 Dec 89 08:59:55 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
7323; Sat, 30 Dec 89 02:57:50 C
Date: Sat, 30 Dec 89 08:49:41 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 114 attempts over 169 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ah00202; 23 Dec 89 7:05 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00309; 23 Dec 89 7:00 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3364; Sat, 23
Dec 89 06:58:47 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0318; Sat, 23 Dec 89 06:58:45 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8455; Fri, 22 Dec 89 22:51:15 C
Date: Fri, 22 Dec 89 18:22:41 GMT
Reply-To: Earle Ake <fac2@com.saic.dayton>
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: Earle Ake <fac2@com.saic.dayton>
Subject: Re: RE: rot13 utility in DCL. (TPU solution!)
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <3286.2590eeeb@fps.mcw.edu>, brodie@fps.mcw.edu writes:
> In article <8912200842.AA22375@uunet.uu.net>, munnari!csc.anu.oz.au!gih900@UUN
ET.UU.NET (Geoff Huston) writes:
>
>> Wouldn't it be better to have a TPU edit procedure called rot13 to allow you
>> to rot the necessary bits??
>> (said he trying to avoid having to add the code)
I wasn't doing much today so I took out the TPU manual and discovered that TPU
has a function called TRANSLATE which will do what I wanted. The example even
shows a way to use it to rotate every character by 13 to 'encrypt' them!
Sounds like just what I have been looking for. I am using Ted Nieland's
EDT-Plus editor so the procedure will have to be modified slightly for use
with an other TPU based editor. I started with the procedure that changes the
case of the letters either one at a time or those within the select range.
Instead of using the change_case function, I made it the TRANSLATE function.
I have defined the key to be GOLD-T as that was not being used.
Let me know what you think.
--
_____________________________________________________________________________
____ ____ ___
Earle Ake /___ /___/ / / Science Applications International Corporation
____// / / /__ Dayton, Ohio
-----------------------------------------------------------------------------
Internet: fac2%dayton.saic.com@uunet.uu.net uucp: uunet!dayvb!fac2
!EDTP ROT13
!
PROCEDURE EDTP$rot13 !gold r (rot13)
LOCAL character ;
!check for active select
EDTP$select_range;
if EDTP$x_select_range <> 0
then
TRANSLATE (EDTP$x_select_range,
"NOPQRSTUVWXYZABCDEFGHIJKLMnopqrstuvwxyzabcdefghijklm",
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
EDTP$x_select_range:=0;
return;
endif;
!change case of current character
if current_character <> EDTP$x_empty
then
character :=current_character;
TRANSLATE (character,
"NOPQRSTUVWXYZABCDEFGHIJKLMnopqrstuvwxyzabcdefghijklm",
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
erase_character(1);
copy_text(character);
if current_direction <> forward
then
move_horizontal(-2);
endif;
return
endif;
ENDPROCEDURE
DEFINE_KEY('EDTP$rot13',key_name('T',shift_key),"rot13"); ! rot13root@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00267; 2 Jan 90 7:17 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00377; 2 Jan 90 7:09 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3750; Tue, 02
Jan 90 07:00:56 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0104; Tue, 02 Jan 90 07:00:55 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5235; Tue, 02 Jan 90 00:57:19 C
Date: Tue, 2 Jan 90 06:28:41 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa10706; 31 Dec 89 4:55 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa07284; 31 Dec 89 4:44 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4504; Sun, 31
Dec 89 04:49:29 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1864; Sun, 31 Dec 89 04:49:29 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
4058; Sat, 30 Dec 89 22:49:03 C
Date: Sat, 30 Dec 89 15:54:21 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: Arbitron
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
Nice job, Lenny!
I've put the following in my NEWSSKIM.COM to automatically run ARBITRON
near the end of the month. Location is not critical (I have it just after
the SKIM operation). Note that it is not necessary to run this code once
per day, ie it need not be "under" the first-run-of-new-day test, but it
won't hurt if it is, either.
I didn't know if decwrl needed some precise format for the mail subject
line, so I just fudged something.
$ ! ---------------------
$ ! If it's close to the end of the month, run the arbitron program and
$ ! mail the results to decwrl.
$
$ test_mo = f$element(1, "-", f$cvtime("''f$time()'+2-0:0:0", "ABSOLUTE"))
$
$ ! In the preceding line, the "2-0:0:0" means that this code will trigger
$ ! if it's 2 days (ie 48 hours -- or closer) to the end of the last day of
$ ! the month. Modify this (ie make it bigger) if you are far away from
$ ! decwrl (in terms of number of days for delivery). To be included in the
$ ! monthly arbitron stats, the mail message should get there before 00:00
$ ! preceding the first of the new month (or 23:59.59.99 ending the last
$ ! day of the current month, if you prefer).
$
$ this_mo = f$element(1, "-", f$time()) ! note: we use this_mo later.
$ day_of_month_ok = this_mo .nes. test_mo
$
$ ! Have we done it this month already?
$
$ if (f$search("news_log:arbitron.out").eqs."")
$ then
$ ! ok if haven't done it before, at all.
$ month_ok = 1
$ else
$ ! ok if last month run is different from current month.
$ last_arb = f$file("news_log:arbitron.out","CDT")
$ month_ok = f$element(1, "-", last_arb) .nes. this_mo
$ endif
$
$ if (day_of_month_ok .and. month_ok)
$ then
$ write sys$output "Arbitron Beginning at ''f$time()'"
$ run uucp_bin:arbitron
$ rename arbitron.out news_log:
$ purge news_log:arbitron.out
$ host = f$logi("uucp_host_name")
$ mmm_yyyy = f$elem(0, " ", f$time()) - f$elem(0, "-", f$time()) - "-"
$ mail news_log:arbitron.out -
/subj="Arbitron stats from uucp host ''host' for ''mmm_yyyy'" -
uucp%"""netsurvey@decwrl.dec.com""",usenet
$ write sys$output "Arbitron Completed at ''f$time()'"
$ endif
$
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00267; 2 Jan 90 7:17 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00373; 2 Jan 90 7:08 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3738; Tue, 02
Jan 90 07:00:05 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0098; Tue, 02 Jan 90 07:00:04 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5181; Tue, 02 Jan 90 00:56:29 C
Date: Tue, 2 Jan 90 06:29:14 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac12347; 30 Dec 89 6:08 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09015; 30 Dec 89 6:02 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0975; Sat, 30
Dec 89 06:07:38 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8513; Sat, 30 Dec 89 06:07:38 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5421; Sat, 30 Dec 89 00:06:40 C
Date: Sat, 30 Dec 89 05:56:06 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 91 attempts over 172 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ad14251; 23 Dec 89 0:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa13513; 23 Dec 89 0:49 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7997; Sat, 23
Dec 89 00:50:31 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
4992; Sat, 23 Dec 89 00:50:31 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8819; Fri, 22 Dec 89 11:52:22 C
Date: Thu, 21 Dec 89 19:55:39 GMT
Reply-To: brodie@edu.mcw.fps
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: brodie@edu.mcw.fps
Subject: Re: RE: rot13 utility in DCL. (and TPU suggestion)
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912200842.AA22375@uunet.uu.net>, munnari!csc.anu.oz.au!gih900@UUNET
.UU.NET (Geoff Huston) writes:
[stuff deleted about my dcl rot13 utility)
> I'm impressed!!!
thanks, geoff!!
>>READ/ROT13, so it shouldn't be TOO tough....)
>
> Wouldn't it be better to have a TPU edit procedure called rot13 to allow you
> to rot the necessary bits??
> (said he trying to avoid having to add the code)
>
> Geoff
hey, now THERE's a neat idea. The tricky part is to tell TPU to do the
ROT13 stuff when WRITING the file upon exit. Sounds neat, and I'm sure
it's pretty easy to do. Unfortunately, I don't know tpu programming
at ALL... never had time do learn it (I really should... maybe this would
be a good project?)
unless someone ELSE wants to do it.....
-------------------------------------------------------------------------------
Kent C. Brodie - Systems Manager brodie@mcw.edu
Medical College of Wisconsin +1 414 778 4500
"Gee, I hope these are the right coordinates..." -Chief O'Brian; STTNGroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00266; 2 Jan 90 7:17 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00375; 2 Jan 90 7:08 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3745; Tue, 02
Jan 90 07:00:31 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0102; Tue, 02 Jan 90 07:00:31 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5215; Tue, 02 Jan 90 00:56:53 C
Date: Tue, 2 Jan 90 06:27:52 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa03350; 28 Dec 89 17:56 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa03918; 28 Dec 89 16:21 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7383; Thu, 28
Dec 89 16:25:42 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
6750; Thu, 28 Dec 89 16:25:42 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
4843; Thu, 28 Dec 89 08:20:57 C
Date: Wed, 27 Dec 89 17:03:14 GMT
Reply-To: Jim Gerland <gerland@edu.buffalo.acsu>
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
Comments: Warning -- original Sender: tag was nobody@ACSU.BUFFALO.EDU
From: Jim Gerland <gerland@edu.buffalo.acsu>
Subject: Help with ANU News V5.9
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
I am trying to install V5.9 and have a few questions.
The person who installed V5.8 is no longer here so please bear with me.
We would like to use the NNTP with V5.9 and WIN/TCP V5.1
I decided to just install V5.9 from scratch and have followed the instructions
in the doc (although it is V5.8 - is there a newer doc?).
I get to the point in section 10.9 First Time Execution of NEWS and things
begin to fall apart. It does not do what paragraph 2 says it should (create
files in news_root: and news_manager:).
So then I invoke NEWS and first do a SET NEWSGROUP DEFAULT /SERVER=NEWS
/PROTOCAL=WINTCP /FILEHOLD=0, where NEWS is the name of my Unix newsserver,
eerie.cs.buffalo.edu
Next, I CREATE CONTROL /LOCAL and CREATE JUNK /LOCAL as per the last paragraph
in section 10.9 and then go into rn on my Unix machine and get the latest
version of checkgroups. from the news.admin newsgroup, copy it to my
VAXcluster, edit it appropriately and do an ADD FILE CHECKGROUPS. but this
only adds an entry into the CONTROL newsgroup. Am I doing something wrong?
Any help would be greatly appreciated. Thanks.
Jim Gerland UUCP: ...Eallegra,decvax,watmathL!sunybcs!gerland
CSNET: gerland@buffalo
UCS BITNET: gerland@ubvms (VAX/VMS)
SUNY at Buffalo gerland@ubvm (VM/CMS)root@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa09748; 30 Dec 89 1:50 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa07790; 30 Dec 89 1:42 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0280; Sat, 30
Dec 89 01:46:54 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
7898; Sat, 30 Dec 89 01:46:54 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
0524; Fri, 29 Dec 89 19:41:24 C
Date: Sat, 30 Dec 89 01:36:29 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 116 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa14379; 23 Dec 89 1:03 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa13555; 23 Dec 89 0:59 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 8191; Sat, 23
Dec 89 00:59:18 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
5176; Sat, 23 Dec 89 00:59:17 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
0592; Fri, 22 Dec 89 12:59:55 C
Date: Thu, 21 Dec 89 21:41:50 GMT
Reply-To: tanner@edu.cerritos
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: tanner@edu.cerritos
Subject: Re: How to use patch?
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <4981.25908cae@pbs.uucp>, sdroppers@pbs.uucp writes:
> I have checked back, but I cannot find anything, is there a man page or such
> that someone can post (or E-Mail) about how to use patch? If patch is a *nix
> tool then I am in the dark, we have no such docs available.
Here's a DCL file I used to patch 5.9C. I copied the News 5.9 sources and the
5.9C .DIFF files to a directory (yes, on the same disk as sys$scratch) and
executed this file. Everything seemed to update fine. Beware the logical
UTL:, it's where we put our utilities.
$ set noon
$ patch := $utl:patch
$ rename newsmail.c newsvmsmail.c
$ context = 0
$loop: ! loop for all .diff files
$ dif = f$search("*.diff",context)
$ if dif .eqs. "" then exit
$ name = f$parse(dif,,,"name") + f$parse(dif,,,"type") ! make short filename
$ open file 'dif'
$ read/end_of_file=empty file line ! read the diff file header
$ start = f$locate("]",line) + 1
$ dest = f$extract(start,f$length(line)-start,line) ! extract filename
$ read/end_of_file=empty file line
$ read/end_of_file=empty file line ! test for empty diff files
$ write sys$output "patching ''dest'"
$ patch 'dest' 'name''type'
$empty: ! .diff file contains header only, skip patch
$ close file
$ goto loop
If you need patch.exe, it's on gray.cerritos.edu for anonymous ftp.
-Bruce
--
Bruce Tanner (213) 860-2451 x 596 Tanner@Cerritos.EDU
Cerritos College Norwalk, CA cerritos!tannerroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ae00418; 2 Jan 90 7:33 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00459; 2 Jan 90 7:22 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3914; Tue, 02
Jan 90 07:29:40 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0236; Tue, 02 Jan 90 07:29:40 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5630; Tue, 02 Jan 90 01:16:00 C
Date: Tue, 2 Jan 90 06:35:47 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00625; 30 Dec 89 7:57 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00540; 30 Dec 89 7:50 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 1160; Sat, 30
Dec 89 07:55:29 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8682; Sat, 30 Dec 89 07:55:29 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6670; Sat, 30 Dec 89 01:53:12 C
Date: Sat, 30 Dec 89 07:48:42 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 77 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00313; 23 Dec 89 7:11 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00343; 23 Dec 89 7:05 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3573; Sat, 23
Dec 89 07:07:18 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0514; Sat, 23 Dec 89 07:07:17 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8488; Fri, 22 Dec 89 22:52:21 C
Date: Fri, 22 Dec 89 14:07:42 GMT
Reply-To: brodie@edu.mcw.fps
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: brodie@edu.mcw.fps
Subject: TPU procedure for rot13. My examples. (enjoy)
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
Well, here it is, my first attempt at TPU programming. I have to
thanks Geoff for forcing me to do this (well, not forcing, but I
needed a good excuse to learn how to do junk inside of TPU for a
change.... up to this point, I'd never used my own SECTION file.
Damned neat, once you take the time to learn it......)
First off, I would like to show you my "first" attempt at a rot-13
procedure. works pretty damned good, for a first try....
(no flames, please. I'm a good programmer, but TPU is totally new to
me. It doesn;t help when you don't know all of the neat stuff available..)
!
! TPU procedure to ROT13 a text file.
! Copyright (C) 1989 Kent C. Brodie / Medical College of Wisconsin
! This software is available to all VAX users, and can be distributed
! freely as long as the above copyright is included. So there.
!
procedure eve_rot13
message ("Beginning ROT13 procedure...");
letterpat := ANY("ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
position(beginning_of(current_buffer)); ! Go to the star
t of the current buffer
loop; ! For each character in buffer
exitif (mark(none) = end_of(current_buffer)); ! exit if EOF found
match_pos := search_quietly (letterpat, FORWARD); ! find the next (A-Z|a-z
)
exitif (match_pos = 0);
position (match_pos); ! go there
letterval := ASCII(current_character);
newletter := "";
if (letterval >= 65) and (letterval <= 90)
then
if (letterval > 77)
then
letterval := letterval - 13;
else
letterval := letterval + 13;
endif;
newletter := ASCII(letterval);
else
if (letterval >= 97) and (letterval <= 122)
then
if (letterval > 109)
then
letterval := letterval - 13;
else
letterval := letterval + 13;
endif;
newletter := ASCII(letterval);
endif;
endif;
if (newletter <> "")
then
deleted_char := erase_character(1);
copy_text(newletter);
endif;
endloop;
endprocedure;
that was my first try. Then I realized that was pretty gross, so I
bettered it. I removed all of those multiple if statements, and
used a long alphabet string. Locate the letter, move 13 right,
grab the new letter, done. My first example used too many of the
old "fortran" or "pascal" methods of doing it. The second pass
made use of the TPU string handling junk. much nicer.
!
! TPU procedure to ROT13 a text file.
! Copyright (C) 1989 Kent C. Brodie / Medical College of Wisconsin
! This software is available to all VAX users, and can be distributed
! freely as long as the above copyright is included. So there.
!
! This procedure works by utilizing the string handling capabilities
! of TPU. The string "letters" is used for the rot-ting process, which
! is why there are TWO sets of upper and lower case. In this fashion,
! the "rot" factor (see variable rotfactor) can be changed to create a
! new rot program (such as rot17, etc.).
!
procedure eve_rot13
!declare program constants to be used. Change "rotfactor" to do the
!rot-ting of your choice. Due to popularity, the default is 13.
!
rotfactor := 13;
letterpat := ANY("ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
letters := "ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmno
pqrstuvwxyzabcdefghijklmnopqrstuvwxyz";
message ("Beginning ROT13 procedure...");
position(beginning_of(current_buffer)); ! Go to the top...
loop; ! For each character in buffer
exitif (mark(none) = end_of(current_buffer)); ! exit if EOF found
match_pos := search_quietly (letterpat, FORWARD); ! find the next (A-Z|a-z
)
exitif (match_pos = 0); ! exit if no more letters found
position (match_pos); ! go there
letterpos := index (letters,current_character); ! Look in "letters" for index
letterpos := letterpos + rotfactor; ! ad the "rot factor" to the ind
ex
newletter := substr (letters,letterpos,1); ! create the new letter
deleted_char := erase_character(1); ! delete the old character
copy_text(newletter); ! replace it with the new one.
endloop;
endprocedure;
Now I thought I was done. Nice, clean, compact code. Then I saw it.
(gee, you mean it helps to RTFM?) heh. God bless it, it was right
in the (^!%^(&! book. Seems there's this neat little TPU built-in
called TRANSLATE that does all the work for you, and is quite flexible.
I basically ended up stealing this from the book, but hey, that's what
us computer folk do best, make use of someone ELSE's work..
!
! TPU procedure to ROT13 a text file.
! 12/20/1989 Kent C. Brodie / Medical College of Wisconsin
!
! This procedure example was taken from page 4-352 of the VAXTPU reference
! manual. Seems that TPU has a REAL easy way to do this, using the TRANSLATE
! built-in.
!
procedure eve_rot13
translate (current_buffer,
"NOPQRSTUVWXYZABCDEFGHIJKLMnopqrstuvwxyzabcdefghijklm",
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
message ("ROT13 complete.")
endprocedure;
cute, eh?
(and about 10 times faster than my code. *sigh*...)
-------------------------------------------------------------------------------
Kent C. Brodie - Systems Manager brodie@mcw.edu
Medical College of Wisconsin +1 414 778 4500
"Gee, I hope these are the right coordinates..." -Chief O'Brian; STTNGroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id af00416; 2 Jan 90 7:33 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00462; 2 Jan 90 7:23 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3921; Tue, 02
Jan 90 07:30:32 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0240; Tue, 02 Jan 90 07:30:31 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5653; Tue, 02 Jan 90 01:16:28 C
Date: Tue, 2 Jan 90 06:49:40 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ae07103; 29 Dec 89 1:41 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09401; 29 Dec 89 1:35 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0242; Fri, 29
Dec 89 01:38:58 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
9333; Fri, 29 Dec 89 01:38:57 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8597; Thu, 28 Dec 89 19:30:01 C
Date: Thu, 28 Dec 89 17:43:00 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: arbitron part 2/2
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
+-+-+-+ Beginning of part 2 +-+-+-+
X short cmp;
X
X prev = NULL;
X userp = top_user;
X while (userp && !past)
X`009`123
X`009cmp = strcmp (userp->devdir, devdir);
X`009if (cmp == 0)
X`009 `123
X`009 printf ("duplicated by %s\n", userp->name);
X`009 return (TRUE);
X`009 `125
X`009if (cmp > 0)
X`009 past = TRUE;
X`009else
X`009 `123
X`009 prev = userp;
X`009 userp = userp->next;
X`009 `125
X`009`125
X
X new = malloc (sizeof (USER_STRUCT));
X new->devdir = malloc (strlen (devdir) + 1);
X strcpy (new->devdir, devdir);
X
X new->name = malloc (strlen (name) + 1);
X strcpy (new->name, name);
X
X if (top_user == NULL)
X`009`123
X`009new->next = NULL;
X`009top_user = new;
X`009`125
X else if (prev == NULL)
X`009`123
X`009new->next = top_user;
X`009top_user = new;
X`009`125
X else
X`009`123
X`009new->next = prev->next;
X`009prev->next = new;
X`009`125
X
X return (FALSE);
X`125
X
X
Xopen_uaf ()
X`123
Xint sts;
Xstatic char filename[] = "sysuaf";
Xstatic char dfltname[] = "sys$system:.dat";
X
X uaffab = cc$rms_fab;
X uafrab = cc$rms_rab;
X uaffab.fab$b_fns = sizeof(filename) - 1;
X uaffab.fab$l_fna = filename;
X uaffab.fab$b_dns = sizeof(dfltname) - 1;
X uaffab.fab$l_dna = dfltname;
X uaffab.fab$b_fac = FAB$M_GET;
V uaffab.fab$b_shr = FAB$M_SHRGET `124 FAB$M_SHRPUT `124 FAB$M_SHRDEL `124 FA
XB$M_SHRUPD;
X uafrab.rab$l_rop = RAB$M_NLK;
X uafrab.rab$w_usz = sizeof(record);
X uafrab.rab$l_ubf = (char *) &record;
X uafrab.rab$l_fab = &uaffab;
X
X sts = SYS$OPEN(&uaffab);
X if (!(sts & 1)) lib$stop (sts, uaffab.fab$l_stv);
X
X sts = SYS$CONNECT(&uafrab);
X if (!(sts & 1)) lib$stop (sts, uafrab.rab$l_stv);
X`125
X
X
Xopen_outfiles ()
X`123
X if ((outfile = fopen ("arbitron.out", "w")) == NULL)
X`009`123
X`009printf ("arbitron: unable to open arbitron.out\n");
X`009exit (0);
X`009`125
X`125
$ GOSUB UNPACK_FILE
$ FILE_IS = "ARBITRON.COM"
$ CHECKSUM_IS = 523836491
$ COPY SYS$INPUT VMS_SHARE_DUMMY.DUMMY
V$! run the arbitron program and send the output to netsurvey@decwrl.dec.com,`
X032
X$! with a copy to the local news manager. This should be run in time to
X$! get to decwrl by the first day of the month.
X$!
X$ run arbitron
X$ mail arbitron.out uucp%"""netsurvey@decwrl.dec.com""",usenet
X$ purge arbitron.out
$ GOSUB UNPACK_FILE
$ FILE_IS = "NEWSRC.PATCH"
$ CHECKSUM_IS = 956767850
$ COPY SYS$INPUT VMS_SHARE_DUMMY.DUMMY
X/* This function clears the profile_flags variable. It is used by arbitron
X in between reading NEWSRC files of different users. It must be included
X in newsrc.c because profile_flags is static to that module.
X*/
X
Xclear_profile_flags ()
X`123
X profile_flags = 0;
X`125
$ GOSUB UNPACK_FILE
$ FILE_IS = "UAF.H"
$ CHECKSUM_IS = 558394689
$ COPY SYS$INPUT VMS_SHARE_DUMMY.DUMMY
X/* add the following for the second longword */
X#define PRV$M_UPGRADE 0x00000001
X#define PRV$M_DOWNGRADE 0x00000002
X#define PRV$M_GRPPRV 0x00000004
X#define PRV$M_READALL 0x00000008
X#define PRV$M_SECURITY 0x00000040
X
X
X/* *** MODULE $UAFDEF *** */
X/* ++ */
X/* User authorization file format */
X/* Note: With the exception of the username and account name, */
X/* all strings are blank padded counted strings. Username and */
X/* account name are uncounted, blank padded. */
X/* -- */
X#define UAF$C_USER_ID 1 /* main user ID record */
X#define UAF$C_VERSION1 1 /* this version */
X#define UAF$C_KEYED_PART 52 /* ISAM keys come this far */
X#define UAF$C_AD_II 0 /* AUTODIN-II 32 bit crc code */
X#define UAF$C_PURDY 1 /* Purdy polynomial over salted input */
X#define UAF$C_PURDY_V 2 /* Purdy polynomial + variable length username */
X#define UAF$K_FIXED 644 /* length of fixed portion */
X#define UAF$C_FIXED 644 /* length of fixed portion */
X#define UAF$K_LENGTH 1412
X#define UAF$C_LENGTH 1412
X#define UAF$S_UAFDEF 1412
X
X#define UAF$S_USERNAME 32
X#define UAF$S_PARENT_ID 8
X#define UAF$S_ACCOUNT 32
X#define UAF$S_OWNER 32
X#define UAF$S_DEFDEV 32
X#define UAF$S_DEFDIR 64
X#define UAF$S_LGICMD 64
X#define UAF$S_DEFCLI 32
X#define UAF$S_CLITABLES 32
X#define UAF$S_PWD 8
X#define UAF$S_PWD2 8
X#define UAF$S_EXPIRATION 8
X#define UAF$S_PWD_LIFETIME 8
X#define UAF$S_PWD_DATE 8
X#define UAF$S_PWD2_DATE 8
X#define UAF$S_LASTLOGIN_I 8
X#define UAF$S_LASTLOGIN_N 8
X#define UAF$S_PRIV 8
X#define UAF$S_DEF_PRIV 8
X#define UAF$S_MIN_CLASS 20
X#define UAF$S_MAX_CLASS 20
X#define UAF$S_NETWORK_ACCESS_P 3
X#define UAF$S_NETWORK_ACCESS_S 3
X#define UAF$S_BATCH_ACCESS_P 3
X#define UAF$S_BATCH_ACCESS_S 3
X#define UAF$S_LOCAL_ACCESS_P 3
X#define UAF$S_LOCAL_ACCESS_S 3
X#define UAF$S_DIALUP_ACCESS_P 3
X#define UAF$S_DIALUP_ACCESS_S 3
X#define UAF$S_REMOTE_ACCESS_P 3
X#define UAF$S_REMOTE_ACCESS_S 3
X
Xstruct uaf$r_flags_bits `123
X unsigned uaf$v_disctly:1; /* no user control-y */
X unsigned uaf$v_defcli:1; /* only allow user default CLI */
X unsigned uaf$v_lockpwd:1; /* disable SET PASSWORD command */
X unsigned uaf$v_captive:1; /* captive account (no overrides) */
X unsigned uaf$v_disacnt:1; /* no interactive login */
X unsigned uaf$v_diswelcom:1; /* skip welcome message */
X unsigned uaf$v_dismail:1; /* skip new mail message */
X unsigned uaf$v_nomail:1; /* disable mail delivery */
X unsigned uaf$v_genpwd:1; /* passwords must be generated */
X unsigned uaf$v_pwd_expired:1; /* password has expired */
X unsigned uaf$v_pwd2_expired:1; /* 2nd password has expired */
X unsigned uaf$v_audit:1; /* audit all actions */
X unsigned uaf$v_disreport:1; /* skip last login messages */
X unsigned uaf$v_disreconnect:1; /* inhibit reconnections */
X unsigned uaf$v_autologin:1; /* auto-login only */
X unsigned uaf$v_disforce_pwd_change:1; /* disable forced password change */
X`125;
X
Xstruct uaf$r_primedays_bits `123
X unsigned uaf$v_monday:1; /* bit clear means this is a primary day */
X unsigned uaf$v_tuesday:1; /* bit set means this is an off day */
X unsigned uaf$v_wednesday:1;`032
X unsigned uaf$v_thursday:1;`032
X unsigned uaf$v_friday:1;`032
X unsigned uaf$v_saturday:1;`032
X unsigned uaf$v_sunday:1;`032
X`125;
X
Xstruct UAFDEF
X`123
X char uaf$b_rtype; /* UAF record type */
X char uaf$b_version; /* UAF format version */
X short int uaf$w_usrdatoff; /* offset of counted string of user data */
X char uaf$t_username[UAF$S_USERNAME]; /* username */
X union `123
X long int uaf$l_uic; /* user ID code */
X struct `123
X short int uaf$w_mem; /* member subfield */
X short int uaf$w_grp; /* group subfield */
X `125 uaf$r_uic_fields;
X `125 uaf$r_uic_overlay;
X long int uaf$l_sub_id; /* user sub-identifier */
X long int uaf$q_parent_id[2]; /* identifier of owner of this account */
X char uaf$t_account[UAF$S_ACCOUNT]; /* account name */
X char uaf$t_owner[UAF$S_OWNER]; /* owner's name */
X char uaf$t_defdev[UAF$S_DEFDEV]; /* default device */
X char uaf$t_defdir[UAF$S_DEFDIR]; /* default directory */
X char uaf$t_lgicmd[UAF$S_LGICMD]; /* login command file */
X char uaf$t_defcli[UAF$S_DEFCLI]; /* default command interpreter */
X char uaf$t_clitables[UAF$S_CLITABLES]; /* user CLI tables */
X union `123
X long int uaf$q_pwd[2]; /* hashed password */
X long int uaf$l_pwd; /* 32 bit subfield */
X `125 uaf$r_pwd_overlay;
X long int uaf$q_pwd2[2]; /* second password */
X short int uaf$w_logfails; /* count of login failures */
X short int uaf$w_salt; /* random password salt */
X char uaf$b_encrypt; /* encryption algorithm */
X/* encryption codes */
X char uaf$b_encrypt2; /* encryption algorithm for 2nd pwd */
X char uaf$b_pwd_length; /* minimum password length */
X char uaf$fill_1;
X long int uaf$q_expiration[2]; /* expiration date for account */
X long int uaf$q_pwd_lifetime[2]; /* password lifetime */
X long int uaf$q_pwd_date[2]; /* date of password change */
X long int uaf$q_pwd2_date[2]; /* date of 2nd password change */
X long int uaf$q_lastlogin_i[2]; /* date of last interactive login */
X long int uaf$q_lastlogin_n[2]; /* date of last non-interactive login */
X union `123
X long int uaf$q_priv[2]; /* process privilege vector */
X union prvdef uaf$r_priv;
X `125 uaf$r_priv_overlay;
X union `123
X long int uaf$q_def_priv[2]; /* default process privileges */
X union prvdef uaf$r_def_priv;
X `125 uaf$r_def_priv_overlay;
X char uaf$r_min_class[UAF$S_MIN_CLASS]; /* minimum security class */
X char uaf$r_max_class[UAF$S_MAX_CLASS]; /* maximum security class */
X union `123
X long int uaf$l_flags; /* user flags longword */
X struct uaf$r_flags_bits uaf$r_flags_bits;
X `125 uaf$r_flags_overlay;
V char uaf$b_network_access_p[UAF$S_NETWORK_ACCESS_P]; /* hourly network acce
Xss, primary */
V char uaf$b_network_access_s[UAF$S_NETWORK_ACCESS_S]; /* hourly network acce
Xss, secondary */
V char uaf$b_batch_access_p[UAF$S_BATCH_ACCESS_P]; /* hourly batch access, pr
Ximary */
V char uaf$b_batch_access_s[UAF$S_BATCH_ACCESS_S]; /* hourly batch access, se
Xcondary */
V char uaf$b_local_access_p[UAF$S_LOCAL_ACCESS_P]; /* hourly local access, pr
Ximary */
V char uaf$b_local_access_s[UAF$S_LOCAL_ACCESS_S]; /* hourly local access, se
Xcondary */
V char uaf$b_dialup_access_p[UAF$S_DIALUP_ACCESS_P]; /* hourly dialup access,
X primary */
V char uaf$b_dialup_access_s[UAF$S_DIALUP_ACCESS_S]; /* hourly dialup access,
X secondary */
V char uaf$b_remote_access_p[UAF$S_REMOTE_ACCESS_P]; /* hourly remote access,
X primary */
V char uaf$b_remote_access_s[UAF$S_REMOTE_ACCESS_S]; /* hourly remote access,
X secondary */
X char uaf$fill_2[514 - 502];
X union `123
X char uaf$b_primedays; /* bits representing primary days */
X struct uaf$r_primedays_bits uaf$r_primedays_bits;
X `125 uaf$r_primedays_overlay;
X char uaf$fill_3[516 - 515];
X char uaf$b_pri; /* base process priority */
X char uaf$b_quepri; /* maximum job queuing priority */
X short int uaf$w_maxjobs; /* maximum jobs for UIC allowed */
X/* 0 means no limit */
X short int uaf$w_maxacctjobs; /* maximum jobs for account allowed */
X/* 0 means no limit */
X short int uaf$w_maxdetach; /* maximum detached processes for UIC */
X/* 0 means no limit */
X short int uaf$w_prccnt; /* subprocess creation limit */
X short int uaf$w_biolm; /* buffered I/O limit */
X short int uaf$w_diolm; /* direct I/O limit */
X short int uaf$w_tqcnt; /* timer queue entry limit */
X short int uaf$w_astlm; /* AST queue limit */
X short int uaf$w_enqlm; /* enqueue limit */
X short int uaf$w_fillm; /* open file limit */
X short int uaf$w_shrfillm; /* shared file limit */
X long int uaf$l_wsquota; /* working set size quota */
X long int uaf$l_dfwscnt; /* default working set size */
X long int uaf$l_wsextent; /* working set size limit */
X long int uaf$l_pgflquota; /* page file quota */
X long int uaf$l_cputim; /* CPU time quota */
X long int uaf$l_bytlm; /* buffered I/O byte count limit */
X long int uaf$l_pbytlm; /* paged buffer I/O byte count limit */
X long int uaf$l_jtquota; /* job-wide logical name table creation quota */
X short int uaf$w_proxy_lim; /* number of proxies user can grant */
X short int uaf$w_proxies; /* number of proxies granted */
X short int uaf$w_account_lim; /* number of sub-accounts allowed */
X short int uaf$w_accounts; /* number of sub-accounts in use */
X char uaf$fill_4[UAF$K_LENGTH - 580];
X`125;
X `032
$ GOSUB UNPACK_FILE
$ EXIT
-+-+-+-+-+ End of part 2 +-+-+-+-+-
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id af00418; 2 Jan 90 7:33 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00464; 2 Jan 90 7:24 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3926; Tue, 02
Jan 90 07:31:22 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0242; Tue, 02 Jan 90 07:31:22 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5699; Tue, 02 Jan 90 01:18:46 C
Date: Tue, 2 Jan 90 07:05:50 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa07126; 29 Dec 89 1:46 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09418; 29 Dec 89 1:36 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0249; Fri, 29
Dec 89 01:40:08 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
9337; Fri, 29 Dec 89 01:40:07 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8552; Thu, 28 Dec 89 19:29:43 C
Date: Thu, 28 Dec 89 17:42:15 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: arbitron part 1/2
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
$! ................... Cut between dotted lines and save. ...................
$!...........................................................................
$! VAX/VMS archive file created by VMS_SHARE V06.10 7-FEB-1989.
$!
$! VMS_SHARE was written by James Gray (Gray:OSBUSouth@Xerox.COM) from
$! VMS_SHAR by Michael Bednarek (U3369429@ucsvc.dn.mu.oz.au).
$!
$! To unpack, simply save, concatinate all parts into one file and
$! execute (@) that file.
$!
$! This archive was created by user GLASSMANN
$! on 28-DEC-1989 12:36:14.35.
$!
$! ATTENTION: To keep each article below 31 blocks (15872 bytes), this
$! program has been transmitted in 2 parts. You should
$! concatenate ALL parts to ONE file and execute (@) that file.
$!
$! It contains the following 6 files:
$! AAAREADME.TXT
$! ARBBUILD.COM
$! ARBITRON.C
$! ARBITRON.COM
$! NEWSRC.PATCH
$! UAF.H
$!
$!============================================================================
$ SET SYMBOL/SCOPE=( NOLOCAL, NOGLOBAL )
$ VERSION = F$GETSYI( "VERSION" )
$ IF VERSION .GES "V4.4" THEN GOTO VERSION_OK
$ WRITE SYS$OUTPUT "You are running VMS ''VERSION'; ", -
"VMS_SHARE V06.10 7-FEB-1989 requires VMS V4.4 or higher."
$ EXIT 44 ! SS$_ABORT
$VERSION_OK:
$ GOTO START
$!
$UNPACK_FILE:
$ WRITE SYS$OUTPUT "Creating ''FILE_IS'"
$ DEFINE/USER_MODE SYS$OUTPUT NL:
$ EDIT/TPU/COMMAND=SYS$INPUT/NODISPLAY/OUTPUT='FILE_IS'/NOSECTION -
VMS_SHARE_DUMMY.DUMMY
b_part := CREATE_BUFFER( "EPartL", GET_INFO( COMMAND_LINE, "file_name" ) )
; s_file_spec := GET_INFO( COMMAND_LINE, "output_file" ); SET( OUTPUT_FILE
, b_part, s_file_spec ); b_errors := CREATE_BUFFER( "EErrorsL" ); i_errors
:= 0; pat_beg_1 := ANCHOR & "-+-+-+ Beginning"; pat_beg_2 := LINE_BEGIN
& "+-+-+-+ Beginning"; pat_end := ANCHOR & "+-+-+-+-+ End"; POSITION
( BEGINNING_OF( b_part ) ); LOOP EXITIF SEARCH( SPAN( ' ' )@r_trail
& LINE_END, FORWARD) = 0; POSITION( r_trail ); ERASE( r_trail ); ENDLOOP
; POSITION( BEGINNING_OF( b_part ) ); i_append_line := 0; LOOP EXITIF MARK
( NONE ) = END_OF( b_part ); s_x := ERASE_CHARACTER( 1 )
; IF s_x = '+' THEN r_skip := SEARCH( pat_beg_1, FORWARD, EXACT ); IF r_skip
<> 0 THEN s_x := ''; MOVE_HORIZONTAL( -CURRENT_OFFSET ); ERASE_LINE; ENDIF
; ENDIF; IF s_x = '-' THEN r_skip := SEARCH( pat_end, FORWARD, EXACT )
; IF r_skip <> 0 THEN s_x := ''; MOVE_HORIZONTAL( -CURRENT_OFFSET ); m_skip
:= MARK( NONE ); r_skip := SEARCH( pat_beg_2, FORWARD, EXACT ); IF r_skip
<> 0 THEN POSITION( END_OF( r_skip ) ); MOVE_HORIZONTAL( -CURRENT_OFFSET )
; MOVE_VERTICAL( 1 ); MOVE_HORIZONTAL( -1 ); ELSE POSITION( END_OF( b_part )
); ENDIF; ERASE( CREATE_RANGE( m_skip, MARK( NONE ), NONE ) ); ENDIF; ENDIF
; IF s_x = 'V' THEN s_x := ''; IF i_append_line <> 0 THEN APPEND_LINE
; MOVE_HORIZONTAL( -CURRENT_OFFSET ); ENDIF; i_append_line := 1
; MOVE_VERTICAL( 1 ); ENDIF; IF s_x = 'X' THEN s_x := ''; IF i_append_line
<> 0 THEN APPEND_LINE; MOVE_HORIZONTAL( -CURRENT_OFFSET ); ENDIF
; i_append_line := 0; MOVE_VERTICAL( 1 ); ENDIF; IF s_x <> '' THEN i_errors
:= i_errors + 1; s_text := CURRENT_LINE; POSITION( b_errors ); COPY_TEXT
( "The following line could not be unpacked properly:" ); SPLIT_LINE
; COPY_TEXT( s_x ); COPY_TEXT( s_text ); POSITION( b_part ); MOVE_VERTICAL
( 1 ); ENDIF; ENDLOOP; POSITION( BEGINNING_OF( b_part ) ); LOOP r_x := SEARCH
( "`", FORWARD, EXACT ); EXITIF r_x = 0; POSITION( r_x ); ERASE_CHARACTER( 1
); COPY_TEXT( ASCII( INT( ERASE_CHARACTER( 3 ) ) ) ); ENDLOOP
; IF i_errors = 0 THEN SET( NO_WRITE, b_errors, ON ); ELSE POSITION
( BEGINNING_OF( b_errors ) ); COPY_TEXT( FAO
( "The following !UL errors were detected while unpacking !AS", i_errors
, s_file_spec ) ); SPLIT_LINE; SET( OUTPUT_FILE, b_errors, "SYS$COMMAND" )
; ENDIF; EXIT;
$ DELETE VMS_SHARE_DUMMY.DUMMY;*
$ CHECKSUM 'FILE_IS
$ WRITE SYS$OUTPUT " CHECKSUM ", -
F$ELEMENT( CHECKSUM_IS .EQ. CHECKSUM$CHECKSUM, ",", "failed!!,passed." )
$ RETURN
$!
$START:
$ FILE_IS = "AAAREADME.TXT"
$ CHECKSUM_IS = 1716919986
$ COPY SYS$INPUT VMS_SHARE_DUMMY.DUMMY
XARBITRON - Create statistics to be sent monthly to netsurvey@decwrl.
X
XThis makes heavy use of subroutines that are part of NEWS. Because of
Xthe intertwining of these subroutines, the EXE winds up being over 600
Xblocks. This means that I can't reasonably post the EXE to the net.
XUnfortunately, this means that arbitron is only available to sites with
XC compilers.
X
XTo build arbitron, you first have to include the file NEWSRC.PATCH into
XNEWSRC.C, and recompile it. Then compile and link arbitron. ARBBUILD.COM
Xis included for this purpose, but you'll probably have to modify it for
Xyour site.
X
XARBITRON.COM should be run monthly. This will also have to be modified
Xfor your site.
X
XLenny Glassmann
Xlenny@ccavax.camb.com
Xuunet!ccavax!lenny
$ GOSUB UNPACK_FILE
$ FILE_IS = "ARBBUILD.COM"
$ CHECKSUM_IS = 1027810274
$ COPY SYS$INPUT VMS_SHARE_DUMMY.DUMMY
X$ cc/include=news_src arbitron
X$ link arbitron,[.news_build]news_library/lib,news_src:options_c_link/opt
$ GOSUB UNPACK_FILE
$ FILE_IS = "ARBITRON.C"
$ CHECKSUM_IS = 1140914158
$ COPY SYS$INPUT VMS_SHARE_DUMMY.DUMMY
X/* ARBITRON.C - Calculate number of readers of each newsgroup for ANU NEWS.
X`009This is meant to be run once per month, with results mailed to
X`009netsurvey@decwrl.dec.com on about the 20th of every month.
X`009The results are placed in the file ARBITRON.OUT.
X
X`009The NEWS database is read to determine what is the oldest and newest
X`009item number still on the system for each newsgroup. Then each
X`009user's NEWSRC file is read to determine what the last item was
X`009that the user read. If the last item read is later than the oldest
X`009one still on the system, then the user is counted as a reader of
X`009the newsgroup.
X
X`009This program makes heavy use of subroutines that are part of NEWS to
X`009read the files. This is not the most efficient way to read these
X`009files because work is done by those subroutines which is not needed
X`009by this program. However, it made this easy to write and maintain,
X`009and since it only runs once a month, we don't care how long it takes.
X
X`009Just about all of the numbers generated by this program are estimates
X`009of some kind. Number of users on the system is the number of
X`009accounts that have logged on interactively in the past 30 days. Number
X`009of news readers is the number of users who are readers of at least
X`009one newsgroup. A reader of a newsgroup is someone who has read an
X`009article that has an item number between the lowest and highest
X`009currently stored in the newsgroup.
X
X`009This has only been tested with ANU NEWS V5.9C, VAX C V3.0, VMS V5.2.
X`009If you have another configuration, you'll probably have to at least
X`009recompile this module.
X
X`009This must run from a place that has read access to every NEWSRC
X`009file on the system. The NEWSRC files must be in the user's
X`009default directory to be counted.
X
X`009Lenny Glassmann
X`009Cambridge Computer Associates
X`00956 Beaver St.
X`009New York, NY 10004
X`009(212) 425-5830
X`009lenny@ccavax.camb.com
X
XThanks to:
X`009Geoff Houston (gih900@csc.anu.oz.au) for ANU NEWS.
X`009Joe Meadows (joe@fhcrcvax.bitnet) for the UAF reading code.
X`009Brian Reid (reid@decwrl.dec.com) for the original UNIX arbitron.
X
XHistory:
X`009Dec 27 1989 - Initial release.
X*/
X
X#include "newsinclude"
X#include lnmdef
X#include libdef
X#include "uaf"
X#include "newsdefine"
X
X#define extrnl
X#define iev(v)`009= v
X#define iv(v)`009v
X#include "newsvariables"
X
Xtypedef struct
X `123
X char name[SUBJLEN];
X unsigned int low_item;
X unsigned int high_item;
X unsigned short readers;
X `125 GRP_INFO;
X
Xtypedef struct u_struct
X `123
X char *devdir;
X char *name;
X struct u_struct *next;
X `125 USER_STRUCT;
X
Xtypedef unsigned long SYSTIME[2];
X
Xstatic struct FAB uaffab;
Xstatic struct RAB uafrab;
Xstatic struct UAFDEF record;
Xstatic FILE *outfile;
Xstatic GRP_INFO *grparray;
Xstatic SYSTIME curtime;
Xstatic char version[] = "vms-arbitron-1.0";
Xstatic int news_readers = 0;
Xstatic int num_users = 0;
X
X
Xarbitron ()
Xmain_program
X`123
Xchar reg_filename[] = "newsrc";
X$DESCRIPTOR (delta_d, "30 0");`009`009/* Thirty days */
Xregister int grp_num;
XITM_PTR itmptr;
Xregister GRP_PTR group;
Xchar *cp;
Xchar *cp2;
Xint lastread;
Xchar user_reads_news;
Xint devlen;
Xint dirlen;
Xshort namelen;
Xchar username[UAF$S_USERNAME + 1];
XSYSTIME delta_t;
XSYSTIME month_ago;
X
X /* figure out the date that was 30 days ago */
X sys$gettim (&curtime);
X sys$bintim (&delta_d, &delta_t);
X lib$sub_times (&curtime, &delta_t, &month_ago);
X
X openfiles ();`009/* open and read NEWS.GROUPS */
X open_uaf ();`009/* open SYSUAF.DAT */
X open_outfiles ();
X
X grparray = malloc (sizeof (GRP_INFO) * ga_size);
X
X /* inspect each group (group 0 is not used) */
X for (grp_num=1; grp_num <= ga_size; grp_num++)
X`009`123
X`009map_items (grp_num);`009`009/* read NEWS.ITEMS */
X`009group = ga[grp_num];
X`009strcpy (grparray[grp_num].name, group->grp_name);
X`009itmptr = group->grp_ia;
X`009if (group->grp_count > 0)
X`009 `123
X`009 /* get high and low item numbers (itmptr[0] is not used) */
X`009 grparray[grp_num].low_item = itmptr[1].itm_num;
X`009 grparray[grp_num].high_item = itmptr[group->grp_count].itm_num;
X`009 `125
X`009else
X`009 `123
X`009 grparray[grp_num].low_item = 0;
X`009 grparray[grp_num].high_item = 0;
X`009 `125
X`009grparray[grp_num].readers = 0;
X`009free (group->grp_ia);`009`009/* no longer need item list */
X`009`125
X
X while (SYS$GET (&uafrab) & 1)`009/* read every record in the UAF */
X`009`123
X`009cp = username;
X`009cp2 = record.uaf$t_username;
X`009namelen = 0;
X`009while ((*cp2 != ' ') && (namelen++ < UAF$S_USERNAME))
X`009 *cp++ = *cp2++;
X`009*cp = '\0';
X
X`009printf ("%s ", username);
X
X`009if (lib$sub_times (&record.uaf$q_lastlogin_i, &month_ago,
X`009`009`009`009`009`009&delta_t) == LIB$_NEGTIM)
X`009 `123
X`009 printf ("hasn't logged in this month\n");
X`009 continue;`009`009`009`009/* skip this user */
X`009 `125
X
X`009num_users++;
X
X`009devlen = *record.uaf$t_defdev;
X`009dirlen = *record.uaf$t_defdir;
X`009if (devlen + dirlen + strlen (reg_filename) + 1 > sizeof(news_register))
X`009 `123
X`009 printf ("register file name is too long\n");
X`009 exit (0);
X`009 `125
X`009memcpy (news_register, &record.uaf$t_defdev[1], devlen);
X`009memcpy (news_register + devlen, &record.uaf$t_defdir[1], dirlen);
X`009*(news_register + devlen + dirlen) = '\0';
X
X`009/* if more than one user has the same default directory, and therfore
X`009 the same NEWSRC file, we only want to count it once.`009`009 */
X`009if (duplicate_user (news_register, username))
X`009 continue;
X
X`009strcat (news_register, reg_filename);
X
X`009if (access (news_register, 0) != 0)
X`009 `123
X`009 printf ("no NEWSRC file found\n");
X`009 continue;`009`009`009/* skip this user */
X`009 `125
X
X`009clear_profile_flags ();`009/* get rid of profile info from other users */
X`009read_reg_file ();`009/* read the NEWSRC file */
X`009user_reads_news = FALSE;
X
X`009for (grp_num=1; grp_num <= ga_size; grp_num++)
X`009 `123
X`009 group = ga[grp_num];
X`009 if (group->grp_reg_text)
X`009`009`123
X`009`009cp = group->grp_reg_text +
X`009`009`009strlen (group->grp_reg_text) - 1;
X`009`009while (isdigit (*cp)) /* find last non-digit */
X`009`009 --cp;
X`009`009lastread = atoi (++cp);
X`009`009free (group->grp_reg_text);
X`009`009group->grp_reg_text = NULL;
X`009`009if ((grparray[grp_num].low_item !=
X`009`009`009`009`009grparray[grp_num].high_item) &&
X`009`009 (lastread >= grparray[grp_num].low_item) &&
X`009`009 (lastread <= grparray[grp_num].high_item))
X`009`009 `123
X`009`009 grparray[grp_num].readers++;
X`009`009 user_reads_news = TRUE;
X`009`009 `125
X`009`009`125
X`009 `125
X`009if (user_reads_news)
X`009 `123
X`009 news_readers++;
X`009 printf ("reads news\n");
X`009 `125
X`009else
X`009 `123
X`009 printf ("doesn't read news\n");
X`009 `125
X`009`125
X
X sort_output ();
X write_header ();
X write_data ();
X`125
X
Xwrite_header ()
X`123
Xchar *cp;
Xunsigned int ret;
Xchar timbuf[13];
X$DESCRIPTOR (timbuf_d, timbuf);
X$DESCRIPTOR (systbl, "LNM$SYSTEM_TABLE");
X$DESCRIPTOR (addr_log_d, "NEWS_ADDRESS");
Xunsigned short hostlen;
Xchar hostnam[80];
Xstruct
X `123
X unsigned short buflen;
X unsigned short itmcode;
X char *buf_addr;
X int *retlen;
X `125 hostitm[] =
X`009`123`123sizeof (hostnam) - 1, LNM$_STRING, &hostnam, &hostlen`125,
X`009`1230, 0, 0, 0`125`125;
X
V if ((ret = sys$trnlnm (0, &systbl, &addr_log_d, 0, &hostitm)) != SS$_NORM
XAL)
X`009lib$stop (ret);
X hostnam[hostlen] = '\0';
X
X for (cp = hostnam; *cp; cp++)
X`009*cp = _tolower (*cp);
X fprintf (outfile, "Host %s\n", hostnam);
X fprintf (outfile, "Users %d\n", num_users);
X fprintf (outfile, "NetReaders %d\n", news_readers);
X sys$asctim (0, &timbuf_d, &curtime, 0);
X fprintf (outfile, "ReportDate %c%c%c%.4s\n",
X`009timbuf[3], _tolower(timbuf[4]), _tolower(timbuf[5]), &timbuf[7]);
X fprintf (outfile, "SystemType %s\n", version);
X`125
X
Xwrite_data ()
X`123
X GRP_INFO group_rec;
X struct dsc$descriptor rec_d;
X unsigned int ret;
X
X rec_d.dsc$w_length = sizeof (group_rec);
X rec_d.dsc$b_dtype = DSC$K_DTYPE_T;
X rec_d.dsc$b_class = DSC$K_CLASS_S;
X rec_d.dsc$a_pointer = &group_rec;
X
X while ((ret = sor$return_rec (&rec_d)) == SS$_NORMAL)
X`009fprintf (outfile, "%d %s\n", group_rec.readers, group_rec.name);
X
X if (ret != SS$_ENDOFFILE)
X`009lib$stop (ret);
X`125
X
X/* sort the newsgroup lines in descending order by number of readers */
Xsort_output ()
X`123
X unsigned int ret;
X unsigned short sort_buf[] =
X`009`1231, DSC$K_DTYPE_WU, 1,
X`009(char *)&grparray[0].readers - (char *)&grparray[0],
X`009sizeof (grparray[0].readers)`125;
X unsigned short reclen = sizeof (grparray[0]);
X struct dsc$descriptor rec_d;
X unsigned int grp_num;
X
X if ((ret = sor$begin_sort (&sort_buf, &reclen, 0, 0, 0, 0, 0, 0, 0)) !=
X`009`009`009`009`009`009`009`009 SS$_NORMAL)
X`009lib$stop (ret);
X rec_d.dsc$w_length = sizeof (grparray[0]);
X rec_d.dsc$b_dtype = DSC$K_DTYPE_T;
X rec_d.dsc$b_class = DSC$K_CLASS_S;
X
X for (grp_num=1; grp_num <= ga_size; grp_num++)
X`009`123
X`009rec_d.dsc$a_pointer = &grparray[grp_num];
X`009if ((ret = sor$release_rec (&rec_d)) != SS$_NORMAL)
X`009 lib$stop (ret);
X`009`125
X
X if ((ret = sor$sort_merge (0)) != SS$_NORMAL)
X`009lib$stop (ret);
X`125
X
X
X/* check for users who have the same default directory */
Xduplicate_user (devdir, name)
Xchar *devdir;
Xchar *name;
X`123
X static USER_STRUCT *top_user = NULL;
X register USER_STRUCT *userp;
X register USER_STRUCT *new;
X USER_STRUCT *prev;
X char past = FALSE;
-+-+-+-+-+ End of part 1 +-+-+-+-+-
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00400; 2 Jan 90 7:28 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00407; 2 Jan 90 7:17 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3843; Tue, 02
Jan 90 07:24:12 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0186; Tue, 02 Jan 90 07:24:12 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5452; Tue, 02 Jan 90 01:13:47 C
Date: Tue, 2 Jan 90 06:24:29 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac07103; 29 Dec 89 1:41 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09384; 29 Dec 89 1:33 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0226; Fri, 29
Dec 89 01:37:25 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
9329; Fri, 29 Dec 89 01:37:25 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8517; Thu, 28 Dec 89 19:27:20 C
Date: Thu, 28 Dec 89 17:41:25 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: Arbitron is coming in 2 parts
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
I'm about to post arbitron V1.0 as a 2 part vms_share set. Extract the parts,
concatenate them, and run the resulting file as a DCL command procedure.
Send any comments or questions to me or post them to this newsgroup.
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ad00418; 2 Jan 90 7:33 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00455; 2 Jan 90 7:22 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3904; Tue, 02
Jan 90 07:28:59 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0232; Tue, 02 Jan 90 07:28:59 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5549; Tue, 02 Jan 90 01:15:05 C
Date: Tue, 2 Jan 90 07:04:46 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa09032; 31 Dec 89 1:41 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa06681; 31 Dec 89 1:33 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3801; Sun, 31
Dec 89 01:38:15 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1159; Sun, 31 Dec 89 01:38:15 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
2567; Sat, 30 Dec 89 19:36:26 C
Date: Fri, 29 Dec 89 23:47:16 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: RE: Troubles adding batches with 5.9B
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912190737.AA16720@uunet.uu.net>,
munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) writes:
>>We are running NEWS 5.9B.
>>
>>Last night a large number of articles that arrived in "rnews" format were
>>rejected by the add/network command, with messages of the form
>>
>> Add <id> news.group: JUNK (Cannot open output file (write access))
>>or
>> Add <id> junk: REJECT (Cannot open output file (write access))
>>
> .......
>
> check which account owns the itm files, and then check the diskquota entry - i
t
> looks like you are out of quota (or out of free space on the disk).
>
Accounts and file ownership and directory protections and all were all as they
used to be and as they are now -- ie I didn't change anything and things just
suddenly started to work again. We don't use diskquotas here, and it's quite
unlikely that the disk was full, since (a) there was 75 Mbytes of free space
the next morning and (b) some batches had some items that were received
correctly.
> its just another of the integration problems - vaxc is not quite VMS - at this
> point the NEWS code sees a -1 value from a file operation and says "oh well -
> nice try" - to get past this to the RMS return status is what you are asking
> for... could be interesting!
imho this is one of the things that really needs to be worked on. It's a
real pain to track down the cause of problems when the only diagnostic is
equivalent to "there's a problem".
Another nicety in the "problem tracking" area would be some trace capability.
Folks are always having troubles getting their news.sys and news.distribution
files right; it'd be nice to turn on a "forwarding trace" feature and get
output like
neighbor system crash: Item not forwarded (news.sys filter)
neighbor system pnet01: Item not forwarded (news.distribution filter)
where each decision is made.
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ae00416; 2 Jan 90 7:33 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00457; 2 Jan 90 7:22 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3909; Tue, 02
Jan 90 07:29:09 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0234; Tue, 02 Jan 90 07:29:09 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5585; Tue, 02 Jan 90 01:15:32 C
Date: Tue, 2 Jan 90 06:24:02 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa11533; 30 Dec 89 5:00 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa08523; 30 Dec 89 4:52 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0867; Sat, 30
Dec 89 04:56:58 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8415; Sat, 30 Dec 89 04:56:57 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
4502; Fri, 29 Dec 89 22:55:33 C
Date: Sat, 30 Dec 89 04:51:14 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 88 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa16705; 23 Dec 89 4:30 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa14346; 23 Dec 89 4:25 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0985; Sat, 23
Dec 89 03:54:48 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
7862; Sat, 23 Dec 89 03:54:48 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
7608; Fri, 22 Dec 89 21:53:46 C
Date: Fri, 22 Dec 89 17:12:43 GMT
Reply-To: Daniel Berglund <foperator@se.chalmers.tekno>
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: Daniel Berglund <foperator@se.chalmers.tekno>
Subject: Re: Troubles adding batches with 5.9B
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912190723.AA14204@uunet.uu.net>,
munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) writes:
>>Suggestions: 1. Add an interpretation of the error status return from
>>file open attempts. These messages would be a lot more helpful if
>>accompanied by "no privilege for attempted operation" or "no such device"
>>or whatever.
> its just another of the integration problems - vaxc is not quite VMS - at this
> point the NEWS code sees a -1 value from a file operation and says "oh well -
> nice try" - to get past this to the RMS return status is what you are asking
> for... could be interesting!
Maybe I'm overlooking something obvious, but the rms STS value can be
found in vaxc$errno (but I don't know how to access the STV value). Example:
#include errno
#include perror
main()
E
fopen("sahdjgf$$$","r");
perror("Blurp");
printf("%d %d\n",errno,vaxc$errno);
fopen("sdf:asjklhdf$$$","r");
perror("Blurp");
printf("%d %d\n",errno,vaxc$errno);
fopen("gdgd%gsgs","r");
perror("Blurp");
printf("%d %d\n",errno,vaxc$errno);
L
yields:
$ r apa
Blurp: no such file or directory
2 98962
Blurp: no such device or address
6 99524
Blurp: non-translatable vms error code: 0x18744, vms message:
%rms-f-wld, invalid wildcard operation
65535 100164
--
Daniel Berglund (foperator@tekno.chalmers.se, BITNET: FOP@SECTHF51)
Chalmers University of Technology, G|teborg, Swedenroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00474; 2 Jan 90 7:43 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00491; 2 Jan 90 7:31 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3954; Tue, 02
Jan 90 07:38:12 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0281; Tue, 02 Jan 90 07:38:12 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5967; Tue, 02 Jan 90 01:35:00 C
Date: Tue, 2 Jan 90 07:11:26 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa10873; 30 Dec 89 3:58 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa08206; 30 Dec 89 3:48 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0662; Sat, 30
Dec 89 03:53:01 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8242; Sat, 30 Dec 89 03:53:00 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
3222; Fri, 29 Dec 89 21:51:58 C
Date: Sat, 30 Dec 89 03:50:07 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 85 attempts over 170 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac14832; 23 Dec 89 1:39 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa13714; 23 Dec 89 1:38 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 8765; Sat, 23
Dec 89 01:38:41 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
5760; Sat, 23 Dec 89 01:38:41 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
3719; Fri, 22 Dec 89 18:00:04 C
Date: Fri, 22 Dec 89 04:49:58 GMT
Reply-To: tlimonce@uucp.drunivac
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: tlimonce@uucp.drunivac
Subject: Re: How do YOU accept a newsfeed?
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912190551.AA27490@uunet.uu.net>,
munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) writes:
> This has me beat - in newsutility do_newg calls sys_accept (or some similar
> name) which should reject newsgroup ba.forsale and NOT create it - what versio
n
> are you running????
We're running version 5.9B (Or is it 5.9A? I'm not sure. I did at
least one set of patches but it's the set that didn't include a
change to the VERSION command. I guess that's 5.9A, eh?)
Guess what? The problem magically fixed itself. How often does NEWS
re-read the NEWS.SYS file? Only when the first person enters news?
The problem went away after a few days, which is about how often
there is a time when everyone exits news.
I don't think we rebooted, we're pretty 24hrs around here (library
automation mostly, students reading news and mail is the other
reason) so if we crashed & rebooted I would have heard about it.
-Tom
(replying to this addres won't work yet... try tlimonce@drew.bitnet,
tlimonce@drew.uucp, rutgers!drew!tlimonce or limonce@pilot.njin.net)root@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00229; 1 Jan 90 7:22 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00389; 1 Jan 90 7:12 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 9676; Mon, 01
Jan 90 07:18:32 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
6612; Mon, 01 Jan 90 07:18:32 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
2474; Mon, 01 Jan 90 01:18:19 C
Date: Sun, 31 Dec 89 20:59:35 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: 5.9C , reject of crossposted item though one group s/b okay?
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
Running NEWS 5.9C (thanks, Geoff!), VMS 5.2.
While reviewing last night's RNEWS log files [RNEWS is a DECUS uucp thing
that takes news batches received via uucp and feeds them to NEWS via
ADD BATCH commands] I noticed a message that was rejected due to my sys
filter.
The message was posted to alt.flame and to news.groups (in that order), and
followups were directed to alt.flame. My sys filter says (among other things)
news,!alt
Is this the intended behavior? I thought that the posting to news.groups
should be alllowed.
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac00418; 2 Jan 90 7:33 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00451; 2 Jan 90 7:21 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3894; Tue, 02
Jan 90 07:28:31 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0228; Tue, 02 Jan 90 07:28:31 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5524; Tue, 02 Jan 90 01:14:40 C
Date: Tue, 2 Jan 90 07:05:12 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa09034; 31 Dec 89 1:42 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa06686; 31 Dec 89 1:34 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3811; Sun, 31
Dec 89 01:39:56 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1169; Sun, 31 Dec 89 01:39:56 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
2643; Sat, 30 Dec 89 19:36:49 C
Date: Sat, 30 Dec 89 00:05:06 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: Help with ANU News V5.9
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <15300@eerie.acsu.Buffalo.EDU>,
gerland@acsu.buffalo.edu (Jim Gerland) writes:
> I am trying to install V5.9 and have a few questions....
You're working too hard. If 5.8 is already set up and running, you need
only to place the executable for 5.9 in the same directory where 5.8 has
always been, and do an INSTALL> REPLACE on it. No need to do any of the
"first time execution" stuff. Maybe do an INSTALL> LIST/FULL to make sure
it's installed with SYSPRV. Repeat as necessary for the NNTP-related
images.
Btw, my personal number one favorite mistake when bringing up a new version
of NEWS is to forget to INSTALL the new image file. Without SYSPRV, NEWS
can't do much. Of course my account has SYSPRV so when I test it all works
well, but when others try it... hoo boy.
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ad00416; 2 Jan 90 7:33 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00453; 2 Jan 90 7:21 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3899; Tue, 02
Jan 90 07:28:47 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0230; Tue, 02 Jan 90 07:28:47 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5500; Tue, 02 Jan 90 01:14:13 C
Date: Tue, 2 Jan 90 07:05:00 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab09032; 31 Dec 89 1:42 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa06684; 31 Dec 89 1:33 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3806; Sun, 31
Dec 89 01:38:41 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1165; Sun, 31 Dec 89 01:38:41 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
2606; Sat, 30 Dec 89 19:36:37 C
Date: Fri, 29 Dec 89 23:55:41 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: Giving NEWS an internal news command at startup
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <ANU-NEWS%89122011084646@NDSUVM1.BITNET>,
JHWELCH@AMHERST.BITNET (Jonathan_Welch) writes:
> I've been modifying my copy of news.c when new releases come out to enable
> one to supply an internal news command to be executed after news has
> started up [by specifying the command as command-line parameters to NEWS, eg
>
> $ news select ecs.announce
>
> Geoff - if you think this feature is a good idea perhaps you could put
> it into forthcoming releases.
This is nice, but I would like to repeat my earlier request that the
NEWS_INI file be allowed to contain generalized commands and not just
DEFINE/KEY . For instance I (and all users at my shop) would like to
specify SET LINE_EDITING automatically upon NEWS startup; I should be
able to put this command in the NEWS_INI file.
A NEWS command found on the DCL command line, as in the example supplied
by Mr. Welch, should of course be executed after any commands found in
NEWS_INI.
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ae00536; 2 Jan 90 7:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00535; 2 Jan 90 7:43 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4053; Tue, 02
Jan 90 07:50:42 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0327; Tue, 02 Jan 90 07:50:42 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6135; Tue, 02 Jan 90 01:37:55 C
Date: Tue, 2 Jan 90 07:20:42 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa01223; 30 Dec 89 9:04 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00908; 30 Dec 89 8:54 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 1257; Sat, 30
Dec 89 08:59:55 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8753; Sat, 30 Dec 89 08:59:55 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
7323; Sat, 30 Dec 89 02:57:50 C
Date: Sat, 30 Dec 89 08:49:41 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 114 attempts over 169 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ah00202; 23 Dec 89 7:05 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00309; 23 Dec 89 7:00 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3364; Sat, 23
Dec 89 06:58:47 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0318; Sat, 23 Dec 89 06:58:45 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8455; Fri, 22 Dec 89 22:51:15 C
Date: Fri, 22 Dec 89 18:22:41 GMT
Reply-To: Earle Ake <fac2@com.saic.dayton>
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: Earle Ake <fac2@com.saic.dayton>
Subject: Re: RE: rot13 utility in DCL. (TPU solution!)
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <3286.2590eeeb@fps.mcw.edu>, brodie@fps.mcw.edu writes:
> In article <8912200842.AA22375@uunet.uu.net>, munnari!csc.anu.oz.au!gih900@UUN
ET.UU.NET (Geoff Huston) writes:
>
>> Wouldn't it be better to have a TPU edit procedure called rot13 to allow you
>> to rot the necessary bits??
>> (said he trying to avoid having to add the code)
I wasn't doing much today so I took out the TPU manual and discovered that TPU
has a function called TRANSLATE which will do what I wanted. The example even
shows a way to use it to rotate every character by 13 to 'encrypt' them!
Sounds like just what I have been looking for. I am using Ted Nieland's
EDT-Plus editor so the procedure will have to be modified slightly for use
with an other TPU based editor. I started with the procedure that changes the
case of the letters either one at a time or those within the select range.
Instead of using the change_case function, I made it the TRANSLATE function.
I have defined the key to be GOLD-T as that was not being used.
Let me know what you think.
--
_____________________________________________________________________________
____ ____ ___
Earle Ake /___ /___/ / / Science Applications International Corporation
____// / / /__ Dayton, Ohio
-----------------------------------------------------------------------------
Internet: fac2%dayton.saic.com@uunet.uu.net uucp: uunet!dayvb!fac2
!EDTP ROT13
!
PROCEDURE EDTP$rot13 !gold r (rot13)
LOCAL character ;
!check for active select
EDTP$select_range;
if EDTP$x_select_range <> 0
then
TRANSLATE (EDTP$x_select_range,
"NOPQRSTUVWXYZABCDEFGHIJKLMnopqrstuvwxyzabcdefghijklm",
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
EDTP$x_select_range:=0;
return;
endif;
!change case of current character
if current_character <> EDTP$x_empty
then
character :=current_character;
TRANSLATE (character,
"NOPQRSTUVWXYZABCDEFGHIJKLMnopqrstuvwxyzabcdefghijklm",
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
erase_character(1);
copy_text(character);
if current_direction <> forward
then
move_horizontal(-2);
endif;
return
endif;
ENDPROCEDURE
DEFINE_KEY('EDTP$rot13',key_name('T',shift_key),"rot13"); ! rot13root@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00538; 2 Jan 90 7:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00531; 2 Jan 90 7:43 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4043; Tue, 02
Jan 90 07:50:12 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0323; Tue, 02 Jan 90 07:50:12 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6084; Tue, 02 Jan 90 01:36:55 C
Date: Tue, 2 Jan 90 07:21:48 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa09748; 30 Dec 89 1:50 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa07790; 30 Dec 89 1:42 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0280; Sat, 30
Dec 89 01:46:54 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
7898; Sat, 30 Dec 89 01:46:54 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
0524; Fri, 29 Dec 89 19:41:24 C
Date: Sat, 30 Dec 89 01:36:29 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 116 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa14379; 23 Dec 89 1:03 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa13555; 23 Dec 89 0:59 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 8191; Sat, 23
Dec 89 00:59:18 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
5176; Sat, 23 Dec 89 00:59:17 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
0592; Fri, 22 Dec 89 12:59:55 C
Date: Thu, 21 Dec 89 21:41:50 GMT
Reply-To: tanner@edu.cerritos
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: tanner@edu.cerritos
Subject: Re: How to use patch?
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <4981.25908cae@pbs.uucp>, sdroppers@pbs.uucp writes:
> I have checked back, but I cannot find anything, is there a man page or such
> that someone can post (or E-Mail) about how to use patch? If patch is a *nix
> tool then I am in the dark, we have no such docs available.
Here's a DCL file I used to patch 5.9C. I copied the News 5.9 sources and the
5.9C .DIFF files to a directory (yes, on the same disk as sys$scratch) and
executed this file. Everything seemed to update fine. Beware the logical
UTL:, it's where we put our utilities.
$ set noon
$ patch := $utl:patch
$ rename newsmail.c newsvmsmail.c
$ context = 0
$loop: ! loop for all .diff files
$ dif = f$search("*.diff",context)
$ if dif .eqs. "" then exit
$ name = f$parse(dif,,,"name") + f$parse(dif,,,"type") ! make short filename
$ open file 'dif'
$ read/end_of_file=empty file line ! read the diff file header
$ start = f$locate("]",line) + 1
$ dest = f$extract(start,f$length(line)-start,line) ! extract filename
$ read/end_of_file=empty file line
$ read/end_of_file=empty file line ! test for empty diff files
$ write sys$output "patching ''dest'"
$ patch 'dest' 'name''type'
$empty: ! .diff file contains header only, skip patch
$ close file
$ goto loop
If you need patch.exe, it's on gray.cerritos.edu for anonymous ftp.
-Bruce
--
Bruce Tanner (213) 860-2451 x 596 Tanner@Cerritos.EDU
Cerritos College Norwalk, CA cerritos!tannerroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00538; 2 Jan 90 7:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00539; 2 Jan 90 7:43 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4058; Tue, 02
Jan 90 07:50:58 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0329; Tue, 02 Jan 90 07:50:58 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6168; Tue, 02 Jan 90 01:38:51 C
Date: Tue, 2 Jan 90 07:21:05 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00267; 2 Jan 90 7:17 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00373; 2 Jan 90 7:08 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3738; Tue, 02
Jan 90 07:00:05 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0098; Tue, 02 Jan 90 07:00:04 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5181; Tue, 02 Jan 90 00:56:29 C
Date: Tue, 2 Jan 90 06:29:14 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac12347; 30 Dec 89 6:08 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09015; 30 Dec 89 6:02 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0975; Sat, 30
Dec 89 06:07:38 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8513; Sat, 30 Dec 89 06:07:38 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5421; Sat, 30 Dec 89 00:06:40 C
Date: Sat, 30 Dec 89 05:56:06 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 91 attempts over 172 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ad14251; 23 Dec 89 0:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa13513; 23 Dec 89 0:49 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7997; Sat, 23
Dec 89 00:50:31 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
4992; Sat, 23 Dec 89 00:50:31 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8819; Fri, 22 Dec 89 11:52:22 C
Date: Thu, 21 Dec 89 19:55:39 GMT
Reply-To: brodie@edu.mcw.fps
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: brodie@edu.mcw.fps
Subject: Re: RE: rot13 utility in DCL. (and TPU suggestion)
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912200842.AA22375@uunet.uu.net>, munnari!csc.anu.oz.au!gih900@UUNET
.UU.NET (Geoff Huston) writes:
[stuff deleted about my dcl rot13 utility)
> I'm impressed!!!
thanks, geoff!!
>>READ/ROT13, so it shouldn't be TOO tough....)
>
> Wouldn't it be better to have a TPU edit procedure called rot13 to allow you
> to rot the necessary bits??
> (said he trying to avoid having to add the code)
>
> Geoff
hey, now THERE's a neat idea. The tricky part is to tell TPU to do the
ROT13 stuff when WRITING the file upon exit. Sounds neat, and I'm sure
it's pretty easy to do. Unfortunately, I don't know tpu programming
at ALL... never had time do learn it (I really should... maybe this would
be a good project?)
unless someone ELSE wants to do it.....
-------------------------------------------------------------------------------
Kent C. Brodie - Systems Manager brodie@mcw.edu
Medical College of Wisconsin +1 414 778 4500
"Gee, I hope these are the right coordinates..." -Chief O'Brian; STTNGroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00536; 2 Jan 90 7:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00527; 2 Jan 90 7:42 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4016; Tue, 02
Jan 90 07:49:45 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0315; Tue, 02 Jan 90 07:49:45 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6025; Tue, 02 Jan 90 01:35:40 C
Date: Tue, 2 Jan 90 07:20:34 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00266; 2 Jan 90 7:17 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00371; 2 Jan 90 7:07 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3733; Tue, 02
Jan 90 06:9:10 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0096; Tue, 02 Jan 90 06:59:10 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2..3B) with BSMTP id
5153; Tue, 02 Jan 90 00:56:08 C
Date: Tue, 2 Jan 90 06:35:33 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa05244; 29 Dec 89 19:07 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa04822; 29 Dec 89 18:56 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7074; Fri, 29
Dec 89 19:01:09 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
5479; Fri, 29 Dec 89 19:01:08 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
9654; Fri, 29 Dec 89 13:00:44 C
Date: Fri, 29 Dec 89 18:49:31 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 107 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab08434; 22 Dec 89 17:57 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09712; 22 Dec 89 17:53 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4931; Fri, 22
Dec 89 17:53:48 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
2225; Fri, 22 Dec 89 17:53:47 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8790; Fri, 22 Dec 89 11:52:08 C
Date: Thu, 21 Dec 89 22:00:50 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: arbitron is coming
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
I've made some progress on writing arbitron. It should be ready in a couple of
days. I'm trying to do approximately the same thing that the unix script does.
I'm writing it in C, using lot's of calls to NEWS functions, there was no
practical way to write it in DCL. I'll send more details soon.
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac00536; 2 Jan 90 7:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00529; 2 Jan 90 7:43 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4035; Tue, 02
Jan 90 07:50:05 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0319; Tue, 02 Jan 90 07:50:05 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6065; Tue, 02 Jan 90 01:36:25 C
Date: Tue, 2 Jan 90 07:21:16 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00266; 2 Jan 90 7:17 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00375; 2 Jan 90 7:08 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3745; Tue, 02
Jan 90 07:00:31 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0102; Tue, 02 Jan 90 07:00:31 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5215; Tue, 02 Jan 90 00:56:53 C
Date: Tue, 2 Jan 90 06:27:52 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa03350; 28 Dec 89 17:56 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa03918; 28 Dec 89 16:21 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7383; Thu, 28
Dec 89 16:25:42 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
6750; Thu, 28 Dec 89 16:25:42 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
4843; Thu, 28 Dec 89 08:20:57 C
Date: Wed, 27 Dec 89 17:03:14 GMT
Reply-To: Jim Gerland <gerland@edu.buffalo.acsu>
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
Comments: Warning -- original Sender: tag was nobody@ACSU.BUFFALO.EDU
From: Jim Gerland <gerland@edu.buffalo.acsu>
Subject: Help with ANU News V5.9
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
I am trying to install V5.9 and have a few questions.
The person who installed V5.8 is no longer here so please bear with me.
We would like to use the NNTP with V5.9 and WIN/TCP V5.1
I decided to just install V5.9 from scratch and have followed the instructions
in the doc (although it is V5.8 - is there a newer doc?).
I get to the point in section 10.9 First Time Execution of NEWS and things
begin to fall apart. It does not do what paragraph 2 says it should (create
files in news_root: and news_manager:).
So then I invoke NEWS and first do a SET NEWSGROUP DEFAULT /SERVER=NEWS
/PROTOCAL=WINTCP /FILEHOLD=0, where NEWS is the name of my Unix newsserver,
eerie.cs.buffalo.edu
Next, I CREATE CONTROL /LOCAL and CREATE JUNK /LOCAL as per the last paragraph
in section 10.9 and then go into rn on my Unix machine and get the latest
version of checkgroups. from the news.admin newsgroup, copy it to my
VAXcluster, edit it appropriately and do an ADD FILE CHECKGROUPS. but this
only adds an entry into the CONTROL newsgroup. Am I doing something wrong?
Any help would be greatly appreciated. Thanks.
Jim Gerland UUCP: ...Eallegra,decvax,watmathL!sunybcs!gerland
CSNET: gerland@buffalo
UCS BITNET: gerland@ubvms (VAX/VMS)
SUNY at Buffalo gerland@ubvm (VM/CMS)root@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ad00536; 2 Jan 90 7:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00533; 2 Jan 90 7:43 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4048; Tue, 02
Jan 90 07:50:28 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0325; Tue, 02 Jan 90 07:50:27 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6105; Tue, 02 Jan 90 01:37:28 C
Date: Tue, 2 Jan 90 07:20:50 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00267; 2 Jan 90 7:17 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00377; 2 Jan 90 7:09 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3750; Tue, 02
Jan 90 07:00:56 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0104; Tue, 02 Jan 90 07:00:55 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5235; Tue, 02 Jan 90 00:57:19 C
Date: Tue, 2 Jan 90 06:28:41 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa10706; 31 Dec 89 4:55 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa07284; 31 Dec 89 4:44 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4504; Sun, 31
Dec 89 04:49:29 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1864; Sun, 31 Dec 89 04:49:29 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
4058; Sat, 30 Dec 89 22:49:03 C
Date: Sat, 30 Dec 89 15:54:21 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: Arbitron
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
Nice job, Lenny!
I've put the following in my NEWSSKIM.COM to automatically run ARBITRON
near the end of the month. Location is not critical (I have it just after
the SKIM operation). Note that it is not necessary to run this code once
per day, ie it need not be "under" the first-run-of-new-day test, but it
won't hurt if it is, either.
I didn't know if decwrl needed some precise format for the mail subject
line, so I just fudged something.
$ ! ---------------------
$ ! If it's close to the end of the month, run the arbitron program and
$ ! mail the results to decwrl.
$
$ test_mo = f$element(1, "-", f$cvtime("''f$time()'+2-0:0:0", "ABSOLUTE"))
$
$ ! In the preceding line, the "2-0:0:0" means that this code will trigger
$ ! if it's 2 days (ie 48 hours -- or closer) to the end of the last day of
$ ! the month. Modify this (ie make it bigger) if you are far away from
$ ! decwrl (in terms of number of days for delivery). To be included in the
$ ! monthly arbitron stats, the mail message should get there before 00:00
$ ! preceding the first of the new month (or 23:59.59.99 ending the last
$ ! day of the current month, if you prefer).
$
$ this_mo = f$element(1, "-", f$time()) ! note: we use this_mo later.
$ day_of_month_ok = this_mo .nes. test_mo
$
$ ! Have we done it this month already?
$
$ if (f$search("news_log:arbitron.out").eqs."")
$ then
$ ! ok if haven't done it before, at all.
$ month_ok = 1
$ else
$ ! ok if last month run is different from current month.
$ last_arb = f$file("news_log:arbitron.out","CDT")
$ month_ok = f$element(1, "-", last_arb) .nes. this_mo
$ endif
$
$ if (day_of_month_ok .and. month_ok)
$ then
$ write sys$output "Arbitron Beginning at ''f$time()'"
$ run uucp_bin:arbitron
$ rename arbitron.out news_log:
$ purge news_log:arbitron.out
$ host = f$logi("uucp_host_name")
$ mmm_yyyy = f$elem(0, " ", f$time()) - f$elem(0, "-", f$time()) - "-"
$ mail news_log:arbitron.out -
/subj="Arbitron stats from uucp host ''host' for ''mmm_yyyy'" -
uucp%"""netsurvey@decwrl.dec.com""",usenet
$ write sys$output "Arbitron Completed at ''f$time()'"
$ endif
$
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00636; 2 Jan 90 8:04 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00599; 2 Jan 90 7:53 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4106; Tue, 02
Jan 90 08:00:35 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0365; Tue, 02 Jan 90 08:00:35 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6404; Tue, 02 Jan 90 01:59:10 C
Date: Tue, 2 Jan 90 07:52:02 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00229; 1 Jan 90 7:22 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00389; 1 Jan 90 7:12 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 9676; Mon, 01
Jan 90 07:18:32 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
6612; Mon, 01 Jan 90 07:18:32 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
2474; Mon, 01 Jan 90 01:18:19 C
Date: Sun, 31 Dec 89 20:59:35 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: 5.9C , reject of crossposted item though one group s/b okay?
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
Running NEWS 5.9C (thanks, Geoff!), VMS 5.2.
While reviewing last night's RNEWS log files [RNEWS is a DECUS uucp thing
that takes news batches received via uucp and feeds them to NEWS via
ADD BATCH commands] I noticed a message that was rejected due to my sys
filter.
The message was posted to alt.flame and to news.groups (in that order), and
followups were directed to alt.flame. My sys filter says (among other things)
news,!alt
Is this the intended behavior? I thought that the posting to news.groups
should be alllowed.
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00657; 2 Jan 90 8:09 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00635; 2 Jan 90 7:58 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4169; Tue, 02
Jan 90 08:05:11 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0415; Tue, 02 Jan 90 08:05:11 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6478; Tue, 02 Jan 90 02:00:11 C
Date: Tue, 2 Jan 90 07:42:10 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00400; 2 Jan 90 7:28 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00407; 2 Jan 90 7:17 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3843; Tue, 02
Jan 90 07:24:12 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0186; Tue, 02 Jan 90 07:24:12 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5452; Tue, 02 Jan 90 01:13:47 C
Date: Tue, 2 Jan 90 06:24:29 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac07103; 29 Dec 89 1:41 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09384; 29 Dec 89 1:33 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0226; Fri, 29
Dec 89 01:37:25 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
9329; Fri, 29 Dec 89 01:37:25 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8517; Thu, 28 Dec 89 19:27:20 C
Date: Thu, 28 Dec 89 17:41:25 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: Arbitron is coming in 2 parts
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
I'm about to post arbitron V1.0 as a 2 part vms_share set. Extract the parts,
concatenate them, and run the resulting file as a DCL command procedure.
Send any comments or questions to me or post them to this newsgroup.
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00656; 2 Jan 90 8:09 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00673; 2 Jan 90 8:01 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4190; Tue, 02
Jan 90 08:08:11 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0431; Tue, 02 Jan 90 08:08:11 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6528; Tue, 02 Jan 90 02:00:23 C
Date: Tue, 2 Jan 90 07:52:27 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac00418; 2 Jan 90 7:33 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00451; 2 Jan 90 7:21 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3894; Tue, 02
Jan 90 07:28:31 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0228; Tue, 02 Jan 90 07:28:31 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5524; Tue, 02 Jan 90 01:14:40 C
Date: Tue, 2 Jan 90 07:05:12 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa09034; 31 Dec 89 1:42 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa06686; 31 Dec 89 1:34 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3811; Sun, 31
Dec 89 01:39:56 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1169; Sun, 31 Dec 89 01:39:56 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
2643; Sat, 30 Dec 89 19:36:49 C
Date: Sat, 30 Dec 89 00:05:06 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: Help with ANU News V5.9
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <15300@eerie.acsu.Buffalo.EDU>,
gerland@acsu.buffalo.edu (Jim Gerland) writes:
> I am trying to install V5.9 and have a few questions....
You're working too hard. If 5.8 is already set up and running, you need
only to place the executable for 5.9 in the same directory where 5.8 has
always been, and do an INSTALL> REPLACE on it. No need to do any of the
"first time execution" stuff. Maybe do an INSTALL> LIST/FULL to make sure
it's installed with SYSPRV. Repeat as necessary for the NNTP-related
images.
Btw, my personal number one favorite mistake when bringing up a new version
of NEWS is to forget to INSTALL the new image file. Without SYSPRV, NEWS
can't do much. Of course my account has SYSPRV so when I test it all works
well, but when others try it... hoo boy.
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00536; 2 Jan 90 7:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00525; 2 Jan 90 7:42 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4011; Tue, 02
Jan 90 07:49:09 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0313; Tue, 02 Jan 90 07:49:09 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5999; Tue, 02 Jan 90 01:35:20 C
Date: Tue, 2 Jan 90 07:11:36 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa01224; 30 Dec 89 9:04 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00905; 30 Dec 89 8:53 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 1252; Sat, 30
Dec 89 08:58:52 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8751; Sat, 30 Dec 89 08:58:51 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
7305; Sat, 30 Dec 89 02:57:36 C
Date: Sat, 30 Dec 89 08:50:23 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 119 attempts over 170 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab17809; 23 Dec 89 6:13 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa14845; 23 Dec 89 6:12 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 2520; Sat, 23
Dec 89 06:13:24 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
9405; Sat, 23 Dec 89 06:13:24 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8506; Fri, 22 Dec 89 22:52:34 C
Date: Fri, 22 Dec 89 20:58:52 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: RE: Troubles adding batches with 5.9B
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912190723.AA14204@uunet.uu.net>, munnari!csc.anu.oz.au!gih900@UUNET
.UU.NET (Geoff Huston) writes:
> its just another of the integration problems - vaxc is not quite VMS - at this
> point the NEWS code sees a -1 value from a file operation and says "oh well -
> nice try" - to get past this to the RMS return status is what you are asking
> for... could be interesting!
>
I thought this info could be gotten from the global variable vaxc$errno.
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00673; 2 Jan 90 8:14 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00693; 2 Jan 90 8:04 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4205; Tue, 02
Jan 90 08:11:44 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0439; Tue, 02 Jan 90 08:11:44 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6548; Tue, 02 Jan 90 02:00:37 C
Date: Tue, 2 Jan 90 07:52:38 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ad00416; 2 Jan 90 7:33 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00453; 2 Jan 90 7:21 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3899; Tue, 02
Jan 90 07:28:47 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0230; Tue, 02 Jan 90 07:28:47 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5500; Tue, 02 Jan 90 01:14:13 C
Date: Tue, 2 Jan 90 07:05:00 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab09032; 31 Dec 89 1:42 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa06684; 31 Dec 89 1:33 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3806; Sun, 31
Dec 89 01:38:41 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1165; Sun, 31 Dec 89 01:38:41 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
2606; Sat, 30 Dec 89 19:36:37 C
Date: Fri, 29 Dec 89 23:55:41 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: Giving NEWS an internal news command at startup
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <ANU-NEWS%89122011084646@NDSUVM1.BITNET>,
JHWELCH@AMHERST.BITNET (Jonathan_Welch) writes:
> I've been modifying my copy of news.c when new releases come out to enable
> one to supply an internal news command to be executed after news has
> started up [by specifying the command as command-line parameters to NEWS, eg
>
> $ news select ecs.announce
>
> Geoff - if you think this feature is a good idea perhaps you could put
> it into forthcoming releases.
This is nice, but I would like to repeat my earlier request that the
NEWS_INI file be allowed to contain generalized commands and not just
DEFINE/KEY . For instance I (and all users at my shop) would like to
specify SET LINE_EDITING automatically upon NEWS startup; I should be
able to put this command in the NEWS_INI file.
A NEWS command found on the DCL command line, as in the example supplied
by Mr. Welch, should of course be executed after any commands found in
NEWS_INI.
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00673; 2 Jan 90 8:14 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00721; 2 Jan 90 8:06 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4227; Tue, 02
Jan 90 08:13:23 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0453; Tue, 02 Jan 90 08:13:22 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6679; Tue, 02 Jan 90 02:01:05 C
Date: Tue, 2 Jan 90 07:47:25 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00474; 2 Jan 90 7:43 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00491; 2 Jan 90 7:31 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3954; Tue, 02
Jan 90 07:38:12 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0281; Tue, 02 Jan 90 07:38:12 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5967; Tue, 02 Jan 90 01:35:00 C
Date: Tue, 2 Jan 90 07:11:26 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa10873; 30 Dec 89 3:58 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa08206; 30 Dec 89 3:48 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0662; Sat, 30
Dec 89 03:53:01 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8242; Sat, 30 Dec 89 03:53:00 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
3222; Fri, 29 Dec 89 21:51:58 C
Date: Sat, 30 Dec 89 03:50:07 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 85 attempts over 170 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac14832; 23 Dec 89 1:39 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa13714; 23 Dec 89 1:38 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 8765; Sat, 23
Dec 89 01:38:41 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
5760; Sat, 23 Dec 89 01:38:41 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
3719; Fri, 22 Dec 89 18:00:04 C
Date: Fri, 22 Dec 89 04:49:58 GMT
Reply-To: tlimonce@uucp.drunivac
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: tlimonce@uucp.drunivac
Subject: Re: How do YOU accept a newsfeed?
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912190551.AA27490@uunet.uu.net>,
munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) writes:
> This has me beat - in newsutility do_newg calls sys_accept (or some similar
> name) which should reject newsgroup ba.forsale and NOT create it - what versio
n
> are you running????
We're running version 5.9B (Or is it 5.9A? I'm not sure. I did at
least one set of patches but it's the set that didn't include a
change to the VERSION command. I guess that's 5.9A, eh?)
Guess what? The problem magically fixed itself. How often does NEWS
re-read the NEWS.SYS file? Only when the first person enters news?
The problem went away after a few days, which is about how often
there is a time when everyone exits news.
I don't think we rebooted, we're pretty 24hrs around here (library
automation mostly, students reading news and mail is the other
reason) so if we crashed & rebooted I would have heard about it.
-Tom
(replying to this addres won't work yet... try tlimonce@drew.bitnet,
tlimonce@drew.uucp, rutgers!drew!tlimonce or limonce@pilot.njin.net)root@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00672; 2 Jan 90 8:14 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00710; 2 Jan 90 8:05 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4210; Tue, 02
Jan 90 08:12:33 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0443; Tue, 02 Jan 90 08:12:33 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6643; Tue, 02 Jan 90 02:00:54 C
Date: Tue, 2 Jan 90 07:44:45 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ad00418; 2 Jan 90 7:33 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00455; 2 Jan 90 7:22 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3904; Tue, 02
Jan 90 07:28:59 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0232; Tue, 02 Jan 90 07:28:59 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5549; Tue, 02 Jan 90 01:15:05 C
Date: Tue, 2 Jan 90 07:04:46 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa09032; 31 Dec 89 1:41 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa06681; 31 Dec 89 1:33 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3801; Sun, 31
Dec 89 01:38:15 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1159; Sun, 31 Dec 89 01:38:15 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
2567; Sat, 30 Dec 89 19:36:26 C
Date: Fri, 29 Dec 89 23:47:16 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: RE: Troubles adding batches with 5.9B
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912190737.AA16720@uunet.uu.net>,
munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) writes:
>>We are running NEWS 5.9B.
>>
>>Last night a large number of articles that arrived in "rnews" format were
>>rejected by the add/network command, with messages of the form
>>
>> Add <id> news.group: JUNK (Cannot open output file (write access))
>>or
>> Add <id> junk: REJECT (Cannot open output file (write access))
>>
> .......
>
> check which account owns the itm files, and then check the diskquota entry - i
t
> looks like you are out of quota (or out of free space on the disk).
>
Accounts and file ownership and directory protections and all were all as they
used to be and as they are now -- ie I didn't change anything and things just
suddenly started to work again. We don't use diskquotas here, and it's quite
unlikely that the disk was full, since (a) there was 75 Mbytes of free space
the next morning and (b) some batches had some items that were received
correctly.
> its just another of the integration problems - vaxc is not quite VMS - at this
> point the NEWS code sees a -1 value from a file operation and says "oh well -
> nice try" - to get past this to the RMS return status is what you are asking
> for... could be interesting!
imho this is one of the things that really needs to be worked on. It's a
real pain to track down the cause of problems when the only diagnostic is
equivalent to "there's a problem".
Another nicety in the "problem tracking" area would be some trace capability.
Folks are always having troubles getting their news.sys and news.distribution
files right; it'd be nice to turn on a "forwarding trace" feature and get
output like
neighbor system crash: Item not forwarded (news.sys filter)
neighbor system pnet01: Item not forwarded (news.distribution filter)
where each decision is made.
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00745; 2 Jan 90 8:24 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00773; 2 Jan 90 8:12 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4362; Tue, 02
Jan 90 08:19:29 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0531; Tue, 02 Jan 90 08:19:29 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6729; Tue, 02 Jan 90 02:01:16 C
Date: Tue, 2 Jan 90 07:44:54 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ae00416; 2 Jan 90 7:33 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00457; 2 Jan 90 7:22 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3909; Tue, 02
Jan 90 07:29:09 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0234; Tue, 02 Jan 90 07:29:09 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5585; Tue, 02 Jan 90 01:15:32 C
Date: Tue, 2 Jan 90 06:24:02 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa11533; 30 Dec 89 5:00 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa08523; 30 Dec 89 4:52 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0867; Sat, 30
Dec 89 04:56:58 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8415; Sat, 30 Dec 89 04:56:57 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
4502; Fri, 29 Dec 89 22:55:33 C
Date: Sat, 30 Dec 89 04:51:14 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 88 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa16705; 23 Dec 89 4:30 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa14346; 23 Dec 89 4:25 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0985; Sat, 23
Dec 89 03:54:48 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
7862; Sat, 23 Dec 89 03:54:48 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
7608; Fri, 22 Dec 89 21:53:46 C
Date: Fri, 22 Dec 89 17:12:43 GMT
Reply-To: Daniel Berglund <foperator@se.chalmers.tekno>
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: Daniel Berglund <foperator@se.chalmers.tekno>
Subject: Re: Troubles adding batches with 5.9B
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912190723.AA14204@uunet.uu.net>,
munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) writes:
>>Suggestions: 1. Add an interpretation of the error status return from
>>file open attempts. These messages would be a lot more helpful if
>>accompanied by "no privilege for attempted operation" or "no such device"
>>or whatever.
> its just another of the integration problems - vaxc is not quite VMS - at this
> point the NEWS code sees a -1 value from a file operation and says "oh well -
> nice try" - to get past this to the RMS return status is what you are asking
> for... could be interesting!
Maybe I'm overlooking something obvious, but the rms STS value can be
found in vaxc$errno (but I don't know how to access the STV value). Example:
#include errno
#include perror
main()
E
fopen("sahdjgf$$$","r");
perror("Blurp");
printf("%d %d\n",errno,vaxc$errno);
fopen("sdf:asjklhdf$$$","r");
perror("Blurp");
printf("%d %d\n",errno,vaxc$errno);
fopen("gdgd%gsgs","r");
perror("Blurp");
printf("%d %d\n",errno,vaxc$errno);
L
yields:
$ r apa
Blurp: no such file or directory
2 98962
Blurp: no such device or address
6 99524
Blurp: non-translatable vms error code: 0x18744, vms message:
%rms-f-wld, invalid wildcard operation
65535 100164
--
Daniel Berglund (foperator@tekno.chalmers.se, BITNET: FOP@SECTHF51)
Chalmers University of Technology, G|teborg, Swedenroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00745; 2 Jan 90 8:24 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00781; 2 Jan 90 8:13 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4398; Tue, 02
Jan 90 08:20:41 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0547; Tue, 02 Jan 90 08:20:40 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
7010; Tue, 02 Jan 90 02:12:14 C
Date: Tue, 2 Jan 90 07:58:04 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00538; 2 Jan 90 7:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00539; 2 Jan 90 7:43 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4058; Tue, 02
Jan 90 07:50:58 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0329; Tue, 02 Jan 90 07:50:58 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6168; Tue, 02 Jan 90 01:38:51 C
Date: Tue, 2 Jan 90 07:21:05 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00267; 2 Jan 90 7:17 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00373; 2 Jan 90 7:08 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3738; Tue, 02
Jan 90 07:00:05 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0098; Tue, 02 Jan 90 07:00:04 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5181; Tue, 02 Jan 90 00:56:29 C
Date: Tue, 2 Jan 90 06:29:14 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac12347; 30 Dec 89 6:08 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09015; 30 Dec 89 6:02 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0975; Sat, 30
Dec 89 06:07:38 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8513; Sat, 30 Dec 89 06:07:38 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5421; Sat, 30 Dec 89 00:06:40 C
Date: Sat, 30 Dec 89 05:56:06 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 91 attempts over 172 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ad14251; 23 Dec 89 0:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa13513; 23 Dec 89 0:49 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7997; Sat, 23
Dec 89 00:50:31 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
4992; Sat, 23 Dec 89 00:50:31 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8819; Fri, 22 Dec 89 11:52:22 C
Date: Thu, 21 Dec 89 19:55:39 GMT
Reply-To: brodie@edu.mcw.fps
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: brodie@edu.mcw.fps
Subject: Re: RE: rot13 utility in DCL. (and TPU suggestion)
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <8912200842.AA22375@uunet.uu.net>, munnari!csc.anu.oz.au!gih900@UUNET
.UU.NET (Geoff Huston) writes:
[stuff deleted about my dcl rot13 utility)
> I'm impressed!!!
thanks, geoff!!
>>READ/ROT13, so it shouldn't be TOO tough....)
>
> Wouldn't it be better to have a TPU edit procedure called rot13 to allow you
> to rot the necessary bits??
> (said he trying to avoid having to add the code)
>
> Geoff
hey, now THERE's a neat idea. The tricky part is to tell TPU to do the
ROT13 stuff when WRITING the file upon exit. Sounds neat, and I'm sure
it's pretty easy to do. Unfortunately, I don't know tpu programming
at ALL... never had time do learn it (I really should... maybe this would
be a good project?)
unless someone ELSE wants to do it.....
-------------------------------------------------------------------------------
Kent C. Brodie - Systems Manager brodie@mcw.edu
Medical College of Wisconsin +1 414 778 4500
"Gee, I hope these are the right coordinates..." -Chief O'Brian; STTNGroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac00745; 2 Jan 90 8:24 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00783; 2 Jan 90 8:14 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4405; Tue, 02
Jan 90 08:20:51 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0551; Tue, 02 Jan 90 08:20:51 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
7047; Tue, 02 Jan 90 02:13:45 C
Date: Tue, 2 Jan 90 07:59:32 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00536; 2 Jan 90 7:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00527; 2 Jan 90 7:42 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4016; Tue, 02
Jan 90 07:49:45 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0315; Tue, 02 Jan 90 07:49:45 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6025; Tue, 02 Jan 90 01:35:40 C
Date: Tue, 2 Jan 90 07:20:34 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00266; 2 Jan 90 7:17 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00371; 2 Jan 90 7:07 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3733; Tue, 02
Jan 90 06:59:10 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0096; Tue, 02 Jan 90 06:59:10 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5153; Tue, 02 Jan 90 00:56:08 C
Date: Tue, 2 Jan 90 06:35:33 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa05244; 29 Dec 89 19:07 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa04822; 29 Dec 89 18:56 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7074; Fri, 29
Dec 89 19:01:09 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
5479; Fri, 29 Dec 89 19:01:08 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
9654; Fri, 29 Dec 89 13:00:44 C
Date: Fri, 29 Dec 89 18:49:31 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 107 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab08434; 22 Dec 89 17:57 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa09712; 22 Dec 89 17:53 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4931; Fri, 22
Dec 89 17:53:48 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
2225; Fri, 22 Dec 89 17:53:47 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8790; Fri, 22 Dec 89 11:52:08 C
Date: Thu, 21 Dec 89 22:00:50 GMT
Reply-To: glassmann@com.camb.ccavax
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: glassmann@com.camb.ccavax
Subject: arbitron is coming
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
I've made some progress on writing arbitron. It should be ready in a couple of
days. I'm trying to do approximately the same thing that the unix script does.
I'm writing it in C, using lot's of calls to NEWS functions, there was no
practical way to write it in DCL. I'll send more details soon.
--
Lenny Glassmann glassmann@ccavax.camb.comroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ad00745; 2 Jan 90 8:24 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00799; 2 Jan 90 8:15 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4432; Tue, 02
Jan 90 08:22:10 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0564; Tue, 02 Jan 90 08:22:09 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
7102; Tue, 02 Jan 90 02:14:09 C
Date: Tue, 2 Jan 90 07:59:50 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ad00536; 2 Jan 90 7:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00533; 2 Jan 90 7:43 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4048; Tue, 02
Jan 90 07:50:28 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0325; Tue, 02 Jan 90 07:50:27 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6105; Tue, 02 Jan 90 01:37:28 C
Date: Tue, 2 Jan 90 07:20:50 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00267; 2 Jan 90 7:17 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00377; 2 Jan 90 7:09 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3750; Tue, 02
Jan 90 07:00:56 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0104; Tue, 02 Jan 90 07:00:55 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5235; Tue, 02 Jan 90 00:57:19 C
Date: Tue, 2 Jan 90 06:28:41 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa10706; 31 Dec 89 4:55 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa07284; 31 Dec 89 4:44 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4504; Sun, 31
Dec 89 04:49:29 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
1864; Sun, 31 Dec 89 04:49:29 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
4058; Sat, 30 Dec 89 22:49:03 C
Date: Sat, 30 Dec 89 15:54:21 GMT
Reply-To: jeh@com.simpact
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: jeh@com.simpact
Subject: Re: Arbitron
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
Nice job, Lenny!
I've put the following in my NEWSSKIM.COM to automatically run ARBITRON
near the end of the month. Location is not critical (I have it just after
the SKIM operation). Note that it is not necessary to run this code once
per day, ie it need not be "under" the first-run-of-new-day test, but it
won't hurt if it is, either.
I didn't know if decwrl needed some precise format for the mail subject
line, so I just fudged something.
$ ! ---------------------
$ ! If it's close to the end of the month, run the arbitron program and
$ ! mail the results to decwrl.
$
$ test_mo = f$element(1, "-", f$cvtime("''f$time()'+2-0:0:0", "ABSOLUTE"))
$
$ ! In the preceding line, the "2-0:0:0" means that this code will trigger
$ ! if it's 2 days (ie 48 hours -- or closer) to the end of the last day of
$ ! the month. Modify this (ie make it bigger) if you are far away from
$ ! decwrl (in terms of number of days for delivery). To be included in the
$ ! monthly arbitron stats, the mail message should get there before 00:00
$ ! preceding the first of the new month (or 23:59.59.99 ending the last
$ ! day of the current month, if you prefer).
$
$ this_mo = f$element(1, "-", f$time()) ! note: we use this_mo later.
$ day_of_month_ok = this_mo .nes. test_mo
$
$ ! Have we done it this month already?
$
$ if (f$search("news_log:arbitron.out").eqs."")
$ then
$ ! ok if haven't done it before, at all.
$ month_ok = 1
$ else
$ ! ok if last month run is different from current month.
$ last_arb = f$file("news_log:arbitron.out","CDT")
$ month_ok = f$element(1, "-", last_arb) .nes. this_mo
$ endif
$
$ if (day_of_month_ok .and. month_ok)
$ then
$ write sys$output "Arbitron Beginning at ''f$time()'"
$ run uucp_bin:arbitron
$ rename arbitron.out news_log:
$ purge news_log:arbitron.out
$ host = f$logi("uucp_host_name")
$ mmm_yyyy = f$elem(0, " ", f$time()) - f$elem(0, "-", f$time()) - "-"
$ mail news_log:arbitron.out -
/subj="Arbitron stats from uucp host ''host' for ''mmm_yyyy'" -
uucp%"""netsurvey@decwrl.dec.com""",usenet
$ write sys$output "Arbitron Completed at ''f$time()'"
$ endif
$
--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG
Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp: ...Ecrash,scubed,decwrlL!simpact!jehroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ad00746; 2 Jan 90 8:24 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00802; 2 Jan 90 8:16 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4455; Tue, 02
Jan 90 08:23:03 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0583; Tue, 02 Jan 90 08:23:02 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6760; Tue, 02 Jan 90 02:01:30 C
Date: Tue, 2 Jan 90 07:39:50 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ae00418; 2 Jan 90 7:33 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00459; 2 Jan 90 7:22 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3914; Tue, 02
Jan 90 07:29:40 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0236; Tue, 02 Jan 90 07:29:40 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5630; Tue, 02 Jan 90 01:16:00 C
Date: Tue, 2 Jan 90 06:35:47 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00625; 30 Dec 89 7:57 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00540; 30 Dec 89 7:50 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 1160; Sat, 30
Dec 89 07:55:29 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
8682; Sat, 30 Dec 89 07:55:29 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6670; Sat, 30 Dec 89 01:53:12 C
Date: Sat, 30 Dec 89 07:48:42 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 77 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00313; 23 Dec 89 7:11 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00343; 23 Dec 89 7:05 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3573; Sat, 23
Dec 89 07:07:18 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0514; Sat, 23 Dec 89 07:07:17 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
8488; Fri, 22 Dec 89 22:52:21 C
Date: Fri, 22 Dec 89 14:07:42 GMT
Reply-To: brodie@edu.mcw.fps
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: brodie@edu.mcw.fps
Subject: TPU procedure for rot13. My examples. (enjoy)
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
Well, here it is, my first attempt at TPU programming. I have to
thanks Geoff for forcing me to do this (well, not forcing, but I
needed a good excuse to learn how to do junk inside of TPU for a
change.... up to this point, I'd never used my own SECTION file.
Damned neat, once you take the time to learn it......)
First off, I would like to show you my "first" attempt at a rot-13
procedure. works pretty damned good, for a first try....
(no flames, please. I'm a good programmer, but TPU is totally new to
me. It doesn;t help when you don't know all of the neat stuff available..)
!
! TPU procedure to ROT13 a text file.
! Copyright (C) 1989 Kent C. Brodie / Medical College of Wisconsin
! This software is available to all VAX users, and can be distributed
! freely as long as the above copyright is included. So there.
!
procedure eve_rot13
message ("Beginning ROT13 procedure...");
letterpat := ANY("ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
position(beginning_of(current_buffer)); ! Go to the star
t of the current buffer
loop; ! For each character in buffer
exitif (mark(none) = end_of(current_buffer)); ! exit if EOF found
match_pos := search_quietly (letterpat, FORWARD); ! find the next (A-Z|a-z
)
exitif (match_pos = 0);
position (match_pos); ! go there
letterval := ASCII(current_character);
newletter := "";
if (letterval >= 65) and (letterval <= 90)
then
if (letterval > 77)
then
letterval := letterval - 13;
else
letterval := letterval + 13;
endif;
newletter := ASCII(letterval);
else
if (letterval >= 97) and (letterval <= 122)
then
if (letterval > 109)
then
letterval := letterval - 13;
else
letterval := letterval + 13;
endif;
newletter := ASCII(letterval);
endif;
endif;
if (newletter <> "")
then
deleted_char := erase_character(1);
copy_text(newletter);
endif;
endloop;
endprocedure;
that was my first try. Then I realized that was pretty gross, so I
bettered it. I removed all of those multiple if statements, and
used a long alphabet string. Locate the letter, move 13 right,
grab the new letter, done. My first example used too many of the
old "fortran" or "pascal" methods of doing it. The second pass
made use of the TPU string handling junk. much nicer.
!
! TPU procedure to ROT13 a text file.
! Copyright (C) 1989 Kent C. Brodie / Medical College of Wisconsin
! This software is available to all VAX users, and can be distributed
! freely as long as the above copyright is included. So there.
!
! This procedure works by utilizing the string handling capabilities
! of TPU. The string "letters" is used for the rot-ting process, which
! is why there are TWO sets of upper and lower case. In this fashion,
! the "rot" factor (see variable rotfactor) can be changed to create a
! new rot program (such as rot17, etc.).
!
procedure eve_rot13
!declare program constants to be used. Change "rotfactor" to do the
!rot-ting of your choice. Due to popularity, the default is 13.
!
rotfactor := 13;
letterpat := ANY("ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
letters := "ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmno
pqrstuvwxyzabcdefghijklmnopqrstuvwxyz";
message ("Beginning ROT13 procedure...");
position(beginning_of(current_buffer)); ! Go to the top...
loop; ! For each character in buffer
exitif (mark(none) = end_of(current_buffer)); ! exit if EOF found
match_pos := search_quietly (letterpat, FORWARD); ! find the next (A-Z|a-z
)
exitif (match_pos = 0); ! exit if no more letters found
position (match_pos); ! go there
letterpos := index (letters,current_character); ! Look in "letters" for index
letterpos := letterpos + rotfactor; ! ad the "rot factor" to the ind
ex
newletter := substr (letters,letterpos,1); ! create the new letter
deleted_char := erase_character(1); ! delete the old character
copy_text(newletter); ! replace it with the new one.
endloop;
endprocedure;
Now I thought I was done. Nice, clean, compact code. Then I saw it.
(gee, you mean it helps to RTFM?) heh. God bless it, it was right
in the (^!%^(&! book. Seems there's this neat little TPU built-in
called TRANSLATE that does all the work for you, and is quite flexible.
I basically ended up stealing this from the book, but hey, that's what
us computer folk do best, make use of someone ELSE's work..
!
! TPU procedure to ROT13 a text file.
! 12/20/1989 Kent C. Brodie / Medical College of Wisconsin
!
! This procedure example was taken from page 4-352 of the VAXTPU reference
! manual. Seems that TPU has a REAL easy way to do this, using the TRANSLATE
! built-in.
!
procedure eve_rot13
translate (current_buffer,
"NOPQRSTUVWXYZABCDEFGHIJKLMnopqrstuvwxyzabcdefghijklm",
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz");
message ("ROT13 complete.")
endprocedure;
cute, eh?
(and about 10 times faster than my code. *sigh*...)
-------------------------------------------------------------------------------
Kent C. Brodie - Systems Manager brodie@mcw.edu
Medical College of Wisconsin +1 414 778 4500
"Gee, I hope these are the right coordinates..." -Chief O'Brian; STTNGroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00746; 2 Jan 90 8:24 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00775; 2 Jan 90 8:12 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4367; Tue, 02
Jan 90 08:19:34 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0533; Tue, 02 Jan 90 08:19:33 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6956; Tue, 02 Jan 90 02:11:34 C
Date: Tue, 2 Jan 90 07:57:57 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa00538; 2 Jan 90 7:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00531; 2 Jan 90 7:43 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4043; Tue, 02
Jan 90 07:50:12 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0323; Tue, 02 Jan 90 07:50:12 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6084; Tue, 02 Jan 90 01:36:55 C
Date: Tue, 2 Jan 90 07:21:48 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa09748; 30 Dec 89 1:50 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa07790; 30 Dec 89 1:42 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0280; Sat, 30
Dec 89 01:46:54 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
7898; Sat, 30 Dec 89 01:46:54 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
0524; Fri, 29 Dec 89 19:41:24 C
Date: Sat, 30 Dec 89 01:36:29 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Timeout
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
The NIFTP process gave up after 116 attempts over 168 hours
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa14379; 23 Dec 89 1:03 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa13555; 23 Dec 89 0:59 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 8191; Sat, 23
Dec 89 00:59:18 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
5176; Sat, 23 Dec 89 00:59:17 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
0592; Fri, 22 Dec 89 12:59:55 C
Date: Thu, 21 Dec 89 21:41:50 GMT
Reply-To: tanner@edu.cerritos
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: tanner@edu.cerritos
Subject: Re: How to use patch?
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
In article <4981.25908cae@pbs.uucp>, sdroppers@pbs.uucp writes:
> I have checked back, but I cannot find anything, is there a man page or such
> that someone can post (or E-Mail) about how to use patch? If patch is a *nix
> tool then I am in the dark, we have no such docs available.
Here's a DCL file I used to patch 5.9C. I copied the News 5.9 sources and the
5.9C .DIFF files to a directory (yes, on the same disk as sys$scratch) and
executed this file. Everything seemed to update fine. Beware the logical
UTL:, it's where we put our utilities.
$ set noon
$ patch := $utl:patch
$ rename newsmail.c newsvmsmail.c
$ context = 0
$loop: ! loop for all .diff files
$ dif = f$search("*.diff",context)
$ if dif .eqs. "" then exit
$ name = f$parse(dif,,,"name") + f$parse(dif,,,"type") ! make short filename
$ open file 'dif'
$ read/end_of_file=empty file line ! read the diff file header
$ start = f$locate("]",line) + 1
$ dest = f$extract(start,f$length(line)-start,line) ! extract filename
$ read/end_of_file=empty file line
$ read/end_of_file=empty file line ! test for empty diff files
$ write sys$output "patching ''dest'"
$ patch 'dest' 'name''type'
$empty: ! .diff file contains header only, skip patch
$ close file
$ goto loop
If you need patch.exe, it's on gray.cerritos.edu for anonymous ftp.
-Bruce
--
Bruce Tanner (213) 860-2451 x 596 Tanner@Cerritos.EDU
Cerritos College Norwalk, CA cerritos!tannerroot@NSFNET-RELAY.AC.UK (01/02/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac00746; 2 Jan 90 8:24 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00785; 2 Jan 90 8:14 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4420; Tue, 02
Jan 90 08:21:52 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0560; Tue, 02 Jan 90 08:21:51 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
7070; Tue, 02 Jan 90 02:13:56 C
Date: Tue, 2 Jan 90 07:59:43 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ac00536; 2 Jan 90 7:53 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00529; 2 Jan 90 7:43 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4035; Tue, 02
Jan 90 07:50:05 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0319; Tue, 02 Jan 90 07:50:05 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
6065; Tue, 02 Jan 90 01:36:25 C
Date: Tue, 2 Jan 90 07:21:16 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id ab00266; 2 Jan 90 7:17 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa00375; 2 Jan 90 7:08 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3745; Tue, 02
Jan 90 07:00:31 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
0102; Tue, 02 Jan 90 07:00:31 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
5215; Tue, 02 Jan 90 00:56:53 C
Date: Tue, 2 Jan 90 06:27:52 GMT
Reply-To: root@uk.ac.nsfnet-relay
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
From: root@uk.ac.nsfnet-relay
Subject: Mail Delivery Failure to uk.ac.king - Rejected
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the remote host was:
Invalid value in command: invalid attribute - filename
"FTP$NETWELL:MAILTMP.TMP".
File open failure reason - device full (insufficient space for allocation).
Secondary reason - device full - allocation failure.
Username ignored.
VAX/VMS FTP (80) Version 5.0.
Your message was not delivered to the following addresses:
GPKING@uk.ac.kingston
Your message begins as follows:
Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK
Via Ethernet with SMTP id aa03350; 28 Dec 89 17:56 GMT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK
via Janet with NIFTP id aa03918; 28 Dec 89 16:21 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7383; Thu, 28
Dec 89 16:25:42 GM
Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id
6750; Thu, 28 Dec 89 16:25:42 G
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
4843; Thu, 28 Dec 89 08:20:57 C
Date: Wed, 27 Dec 89 17:03:14 GMT
Reply-To: Jim Gerland <gerland@edu.buffalo.acsu>
Original-Sender: ANU-NEWS Discussion <ANU-NEWS@earn.ndsuvm1>
Comments: Warning -- original Sender: tag was nobody@ACSU.BUFFALO.EDU
From: Jim Gerland <gerland@edu.buffalo.acsu>
Subject: Help with ANU News V5.9
To: Multiple recipients of list ANU-NEWS <ANU-NEWS@earn.ndsuvm1>
Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay
I am trying to install V5.9 and have a few questions.
The person who installed V5.8 is no longer here so please bear with me.
We would like to use the NNTP with V5.9 and WIN/TCP V5.1
I decided to just install V5.9 from scratch and have followed the instructions
in the doc (although it is V5.8 - is there a newer doc?).
I get to the point in section 10.9 First Time Execution of NEWS and things
begin to fall apart. It does not do what paragraph 2 says it should (create
files in news_root: and news_manager:).
So then I invoke NEWS and first do a SET NEWSGROUP DEFAULT /SERVER=NEWS
/PROTOCAL=WINTCP /FILEHOLD=0, where NEWS is the name of my Unix newsserver,
eerie.cs.buffalo.edu
Next, I CREATE CONTROL /LOCAL and CREATE JUNK /LOCAL as per the last paragraph
in section 10.9 and then go into rn on my Unix machine and get the latest
version of checkgroups. from the news.admin newsgroup, copy it to my
VAXcluster, edit it appropriately and do an ADD FILE CHECKGROUPS. but this
only adds an entry into the CONTROL newsgroup. Am I doing something wrong?
Any help would be greatly appreciated. Thanks.
Jim Gerland UUCP: ...Eallegra,decvax,watmathL!sunybcs!gerland
CSNET: gerland@buffalo
UCS BITNET: gerland@ubvms (VAX/VMS)
SUNY at Buffalo gerland@ubvm (VM/CMS)root@NSFNET-RELAY.AC.UK (01/16/90)
The NIFTP process was unable to
deliver your mail to host uk.ac.king
over janet.
The reason given by the local host was:
file not found