The Transaction Server for ClearPath MCP load file *COMS/SINGLEPOINT/LOAD defines both SINGLEPOINT and SINGLEPOINTTEST. The key differences between them occur in their configuration files and are shown in Figure 1–3:
SINGLEPOINT defaults to allowing keyins from the primary Operations Sentinel server; SINGLEPOINTTEST does not.
SINGLEPOINT defaults to port 10301; SINGLEPOINTTEST defaults to port 10302.
SINGLEPOINT can use the Operations Sentinel API library; SINGLEPOINTTEST cannot.
When you use Transaction Server for ClearPath MCP to load your edited *COMS/SINGLEPOINT/LOAD file, you avoid having to manually define the parameters for the two running instances of the agent.
*COMS/SINGLEPOINT/LOAD sets MIN_COPIES to 1 for SINGLEPOINT and to 0 for SINGLEPOINTTEST. To be able to run SINGLEPOINTTEST, set its MIN_COPIES to 1, either by editing the file or updating it on a screen in UTILITY.
A Multi-Program ID (MPID) attribute in the COMS load file appends a unique identifier after the task name in mix displays, to facilitate distinguishing production (SINGLEPOINT) from testing (SINGLEPOINTTEST) when two copies of SINGLEPOINT/INTERFACE are running.