HDTenEightyP/NetNews huggingface dataset:
X-Envelope-to: MEDLIB-L@UBVM.CC.BUFFALO.EDU
MIME-version: 1.0
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT
Posting-date: 14 Sep 1992 15:02:00 -0500 (EST)
Importance: normal
Priority: non-urgent
X-Hop-count: 2
A1-type: MAIL
Newsgroups: bit.listserv.medlib-l
Date:         Tue, 8 Sep 1992 10:29:00 -0500
From:         Theodore.Morris@UC.EDU
Subject:      More info on tools for CD-ROM prodn?

Thanks to everyone who sent information and suggestions regarding
authoring and retrieval tools for producing/searching CD-ROMs.  We've
begun tracking down information, and trying to evaluate, a number of
products, including but not limited to Ntergaid's HyperWriter, askSAM,
hyperREZ, KAware, Folio Views, and BRS/Search for MS-DOS.

Particularly in regard to the last three (KAware, Folio, and
BRS/Search for MS-DOS)
	Can anyone give me first-hand comments regarding the construction of a
	database with the product, including the type and amount of effort
	required to markup or otherwise prepare data for inclusion into the
	database?

Particularly in regard to BRS/Search for MS-DOS
	Can anyone give me first-hand comments regarding the "hypertext"
	linking features and their implementation?  We are familiar with the
	searching and general database arrangments of the BRS/Search products
	for VMS, but have not gotten much information on the
	mechanics/capabilities of the linking features of the MS-DOS product.

So far we have only seen a working copy of Folio, but are working on
arrangements to try other products as well before making our decision.
Any experiences/anecdotes you can share would be very welcome.

Ted Morris, University of Cincinnati
Medical Center Information and Communications
Information Research & Development
morrista@uc.edu  513-558-0177V, 513-558-0758F
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Subject: (no subject given)
Organization: The Health Foundation
X-Mailer: PSILink (1.0n)
Newsgroups: bit.listserv.medlib-l
Date:         Wed, 9 Sep 1992 09:06:33 -0500
From:         "The Health Foundation" <ny0055@MAIL.NYSER.NET>

Your message was received.

>DATE:   Tue, 8 Sep 1992 14:04:18 CDT
>FROM:   DORMER, LARRY <LDORMER@LIFE.JSC.NASA.GOV>
>
>*************************************************
>*       Please acknowledge receipt of this      *
>*       message back to the originator.         *
>*************************************************
>
>SUBSCRIBE MEDLIB-L LARRY DORMER
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Original_To:  BITNET%"MEDLIB-L@UBVM.BITNET"
Original_cc:  KINGH
Newsgroups: bit.listserv.medlib-l
Date:         Mon, 14 Sep 1992 08:01:00 EDT
From:         KINGH@SNYSYRV1.BITNET
Subject:      RE: Book and Journal repairs

Here at the SUNY HSC Library tech services handles most repairs.  However,
repairs, unless emergency, are the lowest priority.
        Replacement sheets are ordered by ILL, when possible.
        The decision to replace a missing item or one damaged beyond repair is
made by the CD department with input from the reference department.  Decisons
are made according to usage, historical value, faculty and reference department
input, cost, and currency criteria.
        Re-binding decisions are made on the basis of the above criteria with
input from reference staff and are handled by the serials department.
        Training is provided on-site by our archivist and the head of our
special collections department.  Staff are encouraged to attend local CE
courses covering preservation, binding, and repair.
        As I weed the collection I record the call number of each book that
needs repair.  Some books I decide to keep in the collection until they are
no longer usable because their value is less than the cost in time, effort,
and money to repair or to replace.  When the technical services department
determines they can spare time for repairs items will be removed from the
shelf for repair.  If an item is not in usable condition and does not meet
criteria for repair or replacement, it is withdrawn.
        Decisions to replace missing issues are made by the CD department.
        Items needing repair are also identified at the circulation desk,
during re-shelving, and by patrons.  Once identified they are sent to the
technical services department.

Hannah King
SUNY HSC Library at Syracuse
kingh@snysyrv1
kingh@vax.cs.hscsyr.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.medlib-l
Date:         Thu, 10 Sep 1992 16:45:00 EST
From:         "USA::SSC26857" <SSC26857%USA.decnet@USAV01.GLAXO.COM>
Subject:      MESSAGE

YOUR MESSAGE WAS RECEIVED
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: MEDLIB-L@UBVM.BITNET
X-VMS-To: IN%"MEDLIB-L@UBVM.BITNET"
Newsgroups: bit.listserv.medlib-l
Date:         Tue, 8 Sep 1992 09:19:00 MST
From:         Marilyn McCarthy <MCCARTH@ARIZVMS.BITNET>
Subject:      Re: Book and Journal repairs

The person who processes journals for binding is in charge of repairs
for books and journals. I think she has a student do it most of the
time and she trains them.  I think the Head of Serials trained her.
If pages are missing, a form is filled out by the Bindery person
and given to ILL who requests the pages. If a patron wants the pages
that are missing, s/he fills out the form and then when the pages
come in, ILL copies the pages for the library.

Marilyn Mc
Marilyn Mc
AHS Library
University of Arizona
mccarth@ccit.arizona.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.medlib-l
Date:         Mon, 14 Sep 1992 15:47:28 CDT
From:         FRSC4F5@PANAM.BITNET
Subject:      RE: Workshop/Job postings

This was suggested before by other readers. I hope those who post these
valuable information will pay a little more attention to these requests.
F.R. UTPA
From: GIGLIO%VAXA.decnet@FAXON.COM (VAXA::GIGLIO)
Newsgroups: bit.listserv.medlib-l
Subject: RE: publisher address
Date: 15 Sep 92 19:34:00 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU

Deborah,
     The publisher for 'Cardiology in the Young' is World Publishers,
1811 Billabong Ln, Chapel Hill, N.C. 27516.  Phone # is (919-929-9091).
In the Faxon title file is a note that the publisher changed is early
In the Faxon title file is a note that the publisher changed in early
1991.  The 1992 price was $125 (we do not have a price yet for 93).
                         Good luck
Internet  giglio@faxon.com
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.medlib-l
Date:         Thu, 10 Sep 1992 13:42:53 EDT
From:         Nancy Start <HSLSTART@UBVM.BITNET>
Subject:      No more acknowledgments, please!

MEDLIB-L Readers,

Please do NOT respond to the misdirected subscription
request which contained the following:
>
>*************************************************
>*       Please acknowledge receipt of this      *
>*       message back to the originator.         *
>*************************************************
>
>SUBSCRIBE MEDLIB-L LARRY DORMER

This was not a system test!  It was just a request to
be added to MEDLIB-L (with a twist...)

Nancy

*****************************************************************
*  Nancy Start               //                                 *
*  MEDLIB-L List Owner       //   Phone... (716) 829-3337       *
*  Health Sciences Library   //   BITNET... HSLSTART@UBVM       *
*  University at Buffalo     //   Internet...                   *
*  Buffalo, NY 14214         //   HSLSTART@UBVM.CC.BUFFALO.EDU  *
*****************************************************************
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: MEDLIB-L@UBVM.cc.buffalo.edu
X-VMS-To: SSCVAX::IN%"MEDLIB-L@UBVM.cc.buffalo.edu"
X-VMS-Cc: TOMFLEM
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.medlib-l
Date:         Wed, 9 Sep 1992 13:25:13 -0400
From:         "Tom Flemming,
              McMaster University HSL" <TOMFLEM@HSCVAX.CSU.MCMASTER.CA>
Subject:      Re: Seminars in Oncology Supplements

Canadian libraries are receiving at least some of the supplements to
"Seminars in oncology" which are not being distributed in the U.S.

Having checked our shelves and our kardex, I can tell you that we have
received supplements 1 and 2 to volume 19.  We have not received
numbers 5 and 6 yet (we will claim them), although we do have also
supplements 3,4,7,8 and 9 as a part of volume 19.

One of the ways around this dilemna for U.S. librarians wanting to know
what papers appear in the supplements not being distributed in the U.S.
is an ILL request to your nearest friendly Canadian library with a
subscription to the title; you could ask for photocopy of the contents pages
of specific supplementary issues ...

........................................................................
Tom Flemming		    Internet:  tomflem@HSCvax.csu.McMaster.ca
Head of Public Services     Bitnet:    tomflem@McMaster
Health Sciences Library	    Envoy 100: mac.lib.hsl
McMaster University	    LIFEnet:   TFLEMMIN@life.jsc.nasa.gov
1200 Main Street West
Hamilton, Ontario	    (416) 525-9140   x2321	work
Canada   L8N 3Z5	    (416) 527-2848		home
........................................................................
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-VMS-To: IN%"MEDLIB-L@UBVM.cc.buffalo.edu"
Newsgroups: bit.listserv.medlib-l
Date:         Thu, 10 Sep 1992 14:11:00 CST
From:         MEWALKER@MBCF.STJUDE.ORG
Subject:      Re: Seminars in Oncology Supplements

My understanding is that these supplements were "sponsored" by drug
companies not in the US.  These companies (this company?) was not
willing to pay for distribution to US subscribers.  Saunders' position
is that our subscription fee covers only the main issues, not supplements.

We requested on interlibrary loan the table of contents for the first
supplement.  It concerns the drug Ifosfamide, which is certainly used
here.  I have written to Saunders to express my dismay and have asked
faculty members and adminstrators to write also, which some of them
have done.

According to a representative of Majors Scientific Books, there are no
more issues available, even if we wanted to buy one.  Therefore, we will
bind the table of contents with a note that this was not published in
the US.

Oh, we got the ILL from a Canadian library.

Mary Edith Walker (mewalker@mbcf.stjude.org)
St. Jude Children's Research Hospital
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Date:         Tue, 8 Sep 92 09:55:41 PST
From:         Larry Crawford <LCRAWFOR@UCDCVDLS>
Subject:      Share-Ware Screen Painter for VM
Comments: To: 9370-l@hearn, vmesa-l@uafsysb
Newsgroups: bit.listserv.9370-l

Does anyone know of a simple shareware screen painter for VM? We have
ISPF but don't have the time to devote to making screens with it and
we don't have any money for something like XMENU. Any suggestions
would be appreciated.


Thanks,                            \ /   University of Calif  Davis
Larry Crawford, Systems Specialist  *    California Veterinary Diagnostic
lcrawfor%ucdcvdls.bitnet           / \   Laboratory System (916) 752-4407
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Date:         Mon, 14 Sep 92 12:37:33 WST
From:         Amit=Rudra%IS=Staff%CURTIN@BA1.CURTIN.EDU.AU
Subject:      re: Share-Ware Screen Painter for VM
Comments: To: 9370-L%HEARN.BITNET@CUNYVM.CUNY.EDU
Newsgroups: bit.listserv.9370-l

There is a software called ISPFPC but it costs a little. I am not sure if it
will be enough for your need but certainly worth a look.

Thanks.

Amit Rudra
School of Information Systems
Curtin Univ. Of Tech.
Perth,  Australia
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Cambridge Computer Associates, Inc.
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf"
X-VMS-Cc: TINKELMAN
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 15 Sep 92 19:57:27 GMT
From:         Bob Tinkelman <bob@CAMB.COM>
Subject:      Defragment channel
Newsgroups: bit.listserv.pmdf-l

I am trying to use 4.1 facilities to fragment large messages and then
reassemble them between two systems that communicate via PhoneNet.
The sending system is breaking the large messages into smaller
components with what appear to be reasonable MIME headers indicating
the multiple parts.  However, the message is not being reassembled.
The pieces are delivered individually at the 2nd system.  I assume
I've misconfigured something at that end.

I could use a pointer to documentation on how to configure the
target system.  Is there an options file that controls things like
how long the fragments are allowed to sit around before being
forwarded, as is, unreassembled?  etc.

I tried searching the pmdf_root:[doc]*.sdml for `defragment' but,
if the information was there, I missed it.

BTW, this appears to be a feature that will help us a lot on this
particular link which is used to transfer, via 19.2K PhoneNet, some
really large, multimegabyte files.

Regards - Bob Tinkelman
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf-newsgate@mccall.UUCP"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 10 Sep 92 00:39:35 GMT
From:         alistair@MITS.COM.AU
Subject:      Mail system to use with PathWorks?
Newsgroups: bit.listserv.pmdf-l

We are currently in the process of connecting all our PC's to the
network using PathWorks, and I am trying to determine the most
appropriate mail system to put in place.  It must be able to integrate
with VMS Mail.

The possibilities seem to be:

1.      The unsupported mail client.  This is a DOS application and
        most of our users use Windows, so this is a bit clunky.

2.      Microsoft Mail as licensed with MS Office.  Has anyone
        integrated this with PMDF?

3.      DEC's Mailworks.

I would appreciate any comments.  If you wish to avoid a lengthy
argument on the list, feel free to mail opinions directly to me, and I
will summarise in a couple of weeks.

Thanks in advance,

Alistair Grant

Internet:     alistair@mits.com.au
Alternate:    alistair%mits.com.au@ucsvc.ucs.unimelb.edu.au
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Duke University Medical Center, Durham NC, USA
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 15 Sep 92 02:48:22 GMT
From:         "James Dryfoos - Postmaster" <DMPM@DUKEMC>
Subject:      User defined directory service?
Newsgroups: bit.listserv.pmdf-l

We have a database matching user full names, dept , ... to their mail id.
I would like to interface this somehow into PMDF.  What I want to be
able to do is to have a "user defined" directory capability.  For example,
I may want to permit a query structure that is last.first@mc.duke.edu
where one may have only a piece of that last name (i.e. would have to allow for
combinations of possibilities as well as multiple identical names).

As far as I can tell, PMDF only allows a one-to-one matching (i.e.  jim =
dryfo001 or dryfoos.jim = dryfo001).  I would like to do more than this.
Perhaps I need a rewrite rule that maps * to my homebrew channel?  Is
this possible?  I have currently been adding an alias for all users that
are not on the local system and that must go through my homebrew channel.
Once in my channel, I can do anything with the destination address.

Appreciate any responce or suggestions.  Sorry if I have just
overlooked something that already exists.

The only other thing is that this mechanism will need to support thousands of
user names.

-Jim

   =======================================================================
      James D. Dryfoos -- Postmaster    |  dmpm@mc.duke.edu
      Duke University Medical Center    |  dmpm@dukemc.bitnet
      Box 2914 DUMC                     |  (919) 684-6421 - office
      Durham, NC 27710 Earth            |  (919) 684-8675 - fax
   =======================================================================

Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"andrewr@itd.adelaide.edu.au"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sun, 13 Sep 92 00:40:32 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Problems with cc:Mail channel.
Newsgroups: bit.listserv.pmdf-l

>       I'm having two problems with the cc:Mail channel under PMDF.
> The first, of irritance value only, is that it manipulates spaces
> inside quotes in names to underscores in it's output file namem,
> including those around the "AT" which signifies the post office to go
> to, so it's treated as one user. We've got around this with a small
> program on the DOS side to change it back, and using cc:Mail's
> directory propogation so we don't have to specify the post office.

I gather from this that you're entering cc:Mail addresses as

    "user AT postoffice"@ccmail.whatever

on the Internet/PMDF side of things. This is incorrect and unsupported. The
proper form to use is

    user%postoffice@ccmail.whatever

where any spaces in the user part are replace with underscores and any
commas are replaced with plus signs. This is the supported format; it is
also the format that will be produced by the slave channel program.

>       The second problem is that it only works one way. It creates
> the output file just fine, in the correct format, but it doesn't seem
> to look at the input file specified. EG:

What are you doing to force processing of the input file? Processing
is not automatic -- it cannot be since PMDF has no way of sensing the
creation of the input file. You have to arrange to do a

    $ @PMDF_ROOT:[EXE]MASTER CC_LOCAL POLL

at the proper time. The periodic job can be told to do this when it runs if you
mark the channel with the master channel keyword.

> Obviously I'm doing something wrong as others have got this to
> work - can anyone offer any suggestions? The PC accesses the
> filesystem via PC-NFS through Multinet NFS on the VAX side.

What version of PMDF are you running. There have been a number of changes
and enhancements since the initial release. Please contact service@innosoft.com
and request the most recent version if you're not running at least V4.1-10.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@ymir.bitnet"
X-VMS-Cc: DPMSYS
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sun, 6 Sep 92 08:25:21 GMT
From:         "Dave Mulvihill - Technical Support x-6993" <DPMSYS@RITVAX>
Subject:      Using DELIVER
Newsgroups: bit.listserv.pmdf-l


I know this has been covered on this list before, but can
someone explain again why the VMS forwarding address cannot
be used as the determinant for the execution of DELIVER.

I recently encountered the following senario:

A user runs PMDF with integrated DELIVER on his home
machine (TECHNO).  On another machine (VAXA) which also runs
PMDF with DELIVER disabled he has his forwarding address set
to forward mail to his home machine.   His login directory on
VAXA is his home directory on TECHNO mounted on VAXA via
DEC's DFS.

This all worked fine until I enabled DELIVER on VAXA.  PMDF
ignored the forwarding to TECHNO and instead processed all
mail to his account on VAXA using his mail.delivery file
from TECHNO.

I realize there are workarounds such as defining different
mail.delivery file names for different nodes, but what are
the reasons for allowing the file to override a forwarding
address.  If there are no technical limitations to letting
the ~forwarding address be the deciding switch, can the switch
be defined in the PMDF option file.

Thanks,

Dave Mulvihill      (Postmaster)        Allin1: MULVIHILL DP
Systems Programmer                      Email:  dpmsys@ritvax.BITNET
Information Systems & Computing                 dpmsys@ritvax.isc.rit.edu
VAX/VMS, ULTRIX Technical Support
Rochester Institute of Technology, Rochester NY, 14623 (716) 475-6993
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: Buena Vista College, Storm Lake, IA
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf-newsgate@mccall.UUCP"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 11 Sep 92 07:28:03 GMT
From:         kraftjoel@BVC.EDU
Subject:      RE: Limiting access to outgoing mail.
Newsgroups: bit.listserv.pmdf-l

In article <01GOKRXC7ASI9TCNH3@INNOSOFT.COM>, dan@innosoft.com (Daniel C.
 Newman) writes:
>>         I'd like to be able to limit access to non-local (off-node) email.
>> I'm thinking that I can define a rights id, say 'NO_OUTMAIL' for example,
>> and set the appropriate image with an ACL such that anyone holding that id
>> cannot send internet mail messages.  My questions are simple:  Will this
>> work?  and, which image(s) should be set this way?
>
> This won't work since the users only run VMS MAIL or DECWindows MAIL.  They
> don't run the actual images which send outbound mail.  Instead, you probably
> want to associated this rightlist identifier with, say, your TCP/IP channel.
> You do this by merely specifying the rightlist id as a channel keyword; e.g.,
>
>         mtcp_local single smtp mx no_outmail
>
> Then, only processes with the no_outmail rightslist id can queue mail to
> the mtcp_local channel.  Be sure to grant this rightslist id to whatever
> accounts PMDF may run under!

We have the exact same situation here on our campus, and I think that the
solution is just a bit impractical.  On our campus, there are over 1000
accounts that *should* be able to use mail, but only about 50 that should
not.  Our system would be a rightslist nightmare if we tried this.

What we do isn't extremely graceful, but it certainly works.  Try putting an
ACL on the PMDF_MAILSHR image.  You can put this in your startup file or do it
anytime that PMDF is not installed:

        $ SET ACL/ACL=(ID=DISINMAIL,ACCESS=NONE) PMDF_MAILSHR

Then we grant the DISINMAIL identifier to the users that should not be able to
send mail.  They can still receive it, but they wouldn't be able to subscribe
to any lists so the volume here is minimal.  Whenever these users try to use
the IN% transport, they get the following message:

MAIL> send
To:     in%postmaster
%MAIL-E-ERRACTRNS, error activating transport IN
%LIB-E-ACTIMAGE, error activating image $1$DUA0:[PMDF.][EXE]IN_MAILSHR_V5.EXE;
-RMS-F-NOPRIV, no privilege for attempted operation


If these class accounts don't need NETMBX privilege for anything, you could
also try using the 'netmbx' option on the channel (if I am remembering this
correctly) and then anyone without that priv will not be able to queue mail to
the channel.

--------------------------------------------------------------------------
Joel D. Kraft           |  It's not quite the middle of nowhere...
System Manager          |               but you can see it from here...
Buena Vista College     |        I think it's called NEBRASKA!
--------------------------------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU