sched and schedm GPL Applications

The sched and schedm GPL applications will keep track of your schedule of events including budget. You will be able to view your planned and actual expenses and balance for each day. The schedule data is stored in Bbuuzzb tables. These two programs are text/console based.

The sched application is designed for single user use. The Bbuuzzb database engine is linked into this binary/executable. Before you can run the sched application, you must set up a database configuration file called dbeng.cfg with a minimum of the tmp_path, log and catalog entries.

The schedm application is designed for client/server environments and uses either TCP sockets or QNX message passing IPC method. Any mention of QNX in this document refers to the QNX 4.x OS.

schedm requires a Bbuuzzb database server to be running. The schedm application communicates with the Bbuuzzb database server, the socloc server and possibly the system log server (if logging is enabled and the current log destination is the system log server). In order to get schedm to successfully connect to the Bbuuzzb database server, the server must already be running and registered with the socloc server and there must be at least one socloc server, and possibly one system log server (if logging is enabled and the current log destination is the system log server) running within the environment. A socloc startup file must also be composed to connect to a socloc server. The database configuration file is not required for the schedm application.

All configuration files must be located in the same directory as the binary/executable program. The sched and schedm applications must be executed within their current directory so the program can locate the configuration files.

When using either of these two programs, they must be run with the bbuuzzb catalog active. In the following detailed description all table names are logical.

# Detailed Description

Sched and schedm will store and calculate your schedule of events. Events include budgetary and reminder's. Events are tracked on a day to day basis. This program makes it possible to see your bank account balance for every day there is an event.

All data is stored in bbuuzzb tables. Each table is a year's worth of data and this program allows you to see the data one month at a time.

As yearend approaches, you need to manually create next year's bbuuzzb table. The table names have the convention of:

       schedule.nnnn

Where nnnn is the year.

Each time monthly events are listed, they will be displayed in the following form:

       c:mmdd.s desc,cat,pl,plb,act,actp

Where the c is a list event count, mmdd are the month and day of the event, s is the day sequence count (since there may be more than one event per day), des is the event description, cat is the event category (see below), pl is the planned amount, plb is the current planned balance, act is the actual amount spent and actp is the current actual account balance. The balances are as at after the event has taken place.

This program depends on a category table which you need to set up. Every event will belong to one of these categories. The name of the category table must be schedule.category. The field layout of this category table is as follows:

       Field Number  Description
       ===== ======  ===========

          1          category number (sequential count)
          2          category description
          3          category type number (see below)

Each category entry has a type which tells this program what to do with all the events that belong to this type. Here are the category event type numbers and descriptions:

       Category Type Number  Description
       ======== ==== ======  ===========

          1                  credit
          2                  debit
          3                  na (reminder)

You must use the category type number in field 3 of the category record (see above).

This program also uses its own temporary table called schedule.tmp. Ths table must also already exist.

Goto Top | Future Lab Home | Contact Webmaster | Feedback

Copyright © 2006 Future Lab, Last Updated Sep 16, 2006