Group metadata location

As documented in Metadata location, all push-to-client metadata is stored in a directory structure on top of /var/zexpl/pushtoclient/ when using a setup without group support. The same data layout is maintained when group support is activated, but with a slightly different interpretation of the base directory, /var/zexpl/pushtoclient/:
  • Existing data in /var/zexpl/pushtoclient/ is interpreted as the data for the default group. Exporting to the default group creates or updates the metadata in /var/zexpl/pushtoclient/.
  • Exporting to a group creates or updates the metadata in /var/zexpl/pushtoclient/grouping/<devgroup>, as if this were the base directory instead of /var/zexpl/pushtoclient/. The <devgroup> value matches the group name assigned to a specific group of developers.

Initial product customization creates the grouping/ directory in /var/zexpl/pushtoclient/. The client administrator is responsible for adding the <devgroup>/ directories to /var/zexpl/pushtoclient/grouping/.

Note that during initial product customization, the projects/, install/, and install/responsefiles/ directories are created in /var/zexpl/pushtoclient/. The client administrator must repeat these make-directory actions in /var/zexpl/pushtoclient/grouping/<devgroup>/ if there is a need for group-specific product upgrade scenarios.

The following sample z/OS® UNIX command sequence creates the subdirectories with the correct permission bitmask. The commands should be executed by the client administrator to avoid ownership problems.

saved_umask=$(umask)
umask 0000
cd /var/zexpl/pushtoclient/grouping/
mkdir –m775 <devgroup>
cd <devgroup> 
mkdir –m775 install 
mkdir –m775 install/responsefiles 
mkdir –m775 projects 
umask $saved_umask

See UNIX System Services Command Reference (SA22-7802) for more information about the sample z/OS UNIX commands.