LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (March 2003, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Wed, 12 Mar 2003 22:53:46 +0000
Reply-To:     sashole@bellsouth.net
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Paul Dorfman <paul_dorfman@HOTMAIL.COM>
Subject:      Re: JCL Return Code CC=0004
Comments: To: shiling99@YAHOO.COM
Content-Type: text/plain; format=flowed

>From: shiling zhang <shiling99@YAHOO.COM> > >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.

Shiling,

Usually, RC=4 is nothing to worry about.

>More interesting are that >there is no ERROR in SAS logs and all results are matched with those >under V6.09.

An error would set it higher than RC=4. Were there any warnings? But even in their absence, SAS sometimes sets RC=4 internally, even though everything looks clean (see below).

>BTW all programs run fine on both PC and UNIX platform.

So they did on MVS, only RC was set to 4 causing the uneasiness on part of

>The system guys are uncomfortable with JCL Return Code CC=0004. The >problem seem system specific and program specific.

Tell the system guys to take valerian root drops. They know full well that RC=4 is an acceptable return code, and you do not have to tie yourself in a seaknot over their hypersensitive feelings.

>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)?

First, yes. You can do it at invocation in JCL as OPTIONS='MEMSIZE=0' or at the top of the program itself as

Option memsize=0 ;

Note that I suggested memsize=0. Under v6.09, it is a common thing to do because it allows SAS to use its own mechanism of grabbing memory circumventing the value of REGION set in JCL and as a result - the safeguards associated with it. Harking back to your first question, running memory-intensive stuff (which you seem to be doing) can cause SAS to activate this mechanism (system programmers hate it vehemently) and actually set RC=4. In V8, the way SAS handles memory was changed, so that memsize=0 can only grab as much memory as the REGION value allows - a prudent decision on part of SAS and much easier on the system personnel.

Kind regards, ------------------- Paul M. Dorfman Jacksonville, FL -------------------

_________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail


Back to: Top of message | Previous page | Main SAS-L page