If several ZOS User ID use the same RTC ID?
In our client,there is a application installation team with several person.Each person have their own ZOS user id and rtc id.
For load action,component is the smallest part.
Each component has hundreds of files.
So for each installation person,they have to load all components into their private PDS.
But for our client,the ZOS storage is very limited.
So our client ask a question whether several ZOS User ID can use the same RTC ID,which means they can only load one copy for the application on ZOS.
I do some tests ,but I found the answer is no.
Does someone meet the same problem?
Are there some resolutions for this situation?
Thanks a lot!!
For load action,component is the smallest part.
Each component has hundreds of files.
So for each installation person,they have to load all components into their private PDS.
But for our client,the ZOS storage is very limited.
So our client ask a question whether several ZOS User ID can use the same RTC ID,which means they can only load one copy for the application on ZOS.
I do some tests ,but I found the answer is no.
Does someone meet the same problem?
Are there some resolutions for this situation?
Thanks a lot!!
2 answers
Hi
What client are we talking about here? I'm going to guess you are using the ISPF client.
If you are talking about the ISPF client then you are correct. In the 3.0.1.x release the lowest level of source load is the component level. We recognized this as a problem and in the 4.0 release we have been working on allowing load down to the file level. PLease see 146570: Support finer-grained load with ISPF client for details
Something else I think I ought mention is that we have a recommendation of no more than 500 parts per component. This is a general performance related recommendation and one that we have been suggesting to any customers we have been involved with during POC's and migrations
Guy
What client are we talking about here? I'm going to guess you are using the ISPF client.
If you are talking about the ISPF client then you are correct. In the 3.0.1.x release the lowest level of source load is the component level. We recognized this as a problem and in the 4.0 release we have been working on allowing load down to the file level. PLease see 146570: Support finer-grained load with ISPF client for details
Something else I think I ought mention is that we have a recommendation of no more than 500 parts per component. This is a general performance related recommendation and one that we have been suggesting to any customers we have been involved with during POC's and migrations
Guy