The zconsetup processing feels like a snag in the install
I intend to put my configuration files in /u/zosc/server1... which is shared between LPARs.
If I want to put zOS C on 5 LPARs I have to do
create the /var/zosconnect directory
remount /user/lpp/IBM/zosc*/v3r0beta Read write
run the zconsetup command
remount /user/lpp/IBM/zosc*/v3r0beta Read
On each LPAR.
Both the code for v3, and v3 beta update /var/zosconnect/c3r0
______________
The processing of the script is in essence
mkdir -p /var/zosconnect2/v3r0/extensions
change /usr/lpp/IBM/zosconnect/v3r0beta/wlp/etc/extensions to point to /var/zosconnect2/v3r0/extensions
copy a string into /var/zosconnect2/v3r0/extensions/zosconnect.properties
copy a string into /var/zosconnect2/v3r0/extensions/imsmobile.properties
There is a test to see if the system is OS/390 - use "\n" between two strings , else use the new line character.
a) I think it will always be OS/390
b) both work
so it looks like this code is redundant
It feels like the SMPE/libraries shipped with the product could simply have
/usr/lpp/IBM/zosconnect/v3r0beta/wlp/etc/extensions/zosconnect.properties and
/usr/lpp/IBM/zosconnect/v3r0beta/wlp/etc/extensions/imsmobile.properties
with the appropriate content, and we would not need to do this zconsetup, this making the install process slicker
Just a thought....
regards
Colin