Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Accessing a dialog thru DME or ADSC causes abend

158 views
Skip to first unread message

Mundy, Joseph

unread,
Dec 28, 2000, 2:34:40 PM12/28/00
to
Our developers had been working on a dialog when it became unaccessable by
DME or ADSC.

When I try to go to the dialog thru ADSC, I get the following abend:
PREVIOUS TASK ABENDED WITH ABEND CODE D002 AND MESSAGE CODE 001003
V38 IDMSMPGD SYSTEM WIDE AMPS DEV ENTER NEXT TASK CODE:

and the log shows:

14:11 IDMS DC001003 V38 T5044 TASK:ADS2 PROG:ADSCDSTB STALLED WAITING FOR
PROGRAM MPSDP171
14:11 IDMS DC027007 V38 T5044 TASK:ADS2 PROG:ADSCDSTB ABENDED WITH CODE
D002

MPSDP171 is the dialog in question at our site.

CA was great in helping me find an APAR which updated messages on ADSM to
tell me the dialog at one time was checked out from the wrong dictionary but
I was hoping someone else had encountered this type problem when a dialog
goes in limbo.

I have successfully generated the dialog via batch with ADSOBCOM but
accessing the dialog online blows up every time. And the CV otherwise is
functioning just fine.

Any help greatly appreciated!

Joseph E. Mundy II
Information Resources - Data Services
Southern Company Services
> * 770 840 3672 or internal 8 529 3672
* jem...@southernco.com

lpet...@csc.com

unread,
Dec 28, 2000, 2:43:19 PM12/28/00
to
I have found dialog checkout thru ADSM filled with mysteries. The same
with queue records that get created everytime a dialog is compiled. The
software seems to assume there's only one compile a day. Generally I
delete checkouts in ADSM and then create a new checkout.

Lutz Petzold


"Mundy, Joseph" <JEM...@SOUTHERNCO.COM>@LISTSERV.IUASSN.COM> on 12/28/2000
02:32:07 PM

Please respond to IDMS Public Discussion Forum <IDM...@LISTSERV.IUASSN.COM>

Sent by: IDMS Public Discussion Forum <IDM...@LISTSERV.IUASSN.COM>


To: IDM...@LISTSERV.IUASSN.COM
cc:

Subject: Accessing a dialog thru DME or ADSC causes abend

drea...@hannaford.com

unread,
Dec 29, 2000, 9:56:33 AM12/29/00
to
Joseph. I believe I have encountered this before. Try releasing any
checkouts and deleting any queues that contain MPSDP171. The queues can be
found by using the qued prompt command.

"Mundy, Joseph"
<JEMUNDY@SOUTHERNC To: IDM...@LISTSERV.IUASSN.COM
O.COM> cc:
Sent by: IDMS Subject: [IDMS-L] Accessing a dialog thru DME or ADSC causes
Public Discussion abend
Forum
<IDMS-L@LISTSERV.I
UASSN.COM>


12/28/00 02:32 PM


Please respond to
IDMS Public
Discussion Forum

0 new messages