Hi,
During an analysis I found the use of OPTFILE. Which is used in passing the compiler parameters to the compiler step in the endeavor processor. Could they not pass it using the PARM or a dataset used for PARM?
Why do we need to use PARMFILE?
Why do we use OPTFILE.
-
- Registered Member
- Posts: 21
- Joined: Mon Jan 18, 2016 8:16 am
Re: Why do we use OPTFILE.
When you want to pass additional Parms parameters. Also, Parms has limitation of 100 bytes. And if you want to pass parms more than 100 bytes, there is where OPTFILE comes in picture.
https://www.ibm.com/docs/en/zos/2.2.0?t ... -nooptfile
https://www.ibm.com/docs/en/zos/2.2.0?t ... -nooptfile
-
- Registered Member
- Posts: 21
- Joined: Mon Jan 18, 2016 8:16 am
Re: Why do we use OPTFILE.
Yes, Thanks. I did saw that but why do we need an OPTFILE, why can't we pass it using a normal dataset like I'd for a program where I need to pass more than 100 characters. Or is it specific for compiler step?
And I found that with JES3, we can pass more characters in PARM, I lost the link and searching for reference.
And I found that with JES3, we can pass more characters in PARM, I lost the link and searching for reference.
Create an account or sign in to join the discussion
You need to be a member in order to post a reply
Create an account
Not a member? register to join our community
Members can start their own topics & subscribe to topics
It’s free and only takes a minute