On Sun, 18 Oct 2020 06:06:50 -0400, David Spiegel wrote: > >For LNKLSTd PDSEs, modules deemed to be in use aren't "removed" from the >PDSE, which could cause shortage of directory blocks or space. >I usually have to run it twice. The first time is without a PARM, the >second time with PARM='PerformPendingDelete,NoAnalysis'. > Is PARM case-insensitive? Is that unusual for utilities?
>Please see: >https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.idau100/pdsexmp4.htm > That doc appears to have been generated from a Utilities chapter template, carelessly edited by an entry-level programmer. I believe I'll submit an RCF: In: z/OS Version 2 Release 4 DFSMSdfp Utilities IBM SC23-6864-40 Chapter 9. IEBPDSE (PDSE Validation) Program I see: Table 32. Job control statements for IEBPDSE (continued) ... SYSPRINT DD Use Defines a sequential output message data set, which can be written on a system printer, a magnetic tape volume, or a direct access volume. If this statement is omitted, the output appears in the job log. ... The block size for the SYSPRINT data set must be a multiple of 121. If not, the job step will end with a return code of 8. This the only constraint specified on SYSPRINT attributes. so may I assume "//SYSPRINT DD BLKSIZE=12100,RECFM=VBA,LRECL=137" is supported? SYSIN DD If specified, the SYSIN data set must be empty. o Is this enforced? o If SYSIN is nonempty, what RC and messages result? o What attributes and device types are supported? o If SYSIN is the output of a UNIX pipe, does IEBPDSE pause until its input is closed to verify that it's empty? o What other DDNAMEs are allowed, such as SYSUT1, SYSUT2, SYSTERM, WOMBAT, ...? Must they likewise be empty? ... Example 2: Validate two PDSEs This example validates two PDSEs. //STEPCHK2 EXEC PGM=IEBPDSE //SYSLIB DD DSN=IBMUSER.SIMPLE.V2.PDSE,DISP=OLD // DD DSN=IBMUSER.SIMPLE.V3.PDSE,DISP=OLD // DD DSN=SYS1.LINKLIB,DISP=SHR o SYSLIB has three catenands. Which two are validated and which one is ignored? o Indention should be consistent. ... Example 3: Validate a PDSE with the DUMP option This example validates a PDSE and specifies an SVC dump. //STEPLINK EXEC PGM=IEBPDSE, // PARM=’DUMP’ //SYSLIB DD DSN=SYS1.LINKLIB,DISP=SHR o Is the SVC dump unconditional, or only if SYSIN is nonempty? o Why would a programmer want to do this? o Indention should be consistent. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
