SYSDA is a name that the installation is expected to define and that IBM procs
depended on. I'm not sure how relevant it is in an era of SMS.
________________________________________
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of
Paul Gilmartin <0000042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Thursday, June 29, 2023 12:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How batch create a PDSE2 with Generations?
On Thu, 29 Jun 2023 10:27:23 -0400, David Spiegel wrote:
>Hi Lionel,
>SYSDA is a user-defined esoteric group. SYSALLDA, OTOH, encompasses all
>DASD Units and is built-in to z/OS.
>
I have heard that elsewhere; I'm inclined to believe it. And in the JCL Ref.:
SYSALLDA: IBM assigned group-names include SYSALLDA, which
contains all direct access devices defined to the system.
Hiwever, the JCLRef. contains 58 mentions of SYSDA, mostly in
examples; only 8 of SYSALLDA. That nurtures the widespread
misconception which Lionel shares. The JCL User's Guide has
an even worse imbalance.
Have you a better citation? I can't find one in Using Data Sets.
This merits an RCF.
>On 2023-06-26 11:58, Lionel B. Dyck wrote:
>> ...
>> SYSDA, SYSALLDA, or 3390 - all should work as generic unit types and an
>> optional vol=ser=xxxxxx may be needed if SMS is not active and/or the dasd
>> is not mounted as public.
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
