Dear Group,
Thank you for the discussion on this. I started trying to look into writing
a REXX exec to select my KEY input and build the dataset members needed to
continue. I used to do this using the ISPF panels by hand.
I thought the panel was using IBM code. But I was told it was not and we
did something so it was this way. Thank you for pointing out that using
IEBCOPY with REXX also pulled in some other vendor software.
I can read the same file in and massage my key for each need. I usually
build two members that have the same information in two different formats that
are static and I can go back and reference.
So, after consideration. I will go back to REXX EXECIO. I need to massage
the data anyway. It will run two steps, reading the same file twice, but
creating different outputs.
I learned more about the MVS utilities :) Was wondering if IEBGENER allowed
creating two members from the same input data, in one step. IEBGENER appears
to not loop back to the top to re-evaluate (edit) the same input data. Amazing
how copy and sort can lead down so many paths. Need more "GOBACK" commands :)
Thanks again for sharing your knowledge and thoughts with me, Dave
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Paul Gilmartin
Sent: Thursday, March 20, 2014 10:48 AM
To: [email protected]
Subject: Re: Now IEBGENER, Was Help with IEBCOPY?
On Thu, 20 Mar 2014 08:31:27 -0400, Shmuel Metz (Seymour J.) wrote:
>
>>The plain old IEBGENER would be best batch option for a non-source
>>type dataset,
>
>Why is it bettwer than, e.g., IDCAMS REPRO?
>
Choose your evil. It's all relative.
IEBGENER:
o Allows the programmer to omit (some) attributes from SYSUT2, in which
case they are (optionally) replicated from SYSUT1 o Requires that supplied
attributes of SYSUT2 be compatible with SYSUT1.
REPRO:
o Requires that the programmer supply (more) attributes of the output file o
Allows the attributes of the output file to differ (more) from the inout file.
On Thu, 20 Mar 2014 08:41:21 -0500, Tom Marchant wrote:
>
>Your output file is a PDS MEMBER. A PDS member is a sequential data set. You
>don't need GENERATE.
>
The OP's initial objective appeared to involve some editing, in which case he
needs a control file.
On 2014-03-20, at 07:49, Blaicher, Christopher Y. wrote:
>
>//SYSUT2 DD DISP=SHR,DSN=output-pds(member-name)
>
>You can use SHR or OLD for DISP
>
Beware. If you use SHR for PDS SYSUT2 and your two jobs run concurrently, Bad
Things might happen. PDSE and/or newer releases of z/OS may be more robust.
-- gil
----------------------------------------------------------------------
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
