Add CHMOD step to jcl from "6.9. Configure the Web API Server" and "7.1. Configure the z/OSMF Plugin"

When importing the plugin, the zosmf stc user needs write/execute permission on /global/izbr/api/plugin/app to create the symbolic link from /global/zosmf/zoswfx1/data/externalapps/izbr-ui. When running jcl from "6.9. Configure the Web API Server" and "7.1. Configure the z/OSMF Plugin", the directories and files are created under /global/izbr/api/plugin and /global/izbr/api/servers. Permit for OTHERS was set to 0 on /global/izbr/api/plugin/app, causing zosmf being unable to create the symbolic link. Zosmf message IZUG679E then nicely points you in the wrong/different direction (Typically, this error occurs when the z/OSMF data file system is not configured correctly or when the version of Java running on system is not at the correct level.). 
Also, /global/izbr/api/plugin/app/config.json got 640 causing zosmf to be unable to read the file, causing the plugin to not work.

USS processing can have a default UMASK in place that alters the permition bits during creation. UMASK can be set on system and on user level and can have different value for each shop and/or each user.
As these 2 steps only create a handfull of files/directories, can these steps be enhanced with a CHMOD step in the JCL to make sure enough (but not too much) permit is set for all initial files/directories? (And if RWX for Other is too much on /global/izbr/api/plugin/app, perhaps setfacl commands to give rwx to the zosmf stc user.  
i.e. add a step to do
chown -R IZBRSRVU /global/izbr/api/plugin/   
chmod    777      /global/izbr/api/plugin    
chmod    777      /global/izbr/api/plugin/app
chmod    644      /global/izbr/api/plugin/app/config.json
chmod    640      /global/izbr/api/plugin/IZBR.properties        
chmod    640      /global/izbr/api/plugin/IZBR-delete.properties 
etc