Date:         Wed, 12 Mar 2003 20:30:48 -0800
Reply-To:     shiling zhang <shiling99@YAHOO.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         shiling zhang <shiling99@YAHOO.COM>
Organization: http://groups.google.com/
Subject:      Re: JCL Return Code CC=0004
Content-Type: text/plain; charset=ISO-8859-1

Michael & Paul,

U guys are really hitting the nail RIGHT on its head. The number of
RC=0004 is exactly the same as the number of WARNING messages in SAS
log.

After taken care of the WARNINGS, the 'PROBLEM' is gone.

Thanks again!


mbraten@BEAR.COM (Braten, Michael Exchange) wrote in message news:<99CF65C84BD6D611BC130002B3AB23477444CE@whmsx38.is.bear.com>...
> On the Cond Code= 004  , check the LOG for a Warning message.  004 indicates
> that something non--fatal to
> the job has occurred or exists.
>
> On the issue of memsize, or other system options, that can be done on the
> EXEC line in the JCL:
>
>         //STEP1A   EXEC SAS8,OPTIONS='MEMSIZE= '
>
>
> HTH
>
> > -----Original Message-----
> > From: shiling zhang [SMTP:shiling99@YAHOO.COM]
> > Sent: Wednesday, March 12, 2003 11:48 AM
> > To:   SAS-L@LISTSERV.UGA.EDU
> > Subject:      JCL Return Code CC=0004
> >
> > I have 6 SAS pgms that run on mainframe/TSO. The 6 SAS programs are
> > basicly same thing and differ in CLASS and MODEL stetments in PROC
> > GLM. All programs run fine under V6.09. But 4 of them have JCL Return
> > Code CC=0004 instead of CC=0000 under V8.1. More interesting are that
> > there is no ERROR in SAS logs and all results are matched with those
> > under V6.09. BTW all programs run fine on both PC and UNIX platform.
> >
> > The system guys are uncomfortable with JCL Return Code CC=0004. The
> > problem seem system specific and program specific.
> >
> > The question is
> >
> > Is there any way to allocate memsize on MAINFRAME when it kick off a
> > SAS job instead of using the default one(see log for default size
> > below)?
> >
> > Equivelant to,
> >
> > sas -memsize 2g
> >
> > on UNIX
> >
> >
> > Please details in 'HOW'. I am not good at TSO/JCL.
> >
> > TIA.
> >
> >
> >  NOTE: The initialization phase used 0.08 CPU seconds and 5920K.
> >  1    data _null_;
> >  2      x=getoption('memsize');
> >  3      put x=;
> >  4    run;
> >
> >  x=106954752
> >  NOTE: The DATA statement used 0.01 CPU seconds and 7225K.
>
>
> ***********************************************************************
> Bear Stearns is not responsible for any recommendation, solicitation,
> offer or agreement or any information about any transaction, customer
> account or account activity contained in this communication.
> ***********************************************************************