Home

User Guide GUI

1. 83 DETAILED FILE ANALYSIS GRAPH 4 0 c ccccececececececevecevecevevevecevevecececevecececevecececevecevecesecevececececececececececececececesececesesesecevevers 83 DETAILED FILE ANALYSIS GRAPH 5 ccccecececesesevevevecevevevevevevevevecevevevevecevecevevevecevevesecesesesecesecesececesececececececevecevssesesevesess 84 DETAILED FILE ANALYSIS GRAPH 6 rorvvnvnrennnnrnnnnnnnsnnsnnrnnnnnnennssnnrnnvennnsnnsnnnnnsnnsnnsnsnnnnrnenensnnnvsnnrnnnennesnnsnnnnnsnnsensssnnnnrvenensenee 85 DETAILED FILE ANALYSIS GRAPH 7 cccecececececececevecesevevevevevevevevecevevevecesesecesecevesevevesesecesesesecesesesesesecesececesececesesesesesevesess 86 DETAILED FILE ANALYSIS GRAPH 8 sese eese sese E DEEE eane E DEERE n eese eese seen 87 DETAILED FILE ANALYSIS GRAPH 9 0 ccccecececesecevevevecececevevevevevevevecevecesecevecesecevecevecesesevecesesecececesesesesesececesecevecevesesesevesees 87 DETAILED FILE ANALYSIS GRAPH 10 88 DETAILED FILE ANALYSIS GRAPH 11
2. sese 64 WARNING ON REOCCURRING ABORTS 64 RUNNING IN MONITORING sesosevsvesssevsesssnsvssensnsvesssnsesensensesensnsesssnennesnsnnesssnsnsenssnnsesennnnsesennnneessnessennsnnenssnnnseeee 65 RAISING ALERT MESSAGES ON YOUR LOCAL WORKSTATION IWS s cccssssscecsssceceeseeeeceseececseneececseeeeceesaeeeeseeaeessseseeeees 65 RAISING ALERT MESSAGES AS EMAIL SMS 66 RAISING ALERT MESSAGES AS REMEDY TICKETS ccccccccccccccccccecccscscececscceseseeceesescsesesesesesesesesesescceseseseeeececseseseseeeeeeeses 67 RAISING ALERT MESSAGES ON THE 67 RUNNING VDA IN BACKUP 68 SETTING REPORTS DIU HC 69 COMMAND LINE OPTIONS 70 SAVING ABORT REPORTS TO DISC
3. PEDCAITID453 LS EALAIN LH FEDOUTID SZ ETER PM 5 a fa By combining the Abort Reports with Report Filters you can use The Visual Dump Analyzer to monitor specific programs or functions Especially in cases where modified programs are placed on a test system before eventually moved to the production environment you may wish to use The Visual Dump Analyzer to ensure you are informed on every abort taken by these programs Showing Abort Totals The Abort Totals Report provides an overview of how many different types of aborts have occurred during the previous days In the Abort Totals Report each line shows the number of occurrences that have occurred for a specific abort type The Abort Totals Report is initially displayed with the abort type having the most occurrences on the top line This report gives you a quick overview of what is the most common abort or immediate problem allowing you to direct your attention to where it is needed most he Yeu Dump Beak LG Today s D i M ALL U3 31 LES I MER TIMAR aman TIMAR 31MAR TIMAR I MER aman TI FAR J MER amen TIMAR 156 19 18 5967 99009 BOT 68000 PEIG 2 OT 5259 53 185572 amp 5 65
4. 0321 SUBROUTINE SCONT 0323 DMPDDH 1 LINE DOTS LINE 28 49 CONTINGENCY ANALYSIS CALL PRGSAV SAVE 0328 C EXPLAIN REQUESTE SPCERR CODE IF SPCERR NE O 0R DMPTBL CNTPKT NE O THEN 0330 C qj DEBUG CODE FORCE ABORTS IF SPCERR EQ 123456 THEN SRCLIF 1 SRCLIT FORCE CONTINGENCY 5 ZERO DIV ELSE IF SPCERR EQ 123457 THEN LINE 4 SPCERR FORCE SUBSTRING ERROR ELSE IF SPCERR EQ 123458 THEN CALL XBCA 25 100000 FORCE DBA ERROR 0337 CDML IF FALSE THEN TEST CARGO DMS MACROS 0338 CBUG CALL PRTADP MYTEST SPCERR 1 TEST CARGO DEBUG MACROS 0339 CDML ENDIF amp TEST CARGO DMS NACROS ELSE IF SPCERR EQ 123459 THEN By default TRAPS that are set on line numbers will force a new abort the first time the line number is executed However you can alter this setting by right clicking the line and selecting Set Abort Count This will open the below dialog where you can control how many times the line must be executed before a new abort is forced or deselect the request for a new forced abort Set Abort Count Force an abort when this line has executed specific number of times Abort after this many executions 1 If the request to force a new abort is deselected the line number TRAP will remain set and will result in the TR
5. IF exp EQ IBFUNC THEN VALUE IBFUNC PAR1 ELSE IF exp EQ IBLNSZ THEN VALUE IBLNSZ PAR1 ELSE IF exp EQ IBFCCD THEN VALUE IBFCCD 1 ELSE This logic ensures the actual FTN defines are used when an expression is being resolved Once a Resolve Program is generated it should be treated as any other application program Further when a proc is updated the associated Resolve Program must be compiled and mapped Finally when defines are added or removed from a proc the associated Resolve Program must be regenerated In order to generate a Resolve Program from a proc all define names must be prefixed with the proc mnemonic e g all defines within IP F must being with IP Furthermore the proc must be a standard USAS proc that has the xxFSPEC and xxFDEF include areas Defining Resolve Programs Defining a Resolve Program is a two step process The first step informs The Visual Dump Analyzer of which procs are to be handled by the Resolve Program whereas the second step generates the source code proc SEDUSR F that enables The Visual Dump Analyzer to call the Resolve Program Step 1 Associating procs to Resolve Programs This step defines the Resolve Program itself and associates one or more procs to it After copying SEDGEN BATCH from SYSABS into TPF simply execute it with the following input gt XQT SEDGEN gt PID number as requested
6. s 89 WHATSF D VALEUE rtc eS Uie Uer dares 90 FREESPAGE nsi AE EAA 91 93
7. 0 THEM 0330 CODE FORCE ABORTS 03311 IF SPOERK EQ 120456 THEW 0332 SRCLIF i SRCLIT FORCE CONTINGENCY 5 ZERO DIVJ ELSE IF 57 THEM ELSE IP SPCERR EQ 1223450 0336 CALL 25 100000 B FORCE DER ERROR 0337 IF i FALSE THEH Em TEST CARGO DNS MACROS 0338 CHUG CALL FRTADF ETTEST SPCERE 1 BH TEST CARGO DEADE MACROS 0339 CDI S TEST CARGO DNS MACROS 0340 ELSE IF SPCIRR EQ 123459 THEN 0341 IDX Hij CBAREA ADDRS CBAREA 1 4 157 FREE ENTRY 0342 CHARER IOX 0 B DESTROY FREE CHAZM 0343 CHAREA IDE i1 0 DESTROY FREE CHAIM 0344 1 O DESTROY FREE CHAZM 0345 CALL 25 1001 CAUSE TRE ABORT IDA INTEGER LOCAL 4 5113 5558150973 x INTEGER LOCAL 4 5156120 Decimal 11430298155 ACBEDD 24 3 INTEGER GLOBAL 4 516216 Decmal 34 1 12955650 ADR INTEGER 4 515773 Dedma 3303372 X0 CALABS CHARACTER 12 GLOBAL 12 515543 Asti CALREL CHARACTER 12 GLOBAL 12 5 5745 Asi INTEGER GLOBAL 515775 Decimal n oO INTEGER GLOBAL 515764 Decimal 0 COTS CHARACTER O0 GLOBAL B 5156067 Asti In this example the TRAP has been set on line 334 and the ADR variable has been requested to be SNAPPED when line 334 executes Now all you have to do i
8. 51 GENERATING RESOLVE 5 51 ERROR CODE LOOK UP is LEN 52 THE VISUAL DUMP ANALYZER LOG FILE cccccccscssssssssscccsssssssccecccescsssscecccecscsssccececccsscsseccceeccescssescccececsssscsscess 53 FORTRAN OPTIONS PSE 53 BASIC MODE FORTRAN 53 EXTENDED MODE UCS OPTIONS 53 MONITORING USAS APPLICATIONS eeeessssvssssssssessnsvesensnnnsnsnssnesnsnsvsennsnsvssnennnsnsnnnnesnnnsesennnsnsennnnsnsennnnsnnsnnnnssesnnnsnsennnnee 54 ABORT REPORTS OR NR 54 READING ABORT REPORTS FROM THE MAINFRAME evveosesessssvnvnvennsensnnnnnnvnnenessnnnsnnnnnnennsnnnnnnennenesensnennennnsenensnnne 54 ABORT REPORT TYPES R 54 SHOWING ABORT REPORTS aerisire ete ear edlere enurese Pipe vbt e erae Rp vas ea eva ER tr shes eese 54 SHOWING BORT TOTALS Tu 55 CLASSIFYING ABORTS AS IDENTICAL OR 56 SHOWING ABORT SEVERITY REPORT isisssssascsscecsndssensdoessuevaecssusadevsvevebevyacdoedsvlvapevsesades
9. 70 OPENING ABORT REPORTS SAVED ON DISC eeooovsvvveeesesnnvnvnsenessnnnnvnvenssnnsnnnnnnensenessnnnennennsenssnnnnnnenssensnnnnnnnennnsenennnnne 70 EXPORTING ABORT REPORTS issssssssseccdsissscssecsiesseccscsessecesessccssectececcessosceseses seovbavecduoessesceosessecscssescusesevecsebessssestecseeseooesse 70 EMAILING ABORT REPOR US wesssesiesscesssc cssssscesbesveciscscsscssosscsscssseuectucesssscvssees ed oa oe uo e ops Eo eo Re NE NEU VD oe eS EUER 70 THE VDA ADDRESS BOOK qe 71 THE VDA PROGRAM BOOK s sesvesversnvenversnsenverensenverensnnverensensnennsenensnnversnennvenensensensnevnversnsnnverenennvevsnssnsnnsennnennsessnennsensnenne 72 m MONITORING FREESPACE FILES 5 ea aae aene Seen r Pe a oa e ee So Co neo se nee po EF an a oae aono Do ee ua Uo eaae UP Ue Gase ne ooa SUR ES Pe GE Oe ea ea I PEPPER NUR 73 READING FILE REPORT FROM THE MAINFRAME eee eren neon eee tn sanos sette tetas aste tese sn asses e esee sese eese etas 73 FILE REPORTS AM EsS 74 FINDING FILES RR 75 SETTING FREESPACE FILES WARNING LEVELS 00cceeeeeeseeeseeeseseseeeseveseveseeeceseseseseceseceseeesereseeeseeeseeeseseseteseseseseceseseeesere
10. Cancel Use this dialog to change the period using Quick Select on the left or specify exactly what period is desired using Select Specific Period on the right This information is gathered by The Visual Dump Analyzer Freespace Scan process called FSSCAN This process runs through all files daily and records this information so it can be presented in this graph See Freespace Scan Page 85 Detailed File Analysis Graph 6 The sixth graph informs of the record fragmentation per record type Due to the nature of FCSS files all files having more than one record type are likely to get fragmented to some extent However some files may become much more fragmented as it can be difficult to estimate how many records are actually fragmented and how many are truly free and allocatable This graph shows two bars for each record type with the first bar showing the number of free records in GREEN and the number of Release Only records in b Value 4 65 7 Graph 6 The second bar shows the number of logical records that are fragmented in The fragmentation count is found by adding all the basic records that exist but cannot be combined into a logical record of the given type This fragmentation count is then converted into logical records and shown as the value of the second bar Essentially the count given by the second bar is the number of logical records that could have been allocated had there been no fragmen
11. 19 THE EXPRESSION WINDOW 20 THE DRA WING WINDOW 21 THE PROGRAM CALL STACK WALKBACKR csscccccssssecessseeecssaececsesaececsncecnesaeeecsesaeeecaeeecsssaeeecsesaesecseaeeceeseeessesaeeeeseeaeenens 22 THE DATA DISPLAY WINDOW sinistre est tenace sseasesescuccesonseoancesecssesessabscossesssbesdeenvedecssvseeseeensessevsosence 23 RESCHEDULING THE INPUT MESSAGE eveesesessvvnvnvesesensnnnnnnvnsenessnnnnvnvenssnnnnnnvnsennsensnnnnennnsenensnnnnvnnenssensennnnnnennnnenensnnne 25 RESCHEDULING NORMAL TERMINAL TRANSACTIONS eeenanenenenennnrnrnrnrernnnnnnennnsrnnsnnnsnnnsnnnnnsnsnensnnnsnnnsnensnsnenensnenenenerenenenesesenseee 26 RESCHEDULING HTH MESSAGES vile eee 26 RESCHEDULING SERVICES ae 28 EDITING OR FINDING THE INPUT 28 SCHEDULING EDIFACT MESSAGES DIRECTLY USING EDIT 29 SETTING PRA GES pH 29 SETTING VISUAL ADVANCED SNAPS hehehe hehehe hehehe torotoro hee nene ne eene tree nene nene nnn 29 CONTROLLING THE AP DBA eee deret ek eee eese tede eue e EE eek Eee eye ea pe e Ee YEN E RN Yee Ee Ee
12. Page 62 Similar Aborts Alert 1 The Alert Message Analysis may find aborts that are not completely identical but are very similar in nature with these aborts having also caused an Alert Message to be raised These similar aborts are shown here See Classifying Aborts as Identical or Similar Suppressing Alert Messages If an Alert Message has been raised and the aborts are still occurring the new aborts may reach the same Alert Message Warning Level again very quickly To avoid raising the same alert repeatedly Alert Messages will be suppressed if the Alert Message Analysis detects that an identical alert has been raised in the past hour When the same Alert Message Warning Level is reached it will cause a new Alert Message Analysis to be produced but the Alert Message will not be raised For these new aborts The Alert Id column in the Abort Report will be updated with the Alert Id number but the number will be shown in parenthesis e g 3 This notation is used to inform that the Alert Message Warning Level was reached again but the Alert Message was suppressed Page 63 Configuring Alert Message Warning Levels Every time the Abort Report is refreshed The Visual Dump Analyzer will check the new aborts and alert you if it detects a pattern in the aborts or if the number of aborts grows too large The Alert Message Warning Levels are used to customize the frequency of aborts and the pattern of the aborts that yo
13. Select period m Select Week Select Specific Period C 07 January 09 January 131 2 2007 31 December 06 January 24 December 30 December To date 001 2008 17 December 23 December Once the period has been selected The Visual Dump Analyzer will retrieve all Alert Messages raised on the SPO from the VDA SPO Agent VdaSpo exe The VDA SPO Agent will return ALL Alert Messages back to The Visual Dump Analyzer GUI so it can create a complete Statistical Report that contains ALL messages even those that are not raised from this instance of The Visual Dump Analyzer Page 57 Once All Alert Messages have been retrieved for the selected period The Visual Dump Analyzer will organize them according to USAS application and Abort Severity Further it will show how many of the Alert Messages occurred during normal working hours off working hours and during weekends Complete Report from PROD E Mode ALL 08 01 09 15 33 oj x ALL SAFE LOW MINOR NORMAL HIGH Total RES SAFE LOW MINOR NORMAL HIGH Total SYS SAFE LOW MINOR NORMAL HIGH Total TKT SAFE LOW MINOR NORMAL HIGH Total Aborts 35 87 0 265 0 38 Aborts 29 21 0 118 0 168 Aborts 5 0 0 31 0 36 47 45 Pct 100 Pct 12 12 Types 15 16 Pct 100 Pct 11 39 56
14. the File comteina 83 257 3 fres basic marked Release Only char can be upped subFile Info SubCile EF 01202 PETI Sub ile EI 02202 PET MASTER DATA IMP Subtile EE 03202 PCI EASTER DATA Subile Eng 04202 FOI TELETYTTE LKDEX Subliler FR 05202 PCI TELETTTE DATA Subtile 07202 PEI SEGHENT FILE Subfile EJ 010202 FCI TIRE TABLE INDEX SubCile FE 011202 PCI TABLE DATA Subfile FG 012203 PLI FLT F R INDEX OVERFLOW SBub ile ELM 016202 PCI LEG HEAL INFO FILE Subtile 019202 PCT SIN IMFURMATIUM FILE FLIGHT HER INDEX Analysis from the Address Book Further all people in the Address Book that are identified as being responsible for FILES are selected and made part of the Phone List Reason This section informs of what file has caused this Alert Message The analysis is natural language text describing the file situation in as much detail as possible The text will depend on the file and the setting See Configuring Alert Message Warning Levels for Freespace Files Page 79 Subfile Info This section describes the data that is within the file that is becoming full Because TIP file numbers are usually not as helpful when analyzing this type of problem the actual subfiles and their data content are listed in order to help determine the consequences that a full file may bring Once an Alert Message for a fr
15. 3 User Guide for THE VISUAL DUMP ANALYZER GUI Version 5 0 2008 Visual Data Aps All Rights Reserved 9 r To receive further information about Visual Data products please contact Visual Data ApS Visual Data ApS Attn Lars Kruse B ggild Attn Gary J Sowada Hvidtj rnen 36 12181 Highway 27 DK 2791 Drag r CPH Little Falls MN USA 56345 Denmark Tel 1 320 632 6200 Tel 45 32 94 31 94 Fax 1 320 632 6240 e mail support visualdata info e mail Sales visualdata info Internet www visualdata info Internet www visualdata info O 2008 Visual Data ApS All Rights Reserved Page 3 User Guide for The Visual Dump Analyzer 2008 Visual Data ApS All Rights Reserved Overview The Visual Dump Analyzer is an innovative debug tool developed for the Unisys USAS environment It is designed to simplify and expedite the complicated process of solving a mainframe dump abort by intuitively displaying virtually all relevant information in an easy to use graphical environment all with point and click and drag and drop ease Focused on assisting both skillful and novice application programmers alike The Visual Dump Analyzer eliminates the tedious and error prone task of converting symbolic variables and lines of code to their absolute addresses within the dump That is instead of spending considerable time scouring over a raw octal dump to find a variables value you can now simply click on t
16. click ge dbl click Address Rorsgi By using the Pop up menu associated with this window you can toggle whether an area will be included in the drawing or whether is should be decomposed into its specific parts The drawing can be viewed in a Fixed Layout where all blocks are the same size Proportional Layout where block sizes are related to the actual memory size or Adjusted Layout where a combination of these is used This feature is also adjusted with the Pop up menu 01496044 0164107 The Drawing window uses color codes for each memory area so it can be easily recognized Moreover errors that exist within memory such as FCSS errors or Corrupt Free Chain will be color coded R ED so they can be quickly perceived within the drawing zi 0171054 You can also use the Drawing window as an access pad for changing the contents of one of the other windows By simply dragging an instruction or data block from this drawing and then dropping it into another window you will be able to view its contents within a Source Code or Data Display window This drag and drop feature is handy and addictive If you wish to quickly view the BCB in a DBA or the contents at the beginning or the end of a memory area you can click the start end address shown and the first last six octal words will be displayed in a small Pop up box In general the Drawing window provides an ideal way of viewing memory at the time of an abor
17. 272 Feti Bees 104 FBCxD 777 7333 7 s2223ddd 8BBBBBEEEREIGg0SdSBBBSBEEERRISSOOOBOBBBB BBBEERERIS3dd88B TT Y Y TTTTTTTITTT 77 7000855830000 f23258S88BBBBBEEERRIISSSSSSSHSBSBBEEERERRI338888BBBBB BBBEEERERESSSSS8B8BBH D LM ESE Edu i zi Braue 1 38 gt Record allocated by record byger 1 8 1 Record E fres sononding ba Ene bitmap sndiihe Fille marked az 1 Record E se scconding bo the biten but the Alle contains USAS CONTROL WORDS MO Recd is Frese accorde bo tha b map but Ehe File is missing PREE BIT PATTERN Record i allocated according bo Ehe Hitman but Etes File contains FREE DIT FLTTERK E Record slocsted scoonding bo Khe bitmap but the File is missing USAS CONTROL ORIG Enter the number zero relative of the BITMAP you want to inspect press Read Bitmap and the data related to this BITMAP will be displayed Page 90 If the file contains a D value the BITMAP is split according to it to show how the records are allocated within the BITMAP Each logical record is represented by its record type number 1 gt 8 to show how the basic records are actually allocated You can view this BITMAP display for a file while using the What If D value feature to determine what the
18. IOPMSG 7 INTEGER GLOBAL 4 145506 Octal 052052052052 IOPTXT CHARACTER 28 GLOBAL 28 145506 Ascii OUTP LIT I NHIB ITED IOUTPT 20 INTEGER GLOBAL 4 145515 Decimal 0 LEVEL INTEGER GLOBAL 4 143401 Real 1 423194e 045 LWC INTEGER GLOBAL 4 143411 Binary 100000001001100000101 LWCO INTEGER GLOBAL 4 143461 Decimal 0 vi Clicking on some of the cells within the table will result in the contents being adjusted If for example you click on a variable that is an array the array will be expanded with all its values being shown Clicking on it again will reduce the variable to one entry in the table If you click on a cell within the Format column the value of the variable will cycle through a wide range of data types including decimal octal ascii fieldata real date binary and logical Finally if you click the value of a variable the value will be shown in a small box adjacent to the cell value will be displayed in octal decimal ascii and fieldata By right clicking and displaying the Pop up menu of this window you can select deselect the type of variables displayed within this window Note that static variables here refer to variables defined within the static areas of the d bank In this Pop up menu you can also choose to display the AXR registers Page 20 The Expression Window The Expression window allows you to request the value of an expression The expression you enter can be as simple as the name of a define
19. 52 7 484 47 3 54 540 52 7 484 47 3 55 576 56 3 448 43 8 Table 1 D value splits on BITMAP size 1024 As you will note from this table changing the D value from 50 to 49 or 48 would not have any effect on the actual D value used by the FCSS freespace file handler The D value would have to be changed to 47 to actually create an effect To simplify the selection of a new D value the D value PCT column has been updated to only contain the percentage values that actually cause an updated D value Freespace Scans The Visual Dump Analyzer has its own Freespace Scan batch job called SEDFRS BATCH This program has two main features 1 Toscan all freespace files and save counts of records that are used for each subfile 2 To verify the control information for freespace files and fix any discovered errors The first feature to scan all freespace files and save counts is started in HVTIP by entering the following RFIL FSSCAN This input will start The Visual Dump Analyzer Freespace Scan batch job which will scan all the freespace files on the system and save the analysis in file USAS SED FSSCAN Page 92 This input should be entered into Timecall and be run at a predetermined time each day It will enable The Visual Dump Analyzer to produce the fifth graph in the Detailed File Analysis Report which states how many records of each record type are allocated for a subfile in a shared file The Freespac
20. INTEGER GLOBAL 4 515775 Decimal 0 INTEGER GLOBAL 4 515764 Decimal 0 CHARACTER 80 GLOBAL 80 516067 Ascli vann ous vane onee s EDITFC CHARACTER 4 GLOBAL 4 516064 Ascii EDI INTEGER GLOBAL 4 515755 Decimal 21878821189 FDSPAC INTEGER GLOBAL 4 516122 Decimal 5453926725 CHARACTER 40 GLOBAL 40 516052 Asci FTNLIN CHARACTER G GLOBAL 8 515634 Ascii GETHNT LOGICAL GLOBAL 4 515661 Logical FALSE CHADACTED AN an 5165723 LISAS HEEN This will cause the variable to be highlighted in GREEN indicating that the SNAP is active By default the SNAP will contain the number of words occupied by the variable however you can change this by right clicking the GREEN line and selecting Set Number of Words to Snap The SNAP can be removed by again right clicking the GREEN line and selecting Clear Breakpoint Trap Snap Setting SNAPS on DBAs PDBs or a fixed address To set a SNAP for a DBA PDB or a fixed memory address drag the data to the Data Display Window and right click the word you want to SNAP This will open a Pop up menu where you can select Set Snap and the SNAP will be set 08 DBA 733600000003 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 114113102101 040040040040 040040040040 040040040040 040040040040 040040040040 0400400400
21. Live COGN ZDOD FROG IIL PROD E Too mere 127 denice short eve been detect d Tres applications bring phos Cfa PAS now Lire pow 2008 13801817 PODE The et vD Sere i un at Aeg again Trus beach DA os up ian CONN DDO The FOA Backup Saree p met namia Fiame boni oe oe ee To view the entire text for an Alert Message simply click the SPO ID in column 1 and a yellow Pop up window will be displayed showing the entire Alert Message To close this Pop up window just move the mouse outside the windows boundaries and it will close This report provides a quick and accurate overview of the Alert Messages raised as Alarms on the SPO during the period covered by the Abort Report you were looking at See Raising Alert Messages on the SPO Page 59 Customizing the Abort Report Layout An Abort Report contains a wide range of information some of which may not be of interest to you By clicking the column header and selecting Hide the column can be removed The width and location of individual columns can also be changed by dragging the columns to their new location Finally the justification within the column can also be modified Once you have created the layout that you like you can make it persistent by selecting Tools Column Layout Save Column Layout In this way you can create and save a layout for each of the 3 report types To quickly set all
22. Pct Pct 17 18 Alerts Pct 0 42 0 57 0 100 Pct 0 14 0 0 0 14 Pct 14 14 Pct 14 14 Off Hours 0 1 0 0 0 1 Off Hours Off Hours Off Hours Pct Pct ooocon Pct ooocon Pct 50 50 By displaying the number of times USAS application people have been called on duty outside of normal working hours and during weekends The Visual Dump Analyzer provides a method of keeping track of how often aborts within the USAS applications cause application people that are not on site to be called in By organizing the aborts into different types See Classifying Aborts as Identical or Similar these statistics can also provide guidance with the number of times the same USAS abort has caused problems and how often application people have being called on duty due to new aborts See Raising Alert Messages on the SPO Page 58 Showing SPO Alerts The SPO Alerts Report shows a history of all the Alert Messages raised on the Unisys operator Single Point of Operation SPO console Even though the SPO Alert Messages were not raised from this instance of The Visual Dump Analyzer ALL the SPO messages raised during the period covered by the Abort Report will be retrieved from the VDA SPO Agent VdaSpo exe The VDA SPO Agent is responsible for actually raising the Aler
23. To do this first add yourself to the Address Book then select Tools Settings Report Settings and set the User Identification to your name If you dont identify yourself to VDA you can still use all functions related to dump analysis however more Abort Report functions will be restricted as they are only allowed by identified users E g Only identified user can change the Abort Severity from NORMAL See Abort Severity and Showing Alert Restrictions Among other components the Address Book is used to construct the Phone List in Alert Messages If you do not want to be included in this Phone List check the Currently not available for calls option and you will be exempt from the generated Phone lists while still being identified within VDA Moreover you can use this option when you don t want to be notified by the Unisys Center Operators when Alert Messages are raised on the SPO The VDA Address Book is also used is in the Action by column in the Abort Report This column provides the name short name from the Address Book of the person working the abort Therefore when you are viewing an abort you can mark it as being handled by yourself thus allowing others that are viewing the Abort Report to notice this and avoid spending time on the same problem You can change the value of this column by double clicking it and entering a dialog that allows you select a different person from the Address Book Page 72 T
24. When a single file is only selected the detailed graphs are shown over multiple lines to allow for as many graphs to be visible at a time In the Pop up menu you can select either Show Full Files or Show Files This will cause either all full files or simply all files to be automatically included in the Detailed File Analysis When a file is included in the Detailed File Analysis it can be excluded by use of the Pop up menu The Detailed File Analysis contains a number of bar graphs with each informing about different aspects of the specified file To obtain detailed information on the value depicted by a bar click on it and a yellow box window will display the specific values of the bar along with their meaning Single clicking the white space of a detailed graph will display a yellow box window informing of the basic information of the file along with subfile information Double clicking the white space of a detailed graph will cause the graph to toggle between percentage values and actual values Detailed File Analysis Graph 1 The first graph informs of the amount of Free Basic Records Recs in the file When an FCSS freespace file contains a D value that is not 100 the file is actually divided into two logical files the first being below the D value and the second being above the D value In this case The Visual Dump Analyzer will analyze each logical part of the file as if they were separate files D Valu
25. analysis of this dump The Drawing Window This window provides you with a graphical overview of memory at the time the dump occurred Page 21 This comprehensive picture of the memory layout includes the instruction banks static and dynamic data banks the Public Data Bank PDB the Program Control Table PCT the Extended Mode Activity Local Stack ALS the Return Control Stack RCS and any HEAP or POOL banks allocated by the transaction You can view each main area as a single composite or by simply double clicking on it break it down into its basic components That is the instruction bank can be decomposed into all its relocatables the static data bank can be decomposed into its many common blocks the D RDA can be decomposed into its many DMS records and the dynamic data bank can be decomposed into its allocated DBAs free areas and program stacks L th a in wond 4036 PXCRTO Main I n3 03 0 11 05 29 Static D Hmnk Relocsteble shown ini source ences Memory Layout Lpg thir korset dn ascarz Tho durap by drag m drop ODD 1LO00 O0 10077 O140000 0 164107 OL400TL O140426 D140427 01433 73 D132374 01435043 0164110 0157515 167516 01706 66 1 0 When data area is overlaid by the following one dashed lines are drawn to separate the two blocks and the address range is only shown for the first block This is commonly seen with DMS records and static DBAs
26. and the analysis will be shown in a yellow Pop up window You can close the Alert Message Analysis window by simply moving the mouse outside its border Besides a short header line identifying the Alert Message and showing its status the analysis text is divided into the sections below Action This section informs you or the system operator of what action should be taken due to this Alert Message This section can also inform you of who should be called to inform of the file situation This information is intended for Alert Messages that are received by computer center operators rather than programmers 5 z E Phone List VDA Applieatian FreeSpece Fila kleze 1 PEOD C Raised sk 35 31 LT The Phone List displays the responsible Please Call the File Googp row application programmers FILES Phone Liat in cendre order along with their phone YU P Wa p Guard Office boars 8 161 4 7776 Mobile Homer Lers Krusa Haggild Ext 4 3031 Aobiles2eos 3294 Home 3299 3194 numbers The responsible programmers are selected file 40 J0FILE is coming full on FEOD C Analysis The file is 49 9 Full only 945 8087 of 1 955 259 basic cecbbds are available Tee file must have xt laast 905 fres basic cecocde but the fres har dropped to only 51 0 This has been estimaced ro severity level of MINOR Currenr file size is 115 565 tracks with b Valus of 4 5 7
27. available it should be used as it typically contains the documentation lines However if a F does not exist and the F proc contains documentation lines it then should be used for auto generating the view You can auto generate a view from a proc by using the batch program SEDGEN BATCH This program has a variety of functions with view construction being one After copying SEDGEN BATCH from SYSABS into TPF just execute it with the following input cards gt XQT SEDGEN gt PID number as requested gt Airline Code as requested gt VIEW gt VIEW view name apl COM proc f An auto generated view that is named view name will be created and placed in TPF Generally the convention of naming a view by preceding the proc name with V is used For example CA F will become V CASF and IV F will become V IV F Sometimes auto generated views need editing before they function properly This is because the indexes for defines are set to one 1 by default when generating the view e g MYDEF 1 1 Some defines expect a different index value and thus these expressions must be edited to use the correct value When you are satisfied with a view you can make it public to all users of The Visual Dump Analyzer by copying it into the file SED VIEW All views within this file are automatically shown in the View drop down box of the Data selection toolbar Be aware that the SED VIEW file exists on all systems running The Visual Dump Analy
28. been read and analyzed using the selected options The Visual Dump Analyzer obtains all the information it expects you will need for analysis during this process so you will receive quick responses during the time of examining the dump If you have unchecked some of the Include options and later discover that you need the information it will automatically be retrieved when you reference it This dialog box also provides the option of viewing all the aborts that have occurred on a particular system today By clicking on Show Today s Report the Abort Report will be retrieved and shown providing you the ability of browsing the aborts and selecting the specific dump you want to read Dump Analysis Modes Dumps can be downloaded and analyzed using three different modes Each mode varies in the amount of assistance it provides by adjusting the depth of analysis performed by The Visual Dump Analyzer This flexibility allows you to have the dump analyzed based upon your needs while still having the possibility of performing further analysis after the dump is initially retrieved Quick Mode Being the simplest of the dump analysis modes Quick Mode should be used when you know why the program aborted and thus wish to spend no time finding and analyzing the absolute and sources related to the dump In Page 8 this mode you will have access to all D bank data such as Common Blocks DBAs PDBs and the PCT You will not however be able
29. by changing the HTH header from a Stand Alone Query to a HTH First in Series with a TPR matching the dummy session This will force the HTH Query to execute on the PID selected by you The process for handling HTH Session Queries is almost the same Here The Visual Dump Analyzer will check to see if a session is already established for the TPR in question If so you are limited to rescheduling the input message on this PID number If a session is not established The Visual Dump Analyzer will create a new dummy session on the TPR from the HTH header just like Stand Alone Queries In this case you are free to select any unused PID from the Pseudo HTH PID pool for the reschedule Reschedule Input Message Original input message information The original input message was a HTH query HTH queries must execute on pid from the HTH Pseudo Pid Pool used for that specific interface Therefore you must select a pid number from the this pool The preset pid number belongs to this pool but if this pid is now re used for an active session you will not be allowed to use this pid again Further note that the pool may differ from system to system so if you reschedule on an other system you may be force to change the pid number If you don t know what the valid pool is just reschedule the message and if the selected pid does not belong to the pool the reject will inform on what pids can be used VDA will force the reschedule to use the pid y
30. constant or variable or it can be a complex mathematical expression containing any combination of these To determine the value of an expression click on the first empty row and enter the expression you wish to have resolved In the example below IBDIAG 1 has entered as the expression on the first line Expression Type Format value 12872 28 DEFINE Decimal 360416 CABCB 2 DEFINE Octal 07355 IBDIAG 1 DEFINE Decimal 0 IOPTXT VARIABLE Octal 052052052052 117125124120 125124040111 1161101 IOPTXT 5 6 VARIABLE Octal 117125 Enter expression here After an expression is entered The Visual Dump Analyzer calls a processor the mainframe that will use the dump and active absolute in order to resolve it The answer will then be returned and shown in the Value column There are few limitations with the complexity of the expression you may enter It is only required that the process on the mainframe can understand all of the symbols you use within the expression The mainframe process automatically understands many symbols These include ones defined within SPSYS SYS Common Blocks and variables defined within the active absolute Therefore symbols prefixed with S xxxx CAxxxx CBxxxx CQxxxx EYxxxx TAxxxx among others can all be used Beside these symbols you can teach The Visual Dump Analyzer any application defines for PDBs or DBAs by a method that creates Resolve Programs See Resolve
31. effects of a D value change will be for a specific BITMAP See What If D value When the BITMAP analysis only includes numeric values the BITMAP is fine as it matches the file and contains no discrepancies lf the analysis includes any letters F M A and there may be a problem with the BITMAP The letters F and M are not usually a problem as long as the records aren t being used by the application Because the records are considered to be free by FCSS they will eventually be used for a new record allocation which in turn will fix the problem The letter A may not actually be a problem as it indicates that a record has been allocated but it was never written This could be a valid situation for some applications however more likely than not it is an indication that the record has been lost to the system and is orphan The next time a bitmap recovery is run the record will be given back to FCSS and will be considered free The letter E always indicates an error as these records are considered to be used by FCSS even though they can never be read by USAS Thus these records are lost for good Moreover because they do not hold the free bit pattern they will not be recovered by a bitmap recovery The only way to recover these records is to issue an unconditional release XFSR for each basic record flagged with the letter See Freespace Scans What if D value The Visual Dump Analyzer allows you to produce a complete Deta
32. file By simply double clicking the bar for a specific file the file will be analyzed and all the detailed graphs related to it will be displayed More files can be analyzed in detail at the same time to allow for easy comparison Reading File Report from the mainframe To read a File Report from the mainframe select File New File Report or click the File Report icon on the main menu In the dialog you can select the desired system along with the files to be included in the Files Report Read File Report from Mainframe System ID PROD C fan Freespace File Report Cancel The File Report will retrieve information for the selected freespace files on the chosen system The reports are essentially identical except for the actual files that they describe The All Freespace File Report will contain ALL the freespace files on the system whereas a Freespace File Report for a particular application will only contain files within that application An application report can be generated for each one that is known to The Visual Dump Analyzer Page 74 File Reports The File Report is initially shown as a Graph Report with all the files being presented by an individual bar Moreover you can toggle this into a more traditional line based File Report that contains one line of information for each file You can use the line based File Report to update the file name information stored by The Visual Dump Analyzer f
33. for Freespace Files The main Warning Level is either set as a general Warning Level valid for all files or as an individual Warning Level set for a specific file This Warning Level indicates how full a file can be before an alarm will be raised If for example the Warning Level is set to 80 it indicates that when 80 of all basic records in the file are used or blocked by Release Only bitmaps an alarm will be raised That is in this case at least 20 of the basic records must be available for new allocations This 20 is called the Minimum Available Warning Level of the file Two automated Warning Levels exist which are calculated on the Minimum Available Warning Level The first warning is when less than 75 of this level is available and the next when less than 50 of it is allocatable See Alarm Method 1 Early Warnings Minimum Available Warning Level Warning Level lt 75 of the Minimum Available Warning Level is allocatable Warning Level lt 50 of the Minimum Available Warning Level is allocatable Page 80 Freespace File Severity Codes Alarms raised on Freespace files can have three different severity codes with each code requesting action by the people responsible for files i e the people marked with FILES in the address book Further alarms will always be raised when the Warning Level is surpassed If this happens during normal working hours Monday through Friday 8 16 the severi
34. in the future In order to preserve the format you enter line breaks are kept within the text X11 Hint text The X11 Hint is a specialized hint used only for MASM subroutines usually within an ACB that destroy or reused the X11 return register When these MASM subroutines abort it can be difficult to find out where these subroutines are called from Typically these routines store the X11 register in a save location for debug purposes Thus the X11 Hint explains how to regain the X11 register from the save location This allows The Visual Dump Analyzer to calculate the correct return and thus be able to display the source line that actually called this routine The format of the X11 Hint is as follows X11 lt expression gt The following is an example of when an X11 Hint is very helpful The substring routine F2SUBSTR is called when partial strings are manipulated in Fortran e g LINE WORKLN 1 12 When a 531 error occurs indicating the substring length is greater than the string F2SUBSTR saves the original value of the X11 register in IBNOTE 1 and then calls XTCA In order to determine which Fortran statement actually has a substring error a programmer would likely have to spend considerable time studying the system software before it is recognized that IBNOTE 1 actually holds the X11 return address Then the absolute address would need to be converted to the actual line number where the substring err
35. line 407 also when SEDSRC is called and returns in line 416 and finally when SEDOUT is called and returns in line 426 Moreover these call and return TRAPS will occur with every HVTIP program that is called by your program By combining these TRAPS with the snapping of data you can gain valuable information in determining the program that causes the error situation resulting in an abort To set an HVTIP TRAP right click in the Source Window to open the Pop up menu and select Trap calls returns to HVTIP The default abort count setting for HVTIP TRAPS is 1 which will force an abort on the first call to another HVTIP program As with subroutine TRAPS each CALL will result in 2 hits one when the HVTIP program is called and a second when it returns Again this means that all odd hit counts are calls and all even counts are returns Realizing this you can calculate the HVTIP hit count needed to force an abort at the desired time See Setting TRAPS on internal subroutines Page 37 Setting Visual Breakpoint Traps on data The Visual Dump Analyzer allows you to set Visual Breakpoint TRAPS on any data location using the symbolic name of the location whenever possible This can quickly provide you information on where a variable is used or updated within a transaction s execution Technically all TRAPS have to be set using a fixed absolute address however The Visual Dump Analyzer uses its knowledge of USAS to calculate set an
36. mapped and copied into a library bank al rage Error Code Look up The Visual Dump Analyzer is aware of all contingency including HVTIP FCSS OLTP Tuxedo Edifact input and output handler EYERRR error codes and DMS error codes The descriptions for these error codes are not only used during dump analysis but are also available to you upon request You can reference these error codes by entering Tools Error Codes Error Code Look up Simply enter the error code and press Look Up Page 53 The Visual Dump Analyzer Log File The Visual Dump Analyzer has a log file named Vda log This log file of ascii text format can be used to trace the status of Tuxedo communication with the mainframe Enter Tools Settings and then select the General Settings tab to toggle the logging of data to this file With the default setting being OFF you should only change this if you are experiencing communication problems Fortran Options The Visual Dump Analyzer is dependent on the compilers building diagnostic information in the absolutes for the purpose of assisting with debugging The compilers must be requested to do so by supplying specific options on the compile statement Failure to generate the diagnostic tables will not prevent The Visual Dump Analyzer from working with an absolute or a dump caused by it however functions specifically related to variables will not be available Basic Mode Fort
37. not change the D value but it will only generate a report about the file as if the D value had been updated To actually change the D value you will still need to use FREIPS Page 91 Be aware that the D value percentage used by the FCSS freespace handler must split the words used for a BITMAP on word boundaries If a specified D value percentage does not calculate to a word boundary the D value split is rounded so that it will The formula for calculating the BITMAP split is BITMAP_size_below_the_D value BITMAP_SIZE D value_PCT 100 18 36 36 BITMAP_size_above_the_D value BITMAP_SIZE BITMAP_size_below_the_D value Consequently a file with 1024 basic records per BITMAP will use 28 44 words to hold the BITMAP If the file has a D value of 7 50 8 the result will be 14 words equivalent to 14 36 504 basic records or 49 2 used for record types 1 7 and 14 44 words equivalent to 14 44 36 520 basic records or 50 8 for record type 8 The following table shows the actual effect of setting various D value percentages for a file with a BITMAP size of 1024 Basic Records per BITMAP D value PCT BITMAP SIZE lt D PCT lt D BITMAP SIZE gt D PCT gt D 43 432 42 2 592 57 8 44 468 45 7 556 54 3 45 468 45 7 556 54 3 46 468 45 7 556 54 3 47 468 45 7 556 54 3 48 504 49 2 520 50 8 49 504 49 2 520 50 8 50 504 49 2 520 50 8 51 540 52 7 484 47 3 52 540 52 7 484 47 3 53 540
38. number and for masm programs it is the absolute address The aborting subroutine is drawn in RED and the active subroutine the one currently displayed in RUE the Source Code window is drawn in GREEN The WalkBack picture can also be used as an access pad for changing the contents of the Source Code windows By simply dragging a subroutine from the picture and dropping it into another window you will be able to view the source code about the line that produced the forward call Note that you can drop the subroutine into any window type with the destination window automatically changing to a Source Code window The WalkBack picture starts from the first forward call within the dump file Normally this will be the call made by the ICP program calling an application program If the transaction has made a program transfer during execution however the record of calls made before the transfer is erased and the WalkBack picture will start after the program transfer To enable the Visual Dump Analyzer to perform the WalkBack logic it is essential that the correct absolute elements are found If an incorrect absolute is used the HVTIP program stack cannot be decomposed into all of its internal subroutines thus forcing the HVTIP stack to be displayed as one single box Finally this display should be considered an analysis of the program stack areas and not a detailed trace of the program s execution That is this path does not includ
39. place The Visual Dump Analyzer in Monitor Mode select Tools Settings from the main menu then select the Report Setting pane and finally select Enable continued execution Monitor Mode Even though The Visual Dump Analyzer can run continuously when placed in Monitor Mode it is recommended that the Workstation running in Monitor Mode be booted about once every week This helps ensure that Windows or other applications running on the Workstation are not causing problems and thus preventing The Visual Dump Analyzer from properly monitoring the USAS applications The desired method for being informed of an Alert Message can be configured under Tools Settings within the main menu Raising Alert Messages on your local Workstation IWS This method raises the Alert Messages on your local Workstation and is meant for personal use Being the most common method used for raising alerts it allows you to set the warning levels in any way that you wish as they will only apply to you Moreover the levels that you choose for the development test and production systems will not affect other instances of The Visual Dump Analyzer that are running in Monitor Mode and raising Alerts to the SPO or REMEDY for production systems With this method you can produce a Report Filter that will limit the monitoring and thereby the Alert Messages that are raised to your IWS This filter can monitor a limited number of programs and simply ignore
40. reschedule the input message again simply press Schedule Msg Now and the message will be rescheduled Next an information dialog box is displayed with information on the result of the reschedule Finally you can use TST PRINT from a normal HVTIP screen to capture the trace Naturally if the reschedule causes a new abort you can open the new dump by using The Visual Dump Analyzer Rescheduling HTH messages Host to Host HTH messages are more difficult to reschedule than normal VDU transactions because the HTH header along with the HTH configuration determines which PID the transaction will execute on As a result the PID can often not be predicted making it impossible to turn on traces beforehand The Visual Dump Analyzer solves this problem by allowing you to choose the PID that you want the message to be rescheduled on The HTH header in the input message is then manipulating with this PID information before itis rescheduled To do this just enter the PID number in the above dialog box Page 27 The Visual Dump Analyzer will handle the following three types of messages differently due to their unique nature e HTH Stand Alone Query messages e HTH Session Query messages e HTH Reply messages HTH Stand Alone Queries will always execute on a PID from the Pseudo HTH PID pool assigned to the interface Therefore you have to select an unused PID from this pool and The Visual Dump Analyzer will create a dummy session on the PID
41. save it to a local disc so that it can be retrieved later For archival purposes it is a good idea to save Abort Reports on a daily or weekly basis Because the SED Q common bank will wrap around periodically saving Abort Reports to a local disc is the only way to keep a complete history of aborts To save the Abort Report to disc select File Save Abort Report to Disc or click the Diskette icon and the normal Windows dialog for saving files will be displayed Opening Abort Reports saved on disc You can retrieve an Abort Report that is saved locally by selecting File Open Saved Dump or Report or clicking the Open Folder icon This will display the normal Windows dialog for opening files The Visual Dump Analyzer supports a multi document environment thus you can have multiple dumps or Abort Reports opened at the same time Use the Window command in the main menu to arrange and navigate between open dumps Exporting Abort Reports Abort Reports can be exported to CSV Comma Delimited files By selecting Tools Export Report to file you can save the report to the file name of your choice Other Microsoft products such as Excel can then import this file for further processing Emailing Abort Reports Once saved to disc Abort Reports can be attached to an email just like any other file Alternatively you can click the mail icon on the main menu and your configured mail client will be opened with the Abort Repor
42. space in the warning window is clicked rather that the text itself the warning window will be closed and The Visual Dump Analyzer will not be activated Because the Alert Message logic is based on an analysis of the new aborts retrieved by the refresh logic this feature must be turned ON Turning the refresh logic OFF will therefore cause the Alert Message to be turned OFF as well Alert Message Analysis The Alert Message Analysis gives the result of the Abort Report analysis This summary gathers information from the dumps themselves their diagnostic information the VDA Knowledge Database and from the built in knowledge of the USAS applications All this information is processed and the final result is used to generate a natural language text explaining as best possible the reason for the aborts To see this analysis click the Alert Id in the Abort Report and the analysis will be shown in a yellow Pop up window You can close the Alert Message Analysis window by simply moving the mouse outside its border Besides a short header line identifying the Alert Message and showing its status the analysis text is divided into the below sections Page 61 Action This section informs you which application or applications are responsible along with whether this is a new Alert Message or an Identical Alert Message that has been raised in the past hour This section can also inform you of who should be called to inform them of these abort
43. the program absolute is not found you can still analyze global data areas within the dump such as DBAs PDBs and Common Blocks Only the variables within the local storage stack of the programs related to the dump cannot be accessed If a correct version of the absolute does exist but was not actually found it can be easily be manually retrieved See Reading or Replacing Absolutes When the correct absolutes are found they will be used to determine which source programs are to be read Next The Visual Dump Analyzer will check that the sources have not been changed since they were compiled and mapped into the absolute Finally it will verify that known line number references from the absolute actually match the source The result of the validity check performed on both the absolutes and the sources will be displayed using a single validity color code This color code indicates whether the absolute matches the dump and further how well the sources match this absolute The validity color code is shown as the vertical colored bar placed along the left border of the Source Display window f this bar is not green either the absolute or the source should be replaced See Validity Color Codes Reading or Replacing Absolutes It is important to know whether the program absolutes correctly relate to the dump you are analyzing otherwise it can result in misleading information The absolute version can be checked by selecting the absolute and clic
44. the rest For example if you ve just updated a program and have placed it on a test system you can have The Visual Dump Analyzer monitor this specific program and inform you if it starts to abort thus allowing you to be the first that is aware of this condition An Alert Message is raised by animating a small warning window in the bottom right corner of your screen This window will be shown as the top most window so that it will always be visible It will not however take the input focus so you can continue working without interruption Too many identical aborts on You can configure the appearance of this small warning window in the Report PROD E Settings pane and even test its appearance by pressing Show Test Alert The Alert Message will be raised even if The Visual Dump Analyzer application is in the background or is minimized at the time Once the Alert Message is raised you can use it to quickly activate The Visual Dump Analyzer application by clicking the warning text itself The Visual Dump Analyzer will be maximized and brought to the foreground along with maximizing the Abort Report that has raised the Alert Message If you instead click the non text area within the warning window it will simply close without activating The Visual Dump Analyzer It is not required that The Visual Dump Analyzer is running in Monitor Mode to raise Alert Messages on your local Workstation Page 66 Raising Alert Messages as e
45. the system search path Be sure that you update the search path for all mainframes you access Although there is a default Source server for each Dump server that is defined within the configuration of The Visual Dump Analyzer this can be overridden by selecting another server within the Source server drop down menu when the related Dump server is displayed in its drop down menu When searching for an absolute element The Visual Data Analyzer will first search the file from which an absolute was loaded into the HVTIP library If an exact match is not made with the absolute s creation date time your personal search path will next be examined and finally the system search path will be scanned If an exact match cannot be found the absolute which best matches the date time will be used Note if you do not wish to search the library load file deselect the Use library load file in search option in this dialog box When searching for source code related to the dump file The Visual Dump Analyzer will first examine your personal search path and then the system search path Further the date time of the source code that is closest to the date time of its related absolute element will be selected for the analysis Note that unlike searching for an absolute element that can have an exact date time match looking for related source code will always require scanning all files in the search paths Page 6 Absolute and source elements that a
46. to choose a DMS record from a selection list of DMS records present in the DMS Schema used by the active program This allows you to access DMS records by name without knowing their internal DMS record number or location Display data as a View is a short cut method of displaying the block of data present in the window as a view Essentially it is the same as selecting a view in the View drop down menu of the Data selection toolbar Open Dba in editor lets you view the data within an editor of your choice That is you can use the full features of an editor while still having The Visual Dump Analyzer active To configure the editor you wish to use select Tools Settings and enter it in the Editor name prompt Find can be used to search for a string of characters within the window The standard Windows function is used for this thus providing you with various options in the search CARCSZ 896 p hcc ehe ee hee hee III II III II I I SE SCREEN ADDENDUM TERMINAL DATA PAR ee CAAKEY 1 010004555701 gent addendum record keys for agents A E implies this agent is active and the agent addendum is attached to the CLR implies this agent is signed out and no agent addendum exists for this agent NUM Z Page 24 The Data Display window can also be used to present data that is overlaid with a view Views provide a powerful and flexible way of presenting data by having the ability to incorporate freefo
47. to view source code see the values of variables or Walk the Jump Stack The WalkBack picture will only show the flow between absolutes with no breakdown of the individual absolutes being performed Be aware that even though you cannot use symbolic debugging or see variables in Quick Mode you can use the Expression Window to symbolically by name enter any Common Block define or main stack variable and have it resolved to its value Batch programs cannot be analyzed using Quick Mode because they each have unique mappings and thus require the absolute to be read and analyzed so the D Bank structures can be accessed If a batch dump is analyzed in Quick Mode the mode will automatically be changed to Normal Mode once The Visual Dump Analyzer recognizes the dump is originated by a batch program Normal Mode In Normal Mode you will have access to the same D Bank data as with Quick Mode In addition The Visual Dump Analyzer will perform a complete analysis of the dump as it relates to the aborting absolute Absolutes that are called earlier in the Program Call stack however will not be analyzed Besides having access to DBAs PDBs Common Blocks and the PCT you can see the source code and use symbolic debugging The aborting absolute s program stacks will be analyzed and presented in the Variable Window Further you have the possibility to Walk the jump stack in this mode The WalkBack picture will show the aborting absolute broken down int
48. 355000000 000000000000 000012007355 000000000000 124162530421 000000000000 672216231661 121040003000 040015036033 nnnnnnnnnnnn 000000000000 000000000000 000000000000 000000000000 124162530420 000000000000 033013043040 041040017033 142003000000 nnnnnnnnnnnn 000000000000 000244377661 000000000000 221623166105 000000000000 000000000000 000017036 142123111107 000000000000 nnnnnnnnnnnn DO ncs niis Z7 An example of an area that is split into multiple sections is the CABLOC It is divided into the CABCB Screen Addendum Agent Addendum General Information Area Application Table and Application Area A second example is the MSG CB which is split into an Input MPA Host to host header if present Input Message and Output MPA Besides being able to change the display format of the data you can select from several options within this window s Pop up menu Show absolute address and Show relative address inserts removes absolute and relative addresses in the data view Show toggles the display of a six word when a DBA is displayed Break long lines forces all lines that are longer than the width of the window to be broken insert CR LF and thereby ensure the entire line can always be seen All data will be placed in aligned columns Display at Address lets you display data beginning at an address or entry point that you specify Display DMS record allows you
49. 40 040040040040 040040040040 040040040040 040040040040 nannannannan 102123056040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 040040040040 nannannannan LKBABS Due to the nature of defines you cannot set a SNAP directly on a DBA or PDB define by using its symbolic name Instead you must calculate its address location and then set the SNAP on the relative word in the DBA You can change the number of words to SNAP by right clicking the GREEN words and selecting Set Number of Words to Snap Alternatively you can use the normal Windows method by selecting all the words you wish to SNAP then right clicking on the chosen words to open the Pop up menu and finally selecting Set Snap Page 44 Dynamic PRTADP calls To set a Dynamic PRTADP call just set a TRAP on a line number and enter the SNAP data that you would like to be displayed when the TRAP occurs This method is simple and effective and allows you to dynamically produce SNAPS that work just like PRTADP calls but without having to update and recompile your program EXPLAIN REQUESTE SPCERR CODE 0329 IF SPCERR NE 0 08
50. 968 SERT 65978 EEG LOL 4 ft CRI He 1 CSS SST ANTI BENE POIG 1 Ou ie ono 2 7815 PEPE 2 STE cose PCIR 15 000 BERTA LOL Ik 1 zi PEL 2 BRITA EFS LCR Bis 7 3 2 ee LOK PB 95 00 BEREIT LC dite 598 LOL 14 25 63 ETA LOL 14 17 22 I 2719 PCIR EEE 022 QR Pa PCI DOGOGOCZZDOU FCI FCI DOO GEEA R P DIS PCI FCI FCI MEE PCI boost PCI DDOCO4GOT4 3 FCI Mage FCI 0102081007 PU DOXXMECOXTT PCI ROOST FCI DOME PCI WHT PCI DOES 53 40 S41 PCI Hej PCI EDIFFACS EDIFPACS EDIFPACS CPPS EDIFPACS EDIFPACS LH CIERE MH EM L 1X 36 PEDCKIT c nee Tira 25 TIT cours PEDOUT DET ECO TI 2 FPSH D 12 TE DEI 12 PEATRAIL cFRLCISDEE SO LT part zi Page 56 Classifying Aborts as Identical or Similar Aborts are determined to be identical when they occur in the same program have identical diagnostic information For XTCA aborts the diagnostic information is considered identical when IBSERR IBDIAG IBNOTE and IBACBR are alike whereas for XCONT aborts the contingency code and the contingency address need to be the same Aborts are considered to be similar when they occur in the same pr
51. AP occurring every time the line is executed In this case the TRAP will not force a new abort but it will instead snap any data you have requested to the trace file Realize that the TRAP will remain set during the entire execution of the program which may result in the TRAP occurring many times Setting a TRAP on a line number in an ACB or FLSS routine is done in the same way as normal HVTIP programs When a line number TRAP is set it is normally placed on the first assembler instruction generated by the FTN line number If the FTN line does not actually cause any assembler instructions to be generated e g Comment lines ENDIF and CONTINUE statements the TRAP will be rejected indicating that you should set the TRAP on the next FTN line that will generate executable instructions Page 33 If the Z option optimization is used with the FTN compiler assembler code from multiple FTN lines can be merged in order to generate more efficient code This can cause a line number TRAP to be set some instructions away from where it would appear to be set if compared to the source code Usually this is not a problem but if you want to be in complete control of the exact location of your TRAP use Show MASM code to see the assembler code and set the TRAP on the specific MASM instruction you want rather than on a line number See Setting TRAPS on MASM instructions When setting TRAPS on an IF statement it can sometimes be difficult to pr
52. Apply Report filter Auto Close in Seconds 5 IV Show gridlines in reports Enable continued execution Monitor mode Alert Text Color _ Calor Alert Background Color Color Riko Fear Last Alert Color in Report Color Off Prev Alert Color in Report Color m User Identification Show Test Alert LKB Lars Kruse B ggild Reset All OK Cancel Apply The layout and behavior of the alert message warning window itself can also be customized in this dialog Use the Show Test Alert button to raise a test alert and verify the setting Page 60 Auto refreshing Abort Reports To ensure that the Abort Report is kept up to date The Visual Dump Analyzer periodically checks the monitored system for new aborts In the Pop up menu you can toggle the refresh time period between 1 2 or 5 minutes or you can turn the Auto Refresh logic completely OFF If new aborts are found they are retrieved and merge into the report and the display is refreshed to reflect these new aborts To manually refresh an Abort Report press F5 and the report will be immediately refreshed even if Auto Refresh logic is turned OFF Raising Alerts Messages Raising Alert Messages is a powerful feature that will immediately inform you of when the monitored applications start creating aborts Whenever the refresh logic finds and retrieves new aborts the report is analyzed and checked to verify if these new aborts have cause
53. DS esee ee ee eee tn nasse ette snas ases eee see eese ease ses s e setae sas s eese tease s eee eaa 42 SETTING SNAPS ON VARIABLES voee o ae ne dame dene 43 SETTING SNAPS ON DBAS PDBS OR A FIXED ADDRESS cc ccseeeeeeeseseseseseeeceeeseveseseceseseseserecereceseseeeseresetesesesesesereseeesenens 43 DYNAMIC dS LUPO DE SRRRNPRHRR m m m X D e 44 VIEW CONSTRUCTION 45 AUTO GENERATION OF VIEWS ccccccccccccccccccccccccecscceseeeseseseseseseseeeseeeseeeseseseeeseeeseaeseseseseseaeseseseeeseeescesscacecesecsescesscesscessceueseeesenees 46 THE VDA KNOWLEDGE SEiviscicccssscsscssscsssstecscocvecsscecocssesecoessoesesonsscestecsoosiensssecoveoescoasecesseccsensvcsssesoescnscesosoeeies 47 REASON FOR NO GE 48 ANTENT 48 M ED E RR RETRO 48 ABORT SEVERITY mundi detailed denna 49 RESOLVE uice eI HU 50 DEFINING RESOLVE 50 STEP 1 ASSOCIATING PROCS TO RESOLVE PROGRAMS 2 50 STEP 2 UPDATING THE SEDUSR F E
54. E DAT Subfile KG 012202 PCI FLT NBR INDEX OVERFLOW Subfile KLM 016202 PCI LEG MEAL INFO FILE Subfile KLI 017202 PCI SIW INFORMATION FILE Finding Files 4 65 7 Tracks 115 968 When a file number for a specific file is not known or you want to find a file based on the data it contains The Visual Dump Analyzer allows you to search among all files known to The Visual Dump Analyzer by entering free format text Fina rie piano x Enter text to search flight Close Found Name 30FILE TIP File no 430 USAS File no 130 Subfile KF 01202 PCI FLIGHT NBR INDEX Subfile KI 02202 PCI MASTER DATA IND Subfile KM 03202 PCI MASTER DATA Subfile KQ 04202 PCI TELETYPE INDEX Subfile KR 05202 PCI TELETYPE DATA Subfile KS 07202 PCI SEGMENT FILE Subfile KJ 010202 PCI TIME TABLE INDEX Subfile KK 011202 PCI TIME TABLE DATA Subfile KG 012202 PCI FLT NBR INDEX OVERFLOW Subfile KLM 016202 PCI LEG MEAL INFO FILE Subfile KLI 017202 PCI SIW INFORMATION FILE Name 31FILE TIP File no 431 USAS File no 131 Subfile KP 01203 PCI PASSENGER FILE Subfile KPT 02203 PCI TLPH PCI PSGR CITY DAY Subfile KFD 03203 PCI DEPARTURE FLIGHTINDEX To open the File Find dialog right click to open the Pop up menu and select Find File This will open the above dialog where you can search for files The search will be case insensitive and will include
55. ILE can be before an alarm will be raised Use the General Warning Level of 80 pct Use specific Warning Level for file 30FILE 80 In this dialog you can control the specific Warning Level for the file Again note that the specific Warning Level is only valid for the specified file on the system the File Report is being generated upon If you set the specific Warning Level to zero you will turn off all Monitoring for the file and thus no warnings will be raised for the file If a Warning Level is achieved and you have the Alert selected in the Pop up menu an Alert Message will be raised informing you that a file is becoming full See Raising Alert Messages on Freespace Files Page 77 Auto refreshing File Reports To ensure that the File Report is kept up to date The Visual Dump Analyzer periodically checks the monitored system for changes in file statuses In the Pop up menu you can toggle the refresh time period to be either 1 2 or 5 hours or you can turn the Auto Refresh logic completely OFF Every time the File Report is refreshed all the files are checked and if the Warning Level is found to be exceeded for one or more files an Alert Message is raised To manually refresh a File Report press F5 and the report will be immediately refreshed even if Auto Refresh logic is turned OFF Raising Alerts Messages on Freespace Files Raising Alert Messages is a very helpful feature
56. Mail or SMS You can configure The Visual Dump Analyzer to send the Alert Message as eMails or SMS message to promptly inform you when an Alert has been raised Settings General Settings Search Path Applications Reports Settings Abort Filter Alert Message eMail Settings REMEDY Graph Settings The Alert Message can be forwarded as an eMail or SMS do so enter the eMail address of the alert message recipients below and configure the subject layout accordingly To forward the Alert Message as an SMS enter your mobil phone number as the eMail address and tic the Send Alert Messaget as SMS To 25353294 Er EY Use gt to separate recipients Send Alert Message as SMS Subject YDA will auto generate the subject Subject Generation Let VDA generate the subject automatically C Use my fixed subject Send Test Mail Cancel Apply When you want to send the Alert Message as an SMS just enter the mobile phone number in the To field and select Send Alert Message as SMS as shown above To enable The Visual Dump Analyzer to raise Alert Messages via eMail or SMS an email server must be configured in the EMAIL section of the general configuration element USAS SED FILE SED INI on the default mainframe server If the EMAIL section is missing or it does not name an email server the above eMail Settings pane will not be visible It is not requi
57. Programs section later in this manual The following are examples of expressions you can have resolved Expression Action MYTABL X 2 Resolve the value of the table MYTABL defined in the active absolute using the index X 2 where X is a variable in the active absolute MYVAR X 10 Caxxxx 1 Resolve the value from the 3 dimentional table MYVAR defined in the active absolute using the value of X from the active stack as the first index 10 as hard coded value for the second index and a CA define as the third index MYSTR IDX 10 Y Resolve the value of the substring 10 Y of the string MYSTR defined in the active absolute by using IDX as the index and Y as the end character position Both IDX and Y are assumed to be variables in the active absolute MYVAR1 3 3 MYVAR2 Resolve the value of the mathematical expression using the integer variables MYVAR1 and from the active absolute FIATYP Resolve the value of FIATYP variable from the Fl DMS record IBDIAG 1 Resolve the value of the SYS define IBDIAG using a hard coded index of 1 MYDEF Resolve the value of the application define MYDEF using the DBA from the dump and a pre produced resolve program 12875 027 Resolve this mathematical expression assuming 12875 to be decimal and 027 to be octal The Show View values option within the Pop up menu for this window allows you to see all the expression names resolved during the
58. RAP information is completely defined you must press the OK button and the variable TRAP will be set To inform you of the active TRAP the variable will be highlighted in R D indicating the TRAP is active Variable Type Scope Size Address Format value 4 INTEGER LOCAL 516133 Ascii PCI INTEGER LOCAL 516120 Ascii USAS INTEGER GLOBAL 516216 Octal 0401655401655 INTEGER GLOBAL 515773 Octal 040040040040 CHARACTER 12 GLOBAL 515543 Ascii CHARACTER 12 GLOBAL 515745 Ascii INTEGER GLOBAL 515775 Decimal INTEGER GLOBAL 515764 Decimal CHARACTER 80 GLOBAL 516067 Ascii CHARACTER 4 GLOBAL 516064 Ascii INTEGER GLOBAL 515755 Decimal 21878821189 INTEGER GLOBAL 516122 Decimal 5453926725 CHARACTER 40 GLOBAL 516052 Ascii CHARACTER 8 GLOBAL 515634 Ascii LOGICAL GLOBAL 515661 Logical FALSE CHADACTED HAN GL R AI C1572323 Aerii LISAS KSEN m m Bb LM LB HBA Even though a TRAP will only be set one word you can request more words to be snapped to the trace file By default the number of words snapped is set to the variable s word size but you are allowed to update this value To change the number of snapped words right click the RED variable line and select Set number of Words to Snap This will open a dialog allowing you to enter the number of words to be written to the trace file for each snap For example if you set a TRAP on a string variable called LINE that is 80 charac
59. READING DUMPS FROM THE MAINFRAME eeeoosevvveveeesessnnnnvnvenesensnnnnvnnnnenensnnnnnnnensennnnnnvnnenesensnnnnennnsenensnnnnvnvenesnnsensnene 7 DUMP ANALYSIS MODES 7 MODE ec oa ient ag wns seeps ace tenes MI t f tL M I MIS 7 NORMAL MODE 8 FULL MODE 8 FINDING THE ABSOLUTES AND SOURCE CODE sesevesessssssnevnvensennsensnnnnnnnnnenessnnnennnensnnnsnnnnnnennenesennnennenensenensnnnnnnsenesene 9 READING OR REPLACING ABSOLUTES cccccccccccccccsccccescececeescseseseseseseseseseseseseseseseseseseseseseseessesesssescecscecsceesceescesscececeseseseseeeeess 9 READING OR REPLACING 10 BROWSING PROGRAM FILES FOR ABSOLUTE OR ese ese sse etes eset esee esee esee eee 10 VALIDITY COLOR CODES 12 SAVING DUMPS TO DISC wessisiscccisccecccciasscesdescccestesssesccceessasccesssdecccessesssessbccsetedevodsnsdessesdasesodetcodesseccessaonccesueSeseteseecsseedecess 13 OPENING DUMPS SAVED ON DISC sseeessvsvesssevnesnsnsvssensnnvsssnnsesensnnsesensnsesssnennssnsnnenssnnnseessnnsesensnnsesennnsenssnenseennneneen ne
60. TIM keyword option rather than the NO OPTIM keyword option the UCS compilers will optimize the generated code for speed The Visual Dump Analyzer is able to handle this optimized code but be aware that this can cause the instructions generated by one source line to be mixed with code generated by the surrounding source lines Page 54 Monitoring USAS Applications The Visual Dump Analyzer keeps track of all aborts that occur on a system by recording them in The Visual Dump Analyzer s common bank SED Q This common bank has several purposes First it can provide the user with a quick System Abort Status or Abort Report by presenting an overview report of all aborts that have occurred on the system during the last hours days or weeks Second the Abort Report can be used to monitor all USAS applications on a given system and automatically raise an Alert Message if it detects a pattern to the aborts or if the number of aborts simply grows too large within a specific time frame Third the Abort Report enables the user to quickly find and retrieve dumps Fourth The Visual Dump Analyzer can be used to control the number of dumps that are actually processed by the USAS SYS contingency handler when many identical aborts occur on the system within a short period of time See The Visual Dump Analyzer Basic Mode DABT function Abort Reports The Abort Report contains one line of information for each abort that has occurred o
61. TST DOFF transaction will be scheduled It is important to remember to turn traces off once they are no longer needed especially when traces are set on services or internal PIDs Page 31 Setting Visual Breakpoint Traps A trace is commonly used to determine the path taken by a transaction during its execution Normal USAS tracing however only provides a trace that includes calls to ACB and FLSS routines The volume of code that exists between ACB calls is not traced and therefore its path of execution is unknown This problem is solved by Visual Breakpoint Traps TRAPS Because TRAPS do not rely on any special events such as ACB calls for intercepting the execution any piece of code can be analyzed in extensive detail Besides intercepting when a specific piece of code is executed Visual Breakpoint Traps also allows you to gain control when a specific variable or address is referenced or updated This is a very helpful way of finding code that alters or destroys specific data Among its many features TRAPS can inform you whether you have executed a given line number or subroutine it can snap data in various ways it can force an abort at the right spot and it can force an abort when a particular variable acquires a specified value See User Guide for VISUAL TRACE And VISUAL PERFORMANCE ANALYSIS Technically TRAPS are divided into two different types l Bank TRAPS and D Bank TRAPS l Bank TRAPS are traps that occur whenev
62. USAS programmers however these updates are just as relevant as any other updates to the DBA Because the Exec requests a TRAP to be a single full word absolute address The Visual Dump Analyzer will always convert the symbolic TRAP to be a single full word absolute address even if the TRAP is only for a partial word For example if the variable to TRAP is only one character stored within Q1 of a word the TRAP will actually be set for the entire word Therefore any updates to Q2 Q3 and Q4 of this word will also cause the TRAP to hit even though the variable was actually not updated For FTN program with STD66 this is not a problem but for character tables using STD77 this needs to be taken into account Similarly if a TRAP is set on a character variable larger than 4 characters thus taking up more than one word on the stack only the first word will be under the control of the TRAP with updates to the 2 and later words not causing the TRAP to hit These limitations are due to the Breakpoint logic supported by the Exec and therefore cannot be circumvented by The Visual Dump Analyzer For all TRAPS to data areas you must decide if the TRAP should hit only on UPDATE references or on ALL references i e read and update Read references are defined to be any source code statement that references a variable on the right side of the equals sign within an assign statement or uses the variable within a test IF statement That is
63. abort occurs in a program it is often not because the error occurs where the abort is taken but instead because it is at this specific point in the program logic that an error is recognized and continued execution is either pointless or impossible In these cases usually the initial task is to identify the program that caused the error which may or may not be the same program that triggered the abort To assist you in finding the program that actually caused the error The Visual Dump Analyzer allows you to set a TRAP that will occur when your program calls another HVTIP program and when the called HVTIP program returns back to yours 0403 ELSE 0404 SRCLIF Hi DMPTBL 0405 BITS SRCLIF 19 1 0 CLEAR ASYNC INDICATOR 0406 ENDIF 207 AEO ee ee me 8 CIC 0 nie ete m ALLOW USER TO SET Xii 0409 IF USRX11 EQ 1 CALL SUX11 0410 ee eeu GET CGY TEXT 0411 FILE HELPFL 0412 PRG SED CTG 0413 FDPRG FDiPRG 1 6 0414 FDPRG2 FD PRG 7 12 0415 FDVER FDVER2 FDSPAC 0416 CALL SEDSRC FILE LINE 0 0417 IF SRCCNT EQ 0 THEN 0418 IF SPCERR NE 0 THEN 0419 CALL POCTAL SPCERR VORELN 0420 ELSE 0421 CALL POCTAL DMPTEL CNTPET VORELN 0422 ENDIF 0423 LINE UNKNOWN CONTINGENCY CODE amp WORKLN 1 12 0424 SRVSEG BOOL CTG 0425 SRVTXT 1 0427 END IF CR BL eee Ep In this example the TRAP will occur both when SEDOUT is called and returns in
64. aborted with an XTCA 531 as a response RIEP inpur 10 aborts An Alert Analysis of 531 in SEDANA haa d HICH Message Analysis may malysis c h LE n nk as TE SEDANA specific Erge code also contain entries of FESUESTR SUBSTRING LENGTH GREATER THAN STRING aborts that are similar in characteristics Abort D tails Dara Tite Pune Thaere Ibdiag Ibnove kpl Service Savariey Frege ae DAHAT 10 18 11 1 3881 531 52656 2251 VDA TJEDANA DUHAT 10 18 09 1 3881 FONT 1 52656 2251 VDA EICH DAHAT 10 18 07 1 3881 531 52656 2251 VDA SEDANA DUHAT 10 18 06 1 3821 ROH 1 52656 2251 VDA EICH SEDANA DAHAT 10 18 03 1 3821 531 52656 2251 VDA SEDANA Persisting Abort Details This is identical to the Abort Details only the word Persisting is added to inform on the fact that these aborts are identical to aborts that have already been reported within the last hour and the aborts are persistently occurring In this case the original aborts reported are shown using the below section name Original Aborts Reported Alert 1 If an Alert Message was raised and the problem is still occurring another Alert Message may be raised To inform on the fact that this is an already known problem that has been reported this section is used to inform of the original Alert Message and the aborts that caused the original alert
65. age Analysis will deem all these aborts to relate to a SYS problem and request SYS staff to be alerted rather than staff from the aborting applications In case SYS is not part of the aborting applications but the number of aborts have exceeded this warning level by a factor of 3 this problem will also be deemed to be a SYS rather than an application problem Warning on reoccurring aborts This warning level will detect aborts originating from queues or Time Call If an abort occurs 3 or more times and the time intervals between the aborts are the same this warning level is considered to be reached When this occurs it is usually an indication of a minor problem limited to a specific queue or program However this problem is not expected to disappear without human intervention as it has already happened at least 3 times and it is expected to keep occurring with the same time interval until action is taken When this warning level is not set this type of error is normally easily overlooked as is can be difficult to detect the problem when it is not noticed that it a specific abort is reoccurring every hour or daily These latter three warning levels can and should be combined However once a specific abort has been included in one Alert Message it is automatically prevented from occurring in another Alert Message This prevents the same abort from causing more than one Alert Message to be raised Note that if a Report Filter is applied only abor
66. ains information for all mainframes See Getting Started Auto Config Communication setup The communication tool that is used between the client VDA exe and the server can be either The Visual Dump Analyzer s own Transaction Manger TMVDA or it can be the Unisys Open Env OLTP Transaction Manager TM2200 TMVDA uses normal TCP IP communication between the client workstations and TMVDA on the mainframe Independent of the communication tool The Visual Dump Analyzer will be installed on a shared Windows server Then to run The Visual Dump Analyzer you only need to create a normal Windows shortcut to VDA EXE on the shared server place it on your desktop and finally click on it That is nothing needs to be installed on your PC You may choose to install The Visual Dump Analyzer locally on your PC however by simply copying the shared installation probably in a directory called VDA or VDA50 including all subdirectories to your PC you can then execute VDA from that location If TM2200 is the selected communication tool the Bea Tuxedo Workstation Client DLLs v 6 0 or later needs to be accessible to your PC This is accomplished by adding a TUXEDO subdirectory to the shared VDA installation on the Windows server and placing the Tuxedo DLLs within it Once this is done all VDA clients will automatically detect and use the Bea Tuxedo Workstation Client DLLs to access TM2200 on the mainframe Thus you do not have to perform any special T
67. al Dump Analyzer You should create a directory on your PC that will be used as the default directory when saving and reading dumps Specify this directory in the Dump save directory prompt You should also create a directory on your PC that will be used to save program sources This directory will be used when you request The Visual Dump Analyzer to open a source in your preferred editor Specify this directory in the Source save directory prompt Settings Abort Report Filter Alert Message eMail Settings REMEDY Graph Settings General Settings Search Path Applications Reports Settings General Settings Internal YDA Settings IV Show source line numbers Enable tracelog da log IV Warn on source with CTS line numbers v Enable internal CrashHandler Initial prompt for dump Connect to server using Open maximized v Disable hover function Decimal relative address Download Settings Sort subroutines in order of appearance v Read related sources Show subroutines defined within procs v Read all allocated DBAs IV Show what s New on new releases of VDA Read all located Directory Settings E MyD umps Dump save directory Last Used v Preferred server Temp Source save directory NORMAL v Preferred mode Notepad exe Editor name Cancel Apply Viewing the dump The Visual Dump Analyzer uses splitter windows of six different types in displayi
68. all files known to The Visual Dump Analyzer even if the file is not included in the active File Report Page 76 Setting Freespace Files Warning Levels The Visual Dump Analyzer includes two types of configurable warning levels a General Warning Level valid for all files on a given system and a specific Warning Level valid only for a specific file on a given system The General Warning Level is shown on the File Report as a dotted line across the graph To set the General Warning Level right click the white space of the File Report and select Set Warning Level in the Pop up menu This will open the dialog below Freespace File Warning Level Enter the General Warning Level pct specifying how full files can be before an alarm will be raised Enter the General Warning Level pct 80 Cancel Note that the Warning Level set in this dialog is only valid for the system a File Report is being generated upon This allows you to use different General Warning Levels on each system To set the Specific Warning Level for a specific file right click the bar related to the file you re interested in and select Set xxFILE Warning Level Alternatively you can right click the white space in one of the Detailed File Analysis graphs for the specified file In either case you will be directed to the dialog below Freespace File Warning Level Enter the Specific Warning Level pct specifying how full file 30F
69. be activated When the Show Full Files is selected in the Pop up menu the Detailed File Analysis is automatically performed on the full file and a warning flag is shown in the top left corner of each detailed graph D Value 4 65 7 Warning Level lt 90 Recs lt D Recs Recs gt D Graph 1 To view the Alert Message Analysis text describing the results of the analysis and explanation of the error click the red warning flag Page 78 Because the Alert Message logic is based upon an analysis of the new file status retrieved by the refresh logic this feature must be turned ON That is turning the refresh logic OFF will cause the Alert Message to be turned OFF as well Raising Alert Messages for freespace files works just like raising Alert Messages for aborts The configuration parameters in Tools Setting Alert Message that define how Alert Messages are raised apply to both aborts and files See Running in Monitor Mode Alert Message Analysis for Freespace Files The Alert Message Analysis provides the results of the Detailed File Analysis Report This summary gathers information from the files themselves and the Severity Setting in the Graph Settings in Tools Settings Graph Setting All this information is processed and the final result is used to generate a natural language text explaining the reason for the warning To see this analysis click the red warning flag in the Detailed Analysis Report graphs
70. been referenced a specified number of times or second when the TRAP variable obtains a specific value Determining the specific TRAP hit that you would like an abort to occur can sometimes be difficult To assist with this sometimes it is helpful to reschedule the transaction with traces on and without an abort request Then in the trace file you will find all the TRAP hits that have occurred along with the hit number for each of them By scanning the trace file you can easily identify the TRAP hit count that results in erroneous data to appear Next after setting the hit count within the above dialog you can reschedule the transaction thus triggering an abort at this point of interest Finally you need to consider how often you want the snap information to be written to the trace file By default a TRAP will only cause the TRAP variable to be snapped written to the trace file on TRAP hits thus providing you a history of references to the variable In addition to TRAP hits you can also request each CALL to and RETURN from an ACB or FLSS routine to cause a snap of the variable To request The Visual Dump Analyzer to snap the variable on all ACB and FLSS routine activity deselect the Snap on Breakpoint Hits only in the Snap Info area Page 39 At times this TRAP feature can produce very large trace files but this volume of data can often be invaluable in resolving some of the most difficult errors and aborts Once the T
71. below the D value has been used or when 80 of the 25 portion above the D value has been used the file will have reached its Warning Level The files are identified by either their TIP file number or their USAS file number To control the way the files are shown right click and select either Show TIP File numbers or Show USAS File numbers You can control the initial format of this display within the Graphs Setting pane in Tools Settings Graph Settings All the graphs shown in Files Report and in the Detailed File Analysis are normally shown using percentages instead of their actual values This can be toggled by simply double clicking the white space in the graph Page 75 To obtain more detailed information for a given file just single click the bar representing the file you re interested in and actual file sizes along with information on subfiles in the physical file will be displayed Name 30FILE TIP File 430 USAS File no 130 D Value The file is 48 5 full 955 484 of 1 855 488 basic records are available The file contains 65 257 3 free basic records marked as Release Only subfile KF 01202 PCI FLIGHT NBR INDEX subfile KI 02202 PCI MASTER DATA IND subfile KM 03202 PCI MASTER DATA subfile 04202 PCI TELETYPE INDEX Subfile KR 05202 PCI TELETYPE DATA subfile K 07202 PCI SEGMENT FILE Subfile KJ 010202 PCI TIME TABLE INDEX Subfile KK 011202 PCI TIME TABL
72. cation if it occurs outside this time period Similarly Alert messages that due to aborts with a severity setting of LOW will request notification of the responsible application programmer to be delayed until next morning if it occurs after 4PM on Monday through Thursday If it occurs after 4PM Friday or during the weekend it will request notification to be delayed until Monday morning Alerts during normal working hours 9AM through 4PM will cause notification to be immediate The NORMAL severity setting is the default and it is also the setting used for all abort types that are not updated in The VDA Knowledge Database Alerts based on NORMAL severity aborts will request the notification of the application programmers to be immediate Hints logged with a program name of ALL can for safety reasons be set to severity NORNAL only You can however always log a hint for a specific program with the same XTCA error code and then change its severity setting Because the severity setting for aborts can have a significant impact on the way the system is being monitored only known users See the User Identification can change the severity settings from NORMAL Page 50 Resolve Programs A Resolve Program is an auto generated FTN program that is used by The Visual Dump Analyzer to resolve expressions that relate to one or more application procs The following program fragment gives you an idea of its simple but effective structure
73. d even relocate the TRAPS when necessary For example if you set a TRAP on a DBA the TRAP will naturally become active when the DBA is allocated If however the DBA is later expanded causing it to move location The Visual Dump Analyzer will ensure that the actual TRAP address is automatically recalculated and reset to match the new location of the DBA The same is true for variable TRAPS If a TRAP is set on a variable in a program that is called repeatedly the variable s stack may not be allocated at the same location each time the program is called Thus The Visual Dump Analyzer will recalculate the absolute TRAP address and set it to align with the active stack address Continuing The Visual Dump Analyzer will simulate an update to the variable when it is initially created so its initial value is displayed when it first exists on the stack This is done because a variable s type and form of initiation if any may not cause a true update Breakpoint occurrence By simulating a Breakpoint update hit however you will always be able to see what the initial value of a variable is when a program starts execution A simulated breakpoint update hit will also be simulated for any I O read operation that updates the TRAP address in a DBA That is I O reads to DBAs that cause the TRAP address to change are handled as normal TRAP hits even though the Exec will actually not cause a true Breakpoint interrupt for this type of update To
74. d the Alert Message Warning levels to be exceeded If the Alert Me tic mark in the Pop up menu is set and the analysis of the report reveals that one or more of the warning levels have been exceeded an Alert Message is raised An Alert Message is raised by animating a small warning window in the bottom right corner of your screen This window will be shown as the top most window so that it will always stay visible It will however not take the input focus so you can continue working without interruption Too many identical aborts on PROD E The Alert Message will be raised even if The Visual Dump Analyzer application is not the active application at the time Even if The Visual Dump Analyzer application is in the background or is minimized the Alert Message will be raised Once the Alert Message is raised you can use it to quickly activate The Visual Dump Analyzer application by clicking the warning text itself The Visual Dump Analyzer will be brought to the foreground and maximized and the Abort Report that has raised the Alert Message will likewise be maximized to give you the best overview The aborts that have caused one of the Alert Message Warning Levels to be exceeded will be colored RED and the Alert Id column will be updated with the ID number of the Alert Message To see the Alert Message Analysis text giving the result of the analysis and explanation of the error click the Alert Id in the Abort Report If the white
75. dump that you are viewing DEL IF IB3CHP IBCLEM Li THEW 363 CALL SZFEPN 194 ENHDIF IF 1 WETURHN CALL ABORT Symbolic Debugging When the status bar is GREEN LIL you can click on any variable define or parameter within the source code and its value will be displayed in a small box adjacent to the tag you click on This will quickly provide you with many answers related to the status of processing shortly before the dump occurred These values are presented in octal decimal ascii and fieldata Pop up Menu Functions There are many helpful functions that you can perform via the Pop up menu of the Source Code window A description of these follows When the status bar is GREEN you can Walk the program call stack WalkBack Here you can symbolically follow each forward call taken by the processing Walk this path forwards or backwards routine by routine from the very first call from the ICP until you end in the aborting subroutine See The Program Call Stack WalkBack When the status bar is GREEN you can Walk the jump stack for all contingency type aborts Here you will be able to view the contents of the entire Jump Stack symbolically never having to look at a single octal address After selecting this option step by step you will be moved between the lines of code that have executed just prior to the abort occurring Go to Last ACB call Go to Abort addre
76. e 4 65 7 Warning Level lt 20 Recs lt D Recs Recs gt D Graph 1 As a consequence the free Recs are shown using three sets of two bars Page 82 The first bar depicts the counts for the entire file and is labeled Recs It is colored GREEN because the Warning Level has not been exceeded whereas if it had been the graph would be shown in RED The portions of the file below and above the D value are labeled Recs lt D and Recs gt D respectively It is important to realize that the Freespace Handler must select new records for allocation based upon the D value setting which may result in a record not being able to be allocated even though space is available on the other side of the D value setting Further note that Release Only bitmaps are determined and their free Recs are shown The second bar shown here in REB displays the net growth of basic records in the file since the last time the freespace handler statistic was reset When the growth indicates a net allocation the bar is shown in RED whereas net de allocation is displayed as GREEN This graph gives a quick overview of the file usage while also showing if the D value is set correctly When the bars in this graph are almost identical in size it is a good indication that the D value is set correctly as the percentage of free basic records is almost the same both below and above the D value If any of the bars in this graph get below the Warning L
77. e AP DBA and Memory Allocation and Tracing in User Guide for VISUAL TRACE and VISUAL PERFORMANCE ANALYSIS Visual Breakpoint Traps will aid you with this situation as it enables you to run a trace without producing a trace file thereby not altering the memory layout for the transaction Since you do not get a trace file to look at you will have to force a new abort when the bad value is stored in the memory location Before running the transaction you must inform Visual Breakpoint Traps to not produce a trace file You do this by pressing the Advanced button in the reschedule dialog and selecting Drop the AP DBA to preserve memory layout See Setting Advanced TST Traces Now reschedule the transaction while ensuring that you have turned OFF all other TST flags that will cause data to be written to the trace file as it will cause the trace DBA AP to be allocated and thereby change the memory layout This time you should get an abort informing you of the specific code that updated the memory location that contains the bad value Page 42 Setting Visual Breakpoint Snaps The Visual Dump Analyzer allows you to set a SNAP on any memory location causing its value to be written to the USAS trace file as a separate VDA SNAP line You can set SNAPS on Variables DBAs PDBs Basic Mode Addresses and Extended Mode Virtual Addresses The Visual Dump Analyzer will write the SNAP lines to the trace file when one of f
78. e Scan can also be started from demand by starting the batch job as stated below Generally however scanning all the files once a day should be sufficient START USAS SEDS FILE FSSCAN The second feature to verify the control information for freespace files can only be performed by running the SEDFRS BATCH program in demand mode This program has a built in help screen to assist you with its use See The Visual Dump Analyzer Scanning Freespace Files Page 93 Table of Contents USER GUIDE FOR THE VISUAL DUMP ANALYZE R ssccsssscsssssscssscccssssssnccecccsssscssceccccssscssssececcesscsssscececesscssesseess 3 OVERVIEW EE 3 THE ENVIRONMENT eocec ee doose vc eot va ve eiae o riOU ETS ESS Ua Nea pat dose rose dance ATOS eu De seas Vae esso e e Ra ER 3 SYMBOLIC elo 3 CONHIGURATION sissncctesessscocsevedecessccssrcancoseseuetecescessdensessvssvonssssecevecssccesdevesocessessvesdesce seus sossuencessoSesesesdeseves dessesdessscssssevosucesaes 4 COMMUNICATION SETUP kraner helene ele 4 GETTING STARTED AUTO CONFIG ccccccccccccccceceeescececececececeseveeseseseseseessvesscsesesessessessseseseeeseessesesesesesesesesesesesesesesesesesenseeeeess 4 SEARCH PATH BOE 0d M BI ue 5
79. e Visual Dump Analyzer will automatically set the Breakpoint Traps or Snaps on the PID that you have set in the Source Variable or Data Windows You will then be informed of the status of the TST settings as part of the response dialog It is important that the version of the absolute element The Visual Dump Analyzer has found and used to calculate the actual Breakpoint Traps is the absolute that will be executed by the rescheduled transaction This is because Traps and Snaps are set by using an absolute address and not a line number or variable name Moreover the correct absolute is required to convert the line number or variable name to the correct absolute address The Visual Dump Analyzer will attempt to use the same version of the absolute element as the one used to analyze the dump However the correct absolute element for reschedules is always the version of the absolute that the rescheduled transaction will actually execute This may or may not be the same version of the absolute found to be correct when analyzing the dump If the correct version of an absolute element is not found the absolute address that is calculated to set Traps and Snaps will be flawed and then the Traps and Snaps will not be set in the correct locations of the executable code This will cause very unpredictable results Once the Reschedule Msg Now button has been pressed and the TST settings have been placed you can press Show TST flags to redisplay the re
80. e ee ea VE E NE e UE E GEL VERE e dee tee vost sete e leet even 30 REMOVING TST TRACES AGAIN 30 SETTING VISUAL BREAKPOINT ee eese tasa sese e eese toas ss e testo asses e ee tete asas ses 31 SETTING TRAPS ON LINE NUMBERS E 32 SETTING TRAPS ON MASM INSTRUCTIONS 0 0 0c0cceceseseseseseseeeceseseseseveseveseeeseseseseseseseeeseeeseseseseseeeseeeseteseeecesesesesereseeesenens 33 SETTING TRAPS ON INTERNAL SUBROUTINES cccscssseeeseseseeeseseceseseeeseseceveseveseseseseseseseseceseseseseseceseseeeseeeseteseeeseseseeesesesenens 34 SETTING TRAPS ON HVTIP CALS 36 SETTING VISUAL BREAKPOINT TRAPS ON DAT eeeesessvevnvvnvsenensnnnnvnvenesensnnnnenenessnnnennnnnnennsnnnnnnennennsennnnnnenssnenensnnne 37 SETTING TRAPS ON VARIABLES RR PK 38 SETTING TRAPS ON DBAS OR PDBS d ee erbe Er M et nn An den tnt 40 SETTING IR APS FIXED ADDRESS reset 41 m FORCING ABORTS WHEN A MEMORY LOCATION GETS DESTROYED eee e e e n e n nnnn tr errer nn nnn rrr n a nne 41 SETTING VISUAL BREAKPOINT SNAP
81. e side trips to subroutines that have already been returned from as it is not a trace but instead is a snapshot of memory at the time of the abort If a dump has been read from the server using normal mode The Visual Dump Analyzer may not have read all the absolutes during the initial analysis The absolutes that are not yet read are not broken down and interrogated and are thus shown in the WalkBack picture without any detailed information However by double clicking one of these absolutes in the drawing you will inform request The Visual Dump Analyzer to read and interrogate the absolute and update the WalkBack drawing with detailed information on this absolute Page 23 m The Data Display Window You can view raw data from the dump in a variety of formats by using the Data Display window The formats are selected by using the Pop up menu for this window type To set your preferred data display format just enter Customize Data colors and select an entry within the Initial data format drop down menu The Visual Dump Analyzer is aware of many data areas that are divided into smaller sections To provide a better overview of the data these areas are automatically divided so each section is clearly labeled with its own title and relative addressing 000001000035 000000000000 000000110033 000100040000 000000000000 000000000000 000000000000 Input Message 0000 0004 nn1n 104 116040111116 nnnnnnnnnnnn 007
82. e the IB F and the CA F views along with any specific application views that could be of interest as this will enable these data blocks or DBAs to be referenced using their symbolic names This can be important because if the dump is shipped to a different site the location of individual CA and IB block fields may not be the same Page 14 Customizing colors and fonts You can change the colors and fonts that The Visual Dump Analyzer uses by selecting Tools Customize Different colors and fonts can be set for each of the main window types by selecting the tabs at the top of the dialog box Upon clicking OK on this dialog box the changes will have immediate affect To revert back to the default settings click Reset All I ij x Source Colors Data Colors General Colors Memory Drawing Colors Select Language and UFTN v Bold Italic Keyword FF Color COMPILER IMPLICIT EQUIVALENCE DELETE PRECISION Keyword 2 MT Color LE GE GT LT AND OR XOR Macro Keys Color COML CINY CBUG CDUM Separators Color 0 7 i Color Selected Font and Size Strings Color Comments _ Color Courier New Size 10 Col 73 80 FT Color Font Line numbers Color Default Reset All ii E Cancel Apply Page 15 Customizing settings You can use Tools Settings to customize settings within The Visu
83. ed you can activate or deactivate it by using the Pop up menu in the Abort Reports Further you can use the Report Filter to permanently limit the Abort Reports to a specific application or simply to search the Abort Reports for a specific program Page 70 Command line options You can use the command line to make The Visual Dump Analyzer automatically open one or more Abort Reports or Files Reports when it is initially opened In the Windows shortcut that is used to open The Visual Dump Analyzer Vda exe add the following Vda exe R lt no of days gt lt system id gt M lt no of days gt lt system id gt F lt apl gt lt system id gt The R and the M option both use the same data sequence The first data item is a numeric value defining the number of days that is covered by the Abort Report and the second is the system name from which to read the Abort Report Multiple Abort Reports can be initially open by simply adding an entry in the command line for each report Abort Reports that are opened using the R option will all be shown as tiled windows whereas Abort Reports opened using the M option will be opened with the window being minimized To open a File Report use the F option followed by the application name e g ALL RES TKT and system id Finally File Reports and Abort Reports can be combined in any manner Saving Abort Reports to disc Once an Abort Report has been read from the mainframe you can
84. ed back and forth using the Abort Report Pop up menu Showing Abort Reports This report form which is the default includes one line for each abort along with all its diagnostic information Being sorted with the newest abort on the first line the Abort Report presents you with an immediate and accurate status on how the USAS applications are functioning Further by combining this report with the Auto m Page 55 Refresh and Alert Messages you are provided a powerful tool for monitoring the USAS applications and alerting you immediately when aborts occur By detecting aborts very early and raising alerts The Visual Dump Analyzer enables you to take action before the aborts become a serious problem b Fisua Dume Analyzer 4 Todas Eeport from PRL Mode ALL 100 31 1857 15 53 15 1 917 15 98 20 ITAL 1545736 14 47 32 iam 15 24 51 15 75 18 15 29184 15 13 20 14 59150 14 57 53 123164 177004 553 512 ENIS 3 pm PEL Er 13 47 41 IE He rd np 74 FE 1 00 CT EI FE 29 18 SE Zhi BE FE 3 20 CET HE HiST SE pre rar D na 2 2 EE CO x xou gm amp EDIFPACE EDITREACT EI4FPACS ELAFPALS EDIFPACS ELAFFACS EDMFRACS EDIFPACT ETAFPACS EDIFPACS ETATPACT EDIFPACS EDIFPACS CPA 123 LA EFRLCHCNS 100 Sn ETARE
85. edict if the instruction is actually being executing and therefore should be avoided To clear the TRAP again right click on the 0 line and select Clear Breakpoint Trap and the TRAP will be cleared Alternatively on the main menu you can select Tools Clear Breakpoint Trap Setting TRAPS on MASM instructions Setting TRAPS on an FTN line number will attempt to set the TRAP on the first instruction generated by the specified line number When the FTN Z option is used however the compiler sometimes merges instructions from multiple FTN lines in order to optimize the execution and thus the TRAP may not be set on the exact instruction that is wanted To set a TRAP on a specific instruction right click anywhere in the source window and select Show MASM code Once the masm code is shown simply right click the desired masm instruction and select Set Breakpoint Trap on line This will cause the TRAP to be set on this precise absolute address CALL PRGSAV SAVE EXPLAIN REQUESTE SPCERR CODE IF SPCERR NE O 0R DMPTBL CNTPKT HE O THEN As with line number TRAPS it is default is to force a new abort the first time an instruction is executed This can also be altered in the same way by right clicking the R ED line and selecting Set Abort Count Page 34 Setting TRAPS on internal subroutines As an alternative to setting a TRAP on a specific line number The Visual Dump Analyz
86. eespace file has been raised a new Alert Message will not be raised for the same file within the next 24 hours unless the new Alert Message has a higher severity Configuring Alert Message Warning Levels for Freespace Files To configure how File Reports are initially opened in The Visual Dump Analyzer use the Graph Setting pane found in Tools Settings Graph Setting This will open the below dialog allowing you to control the way File Reports are shown along with how Alert Messages are raised for freespace files General Settings Search Path Applications Reports Settings Abort Report Fiter Alert Message eMail Settings REMEDY Graph Settings Graph Settings Show Graphs IV Raise Alert Messages Show Free Basic Recs Graph IV Draw thin box around Graphs Show Allocated Recs Graph Show USAS file numbers rather than TIP numbers Show Subfiles Graph IV Show detailed graphs for all FULL files I Show Recs per Subfile Graph Show detailed graphs for ALL files IV Show Fragmentation Graph Severity Levels Show File Growth Graph High Minor Low Show Record Size Graph When Warning Level WL is boken C C I Show Function Calls Graph When lt 75 of the WL remains C C v Show Historical Graph When lt 50 of the WL remains Show Graph Explain Show Bitmap Graph r Auto Refresh 5 hours Cancel Apply C Off thou 2hous Warning Levels
87. elected relocatable When the source code found by The Visual Dump Analyzer is not the one you desire use this button to enter a dialog that allows you to browse the mainframe files to select a new one Click on the Subroutine button to view the date time the selected subroutine was created along with the line numbers it spans within its element Absolute PxcRro Relocatable PxcRTO Subroutine SENDIT You can use this toolbar to change the contents of an active Source Code window by selecting a different subroutine or relocatable within the drop down lists If multiple Source Code windows are in view the selected entry within the drop down list indicates the one that is currently or most recently active Moreover if you wish to change the contents of a Source Code window just click on it to make it active and then select a different entry within these drop down lists The Data selection toolbar Page 17 This toolbar also contains three buttons with an associated drop down list for each Click on the Dba Pdb button to view information on the selected data area Click on the View button to select a private view or a view from a specific file See View Construction This dialog will allow you to browse through your files on the mainframe searching for a specific view All public views are always in the drop down list for easy selection Click on the Cmn Block button to view information on the
88. er a specific l Bank instruction is executed and D Bank TRAPS are traps that that occur when a given D Bank address is referenced or updated The Visual Dump Analyzer greatly simplifies the complex task of settings Breakpoint Traps To seta trap you only have to point at a specific location or piece of data where you want the trap to be set and right click to open the Pop up menu Then just select Set Breakpoint Trap and this will cause the location or data to be highlighted in R D indicating that Breakpoint Trap has been set Once a Breakpoint Trap has been set you can reschedule the input message again and The Visual Dump Analyzer will set the TRAP as requested before the reschedule Of course not all aborts can be reproduced by rescheduling the input message again but a vast majority of aborts can be With these Visual Breakpoint Traps is a very effective way of finding the cause of an abort See Rescheduling the Input Message Page 32 Setting TRAPS on line numbers In order to set a TRAP on a specific line number just right click the line you want to set the TRAP on This will open a Pop up menu where you can select Set Breakpoint Trap on line This will cause the TRAP to be set and the line will be highlighted in RED In the Source Window indicating that the TRAP is active THIS SUBROUTINE WILL SHOW THE CONTIGENCY ERROR TEXT C BY CALLING ERRPR E
89. er allows you to set a TRAP on an internal FTN subroutine A TRAP that is set on an internal subroutine will cause the TRAP to occur on both the entry to and the exit from the subroutine Setting a TRAP on an internal subroutine differs greatly from manually setting the TRAP on the line number of the subroutine statement This is because of the way FTN enters and exits subroutines A TRAP that is manually set on the line with the subroutine statement will cause the TRAP to only occur on the exit from the subroutine and not on the entry to the subroutine Requesting a TRAP to occur on both the entry and exit from an internal subroutine combined with the snapping of data is a very effective way of verifying what changes an internal subroutine makes to the snapped data The trace will show the values of the snapped data on both entry to and exit from the subroutine regardless of the RETURN statement that is used to exit This is even true if the subroutine contains multiple RETURN statements or if the subroutine uses an error return i e RETURN n to exit Realize that the main routine in an HVTIP program or mapped in relocatable are technically also internal subroutines and thus you can also set a TRAP on the entry and exit from these routines That is you can set a TRAP that will occur every time your program is called and every time your program makes a return To set a TRAP on a subroutine right click anywhere in the Source Window showing the subrou
90. er may know it and can thus set up the needed configuration using the name alone Once you have entered this information press Auto Configure Now This will load the configuration for ALL of the Unisys servers thus enabling you to access all of them Search Path setup Before reading dumps you must first setup your personal search path for both absolute and source elements This will enable The Visual Dump Analyzer to examine the correct files when looking for absolutes and sources Settnos x Abort Report Filter Alert Message eMail Settings REMEDY Graph Settings General Settings Search Path Applications Reports Settings Enter your personal search path to precede the system search path Dump server Personal search path for absolutes Use library load file in search TDEV E m LKBABS vDAABS System path Iv SYSABS PSSABS PCIABS CSCABS Enter the Source server and search path that relates to dumps read from above server Source server Personal search path for sources TDEV E m SASRESLKB SAS SYSLKB VDACOM System path IV PSSYCSSRC D PCIVCSSRC D PSSCOM PCICOM SYSCOM CSCCOM 9 Use commas to separate files in the search path Ex USAS MYFILE USAS SYSABS USAS RESABS E Cancel Apply To update the search path select Tools Settings and then click the Search Path tab In this dialog you can specify which personal files are to be searched before the files in
91. erts occur wihtin this time interval only the first will cause a REMEDY ticket to be raised Remedy fremedy visualdata dk eMail ist visualdata dk Subject SYSTEM GROUP YDA ALERT SEVERITY Groups HIS PSS gt AMA RES FDP HTL LYL SCC CSC eMail only warning HIS TKT gt TKT level is set to 50 HIS PCI gt PCI HIS SYS gt Default OK Apply To enable The Visual Dump Analyzer to raise Alert Messages via REMEDY both an email server EMAIL and a REMEDY configuration REMEDY must exist in the general configuration element If either section is missing or it does not name an email server the above REMEDY pane will not be visible Even though it is not required that The Visual Dump Analyzer is running in Monitor Mode to raise Alert Messages to REMEDY you should not configure your local workstation to raise REMEDY Tickets without prior approval from the person responsible for your REMEDY system Raising Alert Messages on the SPO The Visual Dump Analyzer can raise the Alert Messages as alarms on the Unisys Operator Single Point of Operation SPO console Alert Messages raised by The Visual Dump Analyzer appear on the SPO just like other alarms that are raised and require action by the Unisys Operator When The Visual Dump Analyzer has raised an alarm on the SPO and the Unisys Operator opens the alarm he will be shown the entire Alert Text informing him about the problem along with detail
92. ese default warning levels should be sufficient for most users however you can set more advanced levels for specific systems The advanced sitting will allow you to configure the same four Alert Message Warning Levels but with individual settings per system Further you can specify different values depending on time of day and day of week Warning on All Aborts When selected ALL aborts will cause an Alert Message to be raised whenever an abort occurs The Alert Message Analysis may group more aborts into the same Alert Message if they are found during the same analysis Because this setting covers all cases of aborts it cannot be combined with the other warning levels Warning on too many identical aborts Being the most commonly reached warning level this level detects when a specific program errors multiple times in the same way When this level is reached it is usually an indication that a single specific problem within one application is occurring Page 64 Warning on too many different aborts When this level is reached it is usually an indication of a more serious problem that is not limited to a specific program Instead it often affects more programs that may not even belong to the same application In general it is likely to be an error in shared functionality or shared database contents If this warning level is reached and the aborting programs span three or more applications of which SYS is one the Alert Mess
93. ested in an alert due to this type of abort This level can also be used when an aborting program has been fixed but for it is not be placed into production until a later time In this case it may be desirable to temporarily mark the abort type as SAFE until the program is moved into production The HIGH severity setting is the second severity setting that is used to control when Alert messages are raised Aborts types with a HIGH severity setting will always cause an Alert without regard to how the Alert Message Warning Levels are configured Use the HIGH severity setting with abort types that you always want to raise an Alert message so you can take immediate action Dumps with a HIGH severity setting will be colored RED the abort reports to inform that they are of HIGH severity The LOW and MINOR severity settings do not control when Alert messages are raised These severity settings instead instruct the system operators to delay a call to the responsible programmers in the Alert Message text Note that the Alert will be raised but the text in the Alert message will request the notification to the application programmers to be delayed until the next morning or Monday morning according to the severity setting Alerts messages that are due to aborts with a severity setting of MINOR will request the notification of the responsible programmer to be delayed until next morning if it occurs between 9PM and 9AM whereas it will request immediate notifi
94. evel an Alert Message will be raised If you prefer to have the actual counts with this graph just click the individual bars Detailed File Analysis Graph 2 The second graph in the Detailed File Analysis shows the number of allocated records per record type Each record type has two bars depicting the actual number of allocated records The first bar shows the number of Logical Records within this record type and the second bar shows the number of Basic Records within this record type Graph 2 In this example about 60 of the logical records in this file are used for record type 1 RT 1 whereas this is equivalent to about 13 of all the Basic Records currently allocated in the entire file In order to display the actual counts for each record type just click the individual bars Page 83 Detailed File Analysis Graph 3 The third graph displays the number of allocated logical records per subfile t As per 08 12 05 20 01 Graph 3 This graph along with the fourth graph gives a good overview of all of the record types that are allocated for the individual subfiles To view the actual counts for the subfile click the individual bars Detailed File Analysis Graph 4 The fourth graph shows how many records are allocated for each record type within each of the individual subfiles As per 08 12 05 20 01 Graph 4 As with all of the graphs double clicking the white space within the graph will toggle t
95. execution of line 377 This will cause the SNAP lines in the trace file to be displayed as follows 0002 VDA VAR NEXT 000000000000 ADR 140300 AFTER STACK ALLOCATION 0003 VDA BRKP BREAK POINT HIT NO 1 IN PX7AGS LINE 377 0004 VDA VAR NEXT 000000000000 ADR 140300 AFTER BREAK POINT Note that because the SNAP data is a variable NEXT The Visual Dump Analyzer has added an additional line displaying the value of NEXT right after the stack allocation to inform you of its initial value Be aware that ACB and FLSS calls can be nested so that one ACB routine may call other ACB routines When this happens you will see both the BEFORE and AFTER SNAP on the initial ACB routine call but for technical reasons only BEFORE SNAPS will be produced for the nested ACB calls However SNAPS for XFSxx and XDFxx I O routines will always be shown with both BEFORE and AFTER lines even when they are within nested calls Page 43 Setting SNAPS on variables To set a SNAP for a variable simply right click the variable name in the Variable Window to open the Pop up menu and select Set Variable Snap Variable Type Scope Size Address Format vee al INTEGER LOCAL 4 516133 Decimal 5658150473 INTEGER LOCAL 4 516120 Decimal 11430298195 ACBBDI 24 3 INTEGER GLOBAL 4 516216 Decimal 34112928850 INTEGER GLOBAL 4 515773 Decimal 4303372320 CALABS CHARACTER 12 GLOBAL 12 515543 Asci CALREL CHARACTER 12 GLOBAL 12 515745 Asci
96. ey show releases The last two bars will show the net allocation value in RER or net release value in GREEN Page 87 Detailed File Analysis Graph 8 The eighth graph very simply shows the setup of the individual records types in the file Once the file is established this graph will remain static as long as the setup remains unchanged 3 3 3 2 Ze 2 Ze 2 1 1 1 1 RT 2 RT 4 RT 6 RT 8 RT 1 RT 3 RT 5 RT 7 Graph 8 This graph displays the number of words that are used for each record type and provides a graphical picture of the area gained when switching from one record to the next If you double click the white space of this graph it will toggle between number of words and number of basic records used for each record type Detailed File Analysis Graph 9 The following graph of the Detailed File Report describes how the records within a file are used by each FCSS function Each file has its own unique pattern of FCSS function calls based upon the nature of the file and the data it contains 430 30FILE Function Calls Measured since 08 11 30 08 01 00 Operation Ratio Read to Write 7 70 Write to Allocate 21 61 Lock to Update 3 18 Graph 9 This graph provides very useful information when for example designing data structures for the file or evaluating existing application programs that use the file Page 88 The data within this graph includes ratios describing how t
97. gt Airline Code as requested gt INSERT gt INSERT program name apl COM proc f This will associate the fapl COM proc f to the Resolve Program named program name and ensure that this Resolve Program will be able to resolve all the expression names defines from the apI COM proc f The procs supplied here should be from the application COM files because the proc will be included in the Resolve Program using apl LIB procFSPEC and apl LIB procFDEF statements Multiple procs can be associated with a single Resolve Program To do this just enter the same program name as the input to SEDGEN for each proc that you wish to be contained within it Page 51 Step 2 Updating SEDUSR F proc This step will update the system proc SEDUSR F This proc is used on the mainframe by The Visual Dump Analyzer to associate expression names with their associated Resolve Programs Because of the global affect of this step performing it should be left to the person responsible for supporting The Visual Dump Analyzer After copying SEDGEN BATCH from SYSABS into TPF the SEDUSR F proc is updated in the following manner gt XQT SEDGEN gt PID number as requested gt Airline Code as requested gt NAME gt NAME SEDUSR F The updated version of SEDUSR F will be placed in TPF and must be compiled into The Visual Dump Analyzer program SEDVAL This process should be performed on a regular basis in order to simplify the generation of applicati
98. he VDA Program Book The VDA Program Book is used to link responsibilities between programmers and specific program when such a relationship exists This relationship is used by VDA to produce a more accurate Phone List in the Alert Message Analysis That is if a specific program causes an Alert Message to be raised on the operator console the Alert Message will contain a Phone List that is firstly based on information from the Program Book and secondly from information from the Address Book In short if the aborting program exists in the Program Book only the programmer that has specific responsibility for the program will be included in the Alert Message Phone list If it does not exist responsibility is assumed to be shared between all the programmers in the Address Book that are working in the application of the aborting program See Alert Message Analysis To view the Program Book select Tools Program Book in the main menu and the Program Book will be displayed Just like the Address Book the Program Book is shared between all VDA users To update an entry in the Program Book simply double click it Furthermore you can right click within the Program Book window and select the Add New Program Update Program or Delete Program features This dialog below allows you to update the Program Book Update Program Book Program name SED Responsible Programmers Address Book LKB Lars kruse B ggild Ge
99. he file is logically used The READ TO WRITE ratio describes how often the data in the file is read compared to how often the data is written The WRITE TO ALLOCATE ratio describes how often a record is typically updated after it has been allocated The LOCK TO UPDATE ratio describes how often a record is read with lock compared to how often it is actually updated This ratio should ideally be one with any value higher than this indicating that unnecessary record locks exist Unnecessary record locks can often cause problems with application throughput scalability and general application performance Thus for heavily used files this value should be kept as low as possible Detailed File Analysis Graph 10 The tenth graph is a visual representation of the D value It shows how much of the file is available for record allocation for each record type D Value 4 65 7 RT Z RT 4 RT 6 RT 8 RT 1 RT 3 RT 5 RT 7 Graph 10 In this example record types 1 through 4 are limited to 6596 of the file Because record types 5 and 6 are not specified in the D value allocation these records are not restricted by the D value and thus can be allocated within 100 of the file Finally record types 7 and 8 are restricted to only 35 of the file Page 89 Detailed File Analysis Graph 11 The eleventh graph displays a file as seen from the perspective of individual BITMAPs This unique view of a file shows the basic control informat
100. he percentage values to actual record counts To view the actual counts for the record type and subfile click the individual bars Page 84 Detailed File Analysis Graph 5 The fifth graph shows the historical development of the individual subfiles by displaying how the record usage has developed over time In general this graph conveys the cycles a subfile experiences along with how it is maintaining over time 430 30FILE Allocated Basic Records 08 11 06 20 01 08 12 05 20 01 Change Period gt BS 30FILE KI E Kk E ES KR E KS E KT EI KK OI KS ES KLM GB KLI ThFr Sa MoTuWzThFr Sa MoTuWeThFrSa MoTuWeThFr Sa MoTuWeThFr D9Nowv 16Nov 23Nov 30Nov Graph 5 If a subfile is continuously growing over time it is a strong indication that orphan records are being produced by the application Likewise when new development is introduced if a new and unexpected pattern is observed with the file it may indicate that application problems exist To view the actual count for a given day within a specific subfile click the line squares By default this graph will show the last 31 days To change the period click lt Change Period gt at the top left corner to open the dialog below Select period m Quick Select Select Specific Period C Last 31 days From date 20 Jul 08 C December 2008 C November 2008 To date 07 0 08 October 2008 C September 2008 August 2008
101. he variable within the displayed source code or reference it within an alphabetized table to quickly determine its value Lines of source code that result in abnormal execution contingencies are also quickly recognized as they are immediately displayed and explained making for fast and accurate solutions The Visual Dump Analyzer will also assist you in solving a dump by graphically displaying the complete instruction and data memory layouts by presenting all related source code and data buffers in a variety of formats by describing the nature of the dump in a natural language and by displaying all related information stored within its knowledge database Once a dump is solved you can add this vital information to The Visual Dump Analyzer Knowledge Database so the next time a similar abort occurs the notes and hints will be immediately available for yourself or your colleagues In effect the value of this tool increase with time for critical details that are easily forgotten will always be available for automatic reference The Environment The Visual Dump Analyzer resides on a PC having the MS Windows 95 98 NT 2000 XP VISTA operating system When you enter the name of a dump that you wish to analyze all data associated with this dump is automatically downloaded from the mainframe with virtually all further processing taking place on the PC Realizing some programmers may not use it on a very frequent basis The Visual Dump Analyzer strives
102. ialog box will allow you to read more sources than are initially read or to replace source code if it is determined to be incorrect Read Source from TDE E USAS SYSCOM PXCRTO was created 07 28 03 11 18 32 and it was compiled 07 28 03 11 18 33 To replace this source enter FILE ELM of its new location If FILE is omitted the search path will be used Use date check Source PXCRTO Browse Use the Browse button to scan the mainframe s program files to look for a different source code element Browsing Program Files for Absolute or Sources The Visual Dump Analyzer enables you to browse U2200 files directly on your PC Use this method to locate the correct version of an absolute or source code xi Look in SYSCOM EE al _ Size Type Modified DPS H 4 SYM 05 12 03 12 19 17 EM7HTH 201 SYM 05 12 03 12 19 17 EMCRTI 20 SYM 05 12 03 12 19 17 EMGATES H 14 SYM 05 12 03 12 19 18 EMBCTG 19 SYM 05 12 03 12 19 18 EMPDBL 207 SYM 05 12 03 12 19 18 EMSFBTAS 50 SYM 05 12 03 12 19 19 EMSVRI 21 SYM 05 12 03 12 19 19 EMXBCA 46 SYM 05 12 03 12 19 19 41 SYM 05 12 03 12 19 19 fey Chavocce 20 CEA 11702 19 10 90 File name File of type fan Files v Cancel Page 11 When browsing for source code on the mainframe the Look in drop down box will contain all the files defined in your source search path If you wish to browse a different fi
103. iated with the dump will be automatically displayed in the prompt areas for easy updating Page 48 If you wish to update a hint within the database just enter the program name and XTCA error code and press Read Hint After you have added or changed help information within the dialog box press Update Hint and the data will be stored in the VDA Knowledge Database on all mainframes To delete a hint retrieve it and press Delete Hint This will remove it from all systems Reason for abort text This abort text is a general explanation of the abort Being composed of freeform text it resides in a separate record of the database from the Hint text If the Reason for abort relates to an ACB routine and it is thus valid for all programs the syntax allows you to include the name of the program that produces this XTCA call followed by a colon as the first part of the text e g SFXDBA text This provides The Visual Dump Analyzer with the ability to obtain the source code associated with this abort if needed Hint text The Hint text is composed of freeform text and expressions By using expressions you can create very informative hints by incorporating values from the dump so they will be immediately available in the General Info window the next time an abort of this type occurs Moreover as The Visual Dump Analyzer matures these hints will become more detailed resulting in greater efficiency with dump analysis
104. iled File Analysis Report using a different D value than the one the file is currently using The purpose of this is to allow you to see the consequences of a possible D value change before it is actually updated See Detailed File Analysis above Rather than guessing on a new D value hoping it will eliminate a fragmentation problem within a file you can now determine with certainty if this is true or not This analysis includes detail of the actual number of free records of each record type that will become available if the D value is changed hence the name What lf D value To request a Detailed File Analysis using a new what if D value click the Detailed Analysis Report graph for the file in question and select What if D value on the Pop up menu Or click the bar that represents the file in the File Report This will open the below dialog allowing you to enter the What If D value What If D alue xj The What D Value Function allows you to analyze a free space file using a different D Value to see what the consequences of D Yalue change would be without actually changing the D Value For the file Use this Function to try out new and different D Values and compare the results to Find the best setting For the file Note this function will NOT change the actual D Yalue set for the file it will only analyze it using the specified D Value Enter new What If D Value v 100 v 8 cames Note that this will
105. ion used by the Freespace Handler to find and allocate new records Selected Bitresge O99 Bitna sine 024 Show Brtmaps Tull ttt ttt Ub Lous B B5 Up His B EJ 1n fore Dei Only A 104 ZU 104 Because the number of BITMAPs file be very large this graph only shows a portion of the file at a time To select a different portion of the file click on the horizontal select bar at the top of the graph This graph shows how full each BITMAP is both above and below the D value using a line graph for each area The status of each BITMAP is color coded Click the line square boxes to view a yellow Pop up window containing information on the actual values for the clicked BITMAP To get a more detailed view of a specific BITMAP click lt S how Bitmap gt in the top left corner This will open the below dialog x Enter Drep camber and press lt Rasd Ein 5 Clase r Emap 1 Bitmap 3 Size d Allocated Recs 227 Fres Pecs 401 Faced aj Lp 333 133866566666611 133365 PETE ee 66 666 666661 1 1 221 1 6666665 6666660446666 6eeess 1111 6 6 6556 6 1111 I AAA L 666666 LL 11 1 Eitmap 5 Sire 376 Allaucared Rees
106. ir constructs are the same freeform text and expressions You can update the VDA Knowledge Database by clicking Update Hint on the Pop up menu of the General Info window Hints are associated with dumps by their program name and XTCA error code Unique XTCA errors produced by ACB routines should use ALL as the program name for they will be valid for all programs Hints logged with a program name of ALL will be displayed whenever its related error code occurs throughout the system The VDA Knowledge Database contains three types of information the Reason for abort Hint text and X11 Hint Update Knowledge Database hint stores knowledge about specific XTCA abort type and then presents this information each time this XTCA occurs Use this dialog to enter hint information The X11 Hint is optional and should only be used for XTCAs within MASM programs that have destroyed the X11 return address Use this field to restore X11 to allow for proper debugging Remember that VIEW values can be used within the hint text Program XTC 11 Hint ALL 531 1 4DDRESS REG 40 3 Reason for abort LENGTH GREATER THAN STRING Hint text Abort Severity NORMAL Raise alerts as normal on this abort type v Abort Severity is the default severity for all aborts in this program Update Hint Delete Hint Close When you are analyzing a dump and you open this dialog the hints that are assoc
107. isc file so you won t lose any information or functionality by saving a dump to disc and then rereading it The Visual Dump Analyzer supports a multi document environment thus you can have multiple dumps or Abort Reports opened at the same time Use the Window command in the main menu to arrange and move between open dumps Emailing dumps Once a dump has been saved to local disc it can be attached to an email just like any other file Alternatively you can click the mail icon on the main menu and your configured mail client will be opened with the dump being attached to the new e mail that is prepared to be sent Note that dumps can be sent to different sites with the recipient being able to view the dump as long they have the Visual Dump Analyzer client installed Before sending a dump you should consider whether the recipient has access to the USAS dump d file on their mainframe at the time they are analyzing it If they may not and because only the information retrieved from the server is saved in the dump you should retrieve all the data absolutes and source code that may be needed by the recipient Because this may be difficult to know it is safest to include as much as possible Preferably you should use Full Mode or at least ensure that all absolutes are read if the dump was originally retrieved in Normal Mode You should also consider if the PDBs need to be included as part of the dump retrieval And finally you may want to retriev
108. it in the evaluation Similarly EDIFACT errors returned from either the edifact input or output handler are translated and included in the evaluation If any hints are contained within The Visual Dump Analyzers Knowledge Database they will also be included here See The VDA Knowledge Database When you have solved a dump you can select Update Hint from this window s Pop up menu and save the solution in the VDA Knowledge Database Then the next time a dump similar to this one is being analyzed your notes will automatically be displayed in this window Page 18 The Source Code window This window displays the source code that is applicable to the dump You can change the contents of this window by selecting a different entry within the Subroutine drop down menu of the Source Selection toolbar or by dragging a source code block from the drawing window See The Drawing Window section The left side of this window has a color 03 183 18 58 47 TOEV F coded status bar indicating whether the absolute and displayed source code is valid for this dump See Validity color codes You can click on this status bar to receive PRERTO zj sure z description of the validity status If this bar is GREEN you are free to use the complete set of Symbolic Debugging functions within this window If the bar is not you are responsible for determining whether the absolute and source code relates to the
109. king the Absolute button on the Source selection toolbar x USAS SYSABS PXCRTO OS 25 27 was created 07 28 03 11 23 36 The absolute was found using library bank 25 27 Verification of the absolute indicates that this absolute was actually the one creating the abort To replaced the absolute enter FILE PXCRTO OS of its new location If FILE is omitted the search path is used Auto read source too Absolute PXCRTO 05 Browse Cancel This dialog box will inform you of the location and version of the absolute that has been found and allow you to replace it if you wish Further if the dump was initially retrieved in Normal Mode only the aborting absolute is initially read and analyzed By using this dialog box you can request The Visual Dump Analyzer to read and analyze additional absolutes thus adding their analysis to the overall analysis of the dump Use the Browse button to scan the mainframe s program files to look for a different version of an absolute Page 10 Reading or Replacing Sources It is also important that you are using the correct source code version when you are analyzing a dump You can always check the version of the source by clicking the Relocatable button on the Source selection toolbar This will display the below dialog box describing the details of the source and allow you to select a different source from the mainframe if it is incorrect The below d
110. le you can add more files to the Look in drop down by clicking the add button The contents of the program files in this dialog box are retrieved from the mainframe at the time the file is selected Thus the elements that are shown are always current When browsing for absolutes the Look in drop down box will contain all the files defined in your absolute search path You can select a source or an absolute in the browse dialog by double clicking it This will return you to the original Read Source or Read Absolute dialog with the selected source or absolute being presented Page 12 Validity color codes When the dump is read and the source code is displayed in the Source Display window its validity is shown using color codes in the vertical status bar shown here in GREEN he hal Ay ee Lib Tg Cee GAS TOM CEATA SET TEEN TE im m Tor br M VEM pid 1891 gesultisg in an ETA abort in 5 IF iIBBLEK4j GOTO at Rime 965 At thia line the 0369 all t EMC aborted 1 i CALL disgnestie info gives im IHZEER 58I D ENDIF EBDIRAD U an EBHUTE n IF ilB5 HP IBSCLIHM LerOSTIC EVAL ON FSTiAB RT REQUESTED ARDET Memory Layout TEE SEES mwa lr dump Ey dhag ndrop cckardbl click E IG a5 ne mt 000 OMEN qi
111. ll be opened allowing you to set and customize the TRAP Forcing Aborts when a memory location gets destroyed Some of the most complicated aborts to solve are when a flawed process corrupts data that doesn t belong to it This type of memory destruction is normally very difficult to find as it is likely to cause aborts very far from where the data is actually destroyed often in a completely different process Memory that is destroyed in this manner can relate to common blocks variables or defines in DBAs Visual Breakpoint Traps makes this type of problem much easier to solve To do this first set a Variable DBA or fixed address TRAP for the memory location that is being destroyed and then reschedule the transaction Even though you have not requested the TRAP to abort the transaction the trace file will show a hit every time the memory location was updated Often times this is enough to solve the problem as the trace will show exactly where the memory location was updated what it was updated to and the code or process that performed the update Some very complex problems however can be affected by the fact that traces are turned ON and thus the data location that you are monitoring no longer becomes corrupted Instead the corrupt data may now be at a completely different memory location As a consequence the trace will not show anything wrong but will only inform you of valid updates to the snapped memory location See Controlling th
112. ly being monitored by an individual server This method of handling disaster recovery ensures a simple and safe way of handling cases when one server is not running or cannot access a mainframe for any reason These procedures also ensure that the situations are handled without manual intervention both in the disaster situation and when recovering back to normal operation mode again Page 69 Setting Reports Filters When Abort Reports are retrieved from the mainframe they will always contain information on all aborts taken during the time period covered by the Abort Report To limit the aborts actually allowed in the Abort Report you can apply a Report Filter to the Abort Report Once the Report Filter is defined and applied only aborts that meet the criteria defined in the filter will be shown in the Abort Report To define a Report Filter open the below dialog by selecting Tools Settings Abort Report Filter Settings General Settings Search Path Applications Reports Settings Abort Report Filter Alert Message eMail Settings REMEDY Graph Settings The Abort Report Filter allows you to control what aborts are included in the Abort Reports Apl Aborting Prg cao or or or Service Name i or or No Selection or or No Selection or or u indicates any character value Reset All Cancel Apply Once the Report Filter is defin
113. n along with information controlled by USAS SYS and information gathered by The Visual Dump Analyzer itself during its Freespace Scans First you can use The Visual Dump Analyzer to give you a quick File Report that informs you of how full each file is for all the FCSS freespace files on your system Next if a particular file stands out by for example being nearly full you can receive a more detailed analysis of it The File Report will be displayed as a bar graph that contains a bar for each FCSS freespace file in the selected application The bars depict how much of each file is used for normal record allocation and how much is blocked by a Release Only setting This graph provides all the essential information you need to get a quick overview of how each FCSS freespace file is setup along with the remaining amount of space that is still available for allocation Because this information is gathered and analyzed at request time it is always complete and up to date for all the files in the graph Second the File Report can be used to monitor all freespace files used by the USAS applications on a given system and automatically raise an Alert Message if it detects a file that is growing too full Third and final the File Report graph enables the user to quickly produce Detailed File Analysis for a specific freespace file This analysis is presented in a number of detailed graphs which contain virtually all the data that can be imagined about a
114. n the system being monitored Besides date and time stamps dump name function code pid number and application names the report includes a wide range of diagnostic information Abort Reports will contain much more information than the Basic Mode equivalent the DABT function as it is not restricted to 80 characters per line Further it gives the user control of what is to be displayed in the report Reading Abort Reports from the mainframe To read an Abort Report from the mainframe select File New Abort Report or click the Abort Report icon on the main menu In the dialog you can select the desired system along with the time period covered by the Abort Report Read Abort Report from Mainframe x System ID PROD C This Week s Report Cancel The Abort Report will retrieve information on all dumps from the time of retrieval for a specified time period back in time The time period covered by the report is indicated by the report name i e Today s Report Today s and Yesterday s Report This Week s Report or Complete Report Once the report has been retrieved the data displayed in the report can be limited by use of the Report Filter Abort Report Types Once an Abort Report has been retrieved from the mainframe it can be shown using one of three report forms Each of these reports will present the information differently and the display between these reports can be toggl
115. ng the information contained within the dump Further each window type has its own Pop up menu that allows you to use the functions that it supports Some of these functions are accessible from all window types while others are specific to an individual one To display its Pop up menu simply right click within any of these windows The Source selection and Data selection toolbars control the contents of the splitter windows These toolbars are initially docked at the top border of the main window although you can drag them to any other border or have them floating on the screen Resizing the windows You can use the three resize buttons those which look like the VDA logo in the main menu to change the size of the windows The left most resize button will set the windows to be of equal size The middle resize button will set the windows to their default sizes And the right most button will maximize the active window You can also quickly maximize a window s size by double clicking on it Then if you double click on it again the windows will return to their original sizes For more control in sizing windows you can also drag the borders between windows Page 16 Setting the active window The active window is the window that has most recently been clicked in When applicable the entries within the toolbars describe the contents of the active window Splitting the windows The Split window function is common to the Pop up menu fo
116. ng these time stamps If the backup server detects that the primary server has not updated its time stamp for more than 15 minutes it will take over the responsibility of raising Alert Messages on the SPO Further it will raise an Alert Message to the SPO informing the operator that the backup server has taken over as the primary server and that the primary server appears to not be running When the backup server detects that the primary server is again up and running successfully it will switch over to backup mode and once again leave the responsibility of raising the Alert Messages to the primary server Also it will raise a new Alert Message to the operator informing him that all is now back to normal and that the primary server is running again Similarly if the primary server detects the backup server time stamp to be more than 15 minutes old it will naturally continue raising Alert Messages but it will raise another Alert Message informing the operator that the backup server has failed Once the primary server detects the backup server is again up and running it too will raise an Alert Message informing the operator that all is now back to normal and the backup server is running again Two servers can be monitoring as many systems as you wish but it is imperative that they are monitoring the exact same systems Otherwise one server will conclude that the other one has failed because its time stamps are not present for the system that is on
117. ns 76 AUTO REFRESHING FILE REPORTS eeeessessvevnvvnnvenensnnnnvnnenesensnnnvnnenessnnnennennnnnnennnnnnvnnenenennnnnnennnsenennnnnnvnsenssensnnnnnnnnnenene 77 RAISING ALERTS MESSAGES ON FREESPACE FILES cccccscossssscssssssssccscccccssssssscceccesscsssscscccescsessssscceccsscssssscees 77 ALERT MESSAGE ANALYSIS FOR FREESPACE FILES ssosovoveveeessssnevnvnnnenssnsnnnnvnnenesensnnnnvnnnnenennnnnnvnnenesennnnnnnnennenene 78 CONFIGURING ALERT MESSAGE WARNING LEVELS FOR FREESPACE FILES eere eene eene eee 79 WARNING LEVELS FOR FREESPACE FILES eeeeeeeee e eenemenenenenenenenenesesesesesese ese ese etes esee stesse 79 FREESPACE FILE SEVERITY CODES 0 cccccccccccccccccccccccceusceuscecseeeseseseseseeeeeseseeeseeeseseseseseaesceeseeesceesesescecececseesecesscesscesseeeseeeeeaeees 80 ALARM METHOD 1 EARLY 80 ALARM METHOD 2 SIMPLE 80 DETAILED FILE ANALYSIS sis 81 DETAILED FILE ANALYSIS GRAPH 1 oiccecccecececccececececececececececececececececececececececececececececececececececececesecececececececececececesececesesesesees 81 DETAILED FILE ANALYSIS GRAPH 2 oic ccccccccccccececececececececececececececececececececececececececececececececececececececececececececececececeeececececesesers 82 DETAILED FILE ANALYSIS GRAPH 3 ss
118. ntly viewing is retrieved You are free to obtain more MASM code by selecting this function Open Source in Editor lets you view the source code within an editor of your choice That is you can use the full features of an editor while still having The Visual Dump Analyzer active To configure the editor you wish to use select Tools Settings and enter it in the Editor name prompt The Variable Window You can symbolically view local and global variables by using the Variable window This window will always display variables that are associated with the code being viewed in the Source Code window Moreover the register set can also be viewed in this window You can arrange the columns in this window by simply dragging their header to its new location or sort the columns by clicking their header Variable Type scope Size Address Format 14 CQITEM 1024 INTEGER GLOBAL 4 150631 Octal 0377777377777 CUR1 INTEGER GLOBAL 4 143451 Octal 033013 CUR2 INTEGER GLOBAL 4 143452 Octal 044040017000 END1 INTEGER GLOBAL 4 143445 Decimal 4033659907 ESCB INTEGER GLOBAL 4 143457 Octal 033142000000 ESCM INTEGER GLOBAL 4 143460 Octal 033115 ESCM1 INTEGER GLOBAL 4 143447 Octal 033115000 ESCM2 INTEGER GLOBAL 4 143450 Octal 033115000000 FCC1 INTEGER GLOBAL 4 143431 Binary 11111000100100000100000 FCC2 INTEGER GLOBAL 4 143432 Binary 1111000001 1000000000000000000 IBBUFF 120 1 INTEGER GLOBAL 4 155301 Decimal 402917376
119. o its relocatables and internal subroutines to give a detailed picture of the WalkBack within the aborting absolute Absolutes called earlier in the program stack will not contain this detail While you are inspecting a dump read in Normal Mode if you should request data from an absolute other than the aborting absolute The Visual Dump Analyzer will recognize that this data is missing In this case The Visual Dump Analyzer will prompt you whether the missing absolute should be read and analyzed now If you respond affirmatively the missing absolute will be read and analyzed with the result being merged into the overall analysis of the dump See Reading or Replacing Absolutes By using Normal Mode a dump can be first be analyzed rather quickly with much of the pertinent data being available Then if additional data is required from other absolutes they can easily be integrated into the overall analysis For this reason and because Normal Mode gives access to all the functions within The Visual Dump Analyzer it is the default mode that is recommended for inspecting most dumps Full Mode Full Mode is similar to Normal Mode except that ALL absolutes in the program call stack will be retrieved and analyzed during initial processing of the dump In this mode you will have access to all areas of the dump be able to use symbolic debugging and be able to see variables from all absolutes In Full Mode the WalkBack picture will display the complete
120. o that it can later be retrieved This is often a good idea if you wish to continue examining the dump at a later time or wish to save the dump for archival purposes To save the dump to disc just select File Save Dump to Disc or click the Diskette icon and the normal Windows dialog for saving files will be displayed The Visual Dump Analyzer saves the file in its native ascii format It will contain all information needed to reestablish the environment that you are in including the dump its analysis and the related absolute and source elements Storing dumps on your local disc has benefits Even when the dump has been removed from the mainframe or any of the related absolutes or sources are deleted you still have the capability of examining the dump Furthermore retrieving the dump from a local disc is considerably faster than reading it from the mainframe so if you expect to open it again for analysis saving it to a local disc will save time When you wish to save the dump to disc so you can later inspect it when the dump may no longer exist on the mainframe be sure to retrieve ALL the needed information before saving the dump See Emailing dumps Opening dumps saved on disc You can retrieve dumps that are saved locally by selecting File Open Saved Dump or Report or clicking the Open Folder icon This will display the normal Windows dialog for opening files All information related to a dump is kept in the d
121. ogram and have the same IBSERR or have caused the same contingency Showing Abort Severity Report The Abort Severity Report shows all of the abort types that have been marked with an Abort Severity different than NORMAL The Alert Severity Report is therefore a view into the Knowledge Database see The VDA Knowledge Database later in this document rather than into the SED Q common bank All the abort types that have been marked with a Severity other than NORMAL in the VDA Knowledge Database will appear in the Abort Severity Report even though an abort of the specific type has never occurred As with all report types double clicking the IBSERR column will automatically cause The Visual Dump Analyzer to find and read the specific abort hint in the Knowledge Database and present it in the Update Knowledge Database dialog for inspection or change Showing Statistical Report The Statistical Report will provide an overview for a given period of how many times each abort has occurred what severity each abort has and how often each application programmer has been called on duty due to Alert Messages raised by The Visual Dump Analyzer It is organized by application and Abort Severity To display the Statistical Report open a normal Abort Report then right click on it to open the Pop up menu and finally select Show Statistical Report This will open the below dialog where you can select the period you wish to be covered by the statistics
122. on Resolve Programs Generating Resolve Programs Once a Resolve Program is defined it can be generated When generating a Resolve Program all the procs associated with it are scanned and code is produced to ensure that all defines within the procs can be handled Therefore Resolve Programs must be re generated every time defines are added or removed from the procs they are associated with Failure to do so will cause compile errors when the Resolve Program refers to defines that no longer exist Further The Visual Dump Analyzer will be unable to resolve new defines when they are introduced Because The Visual Dump Analyzer cross references the Resolve Programs and their associated procs generating a Resolve Program is very easy After copying SEDGEN BATCH from SYSABS into TPF you only need to supply the Resolve Program name in the following manner gt XQT SEDGEN gt PID number as requested gt Airline Code as requested gt NAME gt NAME program name The generated the Resolve Program will be placed in TPF If one or more of the procs associated with this Resolve Program contain defines that need other procs to be included these can be added to the SGS cards stored in the element SED FILE SED BLD Please refer to this element for a description of this process Once the Resolve Program is ready to be introduced into the system use the same procedures as those used with other application programs This will result in it being compiled
123. or each freespace file ALL Freespace File ort it 153 1541 33 a au 417 ax ama aal sasi sasi sap sez seal seal 572 n 124 I 252 3 358 1 7 EG T 375 CJF 315 211 4 49 442 494 50 424 4 353 2 T 20 274 642 The Visual Dump Analyzer uses colors to inform of the status of the individual files in the File Report The GREEN color indicates that the file contains enough allocatable records to satisfy the Warning Level The RE color indicates that the Warning Level has been exceeded When a file has not yet been analyzed the file will be shown in GRAM The W amp lliGjjjjcolor represents the actual free records in the portion of the file blocked by Release Only bitmaps Note that the jiji color will show the actual free records blocked by release only and will not count the allocated records in the Release Only blocked bitmaps This means that the 26 color shows the amount of available space that will be gained by increasing the Release Only bitmaps If the record allocation in the file is controlled by a D value that splits the file into two logical files both logical files must satisfy the Warning Level for the file to be shown in GREEN For example if a file has a D value of 7 75 8 and the Warning Level is at 80 the file will surpass the Warning Level when one of the logical files have used more that 80 of the space reserved for that part of the file That is when 80 of the 75 portion
124. or occurs a tedious and time consuming process By simply entering X11 IBNOTE 1 as the X11 Hint for error 531 with ALL programs this extensive analysis will forever be avoided Moreover by entering this hint once in the database aborts of this type will always be able to be solved quickly and accurately Page 49 Abort Severity The Abort Severity setting enables you to mark specific abort types having a severity that is either higher or lower than normal The severity setting is used in two ways First it controls when Alert Messages are raised and second it determines when application programmers should be notified of the aborts when the alert is raised outside normal working hours Never alert on this abort type LOW Postpone alerts outside working hours until next working day MINOR Postpone alerts during the night until next morning NORMAL Raise alerts as normal on this abort type HGH Alert on ALL aborts of this type The SAFE severity level is one of two severity settings that are used to control when Alert messages are raised Aborts types marked SAFE will never cause an Alert without regard to how the Alert Message Warning Levels are configured Also these aborts are not counted when checking the number of aborts against the Warning Levels Dumps with a SAFE severity will be colored GREEN in the aborts reports to inform that these aborts are considered to not be harmful Use the SAFE setting when you are not inter
125. ou have selected thus you can put TST traces the selected pid prior to the reschedule if you want to JUNB 1P SKk 080123 1340 327C3E UNH T CLTREG 96 2 1A 327C3E 10013 Reschedule information Schedule Msg Now TDEV E Schedule on system Schedule on pid 58311 Schedule on valtab JHXCR TH Schedule as service Schedule message for the edifact handler Tum Traces Show TS T flags Advanced Close Because you will not know what PIDs are in the Pseudo PID pools associated with the interface you will not be able to select a proper PID Thus you will have to select a PID at random or leave the original PID as the selected PID and try to reschedule the message As a result The Visual Dump Analyzer will likely reject the PID once the reschedule is attempted The rejection of the PID however will inform you of what PIDs are in the Pseudo PID pool Therefore once you have attempted one reschedule you can change the PID number to a valid number from the pool and reschedule the input message a second time Page 28 If The Visual Dump Analyzer is forced to establish a dummy session it will add the letters VDA to the existing TPR field in HTH header For example if the original TPR was P00012345A it will be changed to PVDA0001235A to make it unique and easy identifiable Also be aware that The Visual Dump Analyzer will NOT remove any dummy TPRs tha
126. our unique events occur BEFORE SNAPS each time an ACB or FLSS routine is called AFTER SNAPS each time the called ACB or FLSS routine returns to the main HVTIP program AFTER BRKPT each time a Visual Breakpoint TRAP hits STACK ALLOCATION when a variable is initially generated on the program stack ELLE Each of these situations will cause The Visual Dump Analyzer to write a SNAP line to the trace file The SNAP line in the trace file varies slightly based upon the type of data that is being written but they all display the data value of the SNAP along with the event that caused it to occur Consider the following source line 2225 CALL PFMAO07 80001 INPUTI 1 CHARS NEXT If a SNAP is defined on the NEXT variable it will cause two SNAP lines to be written to the trace file First a BEFORE 07 line will inform of its value before the PFMAO7 call Second an AFTER 7 line will inform of its value when 7 has returned Below you will note that the NEXT variable was changed to the value of 003 by the PFMAO7 routine 0024 VDA VAR NEXT 000000000000 ADR 140300 BEFORE PFMAO7 0025 CALL SYSACB PFMAO7 CALLED FROM PX7AGS LINE 2225 0026 VDA VAR NEXT 000000000003 ADR 140300 AFTER PFMAO7 By displaying SNAPS before and after an ACB or FLSS routine is executed you can easily note whether a particular piece of data was changed by it In the below example the Visual Breakpoint TRAP has been set on the
127. path taken to the aborting location based upon the Program Call stack with all the absolutes being broken down into its relocatables and internal subroutines The primary purpose of Full Mode is to ensure that all data is initially analyzed and transferred to the client so the dump can be inspected even after the dump has been removed from the mainframe Therefore use Full Mode whenever you want to save the dump to disc for later inspection or when you wish to e mail the dump to someone for assistance Because a dump can potentially have many absolutes that relate to it initially analyzing a dump in Full Mode can be more time consuming Once retrieved by the client however this mode is the most efficient Page 9 Finding the Absolutes and Source Code In order to use Symbolic Debugging The Visual Dump Analyzer must have access to the correct versions of the program absolutes that created the dump Generally this is not a problem because the absolutes will be located in a system file for online dumps and in your personal file when developing code The practice of leaving program absolutes in temporary mainframe files should be avoided because The Visual Dump Analyzer is not able to access them When The Visual Dump Analyzer cannot be certain whether it has found the correct program absolutes you will be warned of the circumstance and be allowed to determine yourself whether the versions are actually correct If the correct version of
128. r PDB is allocated The Trap on Hits and Trap Abort Info areas are identical to those for variable TRAPS The Snap Info area however has an extra field allowing you to set the snap size directly This is because even though the TRAP will only be set for the specified word you can request more words to snapped and written to the trace file with each TRAP hit A quick way to set the number of words to be snapped is to select the words using the normal Windows selection method that you want to be snapped in the Data Display Window before right clicking the first word This will inform The Visual Dump Analyzer of the number of words you want snapped and preset this in this dialog when it is opened Page 41 Once you press the TRAP is set and the location of the TRAP will be highlighted in RE indicating that it is active To remove the TRAP select Tools Clear Breakpoint Trap in the main menu or right click the RED word and select Clear Breakpoint Trap Snap Because only one TRAP can be set at a time setting a new TRAP will automatically cause an old TRAP to be cleared Setting TRAPS on an fixed address TRAPS that are set on a fixed address are defined and execute exactly as TRAPS on DBAs and PDBs To do this drag the common block containing the fixed address to a Data Display Window and right click the address you want the TRAP to be set on Then the same dialog as for and PDB TRAPS wi
129. r all the window types except the Expression Window This function allows you to horizontally split one window into two and then work with the second one independent from all others The new window which will initially take on the characteristics of the window it has been split from can later be removed by dragging its border all the way to its top or bottom There is a limit of one split window for each window initially displayed by The Visual Dump Analyzer Changing window types The Change window to function is also common to the Pop up menu for all window types except the Expression Window This function allows you to change the view of a window into another window type For example after you have read the text in the General Info window you may decide that you no longer need it and would rather have another Data Display window By selecting the Change window to Data Display function you can easily do this The Source selection toolbar This toolbar contains three buttons with an associated drop down list for each Simply press the text of the corresponding button to obtain information related to the selected absolute relocatable or subroutine Click on the Absolute button to view the creation date time of the selected absolute its validity related to this dump the mainframe file it was found in and the method that was used to find it Click on the Relocatable button to view the compilation date time of the s
130. r system All aborts cannot be reproduced by simply rescheduling the input message again but in cases where this is possible it can be extremely helpful for interrogating an abort Moreover when an abort occurs on a production system it can be very beneficial towards solving the abort when it can be reproduced on a test system For this reason The Visual Dump Analyzer allows you to reschedule the input message on a different system For safety reasons however rescheduling messages on a production system is not allowed Dumps are often not taken at the most informative and beneficial location Therefore forcing a dump to be created at the right spot and at the right time is often the best way to solve a problem This can often be very difficult to accomplish By combining the Visual Breakpoint Traps logic with this rescheduling mechanism however it is greatly simplified You only need to decide which line number along the path of the program logic that you would like the dump to be taken and then right click upon it This will set the Visual Breakpoint Trap Once set you can reschedule the message again which will force a Breakpoint Abort Contingency 014 at the specified line number in the rescheduled transaction Now you will have a new and more informative dump to study See Setting Breakpoint Traps Finally you can use the reschedule logic to test and verify that you have repaired the problem by again rescheduling the input message
131. raised when the file has less than 15 available records and again Severity HIGH when the file has less than 10 available records Alarm Method 2 Simple Alarms By setting the Warning Level to a level that is considered critical and the severity code to HIGH an alarm of severity HIGH will be raised immediately when the Warning Level is exceeded This is a simple and effective way to raise alarms as no further alarms will be raised on the file during the next 24 hours regardless of the settings for lt 75 or lt 50 This is because an alarm with the highest possible severity has already be raised Page 81 Detailed File Analysis Once a File Report has been retrieved from the mainframe it can be used to request a Detailed File Analysis performed on any of the files in the File Report The Detailed File Analysis will analyze the file and develop a number of different detailed graphs with each showing a specific aspect of the file You can control how many of these graphs are initially shown by selecting them in the Pop up menu To request a Detailed File Analysis to be produced for a given file simply double click the bar representing the file in the File Report You can have as many files shown in the Detailed File Analysis as you choose by continuing to double click more files If more than one file is included in the Detailed File Analysis all of the individual graphs for each file are shown next to each other for easy comparison
132. rame To read a new dump from the mainframe select File Analyze New Dump or click the Analyze New Dump icon The following dialog will be displayed allowing you to specify the dump you wish to read Read Dump from Mainframe SystemID Mode NORMAL Dump Name PXCATOSD Include v Sources ou can reference all common blocks dbas pdbs and the PCT The aborting absolute is read along with the sources for all areas deemed of interest You can see variables detailed WalkBack pictures and use symbolic debugging for the aborting absolute However absolutes called earlier than the aborting absolute are not initially read but you can request them to be read when needed Data that isn t selected here will be read when referenced Show Today s Report Cancel Select the Mode See Dump Analysis Modes click OK and The Visual Dump Analyzer will begin reading and analyzing the dump This process will not be instantaneous because considerable information needs to be retrieved and correlated Factors that affect the speed of this process include the Dump Retrieval Mode the complexity of the dump the number of Include options checked the power of the mainframe the communication bandwidth and the speed of your PC To assist you in selecting the Dump Retrieval Mode most appropriate for a specific dump the text window describes the possibilities you will have once the dump has
133. ran Options Diagnostic tables under location counter 3 are used by The Visual Dump Analyzer to determine the structures within an absolute element These tables are created when an F option is included on the compiler s processor call i e FTN F Therefore in order for The Visual Dump Analyzer to function it is critical that the F option be used when compiling programs These diagnostic tables will not be part of the executable code and thus they will not increase an absolute s size in the HVTIP online file The Z option will force the ASCII Fortran compiler to optimize the generated MASM code for efficiency This may result in instructions generated by one FTN source line to be mixed with code generated by surrounding source lines Thus when viewing MASM code using Show MASM Code The Visual Dump Analyzer will display MASM instructions by individual source lines but be aware that some instructions may actually be generated by source lines that are nearby Extended Mode UCS options To inform the UCS compilers to generate the SDD Symbolic Debugging Dictionary diagnostic tables you must specify the keyword option DEBUG MONITOR on the compiler statement As with Basic Mode this will not influence the actual generated code but only ensure that SDD banks are created UCS programs have several levels of SDD information with DEBUG MONITOR being the highest and desired level for The Visual Dump Analyzer If you specify the OP
134. ranononn ADS DODI000 00L0777 D1 01 43 LLl E 28 Di CCC 0 140070 Lhe CM bio LIPMAN PSN ohhh 127651 DOPE DPSS OOO Poo npniseg4nnnn pppsggggunnu CeO 2214211665105 pnprpsgggnnun 124242330471 174157310420 opago FPSO 014 amp 1174 rld5D43 BITTER Warnan iiki TOOK O1G042 0141577 4 0 BALI FPL ii LE LOS Penn H IM The color codes indicate the following GREEN You can use Symbolic Debugging i e you can trust the value of all local variables since both the absolute and the source elements are valid You can use Symbolic Debugging because the absolute is valid but you cannot rely on any line number references since the source is not valid GRNT The validity of the absolute cannot be determined thus no check can be performed on the sources either Use Symbolic Debugging only if you know that the absolute and the source are valid RED The absolute is not valid Do not use Symbolic Debugging Trust GLOBAL areas such as Common Blocks DBAs and PDBs only To receive a description of these color codes simply click anywhere on the status bar in the Source Display window Page 13 Saving dumps to disc Once a dump has been read from the mainframe you can save it to a local disc s
135. re delete marked within the files being searched will also be examined so at times it may be advantageous to not remove i e pack outdated versions of these elements Also if you wish to not search the System search path for either absolutes or sources deselect the path at the left side of files listed within it The system search path can be optimized by selecting Tools Settings and then click on the Applications tab The USAS applications listed here will reflect all applications that are included in the system search paths for absolute elements and source code By deselecting an application in this list files within the system search path that are associated with it i e files having the same first three characters as the application will not be traversed when searching for both absolutes and source code settings eee Abort Report Filter Alert Message eMail Settings REMEDY Graph Settings General Settings Search Path Applications Reports Settings Select the applications you want to include files for in your system search path Files belonging to the selected applications will be included in the system search path for both sources and absolutes Cancel Apply By deselecting applications that are known to not relate to the aborts that are being analyzed considerable time will be saved whenever the table of contents for these files needs to be scanned Page 7 Reading dumps from the mainf
136. read references include all references that the source code makes to a variable with actually storing a value into it Continuing update references are those references that actually store a value into the variable Even when a variable has the same value before the store as it did after it will still cause an update TRAP hit For example update references refer to variables that appear on the left side of the equals sign within an assign statement and to variables used within a CALL statement s arguments when the called routine stores returns a value into the variable Realize that update references refer to all updates to a variable even if the store operation was not actually intended That is when a flaw exists within the logic resulting in an unintended update to a variable that is the target of a TRAP the TRAP contingency will still be triggered This could occur for example when a 100 word table is defined and the program accidentally stores a value into the table using an index less than 1 or greater than 100 In this case FTN will produce a flawed address calculation and store the value outside of the address range occupied by the table As a second example an unintended update could occur when a variable within a DBA is updated but the DBA is not actually allocated Page 38 These unintended updates are normally very difficult to remedy but The Visual Dump Analyzer makes them much easier to find by allowing you
137. red that The Visual Dump Analyzer is running in Monitor Mode to raise Alert Messages via eMail or SMS Page 67 Raising Alert Messages as REMEDY Tickets To raise Alert Messages via the REMEDY Action Request System a REMEDY configuration must exist in the REMEDY section of the general configuration element USAS SED FILE SED INI on the default mainframe server Because the REMEDY configuration is shared among all users you cannot change the actual REMEDY configuration using this dialog This dialog only displays the present REMEDY configuration To configure the REMEDY information shown below you must contact the super user for The Visual Dump Analyzer and have him change the REMEDY configuration in the general configuration element on the default mainframe server Settings General Settings Search Path Applications Reports Settings Abort Report Filter Alert Message eMail Settings REMEDY Graph Settings The REMEDY Action Request System configuration is shown below As the REMEDY configuration is shared between all users it cannot be changed by the individual clients The REMEDY configuration is loaded from TDEV E from element USAS SED FILE SED INI This file is shared between all systems monitored by VDA and should thus only be changed by the VDA super user The mininum time interval between identical REMEDY tickets is set to 3 hours and 20 minutes This means that if more identical al
138. rm text and symbolic data from the dump resulting in a very helpful natural language description Views be automatically generated from procs or be manually developed for specialized use When Views are automatically created based on a F or F proc they will show the data as defined by the proc itself All documentation text will also be preserved with the actual define statement only being replaced with the value of the field thus generating views that look very similar to the proc themselves This not only makes the procs easy to understand but ensures the data being read uses the same defines as the program which is essential when a dump is caused by flawed defines rather than corrupt data See View Construction Page 25 Rescheduling the Input Message The Visual Dump Analyzer allows you to again reschedule the input message from a dump There are many benefits with rescheduling input messages all of them assisting you in finding and fixing the cause of an abort The reasons for doing this include Setting and running Traces Causing the dump to be taken at a more informative location Testing and verifying that your fix has worked Causing the same abort on a different system Many of the input messages used in USAS today are Edifact messages and are thus not easily reproduced manually from an HVTIP screen The Visual Dump Analyzer lets you re enter these large messages without requiring them to be resent by anothe
139. rt Birch LKB Lars kruse B ggild DPR Unisys Operator PAS Pas Guard Per nders Wiklund PSE Peter S rensen Down ile This list is in call priority order Use Up Down to sort the list Cancel Note that program names in the Program Book can contain an asterisk to indicate a wild card When the Program Book is searched during Alert Message Analysis only the entry that best matches the program name will be used when multiple entries match the aborting program The best match is defined to be the entry with the least number of asterisk characters To ensure that your updates to the Program Book give the expected results you can perform a test by searching the Program Book To do this right click the Program Book window and select Test Program Test search the Program Book Use this utility to test search the Program Book to ensure the tested program is found on the correct entry The search will find the entry that best matches the specified program Best match is the entry with the smallest number of characters Search for program SED By clicking Test the entry that best matches in the Program Book will be colored GREEN Page 73 Monitoring Freespace Files The Visual Dump Analyzer can provide you with a complete overview of each freespace file on the system It accomplishes this by combining the FCSS File Control Superstructure internal control informatio
140. s This information is intended for Alert Messages that are received by computer center operators rather than programmers Reason This section informs of what Alert Message Warning Level was exceeded and by how much Phone List The Phone List displays the responsible application programmers along with their phone numbers The responsible programmers are found in the Program Book if an entry for the aborting program exists or if none exists the responsibility for the aborting program is assumed to be shared among all programmers working in the aborting application Analysis This section gives a natural language text describing the abort in as much detail as possible The text will depend on the actual aborts and their origin If the VDA Knowledge Database contains information for this abort type it is included in the analysis Abort Details The Abort Details is a list Action of the actual aborts The TDA application is aborting please call the VDA guard now causing this alert They are shown along with their WDA Application Alert 1 from TDEV E Wort Raised SEDANA Phone Lise ib call priority oeder Lars Kruse Baggild 25028 Mabile no Homee 3294 3194 most essential diagnostic information To ensure Pauca that the analysis text does Too many 5 identical have been detected within min re s vise period not grow too large the list Analysis is limited to a maximum of XEDAHA
141. s of the person they should contact The Visual Dump Analyzer accesses the SPO via the VDA SPO Agent VdaSpo exe This is a Windows agent that provides the interface between all instances of The Visual Dump Analyzer that wish to raise Alert Messages or other messages on the SPO and the SPO software provided by Unisys The VDA SPO Agent resides on the SPO Windows server and accepts incoming DCOM calls from the Visual Dump Analyzer GUIs located on various Workstations and servers It then pushes these messages to the SPO using the SPO Windows API Page 68 The VDA SPO Agent will collect and keep a local copy of all the messages raised on the SPO This enables the VDA SPO Agent to provide a history of all messages raised on the SPO no matter what instance of The Visual Dump Analyzer raised the individual messages This history of messages can be fed back to any instance of The Visual Dump Analyzer and displayed in report form allowing them to re open and view all historical messages raised on the SPO See Show SPO Alerts The Visual Dump Analyzer must be running in Monitor Mode in order to raise Alert Messages on the SPO Running VDA in backup mode When The Visual Dump Analyzer is configured to raise Alert Messages on the SPO you can configure a second instance of The Visual Dump Analyzer as a backup server and have it raise the Alert Messages on the SPO if for some reason the primary server should fail The backup server can be located an
142. s reschedule the input message with this setting and examine the trace file The trace file will now contain a Breakpoint Hit for line 334 along with a SNAP line giving the value of ADR every time it was executed See Rescheduling the Input Message Page 45 View Construction A view is an element in a program file that contains freeform text and expressions related to the dump and absolute When a view is displayed the expressions are resolved and their values are replaced within the freeform text of the view In order for the view process to recognize an expression it is always enclosed within square brackets i e expression Following is an example of a simple view This is my first view It contains information from both the IBBLOC and the CABLOC The function code of the aborting trx is IBFCCD 1 and it was processed on PID CABCB 2 When the view is displayed the values of IBFCCD 1 and CABCB 2 will replace IBFCCD 1 and CABCB 2 in the text and the view will looks like this This is my first view It contains information from both the IBBLOC and the CABLOC The function code of the aborted trx is LN and it was processed on PID 3821 This is a very basic view but you can make them as complex and informative as you wish The expression field can have the following formats expression Simple expression The display format is dependent upon the value Ascii fieldata octal or decimal is chosen based upon
143. selected common block including its location x Dba Pd View v CmnBlock You can use this toolbar to change the contents of the active Data Display window by selecting a different DBA PDB view or common block from the drop down lists If multiple Data Display windows are displayed the selected entry within the drop down list indicates the one that is currently or most recently active Moreover if you wish to change the contents of a Data Display window just click on it to make it active and then select a different entry within these drop down lists The Visual Damp Analyzer 3 1 6 PHR Poe View Window Tock Cael tan LL PXCATO Rekcatsbie PCR Dba P view his dump was caused by a D trx m pid 3571 resulting in an XTCA ort in at line 966 At this line the call to XTCC arted he diagnostic info given is IBSERR 591 IBDIAG and 0 PLASTIC EVALEMTI ON ST ABORT REQUESTED ABORT The General Info window This window provides you with a natural language explanation of what has caused the dump The explanation provides all relevant XTCA and CONTINGENCY including HVTIP error codes along with a complete description of these codes when applicable This window also contains I O error information by gathering all the FCSS diagnostics translating it then to natural language and including
144. sen 13 EMAMING DUMPS eis ccsccctacecccisscesccccascceickeccssseuaccestaveseccecdodseescesecausccestoncesseeacecesvesoncessecesseeatesssodebocsecocdesesesscesedubecessendovoseeces 13 CUSTOMIZING COLORS AND FONTS ssscccsssssssssssccesssccscssscccscssscccssnscccessceccessscascessecsscssseccscssaccsssnascccsssacsessscacceses 14 CUSTOMIZING SETTINGS E sonsccsssssbecedsendcs EPOSSE 15 VIEWING THE DUMP Le E SHOPS 15 RESIZING THE WINDOWS caetero ceste 15 SETTING THE ACTIVE WINDOW A 16 SPLITTING THE WINDOWS sunnere ker CHANGING WINDOW TYPES THE SOURCE SELECTION TOOLBAR sicsciicccscccssssscsscecccssosaccascsscssesscssctcsscceseesseosseeessosteseccesesssoseessesseessevesccsessoassvesesses 16 THE DATA SELECTION TOOLBALR csscssssssssssnscsscccsssssscecccccsssssssnccecccsscscscceccccscsessccececccscsscececeecesseessoscececcescsscescess 17 THE GENERAL INFO WINDOW eo es ees ran e no npo FPES Fa SE SES P Go oseveesesbeceeceosousesencescossesabsccesuossosessedsoconeecoecsoseesesonsesvesocesse 17 THE SOURCE CODE WINDOW 18 SYMBOLIC DEBUGGING 18 POP UP MENU FUNCTIONS m 18 THE VARIABLE WINDOW
145. ss Go to FCSS I O error and Go to X11 return address all provide quick ways of going directly to the source code line where an important event occurred related to this dump Again you will be able to view this location symbolically without having to do any address manipulation Go to Address and Go to Line Number are quick ways for you to view source code at a particular location Return to Caller and Go to Forward Call allow you to move one step backwards or forwards in the Program Call Stack WalkBack from the present location enabling you to return to the calling routine or move forward to the next forward call See The Program Call Stack WalkBack Show MASM code lets you view the actual MASM code that is generated by the compiler for the source code you are viewing By selecting this option the window will expand into having each source line displayed with the Page 19 MASM code it produces listed just below When using this function be aware that all sources lines do not produce MASM instructions Further depending upon the compiler options used the MASM instructions may be shifted up down and overlap more sources lines in order to optimize performance Obtain more MASM code should be i Anixi selected when the MASM code that is initially iB x shown does not cover all the source lines you are interested in To save time only the MASM code around the source code you are curre
146. sult of the TST settings and verify that the absolute element found was actually the correct one You can also set additional TST flags manually on the service or PID from a normal HVTIP screen The Visual Dump Analyzer will then add its TST flags to those that are already set For example if you wish to reschedule an alternate library bank you can set the TST ALTs on the PID or service as normal before rescheduling the input message See Setting Breakpoint Traps and Snapping data on Breakpoint Traps Setting Visual Advanced Snaps Before rescheduling a transaction you can press the Advanced button to request The Visual Dump Analyzer to add Visual Advanced Snaps TST trace flags The TST settings selected here will automatically be applied to the PID you have selected prior to rescheduling the input message x Snap PFEDIT lines Snap Free Chain information when the Free Chain gets destroyed Move the AP DBA down to reduce memory shifting Cancel Drop the AP DBA to preserve memory layout In this dialog you can also request PFEDIT output lines to be routed to the trace file This provides a useful way of seeing where you are in the processing when reading the trace file Note that for practical reasons the width of each PFEDIT line is limited to 71 characters Page 30 You can also request Visual Advanced Snaps to monitor the AWA Free Chain and report when it detects the chain to be destroyed Once
147. svevebeveua saved svevanesse4sodevseevsbevsavaoessvebs 56 SHOWING STATISTICAL REPORT ude 56 SHOWING SPO ALERTS atraer eee 58 CUSTOMIZING THE ABORT REPORT LAYOUT cssscssssssssscssccccccsssssececcccsescsscecececccssssssscecccescesssececcccssesesssscees 59 AUTO REFRESHING ABORT REPORTS esevevsvvvsessensnnnnesssessnsnnnnvnsesensnnnnnnennnnnsennnnnnnnsenensnnnnnnennnnesnnnnnnennnnnnsennnnnnnnensesene 60 RAISING ALERTS MESSAGES 0 acccsecssssesscosessncsessssusesesssesevestessseseneiees secssssdesceesshosteuscasesusonsesenscdesssuccssstondceseteccsssacecstennsess 60 ALERT MESSAGE ANALYSIS sccscscaiscssssctcckocsscceuctvsseceseuscsentsosoesvace cosswssvescenccnaceasssesdsesesossceuceseousncdecsssccacdouctsesedveseoscodesssnss 60 SUPPRESSING ALERT MESSAGES cccccscseeeeseseseseseseeeseveceeeseseseseceneseveseseseneseseseseseseseseserececeseresereseeeseeeseeeseteseseseeeceeeseseserens 62 CONFIGURING ALERT MESSAGE WARNING LEVEL cccsssscssssssccsssssccsssccccesssccscsssecesssceccessecssesssscsscssscesesses 63 WARNING ON ALL ABORTS tsiscccssscsccsssssnevenescnscissscsissessscsecsssscssseseecsecestscnesesescsecesss scenes 63 WARNING ON TOO MANY IDENTICAL ABORTS 63 WARNING ON MANY DIFFERENT
148. t and provides easy access for viewing the contents of each area Memory Loen FE 118 H FALL ae LL Fie REC SPELAR ridakirs BLG E RAT ee entra m Tere LDH OLS CCETT j FEELEN RCTS Page 22 The Program Call Stack WalkBack The WalkBack is found in the Pop up menu for the Drawing window When selected the drawing will change from the Memory Layout to the WalkBack picture The information provided by the WalkBack picture reveals the path the processing took in getting to the abort location This picture contains the actual calling sequence Program Call Stack WalkBack of the programs that have program stack areas within the dump That is the location within the source code is shown where each program calls forward to an internal subroutine a mapped in relocatable an ACB routine or another HVTIP program The Withee nak imifarmmals n on the path Boker the aborting Exation FICETI Each of these calls is drawn as a separate box grouped into absolutes Internal subroutines are drawn directly appended to the absolute whereas external mapped in subroutines are drawn under the calling absolute PXQUEZ OG Each box will contain a short written text stating the location of where the forward call was made For Fortran programs the text is the source line
149. t Breakpoint Trap which will open the below dialog where you can set and customize the TRAP Set Breakpoint Trap r Trap Limits Limit Trap to absolute SEDANA Limit Trap to relocatable SEDANA Limit Trap to internal subroutine SCONT m Trap on Hits Trap on ALL references to 04 word 19 Trap on UPDATE references to 04 DBA word 19 m Trap Abort Info Abort when 04 DBA word 19 has been referenced specific number of times Abort after this many references Abort when 04 DBA word 19 is set to a specific value Octal abort value 000000361101 m Snap Info Snap on Breakpoint Hits only Snap number of words Cancel Setting a TRAP on a variable naturally causes the TRAP to be active only when the variable is in scope When setting TRAPS for DBAs or PDBs the scope is from when the DBA or PDB is first allocated until it is released by the XBCF routine Unlike the scope of local variables that only span one program DBA or PDB TRAPS will often span many programs and will thus cause TRAP hits outside the program you are interested in To restrict the duration that a TRAP is active you can use the Trap Limits area Here you can define the boundaries of a trap by specifying an absolute program specifying a relocatable or even specifying an internal FTN subroutine If you deselect these scope limits the TRAP will be active whenever the DBA o
150. t Message UNB 4IATA 1 1P SK 080123 1340 327C 3E UNH amp 1 CLTREQ 36 2 14 327 C 3E 100130015 114817 CLT A U NT 3 1UNZ 1 327C3E Find Input Clear Reset IL ox Cancel In this dialog you can either edit the input message or you can locate the input message in case it has not been located correctly The Visual Dump Analyzer assumes that the input message is located in the Input MPA however that may not be the case for services Thus you can use Find Input to manually load the input message form any valid d bank address within the dump Page 29 Scheduling Edifact Messages directly using EDIT When working with an Edifact message you may not wish to have The Visual Dump Analyzer reschedule the input message as a true HTH message thus avoiding the trouble of selecting a valid PID from the Pseudo PID pool By checking the Schedule the message for the edifact handler box you can request The Visual Dump Analyzer to remove the IATA HTH header and precede the input message with the EDIT transaction code This will change the input message from a HTH message to a normal VDU transaction that is able to execute on any PID selected by you Once you press Schedule Msg Now the transaction will be scheduled and the Edifact message will be routed directly to the Edifact Handler due to the EDIT transaction code Setting TST Traces When you press the Schedule Msg Now button Th
151. t Messages as alarms on the SPO While doing this it keeps a history of all messages that were raised while also allowing them to be fed back to the Visual Dump Analyzer GUI and be shown in this SPO Alert report Lompictic from Pee Med ALL OL E BEAL MODE The and iaaii 5 4 The TET appia call the TET guard resa ALAS CE OO S THYE Prager Jacnbeen run PROCHES Program ro Lone DOM DOS LT BPEL LT PRODE Too unary dent aborts hase been detected The PAS apolicaoon s aborting pissas cai the PES pusnd Mor RELEASE CHUAN DDS 3 54 40 LE IDEE lr Ka J rgensen Panis nn a CAT SDDO TNT Faqestedby Precen lacotuen nier Lore PROPEL LT PROD Toon E dental aborts hawt been detected The BES aborting obese call rfe RES puand ew MORAL DEAN 2008 LT FADDE Tooma 4 centical aborbi heen been detected The PAS m aborting paasa cali P3 guard PROD E Too mene EL aeni shorts have been detected Thes aplication sborting plass cali tfe PAS guand nee Fi RELEASE MANG SS LI TORE Bed by Seren M sen Prairie FUIT habita 200 Z 0 77 LE PRODSC Toney 14 sbort base been deateris The PCI apple stier or aborbng plassa the PCI ard mrs
152. t are produced Instead they will be left active and will be removed by Sys 11r2 s normal clean up process which removes all TPRs that have been inactive for an extended period The construction of dummy TPRs is another reason why The Visual Dump Analyzer does not allow reschedules to be performed on production systems HTH reply message are simpler as they do not require being in a session Instead they will always execute on the PID number in the HTH header TPR field Also because The Visual Dump Analyzer can manipulate the TPR to force the rescheduled message to execute on any PID number you can freely select its value Rescheduling Services Because traces on services are set on the actual service and not on the PID it executes upon the problem of determining the PID that is used for execution does not exist when rescheduling services Be aware that when you have requested The Visual Dump Analyzer to set traces on the service as part of the reschedule logic traces will be set for everyone using the service and not only for your execution Thus you should be careful to remove the traces shortly thereafter Editing or Finding the Input Message Before rescheduling the input message you can choose to edit it in order to gain additional information This may be helpful for example if the error is due to a flawed input message To edit the input message press the Edit button and the below dialog will be displayed Edit Inpu
153. t being attached to a new e mail that is prepared to be sent This quick email option however requires that you have a Microsoft compliant email client installed Page 71 The VDA Address Book The Visual Dump Analyzer has an address book that identifies both personal and functional users within VDA Being used everywhere VDA needs references to users The VDA Address Book is stored on the host system and is shared between all VDA users To view the Address Book select Tools Address Book and the Address Book will be displayed Once the Address Book is shown it is can also be updated To update the Address Book simply double click a person in the Address Book Further by right clicking in the Address Book window you can select the Add New Person Update Person or Delete Person options Selecting a person in the Address Book will open the dialog below Update person Initials LKB First name flasKuse 1 Last name B ggild Applications SYS Work Phone 25028 Mobile Phone Private Phone 45 3294 3194 Currently not available for calls Once the Address Book is updated the changes are made both locally as well as distributed to all the Unisys host systems Because the Address Book is shared between all users it is important that the information within it is kept accurate It is recommended that you add yourself to the Address Book so VDA is able to identify you
154. tation in the file at all Note that fragmented records shown for example for record type 8 may be allocatable as they may be used for record allocation of a smaller record type if the D value will permit such an allocation A large fragmentation for a given record type is naturally only a problem if this record type is actually used in the file Use graphs 4 and 7 to get an idea of how heavily a given record type is used To view the actual count for a record type click the individual bars Page 86 Detailed File Analysis Graph 7 The seventh graph shows the Freespace handlers allocation statistics for each record type It displays the growth pattern along with the present record allocation and record releases within three times two 3x2 bars for each record type 430 30FILE File Growth Measured since 08 11 30 08 01 00 Graph 7 The first two bars show the number of record allocations since the statistics were last reset The first of the two bars when the graph is toggled to show percentages displays the number of allocations in percentage of all the free records of this type The second bar shows the number of allocations in percentage of the total amount of records of this type in the entire file These two bars are always colored RED as they depict record allocations The next two bars will show the number of record releases since the statistics were last reset These two bars are always colored GREEN as th
155. ters long the TRAP will only be set for the first word but you can request any or all of the 20 words to be snapped Similarly you can set a TRAP on the first word in a table while requesting the snap to show any portion or all of the table To remove a TRAP simply right click the RED variable line select Clear Breakpoint Trap Snap and the TRAP will be removed Alternatively you may select Tools Clear Breakpoint Trap in the main menu to clear it Because only one TRAP can be set at a time setting a new TRAP will automatically cause an old TRAP to be cleared Page 40 Setting TRAPS on DBAs or PDBs Setting a TRAP for a DBA or a PDB works similar to setting a TRAP for a variable except that you cannot set a TRAP using the symbolic names of defines This is because the FTN compiler does not register defines to have specific addresses that are predetermined before execution Instead the FTN compiler creates the specific MASM instructions needed to locate the defines each time they are used This prevents The Visual Dump Analyzer from calculating the exact address that relates to a given define beforehand Thus TRAPS for DBAs or PDBs cannot be set by name symbolically rather they have to be set on a specific word within the PDB or DBA To set a TRAP for a DBA or a PDB you must right click the actual word in the DBA or PDB that you want the TRAP to be set on This will open a Pop up menu allowing you to select Se
156. that immediately informs you of when a file within the monitored applications starts becoming full Whenever the refresh logic retrieves the latest file status the report is analyzed and checked to verify if the Warning Levels have been exceeded If the Alert option in the Pop up menu is set and the analysis of the report reveals that one or more of the warning levels have been exceeded an Alert Message is raised An Alert Message is raised by animating a small warning window in the bottom right corner of your screen This window will be shown as the top most window so it will always stay visible It will however not take the input focus so you can 30FILE is continue working without interruption running full on PROD C The Alert Message will be raised even if The Visual Dump Analyzer application is not the active application at the time If The Visual Dump Analyzer application is in the background or is minimized the Alert Message will still be raised Once the Alert Message is raised you can use it to quickly activate The Visual Dump Analyzer application by clicking the warning text itself The Visual Dump Analyzer will be brought to the foreground and maximized with the File Report that has raised the Alert Message also being maximized to give you a helpful overview If the white blank space in the warning window is clicked instead of the text itself the warning window will be closed and The Visual Dump Analyzer will not
157. the AWA Free Chain is destroyed Visual Advanced Snaps will place a line informing of this fact in the trace file This will only be reported once in order to avoid filling the trace file with this identical warning statement Controlling the AP DBA The AP DBA is used by Usas Sys 11 2 to hold the trace lines before they are written to the trace file When traces are ON Usas Sys 11 2 allocates the AP DBA as the first DBA in the AWA It is important to realize that this causes the shifting of memory so that all other DBAs allocated in the AWA will be at different address locations than when traces are OFF See Memory Allocation and Tracing in User Guide for VISUAL TRACE And VISUAL PERFORMANCE ANALYSIS Normally this is not a problem but some complex problems tend to go away when traces are ON and re appear when traces are OFF Naturally this makes finding this type of problem very difficult This troubling behavior is often due to memory allocation and is therefore affected by the fact that the AP DBA is causing all other DBAs to be shifted down in the AWA By setting Move the AP DBA down to reduce memory shifting Visual Advanced Snaps will force the AP DBA to be located at the very bottom of the AWA rather than at the top The memory locations of all other DBAs are thereby preserved and hopefully the problem will then be traceable and reproducible when traces are ON Note that the AP DBA is still present in the AWA when this option is set and
158. the column widths relative to the data within them just click on the Resize Column icon on the main menu To restore the default setting select Tools Column Layout Reset Column Layout Besides these settings you can choose to automatically apply a preset Report Filter when the Abort Report is initially opened This is done by selecting Tools Settings Report Settings and then checking the tic mark for Apply Report Filter In the dialog you can also ensure that the Abort Report is set to be continuously refreshed when it is first opened by setting the tic mark for Raise Alert Messages The settings in this dialog control the general behavior of the Abort Reports along with their initial settings once they are first opened For an individual Abort Report you can also chance these settings via its Pop up menu In the Report Settings dialog you can customize the colors used to identify aborts in Abort Report that have caused Alert Message to be raised By default the aborts that caused the last Alert Message will be colored RED whereas the color used to identify previous Alert Messages are colored ORANGE setts n pn NE Abort Report Filter Alert Message eMail Settings REMEDY Graph Settings General Settings Search Path Applications Reports Settings Report Settings Alert Message Layout IV Color code aborts causing Alerts Messages Animation Raise Alert Messages Windows Header
159. tine and select Trap calls returns to Subroutine name gt This will cause the TRAP to be set on all calls to and returns from the subroutine while highlighting the SUBROUTINE statement in RED indicating the TRAP is active 0319 0320 ed 0324 DMPDDH 1 0325 LINE DOTS 0326 LINE 28 49 CONTINGENCY ANALYSIS 0327 CALL PRGSAV SAVE 0328 0 EXPLAIN REQUESTE SPCERR CODE 0329 IF SPCERR NE O 0R DMPTBL CNTPKT HE 0 THEN 0330 C DEBUG CODE FORCE ABORTS 0331 IF SPCERR EQ 123456 THEN 0332 SRCLIF 1 SRCLIT FORCE CONTINGENCY 5 ZERO DIV 0333 ELSE SPCERR EQ 123457 THEN 0334 LINE 4 SPCERR FORCE SUBSTRING ERROR 0335 ELSE SPCERR EQ 1253455 THEN 0336 CALL 25 100000 FORCE DBA ERROR 0337 CDML IF FALSE THEN TEST CARGO DMS MACROS 0338 CBUG CALL PRTADP MYTEST SPCERR 1 TEST CARGO DEBUG MACROS 0339 CDML ENDIF TEST CARGO DMS NACROS 0340 ELSE SPCERR EQ 123459 THEN O341 IDX H1 CBAREA 2 ADDR CBAREA 1 1 1ST FREE ENTRY 0342 CBAREA IDX 0 DESTROY FREE CHAIN 0343 CBAREA IDX 1 0 DESTROY FREE CHAIN 0344 CBAREA IDX 2 0 DESTROY FREE CHAIN 0345 CALL 25 100 CAUSE THE ABORT It is default for internal subroutine TRAPS to force an abort on the first exit from the routine In same wa
160. to simplify the complex task of dump analysis by using an intuitive design that does not require memorization of commands or tricks that are only gained through experience The Visual Dump Analyzer uses many of the standard MS Windows functions such as scrolling resizing windows copy and paste drag and drop printing and context menus Therefore this familiar environment will allow you to effectively use the product from the very outset Symbolic debugging The Visual Dump Analyzer will retrieve all information necessary to thoroughly analyze a dump the related program source code program absolutes executables file and packet record layouts and the dump itself The program absolute will be used as the glue between the source code and the dump thus enabling you to reference variables and source line numbers rather than their absolute addresses i e symbolic debugging This powerful feature eliminates your need to know where local variables instructions and global data are located within the dump thus freeing yourself to concentrate on the actual task at hand solving the dump Page 4 Configuration The first time you use The Visual Dump Analyzer it will guide you through a simple dialog that will download all the necessary configuration information from one of the mainframes Even though you plan to use The Visual Dump Analyzer towards more mainframes you only have to configure it once as the downloaded configuration cont
161. to set TRAPS on the variable that gets destroyed Setting TRAPS on variables To set a TRAP on a variable right click the variable name in the Variable Window to open the Pop up menu and select Set Breakpoint Trap In this example the variable named ADR was clicked on As a result the below dialog box is opened allowing you to define the TRAP settings Set Breakpoint Trap m Trap on Hits Trap on ALL references to ADR Trap on UPDATE references to ADR m Trap Abort Info Abort when ADR has been referenced a specific number of times Abort after this many references 1 Abort when ADR is set to a specific value Octal abort value 040040040040 m Snap Info Snap on Breakpoint Hits only Cancel Once this dialog is displayed you must first decide whether you want the TRAP to hit on ALL references i e read and update references or only on UPDATE references Next you need to consider whether The Visual Dump Analyzer should or should not abort the transaction at a specific TRAP hit If you choose to not abort the transaction at a given TRAP hit all the hits will be written to the trace file resulting in an informative trace of the scheduled transaction If you choose for the transaction to be aborted you must select one of two options in the Trap Abort Info section This includes either requesting the transaction to be aborted when first the TRAP variable has
162. ts allowed in the Abort Report by the filter will be checked and counted by the Alert Message Analysis and compared with the warning levels Even if an abort is allowed in the Abort Report by the filter it will not be checked or counted by the Alert Message Analysis and compared against these warning levels if it is marked as not being able to raise Alert Messages in the VDA Knowledge Database See Showing Alert Restrictions earlier in this document Page 65 Running in Monitoring Mode The Visual Dump Analyzer can be used to monitor various systems with abnormal conditions generating Alert Messages to the interested parties These Alert Messages can be raised in four different ways As a small Pop up window on your local Workstations IWS As eMail or an SMS to a predefined mailbox or mobile phone To the REMEDY Action Request System making it a REMEDY Ticket On the Unisys Operator SPO Single Point of Operation When The Visual Dump Analyzer is running in Monitor Mode it will prepare itself for continuous execution This includes ensuring that the raw data gathered from the mainframe to produce Abort Reports are not kept in memory once they are used thereby ensuring that the IWS does not drain itself of memory As a consequence of this you cannot request The Visual Dump Analyzer to save the Abort Report to a local disc while it is running in Monitor Mode as it will have already freed the raw data for the report To
163. ty codes will all request immediate action If the Warning Level is exceeded outside of normal working hours however the severity code will determine when the action will be taken HIGH Request action now around the clock MINOR Postpone action outside working hours until next morning LOW Postpone action outside working hours until next working day Alarm Method 1 Early Warning By setting the Warning Level to a level that is considered not too critical and the severity code for the Warning Level to LOW an alarm of severity LOW will be raised early although it will not request action outside normal working hours In this way the alarm functions like an early warning Once an alarm has been raised a new alarm for the same file will not be raised again during the next 24 hours unless the severity level becomes higher By setting the lt 75 Warning Level to MINOR a new alarm will then be raised of severity MINOR if the available space drops to less than 75 of the Minimum Available Warning Level Similarly setting the lt 50 Warning Level to HIGH will ensure that a new alarm of severity HIGH is raised when the available records drops to less the 50 As a result setting the Warning Level to 80 with severity LOW the lt 75 to MINOR and lt 50 to HIGH will result in the following An early warning alarm Severity LOW will be raised once the file has less than 20 available records a new alarm Severity MINOR will be
164. u want to cause an Alert Message To customize your warning levels open the below dialog by selecting Tools Settings Alert Message Then adjust the individual levels and check the patterns you want to be active sett x General Settings Search Path Applications Reports Settings Abort Report Filter Alert Message eMailSettings REMEDY GraphSettings Every time an Abort Report is refreshed The Visual Dump Analyzer can check the new aborts and alert you if it detects 4 pattern in the aborts or if the number of aborts grows too large Use this dialog to configure the warning levels specifying when and where you want the Alert Message to be raised To configure warning levels specific to each host system or warning levels that vary according to the time of day and the day of week use the Advanced button Where to show the Alert Message IV Show Alert Message on my IWS Aborts reoccurring with a fixed time interval Send Alert Message as eMail SMS More than 3 identical aborts within 1 min Send Alert Message to REMEDY More than 10 different aborts within 1 min Show Alert Message on the SPO Using locally installed SPO Agent Advanced Alert Message warning levels Actas backup SPO Alert server Advanced Reset Cancel Apply The four Alert Message Warning Levels defined by this dialog are the default values used for all systems that do not have an advanced setting Th
165. uxedo installations on your PC for VDA to use TM2200 Getting started Auto Config In this dialog you will first need to decide which method of communication TM2200 or TMVDA you will use for accessing the Unisys mainframes With either method you will only need to enter the IP address and the port number of the main development mainframe along with the listener port number of TM2200 or TMVDA Auto Configuration The Auto Configuration facility will allow you to obtain the latest configuration for ALL the servers that have The Visual Dump Analyzer installed This will NOT change your personal settings but only update information related to communication You must Auto Configure every time the Server Configuration Level changes You will be informed automatically every time this happens To gain access for the first time you must enter the IP address of your main development server and select a method of access If the IP address specified cannot be resolved it will cause the connection to HANG for about minute so be patient Communication Information Access mainframe via TM2200 cce Configure Now to Access mainframe IP address of development server fi 59 195 79 134 i i Port number 2000 Cancel Page 5 If you do not know the IP address of the main development server just enter its name in the IP box as The Visual Dump Analyz
166. what appears to be the best choice F expression Format controlled expression F is the display format and must take one of the following values A Ascii X Ascii overlays octal F Fieldata O Octal D Decimal F ADDRESS expression ADDRESS function This function will retrieve the value of the address given by the result of the expression F BITS expr1 expr2 expr3 BITS function This function will return the value of the specified bits It is identical to the Fortran BITS function F REG X3 REG function This function will return the value of the specified AXR register and Extended Mode B registers F DBANAME expression DBANAME function This function will return the ascii name of the requested dba number provided by the expression expression PDBNAME function This function will return the ascii name of the requested pdb number provided by the expression F PRGNAME expression PRGNAME function This function will return the FD name of the program with the provided lib bank in the expression The expression itself must be in the format described in the Expression Window section Special system related expressions can also be used within a view You can see these by selecting the Show View values in the Pop up menu of the Expression window Page 46 Auto generation of views Views can be auto generated from F F procs If a F proc is
167. while executing the program that you have just fixed Page 26 Rescheduling normal terminal transactions To reschedule an input message select Tools Reschedule Msg from the main menu or alternatively right click in the General Information Window to open the Pop up menu and select Reschedule Msg to display the dialog below Reschedule Input Message m Original input message information The original input message was a normal transaction LN so you are free to select any valid signed in pid for the reschedule YDA will force the reschedule to use the pid you have selected thus you can put TST traces the selected pid prior to the reschedule if you want to LNC S K375 21FEB ARNBKK E dit r Reschedule information Schedule on system TDEVE Schedule on pid 30523 Schedule on valtab MANPRO Schedule as service Schedule message for the edifact handler Show 181 flags Tum Traces OFF Advanced Close When rescheduling a normal VDU transaction you can choose to reschedule the input message on another PID or another VALTAB It is your responsibility to ensure that the selected PID is signed in and is allowed to run the transaction Generally a VALTAB should only be changed if you have added extensive traces to the transaction so that a reschedule using the normal VALTAB would cause it to timeout before the abort To
168. will thus still affect the stack locations for HVTIP programs If forcing the AP DBA to the bottom of the AWA does not make the problem traceable the only other solution is to completely drop the AP DBA If you select Drop the AP DBA to preserve memory layout Visual Advanced Snaps will allow Visual Breakpoint Traps to be effective while preventing the AP DBA from being allocated Further you must ensure that any TST trace flag that will place information in the trace file is turned OFF as this will also allocate the AP DBA When the AP DBA is not allocated at all the memory usage will be identical as to when traces are OFF and thus the problem will be reproducible Because the AP DBA is dropped no trace file information will be captured by Usas Sys 11r2 resulting in an empty trace file Instead you will have to rely on Visual Breakpoint Traps to detect where and when the data gets destroyed See Forcing Aborts when a memory location gets destroyed Removing TST Traces again The Visual Dump Analyzer will automatically set all the needed TST flags on a PID or service when the Reschedule Msg Now button is pressed but it will not automatically remove them after the message is rescheduled This is because removing the TST flags would actually prevent you from capturing any trace data collected during the reschedule So to remove all TST flags that are set by The Visual Dump Analyzer and you press the Turn Traces OFF Now and a
169. y as line number or MASM instruction TRAPS you can alter this setting by right clicking the RED line and selecting Set Abort Count Page 35 Note that the default setting for the abort count is 2 rather than 1 This is because FTN technically uses the SUBRUOTINE statement to generate both the entry and return code Set Abort Count x Force an abort when this line has executed specific number of times Abort after this many executions 2 Cancel Because of this The Visual Dump Analyzer controls the execution hit count by tallying the number of times either the entry code or the return code from the SUBROUTINE statement is executed This results in every CALL to the subroutine to make 2 hits 1 on entry and 1 on exit As a natural result of this all the odd hits will be entry hits whereas all the even hits will be exit hits Moreover the default value of 2 will force an abort on the first return from the subroutine Finally by using this method you can calculate the hit count that is needed to force an abort on the precise entry or exit of the subroutine that you want As with line number TRAPS you can also use this dialog to turn the forcing of new aborts completely OFF by deselecting the Force an abort when This will still leave the TRAP active and cause any snaps to be written to the trace file on every entry and exit from the routine Page 36 Setting TRAPS on HVTIP calls When an
170. ywhere including a disaster recovery center so it is ready to automatically take over in case of problems In order to initiate the disaster recovery configuration where two instances of The Visual Dump Analyzer are monitoring the same systems and raising Alerts Messages on the SPO both instances of The Visual Dump Analyzer must be running on predefined servers The two servers are configured in the SPO section of the general configuration element USAS SED FILE SED INI on the default mainframe server The SPO section defines two VDA SPO servers named VdaSpoServer and VdaSpoServer2 which inform The Visual Dump Analyzer of the primary and backup servers respectively Further the backup instance of The Visual Dump Analyzer running on the server specified by VdaSpoServer2 must have Act as backup SPO Alert server set This option is found in the Alert Message pane in the Settings dialog opened by Tools Settings from the main menu Once the two servers are configured and placed in Monitor Mode they will both monitor the USAS Systems from which Abort Reports have been opened Each time either server accesses a monitored system it will place a time stamp in the VDA common bank SED Q on that system to indicate that the operation was successful With a unique time stamp being written by the primary and backup servers they can each verify that the other server is running and has completed its monitoring processes by checki
171. zer so public views should be copied onto all of these systems If you wish to have a view for your own use you can copy it into your personal file and then read the private view by clicking the View button on the Data selection toolbar In the dialog box provided just enter its name and path and it will be included in the View drop down menu If your view contains symbols from a new F or F proc you will need to create a Resolve Program in order to teach The Visual Dump Analyzer how to resolve your new expression names See Hesolve Programs section Page 47 The VDA Knowledge Database The Visual Dump Knowledge Database allows you to save hints and help information related to a specific abort code and program These hints which can contain expressions making for very thorough explanations are automatically displayed the next time an abort occurs that has the identical conditions These hints will be displayed in the General Info window of The Visual Dump Analyzer Saving this valuable information makes analyzing future dumps of this type more accurate and effective Further this knowledge is automatically shared among all programmers a benefit especially helpful to those that are less experienced And finally as The Visual Dump Analyzer matures many dumps will have helpful notes readily available so the overall process of dump analysis will be more efficient Hints can be thought of as small views for the

User Guide GUI

Contents

Download Pdf Manuals

Related Search

Related Contents