. re "But even if the full DSNAMEs were provided, you'd have no way of knowing which PDS actually had the member that was loaded/referenced."
Really? If one knew the names of the PDS' in question, I "assume" one could discern the concatenation order. With that knowledge and the name of the program that was loaded, it should be, somewhat, simple to firgure out which PDS made the contribution. Some simple coding should do the trick... Would it not? On Tue Jun 3 14:07 , Barry Merrill <[EMAIL PROTECTED]> sent: >Unfortunately, the SMF 14 records do NOT contain all DSNAMES. > >Specifically, in the case of interest, whenever there are >concatenated BPAM libraries, (e.g., STEPLIB, JOBLIB, SASLIB, >and even MXG's SOURCLIB DD) you ONLY get the DSNAME of >the FIRST DD in the concatenation. You do get a separate >UCB segment for the second and subsequent contactenations, >but only DEVNR, VOLSER, and EXCPCNT. > > (MXG's 'solution' is to create a false DSNAME=' CONCAT BPAM' > with a blank in the first position, so that if you should > sort the TYPE1415 SAS dataset, those instances will be > printed first - no help with the DSNAME, but at least you'll > know there were missing DSNAMES). > >But even if the full DSNAMEs were provided, you'd have no >way of knowing which PDS actually had the member that was >loaded/referenced. > >Barry Merrill > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
