iCluster Web services run in a dedicated subsystem.
This ensures web services are isolated from other workloads and allows dedicated resources to be allocated to that subsystem when required.
This update also provides clear green-screen control paths to start and end that subsystem directly, or as part of standard iCluster engine lifecycle operations.
What Runs Where
The iCluster Web subsystem is XDMICWEB.
It is controlled by dedicated commands in ICWEBLIB:
- ICWEBLIB/DMSTRICW - starts the iCluster Web subsystem
- ICWEBLIB/DMENDICW - ends the iCluster Web subsystem
Command Entry Options (Equivalent Ways)
You can run the same commands in either format:
Option A: Fully qualified
- ICWEBLIB/DMSTRICW
- ICWEBLIB/DMENDICW
Option B: Set current library first
- CHGCURLIB ICWEBLIB
- DMSTRICW
- DMENDICW
These are equivalent command-invocation methods for the same start/end operations.
ICWEBLIB/DMSTRICW is the same operational command as CHGCURLIB ICWEBLIB followed by DMSTRICW, and similarly for DMENDICW.
Integrated Engine Lifecycle Control
The same iCluster Web subsystem is also controlled through engine lifecycle commands:
- DMSTRCST STRICW(*YES) - includes iCluster Web subsystem start
- DMENDCST ENDICW(*YES) - includes iCluster Web subsystem end
This allows web subsystem handling to be included in normal iCluster start/end orchestration.
Important Default Behavior
When using engine lifecycle commands:
- STRICW default is *NO
- ENDICW default is *NO
So if iCluster Web subsystem control is required in those flows, *YES must be specified explicitly.
Why This Matters
Because iCluster Web runs in its own dedicated subsystem:
- web-service runtime is operationally separated,
- subsystem-level resource planning is simpler,
- lifecycle control is clearer during start/end procedures,
- and web-service handling can be aligned with cluster lifecycle when needed.
Green-Screen Operator Flow
A typical sequence:
- Start iCluster Web subsystem directly: ICWEBLIB/DMSTRICW or CHGCURLIB ICWEBLIB then DMSTRICW
- Verify subsystem state using standard subsystem/job monitoring.
- End iCluster Web subsystem directly: ICWEBLIB/DMENDICW or CHGCURLIB ICWEBLIB then DMENDICW.
- For integrated lifecycle operations, include: DMSTRCST STRICW(*YES) and DMENDCST ENDICW(*YES)
Bottom Line
All iCluster Web services run in a dedicated subsystem.
Administrators can start and end that subsystem directly with DMSTRICW and DMENDICW (qualified or via CHGCURLIB ICWEBLIB), or include it in standard engine lifecycle control through DMSTRCST and DMENDCST using STRICW(*YES) and ENDICW(*YES).
This provides precise operational control with cleaner workload separation and better resource governance.
On nodes where both core web services and agent are installed, both are started.
On nodes where only agent services are installed, only the agent services are started.
This behavior is additive. Existing methods to start and stop services remain unchanged and continue to work as before.
Product Demo
The following video demonstrates how to start and end the dedicated iCluster Web subsystem from green screen using both direct commands and engine lifecycle commands.
