Server Guide : Developing server applications : Preparing projects for cross development : Examining a subapplication's configuration expressions : Referring to a subsystem type in the current image
Referring to a subsystem type in the current image
To refer to subsystem type x for the current image, use the expression:
System image subsystemType: x
Subsystem types should be used to determine which components are loaded and to determine whether the image is a development image or a runtime image. The table below shows the public subsystem types and values for each of the supported public image types.
Image type
OS
CFS
CW
CG
CLIM, CLDT, CPM
Windows development
'WIN32s'
'WIN32s'
'WIN32s'
'WIN32s'
'ES'
UNIX development
'UNIX
'POSIX'
'MOTIF'
'MOTIF'
'ES'
Windows native target
'WIN32s'
'WIN32s'
nil
nil
'ES'
UNIX native target
'UNIX'
'POSIX'
nil
nil
'ES'
For example, if an application uses Common Widgets for a user interface implementation, it should only be loaded in an image for which the expression below evaluates to true:
(System image subsystemType: 'CG') notNil
Note:
Subsystem types that are nil in this release might change if component implementation is added over time. Carefully choose the subsystem to test, ensuring that it is the appropriate test to make.
In addition to the public subsystem types listed above, there are several private subsystem types. In general, these should only be used within the product area which defines them. The private subsystem types include--
CPIC
Configures CPIC Socket Interface. Do not use it in configuration expressions outside the CPIC Socket Interface applications themselves.
SCI
Configures Socket Communications Interface. Do not use it in configuration expressions outside the Socket Communications Interface applications themselves.
TM
Configures Transaction Monitors. You can test the TM subsystem type at run time to determine whether the image was built to run under a transaction monitor and, if so, which one. Do not use it in configuration expressions outside the Transaction Monitor applications themselves.
XDDB
Configures XD Interactive Debugger. You can test the XDDB subsystem type at run time to determine whether the XD Interactive Debugger is loaded and, if so, which transport is being used. Do not use it in configuration expressions outside the XD Interactive Debugger applications themselves.
 
Image type
CPIC
SCI
TM
XDDB
Windows development
'WIN32s'
'WIN32s'
nil
nil
UNIX development
nil
'UNIX'
nil
nil
Windows native target
'WIN32s'
'WIN32s'
nil
'WIN'
Windows native with TXSeries for Multiplatforms
'WIN32s'
'WIN32s'
'CICS'
'WIN'
UNIX native target
nil
'UNIX'
nil
'UNIX'
UNIX native with TXSeries for Multiplatforms
nil
'UNIX'
'CICS'
'UNIX'
 
Last modified date: 05/11/2020