Conference iosg::all-in-1_v30

3157.0. "Successive XOPs and flow control" by EWBV51::NAGURA (Yukiji Nagura /ALL-IN-1 CSC/Tokyo/Japan) Tue Aug 17 1993 09:58

	Hi, 

	My customer has added some more menu options to OAN$MENU1 and 
      experienced a strange behavior of XOP.

	Say, there are two conferences to be look up by all users daily,
      and a menu opition is provided to do this like below.

	;;UD;;

	Notes Initialize "notes$notebook"\
	Get #GPC_1 = "DAILY_REPORTS"\
	XOP "~~DISPLAY_DAILY~~"
	Get #GPC_1 = "BULLETIN_BOARD"\
	XOP "~~DISPLAY_DAILY~~"

        In ~~DISPLAY_DAILY~~, there are some other XOPs to perform check 
      and display of unseen notes using original named data, ~~CHECK_UNSEEN~~
      and so forth.

        The symptom is that the second XOP isn't performed if there is at least
      one unseen note. When tracing, "closing form, OAN$LIST" appears directly
      after "XOP "~~DISPLAY_DAILY~~"", and a preprocessing of OAN$MENU1 follows
      that.

        My customer says his customization works well under V2.4, and
      OAN$READ$MORE is new for V3.0 which he suspects is a cause.
      I also guess some flow processing has been changed because if there are 
      no unseen notes in the first conference, the second XOP runs without
      fail.

	Does anyone know what the possible cause and/or workaround are/is ?
      Any comments are highly appreciated.

	Rgds,					Yukiji/Tokyo CSC

    Hi,
    
    I think you are missing a CLOSE_PRIOR function call before the second
    XOP.
    
    Cheers
    
    Stuart

    Stuart,

    It works !!! Thank you very much.

    Thus you see now I'm not good at ALL-IN-1 programming (^^;

    But I don't understand why the form works under V2.4 environment.
  In V2.4, there were also other form calls, e.g OAN$LIST, nevertheless
  it was said to work fine, or is it not true ?

    Which form context does that CLOSE_PRIOR function close actually in
  this case ?

             						Yukiji

    Hi Yukiji,
    
    Does the application use the NOTES LIST function? That changed a lot in
    V3 so that reading notes is now much like reading mail messages, and it
    may well be that the changes affected your application. Fortunately
    the workround has fixed your problem.
    
    Cheers
    
    Stuart