Built-in number for MATMATR1 is 92.
MATMATR1 (
          materialization      : address
          machine_attributes   : address (of just a selector value)
)

Selection

Attribute

Value

Description (Ref #1.)

Hex 0004

Machine serial identification

The machine serial identification that is materialized is an 8-byte character field that contains the unique physical machine identifier. This identifier is the same for all partitions of a physical machine. (Ref #2.)

Hex 0100

Time-of-day clock (local time)

The time-of-day clock option is used to return the time-of-day clock as the local time for the system. The MATMDATA or MATTODAT instruction can be used to return the time-of-day clock as the Coordinated Universal TIme (UTC) for the system. See Standard Time Format for additional information on the time-of-day clock.

The maximum unsigned binary value that the time of day clock can be modified to contain is hex EFFFFFFFFFFFFFFF. (Ref #3.)

Hex 0101

Time-of-day clock with clock-offset

In addition to returning the system time-of-day (TOD) clock (as defined for selection value hex 0100 described previously), the time-of-day clock with clock-offset option will also return a clock-offset which can be used to convert clocks from different partitions (on a partitioned system) to values referencing the common hardware clock used by all partitions on the same system. This enables users/administrators of a partitioned system to analyze and compare events taking place in different partitions. See Standard Time Format for additional information on the time-of-day clock.

The clock-offset is defined as the difference between the time-of-day clock for the current partition and the value of the hardware clock counter.

The materialize format of the time-of-day clock with clock-offset is as follows:

(Ref #4.)

Hex 0104

Primary initial process definition template

The primary initial process definition template is used by the machine to perform an initial program load.

No check is made and no exception is signaled if the values in the template are invalid; however, the next initial program load will not be successful. (Ref #5.)

Hex 0108

Machine initialization status record

The MISR (machine initialization status record) is used to report the status of the machine. The status is initially collected at IPL and then updated as system status changes.

The materialize format of the MISR is as follows:

Restart IMPL indicates that the machine performed an IMPL without powering down the machine.

Manual power on indicates the power switch on the operation panel was pressed to power the system on.

Timed power on indicates the system was powered on using the system value specified by the customer. This option will only be honored when the timed power on function is enabled.

Remote power on indicates the system was powered on by a phone call placed by the customer. This option will only be honored when the Remote power on function is enabled.

Auto-power restart indicates the system was automatically powered on after a utility failure occurred and power was restored. This option will only be honored when the Auto-power restart function is enabled.

UPS battery low indicates that a UPS battery is installed on the system and the battery is low.

UPS bypass active indicates that the UPS has been bypassed. If a utility power failure occurs, the UPS will not supply power.

UPS power failed indicates that a utility failure has occurred and the system is currently running on battery power.

UPS installed indicates that an Uninterrupted Power Supply is installed on the system and is available for use should the power fail.

Operation panel battery failure indicates the battery in the operation panel has failed and the system will not be able to determine the correct time and date upon the next IMPL. An approximate time and date will be given to the customer for verification.

Operation panel self test failed indicates the operation panel is possibly bad and some function concerning the operation panel may not work correctly.

Console status indicates whether the selected console is functioning normally or is inoperative.

Console state indicates whether the selected console is ready to be used.

Primary console status is set when the customer selected primary console is being used as the system console.

ASCII console status is set when a ASCII console is being used as the system console.

Termination status indicates how the previous IMPL was terminated.

The duplicate user profile is valid only for AIPL and indicates if a user profile that is the same as the AIPL user profile to be created already exists in the machine context. The machine in this instance does not create the user profile for AIPL but rather uses the one located with the same name.

Damaged AIPL user profile indicates if the currently existing user profile was detected as damaged and a new user profile was created as specified in the AIPL user profile creation template.

Damaged machine context indicates if damage was detected in the machine context when an attempt was made to locate the duplicate user profile or to insert addressability to a newly created user profile. In either case, all current addressability is removed from the machine context, the new AIPL user profile is created, its addressability is inserted into the machine context, and the AIPL continues.

The object recovery list status field indicates that the status is complete unless one of the following conditions is true:

• The recovery list was lost.

• More objects were to be placed in the list but there was insufficient space.

The recovery phase completion field indicates that the status is complete unless one of the following conditions occurs:

• An object to be recovered and/or inserted into the object recovery list no longer exists.

• The objects to be recovered could not be determined due to loss of internal machine indicators that specified which objects were in use at machine termination.

The most recent machine termination field is set to binary 0 unless all objects were not ensured at the most recent machine termination.

The last MISR reset field is set to binary 0 if all objects were ensured at every machine termination since the MISR was last reset (to binary 0).

IPL mode indicates which mode DST and the operating system will be IPLed. Either both will be attended or both will be unattended.

Service processor power on indicates if this is the first time the service processor card has been powered on.

MISR damage indicates if the machine detected that the MISR was damaged and its contents have to be reset to the default system values.

Auto key mode indicates if the key mode was set to auto on the operation panel on the most recent IMPL.

Normal key mode indicates if the key mode was set to normal on the operation panel on the most recent IMPL.

Manual key mode indicates if the key mode was set to manual on the operation panel on the most recent IMPL.

Secure key mode indicates if the key mode was set to secure on the operation panel on the most recent IMPL.

Tower two present on 9404 system unit indicates if the system has a second tower when the system is a 9404 system unit.

Battery status for tower one on 9404 system unit indicates if a UPS battery is installed on the first tower of a 9404 system unit, the battery is low.

Battery status for tower two on 9404 system unit indicates if a UPS battery is installed on the second tower of a 9404 system unit, the battery is low.

Termination due to utility power failure and user specified delay time exceeded indicates the last termination of the system was due to a utility power failure and the system value specified by the delay time had elapsed so the system was terminated.

Termination due to utility power failure and battery low indicates the last termination of the system was due to a utility power failure and while running on battery power the voltage dropped below a level to continue to power the system so the system was terminated.

Termination due to forced microcode completion indicates that the system went down by the user selecting power down from DST or the delayed power off switch was pressed on the operation panel.

Auto power restart disabled due to a utility failure indicates the microcode disabled the auto power restart option when a condition was detected that would prevent the auto power restart from functioning properly.

Reset utility power bits indicates that the power bits should be reset. This bit is only looked at when modifying the MISR.

Spread the operating system indicates to spread the operating system on the next install instead of overlaying the existing objects. This bit is set to spread after a new DASD has been added.

Install from disk/tape indicates when performing an install to use the initial install program off of disk or to load the initial install program off of tape.

Primary/alternate process definition template indicates on IPL to initiate the initial process using the primary or the alternate process definition template.

Time/Date source informs the operating system if the machine was able to determine the correct time/date or if it was forced to use the default time/date.

Install type is set to indicate whether an IPL or install was performed and if an install was performed, what type of install occurred.

The number of damaged main storage transfer blocks field indicates the number of main storage transfer blocks that were detected as damaged by the machine during IMPL.

The national language feature is the language feature used on the system.

The number of entries in the object recovery list field indicates how many objects are listed in the space located by the address of object recovery list field.

The tape sequence number is set by the machine to allow the operating system to perform their install.

The tape volume number is set by the machine to allow the operating system to perform their install.

The address of object recovery list field contains a space pointer to the list of the potentially damaged objects that were identified during machine initialization. The number of such objects is indicated by the number of entries in the object recovery list field.

The process control space created as a result of IPL or AIPL is identified by a system pointer returned in this field.

The queue space object pointer addresses the queue space object that was implicitly created by the machine for use by the initial process. This is created for both an IPL or an AIPL. During IPL or AIPL processing, before the queue space is created by the machine, the machine will attempt to destroy the queue space addressed by the MISR (this will be the queue space used on the previous IPL or AIPL). If the destroy fails (the MI user may have destroyed it sometime in the previous IPL), no error is reported and the IPL or AIPL processing continues with the creation of the new queue space. The queue space is a permanent object, owned by the user profile used to initiate the initial process and is not addressed by a context.

The automatic main storage dump IPL occurred field indicates if an automatic IPL was started after a main storage dump occurred. If this field is set to binary 1, the dump was automatically copied to auxiliary storage before the IPL.

The power failure (CPM continuous powered mainstore) recovery field indicates if a CPM recovery was attempted and if it was successfully completed. This field is reset on the next IPL.

Require full main storage dump copy indicates whether or not the system is permitted to copy a subset of the main storage dump. Prefer full main storage dump copy indicates the type of main store dump copy that is preferred. If require full main storage dump copy is set to binary 1, the system is not permitted to copy a subset of the main storage dump and the value of prefer full main storage dump is ignored. If require full main storage dump copy and prefer full main storage dump copy have not been previously set, a default value of binary 0 is used.

Table 3. Main storage dump copy

The automatic main storage dump IPL requested field indicates if an automatic IPL is requested after a main storage dump occurs. If this field is set to binary 1, the dump is automatically copied to auxiliary storage before the IPL.

The main storage dump data -- timestamp and SRC field contains the data associated with the most recent main storage dump.

SRC words 1 through 9 are hexadecimal data. Extended SRC word 1 is EBCDIC character data, which supercedes SRC word 1 on hardware that supports extended SRC data for word 1. If the hardware does not support extended SRC data for word 1, this field is set to the value of the SRC word 1 field followed by blanks.

The service tools national language feature is the language feature used on all the service tools screens.

The start of IPL timestamp field indicates approximately the start of the storage management recovery IPL step. See Standard Time Format for additional information on the format of the timestamp.

The optical volume ID and optical volume sequence fields identify the optical media in use when control was transferred to the operating system.

The Licensed Internal Code MRI level field is used to indicate if the MRI level is at the current release level or at a post-release level.

The Licensed Internal Code PTF install field is used to indicate if the current install was initiated by the PTF install process or by the normal install methods.

The load/dump tape device information is information needed to build a Logical Unit Description and Controller Description object for the device used to install the operating system.

The recovery object list identifies objects that required some activity performed on the object(s) during IPL. The list is located by the recovery object list pointer.

Each entry in the list has the following general format:

All objects-Any damage detected during IPL is reported in the general status information. If this damage is detected as a result of special processing performed during directory rebuild, it is indicated in the IPL detected damage field. A journal synchronization failure indicates the designated object was not made current with respect to the journal. Subsequent attempts to apply journal changes from the journal to this object will not be allowed.

No journal synchronization operations on behalf of journaled objects will be attempted during IPL if the journal port is in standby mode. The implicitly journaled object field indicates whether or not the object has been selected to be automatically journaled by the system.

Commit block-All commit blocks that were attached to an active process during the previous IPL are interrogated at the following IPL. The system attempts to decommit any uncommitted changes referenced through these commit blocks. The results of this attempted decommit is reported in the status field. The system also returns the journal entry sequence number of the start commit journal entry (hex 0500) last created for this commit block if there were any uncommitted changes. If the number is not returned, a value of binary 0 is returned.

Data space-If object damage was detected during IPL, the object is marked as damaged, damage is indicated in the object status field, and an event is signaled. In this case, the highest ordinal entry number is 0. In certain situations, the data space indexes over the data space become detached and therefore must be re-created. If the object is not damaged, the data space is usable and the highest ordinal entry number is set. The ordinal entry number of last entry indicates the last entry in the data space. Updates are not guaranteed. Updates may be out of sequence or partially applied and must be verified by the user for correctness. The user specified subtype is provided to allow for subtype specific logic.

Data space index-If object damage was detected during IPL, the object is marked as damaged, damage is indicated in the object status field, and an event is signaled. If the object was invalidated because changes were made in a data space addressed by the data space index, the data space index is included in the list and marked as invalidated. The ASP number of the data space index is indicated in the list. The associated data space is also included elsewhere in the object recovery list. Only damaged or invalidated data space indexes are included in the list. The user specified subtype is provided to allow for subtype specific logic.

Journal port-Each journal port in the system is interrogated at IPL. The status field contains the result of this checking and also the result of the attempt to synchronize the objects (if necessary) being journaled through the indicated journal port. A default journal port is specified when created, and indicates the port is to be used by the machine in implicitly journaling objects. If the attached journal space is no longer supported as a deposit target for a new release, the need to create and attach a new journal space will be indicated. The system also returns the number of journal spaces attached to the journal port after IPL is complete as well as the number of explicitly journaled objects.

Journal space-Each journal space that was attached to a journal port or used by the system to synchronize an object which was being journaled at the time of the previous machine termination is interrogated during IPL. The status field reports the results of this interrogation and synchronization use. Journal spaces are referenced by the object recovery list if this IPL was preceded by an abnormal failure, some unexpected condition was discovered during the IPL, or the journal space is a default journal space. The cloaking status of each journal space attached to a remote journal will be reported. The last journal sequence number on the journal space is returned. If the journal space is damaged, this field will contain zeroes.

Space objects with a subtype of hex A0, queue objects, and byte stream file objects - if journaled, and the IPL processing is successful such that the object ends up completely synchronized with the journal, an entry for the object will appear. Unlike data spaces, data space indexes, journal ports, and journal spaces, neither queues nor space objects, when journaled, fill in the object specific status field with additional object-unique information regarding the outcome of the IPL. Instead, the object specific status field will contain hex zeroes. (Ref #6.)

Hex 0118

Uninterruptible power supply delay time and calculated delay time.

Note: The UPS delay time is meaningful only if a UPS is installed.

The format of the template for the uninterruptible power supply delay time (including the 8-byte prefix) is as follows:

Hex 012C

Vital product data

The VPD (vital product data) is a template that contains information for memory card VPD, processor VPD, Columbia/Colomis VPD, central electronic complex (CEC) VPD and the panel VPD. The VPD information that is materialized is the same for all partitions of a physical machine.

On a logically partitioned system, this instruction materializes only the hardware resources known to the partition in which it is issued.

The materialize format of the VPD (Including the 8-byte prefix) is as follows:

The system VPD location information is used to determine where each of the separate VPD sections start relative to the beginning of the VPD materialization template.

The usable memory installed field contains the amount of memory (in megabytes) which the system recognizes as being valid. It is strongly recommended that the total usable memory installed value be used instead of usable memory installed. If the amount of usable memory is larger than 32,767 megabytes, this field will contain 32,767 megabytes while total usable memory installed will contain the correct (larger) value.

The total usable memory installed field contains the amount of memory (in megabytes) which the system recognizes as being valid.

The minimum memory required field contains the amount of memory (in megabytes) which is required for the system to run at optimum performance. It is strongly recommended that the minimum required memory value be used instead of minimum memory required. If the amount of memory required for the system to run at optimum performance is larger than 32,767 megabytes, this field will contain 32,767 megabytes while minimum required memory will contain the correct (larger) value.

The minimum required memory field contains the amount of memory (in megabytes) which is required for the system to run at optimum performance.

The remainder of the memory VPD is an array of 16, 64-byte entries which contain specific information about each memory card installed on the system. The memory card status field should be interpreted in the following way:

00 = Memory card usable, no failures

01 = Memory card usable, but has failures

10 = Memory card is not installed

11 = Memory card is not usable due to critical failure

The memory card size is a two byte field which will contain the number of megabytes of main store this card represents.

The number of CCINs field for this card contains a count of the number of CCINs which were found for this card. This number should be used to determine how many CCIN entries follow in the array of CCINs for this card field. This is a 32-byte field which is divided into 8, 4-byte entries. Each entry contains a CCIN number for this memory card.

The processor VPD is an array of 16 entries, each 80 bytes in length. Each entry corresponds to a processor card. To determine the status of a processor card, the processor card status field should be interpreted in the following way:

00 = Processor usable, no failures

01 = Processor usable, but has failures

10 = Processor is not installed

11 = Processor is not usable due to critical failure

The Colomis VPD is in an array of 2 entries, each 64 bytes in length. The first entry is reserved, the second entry contains information concerning the Colomis card.

For licensing purposes, processors are grouped according to performance characteristics. The processor group ID is the 4-character identifier of the processor group category to which this processor type is assigned. Possible values are: " P05", " P10", " P20", " P30", and " P40".

The CEC VPD system type extension is a 1-byte field which provides information on system packaging. The field is bit position dependent.

1nnn nnnn = Server

The CEC VPD system processor feature is an identifier which represents a unique combination of processor feature and interactive feature. This field contains an alphanumeric value.

The panel VPD may or may not be filled in on a particular system depending upon what type of panel is installed. To determine if the panel VPD information is valid, the panel VPD usable bit must be binary 1. If this field is binary 0, the panel VPD information is not valid.

The processor feature is the code, in EBCDIC, used for ordering processor hardware. Blanks (hex 40) are returned if the system does not have a processor feature.

The interactive feature is the code, in EBCDIC, used for ordering interactive hardware. Blanks (hex 40) are returned if the system does not have an interactive feature. (Ref #8.)

Hex 0130

Network attributes

The network attributes is a template that contains information concerning APPN network attributes.

The materialize format of the network attributes is as follows:

The following table shows the value of the default system name for the current partition. MATMATR option hex 01E0 can be used to materialize the current partition identifier and the firmware level.

Table 4. Default system name for current partition

The system name length is kept to determine how long the system name is. The default value for the length is eight.

The new system name is a tentative new value chosen for the machine system name. This value will become the machine system name at the next IPL. The initial value is null and the syntax rules are the same as those for the machine system name.

The new system name length is kept to determine how long the new system name is. The default value for the length is zero.

The local system network identification default is 'APPN' and the default local system network identification length is four.

The end node data compression field controls whether the machine will allow data compression when it's an end node. This value is used when the mode description is equal to *NETATR. If one of the values listed in the table below is not specified, then the value specified is equal to the maximum line speed that data should be compressed. Any configuration with a line speed slower than what is specified here will cause the data to be compressed. Valid values range from 1 bits-per-second through 2,147,483,647.

The intermediate node data compression field controls whether data compression will be requested by the machine when it's an intermediate node. This value is used when the mode description is equal to *NETATR. If one of the values listed in the table below is not specified, then the value specified is equal to the maximum line speed that data should be compressed. Any configuration with a line speed slower than what is specified here will cause the data to be compressed. Valid values range from 1 bits-per-second through 2,147,483,647.

The following table shows the default value of the local system control point name and default local location name for the current partition. MATMATR option hex 01E0 can be used to materialize the current partition identifier and the firmware level.

Table 5. Default local system control point name and local location name

The default local location name length is eight.

The maximum APPN LUDs on virtual APPN CDs default is 100. The maximum is 254.

The path switch timer - network priority traffic default is 1. The maximum is 10000. The unit of measure is minutes.

The path switch timer - high priority traffic default is 2. The maximum is 10000. The unit of measure is minutes.

The path switch timer - medium priority traffic default is 4. The maximum is 10000. The unit of measure is minutes.

The path switch timer - low priority traffic default is 8. The maximum is 10000. The unit of measure is minutes.

The mode name default is all blanks and the default mode length is eight.

The maximum number of intermediate sessions default is 200.

The maximum number of conversations per APPN LUD is 64.

The local system node type default is hex 01.

The route addition resistance default is 128.

All entries of the network server network IDs are defaulted to blanks with all entries of the network server network IDs lengths defaulting to zero.

All entries of the network server control point names are defaulted to blanks with all entries of the network server control point name lengths defaulting to zero.

The network attribute flags are used to communicate status of the network attributes between machine and the operating system.

• If the network attributes initialized field is equal to binary 1, this indicates the network attributes have been initialized to their default values. The default is binary zero.

• If the pending system name made current system name field is equal to binary 1, this indicates the pending system name has been made the current system name. The default is binary zero.

• If allow ANYNET support over any transport protocol flag is equal to binary 1, this indicates ANYNET support is enabled. The default is binary zero.

• If allow APPN traffic to use virtual APPN CDs flag is equal to binary 1, this indicates virtual APPN CDs can be used by APPN traffic. The default is binary zero.

• If allow HPR tower support to be used for APPN flag is equal to binary 1, this indicates that the SNA HPR tower support is enabled. The default is binary zero.

• If the local system performs as a branch extender node flag is equal to binary 1, this indicates the local system is performing as an end node in the APPN network, and as a network node to end nodes that it is serving. The default is binary 0. When the local system performs as a branch extender node flag is set to binary 1, the local system node type is set to hex 01.

Hex 0134

Date format

The date format is the format in which the date will be presented to the customer. The possible values are YMD, MDY, DMY where Y = Year, M = Month, D = Day and JUL = Julian.

The format of the template for date format is as follows:

Hex 0138

Leap year adjustment

The leap year adjustment is added to the leap year calculations to determine the year in which the leap should occur. The valid values are 0, 1, 2, 3.

The format of the template for leap year adjustment is as follows:

Hex 013C

Timed power on

The timed power on is the time and date, as Coordinated Universal Time (UTC), at which the system should automatically power on if it is not already powered on. If the physical machine is powered off, and the time and date at which a partition is automatically powered is set to occur before the time and date at which the physical machine is set to automatically power on (according to their respective time of day clocks), then the partition will be powered on when the physical machine is powered on.

The format of the template for timed power on is as follows:

Hex 0140

Timed power on enable/disable

The timed power on enable/disable allows the timed power on function to be queried to determine if the function is enabled or disabled.

The format of the template for timed power on enable/disable is as follows:

Hex 0144

Remote power on enable/disable

The remote power on enable/disable allows the remote power on function to be queried to determine if the function is enabled or disabled.

The format of the template for remote power on enable/disable is as follows:

Hex 0148

Auto power restart enable/disable

The auto power restart enable/disable allows the auto power restart function to be queried to determine if the function is enabled or disabled.

The format of the template for auto power restart enable/disable is as follows:

Hex 014C

Date separator

The date separator is used when the date is presented to the customer. The valid values are a slash(/), dash(-), period(.), comma(,) and a blank( ).

The format of the template for the date separator is as follows:

Hex 0151

System security indicators

The system security indicators return the current setting of the system security flags.

The format of the template for system security indicators is as follows:

The restrict change of service tool user profile passwords by operating system field indicates whether or not the operating system can change a service tool user profile password. If this field is set to binary 1, the password can only be changed from the Dedicated Service Tools (DST).

The restrict change of operating system security values field indicates whether or not the user can change operating system security related values.

The restrict adds to digital certificates store field indicates whether or not the user can use operating system functions to add digital certificates to a digital certificates store. (Ref #17.)

Hex 0161

Perform hardware checks on IPL

The perform hardware checks on IPL option retrieves the current setting that indicates if the system is skipping hardware checks on all physical machine IPLs. The IPL checks are performed only when the physical machine is IPLed.

The format of the template for perform hardware checks is as follows:

Hex 0164

Uninterruptible power supply type

Note: The UPS type is meaningful only if a UPS is installed.

The uninterruptible power supply type option allows the MI user to tell the machine how much of the system is powered by a UPS (ie, what type of UPS is installed). A full UPS will power all racks in the system. A limited UPS will have enough power to perform main store dump. A mini UPS will power the racks containing the CEC and the load source.

The format of the template for UPS Type is as follows:

Hex 0168

Panel status request

The panel status request option returns the current status of the operations panel.

The format of the template for panel status request is as follows :

The current IPL type is the state of the IPL type at the operations panel. Possible values are A, B, C, D.

UPS installed indicates that an Uninterrupted Power Supply is installed on the system and is available for use should the power fail.

UPS power failed indicates that a utility failure has occurred and the system is currently running on battery power.

UPS bypass active indicates that the UPS has been bypassed. If a utility power failure occurs, the UPS will not supply power.

UPS battery low indicates that a UPS battery is installed on the system and the battery is low.

Auto key mode indicates that the key mode is currently set to auto on the operation panel.

Normal key mode indicates that the key mode is currently set to normal on the operation panel.

Manual key mode indicates that the key mode is currently set to manual on the operation panel.

Secure key mode indicates that the key mode is currently set to secure on the operation panel.

The most recent IPL type is the type of IPL that was performed on the most recent IPL. Possible values are A, B, C, D. (Ref #20.)

Hex 016C

Extended machine initialization status record

The XMISR (extended machine initialization status record) is used to report the status of the machine.

The materialize format of the XMISR is as follows:

Hex 0170

Alternate initial process definition template

The alternate initial process definition template is used by the machine when performing an automatic install.

No check is made and no exception is signaled if the values in the template are invalid; however, the next automatic install will not be successful. (Ref #22.)

Hex 0178

Hardware storage protection enforcement state

The hardware storage protection (HSP) mechanism is always in effect. However, HSP is enforced for individual storage areas in two different ways. For some storage areas, HSP is always enforced. For others, HSP is enforced only when this machine attribute is active. Attempted use of any storage area in a manner inconsistent with its storage protection attributes will result in object domain or hardware storage protection violation  (hex 4401) exception when HSP is being enforced for that storage.

System objects for which HSP is always enforced are:

• programs (object type hex 02)
• modules (object type hex 03)
• any objects with type values greater than hex 20.

The format of the template for the hardware storage protection enforcement state option is as follows :

Hex 0180

Time separator

The time separator is used when the time is presented to the customer. The valid values are a colon(:), period(.), comma(,) and a blank( ).

The format of the template for the time separator is as follows:

Hex 0184

Software error logging

The software error logging machine attribute is used to allow the MI user to determine whether or not software error logging is active for the machine

The format of the template for software error logging is as follows:

Hex 0188

Machine task or secondary thread termination event control option

The machine task or secondary thread termination event option controls whether the machine will signal events when machine tasks or secondary threads terminate. The default, which is established every IPL, is to signal neither machine task nor secondary thread termination events.

There are different events associated with the termination of machine tasks and secondary threads. The machine task or secondary thread termination event option is a bit mask, with individual bits corresponding to machine tasks or secondary threads, and their associated events. If a bit is binary 1, the corresponding event will be signalled; if binary 0, it will not.

The format of the template for the machine task or secondary thread termination event option is as follows:

Hex 01A8

Service attributes

The service attributes is a template that contains system serviceability information.

The materialize format of the service attributes (including the 8-byte prefix) is as follows: