Start with vax90b1

# Fortran port

This is the port of bulleting to Linux but using Fortran.  It's

based on the decus/vax90b1 version.  This is likely close to what

I used.

(Editor's Note:  Sources are in the ZOO file BULL_SOURCE.ZOO)

The following are instructions for creating and installing the BULLETIN

utility. None of the command procedures included here are sophisticated, so it

is likely that several modifications will have to be made by the installer.

The installer should enable all privileges before installation.

Once installation is complete, it is suggested that the installer enter

BULLETIN and read HELP FOLDERS to see the options available when creating

or modifying folders.

One of the main uses of BULLETIN, besides storage of messages that are manually

entered by users, is storage of messages from network mailing lists.  This is

done by using the BBOARD feature, which is enabled using the SET BBOARD command

inside BULLETIN.  The alternative method is for mail messages to be written

directly by a mailing program by calling internal BULLETIN routines.  Such a

a program has been written for the popular mail utility PMDF.  If you wish to

do so for another utility, read the text file WRITEMSG.TXT.  I would be glad to

include any such programs with my distribution if you think such a program

would be of use to other users.

1) CREATE.COM

   This will compile and link the BULLETIN sources. Also, there are several

   INCLUDE files for the fortran sources (.INC files). BULLETIN will create it's

   data files in the directory pointed to by the logical name BULL_DIR.  If you

   elect not to use this definition, BULLFILES.INC should be modified.

   Note that after this procedure compiles the sources, it puts the objects

   into an object library, and then deletes all the OBJ files in the directory.

   NOTE 1: If you elect to have folders with the BBOARD feature that receives

   messages from outside networks, you may have to modify the subroutine

   which executes the RESPOND command.  That command sends messages to either

   the originator of the message or the mailing list associated with the

   folder.  These routines assume that one can simply use the VMS MAIL

   utility to do so.

   NOTE 2: The maximum number of folders for this distribution is 96 folders.

   If you wish to increase this, modify BULLUSER.INC and recompile the sources.

   When the new executable is run, it will create a new BULLUSER.DAT data file

   and rename the old one to BULLUSER.OLD.  You cannot reduce the number of

   folders.

   BULLETIN will work for both V4 & V5.  However, you will have to reassemble

   ALLMACS.MAR if you are upgrading from V5, i.e.

		$ MAC ALLMACS

		$ LIB BULL ALLMACS

		$ DELETE ALLMACS.OBJ;

		$ @BULLETIN.LNK

		$ COPY BULLETIN.EXE BULL_DIR:

		$ RUN SYS$SYSTEM:INSTALL

		BULL_DIR:BULLETIN/REPLACE

2) INSTALL.COM

   The following procedure copies the executable image to SYS$SYSTEM and

   installs it with certain privileges.  It also installs the necessary

   help files in SYS$HELP.  (BULLETIN help file is installed into the

   system help library HELPLIB.HLB.  If you don't wish this done, delete

   or modify the appropriate line in the procedure.  Also, the help

   library for the BULLETIN program, BULL.HLB, can be moved to a different

   directory other than SYS$HELP.  If this is done, the system logical name

   BULL_HELP should be defined to be the directory where the library is

   to be found.)

3) LOGIN.COM

   This contains the commands that should be executed at login time

   by SYS$MANAGER:SYLOGIN.COM.  It defines the BULLETIN commands.

   It also executes the command BULLETIN/LOGIN in order to notify

   the user of new messages.  NOTE: If you wish the utility to be a

   different name than BULLETIN, you should modify this procedure.

   The prompt which the utility uses is named after image executable.

   If you want messages displayed upon logging in starting from

   oldest to newest (rather than newest to oldest), add /REVERSE to

   the BULLETIN/LOGIN command.  Note that users with the DISMAIL

   flag setting in the authorization file will not be notified of

   new messages.  See help on the SET LOGIN command within the BULLETIN

   utility for more information on this.  Also, please note that when

   a brand new user to the system logins, to avoid overwhelming the new

   user with lots of messages, only PERMANENT SYSTEM messages are displayed.

   If you want SYSTEM messages, i.e. messages which are displayed in full

   when logging in, to be continually displayed for a period of time rather

   than just once, you should add the /SYSTEM= qualifier.  This is documented

   in BULLETIN.HLP, although there it is referred to only with respect to

   a user wanting to review system messages.  It can be added with /LOGIN.

4) BULLSTART.COM

   This procedure contains the commands that should be executed after

   a system startup.  It should be executed by SYS$MANAGER:SYSTARTUP.COM.

   It installs the BULLETIN utility with correct privileges.  It also

   includes the command BULLETIN/STARTUP.  This starts up a detached process

   with the name BULLCP.  It periodically check for expire messages, cleanup

   empty space in files, and converts BBOARD mail to messages.  It also allows

   other DECNET nodes to share it's folders.  If you don't want this feature

   and don't plan on having multiple folders or make use of BBOARD, you could

   eliminate this command if you like.  However, it is highly recommended that

   you create this process to avoid extra overhead when users login.  NOTE:

   BULLCP normally is created so it is owned by the DECNET account.  If that

   account does not exist, BULLCP will be owned by the account that issues

   the BULLETIN/START command.  In that case, access via other DECNET nodes

   will not be available.

   If you are installing BULLETIN on a cluster and plan to have the bulletin

   files be shared between all of the cluster nodes, you only need to have

   this process running on one node. On all other nodes, the system logical

   name BULL_BULLCP should be defined (to anything you want) so as to notify

   BULLETIN that BULLCP is running. (On the local node where BULLCP is running,

   this logical name is automatically defined.)

   The use of the MARK command to mark messages require that a file be

   created for each user which saves the marked info.  That file file is

   stored in the directory pointed to by the logical name BULL_MARK.  You can

   either let users who want to use this command define it themselves, or

   you can define it for them, i.e. DEFINE/SYSTEM BULL_MARK SYS$LOGIN.

5) INSTRUCT.COM

   This procedure adds 2 permanent messages which give a very brief

   description about the BULLETIN utility, and how to turn off optional

   prompting of non-system messages (via SET NOREADNEW).

6) BOARD_SPECIAL.COM

   This command procedure describes and illustrates how to use the

   SET BBOARD/SPECIAL feature.  This feature allows the use of BBOARD

   where the input does not come from VMS MAIL.  For example, this could

   be used in the case where mail from a non-DEC network is not stored

   in the VMS MAIL.  Another example is BOARD_DIGEST.COM.  This file

   takes mail messages from "digest" type mailing lists and splits them

   into separate BULLETIN messages for easier reading.

   To use this feature, place the special command procedure into the

   bulletin file directory using the name BOARD_SPECIAL.COM.  If you want

   to have several different special procedure, you should name the command

   procedure after the username specified by the SET BBOARD command.

7) INSTALL_REMOTE.COM

   This procedure, in conjunction with REMOTE.COM and DCLREMOTE.COM allows

   a user to install new versions of BULLETIN on several DECNET nodes from

   a single node, rather than having to login to each node.  This is

   especially useful when a new version modifies the format of one of the

   data file.  Older versions of BULLETIN will not run with newer formats

   and will either issue error statements when run, or may cause major

   problems by attempting to change the files back to the old format.

   (NOTE: Don't attempt to use this if different nodes are running

   different versions of VMS, i.e. V4 and V5, as they require different

   linked executables.)

8) MASTER.COM

   If you are using PMDF, and want to use the BBOARD option, a set of

   routines are included which will allow PMDF to write message directly

   into folders, which is a much more effecient way of doing it than

   the normal BBOARD method of using VMS MAIL.  Read PMDF.TXT for how

   to do this.

9) BULLETIN.COM

   If one wants BULLETIN to be able to send messages to other DECNET

   node's GENERAL folder, but wants to avoid running the process created

   by BULLETIN/STARTUP on this node, another method exists.  This is the

   "older" (and slower) method.  BULLETIN.COM must be put in each node's

   DECNET default user's directory (usually [DECNET]).  Once this is done,

   the /NODE qualifier for the ADD & DELETE commands can be used.

   The object BULLETIN pointing to BULLETIN.COM must be added to the NCP

   database, i.e. the command

	MCR NCP SET OBJ BULLETIN FILE directory:BULLETIN.COM number 0

   must be executed at startup time on the remote node.

   NOTE:  Privileged functions such as /SYSTEM will work on other nodes

   if you have an account on the other node with appropriate privileges.

(Editor's Note:  Sources are in the ZOO file BULL_SOURCE.ZOO)

               Introduction to BULLETIN on the Vax

                                                  2/88 AW

PUBLISHED BY THE DREW UNIVERSITY ACADEMIC COMPUTER CENTER. MAY BE

COPIED WITH WRITING CREDIT GIVEN TO DREW UNIVERSITY.

BULLETIN was written for the Public Domain by Mark London at MIT.

     The BULLETIN utility permits a user to create messages for

reading by other users.  Users may be notified upon logging on

that new messages have been added, and what the topic of the

messages are.  Actual reading of the messages is optional.  (See

the command SET READNEW for info on automatic reading.)  Messages

are automatically deleted when their expiration data has passed.

     The program runs like VAX mail.  The different interest

groups or BULLETIN boards are implemented in the form of

'Folders', just like a filing cabinet.  A Folder contain various

messages on the same general topic.  A message is a piece of text

written by a user or staff person and added to a particular

folder.  All users are not permitted to submit messages to all

folders.

     A message consists of an expiration date, a subject line

and the text of the message.  BULLETIN will prompt the user for

these things when a message is being added.

     Several different folders are currently defined to

BULLETIN.  The General Folders will be used by Computer Center

Staff to post messages of general interest concerning the VAX to

the user community.  If something is of an important nature, it

will be posted in the General folder as a 'System' message.

This is a special message type.  It will be displayed to each

user  as they log in the first time after that message was

posted.  This will be done automatically by BULLETIN on login.

Once a particular system message has been displayed, it will not

be displayed for that user on subsequent logins.

Folders

     Different folders have been created to contain messages on

different topics.  Folders may be public, semi-private, or

private.  The majority of the folders will be public.  However a

few will be semi-private, which will mean that all users may

read messages in the folder but not all will be able to post to

it.  

Using BULLETIN

     BULLETIN is invoked by type the command 'BULLETIN' (or BULL,

for short) at the '$' prompt.  BULLETIN will display its prompt

'BULLETIN>'. Help is available from DCL command level ($) or from

within the BULLETIN program itself by typing the word 'HELP'.  To

leave the BULLETIN program, type 'EXIT'.

To see what is there

     In order to see message and folders, on can use the

'Directory' command. Upon entering BULLETIN, the user is place

in the General folder.  If the user wishes to see which folders

exist, the directory/folders command is used. for example:

typing:

     BULLETIN> directory/folders

will make a display like:

      Folder                       Owner

     *GENERAL                      SYSTEM

     *PUBLIC_ANNOUNCEMENTS         BBEYER

      NETMONTH                     BITNET

     *VAX_SIG                      BBEYER

An asterisk (*) next to the folder name indicates you have unread

messages in that folder.

The command 'DIRECTORY/FOLDERS/DESCRIBE' would list all available

folders, along with a brief description of each.

     To switch from one folder to another folder, the user may

execute the 'SELECT' command.  For example, the following

command would show what a user would do to switch to the folder

called PUBLIC_ANNOUNCEMENTS:

BULLETIN> SELECT PUBLIC_ANNOUNCEMENTS

and BULLETIN would respond:

     Folder has been set to PUBLIC_ANNOUNCEMENTS

     Now the user may get a list of the messages in this folder

by issuing the directory command with no qualifiers.

This command, for example:

BULLETIN> DIRECTORY

would have bulletin respond:

 #     Description               From                  Date

 1     CHRISTMAS PARTY           oleksiak              26-JUN-88

 2     Learning about BULLETIN   oleksiak              26-JUN-87

 3     VAX MAIL                  LLLOYD                01-Jan-87

     The command 'DIR/NEW' will list just unread messages.

Reading messages

     In order to read messages in a folder, the user may type

the read command or he/she may simply type the number of the

message he wishes to read.  The message numbers can be acquired

by doing the 'DIRECTORY' command.  If the user hits a carriage

return with no input whatsoever,  BULLETIN will type the first

message in the folder, or if there are new messages present, it

will type the first new message in the folder.

     If a folder contains the above messages (as seen by the

'Directory' command) then these messages can be read by:

BULLETIN> READ

and BULLETIN would respond:

Message number:  1                       PUBLIC_ANNOUNCEMENTS

Description: CHRISTMAS PARTY

Date:  26-JUN-1988 8:08:40   Expires:  1-JAN-1989 08:08:40

...Body of message.....

     Should the user only wish to see message number 3, he can

enter the 'READ' command with the message number as a parameter.

for example:

BULLETIN> READ 3

     There are three other useful commands that can be used at

the 'BULLETIN>' prompt when reading messages. These are:

BACK - Read the message preceding the message currently being

read.

CURRENT - Start reading the current message at the top.  This is

useful for someone who is reading a message and wishes to reread

it from the beginning.

NEXT - Start reading from the beginning of the next message.

This is handy if the user is reading a very long message and

wants to skip to the next one.

Saving the interesting stuff.

     If the user sees something which he/she wants a copy of,

the extract command can be use to write an ASCII copy of the

message into a file.  This command works on the current message

being read.  It requires the name of the file into which to save

the message.  If the file name is not given, the user will be

prompted for it.  For example:

BULLETIN>  Read 2

********** Message on Screen ********

A person could then type

BULLETIN> extract

file:  FV.TXT

BULLETIN>

BULLETIN has now saved the contents of message number 2 into the

file name 'FV.txt'.

     If the file to which the user is writing already exists,

BULLETIN will append the message to the file.  The user can

force BULLETIN to write a new file containing only the message

being saved by using the '/new' qualifier in the 'extract'

command.  These messages can then be sent to other users, or

downloaded for use in Wordperfect.  (See "Mail on the Vax", or

"Transferring a file between a PC and the VAX").

This command may be useful if you wish to transfer the message to

your PC, perhaps using a BITNET journal message as a reference in

a paper. Once the file is saved, you can transfer it to a PC by

following the instructions in the handout 'Transferring files

from the PC to the VAX of from the VAX to a PC".

Adding messages

     A user may add a message to a folder by selecting the

folder and then using the 'ADD' command.  This is provided that

the user is adding the message to a public folder.  The user has

the option of giving the 'ADD' command and typing a message using

the VAX editor or uploading a message from your PC (see

documentation), or add a message you have extracted from VAX

mail.  BULLETIN will prompt for the expiration date and subject

line.  It will then add the text of the file as the body of the

message. To add a message that is stored in a file (from MAIL or

from your PC, for example) type:

          ADD filename

If the user does not specify a file name, he/she will be

prompted to enter the body of the message.  The user may also

use the EDT text editor by issuing the command with the

'/EDIT'option.

For example:

BULLETIN> sel PUBLIC_ANNOUNCEMENTS

          folder has been set to PUBLIC_ANNOUNCEMENTS

BULLETIN> ADD MESS.TXT

IT IS 10-JUL-1988 12:41:06.15.  SPECIFY WHEN THE MESSAGE SHOULDo

EXPIRE:  ENTER ABsolute TIME:  <DD-MMM-YYYY]HH:MM:SS OR DELTA 

TIME: DDD HH:MM:SS

A user then type the date of expiration and press the 'return'

button.  The time input may be ignored. For example, typing:

20-JUL-1988 or type "10" - for ten days in the future.

BULLETIN responds:

ENTER DESCRIPTION HEADER.  LIMIT HEADER TO 53 CHARACTERS.L

Now the user may enter the subject of the message.

BULLETIN>e

The above session adds the text in the file 'mess.txt' as theo

next message in the PUBLIC_ANNOUNCEMENTS Folder.  The messageo

will be deleted automatically on the 20th of July as requested

by the user adding the message.D

Asking BULLETIN to notify you of new messages upon logging in.

     If the user wishes to get notification on login when newr

messages are in a folder, he should use the 'READNEW' option.b

This command does not force the reader to reading new messages,n

only gives notification.  To do this, 'SELECT' each folder you

are interested in and do a 'SET READNEW' command while set tos

that folder.

Example:

BULLETIN> Select PUBLIC_ANNOUNCEMENTSp

folder has been set to PUBLIC_ANNOUNCEMENTS

BULLETIN> SET READNEWt

Alternately, you may type SET SHOWNEW. This will just display ag

message notifying you that there are new messages.

Mailing a BULLETIN message

     A user may directly mail another user a message found in theT

BULLETIN.  While reading the message that he/she desires to send,p

at the 'BULLETIN>' type 'MAIL'.  The Vax will then ask to whom

you wish to send the information too.r

Check the BULLETIN DISCUSSION folder on ALPHA for new additions.

If you have comments or questions about BULLETIN, leave them

there.

$!

$! BOARD_DIGEST.COM

$!

$! Command file invoked by folder associated with a BBOARD which is

$! is specified with /SPECIAL.  It will convert "digest" mail and

$! split it into separate messages.  This type of mail is used in

$! certain Arpanet mailing lists, such as TEXHAX and INFO-MAC.

$!

$ FF[0,8] = 12			! Define a form feed character

$ SET PROTECT=(W:RWED)/DEFAULT

$ SET PROC/PRIV=SYSPRV

$ USER := 'F$GETJPI("","USERNAME")

$ EXTRACT_FILE = "BULL_DIR:" + "''USER'" + ".TXT"

$ DEFINE/USER EXTRACT_FILE BULL_DIR:'USER'

$ MAIL

READ

EXTRACT EXTRACT_FILE

DELETE

$ OPEN/READ INPUT 'EXTRACT_FILE'

$ OPEN/WRITE OUTPUT 'EXTRACT_FILE'

$ READ INPUT FROM_USER

$AGAIN:

$ READ/END=ERROR INPUT BUFFER

$ IF F$EXTRACT(0,3,BUFFER) .NES. "To:" THEN GOTO SKIP

$ USER = F$EXTRACT(4,F$LEN(BUFFER),BUFFER)

$ GOTO AGAIN1

$SKIP:

$ IF F$EXTRACT(0,15,BUFFER) .NES. "---------------" THEN GOTO AGAIN

$AGAIN1:

$ READ/END=ERROR INPUT BUFFER

$ IF F$EXTRACT(0,15,BUFFER) .NES. "---------------" THEN GOTO AGAIN1

$ FROM = " "

$ SUBJ = " "

$NEXT:

$ READ/END=EXIT INPUT BUFFER

$FROM:

$ IF F$EXTRACT(0,5,BUFFER) .NES. "From:" THEN GOTO SUBJECT

$ FROM = BUFFER 

$ GOTO NEXT

$SUBJECT:

$ IF F$EXTRACT(0,8,BUFFER) .NES. "Subject:" THEN GOTO NEXT

$ SUBJ = BUFFER - "Subject:"

$F2:

$ IF F$LENGTH(SUBJ) .EQ. 0 THEN GOTO WRITE

$ IF F$EXTRACT(0,1,SUBJ) .NES. " " THEN GOTO WRITE

$ SUBJ = F$EXTRACT(1,F$LENGTH(SUBJ),SUBJ)

$ GOTO F2

$WRITE:

$ WRITE OUTPUT FROM_USER

				! Write From: + TAB + USERNAME

$ WRITE OUTPUT "To:	" + USER

				! Write To: + TAB + BBOARDUSERNAME

$ WRITE OUTPUT "Subj:	" + SUBJ

				! Write Subject: + TAB + mail subject

$ WRITE OUTPUT ""		! Write one blank line

$ IF FROM .NES. " " THEN WRITE OUTPUT FROM

$READ:

$ READ/END=EXIT/ERR=EXIT INPUT BUFFER

$ IF F$EXTRACT(0,15,BUFFER) .EQS. "---------------" THEN GOTO READ1

$ WRITE OUTPUT BUFFER

$ GOTO READ

$READ1:

$ READ/END=EXIT/ERR=EXIT INPUT BUFFER

$ IF F$LOCATE(":",BUFFER) .EQ. F$LENGTH(BUFFER) THEN GOTO READ1

$ WRITE OUTPUT FF

$ FROM = " "

$ SUBJ = " "

$ GOTO FROM

$EXIT:

$ CLOSE INPUT

$ CLOSE OUTPUT

$ PUR 'EXTRACT_FILE'

$ EXIT

$ERROR:

$ CLOSE INPUT

$ CLOSE OUTPUT

$ DELETE 'EXTRACT_FILE';