ADSM-L

Reply to S0C4 in ADSM/MVS 2.1

1996-08-12 12:52:00
Subject: Reply to S0C4 in ADSM/MVS 2.1
From: Mike Stewart <STEWAJM AT AUDUCADM.DUC.AUBURN DOT EDU>
Date: Mon, 12 Aug 1996 10:52:00 -06
*** Original Author:  ADSM-L @ MARIST - ** Remote User **; 08/12/96 04:19am

>Received: from VM.MARIST.EDU by AUDUCADM.DUC.AUBURN.EDU (IBM MVS SMTP V3R1)
>   with TCP; Mon, 12 Aug 96 04:19:24 CDT
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (IBM VM SMTP V2R3)
>   with BSMTP id 5075; Mon, 12 Aug 96 05:17:42 EDT
>Received: from VM.MARIST.EDU (NJE origin LISTSERV@MARIST) by VM.MARIST.EDU
> (LMail V1.2b/1.8b) with BSMTP id 3093; Mon, 12 Aug 1996 05:17:41 -0400
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (LISTSERV release 1.8b) with NJE
>          id 0935 for ADSM-L AT VM.MARIST DOT EDU; Mon, 12 Aug 1996 05:17:38 
> -0400
>Received: from MARIST (NJE origin SMTP@MARIST) by VM.MARIST.EDU (LMail
>          V1.2b/1.8b) with BSMTP id 3081; Mon, 12 Aug 1996 05:17:38 -0400
>Received: from klm.nl by VM.MARIST.EDU (IBM VM SMTP V2R3) with TCP; Mon, 12 Aug
>          96 05:17:37 EDT
>Received: by fly.klm.nl id <20481>; Mon, 12 Aug 1996 10:17:29 +0100
>X-Mailer: Internet Series for Microsoft Mail ( V2.0.1B )
>Mime-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>Message-ID:  <96Aug12.101729gmt+0100.20481 AT fly.klm DOT nl>
>Date:         Mon, 12 Aug 1996 12:00:00 +0100
>Reply-To:     "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>Sender:       "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>From:         Eric van Loon <evanloon AT KLM DOT NL>
>Subject:      S0C4 in ADSM/MVS 2.1
>To:           Multiple recipients of list ADSM-L <ADSM-L AT VM.MARIST DOT EDU>
>
Hi ADSM-ers!
We are running ADSM on our MVS test partition. Because we haven't installed
 TCP/IP for MVS yet I specified the TCPNAME *NONE* parameter in our server
 option file. If you don't,  ADSM will issue a error message on the console each
 half hour.
This however causes a S0C4 abend when shutting down the server. If we comment
 out this parameter again, ADSM shuts down fine.
Has anybody seen this before?
Kind regards,
Eric van Loon (evanloon AT klm DOT nl)

*** Comments From: STEWAJM - Stewart, Mike; 08/12/96 10:49am

I haven't seen that specific problem, but I do get an 0C4 if
TCP/IP goes down underneath ADSM.  In our re-IPL procedures,
TCP/IP will occasionally get shutdown before ADSM is down,
and we get:
ANR5965I Console command:  HALT
ANR5093E Unable to establish TCP connection - accept error.
ADSM abending: MVS Abend code 000C4000 generated at location 8667D3E8

CPU 0 General Registers at Entry to Abend:
R00 = 320D9E8E 856E0166 00000023 8667D382
R04 = 0667F388 00000000 06D00878 00000000
R08 = 00000000 06A266A0 06E0EBB4 06A266A0
R12 = 06C26000 06B243E8 8667D3E0 320D9E8E

.
.
.
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=0C4  REASON CODE=00000004
 TIME=03.49.18  SEQ=03444  CPU=0000  ASID=0032
 PSW AT TIME OF ERROR  078C0400   8667D3E8  ILC 4  INTC 04
   ACTIVE LOAD MODULE           ADDRESS=06600F60  OFFSET=0007C488
   NAME=DSMSERV
   DATA AT PSW  0667D3E2 - D0A850F0  812058F0  313E05EF
   GPR  0-3  320D9E8E  856E0166  00000023  8667D382
   GPR  4-7  0667F388  00000000  06D00878  00000000
   GPR  8-11 00000000  06A266A0  06E0EBB4  06A266A0
   GPR 12-15 06C26000  06B243E8  8667D3E0  320D9E8E
 END OF SYMPTOM DUMP
IEF450I ADSM ADSM - ABEND=S0C4 U0000 REASON=00000004
<Prev in Thread] Current Thread [Next in Thread>
  • Reply to S0C4 in ADSM/MVS 2.1, Mike Stewart <=