View previous topic :: View next topic
|
Author |
Message |
rlwood
New User
Joined: 25 Jan 2019 Posts: 2 Location: United States
|
|
|
|
I have had to take over the System Support functions for our IMS DC processes since the folks who set it up retired a couple years ago. We run a Business Class Mainframe and are a very small company so our resources are very short.
During a Test System IPL this past weekend, our IMS instance was not shut down smoothly, so when Operations restarted our IMSTST 'started task', it threw an error. I will post the errors below... I found write ups for the error in an IBM manual and tried to reply. But I got another message asking for more information that I have no idea how to reply to. Again, details below. I am hoping someone can tell me what I am doing wrong - i am afraid I only know enough to be dangerous, but we really don't have anyone else with experience (I am really the DB2 DBA).
I put in a ticket with IBM, but they told me we are out of support since we are STILL running IMS V13. I know - we should upgrade! I am going to also check into seeing if we can get an upgrade in IBM support for 'old' versions since really, this isn't asking for any fix - just assistance to know how to get past a problem that WE caused! But I was hoping someone had experience with an issue like this.
We have NO IMS databases any more. (We moved to DB2 before I started with the company.) So we are just using IMS DC for transaction processing. I was hoping to just tell DBRC to ignore any errors, but I have no idea how to do that. I tried entering shut down commands, but they were ignored. I don't know what else to do at this point that I don't think will just exacerbate the problem.
Thanks for any tips anyone can provide!
Here are the errors and replies from the SYSOUT:
DFS0618A A RESTART OF A NON-ABNORMALLY TERMINATED SYSTEM MUST SPECIFY EMERGENCY BACKUP OR OVERRIDE
DFS3626I RESTART HAS BEEN ABORTED
R 27,/ERE OVERRIDE
31 DFS972A *IMS (DCCTL) AWAITING MORE INPUT*
R 31,/CHE FREEZE
32 DFS972A *IMS (DCCTL) AWAITING MORE INPUT*
The manuals I found are not specific on what 'MORE INPUT' really means.
Thank you again! |
|
Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006 Posts: 1204 Location: Dublin, Ireland
|
|
|
|
Was your restart of the IMSTST system using the/ERESTART command which then resulted in the error message? Or where you trying a normal restart?
Garry |
|
Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009 Posts: 2481 Location: Netherlands, Amstelveen
|
|
|
|
DFS972A *IMS (DCCTL) AWAITING MORE INPUT
That means a multisegment message was started.
So maybe more info can be found in the IMSlog, or answer with a period. |
|
Back to top |
|
|
rlwood
New User
Joined: 25 Jan 2019 Posts: 2 Location: United States
|
|
|
|
Thank you for replying!
I was able to get past our issue - and yes, the period was one issue we had! I entered that, and was then able to move on.
But the reason we were in this situation at all, was our IPL Documentation said to enter /NRE, when we should have entered /ERE OVERRIDE. after the failure on the Shutdown procedures! So we had 2 errors.
We are in good shape now. Thanks again for your responses... |
|
Back to top |
|
|
Gary Jacek
New User
Joined: 17 Dec 2007 Posts: 64 Location: Victoria, BC, Canada
|
|
|
|
rlwood wrote: |
Thank you for replying!
I was able to get past our issue - and yes, the period was one issue we had! I entered that, and was then able to move on.
|
When training new IMS people I always told them that some commands required a period as the final character. With this in mind, if you use a period at the end of every IMS command, you won't run into this problem of IMS waiting for more input. |
|
Back to top |
|
|
|