pvm_mcast(3pvm) [debian man page]

MCAST(3PVM)							  PVM Version 3.4						       MCAST(3PVM)

NAME

       pvm_mcast - Multicasts the data in the active message buffer to a set of tasks.

SYNOPSIS

       C    int info = pvm_mcast( int *tids, int ntask, int msgtag )

       Fortran	 call pvmfmcast( ntask, tids, msgtag, info )

PARAMETERS

       ntask   Integer specifying the number of tasks to be sent to.

       tids    Integer array of length ntask containing the task IDs of the tasks to be sent to.

       msgtag  Integer	message  tag  supplied by the user.  msgtag should be >= 0.  It allows the user's program to distinguish between different
	       kinds of messages .

       info    Integer status code returned by the routine.  Values less than zero indicate an error.

DESCRIPTION

       The routine pvm_mcast multicasts a message stored in the active send buffer to ntask tasks specified in the tids array.	The message is not
       sent  to  the caller even if listed in the array of tids.  The content of the message can be distinguished by msgtag.  If pvm_mcast is suc-
       cessful, info will be 0. If some error occurs then info will be < 0.

       The receiving processes can call either pvm_recv or pvm_nrecv to receive their copy of the multicast.  pvm_mcast is asynchronous and  based
       on  a  minimum spanning tree algorithm between the pvmds.  Computation on the sending processor resumes as soon as the message is safely on
       its way to the receiving processors.  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.

       pvm_mcast  first determines which other pvmds contain the specified tasks.  Then passes the message to these pvmds which in turn distribute
       the message to their local tasks without further network traffic.

       Multicasting is not supported by most multiprocessor vendors.  Typically their native calls only support broadcasting to {m all the user's
       processes  on  a  multiprocessor.  Because of this omission, pvm_mcast may not be an efficient communication method on some multiprocessors
       except in the special case of broadcasting to all PVM processes.

EXAMPLES

       C:
	    info = pvm_initsend( PvmDataRaw );
	    info = pvm_pkint( array, 10, 1 );
	    msgtag = 5 ;
	    info = pvm_mcast( tids, ntask, msgtag );

       Fortran:
	    CALL PVMFINITSEND(PVMDEFAULT)
	    CALL PVMFPACK( REAL4, DATA, 100, 1, INFO )
	    CALL PVMFMCAST( NPROC, TIDS, 5, INFO )

ERRORS

       These error conditions can be returned by pvm_mcast

       PvmBadParam
	      giving a msgtag < 0.

       PvmSysErr
	      pvmd not responding.

       PvmNoBuf
	      no send buffer.

SEE ALSO

       pvm_psend(3PVM), pvm_recv(3PVM), pvm_send(3PVM)

								  30 August, 1993						       MCAST(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_mcast(3pvm) [debian man page]

Check Out this Related Man Page