Conference iosg::all-in-1_v30

    John,
    
    Do you mean you have something like:
    
    Server queue OA$SCRIPT_ENGLISH, on DIMUND::, mounted form DEFAULT
    
      Jobname         Username     Entry  Blocks  Status
      -------         --------     -----  ------  ------
      CM_SM_SWITCH_PRVAPP
                      ZANIEWSKI_D    928      21  Retained on error
        %NONAME-E-NOMSG, Message number 00000002
      CM_SM_SWITCH_PRVAPP
                      ZANIEWSKI_D    197      21  Retained on error
        %NONAME-E-NOMSG, Message number 00000002
      CM_SM_SWITCH_PRVAPP
                      ZANIEWSKI_D    276      21  Retained on error
        %NONAME-E-NOMSG, Message number 00000002
    $
    
    This is on a system running VMS v5.4  so v5.5 may be innocent here 
    
    The problem as they say has been "elevated to engineering" ....
    
    NOt much help I know but at least you know you're not alone.
    
    Regards,
    
    Andrew.D.Wicks
    
      

Andrew,

This is what I get with a SH que/ful, as you can see the queue is 
stopped.  I have deleted the jobs and the queue (using 
OA$LIB:SCRIPT_QUEUES_ALL), then initialised it and started it.

The queue goes into a STOP date as soon as the first script is 
submitted.  So it is not quite the same as previous example of jobs 
retained on error.


Server queue OA$SCRIPT_ENGLISH, stopped, on WEST07::, mounted form 
DEFAULT
  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /NOENABLE_GENERIC
  /LIBRARY=ENGLISH /OWNER=[SYSTEM] /PROCESSOR=OA$SCRIPT_SYMBIONT
  /PROTECTION=(S:E,O:D,G:R,W:W) /RETAIN=ERROR /SCHEDULE=(NOSIZE)

  Entry  Jobname         Username     Blocks  Status
  -----  -------         --------     ------  ------
    835  CM_SM_SWITCH_PRVAPP
                         ALLIN1           21  Pending (queue stopped)
         Submitted 29-APR-1992 10:36 /FORM=DEFAULT /PARAM=("DEMO_1","3")
         /PRIORITY=100
         File: _R2QBRA$DIA0:[ALLIN1.LIB_SHARE]CM_SM_SWITCH_PRVAPP.SCP;1
             /SETUP=("MANAGER",)

    836  CM_SM_SWITCH_PRVAPP
                         ALLIN1           21  Pending (queue stopped)
         Submitted 29-APR-1992 10:37 /FORM=DEFAULT /PARAM=("DEMO_1","3")
         /PRIORITY=100
         File: _R2QBRA$DIA0:[ALLIN1.LIB_SHARE]CM_SM_SWITCH_PRVAPP.SCP;1
             /SETUP=("MANAGER",)


Hope this information helps

John

    I've something like this caused by IMP$IMPSHR and IMP$IMPSHRP 
    not being installed. Could that be causing the problem?
    
    Angela

	I had a problem w VMS A5.5 where the script symbiont queue would not 
start.  The fix was to deinstall OA$SCRIPT_SYMBIONT (Thanks to Derek) before 
starting the queue - actually just don't install it in the first place in 
A1V30START.

HTH

John

OK, I have removed the existing OA$SCRIPT_ENGLISH queue, then removeds 
the installed image.  I then used OA$LIB:SCRIPT_QUEUES_INIT to define 
the queue, and then OA$LIB:SCRIPT_QUEUES_ALL START to start the queue.

The queue goes into an idle state, but as soon as I modify a user 
account, and a script gets submitted to the queue the queue goes into 
a stopped state.

Any more suggestions?

FYI the system is running ALL-IN-1 v3.0 PBL122D

John

If the queue starts successfully, (goes into an idle state) then the script 
symbiont seems to be talking to the 5.5 job controller OK.

The fact that the queue dies when a script is submitted suggests that the
symbiont is having trouble running up the ALL-IN-1 image in a slave process.
You're not by any chance running a parallel 2.4 system on the same machine?
If so, then the symbiont may be running up the 2.4 image, which doesn't know
how to communicate with the symbiont.

The work around in this instance is to 

	create a foo.com file with commands to set the 3.0 system current
	and then run ALL-IN-1.

	copy the foo.com file to sys$system

	stop the queue and re-initialize it with /SEPARATE=RESET=FOO 

	re-start the queue

Cheers,
Derek

No it is not a co-existent system - I don't think the system ever had 
ALL-IN-1 v2.4 installed.

I Upgraded to BL123A last night, and still have the problem.

The search continues.

John

Have you tried going back to the V5.4 job controller yet? If I can get access
to your system I'm willing to look for clues myself.

Cheers,
Derek

    Running on the DECUS system last week (VMS V5.5, BL122D) we had
    terrible problems with the script symbiont. It just wouldn't work. Now
    that I'm back onto a (safe for symbionts) V5.4 system the same commands
    work just fine...
    
    As Derek says in -1, maybe your problem lies in the infamous VMS V5.5
    and printing/queueing/symbionts issue?
    
    Tony

I spotted the fact that there was a batch and print patch for 5.5 
(BATCH_PRINT$02_055) which I have now installed.  I still have 
problems with the script symbiont, but it is a different problem.

I get an OPCOM message saying -

   Invalid data in message from Symbiont on queue oa$script_english is 
being ignored

The queue hoes into a stopped state.  When i show details about the 
queue, the job has been retained on error with the following messages -

   %JBC-E-SYMDEL, unexpected symbiont process termination
   -RMS-F-RNF, record not found

Hopefully with this info somebody might be able to point me in the 
right direction.

Many thanks

John

    
    See Note 232 for details on the cause of this problem and the
    recommended solution which is also available in STARS.
    
    Faith
    

    
    Faith,
    
    I don't want to be picky, but you probably mean Note 322. Note 232 also
    concerns the Script symbiont, but in a different sense (problem in
    CM_SM_SWITCH_PRVAPP.SCP).
    
    Ciao,
    
    	Simon