|
View previous topic :: View next topic
|
| Author |
Message |
DeepaBala
New User
Joined: 20 Feb 2007
Posts: 13
Location: Trivandrum
|
|
|
|
HI,
I am runing the Jcl. It runs the cobol program of display the content in the IMS/DB. At the time of compile NO error in cobol.
But Run time I got the abend S000 U0616 |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Look in your code to see if the program issues a User0616 abend.
If your program (and any called module) does not issue the 0616 abend, look in the IMS documentation.
The User0616 was "planned for", so you need to find which code generated it.
Look in ALL of your output datasets for info and post any messages back to the forum. |
|
| Back to top |
|
|
Bitneuker
CICS Moderator
Joined: 07 Nov 2005
Posts: 1104
Location: The Netherlands at Hole 19
|
|
|
|
Are you sure you are just displaying? If so is this program running in a region where updates to the database are made by other programs? This is what the documentations says about 0616:
| Quote: |
0616
Explanation:
A permanent I/O error occurred on the last remaining IMS log data set. If dual logging is in effect for IMS batch, this will occur when both of the log data sets are damaged. For IMS online, this will occur when the last remaining OLDS has a permanent I/O error or does not have enough space to complete a checkpoint freeze.
System action:
IMS terminates abnormally.
Programmer response:
Allocate new log data sets to replace the ones which have encountered I/O errors. It might be necessary to use the Log Recovery Utility to create log data sets free from write or close errors. When sufficient log data sets are available, emergency restart IMS to resume processing.
|
|
|
| Back to top |
|
|
|
|
