JCL keywords are all or nothing; a PARM override replaces the entire thing. The trick is to use symbolic parameters instead of PARM overrides.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Radoslaw Skorupka <[email protected]> Sent: Thursday, November 28, 2024 10:36 AM To: [email protected] Subject: JES2, HASPPARM and PARM External Message: Use Caution I want to change my JES2 JCL procedure. The goal is to remove HASPPARM and use logical PARMLIB concatenation instead. That mean the initialization member should be specified as PARM='MEMBER=memname' The PARM can be specified directly in JCL procedure or as a part of START command. However I noticed that S JES2,PARM='WARM,NOREQ' nullifies PARM specified on procedure step's PARM. I can put all the parameters into procedure or into the command. However I would like to keep possibility to specify parameters in the command while the PARM in the proc is also present. Is it possible? What trick am I missing? -- Radoslaw Skorupka Lodz, Poland ---------------------------------------------------------------------- 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
