PM56559: The RDz LPEX Editor displays syntax errors for JCL statements which run correctly when executed.
A fix is available
Closed as fixed if next.
A user is editing some z/OS Job Control and he gets 'Too many parameters' messages for some statements although the JCL actually runs without problem on z/OS. Here is a sample of one situation: 000300 //STEPA EXEC PROCA, 000301 // MSGDSN=&DSN11, 000302 // INDSP=(OLD,KEEP,KEEP) 000302 Too many parameters. 000303 // ENDIF 000303 Expected ')' not found. 000304 // * The first KEEP in line 302 and all of line 303 are highlighted in red. The corresponding messages are unnumbered. * Here is another example: 000400 //STEPB EXEC PROCB, 000401 // MSGDSN=&DSNB, 000402 // INDSPB=(OLD,KEEP,KEEP) 000402 Too many parameters. 000403 //STEPC EXEC PGM=PROGC, 000403 Expected parameter continuation not found. 000404 // PARM='FILENAME.OUTFL1 ,FB,00100,365' 000404 Incorrect JCL operation field. The first KEEP in line 402, all of line 403 and only PARM='FILENAME.OUTFL1 in line 404 are highlighted in red. The corresponding messages are unnumbered. * FIN APAR PK60441 may contain additional information and examples.
This APAR is being closed FIN with concurrence from the submitting customer. This means that a fix to this APAR is expected to be delivered from IBM in a release which is being developed at the time that the APAR was closed. The latest release of the product to exit development at the time this APAR was closed was: Rational Developer for System z V8.5.
Reported component name
RATL DEV FOR SY
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels