ABAP / SAP memory

Hi Friends,
Kindly give me  sample programs, for ABAP Memory and SAP memory.
TIA.
Regards,
MARK K

Hi,
DATA TEXT1(10) VALUE 'Exporting'.
DATA ITAB LIKE SBOOK OCCURS 10 WITH HEADER LINE.
DO 5 TIMES.
  ITAB-BOOKID = 100 + SY-INDEX.
  APPEND ITAB.
ENDDO.
EXPORT TEXT1
       TEXT2 FROM 'Literal'
  TO MEMORY ID 'text'.
EXPORT ITAB
  TO MEMORY ID 'table'.
In this example, the text fields TEXT1 and TEXT2 are stored in the ABAP memory of program SAPMZTS1 under the name "text". The internal table ITAB is stored under the name "table".
DATA TEXT1(10) VALUE 'Exporting'.
DATA ITAB LIKE SBOOK OCCURS 10 WITH HEADER LINE.
DO 5 TIMES.
  ITAB-BOOKID = 100 + SY-INDEX.
  APPEND ITAB.
ENDDO.
EXPORT TEXT1
       TEXT2 FROM 'Literal'
  TO MEMORY ID 'text'.
EXPORT ITAB
  TO MEMORY ID 'table'.
SUBMIT SAPMZTS2 AND RETURN.
SUBMIT SAPMZTS3.
The first part of this program is the same as the example in the section Saving Data Objects in Memory. In the example, the programs SAPMZTS1 and SAPMZTS2 are called using SUBMIT. You can create and maintain the programs called using the SUBMIT statement by double-clicking their names in the statement. For further information about the SUBMIT statement, refer to Calling Executable Programs (Reports)
Example for SAPMZTS2:
PROGRAM SAPMZTS2.
DATA: TEXT1(10),
      TEXT3 LIKE TEXT1 VALUE 'Initial'.
IMPORT TEXT3 FROM MEMORY ID 'text'.
WRITE: / SY-SUBRC, TEXT3.
IMPORT TEXT2 TO TEXT1 FROM MEMORY ID 'text'.
WRITE: / SY-SUBRC, TEXT1.
Example for SAPMZTS3:
PROGRAM SAPMZTS3.
DATA JTAB LIKE SBOOK OCCURS 10 WITH HEADER LINE.
IMPORT ITAB TO JTAB FROM MEMORY ID 'table'.
LOOP AT JTAB.
  WRITE / JTAB-BOOKID.
ENDLOOP.
DATA: TEXT(10) VALUE '0123456789',
      IDEN(3)  VALUE 'XYZ'.
EXPORT TEXT TO MEMORY ID IDEN.
TEXT = 'xxxxxxxxxx'.
IMPORT TEXT FROM MEMORY ID IDEN.
WRITE: / SY-SUBRC, TEXT.
FREE MEMORY.
TEXT = 'xxxxxxxxxx'.
IMPORT TEXT FROM MEMORY ID IDEN.
WRITE: / SY-SUBRC, TEXT.
The output is
0 0123456789
4 xxxxxxxxxx
The FREE MEMORY statement deletes the data cluster "XYZ". Consequently, SY-SUBRC is 4 after the following IMPORT statement, and the target field remains unchanged.
sap memory
TABLES SBOOK.
START-OF-SELECTION.
  WRITE: 'Select a booking',
  SKIP.
GET SBOOK.
  WRITE: SBOOK-CARRID, SBOOK-CONNID,
         SBOOK-FLDATE, SBOOK-BOOKID.
  HIDE:  SBOOK-CARRID, SBOOK-CONNID,
         SBOOK-FLDATE, SBOOK-BOOKID.
AT LINE-SELECTION.
  SET PARAMETER ID: 'CAR' FIELD SBOOK-CARRID,
                    'CON' FIELD SBOOK-CONNID,
                    'DAY' FIELD SBOOK-FLDATE,
                    'BOK' FIELD SBOOK-BOOKID.
  CALL TRANSACTION 'BOOK'.
Thanks, 
Das............

Similar Messages

  • SAP paging overflow when storing data in the ABAP/4 memory.

    I am trying to create a data source in  BI7.0 in the Datawarehousing Workbench. But along the process when i need to select a view i get an error detailed in the following error file extract: Please go through and assist.
    untime Errors         MEMORY_NO_MORE_PAGING
    Date and Time          06.06.2009 14:21:35
    Short text
    SAP paging overflow when storing data in the ABAP/4 memory.
    What happened?
    The current program requested storage space from the SAP paging area,
    but this request could not be fulfilled.
    of this area in the SAP system profile.
    What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    Error analysis
    The ABAP/4 runtime system and the ABAP/4 compiler use a common
    interface to store different types of data in different parts of
    the SAP paging area. This data includes the
    ABAP/4 memory (EXPORT TO MEMORY), the SUBMIT REPORT parameters,
    CALL DIALOG and CALL TRANSACTION USING, as well as internally defined
    macros (specified with DEFINE).
    To store further data in the SAP paging area, you attempted to
    allocate a new SAP paging block, but no more blocks were
    available.
    When the SAP paging overflow occurred, the ABAP/4 memory contained
    entries for 20 of different IDs.
    Please note:
    To facilitate error handling, the ABAP/4 memory was
    deleted.
    How to correct the error
    The amount of storage space (in bytes) filled at termination time was:
    Roll area...................... 8176
    Extended memory (EM)........... 13587912
    Assigned memory (HEAP)......... 0
    Short area..................... " "
    Paging area.................... 40960
    Maximum address space.......... " "
    By calling Transaction SM04 and choosing 'Goto' -> 'Block list',
    you can display an overview of the current roll and paging memory
    levels resulting from active users and their transactions. Try to
    decide from this whether another program requires a lot of memory
    space (perhaps too much).
    The system log contains more detailed information about the
    termination. Check for any unwanted recursion.
    Determine whether the error also occurs with small volumes of
    data. Check the profile (parameter "rdisp/PG_MAXFS", see
    Installation Guidelines).
    Is the disk or the file system that contains the paging file
    full to the extent that it cannot be increased, although it has
    not yet reached the size defined in the profile? Is the
    operating system configured to accommodate files of such a
    size?
    The ABAP processor stores different types of data in the SAP
    paging area. These include:
    (1) Data clusters (EXPORT ... TO MEMORY ...)
    (2) Parameters for calling programs (SUBMIT REPORT ...),
    Dialog modules (CALL DIALOG ...) and transactions
    (CALL TRANSACTION USING ...)
    (3) Internally defined program macros (DEFINE ...)
    Accordingly, you should check the relevant statements in a program
    that results in an overflow of the SAP paging area.
    It is critical when many internal tables, possibly with
    different IDs, are written to memory (EXPORT).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "MEMORY_NO_MORE_PAGING" " "
    "SAPLWDTM" or "LWDTMU20"
    "TABC_ACTIVATE_AND_UPDATE"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.

    Hi Huggins,
    Maintenance of the Paging File is owned by your basis team.
    They should increase this in order for your transaction to process successfully.
    Just for your reference, in case the OS used is windows server 2003, paging file value can be checked through;
    Right click in the My Computer>properties.
    Then go to Advance tab;
    Then there should be a performance section, click the settings
    Then Advance tab again. The paging file can be seen from there.
    (and can be adjusted from there also)
    The value of the paging file in general will be dependent with the available RAM from the hardware.
    Hope this helps. Thanks a lot.
    - Jeff

  • Examples for SAP Memory and ABAP Memory

    Hi all,
        can u give me one example of sap memory and abap memory.
                                              Ranjith

    Hi,
    <b>SAP Memory</b>
    SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be set either for a particular user or for a particular program at the time of logon using the SET PARAMETER statement. Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens .
    <b>example:</b>
    ABAP programs can access the parameters using the SET PARAMETER and GET PARAMETERstatements.
    To fill one, use:
    SET PARAMETER ID pid FIELD f
    This statement saves the contents of field f under the ID pid in the SAP memory. The ID pid can be up to 20 characters long. If there was already a value stored under pid, this statement overwrites it. If you double-click pid in the ABAP Editor, parameters that do not exist can be created as a Repository object.
    To read an SPA/GPA parameter, use:
    GET PARAMETER ID pid FIELD f.
    This statement places the value stored under the pid ID into the variable f. If the system does not find any value for pid in the SAP memory, sy-subrc is set to 4. Otherwise, it sets the value to 0.
    <b>ABAP Memory</b>
    ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this memory area remains throughout a sequence of program calls, with the exception of LEAVE TO TRANSACTION. To pass data to a program that you are calling, the data needs to be placed in ABAP memory before the call is made from the internal calling session using the EXPORT statement. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory using the IMPORT statement. If control is then returned to the program that made the initial call, the same procedure operates in reverse.If a transaction is called using LEAVE TO TRANSACTION, the ABAP memory and the call stack are deleted. They cannot be used for data transfer.
    Since objects belonging to ABAP objects can only be accessed within an internal session, it does not make sense and is therefore forbidden (from a syntax point of view) to pass a reference to an object to a calling program through the ABAP memory.
    <b>Example:</b>
    Export hello to memory id 'Hello_world'.
    Import hello from memory id 'Hello_world'
    Regards
    Sudheer

  • Hi Friends ....Difference between SAP memory and ABAP memory

    Hi Friends,
    I faced a interview and they ask this question
    What is the difference between SAP Memory and ABAP memory..

    conti
    SAP Memory
    SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement.
    Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens.
    ABAP Memory
    ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this area remains intact during a whole sequence of program calls. To pass data to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse.
    A simple example of ABAP memory is using the EXPORT/IMPORT statements.
    Here in this program, I get the data, export it to memory,
    clear out the internal table in my progam, then reimport the data into it and write out the data.
    You probably wounldn't do this in a normal program,
    but this is how you can pass data from program a to program b when A Submits program B.
    report zxy_0002 .
    data: it001 type table of t001 with header line.
    select * into table it001 from t001.
    export it001 = it001 to memory id 'ZXY_TEST'.
    clear it001. refresh it001.
    import it001 = it001 from memory id 'ZXY_TEST'.
    loop at it001.
    write:/ it001-bukrs, it001-butxt.
    endloop.
    SAP Memory
    SAP memory is a memory area to which all main sessions within a SAPgui have access.
    You can use SAP memory either to pass data from one program to another within a session,
    or to pass data from one session to another.
    Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters).
    These parameters can be set either for a particular user
    or for a particular program using the SET PARAMETER statement.
    Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement.
    The most frequent use of SPA/GPA parameters is to fill input fields on screens
    ABAP/4 Memory
    ABAP memory is a memory area that all ABAP programs within the same internal session can access
    using the EXPORT and IMPORT statements.
    Data within this area remains intact during a whole sequence of program calls. To pass data
    to a program which you are calling,
    the data needs to be placed in ABAP memory before the call is made.
    The internal session of the called program then replaces that of the calling program.
    The program called can then read from the ABAP memory.
    If control is then returned to the program which made the initial call, the same process operates in reverse.
    SAP memory
    The SAP memory, otherwise known as the global memory,
    is available to a user during the entire duration of a terminal session.
    Its contents are retained across transaction boundaries as well as external and internal sessions.
    The SET PARAMETER and GET PARAMETER statements allow you to write to, or read from, the SAP memory.
    ABAP/4 memory
    The contents of the ABAP/4 memory are retained only during the lifetime of an external session
    (see also Organization of Modularization Units).
    You can retain or pass data across internal sessions.
    The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow you to write data to, or read data from, the ABAP memory.
    ABAP Memmory & SAP Memmory
    http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm
    http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
    Set
    http://www.geocities.com/SiliconValley/Campus/6345/set_para.htm
    GET
    http://www.geocities.com/SiliconValley/Campus/6345/get_para.htm
    EXPORT
    http://www.geocities.com/SiliconValley/Campus/6345/export01.htm
    Other Imp Help
    http://www.geocities.com/SiliconValley/Campus/6345/abapindx.htm

  • Hi All,Can any provide an example for SAP MEMORY AND ABAP memory

    Hi All,
          Can any provide me an example for SAP MEMORY AND ABAP memory.
    thanks&regards.
    Bharat.

    HI Bharat
    A simple example of ABAP memory is using the EXPORT/IMPORT statements.
    Here in this program, I get the data, export it to memory,
    clear out the internal table in my progam, then reimport the data into it and write out the data.
    You probably wounldn't do this in a normal program,
    but this is how you can pass data from program a to program b when A Submits program B.
    report zxy_0002 .
    data: it001 type table of t001 with header line.
    select * into table it001 from t001.
    export it001 = it001 to memory id 'ZXY_TEST'.
    clear it001. refresh it001.
    import it001 = it001 from memory id 'ZXY_TEST'.
    loop at it001.
    write:/ it001-bukrs, it001-butxt.
    endloop.
    SAP Memory
    SAP memory is a memory area to which all main sessions within a SAPgui have access.
    You can use SAP memory either to pass data from one program to another within a session,
    or to pass data from one session to another.
    Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters).
    These parameters can be set either for a particular user
    or for a particular program using the SET PARAMETER statement.
    Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement.
    The most frequent use of SPA/GPA parameters is to fill input fields on screens
    ABAP/4 Memory
    ABAP memory is a memory area that all ABAP programs within the same internal session can access
    using the EXPORT and IMPORT statements.
    Data within this area remains intact during a whole sequence of program calls. To pass data
    to a program which you are calling,
    the data needs to be placed in ABAP memory before the call is made.
    The internal session of the called program then replaces that of the calling program.
    The program called can then read from the ABAP memory.
    If control is then returned to the program which made the initial call, the same process operates in reverse.
    SAP memory
    The SAP memory, otherwise known as the global memory,
    is available to a user during the entire duration of a terminal session.
    Its contents are retained across transaction boundaries as well as external and internal sessions.
    The SET PARAMETER and GET PARAMETER statements allow you to write to, or read from, the SAP memory.
    ABAP/4 memory
    The contents of the ABAP/4 memory are retained only during the lifetime of an external session
    (see also Organization of Modularization Units).
    You can retain or pass data across internal sessions.
    The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow you to write data to, or read data from, the ABAP memory.
    ABAP Memmory & SAP Memmory
    http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm
    http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
    Set
    http://www.geocities.com/SiliconValley/Campus/6345/set_para.htm
    GET
    http://www.geocities.com/SiliconValley/Campus/6345/get_para.htm
    EXPORT
    http://www.geocities.com/SiliconValley/Campus/6345/export01.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3bc4358411d1829f0000e829fbfe/frameset.htm
    Other Imp Help
    http://www.geocities.com/SiliconValley/Campus/6345/abapindx.htm
    Regards Rk

  • ABAP,SAP,LOCAL MEMORY

    Hi,
    Can anybody explain me the differnce b/n Global SAP memory,Local SAP memory,ABAP memory?I cud not understand in the ABAP documentation..
    Thanks,

    hi,
      SAP Memmory - use to acess memmory area between session
    eg:- when u call a transaction or report ( within ur program) want the value of the prticular field  should have value define by U.
    Then u use GET and SET parameter command
    field u set or get should have parameter ID
    Set
    http://www.geocities.com/SiliconValley/Campus/6345/set_para.htm
    GET
    http://www.geocities.com/SiliconValley/Campus/6345/get_para.htm
    EXPORT
    http://www.geocities.com/SiliconValley/Campus/6345/export01.htm
    Other Imp Help
    http://www.geocities.com/SiliconValley/Campus/6345/abapindx.htm
    MArk Helpfull answers
    Regards
    Manoj

  • SAP Memory

    hi all,
    Please tell me the code for passing a particular flag value to a SAP memory . Then calling the memory at any other location and freeing the memory thereafter.
    Also please let me know the code for disabling/enabling  a particular screen field .
    Thanks ,
    Paul

    To fill the input fields of a called transaction with data from the calling program, you can use the SPA/GPA technique. SPA/GPA parameters are values that the system stores in the global, user-specific SAP memory. SAP memory allows you to pass values between programs. A user can access the values stored in the SAP memory during one terminal session for all parallel sessions. Each SPA/GPA parameter is identified by a 20-character code. You can maintain them in the Repository Browser in the ABAP Workbench. The values in SPA/GPA parameters are user-specific.
    <b>SPA/GPA Parameters as Default Values</b>
    The SPA/GPA Parameter Technique is a general procedure for filling the initial screen when a program is called. To use this technique for parameters on selection screens, you must link the parameter to an SPA/GPA parameter from the SAP memory as follows:
    PARAMETERS <p> ...... MEMORY ID <pid>......
    If you use this addition, the current value of SPA/GPA parameter <pid> from the global user-related SAP memory is assigned to parameter <p> as a default value. Description <pid> can contain a maximum of twenty characters and must not be enclosed in quotation marks.
    REPORT DEMO.
    <b>PARAMETERS TEST(16) MEMORY ID RID.</b>
    ABAP programs can access the parameters using the SET PARAMETER and GET PARAMETER statements.
    To fill one, use:
    <b>SET PARAMETER ID <pid> FIELD <f>.</b>
    This statement saves the contents of field <f> under the ID <pid> in the SAP memory. The code <pid> can be up to 20 characters long. If there was already a value stored under <pid>, this statement overwrites it. If the ID <pid> does not exist, double-click <pid> in the ABAP Editor to create a new parameter object.
    To read an SPA/GPA parameter, use:
    <b>GET PARAMETER ID <pid> FIELD <f>.</b>
    <b>Passing Data Between Programs</b>
    There are two ways of passing data to a called program:
    Passing Data Using Internal Memory Areas
    There are two cross-program memory areas to which ABAP programs have access (refer to the diagram in Memory Structures of an ABAP Program) that you can use to pass data between programs.
    <b>SAP Memory</b>
    SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement. Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens (see below).
    <b>ABAP Memory</b>
    ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this area remains intact during a whole sequence of program calls. To pass data to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse. For further information, refer to Data Clusters in ABAP Memory.
    Filling Input Fields on an Initial Screen
    Most programs that you call from other programs have their own initial screen that the user must fill with values. For an executable program, this is normally the selection screen. The SUBMIT statement has a series of additions that you can use to fill the input fields of the called program:
    Filling the Selection Screen of a Called Program
    You cannot fill the input fields of a screen using additions in the calling statement. Instead, you can use SPA/GPA parameters. For further information, refer to Filling an Initial Screen Using SPA/GPA Parameters.
    regards
    vinod

  • In internal sessions sap memory will not use {export to...} statment

    SAP memory does not use "Export tou2026" statement for internal sessions

    hi,
    ABAP memory
    Within the same internal session
    SAP memory
    Across internal sessions
    IN SAP MEMORY
    SET PARAMETER ID <pid> FIELD <f>.-     Writes the contents of the field f to the global SAP memory under the key pid . If the key already contains a value, it is overwritten. 
    GET PARAMETER ID <pid> FIELD <f>.-     Transfers the value stored under the key pid from the global user-related SAP memory to the field f .
    IN ABAP memory
    EXPORT obj1 ... objn TO MEMORY.
    IMPORT f itab FROM MEMORY.
    hope it may help you.
    Thanks
    Sachin

  • In ST02 SAP Memory roll area readings are on disk

    Hi,
    Our production system is running on 16GB RAM and 32bit windows platforn.
    Readings in ST02 of SAP Memory , roll are readings are on disk
    Below are the parameters value configured in the production system.
    Suggest me if any changes to be done
    rdisp/ROLL_SHM                              6000
    rdisp/ROLL_MAXFS                            32768
    rdisp/PG_SHM                                6000
    rdisp/PG_MAXFS                              32768
    abap/swap_reserve                           20971520
    em/initial_size_MB                          8192
    em/blocksize_KB                             4096
    em/stat_log_size_MB                         20
    em/stat_log_timeout                         0
    em/address_space_MB                         512
    rsdb/ntab/ftabsize                          60000
    rsdb/ntab/sntabsize                         3000
    Regards
    Kumar

    Hi Kumar,
    I want to add few suggestions here, which may help here.
    rdisp/ROLL_SHM 6000 ---> increase to 16384
    rdisp/PG_SHM 6000 --> increase to 16384
    (in addition to this i have noticed that the initial records are at 60 % only)??
    If intial record buffers are filled for 60% may not be issue unless you see continuous swaps daily. If you see consecutive more swaps occuring daily, then increase the corresponding buffers to 20% of current size.
    Among all the buffers Program buffer is very important for performance. If more than 10000 swaps are occuring daily, you may incerease by 30% of current size, which surely solved your system performance issues.
    Hope this helps!!
    If you have further queries, plese let me know.
    Thanks and Regards,
    Pavan Kumar Gali.

  • Do itabs in ABAP program memory swap out when the program is swapped out?

    Do itabs in ABAP program memory swap out when the program is swapped out by the app server scheduler?
    If so, has anyone compared the time it takes to open/close an Oracle table n times with the time it takes to swap an itab of 50M in and out n times?

    Andrew -
    Although your suspicion appears to be wrong (according to the answer provided by CharlesF below), I'm awarding 6 because your answer indicates that you are at least sensitive to the issues involved here (which is better than 90% of the SAP practitioners out there.)
    However, I do want to take strong issue with you on the matter of how much available "multi-gig" memory is available, because this is irrelevant to the issue at hand.
    The question is: how does the swapin/out of large program memory affect the scheduler on the app server?
    This is a queueing theory issue that has nothing to do with how much memory is out there.
    Back in the days when folks had to know a little queueing theory (to evaluate the pro's and cons of ISO vs SNA and token-ring vs other protocols, everyone understood that if you ask the scheduler to repeatedly swap "alot" and to do so very often, then there will be a profound ripple effect on system performance, not just for anyone "job" or "program", but for any and every job or program.
    The reason is very simple, and the folks who taught the ISO/SNA seminars always used it: traffic flow on passenger highways is always best when there are few trucks travelling with the cars.  This is why the New Jersey turnpike sometimes splits into two "cars only" and "trucks and cars" highways, and why many other roads have "right lane" only restrictions for trucks in certain areas that tend to get congested ...
    Anyway, always a pleasure to chat with you ...
    Best regards
    djh

  • SAP memory - how to clear?

    Hi,
    I need to clean the SAP memory. What is the command for to do this?
    (not is clear the abap memory but sap memory)
    The command bellow not wiped the memory.
    FREE MEMORY ID 'ZDEMAND'
    best regards,
    Marcelo Bogaz

    Hi.
    Try this . By Using <b>Delete</b>.
    DELETE FROM { {MEMORY ID id}
                | {DATABASE      dbtab(ar) [CLIENT cl] ID id}
                | {SHARED MEMORY dbtab(ar) [CLIENT cl] ID id}
                | {SHARED BUFFER dbtab(ar) [CLIENT cl] ID id} }.
    Eg:.
    DELETE FROM MEMORY ID id.
    Regards
    Bala..

  • What is the diffrence betwen the sap memory &abapmemory.

    what is the diffrence betwen the sap memory &abapmemory.

    SAP memory
    The SAP memory, otherwise known as the global memory, is available to a user during   the entire duration of a terminal session. Its contents are retained across transaction   boundaries as well as external and internal sessions (see also Organization of   Modularization Units). The SET PARAMETER and GET PARAMETER statements allow you to   write to, or read from, the SAP memory.
    ABAP/4 memory
    The contents of the ABAP/4 memory are retained only during the lifetime of an external   session (see also Organization of Modularization Units). You can retain or pass data   across internal sessions. The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow  you to write data to, or read data from, the ABAP/4 memory.
    Hope it helps.
    Chang

  • SAP Memory, Set and Get parameter

    Hi All,
         I am running two programs in background from program1
    Eq: Program1 --> Calls 2 programs
                              Program1_01.(First Program)
                              Program2_01(Second Program).
    Programs1 schedules Program1_01 and Program1_02 in background. These two programs are interdependent.
    Program1_01 extracts data, evaluates and sets the Flag. This Flag is exported to SAP Memory using
    Set parameter id 'p_id_flag' field Flag.
    Program1_02 checks for Program1_01 is completed in background. If complted gets the Flag value from SAP Memory using "Get paramter id 'p_id_flag' field Flag.
    When i checked this is not happning. When saw Flag in Program1_01 is set as Flag = 'X'.
    When I came and checked in Program1_02 after Get Parameter statement Falg value is SPACE.
    Cn hlp on this?

    Hi,
    The problem simply lies in fact that pid was provided in lowercase.
    Use:
    SET PARAMETER ID 'P_ID_FLAG' FIELD flag.
    GET PARAMETER ID 'P_ID_FLAG' FIELD flag.
    It works fine then.
    Note!
    Though SAP claims it is mandatory to create pid in TPARA table, in fact this is not required. Each time SET PARAMETER is executed, system checks if data object P_ID_FLAG was defined in SAP memory. If not it will automatically create it for us. But be carefull here. If there is such data object, its value will be overwritten.
    As for your last question, your statement (FREE MEMORY ....) is ok.
    Regards
    Marcin
    Edited by: Marcin Pciak on Jan 22, 2009 1:14 PM

  • SAP Memory types?

    Hi gurus,
             Anybody pls send me Brief notes about SAP memory areas as Roll area, Paging area , extended memory and Heapmemory.anybody pls send me brief details about these memory areas.in ST02
    Regards,
    Balaram

    Hi Balaram,
    Please refer http://help.sap.com/saphelp_bw30b/helpdata/en/7a/caa6f3bfdb11d188b30000e83539c3/frameset.htm for the details,its the best documentation for the same.
    Regards,
    Sam

  • How to remove a grobal parameter in SAP memory

    As known to all, we can use SET/GET PARAMETER to pass parameters among multiple programs.
    Now I'm just curious about how to remove a grobal parameter in SAP memory, and how can I get the list of all grobal parameter in SAP memory.
    Any idea?

    Hi william,
    1. how to remove a grobal parameter in SAP memory
      Well, i dont think we can REMOVE.
       At most, we can RESET it to blank(initial)
    2. set parameter  id 'BUKRS' FIELD ''.
    regards,
    amit m.

Maybe you are looking for

  • Cannot receive calls

    I cannot receive any calls. Everything else is fine. I can call out easily and broadband is okay. When you dial my number you can hear a ringing tone for a second (although nothing sounds out on my phone), then nothing but the engaged tone. i have ca

  • Cannot copy files to, rename or unmount external HD

    When I try to copy files to my 4TB Mac Os Extended(journaled) G-drive connected via Firewire 800 I get this message "The operation can't be completed because an unexpected error occurred (error code -50)." When I verify the disk itself(the orange dis

  • Purple/Pink screen when bringing Humax Youview box...

    Hi all A quick question. Has any user successfully solved the problem of the "purple screen" when using an HDMI connection from the box to the TV. I am using a BT Humax box with a Samsung LCD flat screen TV. I have upgraded my HDMI cable to a Triple

  • Word doc help

    I have a Word document that is a table and I cut and paste, but it looks blurred both in printing and viewing.  Please help in linking.  What else can I do?  I'm a beginner.  Thanks

  • How do i validate ?

    problem : i want to validate my input with a regex. my input is "27/12/2005 15:41:20"; my validation regex pattern is "dd/MM/yyyy HH:mm:ss" How do i validate ? I did the following but i can not TRUST because of those outputs. it does not validate Str