A symbolic symbol can be defined as: 'NULL='. I then defined an alias as follows: DEFINE ALIAS (NAME(TEST.NEW.JCL.CNTL) SYMBOLICRELATE(TEST.&NULL.JCL.CNTL)) When I reference TEST.NEW.JCL.CNTL in DSLIST (ISPF 3.4) TEST.JCL.CNTL is displayed. Bill
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Wednesday, July 29, 2015 9:07 AM To: [email protected] Subject: Aliases (was: z/OS 2.2 announcement) On Wed, 29 Jul 2015 14:38:50 +0000, Staller, Allan wrote: > ... >Once *EVERYTHING" has moved to the alias, the original dataset can be deleted >and the process repeated in the other direction. >This make take several (days, weeks, months,....) depending on the >installations policies and procedures. > ... >Merely re-point the existing alias to the new dataset. No problem here. > Is there a utility to enumerate all ALIASes to a given RELATED DSN? If not, there's a problem. The information must exist: if the RELATED DSN is deleted, the ALIASes are quietly deleted. Integrity flaw: deleting a DSN when ALIASes exist ought at least to require confirmation. There's a minuscule timing window. SYMBOLIC aliases would be better; they persist when the referenced data set is deleted. But a SYMBOLIC alias must contain at least one substitutable symbol. Stupid rule! (Might one define a system symbol naming the null string, for incorporation in SYMBOLIC aliases?) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
