|
View previous topic :: View next topic
|
| Author |
Message |
dbordon
New User
Joined: 25 Jan 2007
Posts: 20
Location: Argentina
|
|
|
|
Did anyone know any program, clist or any other tool that can help check syntax errors in a given member?
My goal is to avoid problems at the time of IPL due to syntax errors.
I have found a red book with some information, called:
z/OS Planned Outage Avoidance Checklist SG24-7328-00
In that book there is ¨Symbolic Parmlib Parser¨ wich is did not try it yet, but i guess it will only applies to symbols- |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| My goal is to avoid problems at the time of IPL due to syntax errors. |
Things that are started at IPL are rarely changed so this should not be much of an issue. . .
There are several "jcl checkers" available commercially. Many organizations already have one.
Suggest you check with your system support people or the people who authorize/pay for software licenses and see if something is already available on your system.
There is also TYPRUN=SCAN. . . |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
I don't think I've heard of anything to check the SYS1.PARMLIB members to ensure the IPL will work. There's such a variety of parameters for different situations that such a checker would probably have to be updated for each z/OS release before it could be used. The best way I know of the check the syntax is to carefully review every message that shows up during the IPL. Most of them don't mean that much, but every now and then there is one that indicates a problem.
Of course, the real serious problems stop the IPL so you become aware of them very quickly! |
|
| Back to top |
|
|
nevilh
Active User
Joined: 01 Sep 2006
Posts: 262
|
|
|
|
| Image Focus will do what you want |
|
| Back to top |
|
|
dbordon
New User
Joined: 25 Jan 2007
Posts: 20
Location: Argentina
|
|
|
|
Thank like always for reading and answer my post.
I guess the best choise is to use ImageFocus.
If you have time and you are willing to do some testings about the IBM´s parser application try the following (i did and i realize that it is not working the way i need it to be):
- Copy into a dsn with your userid the following two member:
SYS1.SAMPLIB(SPPINST)'
SYS1.SAMPLIB(SPPPACK)'
- Run the installation REXX:
TSO EX ’SYS1.SAMPLIB(SPPINST)’ ’’’SYS1.SAMPLIB(SPPPACK)’’’
- Exec the program:
TSO EX ’myid.PARMLIB.EXEC(SYSPARM)’
- Test program
My conclusion:
Tried to test a stand alone member copied from sys1.parmlib testing continuation symbols like comma or the plus symbol and did not work,
This parser program cannot check JES2PARM (mine is HUGE).
Remember to read the following REDBOOK:
z/OS Planned Outage Avoidance Checklist SG24-7328-00
Thanks again to all |
|
| Back to top |
|
|
|
|
