how to start rtc ispf daemon on each LPAR for PLEX zos
The client mainframe is PLEX architect with two LPAR.
RTC server is installed on a non-mainframe.
On zos,we only use rtc ispf client.
The client asked whether we could start daemon on each LPAR.
I try to start a daemon on a LPAR,and start the second daemon on another LPAR,get error message :
failed to acquire alivelock: com.ibm.team.filesystem.client.internal.utils.filesystelock@
and the first daemon can not work normally ,too
Does the RTC ISPF support to start more than one daemon on PLEX ?
If yes,how to do?
thanks~~~
RTC server is installed on a non-mainframe.
On zos,we only use rtc ispf client.
The client asked whether we could start daemon on each LPAR.
I try to start a daemon on a LPAR,and start the second daemon on another LPAR,get error message :
failed to acquire alivelock: com.ibm.team.filesystem.client.internal.utils.filesystelock@
and the first daemon can not work normally ,too
Does the RTC ISPF support to start more than one daemon on PLEX ?
If yes,how to do?
thanks~~~
One answer
Hi
Yes you can have more than one daemon running. Based on the error we think what is probably happening is both of your daemon instances are sharing some config directories/files that can not be shared. What you need to do is create a second RTC ISPF daemon start up procedure (BLZISPFD) and perform the RACF customization associated with that. In the second start up procedure adjust the CNFG parm to use a separate configuration directory (CNFG). In the second configuration directory modify the "ispfdmn.conf" file so that it uses unique values for the following:
ISPF_REGISTRY_DIR
SCM_WORK
ISPF_DAEMON_LOG
We have multiple daemons going on a single LPAR here at the lab to service various different ISPF client levels so this is definitely doable.
Guy
Yes you can have more than one daemon running. Based on the error we think what is probably happening is both of your daemon instances are sharing some config directories/files that can not be shared. What you need to do is create a second RTC ISPF daemon start up procedure (BLZISPFD) and perform the RACF customization associated with that. In the second start up procedure adjust the CNFG parm to use a separate configuration directory (CNFG). In the second configuration directory modify the "ispfdmn.conf" file so that it uses unique values for the following:
ISPF_REGISTRY_DIR
SCM_WORK
ISPF_DAEMON_LOG
We have multiple daemons going on a single LPAR here at the lab to service various different ISPF client levels so this is definitely doable.
Guy