|
View previous topic :: View next topic
|
| Author |
Message |
E.LAI
New User
Joined: 29 Mar 2016
Posts: 3
Location: hk
|
|
|
|
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 |
|
 |
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
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 |
|
|
E.LAI
New User
Joined: 29 Mar 2016
Posts: 3
Location: hk
|
|
|
|
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 |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013
Posts: 917
Location: The Universe
|
|
|
|
| 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 |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
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 |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013
Posts: 917
Location: The Universe
|
|
|
|
| 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 |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
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 |
|
|
E.LAI
New User
Joined: 29 Mar 2016
Posts: 3
Location: hk
|
|
|
|
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 |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013
Posts: 917
Location: The Universe
|
|
|
|
| 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 |
|
|
|
|
