Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

If you are using the OS/390 Spawner and in SYS1.PARMLIB(BPXPRM**) you
have a MAXASSIZE=2G, when you attempt to connect to the spawner, the
session will not establish and the following messages will be written
to the system console:

  IEF403I SPAWNER - STARTED
   +Requested MEMLEAVE=524288 exceeded available REGION=-   Z Y   Y
   +Requested MEMSIZE=-1 exceeded available REGION=-   Z Y   Y
   +MEMSIZE reset to 2146959360
   +Requested MEMLEAVE=524288 exceeded available REGION=-   Z Y   Y
   +INVALID VALUE SPECIFIED FOR OPTION MEMLEAVE IN CONFIG FILE
   +Requested MEMSIZE=2146959360 exceeded available REGION=-   Z Y   Y
   +MEMSIZE reset to 2146959360

and the SAS Log will show these messages:

ERROR: A communication subsystem partner link setup request failure has
occurred.
ERROR: recv call failed, lost connection with client.
ERROR: Remote signon to xxxxxxxx.SPAWNER canceled


This problem is caused by an internal overflow error.  The MAXASSIZE=2G
is not a recommended value and the circumvention is to lower the
MAXASSIZE in BPXPRM** to the default of 40M.


You can change this BPXPRMxx value without an IPL:

   *The SET OMVS and SETOMVS operator commands dynamically change the
    settings system-wide.

    setomvs maxassize=41943040

   *The RACF ALTUSER or ADDUSER commands apply settings on a per-user
    basis for a particular user. You can use them for the MAXASSIZE.

A Technical Support hot fix for Release 8.2 TSLEVEL TS2M0 for this issue
is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#005971

For customers running SAS with Asian Language Support (DBCS), this hot
fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/82_dbcs_prod_list.html#005971

Operating System and Release Information

A fix for Release 8.2 (TS2M0) for this issue is available at:

A fix for Release 8.2 (TS2M0) for this issue is available at:

A fix for Release 8.2 (TS2M0) with Asian Language Support (DBCS) for this issue is available at: