Manager REFRESH

The processing of the suspend file during a REFRESH consists of the following steps:

1. Preprocessing: The file is read and checked for errors (for example, syntax errors, I/O errors)
2. No errors occurred during preprocessing:
   1. Suspend requests are injected for all resources in the suspend file with the parameters defined in the file as well.
   2. All lines that have been processed are commented out using the line comment character in column 1.
      Note: If column 1 is not empty, the first character will be overwritten with the line comment character.
3. Errors occurred during "preprocessing":
   1. Error messages are written to the system log.
   2. Config REFRESH is canceled and can be retried later.
4. Resources defined in the suspend file are not part of the new or changed configuration:
   1. Informational messages are written to the system log.
   2. Non-existing resources are ignored; all lines with existing resources are processed as described in step 2.
5. If you want to force the REFRESH: use the INGAMS command ( see INGAMS INGAMS) or the MVS Modify command (see Starting, Stopping, and Maintaining the Automation Manager).
   For this purpose, a new parameter for both commands is introduced, which allows to specify the following:

   • NOSUSPEND: Ignore the whole suspend file
   • FORCESUSPEND: Ignore all erroneous lines in the suspend file

   Note:

   • The INGAMS REFRESH or MVS Modify command with FORCESUSPEND option or without any option will process the suspend file only if the configuration file has been changed as well. For example, if you have added, deleted, or modified a resources.
   • This functionality can also be used, if there are no errors in or with the suspend file. For example, you want to REFRESH the configuration and completely ignore the suspend file.