Id | Title |
---|---|
SPI8313 | No process instances exist or existed |
SPI8314 | Garbage Collector |
SPI8315 | Deleting process instances without respective metadata |
SPI8316 | &1 process types were found in the meta store |
SPI8317 | &2 process instances without valid process type were selected (&1) |
SPI8318 | No process instances without valid process type were selected (&1) |
SPI8319 | Deleting in packages for &1 process step instances |
SPI8320 | Package &3: &2 steps deleted (&4 statistical records, &1) |
SPI8321 | No more process steps were selected (&1) |
SPI8322 | Header data of the process instances was deleted (&1) |
SPI8323 | Delete instance steps without associated process instance |
SPI8324 | Deletion in packages for &1 instance steps and payload data |
SPI8325 | Locked by another reorganization run |
SPI8326 | &1 instance step and &2 payload entries deleted |
SPI8330 | Deleting cumulation data without related metadata |
SPI8331 | No cumulation tools were found |
SPI8350 | Reorganization of the event store: &1 |
SPI8351 | &1 events of type &2 deleted |
SPI8403 | &1&2&3&4 |
SPI8404 | &1: Table size and table growth were not monitored for over 24 hours |
SPI8405 | Warning if table growth was not monitored for longer than 24 hours |
SPI8406 | Size of a PMI application data table at the time of the last check |
SPI8407 | Growth of a PMI application data table in the 24 hours before last check |
SPI8408 | Active |
SPI8409 | Active, however the related assembler job has not been scheduled |
SPI8410 | Deactivated, however the related assembler job is active |
SPI8411 | Monitoring status or job status cannot be determined |
SPI8412 | &1: Table size and growth were regularly monitored |
SPI8413 | Agent <&1>: Step <&2> could not be activated for destination <&3> |
SPI8414 | Agent <&1>: Step <&2> could not be deactivated for destination <&3> |
SPI8415 | Deactivation/activation error of a signature for a process step |
SPI8416 | Are the monitoring status and job status of a process consistent? |
SPI8417 | Descriptive text of a process type |
SPI8418 | Distance between end times of the last two jobs to have run, in minutes |
SPI8419 | Agent <&1> is not active for destination &3 |
SPI8420 | Step <&2> is not active for destination &3 |
SPI8421 | Step <&2> is not completely active for destination &3 |
SPI8422 | Field <&4> of step <&2> does not exist on destination &3 |
SPI8423 | Field <&4> of step <&2> exists on destination &3 |
SPI8424 | A condition for field <&4> of step <&2> does not exist (&3) |
SPI8425 | A condition for field <&4> of step <&2> is available but incorrect (&3) |
SPI8426 | The condition for field <&4> of step <&2> is correct (&3) |
SPI8427 | Field <&4> of step <&2> actively exists for destination &3 for nothing |
SPI8428 | A condition for field <&4> of step <&2> exists too many times (&3) |
SPI8429 | Agent <&1> cannot be checked for destination &3 |
SPI8430 | Destination &3 cannot be checked |
SPI8431 | Checking active process <&3> |
SPI8432 | Checking agent <&1> for process <&3> |
SPI8433 | Destinations that cannot be checked |
SPI8434 | Configuration data that should not actually be available |
SPI8435 | Destination <&3> |
SPI8436 | Agent <&1> |
SPI8437 | Inconsistencies & errors in the configuration data of the agents |
SPI8438 | &2: Deactivation/Activation error in configuration data of agents |
SPI8439 | &1 &2: Checking local agent configurations |
SPI8440 | &2 &3: Activating agents of process &1 |
SPI8441 | Step <&2> was successfully activated for <&3> |
SPI8442 | &2 &3: Deactivating agents of process &1 |
SPI8443 | Step <&2> was successfully deactivated for <&3> |
SPI8444 | Activating the self monitoring of the data supplier was unsuccessful |
SPI8445 | Failed for processes in client <&1> |
SPI8446 | Monitoring of PMI application tables for &1 |
SPI8447 | Error in the agent configuration of process &1 |
SPI8448 | Assembler is running too often (currently every &1 minutes) |
SPI8449 | &1: Monitoring of monitoring status and job status of process <&2> |
SPI8450 | &1: Agents activated/deactivated successfully |
SPI8451 | &1: Transport of local PMI data to PMI system |
SPI8452 | General information on transport |
SPI8453 | Transport ran in mode &1 |
SPI8454 | Transport started/scheduled by user &1 |
SPI8455 | Network load for destination &1: |
SPI8456 | Processing terminated due to following: &1 |
SPI8457 | Preparing destination: &1 |
SPI8458 | &1: Transport of PMI data for process: &3 |
SPI8459 | End timestamp for reading PMI data: &1 |
SPI8460 | PMI data from destination &1 not available |
SPI8461 | Read and transport PMI data from destination &1 |
SPI8462 | &1: Instance &2 not available |
SPI8463 | &1: Instance &2 available |
SPI8464 | RFC error: &1 |
SPI8465 | &1 deleted process &2 |
SPI8466 | &1 activated monitoring for process &2 |
SPI8467 | &1 deactivated monitoring for process &2 |
SPI8468 | &1 released process &2 |
SPI8469 | &1 canceled the release for process &2 |
SPI8470 | Read and transport PMI data for following process steps, |
SPI8471 | PMI data not available for process steps specified above |
SPI8472 | Preparing to read PMI data for following process steps, |
SPI8473 | Number of records read: &1 |
SPI8474 | &2 error(s) occurred in target system with destination &1: |
SPI8475 | Instance &1, error/warning: &2 |
SPI8476 | Number of records copied from destination &1: &2 |
SPI8477 | Invalid timestamp (initial) |
SPI8478 | Final status of transport from destination &1: |
SPI8479 | Overview of all errors in destination &1: |
SPI8480 | Transport statistics of agents: |
SPI8481 | Number of inserts; agent <&1>, signature <&2>: &3 |
SPI8482 | Saving administration data |
SPI8483 | End of transport: &1 |
SPI8484 | Accessibility of instances for call number &1 |