Skip to main content

In Process Error message JCLCM0094I and generated JCL line '//SYSIN DD * ***MFE JCL GENERATED STMT***'

  • July 16, 2014
  • 0 replies
  • 1 view

 There are error messages in our JES Spool. Please explain what these mean. The JCL looks and runs fine but we are seeing these messages in our JES Spool
 
 24 //SYSIN DD * ***MFE JCL GENERATED STMT*** For more info, see JCLCM0094I
 

 The Help for message JCLCM0094I can be found at
 
  Enterprise > Micro Focus Enterprise Developer 2.2 for Eclipse > Deployment > Mainframe Support for Deployed Applications > Reference for MSS Deployment > MSS Error Messages > JCL Error Messages > JCLCM Error Messages
 
  JCLCM0094I Non-JCL record in the input stream has caused this SYSIN DD statement to be generated. This message, while it never appears in any JCL listings, is referred to in the generated SYSIN DD statement. It means that in your JCL source stream, you have one or more non-JCL records before the final // if any.
 
 
 This message is saying that the JCL source contains non-JCL lines. Referencing the IBM JCL manual, we find that valid JCL statements can contain five fields:
 
  Identifier, Name, Operation, Parameter or operand, Comments
 
 z/OS MVS JCL Reference Version 2 Release 1 08/15/13
 http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/download/IEA3B600.pdf?DT=20130815104013
 
  Chapter 3. Format of statements
  JCL statement fields
 
  Notice that IBM says that 'A JCL statement consists of one or more 80-byte records. Each record is comparable to an 80-column punched-card image.'
 
 But JCL used in Enterprise Developer can come from various sources. It can be generated by a program. It can come from other platforms. It can be edited by different text editors. Any of these means can cause a line to end in an unexpected manner triggering the error message. The JCLCM0094I error message highlights that Micro Focus has made changes to the JCL by adding a '//SYSIN DD *' statement after internally recognizing invalid lines and has 'fixed' them by adding our generated statement so the JCL can continue. The programmer should fix those bad lines. It may be necessary to view the JCL in a Hex Editor.


#MFDS
#EnterpriseDeveloper

0 replies

Be the first to reply!