\new;poff 8;text off;join off;justify off;head " ";subhead"" \sect "ASAP SERVER T0402V02 15OCT2004 Page "1;center SOFTWARE RELEASE DOCUMENT ADDENDUM Product Name: ASAP SERVER Product Number: T0402V02 Date: 15OCT2004 PVU Number: T0402AAE Copyright Notice: HP CONFIDENTIAL: NEED TO KNOW ONLY Copyright 2004 Hewlett Packard Development Company, L.P. Protected as an unpublished work. The computer program listings, specifications and documentation herein are the property of Compaq Computer Corporation and successor entities such as Hewlett Packard Development Company, L.P., or a third party supplier and shall not be reproduced, copied, disclosed, or used in whole or in part for any reason without the prior express written permission of Hewlett Packard Development Company, L.P. Revision History: # Rev.-Date Description of changes in each revision 1 16OCT2004 Changed ASAP Server Manual part number. Summary: ASAP now supports goals and can take user defined corrective actions. New COMM entity now supports state and Measure stats for comm lines. Disk entity now provides largest fragment stats and actionable goals. Cpu entity now provides break point statistics and actionable goals. DBMaxDays can be configured to automatically retain long term history. Set DBMaxDays option maintains database history on a per entity basis. DB command provides detailed analysis of disk space usage by entity. Process entity now supports wildcards, selection by object file name, and support for OSS process and OSS file names. File entity now supports OSS files, abstract ZLE groups, super-scalar object counts. EMS RANK events allow user defined event numbers and new token types. Smart Gathering Process SGPs can now run in a user defined CPU. New REMOTESECURITY option indicates whether RemotePasswords are checked when shutting down remote ASAP monitors. The Disk SGP now supports the Enterprise Storage Subsystem. The ASAP product now executes 3-4 times faster than in previous releases of ASAP. A variety of minor issues have been corrected. Superseded PVUs: T0402AAA T0402AAB T0402AAD Requisite PVUs: T0346AAE if using D42.00-D45.01 (see note) T0346AAU if using D46.00 onward or G06.00 onward. (see note) T6028AAT if using D42.00-D48.01 or G06.00-G06.08 (see note) T6965AAF if using D42.00 onward or G06.00 onward (see note) T9053ANU if using G06.11-G06.12 (see note) T9057AET if using D42.00-D48.02 (see note) T9086ACE if using D42.00-D43.01 (see note) T9117ABB if using D42.00-D48.02 or T9117ABB if using G06.00-G06.14 or T9117ABG if using G06.15 onward. Note: T0346: The function needed in T0346 is required only if you SET RDF ON. T6028: The function needed is included in G06.09 to G06.11. T6965: The function needed in T6965 is required only if you SET ACTION ON. T9053: Fixes a problem introduced in G06.11 with the Dfreq queue counter. T9057: The function needed in T9057 is included in G06.00 onward. T9086: The function needed in T9086 is included in D43.02 onward and G06.00 onward. Required Hardware: NonStop RISC-based server Communications controller allowing file transfer from PC to NonStop Server PC with 486 or higher processor and all of the following: CD-ROM drive VGA or higher-resolution video adapter and monitor Microsoft Mouse or similar pointing device Required Firmware: NONE Required Software: T9050D42 for D4x.xx T9050G06 for Gxx.xx T9550D40 T9552D40 Microsoft Windows XP, Microsoft Windows 2000, Microsoft Windows ME, or Windows NT 4.0 or later. Microsoft TCP/IP stack and FTP client Manuals: 522303-005 ASAP SERVER Installation Considerations: Subsystem interruption required - Perform these pre-installation steps: 1. Ensure that requirements for using this product are met (see Section the Required Hardware and Required Software sections above). 2. Ensure that prerequisites for the installation utility and any product-specific installation requirements are met (see Section D Installation Prerequisites below). 3. Review the file USRGUIDE.PDF (in the subdirectory NSK_SW on this CD) containing the IPSetup User Guide, which provides instructions for using IPSetup, a utility provided on the CD that enables installation of Independent Products. You need Adobe Acrobat Reader (available on this CD) to read or print the IPSetup User Guide. 4. Decide whether you will use DSM/SCM to move files to Installation Subvolumes (ISVs) after files are placed on the workstation. Using DSM/SCM is optional, but is recommended when DSM/SCM is available. 5. If you are using the ASAP Extension make a copy of the file $SYSTEM.SYSTEM.ASAPUSER. FUP - VOLUME $SYSTEM.SYSTEM - DUP ASAPUSER, ASAPSAVE.*, SAVEALL 6. This SPR includes a change to the Objectives database file and also includes EDL changes for several entities. All records in any old ASAP databases need to be saved prior to installing this version of ASAP. It is very important that you save the records using the old version of ASAP, then restore them using the new version of ASAP. Please follow these instructions to save your current ASAP databases. From the central ASAP collection node: TACL> ASAP +VOLUME $SYSTEM.ASAPSAVE +MONITOR/OUT ASAPOBEY/, OBEYFORM +RANK/OUT ASAPOBEY/, OBEYFORM +MONITOR/OUT ASAPOBEY/ \, OBEYFORM +RANK/OUT ASAPOBEY/ \,OBEYFORM (preceding commands must be done for each remote node) Once data from all nodes has been saved then shutdown ASAP and purge the ASAP objectives database on each node. The objectives database file location is set with the SET OBJECTIVESDB command, or it defaults to $SYSTEM.ZASAP.DBOBJ. 7. Save ASAP CI and all EDL files if you have archived data with the old version of ASAP that you might want to view later. FUP - VOLUME $SYSTEM.SYSTEM - DUP ASAP, ASAPSAVE.*, SAVEALL - DUP ASAP?EDL, ASAPSAVE.*, SAVEALL - DUP ASAP?SYS, ASAPSAVE.*, SAVEALL - DUP ASAP?APP, ASAPSAVE.*, SAVEALL 8. Run IPSetup to place (move files from the CD to the workstation) and install (move NonStop Kernel files to correct ISVs) this product. If TCP/IP and FTP are unavailable, or if you have problems with automatic file placement, use the instructions in the IPSetup User Guide section "Manual Software Placement Using the IPSetup TACL Program" to manually place NonStop Kernel files. 9. Follow the post-installation instructions in Section B below, if any, after using IPSetup to place and install this product. - Perform these post-installation steps: 1. Invoke the INSTALL^TEMPLATES TACL macro to install this SPR's EMS template file(s) in the running system. The macro can be found in $.ZINSAIDS.TACLMACS or Support Note S92067B. For instructions, LOAD the macro and type: INSTALL^TEMPLATES /OUT / HELP 2. Run ASAP setup to update the ASAP subsystem with the following commands: a) VOLUME $.ZASAP b) OBEY INSTALL c) Perform "Full Install on this node" from the central ASAP database node. d) Perform "Remote Monitor Install" for any additional Licensed ASAP nodes that you wish to monitor. See Section 2 of the ASAP manual for detailed information regarding subsystem configuration. e) If you are using the same volume and subvolume location for the ASAP database files, you must delete the old database files before starting the new ASAP nvironment. FUP PURGE $..DB*! f) If you saved ASAP database records prior to the install then reload them now. From the same central node that you saved the data on please enter: ASAP + OBEY $SYSTEM.ASAPSAVE.ASAPOBEY 3. If you are using the ASAP Extension copy the duplicated file from the Pre-Installation instructions Step 1 back to $SYSTEM.SYSTEM. FUP - VOLUME $SYSTEM.ASAPSAVE - DUP ASAPUSER, SYSTEM.*, PURGE, SAVEALL 4. Start the new ASAP version. 5. When looking at ASAP data from earlier ASAP versions please be sure to use the old ASAP CI and EDL files saved to the $SYSTEM.ASAPSAVE subvolume if you performed the save step defined above. New Features: 1. [AAE] ASAP now provides support for user defined goals and actions. ASAP can now take corrective actions based on user defined rules associated with RANK/GOAL commands. A new GOAL command is an alias for the RANK command. Thus the commands GOAL and RANK both have the same meaning and can be used interchangably. A new ACTION option on the GOAL/RANK command provides the ability to associate command interpreter commands with actionable goals. For example, the following configures ASAP to automatically run FUP to SECURE the $SYSTEM.SYSTEM.USERID file if its RWEP security vector does not match the security objective for that file. GOAL FILE $SYSTEM.SYSTEM.USERID, RWEP=OOOO ACTION "FUP SECURE <#object>,'<#goal>'" Thus if the RWEP is not OOOO, the following occurs: FUP SECURE $SYSTEM.SYSTEM.USERID,"OOOO" A new ACTION RULE command allows a user rule library. For example the following creates an action rule named SECURE. ACTION RULE SECURE = FUP SECURE <#object>,"<#goal>" This rule can be used with the goal command above as follows: GOAL FILE $SYSTEM.SYSTEM.USERID, RWEP=OOOO ACTION SECURE More complex recovery actions are also possible using TACL macros and routines. For example: GOAL FILE $SYSTEM.SYSTEM.USERID, RWEP=OOOO ACTION TaclMacro Where TaclMacro is a rule such as: ACTION RULE TaclMacro = TACL MyMacro <#object> <#goal> See HELP RANK and HELP ACTION for more info. (SOLN 10-040912-9705) 2. [AAE] ASAP now supports Communication line monitoring. ASAP now collects both state and performance information for AM3270, ATP6100, CP6100, Envoy, EnvoyACP, Snax, and X.25 lines. The Comm SGP also supports goals and actions. (SOLN 10-040909-4950) 3. [AAE] The ASAP DISK SGP now reports the largest disk space fragment size available on a volume when using the raw command. User goals can be set on the FRAGMENT attribute and actions can be taken. For example the following statement indicates that the largest disk fragment should be at least 10mb in size, if not take corrective ACTION to run DCOM to defragment the volume. GOAL DISK, FRAGMENT > 10 ACTION DCOM <#OBJECT> (SOLN 10-020312-7324) 4. [AAE] The ASAP CPU SGP now reports the number of break points in use when using the raw command. User defined goals can be set on the number of break points. For example the following statement repeatedly generates a critical EMS event if the number of break points set in any CPU exceeds 20. GOAL CPU, BrkPnt <= 20 CRITICAL REPEAT (SOLN 10-040817-8953) 5. [AAE] SGP CPU placement. The ASAP ci SET command now allows you to specify the preferred CPU number where an SGP entity process should execute. Enter HELP SET for more info. Examples: SET DISK, CPU 1 SET EXPAND, CPU 2 SET FILE, CPU 3 (SOLN 10-020222-6888) 6. [AAE] Automatic Database Maintenance. A new SET DBMaxDays option allows ASAP to automatically maintain long term database history. Once set long term history is automatically maintained on a per entity basis. The SET DBMaxDays option controls days of history/entity. This option allows days, weeks, months, and even years of ASAP history to be automatically kept. See HELP SET DBMaxDays for more info. Examples: SET DBMaxDays 1 ! default max days SET DBMaxDays APP 14 ! 2 weeks SET DBMaxDays COM 30 ! 1 month SET DBMaxDays CPU 365 ! 1 year SET DBMaxDays DISK 7 ! 1 week SET DBMaxDays EXPAND 7 ! 1 week SET DBMaxDays FILE 7 ! 1 week SET DBMaxDays NODE 7 ! 1 week SET DBMaxDays PROCESS 7 ! 1 week SET DBMaxDays PROCESSBUSY 30 ! 1 month SET DBMaxDays RDF 0 ! 0 none SET DBMaxDays SPOOLER 30 ! 1 month SET DBMaxDays SYSTEM 365 ! 1 year SET DBMaxDays TAPE 7 ! 1 week SET DBMaxDays TMF 7 ! 1 week (SOLN 10-040909-9662) 7. [AAE] Database space analysis. A new DB command provides detailed disk usage analysis of the ASAP database. Per day usage, as well as total usage by entity are provided. The DETAIL option provides detailed info on the Begin and End time for statistics in a given DB file. See HELP DB for more info. Example: +DB 2004 CPU DETAIL $ASAP.ASAP2004.Z* FILENAME Y/M/D LAST-MOD RWEP Begin-Date-Time End-Time -------- -------------- ---- ---------------- ---------------- Z0115CPU 04/01/16 00:00 NUNU 2004/01/15 17:28 2004/01/16 00:00 Z0116CPU 04/01/17 00:00 NUNU 2004/01/16 00:01 2004/01/17 00:00 Z0117CPU 04/01/18 00:00 NNNN 2004/01/17 00:01 2004/01/18 00:00 Z0118CPU 04/01/19 00:00 NNNN 2004/01/18 00:01 2004/01/19 00:00 Z0119CPU 04/01/20 00:00 NNNN 2004/01/19 00:01 2004/01/20 00:00 Z0120CPU 04/01/21 00:00 NNNN 2004/01/20 00:01 2004/01/21 00:00 Z0121CPU 04/01/22 00:00 NNNN 2004/01/21 00:01 2004/01/22 00:00 (SOLN 10-040915-3892) 8. [AAE] ASAP node up/down EMS event. A new SET NodeDownAlert ON causes ASAP to generate node up/down EMS alerts. See HELP SET NodeDownAlert for details. Example: 12:03:41 \CENTDIV.$ZOOS *TANDEM.ASAP.V02 004000 ASAP ALERT ZOOS Node \ZERO Status Down (SOLN 10-040206-3046) 9. [AAE] Process entity now allows processes to be monitored by Guardian object filename or by the OSS pathname for OSS processes. You can also use wildcard process names to specify the processes to monitor. MONITOR PROCESS SALES\SERVER\$S* MONITOR PROCESS $SYSTEM.SYS00.TACL MONITOR PROCESS $SYSTEM.SYS00.TACL\## MONITOR PROCESS /home/servers/sales.exe This release also adds two new attributes to Process records: Count is the number of domains; and ACount is the number of attributes that are alerting when viewed at the detail level, or when viewed at the aggregate level is the number of domains that are alerting. (SOLN 10-040912-9349) 10. [AAE] Users can now specify custom event numbers for specific objectives using the RANK command. Custom event numbers in the range 6000-9999 are available for this purpose. For example in the following if the goal for Cpu 0, 1, 2, 3 fails, then the EMS event number for the failed goal would be 9000, 9001, 9002, 9003 respectively. GOAL CPU 0, BUSY < 90 CRITICAL 9000-9100 GOAL CPU 1, BUSY < 80 CRITICAL 9001-9101 GOAL CPU 2, BUSY < 70 CRITICAL 9002-9102 GOAL CPU 3, BUSY < 60 CRITICAL 9003-9103 Likewise if SET OBJECTIVESEVENTUP is ON, then event numbers 9100, 9101, 9102, 9103 would be generated when the goal is met. Enter HELP RANK for more information. (SOLN 10-040912-9350) 11. [AAE] ASAP EMS events that are created when objectives are not met now contain three additional tokens in the event buffer: ZASP-TKN-ASAP-STATE - the current state of the domain ZASP-TKN-ASAP-LASTSTATE - the previous state of the domain ZASP-TKN-ASAP-OBJECTNAME - the physical object name (if any) (SOLN 10-040912-9351) 12. [AAE] ASAP now records and displays the date, time and userid of the last person to modify an objectives record. This information is displayed in all RANK/GOAL statement output. Example: Cpu \ZERO Modified: 2004/06/20 16:43 by user 255,255 Status Critical Repeat Action: TACL Reload <#domain>,Prime Wait: 10 Repeat (SOLN 10-040912-9362) 13. [AAE] The STATUS command in the ASAP command interpreter now provides a timeout option for specifying how long and SGP has to respond to the status request. Enter HELP STATUS for more info. The default timeout has been reduced to 15 seconds. You can select another value, example: STATUS \Sierra TIMEOUT 5 (SOLN 10-030826-9164) 14. [AAE] A new SET REMOTESECURITY option has been added to the ASAP command interpreter indicating whether RemotePasswords are checked when shutting down or obtaining status information about remote ASAP monitors. REMOTESECURITY is ON by default, but can be turned off if desired. SET REMOTESECURITY OFF (SOLN 10-040909-9664) 15. [AAE] The AGGREGATE option is now the default when using the APP, FILE and PROCESS commands, so aggregate domains are now automatically displayed. A new NOAGG option has been added to suppress display of aggregate domains when necessary. (SOLN 10-040912-9380) 16. [AAE] The FILE entity now supports the ZLE concepts of logical grouping and aggregation. It also supports wildcard filenames and direct monitoring of OSS files. One to two levels of logical names can preceed a monitored filename to create hierarchical groups of files. Aggregate and aggregate-only domains can then be defined at any level of the grouping. Filenames can now include wildcard characters at the subvolume or filename level, and OSS files can be monitored by specifying the OSS pathname of the file. MONITOR FILE $DATA.SALES*.* MONITOR FILE SALES\DATA\$DATA.SUBV.SALES1 MONITOR FILE SALES\# MONITOR FILE /home/data/salesdata2001.db (SOLN 10-040912-9335) 17. [AAE] New startup parameters, MAXDOMAINS, MAXAGGS and MBYTES, have been added to the FILE and PROCESS SGPs to allow users to monitor many more objects than earlier ASAP versions. MAXDOMAINS controls memory space allocation for the domains read from the objectives database. The default is 999, the maximum is 32766. MAXAGGS controls memory space allocation for aggregate and aggregate-only domains that ASAP creates on your behalf if configured to do so. The default is 199, the maximum is 32766. MBYTES controls the memory space (in megabytes) for the pool used to store domains resolved dynamically at each interval from wildcard specifiers and object filenames. The default is 4, the maximum recommended size is 512. SET FILE PARAM "MAXDOMAINS 10000 MAXAGGS 300 MBYTES 128" SET PROCESS PARAM "MAXDOMAINS 5000 MBYTES 64" An EMS event is generated if space gets depleted from any memory region. New information is provided about the number of monitored files and processes, and about pool space utilization in the FILE and PROCESS SGPs, in response to the MONITOR , LIST, DETAIL command. +m file,l,d File \Centdiv Num Domains: 41 Max Domains: 20000 Num Files: 17384 Num Aggregates: 12 Pool Entries: 17359 Pool MaxEntries: 111891 Pool High Mark: 28339 RankState: Active Sample Time: 2004/08/04 14:07:00 Last Error: 0 . . . +m process,l,d Process \Centdiv Num Domains: 27 Max Domains: 20000 Num Processes: 839 Num Aggregates: 5 Pool Entries: 834 Pool MaxEntries: 25275 Pool High Mark: 1413 RankState: Active Sample Time: 2004/08/04 14:03:01 Last Error: 0 . . . (SOLN 10-040912-9375) 18. [AAE] When you monitor a FILE or PROCESS domain that contains wildcard names, or a PROCESS domain by referencing the object filename, then ASAP will automatically add an aggregate-only domain. If you do not want aggregate-only to be specified for the wildcard or object filename domain, then you must manually remove the aggregate-only domain after first adding the original domain. Please be sure you understand how many records you will be writing to the historical database before removing the aggregate-only domain, however, to limit the amount of historical data that ASAP saves for each entity. + M FILE + M FILE $DATA.*.* File \Centdiv.$Data.*.*, On + M FILE On - $Data.*.* On - $Data.*.*\## + M FILE $DATA.*.*\##,DEL File $Data.*.*\## deleted. + COMMIT (SOLN 10-040912-9378) 19. [AAE] You can enter two asterisks at the end of a FILE or PROCESS domain name to indicate that the MONITOR or RANK command should be applied to all domains beginning with that name. A single asterisk, which can be used for this purpose when entering commands against other entities, can otherwise be confused with actual wildcard domain name specifiers for the FILE and PROCESS entities. + RANK FILE $DATA** + MONITOR PROCESS $A** (SOLN 10-040912-9384) Problems Corrected: 1. [AAE] SYMPTOMS: The status command can time out. CONDITIONS: Would occur when an SGP is busy. LIKELIHOOD: Unlikely (SOLN 10-030826-9164) 2. [AAE] SYMPTOMS: The ASAP Expand SGP does not display the correct PIN for any Expand line handler executing with a PIN greater than 255. CONDITIONS: Would occur when an the Expand IOP is running at a Pin > 255. LIKELIHOOD: Certain (SOLN 10-030826-9165) 3. [AAE] SYMPTOMS: The ASAP DISK SGP did not allow decimal values for setting disk queue length objectives. CONDITIONS: Would occur when the user attempted to set an objective on the queue attribute as a decimal value. LIKELIHOOD: Certain FIX-INFO: Changed the ASAP2SYS EDL Disk Entity typedata from an INT to a REAL64, added the format metric and set the value to 3.2. (SOLN 10-040915-9828) 4. [AAE] SYMPTOMS: The ASAP CI Command status does not display SGP's that did not start, due to setting an incorrect object file name or in the unlikely event if an SGP could not start up. CONDITIONS: Occurs when an SGP is stopped or has abended. LIKELIHOOD: Likely (SOLN 10-040915-9818) 5. [AAE] SYMPTOMS: The ASAP monitor process would attempt to start SGP's constantly when an SGP process is stopped by the user or in the unlikely event and SGP abends. CONDITIONS: Would occur when the SGP was shut down for any reason. LIKELIHOOD: Unlikely (SOLN 10-040915-9822) 6. [AAE] SYMPTOMS: The CPU attributes chit, and disp did not display the correct EMS message when the user specified objective for either attribute was not met. CONDITIONS: Occurs when the an objective was set for chit or disp. LIKELIHOOD: Certain FIX-INFO: Corrected the EDL file ASAP2SYS by adding the format statement for both the Chit and Disp attributes. (SOLN 10-040915-9829) 7. [AAE] SYMPTOMS: EDL mistmatch warning when using RANK OBEYFORM. CONDITIONS: Occurs when user enters RANK OBEYFORM. LIKELIHOOD: Likely (SOLN 10-031205-1759) 8. [AAE] SYMPTOMS: Aggregate codes AVG and CNT did not compute correctly for the Process Busy, MSent, MRecvd and PFaults attributes. CONDITIONS: Occurs when objectives are set AVG or CNT. LIKELIHOOD: Likely (SOLN 10-040120-2522) 9. [AAE] SYMPTOMS: ASAP CI exhausted available PFS space. CONDITIONS: If Process Detail windows were left open in ASAP Client. LIKELIHOOD: Likely (SOLN 10-040120-2511) 10. [AAE] SYMPTOMS: Objective comparisons on the TMF TPS attribute could be incorrect or the TPS value shown in ASAP alert events could be incorrect. CONDITIONS: Occurs when objectives are set on TPS. LIKELIHOOD: Likely (SOLN 10-040128-2750) 11. [AAE] SYMPTOMS: Difficult to know which attributes support objectives. CONDITIONS: Occures when the CI command show is entered. The user has to look for an attribute with a state pair. LIKELIHOOD: Likely FIX-INFO: The SHOW command now marks attributes that can support objectives with an asterisk. (SOLN 10-040326-4551) 12. [AAE] SYMPTOMS: ASAP Collector process stack overflow abend. CONDITIONS: Occurs if the collector is started during cleantime window. LIKELIHOOD: Unlikely FIX-INFO: Data stack size increased. (SOLN 10-040416-5146) 13. [AAE] SYMPTOMS: ASAP Disk SGP did not correctly write the correct state when an I/O error occurred on the write to the collector. CONDITIONS: Would occur when multiple disk updates occurred and the ASAP collector was performing its DB self cleaning routines. LIKELIHOOD: Likely (SOLN 10-040303-3004) 14. [AAE] SYMPTOMS: ASAP CPU was not using the percentage of TLE's in use, but was using the actual number of TLE's in use, causing incorrect thresholds to be computed for the TLE attribute. CONDITIONS: Occurs when the an objective was set for TLE. LIKELIHOOD: Likely FIX-INFO: Use TLEUSE% in call to rank_value_. (SOLN 10-031204-1721) 15. [AAE] SYMPTOMS: ASAP and the ASAP modules have not been accelerated. Preventing ASAP and the ASAP modules from executing at the best possible performance levels. CONDITIONS: Occurs when the ASAP environment was running. LIKELIHOOD: Likely (SOLN 10-030822-9091) 16. [AAE] SYMPTOMS: ASAP Expand SGP did not report the state correctly for the attribute dframsnt or dframrvd when a configured threshold for either attribute was exceeded. CONDITIONS: Occurs when the user set an objective on drfamsnt or on dframrvd. LIKELIHOOD: Likely (SOLN 10-040803-8518) 17. [AAE] SYMPTOMS: ASAP CPU SGP did not report the state correctly for the attribute PCB% or PCBX% when a configured threshold for either attribute was exceeded. CONDITIONS: Occurs when the user set an objective on PCB% or on PCBX%. LIKELIHOOD: Likely (SOLN 10-040817-1135) 18. [AAE] SYMPTOMS: Corrected the Disk SGP not to report path state on non-existent backup controllers. CONDITIONS: Occurs when a disk volume does not have a configured backup controller. LIKELIHOOD: Likely (SOLN 10-040826-9276) 19. SYMPTOMS: The RDF SGP will abend and create saveabend files when communication is lost with the backup node. CONDITIONS: NONE LIKELIHOOD: Certain (SOLN 10-020508-8800) Known Problems Remaining: NONE