Phantom Process Settings

Access

Use this routine to specify your preferences for phantom A process that performs a maintenance function in STORIS, and can be set up to run automatically in the background on a regular basis. processing.  Using phantoms can speed up your over-all data processing.  STORIS comes delivered with multiple phantom processes available for activation on your system.  However, not all STORIS processes have supporting phantoms.  

Each phantom runs a STORIS program in the background, processing transactions and updating pertinent files as you enter the data into the system.  For example, many phantoms such as the GL Posting Phantom process a file in the background while you work during the day in order to reduce the amount of data End-of-Day must process.

If you must shut down your server, STOP ALL PHANTOM PROCESSES RUNNING ON THE SYSTEM BEFORE SHUTTING DOWN. If you are unable to do so, contact your system administrator or STORIS representative for assistance before shutting down the server.

STORIS personnel provide the default values in this routine during the installation of your system. You should NOT change any of these fields without first consulting a STORIS representative.

The settings in this routine determine how each phantom processes data, including the optimum number of phantoms to run at a given time for a selected STORIS process.  In relation to the amount of data ready for processing at any given time, running too many phantoms can slow down your computing operations, and too few phantoms can result in a backlog of data for another process, for example the End-of-Day process.

The Auto Start/Stop feature (see the Auto Start fields below) can automatically determine the optimum number of phantoms to run at a given time for a selected STORIS process based on your settings at the below fields.  

Additional

• All registered phantoms are checked. If any are found to be inactive (dead), their registration is removed from the phantom's record.

• The defined auto-start queue is checked and the correct number of phantom process is calculated using the auto start count. If an insufficient number of phantoms are running, then new phantoms are automatically launched.  If too many phantoms are running, the system stops some of the phantoms and deletes their registrations from the phantoms record.

• The automatic update/refresh mode may be exited at any time by pressing any key.

ProcessEnter the process ID for the phantom you want to edit. If you click on the Search button, a list of valid phantom processes appears from which you can choose.  

DescriptionThe description of the phantom process appears. You can edit this description.

Type

Sleep IntervalEnter the amount of time, in seconds, you want this phantom to "sleep" when no transactions are waiting to be processed. When the time expires, the system checks for transactions waiting in the queue. This is a required field. To specify no sleep time, enter 0 (zero).

Status IntervalEnter the amount of time, in seconds, between status updates.  All phantoms periodically update their current status.  This helps determine if a phantom is actually running or if it has become disabled.  This field is required. Your response must be greater than the sleep interval specified.  

Auto Start Queue File

Auto Start Queue CountUse this field, in conjunction with the Auto Start Queue File, to determine the correct number of phantoms that should be running in the automatic start/stop process. Enter the maximum number of entries allowed in the Auto Start Queue File before the phantom "wakes up" and begins processing.  

Auto Start Max ProcessesUse this field, in conjunction with the Auto Start Queue File, to determine the correct number of phantoms that should be running in the automatic start/stop process. This ensures that an unreasonable number of processes are not automatically launched due to excessive workload or program error.

Extra Information Display Subroutine NameIf additional information exists about the phantom you are viewing, the name of the subroutine that shows this information appears here.

Maximum Number of Concurrent PhantomsEnter the maximum number of concurrent phantom processes that can be run at one time for the selected phantom.

For example, for credit bureau phantoms, the maximum number is one, as this process is “married” to the modem. Thus, two credit bureau phantoms cannot be running at the same time.

Extra Cleanup Subroutine NameUse this field to indicate the subroutine name you want to run when shutting down a phantom process.

For example, when shutting down the credit bureau phantom, subroutine AR.293.SUB tries to reset the modem that you were communicating on since when you shut down a phantom, it does not always “tidy up” after itself.