W dniu 29.07.2021 o 22:50, Paul Gilmartin pisze:
On Thu, 29 Jul 2021 15:47:45 -0400, John Abell wrote:
Why not have them use TSO XMIT files like we do?
Will RECEIVE then allocate (NEW,CATLG) a data set with suitable DSNTYPE,
SPACE, RECFM, LRECL, ...
If the original PDS is large, is there a
To summarize:
1. Not everything can be copied between PDS and PDSE (and vice versa).
Notable examples are program objects, long member names, PDSE v2 member
versions, etc.
2. Despite other possible options there is no harm to read from PDSU to
original PO dataset flavour and then optionally
Multi-step, but universal - you can transfer any number of files and any
file type.
Small assumption: both sides do have DSS.
I use it for VSAM files.
Personally I created small REXX tool which read list of PDS/PDSE and PS
datasets to transport, then XMIT them, then copy them to big PDS, then
Thanks... My mistake - I found my old notes and they mention a Program
Object version number, not PDSE version. So maybe that makes more
sense. During an attempt to IEBCOPY from PDSE to PDS most load members
copied fine, but some newer members failed with:
IEW2606S 4B39 MODULE INCORPORATES
There are PDSE V1 and V2. Never was sure why IBM decided to do that.
There's no significant external difference other than only V2 supports
member generations.
IEBCOPY's unload file format is documented fairly well in an appendix of
the Dataset Utilities manual. I think you were looking at
No, I got that wrong. I should have read the manual instead of relying on
memory, or maybe assumptions. I do cross-load/unloads from time-to-time,
but they must all be non-executables.
Still, it seems like an odd hole in IEBCOPY's functionality.
sas
On Thu, Jul 29, 2021 at 8:37 PM Billy
-dmarc-requ...@listserv.ua.edu]
Sent: Thursday, July 29, 2021 4:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Identifying PDS/E or PDS in IEBCOPY Unload
On Thu, 29 Jul 2021 15:47:45 -0400, John Abell wrote:
>Why not have them use TSO XMIT files like we do?
>
Will RECEIVE then allocate (NEW
Steve, this is from the IEBCOPY doc:
A load module from an unload data set cannot be reloaded into a PDSE as
a program object. The load modules should be reloaded into a partitioned
data set and then the partitioned data set should be copied to a PDSE to
convert the unloaded load module into a
Do PDSE's have format version numbers? I remember (2015) looking at a
problem where IEBCOPY would not copy what I think IBM called a V3 PDSE
member, and that failure could be predicted by looking at a byte pretty
close to the front of the member data (or maybe it was the dir entry)
that was
Where did you get that notion? IEBCOPY can indeed load into a dataset of a
different type than the source. Only exception I know of is from a PDSE
with long aliases.
I'd think your "backup plan" (albeit my first plan), would be to unload the
file into a PDSE and not worry about it until
Subject: Identifying PDS/E or PDS in IEBCOPY Unload
Hey everyone, here is an odd question for y'all.
Is there any way I can tell from an IEBCOPY unload file (that I received from a
vendor) whether it is an unload of a PDS or an unload of a PDS/E?
Since IEBCOPY is pretty particular about only loading
rarely care any more what they are.
Lizette
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Billy Ashton
Sent: Thursday, July 29, 2021 11:37 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Identifying PDS/E or PDS in IEBCOPY Unload
Hey everyone, here is an odd question
problem are you trying to solve by knowing PDS vs PDSe datasets?
I rarely care any more what they are.
Lizette
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Billy Ashton
Sent: Thursday, July 29, 2021 11:37 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Identifying PDS/E
On Thu, 29 Jul 2021 15:47:45 -0400, John Abell wrote:
>Why not have them use TSO XMIT files like we do?
>
Will RECEIVE then allocate (NEW,CATLG) a data set with suitable DSNTYPE,
SPACE, RECFM, LRECL, ...
If the original PDS is large, is there a problem of overflow of a temporary
data set?
But
Of Billy Ashton
Sent: Thursday, July 29, 2021 2:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Identifying PDS/E or PDS in IEBCOPY Unload
Hey everyone, here is an odd question for y'all.
Is there any way I can tell from an IEBCOPY unload file (that I received from a
vendor) whether it is an unload of a PDS
> Is there any way I can tell from an IEBCOPY unload file (that I received
Billy,
You can print the header record of the unloaded IEBCOPY and check for Bit 7
whether the input dataset is a PDSE or NOT.
Here is the lay out the header record from IEBCOPY
, 2021 2:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Identifying PDS/E or PDS in IEBCOPY Unload
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected emails.
Hey everyone, here is an odd question for y'all.
Is there any
Hey everyone, here is an odd question for y'all.
Is there any way I can tell from an IEBCOPY unload file (that I received
from a vendor) whether it is an unload of a PDS or an unload of a PDS/E?
Since IEBCOPY is pretty particular about only loading full libraries
back to the same source type,
18 matches
Mail list logo
