: ADRDSSU VTOC -- also IEBCOPY
::
:: On 2014-06-07, at 11:17, retired mainframer wrote:
::
:: Bob quoted the JCL manual. So yes, DUMMY is usable with QSAM.
::
:: The issue however is what is IEBCOPY's requirement. My manual says
:: SYSUT2
:: must reside on a device that supports QSAM
:: -Original Message-
:: From: IBM Mainframe Assembler List [mailto:ASSEMBLER-
:: l...@listserv.uga.edu] On Behalf Of Paul Gilmartin
:: Sent: Sunday, June 08, 2014 6:25 AM
:: To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
:: Subject: Re: ADRDSSU VTOC -- also IEBCOPY
::
:: On 2014-06-07, at 23:19
On 2014-06-07, at 14:46, John Gilmore wrote:
I certainly concede the possibility of front-ending BSAM or QSAM.
Nevertheless, the data-management facility for multiple-member
operations is BPAM; and in most circumstances it is the one that
should be used. With my back to the wall I could even
On 8 June 2014 18:15, Paul Gilmartin paulgboul...@aim.com wrote:
Another contributor to this thread told me long ago that IEBCOPY did
not (then) rely on customary access methods. Rather, with the goal of
best performance it used specialized channel programs and facilities
such as EXCP V=R and
On 6/8/2014 3:15 PM, Paul Gilmartin wrote:
I suspect that the advent of PDSE partly impelled conversion to more
conventional access methods rather than duplicating in IEBCOPY
facilities available in PDSE and Binder.
Not only that, but the channel programs it used - which were once
considered
On Fri, 6 Jun 2014 10:43:57 -0600, Paul Gilmartin
paulgboul...@aim.com wrote:
I suspect the restriction (we have it at 1.13) spans many
releases. How silly to go to trouble to avoid doing nothing.
DISP={OLD|NEW} seems to make no difference. I suspect that DISP
is among many DD options
On 2014-06-07, at 08:30, Bob Raicer wrote:
On Fri, 6 Jun 2014 10:43:57 -0600, Paul Gilmartin wrote:
I suspect the restriction (we have it at 1.13) spans many
releases. How silly to go to trouble to avoid doing nothing.
...
Use one of the following access methods with the DUMMY
At 08:30 -0600 on 06/07/2014, Bob Raicer wrote about Re: ADRDSSU VTOC
-- also IEBCOPY:
I certainly cannot look at the source code for IEBCOPY, but I
suspect that IEBCOPY simply checks the device type associated with
the DD to be operated upon and if it's not something it likes (i.e.
DASD, TAPE
On 2014-06-07, at 09:30, Robert A. Rosenberg wrote:
...
Support of output to SYSUT2 requires that for each file that is being
selected to be potentially copied to SYSUT2, there is a check to see
if it already is in the PDS(E) UNLESS Replace (SYSUT2,R) is coded in
the Copy command before
Bob Raicer can defend his own positions, but it does seem to me that
he made it clear, with appropriate extracts from the manual, that
DUMMY is usable only with BSAM, QSAM, and VSAM, i.e., not with BPAM.
That being the case, most of this backing and filling is, at best, irrelevant.
John
On 2014-06-07, at 10:06, John Gilmore wrote:
Bob Raicer can defend his own positions, but it does seem to me that
he made it clear, with appropriate extracts from the manual, that
DUMMY is usable only with BSAM, QSAM, and VSAM, i.e., not with BPAM.
Why are people fixated on BPAM? My
-
:: From: IBM Mainframe Assembler List [mailto:ASSEMBLER-
:: l...@listserv.uga.edu] On Behalf Of John Gilmore
:: Sent: Saturday, June 07, 2014 9:07 AM
:: To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
:: Subject: Re: ADRDSSU VTOC -- also IEBCOPY
::
:: Bob Raicer can defend his own positions, but it does seem
To retired mainframer's post my response can be brief: I think not.
A single member of a PDS[E] can be accessed in the usual way using
BSAM or QSAM. A list of them cannot. For that operation BPAM must be
used. BPAM does not support the use of DUMMY.
John Gilmore, Ashland, MA 01721 - USA
allocation).
Bob
On 2014-06-07 9:30 AM, Robert A. Rosenberg wrote:
At 08:30 -0600 on 06/07/2014, Bob Raicer wrote about Re: ADRDSSU VTOC -- also
IEBCOPY:
I certainly cannot look at the source code for IEBCOPY, but I
suspect that IEBCOPY simply checks the device type associated with
the DD
On 2014-06-07, at 11:17, retired mainframer wrote:
Bob quoted the JCL manual. So yes, DUMMY is usable with QSAM.
The issue however is what is IEBCOPY's requirement. My manual says SYSUT2
must reside on a device that supports QSAM, such as (but not limited to)
DASD or tape. Since a DUMMY
:: -Original Message-
:: From: IBM Mainframe Assembler List [mailto:ASSEMBLER-
:: l...@listserv.uga.edu] On Behalf Of Paul Gilmartin
:: Sent: Saturday, June 07, 2014 11:46 AM
:: To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
:: Subject: Re: ADRDSSU VTOC -- also IEBCOPY
::
:: On 2014-06-07, at 11:17
On 2014-06-05, at 17:09, retired mainframer wrote:
IEBCOPY from z/OS 1.11 will not support SYSUT2 with DD DUMMY or
DSN=NULLFILE. This is true for either step in your job. It has no problem
with VIO.
I suspect the restriction (we have it at 1.13) spans many releases.
How silly to go to
Thank you for your message. I will take care of your email after June 22nd,
2014. For urgent issues regarding CICS, please contact AXA-BOX Mainframe CICS
(mainframe.c...@axa-tech.com). For urgent issues regarding IMS, please contact
AXA-BOX IMS Online DB (ims.onl...@axa-tech.com).
-
:: Sent: Tuesday, June 03, 2014 1:30 PM
:: To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
:: Subject: Re: ADRDSSU VTOC -- also IEBCOPY
::
:: On 2014-06-03 14:10, retired mainframer wrote:
:: Why don't you show us the job that built the archive and the job that
:: tried
:: to read it.
::
:: :: -Original
You can run with
//SYSUT1 DD DISP=OLD,DSN=tape.dataset,LABEL=(,SL)
//SYSUT2 DD DISP=OLD,DSN=NULLFILE,DSORG=PO
That will get a listing of what would have been copied back.
On 3 June 2014 02:13, Paul Gilmartin paulgboul...@aim.com wrote:
On 2014-06-02 13:27, Gibson, Vincent wrote:
Is it
On 2014-06-03, at 02:59, Dougie Lawson wrote:
You can run with
//SYSUT1 DD DISP=OLD,DSN=tape.dataset,LABEL=(,SL)
//SYSUT2 DD DISP=OLD,DSN=NULLFILE,DSORG=PO
That will get a listing of what would have been copied back.
I'll take your word for it; I assume you've tested it. But what
if the
IEBCOPY archives are a simple VBS (variable blocked spanned) dataset. It
makes not a jot of difference whether that's on tape or disk (or something
emulating either of those).
On 3 June 2014 15:30, Paul Gilmartin paulgboul...@aim.com wrote:
On 2014-06-03, at 02:59, Dougie Lawson wrote:
You
On 2014-06-03, at 10:01, Dougie Lawson wrote:
IEBCOPY archives are a simple VBS (variable blocked spanned) dataset. It
makes not a jot of difference whether that's on tape or disk (or something
emulating either of those).
Well, you say it works for you with the archive on tape. I tried it
@LISTSERV.UGA.EDU
:: Subject: Re: ADRDSSU VTOC -- also IEBCOPY
::
:: On 2014-06-03, at 10:01, Dougie Lawson wrote:
::
:: IEBCOPY archives are a simple VBS (variable blocked spanned) dataset.
:: It
:: makes not a jot of difference whether that's on tape or disk (or
:: something
:: emulating either
On 2014-06-03 14:10, retired mainframer wrote:
Why don't you show us the job that built the archive and the job that tried
to read it.
:: -Original Message-
:: From: On Behalf Of Paul Gilmartin
:: Sent: Tuesday, June 03, 2014 9:10 AM
::
:: On 2014-06-03, at 10:01, Dougie Lawson
On 2014-06-03 15:03, Dougie Lawson wrote:
You didn't tell us it was your output file that failed. You said it was the
input that got the error.
No, I said merely that the JCL sample failed, but
conceded that I had changed SYSUT1 from tape (which I
assumed you verified) to DASD.
So we've
] On Behalf Of Paul Gilmartin
Sent: Tuesday, June 03, 2014 2:31 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: ADRDSSU VTOC -- also IEBCOPY
On 2014-06-03 15:03, Dougie Lawson wrote:
You didn't tell us it was your output file that failed. You said it
was the input that got the error.
No, I
On 2014-06-02 13:27, Gibson, Vincent wrote:
Is it possible to get a ADRDSSU VTOC listing of data set names were dump on
to tape.
Any help is appreciate.
Similar question for an IEBCOPY archive.
Thanks,
gil
28 matches
Mail list logo
