Re: new SyncCM calander names...???

[esiegel@xxxxxxxxxxxxxxxxxx (Ellen Siegel)]

> 
> > I just upgraded to the new PilotManager 1.100Beta-6 and I now get the
> > following error when trying to sync my calendar:
> > 
> > ...
> > 10/20/97 12:40:27   Synchronizing using the SyncCM conduit
> > 10/20/97 12:40:27   msw@polyslo is in an obsolete data format
> >                     It must be updated to the CDE format before
> >                     SyncCM can interface with it.
> > 10/20/97 12:40:27   Error: fail at ./PilotManager line 1774
> > 10/20/97 12:40:27   No changes
> > ...
> > 
> 
> I had the same problem.  I dug around and found out that there are two 
> formats for the calendar manager data files, the old openwin compatible 
> and the newer CDE only format.  This new version of pilotmanager wants 
> the new CDE only format.  (There are important features that 
> PilotManager uses for recurring appointments.)
> 
> There are utilities in the /usr/dt/bin directory called sdtcm_convert 
> and sdtcm_admin.  sdtcm_convert will convert your current, older file 
> format to the newer, according to the answerbook.  sdtcm_admin is used 
> to create new calendars or destroy old ones.
> 
> I tried to use sdtcm_convert and wound up trashing my calendar to the 
> point where nothing would read it.  At that point, I had the domain 
> sysadmin delete my calendar and then I recreated it using sdtcm_admin.  
> Ever since then, everything has been hunky-dorey.
> 

I was able to successfully use sdtcm_convert, and then successfully 
synchronize my calendar. I am running the beta-6 on a 2.5.1 machine with
CDE 1.1 (June, not March version). The calendar machine is also a 2.5.1
machine with CDE 1.1. Note that after the warning I carefully made a
backup copy of the calendar file before manipulating it, although as it
turns out I didn't need one.

The syntax I used was:

/usr/dt/bin/sdtcm_convert -v 4 <calendarname@calendarhost>

-v 4 tells it to convert to the new CDE format; -v 3 tells it to convert
to the prior Openwin format, so you can always convert back if necessary.

You can also specify a date before which to prune (e.g. -s 10/01/96)
and a directory in which to write a backup file (e.g. -d foo)

	Ellen
---------------------------------------------------------------------
********************************************
*   PLEASE DO NOT POST PILOTMANAGER BUGS   *
*  TO THIS ALIAS.  SUBMIT BUG REPORTS VIA  *
*     THE FEEDBACK MENU IN PILOTMANAGER    *
*             --------------------         *
*      This is a public mailing list!      *
*  Please do not publish Sun proprietary   *
*            information here!             *
********************************************