PK60441: THE LPEX EDITOR IS DISPLAYING SYNTAX ERRORS FOR THE JCL STATEMENTS WHEN THE JCL DOES NOT GET A JCL ERROR

APAR status

• Closed as fixed if next.

Error description

• Environment:  Rational Developer for System Z Ver 7.1
  
  Problem Description:
  
  Problem Description:
  
  The LPEX editor is displaying syntax errors for the JCL
  statements when the JCL does not get a JCL error (passes the
  internal reader) when submitted.
  
  Following syntax situations seem to be issues
   / oversights: (Note these are errors/warnings
  appearing while editing in a source member
  and not during syntax checking)
  
             CBL
             01 ws-variable pic 8(00) value
             duh.
  
  
             JCL
  
  
             //A2109JED JOB
             (2972,DART,NSCCSUPPREGN),'JEDS
             RPT DATA', JOB59399
              // NOTIFY=A210997,
              //* RESTART=STEP030,
              //MSGCLASS=U,CLASS=R,REGION=0K,
              // USER=A210997,PASSWORD=
              Incorrect PASSWORD character or
              length
  
  
              //MAFMQ006 DD DSN
  
              =CIAVT.A210997.OCF.D092302,DISP
              =SHR,
              // AMP=('BUFNI=5','BUFND=2')
              Too many parameters in list.
  
  
              //COB EXEC PGM=&COBPGM,COND
              =((5,LT,TRN),(5,LT,ZERO)),
              // PARM=(
  
              'MAP,NODYNAM,RENT,XREF,LIB,OBJECT,TRUNC(BIN)'
              ,
              // 'APOST',OFFSET,NOSEQ,
              'DATA(31)',NONUMBER,SOURCE,
              FLAG(I))
              Expected delimeter not found
  
  
  
  Client doesn't consider any of the errors returned for the jcl
  members to be "errors" and does not cause an issue
  in a syntax check, jclprep or job run on their system.
  
  In another scenerio
  
  Some statements are flagged in error although the job runs
  correctly.  The parser finds that coding a statement ending
  with ,) is incorrect for instance DISP=(NEW,CATLG,) is flagged.
  
  
  
  For JCL, if there an expectation to relax the checking in the
  LPEX JCL parser then the suggestion is the user has the option
  to enter on the LPEX command line of any JCL file
  
    parserProperty.errorMessages off
  
  and then there will not be any imbedded messages any longer.
  The error style could also be changed from white on red to the
  default colors, and then there will be even less visual
  feedback.
  

Local fix

Problem summary

• 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 V7.5.
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R750 PSY

     UP