I have a task that allocates a few GDG files during its running instance.
I allocated one instance of a GDG and got the G0207V00 extension.
4 seconds later, I allocated another instance (different DDNAME) and got
the very same G0207V00.
It would appear that the first 207 instance was "deferred.". And that
before it could be 'rolled in', we had allocated another instance of the
GDG.
This is not an isolated instance. It seems to happen a handful of
times over several hours.
The time distance between 1st and 2nd instance of same dsn allocation
appears to be about 3 to 5 seconds.
The same program is doing the allocation in all instances.
The program issues a step level exclusive ENQ on a resource that covers...
1. allocation of file.
2. open of the file.
3. first record write of file.
I then release the ENQ, to allow other instances in the region to do the
same.
I have many copies of the program doing the same allocation. All
instances should be serialized as above.
I would have thought this long enough for SMS to finish its work.
Perhaps not.
One instance of the JES log information shows...
>> 19.17.35 JOB01841 IGD101I SMS ALLOCATED TO DDNAME (DXML4302)
001
>> 001 DSN
(CHK.C13U00.S2.DUPDXML.G0207V00
)
>> 001 STORCLAS (SCPROD) MGMTCLAS (MCPRDGDG)
DATACLAS ( )
>> 001 VOL SER NOS=
PNK019
>> 19.17.39 JOB01841 IGD17356I GDG RECLAIM REQUEST WAS SUCCESSFULLY
PROCESSED FOR DATA SET CHK.C13U00.S2.DUPDXML.G0207V00
>> 19.17.39 JOB01841 IGD101I SMS ALLOCATED TO DDNAME (DXML8212)
022
>> 022 DSN
(CHK.C13U00.S2.DUPDXML.G0207V00
)
>> 022 STORCLAS (SCPROD) MGMTCLAS (MCPRDGDG)
DATACLAS ( )
>> 022 VOL SER NOS=
PNK019
>> 19.17.39 JOB01841 IGD107I
CHK.C13U00.S2.DUPDXML.G0207V00 ROLLED IN,
DDNAME=DXML8212
>> 19.17.40 JOB01841 IGD07003I DXML4302-GDS PREVIOUSLY ROLLED
IN
>> 19.17.40 JOB01841 IGD104I
CHK.C13U00.S2.DUPDXML.G0207V00 RETAINED, DDNAME=DXML4302
I can guess that the system is trying to add the new GooVoo value to the
GDG but cannot since the prior one is already added.
Does anyone know what I'm missing here?
Is there something behind the scenes in SMS that might be tripping me up?
Would a non-SMS managed GDG eliminate this problem?
Perhaps I should add a delay as step 4 in my comments above to wait say
about 3 to 6 seconds or so before allowing the next allocation request
to start?
Any help would be appreciated.
regards,
Mark Vollmer
----------------------------------------------------------------------
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
