W dniu 01.12.2024 o 01:12, Seymour J Metz pisze:
Does START FOO, TIME.STEP3= work? If not, you need to code the EXEC with a
symbolic parameter in STEP3 EXEC and override that in the START.
Didn't you try?
As I already wrote I tried this, it doesn't work. "delimiter error".
IEE307I. Does anyone know a trick to provide TIME or PARM to given step?
Explain what? The START for VTAM is like any other START. Normally the device
and volser are omitted, hence the three commas.
Yes, commas. However the LIST is a parameter which is not present in
JCL. Neither VTAM procedure text, nor JCL reference. However it works -
that mean it is a way to provide some information (suffix) to the VTAM.
And AFAIK it is VTAM-specific, that mean I don't know any other started
task using such LIST in the start command.
Back to the thread's topic:
Yes, one can get rid off HASPPARM DD and use logical parmlib
concatenation. Parameters like membername, WARM, NOREQ, etc. can be
specified in JCL (EXEC statement) or in the command. However it is
"exclusive or", that means start command override parameters in the
procedure text.
Thank anyone who joined discussion. I appreciate it.
Regards
--
Radoslaw Skorupka
Lodz, Poland
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
________________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of Radoslaw
Skorupka <[email protected]>
Sent: Saturday, November 30, 2024 3:44 PM
To: [email protected]
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 has been the case since OS.360 F14 that you could have overrides on the
START. The DD overrides are applied to IEFRDER and the EXEC overrides are
applied to the EXEC PROC=. What you can't do is to direct a DD override to
anything other than IEFPROC.IEFRDER.
Of course, you can code the JCL with lots of symbolic parameters, and override
those.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
________________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of Radoslaw
Skorupka <[email protected]>
Sent: Friday, November 29, 2024 9:38 PM
To: [email protected]
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 in MVS START command to override the keyword in JCL. Obvious
reason: a procedure may have more than one step and each step can have
PARM or TIME, etc.
Instead another trick exists: for started jobs (JOBcard present) the
parameters from the START command are considered as SET PARM=...
variables. But this is still not the keyword, just poorly named &VAR.
BTW: It is popular to start VTAM withe LIST= parameter. Obviously there
is no such string ("LIST") in the VTAM procedure.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 29.11.2024 o 00:43, Seymour J Metz pisze:
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
