Conference vaxaxp::vmsnotes

112.0. "SET PROCESS/AFFINITY ?" by POMPY::LESLIE ([email protected]) Thu Jan 30 1997 09:57

    I've tried to use the documented SET PROC/AFFINITY command and get
    
%DCL-W-IVQUAL, unrecognized qualifier - check validity, spelling, and placement
 \AFFINITY\
    
    Does it not apply to VAX OpenVMS 7.1? If so, why am I gettiong errors
    messages?
    
    /a
    
$ show cpu/full reveals
    
POMPY, a VAX 6000-440
Multiprocessing is ENABLED. Streamlined synchronization image loaded.
    
PRIMARY CPU = 01
    
CPU 01 is in RUN state
Current Process: *** None ***
Revision levels:  Pchip microcode = 5, RSSC = 0.0, XCA rev = 1.
    KA64A module revision =  K05, module serial number = GA02058663.
    Compatibility group = 2.  System serial number = 02100612.
Capabilities of this CPU:
	PRIMARY QUORUM RUN 
Processes which can only execute on this CPU:
	CONFIGURE        PID = 00000206  Reason: PRIMARY Capability
    
CPU 02 is in RUN state
Current Process: *** None ***
Revision levels:  Pchip microcode = 6, RSSC = 0.0, XCA rev = 1.
    KA64A module revision = AL05, module serial number = GA01158176.
    Compatibility group = 2.  System serial number = 02100612.
Capabilities of this CPU:
	QUORUM RUN 
Processes which can only execute on this CPU:
        *** None ***
    
CPU 03 is in RUN state
Current Process: *** None ***
Revision levels:  Pchip microcode = 6, RSSC = 0.0, XCA rev = 1.
    KA64A module revision = AL05, module serial number = GA00457831.
    Compatibility group = 2.  System serial number = 02100612.
Capabilities of this CPU:
	QUORUM RUN 
Processes which can only execute on this CPU:
        *** None ***
    
CPU 04 is in RUN state
Current Process: *** None ***
Revision levels:  Pchip microcode = 6, RSSC = 0.0, XCA rev = 1.
    KA64A module revision = AM05, module serial number = GA00858027.
    Compatibility group = 2.  System serial number = 02100612.
Capabilities of this CPU:
	QUORUM RUN 
Processes which can only execute on this CPU:
        *** None ***
    _________________________________________________________________________
    $ HELP SET PROC/AFF says


SET

  PROCESS

    /AFFINITY

          /AFFINITY
          /NOAFFINITY

       Allows bits in the kernel thread affinity mask to be set or
       cleared individually, in groups, or all at once. This qualifier
       is mutually exclusive with the /CAPABILITY qualifier.

                                      NOTE

          The SET PROCESS/[NO]AFFINITY command will fail if none of
          the specified CPUs has the capabilities required by the
          process.

       The /NOAFFINITY qualifier clears all affinity bits currently set
       in the current or permanent affinity masks, based on the setting
       of the /PERMANENT qualifier. Specifying the /AFFINITY qualifier
       has no direct effect, but merely indicates the target of the
       operations specified by the following secondary parameters:

                  Sets affinity for currently active CPUs defined by the
       /SET=(n[,..CPU IDs n, where n has the range of 0 to 31.
                  Clears affinity for currently active CPUs defined by
       /CLEAR=(n[,the]position values n, where n has the range of 0 to
                  31.
                  Performs the operation on the permanent affinity
       /PERMANENT mask as well as the current affinity mask, making the
                  changes valid for the life of the kernel thread. (The
                  default behavior is to affect only the affinity mask
                  for the running image.)

       The secondary qualifiers can all be used at once as long as the
       affinity bits defined in the /SET and /CLEAR parameters do not
       overlap.

       The privileges required to execute the SET PROCESS/AFFINITY
       command match those required by the $PROCESS_AFFINITY system
       service. ALTPRI is the base privilege required to make any
       modifications, and the only privilege required to modify the
       current owner's kernel thread. Modifications within the same UIC
       group require GROUP privilege. Modifications to any unrelated
       kernel thread require WORLD privilege.

       As with the other SET PROCESS qualifiers, the bit operations
       occur on the current process if no /IDENTIFICATION qualifier
       or explicit process name parameter is specified. Specifying a
       process name does not imply that all kernel threads associated
       with the process are affected; the SET PROCESS command affects
       only the initial kernel thread of a multithreaded process.
     
      ...and the DCL dictionary says nothing more useful.

    This is an Alpha only feature. The system service documentation states
    that, unfortunately none of the DCL documentation does.

    d.

    \Bloody marvellous. I was sort of counting on using this to get around
    a bug in an application.
    
    Next time anyone goes near the DOC QAR database, please drop it in. I'm
    a tad busy with two weeks to go before I depart (again).

    I'll cross-post to DOCNOTES.