RZ - Meldungen des RZ-Leistands

The following messages are stored in message class RZ: Meldungen des RZ-Leistands.
 It is part of development package SBTC in software component BC-CCM-BTC. This development package consists of objects that can be grouped under "SAP Background Processing".
Message Nr ▲
Message Text
000Define complete intervals first
001**** Message IDs 100-299 for general purposes ***************************
002**** Message IDs 300-399 for operating modes alphanumeric surface *******
003**** IDs 400-599 f. Alert explaining Texts ** 600-699 Threshold Mainten.
004Could not determine work process information
005No work process satisfies the selection criteria
006Failed to determine DB lock holder / lock waiter information
007At present it is only possible to determine DB lock for ORACLE
008First select a work process
009No auth. to end work processes
010Could not end work processes
011Failed to read work process info. from internal table
012Select a server
013String & not found
014Profile & does not contain any errors
100**** Message IDs 100-299 for general purposes ***************************
101Function not implemented on this platform.
102Command line too long. Permitted length is &.
103Error in ADM response from &
104Error at ADM message at &
105Applications server & does not respond.
110No display authorization for CCMS
111No administration authorization for CCMS
115Server & is not active. Profile check cannot be executed.
120BTCOPTION & with parameter & was not found
300**** Message IDs 300-399 for operating modes alphanumeric surface *******
301No instances were selected.
302Operation only allowed on Enqueue server.
303No operation mode scheduled for the present time.
304&1 no switch because of incompatible state; see status details
310No entries exist for operation mode &
311Switch to operation mode & triggered
312Operation modes timetable will be deleted
350*** Messages for Editing Operation Modes ****************************
351Number of dialog processes automatically results from total number.
352Total number of work processes is determined from the instance profile
353Choose an instance which belongs to operation mode &.
354An operation mode must be assigned.
355Instance is configured for & service, no. of work processes must be > 0
356Not configured for enqueue service, number cannot be changed
357The number of spool work processes cannot be changed.
358&1 &2 &3.
359There is already a server & defined, server name must be unique.
360The passwords specified must be identical
361Start profile & does not exist or cannot be read
362Instance profile & does not exist or cannot be read
363Home directory & does not exist
364Instance parameters that can be checked are OK.
365For service &, a & work process must be started in the profile.
366The start of the gateway is missing in the start profile.
367The start of the message server is missing in the start profile.
368Total no. work processes has changed, check WP allocation
369A sum of & work processes was determined from the instance profile.
370Operation mode & is not a production operation mode.
371Cursor is not on a valid line.
372The production instance data was saved
373Current version of profile & is not activated
374Profile & does not exist
375Data already being edited by user & - display only is possible
376Error in lock management. Editing is continued without locking.
377The checks are only possible with profiles from profile maintenance
378You must specify an application server name
379Server with enqueue process started, number cannot be changed to 0
380Server with update processes started, number cannot be changed to 0
381In start profile &, instance profile & is not specified
382Cursor not positioned on a valid field
383No profile name specified
384Server not started with enqueue process, number cannot be changed
385Assign work process allocation to an operation mode
386An instance name must be specified
387A host name must be specified
388Server & does not exist
389Deletion is not possible! Operation mode is assigned in the time table
390CAUTION: Profile &1 and file &2 are different. Check profile.
391You must specify both instance profile and start profile
392Server started without update processes; number cannot be changed
393Server started without update2 processes; number cannot be changed
394Sum of work processes changed; values from profile used
395Number of work processes exceeds rdisp/configurable_wp_no.
396Weighting successfully changed for round robin procedure
397Weighting for round robin procedure deleted
400**** Message IDs 400-499 for alerts alphanumeric surface ****************
401First open alert details
402Threshold values cannot be specified here
403Position cursor on alert details line
420** 420 - 499 Alert texts ** <- CAUTION: Max. 40 chars.
421Operating system alerts
422CPU load alert
423Paging alert
424Swap space alert
425File system alert
426Enqueue server alert
427System log alerts
428Critical system log occurred
429Frequent writes to system log
430Performance alerts
431Performance alert in dialog task
432Performance alert in update task
433Performance alert in V2 update task
434Performance alert in background task
435Performance alert in spool task
440Multiple buffer alerts
441Abap program buffer alert
442Generic table buffer alert
443Single key table buffer alert
444Presentation buffer alert
445CUA buffer alert
446Database statistics buffer alert
447Table description buffer alert
448Field catalog buffer alert
449Initial record buffer alert
450Short nametab buffer alert
451Alert thresholds for & deleted.
452Alert thresholds are being edited by user &.
453No other alert threshold values found
455Rollfile/pagingfile overflow
456TRACE active
457Dispatcher queue overflow
460Database alerts
461Missing indices
462Freespace problems
463DB log problems
464Backup failed
470Other alerts
500** 500 - 599 Description of alert types ** <- CAUTION: Max. 12 chars.
501?? Al.Undef.
502Summary
503OP system
504CPU load
505Paging
506Swap space
507File system
508Enqueue
509Syslog
510Syslog Id.
511Syslog freq.
512Performance
513Dialog perf.
514Update perf.
515Enqueue prf.
516Jobs perf.
517Spool perf.
518V2 upd. prf.
520Buffers
521Program
522Generic key
523Single Key
524Screen
525BufDBSt.
526Table descr.
527Field cat.
528Initial rec.
529ShortNameTab
530Abap dumps
531Abap errors
532Abap posting
533Abap error
534ABAP SQL Er.
535Roll/Paging
536Roll file
537Paging file
538Trace switch
540Other alerts
541Spool
542SAP Archive
543Backgr. off
544Configur.
545Others
550Disp. queue
551Dialog que.
552Update que.
553Enqueue qu.
554Jobs queue
555Spool queue
556V2 upd. qu.
560Database
561Miss.indexes
562Freespace
563DB logs
564Backup
601No segment data available
602Duplicate Segment or IP Addr. Re-enter data.
603Select only 100 IDs from the list
751IP address invalid: It does not meet the IPV4 or IPV6 standards
769**** Messages 769-791 Logon Group Maintenance (SMLG) ********************
770Single values > 255 not permitted
771Only 4 or 8-byte IP addresses are possible
772Changes were not saved
773Changes saved
774All entries displayed were deleted
775Assignment could not be deleted
776Assignment was deleted
777Table &1 is currently locked by user &2. Only display is possible.
778Table & could not be locked
779No entries were selected
780Enter a valid value
781Could not save data
782No logon groups defined
783Internal error (&)
784Assignment already exists
785Assignment applied
786Group & does not exist
787Group & was deleted
788No group exists on instance &
789All groups of instance & deleted
790Position the cursor on a valid group assignment
791&1 is reserved for system use
792Preferred instance selected for logon group &1: &2
793Error in read response time from monitoring architecture
794Value of parameter &1 should be &2 to &3
795Maximum number (32) of external RFC logon groups reached
796Specify a logon group
797Specify an instance
798Monitoring of logon load information activated
799Error activating monitoring. Check the activation history
800800-899 reserved for external management tool log (XMI)
801No log entries found
802You specified an invalid time period
803You did not specify a time period
804TALIM Table has been updated.
805TALIM Table has been updated.
806Group accepted. Resource allocation will be reset with a restart.
Privacy Policy