ILM_STOR -

The following messages are stored in message class ILM_STOR: .
It is part of development package S_ILM_STOR_TYPES in software component BC-ILM-STO. This development package consists of objects that can be grouped under "ILM DB Store: Basis Types and Elementary Functions".
Message Nr
Message Text
000&1 &2 &3 &4
001Invalid program state
002Business function for activation of ILM DB Store is not active
003Function was replaced by an adequate function in Customizing
004This function will no longer be supported as of &1
005This function is obsolete; use &1 instead
006HTTP connection &1 does not exist
011Interface &1 implemented with &2 instead of &3
012Property &1 changed to &3 for URI &2
013Propterty &1 deleted from URI &2
014&
015E-mail was sent
069Please edit the Customizing for the mandatory property &1
100*** CX_ILM_STRG_EXEPTION ***
101Handle [&1] does not exist
102No processing data sent with URL &1
103Runtime information &1 does not exist for handle &2
104System cannot add runtime information &1 for handle &2
105URL was not transferred or is empty
106URI &1 is invalid
107System cannot determine handle for URL &1/origin &2
108Runtime error in method &1
109Runtime information for handle &2 is inconsistent (keyword &1)
110Command &1 is valid only for &2
111URI &1 is invalid; it must begin with this separator /
112No URI found for handle &1
113Legal hold for URI &1 cannot be changed; the path is already locked
114Legal hold for URI &1 cannot be deleted; the path is already locked
115Expiration date for URI &1 cannot be deleted
116Expiration date &1 for URI &2 has an invalid format
117Cannot change expiration date for URI &1 from date to <unknown>
118Expiration date &1 for URI &2 was shortened with &3
119Expiration date &1 for URI &2 cannot be changed to &3
120Expiration date &1 for URI &2 is in the past and therefore invalid
121URI &1 cannot be deleted because the element has expiration date &2
122Cannot delete URI &1 because there is a legal hold on the element
123Process BAdI could not be determined for &1
124Exception occurred during processing (&1)
125Delete URI &1 from store
126Resource &1 cannot be changed
127Cannot use handle &1: Object is not a resource
128Property &1 not found for URI &2
129Collection &1 cannot be generated under another resource
130Resource &1 cannot be created below another resource
131Cannot delete URI &1; status &2 is invalid
132Exception occurred when creating attribute &1
133You have not entered an ORIGIN
134Process step &1 stops processing
135Exception occurred in process step &1
200*** BEGIN CX_ILM_STRG_TRANSFER ***
201Error while opening file &1: &2
202Error while writing in file &1: &2
203Shared file &1 does not exist
204File name was not copied
205File &1 is read only
206No authorization for opening file &1 for &2
207Error while deleting file &1: &2
208Error while reading file &1: &2
209System caanot determine file name for a temporary file
210Security risk in &1 because of value &2
211File &1 does not exist
212File name already assigned for this data sink
213Memory sink does not recognize file name
214Error during creation / opening ILM DB Store
215Data sink opened in read access, no write access possible
216Data sink open in write access, no attribute changes possible
217Security breach while accessing file &1
218Logical file name was not transferred
219External handle &1 already exists and cannot be used
220Reopening the memory: Entry (&1) not found
221File cannot be copied to itself
222*** END CX_ILM_STRG_TRANSFER ***
250*** BEGIN CX_ILM_STRG_TRANSFER /Background Transfer ***
251Job could not be scheduled for &1 (reason: &2)
252Job could not be copied for &1 (reason: &2)
253Job scheduling could not be completed for &1 (reason: &2)
254Element &1.&2 selected to be moved
255Prepare processing of &1.&2
256Lock element &1.&2
257Unlock element &1.&2
258Process element &1.&2
259Close processing of element &1.&2
260Processing is completed in the background
261Could not lock element &1.&2
262Terminating processing of element &1.&2 due to process errors
263Background processing of element &1.&2 completed
264Element &1.&2 stays in the buffer as defined in Customizing
299*** END CX_ILM_STRG_TRANSFER /Background Transfer ***
300*** BEGIN CX_ILM_STRG_CUST ***
301Value &1 is not a Boolean value
302Value &1 is not a number
303&2.&3 not found for origin &1
304Property &1.&2 is read-only
305Namespace &1 not found
306Origin &1 not found
307Type &1 is not a known data type
308Property &1.&2 for origin &3 already exists
309Database connection &1 not found
311No data connection entered for table &1
312System command &1 for OS &2 is incorrect or not defined
313Logical path or file &1 not found
314Cannot expand logical path or file &1 (message: &2)
315Administrative ORIGIN cannot be changed in the current context (&1.&2)
316Administrative origin not found for origin &1
317Connection &1 to origin &2 doesn't have a type assigned, DBCO unknown
318Check possible only in the context of an origin
319Value &1 not within the permitted area (&2)
400*** BEGIN CMS INTEGRATION ***
401Runtime error: &1
402You need to transfer the repository ID
403You need to transfer the document ID
404No ORIGIN assigned to repository &1
405DOC_ID &1 was changed to &2
406Error while transferring data: &1
407Error while adding data: &1
408Error in attributes: &1
409Error while mapping data: &1
410Access information is missing
411Error during export of physical document (&1.&2.&3) to the store
412Incorrect parameter during document (&1.&2.&3) in the store
413Error while opening the store for document (&1.&2.&3), ORIGIN missing
414Unknown error during operation &4 for document (&1.&2.&3)
415Map for document (&1.&2.&3) could not be updated
416Component ID must be transferred
417Document (&1.&2.&3) not found
418Cannot instantiate HTTP client for connection &1; cause &2
419Store not reached: destination &1, reason &2
420Document larger than Customizing settings made for maximum data size
421Received return code &1 while reading from &2: &3
422Received return code &1 while writing from &2: &3
423Received return code &1 when readng document IDs from &2: &3
424Execution of the LIST command has started
425Execution of the LIST command is complete
426Execution of the READ command has started
427Execution of the READ command is complete
428Reading not possible; the document ID is missing
429Unknown command &1 in mode &2
430You cannot use repository type &1 here; only the ILM Store is possible
431Unknown request mode &1
449*** END CMS INTEGRATION ***
600*** START OF EMAIL RUNTIME ERRORS ***
601E-mail type &1 is unknown
602E-mail was not sent
650*** BEGIN RUNTIME ERRORS ***
651You can only specify one of the optional parameters
652At least one parameter from list of optional parameters is missing
653Transfer already taking place, a second call is not possible
654Calling method &1 is not valid in the current context
655Parameter &1, value [&2] is not within the expected value range
656Unexpected exception &1 when calling &2
657System cannot validate file name &1
658Logical file name &1 does not exist
659File name is empty
660No dictionary support for multiple instances (key &1)
661No class name available for interface &1, version &2, parameter &3
662Parameter &1 was not provided
663DBCON is not available for access to table &1
664Context not initialized before calling method &1
665System cannot determine a table for &1 because of an exception
666Unexpected value &1 found for &2
667Handles must be the same for &1 and &2
668&1 is not a valid date adhering to format yyyy-mm-dd
669&1 is not a valid date
670BLOB size of &1 may not be 0
671ORIGIN must be specified if a URI is transferred
672Double initialization not possible (&1)
673Method cannot be called here, use &1 instead
674Context origin already set, duplicate use not possible
675Area &1 cannot be calculated and excluded at the same time
676Status &1 invalid for HANDLE &2, &3 is expected
677BAdI implementation &1 not permitted in productive systems
678Default BAdI implementation &1 has to be re-implemented
679Error during system command &1: &2
680No authorization to execute an operating system command (&1)
681Virus scan error: &1
682System command &1 supplied return code &2
683Parameter check of system command &1 failed
684Cannot end processing; origin &1 is not equal to origin &2
685You cannot edit data in administrative mode
686Set an origin for system [&1:&2], resource type [&3]
687Parameter &1 needs a value
688Return value cannot be interpreted uniquely
689Specify connection type in the form <DBCON>@<CONN_SYS>
690Method &1 was not initialized after call (&2)
691This function is obsolete and can no longer be used.
698Needs to be done in the near future
699This function has not yet been implemented
700 *** BEGIN ADMIN ERRORS ***
701No authorization to select a data source
702Data source &1 has already been selected
703Use the customer namespace for the data source
704&1 selected as data source to be used
705No authorization to generate administration tables
706No authorization to execute test reports
707No authorization to change Customizing
708You are not authorized to execute this function
709No authorization to use the ILM DB store in production mode
710Enter the connection and select the table to be created
711Origin &1 is already being used elsewhere as an administrative origin
712Data inconsistency: Origin &1 is used more than once
713Origin &1 is already productive; do not use as an administrative origin
714You cannot use origin &1 because it already contains Customizing
715Could not lock origin &1
716Client ID &1 already exists; changing it is possible, creation is not
717Client ID &1 does not exist yet; update not possible
718An error occurred during DB operation &1
719Could not lock CLIENT_ID &1
720Content Repository &1 does not exist
721Origin &1 does not exist
722Origin &1 cannot be assigned to a content repository; it has no parent
724Could not lock mapping for content repository &1 - origin &2
725Origin &1 has already been assigned to another content repository
726Content repository &1 has already been assigned to another origin
727Content repository &1 has not yet been assigned to an orgin
800*** BEGIN DB ERRORS ***
801Key &1 not found in table &2
802Master entry missing in root table for &1.&2
803System could not update entry &1.&2
804Entry with key &1.&2 already exists
805Exception in streaming API for &1 to table &2
806SQL exception when accessing table &1
807Access to table &1 only possible with INSERT or UPDATE
808Security breach when accessing table &1
809Error &1 while attempting to lock table &2 for key &3
810System could not generate new data table for origin &1
811NULL handle / emplty handle cannot be used in method &1
812Name & invalid for data table; name must start with Y, Y, or Z
813Copying not possible, original table &1 is not active
814Copying not possible: &1 already exists
815You are not authorized to delete &1
816Transport request cannot be created: &1
817Pooled table cannot be created: &1
818Pooled table cannot be activated: &1
819Proxy table &1 cannot be created
820Copying not possible: original table &1 does not exist
821Generating data table &1 for connection &2 failed
822Security breach for SQL &1
823Deleting connection &2 from database table &1 failed
824Pooled table &3 was selected for origin &1, URI &2
825New pooled table &3 was generated for origin &1, URI &2
826Property &1 changed for handle &2 = &3
827Property &1 added for handle &2 = &3
828Pooled table &1 reached its size limit; do not add more data
829Generating table &1 for connection &2 failed
830Table &1 already exists on Sybase IQ
831Value &1 already exists in &3 for &2 but it is unique
832CHILD_ORIGIN &1 is already being used as an ADMIN_ORIGIN
833ADMIN_ORIGIN &1 has already been used as a CHILD_ORIGIN
834Origin &1 has already been assigned to another ADMIN_ORIGIN
835An association between origin &1 and ADMIN_ORIGIN &2 is not possible
836Exception while writing data to &1 (&2)
837Exception while reading data from &1 (&2)
838Exception while deleting data from &1 (&2)
839Exception while opening &1 (&2)
840SELECT returns multiple results (only one entry permitted)
841Invalid: Administrative <- operative ORIGIN &1 not unique
842OAuth client configuration &1 does not exist
843OAuth client profile &1 does not exist
Privacy Policy