IBM Support

stmigrate tool introduces -fetch option to migrate non-cache objects to MSAR

Fix Readme


Abstract

The stmigrate tool of IBM FileNet Image Services adds a new option -fetch to migrate non-cache objects to MSAR. The need to set the DOCS status_1 to 3 and cache_id to 1 is not needed anymore. The -fetch option also helps to migrate NLS documents to MSAR or Optical if they are not present in the cache.

Content

The stmigrate tool had a limitation for migrating cache objects to MSAR. The tool needed the following MKF DOC table fields to be set to certain values:
  • status_1=3
  • cache_id=1
What's new
A new option -fetch is added to facilitate migrating documents that are not in cache. The -fetch option first attempts to fetch documents from the cache and then looks for documents elsewhere to migrate to MSAR.

The -fetch option also accepts the following values:
  • status_1 = null or 0 (normal) or 3 (not migrated)
  • cache_id = page cache ID or null
Notes:
  • If a document is already written to MSAR then the document is not migrated.
  • The -fetch option also helps to migrate NLS documents to MSAR or Optical.
Usage statement
-fetch - If documents are not in the cache, then attempt to migrate to the cache first before writing to MSAR or Optical. This is especially useful for moving from NLS documents to MSAR or Optical. By default, if a document is not in the cache, it is not migrated. With this option, if a document not in the cache, -fetch tries to fetch it into the cache first and then migrates. It is not necessary to select the -date option.

Before running the stmigrate tool
  • Ensure that the associated document families use the type MSAR media.
  • If you want to write to SDS use the sds_migr tool instead of the stmigrate tool.
Note that the Background Job completion file now gives a more accurate count of the migrated documents.

Feature availability

The feature is available from the following releases of Image Services on the IBM Fix Central:
  • Image Services 4.1.2.27 interim fix 6102215 and later
  • Image Services 4.2.0 fix pack 16 (4.2.0.16) and later

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVUD","label":"FileNet Image Services"},"ARM Category":[{"code":"a8m50000000Cdy8AAC","label":"FileNet Image Services"},{"code":"a8m50000000Ce5JAAS","label":"FileNet Image Services-\u003ECache Services"},{"code":"a8m50000000Ce4NAAS","label":"FileNet Image Services-\u003EDocument Services (dbp, DOCs)"},{"code":"a8m50000000CdyJAAS","label":"FileNet Image Services-\u003EMKF Services"},{"code":"a8m50000000Ce4BAAS","label":"FileNet Image Services-\u003EMSAR"},{"code":"a8m50000000Ce4lAAC","label":"FileNet Image Services-\u003ENLS"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF057","label":"HP"}],"Version":"4.1.2;4.2.0"}]

Document Information

More support for:
FileNet Image Services

Component:
FileNet Image Services, FileNet Image Services->Cache Services, FileNet Image Services->Document Services (dbp, DOCs), FileNet Image Services->MKF Services, FileNet Image Services->MSAR, FileNet Image Services->NLS

Software version:
4.1.2, 4.2.0

Operating system(s):
AIX, Solaris, Windows, HP

Document number:
6462547

Modified date:
22 December 2021

UID

ibm16462547

Manage My Notification Subscriptions

Page Feedback