[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

2877.0. "Major changes with CAL$MEETING for V3.0?" by BERN02::MUELLERS (Stefan A Mueller 761-4864) Thu Jun 17 1993 13:45

    Hi,
    
    I did some customizations for a customer in the Time Management
    subsystem of ALL-IN-1 V2.4. They wisched to include support for their
    transport codes when they have to travel. I made us of the field filler
    in CAL$MEETING and CAL$ATTENDEE which is loaded by the CALENDAR
    functions if #CAL_xxxx_EXTRA is loaded.
    
    Now they want to upgrade to V3.0 - and it no longer works. There are
    no changes listed in the documentation of the CAL$ data sets and the
    CALENDAR functions. But there seem to be mandatory changes with the
    CAL$MEETING data set. I had a look at V24_MEETING.FRM and MEETING.FRM
    and have seen that the length and number of fields has changed. And the
    badest news in my case: CALENDAR SCHEDULE MEETING does not care about
    the value stored in #CAL_MTNG_EXTRA which should be written into field
    FILLER of CAL$MEETING.
    
    Another problem will be the conversion of the old MEETING.DAT to the
    V3-MEETING.DAT. Will the contents of the V24-FILLER field copied to the
    new file? And how can I get its content? I tried to modify a record of
    MEETING.DAT using the form MEETING. I entered something in the field
    Filler and did a <get cal$meeting.filler[#key]. But this didn't show
    the content of the field.
    
    Some comments?
    
    Stefan

T.R	Title	User	Personal Name	Date	Lines
2877.1	.FILL1 = .FROM_ADDRESS ???	BERN02::MUELLERS	Stefan A Mueller 761-4864	`Thu Jun 17 1993 13:55`	6
	I just tried a <write change cal$meeting %key=#key,fill1="blablabla" and called MEETING. The string "blablabla" has been written into a field called "From Address" (ME_FROM_ADDRESS). Stefan
2877.2	CAL$MEETING: help is still needed!	BERN02::MUELLERS	Stefan A Mueller 761-4864	`Wed Jun 23 1993 10:37`	44
	Hi again! There seem to be nobody having dealed with time management... If somone likes to do a little test, the script below will show that the way CALENDAR SCHEDULE MEETING and CAL$MEETING are working together is different in V2.4 and V3.0. Do the following: $ ALLIN1 TMS <DO A1030_DEMO_MTNG_FILLER ... and enter data as if you were creating a meeting In V2.4 you'll get the following output on line 24: TEST CAL SCHED MEETING This is the content of field FILLER In V3.0 the output looks like this: TEST CAL SCHED MEETING %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ! ! A1030_DEMO_MTNG_FILLER.SCP ! GET #CAL_MTNG_EXTRA = "This is the content of field FILLER" GET #CAL_MTNG_LOC = "Somewhere" GET #CAL_MTNG_DESC = "TEST CAL SCHED MEETING" GET #CAL_MTNG_CONFID= "N" GET #CAL_MTNG_ETIME = "14.00" GET #CAL_MTNG_STIME = "13.00" GET #CAL_MTNG_PRIORITY = "" GET #CAL_MTNG_WHEN = "17.Jun.1994" GET #CAL_MTNG_SCHEDULER = OA$USER GET #ME_AP_FLAG=OA$Y FORM SCHDMA .IF OA$FORM_DISPOSE EQS "0" THEN .EXIT GET #NOVALID="VAL_DONE" CALENDAR SCHEDULE MEETING GET #NOVALID="" GET CAL$MEETING.MEETING_PURPOSE:40[#CAL_MEETING_POINTER] .FILLER .EXIT %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2877.3		PEARS::GRAEF	Ghinees hies good for you.	`Wed Jun 23 1993 13:35`	6
	I hate to say it, but the CAL$MEETING action routine has a bug in the PUT_FIELD and GET_FIELD code. The field offsets for FROM_ADDRESS, FILL1, and FILL2 are off by 1. Cheers, helmut
2877.4	What can I do?	BERN02::MUELLERS	Stefan A Mueller 761-4864	`Wed Jun 23 1993 14:21`	4
	Thanks Helmut! Seems to be easy to get fixed. What would you - or someone else - suggest me to do ? Stefan
2877.5		PEARS::GRAEF	Ghinees hies good for you.	`Wed Jun 23 1993 15:02`	13
	Stefan, unfortunately this problem is more serious. In addtion to the wrong field offsets within the action routine, the form MEETING (which is used to convert an old meeting file) has a different field layout as the one defined in code. Form MEETING defines field ME_FILLER positioned right after the 40 byte ME_FROM_ADDRESS, whereas the code expects to see a 512 byte FROM_ADRRESS followed by field FILLER. Confusing? Imagine how confusing it will be for users working with TM after an upgrade from ALL-IN-1 V2.4. Cheers, helmut
2877.6	Patch?	BERN02::MUELLERS	Stefan A Mueller 761-4864	`Wed Jun 23 1993 15:58`	5
	Helmut, do you know if a patch for this problem is available? Or is it necessary to escalate this problem to get it fixed for the customer? Stefan
2877.7	Surely you know this	AIMTEC::WICKS_A	U.S.A 2 England 0 - I was there!	`Wed Jun 23 1993 17:23`	7
	stefan, Official Support requires SPRs Regards, Andrew.D.Wicks