In 8592377061499272.wa.paulgboulderaim@listserv.ua.edu, on
01/22/2014
at 05:33 PM, Paul Gilmartin paulgboul...@aim.com said:
I try to double check my facts
The relevant fact was that I overlooked something[1]. You assumed that
it was deliberate; nothing remotely like checking your facts.
On Thu, 23 Jan 2014 06:30:43 -0500, Shmuel Metz (Seymour J.) wrote:
The relevant fact was that I overlooked something[1]. You assumed that
it was deliberate; nothing remotely like checking your facts.
[1] Well, that plus misleading text in the manual.
Cite. I saw only an apparent excerpt with
In 4955235761654675.wa.paulgboulderaim@listserv.ua.edu, on
01/21/2014
at 12:09 AM, Paul Gilmartin paulgboul...@aim.com said:
And your (mis)interpretation to be
disingenuous rather than misinformed.
Then I consider you ro be a fool and a hypocrite. Presumably you have
never overlooked an
On Wed, 22 Jan 2014 09:39:14 -0500, Shmuel Metz (Seymour J.) wrote:
on 01/21/2014 at 12:09 AM, Paul Gilmartin said:
And your (mis)interpretation to be
disingenuous rather than misinformed.
Then I consider you ro be a fool and a hypocrite. Presumably you have
never overlooked an individual
I'm trying to use pax to write to a ddname. I'm doing this from a REXX exec
that's running in batch under IKJEFT01. I'm not getting it to work.
Various replies by Elardus, John, Jon, Kirk, Leonardo, Lloyd, Paul, Scott and
Shmuel
Thanks all for the comments and ideas. I'm trying out a couple
On Sun, 19 Jan 2014 02:21:11 -0500, Shmuel Metz (Seymour J.) wrote:
on 01/17/2014 at 08:59 AM, John McKown said:
paxRC=bpxwunix(wCMD,,DD:PAX,stderr.)
That provides a DD for stdout; the OP needs a dd for stdin:
paxRC=bpxwunix(wCMD,DD:PAX,STDOUT.,STDERR.)
I agree with John, rather the
In 0158509868278815.wa.paulgboulderaim@listserv.ua.edu, on
01/20/2014
at 11:17 AM, Paul Gilmartin paulgboul...@aim.com said:
I agree with John, rather the Shmuel. In the OP's command (which
Shmuel trimmed), it appears that he was trying to write a pax
archive, not extract one.
The
On Mon, 20 Jan 2014 22:09:50 -0500, Shmuel Metz (Seymour J.) wrote:
on 01/20/2014 at 11:17 AM, Paul Gilmartin paulgboul...@aim.com said:
I agree with John, rather [than] Shmuel. In the OP's command (which
Shmuel trimmed), it appears that he was trying to write a pax
archive, not extract one.
In
9f187145e7dd6e4398287ff781d211350a308...@046-ch1mpn1-042.046d.mgd.msft.net,
on 01/17/2014
at 01:12 PM, van der Grijn, Bart (B) bvandergr...@dow.com said:
I can't figure out how to override this setting for my IKJEFT01 step.
What happens if your REXX code sets _BPX_SHAREAS using the
In
caajsdjhom97scaffzr_jbb6rokt-yo9+wst3-dxgkca5+cj...@mail.gmail.com,
on 01/17/2014
at 08:59 AM, John McKown john.archie.mck...@gmail.com said:
paxRC=bpxwunix(wCMD,,DD:PAX,stderr.)
That provides a DD for stdout; the OP needs a dd for stdin:
paxRC=bpxwunix(wCMD,DD:PAX,STDOUT.,STDERR.)
--
In 1389977617.39838.yahoomail...@web184806.mail.gq1.yahoo.com, on
01/17/2014
at 08:53 AM, Lloyd Fuller leful...@sbcglobal.net said:
Look at your DSName. It is not a valid MVS dataset name:
What gives you that idea?
too many characters without a period.
No; look at the trace he gives in a
I'm trying to use pax to write to a ddname. I'm doing this from a REXX exec
that's running in batch under IKJEFT01. I'm not getting it to work.
The following code:
...
wCMD = pax -w -X -z -x pax -f //DD:PAX aDir
ALLOC DD(PAX) DSN('aBackupDsn') OLD release
paxRC = bpxwunix(wCMD,,stdout.,stderr.)
code RELEASE or write to tape.
Thanks,
Bart
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Elardus Engelbrecht
Sent: Friday, January 17, 2014 9:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: pax, ddnames and _BPX_SHAREAS
van der
On Fri, Jan 17, 2014 at 7:12 AM, van der Grijn, Bart (B)
bvandergr...@dow.com wrote:
I'm trying to use pax to write to a ddname. I'm doing this from a REXX
exec that's running in batch under IKJEFT01. I'm not getting it to work.
The following code:
...
wCMD = pax -w -X -z -x pax -f
van der Grijn, Bart (B) wrote:
Thanks Elardus,
You're welcome! :-)
z/OS in question is z/OS 1.12
Ok.
Should have clarified this in my original note, but I'm not trying to write to
a 'unix' file, I'm trying to write to a MVS dataset allocated to a DDName.
Using a dataset name in the pax
John,
I think you can make a single change to your REXX program
paxRC=bpxwunix(wCMD,,DD:PAX,stderr.)
I tried that. In my original note:
(I also tried it by specifying a ddname in the bpxwunix call instead of
the stdout., but got a truncation error. I suspect that's because it
exceeded
Have you tried running PGM=BPXBATCH instead and run the exec as a UNIX script?
You would need to place the exec in a UNIX file and change ALLOC to BPXWDYN.
As for the truncation error, have you tried changing the dataset's attributes
(LRECL, BLKSIZE and RECFM)?
Jon Perryman.
Bart,
It isn't clear whether you needed to do this with a TMP and REXX or whether
you were just trying to work around the normal issues with BPXBATCH.
This is very straight forward to do using our COZBATCH utility:
//SHELL EXEC PGM=COZBATCH - a better BPXBATCH
//STDIN DD *
pax -w -X -x pax -v
: pax, ddnames and _BPX_SHAREAS
I'm trying to use pax to write to a ddname. I'm doing this from a REXX exec
that's running in batch under IKJEFT01. I'm not getting it to work.
The following code:
...
wCMD = pax -w -X -z -x pax -f //DD:PAX aDir ALLOC DD(PAX)
DSN('aBackupDsn') OLD release
paxRC
Look at your DSName. It is not a valid MVS dataset name: too many characters
without a period.
Lloyd
From: Elardus Engelbrecht elardus.engelbre...@sita.co.za
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Friday, January 17, 2014 9:59 AM
Subject: Re: pax, ddnames
On Fri, 17 Jan 2014 13:12:09 +, van der Grijn, Bart (B) wrote:
I'm trying to use pax to write to a ddname.
The following code:
...
wCMD = pax -w -X -z -x pax -f //DD:PAX aDir
I don't believe any such construct is supported. Have you seen
any documentation that states that it is.
Submit a
: Re: pax, ddnames and _BPX_SHAREAS
Have you tried running PGM=BPXBATCH instead and run the exec as a UNIX script?
You would need to place the exec in a UNIX file and change ALLOC to BPXWDYN.
As for the truncation error, have you tried changing the dataset's attributes
(LRECL, BLKSIZE and RECFM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: pax, ddnames and _BPX_SHAREAS
Bart,
It isn't clear whether you needed to do this with a TMP and REXX or whether
you were just trying to work around the normal issues with BPXBATCH.
This is very straight forward to do using our COZBATCH utility:
//SHELL EXEC
Fuller
Sent: Friday, January 17, 2014 11:54 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: pax, ddnames and _BPX_SHAREAS
Look at your DSName. It is not a valid MVS dataset name: too many characters
without a period.
Lloyd
On 2014-01-17 07:43, van der Grijn, Bart (B) wrote:
z/OS in question is z/OS 1.12
Should have clarified this in my original note, but I'm not trying to write
to a 'unix' file, I'm trying to write to a MVS dataset allocated to a DDName.
Using a dataset name in the pax command works fine,
without problem
(except syntax issues getting the quotes and double quotes correct).
Lloyd
From: Paul Gilmartin paulgboul...@aim.com
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Friday, January 17, 2014 2:41 PM
Subject: Re: pax, ddnames and _BPX_SHAREAS
On 2014-01-17
oh Gil,
You know very well that the Command Reference documents only that pax
supports MVS data set names and does not mention that DD:XXX names are
supported. You have said this many times before, and I agree that IBM
should formally support this. Have you opened a requirement?
Surely they
MVS archive datasets are supported by the PAX command. The first paragraph of
the MAN PAX page says the archive can be HFS file or MVS dataset. I only have
access to the EFGLOBE.COM system so it may now say something different but
along the same lines.
Jon Perryman
On Fri, 17 Jan 2014 14:01:34 -0800, Jon Perryman wrote:
MVS archive datasets are supported by the PAX command. The first paragraph of
the MAN PAX page says the archive can be HFS file or MVS dataset. I only have
access to the EFGLOBE.COM system so it may now say something different but
along
This has been asked before,here
On Thu, 8 Jan 2009 16:34:41 +0100, Miklos Szigetvari
Post by Miklos Szigetvari
Hi
We have a number of user ZFS datasets, in NON EXTENDED format , and
already has reached the 4Gbyte limit
Till now we have allocated a new extended format ZFS and copied into it
30 matches
Mail list logo
