For example, if the telephone registration system is failing and students are unable to register for classes when they are scheduled, this is an emergency. However, if a routine application change or enhancement is going to fail to meet a desired deadline for whatever reason, this would not be considered an emergency. However, the retesting phase will likely be very quick, the checking of statistics dispensed with, and the modules copied into production as soon as feasibly possible. If no problems are encountered with the memo, an emergency installation usually takes less than an hour from the time the memo is received. Since most of our regions are reloaded each morning, changes to applications are normally installed on an overnight basis.
New applications require a little longer to process for installation into production.
Resources must be defined in the CICS tables, JCL may require modification, dynamic allocation tables must be updated, etc. During this demonstration the application programmer shows how the application works and that it performs its intended task. Other than the items mentioned, the same steps which are required to install a routine change to an application apply to a new installation as well. Monitoring CA-InterTest will be used to monitor any new or changed program after it is installed into production. This is done to protect the CICS region from storage violations or other errors which may not have been caught during testing.