| 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 |
VMS 5.5 with Queue Manager Patch (CSCPAT_1012)
ALL-IN-1 V3.0
Since installing V3.0 we have not been able to get the Script Symbiont queue
to work. When it is started it goes into an idle state but stops as soon as
any jobs are sent to it as follows;
Server queue OA$SCRIPT_BRITISH, stopped, on WALTER::, mounted form DEFAULT
Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
364 TEMP ALLIN1 1 Retained on error
%JBC-E-SYMDEL, unexpected symbiont process termination
-CLI-S-NORMAL, normal successful completion
Completed 17-JUN-1992 18:00 on queue OA$SCRIPT_BRITISH
With Operator message;
%%%%%%%%%%% OPCOM 17-JUN-1992 18:00:32.87 %%%%%%%%%%%
Message from user QUEUE_MANAGE on WALTER
%QMAN-I-INVSMBMSG, invalid data in message from symbiont on queue OA$SCRIPT_BRIT
ISH is being ignored
I have tried de-installing oa$script_symbiont.exe, deleting and recreating the
queue using SCRIPT_QUEUES_INIT and SCRIPT_QUEUES_ALL, and logging in as
A1$SCRIPT which is ok. I have also tried using a command procedure as a sep/res
module on the queue to redefine sys$output to a log (as per Stars article) but
no log is created. JS IAJ gives no further information.
Help...
Regards Aston
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 888.1 | Not the same as 883? | AIMTEC::WICKS_A | DEC Mail Works for ME sometimes | Wed Jun 17 1992 22:27 | 1 |
Seen note 883? | |||||
| 888.2 | No. | WAYOUT::CLARKE | The Cat in the Hat comes back. | Thu Jun 18 1992 13:14 | 10 |
I hadn't noticed note 883. However my queue always remains a Server Queue and can be started ok. It just can't process any scripts and when one is submitted to it the queue stops. The idea of de-installing the Script symbiont image and re-initialising the queue was discussed in a previous topic and I have tried this to no avail. Any more ideas? Aston | |||||
| 888.3 | IOSG::ALLAN | Derek, DTN 830-3669 | Mon Jun 22 1992 13:06 | 24 | |
This case does appear to be different. The symbiont and the job controller seem to be having more of a conversation than in the other case. The evidence for this is the queue entry which has two error messages placed on the job by the script symbiont. > %JBC-E-SYMDEL, unexpected symbiont process termination > -CLI-S-NORMAL, normal successful completion It looks as though the script symbiont is creating (or attempting to create) a slave process in which to run ALL-IN-1, and something is going wrong. Could you check with VMS accounting to see whether or not a process gets created by the symbiont? The accounting record will show a detached process created under the SYSTEM user name shortly after the script job is submitted. Also, does the OA$SYMBIONT... process disappear? The opcom message is a result of the new version of the queue manager being extra fussy about what job parameters are passed to a Server queue. If this problem cannot be fixed you have 3 options: live with it; upgrade to 5.5-1 or take off the job controllor patch. Cheers, Derek | |||||