149 PATCH - Administration and Activation


Interrelationships	Parameter Description
Functions of the AMO	Error Messages and Advisories

Using the AMO PATCH, patch files (PF) which are on the hard disk (HD) can be added into a patch catalog, thus making them known to administration. PFs and Patch Catalog are located in:PDS: area of HD.

In addition, with the AMO PATCH the operator can delete patch files and their catalog entry and output information on patches in protocol form.

The group-id can be changed from all catalogued patches.

The AMO PATCH is used to activate or deactivate a software patch cataloged in the patch catalog on the hard disk. Adding into the patch catalog may be carried out when activating or deactivating the patch.

Patches can be activated and deactivated as MegaPatch or SinglePatch. Activating of many Patches will be faster with MegaPatch.

Patching is possible for:

•

Resident subsystems on central processors: (de)activation possible on the hard disk (in the PGLIB) as well as in the main memory.

There are three possibilities for activation:

•

In the main memory only

•

In the main memory and on the hard disk (in the PGLIB)

•

On hard disk only (in the PGLIB)

An activation on hard disk only is also possible for unloaded subsystems.

Patch activation can be carried out with securing (TEST=YES) or without securing (TEST=NO), with the following checks being carried out depending on the TEST parameter entered

Table 3

Patch Activation Tests

Consistency check

secured
(TEST = YES)

not secured
(TEST = NO)

The functions of the different tests are as follows:

•

Consistency test:
In case of a valid subsystem header, APS-ID and subsystem are checked against the subsystem header. If the dummy correction version entry is valid, values of the subsystem correction version between the dummy and the source correction version are allowed.

•

Address check:
A check is made to determine whether all patch addresses given in the patch file are located in the corresponding subsystems. This check is only carried out when (de)activating a patch.

One significant feature of patch technology is the possibility to return a system to its original status (as it was before initiation of the patch functions) at any time. The deactivation function can be used for this purpose. The "old data" stored in the patch file can be re-imported into the system software using this function. This "old data" must therefore always be available in the patch file, i.e. it is either supplied with the patch or is automatically read from the system software and stored in the patch file as part of the patch activation.

Table 4

Concept of Data Securing during Patch Activation

Data securing in patch file

Data securing in patch file

During (de)activation in the RAM of patches for resident subsystems on central processors, the checksum is always corrected in the JOTA. In addition, the activation status is entered in the patch catalog for every patch.

Structure of a patch file in E-file format


/*SOH2***********************************************************<
	PATCH# MRCAT# TR# DATE AUTHOR RESPONSIBLE CONTACT PROCESSOR APS-NAME SUBSYSTEM SRC-MODULE SRC-PROCEDURE PATCH AREA SUSY CODE AREA (B,E) DATE AREA (B,E) BASIC PATCH ACTIVATION RELATED PATCHES ERROR DESCRIPT. ERROR DESCRIPT. ERROR DESCRIPT.	: : : : : : : : : : : : : : : : : : : :	xxxxxx.xxx< xxxxxx< xxxxxxxx< xx.xx.xx< xxxxxxxxxxxxxxxxxxxx< xxxxxxxxxxxxxxxxxxxx< xxxxxxxxxxxxxxxxxxxx< xxxxx< xxxxxxxxxxxxx< xxxxxxxxxxxxxxxxxxxxxx< xxxxxxxxxxxxxxxxx< xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx< xxxxxxxxxxxxxxxxxxxxxx< xxxxxxxxxxxxxxxxxxxxxxx< xxxxxxxxxxxxxxxxxxxxxxx< xxxxxxxxxx< xxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx< xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx< xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx< xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx<
**EOH***********************************************************/<
	PRO PATCH:

	BYTE 0xxxx:0xxxx LENGTH 0xxxx
/* OLD DATA		= "reserved area (by blanks) for old data" */
/* NEW DATA		=*/
	BYTE 0xxxx:0xxxx = 0xx,0xx,0xx,0xx,0xx,0xx,0xx,.......

Restrictions and Notes

•

Only patches in E-file format are supported

•

Patch only in central subsystems in OMF286

•

No data cross-check

•

Interrupted (de)activation sequences are not recorded

${DocTitle}, ID: ${DocID}

© 02/2025 Mitel Networks Corporation. - All rights reserved.
Mitel and the Mitel logo are trademarks of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH&Co. KG.
All other trademarks herein are the property of their respective owners.