Just to be clear, "RENAME" in the contexts of STOW and IEBCOPY are not the same.
In the case of STOW, an existing member is truly renamed. In the case of IEBCOPY, a copied member is merely assigned an alternate name. Cutting an SMF record for member rename would be misleading. As for "older utilities", IEBCOPY is one that has kept up with current developments, cf. IEHMOVE. = = > Date: Tue, 2 Apr 2013 13:17:25 -0700 > From: [email protected] > Subject: Re: SMF type 42 record - Renaming PDSE member > To: [email protected] > > Actually I think sometimes the older utilities are a bit behind the new > technology. > > PDS/E and IEBCOPY are ones that I would suspect need to catch up to each > other. > > So a bug - probably not. > A technology issue - probably/possibly. > > IEBCOPY is very old and to change it requires a lot of work. > > Starting with z/OS V1.13 there is a new utility called IEBPDSE that may > address that issue. > > At Share in Aug 2010 (I think) was a presentation on IEBCOPY. IBM gave an > hour (or so) presentation on all the enhancements to IEBCOPY. And what was > amazing was the room that holds 20 was over flowing out into the hallway. It > amazed a few of us that there was such a high interest on IEBCOPY > > > Lizette > > > -----Original Message----- > >From: Jose ADAUTO Ribeiro <[email protected]> > >Sent: Apr 2, 2013 12:57 PM > >To: [email protected] > >Subject: Re: SMF type 42 record - Renaming PDSE member > > > >Hi, > > > >I think too. The iebcopy is widely used to run out of this facility. > >But the ISPF/Edit don't use STOW (or DSERV) to rename a member only when the > >file is a PDSE? > > > >José ADAUTO Ribeiro > > > > > > > > > > > >Em 02/04/2013 16:00, Schumacher, Otto < [email protected] > escreveu: > >Lizette, > >Do you not feel like there is a whole in the SMF collection process created > >by IEBCOPY? The omission to create the SMF 42 type 25 records to document > >the changes to members of a PDS/ PDSE results in an inability to produce an > >accurate audit of member change activity. > > > >Regards > >Otto H Schumacher > >Transaction and Database Systems – CICS Specialist > >U. S. Mainframe > >HP Enterprise Services > >Telephone +1 864 987 1417 > >Mobile +1 864 569 5338 > >Email [email protected] > > > > > > > > > >-----Original Message----- > >From: IBM Mainframe Discussion List [mailto:[email protected]] On > >Behalf Of Lizette Koehler > >Sent: Tuesday, April 02, 2013 1:57 PM > >To: [email protected] > >Subject: Re: SMF type 42 record - Renaming PDSE member > > > >According to the SMF Manual > > > >Subtype 25 is written when a member is renamed from a PDS or a PDSE to > >indicate who or what (job, started task, or TSO user) renamed the member. It > >contains the name of the data set and the volume serial of the volume on > >which it resided, as well as the old name and new name of the member. > > > >Only those applications that issue STOW and DESERV calls for PDS or PDSE > >directory processing will generate Subtype 25 records. Some applications, > >such as IEBCOPY, do not issue a STOW or DESERV when updating the directory. > >Thus, a subtype 25 record will not be created. > > > >What process are you using for renaming a member in a PDS/E? > >Can you verify if you do a RENAME using DESERV you get a subtype 25 and if > >you use IEBCOPY with rename you do not? > > > > > >Lizette > > > > > >-----Original Message----- > >>From: Jose ADAUTO Ribeiro <[email protected]> > >>Sent: Apr 2, 2013 10:18 AM > >>To: [email protected] > >>Subject: SMF type 42 record - Renaming PDSE member > >> > >> > >>Hi, all. > >> > >>I am collecting SMF type 42 records to report changes (creations and > >>renaming) of PDS and PDSE members, but for PDSE it is not being written > >>record 42 (subtype 25) when renaming a member. > >> > >>Someone know about this? Is it a bug? Is there another way to take this > >>information? > >> > >>I'm using z/OS 1.12. > >> > >>Thanks in advance. > >> > >>José ADAUTO Ribeiro > >> > >> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
