Re: JES2, HASPPARM and PARM

2024-12-01 Thread Seymour J Metz
יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר From: IBM Mainframe Discussion List on behalf of Radoslaw Skorupka <0471ebeac275-dmarc-requ...@listserv.ua.edu> Sent: Sunday, December 1, 2024 7:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JE

Re: JES2, HASPPARM and PARM

2024-12-01 Thread Radoslaw Skorupka
w Skorupka <0471ebeac275-dmarc-requ...@listserv.ua.edu> Sent: Saturday, November 30, 2024 3:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES2, HASPPARM and PARM External Message: Use Caution How do you override i.e. TIME parameter in STEP3? How do you explain LIST parameter of START VTAM co

Re: JES2, HASPPARM and PARM

2024-11-30 Thread Seymour J Metz
M-MAIN@LISTSERV.UA.EDU Subject: Re: JES2, HASPPARM and PARM External Message: Use Caution How do you override i.e. TIME parameter in STEP3? How do you explain LIST parameter of START VTAM command? -- Radoslaw Skorupka Lodz, Poland W dniu 30.11.2024 o 16:17, Seymour J Metz pisze: > WTF? It

Re: JES2, HASPPARM and PARM

2024-11-30 Thread Radoslaw Skorupka
W dniu 30.11.2024 o 21:44, Radoslaw Skorupka pisze: How do you override i.e. TIME parameter in STEP3? How do you explain LIST parameter of START VTAM command? Just checked: Indeed, the PARM in START command overrides PARM specified in the JCL, however it works only for first step. Majority of

Re: JES2, HASPPARM and PARM

2024-11-30 Thread Radoslaw Skorupka
SERV.UA.EDU Subject: Re: JES2, HASPPARM and PARM External Message: Use Caution It is NOT a JCL. We have two different animals, both having same name: 1. PARM keyword in START command 2. PARM in EXEC card in JCL It is never said that PARM or DISP or SPACE or any other keyword can be specified i

Re: JES2, HASPPARM and PARM

2024-11-30 Thread Seymour J Metz
rupka <0471ebeac275-dmarc-requ...@listserv.ua.edu> Sent: Friday, November 29, 2024 9:38 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES2, HASPPARM and PARM External Message: Use Caution It is NOT a JCL. We have two different animals, both having same name: 1. PARM keyword in START command 2. PARM in E

Re: JES2, HASPPARM and PARM

2024-11-30 Thread Willy Jensen
My latest JES2 proc got boiled down to just this: //* JES2 PROCEDURE WITH EVERYTHING IN THE HASJES2 MEMBER IN //* SYSC.PARMLIB. //IEFPROC EXEC PGM=HASJES20,DPRTY=(15,15),TIME=1440,PERFORM=9 //HASPLIST DD DDNAME=IEFRDER

Re: JES2, HASPPARM and PARM

2024-11-29 Thread Radoslaw Skorupka
ion List on behalf of Paul Gilmartin<042bfe9c879d-dmarc-requ...@listserv.ua.edu> Sent: Thursday, November 28, 2024 9:28 PM To:IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES2, HASPPARM and PARM External Message: Use Caution On Thu, 28 Nov 2024 23:43:33 +, Seymour J Metz roote: JCL key

Re: JES2, HASPPARM and PARM

2024-11-29 Thread Radoslaw Skorupka
eac275-dmarc-requ...@listserv.ua.edu> Sent: Thursday, November 28, 2024 10:36 AM To:IBM-MAIN@LISTSERV.UA.EDU 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 i

Re: JES2, HASPPARM and PARM

2024-11-29 Thread Radoslaw Skorupka
W dniu 29.11.2024 o 17:39, Matthew Stitt pisze: Interesting; An experiment with using PARMLIB instead of HAPPPARM shows that the member must be named HASJES2. The specification of the PARM= is ignored. Wrong. HASJES2 is default name of the member. And it seems the member name was not specif

Re: JES2, HASPPARM and PARM

2024-11-29 Thread Matthew Stitt
Interesting; An experiment with using PARMLIB instead of HAPPPARM shows that the member must be named HASJES2. The specification of the PARM= is ignored. Matthew -- For IBM-MAIN subscribe / signoff / archive access instruction

Re: JES2, HASPPARM and PARM

2024-11-29 Thread Matthew Stitt
>From: IBM Mainframe Discussion List on behalf of >Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu> >Sent: Thursday, November 28, 2024 9:28 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: JES2, HASPPARM and PARM > >External Message: Use Caution

Re: JES2, HASPPARM and PARM

2024-11-28 Thread Seymour J Metz
<042bfe9c879d-dmarc-requ...@listserv.ua.edu> Sent: Thursday, November 28, 2024 9:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES2, HASPPARM and PARM External Message: Use Caution On Thu, 28 Nov 2024 23:43:33 +, Seymour J Metz wrote: >JCL keywords are all or nothing; a PARM

Re: JES2, HASPPARM and PARM

2024-11-28 Thread Paul Gilmartin
On Thu, 28 Nov 2024 23:43:33 +, Seymour J Metz wrote: >JCL keywords are all or nothing; a PARM override replaces the entire thing. >The trick is to use symbolic parameters instead of PARM overrides. > Yes. But PARM is merely a string. Its interpretation is up to the PGM=. If there are def

Re: JES2, HASPPARM and PARM

2024-11-28 Thread Seymour J Metz
From: IBM Mainframe Discussion List on behalf of Radoslaw Skorupka <0471ebeac275-dmarc-requ...@listserv.ua.edu> Sent: Thursday, November 28, 2024 10:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: JES2, HASPPARM and PARM External Message: Use Caution I want to change my JES2 JCL pro

JES2, HASPPARM and PARM

2024-11-28 Thread Radoslaw Skorupka
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 n