XMIT might be but the goal is to be as git compliant as possible with zigi 
being just a git frontend (aka IDE) that provides the interface to z/OS 
datasets for git.  Thus using XMIT format would defeat the purpose and violate 
git in many ways 😊


Lionel B. Dyck <sdg><
Website: https://www.lbdsoftware.com

"Worry more about your character than your reputation.  Character is what you 
are, reputation merely what others think you are." - John Wooden

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Seymour J Metz
Sent: Wednesday, June 17, 2020 12:07 PM
To: [email protected]
Subject: Re: Improve OMVS cp performance?

It might be more efficient to use XMIT format. Is there a REXX function package 
available for unpacking members?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of 
Kirk Wolf [[email protected]]
Sent: Wednesday, June 17, 2020 12:07 PM
To: [email protected]
Subject: Re: Improve OMVS cp performance?

On Wed, Jun 17, 2020 at 10:43 AM Paul Gilmartin < 
[email protected]> wrote:

> On Wed, 17 Jun 2020 09:24:58 -0500, Kirk Wolf wrote:
> >
> >I wasn't thinking of using the "all members" form of cp ...
> >I'm curious - how much time did you save by preallocating the PDS?
> >
> I'm mystified that it made a difference since Lionel never used the 
> allocate "dd" in the call to "cp".  Only SVC 99 knows.
>
>
If you have a reusable allocation, then the cost is less than a new
allocation.   open/close for each member would still be expensive for a PDS
with tons of members.   A BLDL,loop: POINT,READ*  is what you really want
IMO.


> >I would think that you might actually want ISPF-style enqueues.
> >
> I thought later of OGETX/OPUTX, which piggybacks on ISPF.
>
> Good point - that would definitely be something to try.

Another fun thing to try is IEBUPDTE - I once played around with a REXX wrapper 
and then piped the control and data into it via DD:SYSIN pointing to /dev/fd0 
from a shell script.  It's *really* fast as expected, but has issues wrt the 
record format and content of the data that could mess it up.

BTW: If it was as fast as it should be, Lionel probably doesn't need a 
"progress" popup :-)

-- Kirk

----------------------------------------------------------------------
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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to