pvm_reg_tasker(3pvm) [debian man page]

REG_TASKER(3PVM)						  PVM Version 3.4						  REG_TASKER(3PVM)

NAME

       pvm_reg_tasker - Register task as PVM task starter.

SYNOPSIS

       C    #include <pvmsdpro.h>

	    int cc = pvm_reg_tasker()

       Fortran	 Not Available

DESCRIPTION

       Registers  the  calling	task  as  a  PVM  task starter.  When a tasker is registered with a pvmd, and the pvmd receives a DM_EXEC message,
       instead of fork()ing and exec()ing the task itself, it passes a message to the tasker, which does the dirty work and sends a  message  back
       to the pvmd.

       Note:  If this doesn't make sense, don't worry about it.  This function is for folks who are writing stuff like debugger servers and so on.
       For a more complete explanation of what's going on here, you should refer to the PVM source code and/or user guide section  on  implementa-
       tion; this is only a man page.  That said...

       When the pvmd receives a DM_EXEC message (request to exec new tasks), it searches epath (the PVM executable search path) for the file name.
       If it finds the file, it then either attempts to start the processes (using fork() and exec()) or, if a tasker has registered, sends  it  a
       SM_STTASK message.

       The format of the SM_STTASK message is:
	   int tid		 // of task
	   int flags		 // as passed to spawn()
	   string path		 // absolute path of the executable
	   int argc		 // number of args to process
	   string argv[argc]	 // args
	   int nenv		 // number of envars to pass to task
	   string env[nenv]	 // environment strings

       The  tasker must attempt to start the process when it gets one of these messages.  The tasker doesn't reply to the pvmd if the task is suc-
       cessfully started; the task will reconnect to the pvmd on its own, using the cookie in envar PVMEPID to identify itself to the pvmd.

       The tasker must send a SM_TASKX message to the pvmd when any task that it owns (has started) exits, or if it can't start a particular task.
       The format of the SM_TASKX message is:

	   int tid		 // of task
	   int status		 // the Unix exit status (from wait())
	   int u_sec		 // user time used by the task, seconds
	   int u_usec		 // microseconds
	   int s_sec		 // system time used by the task, seconds
	   int s_usec		 // microseconds

       The  tasker  task  must	use  pvm_setopt(PvmResvTids, 1) to allow sending reserved messages.  Messages should be packed using encoding Pvm-
       DataDefault to ensure they can be unpacked anywhere in the system.

       pvm_reg_tasker() returns PvmOk when successful.

SEE ALSO

       pvm_spawn(3PVM), pvm_tasks(3PVM),

								  16 March, 1994						  REG_TASKER(3PVM)

Check Out this Related Man Page

SEND(3PVM)							  PVM Version 3.4							SEND(3PVM)

NAME

       pvm_send - Immediately sends the data in the active message buffer.

SYNOPSIS

       C    int info = pvm_send( int tid, int msgtag )

       Fortran	 call pvmfsend( tid, msgtag, info )

PARAMETERS

       tid     Integer task identifier of destination process.

       msgtag  Integer message tag supplied by the user.  msgtag should be >= 0.

       info    Integer status code returned by the routine.

DESCRIPTION

       The  routine  pvm_send  sends a message stored in the active send buffer to the PVM process identified by tid.  msgtag is used to label the
       content of the message.	If pvm_send is successful, info will be 0. If some error occurs then info will be < 0.

       The pvm_send routine is asynchronous.  Computation on the sending processor resumes as soon as the message is safely  on  its  way  to  the
       receiving  processor.   This is in contrast to synchronous communication, during which computation on the sending processor halts until the
       matching receive is executed by the receiving processor.

       The PVM model guarantees the following about message order.  If task 1 sends message A to task 2, then task 1 sends message B  to  task	2,
       message	A will arrive at task 2 before message B.  Moreover, if both messages arrive before task 2 does a receive, then a wildcard receive
       will always return message A.

       Terminating a PVM task immediately after sending a message or messages from it may result in those messages being lost.	To be sure, always
       call pvm_exit() before stopping.

EXAMPLES

       C:
	    info = pvm_initsend( PvmDataDefault );
	    info = pvm_pkint( array, 10, 1 );
	    msgtag = 3 ;
	    info = pvm_send( tid, msgtag );

       Fortran:
	    CALL PVMFINITSEND(PVMRAW, INFO)
	    CALL PVMFPACK( REAL8, DATA, 100, 1, INFO )
	    CALL PVMFSEND( TID, 3, INFO )

ERRORS

       These error conditions can be returned by pvm_send

       PvmBadParam
	      giving an invalid tid or a msgtag.

       PvmSysErr
	      pvmd not responding.

       PvmNoBuf
	      no active send buffer. Try pvm_initsend() before send.

SEE ALSO

       pvm_initsend(3PVM), pvm_mcast(3PVM), pvm_pack(3PVM), pvm_psend(3PVM), pvm_recv(3PVM)

								  30 August, 1993							SEND(3PVM)

Linux and UNIX Man Pages

pvm_reg_tasker(3pvm) [debian man page]

Check Out this Related Man Page