This service performs the following tasks:
Schedules and synchronizes transfer requests.
Controls shared memory for transfers.
Establishes the default parameter values by reading the
XCOM.GLB
file.Controls the automatic restart of locally initiated transfers.
Writes queue information out to disk periodically.
Deletes aged entries from the queue.
Notifies a local user by executing the XCOMNTFY script when LOCAL_NOTIFY is required.
Communicates with active or pending transfers to terminate a transfer.
Considerations
Only administrative users with user rights to operate the Windows services can start and stop the XCOM Scheduler service
The XCOM Scheduler service XCOM Scheduler service XCOM Scheduler service XCOM Scheduler service
The XCOM Scheduler service
Operate the Service
You can use the command line or the GUI to start and stop the XCOM Scheduler service
Operate using the command line
To start the service, use the following command:
net start xcomdsrv
To stop the service, use the following command:
See AlsoAdventHealth hiring Concierge PRN in Zephyrhills, FL | LinkedInPhysicians Regional Healthcare System hiring Charge RN Neuro Med Surg Weekend Nights in Birmingham, AL | LinkedInRevenue Integrity Manager - CDM - Mon - Fri 8:00am - 5:00pm - Hybrid - On-site days in Gainesville in Gainesville, GA for Northeast Georgia Health SystemCustomizing the TaskScheduler: Queue Your Task Work Items to Run When You Want Them Tonet stop xcomdsrv
Operate using the GUI on the Windows Server Core
Open the Task Manager, navigate to the
Services
tab, and selectxcomdsrv
from the services list.Start or stop the
XCOM Scheduler service
:To start the service, right-clickxcomdsrvand click
Start
.To stop the service, right-clickxcomdsrvand click
Stop
.
Operate using the GUI on the Windows Server (non-core platforms)
Display the list of services by performing
one
of the following procedures:Select
Administrative Tools
,Computer Management
to openthe Computer Management explorer. SelectServices and Applications
, thenServices
.Select
Accessories
,Run
. Typeservices.msc
in the command line.
Select
XCOMD CA XCOM Scheduler Service
from the list.Start or stop the service:
To start the service, right-click the selected service and click
Start
.To stop the service,right-click the selected service and click
Stop
.
Trace the Service
The following steps assume that C:\Program Files\CA\XCOM XCOM Data Transport for Windows
Setting trace options can generate large trace data files.
Enable tracing:
Enter the following command at the prompt:
card3 on
The following message appears, indicating that the trace facility is enabled:
CA-XCOM daemon trace facility now enabled.
Stop the
XCOM Scheduler service
.From the
Services
dialog box, highlight theXCOM Scheduler service
, selectAction
from the menu bar, and selectProperties
.Enter
- d9
in theStart parameters
field.Restart the
XCOM Scheduler service
.The
CA Trace
icon appears in the task bar.
Terminate tracing:
Stop the
XCOM Scheduler service
.The
CA Trace
icon disappears.The
service.trc
file is created inC:\Programfiles\CA\XCOM\trace\
.Enter the following command at the prompt:
card3 off
The following message appears, indicating that the trace facility is disabled:
CA-XCOM daemon trace facility now disabled.
SESSION 0 Isolation
Windows isolates services inSession 0 and makes that session non-interactive. Only system processes and services run in Session 0. The first user logs on to Session 1, and subsequent users log on to subsequent sessions. The services never run in the same session as user applications and are therefore protected from attacks that originate in the application code.
When the XCOM Scheduler service
Invalid parameter name specified in
XCOM.GLB
, or invalid value specified for a valid parameter name:XCOM Scheduler service
logs the error intoXCOM.LOG
instead of displaying an error message through the message box.Pre-processing, end-processing, post-processing, notification processing, send report, or send job scripts with commands that require user inputs:
The script runs in the session corresponding to the owner of the transfer. If the owner is a non-logged in user, then the interactive scripts are shown in session 0.Any user interaction makes the script and the transfer hang.
Interactive commands are useful for debugging scripts in your test environment, but we recommend removing them from your production environment.
