ACS rule dataset masking. My ROT is to have each special case in
it's own DATACLAS identifying why it is an exception.
BTW, we also had this happen to us while attempting to get to
extended-format as the shop standard.
At 03:29 AM 10/8/2018, you wrote:
Good day to all,
I see these restrictions for Edit Recovery Datasets from "z/OS ISPF
Planning and Customizing" (z/OS v2.2):
<quote>
These restrictions apply to edit recovery data sets:
They must be allocated as sequential data sets of record format U.
They cannot be striped, or striped and compressed data sets.
They cannot be multivolume data sets.
<end-quote>
One of my Storage Admin guys changed (to resolve an unrelated
problem) the default SMS Data class to have 'DATA SET NAME TYPE' as
EXTENDED and other new attributes resulting in that the ISPF
Recovery datasets are 'striped'.
Which means that I see 'Recovery suspended-error' in an ISPF Edit
session and a long description what was wrong.
I also see this: IGD17070I DATASET ?.ISP7195.BACKUP ALLOCATED
SUCCESSFULLY WITH 1 STRIPE(S).
... then a IGD101I followed by IGD105I where it was deleted immediately.
That change was reversed eventually because of the allocation error,
but it may be needed to re-apply the new changes in the Data class.
Question:
Where can I change the allocation behaviour of ISPF to force another
Dataclass to be selected? I already looked at ISPCCONFIG, but there
is nothing about selecting right SMS class(es).
If that is not possible, is it Ok to rather create a Data Class rule
where <?>.ISP*.BACKUP datasets are assigned to another dataclass? Or
are there better solutions?
Many thanks in advance.
Groete / Greetings
Elardus Engelbrecht
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
