Attempts made to reference hard-coded /data path

[ian-burnett]

On this system, the /data directory exists, but is not accessible to my user:

MVA1 ~ > ll -d /data
drw-r--r--  2 BPXROOT TSOUSER 0 Nov 18  2020 /data

During terminal interaction I get the following RACF message, although there are no failures in the UNIX System Services console:

ICH408I USER(IBURNET ) GROUP(TSOUSER ) NAME(IAN S BURNETT       ) 981
  /data/zopen/usr/local/zopen/openssl/openssl-3.6.0/ssl/openssl      
  .cnf                                                               
  CL(DIRSRCH ) FID(D7C1C8F0F0F50EAE000000001E5F0A41)                 
  INSUFFICIENT AUTHORITY TO STAT                                     
  ACCESS INTENT(--X)  ACCESS ALLOWED(GROUP      R--)                 
  EFFECTIVE UID(0000000393)  EFFECTIVE GID(0000000005)               

I can trigger this message (twice) by running a zopen info command against a package - presumably that does a call out to a remote server somewhere to check package details.

openssl package information:

MVA1 ~ > zopen info openssl
==> openssl: STABLE 3.6.0
Description:         openssl on z/OS
==> Package
Version:             3.6.0
Release:             20251002_152051
Buildline:           STABLE
Categories:          N/A
GitHub:              https://github.com/zopencommunity/opensslport
License:             https://github.com/zopencommunity/opensslport/blob/main/patches/LICENSE
zopen license:       https://github.com/zopencommunity/opensslport/blob/main/LICENSE
==> Installation Details
Installed:           Yes
Installation Path:   /u/iburnet/zopen/usr/local/zopen/openssl/openssl-3.6.0.20251002_152051.zos
Installation Size:   118.947 MB
==> Test Status
Passed:              297/298 (99%)
==> Package Details
Download Size:       59.08 MB
Commit SHA:          76454eff779e4e46aaa89da2b783f9fbe5e608fb
Community SHA:       c0e4e6b948818720cba79ac6789bb6cdd9226d2e
==> Dependencies
Build:               check_clang, curl, curl, git, git, gzip, gzip, jq, m4, make, perl, sed, tar, tar, zoslib, zoslib
Runtime:             meta

This problem has very similar symptoms to the already-fixed issue 150 in gitport and to the one I have just raised for ncurses as issue 25.