SUPG_SGEN - Message texts for Upgrade SGEN
The following messages are stored in message class SUPG_SGEN: Message texts for Upgrade SGEN.
It is part of development package SAUS_SGEN in software component BC-UPG-TLS-TLA. This development package consists of objects that can be grouped under "SGEN delivered with SUM".
It is part of development package SAUS_SGEN in software component BC-UPG-TLS-TLA. This development package consists of objects that can be grouped under "SGEN delivered with SUM".
Message Nr ▲ | Message Text |
---|---|
065 | User &1 is not authorized to execute report &2 |
066 | Shadow SGEN can only be aborted on the shadow / ZDO / Temp system |
067 | Shadow SGEN aborted. SUM should continue with next phase soon. |
068 | No open generation tasks found in UPGGENSET => shadow SGEN not running |
069 | Number of generation tasks set to ''finished'' in UPGGENSET: &1 |
170 | Report &1 started |
171 | Report &1 finished successfully |
172 | Report &1 finished with errors |
500 | *** MESSAGES FOR SHADOW SGEN *** |
501 | Another generation job is already scheduled active |
502 | Transaction SGEN locked by user &1 |
503 | Server &1 mit machine type &2 not reachable by RFC |
504 | No objects waiting for generation could be found |
505 | No objects found for follow-up generation |
506 | No usable server was found for generation |
507 | No objects found for follow-up generation |
508 | Determining load for all software components |
509 | Starting load detection for invalidated objects |
510 | Total of &1 object(s) still waiting to be generated |
511 | No objects found for follow-up generation |
512 | Another generation job is already scheduled active |
513 | Transaction SGEN locked by user & |
514 | Job &1(&2) started for &3 object(s) |
515 | Job &1(&2) is not in the job overview |
516 | Job &1(&2) for machine type &3 still has &4 object(s) to process |
517 | Job &1(&2) terminated; generation not finished |
518 | Number of checked objects: &1 of &2 |
519 | &1 invalidated load(s) detected |
520 | Status reset for &1 object(s) |
521 | Determining LOAD for transport request &1 |
522 | &2 object(s) determined in transport request &1 |
523 | &1 object(s) determined from transport requests |
524 | Number of checked objects: &1 of &2 |
525 | Unable to find & in the management table (E070) |
526 | Error during existence check of transport request & |
527 | Error when determining source and target release |
528 | Unable to open replist file &1 in directory &2 |
529 | Unable to read replist file |
530 | RC & in DD_DB_OPERATION DEL for table & |
531 | RC & in DD_DB_OPERATION CRE for table & |
532 | RC & in db_truncate_table for table & |
533 | File &1 not found |
534 | Security check failed accessing &1 |
535 | Failure during opening of file &1 |
536 | Failure during reading of file &1 |
537 | Report &1 can only be run in shadow system. |
538 | Generation is being cancelled. Wait until 'Job status: Completed' appears |
539 | Error in termination; job could not be terminated (sy-subrc: &1 ) |
540 | It may take a few minutes to cancel generation |
541 | Deleting old entries in table RZLLITAB failed (sy-subrc: &1 ) |
542 | Error storing group 'parallel_generators' in tab RZLLITAB (sy-subrc: &1 ) |
543 | Job already scheduled or active for machine type &1 |
544 | Scheduled time &1 &2 occurs in the past |
545 | No server selected for generation |
546 | Consistent termination: & objects still to be generated. |
547 | Generation stopped due to & generation errors |
548 | Data basis: & |
549 | & |
550 | Generation for machine type & |
551 | Server & is used during parallel processing |
552 | Control program of the parallel processing on host & was started |
553 | Number of objects processed prior to this run: & |
554 | &2 parallel jobs have been scheduled to generate &1 objects |
555 | Number of objects to be generated: & |
556 | Each job processes & objects for one run |
557 | Task & completed |
558 | Generation was completed after & resumptions |
559 | Generating & objects of the canceled jobs |
560 | Each job processes & objects for one run |
561 | Termination of the generation completed |
562 | Could not initialize RFC group &1 (sy-subrc = &2) |
563 | No resources currently available for RFC group &1 (sy-subrc = &2) |
564 | Could not determine free dialog processes |
565 | Error during existence check of transport request & |
566 | No components selected for generation |
567 | No server selected for generation |
568 | Generation set contains &1 object(s) |
569 | Table UPGGENSET now contains &1 entries |
570 | Found server &1 with machine type &2 for generation |
571 | Function JOB_OPEN failed with sy-subrc &1 |
572 | Function JOB_CLOSE failed with sy-subrc &1 |
573 | Reset task &1 after max waiting time of &2 seconds |
574 | Info: Loads will use approximately &1 MB on database |
575 | Info: Loads will use approximately &1 GB on database |
576 | Note: Too many generation errors are often due to a full database table |
577 | space. Please check the free table spaces before reporting the error. |
578 | Detailed error messages can be found in the work process logs of the |
579 | shadow system, located in <..>/SUM/abap/system/<..>/work |
580 | After increasing the table space size, the SUM execution can be resumed. |
581 | Generate &1 loads in &2 processes with &3 objects |
582 | Reduced loads due to cloud scope from &1 to &2 |
583 | Changed &1 from &2 loads to 'optional' due to switch framework |
584 | No invalid loads found |
585 | &1 object(s) determined from transports intersecting with replist |
586 | No value for SGEN_MODE set in UPGPARAM |
587 | Already generated loads in last run: &1 |
600 | Check load task did not finish successfully (check dumps in ST22) |
601 | &1 : Program not found before generation |
602 | &1 : Generation failed |
603 | &1 : Program not found after generation |
604 | &1 : Before/After headers differ, load had beed invalid! |
605 | Report &1 started |
606 | Report &1 finished successfully |
607 | Report finished with error: &1 |