Step 6. Review Output of CTOFANCI and Perform Manual Conversion Tasks

The output of utility CTOFANCI (run in Step 4 above) consists of:

• Control-O rules created from information in the input libraries.
• Members that do not contain automation definitions and were copied from the input libraries to new locations.
• Reports describing input and output of the utility. Certain reports are mentioned briefly below. These reports are described in detail in Reports.

Perform the following steps to review the output of utility CTOFANCI:

1. Review the list of output rule libraries created or updated by utility CTOFANCI. This list is provided in report RPTFILES.
2. Examine the Control-O rules created by utility CTOFANCI. (These rules are located in the rule libraries identified in the RPTFILES report.) The input script used to create each Control-O rule is included as comments in the rule. Review the input script (in the comments) and verify that statements converted automatically by the utility conform to your site’s requirements.

   Review statements of the input scripts not converted by the utility (in the comment lines of the output rules), and specify Control-O rule definition parameters that provide the required functionality.

   To help identify rules that must be modified, you can sort report RPTRULES by output dataset name, member name, and rule number to prepare an output rule verification checklist.

   You can extract report lines that contain a warning indicator to identify rules that require extra attention. You can assign rule verification tasks according to the completion indicator (<---, <<--, <<<-, or <<<<, where rules with an <<<< indication need only be visually verified while other rules may require more manual work).

   For more information about Control-O rule definition parameters, see the rule parameters chapter in the Control-O User Guide.

   Note: If error message IOAE33E (Insufficient Storage) is displayed during an attempt to view a Rule table online, you can correct this problem by splitting the Rule table into multiple tables.

3. Review report RPTWARN and make sure that each warning in this report has been handled. Possible responses to warnings in this report are:
   • No response, if the default handling performed by the utility satisfies your site’s functional requirements.
   • Modify the output rules (for example, using specification of additional rule definition parameters in the rules) to implement functionality described by input script statements, keywords, or parameters that were not translated by the utility.
4. Rename output members that have duplicate names. Utility CTOFANCI assigns these members a prefix of @DUP (or an alternative prefix specified using utility parameter DUPPREF). The new names assigned to these members should conform to your site’s naming conventions.

   Note: Certain duplicate members may not be needed. Unnecessary duplicate members can be deleted at this stage, or, if necessary, combined with other members to preserve desired functionality. (For more information, see Similar and Duplicate Definitions.)