Hi Gil,
Thank you for the suggestions.
Here is a job that actually worked. (The DSNAMES have been scrubbed.)
// SET DS=MY
//CREATE EXEC PGM=IEFBR14
//PAX DD DISP=(,CATLG),
// UNIT=SYSALLDA,
// DATACLAS=DCZFSEXT,
// STORCLAS=SCZFSEXT,
//
On Wed, 13 Oct 2021 10:24:06 -0400, David Spiegel wrote:
>I agree with your hypothesis ... the PAX fails because it cannot get an
>Exclusive ENQ on MY.PAX
>
>With respect to the spawned (PAX) Address Space, though, it is possible
>that the spawn itself could take longer than the Batch Job switchin
I agree with your hypothesis ... the PAX fails because it cannot get an
Exclusive ENQ on MY.PAX
With respect to the spawned (PAX) Address Space, though, it is possible
that the spawn itself could take longer than the Batch Job switching
steps and defeat the entire purpose.
I think coding a SL
On Wed, 13 Oct 2021 09:36:51 -0400, David Spiegel wrote:
>
>How does changing the allocation for SYSUT1 from JCL to DYNALLOC change
>anything ... they're both non-Exclusive ENQs?
>
If a DD statement exists in a job the Initiator issues the needed ENQ at the
beginning of the job and it's in effect
Hi Gil,
How does changing the allocation for SYSUT1 from JCL to DYNALLOC change
anything ... they're both non-Exclusive ENQs?
Regards,
David
On 2021-10-13 08:58, Paul Gilmartin wrote:
On Mon, 11 Oct 2021 14:03:11 -0400, David Spiegel wrote:
I am trying to PAX and TRS a zFS.
When I run a Ste
On Mon, 11 Oct 2021 14:03:11 -0400, David Spiegel wrote:
>
>I am trying to PAX and TRS a zFS.
>
>When I run a Step to PAX followed by a Step to TRS, I get:
>pax: //'MY.PAX': EDC5061I An error occurred when attempting to define a
>file to the system.
>(I tried TAR and got the same result.)
>When I r
On Mon, 11 Oct 2021 14:03:11 -0400, David Spiegel wrote:
>
>When I run a Step to PAX followed by a Step to TRS, I get:
>pax: //'MY.PAX': EDC5061I An error occurred when attempting to define a
>file to the system.
>(I tried TAR and got the same result.)
>When I run the PAX in one job and the TRS in
I do this, but I allocate the pax file before trying to write it. I also
specify -x OS390 to be sure to get links and other attributes.
Lloyd
Sent from AT&T Yahoo Mail for iPad
On Monday, October 11, 2021, 4:00 PM, Paul Gilmartin
<000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
On Mo
On Mon, 11 Oct 2021 15:20:24 -0400, David Spiegel wrote:
>
>Every time I've used Windows as a "waystation", I've never had a problem
>with TRS Files.
>
What are the attributes of your "pax -z" output data set? If RECFM=FB
it ought to be comparably robust with BINARY transfers. Did you
pre-alloca
I wonder if you can add a step after the pax step adding a delay, going
along with what I think Gil was eluding to, the forked process had not
terminated yet and was still holding an Excusing Enq on the MVS dataset
not a clean way to resolve but a good test to see if the forked process
is not
Hi Gil,
Every time I've used Windows as a "waystation", I've never had a problem
with TRS Files.
Regards,
David
On 2021-10-11 15:10, Paul Gilmartin wrote:
On Mon, 11 Oct 2021 14:51:23 -0400, David Spiegel wrote:
"... "An error occurred" is woefully inadequate. Were other errors
logged? ..."
Yes, dynamically allocated
On 2021-10-11 15:10, Carmen Vitullo wrote:
is the DD for MY.PAX dynamically allocated ?
I've never wrote to a MVS datasets using pax
Carmen
On 10/11/2021 1:03 PM, David Spiegel wrote:
Hi,
I am trying to PAX and TRS a zFS.
When I run a Step to PAX followed by a S
is the DD for MY.PAX dynamically allocated ?
I've never wrote to a MVS datasets using pax
Carmen
On 10/11/2021 1:03 PM, David Spiegel wrote:
Hi,
I am trying to PAX and TRS a zFS.
When I run a Step to PAX followed by a Step to TRS, I get:
pax: //'MY.PAX': EDC5061I An error occurred when atte
On Mon, 11 Oct 2021 14:51:23 -0400, David Spiegel wrote:
>
>"... "An error occurred" is woefully inadequate. Were other errors
>logged? ..." No
>
No comment on my ENQ hypothesis? Thinking further, BPXBATCH probably
forks (see BPXBATSL), then shell exec pax forks to a third ASID while the TRS
ste
Hi Gil,
"... "An error occurred" is woefully inadequate. Were other errors
logged? ..." No
"... Why bother with TRS? Doesn't your "pax -z" achieve comparable
compression?
(Often a second compression expands the file. Or, pax without the -z,
then TRS.) ..."I want a robust backup Dataset whi
On Mon, 11 Oct 2021 14:03:11 -0400, David Spiegel wrote:
>
>I am trying to PAX and TRS a zFS.
>
>When I run a Step to PAX followed by a Step to TRS, I get:
>pax: //'MY.PAX': EDC5061I An error occurred when attempting to define a
>file to the system.
>
"An error occurred" is woefully inadequate. W
Hi,
I am trying to PAX and TRS a zFS.
When I run a Step to PAX followed by a Step to TRS, I get:
pax: //'MY.PAX': EDC5061I An error occurred when attempting to define a
file to the system.
(I tried TAR and got the same result.)
When I run the PAX in one job and the TRS in another job, it works.
17 matches
Mail list logo
