ZWESVSTC fails to start - can't execute run-zowe.sh

[John-A-Davies]

Describe the bug
Zowe server ZWESVSTC fails to start because it can't execute run-zowe.sh. This is because user ZWESVUSR can't traverse the instance directory along the path to run-zowe.sh due to file permissions and ownership of the instance directory's parent directory.

To Reproduce
Steps to reproduce the behavior:

1. install zowe
2. run zowe-configure-instance.sh -c zowe-instance-dir
3. run zowe-instance-dir/bin/zowe-start.sh
4. See error in JESMSGLG

ICH408I USER(ZWESVUSR) GROUP(ZWEADMIN) NAME(J. A. DAVIES        ) 
  /u/userid1/zowe-instance-dir/bin/internal/run-zowe.sh           
  CL(DIRSRCH ) FID(F3C2C8F0F0F45A260000000000010001)              
  INSUFFICIENT AUTHORITY TO STAT                                  
  ACCESS INTENT(--X)  ACCESS ALLOWED(GROUP      ---)              
  EFFECTIVE UID(0000000271)  EFFECTIVE GID(0000000215)            
ICH408I USER(ZWESVUSR) GROUP(ZWEADMIN) NAME(J. A. DAVIES        ) 
  /u/userid1/zowe-instance-dir/bin/internal/run-zowe.sh           
  CL(DIRSRCH ) FID(F3C2C8F0F0F45A260000000000010001)              
  INSUFFICIENT AUTHORITY TO LSTAT                                 
  ACCESS INTENT(--X)  ACCESS ALLOWED(GROUP      ---)              
  EFFECTIVE UID(0000000271)  EFFECTIVE GID(0000000215)            

and in STDERR
/u/userid1/zowe-instance-dir/bin/internal/run-zowe.sh: /u/userid1/zowe-instance-dir/bin/internal/run-zowe.sh: not found

Expected behavior
ZWESVSTC starts without these errors

Additional context
This is a very common mistake. It's because the user installing Zowe creates the zowe-instance-dir but does not set the permission of its parent directory (often the user's home directory) to allow ZWESVUSR to traverse it.

The installation script must not alter the permissions of that parent directory, but at least we should warn the user to do so.

[MarkAckert]

Zowe v1 is end of life.