Hi Rahim,
You said: "... DISP also looks incorrect ...". I think you've made a mistake. It is correct.

Regards, David

On 2025-08-19 19:24, Rahim Azizarab wrote:
Your Space Parm looks excessively large without a ,RLSE and DISP also looks 
incorrect.  You create and then DELETE.

regards;

Rahim



     On Tuesday, August 19, 2025 at 03:22:33 PM CDT, Radoslaw 
Skorupka<[email protected]> wrote:
W dniu 18.08.2025 o 15:41, Steve Estle pisze:
Is anyone else having issues applying / and/or accepting latest ZOS 2.5 
maintenance?  I am trying to run accept of latest received / applied RSU and 
continue to get E37-04 Abends on SMPWRK6 - my JCL specifies:

//SMPWRK6  DD DISP=(NEW,DELETE,DELETE),UNIT=(SYSALLDA,5),
//        SPACE=(CYL,(7000,7000,25000)),
//        DSNTYPE=LIBRARY

For instance, UI94975 Liberty PTF is over 4.1 million records in length?

Is anyone else having issues receiving / applying / accepting these extremely 
large PTF's?  If not what are you doing with your SMPWRK6 DD to get through 
them or do we just have to apply/accept these in piecemeal fashion?
Many moons ago I had a problem with SMPPTS which was PDSE. At the time
the limitation of PDSE: 15 728 639 records per member (~1.2GB for FB
80). And the PTF size was bigger - so I had to go back to PDS which
doesn't have such limit (there is 64k TRKs per dataset, but it wasn't an
issue then).

Nowadays I use PDSE v2 which has the above limit relieved (it is 2 146
435 071 records per member).


BTW: the above JCL code is inconsistent (or silly). UNIT=(,5) has no
sense for single-volume datasets like PDSE or PDS. Number of directory
blocks can be 25000 or anything, but it is dummy number, since you chose
to use PDSE. SPACE pri and sec - adjust it to your volume size and free
space. BTW: I would code DDDEF instead of DD.

HTH


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

Reply via email to