CA Client Automation - 14.0

PDF
English

How to Move the OSIM Job Information

cla140
cla140
Contents
The software delivery functionality lets you transfer the OSIM job information while moving a target computer from one domain manager to another. All the information about completed, planned, and activated OSIM jobs is preserved and moved as part of any standard SD computer move operation. You do not need to perform any manual steps to export or import the information across different domain managers. You can automatically transfer the complete OSIM job information along with the SD installation records while performing any normal computer move operation.
Configure the OSIM Move Configuration Policies
To move the OSIM job information during a computer move operation, configure the OSIM move configuration policies. Using these policies, you can control the overall behavior of transferring the OSIM job information from a previous domain manager to a current domain manager. You must apply these policies on the domain manager to which the agents are being moved. The values of these policies on the previous domain manager do not influence the behavior of moving the OSIM job information to the current domain manager. Thus, the OSIM move policies applied on the current domain manager define the transfer behavior of the OSIM job information, and not the policies applied on the previous domain manager.
To configure the OSIM move configuration policies
  1. Navigate to Control Panel, Configuration, Configuration Policy,
    policy name
    , DSM, Software Delivery, Manager.
    A list of configuration policies appears.
  2. Double-click the following policies, and specify appropriate values in the Setting Properties dialog:
    • Computer move: OSIM Move enabled
      Specifies whether to move the OSIM job information along with the installation records from a previous domain manager during an SD computer move operation. You can set the parameter value to True or False. Setting the parameter value to True always attempts to move the OSIM job information and the installation records from the previous domain manager. However, setting the value to False disables transfer of the OSIM job information, and attempts to move only the installation records.
      Default:
       True
    • Computer move: OSIM Move Postpone codes
      Specifies whether to move the installation records from a previous domain manager after initiating transfer of the OSIM job information. If transfer of the OSIM job information fails with an error code that is present in the error codes list specified for this setting, the transfer of the OSIM job information and the installation records is postponed until the next computer move attempt is made. However, if the transfer of the OSIM job information succeeds or fails with an error code
      not
      included in the list specified for this setting, the process of moving the installation records is initiated.
      The error codes list is a comma-separated list and can include the following error codes:
      1,2,3,4,5,6,8,9,12,13,45,107,207,211,214.
      Default:
       1,2,3,4,5,6,8,12,13,45,211
  3. Click OK.
    The OSIM move configuration policies are configured.
Diagnosing an Error during a Computer Move Operation
The event log lists the reasons for the failure of a computer move operation. You must check the event log to know why the computer move operation has failed. If you find that the computer move operation has failed because of the failure of the OSIM move operation, you can configure the
Computer move: OSIM Move Postpone codes
 configuration policy parameter accordingly.
For example, consider the following sequence of steps to detect and analyze an error that occurs during a computer move operation. In this example, the OSIM job movement fails with an error code 5:
  1. Make sure that the Computer move: OSIM move enabled configuration policy is enabled on the computer.
  2. Make sure that the list of error codes defined for the Computer move: postpone codes configuration policy is as follows:
    1,2,3,4,5,6,8,12,13,45,211.
  3. Attempt a computer move operation for a target computer from domain manager 1 (DM1) to domain manager 2 (DM2). This attempt tries to initiate the movement of the OSIM job records for the target computer. In this example, transfer of the OSIM job records fails with the error code 5.
  4. Check that the error code 5 is present in the list already defined for the Computer move: postpone codes configuration policy. In this example, the error code 5 is available in the list, so the SD move (movement of the installation records) is postponed and the computer move operation fails.
  5. Open the event viewer (Windows event console) and check the reason for this failure. If you find that this error is not going to be corrected on subsequent retries, you can remove the error code 5 from the list. Any further failure with the error code 5 does not postpone the SD move operation.
Error Codes
The following table includes the OSIM job error codes, error codes description, and possible solution:
Error Code
Error Description
Suggested Solution
0
Success
Not Applicable
1
The resource file for the OsimMove program could not be opened.
This is probably an installation problem. Check the installation and start the operation again.
2
Missing or invalid command line arguments.
This is probably an error in the calling program. Contact CA Technical Support.
3
The session with the OSIM Manager could not be established.
This seems to be a temporary problem. Try again later.
4
Unknown command specified on command line. Only “export” and “import” commands are supported.
This is probably an error in the calling program. Contact CA Technical Support.
5
Job data output file not specified or the file could not be created.
This might be a temporary problem (disk full). Try again later.
6
Job data input file not specified or the file could not be loaded.
The job data file does not exist or is corrupted. This might be a temporary problem. Try again later.
7
A specified computer name or UUID was not found in the database (export operation).
This could be a temporary database problem. Try again later.
8
The specified name or UUID list file could not be opened.
This might be a temporary problem. Try again later.
9
A computer was specified by name for export, but its host UUID is unknown.
This is probably an error in the calling program. Contact CA Technical Support.
12
The file compress component could not be initialized or there was an error compressing or uncompressing the job file.
This could be an installation problem. If the error occurs on import, the job data file might be corrupt. Check the compress component and then retry the operation.
13
The result file could not be created or opened.
This could be a temporary problem (disk full). Try again later.
45
Movement of the OSIM job records not supported by the previous domain manager.
Upgrade the previous domain manager from where the movement of OSIM jobs is attempted.
107
A specified computer name or UUID was not found in the database (export operation).
This could be a temporary database problem. Try again later.
207
A specified computer name or UUID was not found in the database (import operation).
The specified computer is not registered with the new domain manager. Register the computer and retry.
211
The required OS image for a job was not found in the database.
A required OS image is not registered in the new domain manager. Register the OS image in the new domain manager with the same name as it was in the previous domain manager.
214
A specified host UUID was not found in the job data file.
This is probably an error in the calling program. Contact CA Technical Support.