Previous Topic: Utility ComponentsNext Topic: Using the SyntaxSCAN Utility


Install the Utility

This section describes how to install the Parmlib SyntaxSCAN utility.

Remember that this utility only simulates CA MIM activation, so keep the following in mind:

To install the Parmlib SyntaxSCAN facility

  1. Customize the PROCSYN JCL PROC, rename it to MIMSCAN, and copy it to an appropriate proclib.

    Use the PROC symbolic override parameters to specify the MIMINIT and MIMCMNDS members to be scanned. You may reference the same members currently being used by currently active CA MIM tasks, or new members you have created.

    The MIMSYNCH member typically contains commands for other products (z/OS, JES2). Because CA MIM cannot accurately verify the syntax of commands for other products, the utility JCL PROC is coded to bypass scanning of the MIMSYNCH member. You will notice a SYNCH=NO parameter purposely coded in the JCL PROC of the utility; leave this as is.

    We recommend that:

  2. You need to APF-authorize the CA MIM load library prior to starting MIMSCAN.
  3. Start the MIMSCAN JCL PROC using the z/OS START command. You may run the SyntaxSCAN Utility alone or concurrently with other active CA MIM tasks. This is possible, because the MIMSYNTX program executes as simulated CA MIM task that really examines CA MIM parmlib members only for syntax errors.
  4. Monitor the execution of the utility. Usually, the JCL PROC of the utility terminates on its own after it has completed the scan of all CA MIM parmlib members. It typically takes less than one minute to complete the scan. After the utility ends, examine the syslog or joblog to determine if any syntax errors were found. If the utility ended with a U0040 abend, then syntax errors were found in the CA MIM parmlib. Examine the error message associated with the U0040 abend to determine which statement or command was in-error, correct the error, and rerun the CA MIM SyntaxSCAN Utility. Continue this process until the utility terminates normally. That is, without any U0040 abends.

    Note: Even if no U0040 abend occurs, there may be unrecognized commands in the commands member. Review the joblog or syslog for any error messages.