Why am I getting a S0C4 abend in IMS program with XRST call?

Document ID : KB000014831
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

Doing an IMS Restart after taking checkpoints. 

Question:

Why am I getting a S0C4 abend in IMS program with XRST call?

Environment:
Doing an IMS XRST after doing multiple CHKP's in a program.
Answer:

There isn't a DLI context in your Easytrieve program..  

The customer's program has the following:  

JOB INPUT NULL 

 

It should be similar to: 

JOB INPUT PARTFILE 

 

Where, PARTFILE is declared as: 

FILE PARTFILE DLI (DI21PART 1)

 

I've added the PARTFILE....., but I think this is more for automating the process of reading through an IMS database which this program doesn't do. Adding the filename to the JOB parameter the compiler then asks for a RETRIEVE statement to be added, but as there are no IMS databases to read, there is nothing to put in a RETRIEVE. 

 

 

Additional Information:

I've added the PARTFILE, but I think this is more for automating the process of reading through an IMS database which this program doesn't do. After adding the filename to the JOB parameter, the compiler then asks for a RETRIEVE statement to be added, but as there are no IMS databases to read, there is nothing to put in a RETRIEVE. 

Check pointing is working in other recently compiled Easytrieve programs, but these all have 'proper' IMS calls in them - reading/writing to databases etc. "