McIDAS-XCD Administrator's Guide
Version 2006

[Search Manual] [Table of Contents] [Go to Previous] [Go to Next]

Starting and Stopping McIDAS-XCD

There are two ways to start and stop running McIDAS-XCD. If you prefer to have a continuous McIDAS session running in the oper account, you may use the McIDAS-XCD STARTXCD command in your McIDAS-X session. If you prefer to configure McIDAS-XCD without a McIDAS-X session running, you may use the xcdadmin command from a Unix shell prompt. If your data source is the LDM, you should start LDM before starting McIDAS-XCD, and stop LDM after stopping McIDAS-XCD.

Using STARTXCD in a McIDAS-X Session

Use the STARTXCD command as described below to start the McIDAS-XCD software. For more information about STARTXCD, see Chapter 3, McIDAS-XCD Administrative Commands.

From a McIDAS-X session running under the oper account, start the McIDAS-XCD software with the command below.

Only one STARTXCD command can be run at a time. Do not include the command STARTXCD in your STARTUP.SYS file.

The STARTXCD command runs continuously in your McIDAS-X session, starting and stopping data monitors and ingestors as needed. If a data monitor or ingestor stops, STARTXCD automatically restarts it. If you cancel STARTXCD, also cancel the associated data monitors and ingestors. If you exit McIDAS-X, your decoders and ingestors will stop running.

Use the DECINFO command to activate and deactivate the data monitors. The STARTXCD process (which is continuously running) will check the status of the monitors and start or stop them accordingly.

To activate or deactivate an individual decoder within a data monitor, you must first deactivate the data monitor. Once the data monitor is no longer active, the status of the decoder(s) can be changed using the DECINFO command. Then use DECINFO to reactivate the data monitor using the new settings.

When you need to stop McIDAS-XCD, the best method is to exit the McIDAS-X session and wait for all -XCD related processes to exit.

Using xcdadmin from a Unix Shell Prompt

From a shell prompt under the oper account, backup your current version of xcdadmin, copy the latest version to /home/oper/mcidas/bin, and change the permissions to make it executable by user oper.

From a shell prompt under the oper account, verify that you are using the correct version of xcdadmin.

The result of this command should be the currently installed version of xcdadmin (e.g. /home/oper/mcidas/bin/xcdadmin). If it is not, remove or rename that version so that it is not the version that is executed. If the result of this command is the currently installed version, then edit the Configurable Options section of the xcdadmin script. It contains variables that change its behavior. These variables must be reviewed before using the script. In particular, the xcd_data_path variable must be set. After reviewing the Configurable Options and setting the xcd_data_path, start the McIDAS-XCD software with the command below.

The xcdadmin start command runs the STARTXCD -XCD command in a mcenv session and behaves exactly as described in the section above, Using STARTXCD in a McIDAS-X Session.

When you need to stop McIDAS-XCD, run the command below from a shell prompt under the oper account to stop all -XCD related processes.

The xcdadmin stop command kills the startxcd.k process. It then waits 30 seconds for all of the -XCD data monitors to exit. At the end of the 30 seconds, it kills the remaining data monitors. You should verify that all of the data monitors were stopped, and kill the processes, if necessary.

[Search Manual] [Table of Contents] [Go to Previous] [Go to Next]