Program Analyzer should install custom rules in writeable USS folder and not in usr/lpp/IBM/akg/cr

Thank you for submitting an idea with IDz, we appreciate your input and suggestions to improve our client experiences. Many of our added enhancements come directly from suggestions from our users like yourself. We?ve spent some time evaluating this idea and have concluded that it is something that can be achieved with no change from the product. Perhaps the following information will help with your request.

Refer to the following documentation here: https://www.ibm.com/docs/en/zos/3.1.0?topic=planning-managing-union-file-system-ufs

The main limitations are
* UFS requires z/OS 2.5 or higher
* UFS is local to a system, so in a sysplex with shared filesystems, things must be duplicated
* updating the (supposedly read-only) product directory outside of UFS results in undefined behavior

work to be done:
* activate Union File System (UFS) in PARMLIB(BPXPRMxx)
FILESYSTYPE TYPE(UFS) ENTRYPOINT(BPXUNINT)

* create this directory structure
mkdir /var/akg
mkdir /var/akg/local
mkdir /var/akg/local/cr
mkdir /var/akg/local/cr/features -> will hold site-specific data
mkdir /var/akg/local/cr/plugins -> will hold site-specific data
mkdir /var/akg/ufs -> UFS mountpoint, data written here will end up in /var/akg/local
mkdir /var/akg/work

* mount writable local dir over read-only product dir on UFS mountpoint
mount -t ufs -o upperdir=/var/akg/local,lowerdir=/usr/lpp/IBM/akg,workdir=/var/akg/work -f akg.ufs /var/akg/ufs

* from now on access CR through the UFS mountpoint for runtime purposes, both for read (AKGCR JCL PROC) or write (add site-specific data)
//AKGCR PROC PATH='/var/akg/ufs'

Notes:
* There is no real need to use sample JCL AKGCRADD, just place your site-specific files in /var/akg/ufs/cr/{plugins|features}
* before applying a PTF, unmount /var/akg/ufs, apply PTF (with SMPE using the /usr/lpp/IBM/akg path) and then remount ufs to avoid undefined behavior