Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Differences between copying members by ISPF 3.3 and IEBCOPY

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF
View previous topic :: :: View next topic  
Author Message
E.LAI

New User


Joined: 29 Mar 2016
Posts: 3
Location: hk

PostPosted: Wed Mar 30, 2016 12:35 pm    Post subject: Differences between copying members by ISPF 3.3 and IEBCOPY
Reply with quote

Hi all,

When we copied members from PDS to PDSE via ISPF 3.3, error messages '*NO-COPY' and '*MIXED' were prompted. By using IEBCOPY, they were copied successfully.

We knew that members were converted PDS's load modules to PDSE's program objects, is there any differences between copying members by ISPF 3.3 and by IEBCOPY from PDS to PDSE?

(The members resided in PDS were repo by IDCAMS)
Back to top
View user's profile Send private message

Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7223

PostPosted: Wed Mar 30, 2016 2:07 pm    Post subject: Reply to: Differences between copying members by ISPF 3.3 and IEBCOPY
Reply with quote

IEBCOPY is the correct way to do this. If IEBCOPY notices that the loadmodule needs to be re-linked/binded to become a Program Object, then it will automatically use the program-binder to do this.

How do you know what is running when you use 3.3?
Back to top
View user's profile Send private message
E.LAI

New User


Joined: 29 Mar 2016
Posts: 3
Location: hk

PostPosted: Wed Mar 30, 2016 2:57 pm    Post subject: Reply to: Differences between copying members by ISPF 3.3 and IEBCOPY
Reply with quote

z/OS 2.1.0>ISPF>z/OS ISPF Planning and Customizing>Planning and customizing>The ISPF Configuration Table>The ISPF Configuration utility>Create/Modify Settings and Regenerate Keyword File>General ISPF Settings Panels

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.f54pc00/isppcgeniset.htm?lang=zh-tw

From the above manual, there is a Modify PDF Configuration Settings panel can be determine 3.3 when to use IEBCOPY.

Figure 7. Modify PDF Configuration Settings panel
Code:
(ISPPMOD3)                       Modify PDF Configuration Settings
 Command ===>                                                                 
                                                                    More:   - +
   Block Size . . . . . 13566         Update Data Set . . . . . . . 0   
   Primary Blocks . . . 200           Profile Data Set  . . . . . . 0   
   Secondary Blocks . . 100           Statements Data Set . . . . . 0   
                                      Listing Primary Quantity  . . 50   
                                      Listing Secondary Quantity    100 
                                      Update Primary Quantity . . . 15   
                                      Update Secondary Quantity . . 30   

 Move/Copy Settings
   Enter "/" to select option
   /  Allow Creation of Move/Copy Target Data Set

   When to Use IEBCOPY
   0  0. Use when processing PDSEs or when using COPYMOD to Copy to a
           Smaller Block Size
      1.  Always use IEBCOPY for Load Modules
      2.  Use IEBCOPY for PDSEs only

   When to use COPY or COPYMOD
  F1=Help      F2=Split     F3=Exit      F7=Backward  F8=Forward   F9=Swap
 F12=Cancel

BTW, please let me know if I misunderstand, thanks
coded (and rest of panel added)
Back to top
View user's profile Send private message
steve-myers

Active User


Joined: 30 Nov 2013
Posts: 460
Location: The Universe

PostPosted: Wed Mar 30, 2016 3:12 pm    Post subject: Re: Differences between copying members by ISPF 3.3 and IEBCOPY
Reply with quote

E.LAI wrote:
... (The members resided in PDS were repo by IDCAMS)
  • IDCAMS will not copy load module members correctly.
  • When copying source members with ISPF statistics, IDCAMS will not copy or reproduce the statistics.
Back to top
View user's profile Send private message
Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7223

PostPosted: Wed Mar 30, 2016 4:15 pm    Post subject: Reply to: Differences between copying members by ISPF 3.3 and IEBCOPY
Reply with quote

I'd be happy using IEBCOPY for everything.

I've not considered using IDCAMS for copying members, perhaps it is "new" (as in "since 1981")? I'll have to check whether there are benefits for non-executable members of a PDS.
Back to top
View user's profile Send private message
steve-myers

Active User


Joined: 30 Nov 2013
Posts: 460
Location: The Universe

PostPosted: Wed Mar 30, 2016 8:42 pm    Post subject: Re: Reply to: Differences between copying members by ISPF 3.3 and IEBCOPY
Reply with quote

Bill Woodger wrote:
... I'll have to check whether there are benefits for non-executable members of a PDS.
You can persuade the Binder to include the member. It will complain, but it will include it. Since the directory entry has been trashed, you have to guess where the entry point is, and guess at the actual module attributes, but other than those considerations, you should produce a valid load module.

As far as I know, there are no benefits for a "load module" that has been copied by IDCAMS (or IEBGENER, for that matter).
Back to top
View user's profile Send private message
Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7223

PostPosted: Wed Mar 30, 2016 9:08 pm    Post subject: Reply to: Differences between copying members by ISPF 3.3 and IEBCOPY
Reply with quote

What I meant was, for plain PDSes, is there any benefit over using IDCAMS rather than IEBCOPY.

I wasn't intending to stick source-code into the binder and hope it produces something useful.
Back to top
View user's profile Send private message
E.LAI

New User


Joined: 29 Mar 2016
Posts: 3
Location: hk

PostPosted: Thu Mar 31, 2016 7:05 am    Post subject: Reply to: Differences between copying members by ISPF 3.3 and IEBCOPY
Reply with quote

First of all, thank you for your repsonses promptly. We copy PDSE / PDS menbers by IEBCOPY instead of IDCAMS now.

Out of curiosity, we just want to know why ISPF 3.3 copied those members unsuccessfully while IEBCOPY copied same members successfully (
Back to top
View user's profile Send private message
steve-myers

Active User


Joined: 30 Nov 2013
Posts: 460
Location: The Universe

PostPosted: Thu Mar 31, 2016 8:37 am    Post subject: Re: Reply to: Differences between copying members by ISPF 3.3 and IEBCOPY
Reply with quote

E.LAI wrote:
... Out of curiosity, we just want to know why ISPF 3.3 copied those members unsuccessfully while IEBCOPY copied same members successfully (
Seems strange to me. I regularly use 3.3 for load modules, though usually 1 at a time.

I understand why IDCAMS won't do load modules. Load modules use the note list feature of PDS data sets and user data in a directory entry, as described in DFSMS Using Data Sets, which requires special attention in a copy, something that IEBCOPY does perfectly, but which IDCAMS does not do.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts ISPF program to set SCRNAME prino TSO/ISPF 5 Fri Sep 30, 2016 2:18 pm
No new posts I am unable to use SWAPBAR ON command... mrsidhu12 TSO/ISPF 3 Thu Sep 01, 2016 1:10 pm
No new posts ISPF Tables Creation newsysprg TSO/ISPF 6 Wed Jul 13, 2016 2:21 pm
No new posts Single step utility for compare and u... ramprakashn JCL & VSAM 5 Fri Apr 29, 2016 3:43 pm
No new posts More ISPF RFE's to vote for prino TSO/ISPF 1 Tue Apr 19, 2016 12:06 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us