Here is a message from Lee Hirz, one of the former Mailman developers:

Mailman sends and receives messages locally in 2 ways.  One method is to can send and receive messages as soon as the user hits the return on the  SEND command. Because MailMan is configured to run according to a standard in VistA, this way is only available if a programmer goes into the code and makes a couple of changes, but it is the best way to run MailMan in a small hospital... because operations are much simpler.

I don't have the code in from of me, but you can recognize it because in order to "queue" messages for delivery by "filers" that are started by TaskMan, there has be be a record inserted into the queue.  There is a transfer of control (GOTO) or a QUIT right after that, but below that, if the code hasn't changed a lot, will be the code that does the delivery and is even called by the filers.  Basically, all that needs to be done is to remove the transfer of control and set a couple of variables.

The second method uses a background filer that must be started by TaskMan.  In either case the Postmaster is just like any other user and can send and receive messages.

MailMan sends message across the network only using TaskMan tasks.


Greg Woodhouse wrote:
The submananagers are the proceses that actually do the work (the
thread pool, if you will). It Taskman goes long enough without any work
to do, th submanagers will shut down anyway. But the manager will
always start submanagers when they are needed. Off the top of my head,
I'm not sure if submanagers will still pick up tasks if Taskman is in a
wait state.

Does anyone know?

--- Kevin Toppenberg <[EMAIL PROTECTED]> wrote:

  
OK Nick,

When I use the menu system to call XUTM WAIT, it asks
if submanagers should be shut down (I answered NO). 
It then says: Done.  I then do option XUTM ZTMON, and
it does not show taskman in a wait state.  Perhaps
because I didn't stop the submanagers...

Don't worry about answering this.  All's well that
ends well.

Thanks
Kevin

--- Nick James <[EMAIL PROTECTED]> wrote:

    
The output of D ^ZTMON will show the submanagers as
in
waiting state.
Bye
Nick

--- Kevin Toppenberg <[EMAIL PROTECTED]> wrote:

      
Nick,

I just played with putting my Taskman into and
        
then
      
back out of the wait state.

I couldn't immediately tell that it was in the
        
wait
      
state.  How did you tell it was stuck in wait?

Thanks
Kevin

--- Nick James <[EMAIL PROTECTED]> wrote:

        
Hi 
Finally I found the culprit.
Actually the Taskman was in WAIT state. As soon
          
as
      
I
        
changed the state, all the messages reached
          
their
      
corresponding recipients.
Bye
Nick
--- "Nancy E. Anthracite"
          
<[EMAIL PROTECTED]>
        
wrote:

          
My guess it that you didn't have any problems
            
only
        
because you put UCI in all 
the places that needed UCI and VOL in all of
            
the
      
places that needed VOL.  Had 
you called whatever was in UCI in the VistA
            
you
      
started with, and VOL what 
was in the VOL, you would have had to have
            
changed
        
it in fewer places.  I  
think the key is always with D GETENV^%ZOSV
            
and
      
then
          
setting all of the 
parameters correctly with NO TYPOS and all
            
that
      
good
          
stuff the first time 
around.  At the risk of being a broken record,
            
that
          
happens to be broken in 
the same place as Lloyd's record that broke
            
from
      
all
          
the times he used it to 
tell me to do this ...

VISTA>D GETENV^%ZOSV
 
VISTA>W  Y

Which give you in the output in the respective
places:

UCI^VOL^NODE^BOX:VOLUME 

This is actually written right into VistA at
            
one
      
of
          
the ?? points, although I 
don't recall which one.

Although I have not done configuration, I sure
            
have
          
had lots of chances to 
help people with installations, and this is
            
where
        
all of the problems are.  
Lloyd knows it so well, he can even tell by
            
the
      
error message where the typos 
are.  Now that is what I call "experienced"!

On Saturday 29 January 2005 04:26 pm, Kevin
Toppenberg wrote:
            
For what it is worth, it seems that most of
              
the
        
problems that I have hear people talk about
              
on
      
this
            
board in regards to taskman, is a problem
              
with
      
the
          
VOL,UCI etc. issue.  Most recommend using
              
the
      
defaults
            
provided by the system, but it seems that
              
this
      
leads
            
poeple to problems.  I cleared out all the
              
other
        
entries, and called my UCI "UCI", and called
              
my
        
VOL,
            
"VOL".  It seems like I haven't had the
              
problems
        
that
            
others have...

Kevin

--- Nick James <[EMAIL PROTECTED]> wrote:
              
Hi
The CPRS problem was due to the change in
                
file
        
access
rights. That has been solved. But the
                
"Waiting
        
for a
            
partition" problem, does not seem to be
                
over
      
yet.
            
Nick

--- Kevin Toppenberg <[EMAIL PROTECTED]>
                
wrote:
        
Nick,

Do you have a way to make your server
                  
accessible
            
on

                
the internet for someone else to poke
                  
around
        
on?
            
I'd be willing to look at it for a
                  
couple
      
of
        
minutes

                
if you want to contact me off-board.

I'm self taught, so no promises as to
                  
whether
          
or
            
not

                
I
can get you up.

Kevin
[EMAIL PROTECTED]

--- Nick James <[EMAIL PROTECTED]>
                  
wrote:
        
Hi
I was able to overcome the previous
                    
problem
          
with
            
the

                  
command  GO^XMKPLQ and GO^XMTDT, to
                    
run
      
the "MOVER" and "TICKLER".
But still I was unable to send and
                    
receive
        
messages.

                  
So I just checked to see the tasks

running in TASKMAN, whose screen shot
                    
I
      
am
        
giving

                
below :

510: ^LRCAPPH, COLLECT PHLEBOTOMY CAP
                    
WORKLOAD.
            
No

                  
device.  VAH,ROU.
     From 1/24/2005 at 18:14,  By you.
                    
      
=== message truncated ===



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive
Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF,
etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

    


=====
A practical man is a man who practices the errors of his forefathers. --Benjamin Disraeli
====
Greg Woodhouse 
[EMAIL PROTECTED] 
[EMAIL PROTECTED] 





-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

  

-- 
Greg Kreis      http://www.PioneerDataSys.com

"You are today where your thoughts have brought you, you will
   be tomorrow where your thoughts take you." (James Lane Allen)

Reply via email to