I believe that IBM has correct this issue with z/OS 1.13. Check the anoucement
letters to verify.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET
Since this makes most uses of a GDG single threaded, would it make
sense to force large GDG files to VTAPE from disk? I assume this
would be implemented with statements in the ACS routine? Anyone have
a sample?
On Fri, Aug 5, 2011 at 10:03 AM, Joel C. Ewing jcew...@acm.org wrote:
On 08/05/2011
Thanks a lot, now i know it is a normal behaviour.
See you,
Enrique Montero
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the
Hi team,
This time is an HSM question related to a GDG dataset.
The problem description :
JOBA is recalling of a large dataset from ML2 to DASD. MY.DATASET.(0).
JOBB during the JOBA recalling creates a new version of the dataset
MY.DATASET.(+1)
JOBB waits until the recall from JOBA ends.
Questions :
During a GDG recall, the HSM keep in exclusive mode all versions of the
dataset and
cannot create new versions till tne recall ends?
Is it normal behaviour of the HSM or is there some parameter to avoid
this?
Best regards and happy weekend.
Enrique Montero
It is normal
Insurance Company.SM
-Original Message-
From: IBM Mainframe Discussion List
[mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lizette Koehler
Sent: Friday, August 05, 2011 6:49 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: GDG recall ENQ IEF861I IEF863I IEF099I
Questions :
During
On 08/05/2011 06:49 AM, Lizette Koehler wrote:
Questions :
During a GDG recall, the HSM keep in exclusive mode all versions of the
dataset and
cannot create new versions till tne recall ends?
Is it normal behaviour of the HSM or is there some parameter to avoid
this?
Best regards and happy
7 matches
Mail list logo