Using Marks's page listed below.

1) We share ISPPROF across all lpars of the shared dasd systems.

2) Edit on other plex/lpar is blocked by ENQ/GRS.

So it sounds like ISPPROF corruption.  Which is consistent w/periodically 
getting thrown into a false recovery.

If I read the information correctly, it would require ISPF to handle 
ISPPROF differently for us to get relief.  At least now I know what the 
problem is.

It also sounds like I could write code to read ISPPROF and find out which 
datasets are"dead" and at least age them.

IBM Mainframe Discussion List <[email protected]> wrote on 05/25/2007 
02:39:19 PM:

> On Fri, 25 May 2007 14:17:24 -0400, Kirk Talman <[EMAIL PROTECTED]> 
wrote:
> 
> >Have problem under 1.8.  Had problem under 1.7 & 1.4.  Oldest one of 
131
> >total is now 2 yrs old.  The only advice I got was to "delete ISPPROF 
and
> >see if that helps."  Kind of answer I would expect from M$weenie not
> >IBMsysprog.
> >
> >If you get a viable solution let me know.
> >
> >fyi our main system is three plexes w/shared dasd.  DSL w/mask of
> >*.ISR*.BACKUP shows 10260 datasets.
> >
> 
> What exactly is the problem?   Just that the data sets are out there? 
This
> can happen if your session is canceled.  Or is it that you edit 
something
> and expect to go into recovery and don't - so therefore the recovery 
files
> sit out there forever.   If you use the same userid(s) on multiple LPARs
> there is a valid explanation for that and it is WAD (or BAD).
> 
> See "ISPF Considerations" in $SNGLTSO on my web site in the
> JOBs/DOC section or CBT file 434:
> http://home.flash.net/~mzelden/mvsfiles/$sngltso.txt
> 
> Mark


-----------------------------------------
The information contained in this communication (including any
attachments hereto) is confidential and is intended solely for the
personal and confidential use of the individual or entity to whom
it is addressed. The information may also constitute a legally
privileged confidential communication. If the reader of this
message is not the intended recipient or an agent responsible for
delivering it to the intended recipient, you are hereby notified
that you have received this communication in error and that any
review, dissemination, copying, or unauthorized use of this
information, or the taking of any action in reliance on the
contents of this information is strictly prohibited. If you have
received this communication in error, please notify us immediately
by e-mail, and delete the original message. Thank you

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

Reply via email to