Technical article 103002

How can I move calendar files from SCO Office Portfolio to the SCO Shell Calendar?

OpenServer 5

Written · Last revised

Problem

I want to use the calendar files created by SCO Office Portfolio Release 2.0.0 or 2.0.1 with SCO OpenServer Release 5's SCO Shell Calendar.

Solution

SCO Office Portfolio 2.0.0/2.0.1 and SCO Shell Calendar data files are located in:

/usr/lib/sco/oadb/caldata
There is an administration utility for SCO Shell utilities
called "scosh adm".  This utility is very similar to "op adm".
To move the SCO Office Portfolio calendar files for use under
SCO Shell Calendar, follow these steps:

1. On the SCO OpenServer 5 machine, stop the calendar server:

# scosh adm
Choose Utility -> Cal Util -> 7) Stop/Start calendar server.

2. Move the files in the caldata directory to a temporary location.

# mkdir /usr/lib/sco/oadb/caldata/caldata.orig
# mv /usr/lib/sco/oadb/caldata/*  caldata.orig

Be sure to remove the original files after you've got everything up and running.

3. Copy the SCO Office Portfolio calendar data files into the caldata directory.

4. Check and fix the new calendar files by choosing:

3) Check and fix calendar database.

in the "scosh adm" Cal Util submenu.

5. Start the calendar server by choosing:

7) Stop/Start calendar server.

in the "scosh adm" Cal Util submenu.

6. If combining the SCO Shell Calendar files with SCO Office Portfolio files, then:

a. Verify that the SCO Office Portfolio files have been successfully added. b. Go into the "scosh adm" Cal Util submenu as stated above. c. Choose '4) Merge two calendar databases'. d. Start the calendar server as stated above.

NOTE:     If you get an error during step 4, that states:

"Error: This database is not release 2.0. The verify program was run, but cannot run calchk on this database. You can run calchk on this database by running the release 1.0 program calverify."

This could indicate that the system LANG setting doesn't match
the LANG used in the database.  By setting the LANG in
/etc/default/lang to match the database, the check should complete.

To find out which LANG setting was used in the data, use the command:

hd /usr/lib/sco/oadb/caldata/link.idx | head
If this returns:
# hd /usr/lib/sco/oadb/caldata/link.idx | head
0000    00 00 01 00 49 00 00 00  00 00 00 38 ce 00 05 00   ....I......8....
0010    03 00 00 00 00 00 87 ae  03 00 81 63 01 00 00 00   ...........c....
0020    00 00 03 00 00 00 00 00  00 00 00 00 00 00 00 00   ................
0030    25 00 65 6e 67 6c 69 73  68 5f 75 73 2e 61 73 63   %.english_us.asc
0040    69 69 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ii..............
0050    00 00 00 00 00 00 01 00  01 00 01 00 13 00 04 00   ................

Set the first LANG variable in /etc/default/lang to english_us.ascii

LANG=english_us.ascii

Exit out of scosh completely, and restart scosh after making this change and try to fix the data again.

See also

For more information on this and other configuration options with SCO Shell accessories, see the SCO OpenServer Operating System User's Guide, Chapter 2, "SCO Shell Accessories".

From the Xinuos technical article database, record 103002. Reproduced with permission. The original is at www.sco.com/ta/103002, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.