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

Conference turris::decc

Title:DECC
Notice:General DEC C discussions
Moderator:TLE::D_SMITHNTE
Created:Fri Nov 13 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2212
Total number of notes:11045

2151.0. "dec v5.5 Vax install error" by SANITY::DAVIS () Fri Apr 11 1997 12:30

    I was upgrading (VAX) DEC C from 5.3 to 5.5 using the SSB kit March
    1997 - cluster running vms v6.2.
    
     Installation failed with the following error
    
    Cluster member WOOZY is affected by installation
    %DELETE-W-FILNOTDEL, error deleting
    DSA0:[SYS9.SYSUPD.CC055]SYSMAN.COM;1
    %DCL-W-USGOTO, target of GOTO not found - check spelling and presence
    of label
    %DCL-W-USGOTO, target of GOTO not found - check spelling and presence
    of label
    %DCL-W-USGOTO, target of GOTO not found - check spelling and presence
    of label
    %VMSINSTAL-E-INSFAIL, The installation of CC V5.5 has failed.
    %DELETE-W-FILNOTDEL, error deleting
    DSA0:[SYS9.SYSUPD.CC055]CCXX$STARTUP.COM;1
    -RMS-E-FLK, file currently locked by another user
    %DELETE-W-FILNOTDEL, error deleting
    DSA0:[SYS9.SYSUPD.CC055]SYSMAN.COM;1
    -RMS-E-FLK, file currently locked by another user
    %DELETE-W-FILNOTDEL, error deleting DSA0:[SYS9.SYSUPD]CC055.DIR;1
    -RMS-E-MKD, ACP could not mark file for deletion
    -SYSTEM-F-DIRNOTEMPTY, directory file is not empty
    
    
            VMSINSTAL procedure done at 10:50
    
    
    Is this a known problem?  Has anyone else seen this?
    
    
    thanks
    linda
    
T.RTitleUserPersonal
Name
DateLines
2151.1Some possibilitiesDECC::ERICWMon Apr 21 1997 16:0136
I understand the error messages, but it is not entirely clear to me why that is
happening.

The file VMI$KWD:SYSMAN.COM is created by the installation procedure itself and
then after executing it, the file is deleted.  If the delete fails, then I
suspect that something unusual is happening on your system.

A couple of possibilities might be:
  1. Do a DIR/OWNER on the file after the failure.  Is the owner the account
     that ran VMSINSTAL?  If not, perhaps the protections on parent directories
     are not set up right so that when the file is created, it gets created with
     an owner other than the current account.

  2. Is the process default protection set to an unusual setting which would
     disallow a file to be created then deleted without an intervening
     SET PROTECTION command?  You can check this by logging into that account
     and creating then deleting a file... any file.

  3. Is there another process running concurrently that might be performing
     installations or setting protections on the files your
     process created?  The message "file currently locked by another user"
     implies it is a possibility.

  4. Was there any other unusual system activity at the time of installation.

  5. Did you run this from a privileged account?  (I think VMSINSTAL ensures
     it)

  6. There was a bug that was discovered in the KITINSTAL in the vicinity of
     where you are having trouble.  It was caused by SYSMAN not returning a
     value for the logical SYS$SYSDEVICE on any one of the nodes in your
     cluster.  You could test that by saying SHOW LOGICAL SYS$SYSDEVICE on
     each cluster node.  If any of the nodes gives an error, then perhaps
     that bug is what is at play here.

Eric
2151.2???CSC32::J_HENSONDon't get even, get ahead!Thu May 22 1997 17:297
I have a customer reporting the same problem as in the basenote.  Can
anyone tell me what the resolution was on the original post?  I
asked the customer to try the items  in .1, but it didn't help much.

Any more suggestions?  

Jerry
2151.3%DCL-W-USGOTO result of read/error=doneCSC32::D_SANFORDFri May 23 1997 18:3861
    The plot thickens...  The KITINSTAL.COM in CC055 has a bug!
    
    $ if loc .ne. f$length(line)
    $ then
    $       node_context = f$extract(loc+26,30,line)
    $       read/error=done infile other_nodes_disk
    $       other_nodes_disk = f$edit(other_nodes_disk,"TRIM,UPCASE")
    $       if other_nodes_disk .eqs. my_sysdisk
    $       then
    $               write sysman_file "set env /node=(''node_context')"
    $               write sysman_file sysman_c_line
    $               write sysman_file sysman_cxx_line
    $               write sys$output "Cluster member ''node_context' is
    affected by
    $       else
    $               write sys$output "Cluster member ''node_context' is not
    affecte
    $       endif
    $ endif
    $ goto more_lines
    
    "read/error=done" causes the %DCL-W-USGOTO errors as there is NO
    "done:" label!  Add a "done:" label in the appropriate place and
    no error.
    
    For my customer this failure was the result of SYSMAN not reporting
    information back correctly, in this case:
    
      SYSMAN> set env/cluster
      SYSMAN> do write sys$output
      f$parse("SYS$SYSDEVICE",,,"DEVICE","NO_CONCEAL")
      %SYSMAN-I-OUTPUT, command execution on node CHIC02
      $3$DIA6:
      %SYSMAN-I-OUTPUT, command execution on node CHIC01
      $1$DKA0:
      %SYSMAN-I-OUTPUT, command execution on node DCDEMO
      SYSMAN>
    
    You note on the last command execution nothing is returned!  It does
    not matter which command is issued or if you perform a "DO" command
    on just node DCDEMO, nothing is returned.
    
    To workaround the problem you have two options:
    
      Fix the SYSMAN reporting problem
    
      Modify KITINSTAL.COM, I did the following and did not verify
      if it is the correct change:
    
    $ endif
    $done:
    $ goto more_lines
    $done_nodes:
    
    I just added a "$done:" where I think it should be.
    
    Please let me know if a formal SPR is needed for this to be fixed
    in a future release of DEC C.
    
    Regards, Drew Sanford
    Customer Support Center
2151.4KITINSTAL.COM output causing %DCL-W-USGOTOCSC32::D_SANFORDFri May 23 1997 18:43132
  The files could not be deleted from the VMI$KWD: because the command
  procedure had them open!


  From SYSMAN which caused initial problem:

SYSMAN> do write sys$output f$parse("SYS$SYSDEVICE",,,"DEVICE","NO_CONCEAL")
%SYSMAN-I-OUTPUT, command execution on node CHIC02
$3$DIA6:
%SYSMAN-I-OUTPUT, command execution on node CHIC01
$1$DKA0:
%SYSMAN-I-OUTPUT, command execution on node DCDEMO
SYSMAN>


  Output from KITINSTAL.COM:

@sys$update:vmsinstal cc055 WCS_DATA_1:[SOFTWARE]
.
.
.

$!      Now figure out the nodes that share the same system disk
$!      with this node.  Then, deassign logicals on those nodes.
$!
$ my_sysdisk = f$edit(f$parse("SYS$SYSDEVICE",,,"DEVICE","NO_CONCEAL"),-
  "TRIM,UPCASE")
$ define/user sys$output vmi$kwd:sysdisks.txt
$!
$ mcr sysman
set env/cluster
do write sys$output f$parse("SYS$SYSDEVICE",,,"DEVICE","NO_CONCEAL")
exit
$!
$ open/read infile vmi$kwd:sysdisks.txt
$ open/write sysman_file vmi$kwd:sysman.com
$more_lines:
$ read/error=done_nodes infile line
$ loc = f$locate("command execution on node",line)
$ if loc .ne. f$length(line)
$ endif
$ goto more_lines
$more_lines:
$ read/error=done_nodes infile line
$ loc = f$locate("command execution on node",line)
$ if loc .ne. f$length(line)
$ endif
$ goto more_lines
$more_lines:
$ read/error=done_nodes infile line
$ loc = f$locate("command execution on node",line)
$ if loc .ne. f$length(line)
$ endif
$ goto more_lines
$more_lines:
$ read/error=done_nodes infile line
$ loc = f$locate("command execution on node",line)
$ if loc .ne. f$length(line)
$ endif
$ goto more_lines
$more_lines:
$ read/error=done_nodes infile line
$ loc = f$locate("command execution on node",line)
$ if loc .ne. f$length(line)
$ then
$       node_context = f$extract(loc+26,30,line)
$       read/error=done infile other_nodes_disk
$       other_nodes_disk = f$edit(other_nodes_disk,"TRIM,UPCASE")
$       if other_nodes_disk .eqs. my_sysdisk
$       else
$               write sys$output "Cluster member CHIC02 is not affected by
insta
llation"
Cluster member CHIC02 is not affected by installation
$       endif
$ endif
$ goto more_lines
$more_lines:
$ read/error=done_nodes infile line
$ loc = f$locate("command execution on node",line)
$ if loc .ne. f$length(line)
$ then
$       node_context = f$extract(loc+26,30,line)
$       read/error=done infile other_nodes_disk
$       other_nodes_disk = f$edit(other_nodes_disk,"TRIM,UPCASE")
$       if other_nodes_disk .eqs. my_sysdisk
$       else
$               write sys$output "Cluster member CHIC01 is not affected by
installation"
Cluster member CHIC01 is not affected by installation
$       endif
$ endif
$ goto more_lines
$more_lines:
$ read/error=done_nodes infile line
$ loc = f$locate("command execution on node",line)
$ if loc .ne. f$length(line)
$ then
$       node_context = f$extract(loc+26,30,line)
$       read/error=done infile other_nodes_disk
$       other_nodes_disk = f$edit(other_nodes_disk,"TRIM,UPCASE")
$       if other_nodes_disk .eqs. my_sysdisk
$       else
$               write sys$output "Cluster member CHIC01 is not affected by
installation"
Cluster member CHIC01 is not affected by installation
$       endif
$ endif
$ goto more_lines
$more_lines:
$ read/error=done_nodes infile line
$ loc = f$locate("command execution on node",line)
$ if loc .ne. f$length(line)
$ then
$       node_context = f$extract(loc+26,30,line)
$       read/error=done infile other_nodes_disk
%DCL-W-USGOTO, target of GOTO not found - check spelling and presence of label
%DCL-W-USGOTO, target of GOTO not found - check spelling and presence of label
%DCL-W-USGOTO, target of GOTO not found - check spelling and presence of label
$s = $status
$tmp = f$verify(vmi$debug)
%VMSINSTAL-E-INSFAIL, The installation of CC V0.G has failed.
%DELETE-W-FILNOTDEL, error deleting
$2$DKA300:[SYS0.SYSUPD.CCDIG]CCXX$STARTUP.CO
M;1
-RMS-E-FLK, file currently locked by another user
%DELETE-W-FILNOTDEL, error deleting $2$DKA300:[SYS0.SYSUPD.CCDIG]SYSMAN.COM;1
-RMS-E-FLK, file currently locked by another user
%DELETE-W-FILNOTDEL, error deleting $2$DKA300:[SYS0.SYSUPD]CCDIG.DIR;1
-RMS-E-MKD, ACP could not mark file for deletion
-SYSTEM-F-DIRNOTEMPTY, directory file is not empty