Server Guide

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
OS/2 development 'OS/2' 'OS/2' 'PM' 'PM' 'ES'
Windows NT and Windows 95 development 'WIN32s' 'WIN32s' 'WIN32s' 'WIN32s' 'ES'
UNIX development 'UNIX 'POSIX' 'MOTIF' 'MOTIF' 'ES'
MVS simulation (OS/2 target) 'OS/2' nil nil nil 'ES'
MVS simulation (Windows NT target) 'WIN32s' nil nil nil 'ES'
MVS native target 'MVS' nil nil nil 'ES'
OS/2 native target 'OS/2' 'OS/2' nil nil 'ES'
Windows NT native target 'WIN32s' 'WIN32s' nil nil 'ES'
UNIX native target 'UNIX' 'POSIX' nil nil 'ES'
OS/400 Native 'OS/400' '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
OS/2 development 'CM/2' 'OS/2' nil nil
Windows NT and Windows 95 development 'WIN32s' 'WIN32s' nil nil
UNIX development nil 'UNIX' nil nil
MVS simulation (OS/2 target) 'CM/2' 'OS/2' 'CICS' 'OS/2'
MVS simulation on OS/2 with CICS Transaction Monitor 'CM/2' 'OS/2' 'IMS' 'OS/2'
MVS simulation on OS/2 with IMS Transaction Monitor 'CM/2' 'OS/2' nil 'OS/2'
MVS simulation (Windows NT target) 'WIN32s' 'WIN32s' nil 'WIN'
MVS simulation on Windows NT with CICS Transaction Monitor 'WIN32s' 'WIN32s' 'CICS' 'WIN'
MVS simulation on Windows NT with IMS Transaction Monitor 'WIN32s' 'WIN32s' 'IMS' 'WIN'
MVS native target nil 'MVS' nil 'MVS'
MVS native with CICS Transaction Monitor nil 'MVS' 'CICS' 'MVS'
MVS native with IMS Transaction Monitor nil 'MVS' 'IMS' 'MVS'
OS/2 native target 'CM/2' 'OS/2' nil 'OS/2'
Windows NT native target 'WIN32s' 'WIN32s' nil 'WIN'
Windows NT native with CICS Transaction Monitor 'WIN32s' 'WIN32s' 'CICS' 'WIN'
UNIX native target nil 'UNIX' nil 'UNIX'
UNIX native with CICS Transaction monitor nil 'UNIX' 'CICS' 'UNIX'
OS/400 Native nil 'OS/400' nil 'OS/400'


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]