Anybody remember my problem of a dataset ENQ conflict message which we
couldn't figure out? The one where an IDCAMS step with a DELETE said the
DSN was in use, but we couldn't find out who was using it? I reproduced
the problem with the following JCL:
<jcl>
//STEP1 EXEC PGM=IDCAMS,COND=(0,NE)
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE TSSTV.PR.GCRMANBL
DEFINE CLUSTER -
(NAME('TSSTV.PR.GCRMANBL') -
INDEXED -
KEYS(57 0) -
RECORDSIZE(1678 1678) -
FREESPACE(5 5) -
SHAREOPTIONS(2 3) -
SPEED -
BUFFERSPACE(18432)) -
DATA -
(NAME('TSSTV.PR.GCRMANBL.DATA') -
VOLUMES(* * * * * * * * * * * * * * * * * * * * * *) -
CYLINDERS(100 100) -
CONTROLINTERVALSIZE(8192)) -
INDEX -
(NAME('TSSTV.PR.GCRMANBL.INDEX') -
VOLUMES(* * * * * * * *) -
TRACKS(30 30) -
CONTROLINTERVALSIZE(2048))
//STEP070 EXEC PGM=VSAMINIT
//*
//SYSPRINT DD SYSOUT=*
//DATASET DD DISP=SHR,DSN=TSSTV.PR.GCRMANBL
//SYSUDUMP DD SYSOUT=*
</jcl>
Nothing there, right. The problem was some sort of conflict between
MIM/Integrity and GRS, due to stupidity on my part. Our MIM parameters
were from many years ago, when we actually used MIM to serialize DSNs
between two OS/390 systems via DASDONLY communications. I had totally
forgotten about them. Well, when I had GRS and MIM both trying to manage
cross system SYSDSN enqueues, the problem occurred. I changed MIM to not
manage the QNAMEs that GRS is managing and the problem went away.
Surprise! Surprise! Surprise!
I only confess this in the hopes that my foolishness helps some other
poor sucker later avoid this. Confession is said to be good for the
soul.
This previous Sunday's sysplex test went very well. We only have a few
problems left, and they are minor.
--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology
The information contained in this e-mail message may be privileged
and/or confidential. It is for intended addressee(s) only. If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense. If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.
----------------------------------------------------------------------
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
