Jump to content

SMPV211 - The Single Processor Utility Program: Difference between revisions

From EDM2
Created page with "{{SMPV211}} As explained previously, some applications written for uniprocessor OS/2 may experience problems running under OS/2 for SMP V2.11 because they rely upon priorities between threads for accessing shared resources, or use the CLI/STI method for protecting resources like semaphores or memory. These types of application are called MP-safe. These programs will still run fine under OS/2 for SMP V2.11 if they are run in a uniprocessor mode. The EXECMODE program is a..."
 
Ak120 (talk | contribs)
mNo edit summary
 
Line 5: Line 5:


The syntax for the EXECMODE utility program is as follows:
The syntax for the EXECMODE utility program is as follows:
  execmode (options)[d:[\[path\]]]filenam1.ext( options) [filenam2.ext]...
  execmode (options)[d:[\[path\]]]filenam1.ext( options) [filenam2.ext]...
 
The EXECMODE program accepts several command line options. Each option must be preceded by a "/" or a "-".
The EXECMODE program accepts several command line options. Each option must be preceeded by a "/" or a "-".
{|
 
|'''sp'''||Set file in single processor mode (default)
;sp:Set file in single processor mode (default)  
|-
;mp:Set file for multiprocessor mode  
|'''mp'''||Set file for multiprocessor mode
;l:List files matching sp or mp  
|-
;s:Enable subdirectory searching  
|'''l'''||List files matching '''sp''' or '''mp'''
;f:Force changes on read-only files  
|-
;v:Set verbose mode on  
|'''s'''||Enable subdirectory searching
;q:Set for quiet mode  
|-
;d:Display debug messages  
|'''f'''||Force changes on read-only files
;t:Set test mode (no disk writes)  
|-
 
|'''v'''||Set verbose mode on
|-
|'''q'''||Set for quiet mode
|-
|'''d'''||Display debug messages
|-
|'''t'''||Set test mode (no disk writes)
|}
Up to 50 arguments, in any order, can be specified on the command line. Wildcards are permitted in filenames.
Up to 50 arguments, in any order, can be specified on the command line. Wildcards are permitted in filenames.

Latest revision as of 14:08, 26 May 2025

Reprint Courtesy of International Business Machines Corporation, © International Business Machines Corporation

OS/2 for SMP V2.11 Reference
  1. Notices
  2. Overview of OS/2 for SMP Version 2.11
  3. Platform Specific Drivers (PSDs)
  4. Understanding Spinlocks
  5. Device Drivers In OS/2 for SMP V2.11
  6. Application Considerations
  7. Avoiding Device Driver Deadlocks
  8. New Device Helper (DevHlp) Routines
  9. New Kernel Debugger Commands
  10. The Single Processor Utility Program
  11. OS/2 for SMP V2.11 Tools
  12. Appendix A
  13. Glossary

As explained previously, some applications written for uniprocessor OS/2 may experience problems running under OS/2 for SMP V2.11 because they rely upon priorities between threads for accessing shared resources, or use the CLI/STI method for protecting resources like semaphores or memory. These types of application are called MP-safe. These programs will still run fine under OS/2 for SMP V2.11 if they are run in a uniprocessor mode.

The EXECMODE program is a utility which marks the executable (EXE) file to be run in a uniprocessor mode. The OS/2 loader detects this bit set and forces the application to run on a single processor. The EXECMODE utility can be used to set and reset the uniprocessor mode in an executable file, as well as list those programs that are marked as MP or SP.

The syntax for the EXECMODE utility program is as follows:

execmode (options)[d:[\[path\]]]filenam1.ext( options) [filenam2.ext]...

The EXECMODE program accepts several command line options. Each option must be preceded by a "/" or a "-".

sp Set file in single processor mode (default)
mp Set file for multiprocessor mode
l List files matching sp or mp
s Enable subdirectory searching
f Force changes on read-only files
v Set verbose mode on
q Set for quiet mode
d Display debug messages
t Set test mode (no disk writes)

Up to 50 arguments, in any order, can be specified on the command line. Wildcards are permitted in filenames.