Peter, I think you found the best (maybe only) solution available to a non-admin person. Fortunately ISPF is good about finding an existing data set and using it, thus avoiding the pesky problem of where to create a new one.
As Lizette mentioned, there is an ISPF Configuration Utility that allows an installation to specify all kinds of values and defaults. One of these is 'PDF_DEFAULT_UNIT', which we happen to set to 'SYSALLDA'. (This esoteric, by the way, is provided by z/OS. It automatically includes every DASD unit. By contrast, an esoteric like 'SYSDA', if defined, has to be explicitly specified in the IODF for every unit the installation wants included.) Beyond ISPF Config settings, however, are SMS and ACS, which can override other default settings. An application programmer has no influence over such settings other than finding out what brand of whiskey the storage administrator prefers. ;-) . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Farley, Peter x23353 Sent: Thursday, November 30, 2017 11:23 AM To: [email protected] Subject: (External):Re: LMDLIST GROUP option question - How to change/override UNIT(SYSDA)? Gil, The problem here was that the allocation is "under the covers" somewhere in the LMDLIST service, and all I could see was the resulting allocation to the "WORKxx" storage pool. No LMDLIST parameters to affect the allocation method are mentioned in the FM. Pre-allocating the dataset before executing LMDLIST solved the problem. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Thursday, November 30, 2017 2:01 PM To: [email protected] Subject: Re: LMDLIST GROUP option question - How to change/override UNIT(SYSDA)? EXTERNAL: This email originated from outside of Broadridge. Do not click any links or open any attachments unless you trust the sender and know the content is safe. On Thu, 30 Nov 2017 18:03:39 +0000, Farley, Peter x23353 wrote: > >I am using the LMDLIST service with the GROUP option in ISPF to save a list of >certain datasets. The GROUP option saves the list to a dataset with name >&PREFIX.group-value.DATASETS, but it uses UNIT(SYSDA) to create this dataset. > >Is there a way to change the UNIT used by ISPF LMDLIST to a different esoteric >unit value? SYSDA here allocates to a storage pool on WORKxx volumes where >datasets are deleted in a very short time (usually just a few minutes, >sometimes less). We programmers use a different unit esoteric to create >permanent datasets in a different storage pool, and I need LMDLIST to use that >testing unit esoteric in place of SYSDA. > >TIA for any help or RTFM you can provide. > SYSDA? SYSALLDA? Whatever. "Using Data Sets" mentions SYSDA only in examples; SYSALLDA not at all. JCL Ref. mentions SYSDA only in examples, and: SYSALLDA: IBM assigned group-names include SYSALLDA, which contains all direct access devices defined to the system. What does IBM recommend? (Perhaps in Init/Config/Admin?) Aren't there better ways of allocating temporary data sets than by relying on esoteric names? SMS guidelines? (My site once genned a (never online) tape address in SYSALLDA.) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
