Content Manager OnDemand for i5/os Spool File Archive Media Migration Facility

Transcription

1 Content Manager OnDemand for i5/os Spool File Archive Media Migration Facility Content Manager OnDemand (OnDemand) Spool File Archive Media Migration Facility (MMF) provides a tool to move Spool File Archive data from one media type to another in an easy, recoverable way that can be stopped and restarted as needed. MMF updates all the necessary Spool File Archive files to point to the new location. The source media for MMF can be an optical volume, a tape volume, or an individual report name. The target media can be disk for all types of source media, optical if the source media is optical, and *ASM (Archive Storage Manager) if the source media is disk and contains reports that have been migrated from the Spool File Archive environment to the Common Server environment. The *ASM option is only available in OnDemand 5.4 and above, for data that has already been migrated from Spool File Archive to Common Server. The command interface is only available in OnDemand 6.1 and above. For example, MMF supports: permanent movement of archived data from optical volumes in an IBM 3995 Optical Library Dataserver to optical volumes in an IBM 3996 Optical Library (or any other optical-to-optical movement). permanent movement of archived data from optical or tape volumes back to disk. permanent recall back to disk of indexes that have been migrated to optical or tape. permanent movement of Spool File Archive data that resides on disk to Common Server s Archive Storage Manager (ASM). This option is available for 5.4 and above, for report definitions and indexes that have already been migrated from Spool File Archive to Common Server using the migration utility program (QRLRMIG). (Detailed information about report definition and index migration from Spool File Archive to Common Server is available in a document entitled Migration Reference which can be found at the OnDemand support website at using "migration reference as search criteria.) Whereas the QRLRMIG migration utility program is designed specifically to migrate report definitions and indexes to Common Server (but leave the archived data itself in its existing location), this option of MMF complements the migration utility program by allowing you to also move the archived data itself into the Common Sever IFS directory structure. Possible source types The following source types are supported by MMF: Optical (The optical media can be any Spool File Archive media type, such as WORM, REWT, LANW, or LANR.) Tape Individual report definition name (to permanently recall archived indexes from optical or tape to disk or to move migrated Spool File Archive data on disk to *ASM for a specific report definition name) Updated April 26, 2012 Page 1 of 9

2 Possible target types The following target types are supported by MMF: Optical (Supported only if source is optical. Typically, the target optical is larger capacity or newer technology than the source optical. In this case, MMF allows multiple smallercapacity optical volumes to be combined onto a single larger-capacity optical volume. For example, you might combine multiple 3995 optical volumes onto a single larger-capacity 3996 or Plasmon UDO optical volume (or Plasmon non-udo optical volume).) Disk ASM (Supported only on 5.4 or above for Spool File Archive data on disk that has already had its report definitions and indexes migrated to Common Server and is to be moved to Common Server s storage management repository and managed by Common Server s Archive Storage Manager.) Supported source/target combinations The following combinations of source and target media are the only scenarios supported by MMF. No other combinations are allowed. Data on OPTICAL can be migrated to DISK, or to another OPTICAL volume Data on TAPE can be migrated to DISK An individual REPORT NAME can be migrated to DISK to permanently recall archived indexes from optical or tape to disk for a specific report definition name. This function does not move the report data; only the indexes. If desired, movement of the actual report data would be accomplished using one of the other source/target combinations listed above that moves archived data by entire optical or tape volume rather than by individual report name. An individual REPORT NAME can be migrated to ASM to permanently move diskresident Spool File Archive data that has already been migrated to Common Server. The data is moved from the Spool File Archive IFS architecture to the Common Server IFS architecture and subsequently managed by Common Server s Archive Storage Manager (ASM) process rather than Spool File Archive s Report Management Cycle (RMC) process. It is not necessary to move all occurrences of a report to disk before you start running MMF. Because MMF will only move those report occurrences that are on disk, it does not know or care that other data exists that is not on disk. You can use MMF to bring a subset of report occurrences back to disk, then use MMF again (with different parameters) to move that data to ASM control. Then, repeat that two step process as many times as you like to bring additional subsets of report occurrences back to disk, and then to ASM until all report occurrences have been migrated to ASM. Then, after MMF processing has been successfully completed for ALL Spool File Archive report definitions, the regularly-scheduled RMC processing is no longer required and should be replaced by regularly-scheduled ASM processing. Considering the combinations defined above, an OnDemand system that has completed the migration of report definitions and indexes from Spool File Archive to Common Server, and Updated April 26, 2012 Page 2 of 9

3 has the majority of archived data resident on optical might use MMF in two steps: Step 1 would use option 1 above with OPTICAL as the source and DISK as the target, then Step 2 would use option 4 above with individual REPORT NAME as the source and ASM as the target. Software prerequisites The following software prerequisites are required for MMF. OnDemand 5.3* (see below) or higher, Spool File Archive environment. The current MMF support is not designed to be used for data that has been archived directly into the OnDemand Common Server environment. It is important to note, however, that while MMF does not support data that has been stored directly into Common Server, if data has been migrated to Common Server from Spool File Archive, the actual Spool File Archive data remains in Spool File Archive s storage management architecture. MMF can move the Spool File Archive report data that has had its report definitions and indexes migrated to Common Server. To determine if your data is a candidate for use with MMF, consider the following: MMF can be used to migrate data if the data has been stored into OnDemand for iseries (i5/os) (5722-RD1) using OnDemand Spool File Archive commands or APIs, or images if the images have been stored using OnDemand AnyStore APIs or the Kofax Ascent Capture release script that interfaces with Spool File Archive and AnyStore. The easiest way to determine if MMF applies to your environment is to confirm that there is a Spool File Archive report definition defined for the data or images you wish to migrate. If the answer is YES, then the use of MMF is appropriate. Note that MMF does not apply for OnDemand Object Archive or Record Archive data. OnDemand PTFs applied. For 5.3, the required OnDemand PTF is SI24487 (or its superseding PTF). The required OnDemand PTF for 5.4 is SI24490 (or its superseding PTF). These PTFs provide the program call interface for OnDemand 5.3 and 5.4. MMF is provided in the base code for 6.1 and above, using the command interface. NOTE: Support for target media of *ASM is available for 5.4 and above only, using the program call interface for 5.4 and the MGRMEDRDAR command interface for 6.1. The 6.1 PTFs for *ASM support are SI32076, SI32112, SI32587, and SI32588 (or their superseding PTFs). The 5.4 PTFs for *ASM support are SI31879, SI31880, SI31881, and SI32604 (or their superseding PTFs). Allowing MMF to continue after an error occurs With PTF SI45365 (for version 5.4), SI45366 (for 6.1), or SI45350 (for 7.1) or its superseding PTF applied, MMF can log an error and continue processing, rather than halting if an error occurs. A data area named QRLCSFAMMF can be created in library QTEMP (created with your choice of type, length, initial value, and description). The existence of this data area will cause MMF to bypass errors and continue processing. Since the data area must be in QTEMP, it only affects the current MMF process or others run from the same job if you Updated April 26, 2012 Page 3 of 9

4 are running MMF interactively. If you prefer to run MMF in batch, you must create a simple CL program that contains two lines. The first line would contain the Create Data Area (CRTDTAARA) command and the second line would contain the Migrate Media (MGRMEDRDAR) command (for version 6.1 or 7.1) or the QRLCSFAMMF program call (for version 5.4). Program call format (OnDemand 5.3 and 5.4) The following command shows the MMF program call format. This method to invoke MMF should be used for OnDemand 5.3 and 5.4. Note that the last two parameters (policyname and instancename) are only available on 5.4 for use with target parameter value of *ASM. CALL QRDARS/QRLCSFAMMF PARM(source sourcetype target instancename policyname) Command format (OnDemand 6.1 and above) The following command shows the MMF command format. This method to invoke MMF should be used for OnDemand 6.1 and above. Note that the last two parameters (policyname and instancename) are only available for use with target parameter value of *ASM. MGRMEDRDAR SRC(source) SRCTYPE(sourceType) TGT(target) POLICY(policyName) INSTANCE(instanceName) Program parameters The following required parameters are available for MMF. 1. Source optical or tape volume name, or report name Required (generic report names and report group names not permitted for report name) 2. Source type - *OPTICAL, *TAPE, or *REPORT Required 3. Target optical volume name, *DISK, or *ASM Required 4. Instance Common Server instance name Required if Target is *ASM 5. Policy Common Server migration policy name Required if Target is *ASM Examples The following program calls and commands are examples of different uses of MMF. Example 1: Permanently move an entire optical volume s contents to a different optical volume Program call interface for 5.3 and 5.4 only: CALL QRDARS/QRLCSFAMMF PARM(OPTVOL01 *OPTICAL NEWOPTVOL01) MGRMEDRDAR SRC(OPTVOL01) SRCTYPE(*OPTICAL) TGT(NEWOPTVOL01) Updated April 26, 2012 Page 4 of 9

5 Example 2: Permanently retrieve an entire optical volume s contents back to disk Program call interface for 5.3 and 5.4 only: CALL QRDARS/QRLCSFAMMF PARM(OPTVOL01 *OPTICAL *DISK) MGRMEDRDAR SRC(OPTVOL01) SRCTYPE(*OPTICAL) TGT(*DISK) Example 3: Permanently retrieve an entire tape volume s contents back to disk Program call interface for 5.3 and 5.4 only: CALL QRDARS/QRLCSFAMMF PARM(TAPVOL01 *TAPE *DISK) MGRMEDRDAR SRC(TAPVOL01) SRCTYPE(*TAPE) TGT(*DISK) Example 4: Permanently retrieve archived indexes (from optical or tape) back to disk (for a specific report definition name) Program call interface for 5.3 and 5.4 only: CALL QRDARS/QRLCSFAMMF PARM(CHECKSTMTS *REPORT *DISK) MGRMEDRDAR SRC(CHECKSTMTS) SRCTYPE(*REPORT) TGT(*DISK) Example 5: Permanently move data on disk to Common Server s ASM (for a specific report definition name) Program call interface for 5.4 only: CALL QRDARS/QRLCSFAMMF PARM(CHECKSTMTS *REPORT *ASM QUSROND LONGTERM) MGRMEDRDAR SRC(CHECKSTMTS) SRCTYPE(*REPORT) TGT(*ASM) POLICY(LONGTERM) INSTANCE(QUSROND) MMF Messages MMF does not send any messages upon successful completion. It simply reports errors or informational messages if any are detected. For example: If there are no multi-volume files (which are files that start on one volume and end on another volume), the joblog will contain the message NO MULTIVOLUME FILES. If there are no files to migrate, for example, if the source volume specified has already been migrated, the joblog will contain the message NO FILES TO PROCESS. If the target volume becomes full during an optical to optical migration, the joblog will contain the message TARGET OUT OF SPACE. To complete migration of the source Updated April 26, 2012 Page 5 of 9

6 volume, simply run MMF again, specifying the same source volume and a different target volume. MMF will resume migration at the point where the previous MMF job ended. If an incorrect volume name is specified, the message ERROR - CHECK JOBLOG. will be issued and the joblog will contain Primary volume xxxxxxxx not found. If the source volume cannot be mounted, the message ERROR - CHECK JOBLOG. will be issued and the joblog will contain messages such as Optical volume OPTVOL01 not found., MOUNT REQUESTED FOR VOLUME-OPTVOL01 and SOURCE OPEN FAILED. Note that for an object that spans volumes, these messages will be issued if either of the source volumes cannot be mounted. If an incorrect value is specified for source type, the message PARAMETER 2 SOURCETYPE MUST BE *OPTICAL, *TAPE, OR *REPORT. will be sent. When indexes are migrated from optical to disk, the standard recall message is issued, The recall of ' ' to directory 'MMFCHKS2RX' is complete. The report is now available for viewing or printing. The following messages apply to the *ASM option of MMF: If the instance does not exist, or if the application group does not exist, the message OND2049 Application group not found. will be sent. If the migration policy does not exist in the named instance, the message INSTANCE- ONDMIGR, POLICY-MY_POLICY NOT FOUND will be sent. If the objects have already been migrated, or if there are no objects to migrate, the message NO FILES TO PROCESS. will be sent. MMF Report A report listing media migration action taken is generated when MMF runs. The file name is QPRLCSFA1 for 5.4 and 6.1 and QPRLCSFA for 7.1. The user data is SFAMMF. The spooled file is created in QRDARS400 output queue in library QRDARS. Sample reports are shown below. SOURCE: OPTVOL03 SOURCE TYPE: *OPTICAL COPY TYPE: *ALL TARGET: OPTVOL07 INSTANCE: *NONE CHECKSTMTS OPTVOL03 OPTVOL07 REPORT CHECKSTMTS OPTVOL03 OPTVOL07 REPORT CHECKSTMTS OPTVOL03 OPTVOL07 REPORT CHECKSTMTS OPTVOL03 OPTVOL07 REPORT CHECKSTMTS OPTVOL03 OPTVOL07 REPORT CHECKSTMTS OPTVOL03 OPTVOL07 REPORT Optical to Optical Updated April 26, 2012 Page 6 of 9

7 SOURCE: OPTVOL02 SOURCE TYPE: *OPTICAL COPY TYPE: *ALL TARGET: *DISK INSTANCE: *NONE CHECKSTMTS OPTVOL02 *DISK REPORT CHECKSTMTS OPTVOL02 *DISK REPORT CHECKSTMTS OPTVOL02 *DISK REPORT CHECKSTMTS OPTVOL02 *DISK REPORT CHECKSTMTS OPTVOL02 *DISK REPORT CHECKSTMTS OPTVOL02 *DISK REPORT Optical to Disk SOURCE: OPTVOL03 SOURCE TYPE: *OPTICAL COPY TYPE: *ALL TARGET: *DISK INSTANCE: *NONE APCHECKS OPTVOL01 *DISK REPORT APCHECKS OPTVOL01 *DISK INDEX APCHECKS OPTVOL01 *DISK REPORT APCHECKS OPTVOL01 *DISK INDEX APCHECKS OPTVOL01 *DISK REPORT APCHECKS OPTVOL01 *DISK INDEX Optical to Disk, Data & Indexes SOURCE: MMFJOBLOG1 SOURCE TYPE: *REPORT COPY TYPE: *INDEXONLY TARGET: *DISK INSTANCE: *NONE MMFJOBLOG *OPTICAL *DISK INDEX MMFJOBLOG *OPTICAL *DISK INDEX MMFJOBLOG *OPTICAL *DISK INDEX MMFJOBLOG *OPTICAL *DISK INDEX MMFJOBLOG *OPTICAL *DISK INDEX MMFJOBLOG *OPTICAL *DISK INDEX Optical to Disk, Indexes only SOURCE: MMF002 SOURCE TYPE: *TAPE COPY TYPE: *ALL TARGET: *DISK INSTANCE: *NONE Updated April 26, 2012 Page 7 of 9

8 MMFCHKS1RX *TAPE *DISK REPORT MMFCHKS1RX *TAPE *DISK REPORT MMFCHKS1RX *TAPE *DISK REPORT MMFCHKS1RX *TAPE *DISK REPORT MMFCHKS1RX *TAPE *DISK REPORT MMFCHKS1RX *TAPE *DISK REPORT Tape to Disk 5722-RD1 V5R4M SOURCE: INVNEW1 SOURCE TYPE: *REPORT COPY TYPE: *ALL TARGET: *ASM INSTANCE: ONDMIGR7 POLICY: RDARSTEST INVNEW *DISK *ASM REPORT Disk to ASM Ending the MMF job You can end the MMF job while it is running, however it must be ended in a CONTROLLED manner to prevent unexpected results. To issue a controlled end to the MMF job, you can either issue a command similar to the one shown below OR use option 4 and then press F4 to prompt from the Work with Active Jobs (WRKACTJOB) screen OR use another i5/os jobrelated panel. In all cases, you must specify a delay time of 500 seconds to be sure that intermediate MMF processes are not interrupted before the job is ended. In most cases, the job will end in less than 500 seconds. Before moving any object, the program checks to see if a controlled end has been issued. The job will end before starting movement of the next object if it detects that the controlled end has been issued. ENDJOB JOB(jobnum/user/jobname) OPTION(*CNTRLD) DELAY(500) where jobnum/user/jobname are the job attributes of the MMF job. Notes MMF first checks to see if an object spans multiple volumes, then migrates that object, putting the multiple pieces back together into one object on the target media. After migrating data to disk, you could then use the Spool File Archive Report Management Cycle (RMC) to migrate the data back to optical. This might be the case if your new 3996 can not attach to your old AS/400 and your old 3995 can not attach to your new i5 system. You could migrate all archived data back to disk using MMF, upgrade to your new i5 system and new 3996, and then use RMC to migrate all archived data back to optical. When migrating from tape to disk, it is recommended that data area QRLCTAPE be created in library QRDARS. The value of QRLCTAPE should be set to *LEAVE. This will prevent OnDemand from unloading the tape after each retrieval. CRTDTAARA DTAARA(QRDARS/QRLCTAPE) TYPE(*CHAR) LEN(7) VALUE(*LEAVE) Updated April 26, 2012 Page 8 of 9

9 When using the *ASM option of MMF, you can specify a different migration policy from that specified in the OnDemand application group definition. If you do this, be aware that the data objects and index objects are now being managed separately, which could mean different media and even a different life if an expire level is used on one or both migration policies. MMF does not require the system to be in a restricted state. MMF can be run at any time, except while RMC is running, because RMC might delete objects that MMF is attempting to move. Updated April 26, 2012 Page 9 of 9