Conference clusta::acms

4158.0. "DCL available close_error, insufficient privilege?" by KERNEL::PULLEY (Come! while living waters flow) Fri Apr 25 1997 07:08

Hi,

I've the following from my customer.
A couple of additions to his text:-
I think there are some display Cobol statements in at least the termination
procedure for teh server.
We think the error occurs during the terminantion.

Thanks for any comments or suggestions,
Steve.

Node Star7, Alpha VMS V6.2 ACMS V4.1-0 

We have a problem with a procedure server called CLIENT_SEARCH_SERVER which 
has the sub-clause DCL AVAILABLE set.  This is required to use a DCL symbol.

Since the sub-clause was set the following error occurs on using the task..

From SWLUP: 

%COB-F-CLOSE_ERROR, unknown error during CLOSE SYS$OUTPUT:.;
-RMS-E-PRV, insufficient privilege or file protection violation

I've tried trapping the problem via OPCOM/AUDIT without success. 
SYS$OUTPUT is defined in the Server, but even if it's not we still get the
error. I've given the server BYPASS priv, - still occurs.

Please see ADF and GDF extracts below....

ADF....

 Server given name : CLIENT_SEARCH_SERVER            Appl. server index: 1
 Server username   : ISTSSTRS_SRV                    Username attribute: FIXED
 Owning task group : GQSA_GDF                        Audit enabled     : YES
 Server proc. range: 1 TO 2                          Wksp protected    : YES
 Process dump      : DISABLED
 Default directory : CLT$ONLINE:
 Creation interval (sec): 10         Creation delay (sec): 10
 Deletion interval (sec): 15         Deletion delay (sec): 30
 Server name tables: (total of 0)
 Server logicals   : (total of 18)
   DIR$CLIENT_SEARCH = "clt$online:"
   SYS$OUTPUT = "CLIENT_SEARCH.LOG"
   GQS$EXE = "$1$DUA1230:[ISTS_STRS_PROD.INFOSYS]"
   BASIS$SYS = "DISK$BASIS_FILES3:[BASIS.SYS]"
   CLT$ONLINE = "DISK$BASIS_FILES3:[DMROOT.ALPHA.EXE]"
   GQS$ALPHA = "DISK$BASIS_FILES3:[DMROOT.ALPHA.EXE]"
   ERIN_BP_SHAREABLE_ALPHA = "gqs$alpha:ERIN_BP_SHAREABLE_ALPHA.EXE"
   BASISPLUS_ERRLOG_FILE = "gqs$exe:BASIS_ERROR_LOG.idx"
   SECURITY_FILE = "gqs$exe:SEARCH_SECURITY.IDX"
   CIVIL_SERVANTS = "gqs$exe:CIVIL_SERVANT.IDX"
   TITLES_FILE = "gqs$exe:TITLES.FIL"
   DM$ = "DM$L1G:[DM]"
   DM$CCF = "DM$CCFA:"
   DM$CCFA = "DM$RUNDMKA:DMCCFILE.CCF"
   DM$KD1 = "DM$:DMKD1.KDF"
   DM$KD2 = "DM$:DMKD2.KDF"
   DM$RUNDMK = "DM$RUNDMKA:"
   DM$RUNDMKA = "$1$MDA1:[DM.RUNDMK]"



GDF ....

 Group server name  : CLIENT_SEARCH_SERVER              Server index : 1
 Server username    : USERNAME OF APPLICATION           Server type  : PROCEDURE
 Rundown on cancel  : YES                               Reusable     : YES
 DCL available      : YES
 Username attribute : NOT EXPLICITLY SPECIFIED
 Server image file  : "GQS$ALPHA:CLIENT_SEARCH_SERVER.EXE"
 Execute termination procedure: ALL RUNDOWNS THAT ARE NOT DUE TO CANCEL
 Initialization procedure     : CLIENT_SEARCH_SERVER_INIT
 Termination procedure        : CLIENT_SEARCH_SERVER_TERM
 Procedure list -
     DECF_CLIENT_SEARCH_TASK_INIT                                1
     CLIENT_SEARCH_INIT_WSP                                      2
     CLIENT_SEARCH_TO_DECF                                       3
     CLIENT_SEARCH_DECF_CONV                                     4
     CLIENT_SEARCH_BP                                            5
     CLIENT_SUMM_RETRIEVE_BP                                     6
     CLIENT_FULL_RETRIEVE_BP                                     7
     FIX_NAME                                                    8
     CLIENT_SEARCH_SERVER_INIT                                   9
     CLIENT_SEARCH_SERVER_TERM                                   10

    
    	The logical names SYS$INPUT, SYS$OUPUT, and SYS$ERROR
    	are used to pass the server logical names to the servers.
    	I wonder if there's some mixup with the definition
    	re-defining SYS$OUTPUT.  Can they try to invoke
    	this image via a DCL command procedure changing
    	SYS$OUTPUT in the command procedure?
    
    	Normally a language like COBOL open the 'console TT'
    	for normal input/output and closes them on exit.  For
    	some reason, Cobol has a problem closing the channel.
    
    	Is this something they started using and found the problem
    	or is it something that's worked for years and now has
    	started to fail?
    
    	Bill
    

    Hi Bill,
    
    It's something they've just started doing.
    They are using DCL available to try to handle a DCL symbol in their
    procedure server, or something like that.
    I'll try them with whether they can run their image in a DCL server.
    
    Thanks,
    Steve.