Conference noted::hackers_v1

re Note 274.0 by NUWAVE::PARK

>    3.) find out if i have new mail from user 'z'
    
Can't help on 1 and 2, but 3 is a piece of cake.

In another note in this conference I provided a MAILFIX.BAS program.
It has all the basics for opening and reading both VMSMAIL.DAT as well
as MAIL.MAI.

You can easily modify it to check your mail file for newmail.

If you think you might move your mail file, open VMSMAIL first and find
out where it should be, then open MAIL.MAI

Otherwise you can hard code it, or use a logical.

I just spawned to find out which note number had MAILFIX in it,
BUT I CANT FIND IT!!!

I tried SEARCH "MAILFIX"
	DIR/AUTHOR=CANYON::OPERATOR
	DIR/AUTHOR=CANYON::HESTERMAN
but found nothing.

Hmmm...  Well you can send me VMSmail at CANYON::HESTERMAN and I will send
a copy to you.

Scott

Well, I found the correct syntax...

SEARCH /NOTES=200.0-274.* "MAILFIX"

This includes subtopics, not just the .0's

Oh well.

MAILFIX.BAS is located in note 256.15

Scott

SEARCH searches through topics and replies.
DIRECTORY only selects topics.

You probably wanted:

Notes> DIRECTORY 200.0-LAST /AUTH=CANYON::*
                    ^^ that a reply is specified implies looking at all replies

Yes, of course /AUTHOR accepts wildcards.

    
    For #2 you can try one of two things, both of which use the lexical
    F$GETSYI.
    
    You probably know that F$GETSYI has an item (CPU) which returns
    an integer (1 = 780, 2 = 750, 3 = 730, and probably more types too).
    
    However you can only use that item on the currently executing system.
    
    So if your target system has DECNET "TASK" still on it, you can
    try something like a remote task to tell you what CPU type it is.
    
    The only other way you might be able to look is through submitting
    a remote job so you are executing on the other system. Of course,
    we are assuming you have normal access to the system. All you really
    need to use is the F$GETSYI lexical, but if you care to write a
    program to extract more specific information you might check out
    the SYS$GETSYI system call which has an item called, interestingly
    enough, SYS$_CPU (8192), which will give you the system ID. The
    key is to make it execute on the remote node, of course. This is
    not terribly difficult if TASK is on the remote system. If TASK
    is not on the remote system, you need to be more creative, which
    I don't feel like getting right now. Hope this helps.
    
    -pjh
    
                                     

Try this:

	$ mail nl: star::sys$announce

If you have as much luck as I did, this will reveal that node STAR
is actually a VAX 8800.

In general, the hack here is that if you mail to NODE::SYSTEM-LOGICAL-NAME,
you tend to get back an error message saying "No such user - TEXT"
where TEXT is the translation of the logical name.

So, names like SYS$ANNOUNCE and SYS$WELCOME etc. tend to be revealing
of all sorts of things, what cpu type, what project etc.

/Eric

    Actually, STAR is a cluster alias. The node you happened to hit
    was an 8800.
    
	Jon

re .5

This has its uses

For example if you're out of the office for a week

$DEFINE/SYSTEM your_username "I_M_out_for_a_week"

or more interesting

$DEFINE/SYSTEM your_username "No_such_user"

Friends can be tipped off to send to _username, in which case the mail gets
through.

	    Eric's mentioned this hack before, and I've made this
	suggestion before:  Don't mail NL:, mail TT:.  If the logical
	you're looking for also happens to be a username, the user
	will end up getting a mail message.  Mailing TT: and aborting
	if it prompts for text can save you from having to explain
	your way out of something.
			<_Jym_>

    re: .0 (3.)
    
    I have a version of my CHECKMAIL procedure that gives the information
    you want;  either counts newmail by username or as is with check
    for mail from specified users.  (nice when awaiting for `that one
    reply'!)
    
    I can make this available, if interested send me mail.
    
    	\rik
            

    Rik's CHECKMAIL tool is available from the Toolshed.
    
    It is indeed *very* useful.  I recommend it.
    
    Walt

	    [RE .7]:  You could play nasty tricks like this.  Like if
	you want to hack J. Random User, you could do this:

		$ define/system USER HITLER

	That'll get some heads scratching.
			<_Jym_>