"SESSMEM - INSUFFICIENT STORAGE TO SATISFY MEMORY REQUEST" error message may be issued if too much session memory is acquired by a session.
Welcome to "KB Articles"
"SESSMEM - INSUFFICIENT STORAGE TO SATISFY MEMORY REQUEST" error message may be issued if too much session memory is acquired by a session.
book
Article ID: KB0085375
calendar_today
Updated On: 01-14-2017
Products
Versions
TIBCO Object Service Broker for z/OS
-
Not Applicable
-
Description
Resolution: "SESSMEM - INSUFFICIENT STORAGE TO SATISFY MEMORY REQUEST" error message may be issued if too much session memory is acquired by a session, followed by messages: S6BDR002E ERROR=U2168 S6BDRSES.SESSMEM +00778 VERSION=06/08/07 18.55 V5R0M0123 IEA995I SYMPTOM DUMP OUTPUT USER COMPLETION CODE=2168
Message "SESSMEM - INSUFFICIENT STORAGE TO SATISFY MEMORY REQUEST" is issued for several reasons: 1) the user's session has exceeded the SESSIONMEMMAX= limit 2) insufficient virtual storage is available to satisfy a z/OS GETMAIN request and the storage request was unconditional 3) an internal storage management control block is found to be in error
In all cases, a U2168 abend will be issued by SESSMEM: S6BDR002E ERROR=U2168 S6BDRSES.SESSMEM +00778 VERSION=06/08/07 18.55 V5R0M0123 IEA995I SYMPTOM DUMP OUTPUT USER COMPLETION CODE=2168
Environment: z/OS running TIBCO Object Service Broker for z/OS 5.0.0 sessions
Symptoms: Symptoms include: 1) on session "INFORMATION LOG": SESSMEM - INSUFFICIENT STORAGE TO SATISFY MEMORY REQUEST 2) on Execution Environment JES log: S6BDR002E ERROR=U2168 S6BDRSES.SESSMEM +00778 VERSION=06/08/07 18.55 V5R0M0123 IEA995I SYMPTOM DUMP OUTPUT USER COMPLETION CODE=2168 and possibly message: S6BST001E STORAGE MANAGER ERROR: GETMAIN REQUEST FAILED; SPID=34,LENGTH=00040000,RETCODE=00000004
Cause: This message is issued for several reasons: 1) the user's session has exceeded the SESSIONMEMMAX= limit 2) insufficient virtual storage is available to satisfy a z/OS GETMAIN request and the storage request was unconditional 3) an internal storage management control block is found to be in error
Resolution: 1) if you have reached SESSIONMEMMAX= limit, you might consider increasing the SESSIONMEMMAX= limit or rewriting your application to use less storage. 2) if there is insufficient z/OS virtual storage available, consider raising the JCL REGION= limit in the Execution Environment (CICS/TS, Native Execution Environment etc) job step. In a CICS/TS environment you might consider using or increasing the CICSREGIONSIZE= parameter to provide additional virtual storage for Object Service Broker sessions. Review the message: S6BST301I STORAGE AVAILABLE AT STARTUP IS nnnnK OF 24 BIT AND nnnnnnK OF 31 BIT which will indicate the largest piece of virtual storage that is available both below and above the line for Object Service Broker Execution Environment's usage. You may find that z/OS system exits are limiting the virtual storage available to your EE despite your REGION settings. in this case, contact your z/OS systems programmer for assistance.
Reference: 1) TIBCO® Object Service Broker Parameters Software Release 5.0 2) TIBCO® Object Service Broker Messages With Identifiers Software Release 5.0 3) TIBCO® Object Service Broker Messages Without Identifiers Software Release 5.0 4) IBM z/OS MVS Initialization and Tuning Guide 5) IBM z/OS MVS Initialization and Tuning Reference 6) TIBCO internal problem reports: CR 1-ASS7U3 -requesting a reason code to distinguish different reasons for message "SESSMEM - INSUFFICIENT STORAGE TO SATISFY MEMORY REQUEST" CR 1-ATH7U3 -requesting documentation of messages issued from SESSMEM
Issue/Introduction
"SESSMEM - INSUFFICIENT STORAGE TO SATISFY MEMORY REQUEST" error message may be issued if too much session memory is acquired by a session.