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

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

5361.0. "Script AM returns: The script has produced no output" by BACHUS::FOLENS () Tue Jul 20 1993 12:26

A colleague of mine who is implementing DECmcc on a Ultrix system
at a customer side has problems with the script am.
He developed some procedures that are returning some values (such as
statistics) and implemented them in DECmcc via the script am.
These scripts worked fine until a few days ago.
The 'show script .... all status' always returns the following: 

MCC> show script .mcc.gkk_statistics command date all char

Script bc:.mcc.gkk_statistics COMMAND date
AT 1993-07-20-17:18:57.432 Characteristics

Examination of attributes show:
                                Command = "date"
MCC> show script .mcc.gkk_statistics command date all statu

Script bc:.mcc.gkk_statistics COMMAND date
AT 1993-07-20-17:20:43.951 Status

The script has produced no output.
    
I tried to register a new script entity but could get the script
working.I found a similar problem in note 4530 but this was running DECmcc on 
VMS.
Is there any way to trace what's going on? A 'setenv MCC_SCRIP_AM_LOG 0xffff'
didn't produce any output.

-Geert-

T.R	Title	User	Personal Name	Date	Lines
5361.1	Sticky debug bits ?	HADRES::KRAUSE	European NewProductEngineer for MCC	`Thu Jul 22 1993 12:07`	29
	You mentioned that you experimented with debug bits. This might be the cause of the problem. At least I was able to reproduce it: > mcc_kill > setenv MCC_SCRIPT_AM_LOG 0xffff > manage DECmcc (V1.3.0) MCC> show script .s.test comm date all statu mcc_script_am_log Routine. Saving log bit mask (ffff) <========1 Script LOCAL_NS:.s.test COMMAND date AT 1993-07-22-17:01:14.039 Status The script has produced no output. MCC> exit 1) This message only appears once. Subsequent commands just say 'no output'. Even logging out and back in does not help. You loose your environment variable, but the bits are saved(!) in the Script AM process. Make sure you do NOT have MCC_SCRIPT_AM_LOG defined and then issue a mcc_kill. This should clear your problem (at least it did for me...). Regards, *Robert
5361.2	BACKUP version works.	KETJE::PACCO	Gallia divisa est in partes tres	`Thu Jul 22 1993 12:56`	14
	I copied a "backup" version of mcc_script_am to mmexe, and from then it works again. I cannot not explain why, because a diff between old and new version didn't gave any difference. Also I used the MCC_SCRIPT_AM_LOG bits AFTER it already behaved as explained. Can anyone mention which trace bits we can use for "debugging" of "tracing" the script_am ? Regards, Dominique.
5361.3	Cause is different.	KETJE::PACCO	Gallia divisa est in partes tres	`Mon Jul 26 1993 10:45`	2
	Reply 5361.2 is not quite true. In fact I was in another "context". Please read note 5387.0 for more info.