Output

The content of each input member is analyzed to determine the language or automation product with which it is associated (for example, CA-AUTOMATE, CA-OPS, REXX program, or documentation member).

• Input members containing console automation definitions are used to create Control-O rules with similar functionality. Each rule is added to a specified output Rule table (PDS member). Depending on utility parameters, more than one Rule table may be created. Additionally, more than one rule with the same ON statement (that is, selection criteria) may be created.

  For information on conversion of specific keywords and parameters in the input scripts, see Conversion Details.

• Input members containing other information (for example, CLISTs, TSO REXX or documentation members) are copied to locations specified using parameters of the utility. Each of these members is copied to a separate member in an output library. A comment is added to the beginning of each member containing the input member name and the date and time the member was processed by utility CTOFANCI. For example:

  /* <--- SITE1.REXX(REXX1) 00/10/13 09:02                            */

  The name of each output dataset and member is determined by the name pattern specified for parameters OUTDSN and OUTMEMNAME (described in Output Parameters).

Note: Certain members in input libraries are neither translated nor copied into output libraries. Examples of such members are PDSMAN control members (for example $$$SPACE) and Control-O rules (if any) in the input libraries.