Skip to main content

CASSI9012E JCL support failed to start. Error returned from casspool, RC=0012 .

  • April 17, 2020
  • 4 replies
  • 0 views

I did Microfocus enterpriser developer and PostgreSQL integration setup and it was successful.
And I edited SQL Preprocessor settings of project , to make project compatible to run SQL queries.
But now , when i am trying to submit JCL to JES , i am not able to submit the same and getting below error .
 
CASSI9012E JCL support failed to start. Error returned from casspool, RC=0012 .
 
And now if i am going to create any new project , JES option under resources tab of  Enterpriser Server Administrator -->Server-->Control-->ES Monitor &  Control is not visible.
Please note that option Server-->MSS-->JES is enabled .
 
I have attached log screenshot for the same

#EnterpriseDeveloper

4 replies

  • Author
  • Rocketeer
  • 19312 replies
  • April 20, 2020
I did Microfocus enterpriser developer and PostgreSQL integration setup and it was successful.
And I edited SQL Preprocessor settings of project , to make project compatible to run SQL queries.
But now , when i am trying to submit JCL to JES , i am not able to submit the same and getting below error .
 
CASSI9012E JCL support failed to start. Error returned from casspool, RC=0012 .
 
And now if i am going to create any new project , JES option under resources tab of  Enterpriser Server Administrator -->Server-->Control-->ES Monitor &  Control is not visible.
Please note that option Server-->MSS-->JES is enabled .
 
I have attached log screenshot for the same

#EnterpriseDeveloper
Hello All ,

Is there any update on the issue ?


  • Author
  • Rocketeer
  • 19312 replies
  • April 20, 2020
I did Microfocus enterpriser developer and PostgreSQL integration setup and it was successful.
And I edited SQL Preprocessor settings of project , to make project compatible to run SQL queries.
But now , when i am trying to submit JCL to JES , i am not able to submit the same and getting below error .
 
CASSI9012E JCL support failed to start. Error returned from casspool, RC=0012 .
 
And now if i am going to create any new project , JES option under resources tab of  Enterpriser Server Administrator -->Server-->Control-->ES Monitor &  Control is not visible.
Please note that option Server-->MSS-->JES is enabled .
 
I have attached log screenshot for the same

#EnterpriseDeveloper

We need proper diagnostic material to have any hope of diagnosing the situation. Attach the actual log files, not screenshots, please.


  • Author
  • Rocketeer
  • 19312 replies
  • April 21, 2020

We need proper diagnostic material to have any hope of diagnosing the situation. Attach the actual log files, not screenshots, please.

Hi  

Thanks for your reply.

Please find attached diagnosis logs 


  • Author
  • Rocketeer
  • 19312 replies
  • April 27, 2020

Hi  

Thanks for your reply.

Please find attached diagnosis logs 

That's just the console log (and when submitting diagnostics files, please keep their original names - console.log in this case). But it's sufficient this time to identify the problem:

200420 17385871 9676 PGSERVER JES000011E Batch Spool File Error; SPLJOB Status Open I/O 9/009 17:38:58

This log message identifies the issue. The spool file could not be opened.

If you search the product documentation for the message number (JES000011E) you will find this topic:

https://www.microfocus.com/documentation/enterprise-developer/ed50/ED-VS2017/HRJERHEJES000011E.html

which explains the message and tells you what to do: Look up the file status code in the message to identify the error.

The documentation also explains that a file status code of 9/009 corresponds to a COBOL Run-Time System error 009, which is documented here:

https://www.microfocus.com/documentation/enterprise-developer/ed50/ED-VS2017/HRERRHRERR0B.html

It's "directory not found". You have specified a spool-file location in a directory that does not exist (or possibly that the region cannot find because it lacks navigation permission for higher-level directories). Correct the region configuration or create the missing directory.

Reading the console log and looking messages up in the product documentation are basic debugging steps - you'll need to be prepared to take those yourself. Posting on the Community forum or contacting Customer Care for minor issues is not efficient.