If it is dataprotection client you can change the location of the command file to be executed to the diffetent partition/Filesystem and then schedule with that new updated path. Review the dsmerror.log file (and dsmsched.log file for scheduled events) to determine what error messages were issued and to assess their impact on the operation. Enter the domain name and password. You are advised to run a a manual backup to ensure your data is backed up. http://u2commerce.com/return-code/tsm-error-return-code-1.html
Check the TSM Self-Registration Page to ensure that you do not have two or more similarly-named registered nodes: it could be that one of them is active and being backed up, Files are not processed for various reasons. To find out when your next scheduled backup is, please see the FAQ item When is my scheduled backup due to run?. 3. Not all file failures cause schedule failures but Windows in particular does sometimes lock open files in such a way that it causes TSM to call a schedule failed when really http://www.ibm.com/support/docview.wss?uid=swg21442741
If the return code is 0, the status of the scheduled operation will be Completed. If you cannot close the file(s) that is/are causing the schedule failure before scheduled backup occurs, then you should exclude them from backup. After scheduled work is performed, check the schedule log to verify that all work completed successfully.
The exception to the above rules are warning or error messages that individual files could not be processed. Enabling firewall support See Tivoli Storage Manager firewall support for information about enabling the backup-archive client, command line admin client, and the scheduler to run outside a firewall. Please make sure that the Command file and the Application not installed in the same partition/Filesystem. Ans1512e Return Code = 12 Therefore it is important both to resolve this issue as soon as possible to enable future scheduled backups to run; and also to perform a manual backup to ensure that your
If the machine was off when the schedule was due to run then the schedule will have been missed. Return Code 8 In Teradata Depending on your operating system, you now need to search through the log file. The latter will cause an error because only drives or partitions may normally be used as domains: hence TSM cannot find the drive /data/fred and so it deems that the schedule For cases where the return code is not 0, you can examine the dsmerror.log file (and, for scheduled events, the dsmsched.log file).
XenForo add-ons by Waindigo™ © 2014Waindigo Ltd. Return Code 8 In Unix Table 1. Once there, select [Edit] and then [Find] (or use CTRL+F) to bring up the search box. Vasanth N vnvasanth, Aug 21, 2008 #6 (You must log in or sign up to reply here.) Show Ignored Content Share This Page Tweet Your name or email address: Do
There were no other errors or warnings. Further investigation is required to determine how much of your data was backed up - it could be some, all, or none of it that got sent to the HFS. Tsm Return Code Is -50 MsgNum 1496 is ANS1496W. Ans9020e Could Not Establish A Session With A Tsm Server Or Client Agent In Windows, in My Computer, right-click on the offending drive (e.g.
NO - If the machine did not switch on, report this problem to the Help Centre as this is an issue with the Wake on Lan service. this content Your administrator associates clients with one or more schedules that are part of the policy domain maintained in the server database. To fix this problem: If your machine is a Mac, ensure that you are running TSM 6.1.3 or higher - please check your TSM version using our instructions under Which version If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful. Tsm Client Return Codes
changed during processing' TSM may send most of your data but ultimately report overall scheduled backup failure if other files are left open. Some commands may issue a nonzero return code to indicate success. In activity log , i am getting ANR2579E error code with RC=1.
Automating tasks This chapter applies to the Authorized User only. failed" and at least one other message as well. Then ask your Tivoli Storage Manager server administrator modify the schedule definition to invoke your script instead of the command. Manual backup - If you already know why this scheduled backup was missed and then you may just wish to run a manual backup.
The file was in use by another application and could not be accessed by the client. This return code is very common. Examining dsmsched.log using a text editor Browse to the appropriate location and open dsmsched.log. E.g.
Any ideas? For OS/390 UNIX: Create a shell script called /tivoli/tsm/client/ba/bin/rundsmc which contains the following entries: cd /usr/lpp/Tivoli/tsm/client/ba/bin sleep 60 ./dsmc schedule This prevents the creation of two jobs with the same name Displaying information about scheduled work To view schedules that are defined for your client node, enter: dsmc query schedule Storage Manager displays detailed information about all scheduled work for your client The listed domain entry does not exist as a drive or partition: One reason for this could be that a folder/directory has been specified as a separate domain.
marclant replied Oct 27, 2016 at 12:47 PM Loading... In the box provided change Files of Type to be [All Files]. This return code is very common. See "Copy serialization". 8 The operation completed with at least one warning message.
If the return code is 0, the status of the scheduled operation will be Completed. The file was in use by another application and could not be accessed by the client. Is your TSM node locked? GlobalRC.cpp ( 408): Old values: rc = 0, rcMacroMax = 0, rcMax = 0.
However, it is clear that the scheduled backup itself has completed and the failure message can be ignored. 2.3.6. 'ANS1030E The operating system refused a TSM request for memory allocation' This