Re: Future ISPF directions



On Tue, 30 Aug 2005 13:23:44 -0700, Edward E. Jaffe
<edjaffe@xxxxxxxxxxxxxxxxxxx> wrote:

>Paul Gilmartin wrote:
>
>>I wondered about the value of PDSE here. Alas, however, our
>>test systems exceed in number and span of releases both limits
>>for SYSPLEX. Using PDSE would aggravate the ENQ logjam.
>>
>>
>
>Just the opposite should be true. It sounds like you're *already*
>sharing a single ISPF profile data set without serialization.
>

It also sounds like he may be sharing between sysplexes (via MII)?
If that's true, then for sure he wouldn't want to use PDSE.

Paul, are you sharing between sysplexes?

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America and Farmers Insurance Group
mailto: mark.zelden@xxxxxxxxxxxx
Systems Programming expert at http://Search390.com/ateExperts/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.



Relevant Pages

  • Re: Future ISPF directions
    ... >>Paul Gilmartin wrote: ... Using PDSE would aggravate the ENQ logjam. ... > It also sounds like he may be sharing between sysplexes? ...
    (bit.listserv.ibm-main)
  • Re: PDSE Sharing
    ... IBM doesn't support sharing PDSE across sysplexes - period. ... I know there are other MIMPLEX sites out there so how do you ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)
  • Re: given the checkered history of stability for PDSEs
    ... I agree that PDSE is here to stay. ... Static PDSE has been no problem. ... All of the problems that I have had have been traced back to sharing issues. ... All corrected by developer education. ...
    (bit.listserv.ibm-main)