[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sas-l
Subject:    Re: Sort abend
From:       Paul Dorfman <paul_dorfman () HOTMAIL ! COM>
Date:       2000-03-31 16:32:41
[Download RAW message or body]

Call SyncSort Product Services at (201) 930-8260. That's what SyncSort
Documentation tells: "WER999A  indicates  that  an error condition occurred,
preventing the successful completion of the sort. This message does not
necessarily mean that SyncSort was responsible for the error... WER999A
indicates that SyncSort got control: after the error, printing this SyncSort
message. The documentation accompanying WER999A varies with the  error
involved.  It  may  consist  of a standard system dump (SYSUDUMP or
SYSABEND)  and/or  a  SyncSort-generated  SNAP dump.  The  SyncSort  SNAP is
  formatted  very much like a SYSUDUMP. In debugging the SNAP,  care  must
be  taken  to avoid  reliance on the PSW AT ENTRY TO SNAP and the general
registers. (A SNAP dump produced through the SyncSort DEBUG PARM or with a
W-abend  (i.e.,  WER999A  UNSUCCESSFUL  SORT xxxW) is  only  useful  to  a
sort analyst at SyncSort MVS Product Services.)... A  W-type abend code
indicates that program termination was forced  by  an  error  condition
internally  detected by
SyncSort;  the  problem cannot be resolved by the user."

>From your dump, I am not sure whether you are using Proc SyncSort or SAS
sort that switched to host (obviously, SyncSort) because of the data volume.
When you call SS, tell them. Sorry for not being more helpful.

Kind regards,
===================Paul M. Dorfman
Jacksonville, Fl
===================
>From: Erjan <write@ERJAN.MYWEB.NL>
>Reply-To: Erjan <write@ERJAN.MYWEB.NL>
>To: SAS-L@LISTSERV.UGA.EDU
>Subject: Sort abend
>Date: Fri, 31 Mar 2000 09:26:13 +0200
>
>In order to make reports about the CICS use on our system, we use MXG
>macro's.
>The information is gathered from SMF records.
>When I tried to implement the job, it abended:
>
>+WER999A AMEG0101,JS0010  ,SAS608  -  UNSUCCESSFUL SORT 13E U
>IEA995I SYMPTOM DUMP OUTPUT
>   USER COMPLETION CODE18
>  TIME .27.35  SEQ561  CPU00  ASID32
>  PSW AT TIME OF ERROR  078D1000   80015DB4  ILC 2  INTC 0D
>    ACTIVE LOAD MODULE           ADDRESS006888  OFFSET00F52C
>    NAME=SASXAL
>    DATA AT PSW  00015DAE - 00181610  0A0D0000  00000000
>    GPR  0-3  80000000  8000013E  00000000  000041A1
>    GPR  4-7  00000001  000933E0  00000000  000933C8
>    GPR  8-11 0BFA8B08  00000000  0006B478  0BD1C3D8
>    GPR 12-15 80041000  0BFA8B38  8BD1C4EA  00015D70
>  END OF SYMPTOM DUMP
>
>As the amount of information is quite large (1 day of SMF records contain
>more than 1 billion records)
>I suspect that this abend has something to do with a space problem. The
>last
>MXG information in the job, before it abended
>(I suspect this to be the amount of '110' (cics) records in SMF) was:
>NOTE: THE DATA SET WORK.MXGSUM1 HAS 2342377 OBSERVATIONS AND 27 VARIABLES.
>NOTE: THE DATA STATEMENT USED THE FOLLOWING RESOURCES:
>       CPU     TIME -         00:00:55.68
>       ELAPSED TIME -         00:02:05.50
>       VECTOR AFFINITY TIME - 00:00:00.00
>       VECTOR USAGE    TIME - 00:00:00.00
>       RSM HIPERSPACE  TIME - 00:00:00.00
>       EXCP COUNT   - 8419
>       TASK  MEMORY - 2712K (96K DATA, 2616K PROGRAM)
>       TOTAL MEMORY - 14917K (11268K DATA, 3649K PROGRAM)
>
>Can anybody help?
>
>Erik Janssen,
>Service Support Engineer,
>Postbank NV,
>The Netherlands.

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

[prev in list] [next in list] [prev in thread] [next in thread]