Mark,
I had a discussion at SHARE (long time ago grant you) with an IBM type.
I think I remember this from the discussion.
IEBCOPY is for copying
COPY does not delete the input as it is a copy.
The design was never meant for "moving", ie copy then deleting the
source member.
------------END conversation-----------
I think a solid easily made requirement for a separate utility for
moving members. ie a replacement for IEHMOVE (shudder) can be made.
Ed
On Sep 18, 2013, at 8:36 AM, Mark Zelden wrote:
On Wed, 18 Sep 2013 15:30:14 +0200, Thomas Berg
<[email protected]> wrote:
Moving should come naturally together with copy...)
Exactly how someone new(ish) to the platform would see it. I've
just always
accepted that IEBCOPY didn't do that and I needed another job step to
do the delete.
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
mailto:[email protected]
ITIL v3 Foundation Certified
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/
ateExperts/
----------------------------------------------------------------------
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
