Date:         Wed, 5 Apr 2000 20:41:18 +1200
Reply-To:     Don Stanley <don_stanley@XTRA.CO.NZ>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Don Stanley <don_stanley@XTRA.CO.NZ>
Organization: Xtra
Subject:      MVS -- U1319, No MKLES
Content-Type: text/plain; charset=us-ascii

I've struck this error many times over the years. Sometimes I've found
my code needs tweaking, like when I had a massive format in a CNTLIN
dataset that wasn't sorted by the START variable. Sorting got round the
problem. SAS themselves document many usage notes and zaps relating to
this. As I understand it, its generally an indicator of a memory
shortage. But I've found no-one, not even at SAS, who can tell me what
MKLE's means.

Can someone enlighten me?

Just as a point of interest, when I strike this problem, I almost always
use the MEMSIZE=0 invocation option as a first try at circumventing it.
I call this a 95% fix, the other 5% of the time I end up rewriting the
code. Today we put a new job into production. We have run it in test 20,
maybe 30 times. Bam. U1319 immediately. Only differences I can tell are
it runs under CONTROL-M (a scheduler) and it runs in a production
service class. The step that failed appears to be setting 13 datasets
(SET A B C ....), all with same structure, and all having a fairly small
number of variables. About 4000 records per dataset. I switched on
MEMSIZE=0 at invocation and its fine. I'd love to know what causes this
in the first place.

Don
--
Don Stanley, B.SC, Dip O.R.S, MNZCS     Director, Sysware Consulting
Group
                                        Box 634, Wellington, NEW ZEALAND

                                        http://www.sysware.co.nz
EMAIL:: don_stanley@xtra.co.nz
http://www.geocities.com/don_stanley_nz/don_home.htm
Genealogy:: http://www.geocities.com/don_stanley_nz/family.htm