On Thu, 24 Aug 2023 18:45:23 -0400, Phil Smith III wrote: > >Well, maybe; I didn't write this stuff but the guy who did was pretty sharp, >and couldn't figure out ways around the above. He also noted this: > Is he too sharp tobe wrong?
>//* ***NOTE*** Some references to variable values are in records >//* provided as part of SYSIN DD *, and thus cannot be >//* filled in using JCL variables (&HLQ et al.). Thus >//* in this job, you must replace all references to >//* !hlq!, !unit!, and !volser!, not just the single >//* SET statement for each. > What's he mean by "not just the single SET statement for each."? It appears as if one SET can't govern multiple applied occurrences. In what language is that true? Did it antedate "DD *,SYMBOLS=JCLONLY"? >Maybe there's a clever way around that? It's referring to things like: > Can't it be refactored as: // EXPORT SYMLIST=* // SET HLQ=MYHLQ // SET VOLSER=MYVOL // SET UNIT=SYSALLDA (All sucn might appear in a reusable JCLLIB member. Then: >//SYSIN DD *,SYMBOLS=JCLONLY > DEFINE CLUSTER( + > NAME(&HLQ..GLOBAL.CSI) + > VOLUMES(&VOLSER.) + > CYLINDERS(20 10) + > FREESPACE(2 2) + > KEYS(24 0) + > RECORDSIZE(24 143) + > SHAREOPTIONS(2 3) + > ) + > DATA ( + > NAME(&HLQ..GLOBAL.CSI.DATA) + > CONTROLINTERVALSIZE(8192) + -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
