Conference iosg::all-in-1_v30

    Valerie,
    
    Which version of VMS? many other topics in this notes file, which is
    also a STARS database contain topics about the script symbiont such
    as 1326, 322, 594, 883, 988 etc etc 
    
    Please see if any of thes notes help

    Bonjour Valerie,                 
    
    >%OA-W-SNDJBC_OPER send JBC operation error
    >JBC-E-SYSMDEL, unexpected symbiont process termination
    
    Today I installed ALL-IN-1 Version 3.0 and WordPerfect for VMS 5.1-1
    this is patch D of WordPerfect. I had the same problems as yourself.
    
    This is what I did 
    
    1. Had all the printer queues set-up for VMS and ALL-IN-1,  WordPerfect
       was not integrated into ALL-IN-1.
    
    2. Installed WordPerfect for VMS and ran the startup procedure for it.
    
    3. Noticed that the OA$FORMATTER, OA$SCRIPT_BRITISH and other printer
       queues had the characteristic set to 126 or some value.  WordPerfect
       stops all printer queues and reset's their characteristic to integrate
       into WordPerfect.  That's when all the problems started.
    
    Luckly this system is an in-house system and I de-integrated the queues
    by removing the characteristic from the queue.  An I still had many
    problems so I de-installed WordPerfect the problems stopped.
    
    My guess is that the two can not live together.  Sorry I can't be of
    much help I can only say that you are not the only one suffering from
    this problem.
    
    Good luck
    
    Sunil

    Sunil,
    
    So, according to you, the only way to solve my problem is to desinstall
    WORDPERFECT.
    Today, I don't know what to do : I've checked that the images IMP$IMPSHR and
    IMP$IMPSHRP are correctly installed. Seeing the notes, I've removed and
    reinstalled the image OA$SCRIPT_SYMBIONT.EXE and I've deleted and
    recreated the queue but the script submitted in the queue is still in
    the STARTING state (I also removed the smbsrvshr logical).
    
    Does someone have a better solution ?
    
    Cheers,
    
    Val�rie.
    

    Hi Val�rie
    
    Please read my note I have outlined what I did to solve the problem.  I
    did not touch IMP$IMPSHR, IMP$IMPSHRP or OA$SCRIPT_SYMBIONT.EXE.
    
    If you do a $ show que/dev/full you may/will see that the queue have
    /CHAR=(127) this means that they are integrated into WordPerfect.  I
    than deintegrated the queues.
    
    WordPerfect in Australia have just installed Version 3.0 of ALL-IN-1
    and WordPerfect and they are having problems.  I have reported the
    problem I experienced and told them about your's.  Hopefully I will
    have something back from them.  The good thing is that they are also
    having problems !!!
    
    The problem you are having may be caused by the co-existent system.  I
    know WordPerfect told me that they deintegrated WordPerfect and
    upgraded ALL-IN-1, then installed the 3.0 integration.  This is how
    things stand at the moment.  Sorry I can not be of much help at the
    moment.
    
    Sunil

    G'day,
    
    I was at WordPerfect yesterday dressed as Superman to help them install
    ALL-IN-1 and WordPerfect integration for ALL-IN-1 3.0.
    
    We had numerous problems and one of them was the base note type of
    problem.  The SYS$STARTUP:WPCORP$STARTUP.COM calls the
    SYS$STARTUP:WPCORP$INTEGRATE_QUEUES.COM this command procedure
    integrates printer queues into WordPerfect.
    
    The problem appears to be that SYS$STARTUP:WPCORP$INTEGRATE_QUEUES.COM
    integrates OA$SCRIPT_<language> and OA$FORMATTER, these queues are
    treated as printer queues.  One way around the problem is to
    de-integrate the queues by @SYS$STARTUP:WPCORP$INTEGRATE_QUEUES.COM D,
    the parameter "D" is for de-integration.  This means that users will
    not be able to print from within WordPerfect only from the ALL-IN-1
    sub-systems like EM and WP.
    
    This is a workaround and not a solution and WordPerfect are looking
    into the problem.  The integration of WordPerfect for ALL-IN-1 by the
    way had a number problems for the Australian version.
    
    By the way did WordPerfect actually talk to us before they slaved away
    on the 3.0 integration ?  From the sounds of it they may not have.
    
    I hope this is of help to some of you out there and I will keep you
    posted on the progress they have made.  I feel much better not wearing my 
    underpants over my stockings :-) !!!!
    
    Have a good day Val�rie
    
    Sunil

    G'day,
    	if you modify the file SYS$STARTUP:WPCORP$STARTUP_SPECIFIC.DAT (or
    SYS$STARTUP:WPCORP$STARTUP_COMMON.DAT if you installed WPCORP cluster
    wide) so that the integration only occurs to latsym or prtsmb queues
    then you shouldn't have any problem with server queues.
    
    Change the line 
    
    	SYS$COMMON:[SYS$STARTUP]WPCORP$INTEGRATE_QUEUES.COM
    
    to
    
    	SYS$COMMON:[SYS$STARTUP]WPCORP$INTEGRATE_QUEUES.COM I PRTSMB,LATSYM
    
    
    This can also be executed manually (if you have already integrated your
    queues then you can deintegrate them by typing
    
    	@SYS$COMMON:[SYS$STARTUP]WPCORP$INTEGRATE_QUEUES.COM D
    
    and then integrate them as above.)
    
    Alternatively, removing characteristic 127 from the server queues will
    do the same thing ($ SET QUEUE/NOCHAR OA$FORMATTER).
    
    Regards,
    		Chris
    

    G'day Chris,
    
    Looks like we have better support for WordPerfect internally than from
    WordPerfect.  Do you know they are still looking at this problem in the
    US !!!
    
    Thanks
    
    Sunil