Conference ssdevo::hsj40_product

1222.0. ""dir" kill the program,how about v3.0" by TPOVC::CHARLESCHANG () Wed Mar 19 1997 11:16

Hello 

 Does "directory" kill the program problem will be solved in HSJ40 Modular
Array Controller Version 3.0 ? Attached please find the problem description.

Thanks advance any help.

regards,

- Charles -


Subj:	[HSD30,HSJ40] CLI Hangs & Eventually Returns %HSCPAD-F-NOLOC

[HSD30,HSJ40] CLI Hangs & Eventually Returns %HSCPAD-F-NOLOCEXE Error


COPYRIGHT (c) 1988, 1993 by Digital Equipment Corporation.
ALL RIGHTS RESERVED. No distribution except as provided under contract.

Copyright (c) Digital Equipment Corporation 1996. All rights reserved.

PRODUCTS:   StorageWorks HSD30 Array Controller, Version 2.7D
            HSJ40 Modular Array Controller, Version 2.7

OP/SYS:     OpenVMS VAX
            OpenVMS Alpha

COMPONENT:  Command Language Interpreter (CLI)

SOURCE:     Digital Equipment Corporation


SYMPTOM 1:

After executing the HSJ or HSD DIRECTORY command, the CLI hangs.  In
addition, you cannot re-set host to an HSJ or HSD.  The following
scenario demonstrates the reported behavior:

     $ SET HOST/DUP/SERVER=MSCP$DUP/TASK=CLI HSJnn

     HSJ> DIRECTORY

     HSUTILV27J   D
     C_SWAPV27J   D
     CFMENUV27J   D
     CHVSN V27J   D
     CLCP  V27J   D
     CLI   V27J   D
     CLONE V27J   D
     CONFIGV27J   D
     CRASH V27J   D
     DILX  V27J   D
     DIRECTV27J   D
     FLS   V27J   D
     FMU   V27J   D
     TILX  V27J   D
     VTDPY V27J   D

At this point, you should receive the CLI back, but do not.  The
escape sequence "^\" places you back at the OpenVMS DCL interface.
However, you can no longer SET HOST/DUP/SERVER=MSCP$DUP/TASK=CLI back
to the HSJ.

SDA shows that there are no MSCP$DUP connections to the HSJ.  However,
the HSJ thinks there are because the new SET HOST command fails with
the following error messages:

     %HSCPAD-F-NOLOCEXE, Local program not executing
     -SYSTEM-F-PGMLDFAIL, program load failure
     %HSCPAD-S-END, Control returned to node NODENM 


SYMPTOM 2:

The command language interpreter (CLI) hangs and eventually returns
the following errors and fails the disks over:

     %HSCPAD-F-NOLOCEXE, Local program not executing
     -SYSTEM-F-PGMLDFAIL, program load failure

The disks continue to operate successfully even though the CLI is
hung.  After some time has passed (38 minutes in one reported case),
the CLI may work for one or two commands before it hangs again.  The
HSD idle time is 97% so the HSD is not saturated.  All other
operations appear normal.  The hang may occur on the console, through
DUP, or both.


DIGITAL RESPONSE:

Engineering has acknowledged this problem and plans to address it in a
future release. 


WORKAROUND 1:

To obtain directory information from the HSJ or HSD use one of the
following two commands:

     $ SET HOST/ DUP/SERVER=MSCP$DUP/TASK=DIRECT HSDxx

     or,

     $ SET HOST/ DUP/SERVER=MSCP$DUP/TASK=DIRECT HSJxx
     
This prints out the directory information without hanging the HSJ or
HSD.

After you receive the directory of the commands, save them and enter
the controller next with /TASK=CLI to run the programs you want.


WORKAROUND 2:

Hard reset the controller.

Since there is not going to be a V3.0 for HSJ/D the answer is no.  Talk
to the product manager as to when V3.1 will be available.

    Hello
    
     Thanks a lot.
    
    
    regards,
    
    
    - Charles -