And, IIRC, the "dsname" portion is equal to what is specified in the &&DSN portion of DSN=&&DSN. Which, if not specified, is that Rnnnnnn thing defaulted and maintained by allocation somewhere. I don't think that there is any way, off hand, to look at the temp dsn and saying "Oh, that is SORTWK." or anything like that. Unless the application which dies the dynamic allocation uses the equivalent of &&DSN.
On Mon, Aug 19, 2013 at 9:46 AM, John Gilmore <[email protected]> wrote: > Lizette, > > Anciently these names were all generated using the skeleton: > > SYSyyddd.Thhmmss.RA000.jobname.dsname.Hnn > > in which jobname and dsname could, often did, have their own internal > structures. In your example 'DB11DBM1' is clearly part-number-like, > but it is also a licit z/OS jobname. > > For temporary datasets the date and time values are allocation-time ones. > > John Gilmore, Ashland, MA 01721 - USA > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- As of next week, passwords will be entered in Morse code. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
