SOI3 - SOI Messages
The following messages are stored in message class SOI3: SOI Messages.
It is part of development package SOI_TOOLBOX in software component BC-UPG-SOI. This development package consists of objects that can be grouped under "Safe Online Import Toolbox".
It is part of development package SOI_TOOLBOX in software component BC-UPG-SOI. This development package consists of objects that can be grouped under "Safe Online Import Toolbox".
Message Nr ▲ | Message Text |
|---|---|
| 000 | ============================= Level C =================================== |
| 001 | No valid action |
| 002 | Level C action &1 failed |
| 003 | Level C action &1 completed successfully |
| 004 | Check Level C prerequisites are not fullfilled |
| 005 | Proposal for server groups could not be established |
| 006 | Proposal for 'Read Only' server group contains: |
| 007 | Proposal for 'Late Blue' server group contains: |
| 008 | Server: &1 |
| 009 | Groups and associated instances could not be saved |
| 010 | Server group (Read Only and Late Blue) instance information not found |
| 011 | Check Level C prerequisites |
| 012 | Check Level C prerequisites checks are completed |
| 013 | Propose system sepration in Read Only and Late Blue group |
| 014 | System separation proposal successfully established |
| 015 | Instantiation of class &1 failed |
| 016 | LeveL C tables to lock cannot be retrieved |
| 017 | Validation of server groups was executed with errors |
| 018 | Server group &1 is not ready for Level C execution |
| 019 | Set profile parameter &1 |
| 020 | Profile parameter &1 set sucessfully |
| 021 | Error setting profile parameter &1 |
| 022 | Server group (Late Blue) instance information not found |
| 023 | Adjustment of Late Blue server group's workprocesses delivers errors |
| 024 | Adjustment of Late Blue server group's workprocesses was successful |
| 025 | Adjust and validate Late Blue server group's workprocesses |
| 026 | Execute subsystem separation |
| 027 | Subsystem separation could not be established |
| 028 | Subsystem separation successfully established |
| 029 | Switching visibility of Late Blue group to 'hidden' |
| 030 | Switching visibility of Late Blue group was successfully executed |
| 031 | Switching visibility of Late Blue group failed |
| 032 | Check that subsystem separation in message server is inactive |
| 033 | Check of subsystem separation in message server was not successful |
| 034 | Subsystem separation in message server is inactive |
| 035 | Re-activate the RKS compatibilty check in the message server |
| 036 | RKS compatibilty check in the message server activated again |
| 037 | RKS compatibilty check in the message server could not be re-activated |
| 038 | Subsystem separation in message server is active |
| 039 | RKS compatibilty check in the message server could not be de-activated |
| 040 | RKS compatibilty check in the message server de-activated |
| 041 | Check server groups (Read Only and Late Blue) |
| 042 | Check server groups (Read Only and Late Blue) successfully executed |
| 043 | No valid switch state |
| 044 | No valid key value &1 |
| 045 | Information &1: &2 saved to deploy parameter table |
| 046 | Prerequisites are fullfilled: Level C transisiton will be executed |
| 047 | Level C transition is possible |
| 048 | Level C transition is not possible |
| 049 | De-activate the RKS compatibilty check in the message server |
| 050 | Proposal for server groups not established as only 1 appl. server exists |
| 051 | Error setting parameter &1 (Object of class &2 not instantiated) |
| 052 | Error handling maintainance mode |
| 053 | Handling maintainance mode was successful |
| 400 | =============================== General & Misc ========================== |
| 401 | System parameters of the viewlayer system are incorrect |
| 402 | HDI containers are inconsistent |
| 403 | Checking consistency of cont. &1 (phys.:&2): incons. objs. in HTA |
| 404 | Start: Checking consistency of container &1 (phys.:&2) |
| 405 | Simulated deployment of container(s) failed |
| 406 | Start: Setting container &1 (phys. name: &2) to read-only |
| 407 | Setting container &1 (phys. name: &2) to writable failed |
| 408 | Current process has to run on green system |
| 409 | Could not retrieve Green Access schema |
| 410 | HTA/HDI test data instanciation failed |
| 411 | V1 test data creation failed |
| 412 | V2 test data creation failed |
| 413 | Unexpected result from target schema check (Target schema &1) |
| 414 | Unknown action: (Set/Release BCP lock are possible) |
| 415 | BCP lock handling failed |
| 416 | Q2P transport(s) could not be retrieved |
| 417 | Q2P transport(s) successfully retrieved |
| 418 | Prerequisites for Q2P transport retrieval not fulfilled -> No action |
| 419 | Reset of control tables for HTA/HDI cloning successful |
| 421 | Current process has to run on blue system |
| 422 | Could not retrieve blue access schema |
| 423 | Reconnect is in an erroneous state |
| 424 | Unknown reconnect state |
| 426 | Check Run &1 |
| 427 | BCP lock handling not possible as lock functionality is not available |
| 428 | BCP Lock handling successfully finished |
| 429 | BCP stop handling not possible as lock functionality is not available |
| 430 | Table buffer for table & could not be reset |
| 431 | Table buffer for table & reset successfully |
| 432 | HDI Reset not required |
| 433 | Tabelle &1 existiert nicht -> Puffer R�cksetzen nicht notwendig |
| 434 | Call of function module RLFW_RECONNECT_TO_BRIDGE_SOI failed |
| 436 | Parameter &1 is unknown |
| 437 | System belongs to a foreign transport domain |
| 438 | TMS configuration could not be read |
| 439 | tp configuration could not be read |
| 440 | tp configuration could not be modified |
| 441 | tp version could not be read |
| 442 | tp version is &1 |