"... In PAGE 48: ... The resource type displayed with the name is link (LNK). Substitution Variables: The resource types that can be associated with each substitution variable shown in Table3 -1 on page 3-3 are defined as follows: 3-2 OS/400 Alerts Support V4R1 ... In PAGE 49: ...Table3... In PAGE 51: ... bulletmed Handle problems differently depending on the type of problem. Table3 -2 shows the relationship between the alert option (ALROPT) parameter in the message description and the alert status (ALRSTS) network attribute. In this figure, the messages defined as *DEFER have the log problem (LOGPRB) param- eter in the message description set to *YES; setting the LOGPRB parameter to *NO in a message causes all alerts for that message to be treated as *IMMED.... In PAGE 59: ... You can control the logging of alerts using the alert logging status (ALRLOGSTS) network attribute. Logging Alerts: Table3 -3 shows whether an alert is logged in the alert database, depending on: 1. The ALRLOGSTS network attribute (*ALL, *LOCAL, *RCV, or *NONE) 2.... In PAGE 60: ... the alert remains in the alert database. If the con- ditions shown in Table3 -3 indicate that the alert should not be logged, it is deleted from the alert database. If the conditions indicate that the alert should be logged, it remains in the alert database, but it is no longer displayed as a held alert.... In PAGE 71: ... Determining the Message ID: The message ID for a code point consists of the code point plus a 3-character prefix. Table3 -6 shows the message ID prefixes for the alert code points: For example, the message ID for failure cause X apos;1234 apos; is ALF1234. The code point for the detail qualifier data ID is only 2 hexadecimal digits.... In PAGE 72: ... For code point X apos;xxYx apos;, Y determines the number. Table3 -7 lists the number of qualifiers required by a code point with the given third digit. Substitution Text for Detailed Qualifiers: When you create a code point message that con- tains detailed qualifiers, you must specify where the qualifiers will be displayed.... In PAGE 72: ... To specify detailed qualifiers that appear on the same line as the code point text, you use substi- tution variables to define the placement of the qualifiers. Table3 -8 shows the substitution vari- able numbers that should be used for each qual- ifier. If the detailed qualifier placement is defined at the end of the code point text, you can omit the sub- stitution variable at the end of the text, and the system displays the detailed qualifier on the line following the code point text.... ..."

"... In PAGE 16: ...List of Tables Table3 -1: Slot States.... In PAGE 16: ...able 3-1: Slot States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Table3 -2: Communication Operations .... In PAGE 16: ...able 3-2: Communication Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Table3 -3: Making a Reservation.... In PAGE 16: ...able 3-3: Making a Reservation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Table3 -4: Canceling a Reservation.... In PAGE 16: ...able 3-4: Canceling a Reservation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Table3 -5: Joining .... In PAGE 52: ...schedule adapts to fluctuating demand in the network. Table3 -1 gives the eight slot states and their durations in the power schedule. The communication operations of the Supply and Demand algorithm primarily set slot states.... In PAGE 52: ... Partial flows support operations such as data aggregation, data compression, query dissemination, time synchronization, and other net- work protocols. Table3 -1: Slot States Slot State Name Stay in Schedule T Transmit until supply/demand or topology change R Receive until supply/demand or topology change I Idle until supply/demand or topology change CB Communication Broadcast until supply/demand or topology change RB Receive Broadcast until supply/demand or topology change TP Transmit Pending at most one cycle RP Receive Pending at most one cycle AA Adaptive Advertisement... In PAGE 53: ...4.3 State Diagram for FPS Protocol Table3 -2 contains all communication operations and the slot states in which they occur. Table 3-2: Communication Operations Operation Slot States Description TxData T transmit data message RxData R receive data message RadioOff I radio off TxAdv CB, AA transmit advertisement and time sync RxAdv RB, joining receive advertisement and time sync TxReq TP, T transmit reservation request RxReq RP, R receive reservation request TxConf RP, R transmit reservation confirmation RxConf TP, T receive reservation confirmation TxCanc T, R transmit cancel reservation RxCanc R, T receive cancel reservation TxCmd CB... In PAGE 53: ....4.3 State Diagram for FPS Protocol Table 3-2 contains all communication operations and the slot states in which they occur. Table3 -2: Communication Operations Operation Slot States Description TxData T transmit data message RxData R receive data message RadioOff I radio off TxAdv CB, AA transmit advertisement and time sync RxAdv RB, joining receive advertisement and time sync TxReq TP, T transmit reservation request RxReq RP, R receive reservation request TxConf RP, R transmit reservation confirmation RxConf TP, T receive reservation confirmation TxCanc T, R transmit cancel reservation RxCanc R, T receive cancel reservation TxCmd CB... In PAGE 54: ... The outputs depend on the bubble state and value of the inputs. Figure 3-7: FPS State Diagram RxCmd RB receive command message Table3 -2: Communication Operations Operation Slot States Description /incr /decr /decr /incr s*/ s+/ s_/ s+/ s+/ s_/ Rx Conf Rx Canc Rx Adv Tx Adv Tx Canc Tx Req Rx Req Tx Conf Demand Supply Radio Off Tx Data Rx Data Tx Cmd Rx... In PAGE 55: ... The input labels for slot states are omitted from the diagram so that it is easier to read. Table3 -2 provides slot state inputs. There are two output labels: 1.... In PAGE 56: ... If multiple requests are received, the parent accepts the first. Table3 -3 shows the communication operations that occur between two nodes when the child node makes a reservation with its parent. The protocol requires two cycles.... In PAGE 56: ... Then, during the reservation slot TP in the same cycle, Child sends TxReq. This is fol- Table3 -3: Making a Reservation Cycle Slot Parent Slot Child 1 CB TxAdv RB RxAdv 1RPRxReq TP TxReq TxConf RxConf 2 R RxData T TxData .... In PAGE 57: ... A parent can also cancel a reservation with a child node by sending TxCanc during the relevant R slot with the same effects. Table3 -4 shows the communication operations that occur between two nodes when the child node cancels a reservation with its parent. The protocol requires only one time slot, Cycle 2 Slot T, to accomplish.... In PAGE 57: ... The protocol requires only one time slot, Cycle 2 Slot T, to accomplish. Table3 -4: Canceling a Reservation Cycle Slot Parent Slot Child 1 R RxData T TxData 2 R RxCanc T TxCanc 2 I RadioOff I... In PAGE 58: ... In the common case, a node has already joined the network and knows who its parent is. Table3 -5 shows the interaction between two nodes as one (Child in this example) joins the network. The joining protocol requires at least two cycles.... In PAGE 63: ... Only coarse-grain synchronization on the order of milliseconds is required, due to the relatively large time slots. In the example from Table3 -5, Node 2 first synchronizes with Node 1 during RxAdv in Cycle 1. FPS allows for a variety of synchronization approaches, and we have implemented a few.... In PAGE 74: ... Cycle state is a modifier, so together they are simply referred to as slot state in the local schedule. A node can be in one of the 8 slot states as shown in Table3... ..."

"... In PAGE 29: ...1) character set. This character set is divided into alphabetic characters (letters), digits, graphic characters, the space (blank) character and formatting characters (for more information, see Table3 -2, Table 3-3, Table 3-4, and Table 3-5 in the CORBA 2.3 specification).... In PAGE 29: ...1) character set. This character set is divided into alphabetic characters (letters), digits, graphic characters, the space (blank) character and formatting characters (for more information, see Table 3-2, Table 3-3, Table3 -4, and Table 3-5 in the CORBA 2.3 specification).... In PAGE 31: ... The value of a space, alphabetic, digit, or graphical character literal is the numerical value of the character as defined in the ISO Latin-1 (8859.1) character set standard (See Table3 -2 on page 3-4, Table 3-3 on page 3-4, and Table 3-4 on page 3-5 in the CORBA 2.... In PAGE 31: ...ORBA 2.3 specification). The value of null is 0. The value of a formatting character literal is the numerical value of the character as defined in the ISO 646 standard (see Table3 -5 on page 3-6 in the CORBA 2.3 specification).... In PAGE 67: ...2.1 IDLscript Representation Table3 -1 lists the IDLscript identifiers that refer to basic OMG IDL types. 3.... In PAGE 89: ... If an exception is thrown during the execution of a deferred call, this exception will be thrown in the client side at the first access to a future object involved in this invocation. Table3 -3 summarizes the functionalities of future objects. 3.... In PAGE 100: ...ORBA.TypeCode binding type. All the OMG IDL type representations can be managed as IDLscript TypeCode objects. Table3 -4 enumerates TypeCode object functionalites. Table 3-4 The CORBA.... In PAGE 104: ... In fact, it is an IDLscript type that defines the standard methods supported by all CORBA object references. Table3 -6 presents the IDLscript reflection of the CORBA::Object operations. Each CORBA::Object operation is reflected by a CORBA.... In PAGE 105: ... However, scripts must use the POA when its advanced features are needed. The Table3 -7 presents the IDLscript reflection of the CORBA::ORB operations. Table 3-7 The Reflection of the CORBA::ORB Operations ORB Operation Reflected by June 2001 CORBA Scripting Language: The Global CORBA Object 3-41 object_to_string object_to_string string_to_object... ..."

"... In PAGE 55: ... and the functions of the required support system have been documented in detail t31; This study was done using many of the principles developed in [I] and [2]; The proposed automated medical record system has been called quot;The Family Systemtt. and it is this application which will be analyzed; Since the proposed system is moderately large, much use is made of tables during the exposition of the design process; FILES FOR THE FAMILY SYSTEN The Family System is envisaged to have 29 data files and several auxiliary index files [3]; The data files are summarized in Table3 -1: The summary provides An estimate of the size of the file: n; The number and total length of all fixed fields: af , Rf; The number and both average and maximum total length of ... In PAGE 57: ...fields; and the size: n(min, avg, max), an, Rn; The nests themselves are denoted using a hierarchical number in^ scheme: entity relation file. level I nest file, second and lowest level nest file: p, p;q, p;q;r The third file (Patient) has multiple record subtypes, containing optional and transient data; These files are denoted 3a and 3b; The length for various element types defined for the Family System is estimated as shown in Table3 -2; Groups of elements are taken in terms of multiple integer bytes; The table does not include any structural non-essential data elements; The estimates are based on data provided for the Family System [3], from the AANRS Study [2], and from statistics presented in [I]; The expected size of the files was verified by Dr; John Dervin of the Family Practice Center; and is shown in Table 3-3; Table 3-2 Lensth of Data Element Types Data-type V(min).,V(avg) ~(max) Reference Name Address Telephone Telephone Note Date Time Sex Flags Response Diglts (individual) 22 (business) 18 2 chars bits bit bits bytes bytes bgtes bytes bytes bytes [ : pit30 and ?:p;ll281 Hislll [2:p;99 and 2:vo1;2 CDB p;21] [3:p;81 I ~3:p;ai I ... In PAGE 57: ...fields; and the size: n(min, avg, max), an, Rn; The nests themselves are denoted using a hierarchical number in^ scheme: entity relation file. level I nest file, second and lowest level nest file: p, p;q, p;q;r The third file (Patient) has multiple record subtypes, containing optional and transient data; These files are denoted 3a and 3b; The length for various element types defined for the Family System is estimated as shown in Table 3-2; Groups of elements are taken in terms of multiple integer bytes; The table does not include any structural non-essential data elements; The estimates are based on data provided for the Family System [3], from the AANRS Study [2], and from statistics presented in [I]; The expected size of the files was verified by Dr; John Dervin of the Family Practice Center; and is shown in Table3 -3; Table 3-2 Lensth of Data Element Types Data-type V(min).,V(avg) ~(max) Reference Name Address Telephone Telephone Note Date Time Sex Flags Response Diglts (individual) 22 (business) 18 2 chars bits bit bits bytes bytes bgtes bytes bytes bytes [ : pit30 and ?:p;ll281 Hislll [2:p;99 and 2:vo1;2 CDB p;21] [3:p;81 I ~3:p;ai I ... In PAGE 59: ...The files presented by the Family System are organized to satisfy the perceived functional needs of the medical record applications; This means that all data attributes are assigned to specific files using conventional progra~ning design procedures; The files, however, exhibit semantic relationships among each other through the use of shared attribute domains; The files themselves are furthermore complex in the sense that they are not in first-normal-form; In order to present the data base model in a form which provides guidance to the design process, the files for the Family System will be normalized; In order tc derive the interrile rs~laLi.onships, the principal attributes of all files are listed alphabetically in Table3 -4; With each attribute the domain, the data type, and the file usage is indicated; Attributes which have a matching domain, but are named differently; are cornputstionally comparable, but ... In PAGE 63: ...A first-order normalization of the 32 Family System Files described in Table3 -1 extracts the nested structures and places them into distinct files; There are 25 nests and two auxiliary files so that the Family System in first-normal form comprises 57 files; In practice some of these nest files can be avoided by designating a fixed number of fields for the nest in the parent entity file as shown in Figure 2-2; The degree to which nests can be omitted depends on the efficiency of the file compression support; Prime candidates for denesting are the following files: 1;l Guarantors - small and low n(max) of repeating entries 4;1 Pap Smears - 11 11 11 II II II 11 4;2 Crug Allergies - quot; 11 11 II 11 11 II 10 ;0 Flowsheet - small flag and few entries 13;1 Day Sheet Patients - few records and high density 20;l Family member - small size of repeating field A sample calculation of the denesting tradeoff for the first of these files (1;1 ... In PAGE 68: ...The remaining files can now be reviewed for structural inter-relationships and redundancies; Linkage keys which have been identified in the 34 primary files are given as the ruling part for these files in Table3 -5; This table also indicates which of these files have a NULL dependent part (1;1, 5, 8, 9, lo), these files were apparently defined in [31 for their utility in providing a linkage, and are hence not an essential part of the data base model; There remain a number of files with identical ruling parts; These files represent different functional needs and were hence defined distinctly; In the model of the data base, however, these files are best combined; The original files are then represented ... In PAGE 69: ... medication code, date non.drugtEerapy, date floV sheet-type : gt; NUL date- date date date, problem-number date, problem-number, 3 code patient-number, aate; problem-number , test code patient-numbeF, date, problem-number , problem-note-number date, office date, office; patient-number - off ice office; patient-number * These files will be eliminated if denesting is carried out as lndlcated earller; In file 2; 1 (Family ember) the catenation of apos;family-number apos; and apos;family-member-number apos; forms the apos;~atient-number apos;, so that this file can also be represented as a segment dependent on the ruling part of apos;patient-number apos;; The new relations created in this manner are listed in Table3... In PAGE 74: ...role; Important linkage domains found in Table3 -4 are Patient name Patient number Provider name Office Family number Problem number Service code Therapy code Dollars Medication code Some redundancy is evident; In order to simplify updating, it may be desirable to define certain attributes as primary, and to update the redundant copies of these attributes asynchronously; Candidate attributes for such a division are the objective medical data as obtained during a patient visit; The primary relation for such data would be the Patient Visit file; The Problem List File; Flow-Sheets; Preventive Care records, etc; could be updated overnight; Redundancy for protection of data is maintained through the service files as the Transaction Log; Associations: An important primitive function for a data base is the ability to associate data from file with data from another file; Associations may be created dynamically through use of the Join operation, or may be bound permanently; A permanent association can contain unlimited dependent-part information; dynamic association only carries information derived from the joining ... In PAGE 78: ...transformed into a manipulatable model; This model was then inspected for function, redundancy; semantic relationships, and consistency; A number of transformations were performed to clarify and simplify the data base model; This model is now suitable for a performance-oriented design effort; Table 3-8 summarizes the transformations performed; The design of the Family System; as developed from an analysis of the service requirements, described 58 distinct files; The data base model now consists of 20 primary entity files (2 of these can be denested) 7 referenced entity files 4 lexicons 9 service files Rzlationships among the entity files are documented in Table3... In PAGE 80: ...hich is to support the Fa.m.i.1t.y System, several design techniques can be employed; These can be categorized as follows: File Organization Choices: pile, sequential, indexed-sequential, indexed, direct or ring; File Partitioning Choices: One record per tuple, or one record per segment; Use 01 apos; auxiliary access files; In practice all three choices will be employed; In order to establish a baseline; the nerf apos;ormance of a pile of unpartitioned records without auxiliary access files will be presented initially; Table 4-1 summarizes the basic relations and their parameters, as derived from the data presented in Table3 -1; Since all files are evaluated independently, the size of the ruling part has been added to the recordsize; The primary files summarized in Table 4-1 do not include the lexicons and referenced entity files; The space required for these is presented in Table 4-3 using the assumptions that they ... In PAGE 84: ...n aspect of information services to the Family System and as indicated in [ 1 :Ch;5; 1 I, the usage of the Family System for information purposes will depend on the quality of services to clinic, research and educational management; The load due to this latter type of usage can be expected to be considerably less and not coincide with times of high clinic activity; This aspect will hence not now be evaluated; The services that a.re to be provided are selected from [2:SeC;4C], and usage qualities are provided by [3:Ch;2] and Table3... In PAGE 104: ...T r log (n R/U) 1 (s+r+B/t) + 1/2 0/5 ~/t apos; F 2 Indexed-Sequential: An indexed-sequential file organization provides faster access through a tree search of key values [I:Ch;3;2;31; Its efficiency depends on a small number of updates per file; Some additional space, SI; is required; This space is a function of the fanout ratio, y, [I:Ch;3;3;1], blocking; and number of records; n, for a two-level (x=2) index; File 12;l only requires one level; The values for Rr depend on the size of the ruling part and are given in Table3 -7; T =s + (2 + Pov (1+1/2~ov)(r+B/t) ; Pov = o/(n+o) F T = ( R/B + 2 Pov (1-R/B) )(r+B/t) (two buffers are available) ... ..."

"... In PAGE 19: ...Mapping Predefined Size Specific Data Types Table3 -2 lists the DCE predefined size specific data types with their corresponding DCE IDL base types from which they are derived. The mapping to OMG IDL for these types is the mapping as defined for the DCE IDL base types they are derived from.... In PAGE 19: ... Unlike data of type char, which is subject to possible ASCII/EBCDIC conversion, data of the predefined international character types are guaranteed not to undergo any conversion during a DCE RPC. Table3 -3 shows the mapping for DCE IDL international character types to corresponding OMG IDL types. A bridge object implementation therefore requires that the underlying CORBA ORB has support for the particular code set.... In PAGE 30: ... The type of the array elements is mapped according to the data type mapping rules. Table3 -4 shows the mapping for DCE IDL fixed array bounds to corresponding OMG IDL array bounds. Thus the DCE IDL: /* DCE IDL */ long array_a[10][12]; long array_b[100.... In PAGE 31: ... Table3 -5 shows the mapping of fixed array bounds in DCE IDL varying arrays to the corresponding maximum size values that are required in OMG IDL for bounded sequences. Any parameter associated with either the last_is or length_is attributes and having the same direction attributes as the array itself, is not retained by the mapping process to OMG IDL, as the current length of a CORBA sequence can be obtained at run-time.... In PAGE 37: ....e, an exception can be raised by any operation of the interface. Mapping DCE System Exceptions The DCE system errors which are identical or closely match a CORBA standard CORBA V2.X Month Year 3-37 exception are mapped to that counterpart exception: the complete set is shown in Table3... ..."

"... In PAGE 48: ... The resource type displayed with the name is link (LNK). Substitution Variables: The resource types that can be associated with each substitution variable shown in Table3 -1 on page 3-4 are defined as follows: Line description This is the name of a line description created by a create line description command. See the Communications Configuration book for the create line description commands.... In PAGE 49: ... Second level resource This is the name of the physical resource that is associated with the failing resource and second closest to the system processor. The type of resource named by this variable depends on the type of subsystem as shown in Table3 -1 on page 3-4. Third level resource This is the name of the physical resource that is associated with the failing resource and third closest to the system processor.... In PAGE 49: ... Third level resource This is the name of the physical resource that is associated with the failing resource and third closest to the system processor. The type of resource named by this variable depends on the type of subsystem as shown in Table3 -1 on page 3-4. Fourth level resource This is the name of the physical resource that is associated with the failing resource and is the fourth closest to the system processor.... In PAGE 49: ... Fourth level resource This is the name of the physical resource that is associated with the failing resource and is the fourth closest to the system processor. The type of resource named by this variable depends on the type of subsystem as shown in Table3 -1 on page 3-4. Network interface description This is the name of a network interface description created by the Create Network Interface Description (CRTNWIISDN) command.... In PAGE 49: ... Refer to the ISDN Support book for more infor- mation. Note: See Table3 -5 on page 3-16 for a list of the resource type abbreviations. Alert Hierarchy: Only one number is defined for the resource name variable, but if this number is known by the system, a complete hierarchy, which includes an entry for each resource in the hier- archy, is built by the system, starting from the name of the failing resource up through the name of the system itself.... In PAGE 51: ... bulletmed Handle problems differently depending on the type of problem. Table3 -2 on page 3-6 shows the relationship between the alert option (ALROPT) parameter in the message description and the alert status (ALRSTS) network attribute. In this figure, the messages defined as *DEFER have the log problem (LOGPRB) parameter in the message description set to *YES; setting the LOGPRB parameter to *NO in a message causes all alerts for that message to be treated as *IMMED.... In PAGE 60: ... You can control the logging of alerts using the alert logging status (ALRLOGSTS) network attribute. Logging Alerts: Table3 -3 shows whether an alert is logged in the alert database, depending on: 1. The ALRLOGSTS network attribute (*ALL, *LOCAL, *RCV, or *NONE) 2.... In PAGE 60: ... When a held alert is successfully sent, the alert logging status network attribute controls whether the alert remains in the alert database. If the con- ditions shown in Table3 -3 indicate that the alert should not be logged, it is deleted from the alert database. If the conditions indicate that the alert should be logged, it remains in the alert database, but it is no longer displayed as a held alert.... In PAGE 72: ... Determining the Message ID: The message ID for a code point consists of the code point plus a 3-character prefix. Table3 -6 shows the message ID prefixes for the alert code points: For example, the message ID for failure cause X apos;1234 apos; is ALF1234. The code point for the detail qualifier data ID is only 2 hexadecimal digits.... In PAGE 73: ... For code point X apos;xxYx apos;, Y determines the number. Table3 -7 lists the number of qualifiers required by a code point with the given third digit. Substitution Text for Detailed Qualifiers: When you create a code point message that con- tains detailed qualifiers, you must specify where the qualifiers will be displayed.... In PAGE 73: ... To specify detailed qualifiers that appear on the same line as the code point text, you use substi- tution variables to define the placement of the qualifiers. Table3 -8 shows the substitution vari- able numbers that should be used for each qual- ifier. If the detailed qualifier placement is defined at the end of the code point text, you can omit the sub- stitution variable at the end of the text, and the system displays the detailed qualifier on the line following the code point text.... ..."

"... In PAGE 48: ... The resource type displayed with the name is link (LNK). Substitution Variables: The resource types that can be associated with each substitution variable shown in Table3 -1 on page 3-4 are defined as follows: Line description This is the name of a line description created by a create line description command. See the Communications Configuration book for the create line description commands.... In PAGE 49: ... Second level resource This is the name of the physical resource that is associated with the failing resource and second closest to the system processor. The type of resource named by this variable depends on the type of subsystem as shown in Table3 -1 on page 3-4. Third level resource This is the name of the physical resource that is associated with the failing resource and third closest to the system processor.... In PAGE 49: ... Third level resource This is the name of the physical resource that is associated with the failing resource and third closest to the system processor. The type of resource named by this variable depends on the type of subsystem as shown in Table3 -1 on page 3-4. Fourth level resource This is the name of the physical resource that is associated with the failing resource and is the fourth closest to the system processor.... In PAGE 49: ... Fourth level resource This is the name of the physical resource that is associated with the failing resource and is the fourth closest to the system processor. The type of resource named by this variable depends on the type of subsystem as shown in Table3 -1 on page 3-4. Network interface description This is the name of a network interface description created by the Create Network Interface Description (CRTNWIISDN) command.... In PAGE 49: ... Refer to the ISDN Support book for more infor- mation. Note: See Table3 -5 on page 3-16 for a list of the resource type abbreviations. Alert Hierarchy: Only one number is defined for the resource name variable, but if this number is known by the system, a complete hierarchy, which includes an entry for each resource in the hier- archy, is built by the system, starting from the name of the failing resource up through the name of the system itself.... In PAGE 51: ... bulletmed Handle problems differently depending on the type of problem. Table3 -2 on page 3-6 shows the relationship between the alert option (ALROPT) parameter in the message description and the alert status (ALRSTS) network attribute. In this figure, the messages defined as *DEFER have the log problem (LOGPRB) parameter in the message description set to *YES; setting the LOGPRB parameter to *NO in a message causes all alerts for that message to be treated as *IMMED.... In PAGE 60: ... You can control the logging of alerts using the alert logging status (ALRLOGSTS) network attribute. Logging Alerts: Table3 -3 shows whether an alert is logged in the alert database, depending on: 1. The ALRLOGSTS network attribute (*ALL, *LOCAL, *RCV, or *NONE) 2.... In PAGE 60: ... When a held alert is successfully sent, the alert logging status network attribute controls whether the alert remains in the alert database. If the con- ditions shown in Table3 -3 indicate that the alert should not be logged, it is deleted from the alert database. If the conditions indicate that the alert should be logged, it remains in the alert database, but it is no longer displayed as a held alert.... In PAGE 72: ... Determining the Message ID: The message ID for a code point consists of the code point plus a 3-character prefix. Table3 -6 shows the message ID prefixes for the alert code points: For example, the message ID for failure cause X apos;1234 apos; is ALF1234. The code point for the detail qualifier data ID is only 2 hexadecimal digits.... In PAGE 73: ... For code point X apos;xxYx apos;, Y determines the number. Table3 -7 lists the number of qualifiers required by a code point with the given third digit. Substitution Text for Detailed Qualifiers: When you create a code point message that con- tains detailed qualifiers, you must specify where the qualifiers will be displayed.... In PAGE 73: ... To specify detailed qualifiers that appear on the same line as the code point text, you use substi- tution variables to define the placement of the qualifiers. Table3 -8 shows the substitution vari- able numbers that should be used for each qual- ifier. If the detailed qualifier placement is defined at the end of the code point text, you can omit the sub- stitution variable at the end of the text, and the system displays the detailed qualifier on the line following the code point text.... ..."

"... In PAGE 8: ...able 2-3 Hazard Causes and Controls - Examples .........................................................16 Table3 -1 NASA Software Lifecycle - Reviews and Documents.... In PAGE 8: ...able 3-1 NASA Software Lifecycle - Reviews and Documents......................................20 Table3 -2 MIL-STD-882C Software Hazard Criticality Matrix.... In PAGE 8: ...able 3-2 MIL-STD-882C Software Hazard Criticality Matrix.......................................28 Table3 -3 Software Sub-system categories.... In PAGE 8: ...able 3-3 Software Sub-system categories........................................................................29 Table3 -4 Required Software Safety Effort .... In PAGE 8: ...able 3-4 Required Software Safety Effort .......................................................................30 Table3 -5 Software Requirements Phase.... In PAGE 8: ...able 3-5 Software Requirements Phase...........................................................................33 Table3 -6 Software Architectural Design Phase.... In PAGE 8: ...able 3-6 Software Architectural Design Phase................................................................34 Table3 -7 Software Detailed Design Phase .... In PAGE 8: ...able 3-7 Software Detailed Design Phase .......................................................................34 Table3 -8 Software Implementation Phase.... In PAGE 8: ...able 3-8 Software Implementation Phase........................................................................35 Table3 -9 Software Testing Phase .... In PAGE 8: ...able 3-9 Software Testing Phase .....................................................................................35 Table3 -10 Dynamic Testing .... In PAGE 8: ...able 3-10 Dynamic Testing .............................................................................................36 Table3 -11 Software Module Testing .... In PAGE 27: ...19 3.1 Software Development Lifecycle Approach Table3 -1 NASA Software Lifecycle - Reviews and Documents (page 20)shows the typical NASA software waterfall design lifecycle phases and lists the reviews and deliverable project documents required at each lifecycle phase. Each of these reviews and project documents should contain appropriate references and reports on software safety.... In PAGE 28: ...20 Table3 -1 NASA Software Lifecycle - Reviews and Documents LIFECYCLE PHASES MILESTONE REVIEWS SOFTWARE SAFETY TASKS DOCUMENTS Software Concept and Initiation (Project System and Subsystem Requirements and Design Development) SCR - Software Concept Review Software Management Plan Review Phase-0 Safety Review Scoping Safety Effort 2.1.... In PAGE 31: ... The system development phases are separated by system design reviews. Each system design review is conducted approximately in parallel with a corresponding system safety review as shown in Table3 -1 NASA Software Lifecycle - Reviews and Documents on page 20. The software development effort may or may not be synchronized with the system development effort.... In PAGE 35: ... 3.3 Scoping of Software Subsystem Safety Effort The level of required software safety effort for a system (shown in Table3 -3) is determined by its System Category, derived from Table 2-2 Hazard Prioritization - System Risk Index (Page 8), and the hazard severity level from Section 2.... In PAGE 36: ...28 Table3 -2 MIL-STD-882C Software Hazard Criticality Matrix HAZARD CATEGORY CONTROL CATEGORY CATASTRO- PHIC CRITICAL MODERATE NEGLIGIBLE / MARGINAL I1135 II 1 2 4 5 III 2 3 5 5 III 3 4 5 5 Software Hazard Risk Index Suggested Criteria 1 High Risk - significant analysis and testing resources 2 Medium risk - requirements and design analysis and in-depth testing required 3-4 Moderate risk - high level analysis and testing acceptable with management approval 5 Low Risk - Acceptable 3.3.... In PAGE 37: ...29 Table3 -3 Software Sub-system categories System Category Descriptions I Partial or total autonomous control of safety critical functions by software. (System Risk Index 2) Complex system with multiple subsystems, interacting parallel processors, or multiple interfaces.... In PAGE 38: ...30 Table3 -4 Required Software Safety Effort SYSTEM CATEGORY HAZARD SEVERITY LEVEL from Section 2.... In PAGE 39: ... Ultimately, the range of selected techniques must be negotiated and approved by project management, software development, software quality assurance, and software systems safety. Table3 -5 Software Requirements Phase through Table 3-11 Software Module Testing are modifications of tables that appear from an early International Electrotechnical Committee (IEC) draft standard IEC 1508, quot;Software For Computers In The Application Of Industrial Safety-Related Systems quot; [5]. This document is currently under review by national and international representatives on the IEC to determine its acceptability as an international standard on software safety for products which contain Programmable Electronic Systems (PESs).... In PAGE 39: ... These tables provide guidance on the types of assurance activities which may be performed during the lifecycle phases of safety-critical software development. For this guidebook, the Required Software Safety Efforts values displayed in Table3 -4 Required Software Safety Effort (page 30), will determine which development activities are required for each level of effort. Each of the following tables lists techniques and recommendations for use based on safety effort level for a specific software development phase or phases.... In PAGE 40: ... The final list of techniques to be used on any project should be developed jointly by negotiations between project management and safety assurance. All the following tables, Table3 -5 Software Requirements Phase through Table 3-11 Software Module Testing , list software development, safety and assurance activities which should be implemented in the stated phases of development. Life Cycle Phase Tasks and Priorities How To: Development Tasks How To: Analysis Tasks Concept Initiation Table 3-5 Software Requirements Phase Section 4.... In PAGE 40: ... All the following tables, Table 3-5 Software Requirements Phase through Table 3-11 Software Module Testing , list software development, safety and assurance activities which should be implemented in the stated phases of development. Life Cycle Phase Tasks and Priorities How To: Development Tasks How To: Analysis Tasks Concept Initiation Table3 -5 Software Requirements Phase Section 4.1 Section 5.... In PAGE 40: ... Table3 -5 Software Requirements Phase Section 4.3 Section 5.... In PAGE 40: ...3 Section 5.1 Software Detailed Design Table3 -7 Software Detailed Design Phase Section 4.4 Section 5.... In PAGE 40: ...4 Section 5.3 Software Implementation Table3 -8 Software Implementation Phase Section 4.5 Section 5.... In PAGE 40: ...5 Section 5.1 Software Test Table3 -9 Software Testing Phase Table 3-10 Dynamic Testing Table 3-11 Software Module Testing Section 4.6... In PAGE 40: ...5 Section 5.1 Software Test Table 3-9 Software Testing Phase Table3 -10 Dynamic Testing Table 3-11 Software Module Testing Section 4.6... In PAGE 40: ...5 Section 5.1 Software Test Table 3-9 Software Testing Phase Table 3-10 Dynamic Testing Table3 -11 Software Module Testing Section 4.6... In PAGE 41: ...33 Table3 -5 Software Requirements Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 2.1 Preliminary Hazard Analysis (PHA) MMM 5.... In PAGE 42: ...34 Table3 -6 Software Architectural Design Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.2.... In PAGE 42: ....2.4.2 Independence Analysis HR M M Table3 -7 Software Detailed Design Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.3.... In PAGE 43: ...35 Table3 -8 Software Implementation Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.4.... In PAGE 43: ...4.9 Formal Methods NR HR HR Table3 -9 Software Testing Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Testing Defensive Programming NR HR M Boundary Value Tests R HR M Error Guessing NR NR R Test Coverage Analysis R HR M Functional Testing M M M Fagan Formal Inspections (Test Plans) HR HR M Reliability Modeling NR HR HR Checklists of Tests R HR... In PAGE 44: ...36 Table3 -10 Dynamic Testing TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Typical sets of sensor inputs HR M M Test specific functions HR M M Volumetric and statistical tests R HR HR Test extreme values of inputs R M M Test all modes of each sensor R M M Path testing R M M Every statement executed once HR M M Every branch tested at least once HR M M Every predicate term tested R HR M Every loop executed 0, 1, many times R M M Every path executed R HR M Every assignment to memory tested NR HR HR Every reference to memory tested NR HR HR All mappings from inputs checked NR HR HR All timing constraints verified R M M Test worst case interrupt sequences R R... In PAGE 45: ...37 Test significant chains of interrupts R R NR Test Positioning of data in I/O space HR M M Check accuracy of arithmetic NR HR M All modules executed at least once M M M All invocations of modules tested HR M M Table3 -11 Software Module Testing TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Simulation (Test Environment) R HR M Load Testing (Stress Testing) HR M M Boundary Value Tests R HR M Test Coverage Analysis R HR M Functional Testing M M M Performance Monitoring R HR M Formal Progress Reviews R M M Reliability Modeling NR HR HR Checklists of Tests R HR... ..."

"... In PAGE 48: ... The resource type displayed with the name is link (LNK). Substitution Variables: The resource types that can be associated with each substitution variable shown in Table3 -1 on page 3-3 are defined as follows: 3-2 OS/400 Alerts Support V4R1 ... In PAGE 49: ... Table 3-1. Resource Name Variables Defined by the System Variable Description Resource Type Com- munications Sub- system Resource Type Storage Sub- system Resource Type Work Station Sub- system 23 Line description LNK, BCH N/A N/A 24 Controller description CTL N/A CTL, LC 25 Device description N/A TAP, DKT DSP, PRT 26 First level resource LC LC LC 27 Second level resource ADP ADP DSP, PRT 28 Third level resource POR DSK, DKT, TAP N/A 29 Fourth level resource BCH N/A N/A 30 Network interface description DCH N/A N/A 30 Network server description SVR N/A N/A Note: See Table3 -5 on page 3-16 for a list of the resource type abbreviations. Alert Hierarchy: Only one number is defined for the resource name variable, but if this number is known by the system, a complete hierarchy, which includes an entry for each resource in the hier- archy, is built by the system, starting from the name of the failing resource up through the name of the system itself.... In PAGE 51: ... bulletmed Handle problems differently depending on the type of problem. Table3 -2 shows the relationship between the alert option (ALROPT) parameter in the message description and the alert status (ALRSTS) network attribute. In this figure, the messages defined as *DEFER have the log problem (LOGPRB) param- eter in the message description set to *YES; setting the LOGPRB parameter to *NO in a message causes all alerts for that message to be treated as *IMMED.... In PAGE 59: ... You can control the logging of alerts using the alert logging status (ALRLOGSTS) network attribute. Logging Alerts: Table3 -3 shows whether an alert is logged in the alert database, depending on: 1. The ALRLOGSTS network attribute (*ALL, *LOCAL, *RCV, or *NONE) 2.... In PAGE 60: ... the alert remains in the alert database. If the con- ditions shown in Table3 -3 indicate that the alert should not be logged, it is deleted from the alert database. If the conditions indicate that the alert should be logged, it remains in the alert database, but it is no longer displayed as a held alert.... In PAGE 71: ... Determining the Message ID: The message ID for a code point consists of the code point plus a 3-character prefix. Table3 -6 shows the message ID prefixes for the alert code points: For example, the message ID for failure cause X apos;1234 apos; is ALF1234. The code point for the detail qualifier data ID is only 2 hexadecimal digits.... In PAGE 72: ... For code point X apos;xxYx apos;, Y determines the number. Table3 -7 lists the number of qualifiers required by a code point with the given third digit. Substitution Text for Detailed Qualifiers: When you create a code point message that con- tains detailed qualifiers, you must specify where the qualifiers will be displayed.... In PAGE 72: ... To specify detailed qualifiers that appear on the same line as the code point text, you use substi- tution variables to define the placement of the qualifiers. Table3 -8 shows the substitution vari- able numbers that should be used for each qual- ifier. If the detailed qualifier placement is defined at the end of the code point text, you can omit the sub- stitution variable at the end of the text, and the system displays the detailed qualifier on the line following the code point text.... ..."

"... In PAGE 48: ... The resource type displayed with the name is link (LNK). Substitution Variables: The resource types that can be associated with each substitution variable shown in Table3 -1 on page 3-3 are defined as follows: 3-2 OS/400 Alerts Support V4R1 ... In PAGE 49: ... Table 3-1. Resource Name Variables Defined by the System Variable Description Resource Type Com- munications Sub- system Resource Type Storage Sub- system Resource Type Work Station Sub- system 23 Line description LNK, BCH N/A N/A 24 Controller description CTL N/A CTL, LC 25 Device description N/A TAP, DKT DSP, PRT 26 First level resource LC LC LC 27 Second level resource ADP ADP DSP, PRT 28 Third level resource POR DSK, DKT, TAP N/A 29 Fourth level resource BCH N/A N/A 30 Network interface description DCH N/A N/A 30 Network server description SVR N/A N/A Note: See Table3 -5 on page 3-16 for a list of the resource type abbreviations. Alert Hierarchy: Only one number is defined for the resource name variable, but if this number is known by the system, a complete hierarchy, which includes an entry for each resource in the hier- archy, is built by the system, starting from the name of the failing resource up through the name of the system itself.... In PAGE 51: ... bulletmed Handle problems differently depending on the type of problem. Table3 -2 shows the relationship between the alert option (ALROPT) parameter in the message description and the alert status (ALRSTS) network attribute. In this figure, the messages defined as *DEFER have the log problem (LOGPRB) param- eter in the message description set to *YES; setting the LOGPRB parameter to *NO in a message causes all alerts for that message to be treated as *IMMED.... In PAGE 59: ... You can control the logging of alerts using the alert logging status (ALRLOGSTS) network attribute. Logging Alerts: Table3 -3 shows whether an alert is logged in the alert database, depending on: 1. The ALRLOGSTS network attribute (*ALL, *LOCAL, *RCV, or *NONE) 2.... In PAGE 60: ... the alert remains in the alert database. If the con- ditions shown in Table3 -3 indicate that the alert should not be logged, it is deleted from the alert database. If the conditions indicate that the alert should be logged, it remains in the alert database, but it is no longer displayed as a held alert.... In PAGE 71: ... Determining the Message ID: The message ID for a code point consists of the code point plus a 3-character prefix. Table3 -6 shows the message ID prefixes for the alert code points: For example, the message ID for failure cause X apos;1234 apos; is ALF1234. The code point for the detail qualifier data ID is only 2 hexadecimal digits.... In PAGE 72: ... For code point X apos;xxYx apos;, Y determines the number. Table3 -7 lists the number of qualifiers required by a code point with the given third digit. Substitution Text for Detailed Qualifiers: When you create a code point message that con- tains detailed qualifiers, you must specify where the qualifiers will be displayed.... In PAGE 72: ... To specify detailed qualifiers that appear on the same line as the code point text, you use substi- tution variables to define the placement of the qualifiers. Table3 -8 shows the substitution vari- able numbers that should be used for each qual- ifier. If the detailed qualifier placement is defined at the end of the code point text, you can omit the sub- stitution variable at the end of the text, and the system displays the detailed qualifier on the line following the code point text.... ..."