Re: "SYSMDUMP can be blocked. But if it is going to be blocked, RECFM must be 
FBS."

Can you share where that may be documented?  The V2.5 JCL Reference 
(SA23-1385-50) has only this advice concerning SYSMDUMP:

SYSMDUMP DD statement
Produces a dump of the system areas and the program’s address space. The
dump is unformatted and machine-readable. It must be processed by the
interactive problem control system (IPCS) and therefore should not be directed
to SYSOUT. z/OS R6 introduced system-determined BLKSIZE support for
SYSMDUMPs. If you wish to control the BLKSIZE for compatibility with tools
developed for earlier releases, add the following DCB attributes to your
SYSMDUMP DD statement.
DCB=RECFM=FB,LRECL=4160,BLKSIZE=4160

Peter

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Tom 
Marchant
Sent: Wednesday, May 24, 2023 2:46 PM
To: [email protected]
Subject: Re: Why does ISPF BROWSE abend with S878 searching a large sequential 
file?

On Wed, 24 May 2023 11:35:19 -0400, Steve Thompson <[email protected]> wrote:

>RECFM=F,LRECL=4160,BLKSIZE=0 (I think blocking works with dumps now)

Yes SYSMDUMP can be blocked. But if it is going to be blocked, RECFM must be 
FBS. RECFM=F will be unblocked.

>And SPACE=(CYL,100,30) I think that should be able to hold the
>whole dump.

Why such a small secondary allocation? That is a pretty small allocation for a 
SYSMDUMP, though it may be adequate for the OP's region size. When I create a 
SYSMDUMP in batch, and I do it several times a year,, I code 
(CYL,(300,500),RLSE). DCB parameters need not be specified, as they will be 
filled in properly by the system.

--


This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


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

Reply via email to