pvmfarchcode(3pvm) [debian man page]

ARCHCODE(3PVM)							  PVM Version 3.4						    ARCHCODE(3PVM)

NAME

       pvm_archcode - Returns the data representation code for a PVM architecture name.

SYNOPSIS

       C    int cod = pvm_archcode( char *arch )

       Fortran	 call pvmfarchcode( arch, cod )

PARAMETERS

       arch    Character string containing the architecture name.

       cod     Integer returning architecture code.

DESCRIPTION

       The  routine pvm_archcode returns an integer given an architecture name.  The code returned identifies machines with compatible binary data
       formats.  For example, SUN4 and RS6K have the same code, while ALPHA has a different one (because a few datatypes  have	different  sizes).
       This  lets  you	know  when you can get away with using PvmDataRaw instead of PvmDataDefault encoding to pass messages between tasks on two
       machines.

       Naturally, you shouldn't assume the values returned by pvm_archcode are etched in stone; the numbers have no intrinsic meaning except  that
       if two different arch names map to the same value then they're compatible.

       This  routine  is  actually  obsolete  in  the sense that the architecture codes returned are already available in the hi_dsig field of the
       pvmhostinfo structure returned by pvm_config(), as shown in the below example.  The routine is maintained for backwards compatibility only.

EXAMPLES

       C:
	    struct pvmhostinfo *hip;
	    int i;

	    pvm_config((int *)0, (int *)0, &hip);
	    i = pvm_archcode(hip[0].hi_arch);

	    /* or you could just do:  i = hip[0].hi_dsig;  */

       Fortran:
	    CALL PVMFARCHCODE( 'RS6K', k )

ERRORS

       On success, pvm_archcode returns a positive integer data signature.

       The following error conditions can be returned as well:

       PvmBadParam
	      giving an invalid architecture name.

       PvmNotFound
	      there is no host with the given architecture name in the current virtual machine configuration.

       PvmSysErr
	      pvmd not responding.

SEE ALSO

       pvm_config(3PVM), pvm_initsend(3PVM), pvm_notify(3PVM), pvm_tasks(3PVM), pvm_tidtohost(3PVM)

								  15 March, 1994						    ARCHCODE(3PVM)

REG_RM(3PVM)							  PVM Version 3.4						      REG_RM(3PVM)

NAME

       pvm_reg_rm - Register task as PVM resource manager.

SYNOPSIS

       C    #include <pvmsdpro.h>

	    int cc = pvm_reg_rm( struct pvmhostinfo **hip )
	    struct pvmhostinfo {
		 int  hi_tid;
		 char *hi_name;
		 char *hi_arch;
		 int  hi_speed;
	    };

       Fortran	 Not Available

PARAMETERS

       hostp  Returns pointer to a pvmhostinfo structure which contains information about the master host.

DESCRIPTION

       Registers  the  calling task as a PVM task and slave host manager.  This means it intercepts certain libpvm calls from other tasks in order
       to have a say in scheduling policy.  The resource manager will asynchronously receive messages from tasks containing requests for  service,
       as well as messages from pvmds notifying it of system failures.

       Before  you  start using this function, be warned that it's not a trivial thing, i.e. you can't just call it to turn off the default round-
       robin task assignment.  Rather, it allows you to write your own resource manager and hook it to PVM.

       To understand what the following messages mean, you should refer to the PVM source  code  and/or  user  guide  section  on  implementation;
       There's just too much to say about them.

       When one of the following libpvm functions is called in a task with resource manager set, the given message tag is sent to to resource man-
       ager.

	   Libpvm call		 RM message	   Normal message
	   pvm_addhosts()	 SM_ADDHOST	   TM_ADDHOST
	   pvm_config() 	 SM_CONFIG	   TM_CONFIG
	   pvm_delhosts()	 SM_DELHOST	   TM_DELHOST
	   pvm_notify() 	 SM_NOTIFY	   TM_NOTIFY
	   pvm_spawn()		 SM_SPAWN	   TM_SPAWN
	   pvm_tasks()		 SM_TASK	   TM_TASK
	   pvm_reg_rm() 	 SM_SCHED	   TM_SCHED

       The resource manager must in turn compose the following messages and send them to the pvmds:

	   RM message	     Normal message
	   SM_EXEC	     DM_EXEC
	   SM_EXECACK	     DM_EXECACK
	   SM_ADD	     DM_ADD
	   SM_ADDACK	     DM_ADDACK
	   SM_HANDOFF	     (none - change of resource manager)

       The following messages are sent asynchronously to the resource manager by the system:

	   RM message	     Meaning
	   SM_TASKX	     notify of task exit/fail
	   SM_HOSTX	     notify of host delete/fail

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

       pvm_reg_rm() returns PvmOk when successful.

SEE ALSO

       pvm_addhosts(3PVM), pvm_config(3PVM), pvm_delhosts(3PVM), pvm_notify(3PVM), pvm_spawn(3PVM), pvm_tasks(3PVM)

								   4 March, 1994						      REG_RM(3PVM)