Abstract:
A computer network analyzes a problem with a first computer in the network. The network comprises a first program which runs on a second computer and analyzes a problem with the first computer. A second program also runs on the second computer and generates an alert for transmission to the third computer. The alert includes a probable cause category encompassing the problem and a recommendation. The recommendation is to contact a service engineer if the problem requires expertise or resources of the service engineer to correct, and is to establish remote access on site at the third computer of the first program to obtain additional information relating to the cause of the problem if at least a reasonable chance exists that the problem can be corrected by a person at the first computer which person not having service engineering expertise or resources. A third program runs on the third computer and remotely controls the first program to obtain the additional information relating to the cause of the problem if there is at least a reasonable chance that the problem can be corrected by a person at the first computer which person not having service engineering expertise or resources. The additional information includes a recommended test or inspection to determine the cause of the problem.

Description:
BACKGROUND OF THE INVENTION 
     The invention relates generally to computer systems and networks, and deals more particularly with apparatus and processes for analyzing problems of a node computer with assistance from a central site. 
     In a prior art IBM AS/400 computer system, when a node computer in a network experiences a problem, the node computer invokes a problem analysis program to identify the problem and then sends an alert to a host computer. The alert includes an identification of the specific problem with the node computer. Then an operator at the central site can take action to correct the problem such as calling a service engineer or a person at the node site. While this system is effective in conveying information to the central site, the problem analysis program at the node is frequently updated to identify additional or different problems. As a result, it is necessary to frequently update the central site program to recognize the additional or different problems. 
     IBM&#39;s prior art system network architecture (SNA) supports the transmission of an alert from such a node to a central site, and then transmission of a request by an operator or application at the central site to the node for further information from the node. 
     IBM&#39;s prior art 4381 computer system includes a local processor console and a remote processor console, and a remote service facility which causes display screens generated by an application running on a local processor console to be displayed at both processor consoles. The remote facility also permits a remote operator to control the application running on a local processor console by keyboard input at the remote processor console. The local processor console ran a problem analysis program when a processor detected an error and stored a result which identified the problem and corrective action that could be taken by the operator. When the operator suspected a problem, the operator could invoke the problem analysis program to obtain the additional information. 
     A general object of the present invention is to provide a solution directed computer system and process for analyzing problems of a computer node with assistance from a central site. 
     Another object of the present invention is to provide a system, network and process which are flexible to accommodate program updates at the node which identify additional or different problems without requiring updates to a program running at the central site. 
     Another object of the present invention is to provide a computer network, system and process of the foregoing type which permit an operator at the central site to have full benefit of resources at the node to solve the problem. 
     SUMMARY OF THE INVENTION 
     The invention resides in a computer network for analyzing a problem with a first computer. The network comprises a first program which runs on a second computer and analyzes a problem with the first computer. 
     A second program also runs on the second computer and generates an alert for transmission to a third computer. The alert includes a probable cause category encompassing the problem and a recommendation. The recommendation is to contact a service engineer if the problem requires expertise or resources of the service engineer to correct, and is to establish remote access on site at the third computer for the first program to obtain additional information relating to the cause of the problem if at least a reasonable chance exists that the problem can be corrected by a person at the first computer which person not having service engineering expertise or resources. 
     A third program runs on the third computer and remotely controls the first program to obtain the additional information relating to the cause of the problem if there is at least a reasonable chance that the problem can be corrected by a person at the first computer which person not having service engineering expertise or resources. The additional information includes a recommended test or inspection to determine the cause of the problem. 
     According to one feature of the invention, a fourth program runs on the second computer and automatically responds to the recommendation to call the service engineer. The fourth program is programmable to respond to the recommendation to authorize the second computer to call the service engineer and is programmable to alert an operator at the third computer of the recommendation without authorizing the service engineer call. 
    
    
     BRIEF DESCRIPTION OF THE FIGURES 
     FIG. 1 is a block diagram illustrating a computer network embodying the present invention. 
     FIGS. 2(a)A, 2(a)B and FIGS. 2(a-c) form a flow chart illustrating an implementation and operation of the network of FIG. 1 to analyze a problem of a node computer with assistance from a central site. 
     FIG. 3 is a block diagram illustrating error detection circuitry and programs within the node computer. 
     FIG. 4 is a flow diagram illustrating processing carried out at the node to build an alert message. 
     FIG. 5 is a diagram illustrating a format of the alert message of FIG. 4. 
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     Referring now to the Figures in detail wherein like reference numerals indicate like elements throughout the several views, FIG. 1 illustrates a computer network generally designated 390 according to the present invention. Network 390 comprises a local processor console (LPC) 14 which analyzes a problem with a local or node computer, CEC 12, with assistance from a central or remote site 392. The central site 392 includes a remote processor console (RPC) 16 and a host computer 400. By way of example, the local processor console 14 and the remote processor console 16 each comprises an IBM PS/2 personal computer with an IBM OS/2 operating system, and central host computer 400 and local host computer 12 each comprises an IBM system 370 computer. The two main program components that participate in the analysis of problems are a problem analysis program 402 which runs on the local processor console 14, and a NetView program 404 which runs on host computer 400 at the central site. As described in more detail below with reference to FIG. 2, problem analysis program 402 is invoked by diagnostics circuitry or a diagnostics program (shown in FIG. 3) when the diagnostic circuitry or program detects a problem with the local or node computer 12. Then, problem analysis program 402 (1) generates an alert signal, (2) determines a probable cause category in which the problem falls and a failing part(s) if any, and (3) determines a recommended action to be performed by the central site, and transmits these three information items (and other information as described below) to the central site. 
     The alert is displayed on NetView display console 51 and comprises a collection of subvectors and associated subfields that provide the aforesaid and other information: 
     SV01--Date/Time Subvector--indicates date and time that the error occurred. Sourced by problem analysis program. 
     SV04--SNA Address List Subvector--requests that VTAM communication facility 418 supply the type and name of SNA resources to NetView focal point i.e. central site 392. 
     SV05--Hierarchy/Resource List Subvector--comprises resource name of the local processor console. This field is sourced by the customer. 
     SV10--Product Set ID Subvector--comprises all of the following sourced by problem analysis program: 
     1) Machine Type (four characters); 
     2) Machine Model (three characters); 
     3) Plant of Manufacture (two characters); and 
     4) Serial Number (seven characters). 
     SV92--Generic Alert Data Subvector--comprises one of the following: (code points sourced from Alerts file): 
     1) x`1003`--CPC HARDWARE FAILURE; 
     2) x`2001`--CPC ENTERED HARD WAIT; or 
     3) x`B100`--SERVICE/REPAIR INFORMATION. 
     SV93--Probable Causes Subvector--comprises one of the following: (code points sourced from Alerts file): 
     1) x`0000`--PROCESSOR; 
     2) x`0002`--VECTOR PROCESSOR; 
     3) x`0200`--POWER SUBSYSTEM; 
     4) x`0100`--STORAGE; 
     5) x`000A`--SERVICE PROCESSOR; 
     6) x`0506`--CHANNEL SUBSYSTEM; 
     7) x`6300`--INPUT/OUTPUT DEVICE; 
     8) x`0040`--INITIAL PROGRAM LOAD; 
     9) x`2300`--CONNECTION NOT ESTABLISHED; or 
     10) x`FE00`--UNDETERMINED. 
     SV94--User Causes Subvector--comprised of SF01 and SF81 subfields. 
     SV95--Install Causes Subvector--comprised of SF01 and SF81 subfields. 
     SV96--Failure Causes Subvector--comprised of SF01 and SF81 subfields. 
     SV97--Undetermined Causes Subvector--comprised of SF81 subfields. 
     SF01--Probable Causes Subfield--comprises one or more of the following: (code points sourced from Alerts file): 
     1) x`0006`--PROCESSOR MACHINE CHECK; 
     2) x`0009`--SYSTEM CHECKSTOP; 
     3) x`0008`--VECTOR PROCESSOR; 
     4) x`0200`--POWER SUBSYSTEM; 
     5) x`0100`--STORAGE; 
     6) x`000A`--SERVICE PROCESSOR; 
     7) x`0506`--CHANNEL SUBSYSTEM; 
     8) x`F0A3`--FAILURE OCCURRED ON (SF82-50, 51, 7D, 7E); 
     9) x`6300`--INPUT/OUTPUT DEVICE; and/or 
     10) x`2300`--CONNECTION NOT ESTABLISHED. 
     SF81--Recommended Actions Subfield--a results analysis program (described below) will determine the recommended action to take based on several pieces of information gathered from the machine. The first is whether a RETAIN link has been activated. If it has, then the recommended action is to authorize service. If the link to Retain fails then the recommended action is to dial the phone number and report the following: problem type, problem number, and FRU list or refcode. If the Retain link is not active, then the recommended action is to contact service representative and report the following: problem type, problem number, and FRU list or refcode. 
     This subfield comprises one or more of the following: 
     1) x`00B3`--PERFORM (SF82-7A) PROBLEM DETERMINATION VIA A REMOTE CONSOLE SESSION; 
     2) x`30A0`--DIAL (SF82-D4) AND REPORT THE MACHINE INFORMATION; 
     3) x`32A0`--REPORT THE FOLLOWING SF82; 
     4) x`30E0`--PROVIDE REMOTE SERVICE CALL AUTHORIZATION FOR (SF83 product text); and/or 
     5) x`30E1`--CONTACT SERVICE REPRESENTATIVE FOR (SF83 product text). 
     SF82--Detailed Data Sub-Subfield--comprises one or more of the following: (code sub-points sourced from Alerts file): 
     1) x`50`--CHANNEL ADDRESS number; 
     2) x`7E`--CHANNEL PATH ID number; 
     3) x`51`--DEVICE ADDRESS number; 
     4) x`7D`--SUBCHANNEL NUMBER number; 
     5) x`7A`--CENTRAL PROCESSOR COMPLEX; 
     6) x`D4`--TELEPHONE NUMBER number; 
     7) x`20`--MESSAGE CODE refcode or FRU-list; 
     8) x`xx`--PROBLEM TYPE type; 
     9) x`xx`--PROBLEM NUMBER number; and/or 
     10) x`xx`--PROBLEM MANAGEMENT HARDWARE (PMH) number. 
     SF83--Product Set ID Index--comprises definition of the failing processor: x`51`--Machine type, model number, and serial number from SV10. 
     The alert message complies with Systems Network Architecture (SNA) as described in a publication entitled &#34;SNA Formats&#34; published by IBM Corp., publication #GA27-3136. See also &#34;Alert Implementation Guide&#34; published by IBM Corp., publication #GC31-6809.: 
     The transmission from the local processor console or node 14 to the central site can be made either via a leased/switched telephone line 410 which normally would not incur a telephone charge to the user, or a switched telephone line 412 which would incur a telephone charge to the user. To utilize the leased telephone line 410, the communication is sent via service call logical processor interface (SCLPI) to an operating system 414 of the local host computer 12 and a virtual telecommunication access method (VTAM) communication facility within the local host computer to a VTAM communication facility of the central site host computer. SCLP is a system 370 architected instruction which is executed by operating system 414 to control movement of data from operating system 414 to hardware within CEC 12. VTAM communication facility is described in detail in a publication entitled &#34;VTAM Programming for LU 6.2&#34; by IBM Corp. of Armonk, N.Y., publication #SC30-3400. During this mode of communication, a portion of a NetView program 420 at the node computer 12 provides a communication program function to pass alerts from operating system 414 to VTAM communication facility 416. The NetView programs 404 and 420 are described in detail in publications entitled &#34;NetView Operation Release 2&#34; by IBM Corp., publication #SC30-3364, &#34;Learning About NetView&#34; by IBM Corp., publication #SK2T-0292, Systems Network Architecture Technical Overview by IBM Corp., publication #GC30-3073, &#34;NetView Hardware Problem Determination Reference&#34; by IBM Corp., publication #SC30-3366; and &#34;NetView Operation Scenarios&#34; by IBM Corp., publication #SC30-3376. NetView programs 404 and 420 are substantially the same but can run on different operating systems. 
     The problem analysis program 402 monitors the status of NetView program 420 and operating system 414 of the local host computer, and when both are available, selects the leased path to avoid the telephone company charge. 
     However, if the leased telephone line path is not available, then problem analysis program 402 selects the switched telephone line path to send the aforesaid information i.e. alert, probable cause category, and recommended action. This path utilizes a Communication Manager program of the IBM OS/2 operating system 13 and an application program to program interface (APPI) which Communication Manager and APPI are collectively identified by reference numeral 430. The OS/2 operating system is further defined in a publication entitled &#34;IBM OS/2 Standard Edition Version 1.2 Getting Started&#34; publication which is part of a package of publications collectively entitled &#34;OS/2 EE 1.2 End User Pubs&#34; IBM publication #SO1F-0285. The path also comprises synchronous data link connection (SDLC) 434 and a modem 436 to access the switched telephone line 412. Then, the transmission is received by a modem 438 and passed to VTAM communication facility 418 under the control of a communications controller 444. 
     After receiving the aforesaid transmission from local processor console 14, NetView program 404 can automatically transmit a response, such as to authorize a call to service engineer, to problem analysis program 402 via the same path. NetView program 404 can also display a recommendation made by the problem analysis program 402 to invoke a remote console support facility 44 using remote processor console 16 to obtain additional information about the problem. The authorization response can be made by a high level &#34;authorize service&#34; command as described in copending U.S. patent application entitled &#34;Remote Control of a Computer Processor&#34; filed by A. K. Fitzgerald, C. W. Gainey, Jr., W. K. Kelley and Samuel L. Wentz on Sep. 4, 1990, which patent application is hereby incorporated by reference as part of the present disclosure. Remote console support facility 44 invokes a remote operator facility 42 at local processor console 14 to permit remote operation at remote processor console 16 to interact with problem analysis program 402 to obtain additional information. Such a remote operation can be a type described in copending U.S. patent application Ser. No. 07/575,746 entitled &#34;Remote Operator Facility for a Computer&#34;, filed by Mary K. Dangler and Samuel L. Wentz on Aug. 31, 1990, which patent application is hereby incorporated by reference as part of the present disclosure. In the first case, the participation by the central site is complete after the transmission of the response to authorize calling the service engineer. However, in the latter case, the remote operator can then prompt the problem analysis program 402 to further identify the problem and permit the remote operator to remotely view display screens generated by the problem analysis program 402. For example, assume that the diagnostic circuitry at the local processor console originally detected a power supply overheating problem. As a result, the problem analysis program would transmit the probable cause category of &#34;Power Subsystem&#34; with the alert to the central host computer 400 as noted above and also the recommended action of &#34;perform central processor complex problem determination via a remote console session&#34;. After receiving the aforesaid information, the NetView operator at the central host computer will initiate the remote operator session as described above and prompt the problem analysis program 402 to display a recommended test which is most likely to identify the actual problem. In this example, the problem analysis program 402 will display &#34;ambient heat problem&#34; which display will be presented on the local processor console screen and the remote processor console screen as described above. In response, the remote operator can make an oral telephone call to the local site to a person (user, owner, janitor, etc.) and ask the person to check the ambient temperature in the room in which the local processor console is located. If the local person responds that the ambient temperature is within the specified temperature range, then the remote operator can direct the local processor console 14 to place a call to a service engineer. However, if the ambient temperature is too hot, the node person can take local action to correct the ambient temperature without the costly need for a service engineer. 
     FIG. 2 illustrates in more detail the aforesaid process for analyzing a problem with assistance from the central site. Initially, a diagnostics circuit or program detects an error condition such as a loss of power, resource or system damage machine check, disabled wait, or parity error, and logs the error condition to LPC 14 (step 500). FIG. 3 illustrates the diagnostics circuitry that detects the problems. Parity checkers 700 checks the parity of data generated by processing unit 702, memory 704, channels 706 (channel control check), and I/O processors 708-711. Power sensors 712 check the voltage(s) supplied by power subsystem 714. A disabled wait register 720 stores a &#34;wait&#34; code written by a program 722 when the program 722 has encountered an unrecoverable condition. The error signals corresponding to each of these errors are transmitted to problem analysis program 402 via LPC interface 724. In response to the detected error, problem analysis program 402 is automatically invoked (step 502). Then, a problem determination (PD) routine within problem analysis program 402 analyzes the processor error condition to determine the data for subvectors SV92, SV93, SV94, SV95, SV96, and SV97 (step 503). Subvector SV93 indicates the probable cause category and subvectors 94-97 including SF 82-29 indicate the failing part number. Then, problem analysis program 402 runs and determines if it should generate an alert for transmission to central site 400 (decision block 504). If problem analysis program 402 is running in an isolated processor, then step 504 leads to step 508 in which the event is logged and reported to the local operator. However, whenever the problem emanates from a node processor i.e. one for which access to central site 392 is available, problem analysis program 402 determines in decision block 504 that an alert and the accompanying information should be generated. Thus, in the illustrated network, decision block 504 leads to step 506. In step 506, problem analysis program 402 actually generates the alert and accompanying information as follows. In step 600, a results analysis portion 584 (FIG. 4) of problem analysis program 402 determines if additional information is required for a central site operator from the node via the remote operation (and possibly from the node person also) to solve the problem. This decision is based on the nature of the problem. For example, as noted above, if the problem is a power subsystem failure and the temperature sensors at node computer 12 indicate high temperature, then results analysis program 584 requires more information from the node via the remote operation to assist the central site operation in determining if the temperature sensor is working properly (i.e. by checking the room temperature). As another example, if the problem emanates from an I/O processor expansion unit, then the results analysis program requires more information to determine whether the problem is in fact a malfunctioning I/O processor expansion unit that requires attention by a service engineer or whether the problem is easily correctable such that a node person who is unskilled in service engineering or operations can correct the problem. For example, if the problem is due to a power switch being in the off position instead of the on position, then the node person who is unskilled in service engineering and operations can simply correct the problem after oral instruction from the central site. As another example, assume that power is lost to the local processor console and the node computer. When power is restored, a &#34;power subsystem&#34; alert will be sent to the central site. The recommended action is to use the remote operation (i.e. remote console support and remote operation facility) to obtain additional information because the problem could be due to an electrical storm which has subsided without any permanent damage to the power subsystem. The additional information provided by the remote operation indicates loss of power that could be due to an external power loss. The screen requests a node person to check whether there has been an external power loss. If there has been an external power loss, then a service call is not required, and jobs can be restarted. However, if there has not been an external power loss, then a service engineer should be called. As another example, assume that operating system 414 is unable to continue operations i.e. a &#34;disabled wait state&#34;. In this case, the probable cause category is &#34;Undetermined&#34; and the recommended action is to initiate remote operations. When the remote session is established, the problem analysis program will display: 
     &#34;The system is in a disabled wait state. The wait state was detected at: (TIME)&#34; 
     &#34;The disabled wait program status word is: (WORD)&#34; 
     &#34;There were input/output (I/O) events preceeding the disabled wait that may be related to the disabled wait. (I/O FAILURE LIST) 
     Problem analysis may be performed at your convenience. 
     To perform Problem Analysis, select `Analyze` on the System Monitor action bar. 
     The system is not operating.&#34; 
     After reading this display screen at RPC16, the remote operator can then analyze the I/O failure list, and can perform further problem analysis and take proper action depending on the cause of failure. 
     The following is a list of actual messages from display screens generated by the problem analysis program and displayed at both LPC 14 and RPC16 to provide the additional information to the remote operator: 
     &#34;A power failure on one of the secondary racks has been detected at: 
     Verify that the `Unit Emergency Power Off` switches on all of the secondary racks are in the `On` position. If all of the switches are in the `On` position, then service is required.&#34; 
     &#34;A failure in the channel subsystem has been detected at: 
     The channel subsystem is still operational but its performance may be degraded. 
     Jobs may have failed as a result of this problem. 
     Restart any jobs that failed.&#34; 
     &#34;A channel subsystem failure has occurred. Your system may still be operational. Analysis may be performed at your convenience. 
     Record the following information. It will be needed to accurately perform Problem Analysis. 
     To perform analysis select Start Problem Analysis from the Task Selection screen and use the following information. 
     Time of error: 
     Date of error: 
     Channel: (Channel #)&#34; 
     &#34;A format error of the Program Status Word has occurred during the load at: 
     Load channel address: 
     Load device address: 
     Verify the following: The load device address is correct. The load mode matches the load data source. The load data source is correct. 
     Re-load the system. Report this message to the person in charge of maintaining your software. 
     If you suspect a hardware problem, then request service.&#34; 
     &#34;A load error has occurred at: 
     No response was detected from the load unit address. 
     Load channel address: 
     Load device address: 
     Verify that the load unit address is correct. Ensure that the control unit and device are powered on and enabled. 
     Re-load the system. 
     If you suspect a hardware problem, then request service.&#34; 
     &#34;The Processor Console was unable to communicate with the processing unit at: 
     The processing unit is not powered on. Verify that the `Unit Emergency Power Off` switch on the primary rack is in the `On` position. Check to see if there have been any external power outages or disturbances. If the switch is in the `On` position and there have not been any external power problems, then service is required.&#34; 
     &#34;The Processor Console was unable to communicate with the processing unit at: 
     There may be a problem with the cable that connects the Processor Console to the processing unit. Check the cable which connects the Processor Console to the primary rack. If there is not a cable connection problem, then service is required.&#34; 
     &#34;Remote or timed power-on did not complete at: 
     The keylock must be in the Normal or Auto position. Place the keylock in the desired position and try the operation again.&#34; 
     &#34;Manual power-on did not complete at: 
     The keylock must be in the Manual or Normal position. 
     Place the keylock in the desired position and try the operation again.&#34; 
     &#34;A power problem was detected at: 
     Power on the processor. Restart any jobs that failed. Check to see if there have been any external power outages or disturbances. If there have not been any external power problems, then service is required. 
     Note: An automatic restart would have been attempted if it had been enabled. If you want the automatic restart feature enabled, place the keylock in the Normal or Auto position.&#34; 
     &#34;A channel control units did not complete power-on at: 
     Service is required. Your system may still be operating if these channels are not being used.&#34; 
     &#34;The system has detected high room temperature, and has powered down the processor at: 
     The processor should not be powered-on until the problem causing the high room temperature has been corrected. 
     If the room temperature is not high, then service is required.&#34; 
     &#34;The alternate external power source is now being used because of a problem detected with the primary external power source at: 
     The primary external power source should be checked to determine the cause of the problem. 
     Restart any jobs that may have failed due to possible power disturbances.&#34; 
     &#34;A rack power problem has been detected at: 
     The rack power supply has restarted automatically. Restart any jobs that failed. Check to see if there have been any external power outages or disturbances. If there have not been any external power problems, then service is required.&#34; 
     In summary, additional information is required from the node person whenever it is possible that the problem could be corrected by the node person who is not highly skilled in service engineering or operations. Conversely, additional information is not required if it is very unlikely that the problem can be corrected by a person who is not skilled in service engineering such as when the problem is due to a circuit failure. The following table indicates for which actual problems is additional information/remote operations of remote console support and remote operator facility required, and for which actual problems is additional information/remote operations of remote console support and remote operator facility not required. In the latter case, the recommended action is to call a service engineer. 
     
         ______________________________________                      IS ADDITIONALACTUAL      PROBABLE CAUSE INFORMATIONPROBLEM     CATEGORY       REQUIRED?______________________________________Hardware Parity       Processor      NoErrorI/O Not Available        &#34;             YesProgram Problem        &#34;             NoLogic Error  &#34;             NoVector Processor        &#34;             NoHardware Parity       Vector Processor                      NoErrorProgram Problem        &#34;             NoLogic Error  &#34;             NoExternal Power       Power Subsystem                      YesLossPower Supply        &#34;             NoHardware FailureSwitch in Wrong        &#34;             YesPositionMalfunctioning       Storage        NoMemoryTape &amp; Disk Not       Service Processor                      YesInserted    (LPC 14)Hardware Error       Service Processor                      No, LPC       (LPC 14)       may be downProgram Error       Service Processor                      No, LPC       (LPC 14)       may be downInterface Problem       Channel Subsystem                      YesHardware Problem        &#34;             NoProgram Problem        &#34;             NoNo Power to  &#34;             YesChannel HardwareSwitch in Wrong       Input/Output Device                      YesPositionUnplugged    &#34;             YesHardware Failure        &#34;             NoPower Failure        &#34;             YesHardware Failure       Initial Program Load                      NoIPL Storage Device        &#34;             YesProblemChannel Problem        &#34;             YesProgram Problem        &#34;             YesCannot Contact       Connection Not No, requestRetain Service       Established    service through                      central site.Disabled Wait       Undetermined   Yes______________________________________ 
    
     If additional information is not required, then decision block 600 leads to decision block 602 in which the results analysis program determines if a communication link 603 to the Retain service is available. If so, then results analysis program generates the alert with the recommended action defined in SF81, 30E0 i.e. &#34;provide remote service call authorization for (SF83 product text)&#34; (step 604). It should be noted that the alert accompanying this recommendation does not include the failing part number(s) because the service call will be made electronically from the node. Referring again to decision block 602, if the Retain link is not available, then the results analysis program generates the alert with the recommended action in this case defined by subfields 30E1, 30A0 and 32A0 i.e. &#34;contact service representative for (SF83 product text)&#34;, &#34;dial (SF82-D4)&#34; and &#34;report the machine information:, &#34; and &#34;report the following SF82,&#34; respectively. It should be noted that the information accompanying this alert includes the failing part number because the service call will be made orally by a person at the central site who will relay the failing part number to the service organization. It should be noted that in the majority of instances, the failing part number(s) is not sent to the central site. Only when the Retain link is not available from the node is the failing part number(s) sent to the central site so that the central site operator can orally telephone a service organization. 
     Referring again to decision block 600, if additional information is required, then the results analysis program generates the alert with the recommended action defined by subfield 00D3 i.e. &#34;perform (SF82-7A) problem determination via a remote console session&#34; (step 610). If the communication path through the SCLPI, the local CEC 12 and the leased/switched line 410 is available, then the alert and accompanying information are routed through this path to avoid the telephone charge (decision block 510 and step 512). Otherwise, the alert is routed through the switched telephone line 412 via the APPI under the Communication Manager program, SDLC and modem 436 (step 516). 
     After either of steps 514 or 516, NetView program 404 reads the alert and accompanying information. It should be noted that the NetView program 404 can be customized by the user with a CLIST or EXEC program 405 before installation to respond to any or all of the alerts in a manner based on a vector contained in the alert information. In the illustrated embodiment, NetView program 404 has been programmed to automatically respond to those alerts which recommend use of a service engineer. When such an alert is received, decision blocks 518 and 519 lead to step 520 in which NetView program 404 executes the &#34;CLIST&#34; or an &#34;EXEC&#34; program 405, to automatically return an &#34;authorize service&#34; command to problem analysis program 402 to authorize the use of the service engineer and/or display the recommended action. The CLIST program is as follows: 
     
         ______________________________________AUTHREQ CLIST&amp;CONTROL ERR(C) COPYRIGHT IBM CORP. 1990DESCRIPTION:       This CLIST performs the required       operations to send the RUNCMD that       authorizes service for the remote       processor.&amp;WRITE&amp;WRITE      AUTHREQ&amp;WRITECheck for valid number of parms&amp;IF &amp;PARMCNT LT 2 &amp;THEN &amp;GOTO -PARMCHKSave the parms passed to CLIST&amp;PARMS = &amp;PARMSTRParse PARMS and select appropriate system to issueservice requestPARSEL3R PARMS APPL INCID RESTSet up checks to determine if the system name is onethat we want to authorize. Also, set the ID used bythe VARY command to communicate with the correct phoneline and system.&amp;ID = `???`&amp;IF &amp;APPL EQ `TARGETSP` &amp;THEN &amp;ID = `T7C`&amp;IF &amp;APPL EQ `TARGETSP` &amp;THEN &amp;SP = `S32B90P4`If ID is `???` then we did not find a system that wecan authorize &amp;IF &amp;ID EQ `???` &amp;THEN &amp;GOTO -INVALIDLINACTInactivate ID so we can auto-dial remote system&amp;WROTE --- Reset line&amp;WAIT `INACT &amp;ID`, IST105I=-LACT, *ERROR= -ERRORLACTInactive ID so we can auto-dial remote system&amp;WRITE --- Dial phone&amp;WAIT `V NET,ACT,IF=&amp;ID,LOGON=&amp;APPLID`,IST598I=-AUTHSVCE,*ERROR=-ERRORAUTHSVCEExecute authorize service RUNCMD for remote system&amp;WRITE&amp;WRITE  Authorize Service for Resource:                       &amp;APPL&amp;WRITE  PU:                 &amp;SP&amp;WRITE  ID:                 &amp;ID&amp;WRITE  Problem Number:     &amp;INCID&amp;WRITERUNCMD   SP=&amp;SP APPL=&amp;APPL CLISTVAR=YES +    DAN(OCFCMD) +    SERVICE +       AUTH(OKOK) +       STYPE(ROSTSVC) +       INCIDENT(&amp;INCID)&amp;WRITE Return message from system &amp;APPL: &amp;DSIRUN001&amp;WRITE --- Hangup phone&amp;WAIT `INACT &amp;ID`,IST105I=-THIRD,*ERROR=-ERRORTHIRD&amp;WRITE --- Reset line&amp;WAIT `ACT &amp;ID`,IST0931=-END,*ERROR=-ERROR&amp;GPTP -ENDINVALID&amp;WRITE Invalid resource name entered: &amp;APPL&amp;EXITPARMCHK&amp;WRITE&amp;WRITE  INVALID NUMBER OF PARMS ENTERED.&amp;WRITE  Correct syntax is..........AUTHREQ resource   problem&amp;WRITE&amp;WRITE  where:&amp;WRITE  resource ==              The name of the resource that sent              the ALERT.&amp;WRITE  problem == The unique problem number              associated with the alert. It is              the first 4 bytes defined in the              MESSAGE CODE.&amp;WRITE&amp;EXITEND&amp;WRITE Ended normally ...............&amp;EXITERROR&amp;WRITE Ended with an ERROR ...............&amp;EXIT______________________________________ 
    
     Another CLIST or EXEC program could be provided to both display the alert and return the command. Program 405 is called in the following manner. When the central site receives the Alert built in step 604 and sent in step 514 or 516, the return program 404 reads the recommended action Subfield SF81 which recommends &#34;provide remote service call authorization . . . &#34;, and executes the program 405. 
     The form of the return command can be that described in the aforesaid copending patent application entitled &#34;Remote Control of a Computer Processor&#34; by Fitzgerald et al. 
     If the program 405 is not provided, then NetView program 404 (by default) automatically displays the alert (step 523). Then the central site operator can either proceed to step 522 described below or orally call the service engineer (step 525). 
     If the recommended action was not to use a service engineer, then decision block 518 leads to step 522 in which NetView program 404 causes a display on NetView display console 51 of the alert and accompanying information i.e. probable cause category and recommended action. Then, the central site operator starts a remote operating session with remote operator facility 42 at the node and prompts problem analysis program 402 to display additional data i.e. a refinement on the probable cause and a recommended test such as to check a power switch or check the ambient temperature at node 12 (step 522). After this additional problem analysis data is displayed and read by the central site operator, the central site operator while in this remote operator session can authorize a service call by entering an &#34;authorize service&#34; command selection through an RPC keyboard 819 which then transmits the selection to the local processor console 14. The local processor console then sends the service information, for example, failed parts and machine ID, to Retain facility. The central site operator also has an option to telephone orally a service organization and report the service information (step 524). After a service call, the service engineer should arrive at the node 14 and make the repair (step 526) and close the call on local processor console 14 (step 528). In response to the closing call, problem analysis program 42 generates a problem resolution vector to notify NetView program 404 that service has been completed (step 530). 
     It should be understood that in most cases, after the central site operator reads the additional problem analysis information in step 522, the central site operator makes an attempt to solve the problem without contacting the service engineer and incurring the expense of a service call. Thus, usually step 522 leads to step 532 in which the central site operator calls a person at node 14 such as a user, owner or janitor to attempt to correct the problem. For example, if the additional problem analysis information indicates an overheating problem, the central site operator can call the person at node 14 and ask the person to check the room temperature, and if the room temperature is too high, correct the problem without calling a computer service engineer. 
     It should be noted that the aforesaid procedure for providing the problem analysis information in two steps, first the probable cause category direct transmission and then the use of the remote console support and remote operator facility to obtain a display of additional information, avoids the need to update the NetView program 404 every time that the problem analysis program 402 is updated to identify a new type of problem. According to the aforesaid procedure, when the problem analysis program is updated to identify a new type of problem, the new type of problem is grouped with an (old) type of problem in a preexisting probable cause category that has the same recommended action and similar subject matter, and the remote console support and remote operator facility session is used to further define the problem. If the problem is solved in step 532, then decision block 534 is conclusive. Otherwise, the central site operator can either make an oral telephone call directly to a service engineer and provide the additional information (i.e. failed part number) in step 524 or make the call via node 14 electronically in step 538. Such an electronic call can be made by sending a service command to node 14 as described above. 
     If the switched line 412 is being used for the remote operator facility session (decision block 540), then the service call request is queued by problem analysis program 402, and problem analysis program 402 automatically dials the Retain service to place the service engineer call once the remote operator session ends (step 542). In the illustrated embodiment, the service is designated as &#34;Retain&#34; service which is a service provided by IBM Corp. If the &#34;Retain&#34; transmission is successful, the &#34;Retain&#34; service will return an acknowledgment in the form of a problem management hardware (PMH) record number, and decision block 544 leads to step 546 in which problem analysis program 402 will send a problem resolution vector to the central site acknowledging the successful service call and including the PMH number. Then, steps 526, 528 and 530 are implemented as noted above. However, if the &#34;Retain&#34; transmission was not successful, decision block 544 leads to step 550 in which problem analysis program 402 transmits information to central site 400 for display, which information enables the central site operator to place the telephone call orally. 
     Referring again to decision block 540, if the remote operator facility session initiated in step 522 utilizes the switched telephone line 412, then the central site operator can terminate the remote operator facility session and authorize the service call via leased/switched telephone line 410 and local CEC (step 552). Then, problem analysis program 402 dials the &#34;Retain&#34; service to place the call (step 556). If the transmission is successful as noted above (decision block 558), the &#34;Retain&#34; service transmits an acknowledgement, and decision block 558 leads to step 560 in which problem analysis program 402 generates a problem resolution vector to communicate the PMH record number and the problem number to the central site. However, if the retain transmission is not successful, decision block 558 leads to step 562 in which problem analysis program 402 generates another alert to the central site and the necessary information to enable the central site operator to report the call directly. After either of steps 560 or 562, steps 526, 528 and 530 are implemented as described above. 
     The following is a list of alerts with the possible combinations of subvectors and subfields providing the accompanying information: 
     
         ______________________________________Processor Machine CheckAlert Description        CPC HARDWARE FAILUREProbable Causes        PROCESSORUser Causes  NoneInstall Causes        NoneFailure Causes        PROCESSOR MACHINE CHECKRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.System CheckstopAlert Description        CPC HARDWARE FAILUREProbable Causes        PROCESSORUser Causes  NoneInstall Causes        NoneFailure Causes        SYSTEM CHECKSTOPRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.Vector Processor ProblemAlert Description        CPC HARDWARE FAILUREProbable Causes        VECTOR PROCESSORUser Causes  NoneInstall Causes        NoneFailure Causes        VECTOR PROCESSORRecommended Action        Determine by the scenario        described under SF81 subfield and        step 506.Power ProblemAlert Description        CPC HARDWARE FAILUREProbable Causes        POWER SUBSYSTEMUser Causes  NoneInstall Causes        NoneFailure Causes        POWER SUBSYSTEMRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.Storage ProblemAlert Description        CPC HARDWARE FAILUREProbable Causes        STORAGEUser Causes  NoneInstall Causes        NoneFailure Causes        STORAGERecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.Service Processor ProblemAlert Description        CPC HARDWARE FAILUREProbable Causes        SERVICE PROCESSORUser Causes  NoneInstall Causes        NoneFailure Causes        SERVICE PROCESSORRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.Channel Problem in System 370 ModeAlert Description        CPC HARDWARE FAILUREProbable Causes        CHANNEL SUBSYSTEMUser Causes  NoneInstall Causes        NoneFailure Causes        CHANNEL SUBSYSTEM        FAILURE OCCURRED ON        CHANNEL ADDRESS numberRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.Channel Path Problem in IBM VM/ESA Operating System ModeAlert Description        CPC HARDWARE FAILUREProbable Causes        CHANNEL SUBSYSTEMUser Causes  NoneInstall Causes        NoneFailure Causes        CHANNEL SUBSYSTEM        FAILURE OCCURRED ON        CHANNEL PATH ID numberRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506..Channel Problem With a Device in System 370 ModeAlert Description        CPC HARDWARE FAILUREProbable Causes        CHANNEL SUBSYSTEMUser Causes  NoneInstall Causes        NoneFailure Causes        CHANNEL SUBSYSTEM        FAILURE OCCURRED ON        CHANNEL ADDRESS number        FAILURE OCCURRED ON DEVICE        ADDRESS numberRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.Channel Problem With a Device in ESA ModeAlert Description        CPC HARDWARE FAILUREProbable Causes        CHANNEL SUBSYSTEMUser Causes  NoneInstall Causes        NoneFailure Causes        CHANNEL SUBSYSTEM        FAILURE OCCURRED ON        CHANNEL PATH ID number        FAILURE OCCURRED ON DEVICE        NUMBER numberRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.IPL Failure In System 370 ModeAlert Description        CPC HARDWARE FAILUREProbable Causes        INITIAL PROGRAM LOADUser Causes  NoneInstall Causes        NoneFailure Causes        FAILURE OCCURRED ON        CHANNEL ADDRESS number        FAILURE OCCURRED ON DEVICE        ADDRESS numberRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.IPL Failure in ESA ModeAlert Description        CPC HARDWARE FAILUREProbable Causes        INITIAL PROGRAM LOADUser Causes  NoneInstall Causes        NoneFailure Causes        FAILURE OCCURRED ON        CHANNEL PATH ID number        FAILURE OCCURRED ON DEVICE        NUMBER numberRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.Hard Wait DetectedAlert Description        CPC ENTERED HARD WAITProbable Causes        UNDETERMINEDUser Causes  NoneInstall Causes        NoneFailure Causes        NoneRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.I/O Error In 370 ModeAlert Description        CPC HARDWARE FAILUREProbable Causes        INPUT/OUTPUT DEVICEUser Causes  NoneInstall Causes        NoneFailure Causes        INPUT/OUTPUT DEVICE        FAILURE OCCURRED ON        CHANNEL ADDRESS number        FAILURE OCCURRED ON DEVICE        ADDRESS numberRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.I/O Error in IBM VM/ESA Operating System ModeAlert Description        CPC HARDWARE FAILUREProbable Causes        INPUT/OUTPUT DEVICEUser Causes  NoneInstall Causes        NoneFailure Causes        INPUT/OUTPUT DEVICE        FAILURE OCCURRED ON        CHANNEL PATH ID number        FAILURE OCCURRED ON DEVICE        NUMBER numberRecommended Action        Determined by the scenario        described under SF81 subfield and        step 506.Unsuccessful Call ReportAlert Description        CENTRAL PROCESSOR COMPLEX        (CPC) PROBLEMProbable Causes        CONNECTION NOT ESTABLISHEDUser Causes  NoneInstall Causes        NoneFailure Causes        CONNECTION NOT ESTABLISHEDRecommended Action        DIAL TELEPHONE NUMBER number        AND REPORT THE MACHINE        INFORMATION REPORT THE        FOLLOWING PROBLEM TYPE        (problem type)        REPORT THE FOLLOWING        PROBLEM NUMBER        (problem number)        REPORT THE FOLLOWING        MESSAGE CODE (message code)Multiple Channel and Device ProblemsAlert Description        CPC HARDWARE FAILUREProbable Causes        CHANNEL SUBSYSTEMUser Causes  NoneInstall Causes        NoneFailure Causes        CHANNEL SUBSYSTEMRecommended Action        PERFORM (SF82-D4) PROBLEM        DETERMINATION VIA A REMOTE        CONSOLE SESSIONProblem Resolution VectorsSuccessfulCall ReportDescription  SERVICE/REPAIR INFORMATIONProbable Causes        UNDETERMINEDUser Causes  SERVICE CALL SUCCESSFULLY        PLACED: PROBLEM NUMBER        numberInstall Causes        NoneFailure Causes        NoneRecommended Action        NO ACTION NECESSARYEnd of Call NotificationDescription  SERVICE/REPAIR INFORMATIONProbable Causes        UNDETERMINEDUser Causes  SERVICE COMPLETE: PROBLEM        NUMBER numberInstall Causes        NoneFailure Causes        NoneRecommended Action        NO ACTION NECESSARY______________________________________ 
    
     In each of the above examples, the &#34;Alert Description&#34; field is the Subvector SU92, the &#34;Probable Causes&#34; field is the Subvector SU93, the &#34;User Causes&#34; field is the Subvector SU94, the &#34;Install Causes&#34; field is Subvector SU95, the &#34;Failure Causes&#34; field is the Subvector SU96 with Subfield SF01, and the &#34;Recommended Action&#34; field is the Subvector SU96 with Subfield SF81. 
     FIG. 4 illustrates processing by the problem analysis program 402 of FIG. 2. Problem analysis program 402 automatically invokes a problem determination (PD) routine (step 580) after the error was detected in step 500. Then, the PD routine analyzes the problem and writes alert data into a file 582, which alert data is required to generate the aforesaid alert. The alert data comprises the data necessary to fill in the subvectors and subfields described above. Next, results analysis program portion 584 of problem analysis program 402 is invoked, and because the error originated from node 14, determines that an alertable condition exists and invokes an alert generation portion 586 of problem analysis program 402. Then, the alert generation program makes an entry in an alert request queue 590 for the current problem, and returns control to results analysis program 584. Then, a queue monitor converts the request corresponding to the current problem to an alert format. FIG. 5 illustrates by example, the format of an alert 800. This example is a power subsystem failure where the recommended action is to authorize service. The queue monitor is also responsible for routing the alert to the correct path. 
     Based on the foregoing, apparatus and processes embodying the present invention have been disclosed. However, numerous modifications and substitutions can be made without deviating from the scope of the invention. Therefore, the invention has been disclosed by way of example and not limitation, and reference should be made to the following claims to determine the scope of the invention.