"IEBCOPY," per se, in no event generates an SMF record. DFSMS generates an SMF record in response to a STOW or DESERV.
IEBCOPY (apparently) contains its own "roll your own" PDS directory manipulation logic rather than STOWs or DESERVs, so whether you call it a rename, an alias, or a re-christening, IEBCOPY never generates nor causes the generation of an SMF Type 42 record. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Gerhard Postpischil Sent: Wednesday, April 03, 2013 10:43 AM To: [email protected] Subject: Re: SMF type 42 record - Renaming PDSE member On 4/3/2013 9:49 AM, John Gilmore wrote: > When a member is copied from a source PDS[E] to another target PDS[E] > and renamed only in the target it is inappropriate to generate an SMF > [record] type 42, action 25 record, which identifies the action of > renaming a source PDS[E] member. Here the source member name is > unchanged; only the new target member is given a different name. However, IEBCOPY is frequently used to generate a larger version of a PDS (more directory blocks for a PDS, more space for either PDS or PDSE, or converting one form to the other). Both the source and target are renamed, and it would be useful in this situation to have a record of member changes. It would be quite appropriate to request a PARM or other option to have an SMF record generated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
