ISL buffer credit allocation

Greetings,
I have four MDS switches that I intend to use as part of a DR solution with native fibre channel and a Cisco ONS. I am moving from a Brocade solution and am interesting in the buffer credits for the ISL. Each link is 2 Gpbs and eventually they will be port channels when I get a couple more links.
<quote>
255 buffer-to-buffer credits-are assigned to each port for optimal bandwidth utilization across distance.
</quote>
Does that mean the B2B credits are automagically assigned for use or we have to set them manually. The max distance in my alternate loop is 35 km. We have found that the traffic is odd and the typical B2B numbers are just not good enough. So, can I set say 70 or 105 BB credits manually to each interface that will be an ISL? If so, then which of the BB Credit options do I use? The list is interesting:
Admin Default
Extended
Admin ISL
Admin FX
and
Perf Bufs Admin.
Oddly enough, after googling a fair bit and going over my training notes, I can't find any doco on this anywhere.
Can someone please comment on this?
Stephen

Phil,
Thanks again for a response.
Do you know why there are so many B2B credits available for the interfaces compared to Brocade? Eg, a Brocade interface will only offer 3 credits on a standard interface compared to the 16 available on the MDS. This causes issues on heavily worked interfaces. Also, after forking out a sum of money to get long distance mode for the Brocade, the maximum is still less that the standard of 255 for ISL's.
Isn't a buffer credit the same for all vendors devices? In relatively simple terms, it lets you extend a 1 Gpbs FC interface up to 2 kilometres. So a 2 Gpbs interface over 32 kilometres would require 64 buffer credits. Was Cisco planning for 8 Gpbs interfaces when they did the buffer credit allocation?
I wonder how the Nexus does this?
Stephen

Similar Messages

  • Buffer-to-buffer credit management scheme of ONS 15454

    Both 15454 SL card (MSPP) and MXP_M_10DME(MSTP) have a buffer-to-buffer credit management scheme to provide FC flow distance extension.
    I can not find any document about a buffer-to-buffer credit management scheme.
    Q1) Are there any buffer-to-buffer credit management scheme difference between 15454 SL card (MSPP) and MXP_M_10DME(MSTP) ?
    Q2)Are there any buffer-to-buffer credit management scheme presentation documents of 15454 SL card (MSPP)?

    Try these links:
    http://www.cisco.com/en/US/products/hw/optical/ps2006/products_technical_reference_chapter09186a00803b3a62.html
    http://www.cisco.com/en/US/products/hw/optical/ps2006/products_white_paper0900aecd8044aa6d.shtml

  • Authorizations in Credit Management

    Hi,
      There is a requirement to control the release of the Blocked Sales Orders due to credit check through a customized transactions. For this a Z transaction has been developed which will have a list of Sales orders which are blocked due to Credit Check. In this case Authorized users need to release the sales orders from the check for further processing. The release of the sales orders Authorization is given to set of people who will release the sales orders based on the Document value.For example if the document value is upto 1000pounds, XYZ user will release the sales order. If 1000 to 3000 pounds, ABC user will release the order. In this case system should not allow the XYZ user to release the sales order or value more than 1000 pounds. Can we control this through Authorization? If yes can you please brief about the same.
    Thanks in advance.
    Regards
    Narendra

    For maintaining authorization:
    SPRO --> IMG >SD> BF> CM/RM> CM/RM settings --> Maintain authorizations
    <b>Document Value Class:</b>
    Document value classes provide a means of assigning sales order and sales and distribution documents depending on their document value
    Using the document value classes, credit representatives, for example, can be given different authorizations for credit allocations depending on the document value.
    Actions
    1. Create document value classes according to your requirements by entering a three-character alphanumeric key and a textual description.
    2. Make sure that the credit representatives are allocated to the document value classes.
    Assign Document value Classes:
    1. Enter a credit control area and allocate a credit value to it in a relevant currency.
    2. Allocate a document value class.
    3. Make sure that the credit control area was entered in the corresponding customer master records.
    Maintain Authorizations:
    Here u need to create roles and for perticular user , you can assign that authorizations.
    If you need more help prefer implementation guide in help.sap.com

  • Regarding program buffer

    hi sapgurus,
    in st02 ,i checked that the hit ratio of the program buffer is 73%
    in st06 my current swap size is 34,830,140 30,414,708 25,600,000
    the parameter abap/buffersize has certain values
    parmeter value 700000
    unsubstited standard value-150000
    substituted value -150000
    comment
    #old_value :550000
    i want to increase the hit ratio up 99%
    what is change i have to do,and which value i have to change and how much.
    please it is bit urgent
    the windows 64bit machine and the sap release 700
    please do help to get result
    regards
    rahul

    Based on what logic do you raise it to these values?
    You have no idea as to the modules used within the system.
    You have no idea as to the number of users on the system.
    You have no idea as to the number of app servers.
    You have no idea as to how load balancing is happening (SMLG).
    You have no idea as to the amount of memory in the server.
    Before changing anything we need to understand why we have a hit rate of only 73% in the first place, Then and only then do we take the most appropriate action, which may, or may not be changing the value stated.
    This is from a app server thats part of a SAP system for 11,000 users on Z-OS
    abap/heap_area_dia                          10000000
    abap/heaplimit                              10000000
    abap/heap_area_nondia                       10000000
    <b>abap/buffersize                             900000</b>
    rsdb/cua/buffersize                         30000
    sap/bufdir_entries                          9000
    zcsa/presentation_buffer_area               120000000
    zcsa/table_buffer_area                      280000000
    zcsa/db_max_buftab                          60000
    My point is dont just change it, correct the problem! it doesnt need to be the bigest number you can think of or get away with. it needs to be balanced.
    My hit ratio is 99.96 and i wager with 1000s more users.
          Buffer            Hitratio   Allocated         Free space        Dir. size      Free directory         Swaps
                               [%]       [kB]         [kB]         [%]      Entries      Entries       [%]
    Program                   99.96       927,192       24,194     2.69       225,000      206,972    91.99        11,796
    The hit ratio is of what has been provided by the buffer rather than by direct DB access. However the buffer could well have been paged out to disk millions of times and still indicate a 99.9% rate.
    Ask yourself are you doing new things, are you doing them for the first time since a reboot?

  • Copying Goods return to AP Credit note

    Hi all,
    We've returned some goods to a supplier, so we do a goods return on SAP, so that credits stock and Debits allocation account.
    Our supplier has sent us an AP credit note. So we 'copy to' AP Credit (from Goods return) and the automatic journal entry is Credit Allocation account Debit Accounts payable.
    My question is, all of the above entries are balance sheet entries. Shouldn't a goods return have some 'income' effect on the P&L?
    Thanks for any help...

    When you make good return
    Then
    Goods Receipt Not Invoice   Debited(Liability )
    Inventory Account                Credited(Asset)
    And when you make A/P Credit note based on Good Return,
    Vendor Account                     Debited(Liability)
    Tax Account                           Credited(Asset)
    Goods Received Not Invoice  Credited(Liability)
    so i think  ,there are not any ledger belong from P & Loses .
    Thanks
    manvendra

  • REDO ALLOCATION LATCH와 REDO COPY LATCH에 대해서

    제품 : ORACLE SERVER
    작성날짜 : 2000-08-28
    REDO ALLOCATION LATCH와 REDO COPY LATCH에 대해서
    ========================================================================
    redo log buffer 사용 시 wait 비율이 높은 경우 log buffer의 크기 조정 외에도
    redo에 관한 latch를 조정함으로써 성능을 향상시킬 수 있다.
    여기에서는 redo allocation latch와 redo copy latch의 작동 원리와, tuning
    방법 등을 설명한다. 그리고 8i에서의 변경 사항도 포함하였다.
    1. redo entry를 redo log buffer에 할당하는 방법
    database에 변경 작업을 수행하는 server process는 PGA 부분에 변경 작업에 대한
    redo entry를 만든다. 그리고 이것을 redo log buffer에 옮기는데, 이 때 먼저
    할당될 redo log buffer의 부분을 allocation하고, 그 이후에 allocation 된
    redo log buffer 공간에, PGA 상에 만들어 둔 redo entry를 copy한다.
    Oracle은 SGA 내에서 발생하는 source code의 action의 serialization을 위해서
    latch를 사용한다. 즉, log buffer에서 redo entry를 save시킬 공간을 할당하는
    작업 절차도 먼저 latch를 부여받은 process가 작업하는 것이고, 할당받은
    공간에 redo entry를 copy시키는 작업 절차도 latch를 획득한 다음에만 수행
    가능하다.
    2. redo allocation latch
    모든 redo entry는 db에 수행된 작업 순서대로 redo log file에 기록되어야 한다.
    그러므로 redo log buffer에 redo entry를 할당하는 작업은 항상 serialization을
    유지하여야 하고, 그런 이유로 인해서 redo allocation latch는 instance마다
    하나만이 가능하다.
    server process는 이 redo allocation latch를 잡고, redo buffer 내에 redo
    entry를 저장시킬 위치를 확보한다.
    다음에 설명할 redo copy latch를 사용할 수 없는 환경에서는, redo buffer 내의
    확보한 공간 내에 redo entry를 copy하는 작업도 이 redo allocation latch를
    잡은 후 진행한다.
    3. redo copy latch (LOG_SIMULTANEOUS_COPIES)
    redo allocation latch 하나를 이용하여 redo buffer 내의 공간을 할당하고,
    redo entry를 copy하는 것은, redo buffer에 대한 작업을 모두 serialize시켜
    performance에 지장을 줄 수 있다.
    redo entry가 위치할 공간을 확보하는 작업은 반드시 시간 순서대로 위치해야
    하기 때문에 모두 순서가 유지되어야 하는 작업이지만, 일단 확보한 log
    buffer의 공간에 redo entry를 copy하는 작업은 동시에 수행되어도 지장이
    없다. 이것을 위해 복수 개의 redo copy latch를 지정하여, redo entry를 확보된
    영역에 동시에 copy가 가능하도록 하였다. 단 이러한 copy 작업은 CPU의
    작업이므로 CPU가 한장이면, 동시 작업이 불가능하여 이 redo copy latch를
    사용하는 것이 의미가 없어 사용이 불가능하다.
    즉, redo buffer에 대한 작업이 redo copy latch를 사용하면, 다음과 같은
    절차로 수행된다.
    (1) A server process가 redo allocation latch를 잡고 redo buffer 내의 공간을
    할당한 후 redo allocation latch는 푼다.
    (2) B server process가 redo allocation latch를 잡고 redo buffer의 새로운
    공간을 할당받은 다음 redo allocation latch를 푼다.
    (3) A process가 redo copy latch를 잡고 A process가 만든 PGA 내의 redo
    entry를 (1)번 단계에서 확보한 공간에 copy한다.
    이와 동시에 B process도 또 다른 redo copy latch를 잡고, (2)번 단계에서
    확보한 공간에 redo entry를 copy한다.
    redo copy latch의 갯수는 log_simultaneous_copies parameter에 의해 지정된다.
    CPU가 하나이면 이 값은 0가 되어, redo allocation latch를 이용해 redo
    allocation과 redo copy 작업을 한번에 수행하게 되며, default는 CPU_COUNT 값이
    된다. CPU_COUNT는 operating system layer에 의해 자동으로 결정되며, init.ora
    file에 명시적으로 지정하지 않는 parameter이다.
    즉, multi CPU 환경에서는 자동으로 redo copy latch를 사용하게 되는 것이다.
    default 외의 값을 사용하고자 한다면, $ORACLE_HOME/dbs/initSID.ora file 내에
    다음과 같이 지정하면 된다. 최대값의 제한은 없다.
    log_simultaneous_copies=n
    redo copy latch의 장점을 정리하면, redo buffer의 공간 할당을 위해 선행된
    작업이 redo entry를 copy할 때까지 기다리지 않아도 되며, redo copy 작업 자체도
    병렬도 수행이 가능하다는 것이다.
    4. LOG_SMALL_ENTRY_MAX_SIZE
    CPU를 복수개를 사용하는 경우 redo copy latch를 사용하는 것이 redo log buffer
    내의 작업에 대한 wait는 줄일 수 있음은 위에서 살펴보았다. 그런데 매우 작은
    redo entry의 경우 redo entry를 copy하는 데 시간이 거의 걸리지 않은 상황에서
    굳이 redo allocation과 redo copy를 별도의 latch를 이용하여 두 단계로 나누어
    작업하는 것이 성능 향상에 도움이 되지 않을 수도 있다. 오히려 copy하는 데 시간이
    거의 안 걸린다면 redo allocation latch 하나를 잡고서 redo allocation과 redo
    copy를 모두 수행하는 것이 나을 수도 있다.
    그렇다면 redo copy latch를 사용하는 상황에서 이 latch를 사용하지 않아도 되는,
    작은 redo entry의 기준을 설정할 필요가 있다.
    이것을 결정하는 parameter가 log_small_entry_max_size이다.
    즉, log_small_entry_max_size보다 큰 redo entry는 redo copy를 위해 redo copy
    latch를 사용하지만, 이보다 작은 크기의 redo entry에 대해서는 redo allocation
    latch를 이용하여 redo allocation과 copy를 모두 수행하게 되는 것이다.
    아무리 작은 redo entry라도 redo copy latch를 사용하게 하고 싶다면 이 값을
    0으로 지정하면 된다.
    5. tuning point
    multi-CPU 환경에서 redo copy latch의 갯수를 늘리거나, log_small_entry_max_size
    값을 줄여야 할때는 redo buffer에 contention이 발생하는 경우이다.
    redo buffer에 contention이 발생하는지 확인하는 방법은 다음과 같다.
    SQL>select name, gets, misses from v$latch where name = 'redo allocation';
    이 값의 결과에서 gets에 대한 misses의 비율이 1%를 넘는다면 이것은 contention
    이 존재한다고 판단될 수 있다. 물론 이것은 절대적인 기준은 아니어서, 1% 미만
    이라 하더라도 miss 율을 더 줄이고자 할 수도 있다.
    contention이 발생하면 log_simultaneous_copies의 값을 CPU의 약 두배 정도까지
    증가시키는 것이 권고할 만하고, log_small_entry_max_size의 값도 0에 가까운
    값으로 줄여서 contention의 상황을 지속적으로 살펴보아야 한다.
    6. 8i 에서의 변경 사항
    Oracle 8.1 에서는 위에서 설명한 두 parameter가 모두 나타나지 않는다.
    log_small_entry_max_size parameter는 완전히 없어졌으며,
    log_simultaneous_copies 값은 CPU_COUNT의 두배로 무조건 설정이 된다.
    이 CPU_COUNT는 앞에서 설명한 것과 같이 operating system layer에 의해
    자동으로 결정되는 parameter로 CPU의 갯수를 나타낸다.
    log_simultaneous_copies가 자동으로 CPU 갯수의 2배로 지정되는 것은 모든
    환경에서 대부분 최적이라고 볼 수 있으므로, user가 변경하지 않도록 하기 위해
    parameter 부분에 display가 안 되도록 하였다.

    제품 : ORACLE SERVER
    작성날짜 : 2000-08-28
    REDO ALLOCATION LATCH와 REDO COPY LATCH에 대해서
    ========================================================================
    redo log buffer 사용 시 wait 비율이 높은 경우 log buffer의 크기 조정 외에도
    redo에 관한 latch를 조정함으로써 성능을 향상시킬 수 있다.
    여기에서는 redo allocation latch와 redo copy latch의 작동 원리와, tuning
    방법 등을 설명한다. 그리고 8i에서의 변경 사항도 포함하였다.
    1. redo entry를 redo log buffer에 할당하는 방법
    database에 변경 작업을 수행하는 server process는 PGA 부분에 변경 작업에 대한
    redo entry를 만든다. 그리고 이것을 redo log buffer에 옮기는데, 이 때 먼저
    할당될 redo log buffer의 부분을 allocation하고, 그 이후에 allocation 된
    redo log buffer 공간에, PGA 상에 만들어 둔 redo entry를 copy한다.
    Oracle은 SGA 내에서 발생하는 source code의 action의 serialization을 위해서
    latch를 사용한다. 즉, log buffer에서 redo entry를 save시킬 공간을 할당하는
    작업 절차도 먼저 latch를 부여받은 process가 작업하는 것이고, 할당받은
    공간에 redo entry를 copy시키는 작업 절차도 latch를 획득한 다음에만 수행
    가능하다.
    2. redo allocation latch
    모든 redo entry는 db에 수행된 작업 순서대로 redo log file에 기록되어야 한다.
    그러므로 redo log buffer에 redo entry를 할당하는 작업은 항상 serialization을
    유지하여야 하고, 그런 이유로 인해서 redo allocation latch는 instance마다
    하나만이 가능하다.
    server process는 이 redo allocation latch를 잡고, redo buffer 내에 redo
    entry를 저장시킬 위치를 확보한다.
    다음에 설명할 redo copy latch를 사용할 수 없는 환경에서는, redo buffer 내의
    확보한 공간 내에 redo entry를 copy하는 작업도 이 redo allocation latch를
    잡은 후 진행한다.
    3. redo copy latch (LOG_SIMULTANEOUS_COPIES)
    redo allocation latch 하나를 이용하여 redo buffer 내의 공간을 할당하고,
    redo entry를 copy하는 것은, redo buffer에 대한 작업을 모두 serialize시켜
    performance에 지장을 줄 수 있다.
    redo entry가 위치할 공간을 확보하는 작업은 반드시 시간 순서대로 위치해야
    하기 때문에 모두 순서가 유지되어야 하는 작업이지만, 일단 확보한 log
    buffer의 공간에 redo entry를 copy하는 작업은 동시에 수행되어도 지장이
    없다. 이것을 위해 복수 개의 redo copy latch를 지정하여, redo entry를 확보된
    영역에 동시에 copy가 가능하도록 하였다. 단 이러한 copy 작업은 CPU의
    작업이므로 CPU가 한장이면, 동시 작업이 불가능하여 이 redo copy latch를
    사용하는 것이 의미가 없어 사용이 불가능하다.
    즉, redo buffer에 대한 작업이 redo copy latch를 사용하면, 다음과 같은
    절차로 수행된다.
    (1) A server process가 redo allocation latch를 잡고 redo buffer 내의 공간을
    할당한 후 redo allocation latch는 푼다.
    (2) B server process가 redo allocation latch를 잡고 redo buffer의 새로운
    공간을 할당받은 다음 redo allocation latch를 푼다.
    (3) A process가 redo copy latch를 잡고 A process가 만든 PGA 내의 redo
    entry를 (1)번 단계에서 확보한 공간에 copy한다.
    이와 동시에 B process도 또 다른 redo copy latch를 잡고, (2)번 단계에서
    확보한 공간에 redo entry를 copy한다.
    redo copy latch의 갯수는 log_simultaneous_copies parameter에 의해 지정된다.
    CPU가 하나이면 이 값은 0가 되어, redo allocation latch를 이용해 redo
    allocation과 redo copy 작업을 한번에 수행하게 되며, default는 CPU_COUNT 값이
    된다. CPU_COUNT는 operating system layer에 의해 자동으로 결정되며, init.ora
    file에 명시적으로 지정하지 않는 parameter이다.
    즉, multi CPU 환경에서는 자동으로 redo copy latch를 사용하게 되는 것이다.
    default 외의 값을 사용하고자 한다면, $ORACLE_HOME/dbs/initSID.ora file 내에
    다음과 같이 지정하면 된다. 최대값의 제한은 없다.
    log_simultaneous_copies=n
    redo copy latch의 장점을 정리하면, redo buffer의 공간 할당을 위해 선행된
    작업이 redo entry를 copy할 때까지 기다리지 않아도 되며, redo copy 작업 자체도
    병렬도 수행이 가능하다는 것이다.
    4. LOG_SMALL_ENTRY_MAX_SIZE
    CPU를 복수개를 사용하는 경우 redo copy latch를 사용하는 것이 redo log buffer
    내의 작업에 대한 wait는 줄일 수 있음은 위에서 살펴보았다. 그런데 매우 작은
    redo entry의 경우 redo entry를 copy하는 데 시간이 거의 걸리지 않은 상황에서
    굳이 redo allocation과 redo copy를 별도의 latch를 이용하여 두 단계로 나누어
    작업하는 것이 성능 향상에 도움이 되지 않을 수도 있다. 오히려 copy하는 데 시간이
    거의 안 걸린다면 redo allocation latch 하나를 잡고서 redo allocation과 redo
    copy를 모두 수행하는 것이 나을 수도 있다.
    그렇다면 redo copy latch를 사용하는 상황에서 이 latch를 사용하지 않아도 되는,
    작은 redo entry의 기준을 설정할 필요가 있다.
    이것을 결정하는 parameter가 log_small_entry_max_size이다.
    즉, log_small_entry_max_size보다 큰 redo entry는 redo copy를 위해 redo copy
    latch를 사용하지만, 이보다 작은 크기의 redo entry에 대해서는 redo allocation
    latch를 이용하여 redo allocation과 copy를 모두 수행하게 되는 것이다.
    아무리 작은 redo entry라도 redo copy latch를 사용하게 하고 싶다면 이 값을
    0으로 지정하면 된다.
    5. tuning point
    multi-CPU 환경에서 redo copy latch의 갯수를 늘리거나, log_small_entry_max_size
    값을 줄여야 할때는 redo buffer에 contention이 발생하는 경우이다.
    redo buffer에 contention이 발생하는지 확인하는 방법은 다음과 같다.
    SQL>select name, gets, misses from v$latch where name = 'redo allocation';
    이 값의 결과에서 gets에 대한 misses의 비율이 1%를 넘는다면 이것은 contention
    이 존재한다고 판단될 수 있다. 물론 이것은 절대적인 기준은 아니어서, 1% 미만
    이라 하더라도 miss 율을 더 줄이고자 할 수도 있다.
    contention이 발생하면 log_simultaneous_copies의 값을 CPU의 약 두배 정도까지
    증가시키는 것이 권고할 만하고, log_small_entry_max_size의 값도 0에 가까운
    값으로 줄여서 contention의 상황을 지속적으로 살펴보아야 한다.
    6. 8i 에서의 변경 사항
    Oracle 8.1 에서는 위에서 설명한 두 parameter가 모두 나타나지 않는다.
    log_small_entry_max_size parameter는 완전히 없어졌으며,
    log_simultaneous_copies 값은 CPU_COUNT의 두배로 무조건 설정이 된다.
    이 CPU_COUNT는 앞에서 설명한 것과 같이 operating system layer에 의해
    자동으로 결정되는 parameter로 CPU의 갯수를 나타낸다.
    log_simultaneous_copies가 자동으로 CPU 갯수의 2배로 지정되는 것은 모든
    환경에서 대부분 최적이라고 볼 수 있으므로, user가 변경하지 않도록 하기 위해
    parameter 부분에 display가 안 되도록 하였다.

  • Buffer cache vs data blocks that can be cache

    Hi Guys,
    Do it means that if we have 2 GB of buffer cache allocated to Oracle, we can only store up to 2GB of data in memory?
    thanks

    dbaing wrote:
    Hi Guys,
    Do it means that if we have 2 GB of buffer cache allocated to Oracle, we can only store up to 2GB of data in memory?Yes, this means that you can any time, can have 2gb of cached blocks in your memory.
    Aman....

  • Automatic V simple credit check

    what r the advantages of automatic over simple credit management

    <b>Simple credit limit check</b>
    A credit limit check can be carried out when sales documents are created or changed. The check is carried out within one credit control area. When changing a document, the check is repeated if changes regarding quantity or value are made. A credit control area consists of one or more company codes. A sales document belongs to one credit control area depending on the allocation of the sales organization to a company code. The SAP System checks the credit limit which was granted to the customer in this credit control area. The credit control areas and the credit limit of a customer are defined in financial accounting and entered in the customer master record. During the check, the SAP System totals the receivables, the open items from special G/L transactions and the net value of the sales order for every item of a sales document. The open items take into account obligations bound by contract which are not recorded for accounting purposes but which involve expenses through diverse business transactions. The total is compared with the credit limit. If the limit is exceeded, the system responds in the way defined by you in the configuration menu.
    <b>Automatic Credit Check</b>
    The automatic credit check can target certain aspects during a check and run at different times during order processing. In this menu option, you can define your own credit checks to correspond to your requirements in the area of Credit Management.
    You can determine an automatic credit check for any combination of the following:
    Credit control area
    Risk class (classifying attribute for your customers from the viewpoint of credit risk which is maintained in FI Customizing)
    Credit group
    <b>Example</b>
    You can define a credit check for a certain credit control area and for all sales orders in which the customer has risk class 2 (RK2).
    It is possible to define a system response for each credit check (for example, warning message). In the case of a warning message, a block can be set in the credit status of a document.
    When you define automatic credit checks, you can also freely define requirements which cause a document or the forwarding of the material requirements to MRP to be blocked. This is described in the IMG section "Make default settings for Credit Management".
    If you define your own credit checks, proceed as follows:
    specify type of check
    specify scope of check
    specify system response to check
    allocate credit control areas
    define and allocate risk classes if necessary
    allocate credit group
    assign description to the credit check
    <b>Types of credit check</b>
    The following types of credit checks can be carried out:
    Static credit limit check
    Credit allocation depends on the total value of open orders, deliveries, billing documents and open items.
    Dynamic credit limit check
    The dynamic check includes both a static part which checks all open items, deliveries and billing documents and a dynamic part which checks all outstanding order values, that is, all orders not yet delivered or partially delivered. The value resulting from the checks is accumulated up to the shipping date in the information structure "S066" in freely definable time units or periods (day, week, month). This information structure is entered in Logistics Controlling and described in the section "Carry out default settings for credit management" under Basic functions.
    To define the credit check, you specify a certain number of relevant periods from which a date in the future can be calculated (for example, 10 days or 2 months depending on the selected period). This ensures that sales orders which lie further in the future are not used to determine the credit exposure.
    The total of the static and dynamic part of the check must not exceed the granted credit limit.
    Credit check on the basis of the maximum document value
    The sales order value or the value of goods to be delivered must not exceed a certain value defined for the credit check. The value is stored in the currency of the credit control area. In particular, this check is useful if the credit limit of new customers has not yet been specified. This check can be accessed explicitly by a risk class reserved for new customers.
    Credit check when changing critical fields
    The credit check is started when changes are made to credit-relevant document fields so that they differ from the default values proposed from the customer master record (terms of payment, value days and fixed value date).
    Credit check at the time of the next internal check
    The credit check is started automatically on a certain date. All sales orders entered up to this time are regarded as not critical.
    Credit check on the basis of overdue open items
    The ratio between open items, which are overdue by more than a certain number of days, and the customer balance must not exceed a certain percentage.
    Credit check on the basis of the oldest open items
    The oldest open item may only be a certain number of days overdue.
    Credit check against maximum allowed dunning levels
    The dunning level of the customer may only assume a certain maximum value.
    Customer-specific credit checks
    If you require further checks to those defined in the standard system, you can define them in the corresponding user exits (LVKMPTZZ and LVKMPFZ1).
    Regards
    Nadarajah Pratheb

  • Reactivate your credit. Your Skype Credit is now i...

    I work in IT Support and one of the users is receiving a message to "Reactivate your credit. Your Skype Credit is now inactive." The Skype name is not the user's.  See information below. Is this suspicious? How can I prevent user from receiving these messages other than sending e-mail to "JUNK" folder?
    I work in IT Support and one of the users is receiving a message to "Reactivate your credit. Your Skype Credit is now inactive." The Skype name is not the user's.  See information below. Is this suspicious? How can I prevent user from receiving these messages other than sending e-mail to "JUNK" folder?
    Hi there John Doe,              
    Reactivate your credit
    Your Skype Credit is now inactive
    We've noticed you haven't used any Skype Credit in 180 days. Your credit is now inactive - but you can reactivate it again at any time.
    How to reactivate your credit
    1. Visit your account on skype.com.
    2. Sign in with your Skype Name and password.
    3. Click Reactivate credit and follow the steps.
    Your account details:
    Skype Name: john.doe.net
    Forgotten your password? No problem. Visit skype.com/go/forgotpassword to reset it.
    Need more help?
    FAQ: How do I reactivate inactive Skype Credit?
    Sign in to talk to us by email or IM
    Talk soon,
    The people at Skype
    The user also received this message several times this week with his Skype name. I changed user's name to John Doe in this message as an example.                                                                                                   
    Hello john.doe.net              
    Skype Credit allocation from Skype Manager
    The administrator - Ron Adams - of the Skype Manager called ABC has allocated you some Skype Credit. You can start using this feature immediately.
    Here's what you have been allocated:
    Skype Credit amount: CAD13.99
    Your Skype Name is john.doe.net
    Date: Jul 30, 2013
    View your Skype account
    What you can do with Skype Credit:
    Call landlines and mobiles worldwide
    Use WiFi hotspots with Skype WiFi
    Activate a Skype To Go number
    Enable call forwarding
    If you need assistance or want to request additional Skype features please contact your administrator – you can find their details on the Members List. Or, if you need help with anything else check out Skype’s support pages.
    We hope you'll enjoy using your Skype Credit.
    Thanks,
    The people at Skype
    Lost Password · Account Settings · Help · Terms of Use · Privacy
    Getting help for Skype
    While you cannot reply to this email, you can contact us through our help section for assistance.
    You can also visit our forums.
    Protect Your Password
    Skype staff will NEVER ask you for your password via email. The only places you are asked for your password are when you sign in to Skype or on our website if you want to buy something or check your account. You will always sign in via a secure connection, and we ask you to ensure that the address in your browser begins exactly like this https://secure.skype.com It should also show a little padlock symbol to indicate the secure connection.
    Be alert to emails that request account information or urgent action. Be cautious of websites with irregular addresses or those that offer unofficial Skype downloads. Security updates and product upgrades are made available at www.skype.com or using the client's upgrade function.
    © 2003-2013 Skype and/or Microsoft. The Skype name, associated trademarks and logos and the "S" logo are trademarks of Skype or related entities.
    Skype Communications S.a.r.l. 23-29 Rives de Clausen, L-2165 Luxembourg.
    Solved!
    Go to Solution.

    Dear Readers,
    In closing this thread (topic), which the original poster marked as "Solved," please remember this FAQ article:
    https://support.skype.com/en/faq/FA10378/what-do-i-do-about-inactive-skype-credit
    If you encounter any difficulties, here is a link to the instruction on how to contact Skype Customer Service via their secure portal: Contact Customer Service
    A few additional notes to help you along the way:
    You will need to proceed through each step, one at a time. Sign on to the Skype website as requested. Choose the subject and topic which most closely matches the item you need assistance with. Then, continue past Step 2 of the instruction where several articles from the FAQ library will appear for you to review, and proceed to Step 3, Continue Support Request (the blue "button" appears at the lower right corner of the website page). You may also skip through Step 4 where you will be referred back here to the Community; no need to do this as the Community is where you started. When you complete the webform and click Submit, your information is relayed to Skype and you will receive a reply via e-mail.
    If you are a Skype Premium or other eligible customer, you will be routed to start an instant message chat session with a Customer Service agent.
    Regards,
    Elaine
    Was your question answered? Please click on the Accept as a Solution link so everyone can quickly find what works! Like a post or want to say, "Thank You" - ?? Click on the Kudos button!
    Trustworthy information: Brian Krebs: 3 Basic Rules for Online Safety and Consumer Reports: Guide to Internet Security Online Safety Tip: Change your passwords often!

  • Remove skype credit from member

    Hi,
    our colleague has left us and there is about 10 EUR credit left on her account. Is it possible to withdraw (retrieve) it from her account back to our general account? Since she will not be using her Skype anymore, the money there is of no use for us.
    Thanks for advice,
    Jana

    jana1238 wrote:
    Hi,
    our colleague has left us and there is about 10 EUR credit left on her account. Is it possible to withdraw (retrieve) it from her account back to our general account? Since she will not be using her Skype anymore, the money there is of no use for us.
    Thanks for advice,
    Jana
    Yes you can retrieve the Skype Credit allocated to her account in Skype Manager,.
    Here are the instructions:
    Sign in to Skype Manager.
    Click Features in the toolbar to display the Credit allocations page.
    Check the box next to each member whose credit allocation you wish to take back.
    Click Take back credit.
    Confirm that you wish to take back the credit by clicking Take back credit. The credit is refunded to your Skype Manager's credit balance.
    Hope this answers your question.
    Regards
    Gary B
    Skype Enterprise Support

  • Regd: Screen Buffer size increase

    Dear Sir/madam,
    We check in ST02. the screen Buffer -   SWAPS are More.
    we want to increase the "SCREEN"  Buffer size  so the Screen Swaps comes down.
    Screen buffer                                                                               
    zcsa/presentation_buffer_area    4400000          Byte   Size of screen buffer                   
    sap/bufdir_entries               2000                    Max. number of buffered screens                                                                               
    Which parameter size i have to Increase here  2 Parameters are available. How much we can increase it.
    here RAM size is 4GB. Any Formula is available to Increase the Buffer size of the Screen. or other like Program Buffer etc.
    Regards
    SNB.

    Thanks for your Reply.
       Buffer            Hitratio   Allocated         Free space        Dir. size      Free directory         Swaps       Database
                            [%]       [kB]               [kB]         [%]      Entries         Entries       [%]                      accesses
    Screen           96.99        4,297          141     3.44         2,000             1,722       86.10         1,506        4,525
    if we want to increase we have to increase for both the parameters.
    zcsa/presentation_buffer_area       4400000 + 440000 =          4840000 (10%)
    sap/bufdir_entries                          2000 + 200  =                   2200   (10%)
    What is the difference between thest 2 parameters.
    1)                   zcsa/presentation_buffer_area    
    2)                   sap/bufdir_entries           
    Do you have any Formula to Handle ST02 Buffer Size Parameter Maintanence.
    Regards
    SNB.

  • Problem interconnecting MDS9124 and MDS9120

    Hello
    We are trying to connect  2 SAN switches .  Details :
    cisco MDS 9124 (1 Slot) Chassis
    Model number is DS-C9124-K9-SUP
    Cisco Nexus Operating System (NX-OS) Software
    Software
      BIOS:      version 1.0.19
      loader:    version N/A
      kickstart: version 5.0(1a)
      system:    version 5.0(1a)
    cisco MDS 9100
    Model number is DS-C9120-K9-SUP
    Cisco Storage Area Networking Operating System (SAN-OS) Software
    Software
      BIOS:      version 1.1.0
      loader:    version 1.2(2)
      kickstart: version 3.3(5)
      system:    version 3.3(5)
    We want to make the  9124 an expansion of the 9120.  Therefore we want to define 2 ports in each switch to mode E, and make an ISL link.
    The problem : when we try to define the E port, we get an error :
    SW_A(config-if)# switchport mode E
    fc1/6: (error) mode E allowed only for interface fc1/5 in group fc1/5-8
    We don't want to define port fc1/5  in mode E, because , if we do that port 6,7,8 become unusable.
    Any suggestions ?
    Thank you.

    Hi,
    The 9120 has a hardware limitation.
    http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/intf.html#wp1242298
    In the Cisco MDS 9100 Series, the left most groups of ports outlined in white (4 ports in the 9120 switch and 8 ports in the 9140 switch) are full line rate like the 16-port switching module. The other ports (16 ports in the 9120 switch and 32 ports in the 9140 switch) are host-optimized like the 32-port switching module. Each group of 4 host-optimized ports have the same rules as for the 32-port switching module.
    When configuring these host-optimized ports, the following port mode guidelines apply:
    You can configure only the first port in each 4-port group (for example, the first port in ports 1-4, the fifth port in ports 5-8 and so on) as an E port. If the first port in the group is configured as an E port, the other three ports in each group (ports 2-4, 6-8 and so on) are not usable and remain shutdown.
    Since the 9120 (Gen1) is attaching to the 9124 (Gen2), keep this in mind.
    http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/sw/5_0/release/notes/nxos/mds_nxos_rel_notes_501a.html#wp419251
    When a Cisco or other vendor switch port is connected to a Generation 1 module port (ISL connection), the receive buffer-to-buffer credit of the port connected to a Generation 1 module port should not exceed 255.
    On the 9124, you may have to configure the interface as...
    switchport fcrxbbcredit 255
    Regards,
    David

  • Regular timeouts and slow system

    Team,
    We are regularly getting timeouts for users on our IDES system.
    This is a dump of our ST02 screen:
    System:                  sap6ides_C10_00             Tune summary
    Date + Time of Snapshot: 18.08.2010      11:32:32    Startup:     20.04.2010 19:18:57
    Buffer             HitRatio % Alloc. KB Freesp. KB % Free Sp. Dir. Size FreeDirEnt % Free Dir    Swaps     DB Accs
    Nametab (NTAB)                                                                                0
       Table definition     98,50     6.798                          20.000                              0
       Table definition     98,50     6.798                          20.000                          4.638     193.422
       Field definition     99,59    51.563      7.928      15,86    20.000     12.853      64,27   36.873      44.444
       Short NTAB           99,74     3.625      1.741      58,03     5.000        905      18,10        0       4.095
       Initial records      58,43     6.625      3.770      62,83     5.000        756      15,12   49.952      54.196
                                                                                    0
    program                98,93   300.000      1.077       0,37    75.000     67.819      90,43  134.795     436.695
    CUA                    99,62     5.000      1.318      32,15     2.500      2.355      94,20  128.786       4.595
    Screen                 99,60     4.297                           2.000      1.671      83,55    1.612      11.290
    Calendar               99,99       488        260      55,20       200         98      49,00        0         102
    OTR                   100,00     4.096      3.375     100,00     2.000      2.000     100,00        0
                                                                                    0
    Tables                                                                                0
       Generic Key          99,97    58.594      3.647       6,39     5.000        221       4,42      180      95.637
       Single record        58,67    10.000        170       1,73       500        450      90,00    1.076  16.922.960
                                                                                    0
    Export/import          66,26     4.096        517      15,31     2.000        904      45,20  351.112
    Exp./ Imp. SHM         80,09     4.096      3.351      99,26     2.000      1.999      99,95        0
    SAP Memory      Curr.Use % CurUse[KB] MaxUse[KB] In Mem[KB] OnDisk[KB] SAPCurCach HitRatio %
    Roll area            4,20      2.519      6.400     60.000          0   IDs           99,99
    Page area            2,09      5.490    161.504     32.000    230.144   Statement    100,00
    Extended memory     21,39    503.808  2.256.896  2.355.200          0                  0,00
    Heap memory                        0          0    524.285          0                  0,00
    There is a lot of RED in the Swaps column. The box is a Windows Server with 4GB of memory allocated to it.  Any thoughts on where to start tuning this system?

    WOw ... Very unreadable format ... Can you repost question ... About time outs are you check the st03n load and know from here this long execution's are coming ? The DB you have are ?
    The box is a Windows Server with 4GB of memory allocated to it
    are is 32 bit? How you divided this 4 GB (how much for DB and for Application server)
    The 4 GB is to small are you trying for testing increae the rdisp/max_wprun_time ?
    Any other information?

  • Performance Issue for BI system

    Hello,
    We are facing performance issues for BI System. Its a preproductive system and its performance is degrading badly everyday. I was checking system came to know program buffer hit ratio is increaasing everyday due to high Swaps. So asked to change the parameter abap/buffersize which was 300Mb to 500Mb. But still no major improvement is found in the system.
    There is 16GB Ram available and Server is HP-UX and with Netweaver2004s with Oracle 10.2.0.4.0 installed in it.
    The Main problem is while running a report or creating a query is taking way too long time.
    Kindly help me.

    Hello SIva,
    Thanks for your reply but i have checked ST02 and ST03 and also SM50 and its normal
    we are having 9 dialog processes, 3 Background , 2 Update and 1 spool.
    No one is using the system currently but in ST02 i can see the swaps are in red.
    Buffer                 HitRatio   % Alloc. KB  Freesp. KB   % Free Sp.   Dir. Size  FreeDirEnt   % Free Dir    Swaps    DB Accs
    Nametab (NTAB)                                                                                0
       Table definition     99,60     6.798                                                   20.000                                            29.532    153.221
       Field definition     99,82      31.562        784                 2,61           20.000      6.222          31,11          17.246     41.248
       Short NTAB           99,94     3.625      2.446                81,53          5.000        2.801          56,02             0            2.254
       Initial records      73,95        6.625        998                 16,63          5.000        690             13,80             40.069     49.528
                                                                                    0
    boldprogram                97,66     300.000     1.074                 0,38           75.000     67.177        89,57           219.665    725.703bold
    CUA                    99,75         3.000        875                   36,29          1.500      1.401          93,40            55.277      2.497
    Screen                 99,80         4.297      1.365                 33,35          2.000      1.811          90,55              119         3.214
    Calendar              100,00       488            361                  75,52            200         42              21,00               0            158
    OTR                   100,00         4.096      3.313                  100,00        2.000      2.000          100,00              0
                                                                                    0
    Tables                                                                                0
       Generic Key          99,17    29.297      1.450                  5,23           5.000        350             7,00             2.219      3.085.633
       Single record        99,43    10.000      1.907                  19,41           500         344            68,80              39          467.978
                                                                                    0
    Export/import          82,75     4.096         43                      1,30            2.000        662          33,10            137.208
    Exp./ Imp. SHM         89,83     4.096        438                    13,22         2.000      1.482          74,10               0    
    SAP Memory      Curr.Use %    CurUse[KB]    MaxUse[KB]    In Mem[KB]    OnDisk[KB]    SAPCurCach      HitRatio %
    Roll area               2,22                5.832               22.856             131.072     131.072                   IDs           96,61
    Page area              1,08              2.832                24.144               65.536    196.608              Statement     79,00
    Extended memory     22,90       958.464           1.929.216          4.186.112          0                                         0,00
    Heap memory                                    0                  0                    1.473.767          0                                         0,00
    Call Stati             HitRatio %     ABAP/4 Req      ABAP Fails     DBTotCalls         AvTime[ms]      DBRowsAff.
      Select single     88,59               63.073.369        5.817.659      4.322.263             0                         57.255.710
      Select               72,68               284.080.387          0               13.718.442             0                        32.199.124
      Insert                 0,00                  151.955             5.458             166.159               0                           323.725
      Update               0,00                    378.161           97.884           395.814               0                            486.880
      Delete                 0,00                    389.398          332.619          415.562              0                             244.495
    Edited by: Srikanth Sunkara on May 12, 2011 11:50 AM

  • EXCEPTION_ACCESS_VIOLATION Problem

    Hello,
    Everytime I launch this Tivoli TME client I get this access Violation error. I have un-install java and re-installed it with the same result. It use to work fine but now just does a dump. Reloaded the program on other pc's and it works fine.
    NULL ------------------------------------------------------------------------
    0SECTION TITLE subcomponent dump routine
    NULL ===============================
    1TISIGINFO signal 11 received
    1TIDATETIME Date: 2011/12/29 at 12:46:01
    1TIFILENAME Javacore filename: C:\Tivoli\TEC39FP8\javacore.20111229.124601.2836.txt
    NULL ------------------------------------------------------------------------
    0SECTION XHPI subcomponent dump routine
    NULL ==============================
    1XHEXCPCODE Exception code: C0000005 Access Violation
    1XHEXCPADDRESS Fault address: 700D6DC3 01:000D5DC3
    1XHEXCPMODULE Fault module: C:\Tivoli\TEC39FP8\jre\bin\awt.dll
    NULL
    1XHREGISTERS Registers:
    2XHREGISTER EAX:00000002
    2XHREGISTER EBX:08246338
    2XHREGISTER ECX:07BEEA8C
    2XHREGISTER EDX:A38E5000
    2XHREGISTER ESI:00000000
    2XHREGISTER EDI:701178E8
    2XHREGISTER CS:EIP:001B:700D6DC3
    2XHREGISTER SS:ESP:0023:07BEE9C0 EBP:00000015
    2XHREGISTER DS:0023 ES:0023 FS:003B GS:0000
    NULL
    1XHFLAGS Flags:00010202
    NULL
    NULL ------------------------------------------------------------------------
    0SECTION CI subcomponent dump routine
    NULL ============================
    1CIJAVAVERSION J2RE 1.4.2 IBM Windows 32 build cn142-20070317 (SR8)
    1CIRUNNINGAS Running as a standalone JVM
    1CICMDLINE C:\Tivoli\TEC39FP8\jre\bin\javaw.exe -Djavax.net.ssl.trustStore=C:\Tivoli\TEC39FP8\jcf.jks -Dnv_inst_flag=NO -Dnvwc.cwd= -Dnvwc.java=C:\Tivoli\TEC39FP8\jre\bin\java.exe -classpath C:\Tivoli\TEC39FP8\log.jar;C:\Tivoli\TEC39FP8\evd.jar;C:\Tivoli\TEC39FP8\tec_console.jar;C:\Tivoli\TEC39FP8\jhall.jar;C:\Tivoli\TEC39FP8\jrim.jar;C:\Tivoli\TEC39FP8\avail_common.jar;C:\Tivoli\TEC39FP8\console.jar;C:\Tivoli\TEC39FP8\ibmjsse.jar;C:\Tivoli\TEC39FP8\jcf.jar;C:\Tivoli\TEC39FP8\jsafe.zip;C:\Tivoli\TEC39FP8\uif.jar;C:\Tivoli\TEC39FP8\jcchart362J-classes.zip;C:\Tivoli\TEC39FP8\tec_ui_svr.jar;C:\Tivoli\TEC39FP8\tec_ui_svr_stubs.jar;C:\Tivoli\TEC39FP8\tec_svr.jar;C:\Tivoli\TEC39FP8\tec_svr_stubs.jar;C:\Tivoli\TEC39FP8\java-getopt-1.0.6.jar;; -DINTERP=w32-ix86 -DDISPLAY= com.tivoli.tec.console.EnterpriseConsoleLauncher
    1CIJAVAHOMEDIR Java Home Dir: C:\Tivoli\TEC39FP8\jre
    1CIJAVADLLDIR Java DLL Dir: C:\Tivoli\TEC39FP8\jre\bin
    1CISYSCP Sys Classpath: C:\Tivoli\TEC39FP8\jre\lib\core.jar;C:\Tivoli\TEC39FP8\jre\lib\graphics.jar;C:\Tivoli\TEC39FP8\jre\lib\security.jar;C:\Tivoli\TEC39FP8\jre\lib\server.jar;C:\Tivoli\TEC39FP8\jre\lib\xml.jar;C:\Tivoli\TEC39FP8\jre\lib\charsets.jar;C:\Tivoli\TEC39FP8\jre\lib\ibmcertpathprovider.jar;C:\Tivoli\TEC39FP8\jre\lib\ibmjaasactivelm.jar;C:\Tivoli\TEC39FP8\jre\lib\ibmjaaslm.jar;C:\Tivoli\TEC39FP8\jre\lib\ibmjcefw.jar;C:\Tivoli\TEC39FP8\jre\lib\ibmjgssprovider.jar;C:\Tivoli\TEC39FP8\jre\lib\ibmjssefips.jar;C:\Tivoli\TEC39FP8\jre\lib\ibmjsseprovider.jar;C:\Tivoli\TEC39FP8\jre\lib\ibmorb.jar;C:\Tivoli\TEC39FP8\jre\lib\ibmorbapi.jar;C:\Tivoli\TEC39FP8\jre\lib\ibmpkcs.jar
    1CIUSERARGS UserArgs:
    2CIUSERARG vfprintf 0x4030F0
    2CIUSERARG -Djavax.net.ssl.trustStore=C:\Tivoli\TEC39FP8\jcf.jks
    2CIUSERARG -Dnv_inst_flag=NO
    2CIUSERARG -Dnvwc.cwd=
    2CIUSERARG -Dnvwc.java=C:\Tivoli\TEC39FP8\jre\bin\java.exe
    2CIUSERARG -DINTERP=w32-ix86
    2CIUSERARG -DDISPLAY=
    2CIUSERARG -Dinvokedviajava
    2CIUSERARG -Djava.class.path=C:\Tivoli\TEC39FP8\log.jar;C:\Tivoli\TEC39FP8\evd.jar;C:\Tivoli\TEC39FP8\tec_console.jar;C:\Tivoli\TEC39FP8\jhall.jar;C:\Tivoli\TEC39FP8\jrim.jar;C:\Tivoli\TEC39FP8\avail_common.jar;C:\Tivoli\TEC39FP8\console.jar;C:\Tivoli\TEC39FP8\ibmjsse.jar;C:\Tivoli\TEC39FP8\jcf.jar;C:\Tivoli\TEC39FP8\jsafe.zip;C:\Tivoli\TEC39FP8\uif.jar;C:\Tivoli\TEC39FP8\jcchart362J-classes.zip;C:\Tivoli\TEC39FP8\tec_ui_svr.jar;C:\Tivoli\TEC39FP8\tec_ui_svr_stubs.jar;C:\Tivoli\TEC39FP8\tec_svr.jar;C:\Tivoli\TEC39FP8\tec_svr_stubs.jar;C:\Tivoli\TEC39FP8\java-getopt-1.0.6.jar;;
    2CIUSERARG vfprintf
    NULL
    1CIJVMMI JVM Monitoring Interface (JVMMI)
    NULL ------------------------
    2CIJVMMIOFF No events are enabled.
    NULL
    NULL ------------------------------------------------------------------------
    0SECTION DC subcomponent dump routine
    NULL ============================
    1DCHEADEREYE Header eye catcher DCST
    1DCHEADERLEN Header length 24
    1DCHEADERVER Header version 1
    1DCHEADERMOD Header modification 0
    1DCINTERFACE DC Interface at 0x70DC039C with 15 entries
    2DCINTERFACE 1 - dcCString2JavaString 0x70CCF0C0
    2DCINTERFACE 2 - dcInt642CString 0x70CCF280
    2DCINTERFACE 3 - dcJavaString2NewCString 0x70CCF4A0
    2DCINTERFACE 4 - dcJavaString2CString 0x70CCF3C0
    2DCINTERFACE 5 - dcJavaString2NewPlatformString 0x70CCF5F0
    2DCINTERFACE 6 - dcJavaString2UTF 0x70CCF990
    2DCINTERFACE 7 - dcPlatformString2JavaString 0x70CCF710
    2DCINTERFACE 8 - dcUnicode2UTF 0x70CCF8C0
    2DCINTERFACE 9 - dcUnicode2UTFLength 0x70CCF830
    2DCINTERFACE 10 - dcUTF2JavaString 0x70CCFD60
    2DCINTERFACE 11 - dcUTFClassName2JavaString 0x70CD0060
    2DCINTERFACE 12 - dcJavaString2ClassName 0x70CCFA60
    2DCINTERFACE 13 - dcUTF2UnicodeNext 0x70CD02E0
    2DCINTERFACE 14 - dcVerifyUTF8 0x70CD03D0
    2DCINTERFACE 15 - dcDumpRoutine 0x70CD0A60
    1DCARRAYINFO Array info at 0x70D749A8 with 16 entries
    2DCARRAYINFO 1 - index 0 signature 0 name N/A factor 0
    2DCARRAYINFO 2 - index 0 signature 0 name N/A factor 0
    2DCARRAYINFO 3 - index 2 signature L name class[] factor 4
    2DCARRAYINFO 4 - index 0 signature 0 name N/A factor 0
    2DCARRAYINFO 5 - index 4 signature Z name bool[] factor 1
    2DCARRAYINFO 6 - index 5 signature C name char[] factor 2
    2DCARRAYINFO 7 - index 6 signature F name float[] factor 4
    2DCARRAYINFO 8 - index 7 signature D name double[] factor 8
    2DCARRAYINFO 9 - index 8 signature B name byte[] factor 1
    2DCARRAYINFO 10 - index 9 signature S name short[] factor 2
    2DCARRAYINFO 11 - index 10 signature I name int[] factor 4
    2DCARRAYINFO 12 - index 11 signature J name long[] factor 8
    2DCARRAYINFO 13 - index 0 signature 0 name uint[] factor 0
    2DCARRAYINFO 14 - index 0 signature 0 name uint1[] factor 0
    2DCARRAYINFO 15 - index 0 signature 0 name uint2[] factor 0
    2DCARRAYINFO 16 - index 0 signature 0 name uint3[] factor 0
    NULL ------------------------------------------------------------------------
    0SECTION DG subcomponent dump routine
    NULL ============================
    1DGTRCENABLED Trace enabled: Yes
    2DGTRCTYPE Trace: Internal
    2DGTRCBUFFERS Buffer specification: 8k
    2DGTRCBUFALLOC Buffers allocated: 0
    2DGTRCBUFUSED Buffers in use: 0
    1DGJDUMPBUFF Javadump buffer size (allocated): 2621440
    NULL ------------------------------------------------------------------------
    0SECTION ST subcomponent dump routine
    NULL ============================
    1STGCMODES Resettable GC: No
    1STGCMODES Concurrent GC: No
    1STCURHBASE Current Heap Base: 0x100401FC
    1STCURHLIM Current Heap Limit: 0x108BFBFC
    1STMWHBASE Middleware Heap Base: 0x100401FC
    1STMWHLIM Middleware Heap Limit: 0x108BFBFC
    1STGCHELPERS Number of GC Helper Threads: 1
    1STJVMOPTS -Xconcurrentlevel: 0
    1STJVMOPTS -Xconcurrentbackground: 0
    1STGCCTR GC Counter: 7
    1STAFCTR AF Counter: 7
    1STHEAPFREE Bytes of Heap Space Free: 1adcb0
    1STHEAPALLOC Bytes of Heap Space Allocated: 87fa00
    1STSMBASE SM Base: 0x0
    1STSMEND SM End: 0x0
    1STPAMSTART PAM Start: 0x0
    1STPAMEND PAM End: 0x0
    1STCOMACTION Compact Action: 0
    NULL ------------------------------------------------------------------------
    0SECTION XE subcomponent dump routine
    NULL ============================
    1XETHRESHOLD MMI threshold for java methods is set to 2000
    1XEJITINIT JIT is initialized
    1XEJVMPIOFF JVMPI is not activated
    1XEJNITHRESH MMI threshold for JNI methods is set to 0
    1XETRCHIS Trace history length is set to 4
    1XEJITDUMP JIT dump routine is not yet implemented.
    NULL ------------------------------------------------------------------------
    0SECTION LK subcomponent dump routine
    NULL ============================
    NULL
    1LKPOOLINFO Monitor pool info:
    2LKPOOLINIT Initial monitor count: 32
    2LKPOOLEXPNUM Minimum number of free monitors before expansion: 5
    2LKPOOLEXPBY Pool will next be expanded by: 16
    2LKPOOLTOTAL Current total number of monitors: 32
    2LKPOOLFREE Current number of free monitors: 29
    NULL
    1LKMONPOOLDUMP Monitor Pool Dump (flat & inflated object-monitors):
    2LKMONINUSE sys_mon_t:0x002BBC90 infl_mon_t: 0x000386A8:
    3LKMONOBJECT java.lang.ref.Reference$Lock@100C2990/100C2998: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "Reference Handler" (0x7014808)
    2LKMONINUSE sys_mon_t:0x002BBCD8 infl_mon_t: 0x000386D4:
    3LKMONOBJECT java.lang.ref.ReferenceQueue$Lock@100C26C8/100C26D0: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "Finalizer" (0x7016BA8)
    2LKMONINUSE sys_mon_t:0x002BBD20 infl_mon_t: 0x00038700:
    3LKMONOBJECT javax.swing.TimerQueue@104FFE50/104FFE58: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "TimerQueue" (0x8082290)
    NULL
    1LKREGMONDUMP JVM System Monitor Dump (registered monitors):
    2LKREGMON JITC PIC Lock (0x070DE440): <unowned>
    2LKREGMON JITC CHA lock (0x070C8748): <unowned>
    2LKREGMON JITC MB UPDATE lock (0x07610070): <unowned>
    2LKREGMON JITC Global_Compile lock (0x07610020): <unowned>
    2LKREGMON Free Class Loader Cache Entry lock (0x0003A490): <unowned>
    2LKREGMON IO lock (0x0003A448): <unowned>
    2LKREGMON Evacuation Region lock (0x0003A3B8): <unowned>
    2LKREGMON Heap Promotion lock (0x0003A370): <unowned>
    2LKREGMON Sleep lock (0x0003A328): <unowned>
    2LKREGMON Method trace lock (0x0003A2E0): <unowned>
    2LKREGMON Heap lock (0x0003A1C0): owner "TivoliEnterpriseConsoleLauncher" (0x80B4138), entry count 1
    2LKREGMON Monitor Cache lock (0x0003A130): owner "TivoliEnterpriseConsoleLauncher" (0x80B4138), entry count 1
    2LKREGMON JNI Pinning lock (0x0003A208): <unowned>
    2LKREGMON JNI Global Reference lock (0x0003A178): <unowned>
    2LKREGMON Classloader lock (0x0003A298): <unowned>
    2LKREGMON Binclass lock (0x0003A0E8): <unowned>
    2LKREGMON Thread queue lock (0x002B2838): owner "TivoliEnterpriseConsoleLauncher" (0x80B4138), entry count 1
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "Thread-0" (0x381F0)
    2LKREGMON Monitor Registry lock (0x0003A250): owner "TivoliEnterpriseConsoleLauncher" (0x80B4138), entry count 1
    2LKREGMON System Heap lock (0x00039408): <unowned>
    2LKREGMON ACS Heap lock (0x00039450): <unowned>
    2LKREGMON PAM lock (0x00039498): <unowned>
    2LKREGMON Intern String Table lock (0x000394E0): <unowned>
    2LKREGMON Classloader lock (0x00039528): <unowned>
    2LKREGMON JIT Byte Code lock (0x00039570): <unowned>
    2LKREGMON JIT Global Compile lock (0x000395B8): <unowned>
    2LKREGMON JIT BINCLASS lock (0x00039600): <unowned>
    2LKREGMON JIT Debug lock (0x00039648): <unowned>
    2LKREGMON JIT Log lock (0x00039690): <unowned>
    2LKREGMON JITmemT 1 lock (0x000396D8): <unowned>
    2LKREGMON JITspaceT 1 lock (0x00039720): <unowned>
    2LKREGMON JITcodeT 1 lock (0x00039768): <unowned>
    2LKREGMON JITnccbT 1 lock (0x000397B0): <unowned>
    2LKREGMON JIT Invoke Interface Cache lock (0x000397F8): <unowned>
    2LKREGMON JIT Class Map lock (0x00039840): <unowned>
    2LKREGMON JIT Code lock (0x00039888): <unowned>
    2LKREGMON JITmblkT 1 lock (0x000398D0): <unowned>
    2LKREGMON JIT MB Update lock (0x00039918): <unowned>
    2LKREGMON Permanent Variable subpool lock (0x00039960): <unowned>
    2LKREGMON Intern String Buckets subpool lock (0x000399A8): <unowned>
    2LKREGMON UTF8 Cache subpool lock (0x000399F0): <unowned>
    2LKREGMON Namespace Cache subpool lock (0x00039A38): <unowned>
    2LKREGMON Class Storage subpool lock (0x00039A80): <unowned>
    2LKREGMON CL Tables subpool lock (0x00039AC8): <unowned>
    2LKREGMON JIT General subpool lock (0x00039B10): <unowned>
    NULL
    1LKFLATMONDUMP Thread identifiers (as used in flat monitors):
    2LKFLATMON ident 0x09 "TimerQueue" (0x8082290) ee 0x080820B0
    2LKFLATMON ident 0x02 "Thread-0" (0x381F0) ee 0x00038010
    2LKFLATMON ident 0x08 "TivoliEnterpriseConsoleLauncher" (0x80B4138) ee 0x080B3F58
    2LKFLATMON ident 0x05 "Finalizer" (0x7016BA8) ee 0x070169C8
    2LKFLATMON ident 0x04 "Reference Handler" (0x7014808) ee 0x07014628
    2LKFLATMON ident 0x03 "Signal dispatcher" (0x7011D58) ee 0x07011B78
    NULL
    1LKOBJMONDUMP Java Object Monitor Dump (flat & inflated object-monitors):
    2LKINFLATEDMON java.lang.ref.ReferenceQueue$Lock@100C26C8/100C26D0
    3LKINFLDETAILS locknflags 80000200 Monitor inflated infl_mon 0x000386D4
    2LKINFLATEDMON java.lang.ref.Reference$Lock@100C2990/100C2998
    3LKINFLDETAILS locknflags 80000100 Monitor inflated infl_mon 0x000386A8
    2LKINFLATEDMON javax.swing.TimerQueue@104FFE50/104FFE58
    3LKINFLDETAILS locknflags 80000300 Monitor inflated infl_mon 0x00038700
    2LKFLATLOCKED sun.awt.Win32GraphicsEnvironment@107D9788/107D9790
    3LKFLATDETAILS locknflags 00080000 Flat locked by thread ident 0x08, entry count 1
    NULL ------------------------------------------------------------------------
    0SECTION XM subcomponent dump routine
    NULL ============================
    NULL
    1XMCURTHDINFO Current Thread Details
    NULL ----------------------
    3XMTHREADINFO "TivoliEnterpriseConsoleLauncher" (TID:0x100ADE40, sys_thread_t:0x80B4138, state:R, native ID:0xA4) prio=5
    4XESTACKTRACE at sun.awt.windows.Win32SurfaceData.initDDraw(Native Method)
    4XESTACKTRACE at sun.awt.windows.Win32SurfaceData.<clinit>(Win32SurfaceData.java:302)
    4XESTACKTRACE at sun.awt.windows.D3DBlitLoops.register(D3DBlitLoops.java:72)
    4XESTACKTRACE at sun.awt.windows.Win32OffScreenSurfaceData.initD3D(Win32OffScreenSurfaceData.java:125)
    4XESTACKTRACE at sun.awt.windows.Win32OffScreenSurfaceData.<clinit>(Win32OffScreenSurfaceData.java:167)
    4XESTACKTRACE at sun.awt.Win32GraphicsDevice.<clinit>(Win32GraphicsDevice.java:91)
    4XESTACKTRACE at sun.awt.Win32GraphicsEnvironment.makeScreenDevice(Win32GraphicsEnvironment.java:201)
    4XESTACKTRACE at sun.java2d.SunGraphicsEnvironment.getScreenDevices(SunGraphicsEnvironment.java:353)
    4XESTACKTRACE at sun.awt.Win32GraphicsEnvironment.getDefaultScreenDevice(Win32GraphicsEnvironment.java:94)
    4XESTACKTRACE at java.awt.Window.init(Window.java:268)
    4XESTACKTRACE at java.awt.Window.<init>(Window.java:312)
    4XESTACKTRACE at java.awt.Frame.<init>(Frame.java:431)
    4XESTACKTRACE at java.awt.Frame.<init>(Frame.java:396)
    4XESTACKTRACE at com.tivoli.uif.controls.UFFrameManager.<init>(UFFrameManager.java:755)
    4XESTACKTRACE at com.tivoli.uif.controls.UFFrameManager.startFrameManager(UFFrameManager.java:97)
    4XESTACKTRACE at com.tivoli.console.ConsoleLauncher.<init>(ConsoleLauncher.java:84)
    4XESTACKTRACE at com.tivoli.console.SingleAppLauncher.<init>(SingleAppLauncher.java:64)
    4XESTACKTRACE at com.tivoli.tec.console.EnterpriseConsoleLauncher.<init>(EnterpriseConsoleLauncher.java:142)
    4XESTACKTRACE at com.tivoli.tec.console.LauncherThread.run(LauncherThread.java:38)
    1XMTHDINFO All Thread Details
    NULL ------------------
    NULL
    2XMFULLTHDDUMP Full thread dump Classic VM (J2RE 1.4.2 IBM Windows 32 build cn142-20070317 (SR8), native threads):
    3XMTHREADINFO "TimerQueue" (TID:0x100ADD90, sys_thread_t:0x8082290, state:CW, native ID:0x169C) prio=5
    4XESTACKTRACE at java.lang.Object.wait(Native Method)
    4XESTACKTRACE at javax.swing.TimerQueue.run(TimerQueue.java:260)
    4XESTACKTRACE at java.lang.Thread.run(Thread.java:570)
    3XMTHREADINFO "Thread-0" (TID:0x100ADDE8, sys_thread_t:0x381F0, state:CW, native ID:0xC3C) prio=5
    3XMTHREADINFO "TivoliEnterpriseConsoleLauncher" (TID:0x100ADE40, sys_thread_t:0x80B4138, state:R, native ID:0xA4) prio=5
    4XESTACKTRACE at sun.awt.windows.Win32SurfaceData.initDDraw(Native Method)
    4XESTACKTRACE at sun.awt.windows.Win32SurfaceData.<clinit>(Win32SurfaceData.java:302)
    4XESTACKTRACE at sun.awt.windows.D3DBlitLoops.register(D3DBlitLoops.java:72)
    4XESTACKTRACE at sun.awt.windows.Win32OffScreenSurfaceData.initD3D(Win32OffScreenSurfaceData.java:125)
    4XESTACKTRACE at sun.awt.windows.Win32OffScreenSurfaceData.<clinit>(Win32OffScreenSurfaceData.java:167)
    4XESTACKTRACE at sun.awt.Win32GraphicsDevice.<clinit>(Win32GraphicsDevice.java:91)
    4XESTACKTRACE at sun.awt.Win32GraphicsEnvironment.makeScreenDevice(Win32GraphicsEnvironment.java:201)
    4XESTACKTRACE at sun.java2d.SunGraphicsEnvironment.getScreenDevices(SunGraphicsEnvironment.java:353)
    4XESTACKTRACE at sun.awt.Win32GraphicsEnvironment.getDefaultScreenDevice(Win32GraphicsEnvironment.java:94)
    4XESTACKTRACE at java.awt.Window.init(Window.java:268)
    4XESTACKTRACE at java.awt.Window.<init>(Window.java:312)
    4XESTACKTRACE at java.awt.Frame.<init>(Frame.java:431)
    4XESTACKTRACE at java.awt.Frame.<init>(Frame.java:396)
    4XESTACKTRACE at com.tivoli.uif.controls.UFFrameManager.<init>(UFFrameManager.java:755)
    4XESTACKTRACE at com.tivoli.uif.controls.UFFrameManager.startFrameManager(UFFrameManager.java:97)
    4XESTACKTRACE at com.tivoli.console.ConsoleLauncher.<init>(ConsoleLauncher.java:84)
    4XESTACKTRACE at com.tivoli.console.SingleAppLauncher.<init>(SingleAppLauncher.java:64)
    4XESTACKTRACE at com.tivoli.tec.console.EnterpriseConsoleLauncher.<init>(EnterpriseConsoleLauncher.java:142)
    4XESTACKTRACE at com.tivoli.tec.console.LauncherThread.run(LauncherThread.java:38)
    3XMTHREADINFO "Finalizer" (TID:0x100AE0B0, sys_thread_t:0x7016BA8, state:CW, native ID:0x1340) prio=8
    4XESTACKTRACE at java.lang.Object.wait(Native Method)
    4XESTACKTRACE at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
    4XESTACKTRACE at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:160)
    4XESTACKTRACE at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:225)
    3XMTHREADINFO "Reference Handler" (TID:0x100AE108, sys_thread_t:0x7014808, state:CW, native ID:0xB00) prio=10
    4XESTACKTRACE at java.lang.ref.Reference.process(Native Method)
    4XESTACKTRACE at java.lang.ref.Reference.access$300(Reference.java:52)
    4XESTACKTRACE at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:132)
    3XMTHREADINFO "Signal dispatcher" (TID:0x100AE160, sys_thread_t:0x7011D58, state:R, native ID:0x194) prio=5
    NULL ------------------------------------------------------------------------
    0SECTION CL subcomponent dump routine
    NULL ============================
    1CLCLASSPATH      Classpath Z(C:\Tivoli\TEC39FP8\jre\lib\core.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\graphics.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\security.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\server.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\xml.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\charsets.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\ibmcertpathprovider.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\ibmjaasactivelm.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\ibmjaaslm.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\ibmjcefw.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\ibmjgssprovider.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\ibmjssefips.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\ibmjsseprovider.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\ibmorb.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\ibmorbapi.jar),Z(C:\Tivoli\TEC39FP8\jre\lib\ibmpkcs.jar)
    1CLFLAGOLDJAVA      Oldjava mode false
    1CLFLAGBOOTSTRP     Bootstrapping false
    1CLFLAGVERBOSE      Verbose class dependencies false
    1CLENUMVERIFY      Class verification VERIFY_REMOTE
    1CLPNTRNAMECLLO     Namespace to classloader 0x00000000
    1CLPNTRCHAINLO      Start of cache entry pool 0x081A1978
    1CLPNTRCHFREE      Start of free cache entries 0x081A39E4
    1CLPNTRMETHODTB     Location of method table 0x06FA2F40
    1CLPNTRANCHRGLN     Global namespace anchor 0x002B383C
    1CLPNTRCLSLOADS     System classloader shadow 0x06F4B008
    1CLPNTRSYSLOADS     Classloader shadows 0x081265C0
    1CLPNTRCLSEXT      Extension loader 0x100ADFD8
    1CLPNTRSYSLOADR     System classloader 0x100ADF58
    1CLTEXTCLLOS      Classloader summaries
    1CLTEXTCLLSS           12345678: 1=primordial,2=extension,3=shareable,4=middleware,5=system,6=trusted,7=application,8=delegating
    2CLTEXTCLLOADER          ------a- Loader sun/reflect/misc/MethodUtil(0x081265C0), Shadow 0x100ADD28, Parent sun/misc/Launcher$AppClassLoader(0x100ADF58)
    3CLNMBRLOADEDCL               Number of loaded classes 1
    3CLNMBRCACHECLS               Number of cached classes 7
    3CLHEXDALLOCTIO               Allocation used for loaded classes 1
    3CLHEXDPCKGEOWN               Package owner 0x100ADD28
    2CLTEXTCLLOADER          -x---t-d Loader sun/reflect/DelegatingClassLoader(0x079559A0), Shadow 0x100ADEA0, Parent sun/misc/Launcher$ExtClassLoader(0x100ADFD8)
    3CLNMBRLOADEDCL               Number of loaded classes 1
    3CLNMBRCACHECLS               Number of cached classes 3
    3CLHEXDALLOCTIO               Allocation used for loaded classes 3
    3CLHEXDPCKGEOWN               Package owner 0x100ADEA0
    2CLTEXTCLLOADER          -----ta- Loader sun/misc/Launcher$AppClassLoader(0x070DC9A0), Shadow 0x100ADF58, Parent sun/misc/Launcher$ExtClassLoader(0x100ADFD8)
    3CLNMBRLOADEDCL               Number of loaded classes 51
    3CLNMBRCACHECLS               Number of cached classes 341
    3CLHEXDALLOCTIO               Allocation used for loaded classes 1
    3CLHEXDPCKGEOWN               Package owner 0x100ADF58
    2CLTEXTCLLOADER          -xh-st-- Loader sun/misc/Launcher$ExtClassLoader(0x070CFFD0), Shadow 0x100ADFD8, Parent none(0x00000000)
    3CLNMBRLOADEDCL               Number of loaded classes 10
    3CLNMBRCACHECLS               Number of cached classes 95
    3CLHEXDALLOCTIO               Allocation used for loaded classes 3
    3CLHEXDPCKGEOWN               Package owner 0x100ADFD8
    2CLTEXTCLLOADER          p-h-st-- Loader System(0x06F4B008), Shadow 0x00000000
    3CLNMBRLOADEDCL               Number of loaded classes 952
    3CLNMBRCACHECLS               Number of cached classes 956
    3CLHEXDALLOCTIO               Allocation used for loaded classes 3
    3CLHEXDPCKGEOWN               Package owner 0x00000000
    3CLTEXT3CLTEXTCLASS                [S(0x002D1D58)
    NULL ------------------------------------------------------------------------
    0SECTION Javadump End section
    1DGJDUMP Javadump Buffer Usage Information
    NULL =================================
    2DGJDUMPALLOC Javadump buffer size (allocated): 2621440
    2DGJDUMPUSED Javadump buffer size (used) : 84652
    NULL ---------------------- END OF DUMP -------------------------------------

    It use to work fine Something changed. Could be a newer (maintenance) version of Java. Seems like those have been having more than a few problems say in the last year or so.
    Wild guess alternative - could also be a graphics driver problem.
    Everytime I launch this Tivoli TME client IThat sounds like a product. This is not a product support site. It is a site for programmers who use java. Product support should be directed to the source of the product.

Maybe you are looking for